Communication method and device

Abstract

The invention provides a communication method and device, relates to the technical field of wireless communication, and can reduce the time required for measuring an RSSI (Received Signal Strength Indicator) of an AP MLD. In the method, a non-AP MLD sends a first frame to a target AP MLD on a first link. And the non-AP MLD receives a second frame from the target AP MLD on the first link, wherein the time interval between the end time of the first frame and the start time of the second frame is SIFS. Based on the above scheme, the time interval between the end time of the first frame and the start time of the second frame is SIFS, so that the time required for measuring the RSSI can be reduced in a mode of measuring the RSSI of the MLD of the target AP through interaction of the first frame and the second frame, and the second frame can also be used for establishing synchronization, so that the synchronization efficiency is improved. The time required for establishing synchronization between the first station and the first access point can also be reduced.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Currently, methods for measuring the received signal strength indication (RSSI) of a target access point (AP) multi-link device (MLD) can include the non-access point (non-AP) MLD receiving beacon frames from the target AP MLD. However, the transmission period for beacon frames is typically 100 milliseconds, thus requiring a relatively long time to measure the RSSI of the target AP MLD.

[0003] In another approach, the non-AP MLD can send a probe request frame to the target AP MLD, requesting the target AP MLD to send a probe response frame. If the target AP MLD sends a probe response frame, the non-AP MLD can then measure the target AP MLD's RSSI. However, the probe request and probe response frames are management frames, requiring more information. Furthermore, because they are management frames, the non-AP MLD, upon receiving the probe request frame, needs to reply with an ACK after SIFS, and then re-contact the channel before replying with a probe response frame. The non-AP MLD also needs to wait for SIFS after receiving the probe response frame before replying with an ACK. This measurement method takes longer. Summary of the Invention

[0004] This application provides a communication method and apparatus that can reduce the time required to measure the RSSI of a target access point multi-link device, and can also help non-access point multi-link devices establish synchronization with the target access point multi-link device during roaming.

[0005] Firstly, a communication method is provided, which can be executed by a non-access point multilink device. Unless otherwise specified, the "non-access point multilink device" involved in the embodiments of this application can refer to a non-access point multilink device, a component within a non-access point multilink device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of a non-access point multilink device. In this method, the non-access point multilink device sends a first frame to a target access point multilink device on a first link. The first frame is used to request the target access point multilink device to send a second frame on the first link. The time interval between the end time of the first frame and the start time of the second frame is the short inter-frame space (SIFS). The non-access point multilink device receives the second frame from the target access point multilink device on the first link. The second frame is used to measure the RSSI of the first link of the target access point multilink device and / or the second frame is used to establish synchronization between the non-access point multilink device and a first access point corresponding to the first link. The first access point is an auxiliary access point corresponding to the target access point multilink device on the first link.

[0006] Based on the above scheme, the time interval between the end time of the first frame and the start time of the second frame is SIFS. Therefore, by measuring the RSSI of the first access point of the target AP MLD through the interaction of the first and second frames, the time required to measure RSSI can be reduced. The second frame can also be used to establish synchronization, helping the first site to establish synchronization with the first access point.

[0007] In one possible implementation, the first frame occupies a bandwidth of 20MHz and is carried on the main 20MHz channel of the first link. Based on this scheme, the large bandwidth occupied by the first frame can be avoided, thus preventing attackers from using the large bandwidth of the first frame to perceive environmental information and reducing security risks.

[0008] In one possible implementation, the second frame occupies a bandwidth of 20MHz and is carried on the primary 20MHz channel of the first link. Based on this scheme, the large bandwidth occupied by the second frame can be avoided, thus preventing attackers from using the high-bandwidth second frame to perceive environmental information and reducing security risks.

[0009] In one possible implementation, the sending address of the first frame is the address of the first station corresponding to the first link, the first station being an auxiliary station of the non-access point multi-link device on the first link, the receiving address of the first frame is the address of the first access point, and the first frame satisfies one or more of the following:

[0010] 1. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the first request and first response interaction with the target access point multi-link device. The first request is used to probe the target access point multi-link device, and carries the address of the first site and / or the link identifier of the first link. The first response is used to provide information about the target access point multi-link device, and carries the address of the first access point and / or the link identifier of the first link. Based on the above, the target access point multi-link device will only reply with a second frame after the non-access point multi-link device has probed the target access point multi-link device through a distributed system (DS) over the DS approach, thereby reducing security risks.

[0011] 2. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the exchange of sending a second request and a second response with the target access point multi-link device. The second request and the second response are used to establish a temporary key between the non-access point multi-link device and the target access point multi-link device, such as a unicast temporary key. The second request carries the address of the first site and / or the link identifier of the first link, and the second response carries the address of the first access point and / or the link identifier of the first link. Based on the above, the target access point multi-link device will only reply with a second frame after the non-access point multi-link device has negotiated the key with the target access point multi-link device through the DS (over the DS) method, thereby reducing security risks.

[0012] For example, the second request and the second response are used to derive a unicast temporary key. Deriving a unicast temporary key can be understood as the AP MLD and non-AP MLD calculating the key themselves based on relevant information such as random numbers carried in the temporary key in the second request and the second response; that is, the unicast key is not carried in the frame.

[0013] 3. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the third request and third response interaction with the target access point multi-link device. The third request and third response are used to establish the first link and / or resource reservation between the non-access point multi-link device and the target access point multi-link device. The third request carries the address of the first site and / or the link identifier of the first link, and the third response carries the address of the first access point and / or the link identifier of the first link. Based on the above, the target access point multi-link device will only reply with a second frame if the non-access point multi-link device establishes a multi-link with the target access point multi-link device through the DS (over the DS) method, thereby reducing security risks.

[0014] In one possible implementation, the first frame is an enhanced long-range physical protocol data unit (PAMP) or an ultra-robust PAMP. In another possible implementation, the second frame is an enhanced long-range PAMP or an ultra-robust PAMP. Based on the above schemes, the enhanced long-range PAMP or ultra-robust PAMP can improve the performance of RSSI measurements.

[0015] In one possible implementation, the first frame is an empty data packet request frame, and the second frame includes an empty data packet notification frame and an empty data packet.

[0016] In one possible implementation, the first frame is the initial control frame, and the second frame is the initial control response frame.

[0017] In one possible implementation, the second frame carries the synchronization time information of the first access point, which is used for the first site to synchronize time with the first access point.

[0018] Based on the above scheme, the first station can synchronize its time with the first access point based on the synchronization time information of the first access point carried in the second frame, which can reduce the time required for time synchronization.

[0019] In one possible implementation, the synchronization time information includes part or all of the timestamp information of the first access point, or the synchronization time information includes the time synchronization function offset of the first access point.

[0020] In one possible implementation, the first field in the first request is a broadcast address. This broadcast address is used by the source access point multi-link device (or the current access point multi-link device) to send the fourth request to one or more neighboring access point multi-link devices. The fourth request is generated based on the first request. Here, the source access point multi-link device is an access point multi-link device associated with a non-access point multi-link device, and the target access point multi-link device is one or more of the one or more neighboring access point multi-link devices.

[0021] Based on the above scheme, when the first field in the first request is a broadcast address, the source access point multilink device can send a fourth request to one or more neighboring access point multilink devices through DS to realize DS-based communication between the non-access point multilink device and the target access point multilink device.

[0022] In one possible implementation, the non-access point multilink device sends an eighth request to the source access point multilink device. This eighth request requests a temporary key, such as a unicast temporary key and / or a multicast temporary key, between the non-access point multilink device and the target access point multilink device, and requests the establishment of a multilink between them. The non-access point multilink device receives an eighth response from the source access point multilink device. This eighth response responds to the eighth request and carries information related to the temporary key between the non-access point multilink device and the target access point multilink device. Optionally, the eighth response may also be used to distribute the multicast temporary key. The source access point multilink device is the access point multilink device associated with the non-access point multilink device.

[0023] For example, distributing a multicast temporary key refers to the AP MLD sending the multicast key to the non-AP MLD, with the multicast key carried in the frame. Optionally, the multicast key can be protected by encryption of the MIC or unicast key.

[0024] Based on the above scheme, non-access point multi-link devices can achieve key negotiation and multi-link establishment through the eighth request, which can reduce the time required for non-access point multi-link devices to transfer to the target access point multi-link device.

[0025] Secondly, a communication method is provided, which can be executed by a target access point multilink device. Unless otherwise specified, the "target access point multilink device" in the embodiments of this application can refer to the target access point multilink device itself, a component within the target access point multilink device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the target access point multilink device. In this method, the target access point multilink device receives a first frame from a non-access point multilink device on a first link. The first frame is used to request the target access point multilink device to send a second frame on the first link. The target access point multilink device sends the second frame to the non-access point multilink device on the first link, and the time interval between the end time of the first frame and the start time of the second frame is SIFS. The second frame is used to measure the RSSI of the first link of the target access point multilink device and / or the second frame is used to establish synchronization between the non-access point multilink device and a first access point corresponding to the first link, where the first access point is an auxiliary access point corresponding to the target access point multilink device on the first link.

[0026] In one possible implementation, the first frame is carried on the primary 20MHz channel of the first link.

[0027] In one possible implementation, the second frame is carried on the primary 20MHz channel of the first link.

[0028] In one possible implementation, the sending address of the first frame is the address of the first station corresponding to the first link, the first station being an auxiliary station of the non-access point multi-link device on the first link, the receiving address of the first frame is the address of the first access point, and the first frame satisfies one or more of the following:

[0029] 1. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the first request and first response interaction with the target access point multi-link device. The first request is used to probe the target access point multi-link device and carries the address of the first site and / or the link identifier of the first link. The first response is used to feed back the information of the target access point multi-link device and carries the address of the first access point and / or the link identifier of the first link.

[0030] 2. Before the non-access point multi-link device sends the first frame on the first link, it has successfully completed the exchange of sending the second request and the second response with the target access point multi-link device. The second request and the second response are used to establish a temporary key for communication between the non-access point multi-link device and the target access point multi-link device, such as a unicast temporary key. The second request carries the address of the first site and / or the link identifier of the first link, and the second response carries the address of the first access point and / or the link identifier of the first link.

[0031] 3. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the third request and third response interaction with the target access point multi-link device. The third request and third response are used to establish the first link and / or resource reservation between the non-access point multi-link device and the target access point multi-link device. The third request carries the address of the first site and / or the link identifier of the first link, and the third response carries the address of the first access point and / or the link identifier of the first link.

[0032] In one possible implementation, the first frame is an enhanced long-range physical protocol data unit or an ultra-robust physical protocol data unit.

[0033] In one possible implementation, the second frame is an enhanced long-range physical protocol data unit or an ultra-robust physical protocol data unit.

[0034] In one possible implementation, the first frame is an empty data packet request frame, and the second frame includes an empty data packet notification frame and an empty data packet.

[0035] In one possible implementation, the first frame is the initial control frame, and the second frame is the initial control response frame.

[0036] In one possible implementation, the second frame carries the synchronization time information of the first access point, which is used for the first site to synchronize time with the first access point.

[0037] In one possible implementation, the synchronization time information includes part or all of the timestamp information of the first access point.

[0038] In one possible implementation, the target access point multilink device receives a fifth request from the source access point multilink device. The fifth request is determined based on a first request, which is received by the source access point multilink device from a non-access point multilink device. The first field in the first request is the broadcast address.

[0039] In one possible implementation, the target access point multilink device receives a ninth request from the source access point multilink device. This ninth request requests a temporary key between the non-access point multilink device and the target access point multilink device, and requests the establishment of a multilink between them. The target access point multilink device sends a ninth response to the source access point multilink device. This ninth response responds to the ninth request and carries information related to the temporary key between the non-access point multilink device and the target access point multilink device. The source access point multilink device is the access point multilink device associated with the non-access point multilink device.

