Communication method of multi-link equipment and electronic equipment

Abstract

The invention provides a communication method of multi-link equipment and electronic equipment. The method comprises: receiving a first association request sent by a second device in a first link, the first association request comprising a first MAC address, and the first MAC address being an MLD MAC address of the second device; the second equipment is multi-link equipment MLD; sending a first association response indicating that connection is allowed to the second device; storing the first MAC address in a first list; under the condition that the first link with the second equipment is disconnected, a second association request sent by the second equipment on a second link is received, and the second association request comprises the first MAC address; and querying that the first list comprises the first MAC address, and according to the type of the first list, responding to the second association request corresponding to the type of the first list. In this way, the situation that a white list or a black list established based on one link of the MLD device fails to another link is avoided.

Description

Technical Field

[0001] The present application relates to the field of terminal equipment, and in particular to a communication method and electronic equipment for a multi-link device. Background Art

[0002] With the update of the WIFI protocol to WIFI7, the protocol supports MLO (Multi-Link Operation). Devices can be connected to the router through multiple links such as 2.4G, 5G, and 6G, which brings lower latency and higher throughput compared to WIFI6.

[0003] MLD (Multi-link Device) identifies devices that support MLO connections. The MAC (Medium Access Control) of MLD is generally the MAC of the wlan0 port, and each link also has its own independent MAC address. The protocol stipulates that the MAC of MLD can be the same as one of the two links, or it can be another unique address.

[0004] In this way, since the MLD device has multiple MAC addresses, the black / white list based on the MAC address in the AP (Access Point, wireless access point) MLD may become invalid. Summary of the invention

[0005] In order to solve the above technical problems, the present application provides a communication method and electronic device of a multi-link device, which can avoid the failure of a blacklist or a whitelist based on a MAC address in an AP MLD device.

[0006] In a first aspect, the present application provides a communication method for a multi-link device, which is applied to a first device, wherein the first device is a multi-link device MLD, and the method comprises: receiving a first association request sent by a second device on a first link, wherein the first association request includes a first MAC address, and the first MAC address is a multi-link device media access control address MLD MAC address of the second device; the second device is a multi-link device MLD; sending a first association response indicating that the connection is allowed to the second device; storing the first MAC address in a first list; in the case where the first link with the second device is disconnected, receiving a second association request sent by the second device on the second link, wherein the second association request includes the first MAC address; querying that the first list includes the first MAC address, and responding to the second association request in accordance with the type of the first list according to the type of the first list. In this way, the AP MLD device uses the MLD MAC of the Non-AP MLD device as the unique identifier of the device in the whitelist or blacklist, so that the whitelist or blacklist is valid for all links of the Non-AP MLD device, thereby avoiding the situation where the whitelist or blacklist established based on one link is invalid for another link.

[0007] According to the first aspect, according to the type of the first list, responding to the second association request in accordance with the type of the first list includes: if the type of the first list is a white list, sending a second association response indicating that the connection is allowed to the second device. In this way, the validity of the white list is ensured, and the situation where the white list established based on one link is invalid for another link is avoided.

[0008] According to the first aspect, according to the type of the first list, responding to the second association request in accordance with the type of the first list includes: if the type of the first list is a blacklist, sending a second association response indicating a rejection of the connection to the second device. In this way, the validity of the blacklist is ensured, and the situation where the blacklist established based on one link is invalid for another link is avoided.

[0009] According to the first aspect, it also includes: after the first device and the third device establish a link on the third link, the MAC addresses of all links of the third device are added to the network restriction blacklist, and all links of the third device include the third link and the fourth link; the third device is an MLD device; receiving a first data frame sent by the third device on the third link, the first data frame includes a third MAC address corresponding to the third link; querying that the third MAC address is in the network restriction blacklist, if it is determined that the current Internet access rate of the third device does not reach the first limit value, forwarding the first data frame to the next hop device; after disconnecting the link with the third device on the third link, establishing a link with the third device on the fourth link; receiving a second data frame sent by the third device on the fourth link, the second data frame includes a fourth MAC address corresponding to the fourth link; querying that the fourth MAC address is in the network restriction blacklist, if it is determined that the current Internet access rate of the third device reaches the first limit value, saving the second data frame to the cache.

[0010] According to the first aspect, after the second data frame is saved in the cache, the method further includes: waiting for a first time period; and after waiting for the first time period, forwarding the second data frame to a next-hop device.

[0011] According to the first aspect, it also includes: after the first device and the third device establish a link on the third link, the MAC addresses of all links of the third device are added to the network restriction blacklist, and all links of the third device include the third link and the fourth link; the third device is an MLD device; receiving a first data frame whose destination device is the third device and needs to be sent to the third device via the third link, the first data frame including a third MAC address corresponding to the third link; querying that the third MAC address is in the network restriction blacklist, if it is determined that the current Internet access rate of the third device does not reach the first limit value, forwarding the first data frame to the third device; after disconnecting the link with the third device on the third link, establishing a link with the third device on the fourth link; receiving a second data frame whose destination device is the third device and needs to be sent to the third device via the fourth link, the second data frame including a fourth MAC address corresponding to the fourth link; querying that the fourth MAC address is in the network restriction blacklist, if it is determined that the current Internet access rate of the third device reaches the first limit value, saving the second data frame to the cache.

[0012] According to the first aspect, after the second data frame is saved in the cache, the method further includes: waiting for a first time period; after waiting for the first time period, forwarding the second data frame to a third device.

[0013] According to the first aspect, it also includes: after the first device and the third device establish a link on the third link, the MAC addresses of all links of the third device are added to the network restriction whitelist, and all links of the third device include the third link and the fourth link; the third device is an MLD device; receiving a first data frame sent by the third device on the third link, the first data frame includes a third MAC address corresponding to the third link; querying that the third MAC address is in the network restriction whitelist, forwarding the first data frame to the next hop device corresponding to the first data frame; after disconnecting the link with the third device on the third link, establishing a link with the third device on the fourth link; receiving a second data frame sent by the third device on the fourth link, the second data frame includes a fourth MAC address corresponding to the fourth link; querying that the fourth MAC address is in the network restriction whitelist, forwarding the second data frame to the next hop device corresponding to the second data frame.

[0014] According to the first aspect, it also includes: after the first device and the third device establish a link on the third link, the MAC addresses of all links of the third device are added to the network restriction whitelist, and all links of the third device include the third link and the fourth link; the third device is an MLD device; receiving a first data frame whose destination device is the third device and needs to be sent to the third device via the third link, the first data frame includes a third MAC address corresponding to the third link; querying that the third MAC address is in the network restriction whitelist, forwarding the first data frame to the third device; after disconnecting the link with the third device on the third link, establishing a link with the third device on the fourth link; receiving a second data frame whose destination device is the third device and needs to be sent to the third device via the fourth link, the second data frame includes a fourth MAC address corresponding to the fourth link; querying that the fourth MAC address is in the network restriction whitelist, forwarding the second data frame to the third device.

[0015] According to the first aspect, it also includes: sending a third association request to a fourth device on a fifth link, the third association request including a fifth MAC address corresponding to the fifth link; the fourth device is an MLD device; receiving a third association response returned by the fourth device for the third association request indicating that the connection is rejected; sending a fourth association request to the fourth device on a sixth link, the fourth association request including a sixth MAC address corresponding to the sixth link; receiving a fourth association response returned by the fourth device for the fourth association request indicating that the connection is allowed, the fourth association response being returned by the fourth device to the first device after the fourth device finds that the sixth MAC address is included in the whitelist.

[0016] According to the first aspect, after receiving a fourth association response indicating that the connection is allowed and returned by the fourth device in response to the fourth association request, the method further includes: recording link information, where the link information is used to indicate that the sixth link can connect to the fourth device and the fifth link cannot connect to the fourth device; when the sixth link with the fourth device is disconnected, when it is necessary to connect to the fourth device, according to the link information, sending a fourth association request to the fourth device in the sixth link, where the fourth association request includes a sixth MAC address corresponding to the sixth link; and receiving a fourth association response indicating that the connection is allowed and returned by the fourth device in response to the fourth association request.

[0017] According to the first aspect, link information is recorded, including: adding a fifth link to a link blacklist, wherein the links in the link blacklist are prohibited from being used to connect to a fourth device; sending a fourth association request to the fourth device on a sixth link according to the link information, including: querying the link blacklist; and in the case where it is found that the fifth link is in the link blacklist, selecting a sixth link that is not in the link blacklist to send a fourth association request to the fourth device.

[0018] According to the first aspect, recording link information includes: adding a sixth link to a link whitelist, where links in the link whitelist are allowed to be used to connect to a fourth device; sending a fourth association request to the fourth device on the sixth link according to the link information, including: querying the link whitelist; and in the case where it is found that the sixth link is in the link whitelist, selecting the sixth link to send the fourth association request to the fourth device.

[0019] According to the first aspect, it also includes: when establishing links with the fifth device through the seventh link and the eighth link respectively, it is detected that the seventh link network is normal and the eighth link network is abnormal, the MAC address corresponding to the seventh link is the seventh MAC address, and the MAC address corresponding to the eighth link is the eighth MAC address; the fifth device is an MLD device, and the seventh MAC address is in the network restriction whitelist of the fifth device; disconnecting the links with the fifth device in the seventh link and the eighth link respectively; sending a fifth association request to the fifth device in the eighth link, the fifth association request including the seventh MAC address; receiving a fifth association response returned by the fifth device in the eighth link for the fifth association request, indicating that the connection is allowed, the fifth association response is returned by the fifth device to the first device when the seventh MAC address is found to be in the network restriction whitelist.

[0020] According to the first aspect, the method further includes: if it is detected that the seventh link network is abnormal and the eighth link network is normal, adding information prohibiting the use of the seventh link to connect to the fifth device into the configuration file.

[0021] According to the first aspect, it also includes: sending a third data frame to the fifth device on the eighth link, the source address in the third data frame is the seventh MAC address, so that the fifth device extracts the seventh MAC address from the third data frame and forwards the third data frame to the next hop device when it is found that the seventh MAC address is in the restricted network whitelist.

[0022] According to the first aspect, it also includes: adding the MLD MAC address of the sixth device to the whitelist; receiving a sixth association request sent by the sixth device through the ninth link, extracting the MLD MAC address of the sixth device from the sixth association request; querying that the MLD MAC address of the sixth device is in the whitelist, and returning a sixth association response indicating that the connection is allowed to the sixth device.

[0023] According to the first aspect, it also includes: adding the MLD MAC address of the sixth device to the blacklist; receiving a sixth association request sent by the sixth device through the ninth link, extracting the MLD MAC address of the sixth device from the sixth association request; querying that the MLD MAC address of the sixth device is in the blacklist, and returning a sixth association response indicating rejection of the connection to the sixth device.

