Implementation method and device for communication mechanism of fttr networking equipment

Abstract

This application provides a method and apparatus for implementing a communication mechanism in FTTR networking devices, relating to the field of optical network management technology. The method includes: defining devices in the FTTR system according to roles in a lightweight distributed management framework; defining communication messages between devices in the FTTR system according to message channels in the lightweight distributed management framework; setting message interfaces and communication protocol stacks for the communication messages to constitute a communication mechanism in the FTTR system; generating an optical gateway topology map through the communication mechanism; and managing the devices in the FTTR system according to the optical gateway topology map. The implementation provided in this application not only supports network topology and WIFI parameter synchronization but also supports the synchronization of more gateway configuration parameters and provides higher security.

Description

Technical Field

[0001] This application relates to the field of optical network management technology, specifically to a method for implementing the communication mechanism of an FTTR networking device, a device for implementing the communication mechanism of an FTTR networking device, an electronic device, and a storage medium. Background Technology

[0002] In FTTR (Fiber to The Room) networking solutions, a home all-optical network typically consists of one optical gateway and multiple optical routers. The optical gateway, as the central node of the network, needs to manage all the optical routers uniformly, including identifying the connection topology of the optical routers, issuing control commands to the optical routers, and obtaining real-time information about the terminal devices connected to the optical routers. However, existing technologies lack a communication mechanism between the optical gateway and the optical routers that can simultaneously meet these three management requirements.

[0003] In current home network environments, optical gateways and optical routers mostly rely on standard LAN protocols for data forwarding, lacking dedicated management-oriented message channels. Some solutions attempt to utilize simple device discovery protocols or remote management models based on TR-069, but these methods struggle to support the optical gateway's proactive and accurate identification of the network topology. They often require manual configuration or rely on additional topology inference methods, resulting in low efficiency and a high risk of errors. Furthermore, control commands and device-reported messages are typically mixed on the same communication link without effective channel separation and type differentiation. This prevents the optical gateway from easily issuing parameter configuration or restart control commands to designated optical routers, and also hinders the real-time and efficient collection of dynamic information such as the access status and signal quality of connected terminal devices. These shortcomings have become key bottlenecks limiting the manageability and controllability of home all-optical networks.

[0004] FTTR: Fiber To The Room. Summary of the Invention

[0005] The purpose of this application is to provide a method and apparatus for implementing the communication mechanism of FTTR networking devices. By providing a new communication mechanism, it supports optical gateways in identifying network topology, controlling optical routes in the topology, and obtaining information of downstream devices, thereby at least solving some of the problems in the background art.

[0006] To achieve the above objectives, this application provides a method for implementing an FTTR networking device communication mechanism, comprising: defining devices in the FTTR system according to roles in a lightweight distributed management framework; defining communication messages between devices in the FTTR system according to message channels in the lightweight distributed management framework; setting message interfaces and communication protocol stacks for the communication messages to constitute a communication mechanism in the FTTR system; generating an optical gateway topology map through the communication mechanism; and managing the devices in the FTTR system according to the optical gateway topology map.

[0007] Optionally, the roles in the lightweight distributed management framework include management end and agent end, and the devices in the FTTR system include optical gateway and optical router; defining the devices in the FTTR system according to the roles in the lightweight distributed management framework includes: designating the optical gateway as the management end in the lightweight distributed management framework, and the optical router as the agent end in the lightweight distributed management framework.

[0008] Optionally, the communication messages between devices in the FTTR system are defined according to the message channel in the lightweight distributed management framework, including: the management end manages the agent end through the DSS_CALL message channel, and the agent end reports information through the DSS_MSG message channel.

[0009] Optionally, a message interface is set for the communication messages, including: the DSS_CALL message channel includes: a query message, a configuration message, and a retrieval message; the query message is used to query the information of the downstream device, the configuration message is used to configure the optical route, and the retrieval message is used to retrieve the configuration of a specific optical route; the DSS_MSG message channel includes: a report message, a configuration return message, and a retrieval return message; the report message is used to report the information of the downstream device, the configuration return message is used for the optical route configuration return value, and the retrieval return message is used for the optical route to retrieve the configuration return value and output.