[0040] Thirdly, a communication method is provided, which can be executed by a source access point multilink device. Unless otherwise specified, the "source access point multilink device" involved in the embodiments of this application can refer to a source access point multilink device, a component within a source access point multilink device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of a source access point multilink device. In this method, the source access point multilink device receives a first request from a non-access point multilink device, where the first field of the first request is a broadcast address. The first request is used to probe a target access point multilink device. The source access point multilink device sends a fifth request to the target access point multilink device, the fifth request being determined based on the first request, and the fifth request is used to probe the target access point multilink device.

[0041] In one possible implementation, the source access point multilink device receives an eighth request from a non-access point multilink device. This eighth request requests a temporary key between the non-access point multilink device and the target access point multilink device, and also requests the establishment of a multilink between them. The source access point multilink device sends a ninth request to the target access point multilink device. This ninth request is generated based on the eighth request and requests a temporary key between the non-access point multilink device and the target access point multilink device, as well as requests to establish a multilink between them. The source access point multilink device receives a ninth response from the target access point multilink device. This ninth response responds to the ninth request and carries the temporary key between the non-access point multilink device and the target access point multilink device. The source access point multilink device then sends an eighth response to the target access point multilink device. This eighth response responds to the eighth request and carries information related to the temporary key between the non-access point multilink device and the target access point multilink device. Optionally, the eighth response may also be used to distribute a multicast temporary key.

[0042] Fourthly, a communication device is provided, including a processing unit and a transceiver unit.

[0043] The transceiver unit is configured to send a first frame to the target access point multi-link device on the first link. The first frame requests the target access point multi-link device to send a second frame on the first link. The time interval between the end time of the first frame and the start time of the second frame is SIFS. The transceiver unit is also configured to receive a second frame from the target access point multi-link device on the first link. The second frame is used to measure the RSSI of the first link of the target access point multi-link device and / or to establish synchronization between a non-access point multi-link device and the first access point corresponding to the first link. The first access point is the auxiliary access point corresponding to the target access point multi-link device on the first link. The processing unit is configured to measure the RSSI of the first link and / or establish synchronization with the first access point.

[0044] In one possible implementation, the first frame occupies a bandwidth of 20MHz and is carried on the main 20MHz channel of the first link.

[0045] In one possible implementation, the second frame occupies a bandwidth of 20MHz and is carried on the main 20MHz channel of the first link.

[0046] In one possible implementation, the sending address of the first frame is the address of the first station corresponding to the first link, the first station being an auxiliary station of the non-access point multi-link device on the first link, the receiving address of the first frame is the address of the first access point, and the first frame satisfies one or more of the following:

[0047] 1. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the first request and first response interaction with the target access point multi-link device. The first request is used to probe the target access point multi-link device and carries the address of the first site and / or the link identifier of the first link. The first response is used to feed back the information of the target access point multi-link device and carries the address of the first access point and / or the link identifier of the first link.

[0048] 2. Before the non-access point multi-link device sends the first frame on the first link, it has successfully completed the exchange of sending the second request and the second response with the target access point multi-link device. The second request and the second response are used to establish a temporary key for communication between the non-access point multi-link device and the target access point multi-link device. The second request carries the address of the first site and / or the link identifier of the first link, and the second response carries the address of the first access point and / or the link identifier of the first link.

[0049] 3. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the third request and third response interaction with the target access point multi-link device. The third request and third response are used to establish the first link and / or resource reservation between the non-access point multi-link device and the target access point multi-link device. The third request carries the address of the first site and / or the link identifier of the first link, and the third response carries the address of the first access point and / or the link identifier of the first link.

[0050] In one possible implementation, the first frame is an enhanced long-range physical protocol data unit (PAMP) or an ultra-robust PAMP. In another possible implementation, the second frame is an enhanced long-range PAMP or an ultra-robust PAMP. Based on the above schemes, the enhanced long-range PAMP or ultra-robust PAMP can improve the performance of RSSI measurements.

[0051] In one possible implementation, the first frame is an empty data packet request frame, and the second frame includes an empty data packet notification frame and an empty data packet.

[0052] In one possible implementation, the first frame is the initial control frame, and the second frame is the initial control response frame.

[0053] In one possible implementation, the second frame carries the synchronization time information of the first access point, which is used for the first site to synchronize time with the first access point.

[0054] In one possible implementation, the synchronization time information includes part or all of the timestamp information of the first access point, or the synchronization time information includes the time synchronization function offset of the first access point.

[0055] In one possible implementation, the first field in the first request is a broadcast address. This broadcast address is used by the source access point multi-link device to send a fourth request to one or more neighboring access point multi-link devices. The fourth request is generated based on the first request. Here, the source access point multi-link device is an access point multi-link device associated with a non-access point multi-link device, and the target access point multi-link device is one or more of the one or more neighboring access point multi-link devices.

[0056] In one possible implementation, the transceiver unit is further configured to send an eighth request to the source access point multilink device. The eighth request requests a temporary key between the non-access point multilink device and the target access point multilink device, and requests the establishment of a multilink between the non-access point multilink device and the target access point multilink device. The transceiver unit is also configured to receive an eighth response from the source access point multilink device. The eighth response responds to the eighth request and carries information related to the temporary key between the non-access point multilink device and the target access point multilink device. Optionally, the eighth response further distributes the multicast temporary key. The source access point multilink device is an access point multilink device associated with the non-access point multilink device.

[0057] Fifthly, a communication device is provided, including a processing unit and a transceiver unit.

[0058] The transceiver unit is configured to receive a first frame from a non-access point multi-link device on the first link. The first frame requests the target access point multi-link device to send a second frame on the first link. The processing unit is configured to generate the second frame, where the time interval between the end time of the first frame and the start time of the second frame is SIFS. The second frame is used to measure the RSSI of the first link of the target access point multi-link device and / or to establish synchronization between the non-access point multi-link device and the first access point corresponding to the first link. The first access point is the auxiliary access point corresponding to the target access point multi-link device on the first link. The transceiver unit is also configured to send the second frame to the non-access point multi-link device on the first link.

[0059] In one possible implementation, the first frame is carried on the primary 20MHz channel of the first link.

[0060] In one possible implementation, the second frame is carried on the primary 20MHz channel of the first link.

[0061] In one possible implementation, the sending address of the first frame is the address of the first station corresponding to the first link, the first station being an auxiliary station of the non-access point multi-link device on the first link, the receiving address of the first frame is the address of the first access point, and the first frame satisfies one or more of the following:

[0062] 1. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the first request and first response interaction with the target access point multi-link device. The first request is used to probe the target access point multi-link device and carries the address of the first site and / or the link identifier of the first link. The first response is used to feed back the information of the target access point multi-link device and carries the address of the first access point and / or the link identifier of the first link.

[0063] 2. Before the non-access point multi-link device sends the first frame on the first link, it has successfully completed the exchange of sending the second request and the second response with the target access point multi-link device. The second request and the second response are used to establish a temporary key for communication between the non-access point multi-link device and the target access point multi-link device. The second request carries the address of the first site and / or the link identifier of the first link, and the second response carries the address of the first access point and / or the link identifier of the first link.

[0064] 3. Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the third request and third response interaction with the target access point multi-link device. The third request and third response are used to establish the first link and / or resource reservation between the non-access point multi-link device and the target access point multi-link device. The third request carries the address of the first site and / or the link identifier of the first link, and the third response carries the address of the first access point and / or the link identifier of the first link.

[0065] In one possible implementation, the first frame is an enhanced long-range physical protocol data unit or an ultra-robust physical protocol data unit.

[0066] In one possible implementation, the second frame is an enhanced long-range physical protocol data unit or an ultra-robust physical protocol data unit.

[0067] In one possible implementation, the first frame is an empty data packet request frame, and the second frame includes an empty data packet notification frame and an empty data packet.

[0068] In one possible implementation, the first frame is the initial control frame, and the second frame is the initial control response frame.

[0069] In one possible implementation, the second frame carries the synchronization time information of the first access point, which is used for the first site to synchronize time with the first access point.

[0070] In one possible implementation, the synchronization time information includes part or all of the timestamp information of the first access point.

[0071] In one possible implementation, the target access point multilink device receives a fifth request from the source access point multilink device. The fifth request is determined based on a first request, which is received by the source access point multilink device from a non-access point multilink device. The first field in the first request is the broadcast address.

[0072] In one possible implementation, the transceiver unit is further configured to receive a ninth request from the source access point multilink device. The ninth request requests a temporary key between the non-access point multilink device and the target access point multilink device, and requests the establishment of a multilink between the non-access point multilink device and the target access point multilink device. The transceiver unit is also configured to send a ninth response to the source access point multilink device. The ninth response responds to the ninth request and carries information related to the temporary key between the non-access point multilink device and the target access point multilink device. Here, the source access point multilink device is the access point multilink device associated with the non-access point multilink device.

[0073] Sixthly, a communication device is provided, including a processing unit and a transceiver unit.

[0074] The transceiver unit is configured to receive a first request from a non-access point multi-link device, wherein the first field in the first request is a broadcast address. The first request is used to probe a target access point multi-link device. The processing unit is configured to generate a fifth request based on the first request, wherein the fifth request is used to probe the target access point multi-link device. The transceiver unit is also configured to send the fifth request to the target access point multi-link device.

[0075] In one possible implementation, the transceiver unit is further configured to receive an eighth request from the non-access point multilink device, the eighth request being used to request a temporary key between the non-access point multilink device and the target access point multilink device, and to request the establishment of a multilink between the non-access point multilink device and the target access point multilink device. The transceiver unit is further configured to send a ninth request to the target access point multilink device, the ninth request being generated based on the eighth request, the ninth request being used to request a temporary key between the non-access point multilink device and the target access point multilink device, and to request the establishment of a multilink between the non-access point multilink device and the target access point multilink device. The transceiver unit is further configured to receive a ninth response from the target access point multilink device, the ninth response being used to respond to the ninth request, and the ninth response carrying the temporary key between the non-access point multilink device and the target access point multilink device. The transceiver unit is further configured to send an eighth response to the target access point multilink device, the eighth response being used to respond to the eighth request, and the eighth response carrying information related to the temporary key between the non-access point multilink device and the target access point multilink device. Optionally, the eighth response is also used to distribute the multicast temporary key.

[0076] In a seventh aspect, a communication apparatus is provided for implementing the various methods described above. This communication apparatus may be a non-access point multi-link device as described in the first aspect; or, it may be a target access point multi-link device as described in the second aspect; or, it may be a source access point multi-link device as described in the third aspect. The communication apparatus includes modules, units, or means for implementing the methods described above. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0077] Eighthly, a communication device is provided, comprising: a processor and a communication interface; the communication interface being configured to communicate with a module outside the communication device; the processor being configured to execute a computer program or instructions to cause the method described in any of the preceding aspects to be performed. The communication device may be a non-access point multi-link device as described in the first aspect; or, the communication device may be a target access point multi-link device as described in the second aspect; or, the communication device may be a source access point multi-link device as described in the third aspect. For example, when the communication device is a non-access point multi-link device, the communication interface is used to communicate with the target access point multi-link device and / or the source access point multi-link device. Again, for example, when the communication device is a target access point multi-link device, the communication interface is used to communicate with the non-access point multi-link device and / or the source access point multi-link device. Again, for example, when the communication device is a non-access point multi-link device, the communication interface is used to communicate with the target access point multi-link device and / or the source access point multi-link device.

[0078] A ninth aspect provides a communication apparatus, comprising: at least one processor; the processor being configured to execute a computer program or instructions stored in a memory to implement the method described in any of the preceding aspects. The memory may be coupled to the processor, or may be independent of the processor. The communication apparatus may be a non-access point multi-link device as described in the first aspect; or, the communication apparatus may be a target access point multi-link device as described in the second aspect; or, the communication apparatus may be a source access point multi-link device as described in the third aspect.

[0079] In a tenth aspect, this application provides a communication system that may include a non-access point multi-link device performing the method described in the first aspect and a target access point multi-link device performing the method described in the second aspect. Optionally, the communication system may further include a source non-access point multi-link device performing the method described in the third aspect.

