DATA TRANSMISSION METHODS, DATA TRANSMISSION EQUIPMENT, COMPUTER-READABLE STORAGE MEDIA, AND CHIPS

Abstract

The invention relates to a method of data transmission, a data transmission apparatus, a computer-readable storage medium, and chips relating to the field of communication technology. The method of data transmission comprises the following steps: generating a first frame, which includes remapping reason information, and remapping reason information indicating the remapping reason; and transmitting the first frame. The reason information for establishing a mapping relationship between the traffic identifier and the link is carried in the radio frame, so that the responding terminal can quickly and accurately establish a mapping relationship between the traffic identifier and the link with the requesting terminal according to the reason information, thus avoiding signaling costs and delays caused by repeated negotiations.

Description

Data transmission method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 29, 2020, with application number 202011058049.4 and invention name “Data Transmission Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a data transmission method and apparatus. Background Art

[0003] With the development of wireless communication technology, more and more wireless communication devices support multi-link communication. For example, they support communication on multiple links in different communication frequency bands (such as 2.4 GHz, 5 GHz, 6 GHz, etc.), or support communication on different channels in the same communication frequency band, to improve the communication efficiency of the communication device. Among them, communication devices that support multi-link communication are called multi-link devices (MLDs). Multi-link devices include multi-link access points (APs) and multi-link stations (STAs).

[0004] Before a multi-link AP and a multi-link STA can communicate, they must establish multiple links. During this process, a mapping relationship can be established between traffic identifiers (TIDs) and links. This allows for better service management during subsequent multi-link communications. For example, different service identifiers can be mapped to corresponding links based on the link rate or service latency characteristics, thereby providing different QoS for different services.

[0005] During the process of establishing a mapping relationship between services and links, the requesting device (e.g., a multi-link AP or STA) sends the mapping relationship between services and links to the responding device (e.g., a multi-link AP or STA) based on its own link conditions and / or service requirements. However, this mapping relationship may not meet the responding device's requirements, resulting in a failure in establishing the mapping relationship.

[0006] It can be seen that multiple negotiations are required between the multi-link AP and the multi-link STA to successfully establish the mapping relationship between services and links. Therefore, how to quickly and effectively establish the mapping relationship between services and links is a technical problem that needs to be solved urgently.

[0007] Summary of the Invention

[0008] The present application provides a data transmission method and apparatus for carrying relevant auxiliary information for establishing a mapping relationship between a service identifier and a link in a wireless frame, so that a responding end device can quickly and accurately establish a mapping relationship between a service identifier and a link between a responding end device and a requesting end device based on the relevant auxiliary information, thereby avoiding signaling overhead and delay caused by repeated negotiations.

[0009] In a first aspect, a data transmission method is provided, the method comprising: generating a first frame, the first frame including remapping reason information, the remapping reason information being used to indicate a remapping reason; and sending the first frame.

[0010] The method may be executed by a first device (such as a multi-link AP or a multi-link STA), or by a component in the first device (such as a chip system).

[0011] Based on the above technical solution, the first device notifies the second device of the reason for initiating the establishment of a mapping relationship between a service identifier and a link. This allows the second device to establish the mapping relationship between the service identifier and the link based on the reason. This prevents TID-to-link mapping negotiation failures caused by the established mapping relationship not meeting the first device's requirements, thereby improving TID-to-link mapping negotiation efficiency.

[0012] In one possible implementation, the remapping reason information is carried in one or more of the following fields: the maximum number of links allowed to be opened field, the closed link set information field, the link quality report information field, and the service quality QoS report information field; among which, the maximum number of links allowed to be opened subfield is used to indicate the maximum number of links allowed to be opened; the closed link set information field is used to indicate the link set that needs to be closed; the link quality report information field is used to indicate link quality information; and the QoS report information field is used to indicate service quality information.

[0013] Optionally, the link quality information includes, for example, the following one or more items: a received signal strength indicator RSSI value, a signal to interference and noise ratio SINR value, indication information of whether the RSSI meets the first condition, and indication information of whether the SINR meets the second condition.

[0014] Optionally, the service quality information includes, for example, a QoS value, or indication information of whether the QoS satisfies the third condition.

[0015] In this way, different remapping reasons are carried in different fields, and after the responding end device receives the first frame, it can obtain the corresponding remapping reason in the corresponding field.

[0016] In one possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying remapping reason information appears in the first frame. The first indication information is carried in the control field, and the control field includes a first subfield, a second subfield, a third subfield, and a fourth subfield. Among them, the first subfield is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. The first subfield and / or the second subfield are used to indicate whether the closed link set information field appears in the first frame. The third subfield is used to indicate whether the link quality report information field appears in the first frame. The fourth subfield is used to indicate whether the QoS report information field appears in the first frame.

[0017] In this way, the remapping reason information contained in the first frame is indicated by the first subfield, the second subfield, the third subfield, and the fourth subfield. Based on the indication, the responding device can obtain the remapping reason in the corresponding field, thereby achieving fast negotiation of TID-to-link mapping.

[0018] In one possible implementation, the first frame includes first indication information, which is used to indicate whether the field carrying remapping reason information appears in the first frame. The first indication information is carried in the remapping reason field, and the first value and / or second value of the remapping reason field is used to indicate whether the shutdown link set information field appears in the first frame. The third value of the remapping reason field is used to indicate whether the link quality report information field appears in the first frame. The fourth value of the remapping reason field is used to indicate whether the QoS report information field appears in the first frame.

[0019] In a possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame. The first indication information is carried in the control field and the remapping reason field, and the control field includes a first subfield, a second subfield, a third subfield and a fourth subfield. Among them, the first subfield and the first value of the remapping reason field are used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. One or more of the first subfield, the second subfield, the first value of the remapping reason field, and the second value of the remapping reason field are used to indicate whether the closed link set information field appears in the first frame. The third subfield and the third value of the remapping reason field are used to indicate whether the received signal strength indication link quality report information field appears in the first frame. The fourth subfield and the fourth value of the remapping reason field are used to indicate whether the QoS report information field appears in the first frame.

[0020] In this way, through the indication of the first subfield, the second subfield, the third subfield, the fourth subfield, and the remapping reason field, double confirmation is performed to determine whether the first frame contains the closed link set information field, and / or the link quality report information field, and / or the QoS report information field, thereby improving the accuracy of the transmission of the remapping reason information.

[0021] It is understandable that only when the remapping reason information carried in the control field and the remapping reason field does not conflict with each other can a valid remapping reason be transmitted.

[0022] In one possible implementation, the method further includes: receiving a second frame, the second frame carrying second service identifier mapping information, the second service identifier mapping information is based on a remapping reason, and the second service identifier mapping information is used to indicate a second mapping relationship between the service identifier and the link.

[0023] Specifically, the second device determines a second mapping relationship between the service identifier and the link based on the first remapping reason and in combination with some of its own considerations, such as the requirement for the link transmission rate, and generates a second frame.

[0024] In one possible implementation, the second service identifier mapping information is carried in the service identifier and link mapping information field, and the service identifier and link mapping information field is used to indicate the second mapping relationship using the correspondence between the service identifier and the bitmap of the link. Alternatively, the service identifier and link mapping information field is used to indicate the second mapping relationship using the correspondence between the link identifier and the bitmap of the service identifier. Alternatively, the service identifier and link mapping information field includes a fifth subfield, and the fifth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bitmap of the link; and the sixth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the bitmap of the service identifier. Alternatively, the service identifier and link mapping information field includes a fifth subfield, the seventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the link bitmap; the eighth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the service identifier bitmap; the ninth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link bitmap and the service identifier bitmap. Alternatively, the service identifier and link mapping information field includes a fifth subfield, the tenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the link bitmap; the eleventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier bitmap and the link bitmap. Alternatively, the service identifier and link mapping information field includes a fifth subfield, and the twelfth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the link identifier and the bit map of the service identifier to indicate the second mapping relationship; the thirteenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the bit map of the link and the bit map of the service identifier to indicate the second mapping relationship.

[0025] In this way, through any of the above six methods, the service identifier mapping information can be flexibly transmitted, so that the responding end device can quickly learn the mapping relationship between the service identifier and the link and complete the TID-to-link mapping negotiation.

[0026] In a possible implementation manner, the second service identifier mapping information further carries the direction of the second mapping relationship between the service identifier and the link.

[0027] Optionally, the control field also includes a service identification direction subfield, which is used to indicate the direction of the service identification. For example, if the service identification direction subfield occupies 1 bit, it is used to indicate whether the TID is unidirectional or bidirectional. The direction indicated by unidirectional is the same as the TID direction corresponding to the device sending the first frame. Bidirectional includes uplink and downlink directions. For another example, if the service identification direction subfield occupies 2 bits, it is used to indicate whether the TID is uplink, downlink, or bidirectional. For example, 10 indicates the uplink direction, 01 indicates the downlink direction, 11 indicates bidirectional, and 00 is a reserved value.

[0028] In a possible implementation, the method further includes: sending a third frame, where the third frame is used to indicate a positive response or a negative response to the second frame.

[0029] That is, the third frame indicates whether the first device accepts the second mapping relationship, or indicates whether the second mapping relationship is successfully established.

[0030] In this way, after receiving the third frame, the second device can determine whether the TID-to-link mapping is successfully established.

[0031] In a possible implementation, the first frame further includes first service identifier mapping information, the first service identifier mapping information is based on a remapping reason, and the first service identifier mapping information is used to indicate a first mapping relationship between a service identifier and a link.

[0032] Optionally, the first device may first determine a mapping relationship between a set of service identifiers and links based on the remapping reason, and then the second device may choose to accept, modify or replace the mapping relationship to improve negotiation efficiency.

[0033] In a possible implementation, the method further includes: the second frame also carries a status code, where the status code is used to indicate whether the mapping relationship between the service identifier and the link is successfully established.

[0034] In a possible implementation, if the mapping relationship between the service identifier and the link fails to be established, the status code carries the reason for the failure.

[0035] In this way, the first device can determine whether the mapping relationship between the service identifier and the link is successfully established based on the status code. Further, if the establishment fails, it determines whether to accept the second service identifier mapping information.

[0036] In a possible implementation, the first frame also carries a remapping mode, where the remapping mode includes an immediate remapping mode or a delayed remapping mode.

[0037] The immediate remapping mode means that after the mapping relationship between the service identifier and the link is successfully negotiated, the service identifier and the link are immediately remapped according to the negotiated TID-to-link mapping. The delayed remapping mode means that after the mapping relationship between the service identifier and the link is successfully negotiated, the service identifier and the link are remapped according to the negotiated TID-to-link mapping after a period of time.

[0038] Specifically, some less capable devices may not be able to immediately move the MAC protocol data unit (MPDU) on one link to another for transmission, meaning they cannot immediately perform remapping. Therefore, a preset wait time is required. Accordingly, the remapping delay timer field in the first frame can also indicate the waiting time to ensure smooth remapping.

[0039] In a second aspect, a data transmission method is provided, the method comprising: receiving a first frame, the first frame including remapping reason information, the remapping reason information being used to indicate a remapping reason; and parsing the first frame.

[0040] In one possible implementation, the remapping reason information is carried in one or more of the following fields: the maximum number of links allowed to be opened field, the closed link set information field, the link quality report information field, and the service quality QoS report information field; among which, the maximum number of links allowed to be opened subfield is used to indicate the maximum number of links allowed to be opened; the closed link set information field is used to indicate the link set that needs to be closed; the link quality report information field is used to indicate link quality information; and the QoS report information field is used to indicate service quality information.

[0041] In one possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying remapping reason information appears in the first frame. The first indication information is carried in the control field, and the control field includes a first subfield, a second subfield, a third subfield, and a fourth subfield. Among them, the first subfield is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. The first subfield and / or the second subfield are used to indicate whether the closed link set information field appears in the first frame. The third subfield is used to indicate whether the link quality report information field appears in the first frame. The fourth subfield is used to indicate whether the QoS report information field appears in the first frame.

[0042] In one possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame. The first indication information is carried in the remapping reason field. The first value of the remapping reason field is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. The first value and / or second value of the remapping reason field is used to indicate whether the closed link set information field appears in the first frame. The third value of the remapping reason field is used to indicate whether the link quality report information field appears in the first frame. The fourth value of the remapping reason field is used to indicate whether the QoS report information field appears in the first frame.

[0043] In a possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame. The first indication information is carried in the control field and the remapping reason field, and the control field includes a first subfield, a second subfield, a third subfield and a fourth subfield. Among them, the first subfield and the first value of the remapping reason field are used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. One or more of the first subfield, the second subfield, the first value of the remapping reason field, and the second value of the remapping reason field are used to indicate whether the closed link set information field appears in the first frame. The third subfield and the third value of the remapping reason field are used to indicate whether the link quality report information field appears in the first frame. The fourth subfield and the fourth value of the remapping reason field are used to indicate whether the QoS report information field appears in the first frame.

