A roaming method and apparatus

Abstract

The application relates to a roaming method and device, and relates to the technical field of communication, which is used for providing a processing flow of master-slave optical network units. The method comprises the following steps: in a roaming process of a site, a master optical network unit (MFU) sends a service closing indication message to a source optical network unit (SFU), the service closing message is used for indicating the SFU to close service interaction with the site; and the MFU receives a service closing feedback message from the SFU, the service closing feedback message is used for indicating whether the service interaction with the site is successfully closed.

Description

[0001] This application is a divisional application. The original application has the application number 202510229010.0 and the original application date is February 26, 2025. The entire contents of the original application are incorporated herein by reference.

[0002] Related cross-references

[0003] This application claims priority to Chinese Patent Application No. 202411567361.4, filed on November 4, 2024, entitled "A Roaming Method and Apparatus", and to Chinese Patent Application No. 202510186613.7, filed on February 19, 2025, entitled "A Roaming Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0005] When a terminal moves within an FTTR network and the channel quality deteriorates with its currently associated access point, it needs to roam to an access point with better channel quality to ensure service continuity. Currently, the processing flow between master and slave optical network units in an FTTR network has not been discussed. Summary of the Invention

[0006] This application provides a roaming method and apparatus for providing a master-slave optical network unit processing flow.

[0007] In a first aspect, an embodiment of this application provides a roaming method, comprising: The main optical network unit (MFU) acquires roaming decision information from the system units (SFUs) in the network; The MFU determines the target SFU for the site based on the roaming decision information; The MFU sends a roaming start indication message to the target SFU, the roaming start indication message being used to instruct the initiation of roaming processing for the site.

[0008] In one possible implementation scenario, the source access point can be an MFU. In another possible implementation scenario, the source access point can be a source SFU.

[0009] In one possible design, the roaming start indication message is carried in a Wi-Fi management control interface message.

[0010] In one possible design, the roaming initiation process includes initiating a roaming switching state machine.

[0011] In one possible design, the roaming start indication message includes the identifier of the site.

[0012] In one possible design, the method further includes: The MFU receives a roaming start confirmation message from the target SFU, which indicates that the target SFU has successfully completed roaming initiation for the site.

[0013] In one possible design, the method further includes: The MFU receives a roaming start failure message from the target SFU, the roaming start failure message indicating that the target SFU failed to initiate roaming for the site; The MFU removes roaming-related information for the site.

[0014] In one possible design, the method further includes: The MFU sends a roaming start indication message to the source SFU, the roaming start indication message being used to instruct the initiation of roaming processing for the site.

[0015] In one possible design, the method further includes: The MFU receives a roaming start confirmation message from the source SFU, which indicates that the source SFU has successfully completed roaming initiation for the site.

[0016] In one possible design, the method further includes: The MFU receives a roaming start failure message from the source SFU, the roaming start failure message indicating that the source SFU failed to initiate roaming for the site; The MFU removes roaming-related information for the site.

[0017] In one possible design, the method further includes: The MFU sends a roaming anomaly handling message to the source SFU and the target SFU. The roaming anomaly handling message is used to instruct the clearing of roaming-related information for the site.

[0018] In one possible design, the method further includes: The MFU receives a roaming exception handling completion message from the source SFU; and / or, The MFU receives the roaming exception handling completion message from the target SFU.

[0019] In one possible design, the roaming decision information includes one or more of the following: signal strength with the station, load information, or channel condition information.

[0020] Secondly, embodiments of this application provide a roaming method, including: The Sub-Optical Network Unit (SFU) receives a roaming start indication message from the Main Optical Network Unit (MFU), which is used to indicate that roaming processing should be initiated for the site; the SFU is either the source SFU currently accessed by the site or the target SFU determined by the MFU for roaming of the site. The SFU initiates roaming processing for the site.

[0021] In one possible design, the roaming start indication message is carried in a Wi-Fi management control interface message.

[0022] In one possible design, the roaming initiation process includes initiating a roaming switching state machine.

[0023] In one possible design, the roaming start indication message includes the identifier of the site.

[0024] In one possible design, the method further includes: The SFU sends the roaming start confirmation message to the MFU, the roaming start confirmation message indicating that the SFU has successfully completed the roaming initiation for the site.

[0025] In one possible design, the method further includes: The SFU sends a roaming start failure message to the MFU, the roaming start failure message indicating that the SFU failed to initiate roaming for the site.

[0026] In one possible design, the method further includes: The SFU receives a roaming error handling message from the MFU, the roaming error handling message being used to instruct the clearing of roaming-related information for the site; The SFU clears roaming-related information for the site.

[0027] In one possible design, the method further includes: The SFU sends a roaming exception handling completion message to the MFU.

[0028] In one possible design, the method further includes: The SFU sends roaming decision information to the MFU.

[0029] In one possible design, the roaming decision information includes one or more of the following: signal strength with the station, load information, or channel condition information.

[0030] Thirdly, embodiments of this application provide a roaming device that implements the functions of the first aspect and optional methods described above. The device includes at least one module for implementing the methods provided by the eleventh aspect and optional methods described above. In one possible design, applied to a main optical network unit (MFU), it includes: The receiving module is used to acquire roaming decision information of SFUs in the network; The processing module is used to determine the target SFU for the site based on the roaming decision information; The sending module is used to send a roaming start indication message to the target SFU, the roaming start indication message being used to instruct the initiation of roaming processing for the site.

[0031] In one possible design, the roaming start indication message is carried in a Wi-Fi management control interface message.

[0032] In one possible design, the roaming initiation process includes initiating a roaming switching state machine.

[0033] In one possible design, the roaming start indication message includes the identifier of the site.

[0034] In one possible design, the receiving module is further configured to: Receive a roaming start confirmation message from the target SFU, the roaming start confirmation message indicating that the target SFU has successfully completed roaming initiation for the site.

[0035] In one possible design, the receiving module is further configured to receive a roaming start failure message from the target SFU, the roaming start failure message indicating that the target SFU's roaming initiation for the site has failed; The processing module is also used to clear roaming-related information for the site.

[0036] In one possible design, the sending module is further configured to send a roaming start indication message to the source SFU, the roaming start indication message being used to instruct the initiation of roaming processing for the site.

[0037] In one possible design, the receiving module is further configured to receive a roaming start confirmation message from the source SFU, the roaming start confirmation message indicating that the source SFU has successfully completed roaming initiation for the site.

[0038] In one possible design, the receiving module is further configured to receive a roaming start failure message from the source SFU, the roaming start failure message indicating that the source SFU failed to initiate roaming for the site; The processing module is also used to clear roaming-related information for the site.

[0039] In one possible design, the sending module is further configured to send roaming exception handling messages to the source SFU and the target SFU, the roaming exception handling messages being used to instruct the clearing of roaming-related information for the site.

[0040] In one possible design, the receiving module is further configured to receive a roaming exception handling completion message from the source SFU; and / or, receive the roaming exception handling completion message from the target SFU.

[0041] In one possible design, the roaming decision information includes one or more of the following: signal strength with the station, load information, or channel condition information.

[0042] Fourthly, embodiments of this application provide a roaming device that implements the functions of the first aspect and optional methods described above. The device includes at least one module for implementing the methods provided by the eleventh aspect and optional methods described above. In one possible design, applied to a sub-optical network unit (SFU), it includes: The receiving module is used to receive a roaming start indication message from the main optical network unit (MFU), the roaming start indication message being used to instruct the initiation of roaming processing for the site; the SFU is either the source SFU currently accessed by the site or the target SFU determined by the MFU for roaming of the site. The processing module is used to initiate roaming processing for the site.

[0043] In one possible design, the roaming start indication message is carried in a Wi-Fi management control interface message.

[0044] In one possible design, the roaming initiation process includes initiating a roaming switching state machine.

[0045] In one possible design, the roaming start indication message includes the identifier of the site.

[0046] In one possible design, the device further includes: The SFU sends the roaming start confirmation message to the MFU, the roaming start confirmation message indicating that the SFU has successfully completed the roaming initiation for the site.

[0047] In one possible design, the device further includes: The SFU sends a roaming start failure message to the MFU, the roaming start failure message indicating that the SFU failed to initiate roaming for the site.

[0048] In one possible design, the device further includes: The SFU receives a roaming error handling message from the MFU, the roaming error handling message being used to instruct the clearing of roaming-related information for the site; The SFU clears roaming-related information for the site.

[0049] In one possible design, the device further includes: The SFU sends a roaming exception handling completion message to the MFU.

[0050] In one possible design, the device further includes: The SFU sends roaming decision information to the MFU.

[0051] In one possible design, the roaming decision information includes one or more of the following: signal strength with the station, load information, or channel condition information.

[0052] Fifthly, this application provides a roaming device, the roaming device including a processor, a memory and a communication interface; the processor is used to execute program instructions in the memory to implement the methods provided in the first aspect and the optional mode of the first aspect, and the communication interface is used to communicate with the SFU.

[0053] In a sixth aspect, this application provides a roaming device, the roaming device including a processor, a memory and a communication interface; the processor is used to execute program instructions in the memory to implement the methods provided in the second aspect and the optional methods of the second aspect, and the communication interface is used to communicate with an MFU.

[0054] In a seventh aspect, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the processor (in an MFU) to perform the method provided in the first aspect or any alternative method of the first aspect.

[0055] Eighthly, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the processor (in the SFU) to perform the method provided in the second aspect or any alternative method of the second aspect.

[0056] Ninthly, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the MFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the MFU to perform the method provided in the first aspect or any alternative method of the first aspect.

[0057] In a tenth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the SFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the SFU to perform the method provided in the second aspect or any alternative method of the second aspect described above.

[0058] Eleventhly, embodiments of this application provide a communication system including a source SFU, a target SFU, and an MFU. The MFU is used to perform the method described in the first aspect or any design of the first aspect. The source SFU or the target SFU is used to perform the method described in the second aspect or any design of the second aspect.

[0059] In a twelfth aspect, embodiments of this application provide a roaming method, including: The main optical network unit (MFU) sends a roaming preprocessing message to the target SFU, the roaming preprocessing message being used to instruct the target SFU to initiate roaming preparation for the site; The MFU receives a roaming preprocessing feedback message from the target SFU, the roaming preprocessing feedback message being used to indicate whether roaming preparation for the site was successful.

[0060] In one possible design, the roaming preprocessing message is carried in a Wi-Fi management control interface message.

[0061] In one possible design, the roaming preprocessing message includes the identifier of the site.

[0062] In one possible design, the roaming preprocessing message includes aggregation parameters used to establish an aggregation between the target SFU and the site.

[0063] In one possible design, the roaming preprocessing message includes aggregation parameters and association parameters. The aggregation parameters are used to establish an aggregation between the target SFU and the site, and the association parameters are used to establish an association between the target SFU and the site.

[0064] In one possible design, the association parameters include: the association request frame of the site and / or the key negotiated by the site with the source SFU for communication.

[0065] In one possible design, the aggregation parameters include: the size of the aggregation window and / or the aggregation strategy.

[0066] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has successfully completed roaming preparation for the site.

[0067] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has failed to roam for the site; The method further includes: The MFU removes roaming-related information for the site.

[0068] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has failed to roam for the site; The method further includes: The MFU sends a roaming anomaly handling message to the target SFU, the roaming anomaly handling message being used to instruct the clearing of roaming-related information for the site.

[0069] In one possible design, the method further includes: the MFU receiving the roaming exception handling completion message from the target SFU.

[0070] In one possible design, the method further includes: The MFU sends the roaming exception handling message to the source SFU, where the source SFU is the SFU currently connected to the site.

[0071] In one possible design, the method further includes: The MFU receives a roaming exception handling completion message from the source SFU.

[0072] In a thirteenth aspect, embodiments of this application provide a roaming method, including: The target sub-optical network unit (SFU) receives a roaming preprocessing message from the main optical network unit (MFU), which instructs the target SFU to initiate roaming preparation for the site. The target SFU sends a roaming preprocessing feedback message to the MFU, the roaming preprocessing feedback message being used to indicate whether the roaming preparation for the site was successful.

[0073] In one possible design, the roaming preprocessing message is carried in a Wi-Fi management control interface message.

[0074] In one possible design, the roaming preprocessing message includes the identifier of the site.

[0075] In one possible design, the roaming preprocessing message includes aggregation parameters used to establish an aggregation between the target SFU and the site.

[0076] In one possible design, the roaming preprocessing message includes aggregation parameters and association parameters. The aggregation parameters are used to establish an aggregation between the target SFU and the site, and the association parameters are used to establish an association between the target SFU and the site.

[0077] In one possible design, the association parameters include: the association request frame of the site and / or the key negotiated by the site with the source SFU for communication.

[0078] In one possible design, the aggregation parameters include: the size of the aggregation window and / or the aggregation strategy.

