Network management system and network management method

Abstract

To provide a network management system and a network management method.SOLUTION: A network management system includes: a route node; and a plurality of network nodes communicably connected o the route node to form a network topology with the route node and receiving a data correspondence table from the route node. The route node receives configuration data, compresses the configuration data into a configuration code on the basis of the data correspondence table and transmits the configuration code to the plurality of network nodes. The plurality of network nodes converts the configuration code into configuration data on the basis of the data correspondence table and adjusts communication connections with external devices on the basis of the configuration data.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to management of a network topology, and more particularly to a network management system and a network management method. [Background technology]

[0002] With the development of science and technology, network communication technology has been widely used in people's lives, and people's demand for network communication is also increasing. Among them, the "stability" of network communication is one of the factors that users pay the most attention to. Summary of the Invention [Problem to be solved by the invention]

[0003] Therefore, how to efficiently manage network topology and ensure the stability of network communication has become an important issue at present.

[0004] In view of the above-mentioned problems, an object of the present disclosure is to provide a network management system and a network management method. [Means for solving the problem]

[0005] In order to achieve the above-mentioned object, a network management system according to the present disclosure includes a root node, and a plurality of network nodes communicatively connected to the root node to form a network topology with the root node and receive a data correspondence table from the root node, wherein the root node is configured to receive configuration data, compress the configuration data into a configuration code based on the data correspondence table, and transmit the configuration code to the plurality of network nodes, and the plurality of network nodes are configured to convert the configuration code into the configuration data based on the data correspondence table, and adjust a communication connection with an external device based on the configuration data.

[0006] In order to achieve the above-mentioned object, the network management method of the present disclosure includes a step of transmitting a data correspondence table to a plurality of network nodes via a root node, the plurality of network nodes being communicatively connected to the root node and forming a network topology with the root node; a step of compressing configuration data into a configuration code via the root node based on the data correspondence table and transmitting the configuration code to the network node; a step of converting the received configuration code into the configuration data via the plurality of network nodes based on the data correspondence table; and a step of adjusting communication connections between the plurality of network nodes and an external device based on the configuration data. Effect of the Invention

[0007] The network management system and the network management method according to the present disclosure compress the configuration data, thereby reducing the amount of data transmission in the network topology and preventing an impact on the stability of signal transmission. In addition, since the root node and the network nodes confirm the type and format of data with each other using a data correspondence table, when the type of external device or the form of data to be transmitted changes, it is not necessary to update the entire firmware in the network node, and the system operation and maintenance management of the network can be made more efficient. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram illustrating a network management system according to some embodiments of the present disclosure. [Diagram 2] 1 is a process flow diagram illustrating a network management method according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, several embodiments of the present disclosure will be described with reference to the drawings. For the sake of clarity, many practical details are described in the following description. However, it should be understood that these practical details are not applied to limit the present disclosure. That is, in some embodiments of the present disclosure, these practical details are not necessary. In addition, in order to simplify the drawings, some conventional structures and elements are simply and diagrammatically shown in the drawings.

[0010] In this specification, when an element is referred to as being "connected" or "coupled," it may mean "electrically connected" or "electrically coupled." "Connected" or "coupled" may also be used to indicate cooperation or interaction between two or more elements. In this specification, terms such as "first," "second," and the like are used only to distinguish elements or methods of operation having the same technical terminology, and are not intended to state or imply any particular order or priority or to limit the present disclosure unless clearly indicated by the context.

[0011] 1 is a schematic diagram illustrating a network management system 100 according to some embodiments of the present disclosure. In one embodiment, the network management system 100 is applied to manage a mesh network, such as a Field Area Network (FAN) built using a Wireless Smart Utility Network (Wi-SUN) network transmission technology, or a network topology built using LoRa, a low-power wide area network technology. The present disclosure is not limited thereto, and the network management system 100 can also be applied to a tree network or other types of mesh networks.