[0024] According to a first aspect, the first device is a mobile phone.

[0025] According to the first aspect, the first association request and the second association request are both association requests based on the WIFI7 protocol.

[0026] In a second aspect, the present application provides an electronic device, comprising: a memory and a processor, the memory being coupled to the processor; the memory storing program instructions, and when the program instructions are executed by the processor, the electronic device executes the communication method of the multi-link device of any one of the first aspects.

[0027] In a third aspect, the present application provides a computer-readable storage medium, including a computer program, which, when executed on an electronic device, enables the electronic device to execute the communication method for a multi-link device according to any one of the aforementioned first aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 is a schematic structural diagram of an illustrative electronic device 100;

[0029] Figure 2 1 is a software structure block diagram of an electronic device 100 according to an embodiment of the present application;

[0030] Figure 3A This is an example diagram of a MAC address of a multi-link MLD device;

[0031] Figure 3BAn example diagram of a physical layer connection of multiple links is shown as an example;

[0032] Figure 3C An example diagram for exemplarily illustrating a multi-link setup;

[0033] Figure 4A An example diagram of a communication process including a router configuration whitelist process is shown as an example;

[0034] Figure 4B Another example diagram of a communication process including a router configuration whitelist process is shown as an example;

[0035] Figure 4C is a schematic diagram of a frame format of a general WIFI frame shown as an example;

[0036] Figure 4D This is an example diagram of newly added information in a frame of the WIFI7 protocol;

[0037] Figure 5A An example diagram of a communication process including a blacklist configuration process of a router is shown as an example;

[0038] Figure 5B Another example diagram of a communication process including a blacklist configuration process of a router is shown as an example;

[0039] Fig. 6A An exemplary diagram of a communication process including a process of pre-configuring a whitelist on a router side is shown as an example;

[0040] Figure 6B Another example diagram of a communication process including a pre-configured whitelist process on a router side is shown as an example;

[0041] Figure 6C An example diagram of a communication process including a process of pre-configuring a blacklist on a router side is shown as an example;

[0042] Fig.6D Another example diagram of a communication process including a pre-configured blacklist process on a router side is shown as an example;

[0043] Fig. 7A An example diagram of a communication process including a process of configuring a network restriction blacklist on a router side is shown as an example;

[0044] Figure 7B Another example diagram of a communication process including a process of configuring a network restriction blacklist on a router side is shown as an example;

[0045] Fig. 8A An example diagram of a communication process including a process of configuring a restricted network whitelist on a router side is shown as an example;

[0046] Figure 8B Another example diagram of a communication process including a process of configuring a restricted network whitelist on a router side is shown as an example;

[0047] Figure 8C This is an example diagram of a process for setting a router restricted network list;

[0048] Fig. 9 This is an example diagram of a communication process in a connection rejection scenario;

[0049] Fig.10 The figure is an example diagram of a communication process in different scenarios showing network conditions of different links. DETAILED DESCRIPTION

[0050] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0051] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0052] The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects rather than to describe a specific order of objects. For example, a first target object and a second target object are used to distinguish different target objects rather than to describe a specific order of target objects.

[0053] This embodiment provides a communication method for a multi-link device, which can be applied to electronic devices such as mobile phones and tablets, but is not limited to these electronic devices.

[0054] In this embodiment, the structure of the electronic device can be as follows Figure 1 shown.

[0055] Figure 1 FIG. 1 is a schematic diagram of the structure of an exemplary electronic device 100. It should be understood that Figure 1 The illustrated electronic device 100 is merely one example of an electronic device, and the electronic device 100 may have more or fewer components than those shown in the figure, may combine two or more components, or may have a different configuration of components. Figure 1The various components shown in the EMBODIMENTS 2000 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0056] See also Figure 1 The electronic device 100 may include: a processor 110, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, an indicator 192, a camera 193, etc.

[0057] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0058] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0059] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory.

[0060] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0061] The UART interface is a universal serial data bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is generally used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

[0062] The USB interface 130 is an interface that complies with the USB standard specification, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and a peripheral device. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0063] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

[0064] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160.

[0065] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0066] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0067] The mobile communication module 150 may provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc.

[0068] The wireless communication module 160 can provide wireless communication solutions for application in the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication technology (NFC), infrared technology (IR), etc.

[0069] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with the network and other devices through wireless communication technology.

[0070] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0071] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0072] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

[0073] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. Indicator 192 can be an indicator light, which can be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0074] Of course, in addition to the above components, the electronic device 100 may also include other hardware components, such as a camera or sensor dedicated to collecting iris data, etc., which are not listed here one by one.

[0075] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100.

[0076] Figure 2 1 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application.

[0077] The layered architecture of the electronic device 100 divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system may include an application layer, an application framework layer, a system library, and a kernel layer.

[0078] The application layer can include a series of application packages.

[0079] like Figure 2 As shown, the application package may include applications such as camera, gallery, settings, map, WLAN, music, short message, call, navigation, Bluetooth, video, etc. Of course, these applications are only exemplary. In other embodiments, the application layer may include Figure 2 The applications not shown in the figure may not include Figure 2 One or more applications shown in .

[0080] Among them, the communication module of the multi-link device may be included in the setting application, and the communication module of the multi-link device is used to execute the communication method of the multi-link device in the embodiment of the present application. In one example, the communication module of the multi-link device can be located in the "Personal Hotspot" module under the "Mobile Network" function module in the setting application. Of course, the above-mentioned location of the communication module of the multi-link device is only an example. In other embodiments, according to actual application requirements, the communication module of the multi-link device can also be placed in other locations, and this embodiment does not limit this.

[0081] like Figure 2 As shown, the application framework layer may include a window manager, a resource manager, a view system, a phone manager, a content provider, a notification manager, and the like.

[0082] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0083] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0084] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0085] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0086] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including connecting, hanging up, etc.).

[0087] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0088] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

[0089] The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

[0090] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0091] The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0092] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

[0093] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0094] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0095] A 2D graphics engine is a drawing engine for 2D (two-dimensional) drawing.

[0096] The kernel layer is the layer between hardware and software.

[0097] like Figure 2 As shown, the kernel layer may include display driver, Wi-Fi driver, audio driver, sensor driver, Bluetooth driver, etc.

[0098] Understandably, Figure 2 The layers in the software structure shown and the components included in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown, and each layer may include more or fewer components, which is not limited in the present application.

[0099] Figure 3A This is an example diagram of the MAC address of a multi-link MLD device. Figure 3A In this embodiment, the service access point SAP (Service Access Point) and the workstation STA (Station) are both multi-link MLD devices, SAP is an AP (Access Point) MLD device, and STA is a non-access point MLD (Non APMLD) device. The MAC address of the SAP includes the MAC address of the MLD device (MLD MAC Addr), the MAC address of link 1 (Link1) (AP1 MAC Addr), and the MAC address of link 2 (Link2) (AP2 MAC Addr). The MAC address of the MLD device is M (expressed as MLD MAC Addr=M), the MAC address of Link1 is w (expressed as AP1 MAC Addr=w), and the MAC address of Link2 is x (expressed as AP2 MAC Addr=x). The MAC address of the MLD device of the SAP is the MLD upper MAC sublayer, and the MAC address of Link1 and the MAC address of Link2 of the SAP are the MLD lower MAC sublayer of the SAP.

[0100] The MAC address of a STA includes the MAC address of the MLD device (MLD MAC Addr), the MAC address of Link 1 (Link1) (STA1 MAC Addr), and the MAC address of Link 2 (Link2) (STA2 MAC Addr). The MAC address of the MLD device is P (expressed as MLD MAC Addr=P), the MAC address of Link1 is y (expressed as STA1 MAC Addr=y), and the MAC address of Link2 is z (expressed as STA2 MAC Addr=z). The MAC address of the MLD device of a STA is the upper MAC sublayer of the MLD, and the MAC address of Link1 and Link2 of a STA are the lower MAC sublayer of the MLD of a STA.

[0101] Because a device has multiple MAC addresses, the MAC address-based blacklist or whitelist in the AP MLD may become invalid.

[0102] The establishment of a multi-link connection is completed on a single link, and data transmission interaction is finally carried out on multiple links. The non-AP MLD device selects one of the STAs to initiate an association request. The Multi-Link connection can only be established when both the association request and the association response contain a Multi-Link element. The APMLD device replies with an Association Response using the link that received the Association Request frame.

[0103] Figure 3B This is a diagram showing an example of a physical layer connection of multiple links. Figure 3B The connection between PHY1 of the Multi-Link AP device and PHY1 of the Multi-Link STA device forms a link Link 1, and the connection between PHY2 of the Multi-Link AP device and PHY2 of the Multi-Link STA device forms a link Link 2. Among them, the PHY (Physical Layer) can send and receive data frames.

[0104] In one example, the general process of establishing a multi-link may be:

[0105] Send an Associate request:

[0106] 1) Select a STA1 link to associate with AP1.

[0107] 2) The transmitter address TA in the association request is: STA1's mac, and the receiver address RA in the association request is: AP1's mac.

[0108] 3) The association request frame body carries the mac information of STAMLD, STA1, STA2, and STA3.

[0109] Receive Association response:

[0110] 1) The transmitter address TA in the association response is: AP1's mac, and the receiver address RA in the association response is: STA1's mac.

[0111] 2) The Associate response frame body carries the MAC information of AP MLD, AP1, AP2, and AP3.

[0112] Figure 3C This is an example diagram showing the establishment of multiple links. Figure 3C The Non-AP MLD device establishes links in the three frequency bands of 2.4 GHz, 5 GHz, and 6 GHz by sending association requests to the AP MLD device and receiving association responses returned by the AP MLD device.

[0113] In the following embodiments, a mobile phone is used as a STA device (Non-AP device) and a router is used as a SAP device (AP device) as an example (wherein the mobile phone and the router are both multi-link MLD devices) to illustrate the principle of the communication method of the multi-link device of this embodiment.

[0114] Furthermore, in the following embodiments, the MAC address of the MLD device of the mobile phone is z, the MAC address of the link 1 (Link1) of the mobile phone is y, and the MAC address of the link 2 (Link2) of the mobile phone is x; the MAC address of the MLD device of the router is a, the MAC address of the link 1 (Link1) of the router is b, and the MAC address of the link 2 (Link2) of the router is c. In one example, the router can be a mobile phone with the hotspot function turned on.

[0115] In the following embodiments, it is assumed that link 1 is a 2.4 GHz link and link 2 is a 5 GHz link.

[0116] In the following embodiments, the frame formats of the association request and the association response may be as follows: Figure 4C and Figure 4D shown. Figure 4C FIG. 1 is a schematic diagram showing an exemplary frame format of a general WIFI frame. Figure 4C The Frame Control field in the Figure 4C The Frame body field in carries the information in the associated frame. The frame format of the frame based on the WIFI7 protocol is also as follows: Figure 4C As shown, the Frame body field of the frame based on the WIFI7 protocol includes Figure 4D Information in.