[0079] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has successfully completed roaming preparation for the site.

[0080] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has failed to roam for the site; The method further includes: Receive a roaming exception handling message from the MFU, the roaming exception handling message being used to instruct the clearing of roaming-related information for the site; Clear roaming-related information for the site.

[0081] In one possible design, the method further includes: Send a roaming exception handling completion message to the MFU.

[0082] In a fourteenth aspect, embodiments of this application provide a roaming method, including: When the source optical network unit (SFU) has initiated roaming processing for the site, a roaming anomaly handling message is received from the main optical network unit (MFU). The roaming anomaly handling message is used to instruct the clearing of roaming-related information for the site. The source SFU is the SFU currently accessed by the site. Clear roaming-related information for the site.

[0083] In one possible design, the method further includes: The source SFU sends a roaming exception handling completion message to the MFU.

[0084] In a fifteenth aspect, embodiments of this application provide a roaming device having the functionality to implement the twelfth aspect and its optional methods described above. The device includes at least one module for implementing the methods provided by the twelfth aspect and its optional methods. One possible design includes: applied to a main optical network unit (MFU), comprising: The sending module is used to send a roaming preprocessing message to the target SFU, the roaming preprocessing message being used to instruct the target SFU to initiate roaming preparation for the site; A receiving module is configured to receive a roaming preprocessing feedback message from the target SFU, the roaming preprocessing feedback message being used to indicate whether roaming preparation for the site was successful.

[0085] In one possible design, the roaming preprocessing message is carried in a Wi-Fi management control interface message.

[0086] In one possible design, the roaming preprocessing message includes the identifier of the site.

[0087] In one possible design, the roaming preprocessing message includes aggregation parameters used to establish an aggregation between the target SFU and the site.

[0088] In one possible design, the roaming preprocessing message includes aggregation parameters and association parameters. The aggregation parameters are used to establish an aggregation between the target SFU and the site, and the association parameters are used to establish an association between the target SFU and the site.

[0089] In one possible design, the association parameters include: the association request frame of the site and / or the key negotiated by the site with the source SFU for communication.

[0090] In one possible design, the aggregation parameters include: the size of the aggregation window and / or the aggregation strategy.

[0091] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has successfully completed roaming preparation for the site.

[0092] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has failed to roam for the site; The device further includes: A processing module is used to clear roaming-related information for the site.

[0093] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has failed to roam for the site; The sending module is used to send a roaming exception handling message to the target SFU, the roaming exception handling message being used to instruct the clearing of roaming-related information for the site.

[0094] In one possible design, the receiving module is further configured to receive the roaming exception handling completion message from the target SFU.

[0095] In one possible design, the sending module is further configured to send the roaming exception handling message to the source SFU, where the source SFU is the SFU currently connected to by the site.

[0096] In one possible design, the receiving module is further configured to: Receive a roaming exception handling completion message from the source SFU.

[0097] In a sixteenth aspect, embodiments of this application provide a roaming device having the functionality to implement the thirteenth aspect and its optional methods. The device includes at least one module for implementing the methods provided by the thirteenth aspect and its optional methods.

[0098] In one possible design, the application to the target sub-optical network unit (SFU) includes: The receiving module is used to receive a roaming preprocessing message from the main optical network unit (MFU), wherein the roaming preprocessing message is used to instruct the target SFU to initiate roaming preparation for the site; The sending module is used to send a roaming preprocessing feedback message to the MFU, the roaming preprocessing feedback message being used to indicate whether the roaming preparation for the site is successful.

[0099] In one possible design, the roaming preprocessing message is carried in a Wi-Fi management and control interface message.

[0100] In one possible design, the roaming preprocessing message includes the identifier of the site.

[0101] In one possible design, the roaming preprocessing message includes aggregation parameters used to establish an aggregation between the target SFU and the site.

[0102] In one possible design, the roaming preprocessing message includes aggregation parameters and association parameters. The aggregation parameters are used to establish an aggregation between the target SFU and the site, and the association parameters are used to establish an association between the target SFU and the site.

[0103] In one possible design, the association parameters include: the association request frame of the site and / or the key negotiated by the site with the source SFU for communication.

[0104] In one possible design, the aggregation parameters include: the size of the aggregation window and / or the aggregation strategy.

[0105] In one possible design, the roaming preprocessing feedback message indicates that the target SFU has successfully completed roaming preparation for the site.

[0106] In one possible design, the roaming preprocessing feedback message indicates that the target SFU's roaming preparation for the site has failed; The receiving module is further configured to receive a roaming exception handling message from the MFU, the roaming exception handling message being used to instruct the clearing of roaming-related information for the site; Also includes: A processing module is used to clear roaming-related information for the site.

[0107] In one possible design, the sending module is used to send a roaming exception handling completion message to the MFU.

[0108] In a seventeenth aspect, embodiments of this application provide a roaming device that has the functionality to implement the first aspect and the optional methods described above. The device includes at least one module for implementing the methods provided by the first aspect and the optional methods described above.

[0109] In one possible design, a receiving module is included, which is used to receive a roaming anomaly handling message from a main optical network unit (MFU) when the source sub-optical network unit (SFU) has initiated roaming processing for the site. The roaming anomaly handling message is used to instruct the clearing of roaming-related information for the site, and the source SFU is the SFU currently accessed by the site. A processing module is used to clear roaming-related information for the site.

[0110] In one possible design, the device further includes: The sending module is used to send a roaming exception handling completion message to the MFU.

[0111] In an eighteenth aspect, this application provides a roaming device, the roaming device including a processor, a memory and a communication interface; the processor is configured to execute program instructions in the memory to implement the methods provided in the twelfth aspect and the optional mode of the twelfth aspect, and the communication interface is configured to communicate with an SFU.

[0112] In a nineteenth aspect, this application provides a roaming device, the roaming device including a processor, a memory and a communication interface; the processor is configured to execute program instructions in the memory to implement the methods provided in the thirteenth aspect and the optional methods of the thirteenth aspect, or to implement the methods provided in the fourteenth aspect and the optional methods of the fourteenth aspect, and the communication interface is configured to communicate with an MFU.

[0113] In a twentieth aspect, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the processor (in an MFU) to perform the method provided in the twelfth aspect or any alternative method of the twelfth aspect.

[0114] In a twentieth aspect, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the processor (in a SFU) to perform the methods provided by the thirteenth aspect and the alternative methods of the thirteenth aspect, or to perform the methods provided by the fourteenth aspect and the alternative methods of the fourteenth aspect.

[0115] In a twentieth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the MFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the MFU to perform the method provided in the twelfth aspect or any alternative method of the twelfth aspect described above.

[0116] In a twentieth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the SFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the SFU to perform the methods provided in the thirteenth aspect and its optional embodiments, or to perform the methods provided in the fourteenth aspect and its optional embodiments.

[0117] In a twentieth aspect, embodiments of this application provide a communication system including a source SFU, a target SFU, and an MFU. The MFU is used to perform the method described in the twelfth aspect or any design of the twelfth aspect. The target SFU is used to perform the method described in the thirteenth aspect or any design of the thirteenth aspect. The source SFU is used to perform the method described in the fourteenth aspect or any design of the fourteenth aspect.

[0118] In a twentieth aspect, embodiments of this application provide a roaming method, including: During site roaming, the main optical network unit (MFU) sends a service shutdown instruction message to the source SFU. The service shutdown message is used to instruct the source SFU to shut down service interaction with the site. The MFU receives a service shutdown feedback message from the source SFU, which indicates whether the service interaction with the site has been successfully shut down.

[0119] In one possible design, the service shutdown message is carried in a Wi-Fi management control interface message.

[0120] In one possible design, the service shutdown instruction message includes the site's identifier.

[0121] In one possible design, the service shutdown instruction message is also used to instruct the source SFU to report context information about the service interaction with the site.

[0122] In one possible design, the service shutdown feedback message indicates that the source SFU has successfully shut down service interaction with the site.

[0123] In one possible design, the service shutdown feedback message includes context information about the service interaction between the source SFU and the site.

[0124] In one possible design, the context information includes one or more of the following: unicast packet sequence number (PN), sequence number (SN), context, or message sequence number.

[0125] In one possible design, the service shutdown feedback message indicates that the source SFU has failed to shut down the service interaction with the site; The method further includes: The MFU sends a first roaming exception handling message to the source SFU, the first roaming exception handling message being used to instruct the restoration of the configuration prior to the start of roaming for the site.

[0126] In one possible design, the method further includes: The MFU sends the second roaming exception handling message to the target SFU. The second roaming exception handling message is used to instruct the deletion of roaming-related information of the site. The target SFU is the target SFU determined by the site roaming handover.

[0127] In one possible design, the service shutdown feedback message indicates that the source SFU has failed to shut down the service interaction with the site; The method further includes: The MFU sends a third roaming anomaly handling message to the source SFU, the third roaming anomaly handling message being used to instruct the site to be removed from the network.

[0128] In one possible design, the method further includes: The MFU sends the third roaming exception handling message to the target SFU, where the target SFU is the target SFU determined by the site roaming handover.

[0129] In a twentieth aspect, embodiments of this application provide a roaming method, including: During site roaming, the source sub-optical network unit (SFU) receives a service shutdown instruction message from the main optical network unit (MFU). The service shutdown message is used to instruct the source SFU to shut down service interaction with the site. The source SFU sends a service shutdown feedback message to the MFU, which indicates whether the source SFU has successfully shut down service interaction with the site.

[0130] In one possible design, the service shutdown instruction message is carried in a Wi-Fi management control interface message.

[0131] In one possible design, the service shutdown instruction message includes the site's identifier.

[0132] In one possible design, the service shutdown instruction message is also used to instruct the source SFU to report context information about the service interaction with the site.

[0133] In one possible design, the service shutdown feedback message indicates that the source SFU has successfully shut down service interaction with the site.

[0134] In one possible design, the service shutdown feedback message includes context information about the service interaction between the source SFU and the site.

[0135] In one possible design, the context information includes one or more of the following: unicast packet sequence number (PN), sequence number (SN), context, or message sequence number.

[0136] In one possible design, the service shutdown feedback message indicates that the source SFU has failed to shut down the service interaction with the site; The method further includes: The source SFU receives a first roaming error handling message from the MFU, the first roaming error handling message being used to instruct the source SFU to restore the configuration before roaming was initiated for the site; The source SFU restores the configuration prior to the start of roaming for the site.

[0137] In one possible design, the service shutdown feedback message indicates that the source SFU has failed to shut down the service interaction with the site; The method further includes: The source SFU receives a third roaming anomaly handling message from the MFU, the third roaming anomaly handling message being used to instruct the source SFU to remove the site from the network; The source SFU removes the site from the network.

[0138] In one possible design, the method further includes: The source SFU sends a roaming exception handling completion message to the MFU.

[0139] In a twenty-seventh aspect, embodiments of this application provide a roaming method, including: When the target sub-optical network unit (SFU) has initiated roaming processing for the site, a second roaming anomaly handling message is received from the main optical network unit (MFU). The second roaming anomaly handling message is used to instruct the clearing of roaming-related information for the site. The source SFU is the SFU currently accessed by the site. Remove roaming-related information for the site or remove the site from the network.

[0140] In one possible design, the method further includes: The target SFU sends a roaming exception handling completion message to the MFU.

[0141] In a twentieth aspect, embodiments of this application provide a roaming device having the functionality to implement the twenty-fourth aspect and the optional methods of the twenty-fourth aspect. The device includes at least one module, which is used to implement the methods provided by the twenty-fourth aspect and the optional methods of the twenty-fourth aspect. One possible design includes: a sending module, used to send a service shutdown indication message to a source SFU during roaming at a site, the service shutdown message being used to instruct the source SFU to shut down service interaction with the site; The receiving module is configured to receive a service shutdown feedback message from the source SFU, the service shutdown feedback message being used to indicate whether the service interaction with the site has been successfully shut down.

[0142] In one possible design, the service shutdown message is carried in a Wi-Fi management control interface message.

[0143] In one possible design, the service shutdown instruction message includes the site's identifier.

[0144] In one possible design, the service shutdown instruction message is also used to instruct the source SFU to report context information about the service interaction with the site.

[0145] In one possible design, the service shutdown feedback message indicates that the source SFU has successfully shut down service interaction with the site.

[0146] In one possible design, the service shutdown feedback message includes context information about the service interaction between the source SFU and the site.

[0147] In one possible design, the context information includes one or more of the following: unicast packet sequence number (PN), sequence number (SN), context, or message sequence number.

[0148] In one possible design, the service shutdown feedback message indicates that the source SFU has failed to shut down the service interaction with the site; The sending module is further configured to send a first roaming exception handling message to the source SFU, the first roaming exception handling message being used to instruct the restoration of the configuration prior to the start of roaming for the site.