[0044] In one possible implementation, the method further includes generating a second frame, the second frame carrying second service identifier mapping information, the second service identifier mapping information being based on a remapping reason and used to indicate a second mapping relationship between the service identifier and the link, and sending the second frame.

[0045] In one possible implementation, the second service identifier mapping information is carried in the service identifier and link mapping information field, and the service identifier and link mapping information field is used to indicate the second mapping relationship using the correspondence between the service identifier and the bitmap of the link. Alternatively, the service identifier and link mapping information field is used to indicate the second mapping relationship using the correspondence between the link identifier and the bitmap of the service identifier. Alternatively, the service identifier and link mapping information field includes a fifth subfield, and the fifth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bitmap of the link; and the sixth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the bitmap of the service identifier. Alternatively, the service identifier and link mapping information field includes a fifth subfield, the seventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the link bitmap; the eighth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the service identifier bitmap; the ninth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link bitmap and the service identifier bitmap. Alternatively, the service identifier and link mapping information field includes a fifth subfield, the tenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the link bitmap; the eleventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier bitmap and the link bitmap. Alternatively, the service identifier and link mapping information field includes a fifth subfield, and the twelfth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the link identifier and the bit map of the service identifier to indicate the second mapping relationship; the thirteenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the bit map of the link and the bit map of the service identifier to indicate the second mapping relationship.

[0046] In a possible implementation manner, the second service identifier mapping information further carries the direction of the second mapping relationship between the service identifier and the link.

[0047] In a possible implementation, the method further includes: receiving a third frame, where the third frame is used to indicate a positive response or a negative response to the second frame.

[0048] In a possible implementation, the first frame further includes first service identifier mapping information, the first service identifier mapping information is based on a remapping reason, and the first service identifier mapping information is used to indicate a first mapping relationship between a service identifier and a link.

[0049] In a possible implementation, the method further includes: the second frame also carries a status code, where the status code is used to indicate whether the mapping relationship between the service identifier and the link is successfully established.

[0050] In a possible implementation, if the mapping relationship between the service identifier and the link fails to be established, the status code carries the reason for the establishment failure.

[0051] In a possible implementation, the first frame also carries a remapping mode, where the remapping mode includes an immediate remapping mode or a delayed remapping mode.

[0052] In addition, the technical effects of the data transmission method of the second aspect can refer to the technical effects of the data transmission method of the first aspect, and will not be repeated here.

[0053] In a third aspect, a data transmission method is provided, comprising: sending a management frame and a target link identifier on a failed second link on a first link, wherein the target link identifier is used to instruct a receiving multi-link device MLD to forward the received management frame to a module corresponding to the target link identifier.

[0054] The management frame is a unicast management frame sent by the first device to a module in the second device. The target link identifier is used to point to the module. The module refers to a device in the MLD device. For example, it can be an AP in the AP MLD or a STA in the STA MLD.

[0055] Based on the above technical solution, using the target link identifier, when some links fail or are unreachable, the management frame that should be sent can be sent to the low MAC layer corresponding to the failed or unreachable link, avoiding the failure of management frame sending.

[0056] In a possible implementation, the method further includes: sending a reporting link identifier on the first link, where the reporting link identifier is used to instruct the receiving end MLD to send a response frame on the first link corresponding to the reporting link identifier.

[0057] In a possible implementation manner, the target link identifier and the reporting link identifier are carried in an aggregation control A-control field of a MAC frame.

[0058] Exemplarily, the management frame includes a reporting link ID and a destination link ID. The reporting link ID includes a reporting link ID, which indicates the ID of the link that actually sent the management frame. The destination link ID includes a destination link ID, which indicates the ID of the final link to which the frame needs to be forwarded.

[0059] In a possible implementation, the management frame, the target link identifier, and the reporting link identifier are carried in the frame body of the function frame.

[0060] Optionally, a new function frame is defined, in which a transparent management frame, a target link identifier, and a reporting link identifier are carried.

[0061] In a fourth aspect, a data transmission method is provided, comprising: receiving a management frame and a target link identifier on a failed second link on a first link, and determining, based on the target link identifier, to forward the received management frame to a module corresponding to the target link identifier.

[0062] In a possible implementation manner, a reporting link identifier is received on the first link, where the reporting link identifier is used to instruct to send a response frame on the first link corresponding to the reporting link identifier.

[0063] In a possible implementation manner, the target link identifier and the reporting link identifier are carried in an aggregation control A-control field of a MAC frame.

[0064] In a possible implementation, the management frame, the target link identifier, and the reporting link identifier are carried in the frame body of the function frame.

[0065] In addition, the technical effects of the data transmission method of the fourth aspect can refer to the technical effects of the data transmission method of the third aspect, and will not be repeated here.

[0066] In a fifth aspect, a data transmission device is provided, comprising a processing module and a communication module. The processing module is configured to generate a first frame, the first frame including remapping reason information indicating a remapping reason. The communication module is configured to send the first frame.

[0067] In one possible implementation, the remapping reason information is carried in one or more of the following fields: the maximum number of links allowed to be opened field, the closed link set information field, the link quality report information field, and the service quality QoS report information field; among which, the maximum number of links allowed to be opened subfield is used to indicate the maximum number of links allowed to be opened; the closed link set information field is used to indicate the link set that needs to be closed; the link quality report information field is used to indicate link quality information; and the QoS report information field is used to indicate service quality information.

[0068] In one possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying remapping reason information appears in the first frame. The first indication information is carried in the control field, and the control field includes a first subfield, a second subfield, a third subfield, and a fourth subfield. Among them, the first subfield is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. The first subfield and / or the second subfield are used to indicate whether the closed link set information field appears in the first frame. The third subfield is used to indicate whether the link quality report information field appears in the first frame. The fourth subfield is used to indicate whether the QoS report information field appears in the first frame.

[0069] In one possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame. The first indication information is carried in the remapping reason field. The first value of the remapping reason field is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. The first value and / or second value of the remapping reason field is used to indicate whether the closed link set information field appears in the first frame. The third value of the remapping reason field is used to indicate whether the link quality report information field appears in the first frame. The fourth value of the remapping reason field is used to indicate whether the QoS report information field appears in the first frame.

[0070] In a possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame. The first indication information is carried in the control field and the remapping reason field, and the control field includes a first subfield, a second subfield, a third subfield and a fourth subfield. Among them, the first subfield and the first value of the remapping reason field are used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. One or more of the first subfield, the second subfield, the first value of the remapping reason field, and the second value of the remapping reason field are used to indicate whether the closed link set information field appears in the first frame. The third subfield and the third value of the remapping reason field are used to indicate whether the link quality report information field appears in the first frame. The fourth subfield and the fourth value of the remapping reason field are used to indicate whether the QoS report information field appears in the first frame.

[0071] In one possible implementation, the communication module is also used to receive a second frame, which carries second service identifier mapping information. The second service identifier mapping information is based on the remapping reason, and the second service identifier mapping information is used to indicate a second mapping relationship between the service identifier and the link.

[0072] In one possible implementation, the second service identifier mapping information is carried in the service identifier and link mapping information field, and the service identifier and link mapping information field is used to indicate the second mapping relationship using the correspondence between the service identifier and the bitmap of the link. Alternatively, the service identifier and link mapping information field is used to indicate the second mapping relationship using the correspondence between the link identifier and the bitmap of the service identifier. Alternatively, the service identifier and link mapping information field includes a fifth subfield, and the fifth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bitmap of the link; and the sixth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the bitmap of the service identifier. Alternatively, the service identifier and link mapping information field includes a fifth subfield, the seventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the link bitmap; the eighth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the service identifier bitmap; the ninth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link bitmap and the service identifier bitmap. Alternatively, the service identifier and link mapping information field includes a fifth subfield, the tenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the link bitmap; the eleventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier bitmap and the link bitmap. Alternatively, the service identifier and link mapping information field includes a fifth subfield, and the twelfth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the link identifier and the bit map of the service identifier to indicate the second mapping relationship; the thirteenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the bit map of the link and the bit map of the service identifier to indicate the second mapping relationship.

[0073] In a possible implementation manner, the second service identifier mapping information further carries the direction of the second mapping relationship between the service identifier and the link.

[0074] In a possible implementation, the communication module is further configured to send a third frame, where the third frame is used to indicate a positive response or a negative response to the second frame.

[0075] In a possible implementation, the first frame further includes first service identifier mapping information, the first service identifier mapping information is based on a remapping reason, and the first service identifier mapping information is used to indicate a first mapping relationship between a service identifier and a link.

[0076] In a possible implementation, the method further includes: the second frame also carries a status code, where the status code is used to indicate whether the mapping relationship between the service identifier and the link is successfully established.

[0077] In a possible implementation, if the mapping relationship between the service identifier and the link fails to be established, the status code carries the reason for the failure.

[0078] In a possible implementation, the first frame also carries a remapping mode, where the remapping mode includes an immediate remapping mode or a delayed remapping mode.

[0079] Optionally, the communication module may include a receiving module and a sending module. The receiving module is used to receive data sent by other devices. The sending module is used to send data to other devices. The embodiments of this application do not specifically limit the specific implementation of the communication module.

[0080] Optionally, the communication device described in the fifth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the data transmission device described in the fifth aspect may execute the data transmission method described in the first aspect.

[0081] It should be noted that the data transmission device described in the fifth aspect can be an AP or a STA, or it can be a chip or chip system set in the AP or the STA, and this application does not limit this.

[0082] The technical effects of the data transmission device described in the fifth aspect can refer to the technical effects of the data transmission method described in the first aspect, and will not be repeated here.

[0083] In a sixth aspect, a data transmission device is provided, comprising a processing module and a communication module. The communication module is configured to receive a first frame, the first frame including remapping reason information indicating a remapping reason. The processing module is configured to parse the first frame.

[0084] In one possible implementation, the remapping reason information is carried in one or more of the following fields: the maximum number of links allowed to be opened field, the closed link set information field, the link quality report information field, and the service quality QoS report information field; among which, the maximum number of links allowed to be opened subfield is used to indicate the maximum number of links allowed to be opened; the closed link set information field is used to indicate the link set that needs to be closed; the link quality report information field is used to indicate link quality information; and the QoS report information field is used to indicate service quality information.

[0085] In one possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying remapping reason information appears in the first frame. The first indication information is carried in the control field, and the control field includes a first subfield, a second subfield, a third subfield, and a fourth subfield. Among them, the first subfield is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. The first subfield and / or the second subfield are used to indicate whether the closed link set information field appears in the first frame. The third subfield is used to indicate whether the link quality report information field appears in the first frame. The fourth subfield is used to indicate whether the QoS report information field appears in the first frame.

[0086] In one possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame. The first indication information is carried in the remapping reason field. The first value of the remapping reason field is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. The first value and / or second value of the remapping reason field is used to indicate whether the closed link set information field appears in the first frame. The third value of the remapping reason field is used to indicate whether the link quality report information field appears in the first frame. The fourth value of the remapping reason field is used to indicate whether the QoS report information field appears in the first frame.

[0087] In a possible implementation, the first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame. The first indication information is carried in the control field and the remapping reason field, and the control field includes a first subfield, a second subfield, a third subfield and a fourth subfield. Among them, the first subfield and the first value of the remapping reason field are used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. One or more of the first subfield, the second subfield, the first value of the remapping reason field, and the second value of the remapping reason field are used to indicate whether the closed link set information field appears in the first frame. The third subfield and the third value of the remapping reason field are used to indicate whether the link quality report information field appears in the first frame. The fourth subfield and the fourth value of the remapping reason field are used to indicate whether the QoS report information field appears in the first frame.

[0088] In one possible implementation, the processing module is further configured to generate a second frame, the second frame carrying second service identifier mapping information, the second service identifier mapping information being based on a remapping reason and indicating a second mapping relationship between the service identifier and the link. The communication module is further configured to send the second frame.

[0089] In one possible implementation, the second service identifier mapping information is carried in the service identifier and link mapping information field, and the service identifier and link mapping information field is used to indicate the second mapping relationship using the correspondence between the service identifier and the bitmap of the link. Alternatively, the service identifier and link mapping information field is used to indicate the second mapping relationship using the correspondence between the link identifier and the bitmap of the service identifier. Alternatively, the service identifier and link mapping information field includes a fifth subfield, and the fifth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bitmap of the link; and the sixth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the bitmap of the service identifier. Alternatively, the service identifier and link mapping information field includes a fifth subfield, the seventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the link bitmap; the eighth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the service identifier bitmap; the ninth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link bitmap and the service identifier bitmap. Alternatively, the service identifier and link mapping information field includes a fifth subfield, the tenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the link bitmap; the eleventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier bitmap and the link bitmap. Alternatively, the service identifier and link mapping information field includes a fifth subfield, and the twelfth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the link identifier and the bit map of the service identifier to indicate the second mapping relationship; the thirteenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the bit map of the link and the bit map of the service identifier to indicate the second mapping relationship.