[0012] As shown in FIG. 1, the network management system 100 includes a controller 110, a root node GR1, and a plurality of network nodes GN1-GN6. In some embodiments, the root node GR1 and the network nodes GN1-GN6 are gateways. The root node GR1 is used to convert data packets between different network communication protocols and is connected to a cloud controller 110 via wired or wireless network communication. The root node GR1 and the network nodes GN1-GN6 are communicatively connected to each other to form a network topology NT, and in some embodiments, the controller 110 may be communicatively connected to multiple root nodes at the same time to manage multiple network topologies, such as another network topology formed by the root node GR2 and the network nodes GNa-GNc shown in FIG. 1. A person skilled in the art can understand how to transmit data between network topologies, so the description will be omitted here.

[0013] Each network node selects to connect to a node with the strongest signal strength among other adjacent network nodes, and connects to the root node via the other nodes. In the following, a network topology NT in which a network node GN5 is connected to a network node GN2, and is connected to a root node GR1 via the network node GN2, is taken as an example for explanation. The network node GN5 can transmit data to and from a plurality of terminal devices TD1 to TD3 communicatively connected to the network topology NT via the network topology NT. Here, the route through which the network node GN5 connects to the root node GR1 is called a "routing path."

[0014] In one embodiment, the controller 110 can generate configuration data Sc1 according to management requirements. The configuration data Sc1 is used to set up communication connections between the network nodes GN1-GN6 and external devices (e.g., terminal devices TD1-TD3) for data transmission such as network names, assigned port numbers, passwords, etc. As shown in FIG. 1, the terminal devices TD1-TD3 may first be connected to corresponding network nodes GN3, GN5. Then, the controller 110 transmits the configuration data Sc1 to the root node GR1, and the root node GR1 transmits the configuration data Sc1 to corresponding network nodes GN3, GN5 so that the network nodes GN3, GN5 can establish communication connections with the terminal devices TD1-TD3.

[0015] The aforementioned "configuration data" may be network setting information including the entire network topology NT, or may be network setting information for a single network node. In other words, in one embodiment, the configuration data Sc1 may include necessary information corresponding to the network nodes GN1 to GN6. Therefore, when the root node GR1 receives the configuration data Sc1, the root node GR1 can further divide the received configuration data Sc1 into multiple different sub-data and transmit them to each of the network nodes GN1 to GN6. If a certain network node (e.g., GN4) is not currently connected to other external devices, the configuration data Sc1 does not include configuration sub-data corresponding to that network node. That is, the root node GR1 does not need to transmit configuration sub-data to these network nodes.

[0016] Also, when a communication connection between any of the network nodes GN1-GN6 and an external device changes, the controller 110 (e.g., controlled by a network operator) can generate or update configuration data Sc1 in the root node GR1 and send new compressed configuration data to the corresponding network node GN1-GN6 to adjust the communication connection between the corresponding network node GN1-GN6 and the external device. "Change in communication connection between a network node and an external device" also means a change in the type of external device or the type of data sent.

[0017] For example, when the network node GN3 is connected to a terminal device TD3 (e.g., a temperature control device) and then connected to a terminal device TD1 (e.g., a humidity control device), since both the type of device to which the network node GN3 is connected and the type of data received have changed (e.g., temperature, humidity), the controller 110 updates the configuration data Sc1 corresponding to the network node GN3 so that the network node GN3 can correctly establish a connection with the terminal device TD1 and correctly read the data transmitted from the terminal device TD1. Similarly, when the network node GN5 is no longer connected to the terminal device TD1, the controller 110 can also update the configuration data corresponding to the network node GN5. Furthermore, when the controller 110 determines that the network node GN3 needs to be removed due to hardware failure or aging of the equipment, it generates the configuration data Sc1 and transmits the configuration data Sc1 to the network node GN4 via the route node GR1 so that the terminal device TD3 can be connected to the network node GN4. At this time, if the terminal device TD3 is connected to the network node GN4 via a physical line, the network node GN4 establishes a communication connection with the terminal device TD3 based on the associated device information recorded in the configuration data Sc1.

[0018] In some embodiments, since the controller 110 needs to simultaneously manage multiple network nodes in a network topology, the configuration data may be compressed, converted, or encoded into other formats for transmission to ensure smooth and stable data transmission. More details on compression / conversion / codecs will be provided below.

[0019] The network management method used in the network management system 100 according to the present disclosure may include four steps: (A) monitoring management, (B) information compression, (C) data handling, and (D) data backup, which will be described later.