[0149] In one possible design, the sending module is further configured to send the second roaming exception handling message to the target SFU, the second roaming exception handling message being used to instruct the deletion of roaming-related information of the site, the target SFU being the target SFU determined by the site roaming handover.

[0150] In one possible design, the service shutdown feedback message indicates that the source SFU has failed to shut down the service interaction with the site; The sending module is further configured to send a third roaming exception handling message to the source SFU, the third roaming exception handling message being used to instruct the site to be removed from the network.

[0151] In one possible design, the sending module is further configured to send the third roaming exception handling message to the target SFU, wherein the target SFU is the target SFU determined by the site roaming handover.

[0152] In a twentieth aspect, embodiments of this application provide a roaming device having the functionality to implement the twenty-fifth aspect and the optional methods of the twenty-fifth aspect. The device includes at least one module for implementing the methods provided by the twenty-fifth aspect and the optional methods of the twenty-fifth aspect. In one possible design, applied to a source sub-optical network unit (SFU), it includes: The receiving module is used to receive a service shutdown indication message from the main optical network unit (MFU) during the roaming process of the site. The service shutdown message is used to instruct the source SFU to shut down service interaction with the site. The sending module is used to send a service shutdown feedback message to the MFU, the service shutdown feedback message being used to indicate whether the source SFU has successfully shut down service interaction with the site.

[0153] In one possible design, the service shutdown instruction message is carried in a Wi-Fi management control interface message.

[0154] In one possible design, the service shutdown instruction message includes the site's identifier.

[0155] In one possible design, the service shutdown instruction message is also used to instruct the source SFU to report context information about the service interaction with the site.

[0156] In one possible design, the service shutdown feedback message indicates that the source SFU has successfully shut down service interaction with the site.

[0157] In one possible design, the service shutdown feedback message includes context information about the service interaction between the source SFU and the site.

[0158] In one possible design, the context information includes one or more of the following: unicast packet sequence number (PN), sequence number (SN), context, or message sequence number.

[0159] In one possible design, the service shutdown feedback message indicates that the source SFU has failed to shut down the service interaction with the site; The receiving module is further configured to receive a first roaming exception handling message from the MFU, the first roaming exception handling message being used to instruct the source SFU to restore the configuration before the site roaming was initiated; Also includes: The processing module is used to restore the configuration prior to the start of roaming for the site.

[0160] In one possible design, the service shutdown feedback message indicates that the source SFU has failed to shut down the service interaction with the site; The receiving module is also configured to receive a third roaming exception handling message from the MFU, the third roaming exception handling message being used to instruct the source SFU to remove the site from the network; Also includes: A processing module for removing the site from the network.

[0161] In one possible design, the sending module is also used to send a roaming exception handling completion message to the MFU.

[0162] In a thirtieth aspect, embodiments of this application provide a roaming device having the functionality to implement the twenty-sixth aspect and the optional methods thereof. The device includes at least one module for implementing the methods provided by the twenty-sixth aspect and the optional methods thereof.

[0163] In one possible design, the application to the target sub-optical network unit (SFU) includes: The receiving module is configured to receive a second roaming anomaly handling message from the main optical network unit (MFU) when the target sub-optical network unit (SFU) has initiated roaming processing for the site. The second roaming anomaly handling message is used to instruct the clearing of roaming-related information for the site, and the source SFU is the SFU currently accessed by the site. A processing module is used to clear roaming-related information for the site.

[0164] In one possible design, the device further includes: The sending module is used to send a roaming exception handling completion message to the MFU.

[0165] In a thirty-first aspect, this application provides a roaming device, the roaming device including a processor, a memory and a communication interface; the processor is configured to execute program instructions in the memory to implement the methods provided in the twenty-fourth aspect and the optional manner of the twenty-fourth aspect, and the communication interface is configured to communicate with an SFU.

[0166] In a thirty-second aspect, this application provides a roaming device, the roaming device including a processor, a memory and a communication interface; the processor is configured to execute program instructions in the memory to implement the methods provided by the twenty-fifth aspect and the optional methods of the twenty-fifth aspect, or to implement the methods provided by the fourteenth aspect and the optional methods of the fourteenth aspect, and the communication interface is configured to communicate with an MFU.

[0167] In a thirty-third aspect, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the processor (in an MFU) to perform the method provided in the twenty-fourth aspect or any alternative method of the twenty-fourth aspect.

[0168] In a thirty-fourth aspect, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the processor (in a SFU) to perform the method provided by the twenty-fifth aspect and the optional method of the twenty-fifth aspect, or to perform the method provided by the twenty-sixth aspect and the optional method of the twenty-sixth aspect.

[0169] In a thirty-fifth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the MFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the MFU to perform the method provided in either the twenty-fourth aspect or any alternative method of the twenty-fourth aspect.

[0170] In a thirty-sixth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the SFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the SFU to perform the methods provided by the twenty-fifth aspect and the optional methods of the twenty-fifth aspect, or to perform the methods provided by the twenty-sixth aspect and the optional methods of the twenty-sixth aspect.

[0171] In a thirty-seventh aspect, embodiments of this application provide a communication system including a source SFU, a target SFU, and an MFU. The MFU is used to perform the method described in or according to any design of the twenty-fourth aspect. The source SFU is used to perform the method described in or according to any design of the twenty-fifth aspect. The target SFU is used to perform the method described in or according to any design of the twenty-sixth aspect.

[0172] In a thirty-eighth aspect, embodiments of this application provide a roaming method, including: During site roaming, the main optical network unit (MFU) sends a service activation instruction message to the target SFU. The service activation instruction message is used to instruct the target SFU to activate service interaction with the site. The MFU receives a service activation feedback message from the target SFU, which indicates whether service interaction with the site has been successfully activated.

[0173] In one possible design, the service activation indication message is carried in a Wi-Fi management control interface message.

[0174] In one possible design, the service activation instruction message includes the site's identifier.

[0175] In one possible design, the service activation indication message includes context information about the service interaction between the source SFU and the site.

[0176] In one possible design, the context information includes one or more of the following: unicast packet sequence number (PN), sequence number (SN), context, or message sequence number.

[0177] In one possible design, the service activation feedback message indicates that the target SFU has successfully initiated service interaction with the site.

[0178] In one possible design, the service activation feedback message indicates that the service interaction between the target SFU and the site has failed. The method further includes: The MFU sends a first roaming exception handling message to the target SFU, the first roaming exception handling message being used to instruct the restoration of the configuration prior to the start of roaming for the site.

[0179] In one possible design, the method further includes: The MFU receives the roaming exception handling completion message sent by the target SFU.

[0180] In one possible design, the method further includes: The MFU sends the first roaming exception handling message to the source SFU.

[0181] In one possible design, the method further includes: The MFU receives a roaming exception handling completion message sent by the source SFU.

[0182] In one possible design, the method further includes: The MFU clears the roaming-related information of the site.

[0183] In one possible design, the service activation feedback message indicates that the service interaction between the target SFU and the site has failed. The method further includes: The MFU sends a third roaming anomaly handling message to the target SFU, the third roaming anomaly handling message being used to instruct the site to be removed from the network.

[0184] In one possible design, the method further includes: The MFU sends the third roaming exception handling message to the source SFU, where the source SFU is the target SFU determined by the site roaming handover.

[0185] In a thirty-ninth aspect, embodiments of this application provide a roaming method, including: During the roaming process at the site, the target sub-optical network unit (SFU) receives a service activation instruction message from the main optical network unit (MFU). The service activation instruction message is used to instruct the target SFU to activate service interaction with the site. The target SFU sends a service activation feedback message to the MFU, which indicates whether the source SFU has successfully activated service interaction with the site.

[0186] In one possible design, the service activation indication message is carried in a Wi-Fi management control interface message.

[0187] In one possible design, the service activation instruction message includes the site's identifier.

[0188] In one possible design, the service activation indication message includes context information about the service interaction between the source SFU and the site.

[0189] In one possible design, the context information includes one or more of the following: unicast packet sequence number (PN), sequence number (SN), context, or message sequence number.

[0190] In one possible design, the service activation feedback message indicates that the target SFU has successfully initiated service interaction with the site.

[0191] In one possible design, the method further includes: The target SFU sends downlink service messages to the site.

[0192] In one possible design, the service shutdown feedback message indicates that the target SFU failed to enable service interaction with the site. The method further includes: The target SFU receives a first roaming exception handling message from the MFU, the first roaming exception handling message being used to indicate the restoration of the configuration before the site roaming was initiated; The target SFU restores the configuration prior to the start of roaming for the site.

[0193] In one possible design, the method further includes: The target SFU sends a roaming exception handling completion message to the MFU.

[0194] In one possible design, the service activation feedback message indicates that the service interaction between the target SFU and the site has failed. The method further includes: The target SFU receives a third roaming anomaly handling message from the MFU, the third roaming anomaly handling message being used to instruct the target SFU to remove the site from the network; The target SFU removes the site from the network.

[0195] In a fortieth aspect, embodiments of this application provide a roaming method, including: When the source optical network unit (SFU) has initiated roaming processing for a site, a first roaming anomaly handling message is received from the main optical network unit (MFU). The first roaming anomaly handling message is used to indicate the restoration of the configuration before the roaming for the site was initiated. The target SFU is the target SFU for the site roaming handover. Restore the configuration for the site prior to roaming initiation and remove the site from the network.

[0196] In one possible design, the method further includes: The source SFU sends a roaming exception handling completion message to the MFU.

[0197] In a forty-one aspect, embodiments of this application provide a roaming device having the functionality to implement the thirty-seventh aspect and the optional methods of the thirty-seventh aspect. The device includes at least one module for implementing the methods provided by the thirty-seventh aspect and the optional methods of the thirty-seventh aspect. In one possible design, applied to a main optical network unit (MFU), it includes: The sending module is used to send a service activation instruction message to the target SFU during the roaming process of the site. The service activation instruction message is used to instruct the target SFU to activate service interaction with the site. The receiving module is used to receive a service activation feedback message from the target SFU, the service activation feedback message being used to indicate whether service interaction with the site has been successfully activated.

[0198] In one possible design, the service activation indication message is carried in a Wi-Fi management control interface message.

[0199] In one possible design, the service activation instruction message includes the site's identifier.

[0200] In one possible design, the service activation indication message includes context information about the service interaction between the source SFU and the site.

[0201] In one possible design, the context information includes one or more of the following: unicast packet sequence number (PN), sequence number (SN), context, or message sequence number.

[0202] In one possible design, the service activation feedback message indicates that the target SFU has successfully initiated service interaction with the site.

[0203] In one possible design, the service activation feedback message indicates that the service interaction between the target SFU and the site has failed. The sending module is further configured to send a first roaming exception handling message to the target SFU, the first roaming exception handling message being used to instruct the restoration of the configuration prior to the start of roaming for the site.

[0204] In one possible design, the receiving module is also configured to receive a roaming exception handling completion message sent by the target SFU.

[0205] In one possible design, the sending module is further configured to send the first roaming exception handling message to the source SFU.

[0206] In one possible design, the receiving module is also used to receive a roaming exception handling completion message sent by the source SFU.

[0207] In one possible design, the device further includes: The processing module is used to clear roaming-related information of the site.

[0208] In a forty-second aspect, embodiments of this application provide a roaming device having the functionality to implement the thirty-eighth aspect and its optional methods. The device includes at least one module for implementing the methods provided by the thirty-eighth aspect and its optional methods. In one possible design, applied to a target sub-optical network unit (SFU), it includes: The receiving module is used to receive a service activation indication message from the main optical network unit (MFU) during the roaming process of the site. The service activation indication message is used to instruct the target SFU to activate service interaction with the site. The sending module is used to send a service activation feedback message to the MFU, the service activation feedback message being used to indicate whether the source SFU has successfully activated service interaction with the site.

[0209] In one possible design, the service activation indication message is carried in a Wi-Fi management control interface message.

[0210] In one possible design, the service activation instruction message includes the site's identifier.

[0211] In one possible design, the service activation indication message includes context information about the service interaction between the source SFU and the site.

[0212] In one possible design, the context information includes one or more of the following: unicast packet sequence number (PN), sequence number (SN), context, or message sequence number.

[0213] In one possible design, the service activation feedback message indicates that the target SFU has successfully initiated service interaction with the site.

[0214] In one possible design, the sending module is also used to send downlink service messages to the station.

[0215] In one possible design, the service shutdown feedback message indicates that the target SFU failed to enable service interaction with the site. The receiving module is further configured to receive a first roaming exception handling message from the MFU, the first roaming exception handling message being used to indicate the restoration of the configuration before the site roaming was initiated; Also includes: The processing module is used to restore the configuration prior to the start of roaming for the site.

