Methods for mapping traffic to links, and multi-link devices.

Abstract

The invention relates to a method for mapping traffic to links, multilink devices, chips, communication devices, and computer-readable storage media. When a multilink device performs multilink establishment, it can establish, on demand, multilink communication on some or all of the links supported by that multilink device. During subsequent communication, links can be added to or removed from the established multilink communication link on demand. In this way, the flexibility of multilink communication can be improved, and the multilink device's requirement for dynamic updating of the communication link can be satisfied.Furthermore, the multi-link device can establish traffic-to-link mapping relationships during the multi-link setup process, or update traffic-to-link mapping relationships after the multi-link setup is complete, to manage traffic transmission more flexibly and improve the quality of service for that traffic.

Description

A multi-link communication method, service and link mapping method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on August 21, 2020, with application number 202010852529.1 and application name “A multi-link communication method, service and link mapping method and device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a multi-link communication method, a service and link mapping method, and a device. Background Art

[0004] With the advancement of wireless technology, more and more wireless devices support multi-link communication. For example, they can communicate simultaneously on the 2.4 GHz, 5 GHz, and 6 GHz bands, or on different channels within the same band. This improves the communication rate between wireless devices. Devices that support multi-link communication are commonly referred to as multi-link devices (MLDs).

[0005] Before MLD and MLD can establish multilink communication, they must first establish multiple links. For example, a first multilink device sends an association request frame to a second multilink device to establish multiple links. The association request frame carries information about the links supported by the first multilink device and with which it wishes to establish multilink communication.

[0006] However, in actual applications, MLD may not initially require communication on every link it supports. If MLD establishes multi-link communication on all supported links from the outset, link resource utilization will be low. In subsequent communications, MLD may need to update communication links. However, the multi-link device initially only provides information about the links on which it wishes to establish multi-link communication, failing to meet this need. Therefore, existing multi-link communication technologies suffer from a lack of flexibility and a technical inability to meet the needs of practical applications.

[0007] Summary of the Invention

[0008] The embodiments of the present application provide a multi-link communication method, a method and a device for mapping services to links, which can improve the flexibility of multi-link devices in performing multi-link communication, meet the requirements of multi-link devices for dynamically updating communication links, and more flexibly manage service transmission, thereby improving the service quality of services.

[0009] In a first aspect, a multi-link communication method is provided, comprising: a first multi-link device receiving a first request message sent from a second multi-link device, the first request message carrying identifiers of at least two links and first indication information of each of the at least two links, the first indication information being used to indicate an operation type of the link, the operation type including establishing multi-link communication, providing only link information, or not establishing multi-link communication; and the first multi-link device sending a first response message to the second multi-link device, the first response message carrying identifiers of the at least two links and second indication information of each of the at least two links, the second indication information being used to indicate a link status.

[0010] In the embodiment of the present application, by carrying the first indication information in the first request message and the second indication information in the first response message, the multi-link device can select, when establishing multi-links, to establish multi-link communication on some of the links it supports, as needed. This can improve the flexibility of the multi-link device in performing multi-link communication.

[0011] In a possible implementation manner, the operation type further includes: adding a link in a multi-link communication link; and / or deleting a link in a multi-link communication link.

[0012] In this embodiment, by carrying the first indication information in the first request message and the second indication information in the first response message, the multi-link device can add or delete links in the established multi-link communication links according to communication needs after the multi-link is established. This can further improve the flexibility of the multi-link device in performing multi-link communication and better meet the needs of the multi-link device for dynamically updating communication links.

[0013] In one possible implementation, the status includes any one or more of the following: successful establishment of multi-link communication; failure to establish multi-link communication; only providing link information or not establishing multi-link communication; successful addition of link; failure to add link; successful deletion of link; failure to delete link.

[0014] In this embodiment, there are multiple link states, which further improves the flexibility of multi-link communication.

[0015] In a possible implementation manner, the first indication information and / or the second indication information is carried in a first preset field of a multi-link information unit.

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

[0017] In one possible embodiment, in the multi-link information unit carried by the first request message, the first value of the first preset field is used to indicate that the operation type is to establish multi-link communication, and the second value of the first preset field is used to indicate that the operation type is to only provide link information or not establish multi-link communication; or, in the multi-link information unit carried by the first response message, the first value of the first preset field is used to indicate that the status is that the multi-link communication is successfully established, the second value of the first preset field is used to indicate that the status is that the multi-link communication fails to be established, and the third value of the first preset field is used to indicate that the status is to only provide link information or not establish multi-link communication.

[0018] In this embodiment, when the multi-link information unit is located in an association request frame and an association response frame, the value of the first preset field can refer to different meanings respectively. The meaning referred to by the value of the first preset field can be determined based on the frame type (i.e., association request frame, association response frame) in which the first preset field is located, and the value of the first preset field, which can save the bits occupied by the first preset field.

[0019] In a possible implementation manner, in the multilink information unit carried by the first request message or the first response message, the value of the first preset field includes any one or more of the following:

[0020] A first value is used to indicate that the operation type is to establish multi-link communication;

[0021] The second value is used to indicate that the state is that the multi-link communication is successfully established;

[0022] A third value is used to indicate that the state is a multi-link communication establishment failure;

[0023] The fourth value is used to indicate that the operation type or the state is to only provide link information or not establish multi-link communication.

[0024] In this implementation, when the multi-link information unit is located in the association request frame and the association response frame, the value of the first preset field can refer to the same meaning, and the meaning referred to by the value of the first preset field can be directly determined based on the value of the first preset field, which can reduce the complexity of the multi-link device in identifying the first preset field.

[0025] In one possible embodiment, in the multi-link information unit carried by the first request message, the first value of the first preset field is used to indicate that the operation type is to add a link in a multi-link communication link, and the second value of the first preset field is used to indicate that the operation type is to delete a link in a multi-link communication link; or, in the multi-link information unit carried by the first response message, the first value of the first preset field is used to indicate that the status is successful addition of the link, the second value of the first preset field is used to indicate that the status is failure to add the link, the third value of the first preset field is used to indicate that the status is successful deletion of the link, and the fourth value of the first preset field is used to indicate that the status is failure to delete the link.

[0026] In this embodiment, when the multi-link information unit is located in the reassociation request frame and the reassociation response frame, the value of the first preset field can refer to different meanings respectively. The meaning referred to by the value of the first preset field can be determined according to the frame type (i.e., reassociation request frame, reassociation response frame) in which the first preset field is located, and the value of the first preset field, which can save the bits occupied by the first preset field.

[0027] In a possible implementation manner, in the multilink information unit carried by the first request message or the first response message, the value of the first preset field includes any one or more of the following:

[0028] A first value is used to indicate that the operation type is adding a link in a multi-link communication link;

[0029] The second value is used to indicate that the operation type is to delete a link in the multi-link communication link;

[0030] The third value is used to indicate that the state is that the link is added successfully;

[0031] A fourth value is used to indicate that the state is failure to add a link;

[0032] A fifth value is used to indicate that the status is that the link is deleted successfully;

[0033] The sixth value is used to indicate that the status is failure to delete the link.

[0034] In this embodiment, when the multi-link information unit is located in the reassociation request frame and the reassociation response frame, the value of the first preset field can refer to the same meaning, and the meaning referred to by the value of the first preset field can be directly determined based on the value of the first preset field, which can reduce the complexity of the multi-link device in identifying the first preset field.

[0035] In a possible implementation manner, in the multilink information unit carried by the first request message or the first response message, the value of the first preset field includes any one or more of the following:

[0036] A first value is used to indicate that the operation type is to establish multi-link communication;

[0037] The second value is used to indicate that the state is that the multi-link communication is successfully established;

[0038] A third value is used to indicate that the state is a multi-link communication establishment failure;

[0039] A fourth value is used to indicate that the operation type or the state is to only provide link information or not establish multi-link communication;

[0040] a fifth value, used to indicate that the operation type is adding a link in a multi-link communication link;

[0041] A sixth value is used to indicate that the operation type is deleting a link in a multi-link communication link;

[0042] A seventh value is used to indicate that the state is that the link is added successfully;

[0043] An eighth value is used to indicate that the state is failure to add a link;

[0044] A ninth value is used to indicate that the status is that the link is deleted successfully;

[0045] The tenth value is used to indicate that the status is failure to delete the link.

[0046] In this embodiment, when the multi-link information unit is located in the association request frame, the association response frame, the reassociation request frame, and the reassociation response frame, the value of the first preset field can refer to the same meaning, and the meaning referred to by the value of the first preset field can be directly determined based on the value of the first preset field, which can further reduce the complexity of the multi-link device in identifying the first preset field.

[0047] In one possible implementation, the operation type is to establish multi-link communication or not to establish multi-link communication or to only provide link information or to add a link in a multi-link communication link, then the first request message also carries the capability information of the site; or, the operation type is to delete a link in a multi-link communication link, then the first request message does not carry the capability information of the site.

[0048] In this implementation, the operation type is deleting a link in a multi-link communication link, and the first request message does not carry the capability information of the site, which can save resource overhead while ensuring the reliability of the solution.

[0049] In a possible implementation, the multi-link information unit also carries information about a newly opened link of an access point device; and the multi-link device MLD common information field of the multi-link information unit carries third indication information for indicating that the multi-link information unit carries information about a newly opened link.

[0050] In this implementation, a multi-link device opens a new link according to communication requirements and promptly informs other multi-link devices, further improving the flexibility of multi-link communication and better meeting the requirements of multi-link devices for dynamically updating communication links.

[0051] In a possible implementation, the information of the newly opened link is carried in each beacon frame of N consecutive beacon frames, where N is a positive integer.

[0052] In this way, it can be ensured that the information of the newly opened link can be effectively received by other multi-link devices, which can further improve the reliability of the solution.

[0053] According to a second aspect, a multi-link communication method is provided, comprising: a first multi-link device receiving a first request message sent from a second multi-link device, the first request message carrying identifiers of at least two links and first indication information of each of the at least two links, the first indication information being used to indicate an operation type of the link, the operation type including adding a link to a multi-link communication link, providing only link information, or not establishing multi-link communication; and the first multi-link device sending a first response message to the second multi-link device, the first response message carrying identifiers of the at least two links and second indication information of each of the at least two links, the second indication information being used to indicate a link status.

[0054] In the embodiment of the present application, by carrying the first indication information in the first request message and the second indication information in the first response message, the multi-link device can add a link to an established multi-link communication link as needed. In addition, information about other links that do not require multi-link communication establishment is also provided to facilitate the multi-link device to subsequently add links as needed. This can improve the flexibility of the multi-link device in performing multi-link communication.

[0055] In a possible implementation manner, the operation type further includes: establishing multi-link communication; and / or deleting a link in the multi-link communication link.

[0056] In one possible implementation, the status includes any one or more of the following: successful establishment of multi-link communication; failure to establish multi-link communication; only providing link information or not establishing multi-link communication; successful addition of link; failure to add link; successful deletion of link; failure to delete link.

[0057] According to a third aspect, a multi-link communication method is provided, comprising: a first multi-link device receiving a first request message sent from a second multi-link device, the first request message carrying identifiers of at least two links and first indication information of each of the at least two links, the first indication information being used to indicate an operation type of the link, the operation type including deleting a link in a multi-link communication link, providing only link information, or not establishing multi-link communication; and the first multi-link device sending a first response message to the second multi-link device, the first response message carrying identifiers of the at least two links and second indication information of each of the at least two links, the second indication information being used to indicate a link status.

[0058] In the embodiment of the present application, by carrying the first indication information in the first request message and the second indication information in the first response message, the multi-link device can delete a link from an established multi-link communication link as needed. At the same time, information about other links that do not need to establish multi-link communication is also provided to facilitate the multi-link device to subsequently add new links as needed. This can improve the flexibility of the multi-link device in performing multi-link communication.

[0059] In a possible implementation, the operation type further includes: establishing multi-link communication; and / or adding a link in the multi-link communication link.

[0060] In one possible implementation, the status includes any one or more of the following: successful establishment of multi-link communication; failure to establish multi-link communication; only providing link information or not establishing multi-link communication; successful addition of link; failure to add link; successful deletion of link; failure to delete link.

[0061] In a fourth aspect, a multi-link communication method is provided, comprising: a second multi-link device sending a first request message to a first multi-link device, the first request message carrying identifiers of at least two links and first indication information for each of the at least two links, the first indication information being used to indicate an operation type of the link, the operation type including establishing multi-link communication, providing only link information, or not establishing multi-link communication; and the second multi-link device receiving a first response message from the first multi-link device, the first response message carrying identifiers of the at least two links and second indication information for each of the at least two links, the second indication information being used to indicate a link status.

