Roaming method and device

Abstract

The invention discloses a roaming method and device, relates to the technical field of communication, and is used for providing a processing flow of master and slave optical network units. The method comprises the following steps: the MFU determines a target SFU for the station according to the roaming decision information; and the MFU sends a roaming start indication message to the target SFU, wherein the roaming start indication message is used for indicating to start roaming processing for the station.

Description

[0001] Related Cross References

[0002] This application claims the priority of a Chinese patent application with the application number 202411563236.6 and the invention title "A Roaming Method and Device" filed on November 4, 2024, and a Chinese patent application with the application number 202411761234.8 and the invention title "A Roaming Method and Device" filed on November 29, 2024. The entire contents thereof are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technologies, and particularly to a roaming method and device. Background Art

[0004] When the channel quality between a terminal and the currently associated access point deteriorates during the movement of the terminal in an FTTR network, it is necessary to roam to an access point with better channel quality to ensure the continuity of services. Currently, the processing flow between the master and slave optical network units in an FTTR network has not been discussed. Summary of the Invention

[0005] Embodiments of this application provide a roaming method and device for providing a processing flow for master and slave optical network units.

[0006] In a first aspect, an embodiment of this application provides a roaming method, including:

[0007] The master optical network unit MFU obtains the roaming decision information of the SFUs in the network;

[0008] The MFU determines a target SFU for the station according to the roaming decision information;

[0009] The MFU sends a roaming start indication message to the target SFU, and the roaming start indication message is used to indicate to start roaming processing for the station.

[0010] In a possible implementation scenario, the source access point may be the MFU. In another possible implementation scenario, the source access point may be the source SFU.

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

[0012] In a possible design, the start of roaming processing includes starting a roaming handover state machine.

[0013] In a possible design, the roaming start indication message includes the identifier of the station.

[0014] In a possible design, the method further includes:

[0015] The MFU receives a roaming start confirmation message from the target SFU, and the roaming start confirmation message indicates that the target SFU has successfully completed the roaming start for the site.

[0016] In a possible design, the method further includes:

[0017] The MFU receives a roaming start failure message from the target SFU, and the roaming start failure message indicates that the roaming start of the target SFU for the site fails;

[0018] The MFU clears the roaming-related information for the site.

[0019] In a possible design, the method further includes:

[0020] The MFU sends a roaming start indication message to the source SFU, and the roaming start indication message is used to indicate to start the roaming process for the site.

[0021] In a possible design, the method further includes:

[0022] The MFU receives a roaming start confirmation message from the source SFU, and the roaming start confirmation message indicates that the source SFU has successfully completed the roaming start for the site.

[0023] In a possible design, the method further includes:

[0024] The MFU receives a roaming start failure message from the source SFU, and the roaming start failure message indicates that the roaming start of the source SFU for the site fails;

[0025] The MFU clears the roaming-related information for the site.

[0026] In a possible design, the method further includes:

[0027] The MFU sends a roaming exception handling message to the source SFU and the target SFU, and the roaming exception handling message is used to indicate to clear the roaming-related information for the site.

[0028] In a possible design, the method further includes:

[0029] The MFU receives a roaming exception handling completion message from the source SFU; and / or,

[0030] The MFU receives the roaming exception handling completion message from the target SFU.

[0031] In a possible design, the roaming decision information includes one or more of the signal strength, load information, or channel condition information between the stations.

[0032] On the other hand, an embodiment of the present application further provides a roaming method, which mainly includes:

[0033] The master optical network unit MFU obtains the roaming decision information of at least one SFU in the network;

[0034] The MFU determines a target access point for the station currently accessing the source SFU according to the roaming decision information, and the target access point is the MFU;

[0035] The MFU sends a roaming start indication message to the source SFU, and the roaming start indication message is used to indicate to start the roaming process for the station.

[0036] The roaming method provided by the present invention can roam the station from the currently accessed source SFU to the target access point, that is, the MFU. Then the station can perform network access at the MFU and continue the current service.

[0037] In a possible design, the MFU obtains the roaming decision information of the SFU by receiving a roaming decision information collection and reporting message sent by the SFU in the network, and obtains the roaming decision information of the SFU from the roaming decision information collection and reporting message.

[0038] In addition, the MFU can also obtain its own roaming decision information.

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

[0040] In a possible design, after the MFU determines that the MFU is the target access point of the station according to the roaming decision information, the MFU starts the roaming process for the station.

[0041] In a possible design, the start of the roaming process includes starting a roaming handover state machine.

[0042] In a possible design, the roaming start indication message includes the identifier of the station, which is convenient for the target SFU to start the roaming process for the station.

[0043] In a possible design, the roaming method further includes: the MFU receives a roaming start confirmation message from the source SFU, and the roaming start confirmation message indicates that the source SFU has successfully completed the roaming start for the station. The MFU can start the subsequent roaming process according to the roaming start confirmation message, such as performing roaming preprocessing.

[0044] In a possible design, the roaming preprocessing includes simulating an aggregated transmission with the STA.

[0045] In a possible design, the roaming preprocessing includes creating a user for the STA.

[0046] In a possible design, the roaming method further includes:

[0047] The MFU receives a roaming start failure message from the source SFU, where the roaming start failure message indicates that the source SFU fails to initiate roaming for the site, and the MFU clears the roaming-related information for the site.

[0048] In a possible design, the roaming method further includes:

[0049] The MFU sends a roaming exception handling message to the source SFU, where the roaming exception handling message is used to indicate clearing the roaming-related information for the site.

[0050] In a possible design, the roaming method further includes:

[0051] The MFU receives a roaming exception handling completion message from the source SFU; and / or,

[0052] The MFU receives the roaming exception handling completion message from the target SFU.

[0053] In a possible design, the roaming decision information obtained by the MFU includes one or more of the signal strength, load information, or channel condition information between the MFU and the site.

[0054] In a second aspect, an embodiment of the present application provides a roaming method, including:

[0055] A sub-optical network unit (SFU) receives a roaming start indication message from a main optical network unit (MFU), where the roaming start indication message is used to indicate initiating roaming processing for the site; the SFU is the source SFU to which the site is currently connected or the target SFU determined by the MFU for roaming of the site;

[0056] The SFU initiates roaming processing for the site.

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

[0058] In a possible design, the initiating roaming processing includes initiating a roaming handover state machine.

[0059] In a possible design, the roaming start indication message includes an identifier of the site.

[0060] In a possible design, the method further includes:

[0061] The SFU sends the roaming start confirmation message to the MFU, and the roaming start confirmation message indicates that the SFU has successfully completed the roaming start for the site.

[0062] In a possible design, the method further includes:

[0063] The SFU sends a roaming start failure message to the MFU, and the roaming start failure message indicates that the roaming start of the SFU for the site fails.

[0064] In a possible design, the method further includes:

[0065] The SFU receives a roaming exception handling message from the MFU, and the roaming exception handling message is used to indicate clearing the roaming-related information for the site;

[0066] The SFU clears the roaming-related information for the site.

[0067] In a possible design, the method further includes:

[0068] The SFU sends a roaming exception handling completion message to the MFU.

[0069] In a possible design, the method further includes:

[0070] The SFU sends roaming decision information to the MFU.

[0071] In a possible design, the roaming decision information includes one or more of the signal strength, load information, or channel condition information with the site.

[0072] In a third aspect, an embodiment of the present application provides a roaming device, and the device has the functions of implementing the above first aspect and the optional manners of the first aspect. The device includes at least one module, and at least one module is used to implement the method provided by the above eleventh aspect and the optional manners of the eleventh aspect. In a possible design, applied to a master optical network unit MFU, it includes:

[0073] A receiving module, configured to obtain the roaming decision information of the SFU in the network;

[0074] A processing module, configured to determine a target SFU for the site according to the roaming decision information;

[0075] A sending module, configured to send a roaming start indication message to the target SFU, where the roaming start indication message is used to indicate to start roaming processing for the site.

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

[0077] In a possible design, the starting of the roaming processing includes starting a roaming handover state machine.

[0078] In a possible design, the roaming start indication message includes an identifier of the site.

[0079] In a possible design, the receiving module is further configured to:

[0080] Receive a roaming start confirmation message from the target SFU, where the roaming start confirmation message indicates that the target SFU has successfully completed the roaming start for the site.

[0081] In a possible design, the receiving module is further configured to receive a roaming start failure message from the target SFU, where the roaming start failure message indicates that the roaming start for the site by the target SFU fails;

[0082] The processing module is further configured to clear the roaming-related information for the site.

[0083] In a possible design, the sending module is further configured to send a roaming start indication message to the source SFU, where the roaming start indication message is used to indicate to start roaming processing for the site.

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

[0085] In a possible design, the receiving module is further configured to receive a roaming start failure message from the source SFU, where the roaming start failure message indicates that the roaming start for the site by the source SFU fails;

[0086] The processing module is further configured to clear the roaming-related information for the site.

[0087] In a possible design, the sending module is further configured to send a roaming exception handling message to the source SFU and the target SFU, where the roaming exception handling message is used to indicate to clear the roaming-related information for the site.

[0088] In a 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.

[0089] In a possible design, the roaming decision information includes one or more of the signal strength between the sites, load information, or channel condition information.

[0090] In a fourth aspect, an embodiment of the present application provides a roaming device. An embodiment of the present application provides a roaming device, which has the functions of implementing the above-mentioned first aspect and the optional manners of the first aspect. The device includes at least one module, and at least one module is used to implement the method provided by the above-mentioned eleventh aspect and the optional manners of the eleventh aspect. In a possible design, it is applied to a sub-optical network unit (SFU), and includes:

[0091] A receiving module, configured to receive a roaming start indication message from a master optical network unit (MFU), where the roaming start indication message is used to indicate to start roaming processing for the site; the SFU is the source SFU to which the site currently accesses or the target SFU determined by the MFU for roaming of the site;

[0092] A processing module, configured to start roaming processing for the site.

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

[0094] In a possible design, the starting of the roaming processing includes starting a roaming handover state machine.

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

[0096] In a possible design, the device further includes:

[0097] The SFU sends the roaming start confirmation message to the MFU, and the roaming start confirmation message indicates that the SFU has successfully completed the roaming start for the site.

[0098] In a possible design, the device further includes:

[0099] The SFU sends a roaming start failure message to the MFU, and the roaming start failure message indicates that the roaming start of the SFU for the site fails.

[0100] In a possible design, the device further includes:

[0101] The SFU receives a roaming exception handling message from the MFU, and the roaming exception handling message is used to indicate clearing the roaming-related information for the site;

[0102] The SFU clears the roaming-related information for the site.

[0103] In a possible design, the device further includes:

[0104] The SFU sends a roaming exception handling completion message to the MFU.

[0105] In a possible design, the device further includes:

[0106] The SFU sends roaming decision information to the MFU.

[0107] In a possible design, the roaming decision information includes one or more of the signal strength, load information, or channel condition information between the SFU and the site.

[0108] In a fifth aspect, the present application provides a roaming device, which includes a processor, a memory, and a communication interface; the processor is configured to execute program instructions in the memory to implement the method provided in any of the above aspects, and the communication interface is configured to communicate with the SFU.

[0109] In a sixth aspect, the present application provides a roaming device, which includes a processor, a memory, and a communication interface; the processor is configured to execute program instructions in the memory to implement the method provided in the second aspect and the optional manners of the second aspect, and the communication interface is configured to communicate with the MFU.

[0110] In a seventh aspect, the present application provides a computer-readable storage medium, in which at least one program instruction is stored, and the program instruction is read by a processor to enable the processor (in the MFU) to execute the method provided in any aspect.

[0111] In an eighth aspect, the present application provides a computer-readable storage medium, in which at least one program instruction is stored, and the program instruction is read by a processor to enable the processor (in the SFU) to execute the method provided in the second aspect or any optional manner of the second aspect.

[0112] In a ninth aspect, the present application provides a computer program product, which includes 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 the processor executes the program instructions, so that the MFU executes the method provided in the first aspect or any optional manner of the first aspect.

[0113] In a tenth aspect, the present application provides a computer program product, which includes program instructions stored in a computer-readable storage medium. A processor of the SFU reads the program instructions from the computer-readable storage medium, and the processor executes the program instructions, so that the SFU executes the method provided in the second aspect or any optional manner of the second aspect.

[0114] In an eleventh aspect, an embodiment of the present application provides a communication system, including a source SFU, a target SFU, and an MFU. The MFU is configured to execute the method described in the first aspect or any design of the first aspect. The source SFU or the target SFU is configured to execute the method described in the second aspect or any design of the second aspect.

[0115] In a twelfth aspect, an embodiment of the present application provides a roaming method, including:

[0116] The master optical network unit MFU sends a roaming preprocessing message to the target SFU, and the roaming preprocessing message is used to instruct the target SFU to initiate roaming preparation for the site;

[0117] The MFU receives a roaming preprocessing feedback message from the target SFU, and the roaming preprocessing feedback message is used to indicate whether the roaming preparation for the site is successful.

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

[0119] In a possible design, the roaming preprocessing message includes an identifier of the site.

[0120] In a possible design, the roaming preprocessing message includes aggregation parameters, and the aggregation parameters are used for the target SFU to establish aggregation with the site.

[0121] In a possible design, the roaming preprocessing message includes aggregation parameters and association parameters. The aggregation parameters are used for the target SFU to establish aggregation with the site, and the association parameters are used for the target SFU to establish an association with the site.

[0122] In a possible design, the association parameters include: an association request frame of the site and / or a secret key negotiated by the site and the source SFU for communication.

[0123] In a possible design, the aggregation parameters include: the size of an aggregation window and / or an aggregation policy.

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

[0125] In a possible design, the roaming preprocessing feedback message indicates that the roaming preparation of the target SFU for the site fails;

[0126] The method further includes:

[0127] The MFU clears the roaming-related information for the site.

[0128] In a possible design, the roaming preprocessing feedback message indicates that the roaming preparation of the target SFU for the site fails;

[0129] The method further includes:

[0130] The MFU sends a roaming exception handling message to the target SFU, and the roaming exception handling message is used to indicate clearing the roaming-related information for the site.

[0131] In a possible design, the method further includes: the MFU receives the roaming exception handling completion message from the target SFU.

[0132] In a possible design, the method further includes:

[0133] The MFU sends the roaming exception handling message to the source SFU, and the source SFU is the SFU to which the site is currently connected.

[0134] In a possible design, the method further includes:

[0135] The MFU receives the roaming exception handling completion message from the source SFU.

[0136] In a thirteenth aspect, an embodiment of the present application provides a roaming method, including:

[0137] The target Subscriber Function Unit (SFU) receives a roaming preprocessing message from the Master Function Unit (MFU), and the roaming preprocessing message is used to indicate that the target SFU starts roaming preparation for the site;

[0138] The target SFU sends a roaming preprocessing feedback message to the MFU, and the roaming preprocessing feedback message is used to indicate whether the roaming preparation for the site is successful.

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

[0140] In a possible design, the roaming preprocessing message includes the identifier of the site.

[0141] In a possible design, the roaming preprocessing message includes aggregation parameters for establishing aggregation between the target SFU and the site.

[0142] In a possible design, the roaming preprocessing message includes aggregation parameters and association parameters, where the aggregation parameters are used for the target SFU to establish aggregation with the site, and the association parameters are used for the target SFU to establish an association with the site.

[0143] In a possible design, the association parameters include: the association request frame of the site and / or the secret key negotiated between the site and the source SFU for communication.

[0144] In a possible design, the aggregation parameters include: the size of the aggregation window and / or the aggregation policy.

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

[0146] In a possible design, the roaming preprocessing feedback message indicates that the roaming preparation of the target SFU for the site has failed;

[0147] The method further includes:

[0148] Receiving a roaming exception handling message from the MFU, where the roaming exception handling message is used to indicate clearing the roaming-related information for the site;

[0149] Clearing the roaming-related information for the site.

[0150] In a possible design, the method further includes:

[0151] Sending a roaming exception handling completion message to the MFU.

[0152] In a fourteenth aspect, an embodiment of the present application provides a roaming method, including:

[0153] When the source sub-optical network unit (SFU) has initiated roaming processing for the site, receiving a roaming exception handling message from the master optical network unit (MFU), where the roaming exception handling message is used to indicate clearing the roaming-related information for the site, and the source SFU is the SFU currently accessed by the site;

[0154] Clearing the roaming-related information for the site.

[0155] In a possible design, the method further includes:

[0156] The source SFU sending a roaming exception handling completion message to the MFU.

[0157] In a fifteenth aspect, an embodiment of the present application provides a roaming device, which has the functions of implementing the above-mentioned twelfth aspect and the optional manners of the twelfth aspect. The device includes at least one module, and the at least one module is used to implement the methods provided by the above-mentioned twelfth aspect and the optional manners of the twelfth aspect. In a possible design, it includes: applied to the master optical network unit MFU, including:

[0158] A sending module, configured to send a roaming preprocessing message to a target SFU, where the roaming preprocessing message is used to instruct the target SFU to initiate roaming preparation for the site;

[0159] A receiving module, configured to receive a roaming preprocessing feedback message from the target SFU, where the roaming preprocessing feedback message is used to indicate whether the roaming preparation for the site is successful.

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

[0161] In a possible design, the roaming preprocessing message includes an identifier of the site.

[0162] In a possible design, the roaming preprocessing message includes aggregation parameters, and the aggregation parameters are used for the target SFU to establish aggregation with the site.

[0163] In a possible design, the roaming preprocessing message includes aggregation parameters and association parameters, the aggregation parameters are used for the target SFU to establish aggregation with the site, and the association parameters are used for the target SFU to establish an association with the site.

[0164] In a possible design, the association parameters include: an association request frame of the site and / or a secret key negotiated by the site and the source SFU for communication.

[0165] In a possible design, the aggregation parameters include: the size of an aggregation window and / or an aggregation policy.

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

[0167] In a possible design, the roaming preprocessing feedback message indicates that the roaming preparation of the target SFU for the site fails;

[0168] The device further includes:

[0169] A processing module, configured to clear the roaming-related information for the site.

[0170] In a possible design, the roaming preprocessing feedback message indicates that the roaming preparation of the target SFU for the site fails;

[0171] The sending module is configured to send a roaming exception handling message to the target SFU, where the roaming exception handling message is used to indicate clearing the roaming-related information for the site.

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

[0173] In a 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 to which the site is currently connected.

[0174] In a possible design, the receiving module is further configured to:

[0175] Receive the roaming exception handling completion message from the source SFU.

[0176] In a sixteenth aspect, an embodiment of the present application provides a roaming device, which has the functions of implementing the above-mentioned thirteenth aspect and the optional manners of the thirteenth aspect. The device includes at least one module, and the at least one module is configured to implement the method provided by the above-mentioned thirteenth aspect and the optional manners of the thirteenth aspect.

[0177] In a possible design, applied to a target Subscriber Frame Unit (SFU), it includes:

[0178] A receiving module, configured to receive a roaming preprocessing message from a Master Frame Unit (MFU), where the roaming preprocessing message is used to indicate that the target SFU starts roaming preparation for the site;

[0179] A sending module, configured to send a roaming preprocessing feedback message to the MFU, where the roaming preprocessing feedback message is used to indicate whether the roaming preparation for the site is successful.

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

[0181] In a possible design, the roaming preprocessing message includes the identifier of the site.

[0182] In a possible design, the roaming preprocessing message includes aggregation parameters, and the aggregation parameters are used for the target SFU to establish aggregation with the site.

[0183] In a possible design, the roaming preprocessing message includes an aggregation parameter and an association parameter. The aggregation parameter is used for the target SFU to establish aggregation with the site, and the association parameter is used for the target SFU to establish an association with the site.

[0184] In a possible design, the association parameter includes: the association request frame of the site and / or the secret key negotiated between the site and the source SFU for communication.

[0185] In a possible design, the aggregation parameter includes: the size of the aggregation window and / or the aggregation policy.

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

[0187] In a possible design, the roaming preprocessing feedback message indicates that the roaming preparation of the target SFU for the site fails;

[0188] The receiving module is further configured to receive a roaming exception handling message from the MFU, where the roaming exception handling message is used to indicate clearing the roaming-related information for the site;

[0189] It further includes:

[0190] The processing module is configured to clear the roaming-related information for the site.

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

[0192] In a seventeenth aspect, an embodiment of the present application provides a roaming device, and the device has the functions of implementing the above-mentioned first aspect and the optional manners of the first aspect. The device includes at least one module, and at least one module is used to implement the method provided by the above-mentioned first aspect and the optional manners of the first aspect.

[0193] In a possible design, it includes a receiving module, configured to receive a roaming exception handling message from a master optical network unit (MFU) when a source sub-optical network unit (SFU) has initiated roaming processing for the site, where the roaming exception handling message is used to indicate clearing the roaming-related information for the site, and the source SFU is the SFU currently accessed by the site;

[0194] The processing module is configured to clear the roaming-related information for the site.

[0195] In a possible design, the device further includes:

[0196] The sending module is configured to send a roaming exception handling completion message to the MFU.

[0197] In the eighteenth aspect, the present application provides a roaming device, which includes 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 above twelfth aspect and the optional manners of the twelfth aspect, and the communication interface is configured to communicate with the SFU.

[0198] In the nineteenth aspect, the present application provides a roaming device, which includes 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 above thirteenth aspect and the optional manners of the thirteenth aspect or to implement the methods provided in the above fourteenth aspect and the optional manners of the fourteenth aspect, and the communication interface is configured to communicate with the MFU.

[0199] In the twentieth aspect, the present application provides a computer-readable storage medium, in which at least one program instruction is stored, and the program instruction is read by a processor to enable the processor (in the MFU) to execute the method provided in the above twelfth aspect or any optional manner of the twelfth aspect; or, the program instruction is read by a processor to enable the processor (in the SFU) to execute the methods provided in the above thirteenth aspect and the optional manners of the thirteenth aspect or to execute the methods provided in the above fourteenth aspect and the optional manners of the fourteenth aspect.

[0200] In the twenty-first aspect, the present application provides a computer program product, which includes 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 the processor executes the program instructions, so that the MFU executes the method provided in the above twelfth aspect or any optional manner of the twelfth aspect.

[0201] In the twenty-second aspect, the present application provides a computer program product, which includes 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 the processor executes the program instructions, so that the SFU executes the methods provided in the above thirteenth aspect and the optional manners of the thirteenth aspect or to execute the methods provided in the above fourteenth aspect and the optional manners of the fourteenth aspect.

[0202] In the twenty-third aspect, an embodiment of the present application provides a communication system, which includes a source SFU, a target SFU, and an MFU. The MFU is configured to execute the method described in the twelfth aspect or any design of the twelfth aspect. The target SFU is configured to execute the method described in the thirteenth aspect or any design of the thirteenth aspect. The source SFU is configured to execute the method described in the fourteenth aspect or any design of the fourteenth aspect.

[0203] In a twenty-fourth aspect, an embodiment of the present application provides a roaming method, including:

[0204] During the roaming process of a station, a master optical network unit (MFU) sends a service shutdown indication message to a source SFU, and the service shutdown message is used to instruct the source SFU to shut down service interaction with the station;

[0205] The MFU receives a service shutdown feedback message from the source SFU, and the service shutdown feedback message is used to indicate whether the service interaction with the station is successfully shut down.

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

[0207] In a possible design, the service shutdown indication message includes an identifier of the station.

[0208] In a possible design, the service shutdown indication message is further used to instruct the source SFU to report context information of service interaction with the station.

[0209] In a possible design, the service shutdown feedback message indicates that the source SFU has successfully shut down service interaction with the station.

[0210] In a possible design, the service shutdown feedback message includes context information of service interaction between the source SFU and the station.

[0211] In a possible design, the context information includes one or more of a unicast packet sequence number (PN number), a sequence number (SN) context, a message sequence number, or station OMI status information.

[0212] In a possible design, the context information further includes an energy-saving mode of the source SFU.

[0213] In a possible design, the station OMI status information includes one or more of the number of received spatial streams, channel bandwidth, shutting down uplink multi-user transmission, the number of transmitted space-time streams, shutting down extended-distance single-user transmission, recommending re-performing downlink multi-user multiple-input multiple-output transmission channel detection, and shutting down uplink data multi-user transmission.

[0214] In a possible design, the service shutdown feedback message indicates that the source SFU fails to shut down service interaction with the station;

[0215] The method further includes:

[0216] The MFU sends a first roaming exception handling message to the source SFU, where the first roaming exception handling message is used to indicate restoring the configuration before the start of roaming for the site.

[0217] In a possible design, the method further includes:

[0218] The MFU sends the second roaming exception handling message to the target SFU, where the second roaming exception handling message is used to indicate deleting the roaming-related information of the site, and the target SFU is the target SFU determined for the roaming handover of the site.

[0219] In a possible design, the service shutdown feedback message indicates that the source SFU fails to close the service interaction with the site;

[0220] The method further includes:

[0221] The MFU sends a third roaming exception handling message to the source SFU, where the third roaming exception handling message is used to indicate removing the site from the network.

[0222] In a possible design, the method further includes:

[0223] The MFU sends the third roaming exception handling message to the target SFU, where the target SFU is the target SFU determined for the roaming handover of the site.

[0224] In a twenty-fifth aspect, an embodiment of the present application provides a roaming method, including:

[0225] During the roaming of a site, a source sub-optical network unit (SFU) receives a service shutdown indication message from a master optical network unit (MFU), where the service shutdown message is used to indicate that the source SFU closes the service interaction with the site;

[0226] The source SFU sends a service shutdown feedback message to the MFU, where the service shutdown feedback message is used to indicate whether the source SFU successfully closes the service interaction with the site.

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

[0228] In a possible design, the service shutdown indication message includes the identifier of the site.

[0229] In a possible design, the service shutdown indication message is further used to indicate that the source SFU reports the context information of the service interaction with the site.

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

[0231] In a possible design, the service shutdown feedback message includes the context information of the service interaction between the source SFU and the site.

[0232] In a possible design, the context information includes one or more of the unicast packet sequence number PN number, sequence number SN context, message sequence number, or site operation mode indication OMI status information.

[0233] In a possible design, the context information further includes the power-saving mode of the source SFU.

[0234] In a possible design, the site OMI status information includes one or more of the number of received spatial streams, channel bandwidth, shutdown of uplink multi-user transmission, number of transmitted space-time streams, shutdown of extended-range single-user transmission, recommendation to re-perform downlink multi-user multiple-input multiple-output transmission channel detection, and shutdown of uplink data multi-user transmission.

[0235] In a possible design, the service shutdown feedback message indicates that the source SFU fails to shut down the service interaction with the site;

[0236] The method further includes:

[0237] The source SFU receives a first roaming exception handling message from the MFU, and the first roaming exception handling message is used to instruct the source SFU to restore the configuration before the start of roaming for the site;

[0238] The source SFU restores the configuration before the start of roaming for the site.

[0239] In a possible design, the service shutdown feedback message indicates that the source SFU fails to shut down the service interaction with the site;

[0240] The method further includes:

[0241] The source SFU receives a third roaming exception handling message from the MFU, and the third roaming exception handling message is used to instruct the source SFU to remove the site from the network;

[0242] The source SFU removes the site from the network.

[0243] In a possible design, the method further includes:

[0244] The source SFU sends a roaming exception handling completion message to the MFU.

[0245] In a possible design, the method further includes:

[0246] The source SFU or MFU may also delete the aggregation sessions established locally with the STA.

[0247] In a twenty-sixth aspect, an embodiment of the present application provides a roaming method, including:

[0248] When the target Subscriber Function Unit (SFU) has initiated the roaming process for the site, receiving a second roaming exception handling message from the Master Function Unit (MFU), where the second roaming exception handling message is used to indicate clearing the roaming-related information for the site, and the source SFU is the SFU to which the site is currently connected;

[0249] Clearing the roaming-related information for the site or removing the site from the network.

[0250] In a possible design, the method further includes:

[0251] The target SFU sends a roaming exception handling completion message to the MFU.

[0252] In a twenty-seventh aspect, an embodiment of the present application provides a roaming device, which has the functions of implementing the above twenty-fourth aspect and the optional manners of the twenty-fourth aspect. The device includes at least one module, and at least one module is used to implement the method provided by the above twenty-fourth aspect and the optional manners of the twenty-fourth aspect. In a possible design, it includes: a sending module, configured to send a service shutdown indication message to the source SFU during the roaming process of the site, where the service shutdown message is used to indicate that the source SFU shuts down the service interaction with the site;

[0253] A receiving module, configured to receive a service shutdown feedback message from the source SFU, where the service shutdown feedback message is used to indicate whether the service interaction with the site has been successfully shut down.

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

[0255] In a possible design, the service shutdown indication message includes the identifier of the site.

[0256] In a possible design, the service shutdown indication message is further used to indicate that the source SFU reports the context information of the service interaction with the site.

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

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

[0259] In a possible design, the context information includes one or more of the unicast packet sequence number PN number, the sequence number SN context, the message sequence number, or the site operation mode indication OMI status information.

[0260] In a possible design, the context information further includes the power-saving mode of the source SFU.

[0261] In a possible design, the site OMI status information includes one or more of the number of received spatial streams, the channel bandwidth, shutting down uplink multi-user transmission, the number of transmitted space-time streams, shutting down extended-range single-user transmission, recommending re-performing downlink multi-user multiple-input multiple-output transmission channel detection, and shutting down uplink data multi-user transmission.

[0262] In a possible design, the service shutdown feedback message indicates that the source SFU fails to shut down the service interaction with the site;

[0263] The sending module is further configured to send a first roaming exception handling message to the source SFU, where the first roaming exception handling message is used to indicate restoring the configuration before the start of roaming for the site.

[0264] In a possible design, the sending module is further configured to send the second roaming exception handling message to the target SFU, where the second roaming exception handling message is used to indicate deleting the roaming-related information of the site, and the target SFU is the target SFU determined for the site roaming handover.

[0265] In a possible design, the service shutdown feedback message indicates that the source SFU fails to shut down the service interaction with the site;

[0266] The sending module is further configured to send a third roaming exception handling message to the source SFU, where the third roaming exception handling message is used to indicate removing the site from the network.

[0267] In a possible design, the sending module is further configured to send the third roaming exception handling message to the target SFU, where the target SFU is the target SFU determined for the site roaming handover.

[0268] In the twenty-eighth aspect, an embodiment of the present application provides a roaming device, which has the functions of implementing the above-mentioned twenty-fifth aspect and the optional manners of the twenty-fifth aspect. The device includes at least one module, and the at least one module is used to implement the methods provided by the above-mentioned twenty-fifth aspect and the optional manners of the twenty-fifth aspect. In a possible design, it is applied to a source sub-optical network unit (SFU) and includes:

[0269] A receiving module, configured to receive a service shutdown indication message from a master optical network unit (MFU) during the roaming process of a site, where the service shutdown message is used to instruct the source SFU to shut down service interaction with the site;

[0270] A sending module, configured to send a service shutdown feedback message to the MFU, where the service shutdown feedback message is used to indicate whether the source SFU has successfully shut down service interaction with the site.

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

[0272] In a possible design, the service shutdown indication message includes an identifier of the site.

[0273] In a possible design, the service shutdown indication message is further used to instruct the source SFU to report context information of service interaction with the site.

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

[0275] In a possible design, the service shutdown feedback message includes context information of service interaction between the source SFU and the site.

[0276] In a possible design, the context information includes one or more of a unicast packet sequence number (PN number), a sequence number (SN) context, a message sequence number, or a site operation mode indication (OMI) status information.

[0277] In a possible design, the context information further includes an energy-saving mode of the source SFU.

[0278] In a possible design, the site OMI status information includes one or more of the number of received spatial streams, channel bandwidth, disabling uplink multi-user transmission, the number of transmitted space-time streams, disabling extended-range single-user transmission, recommending re-performing downlink multi-user multiple-input multiple-output transmission channel detection, and disabling uplink data multi-user transmission.

[0279] In a possible design, the service shutdown feedback message indicates that the source SFU fails to close the service interaction with the site;

[0280] The receiving module is further configured to receive a first roaming exception handling message from the MFU, where the first roaming exception handling message is used to instruct the source SFU to restore the configuration before the roaming of the site is started;

[0281] It further includes:

[0282] The processing module is configured to restore the configuration before the roaming of the site is started.

[0283] In a possible design, the service shutdown feedback message indicates that the source SFU fails to close the service interaction with the site;

[0284] The receiving module is further configured to receive a third roaming exception handling message from the MFU, where the third roaming exception handling message is used to instruct the source SFU to remove the site from the network;

[0285] It further includes:

[0286] The processing module is configured to remove the site from the network.

[0287] In a possible design, the sending module is further configured to send a roaming exception handling completion message to the MFU.

[0288] In a twenty-ninth aspect, an embodiment of the present application provides a roaming device, and the device has the functions of implementing the above twenty-sixth aspect and the optional manners of the twenty-sixth aspect. The device includes at least one module, and at least one module is used to implement the methods provided by the above twenty-sixth aspect and the optional manners of the twenty-sixth aspect.

[0289] In a possible design, it is applied to a target sub-optical network unit SFU and includes:

[0290] The receiving module is configured to receive a second roaming exception handling message from the main optical network unit MFU when the target sub-optical network unit SFU has started the roaming process for the site, where the second roaming exception handling message is used to instruct to clear the roaming-related information for the site, and the source SFU is the SFU currently accessed by the site;

[0291] The processing module is configured to clear the roaming-related information for the site.

[0292] In a possible design, the device further includes:

[0293] The sending module is configured to send a roaming exception handling completion message to the MFU.

[0294] In the thirtieth aspect, the present application provides a roaming device, which includes a processor, a memory, and a communication interface; the processor is configured to execute program instructions in the memory to implement the method provided in the above-mentioned twenty-fourth aspect and the optional manners of the twenty-fourth aspect, and the communication interface is configured to communicate with the SFU.

[0295] In the thirty-first aspect, the present application provides a roaming device, which includes a processor, a memory, and a communication interface; the processor is configured to execute program instructions in the memory to implement the method provided in the above-mentioned twenty-fifth aspect and the optional manners of the twenty-fifth aspect or to implement the method provided in the above-mentioned fourteenth aspect and the optional manners of the fourteenth aspect, and the communication interface is configured to communicate with the MFU.

[0296] In the thirty-second aspect, the present application provides a computer-readable storage medium, in which at least one program instruction is stored, and the program instruction is read by a processor to enable the processor (in the MFU) to execute the method provided in the above-mentioned twenty-fourth aspect or any one of the optional manners of the twenty-fourth aspect.

[0297] In the thirty-third aspect, the present application provides a computer-readable storage medium, in which at least one program instruction is stored, and the program instruction is read by a processor to enable the processor (in the SFU) to execute the method provided in the above-mentioned twenty-fifth aspect and the optional manners of the twenty-fifth aspect or to execute the method provided in the above-mentioned twenty-sixth aspect and the optional manners of the twenty-sixth aspect.

[0298] In the thirty-fourth aspect, the present application provides a computer program product, which includes 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 the processor executes the program instructions, so that the MFU executes the method provided in the above-mentioned twenty-fourth aspect or any one of the optional manners of the twenty-fourth aspect.

[0299] In the thirty-fifth aspect, the present application provides a computer program product, which includes 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 the processor executes the program instructions, so that the SFU executes the method provided in the above-mentioned twenty-fifth aspect and the optional manners of the twenty-fifth aspect or to execute the method provided in the above-mentioned twenty-sixth aspect and the optional manners of the twenty-sixth aspect.

[0300] In a thirty-sixth aspect, an embodiment of the present application provides a communication system, including a source SFU, a target SFU, and an MFU. The MFU is configured to execute the method described in the twenty-fourth aspect or any design of the twenty-fourth aspect. The source SFU is configured to execute the method described in the twenty-fifth aspect or any design of the twenty-fifth aspect. The target SFU is configured to execute the method described in the twenty-sixth aspect or any design of the twenty-sixth aspect.

[0301] In a thirty-seventh aspect, an embodiment of the present application provides a roaming method, including:

[0302] During the roaming process of a station, the master optical network unit MFU sends a service start indication message to the target SFU, and the service start indication message is used to instruct the target SFU to start service interaction with the station;

[0303] The MFU receives a service start feedback message from the target SFU, and the service start feedback message is used to indicate whether the service interaction with the station is successfully started.

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

[0305] In a possible design, the service start indication message includes an identifier of the station.

[0306] In a possible design, the service start indication message includes context information of the service interaction between the source SFU and the station.

[0307] In a possible design, the context information includes one or more of a unicast packet sequence number PN, a sequence number SN context, a message sequence number, or a station operation mode indication OMI status information.