[0020] Here, the "(A) monitoring management" in the network management method according to the present disclosure will be described. As described above, each of the network nodes GN1 to GN6 automatically connects to another node (e.g., an adjacent network node) having the strongest signal strength, forming a network topology NT. Furthermore, when the network nodes GN1 to GN6 receive configuration data Sc1 from the root node GR1, the network nodes GN1 to GN6 connect to an external device (e.g., terminal devices TD1 to TD3) based on the related device information recorded in the configuration data Sc1.

[0021] Furthermore, the network nodes GN1 to GN6 upload routing information Sr to the root node GR1 at predetermined intervals (for example, every 10 minutes). When the root node GR1 receives the routing information Sr of these network nodes GN1 to GN6, it can generate / organize a routing table TB corresponding to the current network topology NT. The routing table TB records the routing information Sr of each network node in the network topology NT. One of the formats of the routing information Sr is as follows:

[0022] “Node 1 Mac”: “Root” “Node 3 Mac”:“Node 1 Mac”

[0023] The above contents respectively record that "network node GN1 is directly connected to root node GR1" and that "network node GN3 is connected to root node GR1 via network node GN1." In other words, in one embodiment, the routing table TB includes the routing paths of network nodes GN1 to GN6, and records the associated devices of each of network nodes GN1 to GN6 (i.e., communication connections between nodes).

[0024] The root node GR1 is used to upload the generated routing table TB to the controller 110 so that the controller 110 can remotely monitor and manage the network topology NT based on the routing table TB. Specifically, the controller 110 can determine the signal strength between the network nodes GN1 to GN6 and determine load distribution among the network nodes GN1 to GN6 based on the routing table TB.

[0025] On the other hand, in some embodiments, the routing table TB also records the radio received signal strength (Received Signal Strength Indication, RSSI) of each network node GN1 to GN6, or the frequency at which each network node GN1 to GN6 changes its communication connection, and the controller 110 determines the signal strength based on this (e.g., if the switching frequency of a particular network node is too high, the signal may not be good), and adjusts the position of the network node or adds a new network node to adjust the network topology NT to improve the overall communication quality.

[0026] Here, "(B) Information Compression" in the network management method according to the present disclosure will be described. The controller 110 generates, adjusts, or updates configuration data Sc1 based on the routing table TB, and controls the route node GR1 to transmit the configuration data Sc1 to the corresponding network node. After the network nodes GN1 to GN6 are connected to external devices (e.g., terminal devices TD1 to TD3) based on the configuration data Sc1, the network nodes GN1 to GN6 transmit data transmitted or requested by the terminal devices TD1 to TD3 via the network topology NT.

[0027] In one embodiment, after receiving the configuration data Sc1 generated by the controller 110, the root node GR1 first performs data compression on the configuration data Sc1 and encodes the configuration data Sc1 into a different format (hereinafter referred to as "configuration code" for short). The root node GR1 then sends the configuration code to the corresponding network node. For example, the controller 110 generates the corresponding configuration data Sc1 based on the "communication connection between the network node GN3 and the terminal device TD3", and when the root node GR1 receives the configuration data Sc1, it compresses the configuration data Sc1 into a configuration code Sc2. Then, it sends the configuration code Sc2 to the network node GN3 via the network node GN1.

[0028] In addition, in network transmission, the root node GR1 transmits the configuration code Sc2-1 to the network node GN1 and transmits the configuration code Sc2-2 to the network node GN3. The configuration code is divided into the configuration code Sc2-1 and the configuration code Sc2-2 according to the contents required by the network node GN1 and the network node GN3, respectively. In other words, the network transmission is treated as two paths, and the network node GN1 is only used to bypass the configuration code Sc2-2 and does not receive the configuration code Sc2-2.

[0029] Similarly, when the network nodes GN1 to GN6 attempt to transmit transmission data (Data) transmitted or requested by the terminal devices TD1 to TD3, the network nodes GN1 to GN6 first compress and encode the transmission data into a different format (hereinafter abbreviated as "data code"), and then transmit the data code via other network nodes in the network topology NT. As a result, the network topology NT transmits the configuration data Sc1 and the transmission data in compressed files, so that the amount of data transmission by the root node GR1 and the network nodes GN1 to GN6 can be reduced, and the potential problem of "data collision" can be avoided.