[0062] In a possible implementation manner, the operation type further includes: adding a link in a multi-link communication link; and / or deleting a link in a multi-link communication link.

[0063] In one possible implementation, the status includes any one or more of the following: successful establishment of multi-link communication; failure to establish multi-link communication; only providing link information or not establishing multi-link communication; successful addition of link; failure to add link; successful deletion of link; failure to delete link.

[0064] In a possible implementation manner, the first indication information and / or the second indication information is carried in a first preset field of a multi-link information unit.

[0065] In one possible embodiment, in the multi-link information unit carried by the first request message, the first value of the first preset field is used to indicate that the operation type is to establish multi-link communication, and the second value of the first preset field is used to indicate that the operation type is to only provide link information or not establish multi-link communication; or, in the multi-link information unit carried by the first response message, the first value of the first preset field is used to indicate that the status is that the multi-link communication is successfully established, the second value of the first preset field is used to indicate that the status is that the multi-link communication fails to be established, and the third value of the first preset field is used to indicate that the status is to only provide link information or not establish multi-link communication.

[0066] In a possible implementation manner, in the multilink information unit carried by the first request message or the first response message, the value of the first preset field includes any one or more of the following:

[0067] A first value is used to indicate that the operation type is to establish multi-link communication;

[0068] The second value is used to indicate that the state is that the multi-link communication is successfully established;

[0069] A third value is used to indicate that the state is a multi-link communication establishment failure;

[0070] The fourth value is used to indicate that the operation type or the state is to only provide link information or not establish multi-link communication.

[0071] In one possible implementation, the operation type is to establish multi-link communication or not to establish multi-link communication or to only provide link information or to add a link in a multi-link communication link, then the first request message also carries the capability information of the site; or, the operation type is to delete a link in a multi-link communication link, then the first request message does not carry the capability information of the site.

[0072] In a possible implementation manner, the multi-link information unit further carries information about a newly opened link of the access point device;

[0073] The multi-link device MLD common information field of the multi-link information unit carries third indication information, which is used to indicate that the multi-link information unit carries information of a newly opened link.

[0074] In a possible implementation, the information of the newly opened link is carried in each beacon frame of N consecutive beacon frames, where N is a positive integer.

[0075] Regarding the technical effects brought about by the fourth aspect or various possible implementation methods of the fourth aspect, reference may be made to the introduction to the technical effects of the first aspect or various possible implementation methods of the first aspect.

[0076] In a fifth aspect, a multi-link communication method is provided, comprising: a second multi-link device sending a first request message to a first multi-link device, the first request message carrying identifiers of at least two links and first indication information for each of the at least two links, the first indication information being used to indicate an operation type of the link, the operation type including adding a link to a multi-link communication link, providing only link information, or not establishing multi-link communication; and the second multi-link device receiving a first response message from the first multi-link device, the first response message carrying identifiers of the at least two links and second indication information for each of the at least two links, the second indication information being used to indicate a link status.

[0077] In a possible implementation manner, the operation type further includes: establishing multi-link communication; and / or deleting a link in the multi-link communication link.

[0078] In one possible implementation, the status includes any one or more of the following: successful establishment of multi-link communication; failure to establish multi-link communication; only providing link information or not establishing multi-link communication; successful addition of link; failure to add link; successful deletion of link; failure to delete link.

[0079] Regarding the technical effects brought about by the fifth aspect or various possible implementation methods of the fifth aspect, reference may be made to the introduction to the technical effects of the second aspect or various possible implementation methods of the second aspect.

[0080] In a sixth aspect, a multi-link communication method is provided, comprising: a second multi-link device sending a first request message to a first multi-link device, the first request message carrying identifiers of at least two links and first indication information of each of the at least two links, the first indication information being used to indicate an operation type of the link, the operation type including deleting a link in a multi-link communication link, providing only link information, or not establishing multi-link communication; and the second multi-link device receiving a first response message from the first multi-link device, the first response message carrying identifiers of the at least two links and second indication information of each of the at least two links, the second indication information being used to indicate a link status.

[0081] In a possible implementation, the operation type further includes: establishing multi-link communication; and / or adding a link in the multi-link communication link.

[0082] In one possible implementation, the status includes any one or more of the following: successful establishment of multi-link communication; failure to establish multi-link communication; only providing link information or not establishing multi-link communication; successful addition of link; failure to add link; successful deletion of link; failure to delete link.

[0083] Regarding the technical effects brought about by the sixth aspect or various possible implementation methods of the sixth aspect, reference may be made to the introduction to the technical effects of the third aspect or various possible implementation methods of the third aspect.

[0084] In a seventh aspect, a method for mapping services to links is provided, comprising: a first multi-link device receiving a second message from a second multi-link device, wherein the second message carries mapping information between services and links; and the first multi-link device establishing or updating a mapping relationship between services and links based on the mapping information.

[0085] In the embodiment of the present application, the second multi-link device carries the mapping information between the service and the link in the second message, so that the first multi-link device can establish the mapping relationship between the service and the link when the multi-link is established, or update the mapping relationship between the service and the link after the multi-link is established, thereby achieving more flexible management of service transmission and improving service quality.

[0086] In one possible implementation, the second message further carries fourth indication information, where the fourth indication information is used to indicate a second mode for negotiating mapping of service identifiers and links. Before the first multi-link device receives the second message from the second multi-link device, the method further includes: the first multi-link device sending a third message to the second multi-link device, where the third message carries fifth indication information, where the fifth indication information is used to indicate the first mode for negotiating mapping of service identifiers and links.

[0087] In this implementation, the first multi-link device and the second multi-link device can negotiate with each other on the mapping between the service identifier and the link, which can further improve the flexibility of service transmission.

[0088] In one possible implementation, the first mode is: requesting to establish a mapping between a service and a link, but not carrying a specific mapping method between the service and the link; or, requesting to establish a mapping between a service and a link, and carrying a suggested mapping method, allowing the responder to modify the mapping relationship in the response frame; or, requesting to establish a mapping between a service and a link, and carrying a required mapping method, and not allowing the responder to modify the mapping relationship in the response frame.

[0089] It should be understood that the above examples are merely examples of the first mode and are not limiting.

[0090] In one possible implementation, the second mode is: the mapping between the service and the link is successfully established and carries the final mapping method; or, the mapping between the service and the link is not successfully established and carries the recommended mapping method; or, the mapping between the service and the link is not successfully established and carries the required mapping method. If the requesting party sends a request again, the mapping method must be used to successfully establish the mapping; or, the mapping between the service and the link fails to be established.

[0091] It should be understood that the above examples are merely examples of the second mode and are not limiting.

[0092] In a possible implementation manner, the second message is an association response frame or an EHT action frame.

[0093] In a possible implementation manner, the second message is a broadcast message.

[0094] In this implementation, the second multi-link device can directly broadcast the mapping information between the service identifier and the link, thereby further improving the flexibility of service transmission.

[0095] In one possible implementation, before the first multi-link device receives the second message from the second multi-link device, the process further includes: the first multi-link device sending a fourth message to the second multi-link device, where the fourth message carries seventh indication information, and the seventh indication information is used to indicate that the first multi-link device supports broadcast service-link mapping information.

[0096] In this implementation, the first multi-link device notifies the second multi-link device in advance of the mapping information between services and links that the first multi-link device supports broadcasting, so that the second multi-link device can notify the first multi-link device to establish or update the mapping relationship between services and links through broadcasting, thereby improving the reliability of the solution.

[0097] In a possible implementation manner, the second message further carries eighth indication information, which is used to indicate the cumulative number of updates of the mapping information between the service and the link.

[0098] In this way, after receiving the second message (broadcast message), the multi-link device that wakes up after dormancy can promptly learn the update status of the mapping information between services and links, and determine whether the mapping relationship between services and links itself needs to be updated.

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

[0100] In a possible implementation manner, the second message further includes ninth indication information for indicating a service direction of mapping the service to the link, where the service direction is uplink, downlink, or any one of uplink and downlink.

[0101] In this embodiment, the multi-link device can establish or update the mapping relationship between services and links only for uplink transmission, or establish or update the mapping relationship between services and links only for downlink transmission, or establish or update the mapping relationship between services and links only for uplink and downlink transmission at the same time, further improving the flexibility of service management.

[0102] In a possible implementation manner, the mapping information between the service and the link is carried in a media access control MAC header or in an information unit used to indicate the mapping relationship between the service and the link.

[0103] In one possible implementation, the information unit used to indicate the service-link mapping relationship carries a second preset field. When the second preset field is a preset value, the second preset field instructs the first multi-link device to map each service identifier to each link on which multi-link communication is established.

[0104] In a possible implementation, when the second preset field is a preset value, the information unit for indicating the mapping relationship between the service and the link does not carry the mapping information between the service and the link.

[0105] In this way, resource overhead can be saved.

[0106] In one possible implementation, the fourth indication information and / or the fifth indication information is carried in a third preset field of an information unit used to indicate a service-link mapping relationship; in the information unit used to indicate a service-link mapping relationship carried by the third message or the fourth message, the value of the third preset field includes any one or more of the following:

[0107] A first value is used to indicate that the second mode is a request to establish a mapping between a service and a link, but does not carry a specific mapping method between the service and the link;

[0108] The second value is used to indicate that the second mode is a request to establish a mapping between a service and a link, and carries a suggested mapping method, allowing the responder to modify the mapping relationship in the response frame;

[0109] The third value is used to indicate that the second mode is a request to establish a mapping between a service and a link, and carries the required mapping method, and the responder is not allowed to modify the mapping relationship in the response frame;

[0110] A fourth value is used to indicate that the first mode is a successful establishment of the mapping between the service and the link, and carries the final mapping method;

[0111] A fifth value is used to indicate that the first mode is that the mapping between the service and the link is not successfully established, and carries a recommended mapping method;

[0112] The sixth value is used to indicate that the mapping between the service and the link in the first mode has not been successfully established, and carries the required mapping method. If the requester sends a request again, the mapping method must be used to successfully establish the connection;

[0113] The seventh value is used to indicate that the first mode is a failure in establishing the mapping between the service and the link.

[0114] It should be understood that the above seven values ​​are only examples and not limitations. In specific implementations, the value of the third preset field may be only a part of the above seven values, or may also include other values ​​in addition to the above seven values.

[0115] In one possible implementation, the mapping information between the service and the link includes: one or more link configuration fields, each of which contains identification information of a link and identification information of one or more services mapped to the link; or, one or more service configuration fields, each of which contains identification information of a service and identification information of one or more links to which the service is mapped.

[0116] This implementation provides two different implementations of the mapping information between services and links, which can further improve the flexibility of the solution.

[0117] In an eighth aspect, a method for mapping services to links is provided, comprising: a second multi-link device generating a second message, the second message carrying mapping information between services and links; and the second multi-link device sending the second message to a first multi-link device.

[0118] In one possible implementation, the second message further carries fourth indication information, where the fourth indication information is used to indicate a second mode for negotiating mapping of service identifiers and links. Before the second multi-link device generates the second message, the method further includes: the second multi-link device receiving a third message from the first multi-link device, where the third message carries fifth indication information, where the fifth indication information is used to indicate the first mode for negotiating mapping of service identifiers and links.

[0119] In one possible implementation, the first mode is: requesting to establish a mapping between a service and a link, but not carrying a specific mapping method between the service and the link; or, requesting to establish a mapping between a service and a link, and carrying a suggested mapping method, allowing the responder to modify the mapping relationship in the response frame; or, requesting to establish a mapping between a service and a link, and carrying a required mapping method, and not allowing the responder to modify the mapping relationship in the response frame.

[0120] In one possible implementation, the second mode is: the mapping between the service and the link is successfully established and carries the final mapping method; or, the mapping between the service and the link is not successfully established and carries the recommended mapping method; or, the mapping between the service and the link is not successfully established and carries the required mapping method. If the requesting party sends a request again, the mapping method must be used to successfully establish the mapping; or, the mapping between the service and the link fails to be established.

[0121] In a possible implementation manner, the second message is an association response frame or an EHT action frame.

[0122] In a possible implementation manner, the second message is a broadcast message.

[0123] In one possible implementation, before the second multi-link device generates the second message, the process further includes: the second multi-link device receiving a fourth message from the first multi-link device, where the fourth message carries seventh indication information, and the seventh indication information is used to indicate that the first multi-link device supports broadcast service-link mapping information.