[0090] In a possible implementation manner, the second service identifier mapping information further carries the direction of the second mapping relationship between the service identifier and the link.

[0091] In a possible implementation, the communication module is further configured to receive a third frame, where the third frame is used to indicate a positive response or a negative response to the second frame.

[0092] In a possible implementation, the first frame further includes first service identifier mapping information, the first service identifier mapping information is based on a remapping reason, and the first service identifier mapping information is used to indicate a first mapping relationship between a service identifier and a link.

[0093] In a possible implementation, the second frame also carries a status code, and the status code is used to indicate whether the mapping relationship between the service identifier and the link is successfully established.

[0094] In a possible implementation, if the mapping relationship between the service identifier and the link fails to be established, the status code carries the reason for the establishment failure.

[0095] In a possible implementation, the first frame also carries a remapping mode, where the remapping mode includes an immediate remapping mode or a delayed remapping mode.

[0096] Optionally, the communication module may include a receiving module and a sending module. The receiving module is used to receive data sent by other devices. The sending module is used to send data to other devices. The embodiments of this application do not specifically limit the specific implementation of the communication module.

[0097] Optionally, the communication device described in the sixth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the data transmission device described in the sixth aspect may execute the data transmission method described in the second aspect.

[0098] It should be noted that the data transmission device described in the sixth aspect can be an AP or a STA, or it can be a chip or chip system set in the AP or the STA, and this application does not limit this.

[0099] The technical effects of the data transmission device described in the sixth aspect can refer to the technical effects of the data transmission method described in the second aspect, and will not be repeated here.

[0100] In a seventh aspect, a data transmission apparatus is provided, comprising a communication module, wherein the communication module is configured to send, on a first link, a management frame and a target link identifier for a failed second link, wherein the target link identifier is configured to instruct a receiving multi-link device (MLD) to forward the received management frame to a module corresponding to the target link identifier.

[0101] In a possible implementation, the communication module is further configured to send a reporting link identifier on the first link, where the reporting link identifier is used to instruct the receiving end MLD to send a response frame on the first link corresponding to the reporting link identifier.

[0102] In a possible implementation manner, the target link identifier and the reporting link identifier are carried in an aggregation control A-control field of a MAC frame.

[0103] In a possible implementation, the management frame, the target link identifier, and the reporting link identifier are carried in the frame body of the function frame.

[0104] Optionally, the communication module may include a receiving module and a sending module. The receiving module is used to receive data sent by other devices. The sending module is used to send data to other devices. The embodiments of this application do not specifically limit the specific implementation of the communication module.

[0105] Optionally, the communication device described in the seventh aspect may further include a processing module and a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the data transmission device described in the seventh aspect may execute the data transmission method described in the third aspect.

[0106] It should be noted that the data transmission device described in the seventh aspect can be an AP or a STA, or it can be a chip or chip system set in the AP or the STA, and this application does not limit this.

[0107] The technical effects of the data transmission device described in the seventh aspect can refer to the technical effects of the data transmission method described in the third aspect, and will not be repeated here.

[0108] In an eighth aspect, a data transmission device is provided, comprising a processing module and a communication module. The communication module is configured to receive, on a first link, a management frame and a target link identifier from a failed second link. The processing module is configured to determine, based on the target link identifier, whether to forward the received management frame to a module corresponding to the target link identifier.

[0109] In a possible implementation, the communication module is further configured to receive a reporting link identifier on the first link, where the reporting link identifier is used to instruct to send a response frame on the first link corresponding to the reporting link identifier.

[0110] In a possible implementation manner, the target link identifier and the reporting link identifier are carried in an aggregation control A-control field of a MAC frame.

[0111] In a possible implementation, the management frame carries the target link identifier and the reporting link identifier in the frame body of the function frame.

[0112] Optionally, the communication module may include a receiving module and a sending module. The receiving module is used to receive data sent by other devices. The sending module is used to send data to other devices. The embodiments of this application do not specifically limit the specific implementation of the communication module.

[0113] Optionally, the communication device described in the eighth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the data transmission device described in the eighth aspect may execute the data transmission method described in the fourth aspect.

[0114] It should be noted that the data transmission device described in the eighth aspect can be an AP or a STA, or it can be a chip or chip system set in the AP or the STA, and this application does not limit this.

[0115] The technical effects of the data transmission device described in the eighth aspect can refer to the technical effects of the data transmission method described in the fourth aspect, and will not be repeated here.

[0116] In a ninth aspect, a data transmission device is provided, comprising a processor and a transceiver, wherein the processor and the transceiver are configured to implement any one of the methods provided in any one of the first to fourth aspects. The processor is configured to perform the processing actions in the corresponding method, and the transceiver is configured to perform the receiving / sending actions in the corresponding method.

[0117] In a tenth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions. When the computer instructions are executed on a computer, the computer executes any one of the methods provided in any one of the first to fourth aspects.

[0118] In an eleventh aspect, a computer program product comprising computer instructions is provided. When the computer instructions are executed on a computer, the computer is caused to execute any one of the methods provided in any one of the first to fourth aspects.

[0119] In a twelfth aspect, a chip is provided, comprising: a processing circuit and a transceiver pin, wherein the processing circuit and the transceiver pin are configured to implement any one of the methods provided in any one of the first to fourth aspects. The processing circuit is configured to perform the processing actions in the corresponding method, and the transceiver pin is configured to perform the receiving / transmitting actions in the corresponding method. BRIEF DESCRIPTION OF THE DRAWINGS

[0120] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0121] FIG2 is a second schematic diagram of a communication system provided in an embodiment of the present application;

[0122] FIG3 is a schematic diagram of a frame structure of a multi-link information unit provided in an embodiment of the present application;

[0123] FIG4 is a schematic diagram of a frame structure of a target wake-up time unit provided in an embodiment of the present application;

[0124] FIG5 is a schematic diagram of the frame format of the first frame provided in an embodiment of the present application;

[0125] FIG6 is a schematic diagram of a frame structure of a service identifier and link mapping information field according to an embodiment of the present application;

[0126] FIG7 is a second schematic diagram of a frame structure of a service identifier and link mapping information field provided in an embodiment of the present application;

[0127] FIG8 is a third schematic diagram of a frame structure of a service identifier and link mapping information field provided in an embodiment of the present application;

[0128] FIG9 is a fourth schematic diagram of a frame structure of a service identifier and link mapping information field provided in an embodiment of the present application;

[0129] FIG10 is a flowchart of a data transmission method according to an embodiment of the present application;

[0130] FIG11 is a second flow chart of a data transmission method according to an embodiment of the present application;

[0131] FIG12 is a third flow chart of a data transmission method according to an embodiment of the present application;

[0132] FIG13 is a schematic structural diagram of an AP MLD and a STA MLD participating in communication according to an embodiment of the present application;

[0133] FIG14 is a fourth flow chart of a data transmission method according to an embodiment of the present application;

[0134] FIG15 is a schematic diagram of a frame format of a transparently transmitted management frame provided in an embodiment of the present application;

[0135] FIG16 is a schematic structural diagram of a data transmission device provided in an embodiment of the present application;

[0136] FIG17 is a schematic structural diagram of another data transmission device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0137] In the description of this application, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, "at least one" means one or more, and "a plurality" means two or more. Words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not limit them to be necessarily different.

[0138] In this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0139] First, as shown in Table 1 below, the abbreviations of the terms involved in this application are introduced.

[0140] Table 1

[0141]

[0142]

[0143] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application. For example, the communication system adopts a system based on the IEEE 802.11 standard. Exemplarily, the IEEE 802.11 standard includes, but is not limited to, the 802.11be standard or a later generation 802.11 standard. The technical solution of the present application is applicable to scenarios including: communication between APs and STAs, communication between APs, and communication between STAs. As shown in FIG1 , the communication system includes at least one multi-link AP 100 and at least one multi-link STA 200. For example, the multi-link STA 200 includes multi-link STA 1, multi-link STA 2, and multi-link STA 3.

[0144] Optionally, the STA involved in the embodiments of the present application may be various user terminals, user devices, access devices, user stations, user units, mobile stations, user agents, user equipment or other names with wireless communication functions, wherein the user terminals may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions, as well as various forms of user equipment (UE), mobile stations (MS), terminals, terminal equipment, portable communication devices, handheld devices, portable computing devices, entertainment devices, gaming devices or systems, global positioning system devices or any other suitable devices configured to communicate over a wireless medium. Here, for the convenience of description, the above-mentioned devices are collectively referred to as stations, or STAs, or multi-link STAs, or multi-link STA devices, or STA MLDs, or non-access point stations (non-AP STAs), or non-AP MLDs.

[0145] Optionally, the access point AP involved in the embodiments of the present application is a device deployed in a wireless communication network to provide wireless communication functions for its associated STAs. The access point AP can serve as the hub of the communication system and can be a communication device such as a base station, router, gateway, repeater, communication server, switch, or bridge. The base station can include various forms of macro base stations, micro base stations, relay stations, etc. Here, for the convenience of description, the above-mentioned devices are collectively referred to as access points AP, or multi-link AP, or multi-link AP devices, or AP MLDs.

[0146] To facilitate understanding, the following first introduces relevant terms and concepts that may be involved in the embodiments of this application.

[0147] 1)Multi-link communication

[0148] With the development and evolution of cellular networks and WLANs, MLDs are able to send and receive data over multiple links. Multilinks can be deployed on multiple frequency bands, where one frequency band can have one or more links. These frequency bands include, but are not limited to, the 2.4 GHz Wi-Fi band, the 5 GHz Wi-Fi band, and the 6 GHz Wi-Fi band. Furthermore, MLDs can communicate over multiple channels on the same frequency band. These multiple frequency bands or channels are collectively referred to as multilinks. Multilink communication improves peak throughput, reduces service transmission latency, and thus increases the communication rate between MLDs.

[0149] For example, as shown in Figure 2, a multi-link AP includes M APs, such as AP#1 to AP#M. The M APs correspond one-to-one to the M links supported by the multi-link AP. A multi-link STA includes N STAs, such as STA#1 to STA#N. The N STAs correspond one-to-one to the N links supported by the multi-link STA. M and N are both integers greater than 1. M may or may not be equal to N.

[0150] A STA operating on a link in a multi-link STA can associate with an AP operating on the same link in a multi-link AP, allowing the STA and AP to communicate over that link. For example, STA#1 in a multi-link STA associates with AP#1 in a multi-link AP, allowing communication between STA#1 and AP#1 over link 1. STA#2 in a multi-link STA associates with AP#2 in a multi-link AP, allowing communication between STA#2 and AP#2 over link 2. STA#3 in a multi-link STA associates with AP#3 in a multi-link AP, allowing communication between STA#3 and AP#3 over link 3. This process continues in this order and is not further detailed.

[0151] Furthermore, the links between a multi-link STA and a multi-link AP can be deployed on the same or different frequency bands. For example, if link 1 is deployed on the 2.4 GHz Wi-Fi band, AP#1 will operate on the 2.4 GHz Wi-Fi band. If link 2 is deployed on the 5 GHz Wi-Fi band, AP#2 will operate on the 5 GHz Wi-Fi band. If link 3 is deployed on the 6 GHz Wi-Fi band, AP#3 will operate on the 6 GHz Wi-Fi band.

[0152] In the embodiment of the present application, the AP / STA corresponding to the link can be described as: the AP / STA working on the link.

[0153] It is understandable that a multi-link device can communicate with other devices. In the embodiment of the present application, the other devices may be multi-link devices or may not be multi-link devices.

[0154] 2) Multi-link establishment

[0155] Before a multi-link STA and a multi-link AP begin multi-link communication, the STA can send an association request frame to the AP. This frame carries information about the STA's multilinks. After receiving the association request frame, the AP sends an association response frame to the STA, which carries information about the AP's multilinks. This exchange of multi-link information establishes multi-links between the STA and the AP, enabling multi-link communication over these established links.

[0156] Exemplarily, multilink information can be carried using a multilink information element (ML element). Figure 3 shows a schematic diagram of the frame structure of a multilink information element. As shown in Figure 3, the multilink information element includes: an element ID field, a length field, an element ID extension field, a control field, a multilink device common information (MLD common info) field, and zero or more link profile subelement fields.

[0157] The Multilink Device Common Information field carries the MLD's common information for all multilinks. For example, this common information includes the MLD's MAC address. Each Link Information subunit carries specific information for each link. For example, specific information includes the capabilities of the MLD's site on each link.

[0158] 3) Uplink and downlink

