Multilink communication method, traffic-to-link mapping method, and device

Abstract

To provide a multi-link communication method, a from-traffic-to-link mapping method, and a device.SOLUTION: When performing multi-link establishment, a multi-link device establishes multi-link communication on some or all of links supported by the multi-link device based on requirements. In subsequent communication, the multi-link device further adds or removes links to or from the established multi-link communication links based on the requirements. The multi-link device establishes a from-traffic-to-link mapping relationship at the time of the multi-link establishment or updates the from-traffic-to-link mapping relationship after the completion of the multi-link establishment.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims priority based on Chinese Patent Application No. 202010852529.1, titled "Multi - link Communication Method, Method for Mapping Traffic to Links, and Device", filed with the China National Intellectual Property Administration on August 21, 2020, the content of which is incorporated herein by reference in its entirety.

[0002] [Technical Field] This application relates to the field of communication technologies, and in particular, to multi - link communication methods, methods for mapping traffic to links, and devices.

Background Art

[0003] With the development of wireless technologies, more wireless devices support multi - link communication. For example, those devices support simultaneous communication in frequency bands of 2.4 [GHz], 5 [GHz], and 6 [GHz], or support communication in multiple different channels of the same frequency band. This improves the communication speed between multiple wireless devices. Wireless devices that support multi - link communication are usually referred to as multi - link devices (MLDs).

[0004] Before multiple MLDs communicate with each other, it is necessary to perform multi - link establishment. For example, the first multi - link device transmits an association request frame to the second multi - link device to perform multi - link establishment. The association request frame carries information about the links supported by the first multi - link device, and the first multi - link device hopes to establish multi - link communication in those links.

[0005] However, in actual application, the MLD does not necessarily have communication requirements for each link it supports in the initial stage. If the MLD establishes multilink communication on all links it supports in the initial stage, the utilization rate of link resources will be low. In subsequent communication processes, the MLD may also have requirements for updating communication links. On the other hand, in the initial stage, the multilink device only provides information about the links on which it wishes to establish multilink communication. This makes it impossible to satisfy the requirement for updating communication links. It is possible to see that conventional multilink communication has technical problems, such as lacking flexibility and being unable to meet the requirements of actual application. [Overview of the project]

[0006] Embodiments of this application provide a multilink communication method, a traffic-to-link mapping method, and a device that can improve the flexibility of multilink communication performed by a multilink device and satisfy the requirement for the multilink device to dynamically update communication links. In addition, it is possible to manage traffic transmission more flexibly and improve the quality of service of traffic.

[0007] According to a first embodiment, a multilink communication method is provided, the method comprising the steps of: a first multilink device receiving a first request message transmitted by a second multilink device, the first request message carrying identifiers of at least two links and first instruction information for each of the at least two links, the first instruction information indicating an operation type for the links, the operation type including establishing multilink communication, and further including providing only link information or not establishing multilink communication; the first multilink device transmitting a first response message to the second multilink device, the first response message carrying identifiers of the at least two links and second instruction information for each of the at least two links, the second instruction information indicating the state of the links.

[0008] In this embodiment of the application, a first request message carries first instruction information, and a first response message carries second instruction information, thereby allowing the multilink device to choose to establish multilink communication on a portion of the links it supports, based on certain requirements, when establishing a multilink. This improves the flexibility of the multilink communication performed by the multilink device.

[0009] In one possible implementation, the operation type further includes adding a link to a multilink communication link and / or removing a link from the multilink communication link.

[0010] In this implementation, the first request message carries first instruction information, and the first response message carries second instruction information, thereby, after completing the establishment of the multilink, the multilink device may add links to the established multilink communication links or remove links from the established multilink communication links based on communication requirements. This further improves the flexibility of the multilink communication performed by the multilink device and better satisfies the requirement for the multilink device to dynamically update communication links.

[0011] In one possible implementation, the state includes one or more of the following: the multilink communication has been successfully established; the multilink communication has not been established; only the link information is provided or the multilink communication has not been established; the link has been successfully added; the link has been successfully added; the link has been successfully added; the link has been successfully deleted; or the link has been deleted.

[0012] In this implementation, multiple link states exist, further improving the flexibility of multilink communication.

[0013] In one possible implementation, the first instruction information and / or the second instruction information are carried in a first pre-configured field within a multilink information element.

[0014] This implementation is simple and easy to implement.

[0015] In one possible implementation, in the multilink information element carried in the first request message, the first value of the first pre-configured field indicates that the operation type is establishing multilink communication, and the second value of the first pre-configured field indicates that the operation type is providing only link information or not establishing multilink communication. Alternatively, in the multilink information element carried in the first response message, the first value of the first pre-configured field indicates that the state is successfully establishing multilink communication, the second value of the first pre-configured field indicates that the state is failing to establish multilink communication, and the third value of the first pre-configured field indicates that the state is providing only link information or not establishing multilink communication.

[0016] In this implementation, when a multilink information element is located in an association request frame and an association response frame, each of the values ​​of the first pre-configured field may represent a different meaning. Based on the type of frame in which the first pre-configured field is located (i.e., an association request frame and an association response frame) and based on the value of the first pre-configured field, it is possible to determine the meaning represented by the value of the first pre-configured field, thereby reducing the bits occupied by the first pre-configured field.

[0017] In one possible implementation, in the multilink information element carried in the first request message or the first response message, the value of the first pre-configured field is: A first value indicating that the operation type is the establishment of multilink communication, A second value indicating that the aforementioned state means that the multilink communication has been successfully established, A third value indicating that the aforementioned state means that the establishment of the multilink communication has failed, or The system includes one or more items from a fourth value indicating that the operation type or state is either providing only the link information or not establishing the multilink communication.

[0018] In this implementation, when the multilink information element is located in the association request frame and the association response frame, the value of the first pre-configured field may have the same meaning, or the meaning of the value of the first pre-configured field may be directly determined based on the value of the first pre-configured field. This reduces the complexity of identifying the first pre-configured field by the multilink device.

[0019] In one possible implementation, in the multilink information element carried in the first request message, the first value of the first pre-configured field indicates that the operation type is adding a link to a multilink communication link, and the second value of the first pre-configured field indicates that the operation type is removing a link from the multilink communication link. Alternatively, in the multilink information element carried in the first response message, the first value of the first pre-configured field indicates that the state is that the link addition was successful, the second value of the first pre-configured field indicates that the state is that the link addition failed, the third value of the first pre-configured field indicates that the state is that the link removal was successful, and the fourth value of the first pre-configured field indicates that the state is that the link removal failed.

[0020] In this implementation, when a multilink information element is located in a reassociation request frame and a reassociation response frame, each of the values ​​of the first pre-configured field may have a different meaning. Based on the type of frame in which the first pre-configured field is located (i.e., a reassociation request frame and a reassociation response frame) and based on the value of the first pre-configured field, it is possible to determine the meaning of the value of the first pre-configured field, thereby reducing the number of bits occupied by the first pre-configured field.

[0021] In one possible implementation, in the multilink information element carried in the first request message or the first response message, the value of the first pre-configured field is: A first value indicating that the operation type is the addition of a link to a multi-link communication link, A second value indicating that the operation type is the deletion of a link from the multi-link communication link, A third value indicating that the state is that the addition of the link has been successful, A fourth value indicating that the state is that the addition of the link has failed, A fifth value indicating that the state is that the deletion of the link has been successful, or, A sixth value indicating that the state is that the deletion of the link has failed, includes any one or more of the above items.

[0022] In this implementation, when the multi-link information element is located in the re-association request frame and the re-association response frame, the value of the first pre-set field may indicate the same meaning, and based on the value of the first pre-set field, the meaning indicated by the value of the first pre-set field may be directly determined. This makes it possible to reduce the complexity when the multi-link device identifies the first pre-set field.

[0023] In one possible implementation, in the multi-link information element carried in the first request message or the first response message, the value of the first pre-set field is A first value indicating that the operation type is the establishment of multi-link communication, A second value indicating that the state is that the establishment of the multi-link communication has been successful, A third value indicating that the state is that the establishment of the multi-link communication has failed, and, A fourth value indicating that the operation type or the state is only the provision of the link information or not establishing the multi-link communication. A fifth value indicating that the operation type is the addition of a link to a multi-link communication link, A sixth value indicating that the operation type is the deletion of a link from the multi-link communication link, A seventh value indicating that the state is that the addition of the link has been successful, An eighth value indicating that the state is that the addition of the link has failed, A ninth value indicating that the state is that the deletion of the link has been successful, or, A tenth value indicating that the state is that the deletion of the link has failed, includes one or more items of any of the above.

[0024] In this implementation, when the multi-link information element is located in the association request frame, the association response frame, the re-association request frame, and the re-association response frame, the value of the first pre-set field may indicate the same meaning, or based on the value of the first pre-set field, the meaning indicated by the value of the first pre-set field may be directly determined. This also makes it possible to reduce the complexity in identifying the first pre-set field by the multi-link device.

[0025] In one possible implementation, when the operation type is the establishment of multi-link communication, not establishing multi-link communication, providing only the link information, or adding the link to the multi-link communication link, the first request message further carries the local capability information. Alternatively, when the operation type is the deletion of the link from the multi-link communication link, the first request message does not carry the local capability information.

[0026] In this implementation, when the operation type is the removal of a link from a multilink communication link, the first request message does not carry station capability information. This allows for a reduction in resource overhead while ensuring the reliability of the resolution method.

[0027] In one possible implementation, the multilink information element further carries information about a new link on the access point device. The multilink device MLD common information field of the multilink information element carries third directive information indicating that the multilink information element is carrying information about the new link.

[0028] In this implementation, the multilink device initiates a new link based on communication requirements and notifies other multilink devices in a timely manner, further improving the flexibility of multilink communication and better meeting the requirements for dynamic updating of communication links by multilink devices.

[0029] In one possible implementation, the information relating to the new link is carried within each of N consecutive beacon frames, where N is a positive integer.

[0030] In this way, it is possible to ensure that information about new links can be effectively received by other multilink devices, and that the reliability of the solution can be further improved.

[0031] A second embodiment provides a multilink communication method, the method comprising the steps of: a first multilink device receiving a first request message transmitted by a second multilink device, the first request message carrying identifiers of at least two links and first instruction information for each of the at least two links, the first instruction information indicating an operation type for the link, the operation type including adding a link to a multilink communication link, and further including providing only link information or not establishing multilink communication; the first multilink device transmitting a first response message to the second multilink device, the first response message carrying identifiers of the at least two links and second instruction information for each of the at least two links, the second instruction information indicating the state of the link.

[0032] In this embodiment of the application, a first request message carries first instruction information, and a first response message carries second instruction information, thereby allowing the multilink device to add a link to an established multilink communication link based on certain requirements. In addition, information is provided regarding other links that do not require the establishment of multilink communication, thereby allowing the multilink device to subsequently add links based on certain requirements. This makes it possible to improve the flexibility of multilink communication performed by the multilink device.

[0033] In one possible implementation, the operation type further includes establishing a multilink communication and / or removing a link from the multilink communication link.

[0034] In one possible implementation, the state includes one or more of the following: the multilink communication has been successfully established; the multilink communication has not been established; only the link information is provided; the multilink communication has not been established; the link has been successfully added; the link has been successfully added; the link has been successfully removed; or the link has been removed.

[0035] A third embodiment provides a multilink communication method, the method comprising the steps of: a first multilink device receiving a first request message transmitted by a second multilink device, the first request message carrying identifiers of at least two links and first instruction information for each of the at least two links, the first instruction information indicating an operation type for the link, the operation type including deleting a link to a multilink communication link, providing only link information, or not establishing multilink communication; the first multilink device transmitting a first response message to the second multilink device, the first response message carrying identifiers of the at least two links and second instruction information for each of the at least two links, the second instruction information indicating the state of the link.