[0124] In a possible implementation manner, the second message further carries eighth indication information, which is used to indicate the cumulative number of updates of the mapping information between the service and the link.

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

[0126] In a possible implementation manner, the second message further includes ninth indication information for indicating a service direction of mapping the service to the link, where the service direction is uplink, downlink, or any one of uplink and downlink.

[0127] In a possible implementation manner, the mapping information between the service and the link is carried in a media access control MAC header or in an information unit used to indicate the mapping relationship between the service and the link.

[0128] In one possible implementation, the information unit used to indicate the service-link mapping relationship carries a second preset field. When the second preset field is a preset value, the second preset field instructs the first multi-link device to map each service identifier to each link on which multi-link communication is established.

[0129] In a possible implementation, when the second preset field is a preset value, the information unit for indicating the mapping relationship between the service and the link does not carry the mapping information between the service and the link.

[0130] In one possible implementation, the fourth indication information and / or the fifth indication information is carried in a third preset field of an information unit used to indicate a service-link mapping relationship; in the information unit used to indicate a service-link mapping relationship carried by the third message or the fourth message, the value of the third preset field includes any one or more of the following:

[0131] A first value is used to indicate that the second mode is a request to establish a mapping between a service and a link, but does not carry a specific mapping method between the service and the link;

[0132] The second value is used to indicate that the second mode is a request to establish a mapping between a service and a link, and carries a suggested mapping method, allowing the responder to modify the mapping relationship in the response frame;

[0133] The third value is used to indicate that the second mode is a request to establish a mapping between a service and a link, and carries the required mapping method, and the responder is not allowed to modify the mapping relationship in the response frame;

[0134] A fourth value is used to indicate that the first mode is a successful establishment of the mapping between the service and the link, and carries the final mapping method;

[0135] A fifth value is used to indicate that the first mode is that the mapping between the service and the link is not successfully established, and carries a recommended mapping method;

[0136] The sixth value is used to indicate that the mapping between the service and the link in the first mode has not been successfully established, and carries the required mapping method. If the requester sends a request again, the mapping method must be used to successfully establish the connection;

[0137] The seventh value is used to indicate that the first mode is a failure in establishing the mapping between the service and the link.

[0138] It should be understood that the above seven values ​​are only examples and not limitations. In specific implementations, the value of the third preset field may be only a part of the above seven values, or may also include other values ​​in addition to the above seven values.

[0139] In one possible implementation, the mapping information between the service and the link includes: one or more link configuration fields, each of which contains identification information of a link and identification information of one or more services mapped to the link; or, one or more service configuration fields, each of which contains identification information of a service and identification information of one or more links to which the service is mapped.

[0140] Regarding the technical effects brought about by the eighth aspect or various possible implementation methods of the eighth aspect, reference may be made to the introduction to the technical effects of the seventh aspect or various possible implementation methods of the seventh aspect.

[0141] In a ninth aspect, a multi-link device is provided, comprising a module for executing the method described in the first aspect or any possible implementation of the first aspect or the second aspect or any possible implementation of the second aspect or the third aspect or any possible implementation of the third aspect.

[0142] Exemplarily, the device includes a transceiver module;

[0143] The transceiver module is configured to: receive a first request message sent from a second multi-link device, where the first request message carries identifiers of at least two links and first indication information of each of the at least two links, where the first indication information is used to indicate an operation type of the link, where the operation type includes establishing multi-link communication, adding a link in a multi-link communication link, or deleting a link in a multi-link communication link, and the operation type also includes only providing link information or not establishing multi-link communication;

[0144] The transceiver module is further configured to send a first response message to the second multi-link device, wherein the first response message carries identifiers of the at least two links and second indication information of each of the at least two links, where the second indication information is used to indicate a link status.

[0145] In a tenth aspect, a multi-link device is provided, comprising a module for executing the method described in the fourth aspect or any possible implementation of the fourth aspect or the fifth aspect or any possible implementation of the fifth aspect or the sixth aspect or any possible implementation of the sixth aspect.

[0146] Exemplarily, the device includes a transceiver module;

[0147] The transceiver module is configured to: send a first request message to the first multi-link device, where the first request message carries identifiers of at least two links and first indication information of each of the at least two links, where the first indication information is used to indicate an operation type of the link, where the operation type includes establishing multi-link communication, adding a link to a multi-link communication link, or deleting a link from a multi-link communication link, and the operation type also includes only providing link information or not establishing multi-link communication;

[0148] The transceiver module is further configured to receive a first response message from the first multi-link device, the first response message carrying identifiers of the at least two links and second indication information of each of the at least two links, the second indication information being used to indicate a link status.

[0149] In an eleventh aspect, a multi-link device is provided, comprising a module for executing the method described in the seventh aspect or any possible implementation manner of the seventh aspect.

[0150] Exemplarily, the device includes:

[0151] a transceiver module, configured to receive a second message from a second multi-link device, wherein the second message carries mapping information between services and links;

[0152] The processing module is used to establish or update the mapping relationship between the service and the link according to the mapping information.

[0153] In a twelfth aspect, a multi-link device is provided, comprising a module for executing the method described in the eighth aspect or any possible implementation manner of the eighth aspect.

[0154] Exemplarily, the device includes:

[0155] A processing module, configured to generate a second message;

[0156] The transceiver module is configured to send the second message to the first multi-link device.

[0157] In a thirteenth aspect, a multi-link device is provided, comprising a processor coupled to a memory; the processor is configured to execute a computer program or instruction stored in the memory, so that the device performs the method described in the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the third aspect or any possible implementation of the third aspect, the fourth aspect or any possible implementation of the fourth aspect, the fifth aspect or any possible implementation of the fifth aspect, the sixth aspect or any possible implementation of the sixth aspect, the seventh aspect or any possible implementation of the seventh aspect, or the eighth aspect or any possible implementation of the eighth aspect.

[0158] Optionally, the memory is located outside the device.

[0159] Optionally, the device includes the memory, which is connected to the at least one processor and stores instructions that can be executed by the at least one processor.

[0160] In the fourteenth aspect, a chip is provided, which is coupled to a memory and is used to read and execute program instructions stored in the memory, so that the method described in the first aspect or any possible implementation of the first aspect or the second aspect or any possible implementation of the second aspect or the third aspect or any possible implementation of the third aspect or the fourth aspect or any possible implementation of the fourth aspect or the fifth aspect or any possible implementation of the fifth aspect or the sixth aspect or any possible implementation of the sixth aspect or the seventh aspect or any possible implementation of the seventh aspect or the eighth aspect or any possible implementation of the eighth aspect is executed.

[0161] In the fifteenth aspect, a computer program product is provided, comprising instructions, which, when run on a computer, enables the method described in the first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect, or the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect, or the sixth aspect or any possible implementation of the sixth aspect, or the seventh aspect or any possible implementation of the seventh aspect, or the eighth aspect or any possible implementation of the eighth aspect to be executed.

[0162] In the sixteenth aspect, a computer-readable storage medium is provided, comprising a program or instructions. When the program or instructions are run on a computer, the method described in the first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect, or the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect, or the sixth aspect or any possible implementation of the sixth aspect, or the seventh aspect or any possible implementation of the seventh aspect, or the eighth aspect or any possible implementation of the eighth aspect is executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0163] FIG1 is a network architecture diagram of a communication system applicable to an embodiment of the present application;

[0164] FIG2 is a schematic structural diagram of a multi-link device 200 provided in an embodiment of the present application;

[0165] FIG3 is a schematic structural diagram of a multi-link device 300 provided in an embodiment of the present application;

[0166] FIG4 is a flow chart of a multi-link communication method provided in an embodiment of the present application;

[0167] FIG5 is a schematic diagram of a multi-link information unit provided in an embodiment of the present application;

[0168] FIG6 is a schematic diagram of another multi-link information unit provided in an embodiment of the present application;

[0169] FIG7A is a schematic diagram of another multi-link information unit provided in an embodiment of the present application;

[0170] FIG7B is a schematic diagram of another multi-link information unit provided in an embodiment of the present application;

[0171] FIG8 is a schematic diagram of another multi-link information unit provided in an embodiment of the present application;

[0172] FIG9 is a flowchart of a method for mapping services to links provided in an embodiment of the present application;

[0173] FIG10A is a schematic diagram of a possible MAC Header provided in an embodiment of the present application;

[0174] FIG10B is a schematic diagram of a possible service identification bitmap provided in an embodiment of the present application;

[0175] FIG10C is a schematic diagram of another possible MAC Header provided in an embodiment of the present application;

[0176] FIG10D is a schematic diagram of another possible MAC Header provided in an embodiment of the present application;

[0177] FIG10E is a schematic diagram of another possible link identification bitmap provided in an embodiment of the present application;

[0178] FIG10F is a schematic diagram of another possible MAC Header provided in an embodiment of the present application;

[0179] FIG11A is a schematic diagram of a service identifier and link mapping information unit provided in an embodiment of the present application;

[0180] FIG11B is a schematic diagram of another service identifier and link mapping information unit provided in an embodiment of the present application;

[0181] FIG11C is a schematic diagram of another service identifier and link mapping information unit provided in an embodiment of the present application;

[0182] FIG11D is a schematic diagram of another service identifier and link mapping information unit provided in an embodiment of the present application;

[0183] FIG11E is a schematic diagram of another service identifier and link mapping information unit provided in an embodiment of the present application;

[0184] FIG12 is a schematic diagram of another possible service identifier and link mapping information unit provided in an embodiment of the present application;

[0185] FIG13 is a schematic diagram of another possible service identifier and link mapping information unit provided in an embodiment of the present application;

[0186] FIG14 is a flowchart of a method for updating a mapping relationship between a service and a link provided in an embodiment of the present application;

[0187] FIG15 is a schematic diagram of a possible frame structure of an EHT action frame provided in an embodiment of the present application;

[0188] FIG16 is a schematic diagram of a service identifier and link mapping information unit carried in a beacon frame according to an embodiment of the present application;

[0189] FIG17 is a schematic diagram of another possible service identifier and link mapping information unit provided in an embodiment of the present application. DETAILED DESCRIPTION

[0190] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fourth-generation (4G) communication systems, fifth-generation (5G) communication systems, sixth-generation (6G) communication systems or other future evolution systems, or various other wireless communication systems using wireless access technologies, etc. As long as there is a demand for multi-link communication in the communication system, the technical solutions of the embodiments of the present application can be adopted.

[0191] For example, Figure 1 is a network architecture diagram of a communication system applicable to an embodiment of the present application. The communication system includes at least one access point station multi-link device (AP station multi-link device, AP STA MLD) and at least one non-AP station multi-link device (non-AP STA MLD). The access point station multi-link device can be simply referred to as an access point multi-link device or access point device, and its corresponding English abbreviation AP STA MLD can be replaced by AP MLD; the non-access point station multi-link device can be simply referred to as a station multi-link device or station device, and its corresponding English abbreviation non-AP STA MLD can be replaced by STA MLD or non-AP MLD. The AP MLD includes one or more access points (AP), and the 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 takes one AP MLD and one non-AP MLD as an example. In actual applications, the communication system can also include more AP MLDs or non-AP MLDs, the AP MLD can also include more or fewer APs, and the non-AP MLD can also include more or fewer non-AP STAs. This embodiment of the present application does not limit this.

[0192] In the embodiments of the present application, multi-link devices can establish associations (or communication links) with each other before communicating. For example, one or more non-AP STAs in a site multi-link device can establish associations with one or more APs in an access point multi-link device before communicating. As shown in Figure 1, AP1 is associated with non-AP STA1, and AP2 is associated with non-AP STA2A. Of course, site multi-link devices can also communicate with each other, i.e., device-to-device (D2D) communication.

[0193] For ease of description, the following implementation mainly uses a first multi-link device and a second multi-link device performing multi-link communication as an example. The first multi-link device is an AP MLD and the second multi-link device is a non-AP MLD; or the second multi-link device is an AP MLD and the first multi-link device is a non-AP MLD; or both the first and second multi-link devices are non-AP MLDs; or both the first and second multi-link devices are AP MLDs.

[0194] Referring to FIG. 2 , a schematic diagram of the structure of a multi-link device 200 provided in an embodiment of the present application is shown. This device 200 can implement the functions or steps performed by the first or second multi-link device in various method embodiments of the present application. For example, these functions include establishing or updating links for multi-link communication and establishing or updating mappings between services and links. The specific functions or steps will be described in detail below.