[0010] Optionally, a communication protocol stack is set for the communication message, including: setting the communication protocol stack to include, from bottom to top: UDP / IP layer, DTLS protocol layer, CoAP protocol layer, and JSON layer; the parameters in the communication message in the JSON layer are defined in JSON format; the CoAP protocol layer is used to provide packet splitting mechanism and message delivery reliability; the DTLS protocol layer is used to provide communication security and integrity; and the UDP / IP layer is used to provide transport layer and network layer transmission services.

[0011] Optionally, the devices in the FTTR system generate an optical gateway topology map through the communication mechanism, including: using the optical gateway as the root node of a tree, the optical router as the child node, and the downstream devices as leaves; the management end obtains all its downstream devices as leaves by reading the local area network host configuration file; the management end adds leaves or updates connection status by receiving message notifications from the local area network host configuration file; the management end receives and processes the MAC traversal tree reported by the agent to obtain the optical gateway topology map.

[0012] Optionally, the devices in the FTTR system are managed according to the optical gateway topology diagram, including: topology update, offline management, and configuration management; the topology update includes: updating the optical gateway topology diagram based on reported information; the offline management includes: delaying the clearing of offline devices by the optical gateway; the configuration management includes: configuration synchronization and configuration acquisition.

[0013] This application also provides an apparatus for implementing a communication mechanism for FTTR networking devices. The apparatus includes: a framework adaptation module, used to define devices in the FTTR system according to roles in a lightweight distributed management framework, and to define communication messages between devices in the FTTR system according to message channels in the lightweight distributed management framework; a mechanism construction module, used to set message interfaces and communication protocol stacks for the communication messages to constitute a communication mechanism in the FTTR system; a topology generation module, used by the devices in the FTTR system to generate an optical gateway topology map through the communication mechanism; and a device management module, used to manage the devices in the FTTR system according to the optical gateway topology map.

[0014] This application also provides an electronic device, including: at least one processor; and a memory connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the at least one processor implements the aforementioned FTTR networking device communication mechanism by executing the instructions stored in the memory.

[0015] This application also provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the aforementioned method for implementing the FTTR networking device communication mechanism.

[0016] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned method for implementing the FTTR networking device communication mechanism.

[0017] The above technical solution has the following beneficial effects: The communication mechanism provided in this application not only supports network topology and WIFI parameter synchronization, but also supports the synchronization of more gateway configuration parameters, and provides higher security.

[0018] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description

[0019] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings: Figure 1 The illustration shows the steps of a method for implementing the communication mechanism of an FTTR networking device according to an embodiment of this application. Figure 2 This diagram illustrates the communication between the management end and the agent end through the DSS_CALL message channel. Figure 3 This diagram illustrates the communication between the agent and the DSS_MSG message channel for information reporting. Figure 4 The diagram illustrates the structure of the generated optical gateway topology. Figure 5 This diagram illustrates the communication process when a new optical route is accessed through an existing optical route. Figure 6 This diagram illustrates the communication process when the connected device is roaming. Figure 7 This diagram illustrates the communication process during periodic queries by the optical gateway. Figure 8 The diagram illustrates the communication process during configuration synchronization. Figure 9 The diagram illustrates the communication process during configuration acquisition. Figure 10 This schematic diagram illustrates the structure of a device for implementing the communication mechanism of an FTTR networking device according to an embodiment of this application. Figure 11 The diagram schematically illustrates the internal structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0020] The specific embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit the embodiments of this application.

[0021] Figure 1The illustration schematically shows the steps of a method for implementing the communication mechanism of an FTTR networking device according to an embodiment of this application. For example... Figure 1 As shown, a method for implementing the communication mechanism of an FTTR networking device is described, the method comprising: S01. Define the devices in the FTTR system according to the roles in the lightweight distributed management framework, and define the communication messages between the devices in the FTTR system according to the message channels in the lightweight distributed management framework. S02. Set up a message interface and a communication protocol stack for the communication message to form the communication mechanism in the FTTR system; S03. The devices in the FTTR system generate an optical gateway topology map through the communication mechanism. S04. Manage the devices in the FTTR system according to the optical gateway topology diagram.

[0022] The above implementation method differs from EasyMesh in that it not only supports network topology and WIFI parameter synchronization, but also supports the synchronization of more gateway configuration parameters, and provides higher security.

