Distributed multi-link operation (MLO) mobility management method, storage medium, electronic apparatus and computer program product

Abstract

Provided in embodiments of the present application are a distributed multi-link operation (MLO) mobility management method, a storage medium, an electronic apparatus, and a computer program product. The method is applied to a multi-link device (MLD) terminal. The method comprises: performing control signaling transmission with a source access point and / or a target access point in a first frequency band, so as to establish a connection with the target access point, and performing user data transmission with the source access point and / or the target access point in a millimeter wave frequency band, the source access point and the target access point belonging to the same preset area or different preset areas.

Description

Distributed multi-link operation (MLO) mobility management methods, storage media, electronic devices, and computer program products

[0001] Cross-reference to related applications

[0002] This disclosure is based on and claims priority to Chinese Patent Application No. 2025104786882, filed on April 16, 2025, entitled “Distributed Multi-Link Operation (MLO) Mobility Management Method, Storage Medium, Electronic Device and Computer Program Product”, and incorporates the entire contents of that patent application by reference. Technical Field

[0003] This application relates to the field of communications, and more specifically, to a distributed multi-link operation (MLO) mobility management method, storage medium, electronic device, and computer program product. Background Technology

[0004] With the continuous advancement of wireless communication technology, Wi-Fi is evolving towards its next generation, particularly Wi-Fi 8, which integrates millimeter-wave (mmWave) and multi-link operation (MLO) technologies to meet the growing demands for high bandwidth and low latency. This combination is expected to become a key feature of wireless communication in the coming years. Wi-Fi 8 is being developed to meet the needs of demanding applications such as Virtual Reality (VR) and Augmented Reality (AR). Millimeter-wave technology, with its high data transmission rates and low latency, is ideal for realizing these applications.

[0005] The main challenges facing millimeter-wave technology include significant signal propagation loss, susceptibility to congestion, and difficulty maintaining stable connections in dense environments. Wi-Fi 8 reduces development costs by reusing low-frequency devices and algorithms and improves network efficiency and stability through Multi-Link Operation (MLO). MLO technology allows devices to transmit and receive data simultaneously across multiple links, which helps improve network reliability and throughput. When combined with millimeter-wave technology, MLO can mitigate the congestion susceptibility of millimeter-wave signals by simultaneously using multiple frequency bands (including sub-7GHz and millimeter waves) to enhance network coverage and stability.

[0006] With the development of Wi-Fi 8, the integration of millimeter-wave technology and MLO will bring new opportunities to wireless communication. Wi-Fi 8 is expected to support data transmission rates up to 100Gbps, meeting the needs of future high-demand applications. Furthermore, millimeter-wave technology will help address the shortage of 6GHz frequency band resources in some areas and provide strong support for integrated communication and sensing.

[0007] Traditional Wi-Fi handover mechanisms use a "break-before-make" model, which causes service interruptions during handover (typically 50-200ms), severely impacting user experience. Existing technologies have the following problems:

[0008] 1) Link instability: Millimeter wave signals are greatly affected by the environment;

[0009] 2) Long handover interruption time: Service interruption during traditional handover processes affects user experience;

[0010] 3) Low resource utilization efficiency: lack of an effective resource pre-allocation mechanism;

[0011] 4) Insufficient security: The authentication and encryption mechanisms during the handover process are inadequate;

[0012] 5) Complex beam management: The directionality of millimeter-wave communication places higher demands on handover;

[0013] 6) Difficulty in ensuring Quality of Service (QoS): It is impossible to maintain the continuity of QoS during the handover process.

[0014] There is still no good solution to the above problems using relevant technologies. Summary of the Invention

[0015] This application provides a distributed multi-link operation (MLO) mobility management method, storage medium, electronic device, and computer program product.

[0016] According to one embodiment of this application, a distributed multi-link operation (MLO) mobility management method is provided, applied to a multi-link device (MLD) terminal, the MLD terminal including a first frequency band and a millimeter-wave frequency band. The method includes: transmitting control signaling with a source access point and / or a target access point in the first frequency band to establish a connection with the target access point, and transmitting user data with the source access point and / or the target access point in the millimeter-wave frequency band; wherein the source access point and the target access point belong to the same preset area or different preset areas.

[0017] According to another embodiment of this application, a distributed multi-link operation (MLO) mobility management method is provided, applied to a source MLD access point, which includes a first frequency band and a millimeter-wave frequency band. The method includes: transmitting control signaling with a terminal and / or a target access point in the first frequency band, instructing the terminal to establish a connection with the target access point, and transmitting user data with the terminal and / or the target access point in the millimeter-wave frequency band; the source MLD access point and the target access point belong to the same preset area or different preset areas.

[0018] According to another embodiment of this application, a distributed multi-link operation (MLO) mobility management method is provided, applied to a target MLD access point, which includes a first frequency band and a millimeter-wave frequency band. The method includes: transmitting control signaling with a terminal and / or a source access point in the first frequency band to establish a connection with the terminal, and transmitting user data with the terminal and / or the source access point in the millimeter-wave frequency band; wherein the source access point and the target MLD access point belong to the same preset area or different preset areas.

[0019] According to yet another embodiment of this application, a computer-readable storage medium is also provided, which stores a computer program, wherein the computer program, when executed by a processor, implements the steps in any of the above method embodiments.

[0020] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in any of the above method embodiments.

[0021] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments. Attached Figure Description

[0022] Figure 1 is a schematic diagram of the architecture of a distributed multi-link operating system according to an embodiment of this application;

[0023] Figure 2 is a schematic diagram of the distributed MLO mobility management process of an MLD terminal according to an embodiment of this application;

[0024] Figure 3 is a schematic diagram of the distributed MLO mobility management process of the source MLD access point according to an embodiment of this application;

[0025] Figure 4 is a schematic diagram of the distributed MLO mobility management process of the target MLD access point according to an embodiment of this application;

[0026] Figure 5 is a flowchart illustrating the pre-switching detection and target selection process in an embodiment of this application.

[0027] Figure 6 is a schematic diagram of the predictive link evaluation process in an embodiment of this application;

[0028] Figure 7 is a schematic diagram of the resource pre-allocation process in an embodiment of this application;

[0029] Figure 8 is a schematic diagram of the data pre-caching and dual-link transmission process in an embodiment of this application;

[0030] Figure 9 is a flowchart illustrating the dynamic load balancing mechanism in an embodiment of this application;

[0031] Figure 10 is a flowchart illustrating the link efficiency optimization mechanism in an embodiment of this application;

[0032] Figure 11 is a flowchart illustrating the security enhancement mechanism in an embodiment of this application;

[0033] Figure 12 is a schematic diagram of the overall mobility management process in an embodiment of this application;

[0034] Figure 13 is a schematic diagram of the handover process between sub-7GHz devices in an embodiment of this application;

[0035] Figure 14 is a schematic diagram of the process of switching from a sub-7GHz device to a millimeter-wave MLO device in an embodiment of this application;

[0036] Figure 15 is a schematic diagram of the process of switching from a millimeter-wave MLO device to a sub-7GHz device in an embodiment of this application;

[0037] Figure 16 is a schematic diagram of the handover process between millimeter-wave MLO devices in an embodiment of this application. Detailed Implementation

[0038] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0039] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0040] The embodiments of this application can run on a distributed multi-link operating system. Figure 1 is a schematic diagram of the architecture of a distributed multi-link operating system according to an embodiment of this application. As shown in Figure 1, the system includes the following structure:

[0041] The mobile terminal (Station, STA) 10, the source access point (SAP) 20, and the target access point (TAP) 30.

[0042] In this embodiment, the mobile terminal 10, the source access point 20, and the target access point 30 are all multi-link devices (MLDs), but this application is not limited to this, and either the source access point 20 or the target access point 30 may be a non-MLD.

[0043] In this embodiment, each MLD includes a control plane, a data plane, and a multi-link operation (MLO) controller. The data plane provides high-speed data transmission via millimeter-wave frequency bands (e.g., 60 GHz), and the control plane provides reliable signaling transmission via a preset first frequency band (e.g., sub-7 GHz).

[0044] In this embodiment, MLD can establish a control plane connection through a reliable sub-7GHz channel, ensuring reliable transmission of system control signaling. The transmission content of the control plane is as follows:

[0045] 1) Between STA and source AP: Link quality reports, handover requests / responses, resource allocation signaling, security authentication messages, etc.;

[0046] 2) Between STA and target AP: pre-handover detection, security parameter exchange, handover confirmation signaling, etc.;

[0047] 3) Between the source AP and the target AP: handover coordination signaling, resource reservation request, resource status exchange, load balancing control, security context transmission, etc.

[0048] In this embodiment, MLD can achieve high-speed data transmission via a millimeter-wave (60GHz) link, supporting high-capacity service requirements. The data plane transmission content is as follows:

[0049] 1) Between STA and source AP: high-speed data transmission, beam training signaling, QoS guarantee mechanism, performance monitoring data, etc.;

[0050] 2) Between STA and target AP: pre-handover test, beamforming training, data transmission preparation, and performance verification test;

[0051] 3) Between the source AP and the target AP: buffered data transmission.

[0052] In this embodiment, the connection characteristics of the control plane include: operating frequency band sub-7GHz, large coverage area, high transmission reliability, and its main purpose is control signaling transmission.

[0053] In this embodiment, the data plane has the following connection characteristics: it operates at a frequency of 60 GHz, has a bandwidth of 320 MHz, has a high transmission rate, and is mainly used for user data transmission.

[0054] In this embodiment, control and data separation can be achieved in a dual-plane interconnect architecture, ensuring system reliability and efficiency. The control plane provides reliable signaling transmission via sub-7GHz, while the data plane provides high-speed data transmission via 60GHz. The two planes work together to support efficient MLO operation. This architecture design achieves separation between the control plane (sub-7GHz) and the data plane (60GHz), realizing a highly efficient and reliable millimeter-wave MLO system. Each network element has a clearly defined functional role, and their collaborative work ensures the overall performance of the system.

[0055] This application provides a mobility management method running on the aforementioned distributed multi-link operating system.

[0056] One embodiment of this application provides a distributed multi-link operation (MLO) mobility management method, applied to a multi-link device (MLD) terminal, the MLD terminal including a first frequency band and a millimeter-wave frequency band.

[0057] Figure 2 is a flowchart illustrating the distributed MLO mobility management of an MLD terminal according to an embodiment of this application. As shown in Figure 2, the process includes the following steps:

[0058] Step S202: Control signaling is transmitted with the source access point and / or the target access point in the first frequency band to establish a connection with the target access point, and user data is transmitted with the source access point and / or the target access point in the millimeter wave frequency band; wherein the source access point and the target access point belong to the same preset area or different preset areas.

[0059] The entity executing step S202 above is the MLD terminal, which can communicate using both the first frequency band and the millimeter wave frequency band simultaneously.

[0060] Through the embodiments of this application, the terminal uses the first frequency band to reliably transmit signaling to the source access point and the target access point, and uses the millimeter wave frequency band to transmit high-speed data. By separating the control plane and the data plane, efficient and stable distributed MLO mobility management is achieved, which solves the link instability problem faced by mobility management in millimeter wave high-frequency communication in related technologies, and achieves the effect of improving the link reliability of the millimeter wave distributed MLO system.

[0061] In some embodiments, each preset area may include one or more access points (APs), and the preset area is identified by an area ID. For example, each AP may indicate the ID of the preset area to which it belongs in a beacon frame or probe response frame.

[0062] In some embodiments, the preset area can be set by an access controller (AC), network management system, or AP, etc. For example, an AP-m can set up an area 1 and broadcast it. Neighboring APs can request to join area 1, and AP-m determines whether to accept the request.

[0063] In some embodiments, the same security parameters are used in the same preset area, while different security parameters are used in different preset areas. For example, multiple APs in the same preset area can use the same security parameters. Therefore, when switching APs within a preset area, the security authentication process can be skipped, enabling seamless switching of STAs within the preset area.

[0064] In some embodiments, the same network configuration parameters, such as IP address allocation, can be used in the same preset area. By sharing mobility management parameters, multiple APs in the same preset area can reduce AP handover latency and improve user experience.

[0065] In some embodiments, the first frequency band includes one or more sub-7GHz frequency bands. Sub-7GHz frequency bands refer to frequency bands with frequencies below 7GHz (such as 2.4GHz, 5GHz, etc.). Compared with millimeter wave frequency bands (such as 28GHz, 39GHz, etc.), sub-7GHz frequency bands have stronger signal penetration capabilities, wider coverage, and are suitable for long-distance and complex environments, thus enhancing network reliability.

[0066] In some embodiments, the first frequency band supports not only the transmission of control signaling but also the transmission of user data.

[0067] In some embodiments, step S202 may include at least one of the following:

[0068] Step S202-1: Perform user data transmission with the source access point in the millimeter wave frequency band;

[0069] Step S202-2: Trigger the source access point to perform pre-handover detection, and obtain the target access point selected by the source access point based on the result of the pre-handover detection;

[0070] Step S202-3: Trigger the source access point to perform predictive link evaluation, and perform beam tracking on the source access point and prepare beam training for the target access point;

[0071] Step S202-4: Obtain the resource allocation information of the target access point from the source access point, and perform initial beam training and reserved resource verification on the target access point, wherein the resource allocation information is determined by the target access point based on the resource reservation mechanism;

[0072] Step S202-5: After the target access point has completed data pre-caching and sequence synchronization, establish a connection with the target access point;

[0073] Step S202-6: Based on the load balancing mechanism, adjust the first beam between the MLD terminal and the source access point, and establish or adjust the second beam between the MLD terminal and the target access point, wherein the source access point and the target access point negotiate and make decisions on load balancing in the first frequency band.

[0074] Step S202-7: Monitor the channel quality of the MLD terminal, and adjust the first beam and / or the second beam based on the link optimization mechanism and the channel quality;

[0075] Step S202-8: Trigger the source access point to perform security verification on the target access point and establish a secure connection with the target access point;

[0076] Step S202-9: Obtain broadcast information related to the candidate access point, select the target access point according to the broadcast information, and establish a connection with the target access point;