[0117] like Figure 4C As shown, a complete WIFI frame includes a MAC header (MAC Header), an MSDU (MAC Service Data Unit) field and a CRC (Cyclic Redundancy Check) field.

[0118] Among them, the MAC header includes a frame control (Frame Control) field, a duration (Duration / ID) field, an Address1 (receiving end address RA) field, an Address2 (transmitting end address TA) field, an Address3 field, a sequence control (Sequence Control) field, an Address4 field, a QoS (Quality of Service) control (QoSControl) field, and an HT control (HTControl) field.

[0119] The content in the MSDU field is the frame body, and the content in the CRC field is the FCS (Frame Check Sequence).

[0120] Figure 4D : is an example diagram of newly added information in a frame of the WIFI7 protocol. Figure 4D As shown, the FrameBody field of the frame of the WIFI7 protocol further includes the content contained in the FrameBody field of WIFI6 Figure 4DThe WIFI7 protocol information element shown may include an Element ID field, a Length field, an Element ID Extension field, a Multi-Link Control field, a Common Info Length field, an MLD MAC Address field, a Per-STA Profile x (Non-AP STAx) field, and a Per-STA Profile y (Non-AP STAy) field.

[0121] The Multi-Link Control field may include a Type field, a Reserved field, and a PresenceBitmap field. The Per-STA Profile x field may include a Subelement ID field, a Length field, and a Data field.

[0122] Among them, the Data field may further include a STAControl field field, a STA Info Length field, a STA MAC Address field, a Capability Information field field, an Elemnent a field, an Elemnentn field, and a Non-Inheritance elemnent (optional) field.

[0123] Among them, the STA Control field may further include a Link ID field, a Complete Profile field, a STA MAC Address Present field, etc.

[0124] The following embodiments may be processes based on the WIFI7 protocol.

[0125] The following are several scenarios to explain.

[0126] Scenario 1: Configuring a whitelist

[0127] Figure 4A This is an example diagram of a communication process including a router configuration whitelist process. Figure 4A In this embodiment, the communication process may include the following steps:

[0128] S1, mobile phone 1 sends association request 1 to router 2 on link 1, and association request 1 includes MAC address y of link 1 of mobile phone 1.

[0129] In this step, the transmitter address TA (ie, source address) of the association request 1 is the MAC address y of the link 1 of the mobile phone 1 .

[0130] In this step, the MAC address y of link 1 of mobile phone 1 can be obtained from Figure 4C The "Address 2" field of the

[0131] S2, the router 2 returns an association response 11 to the mobile phone 1 on the link 1, indicating that the connection is allowed.

[0132] Mobile phone 1 receives association response 1, and thus mobile phone 1 establishes a link with router 2 on link 1.

[0133] It can be seen that through the above steps S1 and S2, mobile phone 1 establishes a link with router 2 in link 1.

[0134] S3, Router 2 adds the MAC address y of link 1 of mobile phone 1 to the whitelist, and Router 2 only allows devices in the whitelist to connect to Router 2.

[0135] S4, mobile phone 1 and router 2 are disconnected from link 1.

[0136] S5, mobile phone 1 sends association request 2 to router 2 on link 2, where association request 2 includes MAC address x of link 2 of mobile phone 1.

[0137] In this step, the frame format of association request 2 is as follows: Figure 4C and Figure 4D shown.

[0138] In this step, the MAC address x of link 2 of mobile phone 1 can be obtained from Figure 4C The "Address 2" field of the

[0139] S6, router 2 receives association request 2, extracts MAC address x of link 2 of mobile phone 1 from association request 2, and finds that MAC address x is not included in the whitelist, so router 2 refuses mobile phone 1 to connect to router 2.

[0140] S7, the router 2 sends an association response 22 indicating the rejection of the connection to the mobile phone 1 on the link 2.

[0141] In this way, although mobile phone 1 is a device in the white list, mobile phone 1 cannot establish a link with router 2 in link 2.

[0142] It can be seen from this embodiment that since Link1 and Link2 use different MAC addresses, the whitelist configured on Router 2 becomes invalid, and Mobile Phone 1 cannot connect to Router 2 as an MLD hotspot on Link2.

[0143] In order to solve the above whitelist failure situation, Figure 4B In the illustrated embodiment, when a Non-AP MLD device is connected to an AP MLD device, the AP MLD device uses the MLD MAC of the Non-AP MLD device as a unique identifier of the whitelist.

[0144] Figure 4B This is another example diagram of a communication process including a router configuration whitelist process. Figure 4B In this embodiment, the communication process may include the following steps:

[0145] S401 , mobile phone 1 sends association request 1 to router 2 on link 1 (Link 1 ), where association request 1 includes MLD MAC address z of mobile phone 1 .

[0146] In this step, the frame format of the association request 1 can be as follows: Figure 4C and Figure 4D As shown. Among them, the Framebody field of the WIFI7 protocol includes the following Figure 4D In one example, the MLD MAC Address field can be found from the Framebody field of the frame corresponding to the association request 1, and the MLD MAC address z of the mobile phone 1 can be read from the MLD MAC Address field.

[0147] In this step, the association request 1 may also include the MAC address y of link 1 of the mobile phone 1 and the MAC address x of link 2. The MAC address x of link 2 can be obtained from Figure 4D The Per-STA Profile x field is shown as follows. The MAC address y of link 1 can be obtained from Figure 4D The Per-STA Profile y field is read as shown.

[0148] S402, the router 2 returns an association response 11 indicating that the connection is allowed to the mobile phone 1 on the link 1.

[0149] Mobile phone 1 receives association response 1, and thus mobile phone 1 establishes a link with router 2 on link 1.

[0150] Through steps S401 and S402 , mobile phone 1 establishes a link with router 2 at link 1 (Link 1 ).

[0151] S403, router 2 adds the MLD MAC address z of mobile phone 1 to the whitelist, and router 2 only allows devices in the whitelist to connect to router 2.

[0152] visible, Figure 4BIn the illustrated embodiment, the address in the MLD MAC Address field is used as the unique identifier of the device in the whitelist.

[0153] S404, mobile phone 1 and router 2 are disconnected from link 1.

[0154] S405 , mobile phone 1 sends association request 2 to router 2 on link 2 , where association request 2 includes the MLD MAC address z of mobile phone 1 .

[0155] The frame format of the association request 2 in this step can be as follows Figure 4C and Figure 4D As shown, it can be obtained from Figure 4D The MLD MAC address z of mobile phone 1 is read from the MLD MAC Address field shown.

[0156] The association request 2 may also include the MAC address y of the link 1 of the mobile phone 1 and the MAC address x of the link 2 of the mobile phone 1 .

[0157] S406 , router 2 receives association request 2 , extracts MLD MAC address z of mobile phone 1 from association request 2 , and router 2 queries and finds that the whitelist includes MLD MAC address z, so router 2 allows mobile phone 1 to connect to router 2 .

[0158] Router 2 may search the MLD MACAddress field from the Frame Body field in the association request frame corresponding to association request 2, and read the MLD MAC address z of mobile phone 1 from the MLD MAC Address field.

[0159] S407 , the router 2 sends an association response 21 to the mobile phone 1 on the link 2 , indicating that the connection is allowed.

[0160] Mobile phone 1 receives association response 2, and thus mobile phone 1 establishes a link with router 2 on link 2.

[0161] It can be seen from this embodiment that router 2, which is an AP MLD device, uses the MLD MAC of mobile phone 1 (Non-AP MLD device) as the unique identifier of the device in the whitelist, so that the whitelist is valid for all links of mobile phone 1, thereby avoiding the situation where the whitelist established based on one link is invalid for another link.

[0162] This is because, in Figure 4A In the embodiment shown, the transmitter address TA in the MAC header (MAC Header) in the WIFI frame is used (see Figure 4C) is used as the unique identifier in the whitelist. After the receiving end (router 2) parses the data packet received from mobile phone 1, it will parse the MAC address of TA in this field, determine the source address of the other device (mobile phone 1), and use it as the unique identifier of the device in the whitelist.

[0163] And in Figure 4B In the embodiment shown, for the MLD device, the MAC Address in the Address2 field of the MAC Header is not used as the device identifier, but the MLD MAC Address in the Frame Body field of the association request frame is used (see Figure 4D ) address as the unique identifier of the device. Among them, MLD MAC Address is a new field in the WIFI7 protocol, such as Figure 4D shown.

[0164] Scenario 2: Configuring a blacklist

[0165] Figure 5A This is an example diagram of a communication process including a blacklist configuration process on the router side. Figure 5A In this embodiment, the communication process may include the following steps:

[0166] S1, mobile phone 1 sends association request 1 to router 2 on link 1, and association request 1 includes MAC address y of link 1 of mobile phone 1.

[0167] In this step, the transmitter address TA (ie, source address) of the association request 1 is the MAC address y of the link 1 of the mobile phone 1 .

[0168] In this step, the frame format of the association request frame corresponding to the association request 1 is as follows: Figure 4C shown.

[0169] In this step, the MAC address y of link 1 of mobile phone 1 can be obtained from Figure 4C The "Address 2" field of the

[0170] S2, the router 2 returns an association response 11 to the mobile phone 1 on the link 1, indicating that the connection is allowed.

[0171] Mobile phone 1 receives association response 1, and thus mobile phone 1 establishes a link with router 2 on link 1.

[0172] It can be seen that through the above steps S1 and S2, mobile phone 1 establishes a link with router 2 in link 1.

[0173] S3, Router 2 adds the MAC address y of link 1 of mobile phone 1 to the blacklist, and Router 2 refuses the devices in the blacklist to connect to Router 2.

[0174] S4, mobile phone 1 and router 2 are disconnected from link 1.

[0175] S5, mobile phone 1 sends association request 2 to router 2 on link 2, where association request 2 includes MAC address x of link 2 of mobile phone 1.

[0176] In this step, the frame format of association request 2 is as follows: Figure 4C shown.

[0177] In this step, the MAC address x of link 2 of mobile phone 1 can be obtained from Figure 4C The "Address 2" field of the

[0178] S6, router 2 receives association request 2, extracts MAC address x of link 2 of mobile phone 1 from association request 2, and finds that MAC address x is not included in the blacklist, so router 2 allows mobile phone 1 to connect to router 2.

[0179] S7, the router 2 sends an association response 21 to the mobile phone 1 on the link 2, indicating that the connection is allowed.

[0180] In this way, although mobile phone 1 is a device in the blacklist, mobile phone 1 can still establish a link with router 2 in link 2, and the blacklist becomes invalid.

