Multi-link communication method, apparatus, and readable storage medium

Abstract

This application relates to the field of wireless communication, specifically to wireless local area networks supporting the 802.11 series standards. More particularly, it relates to a multi-link communication method, apparatus, and readable storage medium. The method includes: an Access Point Management LD (AP MLD) generating a first frame and transmitting the first frame on a first link. The first frame includes supported rates and BSS membership selector elements, with each element including first indication information. This first indication information instructs a non-AP MLD to prohibit the initiation of multi-link establishment with the AP MLD on the first link. Using embodiments of this application, low-latency services on links that only allow TID mappings corresponding to low-latency services (i.e., cleanlinks) can be prevented from being interfered with by non-low-latency services.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a multi-link communication method, apparatus and readable storage medium. Background Technology

[0002] Wireless local area networks (WLANs) have evolved through several generations, including 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, and the currently under discussion 802.11be. The 802.11be standard is also known as the Extremely High Throughput (EHT) standard, Wi-Fi 7, etc.

[0003] Low latency is a key feature of the 802.11be standard. The 802.11be standard reduces packet latency through multi-link and traffic identifier (TID)-to-link mapping. It also allows access points (APs) to establish a restricted target wakeup time (Restricted TWT) for low-latency service transmission, reducing interference from other services and thus lowering the latency of low-latency services.

[0004] To better support low-latency service transmission, a new TID-to-link mapping capability indicator called enhanced link subset mapping has been proposed. For enhanced link subset mapping, the access point multi-link device (AP MLD) broadcasts a TID-to-link mapping scheme. Some links only allow TID data corresponding to low-latency services to be sent on those links, while other links allow TID data corresponding to all services to be sent on those other links. For example, suppose the AP MLD has three links: link 1, link 2, and link 3, and TID 6 and TID 7 are TIDs used by low-latency services. The AP MLD can broadcast the TID-to-link mapping scheme shown in Table 1 below (in Table 1, the symbol "√" indicates that mapping is allowed, and the symbol "╳" indicates that mapping is not allowed). Link 3 only allows TIDs corresponding to low-latency services to be mapped to this link; this link 3 is called a clean link. However, how to establish a clean link that only allows TID mappings corresponding to low-latency services so that low-latency services on this link are not interfered with by non-low-latency services remains unsolved.

[0005] Table 1

[0006] TID 0 TID 1 TID 2 TID 3 TID 4 TID 5 TID 6 TID 7 link 1 √ √ √ √ √ √ √ √ link 2 √ √ √ √ √ √ √ √ link 3 ╳ ╳ ╳ ╳ ╳ ╳ √ √ Summary of the Invention

[0007] This application provides a multi-link communication method, apparatus, and readable storage medium, which can prevent low-latency services on links that only allow TID mappings corresponding to low-latency services (i.e., clean links) from being interfered with by non-low-latency services.

[0008] The present application is described below from different aspects. It should be understood that the different implementation methods and beneficial effects described below can be referenced from each other.

[0009] Firstly, this application provides a multi-link communication method, comprising: an AP MLD generating a first frame and transmitting the first frame on a first link; the first frame including supported rates and BSS membership selector elements; the supported rates and BSS membership selector elements including first indication information, the first indication information being used to instruct a non-AP MLD to prohibit the initiation of multi-link establishment with the AP MLD on the first link. The AP MLD has at least two links, including a first link and a second link. The first link is a link that only allows low-latency service transmission or a link that only allows TID mappings corresponding to low-latency services, i.e., the first link is a clean link.

[0010] It should be understood that if a non-AP MLD initiates multiple link establishment via a clean link, it's possible that the non-AP MLD will only successfully establish this one link (i.e., a clean link) with the AP MLD. In this case, the non-AP MLD might have both low-latency and non-low-latency services on this link, making it impossible for the link to transmit only low-latency services. Therefore, this solution includes indication information in the Supported Rates and BSS Membership Selector elements to instruct that a non-AP MLD not be allowed to initiate multiple link establishment on the clean link. The non-AP MLD must establish this link through another link of the AP MLD to prevent the non-AP MLD from only successfully establishing a clean link with the AP MLD, thus ensuring that low-latency services on the clean link are not interfered with by non-low-latency services.

[0011] In conjunction with the first aspect, in one possible implementation, the method further includes: the AP MLD transmitting a beacon frame or probe response frame on the second link, the beacon frame or probe response frame including a reduced neighbor report element (RNR element), the RNR element including a neighbor AP information field corresponding to the first access point, the channel number field of the neighbor AP information field being set to 0. The first access point is the access point operated on the first link in the APMLD.

[0012] This scheme sets the channel number field of the first access point in the RNR element to 0, so that the traditional STA cannot discover the first access point through the RNR element and will not switch to the corresponding channel to try to associate; thus, the low-latency service on the clean link is not interfered with by the non-low-latency service.

[0013] In this application, "Legacy STA" refers to a site that only supports protocols prior to 802.11be, such as an HE site that supports 802.11ax, a VHT site that supports 802.11ac, or an HT site that supports 802.11n.

[0014] In conjunction with the first aspect, in one possible implementation, the aforementioned first frame is an associated response frame or a reassociated response frame. This first frame also includes a Quality of Service (QoS) mapping element. This QoS mapping element includes DSCP range fields corresponding to eight different user priorities. The DSCP ranges indicated by the DSCP range fields corresponding to m of the eight different user priorities (0-7) cover the DSCP space. The DSCP low value field and DSCP high value field in the DSCP range fields corresponding to the remaining (8-m) of the eight different user priorities are both set to 255. Here, m is a positive integer less than 8. The DSCP space is the interval [0, 63].

[0015] This application does not distinguish between user priority and TID; the two have a one-to-one correspondence and can be used interchangeably in this application.

[0016] In other words, the DSCP range indicated by the DSCP range field corresponding to all TIDs in the first TID set of the above QoS mapping elements covers the entire DSCP space, i.e., the interval [0, 63]; the DSCP low value field and DSCP high value field in the DSCP range field corresponding to all TIDs in the second TID set are both set to 255. The first TID set includes one or more TIDs, and the second TID set includes one or more TIDs. The union of the first TID set and the second TID set is the TID space, i.e., 0, 1, 2, 3, 4, 5, 6, 7. The TIDs in the first TID set are used to identify non-low latency services, and the TIDs in the second TID set are used to identify low latency services, or only the AP MLD is allowed to map SCS Streams successfully added through the SCS mechanism to the second TID set.

[0017] This scheme divides the TID space (0 to 7) into two parts through QoS mapping elements. One part is used for non-low latency services, and the other part is used for low latency services. The TID can be used to distinguish whether the corresponding MPDU is low latency service data or non-low latency service data. In other words, low latency services and non-low latency services will not be mapped to the same TID.

[0018] In conjunction with the first aspect, in one possible implementation, the method further includes: after the AP MLD sends the first frame on the first link, the method further includes: the AP MLD receiving a stream classification service (SCS) request frame, the SCS request frame including an SCS identifier field, the SCS identifier field being used to indicate the reported SCS stream; the AP MLD sending an SCS response frame, the SCS response frame including a status code field, the status code field being used to indicate whether the AP MLD accepts the SCS stream.

[0019] Optionally, when the status code field indicates that the AP MLD accepts the SCS flow, the SCS response frame may also include a TID-to-link mapping element, which is used to indicate the TID mapping rules.

[0020] This solution uses the SCS mechanism to negotiate the mapping from traffic identifier (TID) to the link, which can reduce signaling overhead.

[0021] In conjunction with the first aspect, in one possible implementation, the method further includes: AP MLD sending data packets; wherein, when the data packet does not match an SCS flow, the TID of the data packet is set according to the QoS mapping element; when the data packet matches an SCS flow, the TID of the data packet is set according to the TID-to-link mapping element carried in the SCS response frame.

[0022] Secondly, this application provides a multi-link communication method, which includes: a non-AP MLD receiving a first frame on a first link and parsing the first frame. The first frame includes supported rates and BSS membership selector elements, which include first indication information used to instruct the non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link. The first link is either a link that only allows low-latency service transmission or a link that only allows the TID mapping corresponding to low-latency services; that is, the first link is a clean link.

[0023] In conjunction with the second aspect, in one possible implementation, the method further includes: the non-AP MLD receiving a beacon frame or probe response frame on the second link, the beacon frame or probe response frame including an RNR element, the RNR element including a neighbor AP information field corresponding to the first access point, the channel number field of the neighbor AP information field being set to 0. The first access point is the access point in the AP MLD that operates on the first link.

[0024] In conjunction with the second aspect, in one possible implementation, the aforementioned first frame is an associated response frame or a reassociated response frame. This first frame also includes a QoS mapping element, which comprises DSCP range fields corresponding to eight different user priorities. The DSCP range fields corresponding to m of the eight different user priorities (0-7) indicate DSCP ranges covering the DSCP space. The DSCP low-value field and DSCP high-value field of the DSCP range fields corresponding to the remaining (8-m) of the eight different user priorities are both set to 255. Here, m is a positive integer less than 8. The DSCP space is the interval [0, 63].

[0025] In conjunction with the second aspect, in one possible implementation, after the non-AP MLD parses the first frame, the method further includes: the non-AP MLD sending an SCS request frame, which includes an SCS identifier field used to indicate the reported SCS stream; and the non-AP MLD receiving an SCS response frame, which includes a status code field used to indicate whether the AP MLD accepts the SCS stream.

[0026] Optionally, when the status code field indicates that the AP MLD accepts the SCS flow, the SCS response frame may also include a TID-to-link mapping element, which is used to indicate the TID mapping rules.

[0027] In conjunction with the second aspect, in one possible implementation, the non-AP MLD sends a data packet, wherein when the data packet does not match the SCS flow, the TID of the data packet is set according to the QoS mapping element; when the data packet matches the SCS flow, the TID of the data packet is set according to the TID-to-link mapping element carried in the SCS response frame.

[0028] Thirdly, this application provides a communication device, which can be an AP MLD or a chip within an AP MLD, such as a Wi-Fi chip. The communication device includes: a processing unit for generating a first frame, the first frame including supported rates and BSS membership selector elements, the supported rates and BSS membership selector elements including first indication information, the first indication information being used to instruct a non-AP MLD to prohibit the initiation of multi-link establishment with the AP MLD on a first link; and a transceiver unit for transmitting the first frame on the first link. The AP MLD has at least two links, the at least two links including a first link and a second link. The first link is a link that only allows low-latency service transmission or a link that only allows the TID mapping corresponding to low-latency services, i.e., the first link is a clean link.

[0029] In conjunction with the third aspect, in one possible implementation, the aforementioned transceiver unit is further configured to transmit a beacon frame or probe response frame on the second link. The beacon frame or probe response frame includes an RNR element, which includes a neighbor AP information field corresponding to the first access point. The channel number field in the neighbor AP information field is set to 0. The first access point is the access point in the AP MLD that operates on the first link.

[0030] In conjunction with the third aspect, in one possible implementation, the aforementioned first frame is an associated response frame or a reassociated response frame. This first frame also includes a QoS mapping element, which comprises DSCP range fields corresponding to eight different user priorities. The DSCP range fields corresponding to m of the eight different user priorities (0-7) indicate DSCP ranges covering the DSCP space. The DSCP low-value field and DSCP high-value field of the DSCP range fields corresponding to the remaining (8-m) of the eight different user priorities are both set to 255. Here, m is a positive integer less than 8. The DSCP space is the interval [0, 63].

[0031] In conjunction with the third aspect, in one possible implementation, the aforementioned transceiver unit is further configured to: receive an SCS request frame, the SCS request frame including an SCS identifier field, the SCS identifier field being used to indicate the reported SCS stream; and send an SCS response frame, the SCS response frame including a status code field, the status code field being used to indicate whether the AP MLD accepts the SCS stream.

[0032] Optionally, when the status code field indicates that the AP MLD accepts the SCS flow, the SCS response frame may also include a TID-to-link mapping element, which is used to indicate the TID mapping rules.

[0033] In conjunction with the third aspect, in one possible implementation, the aforementioned transceiver unit is further configured to: send data packets; wherein, when the data packet does not match an SCS flow, the TID of the data packet is set according to the QoS mapping element; and when the data packet matches an SCS flow, the TID of the data packet is set according to the TID-to-link mapping element carried in the SCS response frame.

[0034] Fourthly, this application provides a communication device, which can be a chip in a non-AP MLD or a non-AP MLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit for receiving a first frame on a first link; and a processing unit for parsing the first frame, which includes supported rates and BSS membership selector elements. The supported rates and BSS membership selector elements include first indication information, which instructs the non-AP MLD to prohibit the initiation of multi-link establishment with the AP MLD on the first link. The first link is either a link that only allows low-latency service transmission or a link that only allows TID mappings corresponding to low-latency services, i.e., the first link is a clean link.

[0035] In conjunction with the fourth aspect, in one possible implementation, the aforementioned transceiver unit is further configured to receive a beacon frame or probe response frame on the second link. The beacon frame or probe response frame includes an RNR element, which includes a neighbor AP information field corresponding to the first access point. The channel number field in the neighbor AP information field is set to 0. The first access point is the access point in the AP MLD that operates on the first link.

[0036] In conjunction with the fourth aspect, in one possible implementation, the first frame is an associated response frame or a reassociated response frame. This first frame also includes a QoS mapping element, which comprises DSCP range fields corresponding to eight different user priorities. The DSCP range fields corresponding to m of the eight different user priorities (0-7) indicate a DSCP range covering the DSCP space. The DSCP low value field and DSCP high value field of the DSCP range fields corresponding to the remaining (8-m) of the eight different user priorities are both set to 255. Here, m is a positive integer less than 8. The DSCP space is the interval [0, 63].

[0037] In conjunction with the fourth aspect, in one possible implementation, the aforementioned transceiver unit is further configured to: send an SCS request frame, the SCS request frame including an SCS identifier field, the SCS identifier field being used to indicate the reported SCS stream; and receive an SCS response frame, the SCS response frame including a status code field, the status code field being used to indicate whether the AP MLD accepts the SCS stream.

[0038] Optionally, when the status code field indicates that the AP MLD accepts the SCS flow, the SCS response frame may also include a TID-to-link mapping element, which is used to indicate the TID mapping rules.

[0039] In conjunction with the fourth aspect, in one possible implementation, the aforementioned transceiver unit is further configured to: send data packets, wherein when the data packet does not match an SCS flow, the TID of the data packet is set according to the QoS mapping element; and when the data packet matches an SCS flow, the TID of the data packet is set according to the TID-to-link mapping element carried in the SCS response frame.

[0040] In one possible implementation of any of the above aspects, the first indication information may be the supported rate and the BSS Membership selector in the BSS Membership selector element set to a preset value, such as 120 or 121, or other unused values. In other words, setting the BSS Membership selector to a preset value indicates that the non-AP MLD can only perform limited multi-link establishment, that is, the non-AP MLD can only establish the link (referring to the clean link) by initiating multi-link establishment through other links (referring to links other than the clean link).

[0041] In one possible implementation of any of the above aspects, the first indication information is further used to instruct a single-link station that supports an extremely high throughput protocol to prohibit establishing an association with the AP MLD on that first link. This prevents the transmission of non-low-latency services on the clean link, provided that the single-link EHT STA can understand the first indication information.

[0042] In any possible implementation of the above aspects, the first frame is any of the following: a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. When the first frame is a beacon frame, (even if the non-AP MLD sends a probe request frame and / or an association request frame on the first link) the AP MLD prohibits replying with (corresponding) probe response frames and / or association response frames on the first link. When the first frame is a probe response frame, the AP MLD prohibits replying with an association response frame on the first link. When the first frame is any of a beacon frame, probe response frame, association response frame, or reassociation response frame, the AP MLD can reject the association (sent on the first link) through the status code field in the association response frame or the reassociation response frame. This reduces the probability of collisions when transmitting low-latency services on the first link.

[0043] The beneficial effects of the first to fourth aspects mentioned above can be referenced from each other.

[0044] Fifthly, this application provides a multi-link communication method, which is mainly applied after multi-link establishment or association process. The method includes: an AP MLD sending a beacon frame on a first link, the beacon frame including supported rates and BSS membership selector elements, the supported rates and BSS membership selector elements including first indication information, the first indication information being used to instruct a first non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link; the AP MLD then sending a BSS transfer management request frame on the first link, the BSS transfer management request frame including second indication information, the second indication information being used to instruct a second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame, the BSS transfer management request frame being used to request a first site associated with the first access point to perform BSS transfer. The first access point can be an access point in the AP MLD operating on the first link. The first site only supports protocols prior to the ultra-high throughput (or 802.11be) protocol, i.e., the first site is a legacy site. The first non-AP MLD is a non-AP MLD that has not yet been associated.

[0045] In this application, the AP MLD has at least two links, including a first link and a second link. During the association process, both the first and second links of the AP MLD allow legacy STAs (Standard Sites) and single-link EHT STAs to associate, and also allow non-AP MLDs to initiate multi-link establishment on the first and second links. However, after successful association, the AP MLD may at some point want to designate the first link as a link that only allows low-latency service transmission or a link that only allows the TID mapping corresponding to low-latency services.

[0046] After successful association, when an AP MLD wants to designate a link as a clean link at a certain time, it sends a beacon frame carrying Supported Rates and BSS Membership Selectors elements on that link. This beacon frame contains indication information to instruct unassociated non-AP MLDs to prohibit the establishment of multi-link connections with that AP MLD on the first link. Additionally, a BSS transfer management request frame is sent on this link. Using the indication information carried in the BSS transfer management request frame, the associated non-AP MLD is instructed to ignore the frame, while the associated Legacy STA performs a BSS transfer. This ensures that low-latency services on this link are not interfered with by non-low-latency services.