[0077] Step S202-10: Perform user data transmission with the target access point in the millimeter wave frequency band.

[0078] In this embodiment, steps S202-1 to S202-10 are all mobility management related processes, including but not limited to user data transmission, pre-handover detection, predictive link assessment, beam tracking and training, resource allocation verification, data pre-caching, sequence synchronization, load balancing, channel quality monitoring and link optimization, security verification and establishment of secure connections, and selection of target access points.

[0079] Through the embodiments of this application, the MLD terminal can establish a secure and reliable connection with the target access point while maintaining a connection with the source access point, ensuring uninterrupted user services during WiFi handover. In this embodiment, by combining technologies such as pre-handover detection, predictive link assessment, beam tracking and training, resource reservation and verification, the connection to the target access point can be prepared and optimized in advance, reducing handover latency and improving data transmission efficiency. Load balancing mechanisms, channel quality monitoring, and link optimization further optimize network resource allocation, ensuring the stability and speed of data transmission. Security verification and the establishment of secure connections ensure the security of data transmission.

[0080] In some embodiments, step S202-2, triggering the source access point to perform pre-handover detection and obtaining the target access point selected by the source access point based on the result of the pre-handover detection, includes:

[0081] Send a link quality report to the source access point, wherein the link quality report is used to trigger the source access point to perform MLO link analysis, candidate access point discovery, and target access point selection;

[0082] Obtain the target notification sent by the source access point, wherein the target notification carries the target access point selected by the source access point.

[0083] In this embodiment, the pre-handover detection mechanism achieves fast and seamless link handover by discovering and selecting target access points in advance. The source access point can assess whether link handover is necessary based on the link quality report sent by the MLD terminal and select a suitable access point as the handover target for the MLD terminal.

[0084] In some embodiments, step S202-3, which involves triggering the source access point to perform predictive link evaluation, and performing beam tracking on the source access point and beam training preparation on the target access point, includes:

[0085] Send a link quality report to the source access point, wherein the link quality report is used to trigger the source access point to perform historical data analysis on link quality and movement trajectory, Long Short-Term Memory (LSTM) prediction, and prediction result sharing, and the prediction result is used to trigger the target access point to perform link availability analysis;

[0086] Beam tracking is performed on the source access point;

[0087] If the link availability analysis indicates that the link is available, beam training preparation is performed on the target access point.

[0088] In this embodiment, predictive link assessment and beam training preparation enable rapid link establishment and optimization by predicting link status in advance and preparing beam training, thus solving the link establishment delay problem during handover of high-speed mobile devices. LSTM prediction technology can accurately predict future link status based on historical data and movement trajectory, notifying the target access point in advance to perform link availability analysis and beam training preparation, reducing preparation time during handover. Beam tracking ensures stable connection with the source access point, providing continuity for the handover process.

[0089] In some embodiments, the resource allocation information in step S202-4 is a resource reservation result generated by the target access point after performing a resource check based on the resource reservation request sent by the source access point. The resource reservation request carries resource requirements, and the resource check is used to ensure that the spectrum resources, computing resources, and beam resources of the target access point meet the resource requirements.

[0090] In this embodiment, the resource reservation request includes the terminal's resource requirements. The target access point can reserve the necessary spectrum resources, computing resources and beam resources in advance through resource checks, avoiding resource conflicts during handover and reducing the latency caused by waiting for resource allocation during WiFi handover.

[0091] In some embodiments, before the target access point completes data pre-caching and sequence synchronization in step S202-5, the source access point is further configured to control the target access point to perform cache initialization and sequence synchronization, and to perform transmission status synchronization in the first frequency band.

[0092] In this embodiment, data pre-caching ensures that the data that the terminal may need on the target access point has been pre-loaded, reducing the data waiting time during handover; sequence synchronization ensures the correct parsing and processing of data.

[0093] In some embodiments, step S202-6, adjusting the first beam between the MLD terminal and the source access point based on a load balancing mechanism, and establishing or adjusting the second beam between the MLD terminal and the target access point, includes:

[0094] The first beam is adjusted according to the load balancing decision of the source access point and the target access point, wherein the load balancing decision is determined by the target access point after performing load calculation on the load information of the source access point and the load information of the target access point according to a preset algorithm;

[0095] In response to the second beam not being established, the second beam is established according to the load balancing decision; or, in response to the second beam being established, the second beam is adjusted in the millimeter-wave frequency band according to the load balancing decision.

[0096] The load balancing decision carries a balancing strategy and / or execution parameters, including beam parameters and transmission parameters.

[0097] In this embodiment, the source access point and the target access point can negotiate and determine load balancing decisions through signaling interaction. The source access point and the target access point can negotiate to share the corresponding data traffic through a preset load balancing algorithm.

[0098] In some embodiments, step S202-7, monitoring the channel quality of the MLD terminal and adjusting the first beam and / or the second beam based on the link optimization mechanism and the channel quality, includes:

[0099] The channel quality of the MLD terminal is monitored to obtain the Channel Quality Indicator (CQI) and link performance indicators. The transmission mode, transmission parameters and waveform parameters are selected based on the channel quality indicators, and the target wake-up time of the MLD terminal is determined based on the link performance indicators.

[0100] Based on the transmission mode, the transmission parameters, the waveform parameters, and the target wake-up time, the first beam and / or the second beam are adjusted, and the efficiency of the first beam and / or the second beam is evaluated.

[0101] In this embodiment, channel quality monitoring can detect changes in channel status in a timely manner. By selecting the optimal transmission mode, parameters, and waveform, and adjusting the beam direction and power, the stability and speed of data transmission can be improved.

[0102] In an exemplary embodiment, monitoring of channel state indicators may include channel state matrix, interference level measurement, time-varying characteristic analysis, etc., while monitoring of link performance indicators may include throughput statistics, bit error rate monitoring, delay measurement, beam stability measurement, etc.

[0103] In some embodiments, step S202-8, triggering the source access point to perform security verification on the target access point and establish a secure connection with the target access point, includes:

[0104] Send a security request to the source access point, wherein the security request is used to trigger the source access point to send a Hash-based Message Authentication Code (HMAC) verification message to the target access point;

[0105] Obtain the security parameters of the target access point forwarded by the source access point, wherein the security parameters are the security keys generated by the target access point after HMAC verification is completed;

[0106] Based on the security parameters, a secure connection is established with the target access point, wherein the secure connection is used to encrypt data transmission.

[0107] In this embodiment, HMAC verification ensures the identity of the target access point and the integrity of the data, while the generation of the security key provides data encryption protection, avoiding security risks during data transmission.

[0108] In some embodiments, before steps S202-8, the preset area identifiers of the source access point and the target access point can be matched first. If the area identifiers are the same, then they belong to the same preset area. Since the security parameters used in the same preset area are the same, security verification can be skipped, and a secure connection between the MLD terminal and the target access point can be established directly based on the security parameters of the source access point, thereby further improving the connection establishment efficiency and reducing WiFi switching latency. If the source access point and the target access point belong to different preset areas, security verification needs to be passed first before establishing a secure connection.

[0109] In some embodiments, step S202-9, obtaining broadcast information related to the candidate access point, selecting the target access point according to the broadcast information, and establishing a connection with the target access point, includes:

[0110] Receive load information broadcast sent by the source access point, wherein the load information broadcast carries load information of the candidate access point, wherein the candidate access point includes one or more adjacent access points of the source access point;

[0111] Based on the load information broadcast, the target access point is selected from the candidate access points;

[0112] Establish a connection with the target access point.

[0113] In this embodiment, the MLD terminal can receive load information broadcasts sent by the source access point and select the best target access point based on the load information broadcasts.

[0114] In some embodiments, the method further includes at least one of the following:

[0115] 1) Collect inertial measurement unit (IMU) data from the MLD terminal and predict the movement trajectory based on the IMU data;

[0116] 2) In response to the Received Signal Strength Indication (RSSI) of the MLD terminal being less than a preset threshold, a link establishment request is sent to the target access point in the first frequency band, wherein the link establishment request is used to trigger the target access point to perform resource pre-allocation.

[0117] In this embodiment, a higher RSSI value indicates a stronger received signal. A preset threshold is used to judge the signal quality and can be set according to the user's acceptable level of signal quality. When the RSSI is less than the preset threshold, it indicates poor signal quality (unacceptable). At this time, the MLD terminal can also take corresponding measures to optimize network performance, such as requesting the establishment of a new link (sending a link establishment request to the target access point).

[0118] In some embodiments, at least one of the source access point and the target access point is a multi-link device (MLD), and one of the multiple links supported by the MLD is a millimeter-wave band.

[0119] In some embodiments, the source access point is a millimeter-wave device, and the target access point is a device that supports the first frequency band but does not support the millimeter-wave frequency band; or, the source access point is a device that supports the first frequency band but does not support the millimeter-wave frequency band, and the target access point is a millimeter-wave device.

[0120] In this embodiment, if the target access point only supports the first frequency band, it can transmit control signaling and user data with the MLD terminal and the source access point on the first frequency band. Similarly, if the source access point only supports the first frequency band, it can also transmit control signaling and user data with the MLD terminal and the target access point on the first frequency band. This mechanism is compatible with non-millimeter-wave devices, reduces equipment replacement costs, and improves user experience.

[0121] In some embodiments, the method further includes the following steps:

[0122] 1) Perform MLO capability checks on the source access point and the target access point;

[0123] 2) If both the source access point and the target access point have the MLO capability, enable the "build first, disconnect later" mechanism, wherein the "build first, disconnect later" mechanism means that the MLD terminal establishes a connection with the target access point while maintaining a connection with the source access point; or,

[0124] 3) If neither the source access point nor the target access point has the MLO capability, the disconnect-before-build mechanism is enabled, wherein the disconnect-before-build mechanism means that the MLD terminal establishes a connection with the target access point after disconnecting from the source access point.

[0125] In this embodiment, the establish-before-disconnect mechanism ensures the continuity of data transmission during the handover process, avoiding data loss; while the disconnect-before-build mechanism provides a reliable handover strategy when MLO capabilities are limited, reducing the risk of handover failure. This embodiment can adaptively select different connection establishment mechanisms based on whether the device has MLO capabilities, making it more widely applicable.

[0126] In this embodiment, the system's reliability and efficiency are ensured by separating the control plane and the user plane. The control plane provides reliable signaling transmission through a preset first frequency band (e.g., sub-7GHz), while the data plane provides high-speed data transmission through a millimeter-wave frequency band (e.g., 60GHz). The two planes work collaboratively and can support efficient MLO operation through a make-before-break working mode. This embodiment solves the problems of link instability, high handover latency, and high system overhead faced by traditional mobility management in millimeter-wave high-frequency communication. It can significantly improve the link reliability of millimeter-wave distributed MLO systems, reduce handover latency, reduce system overhead, and improve user experience quality, making it suitable for next-generation high-speed wireless communication networks.

[0127] In another embodiment of this application, a distributed multi-link operation (MLO) mobility management method is provided, which is applied to a source multi-link device (MLD) access point, wherein the source MLD access point includes a first frequency band and a millimeter-wave frequency band.

[0128] Figure 3 is a schematic diagram of the distributed MLO mobility management process of the source MLD access point according to an embodiment of this application. As shown in Figure 3, the process includes the following steps:

[0129] Step S302: Control signaling is transmitted with the terminal and / or the target access point in the first frequency band to instruct the terminal to establish a connection with the target access point and to transmit user data with the terminal and / or the target access point in the millimeter wave frequency band; wherein the source MLD access point and the target access point belong to the same or different preset areas.

[0130] The entity executing step S302 above is the source MLD access point, which can communicate using both the first frequency band and the millimeter wave frequency band simultaneously.

[0131] Through the embodiments of this application, the source MLD access point uses the first frequency band to reliably transmit signaling to the terminal and the target access point, and uses the millimeter wave frequency band to transmit high-speed data. By separating the control plane and the data plane, efficient and stable distributed MLO mobility management is achieved, which solves the link instability problem faced by mobility management in millimeter wave high-frequency communication in related technologies, and achieves the effect of improving the link reliability of the millimeter wave distributed MLO system.

[0132] In some embodiments, each preset area may include one or more access points (APs), and the preset area is identified by an area ID. For example, each AP may indicate the ID of the preset area to which it belongs in a beacon frame or probe response frame.

[0133] In some embodiments, the preset area can be set by an access controller (AC), network management system, or AP, etc. For example, an AP-m can set up an area 1 and broadcast it. Neighboring APs can request to join area 1, and AP-m determines whether to accept the request.

[0134] In some embodiments, the same security parameters are used in the same preset area, while different security parameters are used in different preset areas. For example, multiple APs in the same preset area can use the same security parameters. Therefore, when switching APs within a preset area, the security authentication process can be skipped, enabling seamless switching of STAs within the preset area.

[0135] In some embodiments, the same network configuration parameters, such as IP address allocation, can be used in the same preset area. By sharing mobility management parameters, multiple APs in the same preset area can reduce AP handover latency and improve user experience.

[0136] In some embodiments, the first frequency band includes one or more sub-7GHz frequency bands. Sub-7GHz frequency bands refer to frequency bands with frequencies below 7GHz (such as 2.4GHz, 5GHz, etc.). Compared with millimeter wave frequency bands (such as 28GHz, 39GHz, etc.), sub-7GHz frequency bands have stronger signal penetration capabilities, wider coverage, and are suitable for long-distance and complex environments, thus enhancing network reliability.

[0137] In some embodiments, the following mobility management functions can be achieved through the above step S302: user data transmission, pre-handover detection, predictive link assessment, beam tracking and training, resource reservation and verification, load balancing mechanism, channel quality monitoring, link optimization, security verification, and establishment of secure connections.