[0159] The uplink direction refers to the transmission direction in which the STA sends data to the AP.

[0160] The downlink direction refers to the transmission direction in which the AP sends data to the STA.

[0161] Exemplarily, as shown in FIG2 , the transmission direction in which STA#1 sends data to AP#1 is the uplink direction, and the transmission direction in which AP#2 sends data to STA#2 is the downlink direction.

[0162] 4) TID-to-link mapping

[0163] With the development of communication technology, multi-link technology can support an increasing number of services. To better manage services, mappings can be established between services and links to provide differentiated services for different services. By presetting service identifiers corresponding to the services, the mapping between services and links can be implemented as a mapping between service identifiers and links.

[0164] For example, the service identifiers of non-critical services can be mapped to some links, while the service identifiers of critical services can be mapped to all links to improve the efficiency and accuracy of critical service execution. Alternatively, the service identifiers of different services can be mapped to corresponding links based on the rates of different links and the latency characteristics of the services.

[0165] In some scenarios, during the process of establishing multiple links, a mapping relationship between service identifiers and links is established.

[0166] If, during the process of establishing multiple links, no operation is performed to establish a mapping relationship between service identifiers and links, it is assumed that all service identifiers are mapped to each established link.

[0167] In other scenarios, after multi-link establishment, due to reasons such as device mobility or service changes, it may be necessary to remap service identifiers to links. This remapping relationship should be established to meet current service requirements. For example, if a STA MLD moves to the edge of the AP's signal coverage area, causing latency-sensitive services on certain links to not meet QoS requirements, the mapping relationship between service identifiers and links needs to be re-established to reduce service transmission latency.

[0168] The device requesting to establish the mapping between the service identifier and the link may be a STA MLD or an AP SLD.

[0169] 5) Target wake time (TWT) negotiation

[0170] The IEEE 802.11ax standard proposes that STA and AP determine the same TWT parameters, such as a schedule, through TWT negotiation. The schedule includes a sleep cycle, such as a beacon cycle. After TWT negotiation, the STA can periodically sleep and wake up according to the sleep cycle to achieve energy saving. During the TWT negotiation process, the STA can act as a requesting device that initiates TWT negotiation and initiate a TWT negotiation request to the AP that acts as a responding device. Alternatively, the AP can act as a requesting device that initiates TWT negotiation and initiate a TWT negotiation request to the STA that acts as a responding device.

[0171] Among them, during the TWT negotiation process, the request method of the requesting end device includes any of the following: requesting TWT parameters, suggesting TWT parameters, and requiring TWT parameters. The requesting end device will perform different operations according to different request methods based on its own needs, and send the corresponding TWT negotiation request to the responding end device. After receiving the TWT negotiation request, the responding end device will perform corresponding operations according to different request methods. As shown in Table 2 below, the operations performed by the requesting end device and the responding end device under different request methods are shown.

[0172] Table 2

[0173]

[0174] Accordingly, the operation performed by the responding end device corresponds to any of the following response modes: accept TWT parameters, change TWT parameters, specify TWT parameters, and reject TWT parameters. As shown in Table 3 below, the specific operations that the responding end device needs to perform under different response modes are shown.

[0175] Table 3

[0176]

[0177]

[0178] Exemplarily, FIG4 shows a schematic diagram of a frame structure of a TWT unit (element). As shown in FIG4 , the TWT unit includes an element identification (element ID) field, a length (length) field, a TWT request (TWT request) field, and a TWT setup command (TWT setup command) field. Among them, the TWT request field occupies 1 bit and is used to indicate the type of device sending the TWT unit. For example, when the TWT request field takes a value of 1, it indicates that the device sending the TWT unit is a requesting end device; when the TWT request field takes a value of 0, it indicates that the device sending the TWT unit is a responding end device. The TWT setup command field occupies 3 bits and is used to indicate the type of TWT establishment, as shown in Table 4 below, which shows the command names corresponding to different values ​​of the TWT setup command field, as well as the corresponding operations that need to be performed when acting as a requesting end device or a sending site in the TWT negotiation process.

[0179] Table 4

[0180]

[0181] It should be noted that in Table 4 above, N / A means not applicable.

[0182] The above is an introduction to the relevant terms and concepts involved in the embodiments of this application, which will not be repeated below.

[0183] In the prior art, some solutions propose to use the above-mentioned TWT negotiation rules to exchange TID-to-link mapping between the requesting device and the responding device, so as to establish a mapping relationship between the service identifier and the link between the requesting device and the responding device, thereby improving service efficiency.

[0184] However, directly applying the TWT negotiation rules to the scenario of establishing a mapping relationship between a service identifier and a link, based on Tables 2 to 4 above, problems may arise in at least the following negotiation scenarios:

[0185] (1) The request method is to suggest TID-to-link mapping parameters, and the response method is to change TID-to-link mapping parameters.

[0186] For example, the requesting end device is congested on link 1 due to too much business being carried. After mapping some of the business identifiers on link 1 to other links, it obtains mapping relationship 1, initiates a remapping negotiation request to the responding end device, and sends mapping relationship 1 to the responding end device. After receiving mapping relationship 1, the responding end device, because it does not know the reason why the requesting end device requires remapping, will modify some or all of the mapping relationships in mapping relationship 1 according to its own needs, and may still map some of the business identifiers to link 1 to obtain mapping relationship 2. After receiving mapping relationship 2, the requesting end device determines that mapping relationship 2 cannot be implemented, and it needs to send the updated mapping relationship to the responding end device again for negotiation. In this way, after multiple negotiations, the requesting end device and the responding end device can re-establish the mapping relationship between the business identifier and the link, which is inefficient.

[0187] (2) The request method is to request TID-to-link mapping parameters or suggest TID-to-link mapping parameters, and the response method is to specify TID-to-link mapping parameters.

[0188] In the current scenario, the mapping relationship specified by the responding device may not be applicable to the link and service conditions of the requesting device, which will cause the negotiation to fail.

[0189] Therefore, if the requesting device and the responding device do not know each other's mapping reason during the TID-to-link mapping negotiation process, multiple negotiations are required, resulting in low negotiation efficiency; or negotiation failure may occur, affecting service execution efficiency.

[0190] To address this technical issue, a first frame is proposed for establishing a mapping relationship between a service identifier and a link. This first frame can trigger a TID-to-link mapping negotiation process with a responding device. This first frame includes remapping reason information. Upon receiving the first frame, the responding device can determine the remapping reason indicated by the requesting device based on the remapping reason information, improving negotiation efficiency.

[0191] The first frame may also be referred to as a TID-to-link mapping setup frame. It should be understood that the first frame may be aggregated or carried in the transmitted data. The remapping reason information may also be referred to as auxiliary information, primarily used to assist in determining the TID-to-link mapping.

[0192] The requesting device sending the first frame can be a STA MLD or an AP MLD. The reasons for initiating TID-to-link mapping negotiation for STA MLD and AP MLD may be the same or different. Therefore, before describing the format of the first frame, we first explain the reasons for initiating TID-to-link mapping negotiation for STA MLD and AP MLD.

[0193] For STA MLD, TID-to-link mapping negotiation may be initiated for the following reasons:

[0194] Cause 1: The link fails or is unreachable.

[0195] For example, if a STA MLD moves beyond the signal coverage of an AP, some downlink data may be unreachable, or both uplink and downlink data may be unreachable. For example, as shown in Figure 2, if a STA MLD moves beyond the coverage of AP#1, data transmitted on link 1 may be unreachable.

[0196] It should be noted that link unreachability is a strong constraint during TID-to-link mapping negotiation. This means that if a TID-to-link mapping negotiation is initiated due to link unreachability, the responding device cannot modify the service identifier to map to the unreachable link, thereby preventing TID-to-link mapping negotiation failure.

[0197] Reason 2: Delay-sensitive services do not meet QoS requirements.

[0198] For example, if the amount of data carried by a link is too large, causing the QoS of some delay-sensitive services carried on it to fail to meet the QoS requirements, the service identifiers of these delay-sensitive services need to be mapped to a link that can guarantee better QoS.

[0199] Reason 3: Energy saving.

[0200] For example, if the STA MLD closes one or more links for energy saving, the service identifiers corresponding to the links to be closed need to be remapped to new links.

[0201] It should be noted that if the reason for the STA MLD to initiate TID-to-link mapping negotiation is energy saving, the responding device should accept the TID-to-link mapping.

[0202] For AP MLD, TID-to-link mapping negotiation may be initiated for the following reasons:

[0203] Reason 1: Load balancing.

[0204] For example, if AP MLD determines that the load on the current link is unbalanced, it will adjust the services carried on the link and remap some services on the overly congested link to other links with lighter loads to achieve load balancing and improve service efficiency.

[0205] Reason 2: Reduce the transmission latency of sensitive services.

[0206] For example, AP MLD remaps non-sensitive traffic on link 1 to other links, thereby reducing the transmission latency of sensitive traffic on link 1.

[0207] Reason three: access control.

[0208] For example, AP MLD manages STAs connected to each AP device based on the STA type or capabilities. STA capabilities include the number of supported transmit and receive streams, whether the links corresponding to multi-link devices support simultaneous transmit and receive (STR) data, and whether the links corresponding to multi-link devices support shared transmit and receive chains (Tx / Rx chains).

[0209] Based on the reasons for initiating the TID-to-link mapping negotiation between the STA MLD and AP MLD, the following Table 5 provides exemplary information that may be included in the first frame. The Maximum Number of Links Allowed to Open element, the Link Quality Report element, the QoS Report element, and the Closed Link Set element correspond to the reasons for the TID-to-link mapping negotiation and are optional elements. The information included in the first frame may include one or more of these elements. Optionally, an indication field is provided in the first frame to indicate whether the Maximum Number of Links Allowed to Open element, the Link Quality Report element, the QoS Report element, and the Closed Link Set element are included in the first frame.

[0210] Table 5

[0211] Sequence information: 1 Category field 2 Multi-link action field 3 Dialog token 4 TID-to-link mapping element 5 Maximum number of enabled links element 6 Link quality report element 7 QoS report element 8 Disable link set element

[0212] Optionally, Figure 5 shows a schematic diagram of a frame format of a first frame. As shown in Figure 5, the first frame includes an element ID field, a length field, a control field, a remapping reason field, a maximum number of enabled links field, a disable link set info field, a link quality report info field, a QoS report info field, a service identifier and link mapping information (TID-to-link mapping info) field, and a remapping delay timer field.

[0213] Optionally, the first frame includes remapping reason information, where the remapping reason information is used to indicate the remapping reason.

[0214] The remapping reason information is carried in one or more of the following fields: the maximum number of links allowed to be opened field, the closed link set information field, the link quality report information field, and the service quality QoS report information field. In other words, the remapping reason information contained in the first frame can be indicated by using one or more of the following fields: the maximum number of links allowed to be opened field, the closed link set information field, the link quality report information field, and the QoS report information field.

[0215] In some embodiments, the Maximum Links Allowed field is used to indicate the maximum number of links currently allowed to be opened by the device sending the first frame. For example, when the STA MLD needs to save energy, the Maximum Links Allowed field can be used to indicate the maximum number of links allowed to be opened.

[0216] In some embodiments, the closed link set information field is used to indicate the link set that needs to be closed, corresponding to remapping reasons such as link failure, link unreachability, access control, load balancing, etc.

[0217] In some embodiments, the link quality report information field is used to indicate the link quality of the link, and the link quality report information field carries link quality information.

[0218] Exemplarily, the link quality information includes one or more of the following: an RSSI value, a SINR value, an indication of whether the RSSI meets a first condition, and an indication of whether the SINR meets a second condition. The RSSI value may be an uplink RSSI value, a downlink RSSI value, or may include both uplink and downlink RSSI values. The RSSI value may be an RSSI value measured by a STA based on beacon frames, or may be determined based on the difference between the transmit power of the AP and the transmit power of the STA when sending beacon frames. The first condition is used to measure whether the link is reachable. For example, if the RSSI meets the first condition, the link is reachable, and the corresponding indication is that the link is reachable. For another example, if the RSSI does not meet the first condition, the link is unreachable, and the corresponding indication is that the link is unreachable. The SINR value may be an uplink SINR value, a downlink SINR value, or may include both uplink and downlink SINR values. The second condition is used to measure whether the link is reachable. For example, if the SINR meets the second condition, the link is reachable, and the corresponding indication is that the link is reachable. For another example, if the SINR does not meet the second condition, the link is unreachable, and the corresponding indication information indicates that the link is unreachable.

[0219] In some embodiments, the QoS report information field is used to indicate the service quality of the corresponding service identifier. The QoS report information field carries service quality information.