[0047] In conjunction with the fifth aspect, in one possible implementation, the method further includes: the AP MLD transmitting a beacon frame or probe response frame on the second link, the beacon frame or probe response frame including an RNR element, the RNR element including a neighbor AP information field corresponding to the first access point, the channel number field of the neighbor AP information field being set to 0. The first access point is the access point in the AP MLD that is operating on the first link.

[0048] Sixthly, this application provides a multi-link communication method, which is mainly applied after multi-link establishment or association process. The method includes: a first station receiving a beacon frame on a first link, the beacon frame including supported rates and BSS membership selector elements, the supported rates and BSS membership selector elements including first indication information, the first indication information being used to instruct a first non-AP MLD to prohibit initiating multi-link establishment with an AP MLD on the first link; the first station then receiving a BSS transfer management request frame on the first link, the BSS transfer management request frame including second indication information, the second indication information being used to instruct a second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame, the BSS transfer management request frame being used to request the first station associated with a first access point to perform a BSS transfer. The first access point can be an access point in the AP MLD operating on the first link. The first station only supports protocols prior to the ultra-high throughput (or 802.11be) protocol, i.e., the first station is a traditional station. The first non-AP MLD is a non-AP MLD that has not yet been associated.

[0049] Seventhly, this application provides a communication device, which can be an AP MLD or a chip within an AP MLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to transmit a beacon frame on a first link, the beacon frame including supported rates and BSS membership selector elements, the supported rates and BSS membership selector elements including first indication information, the first indication information being used to instruct a first non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link; the transceiver unit is further configured to transmit a BSS transfer management request frame on the first link, the BSS transfer management request frame including second indication information, the second indication information being used to instruct a second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame, the BSS transfer management request frame being used to request a first site associated with a first access point to perform a BSS transfer. The first access point can be an access point within an AP MLD operating on the first link. The first site only supports protocols prior to the Very High Throughput Protocol, i.e., the first site is a legacy site. The first non-AP MLD is a non-AP MLD that has not yet been associated.

[0050] Optionally, the communication device further includes a processing unit for generating beacon frames and BSS transfer management request frames.

[0051] In conjunction with the seventh aspect, in one possible implementation, the aforementioned transceiver unit is further configured to transmit a beacon frame or a probe response frame on the second link. The beacon frame or probe response frame includes an RNR element, which includes a neighbor AP information field corresponding to the first access point. The channel number field in the neighbor AP information field is set to 0. The first access point is an access point in the AP MLD that operates on the first link.

[0052] Eighthly, this application provides a communication device, which may be a first site or a chip within the first site, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to receive a beacon frame on a first link, the beacon frame including supported rates and BSS membership selector elements, the supported rates and BSS membership selector elements including first indication information, the first indication information being used to instruct a first non-AP MLD to prohibit initiating multi-link establishment with an AP MLD on the first link; the transceiver unit is further configured to receive a BSS transfer management request frame on the first link, the BSS transfer management request frame including second indication information, the second indication information being used to instruct a second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame, the BSS transfer management request frame being used to request the first site associated with a first access point to perform a BSS transfer. The first access point may be an access point within an AP MLD operating on the first link. The first site only supports protocols prior to the Very High Throughput (or 802.11be) protocol, i.e., the first site is a legacy site. The first non-AP MLD is a non-AP MLD that has not yet been associated.

[0053] Optionally, the communication device also includes a processing unit for parsing beacon frames and BSS transfer management request frames.

[0054] In any of the fifth to eighth aspects described above, the first indication information may be the supported rate and the BSS Membershipselector in the BSS Membershipselector element set to a preset value, such as 120 or 121, or other unused values. In other words, setting the BSS Membershipselector to a preset value indicates that the non-AP MLD can only perform limited multi-link establishment, that is, the non-AP MLD can only establish the link (referring to the clean link) by initiating multi-link establishment through other links (referring to links other than the clean link).

[0055] In one possible implementation of any of the fifth to eighth aspects described above, the first instruction information is further used to instruct a single-link site that supports a very high throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

[0056] In any of the fifth to eighth aspects described above, in one possible implementation, the AP MLD prohibits the reply of (corresponding) probe response frames and / or associated response frames on the first link.

[0057] The beneficial effects of aspects five through eight mentioned above can be referenced from each other.

[0058] Ninthly, this application provides a multi-link communication method, which is mainly applied in enhanced link subset mapping scenarios. The method includes: a first device generating and sending an association response frame or a reassociation response frame, wherein the association response frame or the reassociation response frame includes a QoS mapping element. The QoS mapping element includes DSCP range fields corresponding to eight different user priorities, and the DSCP ranges indicated by the DSCP range fields corresponding to m of the eight different user priorities cover the DSCP space. The DSCP low value field and DSCP high value field in the DSCP range fields corresponding to the remaining (8-m) of the eight different user priorities are both set to 255.

[0059] In other words, the DSCP range indicated by the DSCP range field corresponding to all TIDs in the first TID set of this QoS mapping element covers the entire DSCP space, i.e., the interval [0, 63]; the DSCP low value field and DSCP high value field in the DSCP range field corresponding to all TIDs in the second TID set are both set to 255. The first TID set includes one or more TIDs, and the second TID set includes one or more TIDs. The union of the first TID set and the second TID set is the TID space, i.e., 0, 1, 2, 3, 4, 5, 6, 7. The TIDs in the first TID set are used to identify non-low latency services, and the TIDs in the second TID set are used to identify low latency services, or only the AP MLD is allowed to map SCS Streams successfully added through the SCS mechanism to the second TID set.

[0060] The first device is either an AP or an AP MLD. The DSCP space is the interval [0, 63]. m is a positive integer less than 8.

[0061] This application does not distinguish between user priority and TID; the two have a one-to-one correspondence and can be used interchangeably in this application.

[0062] This scheme divides the TID space (0 to 7) into two parts using QoS mapping elements: one part for non-low-latency services and the other for low-latency services. The TID distinguishes whether a corresponding MPDU is low-latency or non-low-latency service data; that is, low-latency and non-low-latency services will not map to the same TID. Furthermore, this scheme also supports the implementation of Enhanced Link Subset Mapping, ensuring that Clean links can only be used for transmitting low-latency services.

[0063] Tenthly, this application provides a multi-link communication method, which is mainly applied in an enhanced link subset mapping scenario. The method includes: a second device receiving and parsing an associated response frame or a reassociated response frame, wherein the associated response frame or the reassociated response frame includes a QoS mapping element. The QoS mapping element includes DSCP range fields corresponding to eight different user priorities, and the DSCP ranges indicated by the DSCP range fields corresponding to m of the eight different user priorities cover the DSCP space. The DSCP low value field and DSCP high value field in the DSCP range fields corresponding to the remaining (8-m) of the eight different user priorities are both set to 255.

[0064] The second device is either an EHT STA or a non-AP MLD. The DSCP space is the interval [0, 63]. m is a positive integer less than 8.

[0065] Eleventhly, this application provides a communication device, which may be a first device or a chip in the first device, such as a Wi-Fi chip. The communication device includes: a processing unit configured to generate an associated response frame or a reassociated response frame, wherein the associated response frame or the reassociated response frame includes a QoS mapping element, the QoS mapping element including DSCP range fields corresponding to eight different user priorities, wherein the DSCP range indicated by the DSCP range fields corresponding to m of the eight different user priorities covers a DSCP space, the DSCP space being the interval [0, 63]; the DSCP low value field and DSCP high value field in the DSCP range fields corresponding to the other (8-m) of the eight different user priorities are both set to 255; and a transceiver unit configured to transmit the associated response frame or the reassociated response frame. m is a positive integer less than 8.

[0066] In a twelfth aspect, this application provides a communication device, which may be a second device or a chip in a second device, such as a Wi-Fi chip. The communication device includes: a transceiver unit for receiving an associated response frame or a reassociated response frame; and a processing unit for parsing the associated response frame or the reassociated response frame, wherein the associated response frame or the reassociated response frame includes a QoS mapping element, the QoS mapping element including DSCP range fields corresponding to eight different user priorities, the DSCP range indicated by the DSCP range fields corresponding to m of the eight different user priorities covering a DSCP space, the DSCP space being the interval [0, 63]; the DSCP low value field and DSCP high value field in the DSCP range fields corresponding to the remaining (8-m) of the eight different user priorities are both set to 255. m is a positive integer less than 8.

[0067] The beneficial effects of aspects ten, eleven, and twelfth above can be referred to the effective effects described in aspect nine above.

[0068] In a thirteenth aspect, this application provides a multi-link communication method, the method comprising: AP MLD receiving an SCS request frame, the SCS request frame carrying a TID-to-link mapping element, the TID-to-link mapping element being used to indicate a TID mapping rule; and AP MLD sending an SCS response frame.

[0069] This solution reduces signaling overhead and improves accuracy by simultaneously negotiating TID-to-link Mapping during SCS negotiation.

[0070] In a fourteenth aspect, this application provides a multi-link communication method, the method comprising: a non-AP MLD sending an SCS request frame, the SCS request frame carrying a TID-to-link mapping element, the TID-to-link mapping element being used to indicate a TID mapping rule; and a non-AP MLD receiving an SCS response frame.

[0071] In a fifteenth aspect, this application provides a communication device, which may be an AP MLD or a chip in an AP MLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to receive an SCS request frame, the SCS request frame carrying a TID-to-link mapping element, the TID-to-link mapping element being used to indicate TID mapping rules; the transceiver unit is also configured to send an SCS response frame.

[0072] Optionally, the communication device may further include a processing unit for generating an SCS response frame.

[0073] In a sixteenth aspect, this application provides a communication device, which may be a chip in a non-AP MLD or a non-APMLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to send an SCS request frame, the SCS request frame carrying a TID-to-link mapping element, the TID-to-link mapping element being used to indicate TID mapping rules; the transceiver unit is also configured to receive an SCS response frame.

[0074] Optionally, the communication device further includes a processing unit for generating an SCS request frame.

[0075] In one possible implementation of any of aspects thirteen through sixteen above, the SCS request frame includes an SCS identifier (SCSID) field to indicate a reported SCS flow; the SCS response frame includes a status code field to indicate whether the AP MLD accepts the SCS flow reported in the SCS request frame. When the status code field indicates that the AP MLD accepts the SCS flow, the SCS response frame also carries a TID-to-link mapping element to indicate the TID mapping rules. When the status code field indicates that the AP MLD rejects the SCS flow, the SCS response frame does not carry a TID-to-link mapping element.

[0076] This scheme indicates whether the AP MLD accepts the negotiation of TID-to-link mapping by including or omitting the TID-to-link mapping element in the SCS response frame, and its implementation is simple.

[0077] The beneficial effects of aspects thirteen through sixteen mentioned above can be referenced from each other.

[0078] In a seventeenth aspect, this application provides a multi-link communication method, the method comprising: an AP MLD receiving an SCS request frame, the SCS request frame including an SCS identifier field for indicating a reported SCS flow; the AP MLD sending an SCS response frame including a status code field set to a first value (e.g., 0) for indicating that the AP MLD accepts the SCS flow; the SCS response frame also carrying a TID-to-link mapping element for indicating a TID mapping rule; and the SCS response frame for instructing a non-AP MLD to transmit data according to the TID mapping rule indicated by the TID-to-link mapping element.

[0079] This scheme reduces signaling overhead by directly including the TID-to-link mapping element in the SCS response frame to instruct the non-AP MLD to transmit data according to the indicated TID-to-link mapping.

[0080] Eighteenthly, this application provides a multi-link communication method, the method comprising: a non-AP MLD sending an SCS request frame, the SCS request frame including an SCS identifier field for indicating a reported SCS flow; the non-AP MLD receiving an SCS response frame, the SCS response frame including a status code field set to a first value (e.g., 0) for indicating that the AP MLD accepts the SCS flow; the SCS response frame also carrying a TID-to-link mapping element for indicating a TID mapping rule; the SCS response frame for instructing the non-AP MLD to transmit data according to the TID mapping rule indicated by the TID-to-link mapping element.

[0081] Nineteenthly, this application provides a communication device, which may be an AP MLD or a chip in the AP MLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to receive an SCS request frame, the SCS request frame including an SCS identifier field used to indicate a reported SCS stream; the transceiver unit is further configured to send an SCS response frame, the SCS response frame including a status code field set to a first value (e.g., 0) to indicate that the AP MLD accepts the SCS stream; the SCS response frame also carries a TID-to-link mapping element, the TID-to-link mapping element used to indicate a TID mapping rule; the SCS response frame is used to instruct a non-AP MLD to transmit data according to the TID mapping rule indicated by the TID-to-link mapping element.

[0082] Optionally, the communication device may further include a processing unit for generating an SCS response frame.

[0083] In a twentieth aspect, this application provides a communication device, which can be a chip in a non-AP MLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to send an SCS request frame, the SCS request frame including an SCS identifier field used to indicate a reported SCS stream; the transceiver unit is further configured to receive an SCS response frame, the SCS response frame including a status code field set to a first value (e.g., 0), used to indicate that the AP MLD accepts the SCS stream; the SCS response frame also carries a TID-to-link mapping element, the TID-to-link mapping element used to indicate a TID mapping rule; the SCS response frame is used to instruct the non-AP MLD to perform data transmission according to the TID mapping rule indicated by the TID-to-link mapping element.

[0084] Optionally, the communication device further includes a processing unit for generating an SCS request frame.

[0085] The beneficial effects of aspects seventeen through twentieth can be referenced from each other.

[0086] In a twentieth aspect, this application provides a multi-link communication method, the method comprising: an AP MLD receiving an SCS request frame, the SCS request frame including an SCS identifier field and a QoS feature element, the SCS identifier field being used to indicate a reported SCS flow, the QoS feature element including third indication information, the third indication information being used to indicate the access method of the SCS flow; and the AP MLD sending an SCS response frame.

[0087] This scheme indicates the access method requested by the STA by carrying indication information in the QoS feature element. It can also indicate the access policy of the corresponding traffic stream through the SCS mechanism, thus saving signaling overhead.

[0088] In a twentieth aspect, this application provides a multi-link communication method, the method comprising: a non-AP MLD sending an SCS request frame, the SCS request frame including an SCS identifier field and a QoS feature element, the SCS identifier field being used to indicate a reported SCS flow, the QoS feature element including third indication information, the third indication information being used to indicate the access method of the SCS flow; and a non-AP MLD receiving an SCS response frame.

[0089] In a twentieth aspect, this application provides a communication device, which may be an AP MLD or a chip within an AP MLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to receive an SCS request frame, the SCS request frame including an SCS identifier field and a QoS feature element, the SCS identifier field indicating a reported SCS flow, and the QoS feature element including third indication information indicating the access method of the SCS flow; the transceiver unit is also configured to send an SCS response frame.

[0090] Optionally, the communication device may further include a processing unit for generating an SCS response frame.

[0091] In a twentieth aspect, this application provides a communication device, which may be a non-AP MLD or a chip within a non-AP MLD, such as a Wi-Fi chip. The communication device includes: a transceiver unit configured to send an SCS request frame, the SCS request frame including an SCS identifier field and a QoS feature element, the SCS identifier field indicating a reported SCS flow, and the QoS feature element including third indication information indicating the access method of the SCS flow; the transceiver unit is also configured to receive an SCS response frame.

[0092] Optionally, the communication device further includes a processing unit for generating an SCS request frame.

[0093] In any of the twenty-first to twenty-fourth aspects described above, the QoS feature elements may further include fourth indication information, which is used to indicate the access type mapped to the data packets of the SCS flow.

[0094] Optionally, both the third and fourth indication information can be located in the control info field of the QoS feature element.

[0095] This scheme also indicates the access type mapped to the data packets of the SCS flow in the QoS feature element, thereby realizing the negotiation of access policy and access type of service flow through a single process and saving signaling overhead.

[0096] The beneficial effects of aspects 21 to 24 mentioned above can be referenced from each other.

[0097] In a twentieth aspect, this application provides a communication device including a processor and a transceiver. The transceiver is used to send and receive various frames. The computer program includes program instructions that, when executed by the processor, cause the communication device to perform the multi-link communication method described in any possible implementation of the first, second, fifth, sixth, ninth, tenth, thirteenth, fourteenth, seventeenth, eighteenth, twenty-first, or twenty-second aspects, or any of these aspects. The transceiver may be a radio frequency module in the communication device, or a combination of a radio frequency module and an antenna, or an input / output interface of a chip or circuit. Optionally, the communication device further includes a memory for storing the computer program.

[0098] In a twentieth aspect, this application provides a computer-readable storage medium storing program instructions that, when executed on a computer, cause the computer to perform the multi-link communication method described in any possible implementation of the first aspect, or the second aspect, or the fifth aspect, or the sixth aspect, or the ninth aspect, or the tenth aspect, or the thirteenth aspect, or the fourteenth aspect, or the seventeenth aspect, or the eighteenth aspect, or the twenty-first aspect, or the twenty-second aspect, or any of the aspects.

[0099] In a twentieth aspect, this application provides a program product containing program instructions that, when executed, causes the multi-link communication method described in any possible implementation of the first aspect, or the second aspect, or the fifth aspect, or the sixth aspect, or the ninth aspect, or the tenth aspect, or the thirteenth aspect, or the fourteenth aspect, or the seventeenth aspect, or the eighteenth aspect, or the twenty-first aspect, or the twenty-second aspect, or any of the aspects, to be executed.

