Communication method and apparatus

Abstract

A communication method and apparatus, which relate to the technical field of communications, and are used for improving resource utilization and avoiding resource waste. The method comprises: upon determining that a station has gone offline, a first SFU sending an offline event report message to an MFU, wherein the offline event report message is used for indicating that the station has gone offline from the first SFU; and the MFU sending a terminal deletion indication message to a second SFU, wherein the terminal deletion indication message is used for indicating deletion of information of the station. When a station goes offline, a source SFU promptly reports an offline event to an MFU, and the MFU promptly notifies other SFUs to delete station information, thereby improving resource utilization and avoiding resource waste.

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411566417.4, filed on November 4, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] In Fiber To The Room (FTTR) networking, terminals may go offline. How to handle this situation with FTTR networking equipment has not been discussed. Summary of the Invention

[0005] This application provides a communication method and apparatus to reduce or avoid prolonged service interruption during site roaming.

[0006] In a first aspect, embodiments of this application provide a communication method, comprising: a first sub-optical network unit (SFU) receiving an association request frame (or reassociation request frame) from a site, and a key used for communication with the site; the association request frame is used for the site to associate with the first SFU; the reassociation request frame is used for the site to associate with the first SFU. The first SFU sends the association request frame (or reassociation request frame) and the key to a main optical network unit (MFU).

[0007] With the above solution, during the online association phase, the SFU synchronizes the obtained association request frame and key to the MFU, so that there is no need to obtain the association request frame and key again during the roaming phase, reducing the complexity of the roaming switching process, thereby reducing or avoiding long business interruption time during site roaming.

[0008] In one possible design, the first SFU sends the association request frame and the key to the main optical network unit (MFU), including: the first SFU sending a virtual information reporting message to the MFU, the virtual information reporting message including the association request frame and the key.

[0009] Virtual information reporting messages, also known as terminal connection information reporting messages, or other names, are not limited to this in the embodiments of this application.

[0010] In one possible design, the virtual information reporting message is carried in a Wi-Fi Management and Control Interface (WMCI) message.

[0011] In one possible design, the virtual information reporting message is carried in the content field of a Wi-Fi Management and Control Interface (WMCI) message.

[0012] In one possible design, the first SFU sends the key to the MFU, including:

[0013] The first SFU sends key information to the MFU, which is obtained by encrypting the key.

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

[0015] The first SFU receives an encryption function enable instruction sent by the MFU, the encryption function enable instruction being used to indicate the enabling of the link layer encryption function.

[0016] In one possible design, the key information is obtained by encrypting the key using a link-layer encryption mechanism.

[0017] In one possible design, the method further includes:

[0018] The first SFU receives a first online indication message from the MFU, the first online indication message being used to indicate that the first SFU is associated with the STA.

[0019] In one possible design, the first online indication message carries an identifier assigned by the MFU to the site, which is used to uniquely identify the site in the network.

[0020] The online notification message can also be called the terminal online message.

[0021] Secondly, embodiments of this application provide a communication method, comprising: a second sub-network unit (SFU) receiving an association request frame from a site from a main optical network unit (MFU), and a key negotiated between the site and a first SFU for communication, wherein the first SFU is the SFU currently associated with the site, and the association request frame is used for the site to associate with the first SFU; and the second SFU creating a virtual user for the site based on the association request frame and the key.

[0022] With the above solution, during the online association phase, the MFU synchronizes the association request frame and key to other SFUs, so that other SFUs do not need to obtain the association request frame and key again during the roaming phase, reducing the complexity of the roaming handover process, thereby reducing or avoiding long service interruption time during site roaming.

[0023] In one possible design, the second SFU receives the association request frame and the key from the MFU, including:

[0024] The second SFU receives a virtual user creation request message from the MFU, the first virtual user creation request message including the association request frame and the key.

[0025] The virtual user creation request message can also be called the virtual user creation message.

[0026] In one possible design, the virtual user creation request message is carried in a Wi-Fi Management Control Interface (WMCI) message.

[0027] In one possible design, the method further includes: the second SFU receiving an authentication request frame from the MFU for the site and an identifier for the site, the identifier being used to uniquely identify the site in the network;

[0028] The second SFU creates a virtual user for the site based on the association request frame and the key, including:

[0029] The second SFU creates a virtual user for the site based on the association request frame, the authentication request frame, the key, and the identifier.

[0030] In one possible design, the method further includes:

[0031] The second SFU receives a second online indication message from the MFU, which instructs the second SFU to close the communication channel with the STA.

[0032] In one possible design, the MFU, the first SFU, and the second SFU have the same Basic Service Set Identifier (BSSID). The MFU, the first SFU, and the second SFU have the same Service Set Identifier (SSID).

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

[0034] One possible design includes: a receiving module, configured to obtain an association request frame (or reassociation request frame) from a site, and a key used for communication with the site, wherein the association request frame is used for the site to associate with the first SFU;

[0035] The sending module is used to send the association request frame (or reassociation request frame) and the key to the main optical network unit (MFU).

[0036] In one possible design, the sending module is specifically used to send a virtual information reporting message to the MFU, the virtual information reporting message including the association request frame and the key.

[0037] In one possible design, the virtual information reporting message is carried in a Wi-Fi Management and Control Interface (WMCI) message.

[0038] In one possible design, the sending module is specifically used for:

[0039] Send key information to the MFU, the key information being obtained by encrypting the key.

[0040] In one possible design, the receiving module is further configured to:

[0041] The encryption function is enabled by the MFU. The encryption function enable instruction is used to indicate that the link layer encryption function is enabled.

[0042] In one possible design, the receiving module is further configured to:

[0043] Receive a first online indication message from the MFU, the first online indication message being used to indicate that the first SFU is associated with the STA.

[0044] In one possible design, the first online indication message carries an identifier assigned by the MFU to the site, which is used to uniquely identify the site in the network.

[0045] Fourthly, embodiments of this application provide a communication device that has the functionality to implement the second aspect and the optional methods described above. The device includes at least one module for implementing the methods provided by the second aspect and the optional methods described above.

[0046] One possible design includes: a receiving module, configured to receive an association request frame from a site in a main optical network unit (MFU), and a communication key negotiated between the site and a first SFU, where the first SFU is the SFU currently associated with the site, and the association request frame is used for the site to associate with the first SFU; and a processing module, configured to create a virtual user for the site based on the association request frame and the key.

[0047] In one possible design, the receiving module is specifically used for:

[0048] Receive a virtual user creation request message from MFU, the first virtual user creation request message including the association request frame and the key.

[0049] In one possible design, the virtual user creation request message is carried in a Wi-Fi Management Control Interface (WMCI) message.

[0050] In one possible design, the receiving module is further configured to:

[0051] A second online indication message is received from the MFU, which instructs the second SFU to close the communication channel with the STA.

[0052] In one possible design, the first SFU and the second SFU have the same Basic Service Set Identifier (BSSID).

[0053] Fifthly, this application provides a communication device, which includes a processor, a memory, and a communication interface; the processor is used to execute program instructions in the memory to implement the methods provided in the first aspect and the optional mode of the first aspect, and the communication interface is used to communicate with an MFU.

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

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

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

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

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

[0059] Eleventhly, embodiments of this application provide a communication method, including:

[0060] The main optical network unit (MFU) receives an association request frame from a site sent by a first SFU, along with a key used for communication between the first SFU and the site. The first SFU is the SFU currently associated with the site, and the association request frame is used for the site to associate with the first SFU. The MFU then sends the association request frame and the key to a second SFU.