[0080] In one aspect, this application provides a computer-readable storage medium storing computer-readable instructions, which, when read and executed by a computer, cause the computer to perform any possible implementation of any of the first to third aspects described above.

[0081] In a twelfth aspect, this application provides a computer program product that, when read and executed by a computer, causes the computer to perform a method in any possible implementation of any of the first to third aspects described above.

[0082] In a thirteenth aspect, this application provides a chip for reading a computer program stored in a memory to execute a method in any possible implementation of any of the first to third aspects described above.

[0083] It is understood that the technical effects of the second to thirteenth aspects can refer to the technical effects of any possible implementation of the first aspect, and will not be repeated here. Attached Figure Description

[0084] Figure 1 A schematic diagram of a communication system provided in an embodiment of this application;

[0085] Figure 2 This is an exemplary flowchart of a fast BSS transfer;

[0086] Figure 3A A schematic diagram of the frame structure of an FT action frame provided in an embodiment of this application;

[0087] Figure 3B A schematic diagram of a fast BSS transfer element format provided for an embodiment of this application;

[0088] Figure 3C A schematic diagram of an MDE format provided for an embodiment of this application;

[0089] Figure 4 A schematic diagram of a frame format for an FT response frame provided in an embodiment of this application;

[0090] Figure 5A A schematic diagram of a frame format for an FT confirmation frame provided in an embodiment of this application;

[0091] Figure 5B A schematic diagram of a frame format for an FT ACK frame provided in an embodiment of this application;

[0092] Figure 6 An exemplary flowchart of a communication method provided in an embodiment of this application;

[0093] Figure 7 A schematic diagram illustrating a multi-link element for a probe request, provided as an embodiment of this application;

[0094] Figure 8 An exemplary flowchart of another communication method provided in an embodiment of this application;

[0095] Figure 9A A schematic diagram illustrating the frame interaction between a first frame and a second frame, provided for an embodiment of this application;

[0096] Figure 9B A schematic diagram illustrating the frame interaction between the first frame and the second frame, provided for an embodiment of this application;

[0097] Figure 9C A schematic diagram illustrating the frame interaction between the first frame and the second frame, provided for an embodiment of this application;

[0098] Figure 10 A schematic diagram of a communication device provided in an embodiment of this application;

[0099] Figure 11 A schematic diagram of yet another communication device provided in the embodiments of this application;

[0100] Figure 12 A schematic diagram of yet another communication device provided in the embodiments of this application;

[0101] Figure 13 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0102] The technical solutions provided by the embodiments of this application are described below with reference to the accompanying drawings.

[0103] The technical solutions in this application can be applied to various communication systems, such as Universal Mobile Telecommunications System (UMTS), Wireless Local Area Network (WLAN), Wireless Fidelity (Wi-Fi) systems, 4th generation (4G) mobile communication systems (e.g., Long Term Evolution, LTE), 5th generation (5G) mobile communication systems (e.g., New Radio, NR), 6th generation (6G), and future evolution communication systems. Of course, the technical solutions provided in this application can also be applied to other possible communication systems, such as Vehicle-to-Everything (V2X) systems, Internet of Things (IoT) systems, and Narrow Band Internet of Things (NB-IoT) systems.

[0104] This application's embodiments can also be applied to WLAN scenarios, for example, to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 system standards, such as 802.11be, Wi-Fi 7, or Extremely High Throughput (EHT), 802.11bf, and next-generation standards of 802.11be, such as 802.11bn, UHR, Wi-Fi 8, or even later standards. Alternatively, this application's embodiments can also be applied to wireless local area network systems such as Internet of Things (IoT) networks or Vehicle-to-X (V2X) networks. Of course, this application's embodiments can also be applied to other possible communication systems, such as worldwide interoperability for microwave access (WiMAX) communication systems, 5G communication systems, and future communication systems.

[0105] This application supports IEEE protocols, such as IEEE 802.11be / Wi-Fi 7 / EHT, IEEE 802.11bn / UHR / Wi-Fi 8, IEEE Integrated mmWave / IMMW, IEEE 802.15 / UWB, or IEEE 802.11bf / sensing; this application may also support Spark Link / NearLink standard protocols.

[0106] The following examples illustrate the application of this application to WLAN scenarios. It should be understood that WLAN standards, starting with 802.11a / g, have evolved through 802.11n, 802.11ac, 802.11ax, 802.11be, and the currently discussed 802.11bn. 802.11n can also be referred to as high throughput (HT); 802.11ac as very high throughput (VHT); 802.11ax as high efficiency (HE) or Wi-Fi 6; 802.11be as EHT or Wi-Fi 7; and 802.11bn as UHR or Wi-Fi 8. Standards prior to HT, such as 802.11a / b / g, can be collectively referred to as non-high throughput (Non-HT).

[0107] In IEEE 802.11 Next Generation Wireless Fidelity (Wi-Fi) Extremely High Throughput (EHT), multi-link technology can be used to improve transmission rates. Devices with multi-link aggregation capabilities are called multi-link devices (MLDs). In one design, an MLD can refer to a device that simultaneously has multiple radio frequency modules, each operating on different frequency bands / channels. When the channel spacing between two radio frequency modules within a device is sufficiently large, they can operate independently without interference. If any two links support simultaneous transmission on one link and reception on the other, then the two links are said to support simultaneous transmit and receive (STR) capability; otherwise, they are said to not support simultaneous transmit and receive capability, i.e., non-STR.

[0108] MLDs can include non-access point (non-AP) MLDs and / or access point (AP) MLDs, where non-AP MLDs can also be referred to as station (STA) MLDs. Non-AP MLDs and AP MLDs can communicate with each other. Due to factors such as movement, a non-AP MLD may experience a switchover of its associated AP MLD. For example, due to movement, a non-AP MLD may move from the coverage area of ​​AP MLD1 to the coverage area of ​​AP MLD2. Therefore, it may be necessary to switch the AP MLD associated with the non-AP MLD.

[0109] like Figure 1 As shown, a communication system is provided, which includes a non-AP MLD and an AP MLD.

[0110] A non-AP MLD can be a device with wireless transceiver capabilities. For example, a non-AP MLD can be a terminal device, user equipment (UE), access terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment. In specific applications, a non-AP MLD can be a cellular phone, mobile phone, tablet, wearable device, point-of-sale (POS) machine, customer-premises equipment (CPE), a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a terminal device in industrial control, a terminal device in self-driving, a terminal device in remote medical care, a terminal device in a smart grid, a terminal device in a smart city, or a terminal device in a smart home, etc.

[0111] A non-AP MLD can include multiple links, each corresponding to a different STA entity. These STA entities typically operate on different frequency bands or channels. Figure 1In the example, the non-AP MLD includes two STA entities, referred to as STA1 and STA2. Both STA1 and STA2 can operate in the 2.4G and 5G frequency bands, but at any given time, STA1 and STA2 are operating in different frequency bands.

[0112] AP MLD can be Figure 1 APMLD1 and / or APMLD2. AP MLDs are devices such as wireless hubs or routers used to provide wireless network access services, and can serve as access points for non-AP MLDs to enter the wired Ethernet backbone.

[0113] Similar to non-AP MLDs, AP MLDs can include multiple links, each corresponding to a different AP entity. These multiple AP entities typically operate on different frequency bands or channels. Figure 1 In the example, APMLD1 and APMLD2 each include two AP entities, referred to as AP1 and AP2 respectively. AP1 and AP2 operate on different frequency bands; AP1 operates in the 2.4 GHz band, and AP2 operates in the 5 GHz band.

[0114] In one design, before handover or roaming, the non-AP MLD is associated with AP MLD1, and AP MLD1 is referred to as the current APMLD. See details. Figure 1 STA1 operates in the 2.4GHz band and establishes a link with AP1. STA2 operates in the 5GHz band and establishes a link with AP2. Due to factors such as mobility, a non-AP MLD moves out of the coverage area of ​​its current AP MLD (i.e., AP MLD1) and into the coverage area of ​​the target AP MLD (i.e., AP MLD2). Therefore, a non-AP MLD needs to switch its associated AP MLD, such as from AP MLD1 to AP MLD2.

[0115] In one possible implementation, Figure 1The communication system shown may also include other non-AP MLDs and / or AP MLDs, or other devices, without limitation. For example, the communication system may also include a distributed system (DS). In one implementation, the DS may be a system that interconnects multiple basic service sets (BSSs) and integrates a local area network to form an extended service set (ESS). That is, the DS can construct an ESS that includes multiple interconnected BSSs, or it can be described as: the DS includes multiple interconnected BSSs, etc. A BSS is a basic component of a local area network (LAN) 802.11. A BSS consists of STAs located within a certain coverage area and forming some kind of connection. For example, an AP MLD may include multiple AP entities, each AP entity corresponds to a BSS, and each BSS corresponding to an AP entity may include at least one STA, and these multiple STAs are associated with the AP entity corresponding to that BSS.

[0116] The following, combined with Figure 2 This section describes the process of rapid BSS transfer in related technologies. (See also...) Figure 2 This is an exemplary flowchart of a fast BSS transfer, which may include the following steps. Figure 2 In the illustrated embodiment, the non-AP MLD can be understood as the fast BSS transition originator (FTO), and the target AP MLD and source AP MLD can be referred to as the target fast BSS transition response (FTR) and source FTR, respectively.

[0117] S201: The non-AP MLD sends a fast BSS transition (FT) request frame to the source AP MLD (current AP MLD).

[0118] Correspondingly, the source AP MLD receives FT request frames from the non-AP MLD.

[0119] The FT request frame can be used to request a pairwise transient key (PTK) used by the target AP MLD to communicate with the non-AP MLD.

[0120] S202: The source AP MLD sends a remote request frame to the target AP MLD.

[0121] Correspondingly, the target AP MLD receives remote request frames from the source AP MLD.

[0122] For example, the source AP MLD can send a remote request frame to the target AP MLD via DS. This remote request frame can be generated based on an FT request and is used to request the target AP MLD to generate the PTK used for communication with the non-AP MLD.

[0123] S203: The target AP MLD sends a remote response frame to the source AP MLD.

[0124] Correspondingly, the source AP MLD receives remote response frames from the target AP MLD.

[0125] For example, the target AP MLDK can send a remote response frame to the source AP MLD via DS. This remote response frame is used to respond to a remote request frame. For example, this remote response frame may carry a PTK for communication between the target AP MLD and the non-AP MLD.

[0126] S204: The source AP MLD sends an FT response frame to the non-AP MLD.

[0127] Correspondingly, the non-AP MLD receives FT response frames from the source AP MLD.

[0128] The FT response frame is used in response to the FT request frame. For example, the FT response frame may carry a PTK for communication between the target APMLD and the non-AP MLD.

[0129] After frame exchanges such as FT request frames, remote request frames, remote response frames, and FT response frames, the non-AP MLD and the target AP MLD can successfully establish a pairwise transient key security association (PTKSA).

[0130] Optionally, the non-AP MLD can reserve resources with the target AP MLD by exchanging FT confirm frames (or FT affirmative frames) and FT acknowledgement (ACK) frames (or FT affirmative acknowledgment frames or FT ACK), such as establishing an uplink block acknowledgment session or adding a quality of service (QoS) traffic flow.

[0131] S205: The non-AP MLD sends a reassociation request frame to the target AP MLD.

[0132] Correspondingly, the target AP MLD receives reassociation request frames from the non-AP MLD.

[0133] For example, a non-AP MLD can send a reassociation request frame to a target AP MLD over the air interface, and the target AP MLD can receive the reassociation request frame over the air interface.

[0134] Among them, the reassociation request frame is used to negotiate link operation parameters between the non-AP MLD and the target AP MLD.

[0135] S206: The target AP MLD sends a reassociation response frame to the non-AP MLD.

[0136] Correspondingly, the non-AP MLD receives the reassociation response frame from the target AP MLD.