[0195] The multi-link device 200 may include a transceiver module 210 and a processing module 220. Optionally, the device may further include a storage unit that can be used to store instructions (code or program) 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 the instructions (code or program) and / or data in the storage unit to implement the corresponding method.

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

[0197] The above-mentioned units may be independently provided or partially or fully integrated. For example, the transceiver module 210 may be integrated with a transmitting unit and a receiving unit.

[0198] The following describes several possible product forms of the multi-link device. It should be understood that the following description is only an example and does not limit the product form of the multi-link device of the embodiment of the application to only this.

[0199] As a possible product form factor, the multi-link device in the embodiments of the present application can be implemented using a general bus architecture. For example, see FIG3 , which is a schematic diagram of the structure of a multi-link device 300 provided in the embodiments of the present application. The multi-link device 300 includes a transceiver 310 and a processor 320.

[0200] The transceiver 310 is configured to communicate with other devices via a transmission medium, thereby enabling the apparatus in the multi-link device 300 to communicate with the other devices. For example, when the multi-link device 300 is a first multi-link device, the other device is a second multi-link device; alternatively, when the multi-link device 300 is a second multi-link device, the other device is a first multi-link device. The processor 320 can use the transceiver 310 to transmit and receive data.

[0201] In a possible implementation, the transceiver 310 may specifically be a radio frequency unit, which may be independent of the multi-link device 300 or integrated within the multi-link device 300 .

[0202] In one possible implementation, the transceiver 310 may further include an antenna, such as a remote antenna independent of the multi-link device 300, or an antenna integrated within the multi-link device 300. The multi-link device 300 includes at least one processor 320, configured to implement or support the multi-link device 300 in implementing the functions of the first multi-link device or the first multi-link device in the method provided in the embodiments of the present application. The dashed box in FIG3 indicates that the antenna is optional for the multi-link device 300.

[0203] In the embodiments of the present 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, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0204] Furthermore, the multi-link device 300 may also include at least one memory 330 for storing program instructions and / or data. The memory 330 is coupled to the processor 320. Coupling in the embodiments of the present application refers to an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between the devices, units, or modules. The processor 320 may operate in conjunction with the memory 330. The processor 320 may execute program instructions and / or data stored in the memory 330 to enable the multi-link device 300 to implement the corresponding method. At least one of the at least one memory may be located in the processor. The dashed box in Figure 3 indicates that the memory is optional for the multi-link device 300.

[0205] In an embodiment of the present application, the memory 330 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or may be a volatile memory, such as a random-access memory (RAM). A memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.

[0206] It should be understood that the specific connection medium between the transceiver 310, processor 320, and memory 330 is not limited in the embodiments of the present application. In Figure 3, the memory 330, processor 320, and transceiver 310 are connected via bus 340. The bus is represented by a bold line in Figure 3. The connection between other components is only for illustrative purposes and is not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 3 only uses a single bold line, but this does not mean that there is only one bus or only one type of bus.

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

[0208] It should be understood that the multi-link devices of various product forms described above have any functions of the first multi-link device or the second multi-link device in the embodiments of the present application, which will not be described in detail here.

[0209] The technical solutions in the embodiments of the present application will be described in detail below with reference to the accompanying drawings in the embodiments of the present application.

[0210] FIG4 is a flowchart of a multi-link communication method provided in an embodiment of the present application, which can be applied to the communication system shown in FIG1 . The method includes:

[0211] S401: A second multi-link device sends a first request message to a first multi-link device, and the first multi-link device receives the first request message from the second multi-link device. The first request message carries identifiers of one or more links and first indication information of each of the one or more links, where the first indication information is used to indicate an operation type of the corresponding link.

[0212] The first multi-link device may be an AP MLD and the second multi-link device may be a non-AP MLD; or the second multi-link device may be an AP MLD and the first multi-link device may be a non-AP MLD; or both the first multi-link device and the second multi-link device may be non-AP MLD.

[0213] In the embodiments of the present application, link operation types may include any one or more of the following: 1) establishing multi-link communication; 2) only providing link information or not establishing multi-link communication; 3) adding a link to a multi-link communication link; 4) deleting a link from a multi-link communication link. It should be understood that the above four operation types are only examples and not limitations, and other operation types are not excluded in actual applications.

[0214] The information of only providing links refers to the information of only providing links in the first request message, and does not request to establish multi-link communication. In other words, not establishing multi-link communication and only providing links in this document can refer to each other.

[0215] For each link, there is only one operation type, for example, any one of the above four operation types.

[0216] If the first request message carries only the identifier of one link and the first indication information, the operation type indicated by the first indication information may be any one of the above four operation types.

[0217] If the first request message carries only identifiers of multiple links and the first indication information, the operation types of any two links among the multiple links may be the same or different.

[0218] Exemplarily, taking the first request message carrying the identifier and first indication information of the first link, and the identifier and first indication information of the second link as an example, the operation type indicated by the first indication information of the first link and the operation type indicated by the first indication information of the second link can be any one of the following a to f:

[0219] a. The operation type indicated by the first indication information of the first link is to establish multi-link communication, and the operation type indicated by the first indication information of the second link is not to establish multi-link communication and only to provide link information;

[0220] b. The operation type indicated by the first indication information of the first link is to add a link to the multi-link communication link, and the operation type indicated by the first indication information of the second link is not to establish multi-link communication and only to provide link information;

[0221] c. The operation type indicated by the first indication information of the first link is to delete a link in the multi-link communication link, and the operation type indicated by the first indication information of the second link is not to establish multi-link communication and only to provide link information;

[0222] d. The operation type indicated by the first indication information of the first link is establishing multi-link communication, and the operation type indicated by the first indication information of the second link is adding a link in the multi-link communication link;

[0223] e. The operation type indicated by the first indication information of the first link is to establish multi-link communication, and the operation type indicated by the first indication information of the second link is to delete a link in the multi-link communication link;

[0224] f. The operation type indicated by the first indication information of the first link is adding a link in the multi-link communication link, and the operation type indicated by the first indication information of the second link is deleting a link in the multi-link communication link.

[0225] The above takes two links as an example. In actual applications, the first request message may also include identifiers and first indication information of other links, such as a third link, a fourth link, etc. The operation types corresponding to the third link and the fourth link may be the same as or different from the operation types of the first link or the second link, and will not be repeated here.

[0226] Optionally, the first request message may also include capability information of sites on each link, or other parameter information of each link, which is not limited in this embodiment of the present application.

[0227] After receiving the first request message, the first multi-link device performs a corresponding operation on each link indicated by the identifier carried in the first request message according to the operation type indicated by the first indication information corresponding to the link.

[0228] Optionally, for a link whose operation type is to only provide link information or not establish multi-link communication, no operation may be performed. Alternatively, for a link whose operation type is to only provide link information or not establish multi-link communication, operations such as link establishment, link deletion, or link addition may not be performed, but other operations may be performed on the link, such as saving the link information or modifying the link information, etc., which are not limited here.

[0229] After executing the corresponding operation on each link indicated by all the identifiers carried in the first request message (excluding the link whose operation type is to only provide link information or not to establish multi-link communication), a first response message may be generated according to the status of each link. Then, S402 is executed:

[0230] S402: The first multi-link device sends a first response message to the second multi-link device, and the second multi-link device receives the first response message sent by the second multi-link device. The first response message carries identifiers of one or more links and second indication information of each link, where the second indication information is used to indicate a link status.

[0231] Specifically, the state of each link corresponds to the operation type indicated by the first indication information corresponding to the link.

[0232] Taking the first link as an example, the status of the first link can be any of the following:

[0233] 1) The status of the first link is success or failure of multi-link communication establishment, which is a response to the operation type of the first link being establishment of multi-link communication;

[0234] 2) The state of the first link is to only provide link information or not establish multi-link communication. This state is a response to the operation type of the first link being to only provide link information or not establish multi-link communication.

[0235] 3) The status of the first link is success or failure in adding a link, and the status is a response to the operation type of the first link being adding a link in a multi-link communication link.

[0236] 4) The status of the first link is success or failure in link deletion, which is a response to the operation type of the first link being link deletion in a multi-link communication link.

[0237] It should be understood that for each link, there is only one type of state. If the first response message carries identifiers of multiple links and the second indication information, the states of any two of the multiple links may be the same or different.

[0238] Of course, the above states are only examples and not limitations, and the possibility of other operation types is not excluded in actual applications.

[0239] It should be noted that, if before the second multi-link device sends the first request message to the first multi-link device, the first multi-link device and the second multi-link device have not yet established a multi-link communication link, for example, S401 to S402 are methods executed by the first multi-link device and the second multi-link device in the multi-link establishment phase, then the operation type indicated by the first indication information carried in the first request message may be establishing multi-link communication, only providing link information, or not establishing multi-link communication, and will not be adding a link to the multi-link communication link or deleting a link from the multi-link communication link. Only if before the second multi-link device sends the first request message to the first multi-link device, the first multi-link device and the second multi-link device have already established a multi-link communication link, for example, S401 to S402 are methods executed by the first multi-link device and the second multi-link device in the link reassociation phase, then the operation type indicated by the first indication information carried in the first request message may be adding a link to the multi-link communication link or deleting a link from the multi-link communication link.

[0240] The following describes in detail the specific implementation of the first link device and the second multi-link device in the multi-link establishment phase.

[0241] Specifically, for example, the first multi-link device is an AP MLD, and the second multi-link device is a non-AP MLD. Before the non-AP MLD and the AP MLD can communicate, they must establish a multi-link. The non-AP MLD can send an association request frame (a first request message) to the AP MLD. After receiving the association request frame, the AP MLD sends an association response frame (a first response message) to the non-AP MLD, thereby establishing the multi-link.

[0242] Optionally, the identifier of each link in the association request frame, the first indication information and other information, or the identifier of each link in the association response frame, the second indication information and other information can be carried by a multi-link information unit (multi-link element, ML element) (the multi-link information unit can also be called a multi-link element).

[0243] Figure 5 is a schematic diagram of a multi-link information unit provided in an embodiment of the present application. As shown in Figure 5, the multi-link information unit includes a control field, a multi-link device common information (MLD common Info) field, and zero or one or more link information sub-units (Link profile subelement) (or referred to as link information fields).

[0244] The multi-link device common information field carries the MLD's common information on all links, such as the MLD's Media Access Control (MAC) address. The link information subunit carries specific information about each link, such as the MLD's station capabilities on each link, link operation type information (i.e., first indication information) or link status information (i.e., second indication information), and other link-related parameter information.

[0245] Non-AP MLD and AP MLD exchange information about multiple links by carrying the ML element in association request and association response frames, thereby establishing multiple links. Communication can then be performed on these links.

[0246] Optionally, the first indication information and / or the second indication information is carried in a first preset field of the multi-link information unit, and the first preset field is located in the link information subunit, as shown in FIG6 .

[0247] In one possible design, when the multi-link information unit is located in an association request frame and an association response frame, the value of the first preset field can refer to different meanings respectively. In other words, the meaning referred to by the value of the first preset field needs to be determined based on the frame type (including association request frame and association response frame) in which the first preset field is located, and the value of the first preset field.

[0248] For example, Table 1 shows possible values ​​of the first preset field (i.e., operation type (Action)) in the multi-link information unit carried by the association request frame and examples of the meaning of each value; Table 2 shows possible values ​​of the first preset field (i.e., status (Status)) in the multi-link information unit carried by the association response frame and examples of the meaning of each value.

[0249] Table 1 Association Request Frame

[0250]

[0251] For the sake of distinction, the first preset field in the multi-link information unit carried by the association request frame is referred to as the first field.

[0252] It should be noted that the above Table 1 lists two possible values ​​of the first field, but it does not mean that the first field must include these two values. In actual applications, the value of the first field may be only a part of Table 1, or may also include other values ​​in addition to the values ​​listed in Table 1.

[0253] Table 2 Association Response Frame

[0254]

[0255] For the sake of distinction, the first preset field in the multi-link information unit carried by the association response frame is referred to as the second field.

[0256] It should be noted that the above Table 2 lists three possible values ​​of the second field, but it does not mean that the second field must include these three values. In actual applications, the value of the second field may be only a part of Table 2, or may also include other values ​​in addition to the values ​​listed in Table 2.

