Mesh networking method, device and equipment based on PON (Passive Optical Network) and medium

Abstract

The invention relates to the technical field of passive optical network (PON), is applied to fiber to room (FTTR), enterprise-level fiber to room-Bus (FTTR-B) and broadband fusion terminal products, and particularly relates to a Mesh networking method, device and equipment based on PON and a medium, topology multicast messages are periodically sent by receiving target network equipment, and the topology multicast messages are transmitted by receiving the target network equipment. Determining host address information in the Mesh network according to a private mesh network protocol identifier in the topology multicast message, generating and sending an M1-stage message for the access point to request wireless configuration to the host according to the host address information in the Mesh network, receiving an M2-stage message replied by the host for the M1-stage message and used for the access point to request wireless configuration, and sending the M2-stage message to the host according to the M1-stage message. And the Mesh networking parameter synchronization is completed according to the AP wireless configuration parameter in the M2-stage message, so that the compatibility problem in the networking process of different Mesh protocols is avoided, the success rate of Mesh networking is effectively improved, and the user experience is improved.

Description

Technical Field

[0001] This invention relates to the field of PON passive optical fiber network technology, and is applied to Fiber to the Room (FTTR), Fiber to the Room-Business (FTTR-B) enterprise-level and broadband converged terminal products. In particular, it relates to a PON-based Mesh networking method, apparatus, equipment and medium. Background Technology

[0002] Mesh networking is a new type of wireless LAN networking method. Mesh networking functions include: onboarding, discovery, configuration synchronization, roaming, and backhaul optimization. Currently, mesh networking technology is widely used in network devices such as home gateways and WiFi routers, providing comprehensive network coverage for home wireless network environments and greatly improving the user's network experience.

[0003] However, in existing Mesh networks, slave devices connect to the Mesh network wirelessly or via wired connections, and the AP configuration synchronization from host to slave devices is achieved based on the 1905 Mesh protocol. However, different Mesh protocol processing mechanisms can lead to compatibility issues during this process, impacting the user experience. Therefore, how to avoid compatibility problems in networking with different Mesh protocols and improve the user experience is a pressing technical problem that needs to be solved. Summary of the Invention

[0004] Therefore, it is necessary to address the above-mentioned technical problems by providing a PON-based Mesh networking method, apparatus, device, and medium in this embodiment of the invention, which can avoid compatibility issues in the networking process of different Mesh protocols and improve the user experience.

[0005] A first aspect of this application provides a PON-based Mesh networking method, the PON-based Mesh networking method comprising: Receive topology multicast messages periodically sent by the target network device, wherein the topology multicast message includes a private mesh network protocol identifier, and the target network device includes a host and / or a sub-machine; Based on the private mesh network protocol identifier in the topology multicast message, determine the host address information in the mesh network; Based on the host address information in the Mesh network, an M1 phase message requesting access point wireless configuration is generated and sent to the host. The system receives an M2 phase message from the host in response to the M1 phase message, which is a request for access point wireless configuration. The M2 phase message includes AP wireless configuration parameters. The Mesh networking parameters are synchronized based on the AP wireless configuration parameters in the M2 phase message.

[0006] A second aspect of this application provides a PON-based Mesh networking device, the PON-based Mesh networking device comprising: A receiving module is used to receive topology multicast messages periodically sent by a target network device, wherein the topology multicast message includes a private mesh network protocol identifier, and the target network device includes a host and / or a sub-machine; The determination module is used to determine the host address information in the Mesh network based on the private mesh network protocol identifier in the topology multicast message; The generation module is used to generate and send an M1 phase message requesting access point wireless configuration to the host based on the host address information in the Mesh network. The configuration module is configured to receive an M2 phase message from the host in response to the M1 phase message, which is a request for wireless configuration of the access point, wherein the M2 phase message includes AP wireless configuration parameters; The networking module is used to synchronize Mesh networking parameters based on the AP wireless configuration parameters in the M2 phase message.

[0007] Thirdly, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the PON-based Mesh networking method as described in the first aspect.

[0008] Fourthly, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program, which, when executed by a processor, implements the PON-based Mesh networking method as described in the first aspect.

[0009] In summary, this invention provides a PON-based Mesh networking method, apparatus, device, and medium. It receives topology multicast messages periodically sent by target network devices. These topology multicast messages include a private mesh network protocol identifier. The target network devices include hosts and / or slave devices. Based on the private mesh network protocol identifier in the topology multicast message, the host address information in the mesh network is determined. Based on the host address information in the mesh network, an M1 phase message requesting access point wireless configuration is generated and sent to the host. The invention receives an M2 phase message from the host in response to the M1 phase message, also requesting access point wireless configuration. The M2 phase message includes AP wireless configuration parameters. Based on the AP wireless configuration parameters in the M2 phase message, mesh networking parameter synchronization is completed. Therefore, this application achieves intelligent protocol type identification by parsing the private mesh network protocol identifier in the topology multicast message and combines this with the transmission mechanism to complete AP parameter synchronization, thereby avoiding compatibility issues in the networking process of different mesh protocols, effectively improving the success rate of mesh networking, and enhancing the user experience. Attached Figure Description