[0181] It can be seen from this embodiment that since Link1 and Link2 use different MAC addresses, the blacklist configured on Router 2 becomes invalid, and Mobile Phone 1 can still connect to Router 2 as an MLD hotspot on Link2.

[0182] In order to solve the above blacklist failure situation, Figure 5B In the illustrated embodiment, when the Non-AP MLD device is connected to the AP MLD device, the AP MLD device uses the MLD MAC of the Non-AP MLD device as the unique blacklist identifier.

[0183] Figure 5B FIG. 1 is another example diagram of a communication process including a router configuration blacklist process. Figure 5B In this embodiment, the communication process may include the following steps:

[0184] S501 , mobile phone 1 sends association request 1 to router 2 on link 1 (Link 1 ), where association request 1 includes MLD MAC address z of mobile phone 1 .

[0185] In this step, the association request 1 may also include the MAC address y of the link 1 of the mobile phone 1 and the MAC address x of the link 2 .

[0186] In this step, the frame format of association request 1 is as follows: Figure 4C As shown. Among them, the Frame body field may include Figure 4D In one example, the information can be found from the Frame body field of the frame corresponding to the association request 1. Figure 4D The MLD MAC Address field in the frame of the WIFI7 protocol shown in the figure is used, and the MLD MAC address z of the mobile phone 1 is read from the MLD MAC Address field.

[0187] S502 , the router 2 returns an association response 11 to the mobile phone 1 on the link 1 , indicating that the connection is allowed.

[0188] Mobile phone 1 receives association response 1, and thus mobile phone 1 establishes a link with router 2 on link 1.

[0189] Through steps S401 and S402 , mobile phone 1 establishes a link with router 2 at link 1 (Link 1 ).

[0190] S503, Router 2 adds the MLD MAC address z of mobile phone 1 to the blacklist, and Router 2 refuses the devices in the blacklist to connect to Router 2.

[0191] S504, mobile phone 1 and router 2 are disconnected from link 1.

[0192] S505 , mobile phone 1 sends association request 2 to router 2 on link 2 , where association request 2 includes the MLD MAC address z of mobile phone 1 .