[0220] Exemplarily, the service quality information includes, for example, a QoS value, or information indicating whether the QoS meets the third condition. The QoS value includes, for example, average packet latency, latency jitter, average rate, etc. The second condition may be whether the QoS requirement is met. For example, if the QoS meets the second condition, then the QoS requirement is met, and the corresponding indication information indicates that the service identifier meets the QoS requirement. For another example, if the QoS does not meet the second condition, then the QoS requirement is not met, and the corresponding indication information indicates that the service identifier does not meet the QoS requirement.

[0221] Optionally, the first frame includes first indication information, which is used to indicate whether the field carrying remapping reason information appears in the first frame. The first indication information can be carried in the control field, or in the remapping reason field, or in both the control field and the remapping reason field. The following describes three indication methods for carrying the first indication information in different fields.

[0222] Method 1: The first indication information is carried in the control field.

[0223] Exemplarily, as shown in FIG5 , the control field includes a first subfield, a second subfield, a third subfield, and a fourth subfield. The first subfield may be the current maximum number of enabled links present subfield, which occupies one bit and is used to indicate whether the maximum number of enabled links field appears in the first frame. The second subfield may be the current disabled link set information subfield, which occupies one bit and is used to indicate whether the disabled link set information field appears in the first frame. The third subfield may be the current link quality information subfield, which occupies one bit and is used to indicate whether the link quality report information field appears in the first frame. The fourth subfield may be the current QoS information subfield, which occupies one bit and is used to indicate whether the QoS report information field appears in the first frame.

[0224] For example, the first field is used to indicate the maximum number of links allowed to be opened and the set of links that need to be closed. For another example, the first field and the second field are used to indicate the set of links that need to be closed.

[0225] In this way, the remapping reason information contained in the first frame is indicated by the first, second, third, and fourth subfields. Based on the indication, the responding device can obtain the remapping reason in the corresponding field, thereby achieving rapid negotiation of TID-to-link mapping.

[0226] In another possible design, if the number of bits required to indicate the maximum number of links allowed to be opened is small, the Maximum Number of Links Allowed to Be Opened field can be used as a subfield of the control field, and the maximum number of links allowed to be opened can be directly indicated in the Maximum Number of Links Allowed to Be Opened subfield of the control field. For example, the Maximum Number of Links Allowed to Be Opened subfield occupies 4 bits. Accordingly, the control field does not need to include the Current Maximum Number of Links Allowed to Be Opened subfield.

[0227] In some embodiments, as shown in FIG5 , the control field further includes other subfields, such as a service identification mapping request (TID mapping request) subfield, a service identification mapping command (TID mapping command) subfield, a service identification mapping mode (TID mapping mode) subfield, and a reserved (reserved) subfield.

[0228] The Service Identification Mapping Request subfield occupies one bit and is used to indicate whether the device sending the first frame is a requesting device or a responding device. For example, when the Service Identification Mapping Request subfield has a value of 1, it indicates that the device currently sending the first frame is a requesting device. For another example, when the Service Identification Mapping Request subfield has a value of 0, it indicates that the device currently sending the first frame is a responding device.

[0229] The service identifier mapping command subfield occupies 3 bits and is used to indicate the type of TID-to-link mapping negotiation. As shown in Table 6 below, when the service identifier mapping command subfield takes different values, the corresponding command meanings are different for different site devices. For example, when the device sending the first frame is the requesting device, when the service identifier mapping command subfield takes the value of 0, it is used to indicate the request for TID-to-link mapping parameters, and the first frame does not carry the TID-to-link mapping parameters. For another example, when the device sending the first frame is the responding device, when the service identifier mapping command subfield takes the value of 4, it is used to indicate that the first frame carries the replaced TID-to-link mapping parameters. The TID-to-link mapping parameters include the mapping relationship between the service identifier and the link.

[0230] Table 6

[0231]

[0232] The service identifier mapping mode subfield occupies 1 bit and is used to indicate the remapping mode, which includes an immediate remapping mode or a delayed remapping mode. Among them, the immediate remapping mode means that after the mapping relationship between the service identifier and the link is successfully negotiated, remapping is performed immediately according to the negotiated TID-to-link mapping. The delayed remapping mode means that after the mapping relationship between the service identifier and the link is successfully negotiated, remapping is performed according to the negotiated TID-to-link mapping after waiting for a period of time. Specifically, for some devices with weaker capabilities, it may not be possible to immediately move the protocol data unit (MAC protocol data unit MAC, MPDU) on one link to another link for transmission, that is, remapping cannot be performed immediately. Therefore, a preset waiting time is required. Accordingly, the waiting time can also be indicated by the remapping delay timer field in the first frame to ensure that the remapping is completed smoothly.

[0233] Method 2: The first indication information is carried in the remapping reason field.

[0234] The first value of the Remapping Reason field indicates whether the Maximum Number of Links Allowed to Be Opened field appears in the first frame. The first and / or second values ​​of the Remapping Reason field indicate whether the Closed Link Set Information field appears in the first frame. The third value of the Remapping Reason field indicates whether the Link Quality Report Information field appears in the first frame. The fourth value of the Remapping Reason field indicates whether the QoS Report Information field appears in the first frame.

[0235] That is, the remapping reason field can indicate whether the first frame includes the maximum number of links allowed to be opened field, and / or the closed link set information field, and / or the link quality report information field, and / or the QoS report information field.

[0236] Optionally, the remapping reason field can also be used to indicate the remapping reason. As shown in Table 7 below, some remapping reasons corresponding to the values ​​of the remapping reason field are exemplarily shown. It is understandable that other remapping reasons may also be included, which will not be repeated here.

[0237] Table 7

[0238] Remapping reason field value Remapping reason 0 Link failure or link unreachable 1 Delay-sensitive services do not meet QoS requirements 2 Energy saving 3 Load balancing 4 Reduce transmission latency of sensitive services 5 Access control

[0239] Mode 3: The first indication information is carried in the control field and the remapping reason field.

[0240] Among them, as described above for method one, the control field includes a first subfield, a second subfield, a third subfield, and a fourth field. The first subfield and the first value of the remapping reason field are used to indicate whether the maximum number of links allowed to be opened field appears in the first frame. One or more of the first subfield, the second field, the first value of the remapping reason field, and the second value of the remapping reason field are used to indicate whether the closed link set information field appears in the first frame. The third subfield and the third value of the remapping reason field are used to indicate whether the link quality report information field appears in the first frame. The fourth subfield and the fourth value of the remapping reason field are used to indicate whether the QoS report information field appears in the first frame.

[0241] The above double confirmation through the first subfield, the second subfield, the third subfield, the fourth subfield, and the indication of the remapping reason field further determines whether the first frame contains the maximum number of links allowed to be opened field, and / or the closed link set information field, and / or the link quality report information field, and / or the QoS report information field, thereby improving the accuracy of the transmission of the remapping reason information. It can be understood that the first indication information carried in the control field and the remapping reason field does not conflict, that is, the indicated remapping reasons do not conflict, in order to achieve the transmission of a valid remapping reason.

[0242] In this way, through any of the above three methods, the remapping reason is sent to the responding end device, so that the responding end device can quickly identify the remapping reason and complete the TID-to-link mapping negotiation.

[0243] Optionally, the first frame may also carry service identifier mapping information, which is based on the remapping reason and is used to indicate the mapping relationship between the service identifier and the link. As shown in Table 6 above, based on the indication of the service identifier mapping command subfield, it is determined that the TID-to-link mapping parameter needs to be provided, and the service identifier mapping information is carried in the first frame.

[0244] In some embodiments, the service identifier mapping information is carried in the service identifier and link mapping information field, and the service identifier and link mapping information field indicates the mapping relationship between the service identifier and the link in at least the following six ways.

[0245] Mode 1: The service identifier and link mapping information field is used to indicate the mapping relationship between the service identifier and the link by using the corresponding relationship between the service identifier and the link bitmap.

[0246] Exemplarily, the number of bits in the link bitmap is P times the number of links, where P is a positive integer. A bit value of 1 indicates that the corresponding link is included in the correspondence; a bit value of 0 indicates that the corresponding link is not included in the correspondence. Assume that there are 3 links, namely link 1, link 2, and link 3. If P = 1, the number of bits is 3. For example, a bitmap of 001 represents link 3. For another example, a bitmap of 101 represents link 1 and link 3.

[0247] Then, by establishing a correspondence between the service identifier and the link bitmap, the mapping relationship between the service identifier and the link is indicated. For example, if the service identifier and link mapping information field indicates that TID3 has a correspondence with the link bitmap 011, it means that TID3 is mapped to link 2 and link 3.

[0248] Mode 2: The service identifier and link mapping information field is used to indicate the mapping relationship between the service identifier and the link by using the corresponding relationship between the bitmap of the link identifier and the service identifier.

[0249] Exemplarily, the number of bits in the bitmap of the service identifier is Q times the number of TIDs, where Q is a positive integer. A bit value of 1 indicates that the corresponding service identifier is included in the correspondence; a bit value of 0 indicates that the corresponding service identifier is not included in the correspondence. Assume that there are 8 TIDs, namely TID0-TID7. If Q = 1, the number of bits is 8. For example, a bitmap of 10000000 represents TID0. For another example, a bitmap of 00011000 represents TID3 and link TID4.

[0250] Then, by establishing a correspondence between the link identifier and the bitmap of the service identifier, the mapping relationship between the service identifier and the link is indicated. For example, if the service identifier and link mapping information field indicates that link 1 has a correspondence with the bitmap of the service identifier 10000000, it means that TID0 is mapped to link 1.

[0251] Mode 3: The service identifier and link mapping information field includes a fifth subfield. The fifth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the corresponding relationship between the service identifier and the link bitmap to indicate the mapping relationship between the service identifier and the link. The sixth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the corresponding relationship between the link identifier and the service identifier bitmap to indicate the mapping relationship between the service identifier and the link.

[0252] For example, Figure 6 shows a schematic diagram of the frame structure of the service identifier and link mapping information field. As shown in Figure 6, the service identifier and link mapping information field includes an element identifier (element ID) field, a length field, a control field, and a bitmap of service identifiers or links (bitmap of TIDs / links) field. As shown in Figure 6, the combination of the repetition control field and the bitmap of service identifiers or links field is used to indicate one or more mapping relationships. The specific mapping relationship indication method is detailed in the example below.

[0253] The control field includes a manner flag subfield, which is used to indicate a combination manner for determining the corresponding relationship, that is, the fifth subfield is the manner flag subfield.

[0254] Optionally, the marking mode subfield occupies 1 bit and is used to indicate that the control field includes a service identification (TID) subfield or a link identification (link ID) subfield.

[0255] In one example, as shown in Figure 6, when the Marking Mode subfield is set to 0, the Control Field includes a Service Identifier subfield, which indicates the TID. Accordingly, the Service Identifier or Link Bitmap field indicates the link bitmap. That is, the Service Identifier and Link Mapping Information field uses the correspondence between the service identifier and the link bitmap to indicate the mapping between the service identifier and the link.

[0256] In another example, as shown in Figure 6, when the Marking Mode subfield is set to 1, the Control Field includes a Link Identifier subfield, which indicates the link identifier. Accordingly, the Service Identifier or Link Bitmap field indicates the bitmap of the service identifier. That is, the Service Identifier and Link Mapping Information field uses the corresponding relationship between the link identifier and the bitmap of the service identifier to indicate the mapping relationship between the service identifier and the link.

[0257] Optionally, as shown in FIG6 , the control field also includes a service identification direction (TID) subfield, which is used to indicate the direction of the service identification. For example, if the service identification direction subfield occupies 1 bit, it is used to indicate whether the TID is unidirectional or bidirectional. The direction indicated by unidirectional is the same as the TID direction corresponding to the device sending the first frame. Bidirectional includes uplink and downlink directions. For another example, if the service identification direction subfield occupies 2 bits, it is used to indicate whether the TID is uplink, downlink, or bidirectional. For example, 10 indicates uplink, 01 indicates downlink, 11 indicates bidirectional, and 00 is a reserved value.

[0258] Exemplarily, if the service identification direction is determined to be a downlink direction according to the service identification direction subfield, it means that the current mapping relationship is applicable to the downlink transmission process.

[0259] Mode 4: The service identifier and link mapping information field includes a fifth subfield. The seventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the service identifier and the link bitmap to indicate the mapping relationship between the service identifier and the link. The eighth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the link identifier and the service identifier bitmap to indicate the mapping relationship between the service identifier and the link. The ninth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the link bitmap and the service identifier bitmap to indicate the mapping relationship between the service identifier and the link.

[0260] Optionally, Figure 7 shows a second schematic diagram of the frame structure of the service identifier and link mapping information field. As shown in Figure 7, the control field includes a marking mode subfield, which occupies 2 bits and is used to indicate whether the control field includes a service identifier (TID) subfield, a link identifier (link ID) subfield, a service identifier bitmap (bitmap of TIDs) subfield, or a link bitmap (bitmap of links) subfield.