[0100] In a twentieth aspect, this application provides an apparatus, which can be implemented as a chip or as a device, including processing circuitry and an input / output interface. The input / output interface is used for sending and receiving frames; the processing circuitry is used to read and execute a program stored in a memory to execute the multi-link communication method described in any possible implementation of the first, second, fifth, sixth, ninth, tenth, thirteenth, fourteenth, seventeenth, eighteenth, twenty-first, or twenty-second aspects, or any of these aspects. Optionally, the apparatus further includes a memory connected to the processor via a circuit.

[0101] Optionally, the processor and memory mentioned above can be physically independent units, or the memory can be integrated with the processor.

[0102] By implementing the embodiments of this application, low-latency services on links (i.e., cleanlinks) that only allow TID mappings corresponding to low-latency services can be prevented from being interfered with by non-low-latency services. Attached Figure Description

[0103] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0104] Figure 1 This is a schematic diagram of the architecture of the wireless communication system provided in the embodiments of this application;

[0105] Figure 2 This is a schematic diagram of multi-link communication provided in an embodiment of this application;

[0106] Figure 3a This is a schematic diagram of the structure of a multi-link device provided in an embodiment of this application;

[0107] Figure 3b This is another structural schematic diagram of the multi-link device provided in the embodiments of this application;

[0108] Figure 4This is a schematic diagram illustrating the connection between an AP MLD and a non-AP MLD according to an embodiment of this application;

[0109] Figure 5 This is a schematic diagram of a frame format for a multi-link element provided in an embodiment of this application;

[0110] Figure 6 This is a schematic diagram of the frame format of an SCS request frame provided in an embodiment of this application;

[0111] Figure 7a This is a schematic diagram of a frame format of the SCS descriptor provided in an embodiment of this application;

[0112] Figure 7b This is a schematic diagram of another frame format of the SCS descriptor provided in the embodiments of this application;

[0113] Figure 8 This is a schematic diagram of the frame format of an internal access category priority element provided in an embodiment of this application;

[0114] Figure 9 This is a schematic diagram of the frame format of an SCS response frame provided in an embodiment of this application;

[0115] Figure 10 This is a schematic diagram of the frame format of a TID-to-link Mapping element provided in an embodiment of this application;

[0116] Figure 11 This is a schematic diagram of the frame format of a QoS mapping element provided in an embodiment of this application;

[0117] Figure 12 This is a schematic diagram of the frame format of an RNR element provided in an embodiment of this application;

[0118] Figure 13 This is a schematic diagram of a BSS transfer management operation process provided in an embodiment of this application;

[0119] Figure 14 This is a schematic diagram of a TXOP sharing method provided in an embodiment of this application;

[0120] Figure 15 This is a first schematic flowchart of the multi-link communication method provided in the embodiments of this application;

[0121] Figure 16 This is a schematic diagram of the frame format of the supported rates and BSS membership selector elements provided in the embodiments of this application;

[0122] Figure 17a This is a schematic diagram of a clean link in the AP MLD provided in the embodiments of this application;

[0123] Figure 17b This is another schematic diagram of the clean link in the AP MLD provided in the embodiments of this application;

[0124] Figure 18 This is a second schematic flowchart of the multi-link communication method provided in the embodiments of this application;

[0125] Figure 19a This is a schematic diagram of the frame format of the BTM Request frame provided in the embodiments of this application;

[0126] Figure 19b This is a schematic diagram of the frame format of the BTM Response frame provided in the embodiments of this application;

[0127] Figure 20 This is a third schematic flowchart of the multi-link communication method provided in the embodiments of this application;

[0128] Figure 21 This is a schematic flowchart of the fourth multi-link communication method provided in the embodiments of this application;

[0129] Figure 22 This is a fifth schematic flowchart of the multi-link communication method provided in the embodiments of this application;

[0130] Figure 23 This is a schematic diagram of the frame format of the QoS feature elements provided in the embodiments of this application;

[0131] Figure 24 This is a schematic diagram of the frame format of the control information field provided in the embodiments of this application;

[0132] Figure 25 This is a schematic diagram of the structure of the communication device 1 provided in the embodiments of this application;

[0133] Figure 26 This is a schematic diagram of the structure of the communication device 2 provided in the embodiments of this application;

[0134] Figure 27 This is a schematic diagram of the structure of the communication device 1000 provided in the embodiments of this application. Detailed Implementation

[0135] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0136] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, and c can be single or multiple.

[0137] In the description of this application, the words "first" and "second" do not limit the quantity or the order of execution, and the words "first" and "second" do not necessarily imply that they are different.

[0138] In this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0139] In this application, the use of singular designations for elements is intended to represent "one or more" rather than "one and only one," unless otherwise specified.

[0140] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0141] To facilitate understanding of the methods provided in the embodiments of this application, the system architecture of the methods provided in the embodiments of this application will be described below. It is understood that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application and does not constitute a limitation on the technical solutions provided in the embodiments of this application.

[0142] This application refers to next-generation 802.11 standard station equipment that simultaneously supports communication across multiple links as a multi-link device (MLD), where the internal entity responsible for any one link is called a station (STA). If all stations within an MLD are access points (APs), it can be further called an AP MLD; if all stations within an MLD are non-access point stations (non-AP STAs), it can be further called a non-AP MLD. In other words, a multi-link device includes one or more affiliated STAs. An affiliated STA is a logical station that can operate on a single link, frequency band, or channel. The affiliated STA can be an access point (AP) or a non-access point station (non-AP STA). 802.11be refers to multi-link devices belonging to AP sites as AP multi-link devices (AP MLDs) and multi-link devices belonging to non-AP STA sites as non-AP multi-link devices (non-AP MLDs).

[0143] Optionally, a multi-link device may include multiple logical stations, each operating on a single link, but multiple logical stations are allowed to operate on the same link. During data transmission, AP MLDs and non-AP MLDs can use link identifiers to identify a link or stations on a link. Before communication, AP MLDs and non-AP MLDs can negotiate or communicate the correspondence between link identifiers and a link or stations on a link. Therefore, during data transmission, it is unnecessary to transmit a large amount of signaling information to indicate the link or stations on the link; carrying the link identifier is sufficient, reducing signaling overhead and improving transmission efficiency.

[0144] Optionally, multi-link devices can implement wireless communication by conforming to the 802.11 series of protocols. For example, they can follow extremely high throughput (EHT) sites or sites based on or compatible with 802.11be to communicate with other devices. Of course, other devices can be multi-link devices or not.

[0145] The technical solution provided in this application is mainly applied in wireless local area networks (WLANs), such as in scenarios where AP MLDs communicate with non-AP MLDs. Optionally, this communication scenario may also include legacy STAs that only support transmission over a single link. In the embodiments of this application, the term "communication" may also be described as "data transmission," "information transmission," or "transmission." The term "transmission" can refer to sending and receiving in general.

[0146] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application. Figure 1 As shown, the wireless communication system includes at least one AP MLD (such as...) Figure 1 AP MLD100 and at least one non-AP MLD (such as Figure 1 (The non-AP MLD200 and non-AP MLD300 are optional). Figure 1 This also includes traditional sites that only support transmission over a single link (such as...). Figure 1 The single-link non-AP STA400 (also known as STA400) is used in this context. The AP MLD provides services to the non-AP MLD. Multiple links can be used between the non-AP MLD and the AP MLD to improve throughput. A STA within a non-AP MLD can also communicate with an AP within an AP MLD via a single link. Understandably... Figure 1 The number of AP MLDs and non-AP MLDs is merely illustrative.

[0147] Optional, see Figure 2 , Figure 2 This is a schematic diagram of multi-link communication provided in an embodiment of this application. For example... Figure 2 As shown, the APMLD includes n stations, namely AP1, AP2, ..., APn; the non-AP MLD also includes n stations, namely STA1, STA2, ..., STAn. Communication between MLDs is multi-link communication. Figure 2Links 1 through n in the network constitute multiple links. In other words, AP MLDs and non-AP MLDs can communicate in parallel using links 1, 2, ..., n. Within an AP MLD, one AP can establish an association with one STA in a non-AP MLD. For example, STA1 in a non-AP MLD can be associated with AP1 in an AP MLD, STA2 in a non-AP MLD can be associated with AP2 in an AP MLD, STAn in a non-AP MLD can be associated with APn in an AP MLD, and so on.

[0148] Optional, see Figure 3a , Figure 3a This is a schematic diagram of a multi-link device provided in an embodiment of this application. The 802.11 standard focuses on the 802.11 physical layer (PHY) and medium access control (MAC) layer portions of the multi-link device. For example... Figure 3a As shown, the multiple STAs in a multi-link device are independent of each other at the low MAC and PHY layers, and also independent at the high MAC layer. See also Figure 3b , Figure 3b This is another structural schematic diagram of the multi-link device provided in the embodiments of this application. For example... Figure 3b As shown, the multiple STAs included in the multi-link device are independent at the low MAC and PHY layers, but share the high MAC layer. Of course, during multi-link communication, the non-AP MLD can adopt an independent high MAC layer structure, while the AP MLD adopts a shared high MAC layer structure; alternatively, the non-AP MLD can adopt a shared high MAC layer structure, while the AP MLD adopts an independent high MAC layer structure; or both the non-AP MLD and AP MLD can adopt a shared high MAC layer structure; or both the non-AP MLD and AP MLD can adopt an independent high MAC layer structure. This application does not limit the internal structure diagram of the multi-link device. Figure 3a and Figure 3b This is merely an illustrative example. For instance, either the high MAC layer or the low MAC layer can be implemented by a processor in the chip system of a multi-link device, or they can be implemented by different processing modules in a single chip system.

[0149] Optionally, High-MAC primarily handles the allocation of sequence numbers (SN) and packet numbers (PN) for MAC service data units (MSDUs), as well as encryption and decryption operations. Low-MAC primarily handles the assembly of MAC protocol data units (MPDUs) for each link, channel access, packet transmission, and reception acknowledgment operations.

[0150] In the embodiments of this application, the multi-link device may allow services with the same traffic identifier (TID) to be transmitted simultaneously on different links, or even allow the same data packet to be transmitted on different links; it may also disallow services with the same TID to be transmitted on different links, but allow services with different TIDs to be transmitted on different links.

[0151] Multi-link devices can operate in one or more frequency bands, including sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz.

[0152] For example, the multi-link device in the embodiments of this application can be a single-antenna device or a multi-antenna device. For instance, it can be a device with two or more antennas. The embodiments of this application do not limit the number of antennas included in the multi-link device.

[0153] For example, a multi-link device (which can be either a non-AP MLD or an AP MLD) is a device with wireless communication capabilities. This device can be a complete device or a chip or processing system installed in a complete device. Devices with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems. For example, the non-AP MLD in the embodiments of this application has wireless transceiver capabilities, can support the 802.11 series protocols, and can communicate with AP MLDs, single-link devices, or other non-AP MLDs. For example, a non-AP MLD is any user communication device that allows users to communicate with an AP and thus with a WLAN. For example, a non-AP MLD can be a user device that can connect to the Internet, such as a tablet, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), or mobile phone, or an IoT node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles; a non-AP MLD can also be a chip and processing system in the above-mentioned terminals. An AP MLD is a device that can provide services to a non-AP MLD and can support the 802.11 series of protocols. For example, an AP MLD can be a communication server, router, switch, bridge, or other communication entity. Alternatively, an AP MLD can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, an AP MLD can also be the chip and processing system within these various types of devices, thereby implementing the methods and functions of the embodiments of this application. The 802.11 protocol can be a protocol that supports or is compatible with 802.11be.

[0154] Understandably, multi-link devices can support high-speed, low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can be applied to even more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-checkout machines, self-ordering machines, etc.). In this application embodiment, the specific forms of non-AP MLD and AP MLD are not limited; they are merely illustrative examples.

[0155] The above content briefly introduces the system structure of the embodiments of this application. The following is a brief introduction to the relevant content, terms or nouns involved in this application.

[0156] I. Multi-link setup

[0157] A non-AP MLD can establish associations with multiple links simultaneously on a single link by performing multi-link establishment operations. The link where association request / response frames are exchanged is called a transmitted link, and the other links are called non-transmitted links. For the association request / response frame, information about multiple links is carried through a multi-link element to enable simultaneous association of multiple links.

[0158] See Figure 4 , Figure 4 This is a schematic diagram illustrating the connection between an AP MLD and a non-AP MLD according to an embodiment of this application. Figure 4 As shown, both the non-AP MLD and AP MLD adopt a shared structure at the high MAC layer. It is assumed that the AP MLD includes two APs and the non-AP MLD includes two STAs. Combined with... Figure 4 The multi-link establishment process is as follows: The non-AP MLD sends an association request frame carrying a multi-link element on Link 1. Link 1 is the transmission link, and Link 2 is a non-transmission link. Upon receiving this association request frame, the AP MLD replies to the non-AP MLD on Link 1 with an association response frame carrying the multi-link element. The AP MLD can indicate the success or failure of each requested link in the association response frame. The association between the non-AP MLD and the AP MLD is successful only when the transmission link is accepted. For example,... Figure 4 As shown, transmission link 1 was accepted, the non-AP MLD was successfully associated with the AP MLD, and link 2 was successfully established. That is, AP1 and STA1 are connected through link 1, and AP2 and STA2 are connected through link 2.

[0159] To reduce signaling overhead, the multi-link element uses an inheritance model format to carry MLD-related information. See also Figure 5 , Figure 5 This is a schematic diagram of a frame format for a multi-link element provided in an embodiment of this application. For example... Figure 5 As shown, the information carried by a multi-link element can be divided into two parts: MLD-level information and per-link profile information. Here, "per-link" refers to each non-transmission link, such as... Figure 5 The Non-transmitted link2 profileinfo field. Information about a non-transmitted link will only be included in the Per link profileinfo if the content of an element on the STA (or AP) side corresponding to a non-transmitted link is different from the content of the same element on the STA (or AP) side corresponding to a transmitted link.

[0160] The MLD-level info field in the multi-link element carries information about the multi-link devices, such as the MAC addresses of the service access points (SAPs) of the non-AP MLD and AP MLD. Each link configuration information begins with a link ID to indicate which link the configuration information pertains to. The non-AP MLD can obtain the link ID information corresponding to each link, as well as the channel and basic service set identifier (BSSID) for each link by receiving probe response frames or beacon frames.

[0161] II. Stream Classification Service (SCS) Mechanism

[0162] On the station (STA) side, a low-latency service flow can be reported to the access point (AP) via the SCS mechanism. Specifically, the STA can send an SCS request frame to its associated AP to report a low-latency service flow and indicate the quality of service (QoS) parameters for that flow. Upon receiving the SCS request frame, the AP replies with an SCS response frame. This SCS response frame informs the STA whether the AP accepts the low-latency service flow reported by the STA. The frame structures of the SCS request frame and the SCS response frame are described below. In this application, the low-latency service flow is also referred to as an SCS flow.

[0163] See Figure 6 , Figure 6 This is a schematic diagram of the frame format of an SCS request frame provided in an embodiment of this application. For example... Figure 6 As shown, an SCS request frame includes a category field, a robust action field, a dialog token field, and an SCS descriptor list. The category field indicates the category to which the action frame belongs, the robust action field indicates which frame within that category, and the SCS descriptor list contains one or more SCS descriptors.

[0164] See Figure 7a , Figure 7a This is a schematic diagram of a frame format of the SCS descriptor provided in an embodiment of this application. For example... Figure 7a As shown, the SCS descriptor includes an element identifier field, a length field, an SCS identifier field, a request type field, an internal access category priority element (optional), a flow classification element (optional), a flow classification processing element (optional), and a flow specification element, etc. See also Figure 7b , Figure 7b This is a schematic diagram of another frame format of the SCS descriptor provided in an embodiment of this application. For example... Figure 7b As shown, the SCS descriptor includes an element identifier field, a length field, an SCS identifier field, a request type field, an internal access category priority element (optional), a flow classification element (optional), a flow allocation processing element (optional), and a QoS feature element, etc.

[0165] The SCS Identifier (SCSID) field, a 1-byte field, indicates the identifier assigned to the SCS flow. The 1-byte request type field indicates the type of request; for example, a request type of 0 indicates addition, 1 indicates removal, and 2 indicates change. The Flow Classification Element (TCLASelement) indicates how to identify the SCS flow, carrying the criteria for determining its identity. The Flow Classification Processing Element (TCLAS Processing element) indicates how to process multiple flow classification elements. The Flow Specification Element (TSPEC element) or QoS Characteristic Element indicates the TID mapped to the corresponding SCS flow and the corresponding QoS parameters. The two most important QoS parameters are: delay bound, indicating the maximum allowed delay for low-latency packets; and packet delivery ratio, indicating the required packet delivery ratio under a given delay bound requirement.

[0166] See Figure 8 , Figure 8 This is a schematic diagram of the frame format of an internal access category priority element provided in an embodiment of this application. For example... Figure 8 As shown, the intra-access category priority element includes an element identifier field, a length field, and a 1-byte intra-access priority field. This intra-access priority field includes a 3-bit (bit0-bit2) user priority subfield, a 1-bit (bit3) alternate queue subfield, and a 1-bit (bit4) dropeligibility subfield. The user priority subfield indicates the user's priority, the alternate queue subfield indicates whether a new alternate queue should be created for this SCS flow, and the dropeligibility subfield indicates whether packets in this SCS flow can be dropped when there are insufficient resources.