[0061] With the above scheme, during the online association phase, the SFU will synchronize the obtained association request frame and key to the MFU, and the MFU will synchronize the association request frame and key to other SFUs. This means that during the roaming phase, other SFUs do not need to obtain the association request frame and key again, reducing the complexity of the roaming handover process and thus reducing or avoiding long service interruption times during site roaming.

[0062] In one possible design, the main optical network unit (MFU) receives an association request frame from a site sent by the first SFU, and a key used for communication between the first SFU and the site, including:

[0063] The MFU receives a virtual information reporting message from the first SFU, the virtual information reporting message including the association request frame and the key.

[0064] In one possible design, the virtual information reporting message is carried in a Wi-Fi Management and Control Interface (WMCI) message.

[0065] In one possible design, the MFU receives the key sent by the first SFU, including:

[0066] The MFU receives key information sent by the first SFU, and the key information is obtained by encrypting the key.

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

[0068] The MFU determines that uplink and downlink encryption is not enabled in the network, and sends an encryption enable instruction to the SFU in the network. The encryption enable instruction is used to indicate that the link layer encryption function is enabled.

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

[0070] The MFU sends the authentication request frame of the site and the identifier of the site to the second SFU. The identifier is used to uniquely identify the site in the network.

[0071] In one possible design, the MFU sends an authentication request frame for the site and an identifier assigned to the site to the second SFU, including:

[0072] The MFU sends a second online indication message to the second SFU, which instructs the second SFU to close the communication channel with the STA and / or not to respond to the site.

[0073] In one possible design, the MFU sends the association request frame and the key to the second SFU, including:

[0074] The MFU sends a virtual user creation request message to the second SFU. The virtual user creation request message includes the association request frame and the key. The virtual user creation request message is used to instruct the second SFU to create a virtual user for the site.

[0075] In one possible design, the virtual user creation request message is carried in a Wi-Fi Management Control Interface (WMCI) message.

[0076] In one possible design, the method further includes:

[0077] The MFU receives a virtual user creation completion message from the second SFU, which instructs the second SFU to complete the creation of a virtual user for the site.

[0078] In one possible design, the method further includes:

[0079] The MFU determines that uplink and downlink encryption is enabled in the network and sends an encryption function disable instruction to the SFU in the network. The encryption function disable instruction is used to indicate that the link layer encryption function is disabled.

[0080] In one possible design, the method further includes:

[0081] The MFU receives a virtual user creation failure message from the second SFU, the virtual user creation failure message being used to indicate that the second SFU failed to create a virtual user for the site;

[0082] The MFU sends a virtual user re-creation request message to the second SFU. The virtual user re-creation request message includes the association request frame and the key.

[0083] In one possible design, the method further includes:

[0084] When the number of times the MFU receives the virtual user creation failure message reaches a threshold, it instructs the second SFU to remove the site from the network.

[0085] In one possible design, the first SFU and the second SFU have the same Basic Service Set Identifier (BSSID).

[0086] In a twelfth aspect, embodiments of this application provide a communication device having the functionality to implement the eleventh aspect and its optional methods. The device includes at least one module for implementing the methods provided by the eleventh aspect and its optional methods. In one possible design, applied to a main optical network unit (MFU), it includes:

[0087] The receiving module is used to receive an association request frame from the site sent by the first SFU, and the key used for communication between the first SFU and the site. The first SFU is the SFU currently associated with the site, and the association request frame is used for the site to associate with the first SFU.

[0088] The sending module is used to send the association request frame and the key to the second SFU.

[0089] In one possible design, the receiving module is specifically used for:

[0090] Receive a virtual information reporting message from the first SFU, the virtual information reporting message including the association request frame and the key.

[0091] In one possible design, the virtual information reporting message is carried in a Wi-Fi Management and Control Interface (WMCI) message.

[0092] In one possible design, the receiving module is specifically used for:

[0093] The system receives key information sent by the first SFU, which is obtained by encrypting the key.

[0094] In one possible design, the device further includes:

[0095] The MFU determines that uplink and downlink encryption is not enabled in the network, and sends an encryption enable instruction to the SFU in the network. The encryption enable instruction is used to indicate that the link layer encryption function is enabled.

[0096] In one possible design, the sending module is further configured to:

[0097] The MFU sends the authentication request frame of the site and the identifier of the site to the second SFU. The identifier is used to uniquely identify the site in the network.

[0098] In one possible design, the sending module is further configured to:

[0099] Send a second online indication message to the second SFU, the second online indication message being used to instruct the second SFU to close the communication channel with the STA and / or not respond to the site.

[0100] In one possible design, the sending module is specifically used for:

[0101] Send a virtual user creation request message to the second SFU. The virtual user creation request message includes the association request frame and the key. The virtual user creation request message is used to instruct the second SFU to create a virtual user for the site.

[0102] In one possible design, the virtual user creation request message is carried in a Wi-Fi Management Control Interface (WMCI) message.

[0103] In one possible design, the receiving module is further configured to:

[0104] Receive a virtual user creation complete message from the second SFU, the virtual user creation complete message being used to instruct the second SFU to complete the creation of a virtual user for the site.

[0105] In one possible design, the sending module is further used for

[0106] Once it is determined that uplink and downlink encryption functions are enabled in the network, an encryption function disabling instruction is sent to the SFU in the network. The encryption function disabling instruction is used to indicate that the link layer encryption function is disabled.

[0107] In one possible design, the receiving module is further configured to receive a virtual user creation failure message from the second SFU, the virtual user creation failure message being used to indicate that the second SFU failed to create a virtual user for the site;

[0108] The sending module is further configured to send a virtual user re-creation request message to the second SFU, the virtual user re-creation request message including the association request frame and the key.

[0109] In one possible design, the device further includes:

[0110] When the number of times the MFU receives the virtual user creation failure message reaches a threshold, it instructs the second SFU to remove the site from the network.

[0111] In one possible design, the first SFU and the second SFU have the same Basic Service Set Identifier (BSSID).

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

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

[0114] In a fifteenth aspect, this application provides a computer program product including program instructions stored in a computer-readable storage medium. The processor of the MFU reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the second SFU to perform the method provided in either the eleventh aspect or any of the optional embodiments of the eleventh aspect.

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

[0116] In a seventeenth aspect, embodiments of this application provide a communication method, comprising: a primary optical network unit (MFU) receiving an offline event reporting message from a first secondary optical unit (SFU), the offline event reporting message indicating that the site is offline; and the MFU sending a deletion terminal indication message to a second SFU, the deletion terminal indication message indicating information for deleting the site.

[0117] In the above method, when a site goes offline, the source SFU promptly reports the offline event to the MFU, and the MFU promptly notifies other SFUs to delete the site information, which can improve resource utilization and avoid resource waste.

[0118] In one possible design, it also includes: receiving the second SFU sending a terminal deletion success indication message.

[0119] In one possible design, the method further includes:

[0120] The MFU sends the terminal deletion instruction message to the first SFU.

[0121] In one possible design, the method further includes:

[0122] The MFU deletes the information from the site.

[0123] In one possible design, the method further includes:

[0124] The MFU reclaims the site's identifier, which uniquely identifies the site within the network.

[0125] In one possible design, the method further includes:

[0126] When the site goes online, the MFU assigns the site's identifier.

[0127] In one possible design, the method further includes:

[0128] The MFU sends the site's identifier to the SFU in the network.

[0129] In one possible design, the MFU sends the site's identifier to the SFUs in the network, including:

[0130] The MFU sends an online indication message to the SFU in the network, and the online indication message includes the identifier of the site.

[0131] Eighteenthly, embodiments of this application provide a communication method, including: a first sub-optical network unit (SFU) determining that a site is offline;