[0308] In a possible design, the context information further includes an energy-saving mode of the source SFU.

[0309] In a possible design, the station OMI status information includes one or more of the number of received spatial streams, channel bandwidth, disabling uplink multi-user transmission, the number of transmitted space-time streams, disabling extended range single-user transmission, recommending re-performing downlink multi-user multiple-input multiple-output transmission channel detection, and disabling uplink data multi-user transmission.

[0310] In a possible design, the service start feedback message indicates that the target SFU has successfully started service interaction with the station.

[0311] In a possible design, the service start feedback message indicates that the target SFU fails to start service interaction with the station;

[0312] The method further includes:

[0313] The MFU sends a first roaming exception handling message to the target SFU, where the first roaming exception handling message is used to indicate restoring the configuration before the start of site roaming.

[0314] In a possible design, the method further includes:

[0315] The MFU receives a roaming exception handling completion message sent by the target SFU.

[0316] In a possible design, the method further includes:

[0317] The MFU sends the first roaming exception handling message to the source SFU.

[0318] In a possible design, the method further includes:

[0319] The MFU receives a roaming exception handling completion message sent by the source SFU.

[0320] In a possible design, the method further includes:

[0321] The MFU clears the roaming-related information of the site.

[0322] In a possible design, the service start feedback message indicates that the target SFU fails to start service interaction with the site;

[0323] The method further includes:

[0324] The MFU sends a third roaming exception handling message to the target SFU, where the third roaming exception handling message is used to indicate removing the site from the network.

[0325] In a possible design, the method further includes:

[0326] The MFU sends the third roaming exception handling message to the source SFU, where the source SFU is the target SFU determined for the site roaming handover.

[0327] In a thirty-eighth aspect, an embodiment of the present application provides a roaming method, including:

[0328] During the roaming of a site, a target Subscriber Optical Network Unit (SFU) receives a service start indication message from a Master Optical Network Unit (MFU), where the service start indication message is used to indicate that the target SFU starts service interaction with the site;

[0329] The target SFU sends a service start feedback message to the MFU, and the service start feedback message is used to indicate whether the source SFU has successfully started service interaction with the site.

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

[0331] In a possible design, the service start indication message includes the identifier of the site.

[0332] In a possible design, the service start indication message includes the context information of the service interaction between the source SFU and the site.

[0333] In a possible design, the context information includes one or more of a unicast packet sequence number PN number, a sequence number SN context, a message sequence number, or a site operation mode indication OMI status information.

[0334] In a possible design, the site OMI status information includes one or more of the number of received spatial streams, the channel bandwidth, disabling uplink multi-user transmission, the number of transmitted space-time streams, disabling extended range single-user transmission, recommending re-performing downlink multi-user multiple-input multiple-output transmission channel detection, and disabling uplink data multi-user transmission.

[0335] In a possible design, the context information includes the site OMI status information; the method further includes:

[0336] The target SFU performs service interaction with the site according to the transceiver parameters indicated by the site OMI status information.

[0337] In a possible design, the context information further includes the power saving mode of the source SFU.

[0338] In a possible design, the context information includes the site OMI status information, and the method further includes:

[0339] When the target SFU determines that the source SFU enters the power saving mode according to the power saving mode of the SFU, it performs service interaction with the site according to the transceiver parameters indicated by the site OMI status information;

[0340] When the target SFU determines that the source SFU enters the power saving mode according to the power saving mode of the SFU, it negotiates an operation mode OM with the site.

[0341] In a possible design, the context information includes the site OMI status information, and the method further includes:

[0342] When the target SFU determines that the energy-saving mode of the source SFU supports the current traffic volume of the target SFU, it conducts service interaction with the site according to the transceiver parameters indicated by the site OMI status information; or,

[0343] When the target SFU determines that the energy-saving mode of the source SFU does not support the current traffic volume of the target SFU, it negotiates the operation mode OMI with the site.

[0344] In a possible design, the method further includes:

[0345] Sending a downlink message to the STA according to the message sequence number, or,

[0346] Sending an aggregated message to the STA according to the SN context, or,

[0347] Determining the channel bandwidth and the number of streams according to the site OMI status information. Through synchronizing the OMI status in the target SFU in this design, the energy-saving state of the site can be synchronized to the SFU after roaming, maintaining the consistency of the energy-saving state of the STA and improving the roaming effect.

[0348] In a possible design, the service start feedback message indicates that the target SFU has successfully started service interaction with the site.

[0349] In a possible design, after receiving the service start indication message, the target SFU establishes an aggregation session with the STA according to the service traffic.

[0350] In a possible design, the method further includes:

[0351] The target SFU sends a downlink service message to the site.

[0352] In a possible design, the service stop feedback message indicates that the target SFU fails to start service interaction with the site;

[0353] The method further includes:

[0354] The target SFU receives a first roaming exception handling message from the MFU, and the first roaming exception handling message is used to indicate restoring the configuration before the start of roaming for the site;

[0355] The target SFU restores the configuration before the start of roaming for the site.

[0356] In a possible design, the method further includes:

[0357] The target SFU sends a roaming exception handling completion message to the MFU.

[0358] In a possible design, the service start feedback message indicates that the target SFU fails to start service interaction with the site;

[0359] The method further includes:

[0360] The target SFU receives a third roaming exception handling message from the MFU, and the third roaming exception handling message is used to instruct the target SFU to remove the site from the network;

[0361] The target SFU removes the site from the network.

[0362] In a thirty-ninth aspect, an embodiment of the present application provides a roaming method, including:

[0363] When the source Subscriber Frontend Unit (SFU) has started the roaming process for a site, receiving a first roaming exception handling message from the Master Frontend Unit (MFU), where the first roaming exception handling message is used to instruct to restore the configuration before the start of the roaming for the site, and the target SFU is the target SFU for the roaming handover of the site;

[0364] Restore the configuration before the start of the roaming for the site and remove the site from the network.

[0365] In a possible design, the method further includes:

[0366] The source SFU sends a roaming exception handling completion message to the MFU.

[0367] In a fortieth aspect, an embodiment of the present application provides a roaming device, and the device has the functions of implementing the above thirty-seventh aspect and the optional manners of the thirty-seventh aspect. The device includes at least one module, and at least one module is used to implement the methods provided by the above thirty-seventh aspect and the optional manners of the thirty-seventh aspect. In a possible design, when applied to the Master Frontend Unit (MFU), it includes:

[0368] A sending module, configured to send a service start indication message to a target SFU during the roaming process of a site, where the service start indication message is used to instruct the target SFU to start service interaction with the site;

[0369] A receiving module, configured to receive a service start feedback message from the target SFU, where the service start feedback message is used to indicate whether the service interaction with the site is successfully started.

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

[0371] In a possible design, the service start indication message includes the identifier of the site.

[0372] In a possible design, the service start indication message includes the context information of the service interaction between the source SFU and the site.

[0373] In a possible design, the context information includes one or more of the unicast packet sequence number PN, the sequence number SN context, the message sequence number, or the site operation mode indication OMI status information.

[0374] In a possible design, the site OMI status information includes one or more of the number of received spatial streams, the channel bandwidth, the closing of uplink multi-user transmission, the number of transmitted space-time streams, the closing of extended range single-user transmission, the recommendation to re-perform downlink multi-user multiple-input multiple-output transmission channel detection, and the closing of uplink data multi-user transmission.

[0375] In a possible design, the context information further includes the energy-saving mode of the source SFU.

[0376] In a possible design, the service start feedback message indicates that the target SFU has successfully started the service interaction with the site.

[0377] In a possible design, the service start feedback message indicates that the target SFU has failed to start the service interaction with the site;

[0378] The sending module is further configured to send a first roaming exception handling message to the target SFU, where the first roaming exception handling message is used to indicate the restoration of the configuration before the roaming of the site is started.

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

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

[0381] In a possible design, the receiving module is further configured to receive a roaming exception handling completion message sent by the source SFU.

[0382] In a possible design, the device further includes:

[0383] A processing module, configured to clear the roaming-related information of the site.

[0384] In a forty-first aspect, an embodiment of the present application provides a roaming device, which has the functions of implementing the above-mentioned thirty-eighth aspect and the optional manners of the thirty-eighth aspect. The device includes at least one module, and the at least one module is used to implement the methods provided by the above-mentioned thirty-eighth aspect and the optional manners of the thirty-eighth aspect. In a possible design, it is applied to a target sub-optical network unit (SFU), and includes:

[0385] a receiving module, configured to receive a service activation indication message from a master optical network unit (MFU) during the roaming process of a station, where the service activation indication message is used to instruct the target SFU to activate service interaction with the station;

[0386] a sending module, configured to send a service activation feedback message to the MFU, where the service activation feedback message is used to indicate whether the source SFU has successfully activated service interaction with the station.

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

[0388] In a possible design, the service activation indication message includes an identifier of the station.

[0389] In a possible design, the service activation indication message includes context information of service interaction between the source SFU and the station.

[0390] In a possible design, the context information includes one or more of a unicast packet sequence number (PN number), a sequence number (SN) context, a message sequence number, or a station operation mode indication (OMI) status information.

[0391] In a possible design, the station OMI status information includes one or more of the number of received spatial streams, channel bandwidth, disabling uplink multi-user transmission, the number of transmitted space-time streams, disabling extended range single-user transmission, recommending re-performing downlink multi-user multiple-input multiple-output transmission channel detection, and disabling uplink data multi-user transmission.

[0392] In a possible design, the context information includes the station OMI status information; a communication module, configured to perform service interaction with the station according to the transceiver parameters indicated by the station OMI status information, and the communication module includes the receiving module and the sending module.

[0393] Specifically, the sending module is further configured to send data to the station according to the sending parameters indicated by the station OMI status information. The receiving module is further configured to receive data from the station according to the receiving parameters indicated by the station OMI status information.

[0394] In a possible design, the context information further includes the energy-saving mode of the source SFU.

[0395] In a possible design, the context information includes the site OMI status information. When the communication module determines that the source SFU enters the energy-saving mode according to the energy-saving mode of the SFU, it performs service interaction with the site according to the transceiver parameters indicated by the site OMI status information; or,

[0396] When it is determined that the source SFU enters the energy-saving mode according to the energy-saving mode of the SFU, it negotiates the operation mode OM with the site.

[0397] In a possible design, the context information includes the site OMI status information. When the communication module determines that the energy-saving mode of the source SFU supports the current traffic volume of the target SFU, it performs service interaction with the site according to the transceiver parameters indicated by the site OMI status information; or,

[0398] When it is determined that the energy-saving mode of the source SFU does not support the current traffic volume of the target SFU, it negotiates the operation mode OM with the site.

[0399] In a possible design, the sending module is configured to:

[0400] Send a downlink packet to the STA according to the packet sequence number, or,

[0401] Send an aggregated packet to the STA according to the SN context, or,

[0402] Determine the channel bandwidth and the number of streams according to the site OMI status information. In this design, by synchronizing the OMI status at the target SFU, the energy-saving state of the site can be synchronized to the SFU after roaming, maintaining the consistency of the energy-saving state of the STA and improving the roaming effect.

[0403] In a possible design, the service start feedback message indicates that the target SFU has successfully started service interaction with the site.

[0404] In a possible design, the sending module is further configured to send a downlink service packet to the site.

[0405] In a possible design, the service stop feedback message indicates that the target SFU fails to start service interaction with the site;

[0406] The receiving module is further configured to receive a first roaming exception handling message from the MFU, and the first roaming exception handling message is used to indicate restoring the configuration before the roaming of the site is started;

[0407] Further included are:

[0408] A processing module, configured to restore the configuration before the start of the site roaming.

[0409] In a possible design, the sending module is further configured to send a roaming exception handling completion message to the MFU.

[0410] In a forty-second aspect, an embodiment of the present application provides a roaming device, which has the functions of implementing the above-mentioned thirty-ninth aspect and the optional manners of the thirty-ninth aspect. The device includes at least one module, and at least one module is used to implement the methods provided by the above-mentioned thirty-ninth aspect and the optional manners of the thirty-ninth aspect.

[0411] In a possible design, when applied to a source sub-optical network unit (SFU), it includes:

[0412] A receiving module, configured to receive a first roaming exception handling message from a master optical network unit (MFU) when the SFU has started the roaming process for a site, where the first roaming exception handling message is used to indicate restoring the configuration before the start of the site roaming;

[0413] A processing module, which restores the configuration before the start of the site roaming.

[0414] In a possible design, the device further includes:

[0415] A sending module, which is further configured to send a roaming exception handling completion message to the MFU.

[0416] In a forty-third aspect, the present application provides a roaming device, which includes 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 above-mentioned thirty-seventh aspect and the optional manners of the thirty-seventh aspect, and the communication interface is used to communicate with the SFU.

[0417] In a forty-fourth aspect, the present application provides a roaming device, which includes 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 above-mentioned thirty-eighth aspect and the optional manners of the thirty-eighth aspect or implement the methods provided by the above-mentioned thirty-ninth aspect and the optional manners of the thirty-ninth aspect, and the communication interface is used to communicate with the MFU.

[0418] In a forty-fifth aspect, the present application provides a computer-readable storage medium storing at least one program instruction, which is read by a processor to cause the processor (in the MFU) to execute the method provided by any of the optional manners of the above-mentioned thirty-seventh aspect or the thirty-seventh aspect.

[0419] In a forty-sixth aspect, the present application provides a computer-readable storage medium storing at least one program instruction, which is read by a processor to cause the processor (in the SFU) to execute the method provided by the above-mentioned thirty-eighth aspect and the optional manner of the thirty-eighth aspect or execute the method provided by the above-mentioned thirty-ninth aspect and the optional manner of the thirty-ninth aspect.

[0420] In a forty-seventh aspect, the present 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 the processor executes the program instructions to cause the MFU to execute the method provided by any of the optional manners of the above-mentioned thirty-seventh aspect or the thirty-seventh aspect.

[0421] In a forty-eighth aspect, the present 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 the processor executes the program instructions to cause the SFU to execute the method provided by the above-mentioned thirty-eighth aspect and the optional manner of the thirty-eighth aspect or execute the method provided by the above-mentioned thirty-ninth aspect and the optional manner of the thirty-ninth aspect.

[0422] In a forty-ninth aspect, an embodiment of the present application provides a communication system including a source SFU, a target SFU, and an MFU. The MFU is configured to execute the method described in any design of the above-mentioned thirty-seventh aspect or the thirty-seventh aspect. The source SFU is configured to execute the method described in any design of the above-mentioned thirty-eighth aspect or the thirty-eighth aspect. The target SFU is configured to execute the method described in any design of the thirty-ninth aspect or the thirty-ninth aspect.

[0423] In some embodiments, the MFU, the source SFU, and the target SFU have the same basic service set identifier BSSID. The MFU, the source SFU, and the target SFU have the same service set identifier SSID.

[0424] Based on the implementations provided in the above aspects, the present application can be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0425] Figure 1ASchematic diagram of an FTTR system architecture provided by an embodiment of the present application;

[0426] Figure 1B Schematic diagram of an FTTR system architecture provided by an embodiment of the present application;

[0427] Figure 1C Schematic flow diagram provided by an embodiment of the present application;

[0428] Figure 2A Schematic flow diagram of a roaming method provided by an embodiment of the present application;

[0429] Figure 2B Another schematic flow diagram of a roaming method provided by an embodiment of the present application;

[0430] Figure 2C Another schematic flow diagram of a roaming method provided by an embodiment of the present application;

[0431] Figure 3A Schematic flow diagram of a roaming method in abnormal state 1 provided by an embodiment of the present application;

[0432] Figure 3B Schematic flow diagram of a roaming method in abnormal state 1 provided by an embodiment of the present application;

[0433] Figure 4A Schematic flow diagram of a roaming method in abnormal state 1 provided by an embodiment of the present application;

[0434] Figure 4B Schematic flow diagram of a roaming method in abnormal state 1 provided by an embodiment of the present application;

[0435] Figure 5 Schematic flow diagram of a roaming method in abnormal state 2 provided by an embodiment of the present application;

[0436] Figure 6 Schematic flow diagram of a roaming method in abnormal state 2 provided by an embodiment of the present application;

[0437] Figure 7 Schematic flow diagram of a roaming method in abnormal state 3 provided by an embodiment of the present application;

[0438] Figure 8 Schematic flow diagram of a roaming method in abnormal state 3 provided by an embodiment of the present application;

[0439] Figure 9 Schematic flow diagram of a roaming method in abnormal state 4 provided by an embodiment of the present application;

[0440] Figure 10 Schematic flow diagram of a roaming method in abnormal state 4 provided by an embodiment of the present application;

[0441] Figure 11 Structural schematic diagram of the roaming device provided by the embodiment of the present application;

[0442] Figure 12 Structural schematic diagram of the device provided by the embodiment of the present application. Detailed implementation manners

[0443] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application.

[0444] Among them, in the description of the present application, unless otherwise specified, "a plurality of" means two or more than two. In addition, " / " means that the objects associated before and after are in an "or" relationship. For example, A / B may represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. These three situations, where A and B may be singular or plural. Also, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the terms "first", "second", etc. do not limit the quantity and execution order, and the terms "first", "second", etc. do not necessarily limit to be different. It should also be noted that unless otherwise specified, the specific descriptions of some technical features in one embodiment can also be applied to explain the corresponding technical features mentioned in other embodiments.

[0445] The importance of seamless Wi-Fi roaming is that it provides users with a continuous and uninterrupted wireless network connection experience, ensuring the stable and reliable network connection in homes, offices, and public places. From the perspective of user experience, Wi-Fi seamless roaming can avoid network interruptions. Wi-Fi seamless roaming technology automatically switches to the best access point by intelligently sensing user movement and signal strength changes, thus avoiding such interruptions and allowing users to enjoy a continuous and stable network connection.

[0446] Embodiments of the present application provide a roaming method for seamless roaming of a station, improving the user experience. The station is any station using a wireless network. For example, the station can be any network - connected terminal such as a mobile phone, a tablet, a computer, or a smart home appliance. The station can also be referred to as a terminal, a user equipment, a user unit, a user station, a mobile station, a mobile device, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device, etc., which is not specifically defined in the present application. The device type of the terminal device 111 can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device, or other processing devices connected to a wireless modem, a vehicle - mounted device, a wearable device, and user equipment in 5G or future networks, etc.