[0216] In one possible design, the sending module is also used to send a roaming exception handling completion message to the MFU.

[0217] In a forty-third aspect, embodiments of this application provide a roaming device that has the functionality to implement the thirty-ninth aspect and the optional methods thereof. The device includes at least one module for implementing the methods provided by the thirty-ninth aspect and the optional methods thereof.

[0218] One possible design applied to the source-sub-optical network unit (SFU) includes: The receiving module is configured to receive a first roaming error handling message from the main optical network unit (MFU) when the source sub-optical network unit (SFU) has initiated roaming processing for the site. The first roaming error handling message is used to indicate the restoration of the configuration before the roaming for the site was initiated. The processing module restores the configuration for the site before roaming was initiated.

[0219] In one possible design, the device further includes: The sending module is also used to send a roaming exception handling completion message to the MFU.

[0220] In a forty-fourth aspect, this application provides a roaming device, the roaming device including a processor, a memory, and a communication interface; the processor is configured to execute program instructions in the memory to implement the methods provided in the thirty-seventh aspect and the optional manner of the thirty-seventh aspect, and the communication interface is configured to communicate with an SFU.

[0221] In a forty-fifth aspect, this application provides a roaming device, the roaming device including a processor, a memory, and a communication interface; the processor is configured to execute program instructions in the memory to implement the methods provided in the thirty-eighth aspect and the optional mode of the thirty-eighth aspect, or to implement the methods provided in the thirty-ninth aspect and the optional mode of the thirty-ninth aspect, and the communication interface is configured to communicate with an MFU.

[0222] In a forty-sixth aspect, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the processor (in an MFU) to perform the method provided in either the thirty-seventh aspect or any alternative method of the thirty-seventh aspect.

[0223] In a forty-seventh aspect, this application provides a computer-readable storage medium storing at least one program instruction that is read by a processor to cause the processor (in a SFU) to perform the method provided by the thirty-eighth aspect and the optional method of the thirty-eighth aspect, or to perform the method provided by the thirty-ninth aspect and the optional method of the thirty-ninth aspect.

[0224] In a forty-eighth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the MFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the MFU to perform the method provided in either the thirty-seventh aspect or any alternative method of the thirty-seventh aspect.

[0225] In a forty-ninth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the SFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the SFU to perform the methods provided by the thirty-eighth aspect and the optional methods of the thirty-eighth aspect, or to perform the methods provided by the thirty-ninth aspect and the optional methods of the thirty-ninth aspect.

[0226] In a fiftieth aspect, embodiments of this application provide a communication system including a source SFU, a target SFU, and an MFU. The MFU is used to perform the method described in any of the designs of the thirty-seventh or thirty-seventh aspects. The source SFU is used to perform the method described in any of the designs of the thirty-eighth or thirty-eighth aspects. The target SFU is used to perform the method described in any of the designs of the thirty-ninth or thirty-ninth aspects.

[0227] In one aspect, embodiments of this application provide a communication system including a source SFU, a target SFU, and an MFU. The MFU is used to perform the method described in aspect 37 or any design of aspect 37. The source SFU is used to perform the method described in aspect 38 or any design of aspect 38. The target SFU is used to perform the method described in aspect 39 or any design of aspect 39.

[0228] In some embodiments, the MFU, source SFU, and target SFU have the same Basic Service Set Identifier (BSSID). The MFU, source SFU, and target SFU also have the same Service Set Identifier (SSID).

[0229] Based on the implementations provided in the above aspects, this application can be further combined to provide more implementations. Attached Figure Description

[0230] Figures 1A-1C A schematic diagram of an FTTR system architecture provided in this application embodiment; Figure 2 This is a schematic flowchart of the roaming method provided in an embodiment of this application; Figure 3A This is a flowchart illustrating a roaming method under abnormal state 1 provided in an embodiment of this application. Figure 3B This is a flowchart illustrating a roaming method under abnormal state 1 provided in an embodiment of this application. Figure 4A This is a flowchart illustrating a roaming method under abnormal state 1 provided in an embodiment of this application. Figure 4B This is a flowchart illustrating a roaming method under abnormal state 1 provided in an embodiment of this application. Figure 5 This is a flowchart illustrating a roaming method under abnormal state 2 provided in an embodiment of this application. Figure 6 This is a flowchart illustrating a roaming method under abnormal state 2 provided in an embodiment of this application. Figure 7 This is a flowchart illustrating a roaming method under abnormal state 3 provided in an embodiment of this application. Figure 8This is a flowchart illustrating a roaming method under abnormal state 3 provided in an embodiment of this application. Figure 9 This is a flowchart illustrating a roaming method under abnormal state 4 provided in an embodiment of this application. Figure 10 This is a flowchart illustrating a roaming method under abnormal state 4 provided in an embodiment of this application. Figure 11 This is a schematic diagram of the roaming device structure provided in an embodiment of this application; Figure 12 This is a schematic diagram of the device structure provided in an embodiment of this application. Detailed Implementation

[0231] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0232] In the description of this application, unless otherwise stated, "multiple" refers to two or more. Additionally, " / " indicates that the related objects are in an "or" relationship; for example, A / B can represent A or B. "And / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, to clearly describe the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and are not necessarily different. It should also be noted that, unless specifically stated, the specific description of some technical features in one embodiment can also be used to explain the corresponding technical features mentioned in other embodiments.

[0233] The importance of seamless Wi-Fi roaming lies in its ability to provide users with a continuous and uninterrupted wireless network connection, ensuring stable and reliable network connectivity in homes, offices, and public places. From a user experience perspective, seamless Wi-Fi roaming avoids network interruptions. Imagine how frustrating it would be to suddenly lose your internet connection while enjoying a smooth online video or conducting an important online meeting, forcing you to move to another room or area. Seamless Wi-Fi roaming technology intelligently senses user movement and signal strength changes, automatically switching to the optimal access point to avoid such interruptions and allow users to enjoy a consistently stable network connection.

[0234] This application provides a roaming method for seamless roaming of sites, enhancing user experience. A site can be any site using a wireless network, such as a mobile phone, tablet, computer, or smart home appliance—any terminal requiring network access. A site can also be referred to as a terminal, user equipment, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc., and is not specifically limited in this application. The terminal device 111 can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and user equipment in 5G or future networks, etc.

[0235] This application's embodiments can be applied to Fiber To The Room (FTTR) system scenarios. An FTTR system includes a master fiber unit (MFU) and a sub-fiber unit (SFU). The MFU and SFU are connected via optical fiber. Access points include both the MFU and SFU, which can be optical network terminals (ONTs) or optical network units (ONUs). The Chinese term for MFU can also be FTTR master device, and the English term for SFU can also be FTTR slave device or FTTR sub-device, and the English term for SFU can also be sub-FTTR unit. The MFU can also be called a master gateway, and the SFU can also be called a sub-gateway.

[0236] When an FTTR system is deployed, the MFU and SFU are configured to belong to the same subnet. Configuration can be done manually or automatically. Alternatively, the MFU and SFU are configured with the same Basic Services Set Identifier (BSSID). BSSID is an important term in Wireless Local Area Networks (WLANs) used to identify a specific Wi-Fi network. For example, as shown in Figure 1, an FTTR system is deployed in the same subnet, including MFU, SFU1, SFU2, and SFU3. The MFU is connected to SFU1, SFU2, and SFU3 via fiber optic cables. In some possible implementation scenarios, the MFU can be connected to SFU1, SFU2, and SFU3 via optical splitters, see [link to relevant documentation]. Figure 1A As shown.

[0237] In one possible application scenario, the roaming handover process may include the following steps, see [link to relevant documentation]. Figure 1B and Figure 1C As shown: initialization process, virtual initialization, information synchronization, and link switching. Figure 1B In this example, we take the initial online status of the STA at SFU1, followed by a link switchover to SFU2. See [link to example]. Figure 1B As shown, the WMCI-based collaborative roaming solution mainly includes four aspects of processing: roaming configuration information synchronization, network information synchronization, terminal online processing, and terminal roaming processing.

[0238] During the initialization process: The STA goes live by executing the scanning process, authentication process, association process, and four-way handshake process. During the initialization process, the SMF and SFU receive the STA's initialization information, and the corresponding SFU responds to the STA's request messages.

[0239] In the virtual initialization process: After the STA comes online, the MFU sends some key information about the STA to each SFU, so that each SFU can create a virtual user for the STA, allowing the STA to virtually come online on other SFUs. This means that the MFU saves information related to communication with the STA but does not currently provide services to the STA. Key information may include one or more of the following: authentication request frame, AID, association request frame, or key.

[0240] In the information synchronization process: the source SFU synchronizes the context information of the STA to the target SFU to achieve fast roaming decision-making and seamless roaming.

[0241] Link switching: After the roaming decision and context information synchronization are completed, the STA switches from the source SFU to the target SFU.

[0242] The roaming process provided in this application embodiment is a switch from a source access point to a target access point. In one implementation scenario, the source access point can be an MFU (Multi-Functional Unit), and the target access point is a target SFU (Single-Functional Unit). In another implementation scenario, the source access point can be a source SFU, and the target access point is a target SFU. The target access point can also be called the destination access point, and the target SFU can also be called the destination SFU. The following description uses roaming from a source SFU to a target SFU as an example; other implementation scenarios can be referred to accordingly, and will not be described in detail.

[0243] The following is an exemplary description of the format of the roaming handover indication and reporting message involved in the embodiments of this application. See Table 1-1.

[0244] Each roaming handover indication and reporting message has different parameters, which can be indicated by a mask. The roaming handover messages include sequence numbers 2-5 and 7-8; the roaming handover completion status reporting messages include sequence numbers 2-8; the roaming handover exception handling messages include sequence numbers 2-5 and 7-8; and the roaming handover exception handling status reporting messages include sequence numbers 2-6. Table 1-1 is only an example; the message types or message states corresponding to the different values ​​can be configured according to requirements, and this application embodiment does not limit this.

[0245] Table 1-1

[0246] The following describes the roaming method flow in the embodiments of this application, such as... Figure 2 As shown.

[0247] S201, the source SFU detects a roaming trigger event of the STA and sends the roaming trigger event of the STA to the MFU.

[0248] Roaming trigger events can include the STA's signal strength falling below the roaming threshold.

[0249] The source SFU periodically determines the signal strength of the STA. For example, the source SFU periodically sends beacon frames to the STA. Upon receiving the beacon frame, the STA sends a reply signal to the source SFU. The source SFU determines the received signal strength indication (RSSI) of this reply signal, which is the signal strength. The source SFU then compares this signal strength with a roaming threshold. If the signal strength is determined to be below the roaming threshold, the source SFU reports this trigger event to the MFU. As the STA moves further away from the source SFU, the signal gradually weakens until it falls below the roaming threshold. If the signal strength is determined to be at least as high as the roaming threshold, the source SFU continues to monitor the STA's signal strength.

[0250] In one possible implementation, the roaming threshold can be manually configured or intelligently configured. The roaming threshold can also be configured by the MFU to the source SFU.

[0251] Optionally, the roaming threshold can be different in different deployment scenarios. For example, a first roaming threshold can be configured in scenarios with dense access point coverage, and a second roaming threshold can be configured in scenarios with sparse access point coverage, with the first roaming threshold being larger than the second. In dense coverage scenarios, because the distance between access points is small, setting the roaming threshold too low would result in roaming occurring even after a short distance, leading to frequent roaming. To conserve roaming management resources, the roaming threshold is configured higher. Conversely, in sparse coverage scenarios, because the distance between access points is large, a greater distance is required to enter the coverage area of ​​an access point with stronger signal strength. Therefore, the roaming threshold is configured lower.

[0252] In one possible implementation, the source SFU can carry the triggering event in a Wi-Fi Management and Control Interface (WMCI) message.

[0253] WMCI is the interface between the MFU and SFU for implementing WLAN control and other functions. The WMCI management channel is a low-latency channel in the FTTR network that enables WLAN control and other functions between the MFU and SFU. It carries WMCI messages via a separate FEMport-ID. The WMCI management channel is also called the Wi-Fi Management and Control Channel (WMCC). WMCI messages are encapsulated in FEM frames and used to manage and control the WLAN functions of the SFU. The FTTR transceiver can identify the destination of the WMCI message through the FEM port ID in the FEM frame.

[0254] See Table 1-2 for the WMCI message encapsulation format.

[0255] Table 1-2

[0256] The message type is an 8-bit field that indicates the type of message and defines the semantics of the message content. When the MFU receives an upstream message with a message type ID indicating that it is unsupported, the MFU ignores the message. When the SFU receives a message with a reserved or unsupported message type ID, it ignores the message.