[0036] In this embodiment of the application, a first request message carries first instruction information, and a first response message carries second instruction information, thereby causing the multilink device to remove a link from an established multilink communication link based on certain requirements. In addition, information is provided regarding other links that do not need to be established for multilink communication, thereby allowing the multilink device to subsequently add links based on certain requirements. This makes it possible to improve the flexibility of multilink communication performed by the multilink device.

[0037] In one possible implementation, the operation type further includes establishing multilink communication and / or adding a link to the multilink communication link.

[0038] In one possible implementation, the state includes one or more of the following: the multilink communication has been successfully established; the multilink communication has not been established; only the link information is provided; the multilink communication has not been established; the link has been successfully added; the link has been successfully added; the link has been successfully removed; or the link has been removed.

[0039] A fourth embodiment provides a multilink communication method, the method comprising the steps of: a second multilink device transmitting a first request message to a first multilink device, the first request message carrying identifiers of at least two links and first instruction information for each of the at least two links, the first instruction information indicating an operation type for the links, the operation type including establishing multilink communication, and further including providing only link information or not establishing multilink communication; the second multilink device receiving a first response message from the first multilink device, the first response message carrying identifiers of the at least two links and second instruction information for each of the at least two links, the second instruction information indicating the state of the links.

[0040] In one possible implementation, the operation type further includes adding a link to a multilink communication link and / or removing a link from the multilink communication link.

[0041] In one possible implementation, the state includes one or more of the following: the multilink communication has been successfully established; the multilink communication has not been established; only the link information is provided; the multilink communication has not been established; the link has been successfully added; the link has been successfully added; the link has been successfully removed; or the link has been removed.

[0042] In one possible implementation, the first instruction information and / or the second instruction information are carried in a first pre-configured field within a multilink information element.

[0043] In one possible implementation, in the multilink information element carried in the first request message, the first value of the first pre-configured field indicates that the operation type is establishing multilink communication, and the second value of the first pre-configured field indicates that the operation type is providing only link information or not establishing multilink communication. Alternatively, in the multilink information element carried in the first response message, the first value of the first pre-configured field indicates that the state is successfully establishing multilink communication, the second value of the first pre-configured field indicates that the state is failing to establish multilink communication, and the third value of the first pre-configured field indicates that the state is providing only link information or not establishing multilink communication.

[0044] In one possible implementation, in the multilink information element carried in the first request message or the first response message, the value of the first pre-configured field is: A first value indicating that the operation type is the establishment of multilink communication, A second value indicating that the aforementioned state means that the multilink communication has been successfully established, A third value indicating that the aforementioned state means that the establishment of the multilink communication has failed, or The system includes one or more items from a fourth value indicating that the operation type or state is either providing only the link information or not establishing the multilink communication.

[0045] In one possible implementation, if the operation type is establishing multilink communication, not establishing multilink communication, providing only the link information, or adding the link to the multilink communication link, the first request message further carries station capability information. Alternatively, if the operation type is removing the link from the multilink communication link, the first request message does not carry station capability information.

[0046] In one possible implementation, the multilink information element further carries information about new links on the access point device.

[0047] The multilink device MLD common information field of the multilink information element carries a third instruction information indicating that the multilink information element is carrying information about the new link.

[0048] In one possible implementation, the information relating to the new link is carried within each of N consecutive beacon frames, where N is a positive integer.

[0049] For the technical effects of the fourth aspect or multiple possible implementations of the fourth aspect, refer to the description of the technical effects of the first aspect or multiple possible implementations of the first aspect.

[0050] A fifth embodiment provides a multilink communication method, the method comprising the steps of: a second multilink device transmitting a first request message to a first multilink device, the first request message carrying identifiers for at least two links and first instruction information for each of the at least two links, the first instruction information indicating an operation type for the link, the operation type further comprising adding a link to a multilink communication link, providing only link information, or not establishing multilink communication; the second multilink device receiving a first response message from the first multilink device, the first response message carrying identifiers for the at least two links and second instruction information for each of the at least two links, the second instruction information indicating the state of the link.

[0051] In one possible implementation, the operation type further includes establishing a multilink communication and / or removing a link from the multilink communication link.

[0052] In one possible implementation, the state includes one or more of the following: the multilink communication has been successfully established; the multilink communication has not been established; only the link information is provided; the multilink communication has not been established; the link has been successfully added; the link has been successfully added; the link has been successfully removed; or the link has been removed.

[0053] For the technical effects of the fifth aspect or any of the possible implementations of the fifth aspect, refer to the description of the technical effects of the second aspect or any of the possible implementations of the second aspect.

[0054] A multilink communication method is provided according to a sixth embodiment, the method comprising the steps of: a second multilink device transmitting a first request message to a first multilink device, the first request message carrying identifiers of at least two links and first instruction information for each of the at least two links, the first instruction information indicating an operation type for the link, the operation type including deleting a link to a multilink communication link, providing only link information, or not establishing multilink communication; the second multilink device receiving a first response message from the first multilink device, the first response message carrying identifiers of the at least two links and second instruction information for each of the at least two links, the second instruction information indicating the state of the link.

[0055] In one possible implementation, the operation type further includes establishing multilink communication and / or adding a link to the multilink communication link.

[0056] In one possible implementation, the state includes one or more of the following: the multilink communication has been successfully established; the multilink communication has not been established; only the link information is provided; the multilink communication has not been established; the link has been successfully added; the link has been successfully added; the link has been successfully removed; or the link has been removed.

[0057] For the technical effects of the sixth aspect or multiple possible implementations of the sixth aspect, refer to the description of the technical effects of the third aspect or multiple possible implementations of the third aspect.

[0058] According to a seventh aspect, a multilink communication method is provided, which includes the step of a first multilink device receiving a second message from a second multilink device, the second message carrying traffic-to-link mapping information; the first multilink device establishing or updating traffic-to-link mapping relationships based on the mapping information.

[0059] In this embodiment of the application, the second multilink device adds traffic-to-link mapping information to the second message, thereby enabling the first multilink device to further establish traffic-to-link mapping relationships when establishing a multilink, or to update those traffic-to-link mapping relationships after the multilink establishment is complete, resulting in more flexible management of traffic transmission and improved quality of service.

[0060] In one possible implementation, the second message further carries a fourth instruction information, the fourth instruction information indicating a second mode used to negotiate a mapping from a traffic identifier to a link. Prior to the step of the first multilink device receiving a second message from the second multilink device, the method further includes the step of the first multilink device sending a third message to the second multilink device, the third message carrying a fifth instruction information, the fifth instruction information indicating a first mode used to negotiate a mapping from a traffic identifier to a link.

[0061] In this implementation, the first and second multilink devices may negotiate the mapping from traffic identifiers to links, thereby further improving the flexibility of traffic transmission.

[0062] In one possible implementation, the first mode is one in which a traffic-to-link mapping is required to be established, but a specific traffic-to-link mapping method is not carried; one in which a traffic-to-link mapping is required, a proposed mapping method is carried, and the responder is permitted to modify the mapping relationships in the response frame; or one in which a traffic-to-link mapping is required, a requested mapping method is carried, and the responder is not permitted to modify the mapping relationships in the response frame.

[0063] It should be understood that the types mentioned above are not limiting, but rather merely examples of the first mode.

[0064] In one possible implementation, the second mode is that the traffic-to-link mapping has been successfully established and the final mapping method is carried; the traffic-to-link mapping has not been successfully established and the proposed mapping method is carried; the traffic-to-link mapping has not been successfully established and the requested mapping method is carried and the mapping can only be successfully established by using the mapping method when the requesting party resends the request; or the traffic-to-link mapping has failed to be established.

[0065] It should be understood that some of the above are not limitations, but rather merely examples of the second mode.

[0066] In one possible implementation, the second message is an association response frame or an EHT operation frame.

[0067] In one possible implementation, the second message is a broadcast message.

[0068] In this implementation, the second multilink device can directly broadcast traffic-to-link mapping information, further improving the flexibility of traffic transmission.

[0069] In one possible implementation, prior to the step of the first multilink device receiving the second message from the second multilink device, the method further includes the step of the first multilink device sending a fourth message to the second multilink device, the fourth message carrying seventh instruction information, the seventh instruction information indicating that the first multilink device supports broadcast traffic-to-link mapping information.

[0070] In this implementation, the first multilink device may notify the second multilink device in advance that it supports broadcast traffic-to-link mapping information, thereby notifying the first multilink device that it will establish or update traffic-to-link mapping relationships in broadcast mode. This improves the reliability of the solution.

[0071] In one possible implementation, the second message further carries an eighth instructional information indicating the cumulative number of updates to the traffic-to-link mapping information.

[0072] Thus, after receiving the second message (broadcast message), a multilink device that wakes up after a sleep cycle can, in a timely manner, know the update status of the traffic-to-link mapping information and determine whether or not the multilink device needs to update the traffic-to-link mapping relationship.

[0073] In one possible implementation, the second message is an association response frame or a beacon frame.

[0074] In one possible implementation, the second message further includes a ninth directive indicating the traffic direction of the traffic-to-link mapping, wherein the traffic direction is uplink, downlink, or uplink and downlink.

[0075] In this implementation, the multilink device may establish or update traffic-to-link mapping relationships for uplink transmission only, or for downlink transmission only, or for both uplink and downlink transmission only. This further improves the flexibility of traffic management.

[0076] In one possible implementation, the traffic-to-link mapping information is carried within the media access control MAC header or within an information element indicating the traffic-to-link mapping relationship.

[0077] In one possible implementation, the information element indicating the traffic-to-link mapping relationship carries a second pre-configured field, and when the second pre-configured field is a pre-configured value, the second pre-configured field instructs the first multilink device to map each traffic identifier to each link establishing multilink communication.

[0078] In one possible implementation, when the second pre-configured field is a pre-configured value, the information element indicating the traffic-to-link mapping relationship does not carry the traffic-to-link mapping information.

[0079] In this way, it is possible to reduce resource overhead.

[0080] In one possible implementation, the fourth instruction information and / or the fifth instruction information is carried in a third pre-configured field in an information element indicating the traffic-to-link mapping relationship, and the value of the third pre-configured field in the information element indicating the traffic-to-link mapping relationship carried in the third message or the fourth message is The first value indicates that the second mode is required to establish a traffic-to-link mapping, but no specific traffic-to-link mapping method is being carried. The second value indicates that the second mode is one in which a request is made to establish a mapping from traffic to a link, the proposed mapping method is carried, and the responder is permitted to modify the mapping relationship in the response frame. A third value indicating that the second mode is one in which a mapping from traffic to a link is requested, the requested mapping method is carried, and the responder is not permitted to modify the mapping relationship in the response frame. A fourth value indicating that the first mode is one in which the mapping from traffic to the link has been successfully established and the final mapping method is being carried, A fifth value indicating that the first mode is one in which the mapping from traffic to the link has not been successfully established and the proposed mapping method is carried out. A sixth value indicating that the first mode has not succeeded in establishing the mapping from the traffic to the link, and that the requested mapping method has been carried, and that the mapping can only be successfully established by using the mapping method when the requesting party resends the request, or The first mode includes one or more of the following seventh values, which indicate that the establishment of the mapping from the traffic to the link has failed.

[0081] It should be understood that the seven values ​​listed above are not limiting, but rather merely examples. In a particular implementation, the value of the third pre-configured field may be only a portion of the seven values ​​listed above, or it may include values ​​other than the seven listed above.

[0082] In one possible implementation, the traffic-to-link mapping information includes one or more link profile fields, each link profile field containing identifier information for one link and identifier information for one or more traffics mapped to the link, or one or more traffic profile fields, each traffic profile field containing identifier information for one traffic and identifier information for one or more links to which the traffic is mapped.

[0083] This implementation provides two different implementations of traffic-to-link mapping information, and further improves the flexibility of its solution.

[0084] According to an eighth aspect, a multilink communication method is provided, the method comprising the steps of: a second multilink device generating a second message, the second message carrying traffic-to-link mapping information; the second multilink device transmitting the second message to a first multilink device.