[0137] For example, the target AP MLD can send a reassociation response frame to the non-AP MLD over the air interface, and the corresponding non-AP MLD can receive the reassociation response frame over the air interface.

[0138] The reassociation response frame can be used to respond to the reassociation request frame. For example, the reassociation response frame may carry link operation parameters between the non-AP MLD and the target AP MLD.

[0139] In one example, if the status code in the reassociation response frame is success, the target AP MLD refreshes the DS mapping. At this time, the non-AP MLD and the target AP MLD change from state 2 to state 4, and the non-AP MLD can delete the key with the source AP MLD.

[0140] In one design, the FT request frame, FT response frame, FT acknowledgment frame, and FT acknowledgment reply frame mentioned above can be FT action frames. For example, FT request frames and FT response frames can be used to negotiate a new PTK and establish a PTKSA. FT acknowledgment frames and FT ACK frames can be used for resource request negotiation. FT acknowledgment frames can be used by a non-AP MLD to request resources, or in other words, the FT acknowledgment frame can be used by a non-AP MLD to request resources from a target AP MLD. FT ACK frames are used to respond to FT acknowledgment frames.

[0141] The FT action frames shown above are merely examples. As the standard progresses, other frames with similar functions may appear in the future. This application does not limit the scope of these frames.

[0142] See Figure 3A An FT action frame may include at least one of the following fields: category, FT action, STA address, target AP address, and FT request frame body. The STA address indicates the MAC address of the non-AP MLD, and the target AP address indicates the MAC address of the target AP MLD.

[0143] The category field indicates the category to which the FT action frame belongs. The FT action field includes the value corresponding to the FT action; different FT action frames have different values ​​for this field. For example, as shown in Table 1:

[0144] Table 1: An example of an FT action field

[0145]

[0146]

[0147] It can be seen that when Figure 3A When a FT action frame is used as an FT request, the value of this FT action field is set to 1. Figure 2 When a middleline frame is used as an FT response, the FT action field is set to 2. This can be used for FT acknowledgment frames and FT acknowledgment response frames mentioned earlier. Figure 3A The format of the FT action frame is different; simply set the FT action field value in Table 1 to the corresponding value.

[0148] The STA address field is set to the media access control (MAC) address of the FTO, and the destination AP address field is set to the MAC address of the destination FTR. If the FTR is a multi-link device, it is set to the corresponding MLD address. The FT request frame body field is used to carry the frame body corresponding to this FT action frame.

[0149] In one implementation, the FT request frame, as shown in Table 2, carries at least one of the following pieces of information in its frame body.

[0150] Table 2: Information carried in the frame body of FT request frames

[0151]

[0152] Figure 3B This is a schematic diagram of the format of the fast BSS transition element (FTE) provided in an embodiment of this application. For example... Figure 3B As shown, the FTE may include at least one of the following: element ID, length, message integrity codes (MIC) control, MIC, a random number provided by the authenticator (such as ANonce), a random number provided by the applicant (such as SNonce), or optional parameter(s).

[0153] Figure 3C This is a schematic diagram of the MDE format provided in an embodiment of this application. For example... Figure 3C As shown, the MDE can include at least one of the following: element ID, length, mobility domain identifier (MDID), or FT capability and policy. The MDID field can be used to indicate the mobile domain ID. The FT capability and policy field can be used to indicate fast BSS transition capability and policy. This FT capability and policy field can include fast BSS transition over DS (FT) or resource request protocol capability. The FT over DS field can be used to indicate whether fast BSS transition over DS is supported, and the resource request protocol capability field can be used to indicate whether resource request protocol is supported. For example, a non-AP MLD can negotiate resources with the target AP MLD through FT acknowledgment frames / FT ACK frames, and with the current AP MLD.

[0154] In one design, refer to Figure 4 This illustrates a schematic diagram of the frame format for an FT response frame. For example... Figure 4 As shown, the FT response frame may include at least one of the following: category, FT action, STA address, target AP address, status code, or FT response frame body. For explanations of each field, please refer to the 802.11 standard, etc., which will not be detailed here. The frame body field is used to carry the frame body corresponding to the FT response frame, as shown in Table 3.

[0155] Table 3: Example of the frame body of an FT response frame

[0156]

[0157] In one design, refer to Figure 5A This shows a schematic diagram of the frame format of the FT confirmation frame. For example... Figure 5A As shown, the FT confirmation frame may include at least one of the following: category, FT action, STA address, target AP address, or FT confirm framebody. For explanations of each field, please refer to the 802.11 standard, etc., which will not be detailed here. The frame body field is used to carry the frame body corresponding to the FT confirmation frame, as shown in Table 4.

[0158] Table 4: An example of the frame body of an FT confirmation frame

[0159]

[0160] In one design, refer to Figure 5B This illustrates a schematic diagram of the FT ACK frame format. For example... Figure 5B As shown, the FTACK frame may include at least one of the following: category, FT action, STA address, target AP address, status code, or FTACK frame body. For explanations of each field, please refer to the 802.11 standard, etc., which will not be detailed here. The frame body field is used to carry the frame body corresponding to the FTACK frame, as shown in Table 5.

[0161] Table 5: Example of the frame body of an FT ACK frame

[0162]

[0163]

[0164] It should be understood that the RIC in the FT confirmation frames shown in Tables 4 and 5 can also be referred to as RIC Request or Resource Request.

[0165] Currently, under the Fast BSS Transfer Protocol, the source AP MLD and the target AP MLD can interact via remote request frames and remote response frames. The frame formats for remote request and remote response frames are shown in Table 6.

[0166] Table 6: Example of a payload format for a remote receiver or remote response.

[0167]

[0168] In the above-mentioned fast BSS transfer process, non-AP MLD often experiences speed drops (i.e., reduced transmission rate).

[0169] Therefore, embodiments of this application provide a communication method. See also... Figure 6 This is an exemplary flowchart of a communication method provided in an embodiment of this application.

[0170] S601: The non-AP MLD sends the first request to the source AP MLD.

[0171] Accordingly, the source AP MLD receives the first request from the non-AP MLD.

[0172] The first request is used to request the detection of the target AP MLD. For example, the first request can be used to obtain information about one or more neighboring AP MLDs of the source AP MLD.

[0173] S602: The source AP MLD sends a fourth request to one or more neighboring AP MLDs.

[0174] Correspondingly, one or more neighboring AP MLDs receive a fourth request from the source AP MLD.

[0175] For example, the source AP MLD can send a fourth request to one or more neighboring AP MLDs via the DS, and the corresponding one or more neighboring AP MLDs can receive the fourth request via the DS. In this embodiment, the fourth request is generated based on the first request. For example, the fourth request can be used to obtain information from one or more neighboring AP MLDs.

[0176] In some embodiments, the source AP MLD can also send a fourth request to one or more neighboring APs. That is, in S602, the source AP MLD can send a fourth request to one or more neighboring AP MLDs, and can also send a fourth request to one or more neighboring APs. For ease of description, AP and AP MLD are collectively referred to as AP MLDs in this document.

[0177] In one possible implementation, the first request can be an FT probe request frame. For example, an FT probe request can be one type of FT action frame, see reference... Figure 3A The frame format implementation shown. Figure 6 In the illustrated embodiment, the target AP address field in the FT probe request frame can indicate the receiving address and can be set to a broadcast address. Therefore, in S602, if the source AP MLD discovers that the target AP address field in the FT probe request frame is set to a broadcast address, the source AP MLD can send a fourth request to one or more neighboring AP MLDs via the DS.

[0178] For example, a broadcast address can be an all-zero element, an all-one element, or other predefined address.

[0179] In one example, an FT probe request frame may carry a probe request multi-link element. This multi-link element may include one or more of the following fields: element ID, length, element ID extension, multi-link control, common info field, and link info field. The multi-link control field may include information (such as a presence bitmap) indicating whether one or more fields in the common info field and / or link info field are present. The common info field may include a common info length field, an AP MLD ID field, and an MLD MAC address field. The link info field may include information about one or more affiliated STAs of a non-AP MLD.

[0180] For example, the multi-link control field may include information indicating whether the AP MLD ID field in the public information field appears. In this embodiment, since the target AP address is a broadcast address, the AP MLD ID presence field can be set to 0 or 1.

[0181] For example, setting the AP MLD ID occurrence field to 0 indicates that the AP MLD ID field does not appear in the public information field, while setting it to 1 indicates that the AP MLD ID appears in the public information field. Conversely, setting the AP MLD ID occurrence field to 1 indicates that the AP MLD ID field does not appear in the public information field, while setting it to 0 indicates that the AP MLD ID appears in the public information field.

[0182] In this embodiment of the application, if the AP MLD ID field indicates that the AP MLD ID appears in the public information field, then the AP MLD ID in the public information field can be set to 255. In the above case, the public information field may also carry the link identifier and / or the MAC address of the affiliated STA. For example, the public information field may carry the link identifier of one or more non-AP MLD links, and / or the MAC address of the affiliated STA corresponding to one or more links.

[0183] Optionally, the fourth request may carry the link identifier of one or more links of the non-AP MLD, and / or the MAC address of the associated STA corresponding to one or more links.

[0184] In this document, the link identifiers of one or more links of a non-AP MLD, and / or the MAC addresses of the associated STAs corresponding to one or more links, can be used by the target AP MLD to obtain the MAC addresses of the associated STAs of a legitimate non-AP MLD. This information is then used by the associated STAs of the non-AP MLD to measure the RSSI of the target AP MLD. This will be explained later and will not be described here.

[0185] Furthermore, in the above scenario, the link information field may or may not appear; that is, the probe request multi-link element may or may not include the link information field. If the link information field appears, the link identifier field can be set to 15, and the complete profile requested field can be set to 1. In some embodiments, if the link information field appears, it may also carry the link identifiers of one or more links and / or the MAC addresses of the associated STAs corresponding to one or more links.

[0186] Based on the above scheme, when the target AP address in the FT probe request frame is a broadcast address, the source AP MLD can send a fourth request to one or more neighboring AP MLDs, thus allowing the source AP MLD to obtain information from one or more neighboring AP MLDs. Furthermore, this application embodiment provides possible scenarios for each field in the FT probe request frame, so that when the target AP address is set to a broadcast address, the source AP MLD can interpret the broadcast address and send a fourth request to one or more neighboring AP MLDs.

[0187] In this embodiment of the application, the link identifier and / or link address in the public information field, and the link identifier and / or link address in the link information field, can be protected by the MIC.

[0188] S603: One or more neighboring APs MLD send a fourth response to the source AP MLD.

[0189] Correspondingly, the source AP MLD receives a fourth response from one or more neighboring AP MLDs.

[0190] For example, one or more neighboring AP MLDs can send a fourth response to the source AP MLD via the DS, and the corresponding source AP MLD can receive the fourth response via the DS. The fourth response can be used to respond to a fourth request. For example, the fourth response can carry information about one or more neighboring AP MLDs. Optionally, the fourth response can carry the link identifiers of one or more links of the non-AP MLD, and / or the MAC addresses of the affiliated STAs corresponding to one or more links.

[0191] S604: The source AP MLD sends a first response to the non-AP MLD.

[0192] Correspondingly, the non-AP MLD receives the first response from the source AP MLD.

[0193] The first response can be used to respond to the first request. For example, the first response can be an FT probe response frame, which can carry information about one or more neighboring AP MLDs.

[0194] In one possible implementation, after receiving a fourth response from one or more neighboring AP MLDs, the source AP MLD can send one or more first responses to the non-AP MLD. See also... Figure 7 This illustrates a frame format for a first response provided in an embodiment of this application.

[0195] The first response may include one or more of the following fields: category, FT action, STA address, target AP address, FTProbe response frame body, or Length of FT Probe Response frame body. The STA address can be understood as the receiving address, i.e., the MLD address of a non-AP MLD; the target AP address can be the MLD address of a neighboring AP MLD; the Length of FT Probe Response frame body field indicates the length of the FT Probe Response frame body field.