[0257] The sequence number is an 8-bit field containing a sequence number counter to ensure the robustness of the WMCI message channel. In the downlink direction, the sequence number field is populated with the corresponding MFU sequence number counter value. The MFU maintains a separate sequence number counter for each SFU unicast and broadcast WMCI message stream. Each sequence number counter rolls from 255 to 1. A value of 0 is not used in the downlink direction. In the uplink direction, when an uplink WMCI message is a response to a downlink message, the value of the sequence number field is equal to the value of the sequence number field in the downlink message. If the WMCI message is initiated by the SFU, sequence number = 0 is used.

[0258] Message length and priority are 2-byte fields, representing the number of bytes in the message content and the message processing requirements. X (the most significant bit of the third byte): Indicates the priority for processing this message. When X=1, the message has high priority; X=0 indicates low priority. LL LLLL LLLL: This field represents the length of the message content. The value range is 0 to 1023. O: Indicates the operation type of the current message. In the downlink direction, when O=1, it indicates that the operation type is a parameter request, requesting the SFU to send the output indicated by the Message type ID field; when O=0, it indicates that the message is a parameter configuration message, with the Message type ID field indicating the parameter type configured in the message. In the uplink direction, when O=1, it indicates that the operation type is a scheduling request, requesting the MFU to send the scheduling configuration indicated by the Message type ID field; when O=0, it indicates that the message is a parameter reporting message, with the Message type ID field indicating the parameter type configured in the message.

[0259] The format of the message content field is related to the specific message. The message content includes two parts: the message mask and the parameter content.

[0260] The message mask consists of a 16-bit mask, as shown in Table 1-3.

[0261] Table 1-3

[0262] Each message type can carry 16 parameters. See the message definition for a detailed explanation of the parameter sequence.

[0263] The message content should be filled in according to the order indicated by the parameter mask. For downlink request messages, the parameter mask represents the parameters that the MFU wants to obtain. For uplink messages, the parameter mask represents the parameters reported and replied to.

[0264] Message verification can employ Cyclic Redundancy Check (CRC). The message verification field, also known as the CRC field, is used to verify whether the message has been corrupted during transmission; its value is generated by the CRC algorithm.

[0265] The messages mentioned in Table 1-1 can be carried within WMCI messages, such as in the content fields of the WMCI message. In some embodiments, the WMCI message includes an access point identifier (such as AP ID or AP index). In one approach, the access point identifier (such as AP ID or AP index) is carried in the message header of the WMCI message. In another approach, the access point identifier (such as AP ID or AP index) is carried in the content fields of the WMCI message, such as in the messages mentioned in Table 1-1, i.e., an AP ID field can be added to Table 1-1.

[0266] For example, the source SFU can carry the triggering event in the message content field of the WMCI message.

[0267] S202, the MFU sends a roaming decision information collection request to multiple SFUs within the network. The roaming decision information collection request instructs the SFUs to collect roaming decision information and report it to the MFU.

[0268] In one possible example, multiple SFUs within a network can include all SFUs within the network. In another possible embodiment, SFUs in the network can be configured into groups; for example, several adjacent SFUs may belong to the same group. Of course, other grouping methods are also applicable to this application, and this application does not limit them. Multiple SFUs within a network can be SFUs within a certain group; for example, the group containing the multiple SFUs may include the source SFU.

[0269] The roaming decision information collection request can also be referred to as roaming decision information collection. This application does not limit the naming method.

[0270] For example, the MFU can carry roaming decision information reporting requests in a WMCI message, such as in the message content field of the WMCI message.

[0271] Furthermore, multiple SFUs separately perform roaming decision information collection. Roaming decision information may include one or more of the following: RSSI, load information, or channel condition information.

[0272] It can be understood that load information represents the busyness of the Wi-Fi channel of the SFU. Higher load indicates a busier Wi-Fi channel and lower communication performance; lower load indicates a less busy Wi-Fi channel and higher communication performance. For example, load information can be the number of sites connected to the SFU. For example, load information can include the number of sites connected to the SFU and the site type. Different site types correspond to different load weights. The correspondence between site type and load weight can be preset. For example, the load weight for the mobile phone site type is 1; the load weight for the VR device site type is 2; and the load weight for the smart refrigerator site type is 0.2. Therefore, the MFU can determine the load of the SFU based on the SFU's load information. For example, when the load information is the number of sites, more sites indicate a larger SFU load. For example, when the load information includes the number of sites and the site type, the number of sites of the same type can be multiplied by the load weight corresponding to that type to obtain the weighted load. Then, the weighted loads of each site type are added together, and the sum can be used to represent the SFU load.

[0273] Channel condition information may include signal to interference plus noise ratio (SINR) and / or packet loss rate.

[0274] As an example, the roaming decision information collection message may include fields numbered 2-5 and 7-8 in Table 1-1, as shown in Table 1-4 for example.

[0275] Table 1-4

[0276] The Payload field can carry the parameters that the SFU needs to report. In some possible implementation scenarios, default or protocol-defined parameters can be used for reporting. In this case, it is not necessary to indicate the parameters that the SFU needs to report. In this case, a set sequence can be added to Payload and PayloadLen, such as all zeros, or these two fields can be omitted.

[0277] S203, multiple SFUs send roaming decision information to the MFU respectively.

[0278] For example, each SFU sends a roaming decision information collection and reporting message to the MFU. For instance, the roaming decision information collection and reporting message sent by the target SFU carries the roaming decision information collected by the target SFU. The roaming decision information collection and reporting message can be called a roaming decision information reporting message, or other naming conventions can be used; this application embodiment does not limit this.

[0279] S204, the MFU selects the target SFU to be switched over (or connected to) based on the roaming decision information. The source SFU can be called the source SFU, and the target SFU can be called the target SFU or destination SFU.

[0280] In one possible example, the roaming decision information sent by the SFU to the MFU includes the RSSI of the Wi-Fi signal received by the SFU from the STA. Specifically, the SFU can measure the RSSI of the Wi-Fi signal it receives from the STA. It can be understood that RSSI reflects the communication performance of the channel or link; the higher the RSSI, the higher the communication performance. The MFU can select the SFU with the highest RSSI among multiple SFUs as the target SFU.

[0281] In another possible example, the roaming decision information sent by the SFU to the MFU includes the load information of the SFU. The MFU can select the SFU with the lowest load among multiple SFUs as the target SFU.

[0282] In another possible example, the roaming decision information sent by the SFU to the MFU includes the SFU's channel condition information. Specifically, the SFU can measure the channel conditions for its communication with the STA to obtain channel condition information. The MFU can select the SFU with the best channel conditions among multiple SFUs as the target SFU. For example, it can select the SFU with the highest SINR as the target SFU, or the SFU with the lowest packet loss rate as the target SFU, or the SFU with the highest SINR among SFUs with packet loss rates below a certain threshold as the second SFU, or SINR and packet loss rate can be weighted differently, and the SFU with the largest weighted value can be selected as the target SFU.

[0283] In another possible example, the roaming decision information sent by the SFU to the MFU includes the SFU's load information and RSSI. For instance, the SFU can select the SFU with an RSSI greater than a certain threshold and the lowest current load as the target SFU. Alternatively, the MFU can weight the RSSIs of multiple SFUs with their load values ​​and determine the SFU with the highest weighted value as the target SFU.

[0284] In another possible example, the roaming decision information sent by the SFU to the MFU includes RSSI, load information, and channel condition information. The MFU can select the target SFU by using a weighted calculation method. For example, RSSI, load, SINR (and / or packet loss rate) each correspond to different weights, and the target SFU is determined by calculating the weights.

[0285] It should be understood that there are other combinations of the above roaming decision information. Therefore, the MFU can select the optimal SFU as the target SFU based on different combinations, which will not be listed here.

[0286] In some possible implementations, after selecting the target SFU, the MFU initiates the roaming process. Initiating the roaming process can involve starting a state machine. The state machine describes the states of the roaming handover. For example, the roaming handover states include: the roaming processing state and the roaming reporting state.

[0287] As an example, the roaming decision information collection and reporting message may include fields numbered 2-8 in Table 1-1, as shown in Table 1-5 for example.

[0288] Table 1-5

[0289] Table 1-6

[0290] The Payload field can carry the parameters that the SFU needs to report. In some possible implementation scenarios, default or protocol-defined parameters can be used for reporting. In this case, it is not necessary to indicate the parameters that the SFU needs to report. In this case, a set sequence can be added to Payload and PayloadLen, such as all zeros, or these two fields can be omitted.

[0291] If the SFU successfully completes the roaming decision information collection, it can reply with a roaming decision information reporting confirmation message, i.e., Status=0 in sequence number 6. Otherwise, it replies with a roaming decision information reporting failure message, i.e., Status=1.

[0292] S205, the MFU sends a roaming start instruction message to both the source SFU and the target SFU.

[0293] The roaming start indication message may also be called the roaming start message or other names, and this application embodiment does not limit this.

[0294] After receiving the roaming start indication message, the source SFU and the target SFU respectively start roaming, such as starting their own roaming switching state machine.

[0295] As an example, the roaming start indication message may include fields numbered 2-5 and 7-8 in Table 1-1, as shown in Table 2.

[0296] Table 2

[0297] In Tables 1-5, Payload and PayloadLen can have specified sequences added, such as all zeros, or these two fields can be excluded.

[0298] S206, the source SFU sends a roaming start confirmation message to the MFU. For example, after the source SFU completes its own roaming handover state machine startup, it sends a roaming start confirmation message to the MFU.

[0299] The roaming start confirmation message can also be named in other ways, such as roaming start successful message. This application embodiment does not limit this.

[0300] If the source SFU fails to initiate roaming processing, it will send a roaming start failure message to the MFU. Roaming start confirmation messages and roaming start failure messages can be collectively referred to as roaming start feedback messages. The roaming start feedback message indicates whether roaming initiation was successful. If it indicates success, it can be called a roaming start confirmation message; if it indicates failure, it can be called a roaming start failure message. The circumstances surrounding roaming initiation failure will be described in detail later and will not be repeated here.

[0301] As an example, the roaming start indication message may include fields numbered 2-8 in Table 1-1, as shown in Table 3 for example.

[0302] Table 3

[0303] In Tables 1-5, Payload and PayloadLen can have specified sequences added, such as all zeros, or these two fields can be excluded.

[0304] In Table 1-5, Status=0 corresponds to the roaming start confirmation message.

[0305] S207, the target SFU sends a roaming start confirmation message to the MFU. For example, after the target SFU completes its own roaming handover state machine startup, it sends a roaming start confirmation message to the MFU.

[0306] In step S208, after receiving roaming start confirmation messages from both the source SFU and the target SFU, the MFU sends a roaming preprocessing instruction to the target SFU. The roaming preprocessing instruction instructs the target SFU to complete preparations before roaming handover. The roaming preprocessing instruction message instructs the target SFU to perform roaming preparations for the STA.

[0307] Roaming preprocessing instructions, also known as roaming preprocessing messages, or other names are not limited to in this application.

[0308] When the target SFU receives the roaming preprocessing instruction message, it performs roaming preprocessing for the STA, or in other words, performs roaming preparation for the STA, and generates preprocessing information.

[0309] In one possible example, the preparation work involves simulating aggregation.

[0310] It should be noted that, to improve air interface transmission efficiency, aggregated transmission is performed between the access point (AP) and the STA. First, an aggregated session is established between the AP and the STA. Then, aggregated transmission occurs between the AP and the STA. For example, after receiving an aggregated frame from the STA, the AP can respond using a block acknowledge (BA) frame.

[0311] Simulated aggregation can be understood as the aggregation transmission between the simulation and the STA.

[0312] For example, the roaming preprocessing instruction includes parameters used to simulate aggregation. These could be aggregation parameters used to implement aggregated transmission with the STA, or aggregated frames.

[0313] As an example, the aggregation parameters are shown in Table 4. Table 4 can be applied to aggregation scenarios.

[0314] Table 4

[0315] In another possible example, the preparation work includes: creating users for STA and simulating aggregation.

[0316] For example, the roaming preprocessing instruction includes one or more of the following communication information: the STA's AID, an authentication request frame from the STA, an association request frame from the STA, or a key used for communication between the STA and the source SFU. Further, the target SFU creates a user for the STA based on the communication information in the roaming preprocessing instruction. The target SFU also performs simulated aggregation.

[0317] In one possible implementation scenario, the destination SFU has already established an association with the user. In this case, the parameters passed by the roaming preprocessing are aggregation parameters, and the destination SFU establishes an aggregation with the STA through the aggregation parameters passed by the MFU.

[0318] In another possible implementation scenario, if the destination SFU has not yet established an association with the user, the parameters passed by the roaming preprocessing are association parameters and aggregation information. The destination SFU establishes an association and aggregation relationship with the terminal through the association and aggregation information passed by the MFU.

[0319] The association parameters include the site's association request frame and / or the key negotiated between the site and the source SFU for communication. The association parameters may also include the site's authentication request frame.