[0447] Embodiments of the present application can be applied to the Fiber To The Room (FTTR) system scenario. The FTTR system includes a master fiber unit (MFU) and a sub fiber unit (SFU). The MFU and the SFU are connected by an optical fiber. The access points include the MFU and the SFU. The MFU and the SFU can be an optical network terminal (ONT) or an optical network unit (ONU). The Chinese name of the MFU can also be the FTTR main device, and the English name is the main FTTR unit. The Chinese name of the SFU can also be the FTTR slave device or the FTTR sub - device, and the English name is the sub FTTR unit. The MFU can also be called the main gateway, and the SFU can also be called the sub - gateway.

[0448] When the FTTR system is deployed and put into operation, the MFU and the SFU are configured to belong to a subnet. The configuration can be manual or automatic. Or rather, the MFU and the SFU are configured with the same basic service set identifier (BSSID). The BSSID is an important term in the wireless local area network (WLAN), and it is used to identify a specific Wi - Fi network. For example, Figure 1AAs shown, the FTTR system is deployed in the same subnet. The FTTR system includes an MFU, SFU1, SFU2, and SFU3. The MFU is connected to SFU1, SFU2, and SFU3 through optical fibers respectively. In some possible implementation scenarios, the MFU can be connected to SFU1, SFU2, and SFU3 through an optical splitter respectively. See Figure 1A as shown.

[0449] In a possible application scenario, the roaming handover process may include the following processes. See Figure 1B and Figure 1C as shown: initialization process, virtual initialization, information synchronization, and link handover. Figure 1B Taking the initial online of the STA on SFU1 as an example, the link is switched to, taking the switch to SFU2 as an example. See Figure 1B As shown, in the collaborative roaming scheme based on WMCI, it mainly includes four aspects of processing. One is the synchronization of roaming configuration information, the second is the synchronization of networking information, the third is the terminal online processing, and the fourth is the terminal roaming processing.

[0450] In the initialization process: During the STA online process, the scanning process, authentication process, association process, and four-way handshake process are executed. In the initialization process, the SMF and SFU will receive the initialization information of the STA, and the corresponding SFU will respond to the request message of the STA.

[0451] In the virtual initialization process: After the STA goes online, the MFU will send some key information of the STA to each SFU to enable each SFU to create a virtual user for the STA, so that the STA is virtually online on other SFUs, that is, save the relevant information for communicating with the STA but not provide services for the STA currently. The key information may include one or more of the authentication request frame, AID, association request frame, or secret key (Pairwise Transient Key PTK or group Transient key GTK). The full English name of the pairwise transient key is Pairwise Transient Key, abbreviated as PTK. The full English name of the group transient key is group Transient key, abbreviated as GTK.

[0452] 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.

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

[0454] The roaming process provided by the embodiments of this application is that the source access point switches to the target access point. In one implementation scenario, the source access point can be an MFU, and the target access point is the target SFU. In another implementation scenario, the source access point can be the source SFU, and the target access point is the MFU. In yet another possible embodiment scenario, the source access point can be the source SFU, and the target access point is the target SFU. The target access point can also be referred to as the destination access point, and the target SFU can also be referred to as the destination SFU. The following description takes roaming from the source SFU to the target SFU as an example, and other implementation scenarios can be referred to accordingly, without specific elaboration.

[0455] The following first gives an exemplary description of the formats of the roaming handover indication and reporting messages involved in the embodiments of this application. See Table 1-1 below.

[0456] The parameters corresponding to each roaming handover indication and reporting message are different and can be indicated by a mask. Among them, the roaming handover message contains sequence numbers 2 to 5 and 7 to 8; the roaming handover completion status reporting message contains sequence numbers 2 to 8; the roaming handover exception handling contains sequence numbers 2 to 5 and 7 to 8; the roaming handover exception handling status reporting message contains sequence numbers 2 to 6. Table 1-1 is only an example, and the message types or message statuses corresponding to different values can be configured according to requirements, and the embodiments of this application do not limit this.

[0457] Table 1-1

[0458]

[0459]

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

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

[0462] The roaming trigger event may include that the signal strength of the STA is lower than the roaming threshold.

[0463] The source SFU periodically determines the signal strength of the STA. For example, the source SFU periodically sends beacon frames to the STA. The STA receives the beacon frames and sends a reply signal to the source SFU. The source SFU determines the received signal strength indication (RSSI) of the reply signal, and the RSSI is the signal strength. The source SFU judges the relationship between the signal strength and the roaming threshold. If it is determined that the signal strength is lower than the roaming threshold, it reports the trigger event to the MFU. For example, as the STA moves away from the source SFU, the signal gradually weakens until it is lower than the roaming threshold. If it is determined that the signal strength is not lower than the roaming threshold, it continues to detect the signal strength of the STA. In a possible implementation, the roaming threshold can be manually configured or intelligently configured. The roaming threshold can also be configured by the MFU for the source SFU.

[0464] Optionally, in different deployment scenarios, the size of the roaming threshold can be different. For example, a first roaming threshold is configured in a scenario with dense access point coverage, and a second roaming threshold is configured in a scenario with sparse access point coverage. The first roaming threshold is greater than the second roaming threshold. In this way, in the case of dense coverage, since the distance between access points is small, if the roaming threshold is set relatively small, roaming will occur when moving a small distance, resulting in frequent roaming. To save the resources of roaming management, the roaming threshold is configured to be larger. In the case of sparse coverage, since the distance between access points is large, it is necessary to be at a relatively far distance from the currently accessed access point to enter the coverage range of an access point with a stronger signal, so the roaming threshold is configured to be smaller.

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

[0466] WMCI is an interface for the MFU and SFU to implement functions such as WLAN control. The WMCI management channel is a low-latency channel for the MFU and SFU to implement functions such as WLAN control in the FTTR network. It is used to carry WMCI messages and is carried by an independent FEMport-ID. The WMCI management channel is called the Wi-Fi Management and Control Channel (WMCC). The WMCI message is encapsulated in the FEM frame and is used to manage and control the WLAN function of the SFU. The FTTR transceiver can identify the destination of the WMCI message through the FEM port ID in the FEM frame.

[0467] As shown in Table 1-2, it is the encapsulation format of the WMCI message.

[0468] Table 1-2

[0469]

[0470] 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 an unsupported message, the MFU ignores the message. When the SFU receives a message with a reserved or unsupported message type ID, the message is ignored.

[0471] The sequence number is an 8-bit field that contains a sequence number counter to ensure the robustness of the WMCI message channel. In the downlink direction, the sequence number field is filled 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 over from 255 to 1. The value 0 is not used in the downlink direction. In the uplink direction, when the 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 actively, the sequence number = 0 is used.

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

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

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

[0475] Table 1-3

[0476]

[0477] Each message type can carry 16 parameters. For the detailed description of the parameter sequence, please refer to the message definition.

[0478] The message content should be filled in the order indicated by the parameter mask. For a downlink request message, the parameter mask indicates the parameters that the MFU wants to obtain. For an uplink message, the parameter mask indicates the reported and replied parameters.

[0479] Message verification can be performed using the Cyclic Redundancy Check (CRC) method. The message verification field can also be referred to as the CRC field and is used to check whether the message is damaged during transmission. The value of this field is generated by the CRC algorithm.

[0480] Each message involved in Table 1-1 can be carried in the WMCI message, such as the content field carried in the WMCI message. In some embodiments, the WMCI message includes the identifier of the access point (such as AP ID or AP index). In one way, the identifier of the access point (such as AP ID or AP index) is carried in the message header of the WMCI message. In another way, the identifier of the access point (such as AP ID or AP index) is carried in the content field of the WMCI message, such as carried in each message involved in Table 1-1, that is, an AP ID field can be added to Table 1-1.

[0481] Exemplarily, the source SFU can carry the trigger event in the message content field of the WMCI message.

[0482] S202, the MFU sends a roaming decision information collection request to multiple SFUs in the network. The roaming decision information collection request is used to instruct the SFU to collect roaming decision information and report it to the MFU.

[0483] In one possible example, the multiple SFUs in the network can include all SFUs in the network. In another possible embodiment, the SFUs in the network can be configured to be grouped. For example, several SFUs in close proximity belong to the same group. Of course, other grouping methods are also applicable to this application, and this application does not limit this. The multiple SFUs in the network can be the SFUs in a certain group. For example, the group where the multiple SFUs are located includes the source SFU.

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

[0485] Exemplarily, the MFU can carry the roaming decision information reporting request in the WMCI message, such as carried in the message content field of the WMCI message.

[0486] Further, multiple SFUs respectively perform roaming decision information collection. The roaming decision information may include one or more of the following: one or more of RSSI, load information, or channel condition information. The roaming decision information may also be referred to as roaming auxiliary decision information, and may also use other names, which are not limited in the embodiments of the present application.

[0487] It can be understood that the load information can represent the busyness degree of the Wi-Fi channel of the SFU. The higher the load, the busier the Wi-Fi channel and the lower the communication performance; the lower the load, the more idle the Wi-Fi channel and the higher the communication performance. Exemplarily, the load information may be the number of stations connected to the SFU. Exemplarily, the load information may include the number of stations connected to the SFU and the station type. Among them, different station types correspond to different load weights. The corresponding relationship between the station type and the load weight can be preset. For example, the load weight corresponding to the station type of mobile phone is 1; the load weight corresponding to the station type of VR device is 2; the load weight corresponding to the station type of smart refrigerator is 0.2. Thus, the MFU can determine the load of the SFU according to the load information of the SFU. Exemplarily, when the load information is the number of stations, the more the number of stations, the greater the load of the SFU. Exemplarily, when the load information includes the number of stations and the station type, the number of stations of the same type can be multiplied by the load weight corresponding to this type to obtain the weighted load. Then, the weighted loads of each station type are added together, and the sum obtained can be used to represent the load of the SFU.

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

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

[0490] Table 1-4

[0491]

[0492] Among them, the Payload field may carry the parameters that the indicated SFU needs to report. In some possible implementation scenarios, default or protocol-specified parameters may be reported. In this case, there is no need to indicate the parameters that the SFU needs to report, and then the Payload and PayloadLen may add a set sequence, such as all 0s, and these two fields may not be included either.

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

[0494] 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 may be referred to as the roaming decision information reporting message, or other naming methods may also be adopted. The embodiments of this application do not limit this.

[0495] S204. The MFU selects a target SFU to be switched (or accessed) according to the roaming decision information. The source SFU may be referred to as the source SFU, and the target SFU may also be referred to as the target SFU or the destination SFU.

[0496] 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 Wi-Fi signal sent by the STA it receives to obtain the RSSI. It can be understood that the RSSI can reflect the communication performance of the channel or the link. The higher the RSSI, the higher the communication performance. The MFU can select the SFU with the largest RSSI among multiple SFUs as the target SFU.

[0497] 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 smallest load among multiple SFUs as the target SFU.

[0498] In yet another possible example, the roaming decision information sent by the SFU to the MFU includes the channel condition information of the SFU. Specifically, the SFU can measure the channel condition of its communication with the STA to obtain the channel state information. The MFU can select the SFU with the best channel condition among multiple SFUs as the target SFU. For example, select the SFU with the largest SINR as the target SFU, or select the SFU with the lowest packet loss rate as the target SFU, or select the SFU with the largest SINR among the SFUs with a packet loss rate less than a certain threshold as the second SFU. Or, the SINR and the packet loss rate respectively correspond to different weights, and the SINR is weighted with the reciprocal of the packet loss rate, and the SFU with the largest weighted value is selected as the target SFU.

[0499] In yet another possible example, the roaming decision information sent by the SFU to the MFU includes the load information and the RSSI of the SFU. For example, the SFU can select the SFU with an RSSI greater than a certain threshold and the smallest current load as the target SFU. For another example, the MFU weights the RSSIs of multiple SFUs with the load amounts, and determines the SFU with the largest weighted value as the target SFU.

[0500] 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 weights. For example, RSSI, load, SINR (and / or packet loss rate) respectively correspond to different weights, and the target SFU is determined by weighted calculation of weights.

[0501] It should be understood that there are other combination methods for the above-mentioned roaming decision information. Therefore, the MFU can select the optimal SFU as the target SFU according to different combinations, and no further examples will be given here.

[0502] In some possible implementation manners, after the MFU selects the target SFU, it starts the roaming processing flow. Starting the roaming processing flow can, for example, start the handover state machine. The handover state machine is used to describe the state of roaming handover. For example, the roaming handover states include: the state of roaming processing, the state of roaming reporting.

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

[0504] Table 1-5

[0505]

[0506] Table 1-6

[0507]

[0508] Among them, the unit of load is bps, and the value range can be 1 to 2^40 bps, and 2^40 bps is approximately equal to 1 Tbps.

[0509] Among them, the Payload field can carry the parameters that the indicated SFU needs to report. In some possible implementation scenarios, default or protocol-specified parameter reporting can be adopted. In this case, there is no need to indicate the parameters that the SFU needs to report, and then the Payload and PayloadLen can add a set sequence, such as all 0s, and these two fields can also be not included.

[0510] If the SFU successfully completes the collection of roaming decision information, it can reply with a roaming decision information reporting confirmation message, that is, Status = 0 for No. 6. Otherwise, it replies with a roaming decision information reporting failure message, that is, Status = 1.

[0511] S205, the MFU sends a roaming start indication message to the source SFU and the target SFU.

[0512] In some embodiments, after the MFU selects the target SFU, it caches the downlink packets of the caching site and stops sending downlink packets to the source SFU, and then starts the roaming process, that is, executes S205.

[0513] The roaming start indication message can also be referred to as the roaming start message, or can adopt other names, which are not limited in the embodiments of the present application.

[0514] After receiving the roaming start indication message, the source SFU and the target SFU respectively start roaming, such as starting their own roaming handover state machines.

[0515] As an example, the roaming start indication message may include the fields of serial numbers 2-5 and 7-8 in Table 1-1, for example, as shown in Table 2.

[0516] Table 2

[0517]

[0518] Among them, the Payload and PayloadLen in Table 1-5 can add a set sequence, such as all 0, and these two fields can also be not included.

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

[0520] The roaming start confirmation message can also adopt other names, such as the roaming start success message, which is not limited in the embodiments of the present application.

[0521] In the case where the source SFU fails to start the roaming process, it will send a roaming start failure message to the MFU. The roaming start confirmation message and the roaming start failure message can be collectively referred to as the roaming start feedback message. The roaming start feedback message indicates whether the roaming start is successful. If it indicates success, it can be called the roaming start confirmation message. If it indicates failure, it can be called the roaming start failure message. The situation of the failure to start the roaming process will be described in detail later and will not be elaborated here.

[0522] As an example, the roaming start confirmation message may include the fields of serial numbers 2-8 in Table 1-1, for example, as shown in Table 3.

[0523] Table 3

[0524]

[0525] Among them, the Payload and PayloadLen in Table 1-5 can add a set sequence, such as all 0, and these two fields can also be not included.

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

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

[0528] S208, after the MFU receives the roaming start confirmation messages from the source SFU and the target SFU respectively, it sends a roaming preprocessing instruction to the target SFU. The roaming preprocessing instruction is used to instruct the target SFU to complete the preparatory work before roaming handover. The roaming preprocessing instruction message is used to instruct the target SFU to perform the preparatory work for roaming for the STA.

[0529] The roaming preprocessing instruction, which can also be called the roaming preprocessing message, can also adopt other names, and the present application does not limit this.

[0530] After receiving the roaming preprocessing instruction message, the target SFU performs roaming preprocessing for the STA, or performs roaming preparation for the STA, generating preprocessing information.

[0531] In one possible example, the preparatory work is: simulated aggregation.

[0532] It should be noted that, in order to improve the air interface transmission efficiency, aggregated transmission is performed between the access point and the STA. First, an aggregation session is established between the access point and the STA. Then, aggregated transmission is performed between the AP and the STA. For example, after the AP receives the aggregation frame from the STA, it can feedback in the form of a block acknowledge (BA) frame.

[0533] Simulated aggregation can be understood as simulating the aggregated transmission with the STA.

[0534] Exemplarily, the roaming preprocessing instruction includes the parameters used for simulated aggregation. For example, the aggregation parameters used to implement the aggregated transmission with the STA, or include the aggregation frame. The parameters used for simulated aggregation, or the context information of the roaming preprocessing.

[0535] As an example, the aggregation parameters are shown in Table 4-1 or Table 4-2. Table 4-1 or Table 4-2 can be applicable to the aggregation scenario. Among them, the parameters in the following table can carry some or all according to needs.

[0536] Table 4-1

[0537]

[0538] Table 4-2

[0539]

[0540]

[0541] In one possible implementation, the Key field may further include an encryption mode.

[0542] In some possible implementations, the aggregated information may further include the content of at least one field in Table 4-3 below. Among them, the parameters in the following table may carry some or all as needed.

[0543] Table 4-3

[0544]

[0545] Among them, dialog Token is the dialogue token. GCR group address element is the retransmittable multicast group address element. Multi-band is the multi-band. TCLAS represents Traffic Classification. ADDBA (AddBlock Acknowledgment) Extension is the add block acknowledgment extension.

[0546] Among them, for the frame format of the ADDBA response frame (response) stipulated by the protocol, there are a total of Tid from 0 to 7. Among them, the optional parameter has not appeared the three elements of GCR Group address, Multi-band, and TCLAS in the real scenario. Refer to Table 4-3.

[0547] In some possible implementations, the aggregated information may include the downlink aggregation parameter + ADDBA response frame (response). For example, the frame format of the downlink aggregation parameter + ADDBA response is shown in Table 4-4. Among them, the parameters in the following table may carry some or all as needed.

[0548] Table 4-4

[0549]

[0550] Among them, A-MSDU (Aggregate MAC Service Data Unit) is the aggregate MAC service data unit.

[0551] In another possible example, the preparation work is: creating a user for the STA and simulating aggregation.

[0552] Exemplarily, the roaming preprocessing indication includes one or more of the following communication information: the AID of the STA, an authentication request frame from the STA, an association (or re-association) request frame from the STA, or a secret key for two-way communication between the STA and the source SFU. Further, the target SFU creates a user for the STA according to the communication information in the roaming preprocessing indication. The target SFU also performs simulated aggregation.

[0553] In a possible implementation scenario, if the destination SFU has already established an association with the user, the parameter passed in the roaming preprocessing is an aggregation parameter, and the destination SFU establishes an aggregation with the STA through the aggregation parameter passed by the MFU.

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