[0138] Through the embodiments of this application, the terminal can establish a secure and reliable connection with the target access point while maintaining a connection with the source MLD access point, ensuring uninterrupted user services during WiFi handover. In this embodiment, by combining technologies such as pre-handover detection, predictive link assessment, beam tracking and training, resource reservation and verification, the connection to the target access point can be prepared and optimized in advance, reducing handover latency and improving data transmission efficiency. Load balancing mechanisms, channel quality monitoring, and link optimization further optimize network resource allocation, ensuring the stability and speed of data transmission. Security verification and the establishment of a secure connection ensure the security of data transmission.

[0139] In this embodiment, the system's reliability and efficiency are ensured by separating the control plane and the user plane. The control plane provides reliable signaling transmission through a preset first frequency band (e.g., sub-7GHz), while the data plane provides high-speed data transmission through a millimeter-wave frequency band (e.g., 60GHz). The two planes work collaboratively and can support efficient MLO operation through a make-before-break working mode. This embodiment solves the problems of link instability, high handover latency, and high system overhead faced by traditional mobility management in millimeter-wave high-frequency communication. It can significantly improve the link reliability of millimeter-wave distributed MLO systems, reduce handover latency, reduce system overhead, and improve user experience quality, making it suitable for next-generation high-speed wireless communication networks.

[0140] In another embodiment of this application, a distributed multi-link operation (MLO) mobility management method is provided, which is applied to a target multi-link device (MLD) access point, the target MLD access point including a first frequency band and a millimeter-wave frequency band.

[0141] Figure 4 is a schematic diagram of the distributed MLO mobility management process for the target MLD access point according to an embodiment of this application. As shown in Figure 4, the process includes the following steps:

[0142] Step S402: Control signaling is transmitted with the terminal and / or the source access point in the first frequency band to establish a connection with the terminal, and user data is transmitted with the terminal and / or the source access point in the millimeter wave frequency band; wherein the source access point and the target MLD access point belong to the same or different preset areas.

[0143] The subject of the above step S402 is the target MLD access point, which can communicate using both the first frequency band and the millimeter wave frequency band.

[0144] Through the embodiments of this application, the target MLD access point uses the first frequency band to reliably transmit signaling with the terminal and the source access point, and uses the millimeter wave frequency band to transmit high-speed data. By separating the control plane and the data plane, efficient and stable distributed MLO mobility management is achieved, which solves the link instability problem faced by mobility management in millimeter wave high-frequency band communication in related technologies, and achieves the effect of improving the link reliability of the millimeter wave distributed MLO system.

[0145] In some embodiments, each preset area may include one or more access points (APs), and the preset area is identified by an area ID. For example, each AP may indicate the ID of the preset area to which it belongs in a beacon frame or probe response frame.

[0146] In some embodiments, the preset area can be set by an access controller (AC), network management system, or AP, etc. For example, an AP-m can set up an area 1 and broadcast it. Neighboring APs can request to join area 1, and AP-m determines whether to accept the request.

[0147] In some embodiments, the same security parameters are used in the same preset area, while different security parameters are used in different preset areas. For example, multiple APs in the same preset area can use the same security parameters. Therefore, when switching APs within a preset area, the security authentication process can be skipped, enabling seamless switching of STAs within the preset area.

[0148] In some embodiments, the same network configuration parameters, such as IP address allocation, can be used in the same preset area. By sharing mobility management parameters, multiple APs in the same preset area can reduce AP handover latency and improve user experience.

[0149] In some embodiments, the first frequency band includes one or more sub-7GHz frequency bands. Sub-7GHz frequency bands refer to frequency bands with frequencies below 7GHz (such as 2.4GHz, 5GHz, etc.). Compared with millimeter wave frequency bands (such as 28GHz, 39GHz, etc.), sub-7GHz frequency bands have stronger signal penetration capabilities, wider coverage, and are suitable for long-distance and complex environments, thus enhancing network reliability.

[0150] In some embodiments, the following mobility management functions can be achieved through the above step S402: user data transmission, pre-handover detection, predictive link assessment, beam tracking and training, resource reservation and verification, load balancing mechanism, channel quality monitoring, link optimization, security verification, and establishing secure connections.

[0151] Through the embodiments of this application, the terminal can establish a secure and reliable connection with the target MLD access point while maintaining a connection with the source access point, ensuring uninterrupted user services during WiFi handover. In this embodiment, by combining technologies such as pre-handover detection, predictive link assessment, beam tracking and training, resource reservation and verification, the connection to the target access point can be prepared and optimized in advance, reducing handover latency and improving data transmission efficiency. Load balancing mechanisms, channel quality monitoring, and link optimization further optimize network resource allocation, ensuring the stability and speed of data transmission. Security verification and the establishment of secure connections ensure the security of data transmission.

[0152] In this embodiment, the system's reliability and efficiency are ensured by separating the control plane and the user plane. The control plane provides reliable signaling transmission through a preset first frequency band (e.g., sub-7GHz), while the data plane provides high-speed data transmission through a millimeter-wave frequency band (e.g., 60GHz). The two planes work collaboratively and can support efficient MLO operation through a make-before-break working mode. This embodiment solves the problems of link instability, high handover latency, and high system overhead faced by traditional mobility management in millimeter-wave high-frequency communication. It can significantly improve the link reliability of millimeter-wave distributed MLO systems, reduce handover latency, reduce system overhead, and improve user experience quality, making it suitable for next-generation high-speed wireless communication networks.

[0153] The various embodiments in this application also have the following beneficial effects:

[0154] 1) Reduce handover interruption time: Reduce interruption time from 200ms to less than 3ms through a pre-establishment mechanism;

[0155] 2) Improve resource utilization efficiency: Improve resource utilization efficiency through forecasting and pre-allocation;

[0156] 3) Enhance system security: Introduce dynamic key updates and dual authentication mechanisms;

[0157] 4) Optimized beam management: Achieve precise beam tracking and switching;

[0158] 5) Ensure service quality: Ensure business continuity through dual-link transmission.

[0159] In this embodiment, distributed MLO can implement the following mobility management functions: pre-handover detection and target selection, predictive link assessment, resource pre-allocation, data pre-caching and dual-link transmission, dynamic load balancing mechanism, link efficiency optimization mechanism, and security enhancement mechanism. The following will take an example where the control channel uses the sub-7GHz band and the data channel uses the millimeter-wave band (60GHz) to provide a detailed explanation of each mobility management function.

[0160] Example 1: Pre-switching detection and target selection.

[0161] Application scenarios: Millimeter-wave MLO pre-handover in high-speed mobile scenarios, such as high-speed rail stations and airports, requires advance identification and selection of target APs to achieve seamless handover.

[0162] Figure 5 is a flowchart illustrating the pre-switching detection and target selection process in an embodiment of this application. As shown in Figure 5, the process includes the following steps:

[0163] Step S501: The mobile terminal sends a link quality report (Link_Quality_Report) to the source AP;

[0164] Step S502: The source AP performs MLO link analysis;

[0165] Step S503: The source AP sends an AP discovery request (AP_Discovery_Request) to the target AP;

[0166] Step S504: The source AP receives an AP discovery response (AP_Discovery_Response) from the target AP;

[0167] Step S505: The source AP performs target AP filtering;

[0168] Step S506: The source AP sends a target notification (Target_Notification) to the mobile terminal;

[0169] Step S507: The source AP receives the target response (Target_Response) from the mobile terminal.

[0170] In this embodiment, the control signaling in steps S501 to S507 is transmitted through a sub-7GHz control channel. During the execution of steps S501 to S507, the mobile terminal can continuously transmit data with the source AP via the millimeter-wave data channel, avoiding connection interruption and thus improving the user experience. Steps S501 to S507 will be described in detail below.

[0171] Step S501: The mobile terminal sends a link quality report to the source AP.

[0172] From a reliability perspective, millimeter-wave links (60GHz) are susceptible to obstruction and fading, while sub-7GHz offers better propagation characteristics and coverage, ensuring reliable transmission of control signaling. From a timeliness perspective, even when millimeter-wave link quality degrades, timely reporting is still possible, preventing control signaling from competing with data transmission for millimeter-wave resources. Adopting a design that separates the control plane (sub-7GHz) and data plane (60GHz) can improve system reliability and flexibility.

[0173] Link quality reports can include the following link quality metrics: Received Signal Strength Indication (RSSI), which reflects changes in signal strength, with a threshold set to -75dBm, primarily used for a rough assessment of link status; Channel State Information (CSI), which includes amplitude and phase information and accurately reflects changes in channel characteristics; Bit Error Rate (BER), which reflects link transmission quality and is used to assess service quality; and Beam Alignment Deviation (BAD), which reflects beam alignment accuracy and is used for beam tracking control.

[0174] Link quality reports can employ a dual reporting mechanism. (1) Periodic reporting, used for routine monitoring, includes basic link status. (2) Event-triggered reporting, triggered when the following conditions occur: RSSI is below the threshold of -75dBm, BER exceeds the threshold, CSI changes significantly (more than 12%), or beam alignment deviation exceeds the threshold.

[0175] Processing flow: On the terminal side, continuously monitor link quality indicators, determine whether reporting conditions are triggered, and send a report via sub-7GHz. On the AP side, receive the quality report, update the link state database, and trigger necessary optimization operations.

[0176] Optimization Mechanism: The system implements an adaptive reporting cycle, shortening the cycle during high-speed movement and extending it when stationary. It also employs intelligent trigger thresholds, adjusting them based on service type and considering historical data trends to dynamically optimize judgment criteria. This mechanism ensures the system can obtain link status information in a timely manner while avoiding unnecessary signaling overhead.

[0177] Step S502: The source AP performs MLO link analysis.

[0178] In distributed MLO systems, both millimeter-wave and sub-7GHz links need to be managed simultaneously, and multi-link coordination is achieved through comprehensive analysis. This analysis can identify link quality degradation trends in advance, avoid service interruptions, and optimize resource utilization. Especially in high-speed mobile scenarios, timely link analysis is crucial for maintaining service continuity.

[0179] Analysis Content: The system can use the Cross-Technology Link Quality Indicator (CLQI) for evaluation. CLQI is calculated using a weighted average: CLQI = w1 × RSSI + w2 × CSI + w3 × BER, where the weighting coefficients w1 to w3 can be dynamically adjusted according to the service type. Simultaneously, LSTM prediction based on historical data provides a 100ms prediction window, with a prediction accuracy requirement exceeding 90%. MLO capacity assessment includes a comprehensive evaluation of current bandwidth utilization, service traffic demand, and QoS requirement fulfillment.

[0180] Triggering Mechanism: The system implements a dual triggering mechanism. Periodic analysis is synchronized with Link_Quality_Report. Event-triggered analysis is initiated when the CLQI falls below the threshold of 0.7, trend predictions show performance degradation, or QoS indicators fail to meet requirements. This mechanism ensures the timeliness of analysis and efficient resource utilization.

[0181] Processing flow: First, data collection is performed, including receiving Link_Quality_Report, obtaining historical data, and collecting resource usage information. Then, analysis and processing are executed, calculating CLQI, performing trend prediction, and generating an analysis report. Finally, decision support is provided, determining whether a switchover is needed, selecting a target AP, and preparing resource reservations.

[0182] Step S503: The source AP sends an AP discovery request (AP_Discovery_Request) to the target AP.

[0183] In a distributed MLO system, AP discovery requests are a critical step in handover preparation. By promptly identifying potential target APs, assessing AP availability, and preparing resource reservations, performance optimization can be achieved, the optimal target AP can be selected, blind handovers can be avoided, and handover failure rates can be reduced. This is particularly important for ensuring the quality of service (QoS) of millimeter-wave communication.

[0184] Request content: (1) Terminal information: including current location coordinates, moving speed and direction, and MLO capability parameters. (2) Resource requirements: explicitly specify bandwidth requirements (320MHz), subcarrier configuration (4×80MHz), and QoS parameter set. (3) Handover parameters: including expected handover time, service continuity requirements, and beam training parameters. This information helps the target AP assess whether it can meet the terminal requirements.

[0185] Request Triggering Mechanism: The system employs a combination of proactive triggering and periodic probing. Proactive probing is triggered when the CLQI falls below a threshold, a performance degradation trend is predicted, or load balancing is required. Periodic probing is executed every 20ms in high-speed mobile scenarios and every 100ms in normal scenarios.

[0186] Processing flow: The pre-transmission preparation phase involves collecting terminal information, organizing resource requirements, and preparing handover parameters. Requests are sent via the sub-7GHz channel, either broadcast or directed, with a response timeout set. Response processing includes waiting for AP responses, collecting available AP information, and preparing for AP filtering. This entire process ensures efficient AP discovery and resource preparation.

[0187] Step S504: The source AP receives an AP discovery response (AP_Discovery_Response) from the target AP.

[0188] In a distributed MLO system, the target AP needs to feed back its availability information to the source AP via a sub-7GHz channel. This response mechanism ensures the accuracy of handover decisions and avoids service interruptions that may result from blind handovers. Especially in millimeter-wave communication scenarios, the AP's load status and resource availability directly affect the success rate of handover.

[0189] Response content: The target AP first reports its basic status, including CPU load (required to be below 70%), available memory, and processing power. Regarding spectrum resources, it details the availability of the 320MHz bandwidth, including the specific configuration of the 4×80MHz subcarriers. Beam resource status includes the number of available beams, spatial multiplexing capability, and current interference level. It also includes the MLO capability set, indicating the degree of support for multi-link operation.

[0190] Response generation mechanism: Upon receiving a request, the target AP first performs a resource assessment, calculating the match between currently available resources and the requested requirements. The assessment includes three dimensions: computing resources, spectrum resources, and beam resources. Based on the assessment results, a response message containing detailed resource information is generated. Response latency is required to be controlled within 1ms to ensure the timeliness of the handover decision.

[0191] Processing flow: Upon receiving a discovery request, the target AP immediately initiates a resource assessment process. After assessment, it sends a response message via a sub-7GHz channel. Upon receiving the response, the source AP stores the information in the candidate AP database, providing a basis for subsequent AP selection. The entire process must ensure the accuracy and timeliness of the response information.

[0192] Step S505: The source AP is used to filter the target AP.