[0261] In one example, as shown in Figure 7, when the Marking Mode subfield is set to 00, the Control Field includes a Service Identification subfield, which indicates the TID. Accordingly, the Service Identification or Link Bitmap field indicates the link bitmap. In other words, the Service Identification and Link Mapping Information field indicates the mapping between service identifiers and links using the corresponding relationship between service identifiers and link bitmaps.

[0262] In another example, as shown in Figure 7, when the Marking Mode subfield is set to 01, the Control Field includes a Link Identifier subfield, which indicates the link identifier. Accordingly, the Service Identifier or Link Bitmap field indicates the bitmap of the service identifier. That is, the Service Identifier and Link Mapping Information field indicates the mapping relationship between the service identifier and the link, using the corresponding relationship between the link identifier and the bitmap of the service identifier.

[0263] In another example, as shown in Figure 7, when the Marking Mode subfield is set to 10, the Control Field includes a Service Identifier Bit Map subfield, which indicates the service identifier bit map. Accordingly, the Service Identifier or Link Bit Map field indicates the link bit map. That is, the Service Identifier and Link Mapping Information field indicates the mapping relationship between service identifiers and links, using the corresponding relationship between the service identifier bit map and the link bit map.

[0264] In another example, as shown in Figure 7, when the Marking Mode subfield is set to 11, the Control Field includes a Link Bit Map subfield, which indicates the link bit map. Accordingly, the Service Identifier or Link Bit Map field indicates the service identifier bit map. That is, the Service Identifier to Link Mapping Information field indicates the mapping relationship between the service identifier and the link, using the corresponding relationship between the link bit map and the service identifier bit map.

[0265] It should be noted that the description of other fields or subfields of the frame structure shown in FIG7 can be found in the above-mentioned method 3, and the relevant description of the frame structure shown in FIG6 will not be repeated here.

[0266] Mode 5: The service identifier and link mapping information field includes a fifth subfield. The tenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the service identifier and the link bitmap to indicate the mapping relationship between the service identifier and the link. The eleventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the service identifier bitmap and the link bitmap to indicate the mapping relationship between the service identifier and the link.

[0267] Optionally, Figure 8 shows a third schematic diagram of the frame structure of the service identifier and link mapping information field. As shown in Figure 8, the control field includes a marking mode subfield, which occupies 1 bit and is used to indicate that the control field includes a service identifier (TID) subfield or a bitmap of service identifiers or links (bitmap of TIDs / links) subfield.

[0268] In one example, as shown in Figure 8 , when the Marking Mode subfield is set to 0, the Control Field includes a Service Identifier subfield, which indicates the TID. Accordingly, the Service Identifier or Link Bitmap field indicates the link bitmap. In other words, the Service Identifier and Link Mapping Information field indicates the mapping between service identifiers and links using the corresponding relationship between service identifiers and link bitmaps.

[0269] In another example, as shown in FIG8 , when the value of the marking mode subfield is 1, the control field includes a service identifier or link bitmap subfield, which is used to indicate the service identifier or link bitmap. That is, the service identifier and link mapping information field is used to indicate the mapping relationship between the service identifier and the link by using the correspondence between the link bitmap and the service identifier bitmap. For example, if the service identifier or link bitmap subfield is used to indicate the link bitmap, the corresponding service identifier or link bitmap field is used to indicate the service identifier bitmap. For another example, if the service identifier or link bitmap subfield is used to indicate the service identifier bitmap, the corresponding service identifier or link bitmap field is used to indicate the link bitmap.

[0270] It should be noted that the description of other fields or subfields of the frame structure shown in FIG8 can be found in the above-mentioned method 3, and the relevant description of the frame structure shown in FIG6 will not be repeated here.

[0271] Mode 6: The service identifier and link mapping information field includes a fifth subfield. The twelfth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the corresponding relationship between the link identifier and the bit map of the service identifier to indicate the mapping relationship between the service identifier and the link. The thirteenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the corresponding relationship between the link bit map and the bit map of the service identifier to indicate the mapping relationship between the service identifier and the link.

[0272] Optionally, Figure 9 shows a fourth schematic diagram of the frame structure of the service identifier and link mapping information field. As shown in Figure 9, the control field includes a marking mode subfield, which occupies 1 bit and is used to indicate that the control field includes a link identifier (link ID) subfield or a service identifier or link bitmap (bitmap of TIDs / links) subfield.

[0273] In one example, as shown in Figure 9, when the Marking Mode subfield is set to 0, the Control Field includes a Link Identifier subfield, which indicates the link identifier. Accordingly, the Service Identifier or Link Bitmap field indicates the bitmap of the service identifier. In other words, the Service Identifier and Link Mapping Information field indicates the mapping relationship between the service identifier and the link, using the corresponding relationship between the link identifier and the bitmap of the service identifier.

[0274] In another example, as shown in FIG9 , when the value of the marking mode subfield is 1, the control field includes a service identifier or link bitmap subfield, which is used to indicate the service identifier or link bitmap. That is, the service identifier and link mapping information field is used to indicate the mapping relationship between the service identifier and the link by using the correspondence between the link bitmap and the service identifier bitmap. For example, if the service identifier or link bitmap subfield is used to indicate the link bitmap, the corresponding service identifier or link bitmap field is used to indicate the service identifier bitmap. For another example, if the service identifier or link bitmap subfield is used to indicate the service identifier bitmap, the corresponding service identifier or link bitmap field is used to indicate the link bitmap.

[0275] It should be noted that the description of other fields or subfields of the frame structure shown in FIG9 can be found in the above-mentioned method 3, and the relevant description of the frame structure shown in FIG6 will not be repeated here.

[0276] In this way, through any of the above six methods, the service identifier mapping information can be flexibly transmitted, so that the responding end device can quickly learn the mapping relationship between the service identifier and the link and complete the TID-to-link mapping negotiation.

[0277] Optionally, the service identifier and link mapping information field may carry all or part of the mapping information between the service identifier and the link. If the service identifier and link mapping information field carries mapping information for part of the service identifier or mapping information for part of the link, the remaining mapping information remains unchanged by default.

[0278] Exemplarily, the links include link 1 to link 5, and the service identifier and link mapping information field indicates the mapping relationship between link 1 to link 4 and the service identifier respectively, then link 5 maintains the original mapping relationship unchanged.

[0279] Optionally, a link between the STA MLD and the AP MLD is preset as an anchor link. A mapping relationship exists between any TID and the anchor link. That is, any TID can be transmitted on the anchor link. The service identifier and link mapping information field may or may not indicate the mapping relationship between the TID and the anchor link. If not indicated, other fields may be used to indicate the anchor link information. The STA MLD and AP MLD then establish a mapping relationship between the TID and the anchor link based on the anchor link information.

[0280] The above is an introduction to the first frame provided in the embodiment of the present application. It is described here uniformly and will not be repeated below.

[0281] FIG10 is a flow chart of a data transmission method according to an embodiment of the present application. As shown in FIG10 , the method includes the following steps:

[0282] S101: A first device generates a first frame.

[0283] The first device is a requesting device, which may be a STA MLD or an AP MLD.

[0284] Optionally, the first frame includes remapping reason information, where the remapping reason information is used to indicate the remapping reason.

[0285] It can be understood that if the first device requests to establish a mapping relationship between a service identifier and a link for the first time, the remapping reason indicates the mapping reason, that is, the remapping reason information can also be described as mapping reason information.

[0286] Optionally, the information carried in the first frame includes one of the following:

[0287] Scenario 1: The first frame includes the first remapping reason information.

[0288] In some embodiments, as shown in Table 6 above, the first device requests to establish a mapping relationship between a service identifier and a link by requesting a TID-to-link mapping parameter. In this case, the remapping reason needs to be sent to the second device to avoid the TID-to-link mapping parameter provided by the second device being inappropriate for the service identifier and link of the first device.

[0289] Scenario 2: The first frame includes first remapping reason information and first service identifier mapping information.

[0290] The first service identifier mapping information is based on a first remapping reason, and is used to indicate a first mapping relationship between a service identifier and a link.

[0291] Optionally, the first device may first determine a mapping relationship between a set of service identifiers and links based on the remapping reason, and then the second device may choose to accept, modify or replace the mapping relationship to improve negotiation efficiency.

[0292] In some embodiments, as shown in Table 6 above, the request method for the first device to request to establish a mapping relationship between a service identifier and a link is to suggest a TID-to-link mapping parameter, or the request method is to require a TID-to-link mapping parameter, then it is necessary to provide a TID-to-link mapping parameter, that is, to provide the first service identifier mapping information.

[0293] It should be noted that, for other information included in the first frame, please refer to the above description of the frame format of the first frame, which will not be repeated here.

[0294] S102: The first device sends a first frame to the second device. Correspondingly, the second device receives the first frame sent by the first device.

[0295] S103: The second device parses the first frame.

[0296] Optionally, after receiving and parsing the first frame, the second device obtains remapping reason information, and further determines the reason why the first device requests to establish a mapping relationship between the service identifier and the link.

[0297] Furthermore, the second device can subsequently establish a mapping relationship between the service identifier and the link based on the reason, thereby avoiding the failure of TID-to-link mapping negotiation caused by the established mapping relationship not meeting the requirements of the first device, thereby improving the efficiency of TID-to-link mapping negotiation.

[0298] Optionally, after receiving the first frame, the second device may use the embodiment shown in FIG11 to feed back the second frame. FIG11 is a flowchart of a data transmission method provided in an embodiment of the present application. As shown in FIG11 , the method includes the following steps:

[0299] S201: The second device generates a second frame.

[0300] The frame format of the second frame may refer to the above introduction to the frame format of the first frame.

[0301] Optionally, for scenario 1 of the information carried in the first frame, the information carried in the second frame includes one of the following scenarios:

[0302] Case 1-1: the second frame carries the second service identity mapping information.

[0303] The second service identifier mapping information is based on the first remapping reason, and is used to indicate a second mapping relationship between the service identifier and the link.

[0304] Specifically, the second device determines a second mapping relationship between the service identifier and the link based on the first remapping reason and in combination with some of its own considerations, such as the requirement for the link transmission rate, and generates a second frame.

[0305] Optionally, in the scenarios described in Scenario 1 and Scenario 1-1, the first frame can be described as a service identifier and link mapping request frame (TID-to-link mapping request frame), and accordingly, the second frame can be described as a service identifier and link mapping response frame (TID-to-link mapping response frame).

[0306] Case 1-2: The second frame carries the second service identity mapping information and the second remapping reason information.

[0307] Specifically, after determining the second service identifier mapping information based on the first remapping reason, the second device can also determine the second remapping reason information based on its own service identifier and link status. Subsequently, upon receiving the second frame, if the first device needs to modify or replace the TID-to-link mapping parameters, it can determine the TID-to-link mapping parameters based on the second remapping reason information, thereby improving negotiation efficiency. Alternatively, the first device can reconfirm the TID-to-link mapping parameters based on the first and second remapping reason information to avoid mapping errors.

[0308] Optionally, in the scenarios described in Scenario 1 and Scenario 1-2, the first frame can be described as a TID-to-link mapping query frame, and correspondingly, the second frame can be described as a TID-to-link mapping request frame. Then, after receiving the second frame, the first device can also send a TID-to-link mapping response frame to the second device.

[0309] Optionally, for scenario 2 of the information carried in the first frame, the information carried in the second frame includes one of the following scenarios:

[0310] Scenario 2-1: The second frame carries the second service identity mapping information and / or status code.

[0311] The second service identifier mapping information is the modified or replaced service identifier mapping information. The status code is used to indicate whether the mapping relationship between the service identifier and the link is successfully established. Optionally, if the mapping relationship between the service identifier and the link fails to be established, the status code carries the reason for the failure.

[0312] In some embodiments, the second frame carries the second service identifier mapping information and a status code. As shown in Table 6 above, the second device responds by changing or specifying the TID-to-link mapping parameters. The second frame carries the modified or changed service identifier mapping information and indicates the reason for the failure. Subsequently, the first device can determine whether to accept the second service identifier mapping information based on the status code.

[0313] In other embodiments, the second frame carries second service identification mapping information. The second service identification mapping information may be modified or replaced service identification mapping information. Alternatively, the second service identification mapping information may be the same as the first service identification mapping information, and the first device may subsequently reconfirm the service identification mapping information.

[0314] In some further embodiments, the second frame carries a status code. The second device uses the status code as a response indication, including a positive acknowledgement (ACK) or a negative acknowledgement (NACK). For example, the status code is used to indicate that the TID-to-link mapping protocol has been established. For another example, the status code is used to indicate that the TID-to-link mapping protocol has failed to be established. For another example, the status code is used to indicate that the TID-to-link mapping protocol has been rejected.