[0023] In some embodiments of this application, the roles in the lightweight distributed management framework include management and proxy ends, and the devices in the FTTR system include optical gateways and optical routers. Defining the devices in the FTTR system according to the roles in the lightweight distributed management framework includes: designating the optical gateway as the management end in the lightweight distributed management framework, and the optical router as the proxy end in the lightweight distributed management framework. In this embodiment, a lightweight distributed management framework is introduced to define the roles of devices in the FTTR system. Specifically, the optical gateway residing at the home network aggregation point, possessing all-optical access and core network functions, is defined as the management end in the management framework; the optical routers distributed in each room, connected to the optical gateway via optical fiber, and responsible for Wi-Fi coverage and wired access, are defined as the proxy ends in the management framework. The management optical gateway assumes a centralized control role, possesses a global network view, and is responsible for the unified management of all optical routers within the home all-optical network. The agent-end optical router acts as a distributed execution node. On one hand, it responds to control commands issued by the management terminal, completing operations such as parameter configuration and state switching. On the other hand, it actively collects its own working status, information on connected terminal devices, and link quality data, and reports this information to the management terminal. Through this role division, the FTTR system establishes a clear management hierarchy and communication relationships. Based on the registration and message reporting of the agents, the management terminal can automatically identify and maintain the topological connection relationships between optical routers, achieving dynamic awareness of the home network structure.

[0024] In some embodiments of this application, the communication messages between devices in the FTTR system are defined according to the message channel in the lightweight distributed management framework, including: the management end manages the agent end through the DSS_CALL message channel, and the agent end reports information through the DSS_MSG message channel. Figure 2 This diagram illustrates the communication between the management end and the agent end via the DSS_CALL message channel. (For example...) Figure 2 As shown, the optical gateway manages optical routes A, B, and C by issuing DSS_query commands to the optical routes A, B, and C below it through the MAC address, based on the internal MAC traversal tree. Figure 3 This diagram illustrates the communication process where the agent reports information via the DSS_MSG message channel. For example... Figure 3 As shown, after the optical router obtains the IP address from the optical gateway, it immediately sends a message to the optical gateway and reports its downstream gateways and downstream devices through the DSS_report command.

[0025] In some embodiments of this application, a message interface is set for the communication messages, including: the DSS_CALL message channel includes: a query message, a configuration message, and an acquisition message; the query message is used to query downstream device information, the configuration message is used to configure optical routing, and the acquisition message is used to acquire specific optical routing configuration; the DSS_MSG message channel includes: a report message, a configuration return message, and an acquisition return message; the report message is used to report downstream device information, the configuration return message is used for optical routing configuration return values, and the acquisition return message is used for optical routing acquisition configuration return values ​​and output. Specific definitions are shown in the table below.

[0026]

[0027] In some embodiments of this application, a communication protocol stack is set up for the communication message, including: setting the communication protocol stack to include, from bottom to top: a UDP / IP layer, a DTLS protocol layer, a CoAP protocol layer, and a JSON layer; the parameters in the communication message in the JSON layer are defined in JSON format; the CoAP protocol layer is used to provide packet splitting mechanism and message delivery reliability; the DTLS protocol layer is used to provide communication security and integrity; and the UDP / IP layer is used to provide transport layer and network layer transmission services. Specifically, the UDP / IP layer should use the standard UDP and IP protocols. DTLS (Datagram Transport Layer Security) is a secure transport protocol based on the UDP protocol, which provides similar security and data integrity protection as TLS (Transport Layer Security), while also having the advantages of the UDP protocol, such as low latency and support for multiplexing. The CoAP protocol is based on UDP and does not have encryption capabilities itself, so it needs to rely on DTLS to ensure data confidentiality and integrity. The DTLS protocol can use the AES-CBC encryption algorithm and a 1024-key length, and uses signature certificates and public key certificates for authentication to ensure the security and integrity of communication. The CoAP protocol layer is based on the UDP protocol layer and should comply with the relevant requirements of RFC 7252 "The Constrained Application Protocol (CoAP)". It should support reliable message delivery and packet fragmentation. CoAP should use binary encoding, begin with a fixed 4-byte header, and support tokens and standard options. The message format is described below: Ver: Current version number is 01. Messages with version numbers other than 01 are discarded. T: Message type, including Confirmable (CON), Non-confirmable (NON), Acknowledgement (ACK), and Reset (RST). TKL: Token length, valid values ​​are 0-8, other values ​​are incorrect. Code: When the message is a request, the Code field indicates the request method (Get / Post / Put / Delete). When the message is a response, the Code field represents the response code (empty / success / client error / server error). Message ID: Used for message duplication detection, and for matching Confirmable, Non-confirmable, Acknowledgement, and Reset messages. Token: Used to match request methods and responses. Option: Supports standard options, no custom options. Payload: From the tag field (0xFF) to the end of the UDP packet. The tag field is not used when there is no payload.