[0132] The first SFU sends an offline event reporting message to the main optical network unit (MFU), the offline event reporting message being used to indicate that the site is offline from the first SFU.

[0133] In one possible design, the method further includes:

[0134] The first SFU receives a terminal deletion instruction message from the MFU, the terminal deletion instruction message being used to instruct the first SFU to delete the information of the site.

[0135] In one possible design, the method further includes:

[0136] The first SFU sends a terminal deletion success indication message to the MFU.

[0137] In one possible design, the method further includes:

[0138] When the site comes online, the first SFU receives the site's identifier from the MFU, and the site's identifier uniquely identifies the site in the network.

[0139] In one possible design, the first SFU receives an identifier of the site from the MFU, including:

[0140] Receive an online indication message from the MFU, the online indication message including the identifier of the site.

[0141] In a nineteenth aspect, embodiments of this application provide a communication method, comprising: a second SFU receiving a deletion terminal indication message from an MFU, the deletion terminal indication message being used to indicate the deletion of information of the site; and the second SFU deleting the information of the site.

[0142] In the above method, when a site goes offline, the source SFU promptly reports the offline event to the MFU, and the MFU promptly notifies other SFUs to delete the site information, which can improve resource utilization and avoid resource waste.

[0143] In one possible design, the second SFU also sends a terminal deletion success indication message to the MFU.

[0144] In a twentieth aspect, embodiments of this application provide a communication device having the functionality to implement the seventeenth aspect and the optional methods of the seventeenth aspect described above. The device includes at least one module for implementing the methods provided by the seventeenth aspect and the optional methods of the seventeenth aspect.

[0145] In one possible design, applied to the main optical network unit (MFU), it includes: a receiving module for receiving an offline event reporting message from a first SFU, the offline event reporting message indicating that the site is offline; and a sending module for sending a delete terminal indication message to a second SFU, the delete terminal indication message indicating information for deleting the site.

[0146] In one possible design, the receiving module is further configured to:

[0147] Receive the terminal deletion success indication message sent by the second SFU.

[0148] In one possible design, the sending module is further configured to:

[0149] Send the terminal deletion instruction message to the first SFU.

[0150] In one possible design, the device further includes:

[0151] The processing module is used to delete the information of the site.

[0152] In one possible design, the device further includes:

[0153] A processing module is used to reclaim the identifier of the site, which uniquely identifies the site in the network.

[0154] In one possible design, the processing module is further configured to:

[0155] When the site goes online, an identifier for the site is assigned to it.

[0156] In one possible design, the sending module is further configured to:

[0157] Send the site's identifier to the SFU in the network.

[0158] In one possible design, the sending module is specifically used for:

[0159] Send an online indication message to the SFU in the network. The online indication message includes the identifier of the site.

[0160] In a twentieth aspect, embodiments of this application provide a communication device having the functionality to implement the seventeenth aspect and the optional methods of the seventeenth aspect described above. The device includes at least one module for implementing the methods provided by the seventeenth aspect and the optional methods of the seventeenth aspect.

[0161] In one possible design, the first sub-optical network unit (SFU) includes: a processing module for determining that a site is offline; and a sending module for sending an offline event reporting message to the main optical network unit (MFU), the offline event reporting message indicating that the site is offline from the first SFU.

[0162] In one possible ear design, the device further includes:

[0163] The receiving module is configured to receive a deletion terminal indication message from the MFU, the deletion terminal indication message being used to instruct the first SFU to delete the information of the site.

[0164] In one possible design, the sending module is further configured to:

[0165] Send a terminal deletion success indication message to the MFU.

[0166] In one possible design, the device further includes:

[0167] A receiving module is configured to receive the site identifier from the MFU when the site comes online, the site identifier being uniquely identified in the network.

[0168] In one possible design, the receiving module is specifically used for:

[0169] Receive an online indication message from the MFU, the online indication message including the identifier of the site.

[0170] In a twentieth aspect, embodiments of this application provide a communication device applied to a second SFU, comprising:

[0171] A receiving module is used to receive a deletion terminal indication message from the MFU, the deletion terminal indication message being used to indicate the deletion of the site information; a processing module is used to delete the site information.

[0172] In the above method, when a site goes offline, the source SFU promptly reports the offline event to the MFU, and the MFU promptly notifies other SFUs to delete the site information, which can improve resource utilization and avoid resource waste.

[0173] In one possible design, it also includes a sending module for sending a terminal deletion success indication message to the MFU.

[0174] In a twentieth aspect, this application provides a communication device, the communication device including a processor, a memory, and a communication interface; the processor is configured to execute program instructions in the memory to implement the methods provided in the seventeenth aspect and the optional manner of the seventeenth aspect, and the communication interface is configured to communicate with other SFUs.

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

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

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

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

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

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

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

[0182] In a thirty-first aspect, embodiments of this application provide a communication system including a first SFU, a second SFU, and an MFU. The first SFU is used to perform the method described in the eighteenth aspect or any design of the eighteenth aspect, the second SFU is used to perform the method described in the nineteenth aspect or any design of the nineteenth aspect, and the MFU is used to perform the method described in the seventeenth aspect or any design of the seventeenth aspect.

[0183] In a thirty-second aspect, embodiments of this application provide a communication method, including:

[0184] The main optical network unit (MFU) obtains the association request frame of the site, the authentication request frame of the site, and the key used for communication between the first SFU and the site from the first sub-optical network unit (SFU). The first SFU is the SFU currently associated with the site.

[0185] The MFU sends a virtual user creation request message to the second SFU. The virtual user creation request message is used to instruct the SFU to create a virtual user for the site. The virtual user creation request message includes the association request frame, the authentication request frame, the key, and the identifier of the site. The identifier is used to uniquely identify the site in the network.

[0186] In one possible design, the virtual user creation request message is carried in a Wi-Fi Management Control Interface (WMCI) message.

[0187] In one possible design, the method also includes:

[0188] The MFU receives a virtual user creation completion message from the second SFU, which instructs the second SFU to complete the creation of a virtual user for the site.

[0189] In one possible design, the method also includes:

[0190] The MFU receives a virtual user creation failure message from the second SFU, the virtual user creation failure message being used to indicate that the second SFU failed to create a virtual user for the site;

[0191] The MFU sends a virtual user re-creation request message to the second SFU. The virtual user re-creation request message includes the association request frame, the authentication request frame, the key, and the identifier of the site.

[0192] In one possible design, the method also includes:

[0193] When the number of times the MFU receives the virtual user creation failure message reaches a threshold, it instructs the second SFU to remove the site from the network.

[0194] In a thirty-third aspect, embodiments of this application provide a communication method, including:

[0195] The second sub-optical network unit (SFU) receives a virtual user creation request message from the main optical network unit (MFU). The virtual user creation request message is used to instruct the SFU to create a virtual user for the site. The virtual user creation request message includes an association request frame for the site, an authentication request frame for the site, a communication key negotiated between the site and the first SFU, and an identifier for the site. The identifier is used to uniquely identify the site in the network. The first SFU is the SFU currently associated with the site.

[0196] The second SFU creates a virtual user for the site based on the association request frame, the authentication request frame, the key, and the site identifier.

[0197] In one possible design, the virtual user creation request message is carried in a Wi-Fi Management Control Interface (WMCI) message.

[0198] In one possible design, the method further includes:

[0199] The second SFU sends a virtual user creation completion message to the MFU, which instructs the second SFU to complete the creation of a virtual user for the site.

[0200] In one possible design, the method further includes:

[0201] The second SFU sends a virtual user creation failure message to the MFU, the virtual user creation failure message being used to indicate that the second SFU failed to create a virtual user for the site.