[0196] When the source AP MLD sends the fourth responses from multiple neighboring AP MLDs along with a first response to the non-AP MLD, the target AP address, FT probe response framebody, and FT probe response frame body length can be repeated multiple times. Each repetition can represent the fourth response sent by a neighboring AP MLD, which in turn can represent the information of a neighboring AP MLD.

[0197] In some embodiments, the first response may carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links, as described in the relevant description in the first request. Optionally, the first response may carry the link identifiers of one or more links of the neighboring AP and / or the MAC addresses of the associated APs of one or more links.

[0198] S605: The non-AP MLD sends a second request to the source AP MLD.

[0199] Correspondingly, the source AP MLD receives the second request from the non-AP MLD.

[0200] For example, the second request can be used to request negotiation of the PTK between the target AP MLD and the non-AP MLD. For instance, the second request can be an FT request frame.

[0201] In this embodiment of the application, the FT request frame may carry the link identifier of one or more non-AP MLD links and / or the MAC address of one or more affiliated STAs of those links. Optionally, the link identifier of the one or more links and / or the MAC address of the affiliated STAs of those links may be protected by a MIC.

[0202] In one possible implementation, a non-AP MLD can select one or more AP MLDs as the target AP MLD from one or more neighboring AP MLDs. The second request may carry information about the target AP MLD, such as its ID or address.

[0203] S606: The source AP MLD sends the fifth request to the target AP MLD.

[0204] Accordingly, the target AP MLD receives the fifth request from the source AP MLD.

[0205] For example, the fifth request can be used to request the PTK between the target AP MLD and the non-AP MLD. For instance, the fifth request can be a remote request frame. Optionally, the fifth request can carry the link identifier of one or more links of the non-AP MLD and / or the MAC address of the associated STA of one or more links.

[0206] S607: The target AP MLD sends a fifth response to the source AP MLD.

[0207] Correspondingly, the source AP MLD receives the fifth response from the target AP MLD.

[0208] The fifth response can be used to respond to a fifth request. For example, the fifth response can be a remote response frame, carrying the PTK between the target AP MLD and the non-AP MLD. Optionally, the fifth response can carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the affiliated STAs of one or more links. Still optionally, the fifth response can carry the link identifiers of one or more links of the target AP MLD and / or the MAC addresses of the affiliated APs of one or more links.

[0209] S608: The source AP MLD sends a second response to the non-AP MLD.

[0210] Correspondingly, the non-AP MLD receives a second response from the source AP MLD.

[0211] The second response is used to respond to the second request. For example, the second response may be an FT response frame, which may carry the PTK between the target AP MLD and the non-AP MLD.

[0212] In some embodiments, the second response may carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links, as described in the relevant description in the first request. Optionally, the second response may carry the link identifiers of one or more links of the target AP and / or the MAC addresses of the associated APs of one or more links.

[0213] Optional, Figure 6 The illustrated embodiments may also include the following steps S609 to S612.

[0214] S609: The non-AP MLD sends a third request to the source AP MLD.

[0215] Correspondingly, the source AP MLD receives a third request from the non-AP MLD.

[0216] The third request can be used to request the establishment of a transmission link between the non-AP MLD and the target AP MLD. For example, the third request can be an FT multi-link setup request.

[0217] Optionally, the third request may carry the link identifiers of one or more non-AP MLD links and / or the MAC addresses of the associated STAs corresponding to one or more links. Optionally, the link identifiers of the one or more links and / or the MAC addresses of the associated STAs corresponding to one or more links may be protected by a MIC.

[0218] S610: The source AP MLD sends a sixth request to the target AP MLD.

[0219] Accordingly, the target AP MLD receives the sixth request from the source AP MLD.

[0220] For example, the source AP MLD can send a sixth request to the target AP MLD through the DS, and the corresponding target AP MLD can receive the sixth request through the DS.

[0221] The sixth request can be used to request the establishment of a transmission link between the non-AP MLD and the target AP MLD. Optionally, the sixth request can carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links.

[0222] S611: The target AP MLD sends a sixth response to the source AP MLD.

[0223] Correspondingly, the source AP MLD receives the sixth response from the target AP MLD.

[0224] For example, the target AP MLD can send a sixth response to the source AP MLD via DS, and the corresponding source AP MLDK can receive the sixth response via DS.

[0225] The sixth response can be used to respond to the sixth request. Optionally, the sixth response may carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links. Alternatively, the sixth response may carry the link identifiers of one or more links of the target AP MLD and / or the MAC addresses of the associated APs of one or more links.

[0226] S612: The source AP MLD sends a third response to the non-AP MLD.

[0227] Correspondingly, the non-AP MLD receives a third response from the source AP MLD.

[0228] The third response can be used to respond to a third request. For example, the third response can be an FT multi-link setup response.

[0229] In some embodiments, the third response may carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links, as described in the relevant description in the first request. Optionally, the third response may carry the link identifiers of one or more links of the target AP MLD and / or the MAC addresses of the associated APs of one or more links.

[0230] After frame interactions from 609 to 612, the non-AP MLD and the target AP MLD can establish multiple transmission links.

[0231] In some embodiments, the second and third requests, and the second and third responses can be combined. Similarly, the fifth and sixth requests, and the fifth and sixth responses can be combined. That is, the key negotiation function and the multi-link establishment function are combined into a single frame for frame interaction. For example, the RSN, MDE, FTE RSNXE, and Basic Multi-link element carried in the second request can be carried in the third request, while the content carried in the second response can be carried in the third response. The establishment of PTKSA and negotiation of PTK are achieved through the third request and the third response. Optionally, changes to the DS mapping may also be included.

[0232] For example, the second and third requests can be combined into an eighth request. The non-AP MLD can send the eighth request to the source AP MLD. This eighth request is used to request the establishment of a PTK and / or distribution of a multicast temporary key between the non-AP MLD and the target AP MLD, and also to request the establishment of a multilink between the non-AP MLD and the target AP MLD. The source AP MLD can send a ninth request to the target AP MLD, such as through a DS. This ninth request can be generated based on the eighth request. This ninth request is used to request the establishment of a PTK and / or distribution of a multicast temporary key between the non-AP MLD and the target AP MLD, and also to request the establishment of a multilink between the non-AP MLD and the target AP MLD.

[0233] The target AP MLD can then send a ninth response to the source AP MLD, such as via DS. This ninth response can be used to respond to a ninth request, and may carry information about the PTK and / or multicast temporary key between the non-AP MLD and the target AP MLD. The source AP MLD can also send an eighth response to the non-AP MLD, which responds to an eighth request and may carry information about the PTK and / or multicast temporary key between the non-AP MLD and the target AP MLD.

[0234] Optionally, the eighth and ninth requests may carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links, as described in the relevant descriptions of the second, third, fifth, and sixth requests. Alternatively, the ninth and eighth responses may carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links, as described in the relevant descriptions of the second, third, fifth, and sixth responses. Alternatively, the ninth and eighth responses may carry the link identifiers of one or more links of the target AP MLD and / or the MAC addresses of the associated APs corresponding to one or more links, as described in the relevant descriptions of the second, third, fifth, and sixth responses.

[0235] S613: The non-AP MLD sends a seventh request to the target AP MLD to request a change in the DS mapping and / or a context transfer.

[0236] Correspondingly, the target AP MLD can receive the seventh request from the non-AP MLD.

[0237] Specifically, the non-AP MLD can measure the received signal strength indication (RSSI) of the target AP MLD before S614. For example, the non-AP MLD can send a first frame, and the target AP MLD can send a second frame. For instance, the handover conditions may include when the RSSI of the target AP MLD's first access point is higher than a certain threshold, or when the target AP MLD's RSSI is higher than a preset RSSI value of a link of the source AP MLD, or when the target AP MLD's RSSI is higher than a certain threshold, etc. These handover conditions can be implemented with reference to those in related technologies for BSS transfer.

[0238] For example, the seventh request could be a reassociation request frame. As another example, the seventh request could be a roaming request frame.

[0239] S614: The target AP MLD sends a seventh response to the non-AP MLD.

[0240] Correspondingly, the non-AP MLD receives the seventh response from the target AP MLD.

[0241] The seventh response can be used to respond to a seventh request. For example, the seventh response can be a reassociation response frame. As another example, the seventh response can be a roaming response frame.

[0242] Through frame exchanges in S613 and S614, the non-AP MLD can be associated with the target AP MLD. In one example, the seventh request in S613 and the seventh response in S614 can be encrypted via PTK between the non-AP MLD and the target AP MLD.

[0243] In one possible implementation, the target AP MLD and the source AP MLD can also perform context transfer, with the target AP MLD obtaining the context of the non-AP MLD from the source AP MLD. For example, the target AP MLD can send a context transfer request to the source AP MLD, requesting the transfer of the non-AP MLD's context. The source AP MLD can send a context transfer response to the target AP MLD to transfer the non-AP MLD's context. Exemplarily, the context transfer response can carry the non-AP MLD's context.

[0244] Based on the above scheme, non-AP MLDs can obtain information about neighboring AP MLDs by using DS to detect the source AP MLD. Figure 6 The method shown associates the non-AP MLD with the target AP MLD without interrupting data transmission between the non-AP MLD and the source AP MLD during the association process, thus improving the roaming performance of the non-AP MLD.

[0245] In this embodiment, fields need to be added to the public information field and link information field in the first request / first response to carry the link identifier of one or more links of the non-AP MLD and / or the MAC address of the associated STA corresponding to one or more links. Optionally, a corresponding presence bit can also be added to indicate whether the corresponding field appears.

[0246] Similarly, for third requests / responses, a field needs to be added to the common information field of the basic multi-link element to carry the link identifier of one or more links of the non-AP MLD and / or the MAC address of the associated STA corresponding to one or more links. Optionally, a corresponding presence bit can also be added to indicate whether the MAC address of the associated STA is present. For example, 1 bit can be added to the presence bitmap subfield to indicate whether the MAC address of the associated STA is present.

[0247] In some embodiments, the link identifiers of one or more of the aforementioned links and / or the MAC addresses of the associated STAs corresponding to one or more links may be protected by the MIC. The following description uses a third request and a third response as examples.

[0248] For the third request, the MIC in the FTE should be calculated based on the concatenation of the following information:

[0249] — MAC address of FTO (6 octets): The MAC address of FTO can be the MAC address of a non-AP MLD.

[0250] — MAC address of the target FTR (6 octets): The MAC address of the target FTR can be the MAC address of the target AP MLD.

[0251] — The transaction sequence number is set to 3.

[0252] —RSNE.

[0253] —MDE, Mobile Domain Information Element.

[0254] —Fast BSS transition element: This field is set to 0 when calculating MIC.

[0255] —Resource information container (RIC) request content (RCI field appears).

[0256] —RSNXE (RSNXE field appears).

[0257] —If the third request carries a Basic Multi-link element, the MAC addresses of the non-AP STAs are concatenated in ascending order of their link IDs;

[0258] For the third response, the MIC in the FTE should be calculated based on the concatenation of the following information:

[0259] – The MAC address of FTO.

[0260] – The MAC address of the target FTR.

[0261] – The transaction sequence number is set to 4.

[0262] –RSNE (if the third response does not carry the underlying multilink element).

[0263] – If the third response carries a Basic Multi-link element, the RSNEs are concatenated in ascending order of their link IDs.

[0264] –MDE: Mobile Domain Information Element.

[0265] – For fast BSS transfer elements, this field is set to 0 when calculating MIC.

[0266] – The content of the resource information container response (resource information container fields appear).

[0267] –RSNXE (The third response does not carry the basic multi-link element)

[0268] – If the third response carries a Basic Multi-link element, RSNXEs are concatenated in ascending order of their link IDs.

[0269] – If the third response carries a Basic Multi-link element, the MAC addresses of the APs are concatenated in ascending order of their link IDs.