[0555] The association parameters include the association request frame of the station and / or the secret key negotiated between the station and the source SFU for communication. The association parameters may also include an authentication request frame of the station.

[0556] In some possible implementation scenarios, the target SFU can create a user for the STA during the STA online phase.

[0557] As an example, the roaming preprocessing indication message may include the fields of serial numbers 2-5 and 7-8 in Table 1-1, as shown in Table 5 for example.

[0558] Table 5

[0559]

[0560] S209, the target SFU sends a roaming preprocessing completion message to the MFU. For example, after the target SFU completes the above preparation work, it sends a roaming preprocessing completion message to the MFU. Then the MFU receives the roaming preprocessing completion message from the target SFU.

[0561] In the case where the roaming preprocessing fails, the target SFU will send a roaming preprocessing failure message to the MFU. The roaming preprocessing completion message and the roaming preprocessing failure message can be collectively referred to as the roaming preprocessing feedback message. The roaming preprocessing feedback message indicates whether the roaming preprocessing is successful. If it indicates success, it can be called the roaming preprocessing completion message, and if it indicates failure, it can be called the roaming preprocessing failure message. The situation of roaming preprocessing failure will be described in detail later and will not be elaborated here.

[0562] As an example, the roaming preprocessing feedback message may include the fields of serial numbers 2-5 and 7-8 in Table 1-1, as shown in Table 6 for example.

[0563] Table 6

[0564]

[0565] Among them, the Payload and PayloadLen in Table 6 can add a set sequence, such as all 0s, and these two fields can also be excluded.

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

[0567] S210, the MFU sends a service shutdown indication message to the source SFU. The service shutdown indication message can also be called a shutdown service indication message, and can also use other names, which are not limited in the embodiments of the present application. The service shutdown indication message is used to instruct the source SFU to shut down the service interaction with the STA.

[0568] In addition, after receiving the service shutdown indication message, the source SFU can also delete the aggregated session (or simply referred to as aggregation) established locally with the STA. The source SFU can also send an aggregation deletion message to the STA, and this aggregation deletion message is used to instruct the STA to delete the established aggregated session (or simply referred to as aggregation). After the source SFU deletes the aggregation of the STA, the service of the STA is shut down.

[0569] As an example, the service shutdown indication message can include the fields of serial numbers 2 - 5, 7 - 8 in Table 1 - 1, for example, as shown in Table 7.

[0570] Table 7

[0571]

[0572] Among them, the Payload field can carry the parameters that the indicated SFU needs to report. In some possible implementation scenarios, default or protocol - specified parameter reporting can be used. In this case, since there is no need to indicate the parameters that the SFU needs to report, the Payload and PayloadLen can add a set sequence, such as all 0s, and these two fields can also be excluded.

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

[0574] In the case of a service shutdown failure, the source SFU will send a service shutdown failure message to the MFU. The service shutdown completion message and the service shutdown failure message can be collectively referred to as service shutdown feedback messages. The service shutdown feedback message indicates whether the service shutdown is 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 situation of service shutdown failure will be described in detail later and will not be elaborated here.

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

[0576] Table 8

[0577]

[0578]

[0579] In Table 8, Status = 0 corresponds to the service shutdown completion (or confirmation) message. Status = 1 - 255 corresponds to the service shutdown failure message.

[0580] After the source SFU successfully shuts down the service, it obtains the parameters that need to be synchronized. The service shutdown completion message includes the parameters that need to be synchronized. The parameters that need to be synchronized include the context information of the service interaction between the source SFU and the STA, such as the aggregated frames to be transmitted between the source SFU and the STA and the sequence numbers of each data packet in the block acknowledgment. Exemplarily, the context information that needs to be synchronized may include one or more of the PN number, SN context, IPID, or site OMI status information. The site OMI status information may include: the number of received spatial streams (Rx NSS), channel bandwidth (CW), uplink multi-user transmission disabled (UL MUdisable), the number of transmitted spatial and time streams (TxNSTS), extended range single user transmission disabled (ER SUdisable), downlink multi-user multiple-input multiple-output resound recommendation (DL MU-MIMO resoundrecommendation), uplink data multi-user transmission disabled (UL MU Data disable), etc., one or more of them.

[0581] As an example, the parameters (context information) that need to be synchronized can be seen in Table 9-1.

[0582] Table 9-1

[0583]

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

[0585] In addition, Table 9 may also include a sleep status field, which contains the sleep status of the STA (sleep or not sleep).

[0586] Among them, key replay represents key reload, and rep replay counter is the counter in the Extensible Authentication Protocol over LAN (EAPOL) frame. Keyreplay counter is the key replay counter. Key replay counter__used represents the number of EAPOL-Key packets sent by the access point. That is, this field will be incremented by 1 each time the access point sends an EAPOL-Key packet, aiming to prevent replay attacks. When starting key negotiation, this field in the EAPOL-Key packet sent by the AP is 0. The client receives the EAPOL-Key packet and records this bit locally. When the client receives the EAPOL-Key packet sent by the AP again, the value of this field in the packet must be greater than the locally recorded value; otherwise, the packet will be discarded and waiting for retransmission. When the AP receives the packet from the client, this field must be the same as that saved locally by the AP; otherwise, it will wait for retransmission until a legitimate Key replay counter is received. If the maximum number of retransmissions is reached, the AP will delete the client.

[0587] As another example, as an example, the parameters (context information) to be synchronized can be seen in Table 9-2. Among them, the parameters in the following table can carry part or all according to needs.

[0588] Table 9-2

[0589]

[0590] The channel bandwidth is used to indicate the channel bandwidth of the Physical Layer Protocol Data Unit (PPDU) that the OM initiator supports for sending or receiving (for bandwidth, sending and receiving are uniformly indicated). The number of receive spatial streams is used to indicate the number of receive spatial streams of the PPDU supported by the OM initiator. This value is less than or equal to the maximum number of spatial streams it supports. In other words, the number of receive spatial streams is the limit when the initiator is the receiver of data transmission and is also the limit on the number of spatial streams of the data sent by the sending end on the other side, and the sending end cannot exceed the capacity range limited by this number of receive spatial streams. The number of transmit spatial streams is used to indicate the number of transmit spatial streams of the PPDU supported by the OM initiator.

[0591] In other words, the number of transmit spatial streams is the limit when the initiator is the sender during data transmission, and during data transmission, it cannot exceed the capacity range limited by this number of transmit spatial streams.

[0592] As another example, the parameters (context information) to be synchronized can be seen in Table 9-3. Among them, the parameters in the following table can carry part or all according to needs.

[0593] Table 9-3

[0594]

[0595]

[0596] The core idea of the Spatial Multiplexing Power Save (SM Power Save) mechanism is to control the antenna usage strategy. In scenarios where power saving is required, the STA can adjust the number of working antennas. For example, it can switch from dual-stream to single-stream, or completely turn off some antennas to reduce the power consumption of wireless transmission. However, since the 802.11 protocol pays more attention to the interaction between the STA and the AP, the requirements for uplink transmission and downlink reception are different.

[0597] During uplink transmission, the STA can independently decide how many antennas to use and indicate the number of spatial streams through the preamble. For downlink reception, it can negotiate with the AP to avoid the situation where the station cannot receive because the AP sends multiple streams. Therefore, the station can inform the AP of its antenna status in advance to coordinate the reception behavior.

[0598] SMPS Enable: In the WIFI network, before enabling SM Power Save, the beacon frame of the AP can be checked. For example, the HTCapability field is used to determine whether the network supports SMPS. Once the network supports it, the station will negotiate the working mode with the AP through the action frame.

[0599] SM Power Save has two working modes, the static mode and the dynamic mode. The static mode is a simple on-off mode. Once enabled, the station will default to the SM power saving mode, and the station will default to single-stream reception. Only when this mode is explicitly turned off will the full-antenna working state be restored. The static mode has some similarities with the 802.11 OMI technology, but the functional scenarios and parameter settings are different.

[0600] Dynamic SM Power Save is more flexible. In the default state, the station maintains single-stream reception. When the AP needs to perform multi-stream transmission, it is triggered by Request To Send / Clear To Send (RTS / CTS). The station will temporarily turn on all antennas to receive multi-stream data. In this process, RTS and CTS may not be for multi-stream transmission, but for single-stream confirmation, because the protocol does not clearly require it. In the dynamic mode, after receiving the RTS, the station will trigger multi-stream reception through a single-stream RTS frame and confirm it with a single-stream CTS. After receiving the data, the station feeds back through a single-stream ACK and returns to single-stream reception after completion. This switching in the dynamic mode ensures high energy efficiency while still guaranteeing the accuracy of data transmission.

[0601] S212, the MFU sends a service start indication message to the target SFU. The service start indication message can also be simply referred to as the service start message. The service start indication message is used to instruct the target SFU to start service interaction with the STA. The service start indication includes configuration parameters. The configuration parameters include parameters that need to be synchronized, such as context information.

[0602] The service start indication message, which can also be simply referred to as the service start message, can also use other names, and the embodiments of this application do not make specific limitations on this.

[0603] Since the source SFU sent a deletion aggregation message to the STA in step S210, the STA has deleted the aggregation session. To restart the aggregation session to improve service transmission efficiency, after receiving the service start indication message, the target SFU can establish an aggregation session with the STA according to the service traffic. For example, the target SFU sends an AddBlock ACK (ADDBA) request frame to the STA to request the establishment of an aggregation session (abbreviated as aggregation). Subsequently, the STA can send an ADDBA response frame to the target SFU. Through the interaction of ADDBA request frames and response frames between the target SFU and the STA, a downlink aggregation session can be established. Subsequently, the target SFU can send an aggregation service frame (abbreviated as an aggregation frame) to the STA, and the aggregation service frame includes service traffic. Correspondingly, the STA can send an ADDBA request frame to the target SFU to request the establishment of an aggregation session. Subsequently, the target SFU can send an ADDBA response frame to the STA. Through the interaction of ADDBA request frames and response frames between the target SFU and the STA, an uplink aggregation session can be established. Subsequently, the STA can send an uplink aggregation service frame (abbreviated as an aggregation frame) to the target SFU, and the uplink aggregation service frame includes service traffic.

[0604] In another possible scenario, instead of sending a deletion aggregation message to the STA after receiving the service shutdown indication message, the target SFU sends a deletion aggregation message to the STA after receiving the service startup indication message. Subsequently, the STA deletes the previous aggregation session based on this message. After the previous aggregation session is deleted, the target SFU can start establishing an aggregation session with the STA. The specific establishment process is as described above and will not be elaborated here.

[0605] In addition, the value of the session token field in the ADDBA request frame is the same as the value of the session token field in the ADDBA response frame, indicating that the ADDBA response frame is a response to this ADDBA request frame.

[0606] In addition, the target SFU and the STA can establish aggregation sessions on a TID-by-TID basis. For example, under each TID, an uplink aggregation session and / or a downlink aggregation session can be established between the target SFU and the STA. For different TIDs, different uplink aggregation sessions and / or downlink aggregation sessions can be established between the target SFU and the STA.

[0607] As an example, the service startup indication message can include the fields with serial numbers 2-5 and 7-8 in Table 1-1, as shown in Table 10 for example.

[0608] Table 10

[0609]

[0610] In another possible scenario, after receiving the service startup indication message, the target SFU can send a Block ACK (BA) request to the STA to request the STA to adjust the start sequence number SSN in the BA frame. The new SSN can be carried in the BA request to facilitate the adjustment of the SSN in the BA frame.

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

[0612] In the case of service startup failure, the target SFU will send a service startup failure message to the MFU. The service startup completion message and the service startup failure message can be collectively referred to as service startup feedback messages. The service startup feedback message indicates whether the service startup is successful. If it indicates success, it can be called a service startup completion message; if it indicates failure, it can be called a service startup failure message. The situation of service startup failure will be described in detail later and will not be elaborated here.

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

[0614] Table 11

[0615]

[0616]

[0617] In Table 11, Status = 0 corresponds to the service start completion (or confirmation) message. Status = 1 - 255 corresponds to the service start failure message.

[0618] In some possible implementation manners, the context information and the aggregation parameters may also be sent to the target SFU in one message. For example, in the service start message.

[0619] In some embodiments, after the MFU receives the service start completion message from the target SFU, the roaming ends. In other embodiments, the MFU may also send the cached downlink packets to the target SFU, so that the target SFU performs service interaction with the site according to the context information. For example, the target SFU sends the cached downlink packets to the site according to the packet sequence number, or sends the aggregated packets to the STA according to the SN context, and determines the channel bandwidth and the number of streams according to the terminal OMI status information.

[0620] It should be noted that the names of the above - mentioned various messages may also adopt other names, such as the first message, the second message, etc. The embodiments of the present application do not limit this.

[0621] In a possible implementation manner, the context information includes the site OMI status information. After the target SFU receives the new site OMI status, it can perform data transmission and reception (or perform service interaction) with the site according to the transceiver parameters indicated by the site OMI status information. Or, it can also perform OM negotiation with the site to negotiate the transceiver parameters.

[0622] In the 802.11ax standard, a method for OMI is designed. By negotiating the operation mode (OM) between the initiator and the responder, the power consumption is reduced by reducing the channel bandwidth of normal operation and reducing the number of spatial - temporal streams supported during normal times. When there is a large amount of traffic to be transmitted, the larger channel bandwidth and the higher number of spatial - temporal streams are restored. Reducing the number of spatial - temporal streams or the channel bandwidth can also be understood as entering the energy - saving mode or entering the energy - saving state. The initiator can be the site, then the responder is the AP, or the initiator is the AP and the responder is the site.

[0623] In a possible implementation scenario, when the initiating end is a station, that is, before roaming, the station enters the energy-saving mode, the source SFU can synchronize the OMI status information of the station to the target SFU through the MFU. That is, the OMI status information is included in the above context information. The target SFU can perform service interactions with the station according to the transceiver parameters indicated by the OMI status information (such as determining the channel bandwidth and the number of streams).

[0624] In another possible implementation scenario, the initiating end is an AP, that is, the source AP, such as the source SFU (i.e., the scenario where the source SFU switches to the target SFU), then the context information can also include the energy-saving mode of the source SFU. Another example is that the source AP is an MFU, that is, the scenario where the MFU switches to the target SFU, and the context information can also include the energy-saving mode of the MFU.

[0625] In a possible way, when the target SFU determines that the source SFU (or MFU) enters the energy-saving mode according to the energy-saving mode of the source SFU (or MFU), it performs service interactions with the station according to the transceiver parameters indicated by the OMI status information of the station.

[0626] In another possible implementation manner, when the target SFU determines that the source SFU (or MFU) enters the energy-saving mode according to the energy-saving mode of the source SFU (or MFU), it negotiates the operation mode OM with the station.

[0627] In yet another possible implementation manner, when the target SFU determines that the energy-saving mode of the source SFU (or MFU) supports the current traffic volume of the target SFU, it performs service interactions with the station according to the transceiver parameters indicated by the OMI status information of the station. When the target SFU determines that the energy-saving mode of the source SFU (or MFU) does not support the current traffic volume of the target SFU, it negotiates the operation mode OM with the station.

[0628] As Figure 2B shown, Figure 2B is another schematic diagram of the roaming method provided by the embodiment of the present application. In this embodiment, the STA is currently connected to the SFU, and the SFU provides services for the STA. This SFU can be called the source SFU. The source SFU can be the one that the STA is actually associated with.

[0629] The roaming method provided by this embodiment includes the following steps:

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

[0631] S102, the MFU sends a roaming decision information collection request to the source SFU.

[0632] S103, The source SFU sends roaming decision information to the MFU.

[0633] Among them, the implementation processes of steps S101 - S103 can refer to the above steps S201 - 203, which will not be elaborated here.

[0634] S104, The MFU determines the target access point for roaming according to the roaming decision information.

[0635] In this embodiment, the MFU selects itself as the target access point for the STA according to the roaming decision information.

[0636] In a 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 Wi-Fi signal sent by the STA to obtain the RSSI. The MFU can also detect the RSSI of the STA. The RSSI can reflect the communication performance of the channel or the link. The higher the RSSI, the higher the communication performance. The MFU can select itself as the target access point according to the RSSI returned by the SFU and the RSSI it detected itself.

[0637] 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 access point (MFU) with the smallest load as the target access point according to the load of the SFU and its own load.

[0638] In yet another possible example, the roaming decision information sent by the SFU to the MFU includes the channel condition information of the SFU. Specifically, the SFU can measure the channel condition of its communication with the STA to obtain the channel state information. The MFU can select the device with the best channel condition among the channel conditions of multiple SFUs and its own channel condition as the target access point. For example, select the device with the largest SINR as the target access point, or select the device with the lowest packet loss rate as the target access point, or select the device with the largest SINR among the devices with a packet loss rate less than a certain threshold, or, the SINR and the packet loss rate correspond to different weights respectively, and the MFU weights the SINR with the reciprocal of the packet loss rate and selects the device with the largest weighted value as the target access point.

[0639] In yet another possible example, the roaming decision information sent by the SFU to the MFU includes the load information and RSSI of the SFU. The MFU can collect its own load information and RSSI. For example, the MFU can select the device with an RSSI greater than a certain threshold and the smallest current load as the target access point. Another example is that the MFU weights the RSSIs of multiple SFUs with the load amount and determines the device with the largest weighted value as the target access point.

[0640] 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 access point by using a weighted calculation method for weights. For example, RSSI, load, SINR (and / or packet loss rate) correspond to different weights respectively, and the target access point is determined by weighted calculation of weights.

[0641] It should be understood that there are other combination methods for the above-mentioned roaming decision information. Therefore, the MFU can select the optimal device as the target access point according to different combinations, and no further examples will be given here.

[0642] In some possible implementation manners, after the MFU selects the target access point (MFU), it starts to initiate the roaming processing flow. Initiating the roaming processing flow can, for example, initiate a handover state machine. The handover state machine is used to describe the state of roaming handover. For example, the roaming handover state includes: the state of roaming processing, the state of roaming reporting.

[0643] Among them, the roaming decision information collection and reporting message sent by the SFU to the MFU can include the fields numbered 2 - 8 in Table 1-1, and the specific format is shown in Table 12 below. In addition, the roaming decision information collection and reporting message can also be referred to as the roaming decision reporting message, or use other names, and the embodiments of the present application do not limit this.

[0644] Table 12

[0645]

[0646] Table 13

[0647]

[0648]