[0202] In one possible design, the method further includes:

[0203] The second SFU receives a virtual user re-creation request message from the MFU, the virtual user re-creation request message including the association request frame, the authentication request frame, the key, and the identifier of the site;

[0204] The second SFU creates a virtual user for the site based on the association request frame, the authentication request frame, the key, and the site identifier.

[0205] In one possible design, the method further includes:

[0206] When the number of times the second SFU fails to create a virtual user for the site reaches a threshold, the site is removed from the network.

[0207] In one possible design, the method further includes:

[0208] When the number of times the second SFU sends the virtual user creation failure message to the MFU reaches a threshold, it receives a removal instruction from the MFU.

[0209] The second SFU removes the site from the network.

[0210] In one possible design, the first SFU and the second SFU have the same Basic Service Set Identifier (BSSID).

[0211] The second SFU mentioned above can be understood as an SFU in the network other than the first SFU, that is, other SFUs in the network besides the first SFU.

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

[0213] Figure 1 is a schematic diagram of the FTTR system architecture provided in an embodiment of this application;

[0214] Figure 2 is a flowchart of the WIFI connection process of the STA provided in the embodiment of this application;

[0215] Figure 3 is a flowchart of a communication method provided in an embodiment of this application;

[0216] Figure 4A is a schematic diagram of the authentication process in a communication method provided in an embodiment of this application;

[0217] Figure 4B is a schematic diagram of the authentication process in a communication method provided in an embodiment of this application;

[0218] Figure 5A is a schematic flowchart of a communication method provided in an embodiment of this application;

[0219] Figure 5B is a schematic flowchart of a communication method provided in an embodiment of this application;

[0220] Figure 6A is a schematic flowchart of a communication method provided in an embodiment of this application;

[0221] Figure 6B is a schematic flowchart of a communication method provided in an embodiment of this application;

[0222] Figure 7A is a schematic diagram of a roaming process provided in an embodiment of this application;

[0223] Figure 7B is a schematic diagram of a roaming switching process provided in an embodiment of this application;

[0224] Figure 8 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0225] Figure 9 is a schematic diagram of a communication device structure provided in an embodiment of this application;

[0226] Figure 10 is a schematic diagram of a device structure provided in an embodiment of this application. Detailed Implementation

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

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

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

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

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

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

[0233] In some possible implementation scenarios, the STA's Wi-Fi connection process can include four stages: scanning, authentication, association, and a four-way handshake. The Wi-Fi connection process can also be the connection process between the site and the access point.

[0234] For example, as shown in Figure 2, the scanning phase described above may include the site sending a probe request frame to the wireless access point, and the wireless access point sending a probe response frame to the site upon receiving the probe request frame. The authentication phase described above may include the site sending an authentication request frame to the wireless access point via an open system upon receiving the probe response frame, and the wireless access point sending an authentication response frame to the site upon receiving the authentication request frame. The association phase described above may include the site sending an association request frame to the wireless access point upon receiving the authentication response frame, and the wireless access point sending an association response frame to the site upon receiving the association request frame. The association request frame may also be called association request information. The association request information, also called an association request frame, contains the necessary information for the access point to establish a connection with the site, including the site's capability information (e.g., the communication protocols supported by the site), so that the access point can communicate with the site using a communication method compatible with the site's capabilities.

[0235] The four-way handshake process described above may include the wireless access point sending an association response frame to the station, followed by an eapol key carrying a random number (AP number once, ANonce) generated by the wireless access point, to complete the first handshake (M1). Next, the station may send a key information frame carrying a station number once (SNonce) and a message integrity code (MIC) to the wireless access point to complete the second handshake (M2). Then, the wireless access point may send a key information frame carrying an encrypted group transient key (GTK) and a message integrity code to the station to complete the third handshake (M3). Finally, the station may send a key information frame carrying a message integrity code to the wireless access point to complete the fourth handshake (M4). After these four handshakes, a key for communication between the access point and the station is generated.

[0236] Among them, the associated request frame can be simply referred to as the associated request, and the associated response frame can be simply referred to as the associated response.

[0237] In an FTTR deployment scenario, multiple SFUs deployed in a subnet with the same BSSID will all receive probe request frames from the STA. Therefore, multiple SFUs may send probe response frames to the same STA, leading to conflicts and affecting site uptime.

[0238] In some embodiments, to avoid the above situation, each SFU that receives a probe request frame sends the received probe request frame and performance parameters representing the communication performance between the SFU and the STA to the MFU. The MFU can determine the SFU to respond to the probe request frame based on the performance parameters sent by the SFU.

[0239] The probe request frame can be simply referred to as the probe request, and the probe response frame can be simply referred to as the probe response.

[0240] The format of the messages involved in the embodiments of this application will be described exemplarily below. Referring to Table 0-1 or 1-1, these are terminal online / offline indication and reporting messages. The parameters corresponding to each terminal online / offline indication and reporting message are different, indicated by a mask. Specifically, terminal detection and authentication reporting messages contain sequence numbers 2-4 and 7-9; terminal connection information reporting messages contain sequence numbers 2-4 and 8-11; terminal online / offline reporting messages contain sequence numbers 2-3 and 12; terminal detection and authentication reply indication messages contain sequence numbers 2-3 and 5; terminal online messages contain sequence numbers 2-3, 6, 12, and 8-9; virtual user creation messages contain sequence numbers 2-4, 6, and 8-11; and terminal deletion messages contain sequence numbers 2-3. Table 1-1 is only an example; the message types or message states corresponding to different values ​​can be configured according to requirements, and this embodiment of the application does not limit this.

[0241] Table 0-1

[0242] Table 1-1

[0243] Referring to Figure 3, this is a flowchart of a communication method provided in an embodiment of this application.

[0244] S301, the SFU that receives the probe request frame can send a probe request reporting message to the MFU. The probe request reporting message carries the probe request frame it received from the STA and performance parameters. The probe request reporting message can also be called a probe message reporting message, or simply a probe reporting message (see Table 1-1), or other names are not specifically limited in this application.

[0245] In one possible implementation, when the SFU that receives the probe request frame sends the received probe request frame and performance parameters to the MFU, it can carry the received probe request frame and performance parameters in a Wi-Fi Management and Control Interface (WMCI) message. For example, the aforementioned probe request reporting message can be carried in a WMCI message.

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

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

[0248] Table 1-2

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

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

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

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

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

[0254] Table 1-3

[0255] Each message type can carry 16 parameters. Please refer to the message definition for a detailed explanation of the parameter sequence.

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

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

[0258] For example, the probe request frames and performance parameters received by the SFU can be carried in the message content field of the WMCI message.

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

[0260] S302, the MFU determines the SFU to respond to the probe request frame based on the performance parameters sent by the SFU. In other words, it determines the SFU to send the probe response to the SFU.

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

[0262] For example, the SFU used to respond to probe request frames can be selected based on the load of the SFU. Specifically, the MFU can select the SFU with the lowest load as the SFU used to respond to probe request frames. For instance, the MFU receives probe request frames and load information from SFU1 through SFU3 respectively. Then, it determines whether the probe request frames sent by SFU1, SFU2, and SFU3 originate from the same site; and determines the load of SFU1 based on the load information sent by SFU1; determines the load of SFU2 based on the load information sent by SFU2; and determines the load of SFU3 based on the load information sent by SFU3. If the probe request frames sent by SFU1, SFU2, and SFU3 originate from the same station (for example, the probe request frames sent by the three to the MFU are probe request frames sent by the STAs received by each of them), and the load of SFU1 is less than the load of SFU2 and the load of SFU3 is less than the load of SFU3, then the MFU can determine that SFU1 is the SFU used to respond to the probe request frames.