[0193] After receiving responses from multiple candidate APs, a comprehensive evaluation is needed to select the optimal target AP. This selection process directly impacts the handover performance and quality of service. In millimeter-wave communication scenarios, due to the instability of link characteristics, choosing a suitable target AP is particularly important.

[0194] Selection Criteria: The system employs a multi-dimensional scoring mechanism, primarily considering factors such as signal quality (RSSI > -65dBm), resource availability (CPU < 70%), beam resources (spatial multiplexing capability), and location prediction (based on movement trajectory). Each dimension has a corresponding weight, and the final score is calculated through weighted summation. Load balancing is also considered to avoid resource concentration.

[0195] Selection Algorithm: A deep reinforcement learning-based selection algorithm is employed, using historical handover success rate as a key reference factor. The algorithm considers both immediate scores and long-term benefits, continuously optimizing the selection strategy through Q-learning. During the selection process, the terminal's location within the next 100ms is predicted to ensure the selected access point (AP) can provide continuous service.

[0196] Processing flow: First, all candidate APs are initially screened, eliminating those that do not meet the basic criteria. Then, a comprehensive score is calculated for each candidate AP, and the AP with the highest score is selected as the target AP. Finally, a screening report is generated, including the selection criteria and expected performance metrics. The entire screening process needs to be completed within 5ms to support rapid switching decisions.

[0197] Step S506: The source AP sends a target notification (Target_Notification) to the mobile terminal.

[0198] In a distributed MLO system, once the target AP is selected, the mobile terminal needs to be notified promptly via the sub-7GHz channel. This notification process is crucial for initiating subsequent handover preparations, especially in millimeter-wave communication scenarios where sufficient time needs to be allocated for beam training and resource preparation.

[0199] Notification content: The notification message contains complete access information of the target AP, such as: (1) Basic information: AP identifier, physical location coordinates, coverage area; (2) Resource information: pre-allocated frequency band (320MHz bandwidth), time slot allocation, beam parameters; (3) Handover parameters: expected handover time window (usually 20-100ms), beam training time schedule; (4) MLO configuration: multi-link aggregation parameters, link priority settings.

[0200] Notification Mechanism: The system can adopt a reliable notification mechanism, such as: (1) Immediate notification: Send immediately after filtering; (2) Confirmation mechanism: Require the terminal to reply with confirmation; (3) Timeout retransmission: Resend if no confirmation is received; (4) Backup scheme: Send simultaneously through multiple links.

[0201] Processing flow: After generating a notification message, the source AP sends it to the terminal via the sub-7GHz control channel. Upon receiving the message, the terminal needs to process it immediately, assess the feasibility of the handover, and prepare the necessary resources. The entire notification process must be completed within 2ms to ensure the timeliness of the handover.

[0202] Step S507: The source AP receives the target response (Target_Response) from the mobile terminal.

[0203] The terminal needs to respond to the target AP's notification to confirm whether it accepts the handover arrangement. This response process is the final confirmation in the handover preparation phase and is crucial for ensuring handover reliability and reducing handover failure rates.

[0204] Response content: The terminal's response message may include the following: (1) Confirmation status: accept / reject the handover arrangement; (2) Readiness status: resource readiness status and beam training readiness status; (3) Time estimate: time required to complete handover preparation; (4) Resource requirements: possible resource requirement updates.

[0205] Response mechanism: Upon receiving the notification, the terminal needs to perform the following operations: immediately assess the feasibility of the switchover, check the resource readiness, estimate the preparation time, and generate a response message.

[0206] Processing flow: Upon receiving the Target_Notification, the terminal first assesses its own status and handover conditions. If the conditions are met, it sends an accept response via the sub-7GHz channel; if there is a problem, it sends a reject response explaining the reason. The entire response process must be completed within 1ms.

[0207] In this embodiment, during the aforementioned handover preparation and execution process, the terminal and the source AP can maintain existing millimeter-wave link data transmission, ensuring service continuity. This is particularly important for applications requiring high bandwidth and low latency.

[0208] The content of millimeter wave data transmission may include: (1) service data: transmitted via the 60GHz band; (2) beam tracking information: real-time beam alignment parameters; (3) link quality indicators: used to dynamically adjust transmission parameters; (4) performance monitoring data: used to evaluate transmission performance.

[0209] The transmission mechanism for millimeter-wave data is as follows: Dynamic beam tracking: real-time adjustment of beam direction; Adaptive MCS: adjustment based on link quality; Spatial multiplexing: improving spectrum utilization efficiency; Dual-link parallel operation: maintaining two links simultaneously during the preparation phase.

[0210] Processing flow: During the switchover preparation phase, the source AP continues to provide data services via the millimeter-wave link, while simultaneously performing beam tracking and parameter optimization. The entire process must maintain service continuity, control latency to within 1ms, and ensure an unaffected user experience.

[0211] The embodiments of this application can realize the functions of pre-switching detection and target selection. When link quality problems occur, the target AP can be automatically detected and selected, reducing handover latency. At the same time, it can also ensure uninterrupted data transmission of services and improve user experience.

[0212] Example 2: Predictive link assessment.

[0213] Application scenarios: Millimeter-wave MLO link prediction in high-speed mobile scenarios, such as high-speed rail stations and airports, requires accurate prediction of link quality changes to enable early handover preparation.

[0214] Figure 6 is a schematic diagram of the predictive link evaluation process in an embodiment of this application. As shown in Figure 6, the process includes the following steps:

[0215] Step S601: The mobile terminal sends an MLO quality report (MLO_Quality_Report) to the source AP;

[0216] Step S602: The source AP performs historical data analysis;

[0217] Step S603: The source AP undergoes LSTM prediction processing;

[0218] Step S604: The source AP shares the prediction results with the target AP;

[0219] Step S605: The target AP performs a link availability assessment.

[0220] In this embodiment, the control signaling in steps S601 to S605 is transmitted through a sub-7GHz control channel. During the execution of steps S601 to S605, the mobile terminal can continuously transmit data and perform beam tracking with the source AP on the millimeter-wave data channel, avoiding connection interruption and thus improving user experience. After step S605, the mobile terminal can also perform beam training preparation with the target AP to accelerate the subsequent connection establishment process. Steps S601 to S605 will be described in detail below.

[0221] Step S601: The mobile terminal sends an MLO quality report (MLO_Quality_Report) to the source AP.

[0222] In a distributed MLO system, it is necessary to monitor the link quality of both millimeter-wave and sub-7GHz channels simultaneously. Since millimeter-wave links are susceptible to obstruction and fading, reporting quality data via a reliable sub-7GHz channel ensures reliable transmission of control signaling. This separation design avoids competition between control signaling and high-speed data transmission, thus improving system reliability.

[0223] Report Content: The MLO quality report includes parameters such as RSSI (threshold -75dBm), CSI matrix, and beam alignment deviation for millimeter-wave links, as well as reliability metrics, channel utilization, and interference levels for sub-7GHz links. This comprehensive information is used to assess the current link status and predict future trends.

[0224] Reporting Mechanism: The system employs a dual reporting mechanism. Periodic reporting is used, with the period shortened for high-speed mobile scenarios. Event reporting is triggered when the millimeter-wave RSSI falls below a threshold, beam alignment deviation is excessive, or CSI changes significantly (exceeding 12%). This mechanism ensures the system can promptly obtain information on link status changes.

[0225] Processing flow: The terminal continuously monitors dual-link quality indicators and sends reports via the sub-7GHz channel. Upon receiving the reports, the source AP updates its link state database and triggers a predictive analysis process. This entire process ensures the real-time performance and reliability of the data.

[0226] Step S602: The source AP performs historical data analysis.

[0227] In millimeter-wave MLO systems, historical data analysis is fundamental for predicting link quality changes. By analyzing historical link data, patterns of link quality variation, beamforming modes, and motion characteristics can be identified, providing reliable training data for LSTM prediction models. This is particularly important for predictive maintenance and handover decisions for millimeter-wave links.

[0228] Analysis content: The system analyzes data from the most recent 100 sampling points, including the RSSI variation trend, CSI matrix evolution, and beam alignment deviation changes of the millimeter-wave link. Simultaneously, it combines historical data from the sub-7GHz link to construct a complete link state timing characteristic. The analysis window is 1 second to ensure the capture of the complete change cycle.

[0229] Analysis Mechanism: An adaptive analysis mechanism is employed to filter outliers and standardize the raw data. In high-speed mobile scenarios, the analysis cycle is shortened, improving timeliness. The system uses pattern recognition algorithms to extract link attenuation patterns, mobile scene features, and interference characteristics, providing input for the prediction model.

[0230] Processing flow: Upon receiving the MLO quality report, the source AP immediately initiates data preprocessing, including data cleaning, feature extraction, and pattern recognition. The processing results are stored in the prediction database, triggering the LSTM prediction process. The entire analysis process must be completed within 5ms.

[0231] Step S603: The source AP undergoes LSTM prediction processing.

[0232] The high data rate and directivity of millimeter-wave links require systems capable of accurately predicting changes in link quality. LSTM models can effectively capture temporal characteristics and predict the link status 20 time points in the future, providing a basis for handover decisions. This predictive capability is crucial for reducing handover latency and improving handover success rates.

[0233] Prediction content: The system predicts link quality changes within the next 200ms, including RSSI trends, CSI changes, and beam alignment status. It also predicts the terminal's movement trajectory, including location, speed, and direction. Prediction accuracy is required to exceed 90% to ensure accurate handover decisions.

[0234] Prediction Mechanism: The LSTM model employs a real-time training mechanism, continuously optimizing model parameters based on the latest historical data. The prediction cycle is synchronized with the link quality report. The system ensures prediction reliability through accuracy verification and dynamic correction of the prediction results.

[0235] Processing flow: The source AP performs LSTM prediction based on preprocessed historical data. The prediction results include link quality trends and movement trajectory predictions. The entire prediction process needs to be completed within 3ms to support rapid handover decisions.

[0236] Step S604: The source AP shares the prediction results with the target AP.

[0237] In a distributed MLO system, prediction results need to be shared between the source and target APs to support collaborative decision-making and resource reservation. Reliable information sharing via a sub-7GHz channel ensures the timeliness and accuracy of handover preparation.

[0238] Shared content: The prediction results include key information such as link quality trends, mobile trajectory predictions, and resource demand predictions. It also includes reliability metrics for the predictions, such as prediction confidence level, error range, and timeliness indicators. This information helps the target access point (AP) prepare resources in advance.

[0239] Sharing Mechanism: The system adopts a basic sharing period of 20ms, triggering an emergency update when a significant change in link quality is predicted. A selective sharing mechanism filters information based on its importance and degree of change, avoiding signaling overhead.

[0240] Processing flow: The source AP sends the prediction result to the target AP via a sub-7GHz channel. Upon receiving the result, the target AP immediately processes it and assesses resource preparation requirements. The entire sharing process must be completed within 2ms to ensure timely information delivery.

[0241] Step S605: The target AP performs a link availability assessment.

[0242] The target access point (AP) needs to be evaluated based on the prediction results to determine whether it can provide reliable millimeter-wave link services to the terminal. This evaluation ensures the accuracy of the handover decision and avoids switching to an unsuitable AP.

[0243] Evaluation content: The evaluation includes multiple dimensions such as predicted link quality, resource availability, and beam resource status. The system calculates the Stability Index (SI), comprehensively considering signal strength, resource margin, and interference level. The evaluation results directly affect handover decisions.

[0244] Evaluation mechanism: An evaluation period of 100ms is adopted, and the evaluation parameters are dynamically adjusted based on the prediction results. The system sets an availability threshold of 0.9; only APs exceeding this threshold can be used as switching targets.

[0245] Processing flow: Upon receiving the prediction results, the target AP immediately initiates an availability assessment. After the assessment is complete, an assessment report is generated and fed back to the source AP via a sub-7GHz channel. The entire assessment process must be completed within 5ms.

[0246] Through the embodiments of this application, the function of predictive link evaluation can be realized, avoiding switching to an unsuitable target AP, and reducing handover latency and improving user experience through beam training preparation.

[0247] Example 3: Resource pre-allocation.

[0248] Application scenarios: Millimeter-wave MLO resource coordination in high-density user environments, such as shopping malls and conference centers, where resources need to be reserved and allocated in advance to ensure a seamless handover.

[0249] Figure 7 is a schematic diagram of the resource pre-allocation process in an embodiment of this application. As shown in Figure 7, the process includes the following steps:

[0250] Step S701: The source AP sends a resource reservation request (Resource_Reserve_Frame) to the target AP;

[0251] Step S702: The target AP performs resource detection;

[0252] Step S703: The target AP sends a resource response (Resource_Response) to the source AP;

[0253] Step S704: The source AP sends security parameters (Security_Parameters) to the target AP;

[0254] In step S705, the target AP sends resource allocation information (Resource_Allocation_Info) to the source AP, and the source AP forwards the resource allocation information to the mobile terminal.

[0255] Step S706: The mobile terminal sends a resource confirmation (Resource_Confirm) to the source AP;

[0256] Step S707: The mobile terminal performs initial beam training with the target AP;

[0257] Step S708: The mobile terminal verifies the reserved resources with the target AP.

[0258] In this embodiment, the control signaling in steps S701 to S706 is transmitted through a sub-7GHz control channel. Steps S707 to S708 are implemented through a millimeter-wave data channel (60GHz). Steps S701 to S708 will be described in detail below.

[0259] Step S701: The source AP sends a resource reservation request (Resource_Reserve_Frame) to the target AP.

[0260] In millimeter-wave MLO systems, due to high bandwidth requirements and directional transmission characteristics, sufficient resources need to be reserved in advance. Sending resource reservation requests via the sub-7GHz channel ensures that the target AP can prepare the necessary spectrum and computing resources for the incoming terminal. This reservation mechanism is crucial for achieving seamless handover.

[0261] Reserved Content: The resource reservation frame contains detailed resource requirements: 320MHz millimeter-wave bandwidth requirement, 4×80MHz subcarrier configuration scheme, beam resource requirements, computing resource requirements, etc. It also includes MLO capability requirements to ensure the target AP can support multi-link aggregation operations.