[0320] In some possible implementation scenarios, the creation of users for the STA by the target SFU can be completed during the STA go-live phase.

[0321] As an example, the roaming preprocessing message may include fields numbered 2-5 and 7-8 in Table 1-1, as shown in Table 5.

[0322] Table 5

[0323] S209, the target SFU sends a roaming preprocessing completion message to the MFU. For example, after completing the above preparations, the target SFU sends a roaming preprocessing completion message to the MFU. The MFU then receives the roaming preprocessing completion message from the target SFU.

[0324] In the event of a roaming preprocessing failure, the target SFU will send a roaming preprocessing failure message to the MFU. Roaming preprocessing completion messages and roaming preprocessing failure messages can be collectively referred to as roaming preprocessing feedback messages. The roaming preprocessing feedback message indicates whether roaming preprocessing was successful. If it indicates success, it can be called a roaming preprocessing completion message; if it indicates failure, it can be called a roaming preprocessing failure message. The circumstances surrounding roaming preprocessing failure will be described in detail later and will not be repeated here.

[0325] As an example, the roaming preprocessing message may include fields numbered 2-5 and 7-8 in Table 1-1, as shown in Table 6 for example.

[0326] Table 6

[0327] In Table 6, Payload and PayloadLen can have specified sequences added, such as all zeros, or these two fields can be excluded.

[0328] In Table 6, Status=0 corresponds to a roaming preprocessing completion (or confirmation) message. Status=1-255 corresponds to a roaming preprocessing failure message.

[0329] S210, the MFU sends a service shutdown indication message to the source SFU. This service shutdown indication message can also be called a service shutdown indication message, or any other name; this embodiment does not limit its usage. The service shutdown indication message is used to instruct the source SFU to shut down service interaction with the STA.

[0330] As an example, the roaming preprocessing message may include fields numbered 2-5 and 7-8 in Table 1-1, as shown in Table 7.

[0331] Table 7

[0332] The Payload field can carry the parameters that the SFU needs to report. In some possible implementation scenarios, default or protocol-defined parameters can be used for reporting. In this case, it is not necessary to indicate the parameters that the SFU needs to report. In this case, a set sequence can be added to Payload and PayloadLen, such as all zeros, or these two fields can be omitted.

[0333] S211, the source SFU sends a service shutdown completion message to the MFU.

[0334] In the event of a service shutdown failure, the source SFU will send a service shutdown failure message to the MFU. Service shutdown completion messages and service shutdown failure messages can be collectively referred to as service shutdown feedback messages. The service shutdown feedback message indicates whether the service shutdown was successful. If it indicates success, it can be called a service shutdown completion message; if it indicates failure, it can be called a service shutdown failure message. The circumstances of service shutdown failure will be described in detail later and will not be repeated here.

[0335] As an example, the service closure completion message may include fields numbered 2-8 in Table 1-1, as shown in Table 8.

[0336] Table 8

[0337] In Table 8, Status=0 corresponds to a service closure completion (or confirmation) message. Status=1-255 corresponds to a service closure failure message.

[0338] After the source SFU successfully shuts down the service, it retrieves the parameters that need to be synchronized. The service shutdown completion message includes these parameters. These parameters include context information about the service interaction between the source SFU and the STA, such as the sequence numbers of the aggregate frames to be transmitted between the source SFU and the STA, and the sequence numbers of each data packet in the block acknowledgment.

[0339] As an example, the parameters that need to be synchronized can be found in Table 9.

[0340] Table 9

[0341] In addition to the sequence number context parameters in the second row (number 2) of the table above, in one possible scenario, the sequence number context field may include one or more of the following parameters: the downlink sequence number of the traffic corresponding to each TID (referred to as each TID), the downlink window start number of each TID, the downlink window last number of each TID, the downlink window bitmap of each TID, the uplink window start number of each TID, the uplink window last number of each TID, and the uplink window bitmap of each TID. After these context parameters are passed to the target SFU, the target SFU can continue the traffic service of the STA and avoid service interruption.

[0342] The information in sequence number 4 is optional. In some implementation scenarios, the key does not need to be updated, and the context information may include the fields in sequences 1-3.

[0343] Here, "key replay" indicates key reloading, and "rep replay counter" is a counter in the Extended Authentication Protocol over LAN (EAPOL) frame. The "Key replay counter__used" indicates the number of EAPOL-Key messages sent by the access point; this field increments by 1 for each EAPOL-Key message sent to prevent replay attacks. At the start of key negotiation, this field is 0 in the EAPOL-Key message sent by the AP. When the client receives the EAPOL-Key message, it records this value locally. When the client receives another EAPOL-Key message from the AP, this field must be greater than the locally recorded value; otherwise, the message is discarded and retransmitted. When the AP receives a message from the client, this field must match the value stored locally; otherwise, it waits for retransmission until a valid Key replay counter is received. If the maximum number of retransmissions is reached, the AP will delete the client.

[0344] In step S212, the MFU sends a service activation instruction message to the target SFU. This message can also be simply called the service activation message. It instructs the target SFU to initiate service interaction with the STA. The service activation instruction includes configuration parameters, such as context information, that need to be synchronized.

[0345] The service activation instruction message, also known simply as the service activation message, may be used under other names, but this application embodiment does not specifically limit it.

[0346] As an example, the service activation instruction message may include fields numbered 2-5 and 7-8 in Table 1-1, as shown in Table 10.

[0347] Table 10

[0348] S213, the target SFU receives the service activation instruction message and sends a service activation completion message to the MFU. After receiving the service activation instruction, the target SFU starts service interaction with the STA according to the parameters to be synchronized, and sends a service activation completion message to the MFU.

[0349] If the target SFU fails to initiate the service, it will send a service initiation failure message to the MFU. Service initiation success messages and service initiation failure messages can be collectively referred to as service initiation feedback messages. The service initiation feedback message indicates whether the service initiation was successful. If it indicates success, it can be called a service initiation success message; if it indicates failure, it can be called a service initiation failure message. The circumstances of service initiation failure will be described in detail later and will not be repeated here.

[0350] As an example, the service closure completion message may include fields numbered 2-8 in Table 1-1, as shown in Table 11 for example.

[0351] Table 11

[0352] In Table 11, Status=0 corresponds to a service activation completion (or confirmation) message. Status=1-255 corresponds to a service activation failure message.

[0353] In some possible implementations, the context information and aggregation parameters can also be sent to the target SFU in a single message. For example, in a service activation message.

[0354] After the MFU receives the service activation completion message from the target SFU, the roaming ends.

[0355] It should be noted that the names of the above messages can also be other names, such as first message, second message, etc., and this application embodiment does not limit this.

[0356] In some possible implementation scenarios, roaming anomalies may occur during the above roaming process. The following describes how to handle roaming anomalies.

[0357] Abnormal state 1: Exception that roaming failed to start.

[0358] Method 1: See Figure 3A and Figure 3B The diagram shown is a schematic flowchart of a roaming method provided in an embodiment of this application. When the MFU determines that the source SFU or the target SFU has failed to initiate roaming, it clears the roaming information of the STA. Figure 3A and Figure 3B The document describes the exception handling method for roaming failure to start.

[0359] In S301, the MFU sends a roaming start indication message to both the source SFU and the target SFU. See S205 for further details.

[0360] In one possible example, after receiving the roaming start indication message, the source SFU initiates roaming, for example, by starting its own roaming switching state machine. However, if roaming initiation fails, S302a is executed.

[0361] In another possible example, after receiving the roaming start indication message, the target SFU initiates roaming, for example, by starting its own roaming switching state machine. However, if roaming initiation fails, S302b is executed.

[0362] See Figure 3A As shown in S302a, the source SFU sends a roaming start failure indication message (which can be simply called a roaming start failure message or other names) to the MFU. For example, a software vulnerability (bug) or hardware failure in the source SFU can cause roaming to fail to start.

[0363] See Figure 3B As shown in S302b, the target SFU sends a roaming start failure indication message to the MFU. For example, a software vulnerability (bug) or hardware failure in the target SFU can cause roaming initiation to fail.

[0364] For example, the format of the roam start failure indication message can be seen in Table 3. Roam ProcessStatus=1, and Status≠0. In some implementation scenarios, Roam Status is a value between 1 and 255, used to indicate the error identification code. Different values ​​indicate different reasons for failure.

[0365] The SFU that fails to initiate roaming is either the source SFU or the target SFU. Figure 3A Taking the source SFU as an example, Figure 3B Take the target SFU as an example. In some possible scenarios, both the source SFU and the target SFU may experience roaming failures simultaneously.

[0366] S303, the MFU clears the roaming information of the STA, or in other words, clears the preparation information made for the STA's roaming, or the MFU clears the current roaming for the STA and waits for the next roaming trigger. Clearing roaming information can be achieved, for example, by disabling the state machine switching.

[0367] The above solution addresses the issue of roaming initiation failure by promptly clearing roaming-related information. The MFU then stops executing the roaming process, reducing instruction overhead, minimizing storage resource waste, and preventing the stored information from impacting subsequent roaming operations.

[0368] In some possible implementations, if the MFU determines that the source SFU has failed to initiate roaming when it sends a roaming start indication message to the source SFU for a certain period of time or when the number of retransmissions reaches a certain number of times, then it executes S303.

[0369] In other possible implementations, if the MFU determines that the target SFU has failed to initiate roaming when the time threshold for sending the roaming start indication message to the target SFU has been reached or the number of retransmissions has reached the number threshold, then S303 is executed.

[0370] Method 2: See Figure 4A and Figure 4B The diagram shown is a schematic flowchart of another roaming method provided in an embodiment of this application.

[0371] S401, see S301, will not be repeated here.

[0372] In one possible example, after receiving the roaming start indication message, the source SFU initiates roaming, for example, by starting its own roaming switching state machine. However, if roaming initiation fails, S402a is executed.

[0373] In another possible example, after receiving the roaming start indication message, the target SFU initiates roaming, for example, by starting its own roaming switching state machine. However, if roaming initiation fails, S402b is executed.

[0374] See Figure 4A As shown in S402a, the source SFU sends a roaming start failure indication message to the MFU.

[0375] See Figure 4B As shown in S402b, the target SFU sends a roaming start failure indication message to the MFU.

[0376] The SFU that fails to initiate roaming is either the source SFU or the target SFU. Figure 4A Taking the source SFU as an example, Figure 4BTaking the target SFU as an example. In some possible scenarios, both the source SFU and the target SFU may experience roaming start failure simultaneously. In such cases, both the source SFU and the target SFU will send a roaming start failure indication to the MFU.

[0377] S403, MFU clears the roaming information of the STA.

[0378] S404, the MFU sends a roaming exception handling message to the source SFU. The roaming exception handling message indicates that the roaming information should be cleared.

[0379] In the exception handling scenario at the start of roaming, the roaming exception handling message can also be called the roaming start exception handling message, or other names can be used. This application embodiment does not specifically limit this.

[0380] S405, the MFU sends a roaming exception handling message to the target SFU.

[0381] S406, the source SFU sends a roaming exception handling completion message to the MFU.

[0382] In the roaming start exception handling scenario, the roaming exception handling completion message can also be called the roaming start exception handling completion message, or other names can be used. This application embodiment does not specifically limit this.

[0383] When the source SFU receives a roaming exception handling message, it deletes the roaming information of the STA, such as deleting the started switching state machine, and then sends a roaming exception handling completion message to the MFU.

[0384] S407, the target SFU sends a roaming exception handling completion message to the MFU.

[0385] When the target SFU receives a roaming exception handling message, it deletes the roaming information of the STA, such as deleting the started switching state machine, and then sends a roaming exception handling completion message to the MFU.

[0386] The above solution addresses the issue of roaming initiation failure by promptly clearing roaming-related information. Neither the MFU nor the SFU will continue executing the roaming process, reducing instruction overhead and minimizing storage resource waste. It also prevents stored information from impacting subsequent roaming operations.

[0387] In some possible implementations, if the MFU determines that the source SFU has failed to initiate roaming when it sends a roaming start indication message to the source SFU for a certain period of time or when the number of retransmissions reaches a certain number of times, then it executes S404-S405.

[0388] In other possible implementations, if the MFU determines that the target SFU has failed to initiate roaming when the time threshold for sending the roaming start indication message to the target SFU has been reached or the number of retransmissions has reached the number threshold, then S404-S405 are executed.

[0389] Abnormal Status 2: Exception of roaming preprocessing failure.

[0390] Method 1: See Figure 5 The diagram shown is a flowchart of a roaming method provided in an embodiment of this application.

[0391] In S501, the MFU sends a roaming preprocessing message to the target SFU. See S208 for details.

[0392] After receiving the roaming preprocessing message, the target SFU completes pre-handover preparations. These preparations may include simulating aggregation. Optionally, the preparations may also include creating users for the STA.