[0028] Message delivery reliability relies on a reliable message retransmission mechanism and should comply with the requirements of RFC 7252, "The Constrained Application Protocol (CoAP)," supporting CON type messages. The retransmission interval at the sender should increase exponentially until it receives an ACK or RST message, or reaches the maximum retransmission count (MAX_RETRANSMIT). The initial timeout is set to a random value (usually not an integer number of seconds) between ACK_TIMEOUT and ACK_TIMEOUT * ACK_RANDOM_FACTOR, and the retransmission count is set to 0. When a timeout occurs and the retransmission count is less than MAX_RETRANSMIT, the message is retransmitted, the retransmission count increases, and the timeout becomes a multiple of ACK_TIMEOUT_SCALE. If the retransmission count reaches MAX_RETRANSMIT when the timeout occurs, or an RST message is received, message transmission is abandoned; if an ACK is received before the timeout, transmission is successful. The subcontracting mechanism should comply with the relevant requirements of RFC 7959 "Block-Wise Transfers in the Constrained Application Protocol" and should support both Block 1 Option and Block 2 Option. Its parameter conventions include:

[0029] The parameters in the FTTR device management message are defined using JSON format.

[0030] In some embodiments of this application, the devices in the FTTR system generate an optical gateway topology map through the communication mechanism, including: using the optical gateway as the root node of a tree, the optical router as the child node, and the downstream devices as leaves; the management terminal obtains all its downstream devices as leaves by reading the local area network host configuration file; the management terminal adds leaves or updates connection status by receiving message notifications from the local area network host configuration file; the management terminal receives and processes the MAC traversal tree reported by the agent to obtain the optical gateway topology map. Specifically, the optical gateway topology map generation algorithm includes: 1. The DSS Controller maintains the following tree diagram of the topology: the optical gateway is the root node, the optical router is the child node, and the downstream devices are the leaves; 2. Controller initializes by reading all devices connected to lanhost and making them leaf nodes; 3. When the Controller receives a lanhost message notification, it adds a leaf when a new device comes online, and updates the connection status when an old device goes offline or online. 4. The Controller serially receives and processes the Agent's report messages. The topology map establishment process includes: a. Traverse the tree using the MAC address of the node itself, including: a.1 If no node or leaf exists, add it to the root node; its subordinate devices become leaves; a.2 If a node already exists, update the online status of its subordinate devices (i.e., child nodes and leaves); a.3 If a leaf already exists, add it to the node, making it its subtree; delete the corresponding leaf from the node. b. Traverse the MAC address tree of the downstream device, including: b.1 If a node already exists, that node becomes its subtree; b.2 If a leaf already exists, keep the online ones and delete the offline ones.

[0031] Figure 4 The diagram illustrates the structure of the generated optical gateway topology. For example... Figure 4 As shown, it generates a topology diagram that includes optical gateways, optical routes, and devices.

[0032] In some embodiments of this application, the devices in the FTTR system are managed according to the optical gateway topology diagram, including: topology update, offline management, and configuration management; the topology update includes: updating the optical gateway topology diagram based on reported information; the offline management includes: delaying the clearing of offline devices by the optical gateway; the configuration management includes: configuration synchronization and configuration acquisition. Details are as follows.

[0033] Figure 5 This diagram illustrates the communication process when a new optical route is accessed through an existing optical route. For example... Figure 5As shown, when a new optical route C connects to optical route B, it actively reports to the optical gateway. Optical route B, upon detecting the connection of optical route C, actively reports the message to the optical gateway, thus achieving a topology update.