[0262] Reservation Mechanism: The system adopts a priority-based reservation mechanism. High-priority services (such as VR / AR) are granted a reservation time of 200ms, while ordinary services receive 100ms. The reservation request contains a detailed set of QoS parameters, supporting differentiated resource allocation.

[0263] Processing flow: The source AP sends a reservation request, containing a complete description of its resource requirements, to the target AP via a sub-7GHz channel. The target AP must complete the resource assessment and reservation operation within 2ms and return an acknowledgment message.

[0264] Step S702: The target AP performs resource detection.

[0265] The target access point (AP) needs to undergo a detailed check of its current resource status to ensure it can meet the requirements of the new terminal. This check involves spectrum resources, computing resources, and beam resources, and is a crucial step in ensuring quality of service.

[0266] The inspection includes: (1) Spectrum resource inspection: 320MHz bandwidth availability, subcarrier allocation scheme, interference level assessment; (2) Computing resource inspection: CPU load (<70%), memory availability, processing capacity assessment; (3) Beam resource inspection: number of available beams, spatial reuse capability, beam scheduling scheme.

[0267] Inspection Mechanism: A multi-dimensional resource inspection mechanism is adopted, with different resource thresholds set. The system uses a resource prediction algorithm to assess resource availability during the reservation period, ensuring the sustainability of resource allocation.

[0268] Processing flow: Upon receiving a reservation request, the target AP immediately initiates a resource check process. After the check is completed, a detailed resource status report is generated to provide a basis for reservation decisions. The entire check process must be completed within 1ms.

[0269] Step S703: The target AP sends a resource response (Resource_Response) to the source AP.

[0270] In millimeter-wave MLO systems, the target AP needs to report the resource reservation results to the source AP via a sub-7GHz channel. This response ensures that both the source AP and the terminal are aware of the target AP's readiness status, which is a crucial prerequisite for initiating the handover process.

[0271] Response content: (1) Resource reservation status: reservation result (success / partial success / failure), reserved resource details (spectrum, calculation, beam), validity period (200ms); (2) MLO configuration information: available subcarrier configuration, beam parameter set, link aggregation scheme.

[0272] Response Mechanism: The system employs a tiered response mechanism. When the reserved requirements are fully met, a complete success message is returned; when only some requirements are met, an alternative solution is returned; and when critical requirements cannot be met, a failure message is returned. Response messages are sent via a sub-7GHz channel to ensure reliable transmission.

[0273] Processing flow: After completing the resource check, the target AP immediately generates a response message. The response needs to be completed within 1ms and contains detailed resource reservation information to provide a basis for subsequent handover preparation.

[0274] Step S704: The source AP sends security parameters (Security_Parameters) to the target AP.

[0275] In a distributed MLO system, the security of the handover process must be ensured. Security parameters are transmitted via a sub-7GHz channel to provide security for the upcoming millimeter-wave link.

[0276] Transmitted content: (1) Authentication parameters: PMKSA information, ECC-256 key material, authentication vector; (2) Encryption parameters: encryption algorithm selection, key update cycle, security policy configuration.

[0277] Transmission mechanism: A dual encryption mechanism is employed. First, the existing security context of the sub-7GHz link is used to encrypt the transmission, while simultaneously preparing security parameters for the newly established millimeter-wave link. The system supports fast re-authentication, reducing authentication latency.

[0278] Processing flow: The source AP transmits security parameters to the target AP via a secure sub-7GHz channel. After verifying the parameters, the target AP prepares the security context. The entire process must be completed within 3ms.

[0279] In step S705, the target AP sends resource allocation information (Resource_Allocation_Info) to the source AP, and the source AP forwards the resource allocation information to the mobile terminal.

[0280] The terminal needs to understand the specific resource reservations of the target AP to prepare for handover. This information is transmitted via a sub-7GHz channel to ensure that the terminal can correctly configure the millimeter-wave link parameters.

[0281] The allocation information includes: (1) Spectrum resource allocation: center frequency, bandwidth configuration (320MHz), subcarrier mapping; (2) Beam parameters: initial beam configuration, training sequence parameters, spatial multiplexing information.

[0282] Allocation Mechanism: The system employs a priority-based allocation mechanism to ensure that critical services receive sufficient resources. The allocation information includes detailed timing arrangements to ensure that terminals can accurately execute the handover process.

[0283] Processing flow: The target AP sends allocation information to the terminal via a sub-7GHz channel. Upon receiving the information, the terminal configures its parameters and prepares to initiate beam training. The entire process must be completed within 2ms.

[0284] Step S706: The mobile terminal sends a resource confirmation (Resource_Confirm) to the source AP.

[0285] In millimeter-wave MLO systems, the terminal needs to acknowledge the received resource allocation information and indicate whether it is ready. An acknowledgment message is sent via the sub-7GHz channel to ensure the accuracy of resource allocation and the completeness of handover preparation.

[0286] Confirmed content: (1) Resource reception status: parameter verification results, resource matching degree evaluation, and ready status; (2) Terminal capability feedback: actual processing capability, beam tracking capability, and MLO support capability.

[0287] Confirmation Mechanism: Upon receiving resource allocation information, the terminal immediately performs parameter verification and capability matching checks. If any mismatch or problem is found, it promptly reports it via the sub-7GHz channel to avoid handover failure.

[0288] Processing flow: After completing parameter verification, the terminal sends an acknowledgment message to the target AP via the sub-7GHz channel. The acknowledgment process needs to be completed within 1ms to ensure the continuity of the handover process.

[0289] Step S707: The mobile terminal performs initial beam training with the target AP.

[0290] The directionality of millimeter-wave communication requires precise beam alignment before establishing a new link. Initial beam training is performed using the 60 GHz band to establish the optimal beam configuration for subsequent data transmission.

[0291] Training content: (1) Beam scanning parameters: scanning angle range, scanning step value, beam width configuration; (2) Training sequence: pilot signal design, timing arrangement, feedback mechanism.

[0292] Training mechanism: A layered beam training strategy is adopted, first performing coarse-grained scanning and then fine alignment. The system supports fast beam training, controlling the training time to within 2ms.

[0293] Processing flow: The terminal performs beam training with the target AP via the 60GHz band, including beam scanning, signal quality measurement, and optimal beam selection. The entire training process requires precise timing control.

[0294] Step S708: The mobile terminal verifies the reserved resources with the target AP.

[0295] Before the official switchover, it is necessary to verify the actual availability of reserved resources to ensure that the millimeter-wave link can meet business requirements. Actual testing was conducted using the 60GHz band to verify the effectiveness of the resource reservation.

[0296] Verification content: (1) Link performance verification: throughput test, delay measurement, bit error rate check; (2) Resource availability verification: bandwidth verification, beam stability, QoS guarantee capability.

[0297] Verification Mechanism: The system employs a rapid verification mechanism, verifying link performance by sending test data packets. Simultaneously, it monitors actual resource usage to ensure it matches the reserved plan.

[0298] Processing flow: The terminal and the target AP verify resources through an established millimeter-wave link. The verification result is fed back through a sub-7GHz channel, and the entire verification process is completed within 3ms.

[0299] In this embodiment, resource pre-allocation ensures reliable handover preparation for the millimeter-wave MLO system, laying the foundation for seamless handover. Each step is performed through a suitable channel (control signaling via sub-7GHz, data transmission via 60GHz), ensuring protocol reliability and efficiency. Notably, the target AP and source AP can be located in a preset area with the same security parameters. Since security parameters are shared within the preset area, the target AP can directly obtain security parameters from the source AP during the resource pre-allocation process. Subsequently, it can choose to perform security verification again (to improve security performance) or not (to improve the efficiency of secure connection establishment) as needed.

[0300] Example 4: Data pre-caching and dual-link transmission.

[0301] Application scenarios: Data transmission in high-throughput MLO application scenarios, such as 4K / 8K video streams, VR / AR and other business scenarios that require seamless switching.

[0302] Figure 8 is a schematic diagram of the data pre-caching and dual-link transmission process in an embodiment of this application. As shown in Figure 8, the process includes the following steps:

[0303] Step S801: The source AP sends a cache initialization request (Cache_Init_Request) to the target AP;

[0304] Step S802: The target AP sends a cache initialization response (Cache_Init_Response) to the source AP;

[0305] Step S803: The source AP sends sequence synchronization information (Sequence_Sync_Info) to the target AP;

[0306] Step S804: The mobile terminal maintains the original link data transmission with the source AP;

[0307] Step S805: The mobile terminal establishes a new link for data transmission with the target AP;

[0308] Step S806: The source AP and the target AP synchronize their transmission status.

[0309] In this embodiment, the control signaling in steps S801 to S803 and step S806 is transmitted through a sub-7GHz control channel. Steps S804 and S805 are implemented through a millimeter-wave data channel (60GHz). Steps S801 to S806 will be described in detail below.

[0310] Step S801: The source AP sends a cache initialization request (Cache_Init_Request) to the target AP.

[0311] In millimeter-wave MLO systems, a data buffer needs to be established at the target access point (AP) to achieve seamless handover. A buffer initialization request is initiated via the sub-7GHz channel to ensure data continuity during handover and prevent the loss or interruption of high-speed data streams.

[0312] Initialization content: (1) Cache configuration parameters: cache size (number of frames); cache policy (priority queue); timeout setting (based on service type); (2) QoS parameters: service type identifier, latency requirement, drop tolerance limit.

[0313] Initialization Mechanism: The system employs a tiered caching mechanism, allocating different sized cache spaces to services of different priorities. High-priority services (such as VR streaming) receive larger cache spaces and shorter processing latency.

[0314] Processing flow: The source AP sends an initialization request to the target AP via the sub-7GHz channel. The target AP needs to complete the buffer space allocation and parameter configuration within 2ms.

[0315] In step S802, the target AP sends a cache initialization response (Cache_Init_Response) to the source AP.

[0316] The target AP needs to confirm the allocation status of the buffer resources and feed back the initialization result to the source AP via the sub-7GHz channel. This ensures the reliable establishment of the pre-buffering mechanism.

[0317] Response content: (1) Resource allocation results: actual cache size, supported QoS levels, and processing capability parameters; (2) Performance indicators: cache processing latency, throughput limit, and concurrent processing capability.

[0318] Response Mechanism: A reliable response mechanism is employed, including detailed resource allocation information and performance parameters. If resource allocation cannot fully meet the demand, alternative solutions will be provided.

[0319] Processing flow: After the target AP completes resource allocation, it sends a response message through the sub-7GHz channel and must complete the response process within 1ms.

[0320] Step S803: The source AP sends sequence synchronization information (Sequence_Sync_Info) to the target AP.

[0321] In millimeter-wave MLO systems, to ensure orderly data transmission and correct reassembly, sequence number information needs to be synchronized between the source and destination APs. Reliable sequence synchronization is achieved through a sub-7GHz channel to avoid data duplication or loss.

[0322] Synchronization content: (1) Sequence number parameters: current sequence number, sequence number window size, retransmission counter status; (2) Synchronization control information: synchronization timestamp, window sliding speed, reassemble buffer status.

[0323] Synchronization Mechanism: A two-way confirmation synchronization mechanism is adopted to ensure that the sequence number spaces of the source AP and the target AP are completely aligned. The system supports a 10ms synchronization period to guarantee the continuity of data transmission.

[0324] Processing flow: The source AP sends synchronization information to the target AP via a sub-7GHz channel, and both sides complete the alignment of their sequence number spaces. The entire synchronization process needs to be completed within 1ms.

[0325] Step S804: The mobile terminal maintains the original link data transmission with the source AP.

[0326] During the switchover process, data transmission on the existing millimeter-wave link must be maintained until the new link is fully established and verified to be usable. This mechanism ensures service continuity.

[0327] Transmission content: (1) Service data: high-speed data stream; (2) Performance monitoring data: link quality indicators, throughput statistics, and latency measurement.

[0328] Transmission mechanism: High-speed data transmission is achieved via a 60GHz millimeter-wave link, with real-time beam tracking and parameter optimization. The system supports dynamic modulation and coding scheme (MCS) adjustments to ensure transmission efficiency.

[0329] Processing flow: The source AP continues to provide data services to the terminal through the existing millimeter-wave link, while simultaneously monitoring link quality. During transmission, end-to-end latency is ensured to be kept within 1ms.

[0330] In step S805, the mobile terminal establishes a new link for data transmission with the target AP.

[0331] After confirming that the target AP's resources are ready, it is necessary to initiate a new millimeter-wave link transmission, verify link performance, and prepare for the switchover. This process needs to be performed in parallel with the original link.

[0332] Transmitted content: (1) Test data: performance verification package, link test sequence, beam evaluation data; (2) Actual service data: partial service migration, dual-link load balancing, QoS guarantee verification.

[0333] Transmission mechanism: Data transmission is conducted via a newly established 60GHz millimeter-wave link, employing a gradual service migration strategy. The system supports dynamic resource allocation and load balancing.

[0334] Processing flow: After the terminal establishes a millimeter-wave link with the target AP, data transmission testing begins. The entire process requires real-time monitoring of link performance to ensure transmission quality.

[0335] Step S806: The source AP and the target AP synchronize their transmission status.

[0336] During parallel transmission across two links, it is necessary to synchronize the transmission status of the two links in a timely manner to ensure correct data reception and reassembly. Reliable status synchronization is achieved through a sub-7GHz channel.

[0337] Synchronization content: (1) Transmission status information: data packet statistics, sequence number progress, and cache usage; (2) Performance indicators: link quality, transmission efficiency, and handover readiness.

[0338] Synchronization Mechanism: A periodic state synchronization mechanism is adopted, with a synchronization period of 10ms. When a performance anomaly is detected, immediate synchronization is triggered to ensure timely system response.

[0339] Processing flow: The target AP reports its transmission status to the source AP via a sub-7GHz channel, and the source AP adjusts its data distribution strategy accordingly. Status synchronization needs to be completed within 2ms.