[0270] Currently, methods for measuring the RSSI of a target AP MLD can include receiving beacon frames from the target AP MLD via a non-AP MLD. However, the transmission period for beacon frames is typically 100 milliseconds, thus requiring a relatively long time to measure the RSSI of the target AP MLD.

[0271] In another approach, the non-AP MLD can send a probe request frame to the target AP MLD, requesting the target AP MLD to send a probe response frame. If the target AP MLD sends a probe response frame, the non-AP MLD can then measure the target AP MLD's RSSI. However, the probe request and probe response frames are management frames, requiring more information. Furthermore, because they are management frames, the non-AP MLD, upon receiving the probe request frame, needs to reply with an ACK after SIFS, and then re-contact the channel before replying with a probe response frame. The non-AP MLD also needs to wait for SIFS after receiving the probe response frame before replying with an ACK. This measurement method takes longer.

[0272] Therefore, embodiments of this application provide a communication method. See also... Figure 8 The following is an exemplary flowchart of a communication method provided in an embodiment of this application, which may include the following steps.

[0273] S801: The non-AP MLD sends the first frame to the target AP MLD on the first link.

[0274] Correspondingly, the target AP MLD can receive the first frame from the non-AP MLD on the first link.

[0275] The first frame can be used to request the target AP MLD to send a second frame on the first link.

[0276] S802: The target AP MLD sends the second frame to the non-AP MLD on the first link.

[0277] Correspondingly, the non-AP MLD receives the second frame from the target AP MLD on the first link.

[0278] The second frame can be used to measure the RSSI of the first link, and / or it can be used to establish synchronization between the first STA and the first AP. For example, the first STA can be a subsidiary STA corresponding to the first link in a non-AP MLD, and the first AP can be a subsidiary AP corresponding to the first link in a target AP MLD.

[0279] Figure 8 In the embodiment shown, the time interval between the end time of the first frame and the start time of the second frame is SIFS.

[0280] Based on the above scheme, compared with the methods for measuring RSSI in related technologies, Figure 8The method for measuring RSSI in the illustrated embodiment is more time-efficient.

[0281] In one example, see Figure 9A The first frame can be NDPA, and the second frame can be NDP. See another example. Figure 9B The first frame can be NDPR, and the second frame can include NDPA and NDP. The time interval between the end time of NDPA and the start time of NDP is SIFS. See another example. Figure 9C The first frame can be an initial control frame (ICF), and the second frame can be an initial control response (ICR) frame. In the example above, there can be one or more NDPs. Optionally, the second frame can also be a management frame (not shown in the figure).

[0282] The RSSI measurement process described above may introduce security risks, such as attackers using NDP to perceive the surrounding environment, including personnel detection. Therefore, embodiments of this application provide operating rules to mitigate these security risks. For example, the operating rules may include one or more of the following.

[0283] Rule 1: The first frame occupies a bandwidth of 20MHz and is carried on the primary 20MHz channel of the first link. And / or, the second frame occupies a bandwidth of 20MHz and is carried on the primary 20MHz channel of the first link.

[0284] Based on rule one above, the bandwidth occupied by the first and / or second frames can be reduced, avoiding excessive bandwidth usage by the first and / or second frames, which would allow attackers to use the first and / or second frames to perceive the surrounding environment and reduce security risks.

[0285] Rule 2: The address of the first STA, if the MAC address of the first STA is in the whitelist stored by the target AP MLD. After receiving the first frame, the target AP MLD can verify whether the address of the first STA is stored in the whitelist. If the address of the first STA is stored in the whitelist, the target AP MLD can send the second frame after SIFS. If the address of the first STA is not stored in the whitelist, the target AP MLD can discard the first frame.

[0286] In one possible implementation, the whitelist can be accessed via... Figure 6The whitelist obtained as shown in the illustrated embodiments can be obtained from a first request, a second request, or a third request. For example, if the non-AP MLD and the target AP MLD have exchanged a first request and a first response, the whitelist may include the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links, carried in the first request. Similarly, if the non-AP MLD and the target AP MLD have exchanged a second request and a second response, the whitelist may include the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links, carried in the second request. And if the non-AP MLD and the target AP MLD have exchanged a third request and a third response, the whitelist may include the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links, carried in the third request.

[0287] The following is a detailed explanation of Rule 2.

[0288] For example, the sending address of the first frame is the address of the first STA (such as the MAC address of the first STA), and the receiving address of the first frame is the address of the first AP (such as the MAC address of the first AP). The first frame satisfies one or more of the following:

[0289] 1. The non-AP MLD and the target AP MLD have exchanged the first request and the first response.

[0290] The first request carries the link identifier of one or more links of the non-AP MLD and / or the MAC address of the associated STA corresponding to one or more links. This first request is used to request the probe of the target AP MLD. After receiving the first frame from the non-AP MLD, if the target AP MLD determines that the address of the first STA appeared in the first request (optionally also in the first response), and the target AP MLD has already interacted with the non-AP MLD of the first STA through the first request and first response, it can send a second frame after SIFS. It should be understood that the target AP MLD and the non-AP MLD of the first STA can interact through the source AP MLD and DS through the first request and first response, which can be referred to as... Figure 6 The relevant descriptions in the illustrated embodiments will not be repeated here. If the address of the first STA did not appear in the first request, the target AP MLD may discard the first frame.

[0291] In other words, the target AP MLD will only respond with a second frame if the non-AP MLD has detected the target AP MLD using the DS-based (over the DS) method.

[0292] 2. The non-AP MLD and the target AP MLD have exchanged a second request and a second response.

[0293] The second request carries the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links. This second request is used to request PTK between the non-AP MLD and the target AP MLD. After receiving the first frame from the non-AP MLD, if the target AP MLD determines that the address of the first STA appeared in the second request (optionally also in the second response), and that the target AP MLD and the non-AP MLD of the first STA have exchanged the second request and second response, it can send the second frame after SIFS. It should be understood that the target AP MLD and the non-AP MLD of the first STA can exchange the second request and second response through the source AP MLD and DS, as can be seen in [reference needed]. Figure 6 The relevant descriptions in the illustrated embodiments will not be repeated here. If the address of the first STA did not appear in the second request, the target AP MLD may discard the first frame.

[0294] In other words, the target AP MLD will only reply with a second frame if the non-AP MLD has negotiated the key with the target AP MLD using the DS-based method.

[0295] 3. The non-AP MLD and the target AP MLD have exchanged third requests and third responses.

[0296] The third request carries the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links. This third request is used to request the establishment of a multi-link between the non-AP MLD and the target AP MLD. After receiving the first frame from the non-AP MLD, if the target AP MLD determines that the address of the first STA appeared in the third request (optionally also in the third response), and that the target AP MLD and the non-AP MLD of the first STA have exchanged third request and third response information, it can send a second frame after SIFS. It should be understood that the target AP MLD and the non-AP MLD of the first STA can exchange third request and third response information through the source AP MLD and DS, as can be found in [reference needed]. Figure 6The relevant descriptions in the illustrated embodiments will not be repeated here. If the address of the first STA did not appear in the third request, the target AP MLD may discard the first frame.

[0297] In other words, the target AP MLD will only respond with a second frame if the non-AP MLD establishes a multi-link with the target AP MLD using the DS-based method.

[0298] 4. The non-AP MLD and the target AP MLD have exchanged the eighth request and the eighth response.

[0299] The eighth request may carry the link identifiers of one or more links of the non-AP MLD and / or the MAC addresses of the associated STAs corresponding to one or more links. This eighth request is used to request the establishment of a PTK between the non-AP MLD and the target AP MLD, and to establish a link between them. After receiving the first frame from the non-AP MLD, if the target AP MLD determines that the address of the first STA appeared in the eighth request (optionally also in the eighth response), and that the target AP MLD and the non-AP MLD of the first STA have exchanged the eighth request and eighth response, it can send a second frame after SIFS. It should be understood that the target AP MLD and the non-AP MLD of the first STA can exchange the eighth request and eighth response through the source AP MLD and DS, as can be seen in [reference needed]. Figure 6 The relevant descriptions in the illustrated embodiments will not be repeated here. If the address of the first STA did not appear in the eighth request, the target AP MLD may discard the first frame.

[0300] In other words, the target AP MLD will only respond with a second frame if the non-AP MLD negotiates PTK and establishes multiple links with the target AP MLD using the DS-based method.

[0301] Based on rule two above, the target AP MLD will only reply with a second frame if the non-AP MLD has probed the target AP MLD using the DS-based method, negotiated a key with the target AP MLD, or established a multi-link with the target AP MLD, thereby reducing security risks.

[0302] Optionally, in NDPR and NDPA, if the receive address is set to the MLD address and the send address is also set to the MLD address, then the MAC address of the auxiliary STA does not need to be carried in the first request / first response, second request / second response, and third request / third response. The target AP MLD can determine whether to reply with a second frame based on the MLD address of the non-AP MLD. Refer to the relevant explanation in Rule 2 above and replace the MAC address of the auxiliary STA with the MLD address; this will not be elaborated further here.

[0303] In one possible implementation, if both the first AP and the first STA support enhanced long range (ELR), the first frame can be an ELR physical protocol data unit (PPDU), and the second frame can also be an ELR PPDU. In another possible implementation, if both the first AP and the first STA support UHR, the first frame can be a UHR PPDU, and the second frame can also be a UHR PPDU. Based on these schemes, ELR PPDUs or UHR PPDUs can improve the measurement performance of RSSI.

[0304] In this embodiment, the second frame may carry synchronization time information of the first AP, such as part or all of the timestamp of the first AP, and the offset of the time synchronization function (TSF) of the first AP. This synchronization time information can be used for time synchronization between the first AP and the first STA. For example, when the second frame includes NDPA and NDP, the NDPA may carry the synchronization time information of the first AP. As another example, the second frame may be a management frame, which may carry the synchronization time information of the first AP. Optionally, the second frame may also carry transmit power information.

[0305] In one possible implementation, the non-AP MLD can also obtain the synchronization time information of the target AP MLD's affiliated APs through other methods, and then synchronize its time with the target AP MLD's affiliated APs. These will be described in detail below.

[0306] Method 1: The source AP MLD can include the synchronization time information of one or more neighboring AP MLDs in the first response (FT probe response).

[0307] For example, since the target AP MLD introduces a random delay when sending the fourth response to the source AP MLD via DS, if the source AP MLD knows the TSF offset of the neighboring AP, then when the source AP MLD sends the first response to the non-AP MLD, it can rewrite the timestamp field in the fourth response, setting it to the current timestamp of the neighboring AP. This current timestamp can be determined based on the TSF offset and random delay between the source AP MLD and the target AP MLD. If the source AP MLD does not know the TSF offset of the neighboring AP, then the timestamp field in the fourth response is set to 0.

[0308] Method 2: Non-AP MLDs can obtain the synchronization time information of neighboring AP MLDs through the neighbor report element.

[0309] For example, a non-AP MLD can obtain the synchronization time information of a neighboring AP MLD through the neighbor report element in a BSS transition management (BTM) response frame or a neighbor report response frame.

[0310] For example, prior to S601, a non-AP MLD can send a BTM request frame to the source AP MLD to request a BSS transfer. The source AP MLD can send a BTM response frame to the non-AP MLD, which may carry a neighbor report element, which may carry information about one or more neighbor AP MLDs of the source AP MLD.

[0311] For example, prior to S601, a non-AP MLD could send a neighbor report request frame to the source AP MLD to request information about its neighboring AP MLDs. The source AP MLD could send a neighbor report response frame to the non-AP MLD, which could carry a neighbor report element, which could carry information about one or more of the source AP MLD's neighboring AP MLDs.

[0312] Optionally, non-AP MLDs can also obtain the synchronization time information of neighboring APs by reducing the neighbor report element.

[0313] Method 3: Carry the synchronization time information of the first AP in the seventh response (roaming response or reassociation response).

[0314] Since the seventh request is sent from the non-AP MLD to the target AP MLD via the air interface, and the seventh response is also sent from the target AP MLD to the non-AP MLD via the air interface, the target AP MLD can directly carry the synchronization time information of the first AP in the seventh response.