[0167] See Figure 9 , Figure 9 This is a schematic diagram of the frame format of an SCS response frame provided in an embodiment of this application. For example... Figure 9As shown, the SCS response frame includes a category field, a robust action field, a dialog token field, an SCS status list, and an SCS descriptor list. The category field indicates the category to which the action frame belongs, and the robust action field indicates which frame within that category. The dialog token field in the SCS response frame must match the dialog token field in the corresponding SCS request frame. The SCS status list contains one or more SCS status groups, each indicated by two subfields: a SCSID subfield, indicating the identifier of the SCS flow; and a Status Code subfield, indicating whether the requested SCSID was accepted. The SCS descriptor list contains one or more SCS descriptors.

[0168] III. Traffic Identifier (TID) and Access Category (AC)

[0169] The traffic identifier (TID) is 4 bits long and is used to indicate the priority of the service. Under enhanced distribution channel access (EDCA), the TID value ranges from 0 to 7, with 8-15 being reserved values.

[0170] The 802.11 protocol defines four access categories (ACs), each with different parameters such as the arbitration inter-frame spacing number (AIFSN) and contention window size, which determine the priority during channel access. Table 2 below shows the contention window size and arbitration inter-frame spacing parameters for each access category.

[0171] Table 2

[0172]

[0173]

[0174] IV. TID-to-link Mapping

[0175] If a non-AP MLD wants to negotiate TID-to-link mapping with its associated AP MLD, it can send a TID-to-link Mapping request frame. Upon receiving the TID-to-link Mapping request frame, the AP MLD can reply with a TID-to-link Mapping response frame. The information contained in the TID-to-link Mapping request frame is shown in Table 3 below. The information contained in the TID-to-link Mapping response frame is shown in Table 4 below. Furthermore, 802.11be also supports negotiating TID-to-link mapping during the association process by including a TID-to-link Mapping element in the (Re)Association Request / Response frame.

[0176] Table 3: Frame format of TID-to-link Mapping request frames

[0177] order information 1 Category 2 EHT Action 3 Dialog Token 4 TID-to-link Mapping element / TID to link mapping element

[0178] Table 4: Frame format of TID-to-link Mapping response frames

[0179] order information 1 Category 2 EHT Action 3 Dialog Token 4 Status Code 5 TID-to-link Mapping element / TID to link mapping element

[0180] See Figure 10 , Figure 10 This is a schematic diagram of the frame format of a TID-to-link Mapping element provided in an embodiment of this application. For example... Figure 10As shown, the TID-to-link Mapping element includes an element identifier field, a length field, an extended element identifier field, and a TID-to-link Mapping control field. The TID-to-link Mapping control field includes a direction subfield, a default link mapping bit, and a link mapping presence indicator subfield. Specifically, a direction subfield set to 0 indicates uplink; 1 indicates downlink; 2 indicates both uplink and downlink; and 3 is a reserved value. The default link mapping bit indicates whether all TIDs are mapped to all links; when the default link mapping bit is set to 1, all TIDs are mapped to all links. For example, assuming there are three links between a non-AP MLD and an AP MLD: link1, link2, and link3; when the default link mapping bit is set to 1, TIDs 0-7 are mapped to link1, TIDs 0-7 to link2, and TIDs 0-7 to link3. The Link Mapping Occurrence Indicator field indicates whether a Link Mapping of TID#n (where n is 0-7) has occurred for each TID. When the default Link Mapping bit is set to 1, the Link Mapping Occurrence Indicator field is reserved or unused. When a Link Mapping of TID#n exists in the TID-to-link Mapping element, it indicates whether TID#n is mapped to the corresponding link. When the corresponding bit is set to 1, it indicates that TID#n is mapped to the corresponding Link.

[0181] V. Quality of Service (QoS) Map Element

[0182] QoS mapping elements can be carried in association response frames or reassociation response frames. See also Figure 11 , Figure 11 This is a schematic diagram of the frame format of a QoS mapping element provided in an embodiment of this application. For example... Figure 11As shown, the QoS mapping element includes an element identifier, a length field, a differentiated services code point (DSCP) exception list field, and a DSCP range field corresponding to user priority #n (n is 0-7). The DSCP exception list field can carry one or more DSCP exception fields. Each DSCP exception field contains the following subfields: DSCP value, which ranges from 0 to 63 or 0 to 255; and user priority, which ranges from 0 to 7. Each user priority has a corresponding DSCP range field, and the DSCP ranges for each user priority do not overlap. The DSCP range field corresponding to user priority #n (n is 0-7) includes the following subfields: DSCP low value and DSCP high value, where the DSCP high value is greater than or equal to the DSCP low value. When both the DSCP low value and DSCP high value are 255, it indicates that the priority is not used.

[0183] VI. Reduced Neighbor Report Element (RNR element)

[0184] APs can carry a simplified Neighbor Reporting Element (RNRelement) in management frames, such as beacon frames and probe response frames. During scanning, STAs receive beacon frames or probe response frames sent by APs to obtain information about surrounding APs, and then select appropriate APs to associate with.

[0185] See Figure 12 , Figure 12 This is a schematic diagram of a frame format for an RNR element provided in an embodiment of this application. For example... Figure 12As shown, the RNR element includes an element identifier field, a length field, and one or more neighbor AP information fields. Each neighbor AP information field includes: a target beacon transmission time (TBTT) info header field, an operating class field, a channel number field, and a TBTT info set field. The operating class field indicates the operating class of the reporting AP's operating channel; values ​​0 and 255, and other values, are reserved. The channel number field indicates the channel number corresponding to the reporting AP's operating channel. Channel number 0 is a reserved value. The STA side can determine the specific location of the AP's channel in the frequency band using the operating class field and the channel number field.

[0186] The TBTT header fields include the TBTT info field type field, the filtered neighbor AP field, reserved bits, the TBTT info count field, and the TBTT info length field. The TBTT info field type indicates the type of TBTT information and, together with the TBTT info length field, indicates the format of the TBTT info field; values ​​1, 2, and 3 are reserved. The filtered neighbor AP field indicates whether the service set IDs (SSIDs) of all BSSs carried in the neighbor AP's info field match the SSIDs in the probe request frame. The TBTT info count field indicates the number of TBTT info fields in the TBTT info set. The TBTT info length field indicates the length of each TBTT info field. The specific information formats carried under different lengths are shown in Table 5 below.

[0187] Table 5

[0188]

[0189] The TBTT information set field includes one or more TBTT information fields. The specific format of the TBTT information fields can be found in the descriptions in existing standards, which will not be repeated here.

[0190] VII. Basic Service Set (BSS) Transfer Management Action Frame

[0191] For a STA already associated with an AP, when the STA detects poor link quality or other issues, it can send a BSS transition management (BTM) query frame to the associated AP. The specific frame format of this BTM query frame is described in existing standards and will not be repeated here. See also... Figure 13 , Figure 13 This is a schematic diagram of a BSS transfer management operation process provided in an embodiment of this application. Figure 13 As shown, when an AP wants a STA to perform a BSS transition, it can send a BSS transition management request frame to the STA. The STA can then send back a BSS transition management response frame to indicate whether to accept or reject the BSS transition request.

[0192] 8. Transmission Opportunity (TXOP) Sharing (TXS)

[0193] Because Wi-Fi (or 802.11) systems are deployed on unlicensed spectrum, stations (in a broad sense, i.e., access points and stations) need to compete for channel resources. In the commonly used EDCA contention mechanism, after a station completes channel backoff, it sends its first frame (e.g., a request-to-send (RTS) frame). If the first frame receives a response frame, the channel contention is successful; otherwise, it needs to backoff again. If the first frame (e.g., a CTS-to-self frame) does not require a response frame, then sending the first frame signifies successful channel contention. After successful channel contention, the station can reserve a period of time for data transmission; this period is called a TXOP (Turn-Only Opportunity Period). The station that successfully reserves a TXOP is called the TXOP holder. Within this TXOP, only the TXOP holder can actively send data; other stations can only receive data or send corresponding response frames.