[0085] In one possible implementation, the second message further carries a fourth instruction information, the fourth instruction information indicating a second mode used to negotiate a mapping from a traffic identifier to a link. Prior to the step of the second multilink device generating the second message, the method further includes the step of the second multilink device receiving a third message from the first multilink device, the third message carrying a fifth instruction information, the fifth instruction information indicating a first mode used to negotiate a mapping from a traffic identifier to a link.

[0086] In one possible implementation, the first mode is one in which a traffic-to-link mapping is required to be established, but a specific traffic-to-link mapping method is not carried; one in which a traffic-to-link mapping is required, a proposed mapping method is carried, and the responder is permitted to modify the mapping relationships in the response frame; or one in which a traffic-to-link mapping is required, a requested mapping method is carried, and the responder is not permitted to modify the mapping relationships in the response frame.

[0087] In one possible implementation, the second mode is that the traffic-to-link mapping has been successfully established and the final mapping method is carried; the traffic-to-link mapping has not been successfully established and the proposed mapping method is carried; the traffic-to-link mapping has not been successfully established and the requested mapping method is carried and the mapping can only be successfully established by using the mapping method when the requesting party resends the request; or the traffic-to-link mapping has failed to be established.

[0088] In one possible implementation, the second message is an association response frame or an EHT operation frame.

[0089] In one possible implementation, the second message is a broadcast message.

[0090] In one possible implementation, prior to the step of the second multilink device generating a second message, the method further includes the step of the second multilink device receiving a fourth message from the first multilink device, wherein the fourth message carries seventh instruction information, the seventh instruction information indicating that the first multilink device supports broadcast traffic-to-link mapping information.

[0091] In one possible implementation, the second message further carries an eighth instructional information indicating the cumulative number of updates to the traffic-to-link mapping information.

[0092] In one possible implementation, the second message is an association response frame or a beacon frame.

[0093] In one possible implementation, the second message further includes a ninth directive indicating the traffic direction of the traffic-to-link mapping, wherein the traffic direction is uplink, downlink, or uplink and downlink.

[0094] In one possible implementation, the traffic-to-link mapping information is carried within the media access control MAC header or within an information element indicating the traffic-to-link mapping relationship.

[0095] In one possible implementation, the information element indicating the traffic-to-link mapping relationship carries a second pre-configured field, and when the second pre-configured field is a pre-configured value, the second pre-configured field instructs the first multilink device to map each traffic identifier to each link establishing multilink communication.

[0096] In one possible implementation, when the second pre-configured field is a pre-configured value, the information element indicating the traffic-to-link mapping relationship does not carry the traffic-to-link mapping information.

[0097] In one possible implementation, the fourth instruction information and / or the fifth instruction information is carried in a third pre-configured field in an information element indicating the traffic-to-link mapping relationship, and the value of the third pre-configured field in the information element indicating the traffic-to-link mapping relationship carried in the third message or the fourth message is The first value indicates that the second mode is required to establish a traffic-to-link mapping, but no specific traffic-to-link mapping method is being carried. The second value indicates that the second mode is one in which a request is made to establish a mapping from traffic to a link, the proposed mapping method is carried, and the responder is permitted to modify the mapping relationship in the response frame. A third value indicating that the second mode is one in which a mapping from traffic to a link is requested, the requested mapping method is carried, and the responder is not permitted to modify the mapping relationship in the response frame. A fourth value indicating that the first mode is one in which the mapping from traffic to the link has been successfully established and the final mapping method is being carried, A fifth value indicating that the first mode is one in which the mapping from traffic to the link has not been successfully established and the proposed mapping method is carried out. A sixth value indicating that the first mode has not succeeded in establishing the mapping from the traffic to the link, and that the requested mapping method has been carried, and that the mapping can only be successfully established by using the mapping method when the requesting party resends the request, or The first mode includes one or more of the following seventh values, which indicate that the establishment of the mapping from the traffic to the link has failed.

[0098] It should be understood that the seven values ​​listed above are not limiting, but rather merely examples. In a particular implementation, the value of the third pre-configured field may be only a portion of the seven values ​​listed above, or it may include values ​​other than the seven listed above.

[0099] In one possible implementation, the traffic-to-link mapping information includes one or more link profile fields, each link profile field containing identifier information for one link and identifier information for one or more traffics mapped to the link, or one or more traffic profile fields, each traffic profile field containing identifier information for one traffic and identifier information for one or more links to which the traffic is mapped.

[0100] For the technical effects of the eighth aspect or any of the possible implementations of the eighth aspect, refer to the description of the technical effects of the seventh aspect or any of the possible implementations of the seventh aspect.

[0101] According to the ninth aspect, a multilink device is provided, which includes a module, which is configured to perform a method according to any one of the first aspect or a plurality of possible implementations of the first aspect, or any one of the second aspect or a plurality of possible implementations of the second aspect, or any one of the third aspect or a plurality of possible implementations of the third aspect.

[0102] For example, the device includes a transceiver module.

[0103] The transceiver module is configured to receive a first request message transmitted by a second multilink device, the first request message carrying identifiers for at least two links and first instruction information for each of the at least two links, the first instruction information indicating the operation type of the link. The operation type includes establishing multilink communication, adding a link to a multilink communication link, or removing a link from a multilink communication link, and the operation type further includes providing only information about the link or not establishing multilink communication.

[0104] The transceiver module is further configured to send a first response message to a second multilink device, the first response message carrying identifiers for at least two links and second indication information for each of the at least two links, the second indication information indicating the state of the link.

[0105] According to the tenth aspect, a multilink device is provided, which includes a module, which is configured to perform a method according to any one of the fourth aspect or a plurality of possible implementations of the fourth aspect, or any one of the fifth aspect or a plurality of possible implementations of the fifth aspect, or any one of the sixth aspect or a plurality of possible implementations of the sixth aspect.

[0106] For example, the device includes a transceiver module.

[0107] The transceiver module is configured to send a first request message to a first multilink device, the first request message carrying identifiers for at least two links and first instruction information for each of the at least two links, the first instruction information indicating the operation type of the link. The operation type includes establishing multilink communication, adding a link to a multilink communication link, or removing a link from a multilink communication link, and the operation type further includes providing only information about the link or not establishing multilink communication.

[0108] The transceiver module is further configured to receive a first response message from a first multilink device, the first response message carrying identifiers for at least two links and second indication information for each of the at least two links, the second indication information indicating the state of the link.

[0109] According to the eleventh aspect, a multilink device is provided, which includes a module, which is configured to perform a method according to the seventh aspect or one of several possible implementations thereof.

[0110] For example, that device is A transceiver module configured to receive a second message from a second multilink device, wherein the second message carries traffic-to-link mapping information, and the transceiver module... Includes a processing module configured to establish or update traffic-to-link mapping relationships based on mapping information.

[0111] According to the twelfth aspect, a multilink device is provided, which includes a module, which is configured to perform a method according to the eighth aspect or any one of several possible implementations thereof.

[0112] For example, that device is A processing module configured to generate a second message, The system includes a transceiver module configured to send a second message to a first multilink device.

[0113] According to the thirteenth aspect, a multilink device is provided, which includes a processor, which is coupled to memory. The processor is configured to execute computer programs or instructions stored in memory, thereby enabling the device to perform a method according to any one of the first aspect or a plurality of possible implementations thereof, or the second aspect or a plurality of possible implementations thereof, or the third aspect or a plurality of possible implementations thereof, or the fourth aspect or a plurality of possible implementations thereof, or the fifth aspect or a plurality of possible implementations thereof, or the sixth aspect or a plurality of possible implementations thereof, or the seventh aspect or a plurality of possible implementations thereof, or the eighth aspect or a plurality of possible implementations thereof.

[0114] Selectively, memory is located outside the device.

[0115] Selectively, the device includes memory. The memory is connected to at least one processor, and the memory stores instructions that can be executed by at least one processor.

[0116] According to the 14th aspect, a chip is provided. The chip is coupled to memory and configured to read and execute program instructions stored in memory, thereby performing a method according to any one of the first aspect or any of several possible implementations thereof, or the second aspect or any of several possible implementations thereof, or the third aspect or any of several possible implementations thereof, or the fourth aspect or any of several possible implementations thereof, or the fifth aspect or any of several possible implementations thereof, or the sixth aspect or any of several possible implementations thereof, or the seventh aspect or any of several possible implementations thereof, or the eighth aspect or any of several possible implementations thereof.

[0117] According to the 15th aspect, a computer program product is provided which includes a plurality of instructions. When these instructions are executed by a computer, the computer performs a method according to the first aspect or one of several possible implementations of the first aspect, or the second aspect or one of several possible implementations of the second aspect, or the third aspect or one of several possible implementations of the third aspect, or the fourth aspect or one of several possible implementations of the fourth aspect, or the fifth aspect or one of several possible implementations of the fifth aspect, or the sixth aspect or one of several possible implementations of the sixth aspect, or the seventh aspect or one of several possible implementations of the seventh aspect, or the eighth aspect or one of several possible implementations of the eighth aspect.

[0118] According to the sixteenth aspect, a computer-readable storage medium containing programs or instructions is provided. When those programs or instructions are executed by a computer, a method is performed according to the first aspect or one of several possible implementations of the first aspect, or the second aspect or one of several possible implementations of the second aspect, or the third aspect or one of several possible implementations of the third aspect, or the fourth aspect or one of several possible implementations of the fourth aspect, or the fifth aspect or one of several possible implementations of the fifth aspect, or the sixth aspect or one of several possible implementations of the sixth aspect, or the seventh aspect or one of several possible implementations of the seventh aspect, or the eighth aspect or one of several possible implementations of the eighth aspect. [Brief explanation of the drawing]

[0119] [Figure 1] This is a network diagram of the architecture of a communication system to which one embodiment of this application may be applied. [Figure 2] This is a schematic diagram of the configuration of a multilink device 200 according to one embodiment of this application. [Figure 3] This is a schematic diagram of the configuration of a multilink device 300 according to one embodiment of this application. [Figure 4] This is a flowchart of a multilink communication method according to one embodiment of this application. [Figure 5] This is a schematic diagram of a multilink information element according to one embodiment of this application. [Figure 6] This is a schematic diagram of another multilink information element according to one embodiment of this application. [Figure 7A] This is a schematic diagram of another multilink information element according to one embodiment of this application. [Figure 7B] This is a schematic diagram of another multilink information element according to one embodiment of this application. [Figure 8] This is a schematic diagram of another multilink information element according to one embodiment of this application. [Figure 9] This is a flowchart of a traffic-to-link mapping method according to one embodiment of this application. [Figure 10A] This is a schematic diagram of a possible MAC header according to one embodiment of this application. [Figure 10B] This is a schematic diagram of a possible traffic identifier bitmap according to one embodiment of this application. [Figure 10C] This is a schematic diagram of another possible MAC header according to one embodiment of this application. [Figure 10D] This is a schematic diagram of another possible MAC header according to one embodiment of this application. [Figure 10E] This is a schematic diagram of another possible link identifier bitmap according to one embodiment of this application. [Figure 10F] This is a schematic diagram of another possible MAC header according to one embodiment of this application. [Figure 11A] This is a schematic diagram of a traffic identifier to link mapping information element according to one embodiment of this application. [Figure 11B] This is a schematic diagram of a mapping information element from another traffic identifier to a link, according to one embodiment of this application. [Figure 11C] This is a schematic diagram of a mapping information element from another traffic identifier to a link, according to one embodiment of this application. [Figure 11D] This is a schematic diagram of a mapping information element from another traffic identifier to a link, according to one embodiment of this application. [Figure 11E] This is a schematic diagram of a mapping information element from another traffic identifier to a link, according to one embodiment of this application. [Figure 12]This is a schematic diagram of other possible traffic identifier-to-link mapping information elements according to one embodiment of this application. [Figure 13] This is a schematic diagram of other possible traffic identifier-to-link mapping information elements according to one embodiment of this application. [Figure 14] This is a flowchart of a method for updating identifier-to-link mapping relationships according to one embodiment of this application. [Figure 15] This is a schematic diagram of a possible frame configuration of an EHT operating frame according to one embodiment of this application. [Figure 16] This is a schematic diagram of a mapping information element from a traffic identifier to a link, carried within a beacon frame according to one embodiment of this application. [Figure 17] This is a schematic diagram of other possible traffic identifier-to-link mapping information elements according to one embodiment of this application. [Modes for carrying out the invention]