[0034] Figure 6 This diagram illustrates the communication process when a connected device is roaming. For example... Figure 6 As shown, when the downstream device roams from optical router C to optical router A, the topology map in the optical gateway is also updated through the reported information, namely DSS_report.

[0035] Figure 7 This diagram illustrates the communication process during periodic queries by the optical gateway. For example... Figure 7 As shown, the optical gateway periodically queries, and the controller periodically queries each agent. The period is configurable, with a default of 5 seconds. Agents report their own information and information about their connected devices. The controller updates the topology map based on the agents' reports; if no report is submitted within the timeout period, the agent and its connected devices are considered offline. The optical gateway delays the cleanup of offline devices, including: 1. Offline devices are cleaned up after a default of 7 days, with a configurable period; 2. All offline connected devices are cleaned up after the device restarts, except for optical routers.

[0036] Figure 8 The diagram illustrates the communication process during configuration synchronization. For example... Figure 8 As shown, when the synchronization node of the optical gateway configuration management is set, it triggers asynchronous DSS configuration to all optical routes. The Agent IPC CALL configuration management's corresponding set interface only configures nodes with the synchronization attribute. If the interface returns an error, an error code message must be sent to the Controller. Upon receiving the error message, the Controller must log it in the system log and report an alarm message. The synchronization attribute of the management layer nodes is specified in the pre-configuration; nodes are not synchronized by default.

[0037] Figure 9 The diagram illustrates the communication process during configuration retrieval. For example... Figure 9 As shown, the configuration is obtained by remotely calling the optical route configuration management get interface of the optical gateway DSS.

[0038] Based on the same inventive concept, this application also provides an apparatus for implementing the communication mechanism of FTTR networking equipment. Figure 10 This diagram schematically illustrates the structure of an apparatus for implementing the communication mechanism of an FTTR networking device according to an embodiment of this application. For example... Figure 10As shown, the device includes: a framework adaptation module, used to define devices in the FTTR system according to roles in the lightweight distributed management framework, and to define communication messages between devices in the FTTR system according to message channels in the lightweight distributed management framework; a mechanism construction module, used to set message interfaces and communication protocol stacks for the communication messages to constitute the communication mechanism in the FTTR system; a topology generation module, used by the devices in the FTTR system to generate an optical gateway topology map through the communication mechanism; and a device management module, used to manage the devices in the FTTR system according to the optical gateway topology map.

[0039] In some optional implementations, the roles in the lightweight distributed management framework include management end and agent end, and the devices in the FTTR system include optical gateway and optical router; defining the devices in the FTTR system according to the roles in the lightweight distributed management framework includes: designating the optical gateway as the management end in the lightweight distributed management framework, and the optical router as the agent end in the lightweight distributed management framework.

[0040] In some optional implementations, the communication messages between devices in the FTTR system are defined according to the message channels in the lightweight distributed management framework, including: the management end manages the agent end through the DSS_CALL message channel, and the agent end reports information through the DSS_MSG message channel.

[0041] In some optional implementations, a message interface is set for the communication messages, including: the DSS_CALL message channel includes: a query message, a configuration message, and an acquisition message; the query message is used to query the information of the downstream device, the configuration message is used to configure the optical route, and the acquisition message is used to acquire the configuration of a specific optical route; the DSS_MSG message channel includes: a report message, a configuration return message, and an acquisition return message; the report message is used to report the information of the downstream device, the configuration return message is used for the optical route configuration return value, and the acquisition return message is used for the optical route acquisition configuration return value and output.

[0042] In some optional implementations, a communication protocol stack is set for the communication messages, including: setting the communication protocol stack to include, from bottom to top: UDP / IP layer, DTLS protocol layer, CoAP protocol layer, and JSON layer; the parameters in the communication messages in the JSON layer are defined in JSON format; the CoAP protocol layer is used to provide packet splitting mechanism and message delivery reliability; the DTLS protocol layer is used to provide communication security and integrity; and the UDP / IP layer is used to provide transport layer and network layer transmission services.

[0043] In some optional implementations, the devices in the FTTR system generate an optical gateway topology map through the communication mechanism, including: using the optical gateway as the root node of a tree, the optical router as the child node, and the downstream devices as leaves; the management terminal obtains all its downstream devices as leaves by reading the local area network host configuration file; the management terminal adds leaves or updates connection status by receiving message notifications from the local area network host configuration file; the management terminal receives and processes the MAC traversal tree reported by the agent to obtain the optical gateway topology map.