[0193] The association request 2 in this step may be an association request based on the WIFI7 protocol. The Frame body field of the association request frame corresponding to the association request 2 may include: Figure 4D After receiving the association request 2, router 2 can obtain the MLD MAC Address field (such as Figure 4D As shown in FIG. 1 , the MLD MAC address z of the mobile phone 1 is read.

[0194] The association request 2 may also include the MAC address y of the link 1 of the mobile phone 1 and the MAC address x of the link 2. The MAC address x of the link 2 may be obtained from Figure 4D The Per-STA Profile x field is shown as follows. The MAC address y of link 1 can be obtained from Figure 4D The Per-STA Profile y field is read as shown.

[0195] S506 , router 2 receives association request 2 , extracts MLD MAC address z of mobile phone 1 from association request 2 , and router 2 finds that the blacklist includes MLD MAC address z, so router 2 refuses mobile phone 1 to connect to router 2 .

[0196] S507 , the router 2 sends an association response 22 indicating a rejection of the connection to the mobile phone 1 in the link 2 .

[0197] Mobile phone 1 receives association response 2, and thus mobile phone 1 establishes a link with router 2 on link 2.

[0198] It can be seen from this embodiment that router 2, which is an AP MLD device, uses the MLD MAC of mobile phone 1 (Non-AP MLD device) as the unique identifier of the device in the blacklist, so that the blacklist is valid for all links of mobile phone 1, thereby avoiding the situation where the blacklist established based on one link is invalid for another link.

[0199] This is because, in Figure 5A In the embodiment shown, the transmitter address TA in the MAC header is used (see Figure 4C ) is used as the unique identifier in the whitelist. After the receiving end (router 2) parses the data packet received from mobile phone 1, it will parse the MAC address of TA in this field, determine the source address of the other device (mobile phone 1), and use it as the unique identifier of the device in the blacklist.

[0200] And in Figure 5B In the embodiment shown, for an MLD device, the MAC Address in the MAC Header is not used as the device identifier, but the MLD MAC Address in the association request is used (see Figure 4D ) address as the unique identifier of the device.

[0201] Scenario 3: User pre-sets router whitelist or blacklist

[0202] (1) Pre-set router whitelist

[0203] Fig. 6A FIG. 1 is a diagram showing an exemplary communication process including a pre-configured whitelist process on the router side. Fig. 6A In this embodiment, the communication process may include the following steps:

[0204] S1, Router 2 adds the MAC address x of Link 2 of mobile phone 1 to the whitelist, and Router 2 allows devices in the whitelist to connect to Router 2.

[0205] In this embodiment, the user sets a whitelist in the router 2 in advance, and the router 2 can perform the operation in this step according to the user's setting information.

[0206] S2, mobile phone 1 sends association request 1 to router 2 on link 1, where association request 1 includes MAC address y of link 1 of mobile phone 1.

[0207] In this step, the frame format of the association request frame corresponding to the association request 1 is as follows: Figure 4C shown.

[0208] In this step, the MAC address y of link 1 of mobile phone 1 can be obtained from Figure 4C The "Address 2" field of the

[0209] S3, Router 2 receives the association request 1, extracts the MAC address y of the link 1 of the mobile phone 1 from the association request 1, and finds that the MAC address y is not included in the whitelist, so Router 2 refuses the mobile phone 1 to connect to Router 2.

[0210] S4, the router 2 sends an association response 12 indicating a connection rejection to the mobile phone 1 on the link 1.

[0211] In this way, although mobile phone 1 is a device in the white list of router 2, it cannot successfully establish a link with router 2.

[0212] It can be seen that in this embodiment, since the whitelist set in the router uses the MAC address x of link 2 of mobile phone 1, when the mobile phone sends an association request to the router through the MAC address y of link 1 on link 1, the router extracts the MAC address y of link 1 from the received association request 1, and compares the MAC address y of link 1 with the address in the whitelist, so it cannot be found that mobile phone 1 is in the whitelist. In this way, although mobile phone 1 is a device in the whitelist, mobile phone 1 cannot connect to router 2 on link 1, which makes the whitelist invalid.

[0213] In another Fig. 6A In a similar embodiment, the communication process may also include the following steps:

[0214] Router 2 adds the MAC address y of link 1 of mobile phone 1 to the whitelist, and router 2 allows devices in the whitelist to connect to router 2.

[0215] Mobile phone 1 sends association request 2 to router 2 on link 2 , where association request 2 includes MAC address x of link 2 of mobile phone 1 .

[0216] Router 2 receives association request 2, extracts MAC address x of link 2 of mobile phone 1 from association request 2, and finds that MAC address x is not included in the whitelist, so router 2 refuses mobile phone 1 to connect to router 2.

[0217] Router 2 sends an association response 22 to mobile phone 1 at link 2 indicating rejection of the connection.

[0218] In this way, although mobile phone 1 is a device in the whitelist of router 2, it cannot successfully establish a link with router 2. Fig. 6A As in the embodiment shown, there is a problem of whitelist failure.

[0219] In order to solve this problem, this embodiment proposes Figure 6B The communication method shown.

[0220] Figure 6B FIG. 1 is another example of a communication process including a pre-configured whitelist process on the router side. Figure 6B In this embodiment, the communication process may include the following steps:

[0221] S601, router 2 adds the MLD MAC address z of mobile phone 1 to the whitelist, and router 2 allows the devices in the whitelist to connect to router 2.

[0222] S602 , mobile phone 1 sends association request 1 to router 2 on link 1 , where association request 1 includes MAC address y of link 1 of mobile phone 1 and MLD MAC address z of mobile phone 1 .

[0223] In this step, the association request 1 may be an association request based on the WIFI7 protocol. The frame format of the association request 1 is as follows: Figure 4C As shown. Among them, the Frame body field in the frame of the association request 1 may include the following Figure 4D In one example, the information can be found from the Frame body field of the frame corresponding to the association request 1. Figure 4D The WIFI7 protocol frame shown in the figure reads the MLD MAC address z of the mobile phone 1 from the MLD MAC Address field.

[0224] S603 , router 2 receives association request 1 , extracts MLD MAC address z of mobile phone 1 from association request 1 , and finds that the whitelist includes MLD MAC address z, so router 2 allows mobile phone 1 to connect to router 2 .

[0225] S604, router 2 sends an association response 11 to mobile phone 1 on link 1, indicating that the connection is allowed.

[0226] In this way, mobile phone 1, as a device in the whitelist of router 2, can successfully establish a link with router 2 in link 1.

[0227] It can be seen that in this embodiment, the whitelist set in the router uses the MLD MAC address z of mobile phone 1, and when the router receives the association request, it also extracts the MLD MAC address of mobile phone 1, and then compares the MLD MAC address of mobile phone 1 with the address in the whitelist. Therefore, it can be queried that mobile phone 1 is in the whitelist, so that mobile phone 1 can establish a link with router 2.

[0228] In another embodiment, the communication process may also include the following steps:

[0229] Router 2 adds the MLD MAC address z of mobile phone 1 to the whitelist, and Router 2 allows devices in the whitelist to connect to Router 2.

[0230] Mobile phone 1 sends association request 2 to router 2 on link 2. Association request 2 includes MAC address x of link 2 of mobile phone 1 and MLD MAC address z of mobile phone 1.

[0231] Router 2 receives association request 2, extracts MLD MAC address z of mobile phone 1 from association request 2, and finds that the whitelist includes MLD MAC address z, so router 2 allows mobile phone 1 to connect to router 2.

[0232] Router 2 sends an association response 21 to mobile phone 1 over link 2 indicating that the connection is allowed.

[0233] In this way, mobile phone 1, as a device in the whitelist of router 2, can successfully establish a link with router 2 in link 2.

[0234] It can be seen that no matter which link mobile phone 1 uses, the association request includes the MLD MAC address of mobile phone 1, which can be successfully compared with the white list, so that a link can be established with router 2 on all links, effectively avoiding the problem of white list failure.

[0235] (2) Pre-set router blacklist

[0236] Figure 6C FIG. 1 is a diagram showing an exemplary communication process including a process of pre-configuring a blacklist on the router side. Figure 6C In this embodiment, the communication process may include the following steps:

[0237] S1, Router 2 adds the MAC address x of Link 2 of mobile phone 1 to the blacklist, and Router 2 does not allow devices in the blacklist to connect to Router 2.

[0238] In this embodiment, the user sets a blacklist in the router 2 in advance, and the router 2 can perform the operation in this step according to the user's setting information.

[0239] S2, mobile phone 1 sends association request 1 to router 2 on link 1, where association request 1 includes MAC address y of link 1 of mobile phone 1.

[0240] In this step, the frame format of the association request frame corresponding to the association request 1 can be as follows: Figure 4C shown.

[0241] In this step, the MAC address y of link 1 of mobile phone 1 can be obtained from Figure 4C The "Address 2" field of the

[0242] S3, router 2 receives association request 1, extracts MAC address y of link 1 of mobile phone 1 from association request 1, and finds that MAC address y is not included in the blacklist, so router 2 allows mobile phone 1 to connect to router 2.

[0243] S4, the router 2 sends an association response 11 to the mobile phone 1 on the link 1, indicating that the connection is allowed.

[0244] In this way, although mobile phone 1 is a device in the blacklist of router 2, it can successfully establish a link with router 2, causing the pre-set blacklist to become invalid.

[0245] It can be seen that in this embodiment, since the blacklist in the router uses the MAC address x of link 2 of mobile phone 1, when the mobile phone sends an association request to the router through the MAC address y of link 1 on link 1, the router extracts the MAC address y of link 1 from the received association request 1, and compares the MAC address y of link 1 with the address in the blacklist, so it cannot be found that mobile phone 1 is in the blacklist. In this way, although mobile phone 1 is a device in the blacklist, mobile phone 1 can successfully connect to router 2 on link 1, which makes the blacklist invalid.

[0246] In another Figure 6C In a similar embodiment, the communication process may also include the following steps:

[0247] Router 2 adds the MAC address y of link 1 of mobile phone 1 to the blacklist, and router 2 does not allow devices in the blacklist to connect to router 2.

[0248] Mobile phone 1 sends association request 2 to router 2 on link 2 , where association request 2 includes MAC address x of link 2 of mobile phone 1 .

[0249] Router 2 receives association request 2, extracts MAC address x of link 2 of mobile phone 1 from association request 2, and finds that MAC address x is not included in the blacklist, so router 2 allows mobile phone 1 to connect to router 2.

[0250] Router 2 sends an association response 21 to mobile phone 1 over link 2 indicating that the connection is allowed.

[0251] In this way, although mobile phone 1 is a device in the blacklist of router 2, it can successfully establish a link with router 2. Figure 6C As in the embodiment shown, there is a problem of blacklist failure.

[0252] In order to solve this problem, this embodiment proposes Fig.6D The communication method shown.

[0253] Fig.6D FIG. 1 is another example of a communication process including a pre-configured blacklist process on a router. Fig.6D In this embodiment, the communication process may include the following steps:

[0254] S611, Router 2 adds the MLD MAC address z of mobile phone 1 to the blacklist, and Router 2 does not allow devices in the blacklist to connect to Router 2.

[0255] S612 , mobile phone 1 sends association request 1 to router 2 on link 1 , where association request 1 includes the MLD MAC address z of mobile phone 1 .

[0256] In this step, the frame format of the association request 1 can be as follows: Figure 4C As shown. Among them, the Framebody field in the frame of the association request 1 may include the following Figure 4D In one example, the information can be found from the Frame body field of the frame corresponding to the association request 1. Figure 4D The MLD MAC Address field shown in the figure is used to read the MLD MAC address z of the mobile phone 1 from the MLD MAC Address field.

[0257] S613 , router 2 receives association request 1 , extracts MLD MAC address z of mobile phone 1 from association request 1 , and finds that the blacklist includes MLD MAC address z, so router 2 refuses mobile phone 1 to connect to router 2 .

[0258] S614, router 2 sends an association response 12 indicating connection rejection to mobile phone 1 on link 1.

[0259] In this way, mobile phone 1, as a device in the blacklist of router 2, cannot establish a link with router 2 in link 1.

[0260] It can be seen that in this embodiment, the blacklist set in the router uses the MLD MAC address z of the mobile phone 1, and when the router receives the association request, it also extracts the MLD MAC address of the mobile phone 1, and then compares the MLD MAC address of the mobile phone 1 with the address in the blacklist. Therefore, it can be queried that the mobile phone 1 is in the blacklist, so that the mobile phone 1 cannot establish a link with the router 2.

[0261] In another embodiment, the communication process may also include the following steps:

[0262] Router 2 adds the MLD MAC address z of mobile phone 1 to the blacklist, and Router 2 does not allow devices in the blacklist to connect to Router 2.

[0263] Mobile phone 1 sends association request 2 to router 2 on link 2. Association request 2 includes MAC address x of link 2 of mobile phone 1 and MLD MAC address z of mobile phone 1.

[0264] Router 2 receives association request 2, extracts MLD MAC address z of mobile phone 1 from association request 2, and finds that the blacklist includes MLD MAC address z, so router 2 refuses mobile phone 1 to connect to router 2.

[0265] Router 2 sends an association response 22 to mobile phone 1 at link 2 indicating rejection of the connection.

[0266] In this way, mobile phone 1, as a device in the blacklist of router 2, cannot establish a link with router 2 in link 2.

[0267] It can be seen that no matter which link mobile phone 1 uses, since the router extracts the MLDMAC address of mobile phone 1 from the association request, it can be successfully compared with the blacklist, so that a link cannot be established with router 2 on any link, effectively avoiding the problem of blacklist failure.

[0268] Scenario 4: Traffic Limitation

[0269] The first case: Internet restriction blacklist

[0270] Devices in the network restriction blacklist are devices whose Internet access speed is restricted.

[0271] Fig. 7A This is an example diagram of a communication process including the process of configuring a network restriction blacklist on the router side. Fig. 7A In this embodiment, the communication process may include the following steps:

[0272] S1, mobile phone 1 sends association request 1 to router 2 on link 1, and association request 1 includes MAC address y of link 1 of mobile phone 1.

[0273] In this step, the frame format of the association request frame corresponding to the association request 1 can be as follows: Figure 4C shown.

[0274] In this step, the MAC address y of link 1 of mobile phone 1 can be obtained from Figure 4C The "Address 2" field of the

[0275] S2, router 2 sends an association response 11 to mobile phone 1 on link 1, indicating that the connection is allowed.

[0276] S3, router 2 extracts MAC address y of link 1 of mobile phone 1 from association request 1, and adds MAC address y to the network restriction blacklist. Router 2 limits the Internet access rate of devices in the network restriction blacklist.

[0277] S4, mobile phone 1 sends data frame 1 to router 2 through link 1, and data frame 1 includes MAC address y of link 1 of mobile phone 1.

[0278] S5, router 2 receives data frame 1 and finds that MAC address y is in the network restriction blacklist. If router 2 determines that the current Internet access rate of mobile phone 1 does not reach the preset limit, router 2 forwards data frame 1 to the next hop device.

[0279] In this step, during data communication between mobile phone 1 and router 2 on link 1, router 2 can limit the Internet access rate of link 1 according to the network restriction blacklist.

[0280] S6, mobile phone 1 and router 2 disconnect from link 1 and establish a connection from link 2.

[0281] The way in which the mobile phone 1 and the router 2 establish a link on the link 2 may be: the mobile phone 1 sends an association request 2 to the router 2 on the link 2, and the router 2 sends an association response 21 to the mobile phone 1 on the link 2 indicating that the connection is allowed.

[0282] S7, mobile phone 1 sends data frame 2 to router 2 through link 2, and data frame 2 includes MAC address x of link 2 of mobile phone 1.

[0283] S8, Router 2 receives data frame 2, finds out that MAC address x is not in the network restriction blacklist, and forwards data frame 2 to the next hop device.

[0284] In this step, during data communication between mobile phone 1 and router 2 on link 2, when router 2 receives data frame 2, regardless of whether the current Internet access rate of mobile phone 1 reaches the preset limit value, router 2 will forward data frame 2 to the next hop device. It can be seen that router 2 cannot limit the Internet access rate of link 2 according to the network restriction blacklist, which makes the network restriction blacklist invalid.

[0285] In order to solve the problem of network restriction blacklist failure, this embodiment proposes Figure 7B The communication flow shown.

[0286] Figure 7B FIG. 1 is another example of a communication process including a process of configuring a network restriction blacklist on a router side. Figure 7B In this embodiment, the communication process may include the following steps:

[0287] S701 , mobile phone 1 sends association request 1 to router 2 on link 1 , where association request 1 includes MAC address y of link 1 of mobile phone 1 , MAC address x of link 2 , and MLD MAC address z of mobile phone 1 .

[0288] In this step, the frame format of the association request 1 can be as follows: Figure 4C As shown. Among them, the Frame body field of the association request 1 based on the WIFI7 protocol may include the following Figure 4D In one example, the information can be found from the Frame body field of the frame corresponding to the association request 1. Figure 4D The MLD MAC Address field shown in the figure reads the MLD MAC address z of mobile phone 1 from the MLD MAC Address field. Figure 4D The Per-STA Profile x field shown reads the MAC address x of link 2 from Figure 4D The Per-STA Profile y field shown reads the MAC address y of Link 1.

[0289] S702, router 2 sends an association response 11 to mobile phone 1 on link 1, indicating that the connection is allowed.

[0290] S703, router 2 extracts MAC address y of link 1 and MAC address x of link 2 of mobile phone 1 from association request 1, and adds both MAC address y and MAC address x to the network restriction blacklist.

[0291] In this embodiment, an example is taken in which two links are included between mobile phone 1 and router 2. In other embodiments, if three links or another number of links are included between mobile phone 1 and router 2, router 2 may add all links between mobile phone 1 and router 2 to the network restriction blacklist.

[0292] Router 2 limits the Internet access speed of devices in the network restriction blacklist.

[0293] S704 , mobile phone 1 sends data frame 1 to router 2 via link 1 , where data frame 1 includes MAC address y of link 1 of mobile phone 1 .

[0294] S705, router 2 receives data frame 1 and finds that MAC address y is in the network restriction blacklist. If router 2 determines that the current Internet access rate of mobile phone 1 does not reach the preset limit, router 2 forwards data frame 1 to the next hop device.

[0295] In this step, during data communication between mobile phone 1 and router 2 on link 1, router 2 can limit the Internet access rate of link 1 according to the network restriction blacklist.

[0296] S706 , mobile phone 1 disconnects from router 2 on link 1 , and establishes a link on link 2 .

[0297] The way that mobile phone 1 and router 2 establish a link in link 2 can be: mobile phone 1 sends association request 2 to router 2 in link 2, and router 2 sends association response 21 indicating that the connection is allowed to mobile phone 1 in link 2. The association request 2 here is based on the WIFI7 protocol.

[0298] S707 , mobile phone 1 sends data frame 2 to router 2 via link 2 , where data frame 2 includes MAC address x of link 2 of mobile phone 1 .

[0299] S708, router 2 receives data frame 2 and finds that MAC address x is in the network restriction blacklist. If router 2 determines that the current Internet access rate of mobile phone 1 reaches the preset limit, router 2 saves data frame 2 to the cache and does not forward data frame 2.

[0300] After waiting for a while, in the next time period, router 2 forwards data frame 2 to the next hop device. In this way, it is ensured that the Internet access rate is limited to below the preset limit value when router 2 receives data frame 2. In the next time period, when router 2 forwards data frame 2 to the next hop device, the Internet access rate is also limited to below the preset limit value.

[0301] In this step, during data communication between mobile phone 1 and router 2 on link 2, router 2 can also limit the Internet access rate of link 2 according to the network restriction blacklist, thereby avoiding the failure of the network restriction blacklist.

[0302] It should be noted that the data packet only has the link MAC, so in this embodiment, the MLD MAC address of mobile phone 1 can be queried based on the MAC address of link 1 of mobile phone 1, and then the MAC of link 2 can be queried based on the MLD MAC address, and the traffic of link 1 and link 2 can be added together.

[0303] In this embodiment, by adding the MAC addresses of all affiliated STAs of mobile phone 1 to the network restriction blacklist, the same strategy is adopted to restrict all affiliated STAs of mobile phone 1, so that the network restriction blacklist established based on one of the links of the MLD device is valid for all links of the MLD device, thereby avoiding the invalidation of the network restriction blacklist.

[0304] It should be noted that although Figure 7B The case where the mobile phone 1 sends data to the router 2 unidirectionally and the flow is limited is used as an example for explanation, but it can be understood that the communication method of the present invention is also applicable to the case where the router 2 sends data to the mobile phone 1 unidirectionally and the case where the router 2 and the mobile phone 1 send data to the flow limited bidirectionally. For example, the communication process of the router 2 sending data to the mobile phone 1 unidirectionally and the flow limited may include the following steps:

[0305] Mobile phone 1 sends association request 1 to router 2 on link 1. Association request 1 includes MAC address y of link 1 of mobile phone 1, MAC address x of link 2, and MLD MAC address z of mobile phone 1.

[0306] Router 2 sends an association response 11 to mobile phone 1 on link 1 indicating that the connection is allowed;

[0307] Router 2 extracts MAC address y of link 1 and MAC address x of link 2 of mobile phone 1 from association request 1, and adds both MAC address y and MAC address x to the network restriction blacklist;

[0308] Router 2 receives data frame 1 whose destination address is mobile phone 1 and needs to be sent to mobile phone 1 through link 1. Data frame 1 includes MAC address y of link 1.

[0309] It is found that MAC address y is in the network restriction blacklist. If router 2 determines that the current Internet access rate of mobile phone 1 does not reach the preset limit value, router 2 forwards data frame 1 to mobile phone 1;

[0310] Mobile phone 1 and router 2 disconnect from link 1 and establish a link from link 2;

[0311] Router 2 receives data frame 2 whose destination address is mobile phone 1 and needs to be sent to mobile phone 1 through link 2. Data frame 2 includes the MAC address x of link 2 of mobile phone 1.

[0312] Router 2 finds that MAC address x is in the network restriction blacklist. If router 2 determines that the current Internet access rate of mobile phone 1 reaches the preset limit value, router 2 saves data frame 2 to the cache and does not forward data frame 2.

[0313] After waiting for a while, in the next time period, router 2 forwards data frame 2 to mobile phone 1. In this way, it is ensured that the Internet access rate of mobile phone 1 is limited to below the preset limit value when router 2 forwards data frame 2. And in the next time period, when router 2 forwards data frame 2 to mobile phone 1, the Internet access rate of mobile phone 1 is also limited to below the preset limit value.

[0314] In the communication process of two-way current limiting, router 2 counts the total rate of the data frames sent by mobile phone 1 and the data frames received from other devices to be sent to mobile phone 1, and determines whether to forward the data frames based on whether the total rate reaches the preset limit value (if the limit value is reached, the data frames will not be forwarded, and if the limit value is not reached, the data frames will be forwarded). The description will not be expanded here.

[0315] The second case: limited network whitelist

[0316] Devices in the network restriction whitelist are devices whose Internet access speed is not restricted.

[0317] Fig. 8A This is an example diagram of a communication process including the process of configuring a restricted network whitelist on the router side. Fig. 8A In this embodiment, the communication process may include the following steps:

[0318] S1, mobile phone 1 sends association request 1 to router 2 on link 1, and association request 1 includes MAC address y of link 1 of mobile phone 1.

[0319] In this step, the frame format of the association request frame corresponding to the association request 1 can be as follows: Figure 4C shown.

[0320] In this step, the MAC address y of link 1 of mobile phone 1 can be obtained from Figure 4C The "Address 2" field of the

[0321] S2, router 2 sends an association response 11 to mobile phone 1 on link 1, indicating that the connection is allowed.

[0322] S3, router 2 extracts MAC address y of link 1 of mobile phone 1 from association request 1, and adds MAC address y to the network restriction whitelist. Router 2 does not restrict the Internet access rate of devices in the network restriction whitelist.

[0323] S4, mobile phone 1 sends data frame 1 to router 2 through link 1, and data frame 1 includes MAC address y of link 1 of mobile phone 1.

[0324] S5, Router 2 receives data frame 1, finds out that MAC address y is in the restricted network whitelist, and forwards data frame 1 to the next hop device.

[0325] In this step, during data communication between mobile phone 1 and router 2 on link 1, router 2 may not restrict the Internet access rate of link 1 according to the network restriction whitelist, and directly forward data frame 1 from mobile phone 1.

[0326] S6, mobile phone 1 and router 2 disconnect from link 1 and establish a connection from link 2.

[0327] The way that mobile phone 1 and router 2 establish a link in link 2 can be: mobile phone 1 sends association request 2 to router 2 in link 2, and router 2 sends association response 21 indicating that the connection is allowed to mobile phone 1 in link 2. The frame format of the association request frame corresponding to the association request 2 can be as follows: Figure 4C shown.

[0328] S7, mobile phone 1 sends data frame 2 to router 2 through link 2, and data frame 2 includes MAC address x of link 2 of mobile phone 1.

[0329] S8, router 2 receives data frame 2 and finds that MAC address x is not in the network restriction whitelist. If router 2 determines that the current Internet access rate of mobile phone 1 reaches the preset limit value (the limit value is set for devices not in the network restriction whitelist), router 2 saves data frame 2 to the cache and does not forward data frame 2. In the next time period, router 2 forwards data frame 2 to the next hop device.

[0330] In this step, during data communication between mobile phone 1 and router 2 on link 2, router 2 cannot lift the restriction on the Internet access rate of link 2 according to the network restriction whitelist, thus causing the network restriction whitelist to become invalid.

[0331] In order to solve the problem of invalid network restriction whitelist, this embodiment proposes Figure 8B The communication flow shown.

[0332] Figure 8B This is another example diagram of a communication process including a process of configuring a restricted network whitelist on the router side.

[0333] exist Figure 8B When restricting the network for a device, the same network restriction policy is adopted for the MAC address in Per-STA Profile x and the MAC address in Per-STA Profile y in the connection frame (i.e., the association request frame) (the frame format of the association request frame is as described above). Figure 4D shown).