[0649] Among them, the Payload field in Table 12 can carry the parameters reported by the SFU. In some possible implementation scenarios, default or protocol-specified parameters can be reported. In this case, there is no need to indicate the parameters that the SFU needs to report, and then the Payload and PayloadLen can add a set sequence, such as all 0, and these two fields can also be not included.

[0650] S105, the MFU sends a roaming start indication message to the source SFU.

[0651] The roaming start indication message can also be referred to as the roaming start message, or use other names, and the embodiments of the present application do not limit this.

[0652] After the MFU makes a roaming decision, it can start the roaming handover state machine. After receiving the roaming start indication message, the source SFU can also start the roaming handover state machine.

[0653] The roaming start indication message can include the fields with serial numbers 2 - 5 and 7 - 8 in Table 1 - 1, as shown in Table 14 below, for example.

[0654] Table 14

[0655]

[0656] Among them, the Payload and PayloadLen in Table 14 can add a set sequence, such as all 0s, and these two fields can also be not included. In addition, the parameters that the payload field can carry include the roaming decision information in Table 13 above, or the roaming pre - processing context information (aggregation parameters) as shown in Table 4 - 1 or Table 4 - 2 above, or the roaming feedback context information (parameters to be synchronized) as shown in Table 9 - 1, Table 9 - 2, or Table 9 - 3 above.

[0657] S106, the source SFU sends a roaming start confirmation message to the MFU.

[0658] Exemplarily, after the source SFU completes the startup of its own roaming handover state machine, it sends a roaming start confirmation message to the MFU.

[0659] The roaming start confirmation message can also use other names, such as the roaming start success message. The embodiments of this application do not limit this.

[0660] In the case where the source SFU fails to start the roaming process, it can send a roaming start failure message to the MFU. The roaming start confirmation message and the roaming start failure message can be collectively referred to as the roaming start feedback message. The roaming start feedback message indicates whether the roaming startup is successful. If it indicates success, it can be called the roaming start confirmation message; if it indicates failure, it can be called the roaming start failure message. The situation of the failure to start the roaming process will be described in detail later and will not be elaborated here.

[0661] As an example, the roaming start indication message can include the fields with serial numbers 2 - 8 in Table 1 - 1, as shown in Table 15 below.

[0662] Table 15

[0663]

[0664]

[0665] Among them, the Payload and PayloadLen in Table 15 can add a set sequence, such as all 0s, and these two fields can also be excluded.

[0666] In Table 15, Status = 0, corresponding to the roaming start confirmation message.

[0667] S107, after the MFU receives the roaming start confirmation message from the source SFU, it performs roaming preprocessing. The purpose of roaming preprocessing is to complete the preparations before roaming handover.

[0668] The MFU can perform roaming preprocessing for the STA, or in other words, perform roaming preparations for the STA to generate preprocessing information.

[0669] In one possible example, the roaming preprocessing includes: simulated aggregation.

[0670] To improve the air interface transmission efficiency, aggregation transmission can be performed between the access point (MFU / SFU) and the STA. First, an aggregation session is established between the access point and the STA. Then, aggregation transmission is performed between the AP (MFU / SFU) and the STA. For example, after the AP receives the aggregation frame from the STA, it can feedback in the form of a block acknowledgment BA frame.

[0671] Simulated aggregation can be understood as simulating the aggregation transmission with the STA.

[0672] As an example, the aggregation parameters are shown in Table 4-1 or Table 4-2 above and will not be elaborated here.

[0673] In another possible example, the roaming preprocessing includes: creating a user for the STA and simulated aggregation.

[0674] Among them, the MFU can create a user for the STA after receiving the roaming start confirmation message from the source SFU, based on the AID of the STA, the authentication request frame from the STA, the association (or re-association) request frame from the STA, or the secret key used for two-way communication between the STA and the source SFU. Among them, when the STA goes online, the MFU can receive the authentication request frame of the STA, the association request frame, and the secret key used for two-way communication between the STA and the source SFU sent by the source SFU.

[0675] In another possible implementation scenario, the MFU receives the authentication request frame of the STA, the association request frame, and the secret key used for two-way communication between the STA and the source SFU sent by the source SFU when the STA goes online, and the MFU creates a user for the STA based on this information.

[0676] In a possible implementation scenario, if the MFU has already established an association with the STA, the MFU establishes an aggregation with the STA according to the aggregation parameters. The aggregation parameters in the MFU are from the source SFU. When the STA goes online in the source SFU, the source SFU can pass the aggregation parameters to the MFU.

[0677] S108, the MFU sends a service shutdown indication message to the source SFU.

[0678] After the MFU completes preprocessing, it sends a service shutdown indication message to the source SFU.

[0679] The service shutdown indication message can also be referred to as a close service indication message, or it can have other names, which are not limited in the embodiments of this application. The service shutdown indication message is used to instruct the source SFU to close the service interaction with the STA.

[0680] As an example, the service shutdown indication message can include the fields of serial numbers 2 - 5 and 7 - 8 in Table 1-1, for example, as shown in Table 16.

[0681] Table 16

[0682]

[0683]

[0684] Among them, the Payload field can carry the parameters that the indicated SFU needs to report. In some possible implementation scenarios, default or protocol-specified parameter reporting can be used. In this case, there is no need to indicate the parameters that the SFU needs to report, and then the Payload and PayloadLen can add a set sequence, such as all 0s, and these two fields can also be not included.

[0685] In another possible solution, after receiving the service shutdown indication message, the source SFU can also delete the aggregation session (or simply referred to as aggregation) established locally with the STA. The source SFU can also send an aggregation deletion message to the STA, and this aggregation deletion message is used to instruct the STA to delete the established aggregation session (or simply referred to as aggregation). After the source SFU deletes the aggregation of the STA, it closes the service of this STA.

[0686] S109, the source SFU sends a service shutdown completion message to the MFU.

[0687] In the case of a service shutdown failure, the source SFU sends a service shutdown failure message to the MFU. The service shutdown completion message and the service shutdown failure message can be collectively referred to as service shutdown feedback messages. The service shutdown feedback message indicates whether the service shutdown is 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 situation of service shutdown failure will be described in detail later and will not be elaborated here.

[0688] As an example, the service shutdown completion message can be seen in Table 8 and will not be elaborated here.

[0689] After the source SFU successfully shuts down the service, it obtains the parameters that need to be synchronized (which can be called the parameters to be synchronized), and sends these parameters that need to be synchronized to the MFU through the service shutdown completion message. The service shutdown completion message includes the parameters that need to be synchronized.

[0690] Among them, the parameters that need to be synchronized may include the context information of the service interaction between the source SFU and the STA, such as the aggregated frames to be transmitted between the source SFU and the STA and the sequence numbers of the data packets in the block acknowledgment BA, etc.

[0691] As an example, the parameters that need to be synchronized (or context information) can be seen in Table 9-1 or Table 9-2 or Table 9-3 and will not be elaborated here.

[0692] S110, the MFU enables the service for the STA according to the synchronization parameters.

[0693] The MFU opens the communication link with the STA, sends and replies to packets to the STA, and receives the packets from the STA.

[0694] In a possible implementation manner, the parameters to be synchronized (context information) include the site OMI status information. After receiving the site OMI status information, the MFU can perform data transmission and reception (or service interaction) with the site according to the transceiver parameters indicated by the site OMI status information. Or, it can also perform OM negotiation with the site to negotiate the transceiver parameters.

[0695] In the 802.11ax standard, a method for OMI is designed. By negotiating the operation mode (OM) between the initiator and the responder, the power consumption is reduced by reducing the channel bandwidth of normal operations and reducing the number of spatial and temporal streams supported during normal times. When there is a large amount of traffic to be transmitted, the larger channel bandwidth and higher number of spatial and temporal streams are restored. Reducing the number of spatial and temporal streams or the channel bandwidth can also be understood as entering an energy-saving mode or an energy-saving state. The initiator can be a site, then the responder is an AP, or the initiator is an AP and the responder is a site.

[0696] In a possible implementation scenario, when the initiating end is a station, that is, before roaming, the station enters the energy-saving mode, and the source SFU can synchronize the station OMI status information to the MFU. That is, the OMI status information is included in the above context information. The MFU can perform service interaction with the station according to the transceiver parameters indicated by the OMI status information.

[0697] In another possible implementation scenario, the initiating end is an AP, that is, the source AP, such as the source SFU (i.e., the scenario where the source SFU switches to the MFU), and the context information can also include the energy-saving mode of the source SFU.

[0698] In a possible way, when the MFU determines that the source SFU enters the energy-saving mode according to the energy-saving mode of the source SFU, it performs service interaction with the station according to the transceiver parameters indicated by the station OMI status information (for example, determines the channel bandwidth and the number of flows).

[0699] In another possible implementation manner, when the MFU determines that the source SFU enters the energy-saving mode according to the energy-saving mode of the source SFU, it negotiates the operation mode OM with the station.

[0700] In yet another possible implementation manner, when the MFU determines that the energy-saving mode of the source SFU supports the current traffic volume of the MFU, it performs service interaction with the station according to the transceiver parameters indicated by the station OMI status information. When the MFU determines that the energy-saving mode of the source SFU does not support the current traffic volume of the MFU, it negotiates the operation mode OM with the station.

[0701] In another possible solution, since the source SFU sent a delete aggregation message to the STA in step S108, the STA has deleted the aggregation session. To restart the aggregation session, after receiving the service close completion message, the MFU can establish an aggregation session with the STA according to the service traffic. For example, the process of the MFU establishing an aggregation session with the STA can refer to the process of the target SFU establishing a federation session with the STA in the above embodiment, which will not be elaborated here.

[0702] In another possible solution, the target SFU does not send a delete aggregation message to the STA after receiving the service close indication message, but the MFU sends a delete aggregation message to the STA after receiving the above service close completion message. Furthermore, the STA deletes the previous aggregation session according to this message. After the previous aggregation session is deleted, the MFU can start to establish an aggregation session with the STA. The specific establishment process is as described above and will not be elaborated here.

[0703] It should be noted that the names of the above various messages can also be other names, such as the first message, the second message, etc. The embodiments of the present application do not limit this.

[0704] As Figure 2C shown, Figure 2C FIG. is a schematic flowchart of another roaming method provided by the embodiments of the present application. In this embodiment, the STA is currently connected to the MFU, and the MFU provides services for the STA. The roaming method provided by this embodiment includes the following steps:

[0705] S001, the MFU detects a roaming trigger event of the STA.

[0706] The roaming trigger event may include that the signal strength of the STA is lower than the roaming threshold.

[0707] Among them, the specific implementation of the MFU detecting the roaming trigger event can refer to the SFU detecting the roaming trigger event in step S201 above.

[0708] S002, the MFU sends a roaming decision information collection request to multiple SFUs in the network.

[0709] S003, multiple SFUs respectively send roaming decision information to the MFU.

[0710] S004, the MFU determines the target access point for roaming according to the roaming decision information.

[0711] Among them, the implementation processes of steps S002 - S004 can refer to steps S202 - 204 above, and will not be elaborated here.

[0712] S005, after the MFU determines the target access point for the STA's roaming during the roaming decision, it starts its own roaming handover state machine and enters the roaming processing state.

[0713] S006, the MFU sends a roaming start indication message to the target SFU.

[0714] The roaming start indication message can also be called the roaming start message, or use other names. The embodiments of the present application do not limit this.

[0715] After receiving the roaming start indication message, the target SFU can start roaming, such as starting its own roaming handover state machine.

[0716] Among them, the roaming start indication message can refer to that shown in Table 2 above, and will not be elaborated here.

[0717] S007, the target SFU sends a roaming start confirmation message to the MFU.

[0718] Exemplarily, after the target SFU starts its roaming handover state machine, it sends a roaming start confirmation message to the MFU.

[0719] S008, after the MFU receives the roaming start confirmation message from the target SFU, it sends a roaming preprocessing indication to the target SFU.

[0720] The roaming preprocessing indication is used to instruct the target SFU to complete the preparatory work before roaming handover. The roaming preprocessing indication message is used to instruct the target SFU to perform preparatory work for roaming for the STA.

[0721] The roaming preprocessing indication, which can also be referred to as the roaming preprocessing message, can also adopt other names, and this application does not limit this.

[0722] S009, the target SFU performs roaming preprocessing.

[0723] Among them, when the target SFU receives the roaming preprocessing indication message, it performs roaming preprocessing for the STA, or in other words, performs roaming preparation for the STA, generating preprocessing information.

[0724] In one possible example, the roaming preprocessing includes: simulated aggregation.

[0725] To improve the air interface transmission efficiency, aggregated transmission is performed between the access point (MFU / SFU) and the STA. First, an aggregation session is established between the access point and the STA. Then, aggregated transmission is performed between the AP (MFU / SFU) and the STA. For example, after the AP receives the aggregation frame from the STA, it can provide feedback in the form of a block acknowledgment BA frame.

[0726] Simulated aggregation can be understood as simulating the aggregated transmission with the STA.

[0727] Exemplarily, the roaming preprocessing indication sent by the MFU includes the parameters used for simulated aggregation. For example, the aggregation parameters used to achieve aggregated transmission with the STA, or it includes the aggregation frame.

[0728] As an example, the aggregation parameters are shown in Table 4-1 or 4-2 above.

[0729] In another possible example, the roaming preprocessing includes: creating a user for the STA, and simulated aggregation.

[0730] Exemplarily, the roaming preprocessing indication received by the target SFU includes one or more of the following information: the AID of the STA, the authentication request frame from the STA, the association request frame from the STA, or the secret key used for communication between the STA and the MFU. Further, the target SFU creates a user for the STA according to the information in the roaming preprocessing indication. The target SFU also performs simulated aggregation.

[0731] In a possible implementation scenario, if the target SFU has already established an association with the user, the parameter transmitted in the roaming preprocessing indication is an aggregation parameter, and the target SFU establishes an aggregation with the STA through the aggregation parameter transmitted by the MFU.

[0732] In another possible implementation scenario, if the target SFU has not yet established an association with the user, the parameters transmitted in the roaming preprocessing indication are association parameters and aggregation information, and the target SFU establishes an association and an aggregation relationship with the terminal through the association and aggregation information transmitted by the MFU.

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

[0734] In some possible implementation scenarios, the creation of a user for the STA by the target SFU can be completed during the online phase of the STA in the FTTR network.

[0735] As an example, the format of the roaming preprocessing message (i.e., the above-mentioned roaming preprocessing indication) can be referred to as shown in Table 5 above, and will not be elaborated here.

[0736] S010, the target SFU sends a roaming preprocessing completion message to the MFU.

[0737] Among them, the implementation process of step S010 can refer to the above-mentioned step S209, and will not be elaborated here.

[0738] S011, the MFU closes the service of the STA.

[0739] The MFU stops sending packets to the STA (closes the communication link with the STA) and closes the service of the STA. After the MFU successfully closes the service, it obtains the parameters that need to be synchronized. The parameters that need to be synchronized include the context information of the service interaction between the MFU and the STA, such as the aggregation frames to be transmitted between the MFU and the STA and the sequence numbers of each data packet in the block acknowledgment, etc.

[0740] As an example, the parameters that need to be synchronized can be referred to as shown in Table 9-1 or Table 9-2 or Table 9-3 above, and will not be elaborated here.

[0741] In another possible solution, the MFU can also delete the aggregation session (or simply referred to as aggregation) established locally with the STA. The MFU can also send an aggregation deletion message to the STA, and this aggregation deletion message is used to instruct the STA to delete the established aggregation session (or simply referred to as aggregation). After the MFU deletes the aggregation of the STA, it closes the service of this STA.

[0742] S012, The MFU sends a service start indication message to the target SFU.

[0743] Among them, the service start indication message can also be simply referred to as the service start message. The service start indication message is used to instruct the target SFU to start service interaction with the STA. The service start indication may include the parameters that need to be synchronized above, such as context information, etc.

[0744] The service start indication message, which can also be simply referred to as the service start message, can also adopt other names, and the embodiments of this application do not make specific limitations on this.

[0745] As an example, the format of the service start indication message can refer to Table 10 above and will not be elaborated here.

[0746] S013, The target SFU receives the service start indication message and starts the service with the STA.

[0747] After receiving the service start indication message, the target SFU starts service interaction with the STA according to the parameters that need to be synchronized. For example, it sends a message to the STA according to context information such as the unicast PN number, SN context, packet sequence number, or site OMI status information.

[0748] In a possible implementation manner, the context information includes the site OMI status information. After receiving the site OMI status information, the target SFU can perform data transmission and reception (or perform service interaction) with the site according to the transmission and reception parameters indicated by the site OMI status information. Or, it can also perform OM negotiation with the site to negotiate the transmission and reception parameters.

[0749] In the 802.11ax standard, a method for OMI is designed. By negotiating the operation mode (OM) between the initiator and the responder, the power consumption is reduced by reducing the channel bandwidth of normal operations and reducing the number of spatial-time streams supported during normal times. When there is a large amount of traffic to be transmitted, the larger channel bandwidth and higher number of spatial-time streams are restored. Reducing the number of spatial-time streams or the channel bandwidth can also be understood as entering the energy-saving mode or entering the energy-saving state. The initiator can be a station, then the responder is an AP, or the initiator is an AP and the responder is a station.

[0750] In a possible implementation scenario, when the initiator is a station, that is, before roaming, the station enters the energy-saving mode, then the MFU can synchronize the site OMI status information to the target SFU. That is, the OMI status information is included in the above context information. The target SFU can perform service interaction with the site according to the transmission and reception parameters indicated by the OMI status information (such as determining the channel bandwidth and the number of streams).

[0751] In another possible implementation scenario, the initiating end is an AP, i.e., the source AP, i.e., the MFU. Then, the context information may further include the power-saving mode of the MFU.

[0752] In one possible way, when the target SFU determines that the MFU enters the power-saving mode according to the power-saving mode of the MFU, it performs service interaction with the station according to the transceiver parameters indicated by the station OMI status information.

[0753] In another possible implementation, when the target SFU determines that the MFU enters the power-saving mode according to the power-saving mode of the MFU, it negotiates with the station on the operation mode OM.

[0754] In yet another possible implementation, when the target SFU determines that the power-saving mode of the MFU supports the current traffic volume of the target SFU, it performs service interaction with the station according to the transceiver parameters indicated by the station OMI status information. When the target SFU determines that the power-saving mode of the MFU does not support the current traffic volume of the target SFU, it negotiates with the station on the operation mode OM.