[0044] In some optional implementations, the devices in the FTTR system are managed according to the optical gateway topology map, including: topology updates, offline management, and configuration management; the topology update includes: updating the optical gateway topology map based on reported information; the offline management includes: delaying the cleanup of offline devices by the optical gateway; the configuration management includes: configuration synchronization and configuration acquisition. Optionally, the roles in the lightweight distributed management framework include management end and agent end, and the devices in the FTTR system include optical gateways and optical routers; defining the devices in the FTTR system according to the roles in the lightweight distributed management framework includes: designating the optical gateway as the management end in the lightweight distributed management framework, and the optical router as the agent end in the lightweight distributed management framework.

[0045] In some optional implementations, the communication messages between devices in the FTTR system are defined according to the message channels in the lightweight distributed management framework, including: the management end manages the agent end through the DSS_CALL message channel, and the agent end reports information through the DSS_MSG message channel.

[0046] In some optional implementations, a message interface is set for the communication messages, including: the DSS_CALL message channel includes: a query message, a configuration message, and an acquisition message; the query message is used to query the information of the downstream device, the configuration message is used to configure the optical route, and the acquisition message is used to acquire the configuration of a specific optical route; the DSS_MSG message channel includes: a report message, a configuration return message, and an acquisition return message; the report message is used to report the information of the downstream device, the configuration return message is used for the optical route configuration return value, and the acquisition return message is used for the optical route acquisition configuration return value and output.

[0047] In some optional implementations, a communication protocol stack is set for the communication messages, including: setting the communication protocol stack to include, from bottom to top: UDP / IP layer, DTLS protocol layer, CoAP protocol layer, and JSON layer; the parameters in the communication messages in the JSON layer are defined in JSON format; the CoAP protocol layer is used to provide packet splitting mechanism and message delivery reliability; the DTLS protocol layer is used to provide communication security and integrity; and the UDP / IP layer is used to provide transport layer and network layer transmission services.

[0048] In some optional implementations, the devices in the FTTR system generate an optical gateway topology map through the communication mechanism, including: using the optical gateway as the root node of a tree, the optical router as the child node, and the downstream devices as leaves; the management terminal obtains all its downstream devices as leaves by reading the local area network host configuration file; the management terminal adds leaves or updates connection status by receiving message notifications from the local area network host configuration file; the management terminal receives and processes the MAC traversal tree reported by the agent to obtain the optical gateway topology map.

[0049] In some optional implementations, the devices in the FTTR system are managed according to the optical gateway topology map, including: topology update, offline management, and configuration management; the topology update includes: updating the optical gateway topology map based on reported information; the offline management includes: delaying the clearing of offline devices by the optical gateway; the configuration management includes: configuration synchronization and configuration acquisition.

[0050] The specific limitations of each functional module in the above-mentioned FTTR networking device communication mechanism implementation device can be found in the limitations of the implementation method of the FTTR networking device communication mechanism described above, and will not be repeated here. Each module in the above system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module. It also achieves the beneficial effects of not only supporting network topology and WIFI parameter synchronization, but also supporting the synchronization of more gateway configuration parameters, and providing higher security.

[0051] In some embodiments of this application, an electronic device is also provided, comprising: at least one processor; and a memory connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the at least one processor executes the aforementioned implementation method of the FTTR networking device communication mechanism. Its internal structure diagram can be shown as follows. Figure 11 As shown. Figure 11This schematic diagram illustrates the internal structure of an electronic device according to an embodiment of this application. The electronic device includes a processor A01, a network interface A02, a memory (not shown), and a database (not shown) connected via a system bus. The processor A01 provides computing and control capabilities. The memory includes internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02, and a database (not shown). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 stored in the non-volatile storage medium A04. The network interface A02 is used for communication with external terminals via a network connection. When the computer program B02 is executed by the processor A01, it implements a method for implementing an FTTR networking device communication mechanism.

[0052] Those skilled in the art will understand that Figure 11 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0053] In one embodiment provided in this application, a machine-readable storage medium is provided, on which instructions are stored, which, when executed by a processor, cause the processor to be configured to perform the aforementioned implementation method of the FTTR networking device communication mechanism.