[0030] In some embodiments, the controller 110, the root node GR1, and the network nodes GN1-GN6 store corresponding encoding and decoding rules (hereinafter abbreviated as "codec rules") so that the received data packets can be decoded to recover the correct contents. In one embodiment, the configuration data may be in a JavaScript (registered trademark) Object Notation (JSON) structured format, and may include, for example, decimal values ​​such as temperature and voltage values, and the encoded configuration data may be in hexadecimal format. The codec rules record the contents represented by each byte in the data packet and the corresponding contents. For example, the first byte records the "data type" and the second byte records the "data length". Details of the codec rules are described in the following paragraphs.

[0031] Here, we will explain "(C) Data Correspondence" in the network management method according to the present disclosure. Since internal settings do not necessarily match perfectly between different devices / nodes, the root node GR1 periodically or actively (for example, when the network topology NT changes) transmits a data correspondence table St to the network nodes GN1 to GN6 so that each of the network nodes GN1 to GN6 can encode and decode data in the same way.

[0032] If the "data correspondence table" is not used, when a new external device is connected to the network topology NT, in order to correctly identify the information transmitted by the new external device, the controller 110 or the root node GR1 needs to actively update the internal firmware of the network nodes GN1 to GN6 so that each network node can correctly identify the type or format of data transmitted by the new external device. However, because the size of the firmware file is relatively large, updating the firmware may complicate management, increase the load of data transmission, and affect the smoothness of other data transmissions.

[0033] FIG. 2 is a process flow diagram illustrating a network management method according to some embodiments of the present disclosure, including the above-mentioned (B) information compression and (C) data correspondence operations. In step S201, the root node GR1 transmits a data correspondence table St to the network nodes GN1 to GN6. The data correspondence table St may be generated by the controller 110 or the root node GR1, and includes at least one codec rule. Each codec rule includes a category field, a length field, and a content field for defining different codes in a data packet. An example of the configuration of the data correspondence table St will be described later.

[0034] In one embodiment, the controller 110 generates or updates the configuration data Sc1 according to the state of the network topology NT (for example, when a communication connection between the network nodes GN1-GN6 and an external device changes). The configuration data Sc1 is used to configure / designate each of the network nodes GN1-GN6 so as to establish a communication connection between each of the network nodes GN1-GN6 and a corresponding external device (for example, terminal devices TD1-TD3). At this time, the controller 110 transmits the configuration data Sc1 to the root node GR1.

[0035] In step S202, the root node GR1 receives the configuration data Sc1 from the controller 110, and converts the source code in the configuration data Sc1 into a compressed code based on the codec rule in the data correspondence table St to obtain the configuration code Sc2. Since the number of bytes of the source code is larger than the number of bytes of the compressed code, the data size of the configuration code Sc2 is smaller than that of the configuration data Sc1.

[0036] In one embodiment, since the configuration data Sc1 includes configuration sub-data of multiple network nodes GN1 to GN6, the root node GR1 may divide the configuration data Sc1 into multiple configuration sub-data and then convert them into different configuration codes corresponding to the network nodes GN1 to GN6. In addition, if some network nodes (e.g., GN4) do not need to connect to an external device at present, the root node GR1 does not need to send the configuration code Sc2 to the network nodes.

[0037] In step S203, the root node GR1 transmits the configuration code Sc2 to the network nodes GN1 to GN6. In step S204, each of the network nodes GN1 to GN6 converts / restores the configuration code Sc2 to the configuration data Sc1 based on the codec rule in the data correspondence table St, thereby enabling each of the network nodes GN1 to GN6 to identify the device settings of the external devices (e.g., terminal devices TD1 to TD3) to be connected from the configuration data Sc1 / configuration code Sc2. As a result, the network nodes GN1 to GN6 adjust (set / establish / release) the communication connections between the network nodes GN1 to GN6 and the corresponding external devices based on the configuration data Sc1.

[0038] After the controller 110 sets up a communication connection between the network topology NT and an external device by the configuration data Sc1, in step S205, the network nodes GN1 to GN6 receive transmission data from the terminal devices TD1 to TD3. The "transmission data" includes device data of the corresponding terminal device (e.g., TD1), and may include a connection request command between the terminal device (e.g., TD1) and the target device (e.g., TD3), and a file that the terminal device transmits to the target device. After the corresponding network node (e.g., GN3, GN5) receives the device data, the transmission data can be compressed and converted into a data code based on the codec rule in the data correspondence table. The data code is transmitted to the route node GR1, which transmits the data code to the corresponding target device via the network topology NT. This can reduce the number of transmission packets and reduce the risk of data collision.