[0010] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 This is a flowchart illustrating a PON-based Mesh networking method according to an embodiment of the present invention. Figure 2 This is a schematic diagram of a PON-based Mesh networking device according to an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0012] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0013] It should be understood that, when used in this specification and the appended claims, terms include indicating the presence of the described feature, integral, step, operation, element and / or component, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0014] It should also be understood that the terms used in this specification and the appended claims refer to any combination of one or more of the associated listed items and all possible combinations, and include such combinations.

[0015] As used in this specification and the appended claims, terms if can be interpreted in context as when... or once or in response to determination. Similarly, the phrase if determined or if matched to [described condition or event] can be interpreted in context as once determined or in response to determination or once matched to [described condition or event] or in response to matching to [described condition or event].

[0016] Furthermore, in the description of this invention and the appended claims, the terms first, second, third, etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0017] References to one or more embodiments described in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in one or more embodiments of the invention. Therefore, phrases appearing in different parts of this specification as referring to one embodiment, some embodiments, some other embodiments, and others do not necessarily refer to the same embodiment, but rather mean one or more, but not all, embodiments, unless otherwise specifically emphasized. The terms include, comprise, have, and variations thereof mean including but not limited to, unless otherwise specifically emphasized.

[0018] It should be understood that the sequence number of each step in the following embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0019] To illustrate the technical solution of the present invention, specific embodiments are described below.

[0020] See Figure 1 This is a flowchart illustrating a PON-based Mesh networking method according to an embodiment of the present invention. Figure 1 As shown, this PON-based Mesh networking method can be implemented through the following steps.

[0021] S101: Receive topology multicast messages periodically sent by the target network device, wherein the topology multicast message includes a private mesh network protocol identifier, and the target network device includes a host and / or a slave device.

[0022] In step S101, the target network device refers to all devices participating in the mesh network, including the host (responsible for network management and configuration synchronization) and / or the sub-machines that extend the coverage (accessing the host or other sub-machines to extend the network range). After startup, both the host and sub-machines actively and periodically send topology multicast messages to ensure that other devices in the network can discover them. A topology multicast message is a network message sent in multicast format. This message is received by all devices within the same network, rather than being sent to a single device. It is mainly used for self-introduction between devices and includes basic information such as device type (host / sub-machine), network identifier, and protocol version. It is the language for devices in the mesh network to discover each other. The private mesh network protocol identifier refers to a custom identifier field embedded in the topology multicast message, specifically represented by a TLV. This field allows sub-machines to identify the private protocol type used by the host.

[0023] In this embodiment, after the host or slave device powers on, it periodically sends topology multicast messages via a network interface (wireless WiFi or wired Ethernet) in a multicast manner. For example, the host sends a message every 30 seconds after startup, and the slave device sends a message every 20 seconds after startup, ensuring that newly connected devices can quickly discover the network. Through the above steps, subsequent receiving devices (such as slave devices) can clearly determine the protocol type of the network to which the sending device belongs, thereby achieving accurate protocol matching and solving compatibility issues.

[0024] S102: Determine the host address information in the Mesh network based on the private mesh network protocol identifier in the topology multicast message.

[0025] In step S102, the submachine continuously listens for topology multicast messages (from the host or other submachines) in the network and performs preliminary filtering based on the protocol type in the previously parsed private mesh network protocol identifier (TLV)—only retaining messages that match its own protocol type (excluding devices with incompatible protocols). The submachine further parses the filtered messages to confirm that the current message originates from the host, and then extracts the specific address from the host's address information subfield: IP address: used for TCP / UDP communication between the submachine and the host (e.g., sending configuration requests), typically a 4-byte IPv4 address (e.g., 192.168.1.1); MAC address: used as the host's physical address identifier for link-layer communication or address conflict detection, typically a 6-byte address (e.g., AA:BB:CC:DD:EE:FF). Finally, after obtaining the host address information, the validity of the host address information is verified by sending a small probe packet (such as an ICMP echo request, i.e., the ping command) to the host IP address. If a response packet is received from the host, the address is confirmed to be valid, the address is recorded, and the resolution process is terminated. If no response is received (possibly due to message transmission errors causing the address to be invalid), the system continues to listen for topology multicast messages sent by other hosts, re-extracts and verifies the host address information, so as to provide a basis for establishing communication with the host in the future (such as parameter synchronization).

[0026] In one embodiment of the invention, determining the host address information in the mesh network based on the private mesh network protocol identifier in the topology multicast message includes: The private mesh network protocol identifier in the topology multicast message is parsed to obtain the first mesh protocol type of the mesh network to which the target network device belongs. Determine whether the first Mesh protocol type is consistent with the second Mesh protocol type corresponding to the submachine itself; If the first Mesh protocol type is consistent with the second Mesh protocol type corresponding to the submachine itself, then the host address information in the Mesh network is obtained.