[0120] The technical solutions in multiple embodiments of this application may be applied to various communication systems, such as, for example, fourth-generation (4G) communication systems, fifth-generation (5G) communication systems, sixth-generation (6G) communication systems, other future evolutionary systems, or various other wireless communication systems using wireless access technology. The technical solutions in multiple embodiments of this application can be used provided that there is a requirement for multilink communication in the communication system.

[0121] For example, Figure 1 is a network diagram of the architecture of a communication system to which one embodiment of this application may be applied. The communication system includes at least one access point station multi-link device (AP STA MLD) and at least one non-access point station multi-link device (non-AP STA MLD). The access point station multi-link device may also be referred to as an access point multi-link device, or simply as an access point device, and the English abbreviation AP STA MLD corresponding to the access point station multi-link device may be replaced by AP MLD. The non-access point station multi-link device may also be referred to as a station multi-link device, or simply as a station device, and the English abbreviation non-AP STA MLD corresponding to the non-AP station multi-link device may be replaced by STA MLD or non-AP MLD. An AP MLD includes one or more access points (AP), and a non-AP MLD includes one or more non-AP stations (non-AP STA). It should be understood that the communication system shown in Figure 1 uses one AP MLD and one non-AP MLD as one example. In actual applications, the communication system may further include more AP MLDs or non-AP MLDs, the AP MLDs may further include more APs or fewer APs, and the non-AP MLDs may further include more non-AP STAs or fewer non-AP STAs. This is not limited to this embodiment of the application.

[0122] In this embodiment of the application, multilink devices can communicate with each other after establishing an association relationship (or communication link) between multiple multilink devices. For example, one or more non-AP STAs in a station multilink device can communicate with one or more APs in an access point multilink device after establishing a certain association relationship. As shown in Figure 1, AP1 is associated with non-AP STA1, and AP2 is associated with non-AP STA 2A. Of course, station multilink devices and station multilink devices can also communicate with each other, i.e., they can communicate device to device (D2D).

[0123] For the sake of clarity, in the following multiple embodiments, we will primarily use one example in which a first multilink device and a second multilink device perform multilink communication. The first multilink device is an AP MLD and the second multilink device is a non-AP MLD, or the second multilink device is an AP MLD and the first multilink device is a non-AP MLD, or both the first and second multilink devices are non-AP MLDs, or both the first and second multilink devices are AP MLDs.

[0124] Figure 2 is a schematic diagram of the configuration of a multilink device 200 according to one embodiment of this application. The multilink device 200 can implement functions or steps implemented by the first or second multilink device in the embodiment of the method of this application, corresponding to the embodiment of the method. For example, establishing or updating a multilink communication link, or establishing or updating a mapping relationship from a traffic identifier to a link. Specific functions or steps are described in detail below.

[0125] The multilink device 200 may include a transceiver module 210 and a processing module 220. Optionally, the communication device may further include a storage unit. The storage unit may be configured to store instructions (code or programs) and / or data. The transceiver module 210 and the processing module 220 may be coupled to the storage unit. For example, the processing module 220 may read instructions (code or programs) and / or data from the storage unit and implement a corresponding method.

[0126] The processing module 220 may be implemented by a processor or a circuit component related to the processor, and the transceiver module 210 may be implemented by a transceiver, a circuit component related to the transceiver, or a communication interface.

[0127] The above-mentioned units may be arranged independently, or they may be partially or completely integrated. For example, the transceiver module 210 may be integrated by a transmitting unit and a receiving unit.

[0128] The following description illustrates some of the multiple possible product forms of the multilink device. It should be understood that the following description is merely illustrative, and the product forms of the multilink device in the multiple embodiments of this application are not limited thereto.

[0129] In one possible product form, the multilink devices in multiple embodiments of this application may be implemented by using a common bus architecture. For example, Figure 3 is a schematic diagram of the configuration of a multilink device 300 according to one embodiment of this application. The multilink device 300 includes a transceiver 310 and a processor 320.

[0130] The transceiver 310 is configured to communicate with other devices using a transmission medium, thereby enabling devices within the multilink device 300 to communicate with other devices. For example, when multilink device 300 is a first multilink device, the other device is a second multilink device, or when multilink device 300 is a second multilink device, the other device is a first multilink device. The processor 320 may transmit and receive data using the transceiver 310.

[0131] In one possible implementation, the transceiver 310 may specifically be a radio frequency unit. The radio frequency unit may be independent of the multilink device 300, or it may be integrated into the multilink device 300.

[0132] In one possible implementation, the transceiver 310 may further include an antenna, such as a remote antenna independent of the multilink device 300, or an antenna integrated into the multilink device 300. The multilink device 300 includes at least one processor 320, which is configured to implement the functions of the first multilink device or the functions of the first multilink device in the manner provided by some embodiments of this application, or to assist the multilink device 300 in implementing those functions. In Figure 3, the antenna is represented by using a dashed box, which is optional for the multilink device 300.

[0133] In some embodiments of this application, the processor 320 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic device, individual gate or transistor logic device, or individual hardware components, which may implement or perform the methods, steps, and logic block diagrams disclosed in some embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in some embodiments of this application may be performed directly by the hardware processor or by using a combination of hardware and software modules in the processor.

[0134] Furthermore, the multilink device 300 may further include at least one memory 330, the at least one memory 330 configured to store program instructions and / or data. The memory 330 is coupled to the processor 320. The coupling in this embodiment of the application may be an indirect coupling or communication connection between a plurality of devices, a plurality of units, or a plurality of modules, in an electrical, mechanical, or other form, used for information exchange between the plurality of devices, a plurality of units, or a plurality of modules. The processor 320 may cooperate with the memory 330. The processor 320 may execute program instructions and / or data stored in the memory 330, thereby the multilink device 300 implements the corresponding method. At least one of the at least one memory may be located within the processor. In Figure 3, the memory is represented by using a dashed box, which is optional for the multilink device 300.

[0135] In this embodiment of the application, the memory 330 may be non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), or it may be volatile memory such as random-access memory (RAM). The memory may also be any other medium that is accessible to a computer and capable of carrying or storing expected program code in the form of instructions or data structures. The memory in this embodiment of the application may also be a circuit or any other device which is capable of implementing a memory function and is configured to store program instructions and / or data.

[0136] It should be understood that certain connecting media between the transceiver 310, processor 320, and memory 330 are not limited to this embodiment of the application. In this embodiment of the application, the memory 330, processor 320, and transceiver 310 are connected by using a bus 340 in Figure 3. The bus is represented by the use of a thick line in Figure 3. The above is merely an example for illustrative purposes. The connection methods of other components are not limited to these. Buses may be classified as address buses, data buses, control buses, etc. For ease of representation, only one thick line is used to represent the bus in Figure 3, but this does not indicate that there is only one bus or only one type of bus.