[0194] The 802.11be standard extends the TXOP mechanism, allowing an AP acting as a TXOP holder to allocate a portion of its TXOP time resources to a first site. During the allocated time, the first site can then engage in peer-to-peer (P2P) transmissions with a second site or send uplink data to the AP. This mechanism is called TXOP sharing. See also... Figure 14 , Figure 14This is a schematic diagram of a TXOP sharing method provided in an embodiment of this application. For example... Figure 14 As shown, after the AP sends a CTS-to-self message, it obtains a TXOP and can allocate the first-time resources within the TXOP to STA1. STA1 then performs P2P transmission with STA2 during the allocated time. This mechanism can reduce the number of first-site (e.g., Figure 14 This improves system efficiency by mitigating collisions caused by STA1 contention for the channel. The P2P link used in this P2P transmission is established between two non-AP STAs via tunneled direct link setup (TDLS) or other P2P protocols. In some scenarios, P2P can also be referred to as device-to-device (D2D) or TDLS, but their essence is the same.

[0195] To better support low-latency service transmission, an enhanced link subset mapping (TID) scheme has been proposed, but some problems remain unresolved. These include: 1. How to establish a clean link that only allows TID mappings corresponding to low-latency services, ensuring that low-latency services on this link are not interfered with by non-low-latency services. 2. How to indicate the TIDs that can only be used by low-latency services, thus distinguishing between low-latency and non-low-latency services through the TIDs.

[0196] Therefore, this application provides a multi-link communication method that prevents unassociated non-AP MLDs from initiating multi-link establishment on a clean link, thus preventing situations where a non-AP MLD and an AP MLD only successfully establish a clean link. This ensures that low-latency services on the clean link are not interfered with by non-low-latency services. Furthermore, the multi-link communication method provided in this application can also divide the TID space (0 to 7) into two parts: one part for non-low-latency services and the other for low-latency services. This is communicated to the STA via a QoS mapping element, allowing for differentiation between low-latency and non-low-latency services during subsequent data transmission.

[0197] The technical solutions provided in this application are illustrated through multiple embodiments. Embodiment 1 describes defining a new access control mode using supported rates and BSS membership selector elements. This mode only allows non-AP MLDs to establish the current link (i.e., a clean link) by initiating a Multi-link Setup on other links. Embodiment 2 describes how an AP MLD operates when it wants to establish a link as a clean link at a certain time after association. Embodiment 3 describes how an AP or AP MLD maps DSCP0-63 to a subset of TIDs (0-7) using QoS mapping elements; the remaining TIDs can only be used by low-latency services. Embodiment 4 describes how non-AP MLDs negotiate TID-to-link mapping using the SCS mechanism. Embodiment 5 describes indicating the access policy of service flows in QoS feature elements.

[0198] In this application, unless otherwise specified, the same or similar parts between various embodiments or implementations can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The embodiments described below do not constitute a limitation on the scope of protection of this application.

[0199] This application refers to "a link that only allows low-latency service transmission" or "a link that only allows TID mappings corresponding to low-latency services" as a "clean link." Of course, it may have other names, and this application does not impose any restrictions.

[0200] In this application, "user priority" and "TID" are not distinguished; they have a one-to-one correspondence and can be used interchangeably. Specifically, user priority 0 corresponds to TID 0, user priority 1 corresponds to TID 1, user priority 2 corresponds to TID 2, user priority 3 corresponds to TID 3, user priority 4 corresponds to TID 4, user priority 5 corresponds to TID 5, user priority 6 corresponds to TID 6, and user priority 7 corresponds to TID 7.

[0201] The number of bytes in each frame mentioned in this application, and the number of bits or bytes in each field in each frame, can be found in the descriptions of existing standards, and will not be repeated here.

[0202] The various embodiments will be described in detail below.

[0203] Example 1

[0204] See Figure 15 , Figure 15 This is a schematic flowchart of the first embodiment of the multi-link communication method provided in this application. This multi-link communication method is mainly applied during or before the establishment of a multi-link connection. Figure 15 As shown, this multi-link communication method includes, but is not limited to, the following steps:

[0205] S101, the AP MLD generates a first frame, which includes a supported rates and BSS membership selector element. The supported rates and BSS membership selector element includes first indication information, which is used to instruct the non-AP MLD to prohibit the initiation of multi-link establishment with the AP MLD on the first link.

[0206] S102, AP MLD sends the first frame on the first link.

[0207] S103, non-AP MLD receives the first frame on the first link.

[0208] S104, non-AP MLD parses this first frame.

[0209] Optionally, in this embodiment, the AP MLD has at least two links, including a first link and a second link. The first link is either a link that only allows low-latency service transmission or a link that only allows the TID mapping corresponding to the low-latency service; that is, the first link is a clean link. In this embodiment, the clean link can be one link or multiple links; this embodiment does not impose any restrictions.

[0210] Optionally, in this embodiment, the first frame refers to a frame transmitted on the first link. The first frame can be any of the following: a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. The first frame may carry a supported rates and BSS membership selector element. This element carries the conditions (such as the rate or BSS membership selector) required to join the BSS (here referring to the BSS formed by APs operating on the first link in the AP MLD). In other words, an STA is allowed to join the BSS only when it meets the conditions indicated by the supported rates and BSS membership selector element. The element includes first indication information, which can be used to instruct the non-AP MLD to prohibit initiating multi-link setup with the AP MLD on the first link. For ease of description, this application refers to the prohibition of non-AP MLD from initiating multi-link establishment with AP MLD on a certain link (or clean link) as restricted multi-link setup.

[0211] Optionally, the first indication information may be the supported rate and the BSS Membership selector in the BSS Membership selector element set to a preset value, such as 120 or 121, or other unused values. That is, in this embodiment, the supported rate and the BSS Membership selector in the BSS Membership selector element are set to preset values ​​(such as 120 or 121, or other unused values) to instruct the non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link. In other words, setting the BSS Membership selector to a preset value indicates that the non-AP MLD can only perform limited multi-link establishment, meaning that the non-AP MLD can only establish the link (i.e., the clean link) by initiating multi-link establishment through other links (i.e., links other than the clean link).

[0212] See Figure 16 , Figure 16This is a schematic diagram of the frame format of the supported rate and BSS membership selector elements provided in this application embodiment. The Supported Rates and BSS Membership Selectors element can specify any combination of up to eight BSS membership selectors and rates. Figure 16 As shown, the Supported Rates and BSS Membership Selector elements include an element identifier field, a length field, and a Supported Rates field. Each byte of the Supported Rates field describes either the supported rate or the BSS membership selector for a single BSS member. Because the BSS membership selector and supported rates are carried in the same field, the value of the BSS membership selector cannot be the same as the value corresponding to any valid supported rate. That is, a value either represents a supported rate or a BSS membership selector.

[0213] When beacon frames, probe response frames, and (Re)association response frames carry the SupportedRates and BSS Membership Selectors elements, each rate in the BSS basic rate set parameters is encoded as follows: the highest bit (bit 7) of each byte is set to 1, and the remaining 7 bits are set in units of 500 Kb / s. For each rate in the operational rate set parameters, the following rules apply: the highest bit (bit 7) of each byte is set to 0, and the remaining 7 bits are set in units of 500 Kb / s.

[0214] When the beacon frame, probe response frame, and (Re)association response frame carry the SupportedRates and BSS Membership Selectors elements, each BSS membership selector in the BSS membership selector set parameter is encoded according to the following rules: the highest bit (bit 7) of each byte is set to 1, and the remaining 7 bits are set according to Table 6 below.

[0215] Table 6: Valid Values ​​of the BSS Membership Selector

[0216]

[0217] As shown in Table 6, when the BSS Membership selector is set to 127, it means that a site wanting to join the BSS must support High Throughput Physical Layer (HT PHY). When the BSS Membership selector is set to 126, it means that a site wanting to join the BSS must support Very High Throughput Physical Layer (VHT PHY). When the BSS Membership selector is set to 125, it means that a site wanting to join the BSS must support GLK features. When the BSS Membership selector is set to 124, it means that a site wanting to join the BSS must support EPD. When the BSS Membership selector is set to 123, it means that a site wanting to join the BSS must support SAE (Site-Agent Execution Environment). When the BSS Membership selector is set to 122, it means that a site wanting to join the BSS must support High Efficiency Physical Layer (HE PHY). When the BSS Membership selector is set to 121, it means that a site wanting to join the BSS must support EHT PHY. When the BSS Membership selector is set to 120, it means that non-AP MLDs wishing to join BSS can only initiate multi-link establishment through other links (excluding clean links). Alternatively, setting the BSS Membership selector to 120 could mean that sites wishing to join BSS must support EHT PHY. When the BSS Membership selector is set to 121, it means that non-AP MLDs wishing to join BSS can only initiate multi-link establishment through other links (excluding clean links). Alternatively, setting the BSS Membership selector to other unused values ​​could mean that non-AP MLDs wishing to join BSS can only initiate multi-link establishment through other links, or that sites wishing to join BSS must support EHT PHY.

[0218] Optionally, because the Supported Rates and BSS Membership Selectors element can specify up to eight BSS membership selectors, it can include multiple BSS Membership selectors simultaneously, and these multiple BSS Membership selectors can be set to different values. For example, if the Supported Rates and BSS Membership Selectors element includes two BSS Membership selectors, one BSS Membership selector set to 127 indicates that a site wanting to join the BSS must support HT PHY; the other BSS Membership selector set to 125 indicates that a site wanting to join the BSS must support GLK features. In other words, a site joining this BSS needs to support both HT PHY and GLK features.

[0219] Understandably, the new generation of standards are compatible with the previous standards. That is to say, a site that supports the VHT protocol also supports protocols that existed before VHT, such as the HT protocol; a site that supports the HE protocol also supports both VHT and HT protocols; and a site that supports the EHT protocol also supports HT, VHT, HE protocols, etc.

[0220] It should be understood that when the BSS Membership selector is set to a default value (such as 120 or 121, or other unused values), because legacy STAs cannot understand this default value, they will assume they do not meet the conditions for joining this BSS (referring to the BSS formed by APs operating on the first / clean link in the AP MLD). Therefore, legacy STAs will not associate with APs operating on the first / clean link in the AP MLD. In other words, legacy STAs cannot associate on the first / clean link.

[0221] In this application, legacy STA refers to a site that only supports protocols prior to 802.11be, such as an HE site that supports 802.11ax, a VHT site that supports 802.11ac, or an HT site that supports 802.11n.

[0222] Similar to legacy STAs, when the BSS Membership selector is set to a default value (such as 120 or 121, or other unused values), if a single-link site that supports extremely high throughput protocols (referred to as a single-link EHT STA) cannot understand this default value, then the single-link EHT STA will also be unable to associate on the first link / clean link.

[0223] Optionally, if a single-link EHT STA can understand this preset value, the aforementioned first indication information is also used to instruct the single-link EHT STA to prohibit establishing an association with the AP MLD on the first link / clean link. That is, if a single-link EHT STA can understand the preset value set in this application, when the BSS Membership selector in the Supported Rates and BSSMembership Selectors element is set to this preset value, it not only instructs the non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link (or clean link), but also instructs the single-link EHT STA to prohibit establishing an association with the AP MLD on the first link (or clean link).

[0224] Optionally, when the first frame is a beacon frame, (even if the non-AP MLD sends a probe request frame and / or association request frame on the first link) the AP MLD prohibits replying with (corresponding) probe response frames and / or association response frames on the first link. That is, when the first frame is a beacon frame, the AP MLD does not reply with probe response frames and association response frames on the clean link. When the first frame is a probe response frame, the AP MLD prohibits replying with association response frames on the first link. That is, when the first frame is a probe response frame, (even if the non-AP MLD sends an association request frame on the first link) the AP MLD does not reply with association response frames on the clean link. When the first frame is any of a beacon frame, probe response frame, association response frame, or reassociation response frame, the AP MLD can reject the association (sent on the first link) by using the status code field in the association response frame or reassociation response frame.

[0225] Optionally, since the AP MLD can send beacon frames or probe response frames on each of its own links, the above multi-link communication method further includes: the AP MLD sending a beacon frame or probe response frame on a second link, and correspondingly, the non-AP MLD receiving the beacon frame or probe response frame on the second link. The beacon frame or probe response frame includes an RNR element, the frame format of which can be found in the foregoing. Figure 12 As shown, details are omitted here. This RNR element includes a neighbor AP information field corresponding to the first access point, where the channel number field is set to 0. This first access point is the access point operating on the first link in the AP MLD.

[0226] Because 802.11be stipulates that affiliated APs of an AP MLD must carry the corresponding information of other affiliated APs under the same AP MLD through the RNR element. Since the first access point itself does not allow legacy STAs to associate, this embodiment sets the channel number field corresponding to the first access point in the RNR element to 0. This prevents legacy STAs from discovering the first access point through the RNR element and thus prevents them from switching to the corresponding channel to attempt association. Essentially, the first access point is invisible to legacy STAs in the RNR element.

[0227] It should be understood that if the first frame is a beacon frame, the AP MLD can send a beacon frame on the second link simultaneously with the execution of step S102; or the AP MLD can send a beacon frame on the second link before the execution of step S102; or the AP MLD can send a beacon frame or a probe response frame on the second link after the execution of step S102. If the first frame is a probe response frame, the AP MLD can send a probe response frame on the second link simultaneously with the execution of step S102; or the AP MLD can send a beacon frame or a probe response frame on the second link before the execution of step S102; or the AP MLD can send a probe response frame on the second link after the execution of step S102. If the first frame is an association response frame or a reassociation response frame, the AP MLD can send a beacon frame or a probe response frame on the second link before the execution of step S102.

[0228] To better understand the multi-link communication method of this application embodiment, two examples are provided below.

[0229] Example 1: See Figure 17a , Figure 17aThis is a schematic diagram of a clean link in the AP MLD provided in this application embodiment. For example... Figure 17a As shown, the AP MLD has three links: link 1, link 2, and link 3. Assume the AP MLD wants to set link 3 as a clean link, while allowing legacy STAs to associate with link 1 and link 2.

[0230] Therefore, for the beacon frame / probe response frame to be transmitted on link 1, the AP MLD sets the BSS Membership selector in its Supported Ratesand BSS Membership Selector element to 127, sets the channel number field for AP2 in the RNR element to the actual value, and sets the channel number field for AP3 in the RNR element to 0. It should be understood that the actual value here refers to the actual channel number of the corresponding AP.

[0231] For the beacon frame / probe response frame to be sent on link 2, AP MLD sets the BSS Membership selector in its Supported Rates and BSS Membership Selector element to 127, sets the channel number field of AP1 in the RNR element to the real value, and sets the channel number field of AP3 in the RNR element to 0.

[0232] For the beacon frame / probe response frame to be sent on link 3, AP MLD sets the BSS Membership selector in its Supported Rates and BSS Membership Selector element to 120, sets the channel number field of AP1 in the RNR element to the real value, and also sets the channel number field of AP2 in the RNR element to the real value.

[0233] When a site on link 3 is a legacy STA, if the legacy STA reads an unfamiliar value (such as 120) for the BSS Membership selector, it will not attempt to initiate an association. When a site on link 3 belongs to a non-AP MLD, if the non-AP MLD reads a value of 120 for the BSS Membership selector, it will jump to other links of that AP MLD (such as link 1 and link 3) to attempt to initiate an association.

[0234] Example 2: See Figure 17b , Figure 17b This is another schematic diagram of the clean link in the AP MLD provided in the embodiments of this application. For example... Figure 17b As shown, the AP MLD has three links: link 1, link 2, and link 3. Assume the AP MLD wants to set link 1 and link 3 as clean links, while allowing legacy STAs to associate with link 2.

[0235] Therefore, for the beacon frame / probe response frame to be sent on link 1, AP MLD sets the BSS Membership selector in its Supported Ratesand BSS Membership Selector element to 120, sets the channel number field of AP2 in the RNR element to the real value, and sets the channel number field of AP3 in the RNR element to 0.

[0236] For the beacon frame / probe response frame to be sent on link 2, AP MLD sets the BSS Membership selector in its Supported Rates and BSS Membership Selector element to 127, sets the channel number field of AP1 in the RNR element to 0, and also sets the channel number field of AP3 in the RNR element to 0.

[0237] For the beacon frame / probe response frame to be sent on link 3, AP MLD sets the BSS Membership selector in its Supported Rates and BSS Membership Selector element to 120, sets the channel number field of AP1 in the RNR element to 0, and sets the channel number field of AP2 in the RNR element to the actual value.

[0238] When a site on link 1 and / or link 3 is a legacy STA, and the legacy STA reads an unfamiliar value (such as 120) for the BSS Membership selector, the legacy STA will not attempt to initiate an association. When a site on link 1 and / or link 3 belongs to a non-AP MLD, and the non-AP MLD reads a value of 120 for the BSS Membership selector, the non-AP MLD will redirect to another link of that AP MLD (such as link 2) to attempt to initiate an association.

[0239] It should be understood that if a non-AP MLD initiates multi-link establishment via a clean link, it's possible that the non-AP MLD will only successfully establish this one link (i.e., the clean link). In this case, the non-AP MLD might carry both low-latency and non-low-latency services on this link, making it impossible for the link to transmit only low-latency services. Furthermore, if the non-AP MLD initiates multi-link establishment via a clean link, it will also consume the clean link's channel resources, potentially interfering with the low-latency services currently being transmitted on the clean link.

[0240] Therefore, this embodiment of the application carries indication information in the Supported Rates and BSS Membership Selector elements to indicate that non-AP MLDs are not allowed to initiate multi-link establishment on the clean link, and non-AP MLDs must establish the link through other links of AP MLDs; and for single-link EHT STAs, it also restricts them from establishing association with affiliated APs on the clean link; and for legacy STAs, since they cannot recognize this indication information, they cannot establish association with affiliated APs on the clean link; thus, low-latency services on the clean link are not interfered with by non-low-latency services.

[0241] In addition, the AP MLD in this application embodiment can comprehensively consider the QoS requirements of low-latency services, as well as the number of legacy STAs and single-link EHT STAs, thereby flexibly and dynamically controlling the number of clean links and TID-to-link mapping; and because there are no legacy STAs and single-link EHT STEs, the AP MLD's operations related to clean links are relatively simple and flexible.

[0242] Example 2

[0243] See Figure 18 , Figure 18 This is a second schematic flowchart of a multi-link communication method provided in this application embodiment. This multi-link communication method is mainly applied after the multi-link establishment or association process. Figure 18 As shown, this multi-link communication method includes, but is not limited to, the following steps:

[0244] S201, the AP MLD sends a beacon frame on the first link. The beacon frame includes a supported rate and BSS membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct the first non-AP MLD to prohibit the initiation of multilink establishment with the AP MLD on the first link.

[0245] Optionally, in this embodiment, the AP MLD has at least two links, including a first link and a second link. During the association process, both the first and second links of the AP MLD allow legacy STAs (traditional sites) and single-link EHT STAs to associate, and also allow non-AP MLDs to initiate multi-link establishment on the first and second links. However, after successful association, the AP MLD may at some point want to designate the first link as a link that only allows low-latency service transmission or a link that only allows the TID mapping corresponding to low-latency services.

[0246] In this scenario, the AP MLD can send a beacon frame on the first link, which may carry a Supported Rates and BSS Membership Selectors element. This Supported Rates and BSS Membership Selectors element includes first indication information, which can be used to instruct non-AP MLDs not yet associated with the AP MLD (denoted as the first non-AP MLD) to prohibit initiating multi-link setup with the AP MLD on the first link. Optionally, the AP MLD may also prohibit replying with probe response frames and / or association response frames on the first link. The implementation of the first indication information can be found in the corresponding description in Embodiment 1 above, and will not be repeated here. The frame format of the Supported Rates and BSS Membership Selectors element is as described above. Figure 16 As shown, it will not be elaborated further here.

[0247] Optionally, the multi-link communication method further includes: the AP MLD can also send beacon frames or probe response frames on the second link, wherein the beacon frame or probe response frame includes an RNR element, and the frame format of the RNR element is described above. Figure 12 As shown, details are omitted here. This RNR element includes a neighbor AP information field corresponding to the first access point, where the channel number field is set to 0. This first access point is the access point operating on the first link in the AP MLD.

[0248] S202, the first station receives the beacon frame on the first link.

[0249] Optionally, in this embodiment, the first station is a legacy STA, meaning that the first station only supports protocols prior to the extremely high throughput (or 802.11be) protocol. Because the first station does not recognize / understand the first indication information in the beacon frame, it will not attempt to initiate association on the first link.

[0250] S203, the AP MLD broadcasts a BSS transfer management request frame on the first link. The BSS transfer management request frame includes second indication information, which is used to instruct the second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame. The BSS transfer request frame is used to request the first site associated with the first access point to perform a BSS transfer.

[0251] S204, The first station receives a BSS transfer management request frame on the first link.

[0252] Optionally, after sending a beacon frame on the first link, the AP MLD can broadcast a BSS transition management request (BTM Request) frame on the first link. This broadcast BTM Request frame may include second indication information, which instructs the second non-APMLD associated with the AP MLD to ignore the BTM Request frame. Because the first station (a legacy STA) does not recognize or understand the second indication information in the BTM Request frame, this BTM Request frame can be used to request the first station associated with the first access point to perform a BSS transfer. This first access point can be an access point operating on the first link within the AP MLD. Therefore, after receiving the BTM Request frame, the first station can perform a BSS transfer according to the instructions in the BTM Request frame.

[0253] Optionally, the aforementioned second indication information can be located in the reserved bits of the request mode field of the BTM Request frame. For example, a reserved bit in the request mode field can be used as an ignore bit to instruct the second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame.

[0254] See Figure 19a , Figure 19a This is a schematic diagram of the frame format of the BTM Request frame provided in an embodiment of this application. For example... Figure 19aAs shown, the BTM Request frame includes a category field, a radio network management operation field, a session token field, a request mode field, a deassociation timer field, a validity period field, a BSS termination duration field, a session information uniform resource locator (URL) field, and a BSS transfer candidate list (optional) field. The request mode field indicates the specific request mode and includes: whether to carry a preferred candidate list field, a bridging field, a deassociation imminent field, a BSS termination field, an extended service set (ESS) deassociation imminent field, an ignore bit (i.e., the second indication information mentioned above), and a reserved bit. The "whether to carry a preferred candidate list" field indicates whether to carry the preferred candidate list information. The "abridged" field sets the abridged indicator to 0 if the associated AP does not recommend or prohibits the STA from switching to a BSS not appearing in the preferred candidate list; it sets it to 1 if the associated AP sets the preference value of a BSS not appearing in the preferred candidate list to 0. When the "disassociation imminent" field is set to 1, it indicates that the AP will send a disassociation frame to perform disassociation. The "BSS termination included" field indicates whether the BSS will be shut down. The "ESS disassociation imminent" field indicates whether the STA will be disassociated by the entire ESS.

[0255] The ignore bit indicates whether the non-AP MLD that receives the BTM Request frame should ignore it. For example, when the ignore bit is set to 1 (i.e., the second indication information mentioned above), it means the non-AP MLD associated with the AP MLD ignores the BTM Request frame; when the ignore bit is set to 0, it means the non-AP MLD associated with the AP MLD cannot ignore the BTM Request frame. Alternatively, the ignore bit can be set to 0 (i.e., the second indication information mentioned above), indicating that the non-AP MLD associated with the AP MLD ignores the BTM Request frame; and the ignore bit can be set to 1, indicating that the non-AP MLD associated with the AP MLD cannot ignore the BTM Request frame.

[0256] See Figure 19b , Figure 19b This is a schematic diagram of the frame format of the BTM Response frame provided in an embodiment of this application. For example... Figure 19b As shown, the BTM Request frame includes: a category field, a radio network management operation field, a session token field, a BTM status code field, a BSS termination delay field, a target BSSID field (optional), and a BSS transfer candidate list field (optional). The BTM status code field indicates whether the BSS transfer request has been accepted. The BSS termination delay field indicates how long after the BSS will terminate.

[0257] To better understand the multi-link communication method of this application embodiment, an example is given below.

[0258] For example, suppose the AP MLD has three links: link 1, link 2, and link 3. During the association process, all three links allow legacy STAs to associate. However, at some point, the AP MLD wants to establish link 3 as a clean link and transfer the legacy STAs associated with link 3 to other links, allowing only low-latency services from non-AP MLDs to use link 3. The AP MLD sends a beacon frame on link 3. This beacon frame includes a BSS MembershipSelector with a value of 120 in the SupportedRates and BSS Membership Selectors element, instructing unassociated non-AP MLDs to initiate multi-link establishment through other links (i.e., link 1 and link 2). The AP MLD also sends a broadcast BSS Transition Management Request frame with the Ignore bit set to 1. Upon receiving this broadcast BSS Transition Management Request frame, legacy STAs on link 3 need to perform a BSS transfer; the associated non-AP MLDs will ignore the frame.

[0259] In this embodiment of the application, after successful association, when the AP MLD wants to designate a link as a cleanlink at a certain time, it sends a beacon frame carrying Supported Rates and BSS Membership Selectors elements on this link, and the BSS MembershipSelector in the Supported Rates and BSS Membership Selectors elements is set to 120; in addition, it also sends a BTM Request frame on this link, using the reserved bits in the BTM Request frame to add an indication, instructing the associated non-AP MLD to ignore the frame, and the associated Legacy STA to perform BSS transfer; thus, the low-latency services on this link are not interfered with by non-low-latency services.

[0260] Furthermore, the AP MLD does not need to create a separate multicast group for legacy STAs to send a multicast BSSTransition Management Request frame to enable all legacy STAs to perform BSS handover. In other words, the AP MLD does not need to exchange unicast BSS Transition Management Request / Response frames with each legacy STA individually to enable all legacy STAs to perform BSS handover. This saves signaling overhead and results in high BSS handover efficiency.

[0261] Example 3

[0262] Embodiment 3 of this application can be implemented alone or together with Embodiment 1 or Embodiment 2 described above; this application makes no limitation on this. When Embodiment 3 of this application is implemented together with Embodiment 1 described above, the first frame in Embodiment 1 is an associated response frame or a re-associated response frame. When Embodiment 3 of this application is implemented together with Embodiment 2 described above, Embodiment 3 can be implemented after step S201 of Embodiment 2 described above, and the second device in Embodiment 3 of this application is the first non-AP MLD in Embodiment 2 described above.

[0263] Optionally, this application embodiment is mainly applied to the enhanced link subset mapping scenario. In this scenario, because clean links can only be used to transmit low-latency services, and how to indicate the TIDs that low-latency services can use has not yet been resolved. Therefore, this application embodiment three divides the TID space (0 to 7) into two parts through QoS mapping elements: one part is used for non-low-latency services, and the other part is used for low-latency services, so as to distinguish between low-latency and non-low-latency services through TIDs. The embodiments of this application are described in detail below.

[0264] See Figure 20 , Figure 20 This is a third schematic flowchart of the multi-link communication method provided in this application embodiment. This multi-link communication method is mainly applied in the multi-link establishment or association process. Figure 20 As shown, this multi-link communication method includes, but is not limited to, the following steps:

[0265] S301, the first device generates an associated response frame or a reassociated response frame, which includes a QoS mapping element. The QoS mapping element includes DSCP range fields corresponding to 8 different user priorities. The DSCP range indicated by the DSCP range fields corresponding to m of the 8 different user priorities covers the DSCP space. The DSCP low value field and DSCP high value field in the DSCP range fields corresponding to the other (8-m) of the 8 different user priorities are both set to 255.

[0266] S302, the first device sends the association response frame or reassociation response frame.

[0267] S303, the second device receives the association response frame or reassociation response frame.

[0268] S304, the second device parses the associated response frame or reassociated response frame.

[0269] Optionally, in the embodiments of this application, the first device is an AP or AP MLD, and the second device is an EHT STA or non-APMLD.

[0270] In this application embodiment, user priority and TID are not distinguished, but they are in a one-to-one correspondence and can be used interchangeably.

[0271] Optionally, the aforementioned associated response frame or the aforementioned reassociated response frame includes a QoS mapping element, the frame format of which can be referred to the foregoing. Figure 11 As shown, details are omitted here. This QoS Map element can be used to tell the second device supporting low-latency services how to perform DSCP to TID / user priority mapping. This QoS Map element includes DSCP range fields corresponding to 8 different user priorities (0-7). The DSCP ranges indicated by the DSCP range fields corresponding to m of these 8 different user priorities cover the DSCP space, which is the interval [0, 63]. That is, the union of the DSCP ranges indicated by the DSCP range fields corresponding to these m user priorities includes the interval [0, 63]. m is a positive integer less than 8.

[0272] The DSCP low value field and DSCP high value field for the other (8-m) user priorities among the 8 different user priorities are both set to 255. As mentioned in the previous introduction to QoS mapping elements, when both the DSCP low value field and DSCP high value field are set to 255, it indicates that the corresponding user priority is unused; that is, this part of the TID (i.e., the TIDs corresponding to the (8-m) user priorities) is reserved for low-latency services.

[0273] In other words, the first device maps the DSCP space to a subset of the TID space using QoS Map elements. The TIDs in this subset are used for non-low-latency services. Meanwhile, the remaining TIDs in the TID space are used for low-latency services reported by STAs or non-AP MLDs via the SCS mechanism, or in other words, to identify SCS flows added via SCS request frames. In one example, the DSCP Range field corresponding to TIDs 0, 2, 4, and 6 indicates a DSCP range covering the entire DSCP space (0 to 63), meaning TIDs 0, 2, 4, and 6 are used for non-low-latency services; and the DSCP Low Value and DSCP High Value fields in the DSCP Range field corresponding to TIDs 1, 3, 5, and 7 are both set to 255, meaning TIDs 1, 3, 5, and 7 are used for low-latency services reported by STAs or non-AP MLDs via the SCS mechanism. In another example, the DSCP range indicated by the DSCP Range field corresponding to TID 0, 1, 2, 3 covers the entire DSCP space (0 to 63), that is, TID 0, 1, 2, 3 are used for non-low latency services; and the DSCP Low Value field and DSCP High Value field in the DSCP Range field corresponding to TID 4, 5, 6, 7 are both set to 255, that is, TID 4, 5, 6, 7 are used for low latency services reported by STA or non-AP MLD through the SCS mechanism.

[0274] Alternatively, in the aforementioned QoS mapping element, the DSCP range indicated by the DSCP range field corresponding to all TIDs in the first TID set covers the entire DSCP space, i.e., the interval [0, 63]; the DSCP low value field and DSCP high value field in the DSCP range field corresponding to all TIDs in the second TID set are both set to 255. The first TID set includes one or more TIDs, and the second TID set includes one or more TIDs. The union of the first TID set and the second TID set is the TID space, i.e., 0, 1, 2, 3, 4, 5, 6, 7. The TIDs in the first TID set are used to identify non-low latency services, and the TIDs in the second TID set are used to identify low latency services, or only the AP MLD is allowed to map SCS Streams successfully added through the SCS mechanism to the second TID set. In other words, the aforementioned QoS mapping element divides the TID space (0 to 7) into two parts, one part for non-low latency services and the other part for low latency services; and configures which TIDs are used for low latency services and which TIDs are used for non-low latency services through the QoS Map element.

[0275] Optionally, because the first device informs the second device which TIDs are used by low-latency services and which are used by non-low-latency services by carrying a QoS Mapelement in the association response frame or reassociation response frame, the second device can select a desired TID from the TIDs used by low-latency services and tell it to the first device when reporting low-latency service flows through the SCS mechanism. The first device then ultimately decides the TID (which may be different from the desired TID) and AC to which the low-latency service flow reported by the second device is mapped. For example, the low-latency service may be mapped to AC_VO, or a new AC_LL (low-latency) may be defined. In this case, more than two TIDs may be mapped to a certain AC. When AC_VO or the newly defined AC_LL obtains channel access, data with higher priority is sent first according to user priority, and low-latency data with different TIDs have separate transmission queues. This ensures fairness in channel access. For example, for the same low-latency service, STA1 expects the AC to be background, while STA2 expects the AC to be voice. STA1 and STA2 belong to the same BSS. If the AP does not uniformly map this low-latency service to the same AC, then the channel access will be unfair to STA1 and STA2 (because the channel access priority of AC_VO is higher than that of AC_BK).

[0276] Optionally, after a second device supporting low-latency services successfully adds a low-latency service flow through the SCS mechanism, both the first and second devices need to map the data of that low-latency service flow to the TID and AC determined by the SCS mechanism. It is understood that although this embodiment allocates some TIDs in the TID space (0-7) to low-latency services and other TIDs to non-low-latency services through the QoS Map element, the first and second devices can still specifically negotiate the TID mapped to a particular low-latency service flow through the SCS mechanism, and use the TID negotiated by the SCS mechanism for identification when subsequently transmitting the data of that low-latency service flow.

[0277] This application embodiment divides the TID space (0 to 7) into two parts using QoS mapping elements. One part is used for non-low-latency services, and the other part is used for low-latency services. The TID can be used to distinguish whether the corresponding MPDU is low-latency service data or non-low-latency service data; that is, low-latency services and non-low-latency services will not be mapped to the same TID. Furthermore, this application embodiment can also support the implementation of the Enhanced Link Subset Mapping scheme, ensuring that Clean links can only be used to transmit low-latency services.

[0278] Example 4

[0279] Embodiment 4 of this application can be implemented alone or together with any one or more of the aforementioned embodiments 1 to 3. This application does not impose any restrictions.

[0280] See Figure 21 , Figure 21 This is a schematic flowchart of the fourth multi-link communication method provided in this application embodiment. This multi-link communication method is mainly applied in the SCS mechanism. Figure 21 As shown, this multi-link communication method includes, but is not limited to, the following steps:

[0281] S401, non-AP MLD sends an SCS request frame, which carries a TID-to-link mapping element, which is used to indicate the TID mapping rules.

[0282] S402, AP MLD receives the SCS request frame.

[0283] S403, AP MLD sends an SCS response frame.

[0284] S404, non-AP MLD receives this SCS response frame.

[0285] Optionally, the non-AP MLD generates and sends an SCS request frame, which includes one or more SCS Identifier (SCSID) fields. An SCS Identifier field indicates a reported SCS flow. The frame format of this SCS request frame is as described above. Figures 6-8 As shown, this will not be elaborated further here. The SCS request frame may carry a TID-to-link mapping element, which indicates the TID mapping rule. In other words, a non-AP MLD can send a desired TID-to-link mapping rule to the AP MLD by including the TID-to-link Mapping element in the SCS Request frame. The final TID-to-link mapping rule determined by the AP MLD may be the same as or different from the TID-to-link mapping rule desired by the non-AP MLD.

[0286] After receiving the SCS request frame, the AP MLD can reply with an SCS response frame. This SCS response frame includes a status code field, which indicates whether the AP MLD accepts the SCS flow reported in the SCS request frame. Specifically, when the status code indicates that the AP MLD accepts the SCS flow, the SCS response frame also carries a TID-to-link mapping element, indicating the TID mapping rules. In other words, when the AP MLD accepts the SCS flow, it also means that the AP MLD accepts the TID-to-link Mapping negotiation initiated by a non-AP MLD. If the content of the TID-to-link mapping element carried in the SCS response frame is exactly the same as that carried in the SCS request frame, it means that the AP MLD agrees to the TID mapping rules indicated by the TID-to-link mapping element carried in the SCS request frame. If the content of the TID-to-link mapping element carried in the SCS response frame is different from that carried in the SCS request frame, it means that the AP MLD does not agree with the TID mapping rule indicated by the TID-to-link mapping element carried in the SCS request frame; while the TID mapping rule recommended by the AP MLD is carried in the TID-to-link mapping element of the SCS response frame.

[0287] When the status code field indicates that the AP MLD rejects the SCS flow, the SCS response frame does not carry a TID-to-link mapping element. In other words, when the AP MLD rejects the SCS flow, it also means that the AP MLD rejects TID-to-link Mapping negotiations initiated by a non-AP MLD.

[0288] Optionally, when this application embodiment is implemented together with the aforementioned embodiment three, because the aforementioned embodiment three informs the non-AP MLD which TIDs are used for low-latency services and which TIDs are used for non-low-latency services through the QoS mapping element; and this application embodiment negotiates TID-to-link Mapping through the SCS mechanism. Therefore, during data transmission, when the sending end (AP MLD or non-AP MLD) sends a data packet, if the data packet does not match the SCS flow (whether the data packet matches the SCS flow can be identified by the TCLAS element described above), the TID of the data packet is set according to the QoS mapping element in the aforementioned embodiment three; when the data packet matches the SCS flow, the TID of the data packet is set according to the TID-to-link mapping element carried in the aforementioned SCS response frame. In other words, when a frame sent by the sender (AP MLD or non-AP MLD) matches a certain SCS stream (specifically identified by the TCLAS element), the sender should map it according to the user priority / TID in the TSPECelement or TCLAS element, that is, according to the TID negotiated in the SCS mechanism, rather than using the user priority / TID calculated according to the mapping rules in the QoS Map element. Only when the frame does not match any SCS stream will it be mapped to the corresponding user priority / TID according to the TID mapping rules in the QoS Map element.

[0289] This application's embodiments reduce signaling overhead and improve accuracy by simultaneously negotiating TID-to-link Mapping during SCS negotiation. This is because, compared to negotiating TID-to-link Mapping during the association process, low-latency services may not have yet occurred, resulting in inaccurate TID-to-link Mapping. However, by negotiating TID-to-link Mapping within the SCS mechanism, the STA has already identified low-latency services, and negotiating which TIDs are used by these services through the SCS mechanism leads to greater accuracy.

[0290] In one optional embodiment, the non-AP MLD does not carry a TID-to-link Mapping element in the SCS Request frame. The AP MLD can still include a TID-to-link Mapping element in the SCS Response frame to instruct the non-AP MLD to transmit data according to the indicated TID-to-link Mapping. Specifically, the non-AP MLD sends an SCS request frame, which includes an SCS identifier field indicating the reported SCS flow. Upon receiving the SCS request frame, the AP MLD replies with an SCS response frame. This SCS response frame includes a status code field set to a first value (e.g., 0), indicating that the AP MLD accepts the SCS flow. The SCS response frame also carries a TID-to-link mapping element, indicating the TID mapping rules. This SCS response frame instructs the non-AP MLD to transmit data according to the TID mapping rules indicated by the TID-to-link mapping element.

[0291] This application embodiment reduces signaling overhead by directly carrying the TID-to-link Mapping element in the SCS Response frame to instruct the non-AP MLD to transmit data according to the indicated TID-to-link Mapping.

[0292] Example 5

[0293] Embodiment 5 of this application can be implemented alone or together with any one or more of the aforementioned embodiments 1 to 4. This application does not impose any restrictions.

[0294] See Figure 22 , Figure 22 This is a fifth schematic flowchart of the multi-link communication method provided in this application embodiment. This multi-link communication method is mainly applied in the SCS mechanism. Figure 22 As shown, this multi-link communication method includes, but is not limited to, the following steps:

[0295] S501, non-AP MLD sends an SCS request frame, which includes an SCS identifier field and a QoS feature element. The SCS identifier field is used to indicate the reported SCS flow, and the QoS feature element includes third indication information, which is used to indicate the access method of the SCS flow.

[0296] S502, AP MLD receives the SCS request frame.

[0297] S503, AP MLD sends an SCS response frame.

[0298] S504, non-AP MLD receives this SCS response frame.

[0299] Optionally, the non-AP MLD generates and sends an SCS request frame, which includes an SCS identifier (SCSID) field and a QoS characteristic element. The SCS identifier field indicates the reported SCS flow. The frame format of this SCS request frame is as described above. Figure 6 , Figure 7b as well as Figure 8 As shown, this will not be elaborated further here. This QoS feature element may include third indication information, which can be used to indicate the access method of the SCS flow.

[0300] Optionally, the aforementioned third indication information can be located in the control info field of the QoS feature element. This third indication information can be a newly added field within the control info field, such as the access policy field. Of course, this third indication information can also have other names, and this embodiment does not impose any limitations.

[0301] Optionally, the aforementioned QoS feature element may further include fourth indication information, which indicates the access type (AC) mapped to the data packets of the SCS flow. This fourth indication information may also be located in the control info field of the QoS feature element. The fourth indication information is 2 bits long and may be a newly added field to the control info field, such as an access type index (AC_index) field. Of course, this fourth indication information may have other names, and this embodiment does not impose any limitations.

[0302] Optionally, the aforementioned QoS feature elements may further include fifth indication information. This fifth indication information is used to indicate the preference of the SCS flow's data packet transmission for restricted target wakeup time (rTWT), or in other words, whether the STA requests the AP to establish an rTWT for the transmission of the SCS flow. This fifth indication information may also be located in the control info field of the QoS feature element. This fifth indication information may be a newly added field to the control info field, such as an rTWT preference field. Of course, this fifth indication information may have other names, and this embodiment does not impose any limitations. For example, assuming the fifth indication information is 2 bits, when rTWT Preference is 00, it indicates that the AP is not required to establish an rTWT; when it is 01, it indicates that the AP is requested to establish an rTWT; when it is 10, it indicates that a trigger-enabled rTWT is requested; and 11 is a reserved value.

[0303] If the fifth indication information is 1 bit, setting it to 1 indicates that the AP is requesting the SCS stream to establish a TWT; otherwise, setting it to 0.

[0304] It should be understood that the target wakeup time (TWT) element contains a 1-bit indicator that the TWT is trigger-enabled. When this bit is set to 1, the STA can only wait for the AP to initiate a trigger and cannot perform EDCA. When it is set to 0, the STA is allowed to perform EDCA.

[0305] See Figure 23 , Figure 23 This is a schematic diagram of the frame format of the QoS feature elements provided in the embodiments of this application. For example... Figure 23 As shown, this QoS feature element includes, but is not limited to, a control info field. See also Figure 24 , Figure 24 This is a schematic diagram of the frame format of the control information field provided in an embodiment of this application. For example... Figure 24As shown, the control information field includes a Direction field, a Service Identifier (TID) field, a User Priority field, a presence bitmap of additional parameters, an access policy field (i.e., the third indication information mentioned above), and optionally, an Access Type Index (AC_index) field (i.e., the fourth indication information mentioned above), an rTWT Preference field (i.e., the fifth indication information mentioned above), and / or reserved bits. Specifically, when the Direction field is set to 00, it indicates uplink; when the Direction field is set to 10, it indicates downlink; when the Direction field is set to 01, it indicates a P2P (Peer-to-peer) direct link; and when the Direction field is set to 11, it is a reserved value. The TID field has values ​​from 0 to 7, with values ​​8-15 reserved. The User Priority field also has values ​​from 0 to 7, set to the same value as the TID field. The 2-bit AC_index field (i.e., the fourth indication information above) is used to indicate which AC the packets of this SCS stream are mapped to. The rTWT Preference field (i.e., the fifth indication information above) is used to indicate whether the STA requests the AP to establish an rTWT for the transmission of this SCS stream.

[0306] For uplink transmissions, the access policy field (i.e., the third indication information mentioned above) can indicate one or more of the following access methods for the SCS stream: EDCA only, scheduling only (including Trigger and TXS), or a hybrid of EDCA and scheduling. In other words, when the Direction field in the control info field is set to 00, the Access Policy can be EDCA only, Scheduling only, or a hybrid of EDCA and Scheduling.

[0307] For downlink transmissions, the access policy field (i.e., the third indication information mentioned above) can indicate one or more of the following access methods for the SCS flow: EDCA only, rTWT, or a combination of both. In other words, when the Direction field in the control info field is set to 10, the Access Policy can be EDCA only, rTWT, or a combination of both.

[0308] For P2P transmissions, the access policy field (i.e., the third indication information mentioned above) can indicate one or more of the following access methods for the SCS stream: EDCA only, or Scheduled Only (TXS). In other words, when the Direction field in the control info field is set to 01, the Access Policy can be EDCA only, Scheduled Only (TXS), or a combination of both.

[0309] Optionally, after receiving the SCS request frame, the AP MLD can reply with an SCS response frame. This SCS response frame includes a status code field, which indicates whether the AP MLD accepts the SCS flow reported in the SCS request frame. In one implementation, when the status code field indicates that the AP MLD accepts the SCS flow, the QoS feature elements included in the SCS response frame can be the same as those included in the SCS request frame. When the status code field indicates that the AP MLD rejects the SCS flow, the QoS feature elements included in the SCS response frame can be different from those included in the SCS request frame.

[0310] It should be understood that when the embodiments of this application are implemented together with the aforementioned Embodiment 4, the frame format of the SCS descriptor in the SCS request frame of the aforementioned Embodiment 4 should adopt the aforementioned... Figure 7b The frame format shown.

[0311] This application embodiment adds a new field, such as Access Policy, to the Control Info field of the QoS Characteristic element to indicate the access method requested by the STA; it also adds another new field, such as AC_index (2 bits), to the Control Info field to indicate which AC the corresponding data packet is mapped to; the access policy of the corresponding traffic stream and which AC it is mapped to can be indicated through the SCS mechanism, saving signaling overhead.

[0312] The foregoing details the method provided in this application. To facilitate the implementation of the above-described solutions in the embodiments of this application, corresponding apparatus or devices are also provided in the embodiments of this application.

[0313] This application embodiment can divide the AP MLD, first device, non-AP MLD, first site, second device, etc. into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following will combine... Figures 25 to 27 The communication device according to the embodiments of this application is described in detail. The communication device is any one of AP MLD, first device, non-AP MLD, first station, and second device. Further, the communication device can be any one of AP MLD, first device, non-AP MLD, first station, and second device.

[0314] In the case of using integrated units, see Figure 25 , Figure 25 This is a schematic diagram of the communication device 1 provided in an embodiment of this application. The communication device 1 can be any one of the AP MLD, the first device, or a chip therein, such as a Wi-Fi chip. Figure 25 As shown, the communication device includes a processing unit 11 and a transceiver unit 12.

[0315] In one design, a processing unit 11 is used to generate a first frame, which includes a supported rate and a BSS membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct a non-access point multi-link device (non-AP MLD) to prohibit the initiation of multi-link establishment with the AP MLD on the first link. A transceiver unit 12 is used to transmit the first frame on the first link.

[0316] Optionally, the AP MLD has at least two links, including the first link and the second link. The transceiver unit 12 is further configured to: transmit a beacon frame or probe response frame on the second link, the beacon frame or probe response frame including a simplified neighbor report (RNR) element, the RNR element including a neighbor AP information field corresponding to the first access point, the channel number field in the neighbor AP information field being set to 0, and the first access point being the access point operating on the first link in the AP MLD.

[0317] Optionally, the aforementioned first indication information is also used to instruct a single-link site that supports a high-throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

[0318] Optionally, the first indication information mentioned above is that the supported rate and the BSS membership selector in the BSS membership selector element are set to a preset value. This preset value is either 120 or 121.

[0319] Optionally, the first frame mentioned above can be any of the following: beacon frame, probe response frame, association response frame, or reassociation response frame.

[0320] Optionally, the first frame mentioned above is an associated response frame or a reassociated response frame. This first frame also includes a Quality of Service (QoS) mapping element. This QoS mapping element includes Differentiated Service Code Point (DSCP) range fields corresponding to eight different user priorities. The DSCP range fields corresponding to m of the eight different user priorities indicate a DSCP space that covers the interval [0, 63]. The DSCP low value field and DSCP high value field of the DSCP range fields corresponding to the other (8-m) of the eight different user priorities are both set to 255. m is a positive integer less than 8.

[0321] Optionally, the transceiver unit 12 is further configured to: receive a Flow Classification Service (SCS) request frame, the SCS request frame including an SCS identifier field, the SCS identifier field being used to indicate the reported SCS flow; and send an SCS response frame, the SCS response frame including a status code field, the status code field being used to indicate whether the AP MLD accepts the SCS flow.

[0322] Optionally, when the status code field indicates that the AP MLD accepts the SCS stream, the SCS response frame may also include a TID-to-link mapping element, which is used to indicate the TID mapping rules.

[0323] Optionally, the transceiver unit 12 is further configured to: send data packets; wherein, when the data packet does not match the SCS flow, the TID of the data packet is set according to the QoS mapping element; when the data packet matches the SCS flow, the TID of the data packet is set according to the TID-to-link mapping element carried in the SCS response frame.

[0324] It should be understood that the communication device in this design can perform the aforementioned Embodiment 1, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of AP MLD in the aforementioned Embodiment 1. For the sake of brevity, they will not be described in detail here.

[0325] In one design, transceiver unit 12 is configured to transmit a beacon frame on a first link. The beacon frame includes supported rate and BSS membership selector elements. The supported rate and BSS membership selector elements include first indication information, which instructs a first non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link. The transceiver unit 12 is also configured to transmit a BSS transfer management request frame on the first link. The BSS transfer management request frame includes second indication information, which instructs a second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame. The BSS transfer management request frame requests a first site associated with a first access point to perform a BSS transfer. The first access point is an access point in the AP MLD that operates on the first link, and the first site only supports protocols prior to the ultra-high throughput protocol.

[0326] Optionally, processing unit 11 is used to generate beacon frames and BSS transfer management request frames.

[0327] Optionally, the aforementioned second indication information is located in the reserved bits of the request mode field of the BSS transfer management request frame.

[0328] Optionally, the aforementioned first indication information is also used to instruct a single-link site that supports a high-throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

[0329] Optionally, the first indication information mentioned above is that the supported rate and the BSS membership selector in the BSS membership selector element are set to a preset value. This preset value is either 120 or 121.

[0330] Optionally, the AP MLD prohibits the reply of probe response frames and / or associated response frames on this first link.

[0331] Optionally, the transceiver unit 12 is further configured to transmit a beacon frame or probe response frame on the second link. The beacon frame or probe response frame includes a simplified neighbor report (RNR) element. The RNR element includes a neighbor AP information field corresponding to the first access point. The channel number field in the neighbor AP information field is set to 0. The first access point is the access point in the AP MLD that is operating on the first link.

[0332] It should be understood that the communication device in this design can perform the aforementioned Embodiment 2, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of AP MLD in the aforementioned Embodiment 2. For the sake of brevity, they will not be described in detail here.

[0333] In one design, processing unit 11 is used to generate an associated response frame or a reassociated response frame. The associated response frame or the reassociated response frame includes a QoS mapping element. This QoS mapping element includes Differentiated Service Code Point (DSCP) range fields corresponding to eight different user priorities. The DSCP ranges indicated by the DSCP range fields corresponding to m of the eight different user priorities cover a DSCP space, which is the interval [0, 63]. The DSCP low value field and DSCP high value field of the DSCP range fields corresponding to the other (8-m) of the eight different user priorities are both set to 255. Transceiver unit 12 is used to transmit the associated response frame or the reassociated response frame. m is a positive integer less than 8.

[0334] It should be understood that the communication device in this design can perform the aforementioned Embodiment 3, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of the first device in the aforementioned Embodiment 3. For the sake of brevity, they will not be described in detail here.

[0335] In one design, transceiver unit 12 is used to receive an SCS request frame, which carries a TID-to-link mapping element and is used to indicate the TID mapping rule; the transceiver unit 12 is also used to send an SCS response frame.

[0336] Optionally, processing unit 11 is used to generate SCS response frames.

[0337] Optionally, the SCS request frame includes an SCS identifier (SCSID) field, which indicates the reported SCS flow. The SCS response frame includes a status code field, which indicates whether the AP MLD accepts the SCS flow reported in the SCS request frame. When the status code indicates that the AP MLD accepts the SCS flow, the SCS response frame also carries a TID-to-link mapping element to indicate the TID mapping rules. When the status code indicates that the AP MLD rejects the SCS flow, the SCS response frame does not carry a TID-to-link mapping element.

[0338] It should be understood that the communication device in this design can perform the aforementioned embodiment four, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of AP MLD in the aforementioned embodiment four. For the sake of brevity, they will not be described in detail here.

[0339] In one design, the transceiver unit 12 is used to receive the SCS request frame, which includes an SCS identifier field and a QoS feature element. The SCS identifier field is used to indicate the reported SCS flow, and the QoS feature element includes third indication information, which is used to indicate the access method of the SCS flow. The transceiver unit 12 is also used to send an SCS response frame.

[0340] Optionally, processing unit 11 is used to generate SCS response frames.

[0341] Optionally, the QoS feature elements mentioned above may also include fourth indication information, which is used to indicate the access type mapped to the data packets of the SCS flow.

[0342] Optionally, both the third and fourth indication information are located in the control information field of the QoS feature element.

[0343] It should be understood that the communication device in this design can perform the aforementioned embodiment five, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of AP MLD in the aforementioned embodiment five. For the sake of brevity, they will not be described in detail here.

[0344] See Figure 26 , Figure 26 This is a schematic diagram of the communication device 2 provided in an embodiment of this application. The communication device 2 can be any one of a non-AP MLD, a first site, a second device, or a chip thereof, such as a Wi-Fi chip. Figure 26 As shown, the communication device includes a transceiver unit 21 and a processing unit 22.

[0345] In one design, a transceiver unit 21 is used to receive a first frame on a first link; a processing unit 22 is used to parse the first frame, which includes a supported rate and a BSS membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct the non-AP MLD to prohibit the initiation of multi-link establishment with the AP MLD on the first link.

[0346] Optionally, the transceiver unit 21 is further configured to receive a beacon frame or probe response frame on the second link. The beacon frame or probe response frame includes a simplified neighbor report (RNR) element. The RNR element includes a neighbor AP information field corresponding to the first access point. The channel number field in the neighbor AP information field is set to 0. The first access point is the access point in the AP MLD that is operating on the first link.

[0347] Optionally, the aforementioned first indication information is also used to instruct a single-link site that supports a high-throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

[0348] Optionally, the first indication information mentioned above is that the supported rate and the BSS membership selector in the BSS membership selector element are set to a preset value. This preset value is either 120 or 121.

[0349] Optionally, the first frame mentioned above can be any of the following: beacon frame, probe response frame, association response frame, or reassociation response frame.

[0350] Optionally, the first frame mentioned above is an associated response frame or a reassociated response frame. The first frame also includes a Quality of Service (QoS) mapping element. The QoS mapping element includes a Differentiated Service Code Point (DSCP) range field corresponding to each of the eight different user priorities. The DSCP range indicated by the DSCP range fields corresponding to m of the eight different user priorities covers the DSCP space, which is the interval [0, 63], where m is a positive integer less than 8. The DSCP low value field and DSCP high value field in the DSCP range fields corresponding to the other (8-m) of the eight different user priorities are both set to 255.

[0351] Optionally, the transceiver unit 21 is further configured to: send a Stream Classification Service (SCS) request frame, including an SCS identifier field, which is used to indicate the reported SCS stream; and receive an SCS response frame, which includes a status code field, which is used to indicate whether the AP MLD accepts the SCS stream.

[0352] Optionally, when the status code field indicates that the AP MLD accepts the SCS flow, the SCS response frame may also include a TID-to-link mapping element, which is used to indicate the TID mapping rules.

[0353] Optionally, the transceiver unit 21 is further configured to: send data packets, wherein when the data packet does not match the SCS flow, the TID of the data packet is set according to the QoS mapping element; when the data packet matches the SCS flow, the TID of the data packet is set according to the TID-to-link mapping element carried in the SCS response frame.

[0354] It should be understood that the communication device in this design can perform the aforementioned Embodiment 1, and the above-mentioned operations or functions of each unit in the communication device are respectively to implement the corresponding operations of the non-AP MLD in the aforementioned Embodiment 1. For the sake of brevity, they will not be described in detail here.

[0355] In one design, transceiver unit 21 is configured to receive a beacon frame on a first link. The beacon frame includes supported rate and BSS membership selector elements. The supported rate and BSS membership selector elements include first indication information, which instructs a first non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link. The transceiver unit 21 is also configured to receive a BSS transfer management request frame on the first link. The BSS transfer management request frame includes second indication information, which instructs a second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame. The BSS transfer management request frame requests a first site associated with a first access point to perform a BSS transfer. The first access point is an access point in the AP MLD that operates on the first link, and the first site only supports protocols prior to the Very High Throughput Protocol.

[0356] Optionally, processing unit 22 is used to parse beacon frames and BSS transfer management request frames.

[0357] Optionally, the aforementioned second indication information is located in the reserved bits of the request mode field of the BSS transfer management request frame.

[0358] Optionally, the aforementioned first indication information is also used to instruct a single-link site that supports a high-throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

[0359] Optionally, the first indication information mentioned above is that the supported rate and the BSS membership selector in the BSS membership selector element are set to a preset value. This preset value is either 120 or 121.

[0360] It should be understood that the communication device in this design can perform the aforementioned Embodiment 2, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of the first station in the aforementioned Embodiment 2. For the sake of brevity, they will not be described in detail here.

[0361] In one design, a transceiver unit 21 is used to receive an associated response frame or a reassociated response frame; a processing unit 22 is used to parse the associated response frame or the reassociated response frame, wherein the associated response frame or the reassociated response frame includes a QoS mapping element, wherein the QoS mapping element includes a Differentiated Service Code Point (DSCP) range field corresponding to 8 different user priorities, wherein the DSCP range indicated by the DSCP range fields corresponding to m of the 8 different user priorities covers the DSCP space, wherein the DSCP space is the interval [0, 63], and m is a positive integer less than 8;

[0362] The DSCP low value field and DSCP high value field in the DSCP range field corresponding to the other (8-m) user priorities among the 8 different user priorities are all set to 255.

[0363] It should be understood that the communication device in this design can perform the aforementioned Embodiment 3, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of the second device in the aforementioned Embodiment 3. For the sake of brevity, they will not be described in detail here.

[0364] In one design, transceiver unit 21 is used to send an SCS request frame, which carries a TID-to-link mapping element, which is used to indicate the TID mapping rule; the transceiver unit 21 is also used to receive an SCS response frame.

[0365] Optionally, processing unit 22 is used to parse SCS response frames.

[0366] Optionally, the SCS request frame includes an SCS identifier (SCSID) field, which indicates the reported SCS flow. The SCS response frame includes a status code field, which indicates whether the AP MLD accepts the SCS flow reported in the SCS request frame. When the status code indicates that the AP MLD accepts the SCS flow, the SCS response frame also carries a TID-to-link mapping element to indicate the TID mapping rules. When the status code indicates that the AP MLD rejects the SCS flow, the SCS response frame does not carry a TID-to-link mapping element.

[0367] It should be understood that the communication device in this design can perform the aforementioned embodiment four, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of the non-AP MLD in the aforementioned embodiment four. For the sake of brevity, they will not be described in detail here.

[0368] In one design, transceiver unit 21 is used to send the SCS request frame, which includes an SCS identifier field and a QoS feature element. The SCS identifier field is used to indicate the reported SCS flow, and the QoS feature element includes third indication information, which is used to indicate the access method of the SCS flow. The transceiver unit 12 is also used to receive an SCS response frame.

[0369] Optionally, processing unit 22 is used to parse SCS response frames.

[0370] Optionally, the QoS feature elements mentioned above may also include fourth indication information, which is used to indicate the access type mapped to the data packets of the SCS flow.

[0371] Optionally, both the third and fourth indication information are located in the control information field of the QoS feature element.

[0372] It should be understood that the communication device in this design can perform the aforementioned embodiment five, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of the non-AP MLD in the aforementioned embodiment five. For the sake of brevity, they will not be described in detail here.

[0373] The above describes the devices according to embodiments of this application. The following describes the possible product forms of these devices. It should be understood that any device possessing the above-described features... Figure 25 Any product of any form that possesses the functions of the aforementioned AP MLD or the first device, and any product that has the above-mentioned Figure 26 Any form of product that embodies the functions of the non-AP MLD, the first site, or the second device falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the product form of the devices in the embodiments of this application to this specific example.

[0374] As a possible product form, the AP MLD, first device, non-AP MLD, first station, and second device described in the embodiments of this application can be implemented by a general bus architecture.

[0375] For clarity, see [link to documentation]. Figure 27 , Figure 27 This is a schematic diagram of the structure of the communication device 1000 provided in an embodiment of this application. The communication device 1000 can be a first device or a second device, or a chip therein. Figure 27 Only the main components of the communication device 1000 are shown. In addition to the processor 1001 and transceiver 1002, the communication device may further include a memory 1003 and input / output devices (not shown).

[0376] The processor 1001 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1003 is mainly used to store software programs and data. The transceiver 1002 may include control circuitry and an antenna. The control circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0377] When the communication device is powered on, the processor 1001 can read the software program in the memory 1003, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1001 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0378] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0379] The processor 1001, transceiver 1002, and memory 1003 can be connected via a communication bus.