[0263] In another possible example, the performance parameters sent by the SFU to the MFU may include the received signal strength indication (RSSI) of the Wi-Fi signals received by the SFU from the STA. Specifically, the SFU can measure the RSSI of the Wi-Fi signals it receives from the STA. It can be understood that RSSI reflects the communication performance of the channel or link; a higher RSSI indicates higher communication performance.

[0264] For example, the MFU can select the SFU to respond to the probe request frame based on the RSSI of the Wi-Fi signal received by the SFU from the STA. Specifically, the MFU can select the SFU with the highest RSSI as the SFU to respond to the probe request frame. For example, consider two SFUs, SFU1 and SFU2. The MFU can receive the probe request frame sent by SFU1 and the RSSI of the Wi-Fi signal received by SFU1 from the STA, as well as the probe request frame sent by SFU2 and the RSSI of the Wi-Fi signal received by SFU1 from the STA. Then, it determines whether the probe request frame sent by SFU1 and the probe request frame sent by SFU2 originate from the same site; and it determines whether the RSSI of the Wi-Fi signal received by SFU1 from the STA is greater than the RSSI of the Wi-Fi signal received by SFU2 from the STA. If the probe request frames sent by SFU1 and SFU2 originate from the same site, and the RSSI of the Wi-Fi signal received by SFU1 from the STA is greater than the RSSI of the Wi-Fi signal received by SFU2 from the STA, then MFU can determine that SFU1 is the SFU used to respond to the probe request frames.

[0265] In another possible example, the performance parameters sent by the SFU to the MFU may include the SFU's own load information and the RSSI of the Wi-Fi signal received by the SFU from the STA. The MFU can comprehensively consider the SFU's own load information and the RSSI of the Wi-Fi signal received by the SFU from the STA to determine the SFU to be used in response to the probe request frame. In one example, at least one SFU whose RSSI of the Wi-Fi signal received by the STA is greater than a preset strength threshold can be identified, and then the SFU with the lowest load among these at least one SFU can be identified as the SFU to be used in response to the probe request frame. In another example, one or more SFUs whose load is less than a preset load threshold can be identified, and then the SFU with the highest RSSI of the Wi-Fi signal received by the STA among these one or more SFUs can be identified as the SFU to be used in response to the probe request frame.

[0266] As an example, the probe request reporting message includes fields numbered 2-4 and 7-9 in Table 1-1. See Table 2-1 for details. In Table 2-1, the performance parameter is based on RSSI. It can also be replaced with load or load + RSSI.

[0267] Table 2-1

[0268] As another example, the format of the probe request reporting message can also be as shown in Table 2-2.

[0269] Table 2-2 uses RSSI as an example of a performance parameter. In some implementation scenarios, the performance parameter uses load information, and RSSI can be replaced with load information. In other implementation scenarios, the performance parameter uses load information + RSSI, in which case a row for load information can be added to Table 2.

[0270] In some possible implementations, the AP index, which may be the AP ID, may not be carried in the probe request message but may be carried in the WMCI header.

[0271] Table 2-2

[0272] Therefore, using the above scheme, the SFU used to respond to the probe request frame can be determined, taking SFU1 as an example. The SFU used to respond to the probe request frame (SFU1) sends a probe response frame to the STA, while other SFUs do not send probe response frames to the STA, realizing single-point online access for the STA and avoiding online conflicts caused by multiple SFUs having the same BSSID.

[0273] S303, the MFU can send a first probe response indication frame to the SFU1. The first probe response indication frame instructs the SFU1 to reply with a probe response message to the STA.

[0274] S304, the MFU can send a second probe response indication frame to other SFUs. The second probe response indication frame indicates that the SFU does not respond to the STA with a probe response message. The aforementioned probe response indication frames (first probe response indication frame, second probe response indication frame) can also be called probe response indication messages or terminal probe response indication messages, or other names can be used. This application embodiment does not limit this.

[0275] It should be noted that this application does not impose a specific restriction on the order of S303 and S304. For example, S304 can precede S303, or S303 can precede S304, and the MFU can send probe response indication frames to each SFU at the same time.

[0276] For example, the probe response indication frame can be carried in a WMCI message, such as in the message content field of the WMCI message.

[0277] As an example, the message format of the probe response indication frame is shown in Table 3. Referring to Table 3, when Rsp Flag = 0, it can be understood as representing the second probe response indication frame; when Rsp Flag = 1, it can be understood as representing the first probe response indication frame.

[0278] Table 3

[0279] S305, SFU1 sends a probe response frame to the STA. Other SFUs do not send probe response frames to the STA.

[0280] In an FTTR deployment scenario, multiple SFUs deployed in a subnet with the same BSSID will all receive authentication request frames from the STA. Therefore, multiple SFUs may send authentication response frames to the same STA, leading to conflicts and affecting site uptime.

[0281] In some embodiments, to avoid the above situation, each SFU that receives an authentication request frame sends the received authentication request frame and performance parameters representing the communication performance between the SFU and the STA to the MFU. The MFU can determine the SFU to respond to the authentication request frame based on the performance parameters sent by the SFU.

[0282] Referring to Figures 4A and 4B, these are schematic diagrams of the authentication process in a communication method provided in an embodiment of this application.

[0283] In step S401, the SFU that receives the authentication request frame can send an authentication request reporting message to the MFU. The authentication request reporting message carries the received authentication request frame and performance parameters. This message can also be called an authentication message reporting message or a terminal authentication reporting message, and other names are not specifically limited in this application.

[0284] In one possible implementation, when the SFU that receives the authentication request frame sends the received authentication request frame and performance parameters to the MFU, it can carry the received authentication request frame and performance parameters in a WMCI message. For example, the aforementioned authentication request reporting message can be carried in a WMCI message.

[0285] For example, the probe request frames and performance parameters received by the SFU can be carried in the message content field of the WMCI message.

[0286] S402, the MFU determines the SFU to respond to the authentication request frame based on the performance parameters sent by the SFU. In other words, it determines the SFU to send the authentication response to the SFU.

[0287] For example, the performance parameters sent by the SFU to the MFU may include the SFU's own load information and / or the RSSI of the Wi-Fi signal received by the SFU from the STA.

[0288] As an example, the authentication request reporting message includes fields numbered 2-4 and 7-9 in Table 1-1. See Table 4-1 for further details. In Table 4-1, the performance parameter is RSSI as an example. It can also be replaced with load or load + RSSI.

[0289] Table 4-1

[0290] As another example, the format of the probe request reporting message can also adopt the format shown in Table 5. Table 5 uses RSSI as the performance parameter as an example. In some implementation scenarios, the performance parameter uses load information, and RSSI can be replaced with load information. In other implementation scenarios, the performance parameter uses load information + RSSI, in which case a row of load information can be added to Table 5.

[0291] Table 5

[0292] Therefore, using the above scheme, the SFU used to respond to the probe request frame can be determined, taking SFU1 as an example. The SFU used to respond to the probe request frame (SFU1) sends an authentication response frame to the STA, while other SFUs do not send authentication response frames to the STA, realizing single point of access for the STA and avoiding access conflicts caused by multiple SFUs having the same BSSID.

[0293] S403, MFU can send a first online indication message to SFU1. The first online indication message is used to instruct SFU1 to reply with an authentication response message to STA.