[0257] In another possible design, when the multi-link information unit is located in the association request frame and the association response frame, the value of the first preset field may refer to the same meaning. In other words, the meaning referred to by the value of the first preset field can be directly determined based on the value of the first preset field.

[0258] For example, Table 3 shows possible values ​​of the first preset field in the multilink information unit carried in the association request frame or the association response frame and examples of the meanings of the values.

[0259] Table 3 Association request frame or association response frame

[0260]

[0261] For ease of distinction, the first preset field in the multilink information unit carried in the association request frame and the association response frame is collectively referred to as the third field (the third field is Status when carried in the association response frame and Action when carried in the association request frame).

[0262] 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 multi-link communication is not established. In specific implementation, different values ​​may be used in the association request frame and the association response frame to indicate that only link information is provided or multi-link communication is not established. For example, the fourth value of the first preset field indicates that the operation type is to only provide link information or not establish multi-link communication, and the fifth value of the first preset field indicates that the state is to only provide link information or not establish multi-link communication.

[0263] It should be noted that the above Table 3 lists four possible values ​​of the third field, but it does not mean that the third field must include these four values. In actual applications, the value of the third field may be only a part of Table 3, or may also include other values ​​in addition to the values ​​listed in Table 3.

[0264] In addition to establishing multiple links, multi-link devices may also need to add or delete one or more links during the communication process, which can be achieved by sending reassociation request frames and response frames.

[0265] The following describes in detail the specific implementation of the first link device and the second multi-link device in the link reassociation phase.

[0266] Specifically, the first multi-link device may send a reassociation request frame (first request message) to the second multi-link device. After receiving the association request frame, the second multi-link device may send a reassociation response frame (second response message) to the second multi-link device, thereby achieving link reassociation.

[0267] Optionally, the identifier of each link in the reassociation request frame, the first indication information and other information, or the identifier of each link in the reassociation response frame, the second indication information and other information can be carried by a multi-link information unit (multi-link element, ML element) (the multi-link information unit can also be called a multi-link element).

[0268] Optionally, the first indication information and / or the second indication information are carried in a second preset field of the multi-link information unit, and the second preset field is located in the link information subunit. The second preset field and the first preset field can be the same field, as shown in FIG7A , or different fields, as shown in FIG7B , and this embodiment of the present application does not impose any limitation.

[0269] The following takes the second preset field and the first preset field as an example, which are the same field.

[0270] In one possible design, when the multi-link information unit is located in a reassociation request frame and a reassociation response frame, the value of the first preset field can refer to different meanings respectively. In other words, the meaning referred to by the value of the first preset field needs to be determined based on the frame type (including reassociation request frame and reassociation response frame) in which the first preset field is located, and the value of the first preset field.

[0271] For example, Table 4 shows possible values ​​of the first preset field (operation type (Action)) in the multi-link information unit carried by the reassociation request frame and examples of the meaning of each value; Table 5 shows possible values ​​of the first preset field (status (Status)) in the multi-link information unit carried by the reassociation response frame and examples of the meaning of each value.

[0272] Table 4 Reassociation Request Frame

[0273]

[0274] For the sake of distinction, the first preset field in the multilink information unit carried by the reassociation request frame is referred to herein as the fourth field.

[0275] It should be noted that the above Table 4 lists three possible values ​​of the fourth field, but it does not mean that the fourth field must include these three values. In actual applications, the value of the fourth field may be only a part of Table 4, or may also include other values ​​in addition to the values ​​listed in Table 4.

[0276] Optionally, when a link information subunit in the multi-link element carried in the reassociation request frame is used to delete a link, the link information subunit may only include the link identifier and the link operation type, or the link information subunit may not carry other information except the link identifier and operation type, such as the capability information of the stations working on the link, so as to save resources.

[0277] Table 5 Reassociation Response Frame

[0278] The meaning of the fifth field: The first value is to add a link success; the second value is to add a link failure; the third value is to delete a link success; the fourth value is to delete a link failure; the fifth value is to provide only link information.

[0279] For the sake of distinction, the first preset field in the multi-link information unit carried by the reassociation response frame is referred to herein as the fifth field.

[0280] It should be noted that the above Table 5 lists five possible values ​​of the fifth field, but it does not mean that the fifth field must include these five values. In actual applications, the value of the fifth field may be only a part of Table 5, or may also include other values ​​in addition to the values ​​listed in Table 5.

[0281] In another possible design, when the multi-link information unit is located in the reassociation request frame and the reassociation response frame, the value of the first preset field may refer to the same meaning. In other words, the meaning referred to by the value of the first preset field can be directly determined based on the value of the first preset field.

[0282] For example, Table 6 shows possible values ​​of the first preset field in the multilink information unit carried in the reassociation request frame or the reassociation response frame and examples of the meanings of the values.

[0283] Table 6 Reassociation Request Frame or Reassociation Response Frame

[0284]

[0285]

[0286] For the sake of distinction, the first preset field in the multilink information unit carried by the reassociation request frame or the reassociation response frame is collectively referred to as the sixth field.

[0287] 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 specific implementation, different values ​​may be used in the reassociation request frame and the reassociation response frame to indicate that only link information is provided or multi-link communication is not established. For example, the seventh value of the first preset field indicates that the operation type is to only provide link information or not establish multi-link communication, and the eighth value of the first preset field indicates that the state is to only provide link information or not establish multi-link communication.

[0288] It should be noted that the above Table 6 lists 7 possible values ​​of the sixth field, but it does not mean that the sixth field must include these 7 values. In actual applications, the value of the sixth field may be only a part of Table 6, or may also include other values ​​in addition to the values ​​listed in Table 6.

[0289] In another possible design, the first field, the second field, the fourth field, and the fifth field may be combined into one field, for example, the seventh field. In other words, when the multilink information unit is located in an association request frame, an association response frame, a reassociation request frame, and a reassociation response frame, the value of the first preset field may represent the same meaning.

[0290] For example, Table 7 shows possible values ​​of the first preset field and examples of the meaning of each value in the multilink information unit carried by the association request frame, association response frame, reassociation request frame or reassociation response frame.

[0291] Table 7 Association Request Frame, Association Response Frame, Reassociation Request Frame or Reassociation Response Frame

[0292]

[0293] For the sake of distinction, the first preset field in the multilink information unit carried by the association request frame, the association response frame, the reassociation request frame or the reassociation response frame is collectively referred to as the seventh field.

[0294] In Table 7, the fourth value is used in both the request frame and the response frame to indicate that only the link is provided. In specific implementation, different values ​​may be used in the request frame and the response frame to indicate that only the link is provided. For example, the fourth value of the first preset field indicates that the operation type is to only provide link information or not establish multi-link communication, and the tenth value of the first preset field indicates that the status is to only provide link information.

[0295] It should be noted that the above Table 7 lists 9 possible values ​​of the seventh field, but it does not mean that the seventh field must include these 9 values. In actual applications, the value of the seventh field may be only a part of Table 7, or may also include other values ​​in addition to the values ​​listed in Table 7.

[0296] In the embodiment of the present application, for AP MLD, not all links may be opened initially. Therefore, a new link may be opened (or enabled or activated) during the communication process. When AP MLD opens a new link, AP MLD may carry information about the newly opened link in a multi-link information unit, for example, in a new link information subunit.

[0297] Optionally, the MLD common information field in the multi-link information element may carry third indication information, which is used to indicate that the multi-link element carries information about a new link, as shown in FIG8 .

[0298] Optionally, when an AP MLD establishes (or activates or enables) a new link, information about the newly established link may be carried in each of N consecutive beacon frames, where N is a positive integer. This ensures that the newly established link information can be effectively received by non-AP MLDs, thereby improving system reliability. The value of N is set and broadcast by the AP, or specified by a standard, and is not limited in this embodiment. Optionally, the value of N can be any value in the interval [1, 10], such as 2, 3, 4, or 5.

[0299] From the above, it can be seen that the embodiment of the present application carries the first indication information in the first request message (association request frame or reassociation request frame) and carries the second indication information in the first response message (association response frame or reassociation response frame), so that when the multi-link is established, the MLD establishes multi-link communication on some or all of the links it supports. In subsequent communications, new links can be added or deleted in the established multi-link communication links according to communication needs. In addition, new links can be opened, which improves the flexibility of the MLD for multi-link communication in many aspects and can well meet the needs of the MLD for dynamically updating communication links.

[0300] In order to further improve the performance of multi-link communications and better manage services, an embodiment of the present application also provides a service and link mapping solution to achieve the purpose of providing different services for different services, such as mapping non-important services to some links and important services to all links, or mapping different services to corresponding links according to the rate and latency characteristics of different links.

[0301] As shown in FIG9 , a flowchart of a method for mapping services to links provided in an embodiment of the present application is provided. The method can be applied to the communication system shown in FIG1 . The method includes:

[0302] S901: A second multi-link device sends a second message to a first multi-link device, and the first multi-link device receives the second message from the second multi-link device. The second message carries mapping information between services and links.

[0303] The second multi-link device may send the second message to the first multi-link device by broadcasting (i.e., the second message is a broadcast message), may send the second message to the first multi-link device by multicasting (i.e., the second message is a multicast message), or may send the second message to the first multi-link device by unicasting (i.e., the second message is a unicast message). This embodiment of the present application does not impose any restrictions on this.

[0304] When the second link can send the second message to the first multi-link device in a unicast manner, the first multi-link device may be an AP MLD and the second multi-link device may be a non-AP MLD; or the second multi-link device may be an AP MLD and the first multi-link device may be a non-AP MLD; or both the first multi-link device and the second multi-link device may be non-AP MLD.

[0305] When the second link can send the second message to the first multi-link device in a broadcast or multicast manner, the second multi-link device may be an AP MLD, and the first multi-link device may be a non-AP MLD.

[0306] Optionally, in unicast mode, before the second multi-link device sends the second message to the first multi-link device, the second multi-link device also receives a third message from the first multi-link device, where the third message is used to request the establishment or update of a mapping relationship between services and links. In other words, the second message is a response message to the third message.

[0307] Optionally, in unicast mode, the second message may further carry fourth indication information, where the fourth indication information is used to indicate the second mode for negotiating the mapping of the service identifier and the link. Before the first multi-link device receives the second message from the second multi-link device, the first multi-link device further sends a third message to the second multi-link device, where the third message carries fifth indication information, where the fifth indication information is used to indicate the first mode for negotiating the mapping of the service identifier and the link.

[0308] The first mode may be: requesting to establish a mapping between a service and a link, but not carrying the specific service-to-link mapping method of the requesting party (i.e., the first multi-link device); or requesting to establish a mapping between a service and a link, carrying a suggested mapping method, and allowing the responding party (i.e., the second multi-link device) to modify the mapping relationship in the response frame; or requesting to establish a mapping between a service and a link, carrying a required mapping method, and not allowing the responding party to modify the mapping relationship in the response frame.

[0309] Among them, the second mode can be: the mapping between the business and the link is successfully established and carries the final mapping method; or, the mapping between the business and the link is not successfully established and carries the recommended mapping method; or, the mapping between the business and the link is not successfully established and carries the required mapping method. If the requester sends the request again, the mapping method must be used to successfully establish it; or, the mapping between the business and the link fails to be established.

[0310] Optionally, in broadcast mode, the second message may further carry sixth indication information, used to indicate that the second message carries mapping information of broadcast services and links.

[0311] Optionally, in broadcast mode, before the first multi-link device receives the second message from the second multi-link device, the first multi-link device may further send a fourth message to the second multi-link device, where the fourth message carries seventh indication information, and the seventh indication information is used to indicate that the first multi-link device supports broadcast service-link mapping information.

[0312] Optionally, in broadcast mode, the second message also carries eighth indication information, which is used to indicate the cumulative number of updates of the mapping information between the service and the link, so that the multi-link device that wakes up after hibernation can know the update status of the mapping information between the service and the link after receiving the second message, and determine whether the mapping relationship between the service and the link needs to be updated.

[0313] In one possible design, the mapping information between services and links can be carried in the header field of MAC.

[0314] Specifically, a new control type is defined using the A-Control subfield in the MAC Header to carry mapping information between services and links.

[0315] Example 1. See Figure 10A, which illustrates a possible MAC header according to an embodiment of the present application. The MAC header carries a control ID and control information corresponding to the control ID. The control information field contains two link profile fields. Each link profile contains the identification information of a link (link ID) and the identification information of the service mapped to the link.

[0316] The service identification information may be a traffic ID (TID) bitmap; it may also be a starting TID and an ending TID of the service identifier, where the TID between the starting TID and the ending TID is mapped to the link; or it may be other forms, which are not limited in the embodiments of the present application.