[0334] See also Figure 8B In this embodiment, the communication process may include the following steps:

[0335] S801 , mobile phone 1 sends association request 1 to router 2 on link 1 , where association request 1 includes MAC address y of link 1 of mobile phone 1 , MAC address x of link 2 , and MLD MAC address z of mobile phone 1 .

[0336] In this step, the frame format of the association request 1 can be as follows: Figure 4C As shown. Among them, the Frame body field may include Figure 4D In one example, the information can be found from the Frame body field of the frame corresponding to the association request 1. Figure 4D The information shown in the figure is read from the MLD MAC Address field of the information, and the MLD MAC address z of mobile phone 1 is read from Figure 4D The Per-STA Profile x field shown reads the MAC address x of link 2 from Figure 4D The Per-STAProfile y field shown reads the MAC address y of link 1.

[0337] S802, router 2 sends an association response 11 to mobile phone 1 on link 1, indicating that the connection is allowed.

[0338] S803, router 2 extracts MAC address y of link 1 and MAC address x of link 2 of mobile phone 1 from association request 1, and adds both MAC address y and MAC address x to the restricted network whitelist.

[0339] Router 2 does not limit the Internet access speed of devices in the network restriction whitelist.

[0340] Among them, the MAC address y of link 1 and the MAC address x of link 2 can be obtained from Figure 4C The Per-STA Profile y and Per-STA Profile x fields of the Association Request frame shown in FIG.

[0341] S804 , mobile phone 1 sends data frame 1 to router 2 via link 1 , where data frame 1 includes MAC address y of link 1 of mobile phone 1 .

[0342] S805, router 2 receives data frame 1, finds out that MAC address y is in the restricted network whitelist, and forwards data frame 1 to the next hop device.

[0343] In this step, during data communication between mobile phone 1 and router 2 on link 1, router 2 can remove restrictions on the Internet access rate of link 1 according to the network restriction whitelist.

[0344] S806 , mobile phone 1 disconnects from router 2 on link 1 , and establishes a link on link 2 .

[0345] The way in which the mobile phone 1 and the router 2 establish a link on the link 2 may be: the mobile phone 1 sends an association request 2 to the router 2 on the link 2, and the router 2 sends an association response 21 to the mobile phone 1 on the link 2 indicating that the connection is allowed.

[0346] S807 , mobile phone 1 sends data frame 2 to router 2 via link 2 , where data frame 2 includes MAC address x of link 2 of mobile phone 1 .

[0347] S808, Router 2 receives data frame 2, finds out that MAC address x is in the restricted network whitelist, and forwards data frame 2 to the next hop device.

[0348] In this step, during data communication between mobile phone 1 and router 2 on link 2, router 2 can also lift the restriction on the Internet access rate of link 2 according to the network restriction whitelist, thereby avoiding the invalidation of the network restriction whitelist.

[0349] In this embodiment, by adding the MAC addresses of all affiliated STAs of mobile phone 1 to the network restriction whitelist, the same strategy is adopted to lift restrictions on all affiliated STAs of mobile phone 1, so that the network restriction whitelist established based on one of the links of the MLD device is valid for all links of the MLD device, thereby avoiding the invalidation of the network restriction whitelist.

[0350] When the AP side receives a data packet (the data packet will not carry MLD MAC and the MAC Address of another LINK), it will only carry the MAC address in its own Link, that is, its own address in the Per-STAProfile in the association request frame. Therefore, a mapping table needs to be established on the AP side, that is, all MAC addresses in the STA-Profiled in the MLD MAC are stored in a table, and all internal MAC addresses correspond to the MLD MAC of a device. When performing network restriction operations, all MAC addresses in the table are treated equally, that is, the same network restriction policy is set.

[0351] It can be seen that in this embodiment, for the MLO device, the MAC of the Link that establishes the link and the MAC of other Links are added to the network restriction list (such as the network restriction whitelist and the network restriction blacklist).