[0054] In one embodiment provided in this application, a computer program product is provided, including a computer program that, when executed by a processor, implements the aforementioned method for implementing the FTTR networking device communication mechanism.

[0055] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0056] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0057] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0058] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0059] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0060] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0061] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0062] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0063] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for implementing the communication mechanism of an FTTR networking device, characterized in that, The method includes: The devices in the FTTR system are defined according to the roles in the lightweight distributed management framework, and the communication messages between the devices in the FTTR system are defined according to the message channels in the lightweight distributed management framework. A message interface and a communication protocol stack are set up for the communication messages to form the communication mechanism in the FTTR system; The devices in the FTTR system generate an optical gateway topology map through the communication mechanism. The devices in the FTTR system are managed according to the optical gateway topology diagram.

2. The method according to claim 1, characterized in that, The roles in the lightweight distributed management framework include the management end and the agent end, and the devices in the FTTR system include optical gateways and optical routers; Devices in the FTTR system are defined according to roles in the lightweight distributed management framework, including: The optical gateway is used as the management terminal in the lightweight distributed management framework, and the optical router is used as the proxy terminal in the lightweight distributed management framework.

3. The method according to claim 2, characterized in that, The communication messages between devices in the FTTR system are defined according to the message channel in the lightweight distributed management framework, including: The management terminal manages the agent terminal through the DSS_CALL message channel, and the agent terminal reports information through the DSS_MSG message channel.

4. The method according to claim 3, characterized in that, Setting up a message interface for the communication message includes: The DSS_CALL message channel includes: query message, configuration message, and retrieval message; the query message is used to query the information of the downstream device, the configuration message is used to configure the optical route, and the retrieval message is used to retrieve the configuration of a specific optical route; The DSS_MSG message channel includes: a report message, a configuration return message, and an acquisition return message; the report message is used to report the information of the connected device, the configuration return message is used for the optical route configuration return value, and the acquisition return message is used for the optical route to acquire the configuration return value and output.

5. The method according to claim 3, characterized in that, Setting up a communication protocol stack for the communication message includes: The communication protocol stack is configured to include, from bottom to top: UDP / IP layer, DTLS protocol layer, CoAP protocol layer, and JSON layer; The parameters in the communication messages of the JSON layer are defined in JSON format. The CoAP protocol layer is used to provide packet splitting mechanisms and message delivery reliability; The DTLS protocol layer is used to provide security and integrity for communication; The UDP / IP layer is used to provide transport services for the transport and network layers.

6. The method according to claim 2, characterized in that, The devices in the FTTR system generate an optical gateway topology map through the communication mechanism, including: The optical gateway is the root node of the tree, the optical router is the child node, and the downstream devices are the leaves; The management terminal obtains all its downstream devices by reading the configuration file of the local area network host, which then become the leaves. The management console adds leaves or updates connection status by receiving message notifications from the local area network host configuration files. The management terminal receives and processes the MAC traversal tree reported by the agent terminal to obtain the optical gateway topology map.

7. The method according to claim 2, characterized in that, The devices in the FTTR system are managed according to the optical gateway topology diagram, including: topology updates, offline management, and configuration management; The topology update includes: updating the optical gateway topology map based on the reported information; The offline management includes: delaying the clearing of offline devices in optical gateways; The configuration management includes configuration synchronization and configuration retrieval.

8. A device for implementing the communication mechanism of an FTTR networking device, characterized in that, The device includes: The framework adaptation module is used to define devices in the FTTR system according to the roles in the lightweight distributed management framework, and to define communication messages between devices in the FTTR system according to the message channels in the lightweight distributed management framework. The mechanism construction module is used to set up message interfaces and communication protocol stacks for the communication messages, thereby forming the communication mechanism in the FTTR system; A topology generation module is used by devices in the FTTR system to generate an optical gateway topology map through the communication mechanism; and The device management module is used to manage the devices in the FTTR system according to the optical gateway topology diagram.

9. An electronic device, characterized in that, include: At least one processor; A memory connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor implements the communication mechanism of the FTTR networking device as described in any one of claims 1 to 7 by executing the instructions stored in the memory.

10. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instruction is executed by the processor, it implements the method for implementing the FTTR networking device communication mechanism as described in any one of claims 1 to 7.

Images