[0317] Each bit in the service identification bitmap corresponds to a service identifier, with different bits corresponding to different service identifiers. Each service identifier represents a specific service. For example, bit i corresponds to service identifier i, where i starts at 0 and has a maximum value equal to the number of service identification bitmap bits minus 1. The service identification bitmap can have 4, 8, 12, or 16 bits, depending on the number of bits configured in the control information. This application does not impose any restrictions on this.

[0318] Referring to Figure 10B, a schematic diagram of a possible service identification bitmap provided in an embodiment of the present application is provided. The service identification bitmap contains 8 bits, wherein the first bit (bit 0) corresponds to the service with TID=0, the second bit (bit 1) corresponds to the service with TID=1, the third bit (bit 2) corresponds to the service with TID=3, the fourth bit (bit 3) corresponds to the service with TID=4, the fifth bit (bit 4) corresponds to the service with TID=4, the sixth bit (bit 5) corresponds to the service with TID=5, the seventh bit (bit 6) corresponds to the service with TID=6, and the eighth bit (bit 7) corresponds to the service with TID=7. Among them, the service with a corresponding field value of 1 is mapped to the link, or the service with a corresponding field value of 0 is mapped to the link. Taking the service with a corresponding field value of 1 being mapped to the link as an example, the service identification bitmap shown in Figure 10B indicates that services 1, 2, and 7 are mapped to the link corresponding to the link profile field.

[0319] Optionally, when only one link profile is required, a special link ID can be carried in another link profile to indicate that the information in this link profile is invalid.

[0320] Example 2. See Figure 10C, which is a schematic diagram of another possible MAC header provided in an embodiment of the present application. The control information field corresponding to each control ID includes a link profile field. Each link profile includes identification information (link ID) of a link and identification information of the service mapped to the link. The second multi-link device can carry link profiles of one or more links in the MAC header based on the actual link-to-service mapping requirements.

[0321] Similarly, the service identification information in the link profile in Example 2 can be a service identification bitmap, a service identification start point and end point, or other forms, which are not limited in this embodiment. For the case where the service identification information is a service identification bitmap, please refer to Figure 10B, which will not be repeated here.

[0322] Example 3. See Figure 10D, which is a schematic diagram of another possible MAC header provided in an embodiment of the present application. The MAC header carries a service identifier (TID) and control information corresponding to the TID. The control information field contains two service profile fields. Each TID profile contains identification information (TID ID) for a service and identification information for the link to which the service is mapped.

[0323] Among them, the link identification information can be a link identification bitmap (link ID bitmap); it can also be the starting point (starting link ID) and ending point (ending link ID) of the link identification, and the service is mapped to the link corresponding to the link ID falling between the starting point and ending point of the link ID; or it can also be other forms, which are not limited in the embodiments of the present application.

[0324] Each bit in the link identification bitmap corresponds to a link identifier, and different bits correspond to different link identifiers. For example, bit i corresponds to link identifier i, where i starts at 0 and has a maximum value equal to the number of link identification bitmap bits minus 1. The number of link identification bitmap bits can be 4, 8, 12, or 16, and the specific number of bits can be determined based on the number of bits configured in the control information. This application does not impose any restrictions on this.

[0325] Referring to Figure 10E, a schematic diagram of a possible link identification bitmap provided in an embodiment of the present application. The link identification bitmap contains 8 bits, wherein the first bit (bit 0) corresponds to the link with Link ID = 0, the second bit (bit 1) corresponds to the link with Link ID = 1, the third bit (bit 2) corresponds to the link with Link ID = 3, the fourth bit (bit 3) corresponds to the link with Link ID = 4, the fifth bit (bit 4) corresponds to the link with Link ID = 4, the sixth bit (bit 5) corresponds to the link with Link ID = 5, the seventh bit (bit 6) corresponds to the link with Link ID = 6, and the eighth bit (bit 7) corresponds to the link with Link ID = 7. Among them, the business is mapped to the link with the corresponding field value of 1, or the business is mapped to the link with the corresponding field value of 0. Taking the business being mapped to the link with the corresponding field value of 1 as an example, the link identification bitmap shown in Figure 10E indicates that the business is mapped to links 1, 2, and 7.

[0326] Optionally, when only one TID profile needs to be carried, a special TID ID can be carried in another TID profile to indicate that the information in this TID profile is invalid.

[0327] Of course, FIG10E is only an example and not a limitation. For example, in actual situations, the number of bits of the link identification bitmap may also be other values, such as 4, 12 or 16, etc., which may be determined according to the number of bits configured by the control information.

[0328] Example 4. See Figure 10F, which is a schematic diagram of another possible MAC header provided in an embodiment of the present application. The control information field corresponding to each control ID includes a service configuration (TID profile) field. Each TID profile includes identification information (TID) of a service and information about the link to which the service is mapped. The second multi-link device can carry one or more service TID profiles in the MAC header based on the actual link-to-service mapping requirements.

[0329] Similarly, the link identification information in the TID profile in Example 4 can be a link identification bitmap, the starting and ending points of the link identification, or other forms, which are not limited in this embodiment of the present application. For the case where the link identification information is a link identification bitmap, please refer to Figure 10E, which will not be repeated here.

[0330] In another possible design, the mapping information between the service and the link is carried in an information unit used to indicate the mapping relationship between the service and the link.

[0331] The present embodiment does not limit the name of the information element used to indicate the service-link mapping relationship. For example, the name may be a service identifier and link mapping information element (TID-to-Link Mapping element). For ease of description, the following uses the service identifier and link mapping information element as an example.

[0332] Refer to Figure 11A, which is a schematic diagram of a service identification and link mapping information unit provided in an embodiment of the present application. The service identification and link mapping information unit includes a control (Control) field and a service identification and link mapping information (TID-to-Link Mapping info) field, and the TID-to-Link Mapping info field is used to carry the mapping information between the service and the link. It should be understood that the service identification and link mapping information (TID-to-Link Mapping info) field can also have other names, which are not limited in the embodiment of the present application. Optionally, the service identification and link mapping information unit can also include fields such as element identification (Element ID), length (Length) or element ID extension (Element ID Extension), which are not limited here.

[0333] There may be various specific implementation forms of the service identifier and link mapping information field. Several possible examples are listed below.

[0334] Example 1, as shown in Figure 11B, the service identification and link mapping information field includes one or more link configuration (Link profile) fields, each link configuration field contains the identification information of a link and the identification information of one or more services mapped to a link. Among them, the identification information of the service can be a service identification bitmap (TID bitmap); it can also be the starting point (starting TID) and the ending point (ending TID) of the service identification, and the TID falling between the starting point and the ending point of the TID is mapped to this link; or it can also be other forms, which are not limited by the embodiments of the present application. In Figure 11B, the identification information of the service is a service identification bitmap as an example. The specific implementation form of the service identification bitmap can refer to Figure 10B and will not be repeated here.

[0335] Optionally, when the TID bitmap in the link configuration field is all 0, it may indicate that the link is closed.

[0336] Optionally, as shown in FIG11C , the link configuration field may further include a field for indicating whether the corresponding link is closed, such as a disable field (or other names, which are not limited in this application). Furthermore, if the disable field indicates that the link is closed, the link configuration field may not carry the service identification information mapped to the link ( FIG11C uses the service identification bitmap as an example), or the link configuration field may only carry the link identification and the disable field, or the TID bitmap may be all 0s.

[0337] Example 2, as shown in Figure 11D, the service identification and link mapping information field includes one or more service configuration fields, each of which contains identification information of a service and identification information of one or more links to which the service is mapped. Among them, the identification information of the link can be a link identification bitmap (link ID bitmap); it can also be the starting point (starting link ID) and the ending point (ending link ID) of the link identifier, and the service is mapped to the link corresponding to the link ID that falls between the starting point and the ending point of the link ID; it can also be a list of link identifiers (link ID list), which contains one or more link identifiers; or other forms, which are not limited by the embodiments of the present application. In Figure 11D, the identification information of the link is a link identification bitmap as an example. The specific implementation form of the link identification bitmap can refer to Figure 10E, which will not be repeated here.

[0338] Optionally, the service configuration field may also exist in the form of an information unit. In this case, the service configuration field may further include fields such as element ID, length, and element ID extension (element ID Extension field), as shown in FIG11E .

[0339] The specific content of the control field may vary depending on the manner in which the second message is sent (or the type of the second message). The broadcast and unicast modes are described below.

[0340] 1. Unicast

[0341] Both the request frame (third message) and the response frame (second message) may carry the service identifier and link mapping information unit.

[0342] See Figure 12, which illustrates another possible service identifier and link mapping information unit according to an embodiment of the present application. As shown in Figure 12, the control field includes a mapping request (TID-to-Link Mapping request) field, which is used to identify the type of frame in which the service identifier and link mapping information unit resides. This field can be 1 bit long, where a 1 indicates a request and a 0 indicates a response.

[0343] As shown in Figure 12, the control field may also include a third preset field, such as a negotiation type field (or negotiation mode field, or other names, not limited here), which is used to negotiate the mapping mode of the service identifier and the link. The negotiation type field in the service identifier and link mapping information unit carried in the request frame is used to indicate the mode used by the requesting party to negotiate the mapping of the service identifier and the link (i.e., the first mode described above), and the negotiation type field in the service identifier and link mapping information unit carried in the response frame is used to indicate the mode used by the responding party to negotiate the mapping of the service identifier and the link (i.e., the second mode described above).

[0344] In one possible design, when the service identification and link mapping information units are located in the request frame and the response frame, the value of the negotiation type field can refer to different meanings respectively. In other words, the meaning referred to by the value of the negotiation type field needs to be determined based on the frame type (including request frame and response frame) in which the negotiation type field is located and the value of the negotiation type field.

[0345] For example, Table 8 shows the possible values ​​of the negotiation type field in the service identification and link mapping information unit carried by the request frame and an example of the meaning of each value; Table 9 shows the possible values ​​of the negotiation type field in the service identification and link mapping information unit carried by the response frame and an example of the meaning of each value.

[0346] Table 8 Request frame

[0347]

[0348] It should be noted that the above Table 8 lists three possible values ​​of the negotiation type field in the request frame, but it does not mean that the negotiation type field must include these three values. In actual applications, the value of the negotiation type field may be only a part of Table 8, or may also include other values ​​in addition to the values ​​listed in Table 8.

[0349] Table 9 Response frame

[0350]

[0351]

[0352] It should be noted that the above Table 9 lists four possible values ​​of the negotiation type field in the response frame, but it does not mean that the negotiation type field must include these four values. In actual applications, the value of the negotiation type field may be only a part of Table 9, or may also include other values ​​in addition to the values ​​listed in Table 9.

[0353] In another possible design, when the service identifier and link mapping information units are located in the request frame and the response frame, the values ​​of the negotiation type fields can respectively refer to the same meaning. In other words, the meaning referred to by the value of the negotiation type field can be directly determined based on the value of the negotiation type field.

[0354] For example, Table 10 shows possible values ​​of the negotiation type field in the service identifier and link mapping information unit carried in a request frame or a response frame, and examples of the meanings of each value.

[0355] Table 10 Request frame or response frame

[0356]

[0357]

[0358] It should be noted that the above Table 10 lists 7 possible values ​​of the negotiation type field in the request frame and the response frame, but it does not mean that the negotiation type field must include these 7 values. In actual applications, the value of the negotiation type field may be only a part of Table 10, or may also include other values ​​in addition to the values ​​listed in Table 10.

[0359] Optionally, as shown in FIG12 , the control field may further include ninth indication information, such as a service direction (Dection) field (or other names, not limited here), used to identify the direction of the service mapped to the link. Direction types may include downlink, uplink, and both UL and DL. The field length may be 1 bit or 2 bits. For example, a field value of 0 indicates uplink, 1 indicates downlink, and 3 indicates both uplink and downlink.

[0360] Optionally, as shown in FIG12 , the control field may further include a second preset field, such as a default mode field (or other names, not limited herein), which may be 1 bit in length. When the default mode field takes a preset value (e.g., 1), it indicates that a default mapping method is used, i.e., all TIDs (or each TID) can be mapped to each link for which multi-link communication is established. In this case, the service identifier and link mapping information unit may not carry service-link mapping information, or the service identifier and link mapping information unit may only carry other fields such as the control field, element identifier, length, or element ID extension.