[0294] In S404a, the MFU can send a second online indication message to other SFUs. This second online indication message instructs other SFUs not to reply to the STA with an authentication response message, or instructs other SFUs to close the communication channel (or transceiver channel) with the STA. Therefore, other SFUs will neither receive nor send information to the STA. It should be noted that if the second online indication message instructs other SFUs to close the communication channel with the STA, since the communication channel is already closed, other SFUs will not reply to the STA with an authentication response frame. This can also be understood as the second online indication message indirectly instructing other SFUs not to reply to the STA with an authentication response frame.

[0295] The online indication information can also be called an online indication frame, an online indication information frame, an authentication response indication frame, or an authentication response indication message. Other names may also be used, such as the first indication frame or the first indication information frame. This application does not make any specific limitation in this regard.

[0296] The authentication request frame can be simply referred to as the authentication request, and the authentication response frame can be simply referred to as the authentication response.

[0297] It should be noted that this application does not impose a specific restriction on the order of S403 and S404. For example, S404 can be earlier than S403, or S403 can be earlier than S404. The MFU can also send online indication information to each SFU at the same time, that is, send the first online indication information to SFU1 and send the second online indication information to other SFUs at the same time.

[0298] For example, the online indication information can be carried in a WMCI message, such as in the message content field of the WMCI message.

[0299] The MFU can also select an available AID in the network to assign to the STA. An AID is a unique identifier assigned by the MFU across the entire network to identify the STA. Multiple AIDs exist within an MFU, such as those configured manually or intelligently.

[0300] In one possible implementation, the first online indication information can also be used to instruct SFU1 to create user information for the STA. For example, SFU1 stores the STA's AID and authentication information. Exemplarily, the first online indication information carries the STA's AID and authentication information (or an authentication request frame).

[0301] It should be noted that the online instruction message can also be called the terminal online message, or other names may be used. This application embodiment does not limit this.

[0302] As an example, the online indication message includes fields with sequence numbers 2-3, 6, 12, and 8-9 from the terminal online message in Table 1-1, as shown in Table 6-1. When Online Status = 0, it indicates the first online indication. When Online Status = 1, it indicates a virtual online status, indicating the disconnection of the communication channel with the site, such as the second or third online indication.

[0303] Table 6-1

[0304] As another example, the format of the online indication information can be seen in Table 6-2. Referring to Table 6-2, when Online Status = 0, it indicates the first online indication information, which can instruct the SFU to reply with an authentication response frame. Optionally, Online Status = 0 can also instruct the creation of user information. When Online Status = 1, it indicates the second online indication information, which can instruct the SFU not to reply with an authentication response frame. Optionally, Online Status = 1 can also instruct the closure of the communication channel with the STA.

[0305] Table 6-2

[0306] As another example, the format of the online indication information can be seen in Table 7. Referring to Table 7, when Online Status = 0 and user in = 1, it indicates the first online indication information, which can instruct the SFU to reply with an authentication response frame. When Online Status = 1 and user in = 1, it indicates the second online indication information, which can instruct the SFU not to reply with an authentication response frame. Optionally, Online Status = 1 can also instruct the communication channel with the STA to be closed.

[0307] Table 7

[0308] In some implementation scenarios, to achieve seamless roaming, other SFUs can create user information for the STA, facilitating subsequent STA switching to other SFUs. Optionally, the MFU does not execute S404a, but instead executes S404b, as shown in Figure 4B. In S404b, the MFU sends a third online indication message to other SFUs. The third online indication message instructs other SFUs not to reply to the STA with an authentication response frame or to close the communication channel with the STA. It should be noted that if the third online indication message instructs other SFUs to close the communication channel with the STA, since the communication channel is already closed, other SFUs will not reply to the STA with an authentication response frame. This can also be understood as the third online indication message indirectly instructing other SFUs not to reply to the STA with an authentication response frame. The third online indication can also be used to instruct other SFUs to create user information for the STA. The third online indication message can carry the authentication request frame sent by the STA and the STA's AID.

[0309] Optionally, the third online indication information can also reuse the format of the online indication information shown in Table 7. Referring to Table 7, when Online Status = 0 and user in = 1, it indicates the first online indication information, which can instruct the SFU to reply with an authentication response frame. When Online Status = 1 and user in = 1, it indicates the third online indication information, which can instruct the SFU not to reply with an authentication response frame and to perform a user creation operation. Optionally, Online Status = 1 can also instruct the closure of the communication channel with the STA.

[0310] As another example, the format of the online indication information can be seen in Table 8. Referring to Table 8, when Online Status = 0, it indicates the first online indication information, which can instruct the SFU to reply with an authentication response frame. When Online Status = 1, it indicates the third online indication information, which can instruct the SFU not to reply with an authentication response frame. Optionally, Online Status = 1 can also instruct the closure of the communication channel with the STA. In this example, the SFU will create user information by default as soon as it receives the online indication information. In another possible implementation, the online indication information can also indicate whether to perform a user creation operation by checking whether the payload field or the AID field is empty.

[0311] Table 8

[0312] S405, SFU1 sends an authentication response frame to the STA. Other SFUs do not send authentication response frames to the STA.

[0313] In some possible implementation scenarios, after receiving the authentication response frame, the STA sends an association request frame to SFU1. SFU1 then sends an association response frame to the STA. Since the other SFUs have closed their communication channels with the STA, they will not receive the STA's association request frame, nor will they send an association response frame. A four-way handshake process then occurs between the STA and SFU1 to obtain the key used for communication between the two parties.

[0314] In some embodiments, the MFU can determine whether uplink and downlink encryption has been enabled in the entire network. If not, the MFU can enable uplink and downlink encryption in the entire network according to the link layer specifications for encryption of subsequent key transmissions.

[0315] In some possible implementations, in order to enable rapid roaming handover for subsequent STAs, other SFUs may be allowed to obtain the association request frame in advance, and / or the key for communication between the STA and the SFU.

[0316] Referring to Figures 5A and 5B, a schematic flowchart of a communication method provided in an embodiment of this application is shown. The flowcharts in Figures 5A and 5B can also be referred to as a virtual online process or a virtual initialization process.

[0317] S501, SFU1 sends an association request frame from the STA to the MFU. Optionally, it can also send the key for communication with the STA to the MFU.

[0318] For example, SFU1 sends WMCI message 1 to MFU. WMCI message 1 includes an association request frame from STA and may also include a key for communication with STA.

[0319] SFU1 can encrypt the key and send it to MFU. The encrypted key can be called key information or other names, and this application embodiment does not make specific limitations.

[0320] For example, SFU1 can send a virtual information reporting message (also known as a terminal connection information reporting message) to MFU. The terminal connection information reporting message may include fields numbered 2 to 4 and 8 to 11 in Table 1-1.

[0321] S502a, the MFU sends an association request frame to other SFUs. Optionally, it can also send a key to other SFUs.

[0322] For example, the MFU sends WMCI message 2 to other SFUs. WMCI message 2 includes an association request frame from the STA and may also include a key for communication with the STA.

[0323] For example, the MFU sends a virtual user creation message to other SFUs, as shown in Figure 5A. The virtual user creation message is carried in WMCI message 2. The virtual user creation message includes an association request frame from the STA. Optionally, the virtual user creation message may also include a key. The virtual user creation message may use other names, such as "first message," which is not limited in this embodiment. The virtual user creation message instructs other SFUs to create a virtual user for the STA. In some implementation scenarios, other SFUs belong to the same group as SFU1, or all other SFUs are managed by the MFU.

[0324] As an example, the format of a virtual user creation message can be found in Table 9-1.

[0325] Table 9-1

[0326] As another example, the virtual user creation message includes fields numbered 2–4, 6, and 8–11 in Table 1-1. See Table 9-2 for details.

[0327] Table 9-2