[0380] In one design, the communication device 1000 can be used to perform the functions of the AP MLD in the aforementioned embodiment 1: the processor 1001 can be used to perform... Figure 15 In step S101, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 15 Step S102 in the document, and / or other processes used in the techniques described herein.

[0381] In another design, the communication device 1000 can be used to perform the functions of the non-AP MLD in the aforementioned embodiment one: the processor 1001 can be used to perform... Figure 15 In step S104, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 15 Step S103 in the document, and / or other processes used in the techniques described herein.

[0382] In one design, the communication device 1000 can be used to perform the functions of the AP MLD in the aforementioned embodiment two: the processor 1001 can be used to generate Figure 18 The beacon frame sent in step S201 and the BSS transfer management request frame sent in step S203, and / or other processes used to perform the techniques described herein; transceiver 1002 can be used to perform Figure 18 Steps S201 and S203 in the document, and / or other processes used in the techniques described herein.

[0383] In another design, the communication device 1000 can be used to perform the functions of the first station in the aforementioned embodiment two: the processor 1001 can be used to parse... Figure 18 The transceiver 1002 may be used to perform the beacon frame received in step S202 and the BSS transfer management request frame received in step S204, and / or other processes for performing the techniques described herein; the transceiver 1002 may be used to perform Figure 18 Steps S202 and S204 in the document, and / or other processes used in the techniques described herein.