[0315] Case 2-2: The second frame carries second service identity mapping information and / or status code, and second remapping reason information.

[0316] Specifically, the role of the second remapping reason information in the current scenario can be found in the relevant description in scenario 1-2, which will not be repeated here.

[0317] Optionally, in scenario 2 and scenario 2-1, or in the scenarios described in scenario 2 and scenario 2-2, the first frame can be described as a service identifier and link mapping setup frame (TID-to-link mapping setup frame), and accordingly, the second frame can be described as a service identifier and link mapping setup frame (TID-to-link mapping setup frame).

[0318] It should be noted that, for other information included in the second frame, refer to the above description of the frame format of the first frame, which will not be repeated here.

[0319] S202: The second device sends a second frame to the first device. Correspondingly, the first device receives the second frame sent by the second device.

[0320] S203: The first device parses the second frame.

[0321] Based on the above scheme, on the one hand, based on the scenarios shown in Scenario 1, Scenario 1-1, and Scenario 1-2 above, the second device can determine the mapping relationship between the service identifier and the link according to the remapping reason and its own situation. Then, the mapping relationship will not cause the first device to be unable to complete the establishment of the mapping relationship, thus avoiding negotiation failure and improving negotiation efficiency. On the other hand, based on the scenarios shown in Scenario 2, Scenario 2-1, and Scenario 2-2 above, the second device can modify or replace the mapping relationship between the received service identifier and the link according to the remapping reason and its own situation. Similarly, the modified or replaced mapping relationship will not cause the first device to be unable to complete the establishment of the mapping relationship, thus avoiding negotiation failure and improving negotiation efficiency.

[0322] In this way, the first device and the second device can determine the mapping relationship between the service identifier and the link through a limited number of negotiations, thereby improving negotiation efficiency.

[0323] Optionally, after receiving the second frame, the first device may use the embodiment shown in FIG12 to feed back the third frame. FIG12 is a flowchart of a data transmission method provided in an embodiment of the present application. As shown in FIG12, the method includes the following steps:

[0324] S301: The first device generates a third frame.

[0325] S302: The first device sends a third frame to the second device. Correspondingly, the second device receives the third frame sent by the first device.

[0326] The third frame is used to indicate a positive response or a negative response to the second frame, that is, whether the first device accepts the second mapping relationship, or whether the second mapping relationship is successfully established.

[0327] In this way, after receiving the third frame, the second device can determine whether the TID-to-link mapping is successfully established.

[0328] Figure 13 shows a schematic diagram of the structures of the AP MLD and STA MLD involved in the communication. The 802.11 standard focuses on the 802.11 physical layer (PHY) and MAC layer parts in the AP MLD and STA MLD.

[0329] As shown in Figure 13(a), the multiple APs included in the AP MLD are independent of each other at the low MAC and PHY layers, and also at the high MAC layer. The multiple STAs included in the STA MLD are independent of each other at the low MAC and PHY layers, and also at the high MAC layer.

[0330] As shown in Figure 13(b), the multiple APs included in the AP MLD are independent of each other at the lower MAC layer and PHY layer, and share the upper MAC layer. The multiple STAs included in the STA MLD are independent of each other at the lower MAC layer and PHY layer, and share the upper MAC layer.

[0331] Of course, the STA MLD can adopt an independent high MAC layer architecture, while the AP MLD can adopt a shared high MAC layer architecture. Alternatively, the STA MLD can adopt a shared high MAC layer architecture, while the AP MLD can adopt an independent high MAC layer architecture. Exemplarily, both the high MAC layer and the low MAC layer can be implemented by a processor in a chip system of a multi-link device, or respectively by different processing modules in a chip system.

[0332] As can be seen, the independent lower MAC layer structure in multi-link devices enables each STA or AP's lower MAC layer to correspond to its own link. Management frames transmitted on a link are sent to the lower MAC layer corresponding to the link. In existing technologies, if a link fails or is unreachable, the management frames required to be sent to the lower MAC layer corresponding to that link will fail to be sent.

[0333] Based on this, an embodiment of the present application provides a data transmission method. FIG14 is a flowchart of a data transmission method provided by an embodiment of the present application. As shown in FIG14 , the method includes the following steps:

[0334] S401: A first device sends a management frame and a target link identifier on a failed second link to a second device on a first link. Correspondingly, the second device receives the management frame and the target link identifier sent by the first device on the first link.

[0335] The management frame is a unicast management frame sent by the first device to a module in the second device. The target link identifier is used to point to the module. Specifically, the target link identifier is used to instruct the receiving multi-link device to forward the received management frame to the module corresponding to the target link identifier. The module refers to a device in the MLD. For example, it can be an AP in the AP MLD. Another example is a STA in the STA MLD.

[0336] Optionally, the first device further sends a reporting link identifier on the first link, wherein the link corresponding to the reporting link identifier is the first link for sending management frames, and the reporting link identifier is used to instruct the receiving end MLD to send a response frame on the first link corresponding to the reporting link identifier.

[0337] In some embodiments, the management frame includes a reporting link ID and a destination link ID. The reporting link ID includes a reporting link ID, which indicates the ID of the link to which the management frame is actually sent. The destination link ID includes a destination link ID, which indicates the ID of the final link to which the frame is to be forwarded.

[0338] Exemplarily, the target link identifier and the reporting link identifier are carried in an aggregation control (A-control) field of a MAC frame.

[0339] In other embodiments, a new function frame is defined, and the management frame, the target link identifier, and the reporting link identifier are carried in the frame body of the function frame, thereby enabling transparent transmission of the management frame, the target link identifier, and the reporting link identifier carried in the newly defined function frame.

[0340] For example, as shown in Table 8 below, part of the information carried in the newly defined function frame is shown, wherein the target link identifier and the reporting link identifier are carried in the X element.

[0341] Table 8

[0342] Sequence information 1 Category field (category) 2 Function field (action) 3 Transparent management frame 4 X element (element)

[0343] In addition, a schematic diagram of the frame format of a transparently transmitted management frame is shown in Figure 15. As shown in Figure 15, the transparently transmitted management frame includes a management MPDU length field (MMPDU length), a management MPDU frame control field (MMPDU frame control), and a management MPDU frame body field (MMPDU frame body).

[0344] S402: The second device determines, based on the target link identifier, to forward the received management frame to a module corresponding to the target link identifier.

[0345] For example, as shown in Figure 2, the first device is an AP MLD and the second device is a STA MLD. AP MLD needs to use link 2 to send a management frame to STA#2. Assume that the reporting link identifier corresponds to link 1 and the target link identifier corresponds to link 2. If link 2 fails, AP MLD uses link 1 to send a management frame to STA#1. After receiving the management frame, STA#1 determines that the target link identifier corresponds to link 2, that is, STA#2, and forwards the received management frame to STA#2. Optionally, STA#1 can also send a response frame on link 1 corresponding to the reporting link identifier based on the reporting link identifier to notify AP MLD whether the management frame was sent successfully. The response frame includes a positive acknowledgment or a negative acknowledgment.

[0346] In this way, by using the target link identifier, when some links fail or are unreachable, the management frame that should be sent can be sent to the lower MAC layer corresponding to the failed or unreachable link, avoiding the failure of management frame sending.

[0347] It should be understood that the embodiment shown in FIG. 14 can be combined with the embodiment shown in FIG. 10 , FIG. 11 or FIG. 12 in the foregoing text.

[0348] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of a data transmission device (such as a first device and a second device). It is understandable that, in order to realize the above functions, the data transmission device includes a hardware structure and / or software module corresponding to each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0349] The embodiment of the present application can divide the functional modules of the device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one functional module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function:

[0350] FIG16 is a schematic diagram of the structure of a data transmission device provided in an embodiment of the present application. As shown in FIG16 , the data transmission device 1600 includes: a processing module 1601 and a communication module 1602 .

[0351] In one possible design, when the data transmission apparatus 1600 serves as the first device, the processing module 1601 is used to support the data transmission apparatus 1600 in executing step S101 in FIG. 10 , and / or to support the data transmission apparatus 1600 in executing step S301 in FIG. 12 . The communication module 1602 is used to support the data transmission apparatus 1600 in executing step S102 in FIG. 10 , and / or to support the data transmission apparatus 1600 in executing step S202 in FIG. 11 , and / or to support the data transmission apparatus 1600 in executing step S302 in FIG. 12 , and / or to support the data transmission apparatus 1600 in executing step S401 in FIG. 14 .

[0352] In another possible design, when the data transmission apparatus 1600 serves as the second device, the processing module 1601 is configured to support the data transmission apparatus 1600 in executing step S103 in FIG. 10 , and / or to support the data transmission apparatus 1600 in executing step S201 in FIG. 11 , and / or to support the data transmission apparatus 1600 in executing step S402 in FIG. 14 . The communication module 1602 is configured to support the data transmission apparatus 1600 in executing step S102 in FIG. 10 , and / or to support the data transmission apparatus 1600 in executing step S202 in FIG. 11 , and / or to support the data transmission apparatus 1600 in executing step S301 in FIG. 12 .

[0353] Optionally, the communication module 1602 may include a receiving module and a sending module. The receiving module is used to receive data sent by other devices. The sending module is used to send data to other devices. The specific implementation of the communication module 1602 is not specifically limited in this embodiment of the application.

[0354] Optionally, the data transmission device 1600 shown in FIG16 may further include a storage module (not shown in FIG16 ) storing a program or instruction. When the processing module 1601 executes the program or instruction, the data transmission device 1600 shown in FIG16 may execute the data transmission method shown in FIG10 , FIG11 , FIG12 , or FIG14 .

[0355] The technical effects of the data transmission device 1600 shown in FIG16 can refer to the technical effects of the data transmission method shown in FIG10 , FIG11 , FIG12 or FIG14 , and will not be repeated here.

[0356] The processing modules involved in the data transmission device 1600 shown in FIG16 can be implemented by a processor or processor-related circuit components, and can be a processor or a processing unit. The operations and / or functions of each module in the data transmission device 1600 are respectively to implement the corresponding processes of the data transmission method shown in FIG10, FIG11, FIG12, or FIG14, and are not further described here for the sake of brevity.

[0357] FIG17 is a structural diagram of a possible product form of the data transmission device described in an embodiment of the present application.

[0358] As a possible product form, the data transmission device described in the embodiment of the present application may be the first device described above, and the data transmission device includes a processor 1701 and a transceiver 1702. Optionally, the data transmission device further includes a memory 1703.

[0359] The processor 1701 is configured to support the data transmission apparatus in executing step S101 in FIG. 10 , and / or support the data transmission apparatus in executing step S301 in FIG. 12 . The transceiver 1702 is configured to support the data transmission apparatus in executing step S102 in FIG. 10 , and / or support the data transmission apparatus in executing step S202 in FIG. 11 , and / or support the data transmission apparatus in executing step S302 in FIG. 12 , and / or support the data transmission apparatus in executing step S401 in FIG. 14 .

[0360] As another possible product form, the data transmission device described in the embodiment of the present application may be the second device described above, and the data transmission device includes a processor 1701 and a transceiver 1702. Optionally, the data transmission device further includes a memory 1703.

[0361] The processor 1701 is configured to support the data transmission apparatus in executing step S103 in FIG. 10 , and / or support the data transmission apparatus in executing step S201 in FIG. 11 , and / or support the data transmission apparatus in executing step S402 in FIG. The transceiver 1702 is configured to support the data transmission apparatus in executing step S102 in FIG. 10 , and / or support the data transmission apparatus in executing step S202 in FIG. 11 , and / or support the data transmission apparatus in executing step S301 in FIG. 12 .

[0362] As another possible product form, the data transmission device described in the embodiment of the present application can also be implemented by a chip. The chip includes: a processing circuit 1701 and a transceiver pin 1702. Optionally, the chip can also include a memory 1703.

[0363] The bus may include a path for transmitting information between the components.

[0364] The transceiver / transceiver pin 1702 is used to communicate with other devices. In the embodiments of the present application, the transceiver / transceiver pin can be a module, circuit, bus, interface, communication interface, or other device capable of implementing communication functions, used to communicate with other devices. Optionally, the transceiver can be a standalone transmitter that can be used to send information to other devices, or a standalone receiver that can be used to receive information from other devices. The transceiver can also be a component that integrates the functions of sending and receiving information. The embodiments of the present application do not limit the specific implementation of the transceiver.

[0365] The memory 1703 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. By way of example and not limitation, many forms of RAM may be used, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM), or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory 1703 may be independent or integrated with processor 1701.

[0366] As another possible product form, the data transmission device described in the embodiments of the present application can also be implemented using the following circuits or devices: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits that can perform the various functions described throughout this application.

[0367] An embodiment of the present application also provides a chip system, including: a processor, the processor is coupled to a memory, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the chip system implements the method in any of the above method embodiments.