[0315] In this scenario, the non-AP MLD negotiates or reserves resources with the target AP MLD via the DS before the first AP synchronizes its time with the first STA. Therefore, when the non-AP MLD negotiates or reserves resources with the target AP MLD via the DS, such as during resource reservation or negotiation between the source AP MLD and the non-AP MLD (e.g., negotiation of service start time and target wake time (TWT) within QoS characteristic elements during stream classification service (SCS) negotiation), the source AP MLD can indicate a relative time to the non-AP MLD, rather than an absolute time. This allows the target AP MLD to determine the accurate service start time and target wake time based on this relative time after a context transition.

[0316] Based on the above methods one to three, the method of non-AP MLD obtaining the synchronization time information of target AP MLD in the embodiments of this application is shown, so that non-AP MLD and target AP MLD can synchronize time.

[0317] Based on the same concept, this application provides a communication device. Figure 10This is a schematic block diagram of a communication device 1000 provided in an embodiment of this application. The communication device 1000 can correspondingly implement the functions or steps implemented by the non-APMLD, source AP MLD, or target AP MLD in the various method embodiments described above. The communication device may include a processing unit 1001 and a transceiver unit 1002. Optionally, it may also include a storage unit, which can be used to store instructions (code or program) and / or data. The processing unit 1001 and the transceiver unit 1002 can be coupled to the storage unit; for example, the processing unit 1001 can read instructions (code or program) and / or data from the storage unit to implement the corresponding method. The aforementioned units can be set independently or partially or completely integrated.

[0318] Optionally, the transceiver unit 1002 may include a transmitting unit and a receiving unit. The transmitting unit may be used to perform all transmitting operations performed by the communication device 1000, and the receiving unit may be used to perform all receiving operations performed by the communication device 1000.

[0319] In some possible implementations, the communication device 1000 can correspondingly implement the behavior and functions of the non-AP MLD, etc., in the above method embodiments. For example, the communication device 1000 can be a non-AP MLD, or a component (e.g., a chip or circuit) applied in a non-AP MLD. The transceiver unit 1002 can be used to perform... Figure 6 The illustrated embodiment represents all receive or transmit operations performed by non-APMLD. For example... Figure 6 S601 and S604 in the illustrated embodiments, and / or other processes used to support the technology described herein; wherein, processing unit 1001 is used to perform, for example Figure 6 The embodiments shown include all operations performed by the non-AP MLD except for the send and receive operations.

[0320] For example, transceiver unit 1002 is configured to send a first frame to a target access point multi-link device on the first link. The first frame is used to request the target access point multi-link device to send a second frame on the first link. The time interval between the end time of the first frame and the start time of the second frame is SIFS. Transceiver unit 1002 is also configured to receive a second frame from the target access point multi-link device on the first link. The second frame is used to measure the RSSI of the first link of the target access point multi-link device and / or for a non-access point multi-link device to establish synchronization with a first access point corresponding to the first link. The first access point is a secondary access point corresponding to the target access point multi-link device on the first link. Processing unit 1001 is configured to measure the RSSI of the first link and / or establish synchronization with the first access point.

[0321] In some possible implementations, the communication device 1000 can correspondingly implement the behavior and functions of the target AP MLD in the above method embodiments. For example, the communication device 1000 can be the target AP MLD, or it can be a component (e.g., a chip or circuit) applied in the target AP MLD. The transceiver unit 1002 can be used to perform... Figure 6 The illustrated embodiment represents all receive or transmit operations performed by the target AP MLD. For example... Figure 6 S601 and S602 in the illustrated embodiments, and / or other processes used to support the technology described herein; wherein, processing unit 1001 is used to perform, for example Figure 6 The illustrated embodiment includes all operations performed by the target APMLD except for send and receive operations.

[0322] For example, transceiver unit 1002 is used to receive a first frame from a non-access point multi-link device on the first link. The first frame is used to request the target access point multi-link device to send a second frame on the first link. Processing unit 1001 is used to generate the second frame, where the time interval between the end time of the first frame and the start time of the second frame is SIFS. The second frame is used to measure the RSSI of the first link of the target access point multi-link device and / or to establish synchronization between the non-access point multi-link device and the first access point corresponding to the first link. The first access point is the auxiliary access point corresponding to the target access point multi-link device on the first link. Transceiver unit 1002 also sends the second frame to the non-access point multi-link device on the first link.

[0323] In some possible implementations, the communication device 1000 can correspondingly implement the behavior and functions of the source AP MLD in the above method embodiments. For example, the communication device 1000 can be the source AP MLD, or it can be a component (e.g., a chip or circuit) applied in the source AP MLD. The transceiver unit 1002 can be used to perform... Figure 6 The illustrated embodiment represents all receive or transmit operations performed by the source AP MLD. For example... Figure 6 S602 and S603 in the illustrated embodiments, and / or other processes used to support the technology described herein; wherein, processing unit 1001 is used to perform, for example Figure 6 The illustrated embodiment includes all operations performed by the source AP MLD except for send and receive operations.

[0324] For example, transceiver unit 1002 is used to receive a first request from a non-access point multilink device, wherein the first field in the first request is a broadcast address. The first request is used to probe the target access point multilink device. Processing unit 1001 is used to generate a fifth request based on the first request, wherein the fifth request is used to probe the target access point multilink device. Transceiver unit 1002 is also used to send the fifth request to the target access point multilink device.

[0325] For details regarding the operations performed by the processing unit 1001 and the transceiver unit 1002, please refer to the relevant descriptions in the foregoing method embodiments.

[0326] It should be understood that the processing unit 1001 in the embodiments of this application can be implemented by a processor or processor-related circuit components, and the transceiver unit 1002 can be implemented by a transceiver or transceiver-related circuit components or a communication interface.

[0327] Based on the same concept, such as Figure 11 As shown in the figure, this application embodiment provides a communication device 1100. The communication device 1100 includes a processor 1110. Optionally, the communication device 1100 may further include a memory 1120 for storing instructions executed by the processor 1110, or storing input data required by the processor 1110 to execute the instructions, or storing data generated after the processor 1110 executes the instructions. The processor 1110 can implement the method shown in the above method embodiment through the instructions stored in the memory 1120.

[0328] Based on the same concept, such as Figure 12 As shown, this application embodiment provides a communication device 1200, which may be a chip or a chip system. Optionally, in this application embodiment, the chip system may be composed of chips, or may include chips and other discrete devices.

[0329] The communication device 1200 may include at least one processor 1210 coupled to a memory, which may optionally be located within or outside the device. For example, the communication device 1200 may also include at least one memory 1220. The memory 1220 stores computer programs, configuration information, computer programs or instructions, and / or data necessary for implementing any of the above embodiments; the processor 1210 may execute the computer programs stored in the memory 1220 to perform the methods in any of the above embodiments.

[0330] The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1210 may operate in conjunction with the memory 1220. This embodiment does not limit the specific connection medium between the transceiver 1230, processor 1210, and memory 1220.

[0331] The communication device 1200 may also include a transceiver 1230, through which the communication device 1200 can exchange information with other devices. The transceiver 1230 can be a circuit, a bus, a transceiver unit, or any other device that can be used for information exchange, or a signal transceiver unit. Figure 12 As shown, the transceiver 1230 includes a transmitter 1231, a receiver 1232, and an antenna 1233. Furthermore, when the communication device 1200 is a chip-based device or circuit, the transceiver in the communication device 1200 can also be an input / output circuit and / or a communication interface, capable of inputting data (or receiving data) and outputting data (or transmitting data). The processor is an integrated processor, a microprocessor, or an integrated circuit, and the processor can determine the output data based on the input data.

[0332] In one possible implementation, the communication device 1200 can be applied to a non-AP MLD. Specifically, the communication device 1200 can be a non-AP MLD or a device capable of supporting the non-AP MLD to perform the functions of any of the above-mentioned embodiments. The memory 1220 stores the necessary computer programs, computer programs or instructions and / or data for implementing the functions of the non-AP MLD in any of the above embodiments. The processor 1210 can execute the computer program stored in the memory 1220 to complete the method of non-AP MLD execution in any of the above embodiments.

[0333] In one possible implementation, the communication device 1200 can be applied to the target AP MLD. Specifically, the communication device 1200 can be the target AP MLD itself, or it can be any device capable of supporting the target AP MLD in implementing the functions of the target AP MLD in any of the above embodiments. The memory 1220 stores the necessary computer programs, computer programs or instructions and / or data for implementing the functions of the target AP MLD in any of the above embodiments. The processor 1210 can execute the computer programs stored in the memory 1220 to complete the methods executed by the target AP MLD in any of the above embodiments.

[0334] In one possible implementation, the communication device 1200 can be applied to the source AP MLD. Specifically, the communication device 1200 can be the source AP MLD itself, or it can be any device capable of supporting the source AP MLD in implementing the functions of the source AP MLD in any of the above embodiments. The memory 1220 stores the necessary computer programs, computer programs or instructions and / or data for implementing the functions of the source AP MLD in any of the above embodiments. The processor 1210 can execute the computer programs stored in the memory 1220 to complete the method of executing the source AP MLD in any of the above embodiments.

[0335] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0336] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory can also be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store computer programs, computer program or instruction and / or data.

[0337] Based on the above embodiments, see Figure 13 This application embodiment also provides another communication device 1300, including: an input / output interface 1310 and a logic circuit 1320; the input / output interface 1310 is used to receive code instructions and transmit them to the logic circuit 1320; the logic circuit 1320 is used to run the code instructions to execute the method of non-AP MLD, target APMLD or source AP MLD execution in any of the above embodiments.

[0338] Optionally, the input / output interface 1310 can be an on-chip interface, and the logic circuit 1320 can be one or more processors. Optionally, the one or more processors can be located inside or outside the device.

[0339] The following provides a detailed description of the operations performed by this communication device when applied to a non-AP MLD, target AP MLD, or source AP MLD.

[0340] In an optional implementation, the communication device 1300 can be applied to a non-AP MLD to perform the methods described above for non-AP MLDs, specifically as described in the preceding examples. Figure 6 The method performed by the non-AP MLD in the illustrated embodiment.

[0341] For example, input / output interface 1310 is used to send a first frame to the target access point multilink device on the first link. The first frame is used to request the target access point multilink device to send a second frame on the first link. The time interval between the end time of the first frame and the start time of the second frame is SIFS. Input / output interface 1310 is also used to receive a second frame from the target access point multilink device on the first link. The second frame is used to measure the RSSI of the first link of the target access point multilink device and / or for a non-access point multilink device to establish synchronization with the first access point corresponding to the first link. The first access point is the auxiliary access point corresponding to the target access point multilink device on the first link. Logic circuit 1320 is used to measure the RSSI of the first link and / or establish synchronization with the first access point.

[0342] Since the communication device 1300 provided in this embodiment can be applied to non-AP MLD to complete the above-described method for executing non-AP MLD, the technical effects it can achieve can be referred to the above-described method embodiment, and will not be repeated here.

[0343] In an optional implementation, the communication device 1300 can be applied to the target AP MLD to execute the method performed by the target AP MLD, specifically as described above. Figure 6 The method performed by the target AP MLD in the illustrated embodiment.

[0344] For example, input / output interface 1310 is used to receive a first frame from a non-access point multilink device on the first link. The first frame is used to request the target access point multilink device to send a second frame on the first link. Logic circuit 1320 is used to generate the second frame, where the time interval between the end time of the first frame and the start time of the second frame is SIFS. The second frame is used to measure the RSSI of the first link of the target access point multilink device and / or to establish synchronization between the non-access point multilink device and the first access point corresponding to the first link, where the first access point is the auxiliary access point corresponding to the target access point multilink device on the first link. Input / output interface 1310 is also used to send the second frame to the non-access point multilink device on the first link.