[0755] In another possible solution, since the MFU sent a delete aggregation message to the STA in step S011, the STA has deleted the aggregation session. To restart the aggregation session, after receiving the service start indication message, the target SFU may establish an aggregation session with the STA according to the traffic flow. For the specific establishment process, refer to the above embodiments and will not be elaborated here.

[0756] In another possible solution, instead of the MFU sending a delete aggregation message to the STA, after receiving the service start indication message, the MFU sends a delete aggregation message to the STA. Then, the STA deletes the previous aggregation session according to this message. After the previous aggregation session is deleted, the target SFU may start to establish an aggregation session with the STA. The specific establishment process is as described above and will not be elaborated here.

[0757] In another possible solution, after receiving the service start indication message, the target SFU may send a Block ACK (BA) request to the STA to request the STA to adjust the start sequence number SSN in the BA frame. The new SSN may be carried in the BA request to facilitate the adjustment of the SSN in the BA frame.

[0758] S014, the target SFU sends a service start completion message to the MFU.

[0759] After the service starts successfully, the target SFU sends a service start completion message to the MFU.

[0760] When the target SFU fails to start a service, it can send a service start failure message to the MFU. The service start completion message and the service start failure message can be collectively referred to as service start feedback messages. The service start feedback message indicates whether the service start is successful. If it indicates success, it can be called a service start completion message; if it indicates failure, it can be called a service start failure message. The situation of service start failure will be described in detail later and will not be elaborated here.

[0761] As an example, the format of the service start completion message can refer to Table 11 above.

[0762] In some possible implementation manners, the context information and the aggregation parameter can also be sent to the target SFU in one message. For example, the MFU sends them to the target SFU in the service start message in step S012.

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

[0764] It should be noted that the names of the above various messages can also be other names, such as the first message, the second message, etc. The embodiments of the present application do not limit this.

[0765] In some possible implementation scenarios, in the above roaming process, a roaming abnormal state may occur. The following describes the processing method for the roaming abnormal state.

[0766] Abnormal state 1: The abnormality of failed roaming start.

[0767] Method 1:

[0768] Refer to Figure 3A and Figure 3B As shown, it is a schematic diagram of a roaming method flow provided by the embodiments of the present application. When the MFU determines that the roaming of the source SFU or the target SFU fails to start, it clears the roaming information of the STA. Figure 3A and Figure 3B describe the abnormal handling method for failed roaming start.

[0769] S301. The MFU sends a roaming start indication message to the source SFU and the target SFU. Refer to S205, which will not be elaborated here.

[0770] In a possible example, after receiving the roaming start indication message, the source SFU starts roaming, such as starting its own roaming handover state machine. However, if the roaming start fails, S302a is executed.

[0771] In another possible example, after receiving the roaming start indication message, the target SFU starts roaming, such as starting its own roaming handover state machine. However, if the roaming start fails, S302b is executed.

[0772] See Figure 3A As shown in S302a, the source SFU sends a roaming start failure indication message to the MFU (which can be abbreviated as a roaming start failure message or have other names). For example, if there is a vulnerability (bug) in the software level of the source SFU, or a hardware level failure, etc., the roaming start may fail.

[0773] See Figure 3B As shown in S302b, the target SFU sends a roaming start failure indication message to the MFU. For example, if there is a vulnerability (bug) in the software level of the target SFU, or a hardware level failure, etc., the roaming start may fail.

[0774] Exemplarily, the format of the roaming start failure indication message can be seen in Table 3. Roam ProcessStatus = 1 and Status ≠ 0. In some implementation scenarios, Roam Status is equal to a value between 1 and 255, which is used to indicate the error identification code. Different values are used to indicate different failure reasons.

[0775] The SFU with roaming start failure is the source SFU or the target SFU. Figure 3A Taking the source SFU as an example, Figure 3B Taking the target SFU as an example. In some possible scenarios, the source SFU and the target SFU may both experience roaming start failure at the same time.

[0776] S303, the MFU clears the roaming information of the STA, or clears the preparation information for the STA's roaming, or the MFU clears this roaming for the STA and waits for the next roaming trigger. Clearing the roaming information can, for example, close the handover state machine.

[0777] Through the above solution, in case of roaming start failure, the roaming-related information is promptly cleared, the MFU no longer continues to execute the roaming process, reducing instruction overhead and storage resource waste, and also preventing the impact of the stored information on subsequent roaming.

[0778] In some possible implementation manners, when the time threshold for the MFU to send the roaming start indication message to the source SFU is reached or the number of retransmissions reaches the number threshold, it is determined that the source SFU fails to start roaming, and then S303 is executed.

[0779] In some other possible embodiments, if the MFU determines that the roaming start fails because the time threshold for sending the roaming start indication message to the target SFU is reached or the number of retransmissions reaches the number threshold, then S303 is executed.

[0780] Method 2:

[0781] Refer to Figure 4A and Figure 4B As shown, it is a schematic flowchart of another roaming method provided by an embodiment of the present application.

[0782] S401, refer to S301, which will not be elaborated here.

[0783] In one possible example, after receiving the roaming start indication message, the source SFU starts roaming, for example, starting its own roaming handover state machine. However, if the roaming start fails, S402a is executed.

[0784] In another possible example, after receiving the roaming start indication message, the target SFU starts roaming, for example, starting its own roaming handover state machine. However, if the roaming start fails, S402b is executed.

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

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

[0787] The SFU for which the roaming start fails is the source SFU or the target SFU. Figure 4A Taking the source SFU as an example, Figure 4B Taking the target SFU as an example. In some possible scenarios, the source SFU and the target SFU may both experience a roaming start failure at the same time, then both the source SFU and the target SFU send a roaming start failure indication to the MFU.

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

[0789] S404, the MFU sends a roaming exception handling message to the source SFU. The roaming exception handling message instructs to clear the roaming information.

[0790] In this roaming start exception handling scenario, the roaming exception handling message can also be referred to as the roaming start exception handling message, or it can also use other names. The embodiments of the present application do not make specific limitations in this regard.

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

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

[0793] In the exception handling scenario at the start of this roaming, the roaming exception handling completion message can also be referred to as the roaming start exception handling completion message, or it can adopt other names. The embodiments of this application do not make specific limitations on this.

[0794] When the source SFU receives a roaming exception handling message, it deletes the roaming information of the STA. For example, it deletes the started handover state machine, and then sends a roaming exception handling completion message to the MFU.

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

[0796] When the target SFU receives a roaming exception handling message, it deletes the roaming information of the STA. For example, it deletes the started handover state machine, and then sends a roaming exception handling completion message to the MFU.

[0797] Through the above solution, in the case of a failed roaming start, the roaming-related information is promptly cleared, and neither the MFU nor the SFU continues to execute the roaming process, reducing instruction overhead, and also reducing the waste of storage resources, and can also prevent the impact of the stored information on subsequent roaming.

[0798] In some possible implementation manners, when the time threshold is reached for the MFU to send a roaming start indication message to the source SFU or the number of retransmissions reaches the number threshold, it is determined that the source SFU fails to start roaming, and then S404 - S405 are executed.

[0799] In some other possible implementation manners, when the time threshold is reached for the MFU to send a roaming start indication message to the target SFU or the number of retransmissions reaches the number threshold, it is determined that the target SFU fails to start roaming, and then S404 - S405 are executed.

[0800] Abnormal state 2: The exception of failed roaming preprocessing.

[0801] Method 1:

[0802] Refer to Figure 5 As shown, it is a schematic diagram of a roaming method flow provided by the embodiments of this application.

[0803] S501, the MFU sends a roaming preprocessing message to the target SFU. Refer to S208, which will not be elaborated here.

[0804] After the target SFU receives the roaming preprocessing message, the target SFU completes the preparations before handover. For example, the preparations include analog aggregation. Optionally, the preparations can also include creating a user for the STA.

[0805] S502. The target SFU sends a roaming pre - processing failure indication message to the MFU. When the MFU receives the roaming pre - processing failure indication message, it determines that the roaming pre - processing of the target SFU has failed. For example, if there are bugs in the software level of the target SFU, or hardware - level failures, etc., the roaming pre - processing may fail.

[0806] Exemplarily, the format of the roaming pre - processing failure indication message can be seen in Table 6. Roam NotifyStatus = 2, and Roam Status ≠ 0. In some implementation scenarios, Roam Status is equal to a value between 1 and 255, which is used to indicate the error identification code. Different values are used to indicate different failure reasons.

[0807] S503. The MFU clears the roaming information of the STA, or in other words, clears the preparation information for the STA's roaming. Clearing the roaming information can, for example, close the handover state machine, etc.

[0808] In some possible implementation manners, when the time threshold for the MFU to send the roaming pre - processing indication message to the target SFU is reached or the number of re - transmissions reaches the number threshold, it is determined that the roaming pre - processing of the target SFU has failed, and then S503 is executed.

[0809] Method 2:

[0810] See Figure 6 shown in the following figure, which is another schematic diagram of the roaming method flow provided by the embodiments of the present application.

[0811] S601. Refer to S501, which will not be elaborated here.

[0812] S602. The target SFU sends a roaming pre - processing failure indication to the MFU. When the MFU receives the roaming pre - processing failure indication message, it determines that the roaming pre - processing of the target SFU has failed. For example, if there are bugs in the software level of the target SFU, or hardware - level failures, etc., the roaming pre - processing may fail.

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

[0814] S604. The MFU sends a roaming exception handling message to the target SFU. The roaming exception handling message instructs to delete the roaming - related information for this station.

[0815] S605. The MFU sends a roaming exception handling message to the source SFU. The roaming exception handling message instructs to delete the roaming - related information for this station.

[0816] In the exception handling scenario of the roaming preprocessing, the roaming exception handling message can also be referred to as the roaming preprocessing exception handling message, or other names can be adopted. The embodiments of this application do not make specific limitations in this regard.

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

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

[0819] In the exception handling scenario of the roaming preprocessing, the roaming exception handling completion message can also be referred to as the roaming preprocessing exception handling completion message, or other names can be adopted. The embodiments of this application do not make specific limitations in this regard.

[0820] When the target SFU receives the roaming exception handling message, it deletes the roaming information and preprocessing information of the STA. For example, deleting the roaming information of the STA includes deleting the started handover state machine. For example, deleting the preprocessing information includes deleting the simulated aggregation information and deleting the user information of the created STA. Then it sends a roaming exception handling completion message to the MFU.

[0821] When the source SFU receives the roaming exception handling message, it clears the roaming message, such as deleting the started handover state machine.

[0822] In some possible implementation manners, when the time threshold is reached for the MFU to send the roaming preprocessing indication message to the target SFU or the number of retransmissions reaches the number threshold, and the roaming preprocessing completion message replied by the target SFU is not received (or the message replied by the target SFU is not received), it is determined that the roaming preprocessing of the target SFU fails, and then S604 - S605 are executed.

[0823] Exception state 3: Exception of failed service shutdown.

[0824] Method 1:

[0825] See Figure 7 As shown, it is a schematic flowchart of a roaming method provided by the embodiments of this application.

[0826] S701. The MFU sends a service shutdown indication message to the source SFU. See S209, which will not be elaborated here.

[0827] S702. The source SFU sends a service shutdown failure indication message to the MFU. When the MFU receives the service shutdown failure indication message, it determines that the service shutdown of the source SFU fails.

[0828] For example, a bug in the software level of the source SFU, or a hardware level failure, etc. may all result in a failed service shutdown.

[0829] Exemplarily, the format of the roaming preprocessing failure indication message can be referred to as shown in Table 6. Roam NotifyStatus = 3, and Roam Status ≠ 0. In some implementation scenarios, Roam Status is equal to a value between 1 and 255, which is used to indicate the error identification code. Different values are used to indicate different failure reasons.

[0830] 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 before the site resumes roaming.

[0831] 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 the roaming-related information for the STA.

[0832] Optionally, the MFU deletes the roaming-related information of the site.

[0833] In the exception handling scenario of this service shutdown, the roaming exception handling message can also be referred to as the service shutdown exception handling message, or it can adopt other names. The embodiments of the present application do not make specific limitations on this.

[0834] S705, the source SFU sends a roaming exception handling completion message to the MFU. After receiving the roaming exception handling message a1 and restoring the configuration before the STA resumes roaming, the source SFU feeds back the roaming exception handling completion message after completion.

[0835] S706, the target SFU sends a roaming exception handling completion message to the MFU. After receiving the roaming exception handling message a2 and deleting the roaming-related information for the STA, the target SFU feeds back the roaming exception handling completion message after completion.

[0836] In the exception handling scenario of this service shutdown, the roaming exception handling completion message can also be referred to as the service shutdown exception handling completion message, or it can adopt other names. The embodiments of the present application do not make specific limitations on this.

[0837] In some possible implementation manners, the MFU can restore the configuration before the site resumes roaming, such as deleting the roaming-related information of the site.

[0838] In some possible implementation manners, when the time threshold is reached for the MFU to send the service shutdown indication message to the source SFU or the number of retransmissions reaches the number threshold, and the service shutdown completion message replied by the source SFU (or the message replied by the source SFU) is not received, it is determined that the service shutdown of the source SFU fails, and then S703 - S704 are executed.

[0839] Method 2:

[0840] See Figure 8 As shown, it is a schematic flowchart of a roaming method provided by an embodiment of the present application.

[0841] S801, the MFU sends a service shutdown indication message to the source SFU. Refer to S209, which will not be elaborated here.

[0842] S802, the source SFU sends a service shutdown failure indication message to the MFU. When the MFU receives the service shutdown failure indication message, it determines that the service shutdown of the source SFU fails. For example, vulnerabilities (bugs) in the software layer of the source SFU, or hardware layer failures, etc. may all result in service shutdown failures.

[0843] Exemplarily, 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 equal to a value between 1 and 255, which is used to indicate the error identification code. Different values are used to indicate different failure reasons.

[0844] S803, the MFU sends a roaming exception handling message b1 to the source SFU. The roaming exception handling message b1 indicates to remove this site from the network.

[0845] S804, the MFU sends a roaming exception handling message b2 to the target SFU. The roaming exception handling message b2 indicates to remove this site from the network.

[0846] In this exception handling scenario of service shutdown, the roaming exception handling message can also be called the service shutdown exception handling message, or it can adopt other names. The embodiments of the present application do not make specific limitations on this.

[0847] Optionally, the MFU removes this site from the network.

[0848] S805, the source SFU sends a roaming exception handling completion message to the MFU. After the source SFU receives the roaming exception handling message b1 and removes this site from the network, it feeds back the roaming exception handling completion message after completion.

[0849] S806, the target SFU sends a roaming exception handling completion message to the MFU. After the target SFU receives the roaming exception handling message b2 and removes this site from the network, it feeds back the roaming exception handling completion message after completion.

[0850] In this exception handling scenario of service shutdown, the roaming exception handling completion message can also be called the service shutdown exception handling completion message, or it can adopt other names. The embodiments of the present application do not make specific limitations on this.

[0851] In some possible embodiments, if the MFU determines that the service shutdown fails because the time threshold is reached or the number of retransmissions reaches the threshold when sending a service shutdown indication message to the source SFU and the service shutdown completion message replied by the source SFU (or the message replied by the source SFU) is not received, then S803 - S804 are executed.

[0852] Abnormal state 4: Abnormality of service startup failure.

[0853] Method 1:

[0854] See Figure 9 As shown, it is a schematic flowchart of a roaming method provided by an embodiment of the present application.

[0855] S901, the MFU sends a service startup indication to the target SFU. Refer to S211, which will not be elaborated here.

[0856] S902, the target SFU sends a service startup failure indication to the MFU. When the MFU receives the service startup failure indication message, it determines that the service startup of the target SFU fails. For example, a vulnerability (bug) in the software layer of the target SFU, or a hardware layer failure, etc. may all result in service startup failure.

[0857] Optionally, when the MFU receives the service startup failure indication, the MFU deletes the roaming - related information of the site, or restores the configuration before the roaming of the STA is started.

[0858] S903, the MFU sends a roaming exception handling message c1 to the target SFU. The roaming exception handling message c1 instructs to restore the configuration before the roaming of the STA is started.

[0859] S904, the MFU sends a roaming exception handling message c1 to the source SFU. The roaming exception handling message c2 instructs to restore the configuration before the roaming of the STA is started.

[0860] In this service startup exception handling scenario, the roaming exception handling message can also be called a service startup exception handling message, or it can use other names. The embodiments of the present application do not make specific limitations on this.

[0861] S905, the target SFU sends a roaming exception handling completion message to the MFU. After the target SFU receives the roaming exception handling message c1 and restores the configuration before the roaming of the STA is started, it feeds back the roaming exception handling completion message.

[0862] S906, the source SFU sends a roaming exception handling completion message to the MFU. After the source SFU receives the roaming exception handling message c2 and restores the configuration before the roaming of the STA is started, it feeds back the roaming exception handling completion message.

[0863] In the abnormal handling scenario when this service is enabled, the roaming abnormal handling completion message can also be referred to as the service enabling abnormal handling completion message, or other names can be adopted. The embodiments of this application do not make specific limitations in this regard.

[0864] In some possible implementation manners, when the time threshold is reached for the MFU to send the service enabling indication message to the target SFU or the number of retransmissions reaches the number threshold, and the service enabling completion message replied by the target SFU (or the message replied by the target SFU) is not received, it is determined that the service enabling of the target SFU fails, and then S903 - S904 are executed.

[0865] Method 2:

[0866] See Figure 10 As shown, it is a schematic flowchart of a roaming method provided by the embodiments of this application.

[0867] S1001, the MFU sends a service enabling indication to the target SFU. See S211, which will not be elaborated here.

[0868] S1002, the target SFU sends a service enabling failure indication to the MFU.

[0869] S1003, the MFU sends a roaming abnormal handling message d1 to the target SFU. The roaming abnormal handling message d1 instructs to remove the STA from the network. The target SFU deletes the relevant information of the STA.

[0870] S1004, the MFU sends a roaming abnormal handling message d1 to the source SFU. The roaming abnormal handling message d1 instructs to kick the STA out of the network. The source SFU deletes the relevant information of the STA.

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

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

[0873] In some possible implementation manners, when the time threshold is reached for the MFU to send the service enabling indication message to the target SFU or the number of retransmissions reaches the number threshold, and the service enabling completion message replied by the target SFU (or the message replied by the target SFU) is not received, it is determined that the service enabling of the target SFU fails, and then S1003 - S1004 are executed.