[0393] S502, the target SFU sends a roaming preprocessing failure indication message to the MFU. Upon receiving the roaming preprocessing failure indication message, the MFU determines that the target SFU's roaming preprocessing has failed. For example, a software vulnerability (bug) or hardware failure in the target SFU can both lead to roaming preprocessing failure.

[0394] For example, the format of the roaming preprocessing failure indication message can be seen in Table 6. Roam NotifyStatus=2, and Roam Status≠0. In some implementation scenarios, Roam Status is a value between 1 and 255, used to indicate the error identification code. Different values ​​indicate different reasons for failure.

[0395] S503, MFU clears the roaming information of the STA, or in other words, clears the preparation information made for the STA's roaming. Clearing roaming information can, for example, disable the switching state machine.

[0396] In some possible implementations, if the MFU determines that the roaming preprocessing of the target SFU has failed when the time threshold for sending the roaming preprocessing instruction message to the target SFU is reached or the number of retransmissions reaches the number threshold, then S503 is executed.

[0397] Method 2: See Figure 6 The diagram shown is a schematic flowchart of another roaming method provided in an embodiment of this application.

[0398] S601, see S501, will not be repeated here.

[0399] S602, the target SFU sends a roaming preprocessing failure indication to the MFU. Upon receiving the roaming preprocessing failure indication message, the MFU determines that the target SFU's roaming preprocessing has failed. For example, a software vulnerability (bug) or hardware failure in the target SFU can both lead to roaming preprocessing failure.

[0400] Optionally, in step S603, the MFU clears the roaming information of the STA.

[0401] S604, the MFU sends a roaming exception handling message to the target SFU. The roaming exception handling message instructs the deletion of roaming-related information for that site.

[0402] S605, the MFU sends a roaming exception handling message to the source SFU. The roaming exception handling message instructs the removal of roaming-related information for that site.

[0403] In the exception handling scenario of this roaming preprocessing, the roaming exception handling message can also be called the roaming preprocessing exception handling message, or other names can be used. This application embodiment does not specifically limit this.

[0404] S606, the target SFU sends a roaming exception handling completion message to the MFU.

[0405] S607, the source SFU sends a roaming exception handling completion message to the MFU.

[0406] In the exception handling scenario of this roaming preprocessing, the roaming exception handling completion message can also be called the roaming preprocessing exception handling completion message, or other names can be used. This application embodiment does not specifically limit this.

[0407] When the target SFU receives a roaming exception handling message, it deletes the roaming information and preprocessing information of the STA. For example, deleting the STA's roaming information includes deleting the initiated switching state machine. It also deletes preprocessing information, including deleting simulated aggregation information and user information for created STAs. Then, it sends a roaming exception handling complete message to the MFU.

[0408] When the source SFU receives a roaming exception handling message, it clears the roaming message, such as by deleting the started switching state machine.

[0409] In some possible implementations, if the MFU sends a roaming preprocessing instruction message to the target SFU for a certain period of time or a certain number of retransmissions, and does not receive a roaming preprocessing completion message from the target SFU (or does not receive a reply message from the target SFU), it determines that the roaming preprocessing of the target SFU has failed, and then executes S604-S605.

[0410] Abnormal Status 3: Service shutdown failure exception.

[0411] Method 1: See Figure 7 The diagram shown is a flowchart of a roaming method provided in an embodiment of this application.

[0412] In S701, the MFU sends a service shutdown instruction message to the source SFU. See S209 for details.

[0413] S702, the source SFU sends a service shutdown failure indication message to the MFU. Upon receiving the service shutdown failure indication message, the MFU determines that the service shutdown of the source SFU has failed.

[0414] For example, if the source SFU has a software vulnerability (bug) or a hardware failure, the service shutdown may fail.

[0415] For example, the format of the roaming preprocessing failure indication message can be seen in Table 6. Roam NotifyStatus=3, and Roam Status≠0. In some implementation scenarios, Roam Status is a value between 1 and 255, used to indicate the error identification code. Different values ​​indicate different reasons for failure.

[0416] S703, the MFU sends a roaming exception handling message a1 to the source SFU. The roaming exception handling message a1 instructs the source SFU to restore the configuration prior to roaming initiation for the site.

[0417] S704, the MFU sends a roaming exception handling message a2 to the target SFU. The roaming exception handling message a2 instructs the target SFU to delete roaming-related information for the STA.

[0418] Optionally, MFU removes roaming-related information from a site.

[0419] In the abnormal handling scenario of service shutdown, the roaming abnormal handling message can also be called the service shutdown abnormal handling message, or other names can be used. This application embodiment does not make specific limitations on this.

[0420] S705, the source SFU sends a roaming exception handling completion message to the MFU. Upon receiving the roaming exception handling message a1, the source SFU restores the configuration of the STA before roaming startup, and then sends back a roaming exception handling completion message.

[0421] S706, the target SFU sends a roaming exception handling completion message to the MFU. Upon receiving the roaming exception handling message a2, the target SFU deletes the roaming-related information for the STA, and then sends back a roaming exception handling completion message.

[0422] In the abnormal handling scenario of service shutdown, the roaming abnormal handling completion message can also be called the service shutdown abnormal handling completion message, or other names can be used. This application embodiment does not make specific limitations on this.

[0423] In some possible implementations, the MFU can restore the configuration of the site before roaming was initiated, such as deleting the site's roaming-related information.

[0424] In some possible implementations, if the MFU determines that the source SFU service shutdown has failed when the time threshold for sending the service shutdown indication message to the source SFU has been reached or the number of retransmissions has reached the number of times it has been retransmitted has been reached, and no service shutdown completion message has been received from the source SFU (or no reply message has been received from the source SFU), then S703-S704 are executed.

[0425] Method 2: See Figure 8 The diagram shown is a flowchart of a roaming method provided in an embodiment of this application.

[0426] In S801, the MFU sends a service shutdown instruction message to the source SFU. See S209 for details.

[0427] S802, the source SFU sends a service shutdown failure indication message to the MFU. Upon receiving the service shutdown failure indication message, the MFU determines that the service shutdown of the source SFU has failed. For example, a software vulnerability (bug) or hardware failure in the source SFU may cause service shutdown failure.

[0428] For example, the format of the roaming preprocessing failure indication message can be seen in Table 6. Roam NotifyStatus=3, and Roam Status≠0. In some implementation scenarios, Roam Status is a value between 1 and 255, used to indicate the error identification code. Different values ​​indicate different reasons for failure.

[0429] S803, the MFU sends a roaming anomaly handling message b1 to the source SFU. Roaming anomaly handling message b1 indicates that the site should be removed from the network.

[0430] S804, the MFU sends a roaming anomaly handling message b2 to the target SFU. Roaming anomaly handling message b2 indicates that the site should be removed from the network.

[0431] In the abnormal handling scenario of service shutdown, the roaming abnormal handling message can also be called the service shutdown abnormal handling message, or other names can be used. This application embodiment does not make specific limitations on this.

[0432] Optionally, the MFU removes the site from the network.

[0433] S805, the source SFU sends a roaming exception handling completion message to the MFU. Upon receiving the roaming exception handling message b1, the source SFU removes the site from the network and then sends back a roaming exception handling completion message.

[0434] S806, the target SFU sends a roaming exception handling completion message to the MFU. Upon receiving the roaming exception handling message b2, the target SFU removes the site from the network and then sends back a roaming exception handling completion message.

[0435] In the abnormal handling scenario of service shutdown, the roaming abnormal handling completion message can also be called the service shutdown abnormal handling completion message, or other names can be used. This application embodiment does not make specific limitations on this.

[0436] In some possible implementations, if the MFU determines that the source SFU service shutdown has failed when the time threshold for sending the service shutdown indication message to the source SFU has been reached or the number of retransmissions has been reached, and no service shutdown completion message has been received from the source SFU (or no reply message has been received from the source SFU), then S803-S804 are executed.

[0437] Abnormal Status 4: Service startup failure.

[0438] Method 1: See Figure 9 The diagram shown is a flowchart of a roaming method provided in an embodiment of this application.

[0439] In S901, the MFU sends a service activation instruction to the target SFU. See S211 for details, which will not be repeated here.

[0440] S902, the target SFU sends a service activation failure indication to the MFU. Upon receiving the service activation failure indication message, the MFU determines that the service activation of the target SFU has failed. For example, a software vulnerability (bug) or hardware failure in the target SFU can lead to service activation failure.

[0441] Optionally, if the MFU receives a service activation failure indication, the MFU will delete the roaming-related information for the site or restore the configuration prior to roaming activation for that STA.

[0442] S903, the MFU sends a roaming exception handling message c1 to the target SFU. The roaming exception handling message c1 indicates that the configuration prior to the start of roaming for this STA should be restored.

[0443] S904, the MFU sends a roaming exception handling message c1 to the source SFU. The roaming exception handling message c2 indicates that the configuration prior to the start of roaming for this STA should be restored.

[0444] In the scenario of handling exceptions during service activation, the roaming exception handling message can also be called the service activation exception handling message, or other names can be used. This application embodiment does not specifically limit this.

[0445] S905, the target SFU sends a roaming exception handling completion message to the MFU. Upon receiving the roaming exception handling message c1, the target SFU restores the configuration prior to roaming initiation for that STA, and then sends back a roaming exception handling completion message.

[0446] S906, the source SFU sends a roaming exception handling completion message to the MFU. Upon receiving the roaming exception handling message c2, the source SFU restores the configuration prior to roaming initiation for that STA, and then sends back a roaming exception handling completion message.

[0447] In the scenario of handling exceptions during the service activation, the roaming exception handling completion message can also be called the service activation exception handling completion message, or other names can be used. This application embodiment does not specifically limit this.

[0448] In some possible implementations, if the MFU sends a service activation instruction message to the target SFU for a certain period of time or a certain number of retransmissions, and does not receive a service activation completion message from the target SFU (or does not receive a reply message from the target SFU), it determines that the service activation of the target SFU has failed, and then executes S903-S904.

[0449] Method 2: See Figure 10 The diagram shown is a flowchart of a roaming method provided in an embodiment of this application.

[0450] In S1001, the MFU sends a service activation instruction to the target SFU. See S211 for details, which will not be repeated here.

[0451] S1002, the target SFU sends a service activation failure indication to the MFU.

[0452] S1003, the MFU sends a roaming anomaly handling message d1 to the target SFU. Roaming anomaly handling message d1 instructs the STA to be removed from the network. The target SFU deletes the relevant information of the STA.

[0453] S1004, the MFU sends a roaming anomaly handling message d1 to the source SFU. Roaming anomaly handling message d1 instructs the STA to be removed from the network. The source SFU deletes the relevant information of the STA.

[0454] S1005, the target SFU sends a roaming exception handling completion message to the MFU.

[0455] S1006, the source SFU sends a roaming exception handling completion message to the MFU. The MFU records the failure error code of the STA.

[0456] In some possible implementations, if the MFU sends a service activation instruction message to the target SFU for a certain period of time or a certain number of retransmissions, and does not receive a service activation completion message from the target SFU (or does not receive a reply message from the target SFU), it determines that the service activation of the target SFU has failed, and then executes S1003-S1004.

[0457] As an example, the roaming exception handling messages involved in the above roaming exception handling process can reuse the format of the roaming handover indication message. See Table 12 for example.

[0458] Table 12

[0459] As an example, the roaming exception handling completion message involved in the above roaming exception handling process can reuse the format of the roaming switchover feedback indication message. See Table 13 for example.

[0460] Table 13

[0461] In some possible implementation scenarios, load-related fields in some roaming exception handling messages and roaming exception handling completion messages can be empty.

[0462] As another example, the roaming exception handling messages involved in the above roaming exception handling process may include fields 2-5 and 7-8 in Table 1-1. See Table 14.

[0463] Table 14

[0464] Among them, Roam Process Status=1 corresponds to the roaming start exception handling message. Roam ProcessStatus=2 corresponds to the roaming preprocessing exception handling message. Roam Process Status=3 corresponds to the service shutdown exception handling message. Roam Process Status=4 corresponds to the service startup exception handling message.

[0465] As another example, the roaming exception handling messages involved in the above roaming exception handling process may include fields 2-5 and 7-8 in Table 1-1. See Table 15.

[0466] Table 15

[0467] Specifically, Roam Process Status=1 and Status=0 corresponds to the roaming start exception handling completion (or confirmation or success) message. Roam Process Status=2 and Status=0 corresponds to the roaming preprocessing exception handling completion (or confirmation or success) message. Roam Process Status=3 and Status=0 corresponds to the service closure exception handling completion (or confirmation or success) message. Roam Process Status=4 and Status=0 corresponds to the service startup exception handling completion (or confirmation or success) message.