[0384] In one design, the communication device 1000 can be used to perform the functions of the first device in the aforementioned embodiment three: the processor 1001 can be used to execute... Figure 20 In step S301, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 20 Step S302 in the document, and / or other processes used in the techniques described herein.

[0385] In another design, the communication device 1000 can be used to perform the functions of the second device in the aforementioned embodiment three: the processor 1001 can be used to perform... Figure 20 In step S304, and / or other processes for performing the techniques described herein; transceiver 1002 can be used to perform Figure 20 Step S303 in the document, and / or other processes used in the techniques described herein.

[0386] In one design, the communication device 1000 can be used to perform the functions of the AP MLD in the aforementioned embodiment four: the processor 1001 can be used to generate Figure 21 The SCS response frame sent in step S403, and / or other processes used to perform the techniques described herein; transceiver 1002 can be used to perform Figure 21 Steps S403 and S402 in the document, and / or other processes used in the techniques described herein.

[0387] In another design, the communication device 1000 can be used to perform the functions of the non-AP MLD in the aforementioned embodiment four: the processor 1001 can be used to generate Figure 21 The SCS request frame sent in step S401, and / or other processes used to perform the techniques described herein; transceiver 1002 can be used to perform Figure 21 Steps S401 and S404 in the document, and / or other processes used in the techniques described herein.