[0027] Specifically, when the slave device receives a topology multicast message from the target network device, it first extracts the private mesh network protocol identifier field from the message and parses it to determine the protocol type identifier used by the mesh network to which the target device belongs. Then, the slave device compares the parsed protocol type with its own supported protocol types. If they match, the host address information acquisition process is triggered; if they do not match, the multicast message is discarded to avoid networking errors caused by protocol incompatibility. For example, if the slave device discovers that the target network device uses an extended version of the IEEE 1905.1 protocol, while the slave device only supports the basic version, it will terminate subsequent networking operations to prevent configuration synchronization failures caused by protocol differences. The private mesh network protocol identifier refers to the field carried by the network device in the multicast message to identify the mesh protocol type. This can be implemented using a field in the TLV format where the type field has a private reserved value, and this field contains the mesh protocol version or standard information. The first Mesh protocol type refers to the communication protocol type used by the target network device during the Mesh networking process. This can be achieved by parsing the protocol identifier in the private mesh network protocol identifier, which can be, for example, a numerical code based on the IEEE 1905.1 protocol extension definition. The second Mesh protocol type refers to the Mesh protocol type supported by the slave device itself. This can be achieved through protocol configuration parameters pre-configured in the slave device firmware, which are loaded into memory during device initialization. Through the above technical solution, this application ensures that the slave device only establishes connections with hosts using the same Mesh protocol type, eliminating configuration synchronization errors caused by inconsistent protocol versions, improving the stability and device compatibility of the Mesh network networking process, and thus reducing network interruptions or reconfiguration operations caused by protocol conflicts.

[0028] In one embodiment of the invention, before obtaining host address information in the Mesh network, the following steps are included: Send a topology query message to the Mesh network to determine whether there are hosts in the Mesh network that meet the preset communication connection requirements; If it is determined that there is a host in the Mesh network that meets the preset communication connection requirements, then a topology response message is received from the host in the Mesh network in response to the topology query message. The topology response message is parsed to obtain the host address information in the Mesh network.

[0029] Specifically, when a slave device needs to join the Mesh network, it first broadcasts a topology query message carrying preset conditions to the network layer. Upon receiving the query message, host devices in the network match their communication parameters with the preset conditions. If the requirements are met, they return a topology response message containing their own address. The slave device, by parsing the host's response message, can match the address of the host with the best signal quality and establish a targeted communication connection. For example, if the preset condition requires the Mesh protocol version to be 2.0, only hosts running that version will respond to the query, thus avoiding network failure due to protocol incompatibility. The topology query message is a network probe message used to actively detect available hosts in the Mesh network. It can be implemented using the LLDP protocol or a custom broadcast message format. Periodically sending such messages allows for dynamic detection of network topology changes. The preset communication connection requirements refer to pre-defined host access conditions, which may include signal strength thresholds, protocol version compatibility, or device authentication status. Setting these conditions allows for the selection of host devices that conform to the network specifications. Topology response messages refer to the host's response data packets to topology query messages. Specifically, they can be encapsulated in TLV format, containing the host's MAC address, IP address, and protocol support list. Parsing these responses allows for accurate acquisition of the host's network identification information. Through the above technical solution, this application enables accurate discovery and protocol matching of host devices during Mesh networking, avoiding networking errors caused by passively receiving outdated topology information. Furthermore, through dynamic filtering of preset communication conditions, it ensures optimal matching between slave devices and hosts in terms of protocol compatibility, signal quality, and other key parameters, thereby improving networking success rate and network stability.

[0030] In this embodiment, by determining the host address information in the Mesh network based on the private mesh network protocol identifier in the topology multicast message, the host identity identifier and address information can be effectively bound through the private mesh network protocol identifier. This enables the slave machine to efficiently and accurately locate the host and obtain the communication address, avoiding the erroneous sending of configuration requests to other slave machines, ensuring the reliability of the address information, thereby ensuring the accuracy of subsequent communication objects and improving networking efficiency.

[0031] S103: Based on the host address information in the Mesh network, generate and send an M1 phase message requesting access point wireless configuration to the host.