[0361] It should be understood that any service identification and link mapping information field in the embodiments shown in Figures 11A to 11D can be combined with any control field in the embodiment shown in Figure 12. For example, Figure 13 is a schematic diagram of the service identification and link mapping information unit obtained by one of the combinations.

[0362] The following describes a method for using any of the service identifiers and link mapping information units shown in FIG. 11A to FIG. 13 .

[0363] One is to carry the service identifier and link mapping information unit in the association request frame (third message) and the association response frame (second message) during the multi-link establishment process, thereby completing the negotiation of the service identifier and link mapping when the multi-link is established.

[0364] Another method is that after the multi-link is established, if the multi-link device wants to update the mapping relationship between the service and the link, it can define an extremely high throughput (EHT) action frame and carry the service identifier and link mapping information unit in the EHT action frame to update the mapping relationship.

[0365] Refer to Figure 14, which is a flowchart of a method for updating the mapping relationship between services and links provided in an embodiment of the present application. This method can be applied to the communication system shown in Figure 1.

[0366] S1401: A first multi-link device sends a request frame (third message) to a second multi-link device. The request frame carries a first service identifier and link mapping information unit, requesting to update a service identifier and link mapping relationship.

[0367] S1402: The second multi-link device sends a response frame (second message) to the first multi-link device. The response frame carries a second service identifier and link mapping information unit, which is used to respond to the update of the service identifier and link mapping relationship.

[0368] The request frame and the response frame are both EHT action frames. Figure 15 is a schematic diagram of a possible EHT action frame structure provided by an embodiment of the present application. The value of the Category field can be "EHT", indicating an action frame in 802.11be.

[0369] In order to distinguish between request frames and response frames, the value of the TID-to-Link mapping request field in the service identification and link mapping information unit in the request frame can be set to 1; the value of the TID-to-Link mapping request field in the service identification and link mapping information unit in the response frame can be set to 0.

[0370] In one implementation, the value of the EHT Action field in the EHT Action frame may be "TID-to-Link mapping update information," indicating that the EHT Action frame is used to update the TID-to-Link mapping relationship.

[0371] In another implementation, the value of the EHT Action field in the request frame can be "TID-to-Link mapping update request"; the value of the EHT Action field in the response frame can be "TID-to-Link mapping update response." Taking Table 10 as an example, when the value of the Negotiation Type field in the TID-to-Link Mapping information element in the response frame is the fourth value (accept), the mapping relationship between the TID and the link is negotiated. Otherwise, the first multi-link device can continue to send request frames until the value of the Negotiation Type field in the received response frame is the fourth value (accept).

[0372] 2. Broadcasting Method

[0373] In this manner, the second multi-link device may be an AP MLD, and the first multi-link device may be a non-AP MLD.

[0374] The second multi-link device may carry a service identifier and link mapping information unit in a beacon frame, so as to broadcast the current service identifier and link mapping information to the station.

[0375] Referring to Figure 16, a schematic diagram of another service identification and link mapping information unit provided in an embodiment of the present application, which can be carried in a beacon frame. The control field of the service identification and link mapping information unit includes a broadcast field (sixth indication information), which is used to indicate that the current service identification and link mapping information unit carries broadcast service and link mapping information, that is, the service and link mapping information can be sent to multiple sites for mapping services and links for the multiple sites.

[0376] Optionally, as shown in Figure 16, the control field may also include a service direction (Dection) field, which is used to identify the direction of the service mapped to the link. The direction type may include downlink, uplink, or both UL and DL. The field length may be 1 bit or 2 bits, where 0 indicates uplink, 1 indicates downlink, and 3 indicates both uplink and downlink.

[0377] Optionally, as shown in Figure 16 , the control field may also include a default mode field, which may be 1 bit long. When the default mode field takes a preset value (e.g., 1), it indicates that a default mapping method is used, meaning that all TIDs (or each TID) can be mapped to every link for established multi-link communication. In this case, the service identifier and link mapping information element may not carry service-link mapping information, or the service identifier and link mapping information element may only carry other fields such as the control field, element identifier, length, or element ID extension.

[0378] Before the second multi-link device broadcasts a beacon frame (second message), a station multi-link device, such as the first multi-link device, may send seventh indication information to the second multi-link device, indicating that its device type is a device that supports broadcast service identifier and link mapping (broadcast TID-to-Link mapping supported MLD). Furthermore, when the second multi-link device broadcasts a beacon frame, the first multi-link device will receive the service identifier and link mapping information element in the beacon frame and update its service identifier and link mapping relationship according to the service identifier and link mapping information element.

[0379] For a non-AP MLD, if it supports broadcast TID-to-Link mapping, it cannot send a service identifier and link mapping information element to the AP MLD to change its service identifier and link mapping relationship.

[0380] In a specific embodiment, when requesting multi-link establishment, the non-AP MLD claims that it is broadcast TID-to-Link mapping supported. Specifically, it can carry seventh indication information in the association request frame, indicating that it is broadcast TID-to-Link mapping supported. The seventh indication information can be carried in the EHT capabilities element. The AP MLD can reply with an association response frame and carry a service identifier and link mapping information unit for assigning an initial value to the mapping relationship between the service identifier and the link. After the multi-link establishment is completed, if the AP MLD wants to update the mapping relationship between the service identifier and the link, it can carry the service identifier and link mapping information unit in the beacon frame to broadcast the current service and link mapping information to the station. After receiving it, the non-AP MLD needs to update the mapping relationship.

[0381] Optionally, in order for a dormant non-AP MLD to receive a new mapping relationship after waking up, when the service identifier and link mapping information unit content carried in the beacon frame changes, the AP MLD needs to treat this event as a critical update and increase the value of the check beacon frame field (i.e., the eighth indication information) in the next traffic indication map (TIM) frame sent by one. After waking up from dormancy, the non-AP MLD can compare the value of the received check beacon frame field with the value of the check beacon frame field before dormancy to determine whether the AP MLD has updated the mapping relationship. If it is determined that the AP MLD has updated the mapping relationship, the non-AP MLD can update the mapping relationship based on the latest service identifier and link mapping information unit content.

[0382] Alternatively, the AP MLD may carry a counter field (i.e., the eighth indication information) in the beacon frame, for example, a TID-to-Link mapping update counter. The value of this counter is initialized to 0. When the content of the TID-to-Link mapping information unit changes, the counter value is incremented by 1.

[0383] The number of bits in the counter can be set and broadcast by the AP or specified by the standard, and is not limited in the embodiments of the present application. For example, assuming that the counter is represented by 8 bits, the maximum value of the counter is 255. When the counter value exceeds 255, a modulo (mod) operation is performed on 256, so that 255 plus 1 becomes 0.

[0384] After waking up from hibernation, the non-AP MLD can compare the received counter field value with the counter field value before hibernation to determine whether the AP MLD has updated the mapping relationship. If it is determined that the AP MLD has updated the mapping relationship, the non-AP MLD updates the mapping relationship based on the latest service identifier and link mapping information unit content.

[0385] Optionally, the counter may be carried in the service identifier and link mapping information unit in the beacon frame, as shown in FIG17 .

[0386] S902: The first multi-link device establishes or updates a mapping relationship between services and links according to the mapping information.

[0387] For example, the second message is an association response frame sent by the second multi-link device to the first multi-link device during the multi-link establishment phase (i.e., the second message is a message for establishing a mapping relationship), and the first multi-link device establishes a mapping relationship between the service and the link according to the mapping information between the service and the link carried in the association response frame.

[0388] Alternatively, for example, the second message is an EHT action frame sent by the second multi-link device to the first multi-link device after the multi-link establishment phase is completed (i.e., the second message is a message for updating the mapping relationship). The first multi-link device updates the mapping relationship between the service and the link according to the service-link mapping information carried in the EHT action frame.

[0389] Or for example, the second message is a beacon frame broadcast by the second multi-link device after the multi-link establishment phase is completed (i.e., the second message is a message for updating the mapping relationship), then the first multi-link device updates the mapping relationship between the service and the link according to the mapping information between the service and the link carried in the beacon frame.

[0390] As can be seen from the above, in the embodiment of the present application, the second multi-link device carries the mapping information between the service and the link in the second message, so that the multi-link device can establish the mapping relationship between the service and the link when the multi-link is established, or update the mapping relationship between the service and the link after the multi-link is established. This can more flexibly manage the service and improve the service quality.

[0391] It should be understood that the various embodiments provided in the embodiments of the present application can be combined with each other to achieve different technical effects.

[0392] The terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can represent: a, or b, or c, or a and b, or b and c, or a and c, or a and b and c.

[0393] Furthermore, unless otherwise indicated, ordinal numbers such as "first" and "second" in the embodiments of this application are used to distinguish between multiple objects and are not used to define the order, timing, priority, or importance of multiple objects. For example, the first priority criterion and the second priority criterion are only used to distinguish different criteria and do not indicate differences in the content, priority, or importance of the two criteria.

[0394] In addition, the terms "including" and "having" in the embodiments, claims, and drawings of this application are not exclusive. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules and may also include steps or modules that are not listed.

[0395] The present application embodiment is described with reference to the flow chart and / or block diagram according to the method, device (system) and computer program product of the embodiment of the present application.It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processor of general-purpose computer, special-purpose computer, embedded processing machine or other programmable data processing equipment to produce a machine, so that the instruction executed by the processor of computer or other programmable data processing equipment produces the device for realizing the function specified in one flow chart flow chart or multiple flow charts and / or one block or multiple blocks of block diagram.

[0396] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose 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, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0397] Obviously, those skilled in the art may make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations.

Claims

1. A multi-link communication method, characterized in that, it includes: A first multi-link device receives a first request message sent from a second multi-link device. The first request message carries identifiers of at least two links and first indication information for each of the at least two links. The first indication information is used to indicate the operation type of the link. The operation type includes establishing multi-link communication, and also includes only providing link information or not establishing multi-link communication; The first multi-link device sends a first response message to the second multi-link device. The first response message carries the identifiers of the at least two links and second indication information for each of the at least two links. The second indication information is used to indicate the status of the link.

2. A multi-link communication method, characterized in that, it includes: A second multi-link device sends a first request message to a first multi-link device. The first request message carries identifiers of at least two links and first indication information for each of the at least two links. The first indication information is used to indicate the operation type of the link. The operation type includes establishing multi-link communication, and also includes only providing link information or not establishing multi-link communication; The second multi-link device receives a first response message from the first multi-link device. The first response message carries the identifiers of the at least two links and second indication information for each of the at least two links. The second indication information is used to indicate the status of the link.

3. A multi-link device, characterized in that, it includes a processor, and the processor is coupled to a memory; the processor is configured to execute computer programs or instructions stored in the memory to enable the device to perform the following method: Receive a first request message sent from a second multi-link device. The first request message carries identifiers of at least two links and first indication information for each of the at least two links. The first indication information is used to indicate the operation type of the link. The operation type includes establishing multi-link communication, and also includes only providing link information or not establishing multi-link communication; Send a first response message to the second multi-link device. The first response message carries the identifiers of the at least two links and second indication information for each of the at least two links. The second indication information is used to indicate the status of the link.

4. A multi-link device, characterized in that, it includes a processor, and the processor is coupled to a memory; the processor is configured to execute computer programs or instructions stored in the memory to enable the device to perform the following method: Send a first request message to a first multi-link device. The first request message carries identifiers of at least two links and first indication information for each of the at least two links. The first indication information is used to indicate the operation type of the link. The operation type includes establishing multi-link communication, and also includes only providing link information or not establishing multi-link communication; Receive a first response message from the first multi-link device, where the first response message carries the identifiers of the at least two links and second indication information for each of the at least two links, and the second indication information is used to indicate the status of the link.

5. The method according to claim 1 or 2 or the device according to claim 3 or 4, characterized in that the operation type further includes: adding a link in a multi-link communication link; and / or deleting a link in a multi-link communication link.

6. The method according to any one of claims 1, 2, and 5 or the device according to any one of claims 3, 4, and 5, characterized in that the status includes any one or more of the following: Multi-link communication established successfully; Multi-link communication establishment failed; Only provide link information or do not establish multi-link communication; Link addition successful; Link addition failed; Link deletion successful; Link deletion failed.

7. The method according to any one of claims 1, 2, 5, and 6 or the device according to any one of claims 3 - 6, characterized in that the first indication information and / or the second indication information is carried in a first preset field of a multi-link information unit.