[0340] In this embodiment, the pre-buffering and dual-link transmission mechanism ensures data continuity in the millimeter-wave MLO system during handover, effectively supporting the high-speed, low-latency service requirements. By separating the control plane (sub-7GHz) and data plane (60GHz), reliable control signaling transmission and efficient data transmission are achieved.

[0341] Example 5: Dynamic load balancing mechanism.

[0342] Application scenarios: Millimeter-wave MLO load balancing in high-density user environments, such as stadiums and conference centers, where real-time adjustment of load distribution is required.

[0343] Figure 9 is a flowchart illustrating the dynamic load balancing mechanism in an embodiment of this application. As shown in Figure 9, the process includes the following steps:

[0344] Step S901: The source AP sends load exchange information (Load_Exchange_Info) to the target AP;

[0345] Step S902: The target AP performs load calculation;

[0346] Step S903: The target AP sends a load balancing decision to the source AP.

[0347] Step S904: Beam adjustment and data transmission are performed between the mobile terminal and the source AP;

[0348] Step S905: The mobile terminal establishes or adjusts a new beam with the target AP (if a new beam has already been established).

[0349] In this embodiment, the control signaling in steps S901 to S903 is transmitted through a sub-7GHz control channel. Steps S904 and S905 are implemented through a millimeter-wave data channel (60GHz). Steps S901 to S905 will be described in detail below.

[0350] Step S901: The source AP sends load exchange information (Load_Exchange_Info) to the target AP.

[0351] In a distributed MLO system, access points (APs) need to exchange load information via a sub-7GHz channel to achieve global load balancing. This is particularly important for millimeter-wave communication, as load imbalance can lead to a degradation in service quality.

[0352] Exchange content: (1) Load indicators: bandwidth utilization, number of user connections, beam resource occupancy, QoS statistics; (2) Resource status: available spectrum resources, computing resource margin, beam resource status.

[0353] Switching mechanism: A periodic switching mechanism is adopted, with a basic period of 100ms. When the load change exceeds a threshold (20%), instant switching is triggered. The reliability of information exchange is ensured through a sub-7GHz channel.

[0354] Processing flow: The source AP sends load information, including a complete load status description, to the target AP via a sub-7GHz channel. The exchange process must be completed within 2ms.

[0355] Step S902: The target AP performs load calculation.

[0356] In millimeter-wave MLO systems, accurate calculation of the current load status is crucial to inform load balancing decisions. Comprehensive analysis of multi-dimensional load metrics ensures the rational allocation of resources.

[0357] Calculation content: (1) Comprehensive load indicators: CPU utilization (threshold 70%), memory utilization, millimeter wave channel utilization, beam resource utilization; (2) Predicted load trend: Deep Q Network (DQN) deep learning processing, load change prediction, resource demand estimation.

[0358] Calculation Mechanism: A real-time calculation mechanism is adopted, with an evaluation period of 100ms. The system learns load change patterns through the DQN algorithm to predict the load status for the next 20 time slots.

[0359] Processing flow: After receiving the load information, the target AP immediately initiates the calculation process. The entire calculation process needs to be completed within 3ms, generating a load assessment report.

[0360] Step S903: The target AP sends a load balancing decision to the source AP.

[0361] Based on the load calculation results, the system needs to formulate a reasonable load balancing strategy to coordinate the resource allocation of each AP through the sub-7GHz channel and ensure the service quality of the millimeter wave link.

[0362] Decision content: (1) Balancing strategy: user reallocation scheme, resource adjustment plan, beam reconfiguration strategy; (2) Execution parameters: adjustment time window, priority setting, QoS guarantee measures.

[0363] Decision-making mechanism: A priority-based decision-making mechanism is adopted to ensure the service quality of critical business operations. The system supports gradual load balancing to avoid sudden performance fluctuations.

[0364] Processing flow: After the target AP generates a decision, it notifies the relevant APs via the sub-7GHz channel. The decision-making process needs to be completed within 2ms.

[0365] In step S904, the mobile terminal and the source AP perform beam adjustment and data transmission.

[0366] In millimeter-wave MLO systems, after load balancing decisions are made, beam parameters need to be adjusted via the 60GHz link to optimize spatial multiplexing efficiency. This adjustment ensures high-quality data transmission during load balancing.

[0367] Adjustment content: (1) Beam parameters may include: beam direction, supporting adjustment speed of 300° / s; power level, multi-level dynamic adjustment; beam width, adaptive configuration; spatial multiplexing parameters; (2) Transmission parameters: MCS level adjustment, power allocation scheme, subcarrier mapping.

[0368] Adjustment Mechanism: A real-time beam tracking and adjustment mechanism is employed, performing beam optimization simultaneously with data transmission via the 60GHz link. The system supports Co-BF cooperative beamforming, providing 18dB gain.

[0369] Processing flow: The terminal and the source AP maintain data transmission via a millimeter-wave link while beam parameter optimization is performed. Service continuity must be guaranteed throughout the entire process.

[0370] Step S905: The mobile terminal establishes or adjusts a new beam with the target AP (if a new beam has already been established).

[0371] To support load balancing, a new millimeter-wave link needs to be established with the target AP. A high-quality beam connection is established via the 60GHz band to prepare for data migration. Furthermore, if a beam has already been established between the mobile terminal and the target AP, dynamic load balancing can continue to be achieved on the basis of dual-link parallel data transmission by adjusting the beam between the mobile terminal and the target AP.

[0372] The content to be established includes: (1) Beam training: training sequence design, beam scanning scheme, spatial separation requirements, and interference control; (2) Link verification: signal quality testing, throughput verification, delay measurement, and stability assessment.

[0373] Beam establishment mechanism: A fast beam training mechanism is adopted, completing beam establishment within 5ms. The system supports parallel beam training to improve establishment efficiency.

[0374] Processing flow: The terminal and the target AP perform beam training and link establishment via the 60GHz band. After completion, link verification is performed to ensure that service requirements are met.

[0375] In this embodiment, the dynamic load balancing mechanism achieves efficient load management of the millimeter-wave MLO system and improves the overall system performance through the cooperation of the control plane (sub-7GHz) and the data plane (60GHz).

[0376] Example 6: Link efficiency optimization mechanism.

[0377] Application scenarios: Millimeter-wave MLO link optimization in complex environments, such as mixed indoor and outdoor scenarios, where transmission parameters need to be dynamically adjusted based on channel quality.

[0378] Figure 10 is a flowchart illustrating the link efficiency optimization mechanism in an embodiment of this application. As shown in Figure 10, the process includes the following steps:

[0379] Step S1001, Channel quality monitoring;

[0380] Step S1002: Channel Quality Indicator (CQI) determination;

[0381] Step S1003, transmission mode selection;

[0382] Step S1004, adjust the wake-up interval (Target Wake Time, TWT);

[0383] Step S1005, millimeter-wave link optimization;

[0384] Step S1006, beam parameter adjustment;

[0385] Step S1007, Orthogonal Frequency Division Multiplexing (OFDM) transmission optimization;

[0386] Step S1008, efficiency evaluation.

[0387] In this embodiment, steps S1001 to S1004 are all implemented in the control plane. Steps S1005 to S1008 are all implemented in the data plane. Steps S1001 to S1008 will be described in detail below.

[0388] Step S1001, Channel quality monitoring.

[0389] In millimeter-wave MLO systems, channel quality needs to be monitored in real time, and the monitoring results are reported through the sub-7GHz channel. This monitoring mechanism is fundamental to link optimization, especially in complex environments.

[0390] Monitoring content: (1) Channel status indicators: CQI, channel status matrix, interference level measurement, time-varying characteristic analysis; (2) Link performance indicators: throughput statistics, bit error rate monitoring, delay measurement, beam stability.

[0391] Monitoring mechanism: A dual-cycle monitoring mechanism is adopted: (1) rapid monitoring: used for real-time status tracking; (2) in-depth monitoring: used for trend analysis.

[0392] Processing flow: The terminal and the access point (AP) exchange monitoring information via a sub-7GHz channel to provide a basis for subsequent optimization decisions. The monitoring data needs to be processed and analyzed in real time.

[0393] Step S1002: Determine the Channel Quality Indicator (CQI).

[0394] In millimeter-wave MLO systems, it is necessary to select an appropriate transmission mode based on the CQI value. The CQI judgment result is transmitted through the sub-7GHz channel to guide the parameter adjustment of the 60GHz link.

[0395] The judgment content is as follows: (1) CQI threshold judgment: high quality: CQI>12; medium quality: 8≤CQI≤12; low quality: CQI<8. (2) Trend analysis: short-term fluctuation assessment, long-term trend identification, and scene feature matching. Judgment mechanism:

[0396] An adaptive judgment mechanism is adopted: (1) High-speed movement, 20ms judgment cycle; (2) Stationary state, 100ms judgment cycle; (3) Sudden change trigger, real-time judgment.

[0397] Processing flow: The AP makes a judgment based on the received CQI information and sends an adjustment command through the sub-7GHz channel. The entire judgment process needs to be completed within 1ms.

[0398] Step S1003, select transmission mode.

[0399] Based on the CQI judgment results, the system needs to select the optimal transmission mode. Transmission mode switching is coordinated through the sub-7GHz channel to optimize 60GHz link performance.

[0400] Select the following options: (1) Transmission parameter configuration: Full speed mode, 320MHz bandwidth; Optimized mode, 50% subcarrier; Protection mode, critical service protection. (2) OFDM parameters: Subcarrier allocation, power configuration, coding scheme.

[0401] Selection mechanism: Dynamic mode selection: (1) CQI>12: Full speed transmission; (2) CQI≤12: OFDM optimized transmission; (3) Emergency: Protection mode.

[0402] Processing flow: The AP notifies the terminal of the selection result via the sub-7GHz channel, and the terminal executes the corresponding configuration on the 60GHz link. The handover process must be completed within 2ms.

[0403] Step S1004: Adjust the wake-up interval (Target Wake Time, TWT).

[0404] Based on link status and mobility, TWT needs to be dynamically adjusted to optimize the balance between energy consumption and performance.

[0405] Adjustments: (1) Wake-up interval: 20ms for high-speed movement; 100ms for low-speed movement; 200ms for stationary state; (2) Scheduling parameters: service cycle, wake-up duration, data transmission window.

[0406] Adjustment mechanism: Adaptive TWT adjustment: based on mobile speed, considering service type, and energy consumption balance.

[0407] Processing flow: TWT parameters are negotiated through the sub-7GHz channel, and the adjusted wake-up plan is executed on the 60GHz link.

[0408] Step S1005, millimeter-wave link optimization.

[0409] On 60GHz millimeter-wave links, real-time optimization is required based on decisions received from the sub-7GHz control channel to improve transmission efficiency.

[0410] Optimization content: (1) Physical layer parameters: 320MHz bandwidth configuration, 4×80MHz subcarrier allocation, dynamic MCS adjustment, spatial multiplexing optimization; (2) MAC layer parameters: frame aggregation level, retransmission strategy, buffer management, queue scheduling.

[0411] Optimization mechanism: Real-time optimization execution: Configuration is updated every 10ms, adjustments are made immediately in case of anomalies, and efficiency is improved by 32%.

[0412] Processing flow: Optimization configuration is performed on the 60GHz link, while the optimization effect is fed back via the sub-7GHz channel. The entire optimization process must be completed within 3ms.

[0413] Step S1006, beam parameter adjustment.

[0414] The directionality of millimeter-wave communication requires real-time adjustment of beam parameters to ensure optimal communication quality.

[0415] Adjustment content: (1) Beam parameters: Direction, supports 300° / s adjustment; Power, 15 levels of dynamic adjustment; Beamwidth, adaptive configuration; Gain, target 18dB; (2) Tracking parameters: Angle accuracy, tracking rate, prediction compensation, interference suppression.

[0416] Adjustment mechanism: Dynamic beam tracking: real-time angle compensation, predictive adjustment, and fast recovery mechanism.

[0417] Processing flow: Beam adjustment is performed on the 60GHz link, and the adjustment results are fed back through the sub-7GHz channel.

[0418] Step S1007, OFDM transmission optimization.

[0419] In complex environments, it is necessary to optimize OFDM transmission parameters and improve spectrum utilization efficiency.

[0420] Optimization content: (1) Subcarrier configuration: subcarrier selection, power allocation scheme, bit loading optimization, pilot design; (2) Coding and modulation: adaptive MCS, interleaving parameters, error correction capability, constellation mapping.

[0421] Optimization mechanism: Adaptive optimization: Based on channel conditions, considering service requirements, and dynamically adjusting strategies.

[0422] Processing flow: OFDM optimization is performed on the 60GHz link, and control and feedback are carried out through the sub-7GHz channel.

[0423] Step S1008, efficiency evaluation.

[0424] The optimization effect needs to be evaluated in real time to guide subsequent adjustment strategies.

[0425] Evaluation content: (1) Performance indicators: throughput improvement, latency improvement, bit error rate reduction, energy efficiency improvement; (2) Resource utilization: spectrum efficiency, spatial reuse, energy efficiency, processing overhead.

[0426] Evaluation Mechanism: Continuous evaluation mechanism: real-time performance monitoring, periodic statistics, and trend analysis.

[0427] Processing flow: The evaluation results are reported through the sub-7GHz channel to guide the adjustment of the system optimization strategy. The evaluation period is 100ms.

[0428] In this embodiment of the application, the overall system performance can be improved through the link efficiency optimization mechanism, thereby enhancing the user experience.

[0429] Example 7: Security Enhancement Mechanism.

[0430] Application scenarios: Millimeter-wave MLO service scenarios requiring high security, such as enterprise networks and financial institutions, where the security of the handover process needs to be ensured.

[0431] Figure 11 is a flowchart illustrating the security enhancement mechanism in an embodiment of this application. As shown in Figure 11, the process includes the following steps:

[0432] Step S1101: The mobile terminal sends a security request (Security_Request) to the source AP;

[0433] Step S1102: The source AP sends a Hash-Based Message Authentication Code (HMAC) verification (HMAC_Verification) to the target AP;

[0434] Step S1103: The target AP performs key generation (Key_Generation);