[0039] For ease of understanding, the following description will be given by way of example of the "Data Correspondence Table St." The following is an example of a codec format (packet format) included in the Data Correspondence Table St. [Table 1]

[0040] The above table defines each field in the code, and the fields are arranged in the order of their code in the data packet. The "category field" corresponds to the first byte and indicates the category code of the data. The length field corresponds to the second byte and records the number of bytes contained in the contents field. The "contents field" corresponds to the other bytes after the second byte and records / indicates the content of the data actually being sent.

[0041] In one embodiment, the firmware of the controller 110, the root node GR1, and the network nodes GN1 to GN6 stores / sets in advance, for example, a correspondence between the category code and the data type. For example, "0x01 is the data source (id)", "0x02 is the time stamp", "0x03 is the temperature", "0x04 is the humidity", etc. In another embodiment, the correspondence between the category code and the data type may be transmitted, stored, or updated together with the data correspondence table.

[0042] Here, the coding method in some embodiments of the present disclosure will be described using transmission data as an example. The coding method is also applicable to the case where configuration data is compressed into configuration code. In this embodiment, the transmission data includes two pieces of content, a data source (id) and a timestamp, which are in JSON format (herein referred to as "source code").

[0043] {"id":"1234", “Timestamp”:1250999896491}

[0044] The transmission data is converted according to the codec format described above, and then converted to a hexadecimal code. For example, "1234" indicating the data source (id) is converted to "04D2" as shown in the following table. [Table 2]

[0045] Similarly, a timestamp "1250999896491" is converted to "0123456789ab" as shown in the following table. [Table 3]

[0046] According to the two tables above, the transmitted data is converted from JSON format into a hexadecimal code "010204D202060123456789ab" (simply referred to as "compressed code" here). This hexadecimal code can be interpreted according to the table above. The first code "01" is recorded as "category is id", and the next code "02" is recorded as "code length is 2 bytes (0x02)". The next code "04D2" is recorded as "id contents (i.e., contents after converting 1234 to hexadecimal)".

[0047] Furthermore, the latter half of the code is interpreted in the same way. The code "02" records "the category is a time stamp", the code "06" records "the code length is 6 bytes (0x06)", and the code "0123456789ab" records "the contents of the time stamp (1250999896491 is the contents after conversion to hexadecimal)". Therefore, the network nodes GN1 to GN6 can decode the received transmission data based on the data correspondence table St and correctly convert the compressed code into source code (for example, the contents in JSON format). Similarly, the root node GR1 or the network nodes GN1 to GN6 encode or decode the received data. For example, the "network name, assigned port number, password" in the configuration data Sc1 can be converted in the same way and compressed into the configuration code Sc2.

[0048] That is, when the root node GR1 or the network nodes GN1 to GN6 convert the data code into transmission data (or restore the configuration code Sc2 into the configuration data Sc1), the root node GR1 or the network nodes GN1 to GN6 first identifies the category code from the first byte (i.e., the code / byte corresponding to the category field in the compressed code) based on the codec rule in the data correspondence table St. For example, 0x01 represents an id. Next, the "number of bytes contained in the content field" is identified based on the second byte (i.e., the code / byte corresponding to the length field in the compressed code). For example, 0x02 represents 2 bytes. Finally, the root node GR1 or the network nodes GN1 to GN6 converts the "bytes belonging to the content field" to restore and identify the content (e.g., 1234) transmitted by the source code.

[0049] In some embodiments, the controller 110 may generate or update the configuration data Sc1 when a new external device is connected to the network topology NT. Specifically, as shown in FIG. 1, when the terminal device TD3 is ready to connect to the network topology NT, the controller 110 controls the root node GR1 to send the configuration code Sc2 to the corresponding network node (i.e., GN3), and the controller 110 controls the root node GR1 to send the data correspondence table St to the network node on the corresponding routing path or to all network nodes, so that the network node GN3 can correctly encode and decode.