[0352] Figure 8C FIG. 1 is an exemplary diagram showing the process of setting a router restricted network list. Figure 8C As shown, in this embodiment, the process of setting the router restricted network list may include the following steps:

[0353] A non-AP MLD device is connected to an AP MLD device, for example Figure 8B Mobile phone 1 is connected to router 2;

[0354] The AP MLD device records the MAC addresses of all the attached workstations STA of the non-AP MLD device, for example Figure 8B The MAC address y of link 1 and the MAC address x of link 2 of mobile phone 1;

[0355] When setting up a restricted network list, set the same policy for all corresponding MAC addresses, which is referred to as the restricted network policy.

[0356] so, Figure 7B The network restriction blacklist in the embodiment shown, Figure 8B The network restriction whitelist in the embodiment shown can be Figure 8C Set up according to the process shown.

[0357] Scenario 5: Connection Refused

[0358] Fig. 9 This is an example diagram of a communication process in a connection rejection scenario. Fig. 9 In this embodiment, the communication process may include the following steps:

[0359] S901 , mobile phone 1 sends association request 1 to router 2 on link 1 , where association request 1 includes MAC address y of link 1 of mobile phone 1 .

[0360] The association request 1 in this step can be an association request based on the WIFI6 protocol or an association request based on the WIFI7 protocol.

[0361] S902, router 2 returns an association response 11 indicating that the connection is allowed to mobile phone 1 on link 1.

[0362] Mobile phone 1 receives association response 1, and thus mobile phone 1 establishes a link with router 2 on link 1.

[0363] It can be seen that through the above steps S1 and S2, mobile phone 1 establishes a link with router 2 in link 1.

[0364] S903, router 2 adds the MAC address y of link 1 of mobile phone 1 to the white list, and router 2 only allows devices in the white list to connect to router 2.

[0365] S904, mobile phone 1 and router 2 are disconnected from link 1.

[0366] S905 , mobile phone 1 sends association request 2 to router 2 on link 2 , where association request 2 includes MAC address x of link 2 of mobile phone 1 .

[0367] S906 , router 2 receives association request 2 , extracts MAC address x of link 2 of mobile phone 1 from association request 2 , and finds that MAC address x is not included in the whitelist, so router 2 refuses mobile phone 1 to connect to router 2 .

[0368] S907 , the router 2 sends an association response 22 indicating a rejection of the connection to the mobile phone 1 in the link 2 .

[0369] S908 , mobile phone 1 receives association response 22 , and sends association request 1 to router 2 on link 1 , where association request 1 includes MAC address y of link 1 of mobile phone 1 .

[0370] S909 , router 2 receives association request 1 , extracts MAC address y of link 1 of mobile phone 1 from association request 1 , and finds that MAC address y is included in the whitelist, so router 2 allows mobile phone 1 to connect to router 2 .

[0371] S910, router 2 sends an association response 11 to mobile phone 1 on link 1, indicating that the connection is allowed.

[0372] S911, mobile phone 1 receives association response 11, and records link information, wherein the link information is used to indicate that link 1 can connect to router 2, and link 2 cannot connect to router 2.

[0373] In one example, recording the link information may include, for example: writing link 2 into a link blacklist, where the links in the link blacklist are prohibited from being used to connect to router 2 .

[0374] In another example, recording the link information may include, for example: writing link 1 into a link whitelist, and the links in the link whitelist are allowed to be used to connect to router 2 .

[0375] S912, mobile phone 1 and router 2 are disconnected from link 1.

[0376] S913, when it is necessary to connect to router 2, mobile phone 1 sends association request 1 to router 2 on link 1 according to the recorded link information, and association request 1 includes MAC address y of link 1 of mobile phone 1.

[0377] S914 , router 2 receives association request 1 , extracts MAC address y of link 1 of mobile phone 1 from association request 1 , and finds that MAC address y is included in the whitelist, so router 2 allows mobile phone 1 to connect to router 2 .

[0378] S915, router 2 sends an association response 11 to mobile phone 1 on link 1, indicating that the connection is allowed.

[0379] It can be seen from this embodiment that after the STA device (also a Non-AP MLD device) is denied access by the AP MLD device on one of its links, it selects the MAC address of another link as the source address to connect to the AP MLD device again, thereby successfully establishing a connection with the APMLD device.

[0380] In this embodiment, consider the case where the router manually sets the source address of the device as a whitelist to allow access. If other links are used to associate with the router, the MAC Address under the link may be inconsistent with the MACAddress associated last time, causing the whitelist to become invalid and the link cannot be accessed. Therefore, you can use the MAC Address with the last connection record to try.

[0381] In addition, mobile phone 1 can also record the information that link 1 can connect to router 2 and link 2 cannot connect to router 2 in the link information. When mobile phone 1 subsequently initiates a connection with router 2, it will no longer use link 2 to connect to router 2 according to the link information, but directly use link 1 to connect to router 2.

[0382] For example, steps S911 to S915 may also be replaced by the following steps:

[0383] Mobile phone 1 can add link 2 to the link blacklist;

[0384] When link 1 is disconnected and needs to be connected to router 2 again, mobile phone 1 queries the link blacklist;

[0385] When mobile phone 1 finds that link 2 is in the link blacklist, it selects link 1 which is not in the link blacklist and sends association request 1 to router 2;

[0386] The mobile phone 1 receives an association response 11 returned by the router 2 in response to the association request 1 , indicating that the connection is allowed. In this way, the mobile phone 1 successfully establishes a link with the router 2 .

[0387] Alternatively, steps S911 to S915 may also be replaced by the following steps:

[0388] Mobile phone 1 can add link 1 to the link whitelist;

[0389] When link 1 is disconnected and needs to be connected to router 2 again, mobile phone 1 queries the connection whitelist;

[0390] When mobile phone 1 finds that link 1 is in the link whitelist, it selects link 1 and sends association request 1 to router 2;

[0391] The mobile phone 1 receives an association response 11 returned by the router 2 in response to the association request 1 , indicating that the connection is allowed. In this way, the mobile phone 1 successfully establishes a link with the router 2 .

[0392] Of course, in other embodiments, it is also possible not to include Fig. 9 Steps S911 to S915 in the illustrated embodiment.

[0393] In this embodiment, when the mobile phone has an Internet access record on one of the links, if the connection fails on another link, the connection is made on the original link. If the connection is successful at this time, the connection information is recorded, and the connection is no longer made on the link that failed to connect.

[0394] Scenario 6: One link of the Non-AP MLD device can access the Internet normally, but the other link cannot access the Internet normally. That is, the network conditions of the two links are different.

[0395] For example, when the mobile phone can access the Internet normally on one Link but cannot access the Internet normally on another Link, this embodiment attempts to reassociate on a better Link using the MAC Address of the Link that can access the Internet normally.

[0396] When a mobile phone can access the Internet normally on one link but is restricted on another link, it may indicate that the router has restricted the Internet access to the MAC Address on one of the links. The current link that can access the Internet is not necessarily a better link (it is generally believed that 5G transmission performance is better than 2.4G). Therefore, when this phenomenon is found, the MAC Address in the whitelist can be used on the better link to access the Internet. And record the current status, and use this strategy the next time you associate.

[0397] Fig.10 This is an example diagram of a communication process in different scenarios under different link network conditions. Fig.10 In this embodiment, the communication process may include the following steps:

[0398] S1001, router 2 adds the MAC address y of link 1 of mobile phone 1 to the restricted network whitelist.

[0399] S1002, mobile phone 1 establishes a connection with router 2 on link 1. During the connection establishment process of link 1, association request 1 sent by mobile phone 1 includes MAC address y of link 1 of mobile phone 1.

[0400] In one example, the frame format of the association request 1 in this step can be as follows: Figure 4C and Figure 4D shown.

[0401] S1003, mobile phone 1 establishes a connection with router 2 in link 2. During the connection establishment process of link 2, association request 2 sent by mobile phone 1 includes MAC address x of link 1 of mobile phone 1.

[0402] S1004, mobile phone 1 detects that link 1 is online normally, but link 2 is online abnormally.

[0403] S1005, mobile phone 1 disconnects the links with router 2 on link 1 and link 2 by means of deauth (disassociation).

[0404] S1006 , mobile phone 1 sends association request 3 to router 2 on link 2 , where the source address in association request 3 is MAC address y of link 1 of mobile phone 1 .

[0405] S1007, router 2 receives association request 3, extracts MAC address y from association request 3, and router 2 finds that MAC address y is in the restricted network whitelist, so mobile phone 1 is allowed to connect.

[0406] S1008, the router returns an association response 31 to mobile phone 1 on link 2, indicating that the connection is allowed.

[0407] In this way, mobile phone 1 receives association response 31 and successfully establishes a link with router 2 on link 2.

[0408] S1009, mobile phone 1 detects that link 1 is abnormal in accessing the Internet, but link 2 is normal in accessing the Internet, mobile phone 1 disables link 1, and saves the information of disabling link 1 to the configuration file.

[0409] S1010, mobile phone 1 sends data frame 1 to router 2 on link 2, and the source address in data frame 1 is MAC address y of link 1 of mobile phone 1.

[0410] S1011, router 2 receives data frame 1, extracts MAC address y from data frame 1, and finds that MAC address y is in the restricted network whitelist, so it forwards data frame 1 to the next hop device.

[0411] It can be seen that in this embodiment, if the current limiting is due to the black and white list of the instruction MAC address, the MAC address is exchanged and attempted. If the self-healing is successful, the information of the disabled link is saved.

[0412] In this embodiment, when the mobile phone can access the Internet normally on one Link but cannot access the Internet normally on another Link, a better communication experience can be obtained by re-association using the MAC Address of the Link that can access the Internet normally on the better Link.

[0413] After saving the information of disabling link 1 to the configuration file, when mobile phone 1 subsequently initiates a connection, link 1 will no longer be used, but mobile phone 1 will continue to connect to router 2 as in steps S1006 and S1007. It can be seen that this embodiment can communicate on a better 5G link, which has less interference, larger bandwidth, and faster Internet access rate, thereby improving communication quality and reducing latency.

[0414] In the above embodiments, the router 2 may be an electronic device such as a mobile phone or a tablet, but is certainly not limited thereto.

[0415] It should be noted that, although the above embodiments are described by taking an MLD device having two links as an example, the communication method of a multi-link device of the present application is also applicable to the communication process of an MLD device having more than three links.

[0416] An embodiment of the present application also provides an electronic device, which includes a memory and a processor, wherein the memory is coupled to the processor, and the memory stores program instructions. When the program instructions are executed by the processor, the electronic device implements the communication method of the multi-link device executed by the aforementioned electronic device.

[0417] It is understandable that, in order to realize the above functions, the electronic device includes hardware and / or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of the present application.