[0345] Since the communication device 1300 provided in this embodiment can be applied to the target AP MLD to complete the above-described method for executing the target AP MLD, the technical effects it can achieve can be referred to the above-described method embodiment, and will not be repeated here.

[0346] In one optional implementation, the communication device 1300 can be applied to the source AP MLD to execute the methods performed by the source AP MLD, specifically as described above. Figure 6 The method executed by the source AP MLD in the illustrated embodiment.

[0347] For example, input / output interface 1310 is used to receive a first request from a non-access point multilink device, wherein the first field of the first request is a broadcast address. The first request is used to probe a target access point multilink device. Logic circuit 1320 is used to generate a fifth request based on the first request, the fifth request being used to probe the target access point multilink device. Input / output interface 1310 is also used to send the fifth request to the target access point multilink device.

[0348] Since the communication device 1300 provided in this embodiment can be applied to the source AP MLD to complete the above-described source AP MLD execution method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.

[0349] Based on the above embodiments, this application also provides a communication system. This communication system includes at least one communication device applied to a non-AP MLD, at least one communication device applied to a target AP MLD, and at least one communication device applied to a source AP MLD. The technical effects obtained can be referred to the above method embodiments, and will not be repeated here.

[0350] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program or instructions. When the instructions are executed, the method for executing the non-AP MLD, target AP MLD, or source AP MLD in any of the above embodiments is implemented. The computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.

[0351] To achieve the above Figures 10-13 In addition to the functions of the communication device, this application also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the non-AP MLD, target AP MLD, or source APMLD in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing the computer programs or instructions and data necessary for the communication device.

[0352] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0353] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by a computer program or instructions. Such computer programs or instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0354] These computer programs or instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0355] These computer programs or instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0356] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A communication method, characterized in that, include: A non-access point multi-link device sends a first frame to a target access point multi-link device on a first link. The first frame is used to request the target access point multi-link device to send a second frame on the first link. The time interval between the end time of the first frame and the start time of the second frame is the short frame interval (SIFS). The non-access point multi-link device receives the second frame from the target access point multi-link device on the first link. The second frame is used to measure the Received Signal Strength Indicator (RSSI) of the first link of the target access point multi-link device and / or the second frame is used for the non-access point multi-link device to establish synchronization with the first access point corresponding to the first link. The first access point is the auxiliary access point corresponding to the target access point multi-link device on the first link.

2. The method according to claim 1, characterized in that, The first frame occupies a bandwidth of 20MHz and is carried on the main 20MHz channel of the first link.

3. The method according to claim 1 or 2, characterized in that, The second frame occupies a bandwidth of 20MHz and is carried on the main 20MHz channel of the first link.

4. The method according to any one of claims 1 to 3, characterized in that, The first frame is sent from the address of the first station corresponding to the first link, where the first station is an auxiliary station of the non-access point multi-link device on the first link. The first frame is received from the address of the first access point, and the first frame satisfies one or more of the following: Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the first request and first response interaction with the target access point multi-link device. The first request is used to probe the target access point multi-link device and carries the address of the first site and / or the link identifier of the first link. The first response is used to feed back the information of the target access point multi-link device and carries the address of the first access point and / or the link identifier of the first link. or, Before sending the first frame on the first link, the non-access point multi-link device has successfully completed the sending of a second request and a second response with the target access point multi-link device. The second request and the second response are used to establish a temporary key for communication between the non-access point multi-link device and the target access point multi-link device. The second request carries the address of the first site and / or the link identifier of the first link, and the second response carries the address of the first access point and / or the link identifier of the first link. or, Before sending the first frame on the first link, the non-access point multi-link device has successfully completed a third request and a third response interaction with the target access point multi-link device. The third request and the third response are used to establish a first link and / or resource reservation between the non-access point multi-link device and the target access point multi-link device. The third request carries the address of the first site and / or the link identifier of the first link, and the third response carries the address of the first access point and / or the link identifier of the first link.

5. The method according to any one of claims 1 to 4, characterized in that, The first frame is an enhanced long-range physical protocol data unit or an ultra-robust physical protocol data unit.

6. The method according to any one of claims 1 to 5, characterized in that, The second frame is an enhanced long-range physical protocol data unit or an ultra-robust physical protocol data unit.

7. The method according to any one of claims 1 to 4, characterized in that, The first frame is an empty data packet request frame, and the second frame includes an empty data packet notification frame and an empty data packet.

8. The method according to any one of claims 1 to 4, characterized in that, The first frame is the initial control frame, and the second frame is the initial control response frame.

9. The method according to any one of claims 1 to 8, characterized in that, The second frame carries the synchronization time information of the first access point, which is used for the first site to synchronize time with the first access point.

10. The method according to claim 9, characterized in that, The synchronization time information includes part or all of the timestamp information of the first access point, or the synchronization time information includes the timed synchronization function offset of the first access point.

11. The method according to claim 4, characterized in that, The first field in the first request is a broadcast address, which is used by the source access point multi-link device to send the fourth request to one or more neighboring access point multi-link devices of the source access point multi-link device. The fourth request is generated based on the first request. Wherein, the source access point multilink device is the access point multilink device associated with the non-access point multilink device, and the target access point multilink device is one or more of the one or more neighboring access point multilink devices.

12. The method according to any one of claims 1 to 11, characterized in that, Also includes: The non-access point multilink device sends an eighth request to the source access point multilink device. The eighth request is used to request a temporary key between the non-access point multilink device and the target access point multilink device, and to request the establishment of a multilink between the non-access point multilink device and the target access point multilink device. The non-access point multi-link device receives an eighth response from the source access point multi-link device. The eighth response is used to respond to the eighth request and carries information related to the temporary key between the non-access point multi-link device and the target access point multi-link device. The source access point multilink device is the access point multilink device associated with the non-access point multilink device.

13. A communication method, characterized in that, include: The target access point multi-link device receives a first frame from the non-access point multi-link device on the first link. The first frame is used to request the target access point multi-link device to send a second frame on the first link. The target access point multilink device sends a second frame to the non-access point multilink device on the first link, and the time interval between the end time of the first frame and the start time of the second frame is the short frame interval (SIFS). The second frame is used to measure the Received Signal Strength Indication (RSSI) of the first link of the target access point multi-link device and / or the second frame is used for the non-access point multi-link device to establish synchronization with the first access point corresponding to the first link, where the first access point is the auxiliary access point corresponding to the target access point multi-link device on the first link.

14. The method according to claim 13, characterized in that, The first frame is carried on the primary 20MHz channel of the first link.

15. The method according to claim 13 or 14, characterized in that, The second frame is carried on the primary 20MHz channel of the first link.

16. The method according to any one of claims 13 to 15, characterized in that, The first frame is sent from the address of the first station corresponding to the first link, where the first station is an auxiliary station of the non-access point multi-link device on the first link. The first frame is received from the address of the first access point, and the first frame satisfies one or more of the following: Before receiving the first frame on the first link, the target access point multi-link device has successfully completed the first request and first response interaction with the non-access point multi-link device. The first request is used to detect the target access point multi-link device and carries the address of the first site and / or the link identifier of the first link. The first response is used to feed back the information of the target access point multi-link device and carries the address of the first access point and / or the link identifier of the first link. or, Before receiving the first frame on the first link, the target access point multi-link device has successfully completed the exchange of sending a second request and a second response with the non-access point multi-link device. The second request and the second response are used to establish a temporary key for communication between the non-access point multi-link device and the target access point multi-link device. The second request carries the address of the first site and / or the link identifier of the first link, and the second response carries the address of the first access point and / or the link identifier of the first link. or, Before receiving the first frame on the first link, the target access point multi-link device has successfully completed the third request and third response interaction with the non-access point multi-link device. The third request and the third response are used to establish the first link and / or resource reservation between the non-access point multi-link device and the target access point multi-link device. The third request carries the address of the first site and / or the link identifier of the first link, and the third response carries the address of the first access point and / or the link identifier of the first link.

17. The method according to any one of claims 13 to 16, characterized in that, The first frame is an enhanced long-range physical protocol data unit or an ultra-robust physical protocol data unit.

18. The method according to any one of claims 13 to 17, characterized in that, The second frame is an enhanced long-range physical protocol data unit or an ultra-robust physical protocol data unit.

19. The method according to any one of claims 13 to 16, characterized in that, The first frame is an empty data packet request frame, and the second frame includes an empty data packet notification frame and an empty data packet.

20. The method according to any one of claims 13 to 16, characterized in that, The first frame is the initial control frame, and the second frame is the initial control response frame.

21. The method according to any one of claims 13 to 20, characterized in that, The second frame carries the synchronization time information of the first access point, which is used for the first site to synchronize time with the first access point.

22. The method according to claim 21, characterized in that, The synchronization time information includes part or all of the timestamp information of the first access point.

23. The method according to any one of claims 13 to 22, characterized in that, Also includes: The target access point multi-link device receives a fifth request from the source access point multi-link device. The fifth request is determined based on a first request, which is received by the source access point multi-link device from the non-access point multi-link device. The first field in the first request is a broadcast address.

24. The method according to any one of claims 13 to 23, characterized in that, Also includes: The target access point multilink device receives a ninth request from the source access point multilink device. The ninth request is used to request a temporary key between the non-access point multilink device and the target access point multilink device, and to request the establishment of a multilink between the non-access point multilink device and the target access point multilink device. The target access point multi-link device sends a ninth response to the source access point multi-link device. The ninth response is used to respond to the ninth request and carries information related to the temporary key between the non-access point multi-link device and the target access point multi-link device. The source access point multilink device is the access point multilink device associated with the non-access point multilink device.

25. A communication method, characterized in that, include: The source access point multilink device receives a first request from a non-access point multilink device, wherein the first field in the first request is a broadcast address; wherein the first request is used to probe the target access point multilink device; The source access point multi-link device sends a fifth request to the target access point multi-link device. The fifth request is determined based on the first request and is used to probe the target access point multi-link device.

26. The method according to claim 25, characterized in that, Also includes: The source access point multilink device receives an eighth request from the non-access point multilink device. The eighth request is used to request a temporary key between the non-access point multilink device and the target access point multilink device, and to request the establishment of a multilink between the non-access point multilink device and the target access point multilink device. The source access point multilink device sends a ninth request to the target access point multilink device. The ninth request is generated based on the eighth request. The ninth request is used to request a temporary key between the non-access point multilink device and the target access point multilink device, and to request the establishment of a multilink between the non-access point multilink device and the target access point multilink device. The source access point multilink device receives a ninth response from the target access point multilink device. The ninth response is used to respond to the ninth request and carries information related to the temporary key between the non-access point multilink device and the target access point multilink device. The source access point multi-link device sends an eighth response to the target access point multi-link device. The eighth response is used to respond to the eighth request and carries information related to the temporary key between the non-access point multi-link device and the target access point multi-link device.

27. A communication device, characterized in that, It includes units for performing the method as described in any one of claims 1 to 12, or units for performing the method as described in any one of claims 13 to 24, or units for performing the method as described in any one of claims 25 to 26.

28. A communication device, characterized in that, include: Processor and memory; The memory is used to store computer programs or instructions; The processor is configured to execute a computer program or instructions in a memory to cause the device to perform the method as described in any one of claims 1 to 12, or to cause the device to perform the method as described in any one of claims 13 to 24, or to cause the device to perform the method as described in any one of claims 25 to 26.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when invoked by an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 12, or the method as described in any one of claims 13 to 24, or the method as described in any one of claims 25 to 26.

30. A computer program product, characterized in that, It includes computer execution instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 12, or cause the computer to perform the method as described in any one of claims 13 to 24, or cause the computer to perform the method as described in any one of claims 25 to 26.

31. A chip system, characterized in that, The chip system includes: Communication interface; A processor is configured to invoke and execute the instructions via the communication interface, causing a device equipped with the chip system to perform the method as described in any one of claims 1 to 12, or to perform the method as described in any one of claims 13 to 24, or to perform the method as described in any one of claims 25 to 26.

Images