[0468] In this application, all parameters in the tables above, except for Table 1-2, can be carried in the message content field of the WMCI message in Table 1-2 as optional or required fields for transmission.

[0469] The parameters in each row of Tables 1-1, 1-4, 1-5, 1-6, and 2-15 above (e.g., AP ID, VAP ID, Macaddress, Token, Roma process status, Rsp flag, Tidvalid, payload, payload_len, RSSI, SSID, Auth information, Assoc information, aggregation information, PN number, SN context, IP ID, key update information, payload, Fram type, STA_ID, AP_ID, Ap inst, Cb, Cb_len, Type, key information, status, etc.) can be represented in the WMCI message not only in the masked form shown in Table 1-2 (bytes 5-N), but also in other forms. For example, one or more of the above parameters can be represented in the message using the type-length-value (TLV) format. Each TLV can carry one or more parameters. If a TLV carries multiple parameters, these parameters can be used as the "value" of that TLV, or multiple parameters can be carried as sub-TLVs. For example, the "value" of a TLV can include two parameters, Cb and Cb_len, or the TLV can include at least two sub-TLVs, one of which has the "value" of Cb and the other has the "value" of Cb_len.

[0470] Furthermore, each parameter can be carried in a single message or multiple messages. For example, the MAC address parameter can be carried in a roaming exception handling message or a service shutdown completion message, while the VAP ID parameter can be carried in a service activation indication message or a roaming preprocessing message. If a parameter is carried in multiple different messages, it can be an optional parameter in one or more messages, or a required parameter in another or some messages.

[0471] If the above parameters are represented in TLV format, the format of the WMCI message can be shown in Table 16 below: Table 16

[0472] Figure 11 This is a structural diagram of the roaming device provided in the embodiments of this application. This device can be implemented as part or all of a device through software, hardware, or a combination of both, and is applied to an MFU or SFU. The device provided in the embodiments of this application can implement some of the processes described in the methods of the embodiments of this application. The device includes: a sending module 1101 and a receiving module 1102. Optionally, it also includes a processing module 1103.

[0473] In one possible implementation scenario, this device is applied to an MFU (Multi-Functional Unit). The various modules described above work together to achieve... Figures 2-10 The method flow executed by the MFU in any corresponding embodiment.

[0474] In one possible embodiment, the receiving module 1102 is used to obtain roaming decision information of SFUs in the network; Processing module 1103 is used to determine the target SFU for the site based on the roaming decision information; The sending module 1101 is used to send a roaming start indication message to the target SFU, the roaming start indication message being used to indicate that roaming processing is initiated for the site.

[0475] In another possible embodiment, Sending module 1101 is used to send a roaming preprocessing message to the target SFU, the roaming preprocessing message being used to instruct the target SFU to initiate roaming preparation for the site; The receiving module 1102 is used to receive a roaming preprocessing feedback message from the target SFU, the roaming preprocessing feedback message being used to indicate whether the roaming preparation for the site is successful.

[0476] In another possible embodiment, The sending module 1101 is used to send a service shutdown instruction message to the source SFU during the roaming process of the site. The service shutdown message is used to instruct the source SFU to shut down the service interaction with the site. The receiving module 1102 is used to receive a service shutdown feedback message from the source SFU, the service shutdown feedback message being used to indicate whether the service interaction with the site has been successfully shut down.

[0477] In another possible embodiment, The sending module 1101 is used to send a service activation indication message to the target SFU during the roaming process of the site. The service activation indication message is used to instruct the target SFU to activate service interaction with the site. The receiving module 1102 is used to receive a service activation feedback message from the target SFU, the service activation feedback message being used to indicate whether the service interaction with the site has been successfully activated.

[0478] In another possible implementation scenario, the device is applied to the source SFU. The various modules described above work together to achieve... Figures 2-10 The method flow executed by the source SFU in any corresponding embodiment.

[0479] In one possible implementation: The receiving module 1102 is configured to receive a roaming start indication message from the main optical network unit (MFU), wherein the roaming start indication message is used to indicate that roaming processing is initiated for the site; the SFU is either the source SFU currently accessed by the site or the target SFU determined by the MFU for roaming of the site. Processing module 1103 is used to initiate roaming processing for the site.

[0480] In another possible embodiment, The receiving module 1102 is configured to receive a roaming anomaly handling message from the main optical network unit (MFU) when the source sub-optical network unit (SFU) has initiated roaming processing for the site. The roaming anomaly handling message is used to instruct the clearing of roaming-related information for the site. The source SFU is the SFU currently accessed by the site. Processing module 1103 is used to clear roaming-related information for the site.

[0481] In another possible embodiment, The receiving module 1102 is used to receive a service shutdown indication message from the main optical network unit (MFU) during the roaming process of the site. The service shutdown message is used to instruct the source SFU to shut down service interaction with the site. The sending module 1101 is used to send a service shutdown feedback message to the MFU, the service shutdown feedback message being used to indicate whether the source SFU has successfully shut down the service interaction with the site.

[0482] In another possible embodiment, The receiving module 1102 is configured to receive a first roaming error handling message from the main optical network unit (MFU) when the source sub-optical network unit (SFU) has initiated roaming processing for the site. The first roaming error handling message is used to indicate the restoration of the configuration before the roaming for the site was initiated. The target SFU is the target SFU for the site roaming handover. Processing module 1101 restores the configuration for the site before roaming was initiated.

[0483] In another possible implementation scenario, the device is applied to the target SFU. The various modules described above work together to achieve... Figures 2-10 The method flow executed by the target SFU in any corresponding embodiment.

[0484] In one possible implementation: The receiving module 1102 is configured to receive a roaming start indication message from the main optical network unit (MFU), wherein the roaming start indication message is used to indicate that roaming processing is initiated for the site; the SFU is either the source SFU currently accessed by the site or the target SFU determined by the MFU for roaming of the site. Processing module 1103 is used to initiate roaming processing for the site.

[0485] In another possible embodiment, the receiving module 1102 is configured to receive a roaming preprocessing message from the main optical network unit (MFU), the roaming preprocessing message being used to instruct the target SFU to initiate roaming preparation for the site; The sending module 1101 is used to send a roaming preprocessing feedback message to the MFU, the roaming preprocessing feedback message being used to indicate whether the roaming preparation for the site is successful.

[0486] In another possible embodiment, The receiving module 1102 is configured to receive a second roaming anomaly handling message from the main optical network unit (MFU) when the target sub-optical network unit (SFU) has initiated roaming processing for the site. The second roaming anomaly handling message is used to instruct the clearing of roaming-related information for the site. The source SFU is the SFU currently accessed by the site. Processing module 1103 is used to clear roaming-related information for the site.

[0487] In another possible embodiment, The receiving module 1102 is used to receive a service activation indication message from the main optical network unit (MFU) during the roaming process of the site. The service activation indication message is used to instruct the target SFU to activate service interaction with the site. The sending module 1101 is used to send a service activation feedback message to the MFU, the service activation feedback message being used to indicate whether the source SFU has successfully activated service interaction with the site.

[0488] Figure 11 For details on the roaming process of the roaming device shown, please refer to the descriptions in the previous embodiments; they will not be repeated here.

[0489] This application also provides a device 100. For example... Figure 12 As shown, device 100 includes a bus 102, a processor 104, a memory 106, and a communication interface 108. The processor 104, memory 106, and communication interface 108 communicate via the bus 102. Device 100 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in device 100.

[0490] Bus 102 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 9 The bus 104 may be represented by a single line, but this does not mean that there is only one bus or one type of bus. The bus 104 may include a path for transmitting information between various components of the device 100 (e.g., memory 106, processor 104, communication interface 108).

[0491] The processor 104 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0492] Memory 106 may include volatile memory, such as random access memory (RAM). Memory 106 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0493] The memory 106 stores executable program code, which the processor 104 executes to implement the roaming method. That is, the memory 106 stores program instructions for executing the roaming management method.

[0494] The communication interface 108 uses an optical module to enable communication between the device 100 and other devices or communication networks.

[0495] In one possible embodiment, processor 104 executes executable program code stored in memory 106. Figures 2-10 The method flow executed by the source SFU in any corresponding embodiment.

[0496] In another possible embodiment, processor 104 executes executable program code in memory 106. Figures 2-10The method flow executed by the target SFU in any corresponding embodiment.

[0497] In another possible implementation, processor 104 executes executable program code stored in memory 106. Figures 2-10 The method flow executed by the MFU in any corresponding embodiment.

[0498] This application also provides a computer program product including program instructions stored in a computer-readable storage medium. A processor reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the processor to perform the above-described actions. Figures 2-10 The process of MFU execution, or execution Figures 2-10 The process executed by the source SFU in the middle, or Figures 2-10 The process of executing the target SFU in the process.

[0499] One embodiment of this application provides a communication system including the aforementioned MFU, a source SFU, and a target SFU. Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the communication system described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0500] One embodiment of this application provides a computer-readable medium for storing a computer program, the computer program including functions for executing... Figures 2-10 The instructions for the method steps executed by the MFU in the corresponding method embodiment, or for executing Figures 2-10 The instructions for the method steps executed by the source SFU in the corresponding method embodiment, or for executing Figures 2-10 The instructions for the method steps executed by the target SFU in the corresponding method embodiment.

[0501] Those skilled in the art will recognize that the method steps and units described in the embodiments disclosed in this application can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0502] In the embodiments provided in this application, it should be understood that the disclosed system architecture, apparatus, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, or may be electrical, mechanical, or other forms of connection.

[0503] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0504] Furthermore, the modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or in software.

[0505] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0506] In this application, the terms "first" and "second," etc., are used to distinguish identical or similar items that have substantially the same function and purpose. It should be understood that there is no logical or temporal dependency between "first" and "second," nor does it limit the quantity or execution order. It should also be understood that although the following description uses the terms "first" and "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are merely used to distinguish one element from another. For example, without departing from the scope of the various examples, a first access point can be referred to as a second access point, and similarly, a second access point can be referred to as a first access point. Both a first access point and a second access point can be access points, and in some cases, they can be separate and distinct access points.

[0507] The above description is merely an exemplary embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and such modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A roaming method, characterized in that, include: The target sub-optical network unit (SFU) receives a roaming preprocessing message from the main optical network unit (MFU), which instructs the target SFU to initiate roaming preparation for the site. The target SFU sends a roaming preprocessing feedback message to the MFU, the roaming preprocessing feedback message being used to indicate whether the roaming preparation for the site was successful.

2. The method as described in claim 1, characterized in that, The roaming preprocessing message is carried in the Wi-Fi management and control interface message.

3. The method as described in claim 1 or 2, characterized in that, The roaming preprocessing message includes the identifier of the site.

4. The method according to any one of claims 1-3, characterized in that, The roaming preprocessing message includes aggregation parameters, which are used to establish an aggregation between the target SFU and the site.

5. The method according to any one of claims 1-3, characterized in that, The roaming preprocessing message includes aggregation parameters and association parameters. The aggregation parameters are used to establish an aggregation between the target SFU and the site, and the association parameters are used to establish an association between the target SFU and the site.

6. The method as described in claim 5, characterized in that, The association parameters include: the association request frame of the site and / or the key used for communication.

7. The method according to any one of claims 4-6, characterized in that, The aggregation parameters include traffic identifiers and / or aggregation information.

8. The method as described in claim 7, characterized in that, The traffic identifier indicates the traffic that needs to be aggregated in the uplink or downlink direction.

9. The method as described in claim 7, characterized in that, The aggregation information includes aggregation request frames and / or aggregation response frames.

10. The method as described in claim 7, characterized in that, The aggregation information includes: aggregation request frames for uplink traffic and / or aggregation request parameters and aggregation response frames for downlink traffic.

11. The method according to any one of claims 1-7, characterized in that, The roaming preprocessing feedback message indicates that the target SFU has successfully completed roaming preparation for the site.

12. The method according to any one of claims 1-7, characterized in that, The roaming preprocessing feedback message indicates that the target SFU's roaming preparation for the site has failed; The method further includes: The target SFU receives a roaming exception handling message sent by the MFU, which is used to instruct the clearing of roaming-related information for the site.

13. The method as described in claim 12, characterized in that, The method further includes: the target SFU sending a roaming exception handling completion message to the MFU.

14. A sub-optical network unit (SFU), characterized in that, The SFU is used to perform the roaming method as described in any one of claims 1 to 13.

15. A computer storage medium, characterized in that, The computer storage medium includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method according to any one of claims 1-13.

16. A computer program product, characterized in that, When the program code contained in the computer program product is executed by a processor in an electronic device, the electronic device performs the method according to any one of claims 1-13.

17. A communication system comprising a sub-optical network unit (SFU) and a main optical network unit (MFU), wherein the SFU is configured to perform the method according to any one of claims 1-13.

Images