[0328] In some possible implementation scenarios, the MFU can also send association request frames from the STA and the STA's AID to other SFUs. For example, see Figure 5B. In S502b, the MFU sends a virtual user creation message to other SFUs. The virtual user creation message includes an association request frame from the STA, a key (encrypted key information), an association request frame from the STA, and the STA's AID. For example, the MFU sends a WMCI message 2 to other SFUs. The WMCI message 2 includes the virtual user creation message.

[0329] As an example, the format of a virtual user-created message can be seen in Table 10.

[0330] Table 10

[0331] S503: After completing the virtual user creation for the STA, other SFUs send a virtual user creation completion message to the MFU. This virtual user creation completion message can be carried in a WMCI message.

[0332] As an example, the message format for a virtual user creation completion message is shown in Table 11-1.

[0333] Table 11

[0334] In some embodiments, after other SFUs create virtual users for STAs, it is determined that the uplink and downlink encryption functions of the entire network are enabled at this time. The uplink and downlink encryption functions of the entire network can be disabled, for example, by sending an instruction to each SFU to disable the encryption function.

[0335] In some possible implementation scenarios, during the STA go-live phase, if the MFU does not instruct other SFUs to create a user and the other SFUs do not obtain the authentication request frame and AID, such as executing the process in Figure 4A, then to avoid re-authentication when the STA roams to another SFU, the process in Figure 5B can be executed. The MFU sends the authentication request frame and AID to other SFUs in the virtual user creation message, so that the other SFUs create a virtual user for the STA, as shown in Figure 6A. This avoids re-executing the authentication process, association process, and four-way handshake process when the STA roams to another SFU, reducing handover latency.

[0336] In other possible implementation scenarios, during the STA go-live phase, if the MFU instructs other SFUs to create a user and the other SFUs also obtain the authentication request frame and AID, such as executing the process in Figure 4B, then the process in Figure 5A can be executed. The MFU will no longer need to send the authentication request frame and AID to other SFUs in the virtual user creation message, so that other SFUs can create a virtual user for the STA, as shown in Figure 6B. This avoids re-executing the authentication process, association process, and four-way handshake process when the STA roams to switch to another SFU, reducing handover latency.

[0337] In some possible implementations, if an SFU fails to create a virtual user for a STA, it can report a creation failure message to the MFU. The MFU will then issue a virtual user reconstruction message. If the number of times a virtual user creation fails for a STA exceeds a threshold, the STA can be removed from the network.

[0338] In some possible implementations, each message in this application embodiment has an N / ACK mechanism. If the sender does not receive an ACK or receives a NACK, it can retransmit the message. Furthermore, each message involved in this application embodiment can execute a token verification mechanism to ensure message security and prevent message tampering.

[0339] In one possible application scenario, the roaming handover process of the STA in conjunction with the above embodiments may include the following processes, as shown in Figures 7A and 7B: initialization process, virtual initialization, information synchronization, and link switching. Figure 7A illustrates the initial online status of the STA at SFU1, followed by link switching to SFU2. As shown in Figure 7A, the WMCI-based collaborative roaming scheme mainly includes four aspects of processing: roaming configuration information synchronization, network information synchronization, terminal online processing, and terminal roaming processing.

[0340] During the initialization process: The STA goes live by executing the scanning process, authentication process, association process, and four-way handshake process. In the initialization process, the SMF and SFU receive the STA's initialization information, and the corresponding SFU responds to the STA's request messages. For example, the scanning process can be seen in Figure 3, and the authentication process can be seen in Figures 4A and 4B.

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

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

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

[0344] In some possible scenarios, the site may go offline. The following describes the process for handling a site going offline.

[0345] Taking the currently associated SFU1 of the site as an example. See Figure 8, which is a schematic diagram of the site offline processing flow in the communication method provided in the embodiment of this application.

[0346] S801, SFU1 determines that the site is offline, and SFU1 sends an offline event reporting message to MFU. The offline event reporting message (also known as the offline reporting message or the offline event reporting message) is used to indicate that the site has gone offline from SFU1.

[0347] For example, offline event reporting messages include the site's identifier, such as an AID.

[0348] As an example, offline event reporting messages may include fields numbered 2-3 and 12 in Table 1-1.

[0349] As another example, offline event reporting messages (offline reporting messages) can adopt the format shown in Table 12.

[0350] Table 12

[0351] S802, MFU sends a terminal deletion instruction message (or terminal deletion message or user deletion instruction message) to SFU1. The terminal deletion instruction message is used to indicate the deletion of user information of the site.

[0352] S803, the MFU sends a terminal deletion instruction message to other SFUs (meaning SFUs other than SFU1), the terminal deletion instruction message being used to instruct the deletion of user information from the site. Furthermore, the MFU can reclaim AIDs.

[0353] For example, the deletion terminal instruction message includes the site's identifier, such as an AID.

[0354] As an example, the deletion terminal instruction message may include fields numbered 2 to 3 in Table 1-1.

[0355] As another example, the deletion terminal instruction message can be in the format shown in Table 13.

[0356] Table 13

[0357] After completing the deletion of user information, SFU1 sends a message to MFU indicating that the user has been successfully deleted.

[0358] S805, after other SFUs complete the deletion of user information, they send a message to the MFU indicating successful deletion of the user (which is a message indicating completion of deletion of the user).

[0359] For example, removing the user-instructed completion message from including the site's identifier, such as an AID.

[0360] As an example, the deletion of a user's completion message can be formatted as shown in Table 14.

[0361] Table 14

[0362] The "Field Description" in Table 1-14 above is used to understand the field names. Parameters in all tables except Table 1-2 can be carried over to the message content field in Table 1-2 as optional or required fields.

[0363] Figure 9 is a structural diagram of the communication device provided in an embodiment of this application. This device can be implemented as part or all of a device through software, hardware, or a combination of both, and is applied to an MFU or SFU. The device provided in this embodiment can implement some of the processes described in the above-described method of this application. The device includes a transmitting module 901 and a receiving module 902. Optionally, it also includes a processing module 903.

[0364] In one possible implementation scenario, the device is applied to an MFU. The various modules described above work together to implement the method flow executed by the MFU in any of the embodiments corresponding to Figures 3-8.

[0365] In one possible embodiment, the receiving module 901 is configured to receive an association request frame from a site sent by a first SFU, and a key used for communication between the first SFU and the site, wherein the first SFU is the SFU currently associated with the site, and the association request frame is used for the site to associate with the first SFU. The sending module 902 is configured to send the association request frame and the key to a second SFU.

[0366] In another possible embodiment, the receiving module 901 is configured to receive an offline event reporting message from the first SFU, the offline event reporting message being used to indicate that the site is offline; the sending module is configured to send a delete terminal indication message to the second SFU, the delete terminal indication message being used to indicate information for deleting the site.

[0367] In another possible implementation scenario, the device is applied to the first SFU. The various modules described above work together to implement the method flow executed by the first SFU in any of the embodiments corresponding to Figures 3-8.

[0368] In one possible embodiment, the receiving module 901 is configured to obtain an association request frame (or reassociation request frame) from the site, and a key used for communication with the site, wherein the association request frame is used for the site to associate with the first SFU; the sending module 902 is configured to send the association request frame (or reassociation request frame) and the key to the main optical network unit (MFU).

[0369] Among them, the reassociation request frame can be simply referred to as the reassociation request.

[0370] In another possible embodiment, the processing module 903 is used to determine that the site is offline; the sending module 902 is used to send an offline event reporting message to the main optical network unit (MFU), the offline event reporting message being used to indicate that the site is offline from the first SFU.