[0032] In step S103, the slave device needs to verify the availability of the acquired host address information to avoid sending messages to invalid addresses. This involves address type verification or role-based secondary verification. Taking address type verification as an example: if the host address is an IP address (e.g., 192.168.1.100), the slave device sends an address resolution request via ARP (IPv4) or NDP (IPv6) to confirm whether the host corresponding to that IP address is online (whether it can receive an ARPReply / NDP response); if the host address is a MAC address (e.g., AA:BB:CC:DD:EE:FF), it directly verifies whether the MAC address is within the current wireless coverage area via the data link layer (to avoid invalid transmission across network segments). M1 messages must conform to the Mesh protocol's TLV (Type-Length-Value) format to ensure that the host can correctly parse them. Taking Wi-FiEasyMesh's M1 message as an example, its structure typically includes three layers: a frame header, a core TLV segment, and a checksum. Mesh networks need to prevent messages from being eavesdropped on or forged, so M1 messages must undergo secure processing. If the slave device and the host have not yet established a long-term key, the core TLV segment of the M1 message is usually encrypted with AES-128 using a predefined public key of the Mesh protocol (such as EasyMesh's ProvisioningKey) (only the frame header is not encrypted to ensure routing). Some proprietary Mesh protocols will add a slave device certificate digest (such as the CA certificate hash value built into the device at the factory) to the M1 message. The host verifies the slave device by verifying the digest to confirm that the slave device is a legitimate device (to prevent unauthorized devices from forging M1 messages to access the network). The slave device then sends an M1 message via the same Mesh-dedicated frequency band as the host. This message is sent with high priority to ensure transmission even in congested wireless channels. If the slave device does not receive an M2 response message from the host within a preset time (e.g., 500ms), it automatically retransmits the M1 message (usually three times with gradually increasing intervals to avoid channel congestion). If this number of retransmissions is exceeded, the host is deemed unreachable, and the topology discovery process is retried. The M1 message in the M1 phase is the first active request message in the slave device's access process. Essentially, it's a configuration request frame / packet, its core function being to announce its identity to the host and request configuration parameters. It is a crucial trigger signal for the slave device to never connect to the host and be configured.

[0033] In one embodiment of the invention, before generating and sending an M1 phase message requesting access point radio configuration to the host, the process includes: Based on the host address information in the Mesh network, send an access point auto-configuration search message to the host; Receive an access point autoconfiguration response message from the host in response to the access point autoconfiguration search message; Obtain access point load information and access point link information in the MESH network; Based on the access point load information and the access point link information, the step of sending an M1 phase message requesting access point wireless configuration to the host is executed.

[0034] Specifically, during Mesh networking, the slave devices first initiate active probing based on the acquired host address information, verifying the host's responsiveness by sending access point auto-configuration search messages. Upon receiving a response message from the host, the slave device further collects operational status data of each access point in the current Mesh network, including load levels and link quality parameters. After comprehensive analysis of these parameters, the slave device, through encryption, can choose a time when the network load is relatively light and the link quality is optimal to send an M1 phase message to the host, thereby avoiding configuration synchronization operations under high load or weak signal environments and ensuring information security. For example, when an access point's CPU utilization exceeds 60% or its signal strength is below -70dBm, the slave device will delay sending the M1 message until the network status recovers to a preset threshold range. Access point auto-configuration search messages are network probe messages used to detect whether a host has auto-configuration capabilities. This can be achieved by sending a broadcast message with a specific format, which can carry the slave device identifier to establish a communication session. The access point auto-configuration response message refers to the host's response message to the search message. Specifically, it can be implemented using a unicast message containing host device capability information to confirm the host's availability status. Access point load information refers to indicators reflecting the current data processing pressure of the network access point. This can be quantified by statistically analyzing system parameters such as CPU utilization or memory usage, and is used to assess the network node's carrying capacity. Access point link information refers to data describing the quality of the wireless transmission channel. This can be characterized using parameters such as signal strength, bit error rate, or transmission delay, and is used to determine the stability of the wireless link. Through the above technical solutions, this application solves the configuration synchronization failure problem caused by excessive host load or poor wireless link quality in existing Mesh networking processes. By introducing a network status monitoring mechanism, the slave device can initiate configuration requests under optimal network conditions, significantly improving the success rate and efficiency of AP parameter synchronization, while reducing network resource waste caused by repeated attempts.

[0035] In this embodiment, by generating and sending an M1 phase message requesting wireless configuration to the host based on the host address information in the Mesh network, the security of information configuration transmission is ensured, unauthorized access is prevented, thereby improving the access efficiency of the Mesh network and enabling rapid networking of the Mesh network.

[0036] S104: Receive the host's reply to the M1 phase message, which is an M2 phase message for the access point to request wireless configuration, wherein the M2 phase message includes AP wireless configuration parameters.

[0037] In step S104, the slave device must first send the M1 phase message (e.g., via Mesh multicast address, or directly unicast to the discovered host address) and ensure the control link with the host is unobstructed (usually based on the Mesh control channel, separated from the data channel to ensure configuration messages are not interfered with by data traffic). The host must first parse the M1 message, verifying the slave device's identity (e.g., whether it is an allowed device model, whether it is on the whitelist), confirming protocol compatibility (e.g., the Mesh protocol supported by the slave device is consistent with the host), and then generating the M2 phase message. The slave device listens for the host's reply through the Mesh control port (e.g., a specific UDP port, or a dedicated control channel defined by the protocol). Since the M2 phase message contains sensitive configurations (e.g., keys), a reliable transmission mechanism (e.g., TCP, or UDP + acknowledgment and retransmission mechanism) is usually used to avoid message loss. The slave device first verifies the link layer legitimacy of the M2 phase message—checking whether the source MAC address of the message is the MAC address of the identified host (to prevent message forgery) and whether the check frame verification sequence (FCS) is correct (to exclude data corruption during transmission). If the verification fails, the message is discarded and a retransmission request is triggered. The AP wireless configuration parameters in the M2 phase message are usually encapsulated in a Type-Length-Value (TLV) format. The slave device needs to extract the corresponding AP wireless configuration parameters according to the TLV type code agreed in the protocol. Finally, it verifies whether the parsed AP wireless configuration parameters are valid and executable to avoid slave device malfunction due to host configuration errors. Common verification rules include: compatibility verification: if the slave device hardware only supports the 2.4G band, and the M2 phase message is configured with a 5G channel, the parameters are determined to be incompatible, triggering a parameter negotiation request; range verification: the channel must be within the legal range (2.4G channel 1~14, 5G channel 36~165), and the transmit power must be within the hardware maximum threshold (e.g., if the slave device's maximum transmit power is 20dBm, configuring it as 25dBm is invalid); logical verification: such as the encryption protocol and key length matching (WPA2-PSK requires a key length of 8~63 bytes, configuring it as 6 bytes is invalid), etc. If the verification passes, the parameter application phase begins. If the verification fails, the slave device sends an M2 parameter error response to the host, indicating the error type (e.g., channel not supported, invalid key length), and requests the host to regenerate the M2 phase message. This allows the host to write the valid AP wireless configuration parameters into the wireless driver module and Mesh protocol stack, completing hardware and software configuration synchronization. The M1 phase message is actively sent by the slave device, its core purpose being to initiate an access request to the host, carrying basic slave device identity information (such as slave device MAC address, supported Mesh protocol types, hardware model, etc.), essentially the slave device reporting to the host and requesting configuration.The M2 phase message is a passive response from the host, which is a reply to the M1 phase message request and a delivery of configuration. The core content is the AP wireless configuration parameters (the slave device must follow these parameters to access the Mesh and provide wireless services). It may also contain key information such as authentication results and encryption keys. The AP wireless configuration parameters include wireless SSID, password, channel, and encryption method information.

[0038] In one embodiment of the invention, receiving an M2 phase message from the host in response to the M1 phase message, for which the access point requests radio configuration, includes: Receive public key information and encrypted information sent by the host, wherein the encrypted information is obtained by performing encryption operation on the network configuration information in response to the M1 phase message based on the encryption key; The encrypted information is decrypted based on the public key information, and the decrypted encrypted information is filled into the management frame of the protocol message to generate an M2 phase message for the access point to request wireless configuration in response to the M1 phase message. The protocol message is generated based on a preset wireless LAN general standard.

[0039] Specifically, after the slave device receives the public key information and encrypted information sent by the host, it first uses the public key to decrypt the encrypted information to restore the network configuration information. For example, when the encrypted information is encrypted using the AES algorithm, decryption can be performed using the private key associated with the public key. After decryption, the network configuration information containing AP wireless configuration parameters is filled into the management frame of the protocol message according to the preset wireless LAN standard format. For example, channel parameters are written into the DSParameterSet field of the Beacon frame, and SSID information is written into the SSID field. The M2 stage message generated in this way satisfies the standardized communication requirements between devices and ensures the integrity and confidentiality of the configuration parameters during transmission. The public key information refers to the publicly distributed key data used in asymmetric encryption algorithms. Specifically, it can be implemented using a public key generated by the RSA algorithm, used to decrypt and verify the encrypted information, ensuring the legitimacy of data transmission. The encrypted information refers to the data set processed by the encryption algorithm. Specifically, the network configuration information can be encrypted using the AES algorithm, and secure data transmission is achieved through key pairs, preventing the configuration parameters from being tampered with or stolen during transmission. Protocol messages refer to data packets conforming to a standardized communication format. Specifically, they can be implemented using the management frame structure defined in the IEEE 802.11 standard, ensuring compatibility between devices from different manufacturers through a pre-defined universal wireless LAN standard. Management frames are message types used for network control information exchange, specifically encapsulated using Beacon or ProbeResponse frame structures, carrying decrypted configuration parameters through standardized fields. Through the above technical solution, this application achieves secure transmission of Mesh networking configuration information in an encrypted state. Simultaneously, the standardized protocol message encapsulation ensures that different Mesh protocol devices can correctly parse configuration parameters, solving the data parsing compatibility problem between cross-protocol devices and avoiding potential security risks caused by fixed keys.

[0040] In this embodiment, by receiving the M2 phase message (used by the access point to request wireless configuration) in response to the M1 phase message from the host, connection failures caused by configuration errors are reduced. This approach is compatible with the format requirements of M2 messages for different Mesh network protocols, thereby broadening the scope of Mesh networking and improving its accuracy.

[0041] S105: Complete the Mesh networking parameter synchronization based on the AP wireless configuration parameters in the M2 phase message.

[0042] In step S105, the AP configuration parameters in the M2 phase message are parsed, and the sub-machine wireless interface is called to set the parsed AP configuration parameters to complete the AP parameter network configuration synchronization. Specifically, the sub-machine's Mesh protocol stack (such as the Multi-AP protocol module in an embedded system) first locates the starting position of the AP wireless configuration parameter TLV in the frame structure of the M2 phase message (identified by the TLV type field, such as 0x0A representing the AP configuration set as specified in the protocol). It then determines the number of bytes in the parameter block based on the TLV length field to avoid reading out of bounds. Finally, it parses each sub-parameter according to the format defined by the protocol (e.g., SSID is a UTF-8 string, and the key is 16 / 32 bytes of binary data), and temporarily stores the parsing results. After the configuration is stored in the slave device's configuration cache and parsed, the parameters must be verified for validity (to prevent incorrect configuration from the host causing abnormalities in the slave device's wireless interface). Core verification rules include: Protocol compatibility verification: If the slave device hardware only supports the 2.4GHz band, sending a 5GHz configuration via M2 message is considered invalid and requires triggering a configuration anomaly feedback; Parameter range verification: For example, the valid channels for the 2.4GHz band are 1-14; sending channel 15 is considered invalid; The encryption method must be a type supported by the slave device (e.g., if WEP is not supported, the configuration will be rejected); Logical consistency verification: For example, the SSID length must be 1-32 bytes (compliant with the 802.11 standard), and the key length must match the encryption method (e.g., WPA3-PSK requires a key of 8-63 bytes), etc. Then, the slave device's Mesh protocol stack passes the configuration parameters to the wireless interface driver through a standardized driver interface (such as the nl80211 kernel interface in Linux systems or a vendor's proprietary driver API). Upon receiving the parameters, the wireless interface driver writes them into the RF chip's hardware register to complete the AP parameter networking configuration synchronization. After the final configuration is written, it is necessary to confirm that the actual parameters of the wireless interface of the slave device are consistent with the configuration sent by the host. Driver readback verification is required: the protocol stack calls the driver interface to read the current actual parameters of the wireless interface, and then compares and confirms them: the actual parameters read back are compared with the host configuration parameters parsed in the cache field by field. If they are completely consistent, the configuration synchronization is determined to be successful. Then the slave device sends a configuration confirmation message to the host to inform the host that the parameter synchronization has been completed and it can join the Mesh network to provide services.

[0043] In one embodiment of the invention, after completing the AP parameter network configuration synchronization, the process includes: Determine whether the synchronization duration of the AP parameter configuration meets the preset duration range; If the synchronization duration of the AP parameter configuration meets the preset duration range, then the load status and transmission rate of any network device in the Mesh network are obtained; Based on the load status of any network device in the Mesh network, determine whether the networking connection request of the Mesh network meets the preset rate limiting rules; If the networking connection request of the Mesh network meets the preset rate limiting rules, then it is determined whether the transmission rate of any network device is lower than the preset transmission rate threshold. If the transmission rate of any network device is lower than a preset transmission rate threshold, then the network device will be connected to the network access point with the lowest load in the Mesh network.

[0044] Specifically, after the AP parameter configuration synchronization is completed, the system first checks whether the duration of the synchronization process is within a preset reasonable range. If the synchronization duration meets the requirements, the network status monitoring mechanism is activated to collect load indicators and transmission rate data of each network device in real time. Based on the load data, it determines whether the current network is under high load. If the network connection requests exceed the threshold set by the rate limiting rules, devices with transmission rates lower than the minimum standard are further filtered out. For such underperforming devices, the system automatically switches them to the access point with the lowest current load, thereby avoiding network performance degradation due to local node overload. The AP parameter configuration synchronization duration refers to the time span from the start of parameter configuration to the completion of configuration synchronization. This can be achieved by using a timer module to record the timestamp difference. This feature ensures that the configuration synchronization process is completed within a reasonable time to avoid wasting network resources. The preset duration range refers to a pre-set time interval threshold, which can be dynamically adjusted using network performance test data. This feature constrains the efficiency boundary of the configuration synchronization process. The load status refers to the current data traffic or number of connections processed by the network device. This can be achieved by using a traffic statistics module to collect device port data in real time. This feature quantifies the device operating status to assess network carrying capacity. Transmission rate refers to the amount of data transmitted by a network device per unit time, which can be obtained through a physical layer rate negotiation mechanism. This feature is used to measure whether the device's communication performance meets basic service requirements. Rate limiting rules refer to strategies for limiting the rate of network connection requests, which can be implemented using a token bucket algorithm or a sliding window counter. This feature is used to prevent network congestion caused by sudden traffic surges. The preset transmission rate threshold refers to the minimum acceptable communication rate standard, which can be set as a fixed value or dynamically adjusted according to network service quality requirements; this application does not impose any limitations on this. Through the above technical solutions, this application solves the problem of decreased network stability caused by differences in device performance in existing Mesh networks. By optimizing device access strategies through a dynamic load balancing mechanism, it ensures that the network can maintain stable transmission performance under high load scenarios, thereby avoiding network congestion caused by insufficient device performance and improving the user experience in multi-device access environments.

[0045] In some specific implementations, the preset duration range can be set to 30 to 60 seconds, the rate limiting rule can adopt a dynamic threshold adjustment mechanism based on historical traffic data, and the transmission rate threshold can be automatically adapted to 70%-90% of the current average rate according to the network environment. The load sorting algorithm can prioritize nodes with memory usage below 40% and fewer than 50 connections as low-load access points.

[0046] In this embodiment, by synchronizing the Mesh networking parameters according to the AP wireless configuration parameters in the M2 phase message, the protocol compatibility problem between heterogeneous Mesh devices can be effectively solved. This enables the slave devices to automatically identify and adapt to the private protocols of different manufacturers, thereby improving the accuracy and efficiency of Mesh networking and enhancing the user experience.

[0047] In summary, this invention provides a PON-based Mesh networking method, apparatus, device, and medium. It receives topology multicast messages periodically sent by target network devices. These topology multicast messages include a private mesh network protocol identifier. The target network devices include hosts and / or slave devices. Based on the private mesh network protocol identifier in the topology multicast message, the host address information in the mesh network is determined. Based on the host address information in the mesh network, an M1 phase message requesting access point wireless configuration is generated and sent to the host. The invention receives an M2 phase message from the host in response to the M1 phase message, also requesting access point wireless configuration. The M2 phase message includes AP wireless configuration parameters. Based on the AP wireless configuration parameters in the M2 phase message, mesh networking parameter synchronization is completed. Therefore, this application achieves intelligent protocol type identification by parsing the private mesh network protocol identifier in the topology multicast message and combines this with the transmission mechanism to complete AP parameter synchronization, thereby avoiding compatibility issues in the networking process of different mesh protocols, effectively improving the success rate of mesh networking, and enhancing the user experience.

[0048] Please see Figure 2 , Figure 2 This is a schematic diagram of the structure of a PON-based Mesh networking device provided in an embodiment of the present invention. This PON-based Mesh networking device corresponds one-to-one with the PON-based Mesh networking method in the above embodiments. Please refer to [link / reference] for details. Figure 1 as well as Figure 1 The relevant descriptions in the corresponding embodiments are shown below. For ease of explanation, only the parts relevant to this embodiment are shown. See also... Figure 2 The PON-based Mesh networking device 20 includes: a receiving module 21, a determining module 22, a generating module 23, a configuring module 24, and a networking module 25.

[0049] The receiving module 21 is used to receive topology multicast messages periodically sent by the target network device, wherein the topology multicast message includes a private mesh network protocol identifier, and the target network device includes a host and / or a sub-machine; The determining module 22 is used to determine the host address information in the Mesh network based on the private mesh network protocol identifier in the topology multicast message; The generation module 23 is used to generate and send an M1 phase message requesting access point wireless configuration to the host based on the host address information in the Mesh network. Configuration module 24 is configured to receive an M2 phase message from the host in response to the M1 phase message, which is a request for wireless configuration of the access point, wherein the M2 phase message includes AP wireless configuration parameters; The networking module 25 is used to synchronize the Mesh networking parameters according to the AP wireless configuration parameters in the M2 phase message.

[0050] Optionally, the aforementioned determining module 22 is specifically used for: The private mesh network protocol identifier in the topology multicast message is parsed to obtain the first mesh protocol type of the mesh network to which the target network device belongs. Determine whether the first Mesh protocol type is consistent with the second Mesh protocol type corresponding to the submachine itself; If the first Mesh protocol type is consistent with the second Mesh protocol type corresponding to the submachine itself, then the host address information in the Mesh network is obtained.

[0051] Optionally, the determining module 22 is further configured to: Send a topology query message to the Mesh network to determine whether there are hosts in the Mesh network that meet the preset communication connection requirements; If it is determined that there is a host in the Mesh network that meets the preset communication connection requirements, then a topology response message is received from the host in the Mesh network in response to the topology query message. The topology response message is parsed to obtain the host address information in the Mesh network.

[0052] Optionally, the aforementioned generation module 23 is specifically used for: Based on the host address information in the Mesh network, send an access point auto-configuration search message to the host; Receive an access point autoconfiguration response message from the host in response to the access point autoconfiguration search message; Obtain access point load information and access point link information in the MESH network; Based on the access point load information and the access point link information, the step of sending an M1 phase message requesting access point wireless configuration to the host is executed.

[0053] Optionally, the above configuration module 24 is specifically used for: Receive public key information and encrypted information sent by the host, wherein the encrypted information is obtained by performing encryption operation on the network configuration information in response to the M1 phase message based on the encryption key; The encrypted information is decrypted based on the public key information, and the decrypted encrypted information is filled into the management frame of the protocol message to generate an M2 phase message for the access point to request wireless configuration in response to the M1 phase message. The protocol message is generated based on a preset wireless LAN general standard.

[0054] Optionally, the networking module 25 mentioned above is specifically used for: Determine whether the synchronization duration of the AP parameter configuration meets the preset duration range; If the synchronization duration of the AP parameter configuration meets the preset duration range, then the load status and transmission rate of any network device in the Mesh network are obtained; Based on the load status of any network device in the Mesh network, determine whether the networking connection request of the Mesh network meets the preset rate limiting rules; If the networking connection request of the Mesh network meets the preset rate limiting rules, then it is determined whether the transmission rate of any network device is lower than the preset transmission rate threshold. If the transmission rate of any network device is lower than a preset transmission rate threshold, then the network device will be connected to the network access point with the lowest load in the Mesh network.

[0055] It should be noted that the information interaction and execution process between the above-mentioned units are based on the same concept as the method embodiments of the present invention. For details on their specific functions and technical effects, please refer to the method embodiments section, which will not be repeated here.

[0056] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. For example... Figure 3 As shown, the electronic device of this embodiment includes: at least one processor ( Figure 3 Only one is shown in the diagram), a memory, and a computer program stored in the memory that can run on at least one processor. When the processor executes the computer program, it implements the steps in any of the above embodiments of the PON-based Mesh networking method.

[0057] This electronic device may include, but is not limited to, a processor and memory. Those skilled in the art will understand that... Figure 3 This is merely an example of an electronic device and does not constitute a limitation on electronic devices. Electronic devices may include more or fewer components than shown, or combinations of certain components, or different components, such as network interfaces, displays, and input systems.

[0058] In one embodiment, a computer-readable storage medium is provided. When the instructions in the computer-readable storage medium are executed by a processor in an electronic device, the electronic device is able to perform the steps of any embodiment of the PON-based Mesh networking method disclosed in this invention, which will not be repeated here. The computer-readable storage medium may be non-volatile or volatile.

[0059] The processor referred to can be a CPU, but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0060] The memory includes readable storage media, internal memory, etc., wherein the internal memory can be the RAM of an electronic device, providing an environment for the operation of the operating system and computer-readable instructions stored in the readable storage media. The readable storage media can be the hard drive of the electronic device, or in other embodiments, it can be an external storage device of the electronic device, such as a plug-in hard drive, SmartMediaCard (SMC), SecureDigital (SD) card, or FlashCard. Furthermore, the memory can include both internal storage units and external storage devices of the electronic device. The memory is used to store the operating system, cooperative applications, bootloader, data, and other programs, such as program code for computer programs. The memory can also be used to temporarily store data that has been output or will be output.

[0061] Those skilled in the art will understand that implementing all or part of the processes in the above embodiments can be accomplished by a computer program instructing related hardware. This computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0062] Those familiar with the technical field will understand that, for ease of description and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the system can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this invention. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.

[0063] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A PON-based Mesh networking method, characterized in that, include: Receive topology multicast messages periodically sent by the target network device, wherein the topology multicast message includes a private mesh network protocol identifier, and the target network device includes a host and / or a sub-machine; Based on the private mesh network protocol identifier in the topology multicast message, determine the host address information in the mesh network; Based on the host address information in the Mesh network, an M1 phase message requesting access point wireless configuration is generated and sent to the host. The system receives an M2 phase message from the host in response to the M1 phase message, which is a request for access point wireless configuration. The M2 phase message includes AP wireless configuration parameters. The Mesh networking parameters are synchronized based on the AP wireless configuration parameters in the M2 phase message.

2. The PON-based Mesh networking method as described in claim 1, characterized in that, The step of determining the host address information in the mesh network based on the private mesh network protocol identifier in the topology multicast message includes: The private mesh network protocol identifier in the topology multicast message is parsed to obtain the first mesh protocol type of the mesh network to which the target network device belongs. Determine whether the first Mesh protocol type is consistent with the second Mesh protocol type corresponding to the submachine itself; If the first Mesh protocol type is consistent with the second Mesh protocol type corresponding to the submachine itself, then the host address information in the Mesh network is obtained.

3. The PON-based Mesh networking method as described in claim 2, characterized in that, Before obtaining the host address information in the Mesh network, the following steps are included: Send a topology query message to the Mesh network to determine whether there are hosts in the Mesh network that meet the preset communication connection requirements; If it is determined that there is a host in the Mesh network that meets the preset communication connection requirements, then a topology response message is received from the host in the Mesh network in response to the topology query message. The topology response message is parsed to obtain the host address information in the Mesh network.

4. The PON-based Mesh networking method as described in claim 1, characterized in that, Before generating and sending the M1 phase message requesting access point wireless configuration to the host, the process includes: Based on the host address information in the Mesh network, send an access point auto-configuration search message to the host; Receive an access point autoconfiguration response message from the host in response to the access point autoconfiguration search message; Obtain access point load information and access point link information in the MESH network; Based on the access point load information and the access point link information, the step of sending an M1 phase message requesting access point wireless configuration to the host is executed.

5. The PON-based Mesh networking method as described in claim 1, characterized in that, The step of receiving the M2 phase message, which is the access point requesting radio configuration, in response to the M1 phase message from the host, includes: Receive public key information and encrypted information sent by the host, wherein the encrypted information is obtained by performing encryption operation on the network configuration information in response to the M1 phase message based on the encryption key; The encrypted information is decrypted based on the public key information, and the decrypted encrypted information is filled into the management frame of the protocol message to generate an M2 phase message for the access point to request wireless configuration in response to the M1 phase message. The protocol message is generated based on a preset wireless LAN general standard.

6. The PON-based Mesh networking method as described in claim 1, characterized in that, After completing the AP parameter network configuration synchronization, the following is included: Determine whether the synchronization duration of the AP parameter configuration meets the preset duration range; If the synchronization duration of the AP parameter configuration meets the preset duration range, then the load status and transmission rate of any network device in the Mesh network are obtained; Based on the load status of any network device in the Mesh network, determine whether the networking connection request of the Mesh network meets the preset rate limiting rules; If the networking connection request of the Mesh network meets the preset rate limiting rules, then it is determined whether the transmission rate of any network device is lower than the preset transmission rate threshold. If the transmission rate of any network device is lower than a preset transmission rate threshold, then the network device will be connected to the network access point with the lowest load in the Mesh network.

7. A PON-based Mesh networking device, characterized in that, include: A receiving module is used to receive topology multicast messages periodically sent by a target network device, wherein the topology multicast message includes a private mesh network protocol identifier, and the target network device includes a host and / or a slave device; The determination module is used to determine the host address information in the Mesh network based on the private mesh network protocol identifier in the topology multicast message; The generation module is used to generate and send an M1 phase message requesting access point wireless configuration to the host based on the host address information in the Mesh network. The configuration module is configured to receive an M2 phase message from the host in response to the M1 phase message, which is a request for wireless configuration of the access point, wherein the M2 phase message includes AP wireless configuration parameters; The networking module is used to synchronize Mesh networking parameters based on the AP wireless configuration parameters in the M2 phase message.

8. The PON-based Mesh networking device as described in claim 7, characterized in that, The determining module is also used for: The private mesh network protocol identifier in the topology multicast message is parsed to obtain the first mesh protocol type of the mesh network to which the target network device belongs. Determine whether the first Mesh protocol type is consistent with the second Mesh protocol type corresponding to the submachine itself; If the first Mesh protocol type is consistent with the second Mesh protocol type corresponding to the submachine itself, then the host address information in the Mesh network is obtained.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the PON-based Mesh networking method as described in any one of claims 1 to 6.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the PON-based Mesh networking method as described in any one of claims 1 to 6.

Images