[0418] This embodiment further provides a computer storage medium, in which computer instructions are stored. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the communication method of the multi-link device in the above-mentioned embodiment.

[0419] This embodiment further provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the above-mentioned related steps to implement the communication method of the multi-link device in the above-mentioned embodiment.

[0420] In addition, an embodiment of the present application further provides a device, which may specifically be a chip, a component or a module, and the device may include a connected processor and a memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor may execute the computer-executable instructions stored in the memory, so that the chip executes the communication method of the multi-link device in the above-mentioned method embodiments.

[0421] Among them, the electronic device, computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above and will not be repeated here.

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

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

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

[0425] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0426] Any content of each embodiment of the present application, as well as any content of the same embodiment, can be freely combined. Any combination of the above content is within the scope of the present application.

[0427] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0428] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

[0429] The steps of the method or algorithm described in conjunction with the disclosure of the embodiments of the present application can be implemented in a hardware manner, or can be implemented by a processor executing a software instruction. The software instruction can be composed of corresponding software modules, and the software module can be stored in a random access memory (Random Access Memory, RAM), a flash memory, a read-only memory (Read Only Memory, ROM), an erasable programmable read-only memory (Erasable Programmable ROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), a register, a hard disk, a mobile hard disk, a read-only compact disk (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC.

[0430] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented with hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0431] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A communication method for a multi-link device, characterized in that: Applied to a first device, where the first device is a multi-link device MLD, the method includes: Receive a first association request sent by a second device on a first link, wherein the first association request includes a first MAC address, and the first MAC address is a multi-link device media access control address MLD MAC address of the second device; the second device is a multi-link device MLD; sending a first association response indicating that the connection is allowed to the second device; Storing the first MAC address in a first list; In a case where the first link with the second device is disconnected, receiving a second association request sent by the second device on the second link, wherein the second association request includes the first MAC address; It is found that the first list includes the first MAC address, and according to the type of the first list, a response is made to the second association request that is appropriate to the type of the first list.

2. The method according to claim 1, characterized in that According to the type of the first list, responding to the second association request in accordance with the type of the first list includes: The type of the first list is a white list, and a second association response indicating that the connection is allowed is sent to the second device.

3. The method according to claim 1, characterized in that According to the type of the first list, responding to the second association request in accordance with the type of the first list includes: The type of the first list is a blacklist, and a second association response indicating rejection of the connection is sent to the second device.

4. The method according to claim 1, characterized in that: Also includes: After the first device and the third device establish a link on the third link, the MAC addresses of all links of the third device are added to the network restriction blacklist, where all links of the third device include the third link and the fourth link; the third device is an MLD device; receiving a first data frame sent by the third device on the third link, where the first data frame includes a third MAC address corresponding to the third link; It is found that the third MAC address is in the network restriction blacklist, and if it is determined that the current Internet access rate of the third device does not reach the first limit value, the first data frame is forwarded to the next hop device; After disconnecting the link with the third device on the third link, establishing a link with the third device on the fourth link; receiving a second data frame sent by the third device on the fourth link, where the second data frame includes a fourth MAC address corresponding to the fourth link; It is found that the fourth MAC address is in the network restriction blacklist, and if it is determined that the current Internet access rate of the third device reaches the first limit value, the second data frame is saved in the cache.

5. The method according to claim 4, characterized in that After the second data frame is saved in the cache, the method further includes: Wait for the first duration; After waiting for the first time period, the second data frame is forwarded to the next hop device.

6. The method according to claim 1, characterized in that Also includes: After the first device and the third device establish a link on the third link, the MAC addresses of all links of the third device are added to the network restriction blacklist, where all links of the third device include the third link and the fourth link; the third device is an MLD device; receiving a first data frame whose destination device is the third device and needs to be sent to the third device through the third link, wherein the first data frame includes a third MAC address corresponding to the third link; It is found that the third MAC address is in the network restriction blacklist, and if it is determined that the current Internet access rate of the third device does not reach the first limit value, forwarding the first data frame to the third device; After disconnecting the link with the third device on the third link, establishing a link with the third device on the fourth link; receiving a second data frame whose destination device is the third device and needs to be sent to the third device through the fourth link, wherein the second data frame includes a fourth MAC address corresponding to the fourth link; It is found that the fourth MAC address is in the network restriction blacklist, and if it is determined that the current Internet access rate of the third device reaches the first limit value, the second data frame is saved in the cache.

7. The method according to claim 6, characterized in that After the second data frame is saved in the cache, the method further includes: Wait for the first duration; After waiting for the first time period, the second data frame is forwarded to the third device.

8. The method according to claim 1, characterized in that Also includes: After the first device and the third device establish a link on the third link, the MAC addresses of all links of the third device are added to the restricted network whitelist, where all links of the third device include the third link and the fourth link; the third device is an MLD device; receiving a first data frame sent by the third device on the third link, where the first data frame includes a third MAC address corresponding to the third link; Finding that the third MAC address is in the network restriction whitelist, forwarding the first data frame to a next hop device corresponding to the first data frame; After disconnecting the link with the third device on the third link, establishing a link with the third device on the fourth link; receiving a second data frame sent by the third device on the fourth link, where the second data frame includes a fourth MAC address corresponding to the fourth link; It is found that the fourth MAC address is in the network restriction whitelist, and the second data frame is forwarded to the next hop device corresponding to the second data frame.

9. The method according to claim 1, characterized in that: Also includes: After the first device and the third device establish a link on the third link, the MAC addresses of all links of the third device are added to the restricted network whitelist, where all links of the third device include the third link and the fourth link; the third device is an MLD device; receiving a first data frame whose destination device is the third device and needs to be sent to the third device through the third link, wherein the first data frame includes a third MAC address corresponding to the third link; Finding that the third MAC address is in the network restriction whitelist, forwarding the first data frame to the third device; After disconnecting the link with the third device on the third link, establishing a link with the third device on the fourth link; receiving a second data frame whose destination device is the third device and needs to be sent to the third device through the fourth link, wherein the second data frame includes a fourth MAC address corresponding to the fourth link; It is found that the fourth MAC address is in the network restriction whitelist, and the second data frame is forwarded to the third device.

10. The method according to claim 1, characterized in that Also includes: Sending a third association request to a fourth device on a fifth link, wherein the third association request includes a fifth MAC address corresponding to the fifth link; the fourth device is an MLD device; receiving a third association response returned by the fourth device in response to the third association request and indicating connection rejection; Sending a fourth association request to the fourth device on a sixth link, wherein the fourth association request includes a sixth MAC address corresponding to the sixth link; A fourth association response indicating that the connection is allowed and returned by the fourth device in response to the fourth association request is received, wherein the fourth association response is returned by the fourth device to the first device after the fourth device finds that the sixth MAC address is included in the whitelist.

11. The method according to claim 10, characterized in that After receiving a fourth association response returned by the fourth device in response to the fourth association request and indicating that the connection is allowed, the method further includes: Recording link information, where the link information is used to indicate that the sixth link can be connected to the fourth device and the fifth link cannot be connected to the fourth device; In the case of disconnecting the connection with the fourth device on the sixth link, when a connection with the fourth device is needed, sending the fourth association request to the fourth device on the sixth link according to the link information, wherein the fourth association request includes a sixth MAC address corresponding to the sixth link; The fourth association response returned by the fourth device in response to the fourth association request and indicating that the connection is allowed is received.

12. The method according to claim 11, characterized in that Record link information, including: adding the fifth link to a link blacklist, wherein the links in the link blacklist are prohibited from being used to connect to the fourth device; Sending the fourth association request to the fourth device on the sixth link according to the link information includes: Query the link blacklist; In the case that the fifth link is found to be in the link blacklist, the sixth link which is not in the link blacklist is selected to send a fourth association request to the fourth device.

13. The method according to claim 11, characterized in that Record link information, including: Adding the sixth link to a link whitelist, wherein the links in the link whitelist are allowed to be used to connect to the fourth device; Sending the fourth association request to the fourth device on the sixth link according to the link information includes: Query the link whitelist; In the case that the sixth link is found in the link whitelist, the sixth link is selected to send a fourth association request to the fourth device.

14. The method according to claim 1, characterized in that Also includes: When links are established with the fifth device through the seventh link and the eighth link respectively, it is detected that the seventh link network is normal and the eighth link network is abnormal, the MAC address corresponding to the seventh link is the seventh MAC address, and the MAC address corresponding to the eighth link is the eighth MAC address; The fifth device is an MLD device, and the seventh MAC address is in a network restriction whitelist of the fifth device; Disconnecting the link with the fifth device on the seventh link and the link with the eighth link respectively; Sending a fifth association request to the fifth device on the eighth link, wherein the fifth association request includes the seventh MAC address; Receive a fifth association response returned by the fifth device on the eighth link in response to the fifth association request, indicating that the connection is allowed, wherein the fifth association response is returned by the fifth device to the first device when the fifth device finds that the seventh MAC address is in the network restriction whitelist.

15. The method according to claim 14, characterized in that Also includes: If it is detected that the seventh link network is abnormal and the eighth link network is normal, information prohibiting the use of the seventh link to connect to the fifth device is added to the configuration file.

16. The method according to claim 14, characterized in that Also includes: A third data frame is sent to the fifth device over the eighth link, wherein the source address in the third data frame is the seventh MAC address, so that the fifth device forwards the third data frame to the next-hop device when extracting the seventh MAC address from the third data frame and finding that the seventh MAC address is in the network restriction whitelist.

17. The method according to claim 1, characterized in that Also includes: Add the MLD MAC address of the sixth device to the whitelist; receiving a sixth association request sent by the sixth device through a ninth link, and extracting an MLD MAC address of the sixth device from the sixth association request; It is found that the MLD MAC address of the sixth device is in the white list, and a sixth association response indicating that the connection is allowed is returned to the sixth device.

18. The method according to claim 1, characterized in that Also includes: Add the MLD MAC address of the sixth device to the blacklist; receiving a sixth association request sent by the sixth device through a ninth link, and extracting an MLD MAC address of the sixth device from the sixth association request; It is found that the MLD MAC address of the sixth device is in the blacklist, and a sixth association response indicating connection rejection is returned to the sixth device.

19. The method according to claim 1, characterized in that The first device is a mobile phone.

20. The method according to claim 1, characterized in that The first association request and the second association request are both association requests based on the WIFI7 protocol.

21. An electronic device, characterized in that: include: a memory and a processor, the memory being coupled to the processor; The memory stores program instructions, and when the program instructions are executed by the processor, the electronic device executes the communication method of the multi-link device according to any one of claims 1 to 20.

22. A computer-readable storage medium comprising a computer program, characterized in that: When the computer program is executed on an electronic device, the electronic device is enabled to execute the communication method for a multi-link device according to any one of claims 1 to 20.

Images