[0874] As an example, the roaming abnormal handling message involved in the above roaming abnormal handling process can reuse the format of the roaming handover indication message. For example, as shown in Table 12 - 1.

[0875] Table 12-1

[0876]

[0877] As an example, the roaming exception handling completion message involved in the above roaming exception handling process can reuse the format of the roaming handover feedback indication message. For example, see Table 13-1 below.

[0878] Table 13-1

[0879]

[0880]

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

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

[0883] Table 14-1

[0884]

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

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

[0887] Table 15-1

[0888]

[0889]

[0890] Among them, Roam Process Status = 1 and Status = 0, corresponding to the completion (or confirmation or success) message of abnormal roaming start processing. Roam Process Status = 2 and Status = 0, corresponding to the completion (or confirmation or success) of abnormal roaming pre - processing message, Roam Process Status = 3 and Status = 0, corresponding to the completion (or confirmation or success) message of service shutdown abnormal processing, Roam Process Status = 4 and Status = 0, corresponding to the completion (or confirmation or success) message of service startup abnormal processing.

[0891] In this application, the parameters in all the above tables except Table 1 - 2 can be carried in the message content field of the WMCI message in Table 1 - 2 and transmitted as optional or mandatory fields.

[0892] Figure 11 It is the structural diagram of the roaming device provided by the embodiments of this application. This device can be implemented as part or all of the device through software, hardware or a combination of both. This device is applied to MFU or SFU. The device provided by the embodiments of this application can implement part of the processes described in the above - mentioned methods of the embodiments of this application. This device includes: a sending module 1101 and a receiving module 1102. Optionally, it further includes a processing module ( Figure 11 not shown in the figure).

[0893] In a possible implementation scenario, this device is applied to MFU. Each of the above - mentioned modules cooperates with each other to implement Figures 2A - 10 the method flow executed by MFU in any corresponding embodiment.

[0894] In a possible embodiment, the receiving module 1102 is used to obtain the roaming decision information of the SFU in the network;

[0895] The processing module is used to determine the target SFU for the site according to the roaming decision information;

[0896] The sending module 1101 is used to send a roaming start indication message to the target SFU, and the roaming start indication message is used to indicate to start roaming processing for the site.

[0897] In another possible embodiment,

[0898] The sending module 1101 is used to send a roaming pre - processing message to the target SFU, and the roaming pre - processing message is used to indicate the target SFU to start roaming preparation for the site;

[0899] A receiving module 1102, configured to receive a roaming preprocessing feedback message from the target SFU, where the roaming preprocessing feedback message is used to indicate whether the roaming preparation for the site is successful.

[0900] In another possible embodiment,

[0901] A sending module 1101, configured to send a service shutdown indication message to a source SFU during the roaming process of a site, where the service shutdown message is used to instruct the source SFU to shut down service interaction with the site;

[0902] A receiving module 1102, configured to receive a service shutdown feedback message from the source SFU, where the service shutdown feedback message is used to indicate whether the service interaction with the site has been successfully shut down.

[0903] In another possible embodiment,

[0904] A sending module 1101, configured to send a service start indication message to a target SFU during the roaming process of a site, where the service start indication message is used to instruct the target SFU to start service interaction with the site;

[0905] A receiving module 1102, configured to receive a service start feedback message from the target SFU, where the service start feedback message is used to indicate whether the service interaction with the site has been successfully started.

[0906] In another possible implementation scenario, the device is applied to a source SFU. The above-mentioned modules cooperate with each other to implement Figures 2A - 10 The method flow executed by the source SFU in any corresponding embodiment.

[0907] In a possible embodiment:

[0908] A receiving module 1102, configured to receive a roaming start indication message from a main optical network unit MFU, where the roaming start indication message is used to indicate to start roaming processing for the site; the SFU is the source SFU currently accessed by the site or the target SFU determined by the MFU for the roaming of the site;

[0909] A processing module, configured to start roaming processing for the site.

[0910] In another possible embodiment,

[0911] A receiving module 1102, configured to receive a roaming exception handling message from a main optical network unit MFU when a source sub-optical network unit SFU has started roaming processing for the site, where the roaming exception handling message is used to indicate to clear the roaming-related information for the site, and the source SFU is the SFU currently accessed by the site;

[0912] A processing module, configured to clear roaming-related information for the site.

[0913] In another possible embodiment,

[0914] A receiving module 1102, configured to receive a service shutdown indication message from a master optical network unit (MFU) during the roaming process of a site, where the service shutdown message is used to instruct a source SFU to shut down service interaction with the site;

[0915] A sending module 1101, configured to send a service shutdown feedback message to the MFU, where the service shutdown feedback message is used to indicate whether the source SFU has successfully shut down service interaction with the site.

[0916] In another possible embodiment,

[0917] A receiving module 1102, configured to receive a first roaming exception handling message from a master optical network unit (MFU) when a source sub-optical network unit (SFU) has initiated roaming processing for a site, where the first roaming exception handling message is used to instruct to restore the configuration before the start of roaming for the site, and the target SFU is the target SFU for the roaming handover of the site;

[0918] A processing module 1101, configured to restore the configuration before the start of roaming for the site.

[0919] In another possible implementation scenario, the apparatus is applied to a target SFU. The above-mentioned modules cooperate with each other to implement Figures 2A - 10 The method flow executed by the target SFU in any corresponding embodiment.

[0920] In a possible embodiment:

[0921] A receiving module 1102, configured to receive a roaming start indication message from a master optical network unit (MFU), where the roaming start indication message is used to instruct to initiate roaming processing for the site; the SFU is the source SFU currently accessing the site or the target SFU determined by the MFU for the roaming of the site;

[0922] A processing module, configured to initiate roaming processing for the site.

[0923] In another possible embodiment, a receiving module 1102, configured to receive a roaming preprocessing message from a master optical network unit (MFU), where the roaming preprocessing message is used to instruct the target SFU to initiate roaming preparation for the site;

[0924] A sending module 1101, configured to send a roaming pre - processing feedback message to the MFU, where the roaming pre - processing feedback message is used to indicate whether the roaming preparation for the site is successful.

[0925] In another possible embodiment,

[0926] A receiving module 1102, configured to receive a second roaming exception handling message from a master optical network unit (MFU) when a target sub - optical network unit (SFU) has initiated roaming processing for the site, where the second roaming exception handling message is used to indicate clearing the roaming - related information for the site, and the source SFU is the SFU to which the site is currently connected;

[0927] A processing module, configured to clear the roaming - related information for the site.

[0928] In another possible embodiment,

[0929] A receiving module 1102, configured to receive a service enabling indication message from a master optical network unit (MFU) during the roaming process of the site, where the service enabling indication message is used to indicate that the target SFU enables service interaction with the site;

[0930] A sending module 1101, configured to send a service enabling feedback message to the MFU, where the service enabling feedback message is used to indicate whether the source SFU has successfully enabled service interaction with the site.

[0931] Figure 11 For the detailed process of the roaming device during roaming, please refer to the descriptions in the previous embodiments and will not be repeated here.

[0932] This application also provides a device 100. As Figure 12 shown, the device 100 includes: a bus 102, a processor 104, a memory 106, and a communication interface 108. The processor 104, the memory 106, and the communication interface 108 communicate with each other through the bus 102. The device 100 may be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the device 100.

[0933] The bus 102 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 9It is represented by only one line in the figure, but it does not mean that there is only one bus or one type of bus. Bus 104 may include a path for transmitting information between various components of device 100 (e.g., memory 106, processor 104, communication interface 108).

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

[0935] 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, a hard disk drive (HDD), or a solid state drive (SSD).

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

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

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

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

[0940] In yet another possible embodiment, the processor 104 executes the executable program code in the memory 106 to implement Figures 2A - 10 The method flow executed by the MFU in any corresponding embodiment.

[0941] An embodiment of the present application also provides a computer program product, which includes program instructions stored in a computer-readable storage medium. The processor reads the program instructions from the computer-readable storage medium, and the processor executes the program instructions, so that the processor executes the processes performed by the MFU in the above Figures 2A - 10 , or executes the processes performed by the source SFU in Figures 2A - 10 , or Figures 2A - 10 the processes performed by the target SFU in.

[0942] An embodiment of the present application provides a communication system, which includes the aforementioned MFU, source SFU, and target SFU. Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working process of the communication system described above can refer to the corresponding process in the foregoing method embodiment, and will not be elaborated herein.

[0943] An embodiment of the present application provides a computer-readable medium for storing a computer program, which includes instructions for executing the method steps performed by the MFU in the corresponding Figures 2A - 10 method embodiment, or instructions for executing the method steps performed by the source SFU in the corresponding Figures 2A - 10 method embodiment, or instructions for executing the method steps performed by the target SFU in the corresponding Figures 2A - 10 method embodiment.

[0944] Those of ordinary skill in the art can realize that, in combination with the method steps and units described in the embodiments disclosed in the present application, they can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the steps and components of the embodiments have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those of ordinary skill in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0945] In several embodiments provided by the present application, it should be understood that the disclosed system architectures, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division, and there may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed couplings, direct couplings, or communication connections to each other can be indirect couplings or communication connections through some interfaces, devices, or modules, and can also be electrical, mechanical, or other forms of connection.

[0946] The module described as a separate component may or may not be physically separated. The component shown as a module may or may not be a physical module, that is, it may be located in one place, or it may be distributed across multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present application.

[0947] In addition, in each embodiment of the present application, each module can be integrated into a processing module, or each module can exist physically alone, or two or more modules can be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software modules.

[0948] If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present 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. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical discs that can store program codes.

[0949] In the present application, terms such as "first" and "second" are used to distinguish between identical or similar items with basically the same functions and effects. It should be understood that there is no logical or chronological dependency between "first" and "second", nor are the quantity and execution order limited. It should also be understood that although the following description uses terms such as "first" and "second" to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the various examples, the first access point can be referred to as the second access point, and similarly, the second access point can be referred to as the first access point. The first access point and the second access point can both be access points, and in some cases, they can be separate and different access points.

[0950] The above description is only an exemplary implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art in the technical field disclosed by the present application can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A roaming method, characterized in that: include: The master optical network unit MFU obtains the roaming decision information of the SFU in the network; The MFU determines a target SFU for the site according to the roaming decision information; The MFU sends a roaming start indication message to the target SFU, where the roaming start indication message is used to indicate starting a roaming process for the site.

2. The method according to claim 1, characterized in that The roaming start indication message is carried in a Wi-Fi management control interface message.

3. The method according to claim 1 or 2, characterized in that The starting roaming process includes starting a roaming switching state machine.

4. The method according to any one of claims 1 to 3, characterized in that: The roaming start indication message includes the identifier of the site.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The MFU receives a roaming start confirmation message from the target SFU, where the roaming start confirmation message indicates that the target SFU successfully completes the roaming initiation for the site.

6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The MFU receives a roaming start failure message from the target SFU, where the roaming start failure message indicates that the roaming start of the target SFU for the site fails; The MFU clears the roaming related information for the site.

7. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The MFU sends a roaming start indication message to the source SFU, where the roaming start indication message is used to indicate starting a roaming process for the site.

8. The method according to claim 7, characterized in that The method further comprises: The MFU receives a roaming start confirmation message from the source SFU, where the roaming start confirmation message indicates that the source SFU successfully completes the roaming initiation for the site.

9. The method according to claim 7, characterized in that The method further comprises: The MFU receives a roaming start failure message from a source SFU, where the roaming start failure message indicates that the source SFU fails to initiate roaming for the site; The MFU clears the roaming related information for the site.

10. The method according to claim 6 or 9, characterized in that The method further comprises: The MFU sends a roaming exception handling message to the source SFU and the target SFU, where the roaming exception handling message is used to instruct to clear the roaming related information for the site.

11. The method according to claim 10, characterized in that The method further comprises: The MFU receives a roaming exception processing completion message from the source SFU; and / or, The MFU receives the roaming exception handling completion message from the target SFU.

12. The method according to any one of claims 1 to 11, characterized in that: The roaming decision information includes one or more of signal strength, load information or channel status information between the site and the site.

13. A roaming method, characterized in that: include: The sub-optical network unit SFU receives a roaming start indication message from the main optical network unit MFU, where the roaming start indication message is used to indicate the start of roaming processing for a site; the SFU is a source SFU currently accessed by the site or a target SFU determined by the MFU for roaming the site; The SFU initiates a roaming process for the site.

14. The method according to claim 13, characterized in that The roaming start indication message is carried in a Wi-Fi management control interface message.

15. The method according to claim 13 or 14, characterized in that The starting roaming process includes starting a roaming switching state machine.

16. The method according to any one of claims 13 to 15, characterized in that: The roaming start indication message includes the identifier of the site.

17. The method according to any one of claims 13 to 16, characterized in that: The method further comprises: The SFU sends the roaming start confirmation message to the MFU, and the roaming start confirmation message indicates that the SFU successfully completes the roaming start for the site.

18. The method according to any one of claims 13 to 16, characterized in that: The method further comprises: The SFU sends a roaming start failure message to the MFU, where the roaming start failure message indicates that the SFU fails to initiate roaming for the site.

19. The method according to claim 18, characterized in that The method further comprises: The SFU receives a roaming exception handling message from the MFU, where the roaming exception handling message is used to instruct to clear roaming related information for the site; The SFU clears the roaming related information for the site.

20. The method of claim 19, wherein: The method further comprises: The SFU sends a roaming exception processing completion message to the MFU.

21. The method according to any one of claims 13 to 20, characterized in that: The method further comprises: The SFU sends roaming decision information to the MFU.

22. The method according to claim 21, characterized in that The roaming decision information includes one or more of signal strength, load information or channel status information between the site and the site.

23. A roaming device, characterized in that: Applied to the main optical network unit MFU, including: A receiving module, used for obtaining roaming decision information of the SFU in the network; A processing module, configured to determine a target SFU for a site according to the roaming decision information; The sending module is used to send a roaming start indication message to the target SFU, where the roaming start indication message is used to indicate starting a roaming process for the site.

24. The device according to claim 23, characterized in that The roaming start indication message is carried in a Wi-Fi management control interface message.

25. The device according to claim 23 or 24, characterized in that The starting roaming process includes starting a roaming switching state machine.

26. The device according to any one of claims 23 to 25, characterized in that The roaming start indication message includes the identifier of the site.

27. The device according to any one of claims 23 to 26, characterized in that The receiving module is further used for: A roaming start confirmation message is received from a target SFU, where the roaming start confirmation message indicates that the target SFU successfully completes roaming initiation for the site.

28. The device according to any one of claims 23 to 26, characterized in that The receiving module is further configured to receive a roaming start failure message from the target SFU, wherein the roaming start failure message indicates that the roaming start of the target SFU for the site fails; The processing module is further configured to clear roaming related information for the site.

29. The device according to any one of claims 23 to 26, characterized in that The sending module is further used to send a roaming start indication message to the source SFU, where the roaming start indication message is used to indicate starting a roaming process for the site.

30. The device according to claim 29, characterized in that The receiving module is further configured to receive a roaming start confirmation message from a source SFU, wherein the roaming start confirmation message indicates that the source SFU successfully completes the roaming start for the site.

31. The device according to claim 29, characterized in that The receiving module is further configured to receive a roaming start failure message from a source SFU, wherein the roaming start failure message indicates that the source SFU fails to start roaming for the site; The processing module is further configured to clear roaming related information for the site.

32. The device according to claim 29 or 31, characterized in that The sending module is further used to send a roaming exception handling message to the source SFU and the target SFU, wherein the roaming exception handling message is used to instruct to clear the roaming related information for the site.

33. The device according to claim 32, characterized in that The receiving module is further used 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.

34. The device according to any one of claims 23 to 33, characterized in that The roaming decision information includes one or more of signal strength, load information or channel status information between the site and the site.

35. A roaming device, characterized in that: Applied to sub-optical network unit SFU, including: A receiving module, used to receive a roaming start indication message from a master optical network unit MFU, wherein the roaming start indication message is used to indicate the start of roaming processing for a site; the SFU is a source SFU currently accessed by the site or a target SFU determined by the MFU for roaming the site; The processing module is used to start roaming processing for the site.

36. The device according to claim 35, characterized in that The roaming start indication message is carried in a Wi-Fi management control interface message.

37. The device according to claim 35 or 36, characterized in that The starting roaming process includes starting a roaming switching state machine.

38. The device according to any one of claims 35 to 37, characterized in that The roaming start indication message includes the identifier of the site.

39. The device according to any one of claims 35 to 38, characterized in that The device also includes: The SFU sends the roaming start confirmation message to the MFU, and the roaming start confirmation message indicates that the SFU successfully completes the roaming start for the site.

40. The device according to any one of claims 35 to 38, characterized in that The device also includes: The SFU sends a roaming start failure message to the MFU, where the roaming start failure message indicates that the SFU fails to initiate roaming for the site.

41. The device according to claim 40, characterized in that The device also includes: The SFU receives a roaming exception handling message from the MFU, where the roaming exception handling message is used to instruct to clear roaming related information for the site; The SFU clears the roaming related information for the site.

42. The device according to claim 41, characterized in that The device also includes: The SFU sends a roaming exception processing completion message to the MFU.

43. The device according to any one of claims 35 to 42, characterized in that The device also includes: The SFU sends roaming decision information to the MFU.

44. The device according to claim 43, characterized in that The roaming decision information includes one or more of signal strength, load information or channel status information between the site and the site.

45. A roaming device, characterized in that: The roaming device includes a processor, a memory and a communication interface; The processor is used to execute the program instructions in the memory to perform the processing functions in the roaming method according to any one of claims 1 to 12; The communication interface is used to communicate with the sub-optical network unit SFU.

46. ​​A roaming device, characterized in that: The roaming device includes a processor, a memory and a communication interface; The processor is used to execute the program instructions in the memory to perform the processing functions in the roaming method according to any one of claims 13 to 22; The communication interface is used to communicate with the master optical network unit MFU.

47. A computer storage medium, characterized in that The computer storage medium includes computer instructions, and when the computer instructions are executed on an electronic device, the electronic device executes the method according to any one of claims 1 to 12, or the electronic device executes the method according to any one of claims 13 to 22.

48. A computer program product, characterized in that When the program code contained in the computer program product is used for execution by a processor in an electronic device, the electronic device executes the method according to any one of claims 1 to 12, or the electronic device executes the method according to any one of claims 13 to 22.

Images