[0368] Optionally, there may be one or more processors in the chip system. The processor may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

[0369] Optionally, the memory in the chip system may be one or more memories. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited in this application. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or provided on different chips. This application does not specifically limit the type of memory or the configuration of the memory and the processor.

[0370] Exemplarily, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.

[0371] Optionally, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer executes the data transmission method in the aforementioned method embodiment.

[0372] Optionally, an embodiment of the present application further provides a computer program product comprising computer instructions, which, when executed on a computer, enables the computer to execute the data transmission method in the aforementioned method embodiment.

[0373] It should be understood that the computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium, or a semiconductor medium (e.g., a solid-state drive).

[0374] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0375] It should be understood that the devices and methods disclosed in the several embodiments provided in this application can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0376] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0377] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0378] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application.

[0379] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A data transmission method, It is characterized in that The method comprises: generating a first frame, wherein the first frame includes remapping reason information, and the remapping reason information is used to indicate a remapping reason; The first frame is sent.

2. The method according to claim 1, It is characterized in that The remapping reason information is carried in one or more of the following fields: a field for the maximum number of links allowed to be opened, a field for closed link set information, a field for link quality report information, and a field for service quality QoS report information; wherein the subfield for the maximum number of links allowed to be opened is used to indicate the maximum number of links allowed to be opened; the closed link set information field is used to indicate the set of links that need to be closed; the link quality report information field is used to indicate link quality information; and the QoS report information field is used to indicate service quality information.

3. The method according to claim 2, It is characterized in that The first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame; the first indication information is carried in a control field, and the control field includes a first subfield, a second subfield, a third subfield and a fourth subfield; wherein, The first subfield is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame; The first subfield and / or the second subfield is used to determine whether the link set shutdown information field appears in the first frame; The third subfield is used to indicate whether the link quality report information field appears in the first frame; The fourth subfield is used to indicate whether the QoS report information field appears in the first frame.

4. The method according to claim 2, It is characterized in that The first frame includes first indication information, and the first indication information is used to indicate whether a field carrying the remapping reason information appears in the first frame; the first indication information is carried in the remapping reason field, wherein: The first value of the remapping reason field is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame; The first value and / or the second value of the remapping reason field is used to indicate whether the closed link set information field appears in the first frame; A third value of the remapping reason field is used to indicate whether the link quality report information field appears in the first frame; The fourth value of the remapping reason field is used to indicate whether the QoS report information field appears in the first frame.

5. The method according to claim 2, It is characterized in that The first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame; the first indication information is carried in the control field and the remapping reason field, and the control field includes a first subfield, a second subfield, a third subfield and a fourth subfield; wherein, The first value of the first subfield and the remapping reason field is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame; One or more of the first subfield, the second subfield, the first value of the remapping reason field, and the second value of the remapping reason field are used to indicate whether the closed link set information field appears in the first frame; The third subfield and the third value of the remapping reason field are used to indicate whether the link quality report information field appears in the first frame; The fourth subfield and the fourth value of the remapping reason field are used to indicate whether the QoS report information field appears in the first frame.

6. The method according to any one of claims 1 to 5, It is characterized in that The method further comprises: A second frame is received, where the second frame carries second service identifier mapping information, where the second service identifier mapping information is based on the remapping reason, and where the second service identifier mapping information is used to indicate a second mapping relationship between a service identifier and a link.

7. The method according to claim 6, It is characterized in that The second service identifier mapping information is carried in a service identifier and link mapping information field, and the service identifier and link mapping information field is used to indicate the second mapping relationship by using a corresponding relationship between the service identifier and a bit map of the link; or, The service identifier and link mapping information field is used to indicate the second mapping relationship by using the corresponding relationship between the link identifier and the bit map of the service identifier; or, The service identifier and link mapping information field includes a fifth subfield, and the fifth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bit map of the link; the sixth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the identifier of the link and the bit map of the service identifier; or, The service identifier and link mapping information field includes a fifth subfield, the seventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bit map of the link; the eighth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the bit map of the service identifier; the ninth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the bit map of the link and the bit map of the service identifier; or, The service identifier and link mapping information field includes a fifth subfield, and the tenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the corresponding relationship between the service identifier and the bit map of the link; the eleventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the corresponding relationship between the bit map of the service identifier and the bit map of the link; or, The service identifier and link mapping information field includes a fifth subfield, and the twelfth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the link identifier and the bit map of the service identifier to indicate the second mapping relationship; the thirteenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the bit map of the link and the bit map of the service identifier to indicate the second mapping relationship.

8. The method according to claim 6 or 7, It is characterized in that The second service identifier mapping information also carries the direction of the second mapping relationship between the service identifier and the link.

9. The method according to any one of claims 6 to 8, It is characterized in that The method further comprises: A third frame is sent, where the third frame is used to indicate a positive response or a negative response to the second frame.

10. The method according to any one of claims 1 to 9, It is characterized in that The first frame further includes first service identifier mapping information, where the first service identifier mapping information is based on the remapping reason and is used to indicate a first mapping relationship between a service identifier and a link.

11. The method according to claim 10, It is characterized in that The second frame also carries a status code, which is used to indicate whether the mapping relationship between the service identifier and the link is successfully established.

12. The method according to claim 11, It is characterized in that If the mapping relationship between the service identifier and the link fails to be established, the status code carries the reason for the failure.

13. The method according to any one of claims 1 to 12, It is characterized in that The first frame also carries a remapping mode, and the remapping mode includes an immediate remapping mode or a delayed remapping mode.

14. A data transmission method, It is characterized in that The method comprises: receiving a first frame, wherein the first frame includes remapping reason information, where the remapping reason information is used to indicate a remapping reason; The first frame is parsed.

15. The method according to claim 14, It is characterized in that The remapping reason information is carried in one or more of the following fields: a field for the maximum number of links allowed to be opened, a field for closed link set information, a field for link quality report information, and a field for service quality QoS report information; wherein the subfield for the maximum number of links allowed to be opened is used to indicate the maximum number of links allowed to be opened; the closed link set information field is used to indicate the set of links that need to be closed; the link quality report information field is used to indicate link quality information; and the QoS report information field is used to indicate service quality information.

16. The method according to claim 15, It is characterized in that The first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame; the first indication information is carried in a control field, and the control field includes a first subfield, a second subfield, a third subfield and a fourth subfield; wherein, The first subfield is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame; The first subfield and / or the second subfield is used to indicate whether the closed link set information field appears in the first frame; The third subfield is used to indicate whether the link quality report information field appears in the first frame; The fourth subfield is used to indicate whether the QoS report information field appears in the first frame.

17. The method according to claim 15, It is characterized in that The first frame includes first indication information, and the first indication information is used to indicate whether a field carrying the remapping reason information appears in the first frame; the first indication information is carried in the remapping reason field, wherein: The first value of the remapping reason field is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame; The first value and / or the second value of the remapping reason field is used to indicate whether the closed link set information field appears in the first frame; A third value of the remapping reason field is used to indicate whether the link quality report information field appears in the first frame; The fourth value of the remapping reason field is used to indicate whether the QoS report information field appears in the first frame.

18. The method according to claim 15, It is characterized in that The first frame includes first indication information, and the first indication information is used to indicate whether the field carrying the remapping reason information appears in the first frame; the first indication information is carried in the control field and the remapping reason field, and the control field includes a first subfield, a second subfield, a third subfield and a fourth subfield; wherein, The first value of the first subfield and the remapping reason field is used to indicate whether the maximum number of links allowed to be opened field appears in the first frame; One or more of the first subfield, the second subfield, the first value of the remapping reason field, and the second value of the remapping reason field are used to indicate whether the closed link set information field appears in the first frame; The third subfield and the third value of the remapping reason field are used to indicate whether the link quality report information field appears in the first frame; The fourth subfield and the fourth value of the remapping reason field are used to indicate whether the QoS report information field appears in the first frame.

19. The method according to any one of claims 15 to 18, It is characterized in that The method further comprises: Generate a second frame, where the second frame carries second service identifier mapping information, where the second service identifier mapping information is based on the remapping reason, and where the second service identifier mapping information is used to indicate a second mapping relationship between the service identifier and the link; The second frame is sent.

20. The method according to claim 19, It is characterized in that The second service identifier mapping information is carried in a service identifier and link mapping information field, and the service identifier and link mapping information field is used to indicate the second mapping relationship by using a corresponding relationship between the service identifier and a bit map of the link; or, The service identifier and link mapping information field is used to indicate the second mapping relationship by using the corresponding relationship between the link identifier and the bit map of the service identifier; or, The service identifier and link mapping information field includes a fifth subfield, and the fifth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bit map of the link; the sixth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the identifier of the link and the bit map of the service identifier; or, The service identifier and link mapping information field includes a fifth subfield, the seventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bit map of the link; the eighth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the link identifier and the bit map of the service identifier; the ninth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the bit map of the link and the bit map of the service identifier; or, The service identifier and link mapping information field includes a fifth subfield, and the tenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the service identifier and the bit map of the link; the eleventh value of the fifth subfield is used to indicate that the service identifier and link mapping information field indicates the second mapping relationship using the correspondence between the bit map of the service identifier and the bit map of the link; or, The service identifier and link mapping information field includes a fifth subfield, and the twelfth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the link identifier and the bit map of the service identifier to indicate the second mapping relationship; the thirteenth value of the fifth subfield is used to indicate that the service identifier and link mapping information field uses the correspondence between the bit map of the link and the bit map of the service identifier to indicate the second mapping relationship.

21. The method according to claim 19 or 20, It is characterized in that The second service identifier mapping information also carries the direction of the second mapping relationship between the service identifier and the link.

22. The method according to any one of claims 19 to 21, It is characterized in that The method further comprises: A third frame is received, where the third frame is used to indicate a positive response or a negative response to the second frame.

23. The method according to any one of claims 15 to 22, It is characterized in that The first frame further includes first service identifier mapping information, where the first service identifier mapping information is based on the remapping reason and is used to indicate a first mapping relationship between a service identifier and a link.

24. The method according to claim 23, It is characterized in that The second frame also carries a status code, which is used to indicate whether the mapping relationship between the service identifier and the link is successfully established.

25. The method according to claim 24, It is characterized in that If the mapping relationship between the service identifier and the link fails to be established, the status code carries the reason for the failure.

26. The method according to any one of claims 15 to 25, It is characterized in that The first frame also carries a remapping mode, and the remapping mode includes an immediate remapping mode or a delayed remapping mode.

27. A data transmission method, It is characterized in that The method comprises: A management frame and a target link identifier on the failed second link are sent on the first link, wherein the target link identifier is used to instruct the receiving-end multi-link device MLD to forward the received management frame to a module corresponding to the target link identifier.

28. The method according to claim 27, It is characterized in that The method further comprises: A reporting link identifier is sent on the first link, where the reporting link identifier is used to instruct the receiving end MLD to send a response frame on the first link corresponding to the reporting link identifier.

29. The method according to claim 27 or 28, It is characterized in that The target link identifier and the reporting link identifier are carried in the aggregation control A-control field of the MAC frame.

30. The method according to claim 27 or 28, It is characterized in that The management frame, the target link identifier and the reporting link identifier are carried in the frame body of the function frame.

31. A data transmission method, It is characterized in that The method comprises: Receiving, on the first link, a management frame and a target link identifier on the failed second link; According to the target link identifier, it is determined to forward the received management frame to a module corresponding to the target link identifier.

32. The method according to claim 31, It is characterized in that The method further comprises: A reporting link identifier is received on the first link, where the reporting link identifier is used to indicate that a response frame is sent on the first link corresponding to the reporting link identifier.

33. The method according to claim 31 or 32, It is characterized in that The target link identifier and the reporting link identifier are carried in the aggregation control A-control field of the MAC frame.

34. The method according to claim 31 or 32, It is characterized in that The management frame, the target link identifier and the reporting link identifier are carried in the frame body of the function frame.

35. A data transmission device, It is characterized in that The data transmission device includes a unit for executing each step of the method involved in any one of claims 1-13, or a unit for executing each step of the method involved in any one of claims 14-26, or a unit for executing each step of the method involved in any one of claims 27-30, or a unit for executing each step of the method involved in any one of claims 31-34.

36. A computer readable storage medium, It is characterized in that The computer-readable storage medium stores computer instructions, which, when executed on a computer, cause the computer to execute the method described in any one of claims 1 to 13, or cause the computer to execute the method described in any one of claims 14 to 26, or cause the computer to execute the method described in any one of claims 27 to 30, or cause the computer to execute the method described in any one of claims 31 to 34.

37. A chip, It is characterized in that The chip includes a processing unit and transceiver pins; the processing unit is used to perform the processing operations in the method involved in any one of claims 1-34, and the transceiver pins are used to perform the communication operations in the method involved in any one of claims 1-34.

Images