8. The method according to claim 7 or the device according to claim 7, characterized in that in the multi-link information unit carried by the first request message, the first value of the first preset field is used to indicate that the operation type is to establish multi-link communication, and the second value of the first preset field is used to indicate that the operation type is to only provide link information or not establish multi-link communication; or, in the multi-link information unit carried by the first response message, the first value of the first preset field is used to indicate that the status is multi-link communication established successfully, the second value of the first preset field is used to indicate that the status is multi-link communication establishment failed, and the third value of the first preset field is used to indicate that the status is to only provide link information or not establish multi-link communication.

9. The method according to claim 7 or the device according to claim 7, characterized in that in the multi-link information unit carried by the first request message or the first response message, the values of the first preset field include any one or more of the following: A first value, used to indicate that the operation type is to establish multi-link communication; A second value, used to indicate that the status is multi-link communication established successfully; A third value, used to indicate that the status is multi-link communication establishment failed; A fourth value, used to indicate that the operation type or the status is to only provide link information or not establish multi-link communication.

10. The method according to any one of claims 5 - 9 or the device according to any one of claims 5 - 9, characterized in that if the operation type is to establish multi-link communication or not establish multi-link communication or only provide link information or add a link in a multi-link communication link, then the first request message further carries the capability information of the station; or, if the operation type is to delete a link in a multi-link communication link, then the first request message does not carry the capability information of the station.

11. The method according to any one of claims 7-9 or the device according to any one of claims 7-9, characterized in that, the multi-link information unit further carries information about a newly opened link of the access point device; third indication information is carried in the multi-link device MLD common information field of the multi-link information unit, for indicating that the multi-link information unit carries information about a newly opened link.

12. The method according to claim 11 or the device according to claim 11, characterized in that, the information about the newly opened link is carried in each of N consecutive beacon frames, where N is a positive integer.

13. A method for service and link mapping, characterized in that, comprising: a first multi-link device receives a second message from a second multi-link device, and the second message carries service and link mapping information; the first multi-link device establishes or updates a service and link mapping relationship according to the mapping information.

14. A method for service and link mapping, characterized in that, comprising: a second multi-link device generates a second message, and the second message carries service and link mapping information; the second multi-link device sends the second message to a first multi-link device.

15. A multi-link device, characterized in that, comprising a processor, the processor is coupled to a memory; the processor is configured to execute a computer program or instruction stored in the memory, so that the device executes the following method: receive a second message from a second multi-link device, and the second message carries service and link mapping information; establish or update a service and link mapping relationship according to the mapping information.

16. A multi-link device, characterized in that, comprising a processor, the processor is coupled to a memory; the processor is configured to execute a computer program or instruction stored in the memory, so that the device executes the following method: generate a second message, and the second message carries service and link mapping information; send the second message to a first multi-link device.

17. The method according to claim 13, characterized in that, the second message further carries fourth indication information, and the fourth indication information is used to indicate a second mode for negotiating the mapping of service identifiers and links; before the first multi-link device receives the second message from the second multi-link device, further comprising: the first multi-link device sends a third message to the second multi-link device, and the third message carries fifth indication information, and the fifth indication information is used to indicate a first mode for negotiating the mapping of service identifiers and links.

18. The method according to claim 14, characterized in that, the second message further carries fourth indication information, and the fourth indication information is used to indicate a second mode for negotiating the mapping of service identifiers and links; before the second multi-link device generates the second message, further comprising: the second multi-link device receives a third message from the first multi-link device, and the third message carries fifth indication information, and the fifth indication information is used to indicate a first mode for negotiating the mapping of service identifiers and links.

19. The device according to claim 15, wherein, a fourth indication information is further carried in the second message, and the fourth indication information is used to indicate a second mode for negotiating the mapping between the service identifier and the link; the processor is further configured to execute the computer program or instruction stored in the memory, so that the device executes the following method: Before receiving the second message from the second multi-link device, send a third message to the second multi-link device, where a fifth indication information is carried in the third message, and the fifth indication information is used to indicate a first mode for negotiating the mapping between the service identifier and the link.

20. The device according to claim 16, wherein, a fourth indication information is further carried in the second message, and the fourth indication information is used to indicate a second mode for negotiating the mapping between the service identifier and the link; the processor is further configured to execute the computer program or instruction stored in the memory, so that the device executes the following method: Before generating the second message, receive a third message from the first multi-link device, where a fifth indication information is carried in the third message, and the fifth indication information is used to indicate a first mode for negotiating the mapping between the service identifier and the link.

21. The method according to claim 17 or 18 or the device according to claim 19 or 20, wherein, the first mode is: Request to establish the mapping between the service and the link, but do not carry the specific mapping method between the service and the link; Or, request to establish the mapping between the service and the link, and carry the proposed mapping method, allowing the responder to modify the mapping relationship in the response frame; Or, request to establish the mapping between the service and the link, and carry the required mapping method, not allowing the responder to modify the mapping relationship in the response frame.

22. The method according to claim 17 or 18 or the device according to claim 19 or 20, wherein, the second mode is: The mapping between the service and the link is successfully established, and the final mapping method is carried; Or, the mapping between the service and the link is not successfully established, and the proposed mapping method is carried; Or, the mapping between the service and the link is not successfully established, and the required mapping method is carried. If the requester sends a request again, the mapping must be established successfully by using this mapping method; Or, the mapping between the service and the link fails to be established.

23. The method according to any one of claims 17, 18, 21, 22 or the device according to any one of claims 19, 20, 21, 22, wherein, the second message is an association response frame or an EHT action frame.

24. The method according to claim 13 or 14 or the device according to claim 15 or 16, wherein, the second message is a broadcast message.

25. The method according to claim 24, wherein, Before the first multi-link device receives the second message from the second multi-link device, it further includes: The first multi-link device sends a fourth message to the second multi-link device, where a seventh indication information is carried in the fourth message, and the seventh indication information is used to indicate the mapping information between the service and the link supported by the first multi-link device for broadcasting.

26. The method according to claim 24, wherein, before the second multi-link device generates the second message, it further includes: the second multi-link device receives a fourth message from the first multi-link device, and the seventh indication information is carried in the fourth message, and the seventh indication information is used to indicate the mapping information between the services supported by the first multi-link device and the links.

27. The device according to claim 24, wherein, the processor is further configured to execute the computer program or instruction stored in the memory, so that the device executes the following method: before receiving the second message from the second multi-link device, send a fourth message to the second multi-link device, and the seventh indication information is carried in the fourth message, and the seventh indication information is used to indicate the mapping information between the services supported by the device and the links.

28. The device according to claim 24, wherein, the processor is further configured to execute the computer program or instruction stored in the memory, so that the device executes the following method: before generating the second message, receive a fourth message from the first multi-link device, and the seventh indication information is carried in the fourth message, and the seventh indication information is used to indicate the mapping information between the services supported by the first multi-link device and the links.

29. The method according to any one of claims 24, 25, 26 or the device according to any one of claims 24, 27, 28, wherein, the eighth indication information is further carried in the second message, and is used to indicate the cumulative update times of the mapping information between the services and the links.

30. The method according to any one of claims 24, 25, 26, 29 or the device according to any one of claims 24, 27, 28, 29, wherein, the second message is an association response frame or a beacon frame.

31. The method according to any one of claims 13, 14, 17, 18, 21-26, 29, 30 or the device according to any one of claims 15, 16, 19-24, 27-30, wherein, the ninth indication information is further included in the second message, and is used to indicate the service direction of the mapping between the services and the links, and the service direction is any one of uplink, downlink or both uplink and downlink.

32. The method according to any one of claims 13, 14, 17, 18, 21-26, 29-31 or the device according to any one of claims 15, 16, 19-24, 27-31, wherein, the mapping information between the services and the links is carried in the media access control (MAC) header or the information element for indicating the mapping relationship between the services and the links.

33. The method according to claim 32 or the device according to claim 32, wherein, the second preset field is carried in the information element for indicating the mapping relationship between the services and the links, and when the second preset field is a preset value, the second preset field indicates that the first multi-link device maps each service identifier to each link established with multi-link communication.

34. The method according to claim 33 or the apparatus according to claim 33, characterized in that, when the second preset field is a preset value, the mapping information of the service and the link is not carried in the information unit for indicating the mapping relationship between the service and the link.

35. The method according to claim 17 or 18 or the apparatus according to claim 19 or 20, characterized in that, the fourth indication information and / or the fifth indication information is carried in a third preset field of the information unit for indicating the mapping relationship between the service and the link; in the information unit for indicating the mapping relationship between the service and the link carried in the third message or the fourth message, the value of the third preset field includes any one or more of the following items: The first value is used to indicate that the second mode is to request to establish the mapping between the service and the link, but does not carry the specific mapping method between the service and the link; The second value is used to indicate that the second mode is to request to establish the mapping between the service and the link, and carries a recommended mapping method, allowing the responder to modify the mapping relationship in the response frame; The third value is used to indicate that the second mode is to request to establish the mapping between the service and the link, and carries a required mapping method, not allowing the responder to modify the mapping relationship in the response frame; The fourth value is used to indicate that the first mode is that the mapping between the service and the link is successfully established, and carries the final mapping method; The fifth value is used to indicate that the first mode is that the mapping between the service and the link is not successfully established, and carries a recommended mapping method; The sixth value is used to indicate that the first mode is that the mapping between the service and the link is not successfully established, and carries a required mapping method. If the requester sends a request again, the mapping method must be used to establish success; The seventh value is used to indicate that the first mode is that the mapping between the service and the link fails to be established.

36. The method according to any one of claims 13, 14, 17, 18, 21-26, 29-35 or the apparatus according to any one of claims 15, 16, 19-24, 27-35, characterized in that, the mapping information of the service and the link includes: one or more link configuration fields, each of the link configuration fields contains the identification information of a link and the identification information of one or more services mapped to the one link; or, one or more service configuration fields, each of the service configuration fields contains the identification information of a service and the identification information of one or more links mapped to the one service.

37. The method according to any one of claims 13, 14, 17, 18, 21-26, 29-31 or the apparatus according to any one of claims 15, 16, 19-24, 27-31, characterized in that, the second message includes an information unit for indicating the mapping relationship between the service and the link, and the information unit carries a second preset field, and the second preset field is used to indicate that the first multi-link device establishes or updates the mapping relationship between the service and the link by using a default mapping method.

38. The method according to claim 37 or the apparatus according to claim 37, characterized in that, The default mapping method includes: the first multi-link device maps each service identifier to each link on which multi-link communication is established.

39. The method or device according to claim 37, wherein, the information element indicating the service-link mapping relationship does not carry the mapping information of the service and the link.

40. The method or device according to claim 37, wherein, the length of the second preset field is 1 bit; when the value of the second preset field is 1, the second preset field is used to indicate that the first multi-link device establishes or updates the service-link mapping relationship in the default mapping method.

41. A chip, wherein, the chip is coupled to a memory and is configured to read and execute program instructions stored in the memory, so that the method according to any one of claims 1, 5-12 or the method according to any one of claims 2, 5-12 or the method according to any one of claims 13, 17, 21-24, 25, 29-40 or the method according to any one of claims 14, 18, 21-24, 26, 29-40 is executed.

42. A communication device, wherein, comprising: a transceiver module for communicating with other communication devices outside the communication device; a processing module for executing the method according to any one of claims 1, 5-12 or the method according to any one of claims 2, 5-12 or the method according to any one of claims 13, 17, 21-24, 25, 29-40 or the method according to any one of claims 14, 18, 21-24, 26, 29-40 through the transceiver module.

43. A computer program product, wherein, including instructions, when running on a computer, enabling the method according to any one of claims 1, 5-12 or the method according to any one of claims 2, 5-12 or the method according to any one of claims 13, 17, 21-24, 25, 29-40 or the method according to any one of claims 14, 18, 21-24, 26, 29-40 to be executed.

44. A computer-readable storage medium, wherein, including a program or instructions, when the program or instructions run on a computer, enabling the method according to any one of claims 1, 5-12 or the method according to any one of claims 2, 5-12 or the method according to any one of claims 13, 17, 21-24, 25, 29-40 or the method according to any one of claims 14, 18, 21-24, 26, 29-40 to be executed.

45. A computer program, wherein, When it runs on a computer, it causes the method described in any one of claims 1, 5 - 12 or the method described in any one of claims 2, 5 - 12 or the method described in any one of claims 13, 17, 21 - 24, 25, 29 - 40 or the method described in any one of claims 14, 18, 21 - 24, 26, 29 - 40 to be executed.

Images