[0388] In one design, the communication device 1000 can be used to perform the functions of the AP MLD in the aforementioned embodiment five: the processor 1001 can be used to generate Figure 22The SCS response frame sent in step S503, and / or other processes used to perform the techniques described herein; transceiver 1002 can be used to perform Figure 22 Steps S503 and S502, and / or other processes used in the techniques described herein.

[0389] In another design, the communication device 1000 can be used to perform the functions of the non-AP MLD in the aforementioned embodiment five: the processor 1001 can be used to generate Figure 22 The SCS request frame sent in step S501, and / or other processes used to perform the techniques described herein; transceiver 1002 can be used to perform Figure 22 Steps S501 and S504 in the document, and / or other processes used in the techniques described herein.

[0390] In any of the above designs, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0391] In any of the above designs, the processor 1001 may store instructions, which may be computer programs. These computer programs, running on the processor 1001, cause the communication device 1000 to execute the methods described in any of the above method embodiments. The computer program may be embedded in the processor 1001; in this case, the processor 1001 may be implemented in hardware.

[0392] In one implementation, the communication device 1000 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0393] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 27 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0394] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0395] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0396] (3) ASIC, such as modem;

[0397] (4) Modules that can be embedded in other devices;

[0398] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.

[0399] (6) Others, etc.

[0400] As a possible product form, the AP MLD, first device, non-AP MLD, first site, and second device described in the embodiments of this application can be implemented by a general-purpose processor.

[0401] A general-purpose processor for implementing AP MLD includes processing circuitry and input / output interfaces that are internally connected and communicate with the processing circuitry.

[0402] In one design, a general-purpose processor can be used to perform the functions of the AP MLD in the aforementioned embodiment one. Specifically, the processing circuitry can be used to perform... Figure 15 In step S101, and / or other processes for performing the techniques described herein; the input / output interface can be used to perform Figure 15 Step S102 in the document, and / or other processes used in the techniques described herein.

[0403] In one design, a general-purpose processor can be used to perform the functions of the AP MLD in the aforementioned embodiment two. Specifically, the processing circuitry can be used to generate... Figure 18 The beacon frame sent in step S201 and the BSS transfer management request frame sent in step S203, and / or other processes used to perform the techniques described herein; the input / output interface can be used to perform Figure 18 Steps S201 and S203 in the document, and / or other processes used in the techniques described herein.

[0404] In one design, a general-purpose processor can be used to perform the functions of the AP MLD in the aforementioned embodiment four. Specifically, the processing circuitry can be used to generate... Figure 21 The SCS request frame sent in step S401, and / or other processes used to perform the techniques described herein; the input / output interface can be used to perform Figure 21 Steps S401 and S404 in the document, and / or other processes used in the techniques described herein.

[0405] In one design, a general-purpose processor can be used to perform the functions of the AP MLD in the aforementioned embodiment five. Specifically, the processing circuitry can be used to generate... Figure 22 The SCS response frame sent in step S503, and / or other processes used to perform the techniques described herein; the input / output interface can be used to perform Figure 22 Steps S503 and S502, and / or other processes used in the techniques described herein.

[0406] The general-purpose processor implementing the first device includes processing circuitry and input / output interfaces internally connected and communicating with the processing circuitry. The general-purpose processor can be used to perform the functions of the first device in the aforementioned embodiment three. Specifically, the processing circuitry can be used to perform… Figure 20In step S301, and / or other processes for performing the techniques described herein; the input / output interface can be used to perform Figure 20 Step S302 in the document, and / or other processes used in the techniques described herein.

[0407] A general-purpose processor for implementing non-AP MLD includes processing circuitry and input / output interfaces that are internally connected and communicate with the processing circuitry.

[0408] In one design, a general-purpose processor can be used to perform the functions of the non-AP MLD in the aforementioned embodiment one. Specifically, the processing circuitry can be used to perform... Figure 15 Step S104, and / or other processes for performing the techniques described herein; the input / output interface can be used to perform Figure 15 Step S103 in the document, and / or other processes used in the techniques described herein.

[0409] In one design, a general-purpose processor can be used to perform the functions of the non-AP MLD in the aforementioned embodiment four. Specifically, the processing circuitry can be used to generate... Figure 21 The SCS request frame sent in step S401, and / or other processes used to perform the techniques described herein; the input / output interface can be used to perform Figure 21 Steps S401 and S404 in the document, and / or other processes used in the techniques described herein.

[0410] In one design, a general-purpose processor can be used to perform the functions of the non-AP MLD in the aforementioned embodiment five. Specifically, the processing circuitry can be used to generate... Figure 22 The SCS request frame sent in step S501, and / or other processes used to perform the techniques described herein; the input / output interface can be used to perform Figure 22 Steps S501 and S504 in the document, and / or other processes used in the techniques described herein.

[0411] The general-purpose processor implementing the first station includes processing circuitry and input / output interfaces internally connected and communicating with the processing circuitry. The general-purpose processor can be used to perform the functions of the first station in the aforementioned embodiment two. Specifically, the processing circuitry can be used to parse... Figure 18 The beacon frame received in step S202 and the BSS transfer management request frame received in step S204 are parsed, and / or other processes are used to perform the techniques described herein; the input / output interface can be used to perform... Figure 18 Steps S202 and S204 in the document, and / or other processes used in the techniques described herein.

[0412] The general-purpose processor implementing the second device includes processing circuitry and input / output interfaces internally connected and communicating with the processing circuitry. The general-purpose processor is used to perform the functions of the second device in the aforementioned embodiment three. Specifically, the processing circuitry can be used to perform... Figure 20 Step S304, and / or other processes for performing the techniques described herein; the input / output interface can be used to perform Figure 20 Step S303 in the document, and / or other processes used in the techniques described herein.

[0413] It should be understood that the communication devices of the various product forms described above have any of the functions of the devices in any of the above embodiments, which will not be repeated here.

[0414] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device performs the method in any of the foregoing embodiments.

[0415] This application also provides a computer program product that, when run on a computer, causes the computer to perform the methods in any of the foregoing embodiments.

[0416] This application also provides a communication device, which can exist in the form of a chip. The device includes a processor and an interface circuit. The processor is used to communicate with other devices through a receiving circuit, so that the device can execute the method in any of the foregoing embodiments.

[0417] This application also provides a wireless communication system including an AP MLD and a non-AP MLD, which can perform any of the methods in the foregoing embodiments one, four, and five.

[0418] This application also provides a wireless communication system, including an AP MLD and a first station, which can perform any of the methods in the aforementioned embodiment two.

[0419] This application also provides a wireless communication system, including a first device and a second device, which can perform any of the methods in the aforementioned embodiment three.

[0420] The steps of the methods or algorithms described in this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

[0421] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0422] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A multi-link communication method, characterized in that, include: Access Point Multilink Device (AP MLD) generates a first frame, which includes a supported rate and Basic Service Set (BSS) membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct a non-AP MLD to prohibit the initiation of multilink establishment with the AP MLD on the first link. The AP MLD transmits the first frame on the first link.

2. The method according to claim 1, characterized in that, The AP MLD has at least two links, including the first link and the second link; The method further includes: The AP MLD sends a beacon frame or probe response frame on the second link. The beacon frame or probe response frame includes a simplified neighbor report (RNR) element. The RNR element includes a neighbor AP information field corresponding to the first access point. The channel number field in the neighbor AP information field is set to 0. The first access point is the access point in the AP MLD that operates on the first link.

3. The method according to claim 1, characterized in that, The first indication information is also used to instruct a single-link site that supports a very high throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

4. The method according to any one of claims 1-3, characterized in that, The first indication information is that the supported rate and the BSS membership selector in the BSS membership selector element are set to a preset value.

5. The method according to any one of claims 1-3, characterized in that, The first frame is any one of the following: beacon frame, probe response frame, association response frame, reassociation response frame.

6. The method according to any one of claims 1-3, characterized in that, The first frame is an associated response frame or a reassociated response frame. The first frame also includes a Quality of Service (QoS) mapping element. The QoS mapping element includes a Differentiated Service Code Point (DSCP) range field corresponding to each of the eight different user priorities. The DSCP range indicated by the DSCP range fields corresponding to m of the eight different user priorities covers the DSCP space. The DSCP space is the interval [0, 63], where m is a positive integer less than 8. The DSCP low value field and DSCP high value field in the DSCP range field corresponding to the other (8-m) user priorities among the 8 different user priorities are all set to 255.

7. The method according to claim 6, characterized in that, After the AP MLD transmits the first frame on the first link, the method further includes: The AP MLD receives a Stream Classification Service (SCS) request frame, which includes an SCS identifier field used to indicate the reported SCS stream. The AP MLD sends an SCS response frame, which includes a status code field to indicate whether the AP MLD accepts the SCS stream.

8. The method according to claim 7, characterized in that, When the status code field indicates that the AP MLD accepts the SCS stream, the SCS response frame also includes a TID-to-link mapping element, which is used to indicate the TID mapping rules.

9. The method according to claim 8, characterized in that, The method further includes: AP MLD sends data packets; wherein, when the data packet does not match the SCS flow, the TID of the data packet is set according to the QoS mapping element; when the data packet matches the SCS flow, the TID of the data packet is set according to the TID to link mapping element carried in the SCS response frame.

10. A multi-link communication method, characterized in that, include: The non-access point multi-link device (non-AP MLD) receives the first frame on the first link. The non-AP MLD parses the first frame, which includes supported rates and BSS membership selector elements. The supported rates and BSS membership selector elements include first indication information, which is used to instruct the non-AP MLD to prohibit the initiation of multi-link establishment with the access point multi-link device AP MLD on the first link.

11. The method according to claim 10, characterized in that, The method further includes: The non-AP MLD receives beacon frames or probe response frames on the second link. The beacon frame or probe response frame includes a simplified neighbor report (RNR) element. The RNR element includes a neighbor AP information field corresponding to the first access point. The channel number field in the neighbor AP information field is set to 0. The first access point is the access point in the AP MLD that operates on the first link.

12. The method according to claim 11, characterized in that, The first indication information is also used to instruct a single-link site that supports a very high throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

13. The method according to any one of claims 11-12, characterized in that, The first indication information is that the supported rate and the BSS membership selector in the BSS membership selector element are set to a preset value.

14. The method according to any one of claims 11-12, characterized in that, The first frame is any one of the following: beacon frame, probe response frame, association response frame, reassociation response frame.

15. The method according to any one of claims 11-12, characterized in that, The first frame is an associated response frame or a reassociated response frame. The first frame also includes a Quality of Service (QoS) mapping element. The QoS mapping element includes a Differentiated Service Code Point (DSCP) range field corresponding to each of the eight different user priorities. The DSCP range indicated by the DSCP range fields corresponding to m of the eight different user priorities covers the DSCP space. The DSCP space is the interval [0, 63], where m is a positive integer less than 8. The DSCP low value field and DSCP high value field in the DSCP range field corresponding to the other (8-m) user priorities among the 8 different user priorities are all set to 255.

16. The method according to claim 15, characterized in that, After the non-AP MLD parses the first frame, the method further includes: The non-AP MLD sends a Stream Classification Service (SCS) request frame, which includes an SCS identifier field to indicate the reported SCS stream. The non-AP MLD receives an SCS response frame, which includes a status code field to indicate whether the AP MLD accepts the SCS stream.

17. The method according to claim 16, characterized in that, When the status code field indicates that the AP MLD accepts the SCS stream, the SCS response frame also includes a TID-to-link mapping element, which is used to indicate the TID mapping rules.

18. The method according to claim 17, characterized in that, The method further includes: When a non-AP MLD sends a data packet, the TID of the data packet is set according to the QoS mapping element when the data packet does not match the SCS flow; when the data packet matches the SCS flow, the TID of the data packet is set according to the TID-to-link mapping element carried in the SCS response frame.

19. A multi-link communication method, characterized in that, include: The AP MLD sends a beacon frame on the first link. The beacon frame includes a supported rate and a BSS membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct the first non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link. The AP MLD sends a BSS transfer management request frame on the first link. The BSS transfer management request frame includes second indication information, which is used to instruct a second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame. The BSS transfer request frame is used to request a first site associated with the first access point to perform a BSS transfer. The first access point is the access point in the AP MLD that operates on the first link. The first site only supports protocols prior to the ultra-high throughput protocol.

20. The method according to claim 19, characterized in that, The first indication information is also used to instruct a single-link site that supports a very high throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

21. The method according to claim 19 or 20, characterized in that, The first indication information is that the supported rate and the BSS membership selector in the BSS membership selector element are set to a preset value.

22. A multi-link communication method, characterized in that, include: The first site receives a beacon frame on the first link. The beacon frame includes a supported rate and a BSS membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct the first non-AP MLD to prohibit initiating multi-link establishment with the AP MLD on the first link. The first site receives a BSS transfer management request frame on the first link. The BSS transfer management request frame includes second indication information, which is used to instruct the second non-AP MLD associated with the AP MLD to ignore the BSS transfer management request frame. The BSS transfer request frame is used to request the first site associated with the first access point to perform a BSS transfer. The first access point is the access point in the AP MLD that operates on the first link. The first site only supports protocols prior to the ultra-high throughput protocol.

23. The method according to claim 22, characterized in that, The first indication information is also used to instruct a single-link site that supports a very high throughput protocol to prohibit it from establishing an association with the AP MLD on the first link.

24. The method according to claim 22 or 23, characterized in that, The first indication information is that the supported rate and the BSS membership selector in the BSS membership selector element are set to a preset value.

25. A communication device, characterized in that, include: The processing unit is configured to generate a first frame, which includes a supported rate and a Basic Service Set (BSS) membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct the non-access point multilink device (non-AP MLD) to prohibit initiating multilink establishment with the AP MLD on the first link. The transceiver unit is used to transmit the first frame on the first link.

26. A communication device, characterized in that, include: A transceiver unit, used to receive the first frame on the first link; The processing unit is configured to parse the first frame, which includes a supported rate and a BSS membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct the non-AP MLD to prohibit the initiation of multi-link establishment with the AP MLD on the first link.

27. A communication device, characterized in that, include: A transceiver unit is configured to transmit a beacon frame on a first link. The beacon frame includes a supported rate and a BSS membership selector element. The supported rate and BSS membership selector element includes first indication information, which is used to instruct a first non-AP MLD to prohibit initiating multi-link establishment with an AP MLD on the first link. The transceiver unit is further configured to send a BSS transfer management request frame on the first link. The BSS transfer management request frame includes second indication information, which is used to instruct a second non-APMLD associated with the AP MLD to ignore the BSS transfer management request frame. The BSS transfer management request frame is used to request a first site associated with the first access point to perform a BSS transfer. The first access point is an access point in the AP MLD that operates on the first link. The first site only supports protocols prior to the ultra-high throughput protocol.

28. A communication device, characterized in that, include: A transceiver unit is configured to receive a beacon frame on a first link, the beacon frame including a supported rate and a BSS membership selector element, the supported rate and BSS membership selector element including first indication information, the first indication information being used to instruct a first non-AP MLD to prohibit initiating multi-link establishment with an AP MLD on the first link; The transceiver unit is further configured to receive a BSS transfer management request frame on the first link. The BSS transfer management request frame includes second indication information, which is used to instruct a second non-APMLD associated with the AP MLD to ignore the BSS transfer management request frame. The BSS transfer management request frame is used to request a first site associated with the first access point to perform a BSS transfer. The first access point is an access point in the AP MLD that operates on the first link. The first site only supports protocols prior to the ultra-high throughput protocol.

29. A communication device, characterized in that, The device includes a processor and a transceiver, the transceiver being used to send and receive frames, and the processor, when executing program instructions, causing the communication device to perform the method of any one of claims 1-24.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-24.

31. A computer program product containing program instructions, characterized in that, When the program instructions are executed on a computer, the computer performs the method as described in any one of claims 1-24.

Images