[0435] Step S1104: The target AP sends security parameters (Security_Parameters) to the source AP, and the source AP forwards the security parameters to the mobile terminal.

[0436] Step S1105: The mobile terminal establishes a secure beam with the target AP;

[0437] Step S1106: The mobile terminal transmits encrypted data with the target AP.

[0438] In this embodiment, the control signaling in steps S1101 to S1104 is transmitted through a sub-7GHz control channel. Steps S1105 and S1106 are implemented through a millimeter-wave data channel (60GHz). Steps S1101 to S1106 will be described in detail below.

[0439] Step S1101: The mobile terminal sends a security request (Security_Request) to the source AP.

[0440] In millimeter-wave MLO systems, a secure authentication request needs to be initiated via a reliable sub-7GHz channel to establish a security mechanism during handover. This is crucial for protecting high-speed millimeter-wave data transmission.

[0441] Request content: (1) Authentication parameters: authentication type selection, security level requirements, timestamp information, random number generation; (2) Capability declaration: supported encryption algorithms, authentication protocol version, key generation capability, security processing performance;

[0442] Request mechanism: Employs a two-factor authentication mechanism: fast authentication, completed within 5ms; full authentication, initiated when needed; emergency rollback and exception handling.

[0443] Processing flow: The terminal sends a security request to the source AP via the sub-7GHz channel to initiate the authentication process. The entire request process must be completed within 2ms.

[0444] Step S1102: The source AP sends an HMAC verification (HMAC_Verification) to the target AP.

[0445] In millimeter-wave MLO systems, message authentication is required via a sub-7GHz channel to ensure the authenticity and integrity of control signaling during handover.

[0446] Verification content: (1) HMAC calculation: using SHA-256 algorithm, key length is 256 bits, message integrity verification, time window is 10ms; (2) Security parameter verification: timestamp check, sequence number verification, permission level confirmation, security policy matching.

[0447] Verification mechanism: Employs a fast verification process: verification latency <5ms; parallel processing; caching mechanism; exception handling.

[0448] Processing flow: The source AP and the target AP complete HMAC verification through the sub-7GHz channel to ensure the establishment of secure communication.

[0449] Step S1103: The target AP performs key generation (Key_Generation).

[0450] A security key is generated for the newly established millimeter-wave link, and the key is distributed via a sub-7GHz channel.

[0451] The generated content includes: (1) Key materials: PSK-T temporary key, session key pair, authentication vector, key update parameters; (2) Security context: encryption algorithm selection, key lifecycle, update strategy, backup mechanism.

[0452] Generation mechanism: A hierarchical key system is adopted: master key generation, session key derivation, real-time updates, and secure storage.

[0453] Processing flow: The target AP generates a new key and securely distributes it via the sub-7GHz channel. The generation process must be completed within 3ms.

[0454] In step S1104, the target AP sends security parameters (Security_Parameters) to the source AP, and the source AP forwards the security parameters to the mobile terminal.

[0455] In millimeter-wave MLO systems, security parameters need to be distributed to terminals via sub-7GHz channels to establish a security protection mechanism for 60GHz high-speed links.

[0456] Parameter content: (1) Encryption parameters: ECC-256 key material, encryption algorithm configuration, key update cycle, security policy set; (2) Authentication parameters: PMKSA information, authentication vector, session identifier, timeliness control.

[0457] Transmission mechanism: A secure transmission mechanism is adopted, including segmented transmission, integrity protection, timeliness verification, and confirmation mechanism.

[0458] Processing flow: The target AP sends security parameters to the terminal via the sub-7GHz channel. The transmission process must be completed within 2ms.

[0459] Step S1105: The mobile terminal establishes a secure beam with the target AP.

[0460] After completing the security parameter configuration, a secure beam connection needs to be established in the 60GHz band to ensure the security of high-speed data transmission.

[0461] The content to be established includes: (1) Beam parameters: encrypted beam training, secure space reuse, interference protection, and certified beam sequence; (2) Security verification: beam integrity check, identity association verification, spatial isolation guarantee, and security level confirmation.

[0462] Establish a mechanism: Implement secure beam training: encrypted training sequences, authentication feedback, dynamic adjustment, and anti-interference protection.

[0463] Processing flow: The terminal and the target AP perform secure beam establishment in the 60GHz band to ensure physical layer security.

[0464] Step S1106: The mobile terminal transmits encrypted data with the target AP.

[0465] High-speed encrypted data transmission is required on millimeter-wave links to protect the security of business data.

[0466] Transmission content: (1) Data encryption: real-time encryption processing, integrity protection, replay protection, key update; (2) Security monitoring: anomaly detection, performance monitoring, security audit, threat response.

[0467] Transmission mechanism: High-efficiency encryption mechanism: hardware acceleration, stream encryption, block encryption, and security feedback.

[0468] Processing flow: Encrypted data transmission is performed on the 60GHz link, with security control via the sub-7GHz channel.

[0469] In this embodiment, this security enhancement mechanism achieves comprehensive security protection for the millimeter-wave MLO system through the cooperation of the control plane (sub-7GHz) and the data plane (60GHz), meeting the needs of high-security scenarios.

[0470] Example 8: Overall Mobility Management Process.

[0471] Application scenarios: Millimeter-wave MLO mobility management in high-speed mobile scenarios, such as high-speed rail stations and airports, requires predictive handover and seamless service migration.

[0472] Figure 12 is a schematic diagram of the overall mobility management process in an embodiment of this application. As shown in Figure 12, the process includes the following steps:

[0473] Step S1201: The source AP broadcasts load information to the mobile terminal;

[0474] Step S1202: The mobile terminal performs target AP screening;

[0475] Step S1203: The mobile terminal performs motion trajectory prediction;

[0476] Step S1204: The mobile terminal sends a link establishment request to the target AP;

[0477] Step S1205: The target AP performs resource pre-allocation;

[0478] Step S1206: The source AP and the mobile terminal perform original link data transmission;

[0479] Step S1207: The source AP sends a data packet buffer to the target AP;

[0480] Step S1208: The mobile terminal establishes a new link and migrates data with the target AP.

[0481] In this embodiment, the control signaling in steps S1201 to S1205 is transmitted through a sub-7GHz control channel. Steps S1206 to S1208 are implemented through a millimeter-wave data channel (60GHz). Steps S1201 to S1208 will be described in detail below.

[0482] Step S1201: The source AP broadcasts load information to the mobile terminal.

[0483] In a distributed MLO system, the load and beam information of neighboring APs need to be periodically broadcast through the sub-7GHz channel so that the terminal can identify potential handover targets in advance.

[0484] Broadcast content: (1) AP status information: current load level, available resources, service quality indicators, beam configuration parameters; (2) Network topology information: location of adjacent APs, coverage area, supported service types, MLO capability set.

[0485] Broadcast mechanism: period is 100ms; trigger condition: load change exceeds 20%; update strategy: real-time load status; transmission reliability is guaranteed.

[0486] Step S1202: The mobile terminal performs target AP screening.

[0487] The terminal needs to select the optimal potential handover target based on the received broadcast information and its own needs.

[0488] Screening criteria: (1) Evaluation indicators: load balancing, resource availability, signal quality prediction, and service support capability; (2) Screening strategy: multi-dimensional scoring, dynamic weight adjustment, historical performance consideration, and mobile prediction.

[0489] Step S1203: The mobile terminal performs motion trajectory prediction.

[0490] Predicting user movement trajectories using inertial measurement unit (IMU) data provides a basis for beam tracking and handover decisions.

[0491] Prediction content: (1) IMU data processing: acceleration analysis, angular velocity calculation, direction recognition, velocity estimation; (2) Trajectory modeling: Kalman filtering, prediction algorithm, error compensation, real-time update.

[0492] Steps S1204 to S1208 mainly involve the establishment of parallel links and data migration, which are used to ensure service continuity during the handover process and achieve zero packet loss transmission. For specific implementation details, please refer to the relevant descriptions in the preceding embodiments.

[0493] Implementation mechanism: (1) Triggering conditions: RSSI is below the threshold, predicting an imminent switchover, and resources are reserved and ready; (2) Resource pre-allocation: millimeter wave resource blocks, beam configuration parameters, buffer space allocation, and QoS guarantee configuration; (3) Data plane processing: dual connection maintenance, data packet caching, sequence number synchronization, and zero packet loss transmission; (4) Beam tracking compensation: dynamic angle adjustment, predictive compensation, real-time feedback control, and performance improvement of 70%.

[0494] In this embodiment, the mobility management mechanism achieves efficient and reliable millimeter-wave MLO mobility management through technologies such as pre-switching detection, parallel link establishment, data plane migration, and beam tracking compensation, making it particularly suitable for high-speed mobile scenarios.

[0495] Example 9: Handover between sub-7GHz devices.

[0496] Application scenarios include:

[0497] Scenario A supports make-before-break mode: The prerequisite is that the STA must be an MLO device. In this case, the STA can maintain a connection with both the source AP and the target AP at the same time.

[0498] Scenario B, the traditional break-before-make mode: when the above prerequisites are not met, i.e. the STA is not an MLO device, only the traditional handover method can be used.

[0499] Figure 13 is a schematic diagram of the handover process between sub-7GHz devices in an embodiment of this application. As shown in Figure 13, the process includes the following stages:

[0500] Phase 1, MLO capability check;

[0501] In Phase 2, if the conditions are met, the make-before-break mode is used; if the conditions are not met, the break-before-make mode is used.

[0502] In Phase 1, i.e., the equipment capability assessment phase, the following operations can be performed:

[0503] 1) MLO Capability Check: Check the STA's MLO capability;

[0504] 2) Handover strategy selection: If the STA is an MLO device: use make-before-break to maintain the source AP connection while establishing a new connection; if the STA is not an MLO device: use break-before-make, the traditional handover process, which accepts a brief interruption.

[0505] Phase 2 Make-before-break switching implementation (applicable to MLO devices) includes:

[0506] 1) Preparation phase: Utilize the multi-link capability of MLO devices to maintain some links of the source AP and reserve resources for new connections;

[0507] 2) New Link Establishment: Using idle link resources, establish a connection with the target AP and verify the availability of the new link;

[0508] 3) Business migration: Gradually migrate data streams, dynamically adjust link allocation, and maintain business continuity;

[0509] 4) Complete the switchover: Confirm that the new link is stable, gradually release the source AP link, and complete the overall migration.

[0510] In Phase 2, the Break-before-make handover implementation (for non-MLO devices) adopts the traditional handover process: disconnect the source AP connection, establish a new AP connection, and resume data transmission.

[0511] In this embodiment, the following key technical points need to be considered: (1) MLO capability judgment: accurately identify the MLO capability of the device, select the appropriate switching strategy, and optimize resource allocation; (2) Link management: for MLO devices: multi-link concurrent control, dynamic resource allocation, and link status monitoring; for non-MLO devices: single-link switching optimization, minimizing interruption time, and fast recovery mechanism; (3) Service assurance: for MLO scenarios: seamless service migration, dynamic load balancing, and smooth performance transition; for non-MLO scenarios: fast switching recovery, service priority assurance, and interruption time optimization.

[0512] The embodiments of this application can have the following application effects: (1) MLO device advantages: realize truly uninterrupted switching, ensure business continuity, and provide a better user experience; (2) compatibility guarantee: support various device combinations, backward compatibility with existing mechanisms, and smooth evolution strategy.

[0513] Example 10: Switching from a sub-7GHz device to a millimeter-wave MLO device.

[0514] Application scenarios include:

[0515] Scenario A supports make-before-break, provided that the STA must be an MLO device.

[0516] In scenario B, when the STA is not an MLO device, break-before-make must be used.

[0517] Figure 14 is a schematic diagram of the process of switching from a sub-7GHz device to a millimeter-wave MLO device in an embodiment of this application. As shown in Figure 14, the process includes the following stages:

[0518] Phase 1, MLO capability check;

[0519] In Phase 2, if the conditions are met, the make-before-break mode is used; if the conditions are not met, the break-before-make mode is used.

[0520] In Phase 1, i.e., the equipment capability assessment phase, the following operations can be performed:

[0521] 1) MLO Capability Check: Check the STA's MLO capability;

[0522] 2) Switching strategy selection: If the STA is an MLO device: use make-before-break, plan multi-link resources, and prepare for concurrent connections; if the STA is not an MLO device: use break-before-make, accept service interruption, and plan for rapid switching.

[0523] The Make-before-break implementation in Phase 2 (MLO device) includes:

[0524] 1) Initial state: STA maintains connection with source AP: 2.4GHz link, 5GHz link, possible 6GHz link.

[0525] 2) New link establishment: Keep some links of the source AP active; utilize idle link resources to establish the target AP sub-7GHz main link, negotiate MLO capabilities, and prepare millimeter wave links.

[0526] 3) Millimeter-wave link activation: Through the established sub-7GHz link, coordinate millimeter-wave parameters, perform beam training, and establish millimeter-wave connection;

[0527] 4) Service migration: Service allocation is based on link characteristics, the control plane remains in sub-7GHz, high-speed data is migrated to millimeter wave, and load distribution is dynamically adjusted.

[0528] 5) Complete the switchover: After confirming that the new link is stable, gradually release the source AP link to complete the overall migration.

[0529] The Break-before-make implementation in Phase 2 (for non-MLO devices) adopts a conventional handover process: disconnect from the source AP, establish a connection to the target AP, enable millimeter wave as needed, and resume service transmission.

[0530] In this embodiment, the following key technical points need to be considered: (1) MLO capability management: strict capability checks, accurate resource planning, and dynamic link scheduling; (2) Multi-link collaboration: sub-7GHz link management, millimeter-wave link control, and cross-band collaboration; (3) Service assurance mechanism: for MLO scenarios: seamless service migration, link quality assurance, and smooth performance transition; for non-MLO scenarios: minimizing interruption time, rapid service recovery, and backup mechanism.

[0531] The embodiments of this application may have the following technical advantages: (1) MLO equipment advantages: realize truly uninterrupted switching, ensure service continuity, and provide a better experience; (2) performance improvement: efficient spectrum utilization, flexible resource scheduling, and reliability assurance.