[0050] The root node GR1 and the network nodes GN1 to GN6 transmit data to be transmitted in a compressed packet format based on the codec rules in the data correspondence table St in order to reduce the amount of data transmission. When data is to be transmitted outside the network topology NT (for example, to the controller 110 or the terminal devices TD1 to TD3), the root node GR1 and the network nodes GN1 to GN6 restore the compressed data based on the decoding rules in the data correspondence table St in order to reduce the risk of data collision.

[0051] Here, we will explain "(D) Data Backup" in the network management method according to the present disclosure. In some embodiments, the root node GR1 periodically backs up various network data received from the network nodes GN1 to GN6 in the internal memory of the root node GR1. Similarly, each of the network nodes GN1 to GN6 may periodically back up the received network data in its internal memory. "Network data" refers to any data transmitted by a network protocol, such as the above-mentioned configuration data / configuration code, transmission data / data code, etc.

[0052] "Data backup" allows some nodes in the network topology to maintain operation even when a connection abnormality occurs, and to automatically connect and transmit data after the connection is restored to normal. For example, when the connection between the root node GR1 and the controller 110 is disconnected, the root node GR1 records the upload data last uploaded to the controller 110. While the connection between the root node GR1 and the controller 110 remains disconnected, the root node GR1 temporarily stores the transmission data (which may be compressed data code) transmitted from the other network nodes GN1 to GN6 in the internal memory of the root node GR1. In other words, the transmission data has not been uploaded to the controller 110 because the reception time of the transmission data is later than the reception time of the upload data. In some embodiments, the root node GR1 sequentially stores multiple transmission data based on the time of reception, or the root node GR1 records the time when the transmission data is stored in the internal memory.

[0053] In addition, the root node GR1 continues to periodically determine the connection state with the controller 110. When the root node GR1 determines that the connection state with the controller 110 has been restored, the root node GR1 uploads the "transmission data that has not yet been uploaded to the controller 110" in the internal memory to the controller 110. In some embodiments, the root node GR1 may sequentially upload the transmission data to the controller 110 based on the time point (i.e., the time point when the data was received or the time point when the data was stored in the internal memory).

[0054] Similarly, the network nodes GN1 to GN6 can store the received transmission data according to the connection state. When the network nodes GN1 to GN6 determine that the connection with the root node GR1 has been disconnected, the network nodes GN1 to GN6 record the upload data last uploaded to the root node GR1. While the connection between the network nodes GN1 to GN6 and the root node GR1 remains disconnected, the network nodes GN1 to GN6 temporarily store the transmission data (which may be compressed data code) transmitted from other network nodes or terminal devices (e.g., TD1) in the internal memory of the network nodes GN1 to GN6. When the network nodes GN1 to GN6 determine that the connection with the root node GR1 has been restored, the network nodes GN1 to GN6 sequentially upload the "transmission data not yet uploaded to the root node GR1" in the internal memory to the root node GR1.

[0055] In addition to the configuration data Sc1, the transmission data, data correspondence table, network data, etc. mentioned in the above embodiments may also be compressed and coded based on the above (B) information compression and (C) data correspondence methods, and transmitted between the root node GR1 and the network nodes GN1 to GN6.

[0056] The present disclosure uses the aforementioned network management method to correlate, synchronize and back up information of root nodes / network nodes using limited network bandwidth, and does not require full firmware update in the root nodes / network nodes, which not only improves management efficiency but also makes it easy to implement.

[0057] The elements, method steps, or technical features in each of the above-described embodiments can be combined with each other without being limited to the order of description in words or the order of description in the drawings in this disclosure.

[0058] Although the present disclosure has been disclosed above by the embodiments, the embodiments do not limit the present disclosure, and those skilled in the art may make various changes and modifications without departing from the spirit and scope of the present disclosure. Therefore, the scope of protection of the present disclosure is based on the contents specified in the following claims. [Explanation of symbols]

[0059] 100 Network Management Systems 110 Controller Sc1 configuration data Sc2 configuration code Sc2-1 Configuration code Sc2-2 Configuration code Sr Routing Information St Data Compatibility Table TB Routing Table GR1 Root node GR2 root node GN1~GN6 network nodes GNa~GNc network nodes TD1~TD3 Terminal equipment NT Network Topology

Claims