[0137] As another possible product form, the multilink device in this embodiment of this application may further be implemented by using components such as one or more FPGAs (field-programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gate logic, individual hardware components, any other suitable circuitry, or any combination of circuits capable of performing the various functions described in this application.

[0138] It should be understood that the multilink device in the above-described product form has the function of either the first or second multilink device in any of the embodiments of this application. Details are not repeated herein.

[0139] The following description details several technical solutions in several embodiments of this application with reference to several accompanying drawings in several embodiments of this application.

[0140] Figure 4 is a flowchart of a multilink communication method according to one embodiment of this application. The method may be applied to the communication system shown in Figure 1. The method includes the following steps:

[0141] S401: The second multilink device sends a first request message to the first multilink device, the first multilink device receives the first request message sent by the second multilink device, the first request message carries identifiers for one or more links and first instruction information for each of those links, the first instruction information indicating the operation type of the corresponding link.

[0142] The first multilink device may be an AP MLD and the second multilink device may be a non-AP MLD, or the second multilink device may be an AP MLD and the first multilink device may be a non-AP MLD, or both the first and second multilink devices may be non-AP MLDs.

[0143] In this embodiment of this application, the link operation type may include one or more of the following: (1) establishing multilink communication; (2) providing only link information or not establishing multilink communication; (3) adding a link to a multilink communication link; and (4) removing a link from a multilink communication link. It should be understood that the above four operation types are not limiting but rather examples, and other operation types are also applicable to actual applications.

[0144] Providing only link information means that the first request message provides only link information and is not used to request the establishment of multilink communication. In other words, in this specification, not establishing multilink communication and providing only link information may be used interchangeably.

[0145] Each link has only one operation type, for example, one of the four operation types mentioned above.

[0146] If the first request message carries only the identifier of a single link and first instruction information, the operation type indicated by the first instruction information may be any one of the four operation types described above.

[0147] When the first request message carries only the identifiers of multiple links and the first instruction information, the operation types of any two of those multiple links may be the same or different.

[0148] For example, when the first request message carries the identifier of the first link and the first instruction information, and the identifier of the second link and the first instruction information, the operation type indicated by the first instruction information of the first link and the operation type indicated by the first instruction information of the second link may be any one of the following a to f.

[0149] a. The operation type indicated by the first instruction information for the first link is the establishment of multilink communication, and the operation type indicated by the first instruction information for the second link is not to establish multilink communication and to provide only link information.

[0150] b. The operation type indicated by the first instruction information for the first link is adding a link to a multilink communication link, and the operation type indicated by the first instruction information for the second link is not establishing multilink communication and providing only link information.

[0151] c. The operation type indicated by the first instruction information for the first link is the removal of the link from the multilink communication link, and the operation type indicated by the first instruction information for the second link is the failure to establish multilink communication and the provision of link information only.

[0152] d. The operation type indicated by the first instruction information for the first link is the establishment of multilink communication, and the operation type indicated by the first instruction information for the second link is the addition of a link to the multilink communication link.

[0153] e. The operation type indicated by the first instruction information for the first link is the establishment of multilink communication, and the operation type indicated by the first instruction information for the second link is the removal of the link from the multilink communication link.

[0154] f. The operation type indicated by the first instruction information for the first link is the addition of a link to a multilink communication link, and the operation type indicated by the first instruction information for the second link is the removal of a link from a multilink communication link.

[0155] The two links are used as examples above. In actual application, the first request message may further include identifiers for other links, such as the third and fourth links, and the first instruction information. The operation types corresponding to the third and fourth links may be the same as or different from the operation types of the first or second link, and further details are not described herein.

[0156] Selectively, the first request message may further include station capability information for each link or other parameter information for each link. This is not limited to this embodiment of the application.

[0157] After receiving the first request message, the first multilink device performs the corresponding operation on each link indicated by the identifier carried in the first request message, based on the operation type indicated by the first instruction information corresponding to that link.

[0158] For links where the operation type is to provide only link information or to not establish multilink communication, the following operations may not be performed. Alternatively, for links where the operation type is to provide only link information or to not establish multilink communication, operations such as link establishment, link deletion, or link addition may not be performed, and other operations such as saving or modifying link information may be performed on such links. This is not limited herein.

[0159] For all links indicated by all identifiers carried in the first request message (except for links where the operation type is to provide only link information or to not establish multilink communication), a first response message may be generated based on the status of each link after performing the corresponding operation. Then, S402 is performed.

[0160] S402: The first multilink device sends a first response message to the second multilink device, and the second multilink device receives the first response message sent by the first multilink device, the first response message carrying identifiers for one or more links and second instruction information for each link, the second instruction information indicating the status of the links.

[0161] Specifically, the state of each link corresponds to the operation type indicated by the first instruction information corresponding to that link.

[0162] As one example, use the first link, and the state of the first link may be one of the following states:

[0163] (1) The state of the first link is either that multilink communication has been successfully established or that multilink communication has failed to be established. This state is used as a response to the operation type of the first link, which is the establishment of multilink communication.

[0164] (2) The state of the first link is that only link information is provided or multilink communication is not established, and this state is used as a response to the operation type of the first link, which is that only link information is provided or multilink communication is not established.

[0165] (3) The state of the first link is either that the link was added successfully or that the link was added unsuccessfully. This state is used as a response to the operation type of the first link, which is adding a link to a multilink communication link.

[0166] (4) The state of the first link is either that the link has been successfully deleted or that the link has been deleted. This state is used as a response to the operation type of the first link, which is the deletion of a link from a multilink communication link.

[0167] It should be understood that each link has only one type of state. When the first response message carries identifiers for multiple links and second instruction information, any two of those links may have the same or different states.

[0168] Of course, some of the above conditions are not limiting, but rather examples, and other types of operations may also be applicable in actual applications.

[0169] It should be noted that, assuming no multilink communication link has been established between the first and second multilink devices before the second multilink device sends the first request message to the first multilink device, steps S401 to S402, for example, represent the methods performed by the first and second multilink devices during the multilink establishment phase. In this case, the type of operation indicated by the first instruction information carried in the first request message may be the establishment of multilink communication, the provision of link information only, or the failure to establish multilink communication, and not the addition of a link to a multilink communication link or the removal of a link from a multilink communication link. For example, S401 to S402 are methods performed by the first multilink device and the second multilink device during the link reassociation stage. Only if the first multilink device and the second multilink device have already established a multilink communication link before the second multilink device sends the first request message to the first multilink device, the operation type of the first instruction information carried in the first request message may be to add a link to the multilink communication link or to delete a link from the multilink communication link.

[0170] The following description details the specific implementation of the first link device and the second multilink device during the multilink establishment phase.

[0171] Specifically, we will use an example where the first multilink device is an AP MLD and the second multilink device is a non-AP MLD. Before the non-AP MLD can communicate with the AP MLD, it must perform multilink establishment. The non-AP MLD may send an association request frame (the first request message) to the AP MLD. After receiving the association request frame, the AP MLD implements multilink establishment by sending an association response frame (the first response message) to the non-AP MLD.

[0172] Selectively, information such as the identifier of each link and the first instruction information in the association request frame, or information such as the identifier of each link and the second instruction information in the association response frame, may be carried within a multi-link information element (ML element) (the multi-link information element may also be referred to as a multi-link element).

[0173] Figure 5 is a schematic diagram of a multilink information element according to one embodiment of this application. As shown in Figure 5, the multilink information element includes a Control field, a Multilink Device Common Information (MLD common Info) field, and zero or one or more Link profile subelements (or referred to as Link Information fields).

[0174] The multilink device common information field carries common MLD information across all links, such as the MLD's Media Access Control (MAC) address. Link-specific information, such as the MLD's station capability information, link operation type information (i.e., first instruction information), or link status information (i.e., second instruction information), and other link-related parameter information, is carried within the link profile sub-elements.

[0175] Non-AP MLDs and AP MLDs can exchange information about multilinks and complete multilink establishment by including ML elements in association request frames and association response frames. Communication may then be performed on these links.

[0176] Selectively, the first instruction information and / or the second instruction information are carried within a first pre-configured field in the multilink information element, the first pre-configured field is located within the link profile sub-element, as shown in Figure 6.

[0177] In one possible design, when a multilink information element is located within an association request frame and an association response frame, each of the values ​​of a first pre-defined field may represent a different meaning. In other words, the meaning of the value of the first pre-defined field must be determined based on the frame type in which the first pre-defined field is located (including association request frames and association response frames), and based on the value of the first pre-defined field.

[0178] For example, Table 1 shows several possible values ​​for the first pre-configured field (i.e., Action) in the multilink information element carried in the association request frame, and examples of the meanings of those values. Table 2 shows several possible values ​​for the first pre-configured field (i.e., Status) in the multilink information element carried in the association response frame, and examples of the meanings of those values. [Table 1]

[0179] To facilitate identification, a first pre-configured field in the multilink information element carried within the association request frame is referred to herein as the first field.

[0180] Table 1 lists two possible values ​​for the first field, but it should be noted that this does not mean that the first field must contain only those two values. In practical application, the value of the first field may be only a subset of the values ​​in Table 1, and may also contain other values ​​not listed in Table 1. [Table 2]

[0181] To facilitate identification, the first pre-configured field in the multilink information element carried within the association response frame is referred to herein as the second field.

[0182] Table 2 above lists three possible values ​​for the second field, but it should be noted that this does not mean that the second field must contain all three of those values. In practical application, the value of the second field may be only a subset of the values ​​in Table 2, and may also contain other values ​​not listed in Table 2.

[0183] In other possible designs, when the multilink information element is located within the association request frame and the association response frame, the value of the first pre-configured field may have the same meaning. In other words, the meaning of the value of the first pre-configured field may be directly determined based on the value of the first pre-configured field.

[0184] For example, Table 3 shows examples of multiple possible values ​​for a first pre-configured field in a multilink information element carried within an association request frame or association response frame, and the meanings of those values. [Table 3]

[0185] To facilitate identification, the first pre-configured field in the multilink information element carried within the association request frame and association response frame is collectively referred to herein as the third field (the third field is the state when carried within the association response frame and the operation when carried within the association request frame).

[0186] In Table 3, the fourth value is used in both the association request frame and the association response frame to indicate that only link information is provided or that multilink communication is not established. In a particular implementation, multiple different values ​​may be used in the association request frame and the association response frame to indicate that only link information is provided or that multilink communication is not established. For example, the fourth value of the first pre-configured field indicates that the operation type is to provide only link information or not establish multilink communication, and the fifth value of the first pre-configured field indicates that the state is to provide only link information or not establish multilink communication.

[0187] Table 3 above lists four possible values ​​for the third field, but it should be noted that this does not mean that the third field must contain all four of those values. In actual application, the value of the third field may be only a subset of the values ​​in Table 3, and may also contain values ​​other than those listed in Table 3.

[0188] In addition to establishing multilinks, multilink devices may need to add or remove one or more links in a communication process that may be implemented by sending reassociation request frames and reassociation response frames.

[0189] The following description details the specific implementation of the first link device and the second multilink device during the link reassociation phase.

[0190] Specifically, the first multilink device may send a reassociation request frame (first request message) to the second multilink device, and after receiving the association request frame, the second multilink device sends a reassociation response frame (second response message) to the second multilink device to implement link reassociation.

[0191] Selectively, information such as the identifier of each link and the first instruction information in the reassociation request frame, or information such as the identifier of each link and the second instruction information in the reassociation response frame, may be carried within a multi-link information element (ML element) (the multi-link information element may also be referred to as a multi-link element).

[0192] Selectively, the first instruction information and / or the second instruction information are carried in a second preset field within a multilink information element, the second preset field being located within a link profile sub-element. The second preset field and the first preset field described herein may be the same field, as shown in Figure 7A, or they may be multiple different fields, as shown in Figure 7B. This is not limited to this embodiment of the application.

[0193] The following description uses one example where the second pre-configured field and the first pre-configured field are the same field.

[0194] In one possible design, when a multilink information element is located within a reassociation request frame and a reassociation response frame, each of the values ​​of the first pre-configured field may represent a different meaning. In other words, the meaning of the value of the first pre-configured field must be determined based on the frame type in which the first pre-configured field is located (including the reassociation request frame and the reassociation response frame), and based on the value of the first pre-configured field.

[0195] For example, Table 4 shows multiple possible values ​​for the first pre-configured field (Action) in the multilink information element carried in the reassociation request frame, and examples of the meanings of those values. Table 5 shows multiple possible values ​​for the first pre-configured field (Status) in the multilink information element carried in the reassociation response frame, and examples of the meanings of those values. [Table 4]

[0196] To facilitate identification, the first pre-configured field in the multilink information element carried within the reassociation request frame is referred to herein as the fourth field.

[0197] Table 4 above lists three possible values ​​for the fourth field, but it should be noted that this does not mean that the fourth field must contain only those three values. In actual application, the value of the fourth field may be only a subset of the values ​​in Table 4, and may also contain values ​​other than those listed in Table 4.

[0198] Selectively, when a specific link profile sub-element within a multilink element carried in a reassociation request frame is used to remove a link, that link profile sub-element may contain only the link identifier and the operation type of that link, or it may not carry any information other than the link identifier and operation type, for example, it may not need to carry capability information of the stations operating on the link, thereby reducing resources. [Table 5]

[0199] To facilitate identification, the first pre-configured field in the multilink information element carried within the reassociation response frame is referred to herein as the fifth field.

[0200] Table 5 above lists the five possible values ​​for the fifth field, but it should be noted that this does not mean that the fifth field must contain all five of those values. In actual application, the value of the fifth field may be only a subset of the values ​​in Table 5, and may also contain other values ​​not listed in Table 5.

[0201] In other possible designs, when the multilink information element is located within the reassociation request frame and the reassociation response frame, the value of the first pre-configured field may have the same meaning. In other words, the meaning of the value of the first pre-configured field may be directly determined based on the value of the first pre-configured field.

[0202] For example, Table 6 shows several possible values ​​for a first pre-configured field in a multilink information element carried within a reassociation request frame or reassociation response frame, and examples of the meanings of those values. [Table 6]

[0203] To facilitate identification, the first pre-configured field in the multilink information element carried within the reassociation request frame or reassociation response frame is collectively referred to herein as the sixth field.

[0204] In Table 6, the seventh value is used in both the reassociation request frame and the reassociation response frame to indicate that only link information is provided. In a particular implementation, multiple different values ​​may be used in the reassociation request frame and the reassociation response frame to indicate that only link information is provided or that multilink communication is not established. For example, the seventh value of the first pre-configured field indicates that the operation type is to provide only link information or not to establish multilink communication, and the eighth value of the first pre-configured field indicates that the state is to provide only link information or not to establish multilink communication.

[0205] Table 6 above lists seven possible values ​​for the sixth field, but it should be noted that this does not mean that the sixth field must contain all seven of those values. In practical application, the value of the sixth field may be only a subset of the values ​​in Table 6, and may also contain other values ​​not listed in Table 6.

[0206] In other possible designs, the first, second, fourth, and fifth fields may be combined to form a single field, such as a seventh field. In other words, the value of the first pre-configured field may have the same meaning when the multilink information element is located within an association request frame, an association response frame, a reassociation request frame, and a reassociation response frame.

[0207] For example, Table 7 shows examples of multiple possible values ​​for a first pre-configured field in a multilink information element carried within an association request frame, association response frame, reassociation request frame, or reassociation response frame, and the meanings of those values. [Table 7]

[0208] To facilitate identification, the first pre-configured field in the multilink information element carried within the association request frame, association response frame, reassociation request frame, or reassociation response frame is collectively referred to herein as the seventh field.

[0209] In Table 7, the fourth value is used in both the request frame and the response frame to indicate that only link information is provided. In a particular implementation, multiple different values ​​may be used in the request frame and the response frame to indicate that only link information is provided. For example, the fourth value of the first pre-configured field indicates that the operation type is to provide only link information or not to establish multilink communication, and the tenth value of the first pre-configured field indicates that the state is to provide only link information.

[0210] Table 7 above lists nine possible values ​​for the seventh field, but it should be noted that this does not mean that the seventh field must contain all nine of those values. In actual application, the value of the seventh field may be only a subset of the values ​​in Table 7, and may include additional values ​​not listed in Table 7.

[0211] In this embodiment of the application, with respect to the AP MLD, not all links may be initiated initially. Therefore, new links may exist (or be in use or activated) in the communication process. When the AP MLD initiates a new link, it may carry information about the new link in a multilink information element, such as a new link profile sub-element.

[0212] Selectively, as shown in Figure 8, the MLD common information field within the multilink information element may carry a third instruction information indicating that the multilink element is carrying information about a new link.

[0213] Selectively, when an AP MLD initiates (or uses or activates) a new link, it is possible to ensure that information about the new link is effectively received by non-AP MLDs by carrying information about the new link in each of N consecutive beacon frames where N is a positive integer. This improves the reliability of the system. The value of N is set and broadcast by the AP or specified in the standard. This is not limited to this embodiment of the application. Selectively, the value of N may be any value in the range [1,10], for example, 2, 3, 4, 5, etc.

[0214] From the above, it is possible to know that in this embodiment of the application, the first instruction information is carried in the first request message (association request frame or reassociation request frame), and the second instruction information is carried in the first response message (association response frame or reassociation response frame). Thus, when establishing a multilink, the MLD establishes multilink communication on some or all of the links it supports, and further, based on the communication requirements for subsequent communications, it may add links to the established multilink communication links or remove links from the established multilink communication links. In addition, it may start new links. This improves the flexibility of the multilink communication performed by the MLD in several ways and fully satisfies the requirement for the MLD to dynamically update communication links.

[0215] Furthermore, in order to improve multilink communication performance and better manage traffic, several embodiments of this application further provide traffic-to-link mapping solutions to serve multiple different services for different traffic. For example, non-critical traffic is mapped to a portion of the links, while critical traffic is mapped to all of the links. Alternatively, different traffic is mapped to corresponding links based on the rate and latency characteristics of multiple different links.

[0216] Figure 9 is a flowchart of a traffic-to-link mapping method according to one embodiment of this application. The method may be applied to the communication system shown in Figure 1. The method includes the following steps:

[0217] S901: The second multilink device sends a second message to the first multilink device, and the first multilink device receives the second message from the second multilink device, which carries mapping information from traffic identifier to link.

[0218] The second multilink device may transmit the second message to the first multilink device in broadcast mode (in other words, the second message is a broadcast message), or in multicast mode (in other words, the second message is a multicast message), or in unicast mode (in other words, the second message is a unicast message). This is not limited to this embodiment of the application.

[0219] When the second link may send a second message to the first multilink device in unicast mode, the first multilink device may be an AP MLD and the second multilink device may be a non-AP MLD, or the second multilink device may be an AP MLD and the first multilink device may be a non-AP MLD, or both the first and second multilink devices are non-AP MLDs.

[0220] When the second link may send a second message to the first multilink device in broadcast mode or multicast mode, the second multilink device may be an AP MLD, and the first multilink device may be a non-AP MLD.

[0221] Selectively, in unicast mode, before the second multilink device sends a second message to the first multilink device, the second multilink device also receives a third message from the first multilink device, which is used to request the establishment or updating of a traffic identifier-to-link mapping relationship. In other words, the second message is a response message to the third message.

[0222] Selectively, in unicast mode, the second message may further carry a fourth instruction information, the fourth instruction information indicating a second mode used to negotiate the mapping from traffic identifiers to links. Before the first multilink device receives the second message from the second multilink device, the first multilink device may further send a third message to the second multilink device, the third message carrying a fifth instruction information, the fifth instruction information indicating a first mode used to negotiate the mapping from traffic identifiers to links.

[0223] The first mode may be: a traffic-to-link mapping is required to be established, but the specific traffic-to-link mapping method of the requesting party (i.e., the first multilink device) is not carried; a traffic-to-link mapping is required to be established, the proposed mapping method is carried, and the responding party (i.e., the second multilink device) is permitted to modify the mapping relationships in the response frame; or a traffic-to-link mapping is required to be established, the requested mapping method is carried, and the responding party is not permitted to modify the mapping relationships in the response frame.

[0224] The second mode may be that the mapping from traffic to link has been successfully established and the final mapping method is carried; that the mapping from traffic to link has not been successfully established and the proposed mapping method is carried; that the mapping from traffic to link has not been successfully established and the requested mapping method is carried and the mapping can only be successfully established by using the mapping method if the requesting party resends the request; or that the mapping from traffic to link has failed to be established.

[0225] Selectively, in broadcast mode, the second message may also carry a sixth instruction, which indicates that the second message carries mapping information from the traffic to the link being broadcast.

[0226] Selectively, in broadcast mode, when the first multilink device receives a second message from the second multilink device, the first multilink device sends a fourth message to the second multilink device, the fourth message carries seventh instruction information, which indicates that the first multilink device supports mapping information from broadcast traffic to the link.

[0227] Selectively, in broadcast mode, the second message further carries an eighth instruction indicating the cumulative number of updates to the traffic-to-link mapping information, so that a multilink device that wakes up after sleep after receiving the second message knows the update status of the traffic-to-link mapping information and decides whether or not it needs to update the traffic-to-link mapping relationship.

[0228] In one possible design, the traffic-to-link mapping information may be carried within the MAC's header field.

[0229] Specifically, the new control type is defined by using the A-Control subfield in the MAC header to carry mapping information from traffic identifiers to links.

[0230] Example 1: Figure 10A is a schematic diagram of a possible MAC header according to one embodiment of this application. The MAC header carries a control ID and control information corresponding to the control ID. The control information field includes two link profile fields. Each link profile includes one link identifier (link ID) and identifier information for the traffic mapped to the link.

[0231] Traffic identifier information may be a Traffic ID (TID) bitmap, or it may be a starting TID and an ending TID. TIDs between the starting TID and the ending TID are mapped to their respective links. Alternatively, the identifier information may take other forms, and this is not limited to this embodiment of the application.

[0232] Each bit in the traffic identifier bitmap corresponds to one traffic identifier, multiple different bits correspond to multiple different traffic identifiers, and each traffic identifier represents a specific type of traffic. For example, bit i corresponds to traffic identifier i, the value of i starts from 0 and the maximum value is the number of bits in the traffic identifier bitmap minus 1. The number of bits in the traffic identifier bitmap may be 4, 8, 12, or 16, etc. A specific number of bits may be determined based on the number of bits configured in the control information. This is not limited to this application.

[0233] Figure 10B is a schematic diagram of one possible traffic identifier bitmap according to one embodiment of this application. The traffic identifier bitmap contains 8 bits. The first bit (bit 0) corresponds to traffic with a TID of 0, the second bit (bit 1) corresponds to traffic with a TID of 1, the third bit (bit 2) corresponds to traffic with a TID of 3, the fourth bit (bit 3) corresponds to traffic with a TID of 4, the fifth bit (bit 4) corresponds to traffic with a TID of 4, the sixth bit (bit 5) corresponds to traffic with a TID of 5, the seventh bit (bit 6) corresponds to traffic with a TID of 6, and the eighth bit (bit 7) corresponds to traffic with a TID of 7. Traffic with a corresponding field value of 1 is mapped to a link, or traffic with a corresponding field value of 0 is mapped to that link. For example, traffic with a corresponding field value of 1 is mapped to that link. In this case, the traffic identifier bitmap shown in Figure 10B indicates that traffic 1, traffic 2, and traffic 7 are mapped to the links corresponding to the link profile fields.

[0234] When selectively needing to carry only one link profile, a specific link ID may be carried from another link profile to indicate that the information in the current link profile is invalid.

[0235] Example 2: Figure 10C is a schematic diagram of another possible MAC header according to one embodiment of this application. Each control ID corresponds to a control information field which includes a link profile field. Each link profile includes one link identifier (link ID) and identifier information for the traffic mapped to that link. A second multilink device may include link profiles for one or more links in the MAC header based on the actual traffic-to-link mapping requirements.

[0236] Similarly, the traffic identifier information in the link profile in Example 2 may be a traffic identifier bitmap, a start traffic identifier and an end traffic identifier, or in other forms. This is not limited to this embodiment of the application. For the case where the traffic identifier information is a traffic identifier bitmap, refer to Figure 10B. Details are not repeated herein.

[0237] Example 3: Figure 10D is a schematic diagram of another possible MAC header according to one embodiment of this application. The MAC header carries a Traffic Identifier (TID) ID and control information corresponding to that TID ID. The control information field includes two Traffic Profile (TID profile) fields. Each TID profile contains one Traffic Identifier (TID ID) identifier for the link to which the traffic is mapped.

[0238] Link identifier information may be a link ID bitmap, or it may be a starting link ID and an ending link ID. Traffic is mapped to the link corresponding to the link ID between the starting link ID and the ending link ID. Alternatively, link identifier information may take other forms; this is not limited to this embodiment of the application.

[0239] Each bit in the link identifier bitmap corresponds to one link identifier, and multiple different bits correspond to multiple different link identifiers. For example, bit i corresponds to link identifier i, and the value of i starts from 0, with a maximum value of the number of bits in the link identifier bitmap minus 1. The number of bits in the link identifier bitmap may be 4, 8, 12, or 16, etc. A specific number of bits may be determined based on the number of bits configured in the control information. This is not limited to this application.

[0240] Figure 10E is a schematic diagram of one possible link identifier bitmap according to one embodiment of this application. The link identifier bitmap contains 8 bits. The first bit (bit 0) corresponds to a link with link ID 0, the second bit (bit 1) corresponds to a link with link ID 1, the third bit (bit 2) corresponds to a link with link ID 3, the fourth bit (bit 3) corresponds to a link with link ID 4, the fifth bit (bit 4) corresponds to a link with link ID 4, the sixth bit (bit 5) corresponds to a link with link ID 5, the seventh bit (bit 6) corresponds to a link with link ID 6, and the eighth bit (bit 7) corresponds to a link with link ID 7. Traffic is mapped to a link with a corresponding field value of 1, or traffic is mapped to a link with a corresponding field value of 0. For example, traffic is mapped to a link with a corresponding field value of 1. In this case, the link identifier bitmap shown in Figure 10E indicates that the traffic is mapped to Link 1, Link 2, and Link 7.

[0241] When selectively needing to carry only one TID profile, it is possible to carry a specific TID within other TID profiles to indicate that the information in that TID profile is invalid.

[0242] Of course, Figure 10E is not an exhaustive representation, but rather merely an example. For example, in practice, the number of bits in the link identifier bitmap may alternatively be other values, such as 4, 12, or 16, and may be determined specifically based on the number of bits configured in the control information.

[0243] Example 4: Figure 10F is a schematic diagram of another possible MAC header according to one embodiment of this application. Each control ID corresponds to a control information field which includes a traffic profile (TID profile) field. Each TID profile includes one traffic identifier (TID) information relating to the link to which the traffic is mapped. A second multilink device may include one or more traffic TID profiles in the MAC header based on the actual traffic-to-link mapping requirements.

[0244] Similarly, the link identifier information in the TID profile in Example 4 may be a link identifier bitmap, a start link identifier and an end link identifier, or in other forms. This is not limited to this embodiment of the application. For the case where the link identifier information is a link identifier bitmap, see Figure 10E. Details are not repeated herein.

[0245] In other possible designs, the mapping information from traffic identifiers to links is carried within an information element that indicates the mapping relationship from traffic identifiers to links.

[0246] In this embodiment of the application, the name of the information element indicating the mapping relationship from a traffic identifier to a link is not limited. For example, its name may be a traffic identifier-to-link mapping element (or it may be referred to as a traffic identifier-to-link mapping element). For simplicity of explanation, the following description uses a traffic identifier-to-link mapping element as one example.

[0247] Figure 11A is a schematic diagram of a traffic identifier-to-link mapping information element according to one embodiment of this application. The traffic identifier-to-link mapping information element includes a Control field and a Traffic Identifier-to-Link Mapping info (TID-to-Link Mapping info) field. The TID-to-Link Mapping info field carries the traffic identifier-to-link mapping information. It should be understood that the Traffic Identifier-to-Link Mapping info (TID-to-Link Mapping info) field may have other names, and this is not limited to this embodiment of this application. Optionally, the traffic identifier-to-link mapping information element may further include fields such as an Element ID field, a Length field, or an Element ID Extension field, but these are not limited to the foregoing.

[0248] Numerous specific implementations may exist for the traffic identifier to link mapping information field. The following description uses some of the possible examples.

[0249] Example 1: As shown in Figure 11B, the traffic identifier to link mapping information field includes one or more link profile fields, each link profile field containing identifier information for one link and identifier information for one or more traffics mapped to that link. The traffic identifier information may be a traffic identifier bitmap (TID bitmap), or it may be a starting traffic identifier (starting TID) and a ending traffic identifier (starting TID). The TIDs between the starting TID and the ending TID are mapped to the link. Alternatively, the identifier information may take other forms; this is not limited to this embodiment of the application. In Figure 11B, as one example, an example is used in which the traffic identifier information is a traffic identifier bitmap. For a specific implementation of the traffic identifier bitmap, see Figure 10B. Details are not repeated herein.

[0250] Selectively, a link profile field may indicate that a link is disabled when all of its TID bitmap values ​​are 0.

[0251] Selectively, as shown in Figure 11C, the link profile field may further include a field indicating whether the corresponding link should be disabled, such as a Disable field (or, but not limited to, another name). Furthermore, if the Disable field indicates that the link is disabled, the link profile field does not have to carry the traffic identifier information mapped to the link (in Figure 11C, a traffic identifier bitmap is used as one example), or the link profile field carries only the link identifier and the Disable field, or all of the TID bitmap is 0.

[0252] Example 2: As shown in FIG. 11D, the mapping information field from the traffic identifier to the link includes one or more traffic profile fields, and each traffic profile field includes the identifier information of one traffic and the identifier information of one or more links to which the traffic is mapped. The link identifier information may be a link ID bitmap, or may be a starting link ID and an ending link ID. The traffic is mapped to the link corresponding to the link ID between the starting link ID and the ending link ID. Alternatively, the link identifier information may be in other forms. This is not limited in this embodiment of this application. In FIG. 11D, an example where the link identifier information is a link ID bitmap is used. For the specific implementation of the link ID bitmap, reference should be made to FIG. 10E. Details are not repeatedly described herein.

[0253] Optionally, the traffic profile field may alternatively exist in the form of information elements. In this case, the traffic profile field may further include fields such as an element ID field, a Length field, and an element ID Extension field, as shown in FIG. 11E.

[0254] The specific content of the control field may vary according to the method of delivering the second message (or the type of the second message). The following description explains the broadcast mode and the unicast mode.

[0255] 1. Unicast mode

[0256] Each of the request frame (third message) and the response frame (second message) may carry a mapping information element from the traffic identifier to the link.

[0257] Figure 12 is a schematic diagram of another possible traffic identifier-to-link mapping information element according to one embodiment of this application. As shown in Figure 12, the control field includes a mapping request (TID-to-Link Mapping request) field indicating the type of frame in which the traffic identifier-to-link mapping information element is located. The length of the field may be 1 bit, where 1 indicates a request and 0 indicates a response.

[0258] As shown in Figure 12, the control field may further include a third pre-configured field, such as a negotiation type field (or negotiation mode field, or other name, not limited herein), which indicates the mode used to negotiate the mapping from traffic identifiers to links. The negotiation type field in the traffic identifier-to-link mapping information element carried in the request frame indicates the mode used by the requester to negotiate the mapping from traffic identifiers to links (i.e., the first mode described above). The negotiation type field in the traffic identifier-to-link mapping information element carried in the response frame indicates the mode used by the responder to negotiate the mapping from traffic identifiers to links (i.e., the second mode described above).

[0259] In one possible design, when the traffic identifier-to-link mapping information element is located within the request and response frames, the value of the negotiation type field may have different meanings. In other words, the meaning of the negotiation type field's value must be determined based on the frame type in which the negotiation type field is located (including the request and response frames) and the value of the negotiation type field itself.

[0260] For example, Table 8 shows multiple possible values ​​for the negotiation type field in the traffic identifier to link mapping information element carried in the request frame, and examples of the meanings of those values. Table 9 shows multiple values ​​for the negotiation type field in the traffic identifier to link mapping information element carried in the response frame, and examples of the meanings of those values. [Table 8]

[0261] Table 8 lists three possible values ​​for the negotiation type field in the request frame, but it should be noted that this does not mean that the negotiation type field must contain all three values. In practice, the value of the negotiation type field may be only a subset of the values ​​in Table 8, or it may contain additional values ​​not listed in Table 8. [Table 9]

[0262] Table 9 lists four possible values ​​for the negotiation type field in the response frame, but it should be noted that this does not mean that the negotiation type field must contain all four of those values. In actual application, the value of the negotiation type field may be only a subset of the values ​​in Table 9, or it may contain additional values ​​not listed in Table 9.

[0263] In other possible designs, when the traffic identifier-to-link mapping information element is located within the request and response frames, the value of the negotiation type field may have the same meaning. In other words, the meaning indicated by the value of the negotiation type field may be directly determined based on the value of the negotiation type field.

[0264] For example, Table 10 shows several possible values ​​for the negotiation type field in the link mapping information element from a traffic identifier carried in a request frame or response frame, and examples of the meanings of those values. [Table 10]

[0265] Table 10 above lists seven possible values ​​for the negotiation type field in request and response frames, but it should be noted that this does not mean that the negotiation type field must contain all seven values. In practice, the value of the negotiation type field may be only a subset of the values ​​in Table 10, or it may contain additional values ​​not listed in Table 10.

[0266] Selectively, as shown in Figure 12, the control field may further include a ninth directive information, such as a Traffic Direction field (or, but not limited to, other names herein), which indicates the direction of traffic mapped to the link. The type of direction may include downlink and uplink, or further include both uplink and downlink (both UL and DL). The field length may be 1 bit or 2 bits. For example, a value of 0 in the field indicates an uplink, a value of 1 indicates a downlink, and a value of 3 indicates both uplink and downlink.

[0267] Optionally, as shown in FIG. 12, the control field may further include a second pre-set field such as, for example, a default mode field (or, although not limited herein, other names), and the length may be 1 bit. When the default mode field is set to a pre-set value (e.g., 1), the default mode field indicates that the default mapping method is used. Specifically, all TIDs (or each TID) may be mapped to each link for which multi-link communication is established. In this case, the mapping information element from the traffic identifier to the link may not carry the mapping information from the traffic identifier to the link, or the mapping information element from the traffic identifier to the link may carry only other fields such as the control field, element identifier, length, or element ID extension.

[0268] It should be understood that any mapping information field from a traffic identifier to a link in the embodiments shown in FIGS. 11A to 11D may be combined with any control field in the embodiment shown in FIG. 12. For example, FIG. 13 is a schematic diagram of a mapping information element from a traffic identifier to a link obtained by one of a plurality of combination methods.

[0269] The following description explains a method for using any one of the mapping information elements from a traffic identifier to a link shown in FIGS. 11A to 13.

[0270] One method is that in the multi-link establishment process, the association request frame (the third message) and the association response frame (the second message) carry the mapping information element from the traffic identifier to the link, thereby completing the negotiation of the mapping from the traffic identifier to the link during multi-link establishment.

[0271] Another approach is to define an Extremely High Throughput (EHT) Action Frame if the multilink device wishes to update the traffic-to-link mapping relationship after completing multilink establishment, in which case the EHT Action Frame carries the traffic identifier-to-link mapping information element to update the mapping relationship.

[0272] Figure 14 is a flowchart of a method for updating a traffic identifier-to-link mapping relationship according to one embodiment of this application. The method may be applied to the communication system shown in Figure 1.

[0273] S1401: The first multilink device sends a request frame (third message) to the second multilink device, which carries the mapping information elements from the first traffic identifier to the link and is used to request that the mapping relationship from the traffic identifier to the link be updated.

[0274] S1402: The second multilink device sends a response frame (second message) to the first multilink device, which carries a second traffic identifier-to-link mapping information element and is used to respond to an update of the traffic identifier-to-link mapping relationship.

[0275] Both the request frame and the response frame are EHT operation frames. Figure 15 is a schematic diagram of one possible frame configuration of an EHT operation frame according to one embodiment of this application. The value of the Category field may be "EHT" and indicates an operation frame in 802.11be.

[0276] To distinguish the request frame from the response frame, the value of the TID to link mapping request field in the traffic identifier to link mapping information element in the request frame may be set to 1, or the value of the TID to link mapping request field in the traffic identifier to link mapping information element in the response frame may be set to 0.

[0277] In one implementation, the value of the EHT Action field in the EHT Action frame may be "TID-to-Link mapping update information," which indicates that the EHT Action frame is used to update the mapping relationship from traffic identifiers to links.

[0278] In other implementations, the value of the EHT operation field in the request frame may be "TID-to-Link mapping update request", and the value of the EHT operation field in the response frame may be "TID-to-Link mapping update response". See Table 10 for one example. The negotiation of the traffic identifier-to-link mapping relationship is completed when the value of the negotiation type field in the traffic identifier-to-link mapping information element in the response frame is the fourth value (acceptance). Otherwise, the first multilink device may continue sending request frames until the value of the negotiation type field in the received response frame is the fourth value (acceptance).

[0279] 2. Broadcast Mode

[0280] In this mode, the second multilink device may be an AP MLD, and the first multilink device may be a non-AP MLD.

[0281] The second multilink device may include a traffic identifier-to-link mapping information element in the beacon frame, which is used to broadcast the traffic identifier-to-link mapping information to the station.

[0282] Figure 16 is a schematic diagram of another traffic identifier-to-link mapping information element according to one embodiment of this application. The traffic identifier-to-link mapping information element may be carried within a beacon frame. The control field of the traffic identifier-to-link mapping information element includes a broadcast field (sixth instruction information), which indicates that the current traffic identifier-to-link mapping information element is carrying broadcast traffic-to-link mapping information. In other words, the traffic-to-link mapping information may be transmitted to multiple stations, which are used to perform traffic-to-link mapping.

[0283] Selectively, as shown in Figure 16, the control field may further include a Traffic Direction field, which indicates the direction of traffic mapped to the link. The direction type may include downlink and uplink, or further include both uplink and downlink (both UL and DL). The field length may be 1 bit or 2 bits. A value of 0 indicates an uplink, a value of 1 indicates a downlink, and a value of 3 indicates both uplink and downlink.

[0284] Selectively, as shown in Figure 16, the control field may further include a default mode field, which may have a length of 1 bit. When the default mode field is set to a preset value (e.g., 1), that default mode field indicates that the default mapping scheme will be used. Specifically, all TIDs (or each TID) may be mapped to each link on which multilink communication is established. In this case, the traffic identifier-to-link mapping information element may not carry the traffic identifier-to-link mapping information, or it may carry only the control field, element identifier, length, or other fields such as element ID extensions.

[0285] Before the second multilink device broadcasts the beacon frame (second message), a station multilink device such as the first multilink device may transmit seventh instruction information to the second multilink device to indicate that the device type of the first multilink device is a device that supports the mapping of broadcasted traffic identifiers to links (an MLD that supports the mapping of broadcasted TIDs to links). Furthermore, when the second multilink device broadcasts the beacon frame, the first multilink device receives the traffic identifier-to-link mapping information element in the beacon frame and updates the traffic identifier-to-link mapping relationship based on the traffic identifier-to-link mapping information element.

[0286] In the case of a non-AP MLD, if the non-AP MLD supports mapping from broadcasted TIDs to links, it is not possible for the non-AP MLD to change the traffic identifier-to-link mapping relationship of that AP MLD by sending the traffic identifier-to-link mapping information element to the AP MLD.

[0287] In one particular implementation, in a multilink establishment request, the non-AP MLD asserts that it supports the broadcasted TID-to-link mapping. Specifically, the seventh directive information may be carried in the association request frame, which indicates that the non-AP MLD supports the broadcasted TID-to-link mapping. Specifically, the seventh directive information is carried in the EHT capabilities element. The AP MLD may respond with an association response frame, which carries a traffic identifier-to-link mapping information element, which is used to assign initial values ​​to the traffic identifier-to-link mapping relationship. If the AP MLD wishes to update the traffic identifier-to-link mapping relationship after completing multilink establishment, it may include the traffic identifier-to-link mapping information element in the beacon frame, which is used to broadcast the current traffic identifier-to-link mapping information to the station. After receiving data via non-AP MLD, the non-AP needs to update the mapping relationship.

[0288] Selectively, when the content of the traffic identifier to link mapping information element carried in the beacon frame changes so that a dormant non-AP MLD receives a new mapping relationship after waking up, the AP MLD uses this event as a critical update and must add 1 to the value of the check Beacon field (i.e., the eighth instruction information) in the next Traffic Indication Map (TIM) frame to be transmitted. After a non-AP MLD wakes up from dormancy, the non-AP MLD may know whether the AP MLD should update the mapping relationship by comparing the value of the check beacon frame field before dormancy with the value of the received check beacon frame field, and if the AP MLD decides to update the mapping relationship, it may update the mapping relationship based on the content of the latest traffic identifier to link mapping information element.

[0289] Alternatively, the AP MLD may carry a counter field (i.e., the eighth instruction information) within the beacon frame, for example, called the traffic identifier-to-link mapping update counter. The counter value is initialized to 0. When the content of the traffic identifier-to-link mapping information element changes, the counter value is incremented by 1.

[0290] The number of bits in the counter may be set and broadcast by the AP, or it may be specified in the standard. This is not limited to this embodiment of the application. For example, suppose the counter is represented by 8 bits and the maximum value of the counter is 255. When the count of the counter is greater than 255, a modulo operation (mod) is performed on 256, so that 255 plus 1 becomes 0.

[0291] After a non-AP MLD wakes up from a dormant state, it may compare the value of the counter frame field before the dormant state with the value of the received counter frame field to determine whether the AP MLD should update the mapping relationship, and when the AP MLD decides to update the mapping relationship, it may update the mapping relationship based on the content of the latest traffic identifier to link mapping information element.

[0292] Selectively, as shown in Figure 17, the counter may be carried within the traffic identifier-to-link mapping information element in the beacon frame.

[0293] S902: The first multilink device establishes or updates the traffic-to-link mapping relationship based on the mapping information.

[0294] For example, if the second message is an association response frame that the second multilink device sends to the first multilink device during the multilink establishment phase (i.e., the second message is a message used to establish a mapping relationship), the first multilink device establishes an identifier-to-link mapping relationship based on the identifier-to-link mapping information carried in the association response frame.

[0295] Alternatively, for example, if the second message is an EHT operation frame that the second multilink device sends to the first multilink device after the completion of the multilink establishment phase (in other words, if the second message is a message used to update the mapping relationship), the first multilink device updates the identifier-to-link mapping relationship based on the identifier-to-link mapping information carried in the EHT operation frame.

[0296] Alternatively, for example, if the second message is a beacon frame broadcast by the second multilink device after the completion of the multilink establishment phase (in other words, if the second message is a message used to update the mapping relationship), the first multilink device updates the identifier-to-link mapping relationship based on the identifier-to-link mapping information carried in the beacon frame.

[0297] As described above, in this embodiment of the application, the second multilink device adds traffic-to-link mapping information to the second message, thereby enabling the multilink device to further establish a traffic-to-link mapping relationship when establishing a multilink, or to update the traffic-to-link mapping relationship after the multilink establishment is complete, resulting in more flexible traffic management and improved service quality.

[0298] It should be understood that the multiple embodiments provided by the multiple embodiments of this application can be combined with each other to implement multiple different technical effects.

[0299] In several embodiments of this application, the terms “system” and “network” may be used interchangeably. “At least one” means one or more, and “multiple” means two or more. The terms “and / or” describe a relationship of relevance to describe multiple related subjects, indicating that there may be three such relationships. For example, A and / or B may refer to three cases: when only A exists, when both A and B exist, and when only B exists. Each of A and B may be singular or plural. The symbol “ / ” generally indicates an “or” relationship between multiple related subjects. “At least one of the following items (parts)” or similar expressions refer to any combination of those items, the combination including either a single item (part) or a combination of multiple items (parts). For example, at least one of a, b, or c may refer to a, b, c, a and b, a and c, b and c, or a, b, and c.

[0300] In addition, unless otherwise specified, the sequential numbers such as "first" and "second" in the various embodiments of this application are used to distinguish between multiple subjects, but are not intended to limit the order, chronological order, priority, or importance of those multiple subjects. For example, the first priority criterion and the second priority criterion are used merely to distinguish between multiple different criteria, but do not indicate different content, priority, or importance of the two criteria.

[0301] In addition, the words “includes” and “have” in the various embodiments, claims, and accompanying drawings of this application are not exclusive. For example, a process, method, system, product, or device comprising a series of steps or modules is not limited to the steps or modules described and may further include steps or modules not described.

[0302] Multiple embodiments of this application are described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to multiple embodiments of this application. It should be understood that computer program instructions may be used to implement each process and / or each block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams. These computer program instructions are provided to the processor of a general-purpose computer, a dedicated computer, an embedded processor, or any other programmable data processing device to generate a machine, thereby generating a device for implementing one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

[0303] All or part of the above embodiments may be implemented by using software, hardware, firmware, or a combination thereof. When using software to implement the above embodiments, all or part of those embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When those computer program instructions are loaded into a computer and executed by the computer, all or part of the procedures or functions according to the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, those computer instructions may be transmitted by a wired method (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or by a wireless method (e.g., infrared, radio, or microwave) from one website, computer, server, or data center to another website, computer, server, or data center. Computer-readable storage media may be any available media accessible by a computer, or a data storage device such as a server or data center that integrates one or more available media. Available media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., digital versatile discs, DVDs), or semiconductor media (e.g., solid state disks, SSDs).

[0304] Clearly, a person skilled in the art can make various modifications and variations to the various embodiments of this application without departing from the spirit and scope of this application. This application is intended to extend to such modifications and variations, insofar as they fall within the scope of protection provided for by the following claims of this application and their equivalent art.

Claims

1. A multilink communication method, The steps include: sending a first request message to a first multilink device via a second multilink device, wherein the first request message carries identifiers for one or more links and first instruction information for each of the one or more links, the first instruction information indicating the operation type of the link, the operation type including one or more of adding a link to a multilink communication link and removing a link from a multilink communication link; The steps include: receiving a first response message from the first multilink device via the second multilink device, wherein the first response message carries the identifier of one or more links and second instruction information for each of the one or more links, and the second instruction information indicates the status of the link; A method that includes this.

2. The aforementioned operation type is, Establishment of multilink communication, and / or Providing only link information or not establishing multilink communication, The method according to claim 1, further comprising:

3. The aforementioned state is one or more of the following, namely: They have successfully established multilink communication. The establishment of multilink communication has failed. Only link information is provided or multilink communication has not been established. The aforementioned link has been successfully added. The above link failed to be added. The aforementioned link has been successfully removed, or The above link has failed to be removed. The method according to claim 1 or 2, comprising one or more of the following.

4. The method according to claim 1 or 2, wherein the first instruction information and the second instruction information are transported within a first pre-set field in a multilink information element.

5. In the multilink information element carried in the first request message, the value of the first pre-set field is one or more of the following: A first value indicating that the operation type is the addition of a link to a multilink communication link, or A second value indicating that the operation type is the deletion of a link from a multilink communication link, Includes one or more of the following: In the multilink information element carried in the first response message, the value of the first pre-set field is one or more of the following: A third value indicating that the aforementioned state is one in which the link has been successfully added, A fourth value indicating that the aforementioned state is one in which the addition of the link has failed, A fifth value indicating that the aforementioned state is one in which the deletion of the link has been successful, or A sixth value indicating that the aforementioned state is one in which the deletion of the link has failed, The method according to claim 4, comprising one or more of the following.

6. If the operation type is establishing multilink communication, not establishing multilink communication, providing only link information, or adding a link to a multilink communication link, the first request message further carries station capability information, or If the operation type is the removal of a link from a multilink communication link, the first request message does not carry station capability information. The method according to any one of claims 2 to 5.

7. The aforementioned multilink information element further carries information about new links of the access point device, The multilink device MLD common information field of the multilink information element carries a third instruction information indicating that the multilink information element carries information about the new link. The method according to claim 4.

8. The method according to claim 7, wherein the information relating to the new link is carried within each of N consecutive beacon frames, where N is a positive integer.

9. A multilink communication method, The steps include: receiving a first request message transmitted by a second multilink device using a first multilink device, wherein the first request message carries identifiers for one or more links and first instruction information for each of the one or more links, the first instruction information indicating the operation type of the link, the operation type including one or more of adding a link to a multilink communication link and removing a link from a multilink communication link; The first multilink device transmits a first response message to the second multilink device, wherein the first response message carries the identifier of one or more links and second instruction information for each of the one or more links, and the second instruction information indicates the status of the link. A method that includes this.

10. The aforementioned operation type is, Establishment of multilink communication, and / or Providing only link information or not establishing multilink communication, The method according to claim 9, further comprising:

11. The aforementioned state is one or more of the following, namely: They have successfully established multilink communication. The establishment of multilink communication has failed. Only link information is provided or multilink communication has not been established. The aforementioned link has been successfully added. The above link failed to be added. The aforementioned link has been successfully removed, or The above link has failed to be removed. The method according to claim 9 or 10, comprising one or more of the following.

12. The method according to claim 9 or 10, wherein the first instruction information and the second instruction information are transported within a first pre-set field in a multilink information element.

13. In the multilink information element carried in the first request message, the value of the first pre-set field is one or more of the following: A first value indicating that the operation type is the addition of a link to a multilink communication link, or A second value indicating that the operation type is the deletion of a link from a multilink communication link, Includes one or more of the following: In the multilink information element carried in the first response message, the value of the first pre-set field is one or more of the following: A third value indicating that the aforementioned state is one in which the link has been successfully added, A fourth value indicating that the aforementioned state is one in which the addition of the link has failed, A fifth value indicating that the aforementioned state is one in which the deletion of the link has been successful, or A sixth value indicating that the aforementioned state is one in which the deletion of the link has failed, The method according to claim 12, comprising one or more of the following.

14. If the operation type is establishing multilink communication, not establishing multilink communication, providing only link information, or adding a link to a multilink communication link, the first request message further carries station capability information, or If the operation type is the removal of a link from a multilink communication link, the first request message does not carry station capability information. The method according to any one of claims 10 to 13.

15. The aforementioned multilink information element further carries information about new links of the access point device, The multilink device MLD common information field of the multilink information element carries a third instruction information indicating that the multilink information element carries information about the new link. The method according to claim 12.

16. The method according to claim 15, wherein the information relating to the new link is carried within each beacon frame of N consecutive beacon frames, where N is a positive integer.

17. A chip, which is coupled to a memory and configured to read and execute program instructions stored in the memory, thereby enabling the method according to any one of claims 1 to 8 to be performed.

18. A chip, which is coupled to a memory and configured to read and execute program instructions stored in the memory, thereby performing the method according to any one of claims 9 to 16.

19. A communication device, A transceiver module configured to communicate with other communication devices besides the said communication device, A processing module configured to perform the method described in any one of claims 1 to 8 by using the transceiver module, A communication device that includes [this].

20. A communication device, A transceiver module configured to communicate with other communication devices besides the said communication device, A processing module configured to perform the method described in any one of claims 9 to 16 by using the transceiver module, A communication device that includes [this].

21. A computer-readable storage medium having a program or instructions, wherein when the program or instructions are started or executed on a computer, the method according to any one of claims 1 to 8 is executed.

22. A computer-readable storage medium having a program or instructions, wherein when the program or instructions are started or executed on a computer, the method according to any one of claims 9 to 16 is performed.

23. A computer program wherein, when the computer program is executed on a computer, the method described in any one of claims 1 to 8 is executed.

24. A computer program wherein, when the computer program is executed on a computer, the method described in any one of claims 9 to 16 is executed.

Images