[0371] In another possible implementation scenario, the device is applied to a second SFU. The various modules described above work together to implement the method flow executed by the second SFU in any of the embodiments corresponding to Figures 3-8.

[0372] In one possible embodiment, the receiving module 901 is configured to receive an association request frame from a site in a main optical network unit (MFU), and a key negotiated between the site and a first SFU for communication, wherein the first SFU is the SFU currently associated with the site, and the association request frame is used for the site to associate with the first SFU; the processing module 903 is configured to create a virtual user for the site based on the association request frame and the key.

[0373] In another possible embodiment, the receiving module 901 is used to receive a deletion terminal indication message from the MFU, the deletion terminal indication message being used to indicate the deletion of the site information; the processing module 903 is used to delete the site information.

[0374] For a detailed description of the communication process of the communication device shown in Figure 9, please refer to the descriptions in the various embodiments in Figures 3-8 above, which will not be repeated here.

[0375] This application also provides a device 100. As shown in FIG10, 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 via the bus 102. 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 device 100.

[0376] Bus 102 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one line is used in Figure 10, but this does not imply that there is only one bus or one type of bus. Bus 102 can include pathways for transmitting information between various components of device 100 (e.g., memory 106, processor 104, communication interface 108).

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

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

[0379] The memory 106 stores executable program code, and the processor 104 executes the executable program code to implement the communication method. That is, the memory 106 stores program instructions for executing the aforementioned communication method.

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

[0381] In one possible embodiment, the processor 104 executes executable program code in the memory 106 to implement the method flow executed by the first SFU in any of the embodiments corresponding to FIG3-FIG8.

[0382] In another possible embodiment, the processor 104 executes executable program code in the memory 106 to implement the method flow executed by the second SFU in any of the embodiments corresponding to FIG3-FIG8.

[0383] In another possible implementation, the processor 104 executes executable program code in the memory 106 to implement the method flow executed by the MFU in any of the embodiments corresponding to Figures 3-8.

[0384] This application also provides a computer program product, which includes program instructions stored in a computer-readable storage medium. A processor reads the program instructions from the computer-readable storage medium and executes the program instructions, causing the processor to execute the MFU execution flow in Figures 2-8, or the SFU1 execution flow in Figures 2-8, or the execution flow of other SFUs in Figures 2-8.

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

[0386] One embodiment of this application provides a computer-readable medium for storing a computer program, the computer program including instructions for executing method steps performed by the MFU in the method embodiments corresponding to FIG2-FIG 8, or instructions for executing method steps performed by the SFU1 in the method embodiments corresponding to FIG2-FIG 8, or instructions for executing method steps performed by other SFUs in the method embodiments corresponding to FIG2-FIG 8.

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

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

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

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

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

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

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

Claims

1. A communication method, characterized in that, include: The main optical network unit (MFU) receives an offline event reporting message from the first SFU, the offline event reporting message being used to indicate that the site is offline; The MFU sends a terminal deletion instruction message to the second SFU, the terminal deletion instruction message being used to indicate the deletion of the site information.

2. The method as described in claim 1, characterized in that, Also includes: Receive the terminal deletion success indication message sent by the second SFU.

3. The method as described in claim 1 or 2, characterized in that, The method further includes: The MFU sends the terminal deletion instruction message to the first SFU.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: The MFU deletes the information from the site.

5. The method according to any one of claims 1-3, characterized in that, The method further includes: The MFU reclaims the site's identifier, which uniquely identifies the site within the network.

6. The method as described in claim 5, characterized in that, The method further includes: When the site goes online, the MFU assigns the site's identifier.

7. The method as described in claim 6, characterized in that, The method further includes: The MFU sends the site's identifier to the SFU in the network.

8. The method as described in claim 7, characterized in that, The MFU sends the site's identifier to the SFU in the network, including: The MFU sends an online indication message to the SFU in the network, and the online indication message includes the identifier of the site.

9. A communication method, characterized in that, include: The first sub-optical network unit (SFU) determines that the site is offline; The first SFU sends an offline event reporting message to the main optical network unit (MFU), the offline event reporting message being used to indicate that the site is offline from the first SFU.

10. The method as described in claim 9, characterized in that, The method further includes: The first SFU receives a terminal deletion instruction message from the MFU, the terminal deletion instruction message being used to instruct the first SFU to delete the information of the site.

11. The method as described in claim 10, characterized in that, The method further includes: The first SFU sends a terminal deletion success indication message to the MFU.

12. The method according to any one of claims 9-11, characterized in that, The method further includes: When the site comes online, the first SFU receives the site's identifier from the MFU, and the site's identifier uniquely identifies the site in the network.

13. The method as described in claim 12, characterized in that, The first SFU receives the identifier of the site from the MFU, including: Receive an online indication message from the MFU, the online indication message including the identifier of the site.

14. A communication device, characterized in that, Applied to the main optical network unit (MFU), including: A receiving module is configured to receive an offline event reporting message from the first SFU, wherein the offline event reporting message is used to indicate that the site is offline; The sending module is used to send a terminal deletion indication message to the second SFU, the terminal deletion indication message being used to indicate the deletion of the site.

15. The apparatus as claimed in claim 14, characterized in that, The receiving module is further configured to: Receive the terminal deletion success indication message sent by the second SFU.

16. The apparatus as claimed in claim 14 or 15, characterized in that, The sending module is further configured to: Send the terminal deletion instruction message to the first SFU.

17. The apparatus according to any one of claims 14-16, characterized in that, The device further includes: The processing module is used to delete the information of the site.

18. The apparatus according to any one of claims 14-17, characterized in that, The device further includes: A processing module is used to reclaim the identifier of the site, which uniquely identifies the site in the network.

19. The apparatus as claimed in claim 18, characterized in that, The processing module is further configured to: When the site goes online, an identifier for the site is assigned to it.

20. The apparatus as claimed in claim 19, characterized in that, The sending module is further configured to: Send the site's identifier to the SFU in the network.

21. The apparatus as claimed in claim 20, characterized in that, The sending module is specifically used for: Send an online indication message to the SFU in the network. The online indication message includes the identifier of the site.

22. A communication device, characterized in that, Applied to the first sub-optical network unit (SFU), including: The processing module is used to determine when a site is offline; The sending module is used to send an offline event reporting message to the main optical network unit (MFU), the offline event reporting message being used to instruct the station to go offline from the first SFU.

23. The apparatus as claimed in claim 22, characterized in that, The device further includes: The receiving module is configured to receive a deletion terminal indication message from the MFU, the deletion terminal indication message being used to instruct the first SFU to delete the information of the site.

24. The apparatus as claimed in claim 23, characterized in that, The sending module is further configured to: Send a terminal deletion success indication message to the MFU.

25. The apparatus according to any one of claims 22-24, characterized in that, The device further includes: A receiving module is configured to receive the site identifier from the MFU when the site comes online, the site identifier being uniquely identified in the network.

26. The apparatus as claimed in claim 25, characterized in that, The receiving module is specifically used for: Receive an online indication message from the MFU, the online indication message including the identifier of the site.

27. A communication device, characterized in that, The communication device includes a processor, a memory, and a communication interface; The processor is configured to execute program instructions in the memory to perform the processing functions in the communication method as described in any one of claims 1 to 8; The communication interface is used to communicate with the Sub-Optical Network Unit (SFU) in the network.

28. A communication device, characterized in that, The communication device includes a processor, a memory, and a communication interface; The processor is used to execute program instructions in the memory to perform the processing functions in the communication method as described in any one of claims 9 to 13; The communication interface is used to communicate with the main optical network unit (MFU).

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

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

Images