1. A root node; a plurality of network nodes communicatively connected to the root node to form a network topology with the root node and to receive a data correspondence table from the root node; the root node is configured to receive configuration data, compress the configuration data into a configuration code based on the data correspondence table, and transmit the configuration code to the plurality of network nodes; the plurality of network nodes are configured to convert the configuration code to the configuration data based on the data correspondence table, and adjust a communication connection with an external device based on the configuration data; Network Management Systems.

2. 、 2. The network management system of claim 1, wherein the data correspondence table includes a codec rule, and the plurality of network nodes are used to convert source code in the configuration data into compressed code based on the codec rule, and the number of bytes of the source code is greater than the number of bytes of the compressed code.

3. 3. The network management system of claim 2, wherein the codec rule includes a category field, a length field, and a content field, the category field being used to record a category code, and the length field being used to record a number of bytes included in the content field.

4. 4. The network management system of claim 3, wherein the plurality of network nodes are configured to identify the number of bytes included in the content field based on a code in the compressed code that corresponds to the length field to identify the category code and convert the compressed code to the source code.

5. 5. The network management system of claim 4, wherein the compressed code is in hexadecimal format.

6. 2. The network management system of claim 1, further comprising a controller communicatively coupled to the root node and configured to receive from the root node a routing table corresponding to the network topology, and to generate the configuration data based on the routing table.

7. 7. The network management system of claim 6, wherein the controller is configured to generate or update the configuration data when the routing table determines that a routing path corresponding to the external device in the network topology has changed.

8. The network management system according to claim 6, wherein the root node is configured to periodically back up the network data received from the network nodes to an internal memory of the root node.

9. 7. The network management system according to claim 6, wherein when a connection between the root node and the controller is disconnected, the root node is used to record the upload data last uploaded to the controller and store a plurality of transmission data received from the plurality of network nodes in an internal memory of the root node, and the reception times of the plurality of transmission data are later than the reception times of the upload data.

10. 10. The network management system of claim 9, wherein the root node is further configured to determine a connection status between the root node and the controller, and when the root node regains connection with the controller, the root node is configured to upload the plurality of transmission data stored in the internal memory to the controller.

11. transmitting the data correspondence table to a plurality of network nodes via a root node, the plurality of network nodes being communicatively connected to the root node and forming a network topology with the root node; compressing the configuration data into a configuration code based on the data correspondence table via the root node, and transmitting the configuration code to the network node; converting the received configuration code into the configuration data based on the data correspondence table via the plurality of network nodes; and adjusting communication connections between the plurality of network nodes and an external device based on the configuration data. Network management methods.

12. 12. The network management method of claim 11, wherein the data correspondence table includes a codec rule, and the step of compressing the configuration data into the configuration code based on the data correspondence table includes a step of converting source code in the configuration data into compressed code based on the codec rule, wherein the number of bytes of the source code is greater than the number of bytes of the compressed code.

13. 13. The network management method of claim 12, wherein the codec rule includes a category field, a length field, and a content field, the category field being used to record a category code, and the length field being used to record a number of bytes included in the content field.

14. The step of converting the received configuration code into the configuration data includes: identifying said category code; and converting the compressed code to the source code by identifying the number of bytes contained in the content field based on a code in the compressed code that corresponds to the length field.

15. 15. The method of claim 14, wherein the compressed code is in hexadecimal format.

16. receiving, by a controller, from the root node a routing table corresponding to the network topology; The method of claim 11, further comprising: generating the configuration data based on the routing table.

17. 17. The network management method of claim 16, further comprising the step of generating or updating the configuration data when the routing table determines that a routing path corresponding to the external device in the network topology has changed.

18. 17. The network management method according to claim 16, further comprising the step of periodically backing up the network data received from the network nodes via the root node in an internal memory of the root node.

19. When the connection between the root node and the controller is disconnected, recording the last uploaded data to the controller; 20. The network management method of claim 16, further comprising: storing a plurality of transmission data received from the plurality of network nodes in an internal memory of the root node, wherein a reception time of the plurality of transmission data is later than a reception time of the upload data.

20. determining a connection state between the root node and the controller; 20. The network management method of claim 19, further comprising the step of: uploading the plurality of transmission data stored in the internal memory to the controller when the root node regains connection with the controller.

Images