[0532] Example 11: Switching from a millimeter-wave MLO device to a sub-7GHz device.

[0533] Application scenarios include:

[0534] Scenario A supports make-before-break, provided that the STA must be an MLO device.

[0535] In scenario B, when the STA is not an MLO device, break-before-make must be used.

[0536] Figure 15 is a schematic diagram of the process for switching from a millimeter-wave MLO device to a sub-7GHz device in an embodiment of this application. As shown in Figure 15, the process includes the following stages:

[0537] Phase 1, MLO capability check;

[0538] In Phase 2, if the conditions are met, the make-before-break mode is used; if the conditions are not met, the break-before-make mode is used.

[0539] In Phase 1, i.e., the equipment capability assessment phase, the following operations can be performed:

[0540] 1) MLO Capability Check: Check the STA's MLO capability;

[0541] 2) Switching strategy selection: If the STA is an MLO device: enable make-before-break, prioritize the use of the source AP's sub-7GHz link, and plan a smooth migration strategy; if the STA is not an MLO device: adopt break-before-make, accept service interruption, and prepare a rapid switching solution.

[0542] The Make-before-break implementation in Phase 2 (MLO device) includes:

[0543] 1) Initial state maintenance: Maintain dual-band connectivity of the source AP: keep the sub-7GHz main link active, continue service on the millimeter-wave link, and monitor the link status.

[0544] 2) Establish new connection: Utilize the sub-7GHz resources of the source AP: Scan the target AP, establish a new connection, and verify link availability.

[0545] 3) Service migration: Prioritize migration from millimeter-wave links: Transfer services to sub-7GHz links, gradually reduce millimeter-wave link load, and maintain service continuity; Smoothly switch to the target AP: Gradually migrate service flows, dynamically adjust resource allocation, and monitor service quality.

[0546] 4) Link switching complete: Verify new link: Confirm the target AP connection is stable and verify that the service is running normally; Release existing resources: Shut down the millimeter wave link, disconnect the source AP connection, and complete the switching process.

[0547] The Break-before-make implementation in Phase 2 (for non-MLO devices) uses a conventional handover process.

[0548] In this embodiment, the following key technical points need to be considered: (1) Link management strategy: Prioritize maintaining sub-7GHz connections, smoothly reduce millimeter wave services, and ensure control plane reliability; (2) Service migration mechanism: Hierarchical migration strategy: Prioritize control services, smoothly migrate data services, and dynamically adjust QoS; Resource scheduling optimization: Adapt bandwidth requirements, ensure link quality, and control load balancing; (3) Reliability guarantee: Dual link backup mechanism, rapid fault detection, and emergency rollback scheme.

[0549] The embodiments of this application can have the following technical advantages: (1) Service continuity: zero interruption switching, smooth performance transition, QoS guarantee; (2) Resource utilization: efficient spectrum use, dynamic load adjustment, flexible link scheduling; (3) Reliability improvement: multi-link redundancy, fast fault recovery, stability guarantee.

[0550] Example 12: Millimeter-wave MLO device handover (make-before-break strategy).

[0551] Application scenario: Switching between two millimeter-wave MLO devices using the make-before-break strategy; the prerequisite is that the STA must be an MLO device, and both the source AP and the target AP are millimeter-wave MLO devices (supporting sub-7GHz and millimeter-wave).

[0552] Figure 16 is a schematic diagram of the handover process between millimeter-wave MLO devices in an embodiment of this application. As shown in Figure 16, the process includes the following stages:

[0553] Phase 1, initial state, for example, the connection state between the STA and the source AP, including:

[0554] 1) Sub-7GHz main link: 2.4 / 5 / 6GHz link, responsible for control plane communication, ensuring reliable connection.

[0555] 2) Millimeter wave link: 60GHz high-speed link, carrying data services and providing high throughput.

[0556] Phase 2, the switch preparation phase, includes:

[0557] 1) Target AP discovery: Scan target APs through the sub-7GHz link of the source AP to obtain MLO capabilities and assess link quality; collect millimeter wave information, including available channel resources, beamforming capabilities, and spatial coverage.

[0558] 2) Resource assessment: Determine available links, including: identifying idle sub-7GHz resources and assessing millimeter wave feasibility; plan handover timing, including: designing link establishment sequence and preparing resource allocation scheme.

[0559] Phase 3, the new link establishment phase, includes:

[0560] 1) Maintain source AP connectivity: Maintain existing services, including: maintaining the sub-7GHz control link and continuing millimeter-wave data transmission; monitor link status, including: tracking link quality and recording performance metrics.

[0561] 2) Establish target AP connection: Establish sub-7GHz main link, utilize idle resources, complete authentication association, and establish control channel; enable millimeter wave link, perform beam training, establish high-speed connection, and verify link performance.

[0562] Phase 4, the business migration phase, includes:

[0563] 1) Control plane migration: Through the sub-7GHz link, control information is synchronized to prepare for service switching and ensure reliability.

[0564] 2) Data plane migration: Millimeter wave link switching, establishing new data channels, gradually migrating business flows, and dynamically adjusting the load.

[0565] Phase 5, completing the transition phase, includes:

[0566] 1) Performance optimization: Dual-band collaboration optimizes resource allocation, adjusts link configuration, and balances load distribution.

[0567] 2) Release source AP resources: Confirm migration is complete, verify service stability, and check performance indicators; disconnect the original link, shut down the millimeter-wave link, and release sub-7GHz resources.

[0568] In this embodiment, the following key technical points need to be considered: (1) Dual-band concurrent management: sub-7GHz main link guarantee, millimeter wave link dynamic adjustment, and resource collaborative allocation; (2) Seamless service migration: reliable control plane switching, smooth data plane migration, and zero performance interruption; (3) Link quality assurance: real-time performance monitoring, dynamic resource adjustment, and rapid fault recovery.

[0569] The embodiments of this application can have the following technical advantages: (1) Service continuity: truly uninterrupted switching, smooth performance transition, and continuous QoS guarantee; (2) Efficient resource utilization: dual-band collaboration, dynamic load balancing, and flexible resource scheduling; (3) Reliability guarantee: multi-link redundancy, real-time performance optimization, and rapid fault response.

[0570] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0571] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0572] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps in any of the above method embodiments.

[0573] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0574] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0575] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0576] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0577] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0578] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than that described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0579] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method of distributed multi-link operation (MLO) mobility management, applied to a multi-link device (MLD) terminal, the MLD terminal comprising a first frequency band and a millimeter wave frequency band, wherein, The method comprises: performing control signaling transmission with the source access point and / or the target access point in the first frequency band to establish a connection with the target access point and perform user data transmission with the source access point and / or the target access point in the millimeter wave frequency band; wherein the source access point and the target access point belong to the same preset area or different preset areas.

2. The method of claim 1, wherein, The same preset area adopts the same security parameter, and the different preset areas adopt different security parameters.

3. The method of claim 1, wherein, The first frequency band comprises one or more sub-7GHz frequency bands, and the first frequency band is also used for transmitting control signaling and user data.

4. The method of claim 1, wherein, The control signaling transmission with the source access point and / or the target access point in the first frequency band to establish a connection with the target access point and perform user data transmission with the source access point and / or the target access point in the millimeter wave frequency band comprises at least one of: performing user data transmission with the source access point in the millimeter wave frequency band; triggering the source access point to perform pre-handover detection and obtaining the target access point selected by the source access point based on the result of pre-handover detection; triggering the source access point to perform predictive link evaluation, and performing beam tracking on the source access point and beam training preparation on the target access point; obtaining resource allocation information of the target access point from the source access point, and performing initial beam training and reserved resource verification on the target access point, wherein the resource allocation information is determined by the target access point based on a resource reservation mechanism; establishing a connection with the target access point in the case that the target access point completes data pre-caching and sequence synchronization; adjusting a first beam of the MLD terminal with the source access point and establishing or adjusting a second beam of the MLD terminal with the target access point based on a load balancing mechanism, wherein the source access point and the target access point perform negotiation and decision of load balancing in the first frequency band; monitoring channel quality of the MLD terminal, and adjusting the first beam and / or the second beam based on a link optimization mechanism and the channel quality; triggering the source access point to perform security verification on the target access point, and establishing a secure connection with the target access point; obtaining broadcast information related to candidate access points, selecting the target access point according to the broadcast information, and establishing a connection with the target access point; performing user data transmission with the target access point in the millimeter wave frequency band.

5. The method of claim 4, wherein, The triggering the source access point to perform pre-handover detection and obtaining the target access point selected by the target access point based on the result of pre-handover detection comprises: sending a link quality report to the source access point, wherein the link quality report is used to trigger the source access point to perform MLO link analysis, candidate access point discovery and target access point selection; obtaining a target notification sent by the source access point, wherein the target notification carries the target access point selected by the source access point.

6. The method of claim 4, wherein, The triggering the source access point to perform predictive link evaluation, and performing beam tracking on the source access point, and beam training preparation on the target access point comprises: A link quality report is sent to the source access point, wherein the link quality report is used to trigger the source access point to perform historical data analysis on link quality and movement trajectory, long short-term memory LSTM prediction, and prediction result sharing, and the prediction result is used to trigger the target access point to perform link availability analysis; Beam tracking is performed on the source access point; If the link availability analysis indicates that the link is available, beam training preparation is performed on the target access point.

7. The method according to claim 4, wherein, The resource allocation information is a resource reservation result generated by the target access point after performing a resource check based on the resource reservation request sent by the source access point. The resource reservation request carries resource requirements, and the resource check is used to ensure that the target access point's spectrum resources, computing resources, and beam resources meet the resource requirements.

8. The method of claim 4, wherein, The source access point is used to control the target access point to perform cache initialization and sequence synchronization, and to perform transmission status synchronization in the first frequency band.

9. The method of claim 4, wherein, The method of adjusting the first beam between the MLD terminal and the source access point based on the load balancing mechanism, and establishing or adjusting the second beam between the MLD terminal and the target access point, includes: The first beam is adjusted according to the load balancing decision of the source access point and the target access point, wherein the load balancing decision is determined by the target access point after performing load calculation on the load information of the source access point and the load information of the target access point according to a preset algorithm; In response to the second beam not being established, the second beam is established according to the load balancing decision; or, in response to the second beam being established, the second beam is adjusted in the millimeter-wave frequency band according to the load balancing decision. The load balancing decision carries a balancing strategy and / or execution parameters, including beam parameters and transmission parameters.

10. The method of claim 4, wherein, The monitoring of the channel quality of the MLD terminal, and the adjustment of the first beam and / or the second beam based on the link optimization mechanism and the channel quality, includes: The channel quality of the MLD terminal is monitored to obtain channel status indicators and link performance indicators. Based on the channel status indicators, the transmission mode, transmission parameters and waveform parameters are selected, and the target wake-up time of the MLD terminal is determined based on the link performance indicators. Based on the transmission mode, the transmission parameters, the waveform parameters, and the target wake-up time, the first beam and / or the second beam are adjusted, and the efficiency of the first beam and / or the second beam is evaluated.

11. The method of claim 4, wherein, The step of triggering the source access point to perform security verification on the target access point and establish a secure connection with the target access point includes: Send a security request to the source access point, wherein the security request is used to trigger the source access point to send a Hash Message Authentication Code (HMAC) verification message to the target access point; Obtain the security parameters of the target access point forwarded by the source access point, wherein the security parameters are the security keys generated by the target access point after HMAC verification is completed; Based on the security parameters, a secure connection is established with the target access point, wherein the secure connection is used to encrypt data transmission.

12. The method of claim 4, wherein, The step of acquiring broadcast information related to candidate access points, selecting the target access point based on the broadcast information, and establishing a connection with the target access point includes: Receive load information broadcast sent by the source access point, wherein the load information broadcast carries load information of the candidate access point, wherein the candidate access point includes one or more adjacent access points of the source access point; Based on the load information broadcast, the target access point is selected from the candidate access points; Establish a connection with the target access point.

13. The method of claim 12, wherein, The method further includes at least one of the following: The inertial measurement unit (IMU) data of the MLD terminal is collected, and the movement trajectory is predicted based on the IMU data; In response to the received signal strength indicator (RSSI) of the MLD terminal being less than a preset threshold, a link establishment request is sent to the target access point in the first frequency band, wherein the link establishment request is used to trigger the target access point to perform resource pre-allocation.

14. The method of any one of claims 1 to 13, wherein, At least one of the source access point and the target access point is a multi-link device (MLD), and one of the multiple links supported by the MLD is a millimeter-wave band.

15. The method of claim 1, wherein, The method further includes: Perform MLO capability checks on the source access point and the target access point; If both the source access point and the target access point have the MLO capability, a "build-before-disconnect" mechanism is enabled. This mechanism means that the MLD terminal establishes a connection with the target access point while maintaining a connection with the source access point; or... If neither the source access point nor the target access point has the MLO capability, a disconnect-before-build mechanism is enabled. The disconnect-before-build mechanism means that the MLD terminal establishes a connection with the target access point after disconnecting from the source access point.

16. A method of distributed multi-link operation (MLO) mobility management, applied to a source multi-link device (MLD) access point, the source MLD access point comprising a first frequency band and a millimeter wave frequency band, wherein, The method includes: Control signaling is transmitted with the terminal and / or the target access point in the first frequency band to instruct the terminal to establish a connection with the target access point and to transmit user data with the terminal and / or the target access point in the millimeter wave frequency band. The source MLD access point and the target access point may belong to the same preset area or different preset areas.

17. A method of distributed multi-link operation (MLO) mobility management, applied to a target multi-link device (MLD) access point, the target MLD access point comprising a first frequency band and a millimeter wave frequency band, wherein, The method includes: Control signaling is transmitted with the terminal and / or the source access point in the first frequency band to establish a connection with the terminal and to transmit user data with the terminal and / or the source access point in the millimeter wave frequency band. The source access point and the target MLD access point may belong to the same preset area or different preset areas.

18. A computer-readable storage medium having stored therein a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 17.

19. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 17.

20. A computer program product comprising a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 17.

Images