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] This disclosure relates to the management of network topology, and particularly to a network management system and a network management method.

Background Art

[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 most important factors that users value.

Summary of the Invention

Problems to be Solved by the Invention

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

[0004] In view of the above problems, an object of this disclosure is to provide a network management system and a network management method.

Means for Solving the Problems

[0005] To achieve the above object, a network management system according to this disclosure includes a root node, and a plurality of network nodes communicably connected to the root node to form a network topology with the root node and receiving 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 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] To achieve the above objectives, the network management method relating to this disclosure includes the steps of: transmitting a data correspondence table to a plurality of network nodes via a root node, wherein the plurality of network nodes are communicably connected to the root node and form a network topology with the root node; compressing configuration data into configuration code based on the data correspondence table via the root node and transmitting the configuration code to the network nodes; converting the received configuration code into configuration data based on the data correspondence table via the plurality of network nodes; and coordinating communication connections between the plurality of network nodes and external devices based on the configuration data. [Effects of the Invention]

[0007] The network management system and network management method described herein can reduce the amount of data transmitted in the network topology by compressing configuration data, without affecting the stability of signal transmission. Furthermore, because the root node and network nodes confirm the type and format of data using a data correspondence table, it becomes unnecessary to update the entire firmware on the network node when the type of external device or the form of data to be transmitted changes, thereby streamlining the system operation and maintenance management of the network. [Brief explanation of the drawing]

[0008] [Figure 1] This is a schematic diagram illustrating a network management system according to several embodiments of the present disclosure. [Figure 2] This is a process flowchart illustrating a network management method according to several embodiments of the present disclosure. [Modes for carrying out the invention]

[0009] Several embodiments of this disclosure will be described below with reference to the drawings. For clarity, many practical details will also be described below. However, it should be understood that these practical details are not applicable to limit this disclosure. In other words, these practical details are not necessary in some embodiments of this disclosure. Also, for the sake of simplification of the drawings, some conventional structures and elements are shown simply and schematically in the drawings.

[0010] In this specification, when an element is referred to as “connected” or “coupled,” it may mean “electrically connected” or “electrically coupled.” “Connected” or “coupled” is also used to indicate coordinated operation or interaction between two or more elements. In this specification, terms such as “first,” “second,” etc., are used solely to distinguish between elements or methods of operation having the same technical terminology, and are not intended to imply or suggest any particular order or priority, or to limit this disclosure, unless explicitly indicated by the context.

[0011] Figure 1 is a schematic diagram showing a network management system 100 according to several embodiments of the present disclosure. In one embodiment, the network management system 100 is applied to manage mesh networks such as FANs (Field Area Networks) built using Wi-SUN (Wireless Smart Utility Network) network transmission technology, or network topologies built using LoRa, a low-power wide-area network technology. The present disclosure is not limited to these, and the network management system 100 is also applicable to tree networks or other types of mesh networks.

[0012] As shown in Figure 1, the network management system 100 includes a controller 110, a root node GR1, and a plurality of network nodes GN1 to GN6. In some embodiments, the root node GR1 and network nodes GN1 to GN6 are each gateways. The root node GR1 is used to translate data packets between different network communication protocols and is connected to the cloud controller 110 via wired or wireless network communication. The root node GR1 and network nodes GN1 to GN6 are communicated with each other to form a network topology NT, and in some embodiments, the controller 110 may be communicated with multiple root nodes simultaneously to manage multiple network topologies, such as another network topology formed by the root node GR2 and network nodes GNa to GNc shown in Figure 1. Those skilled in the art will understand how data is transmitted between network topologies, and therefore will not be described here.

[0013] Each network node chooses to connect to the node with the strongest signal strength among its neighbors, and connects to the root node via other nodes. The following explanation uses network topology NT as an example, where network node GN5 is connected to network node GN2, and then to the root node GR1 via network node GN2. Network node GN5 can transmit data to multiple terminal devices TD1-TD3, which are connected to network topology NT, through network topology NT. Here, the path from network node GN5 to the root node GR1 is referred to as the "routing path."

[0014] In one embodiment, the controller 110 can generate configuration data Sc1 in response to administrative requests. The configuration data Sc1 is used to establish a communication connection between network nodes GN1~GN6 and external devices (e.g., terminal devices TD1~TD3) for the transmission of data such as network name, assigned port number, and password. As shown in Figure 1, terminal devices TD1~TD3 may first be connected to the corresponding network nodes GN3 and GN5. Next, the controller 110 sends the configuration data Sc1 to the root node GR1, and the root node GR1 sends the configuration data Sc1 to the corresponding network nodes GN3 and GN5, enabling network nodes GN3 and GN5 to establish a communication connection with terminal devices TD1~TD3.

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

[0016] Furthermore, if the communication connection between any of the network nodes GN1 to GN6 and an external device changes, the controller 110 (for example, controlled by the network administrator) can generate or update configuration data Sc1 on the root node GR1 and send the compressed new configuration data to the corresponding network nodes GN1 to GN6 to adjust the communication connection between the corresponding network nodes GN1 to GN6 and the external device. "Change in communication connection between network nodes and external devices" also means a change in the type of external device or the type of data being transmitted.

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

[0018] In some embodiments, since the controller 110 needs to manage a large number of network nodes in the network topology simultaneously, the configuration data may be compressed, converted, and encoded into other formats for transmission to ensure smooth and stable data transmission. Details of compression / conversion / codecs will be described later.

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

[0020] This section describes "(A) Monitoring and Management" in the network management method relating to this disclosure. As mentioned above, each network node GN1 to GN6 automatically connects to the other node with the strongest signal strength (for example, an adjacent network node) to form a network topology NT. When network nodes GN1 to GN6 receive configuration data Sc1 from the root node GR1, network nodes GN1 to GN6 connect to external devices (for example, terminal devices TD1 to TD3) based on the relevant device information recorded in the configuration data Sc1.

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

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

[0023] In the above content, it records respectively that "network node GN1 is directly connected to root node GR1" and "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 the associated devices (i.e., communication connections between nodes) of each network node GN1 to GN6 are recorded.

[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 network nodes GN1 to GN6 or the load distribution of 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 when each network node GN1 to GN6 changes the communication connection. The controller 110 determines the signal strength based on this (for example, if the switching frequency of a specific network node is too high, the signal may not be good), 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] This section describes "(B) Information Compression" in the network management method relating to this disclosure. The controller 110 generates, adjusts, or updates configuration data Sc1 based on the routing table TB, and controls the root 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 sent or requested from terminal devices TD1 to TD3 via the network topology NT.

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

[0028] In network transmission, the root node GR1 sends configuration code Sc2-1 to network node GN1 and configuration code Sc2-2 to network node GN3. The configuration code is split into configuration code Sc2-1 and configuration code Sc2-2 according to the requirements of network node GN1 and network node GN3, respectively. In other words, network transmission is treated as two paths, and network node GN1 is used only to bypass configuration code Sc2-2 and never receives it.

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

[0030] In some embodiments, the controller 110, root node GR1, and network nodes GN1 to GN6 store corresponding encoding and decoding rules (hereinafter abbreviated as "codec rules") so that received data packets can be decoded and their correct contents restored. In one embodiment, the configuration data may be in a JavaScript® Object Notation (JSON) structured format and may include decimal values ​​such as temperature and voltage values, and the encoded configuration data may be in hexadecimal format. The codec rules record the content represented by each byte in the data packet and the corresponding content. 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] This section describes "(C) Data correspondence" in the network management method relating to this disclosure. Since internal settings may not always be perfectly identical between different devices / nodes, the root node GR1 periodically or proactively (for example, when the network topology NT changes) sends a data correspondence table St to network nodes GN1-GN6 so that each network node GN1-GN6 can encode and decode in the same way.

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

[0033] Figure 2 is a process flowchart illustrating a network management method according to several embodiments of the present disclosure, including the (B) information compression and (C) data mapping operations described above. In step S201, the root node GR1 transmits a data mapping table St to network nodes GN1 to GN6. The data mapping 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 to define different codes within a data packet. An example of the configuration of the data mapping table St will be described later.

[0034] In one embodiment, the controller 110 generates or updates configuration data Sc1 according to the state of the network topology NT (for example, when the communication connection between network nodes GN1 to GN6 and external devices changes). The configuration data Sc1 is used to configure / specify each network node GN1 to GN6 to establish a communication connection between each network node GN1 to GN6 and the corresponding external device (for example, terminal devices TD1 to 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 configuration data Sc1 from the controller 110 and converts the source code in configuration data Sc1 into compressed code based on the codec rules in the data correspondence table St to obtain configuration code Sc2. Since the number of bytes in the source code is larger than the number of bytes in the compressed code, the data size of configuration code Sc2 is smaller than that of configuration data Sc1.

[0036] In one embodiment, since the configuration data Sc1 includes configuration subdata for multiple network nodes GN1 to GN6, the root node GR1 may divide the configuration data Sc1 into multiple configuration subdata and then convert each into a different configuration code corresponding to each network node GN1 to GN6. Also, if some network nodes (e.g., GN4) do not currently need to connect to an external device, the root node GR1 does not need to send the configuration code Sc2 to the network node.

[0037] In step S203, root node GR1 sends configuration code Sc2 to network nodes GN1 to GN6. In step S204, each network node GN1 to GN6 converts / restores configuration code Sc2 to configuration data Sc1 based on the codec rules in data correspondence table St, allowing each network node GN1 to GN6 to identify the device settings of the external devices (e.g., terminal devices TD1 to TD3) to which it connects from the configuration data Sc1 / configuration code Sc2. As a result, network nodes GN1 to GN6 adjust (set / establish / disconnect) the communication connection between network nodes GN1 to GN6 and the corresponding external devices based on the configuration data Sc1.

[0038] After the controller 110 sets up the communication connection between the network topology NT and the external device using configuration data Sc1, in step S205, network nodes GN1 to GN6 receive transmission data from terminal devices TD1 to TD3. The "transmission data" includes device data of the corresponding terminal device (e.g., TD1), and may also include connection request commands between the terminal device (e.g., TD1) and the target device (e.g., TD3), or files that the terminal device sends to the target device. After the corresponding network nodes (e.g., GN3, GN5) receive the device data, they can compress the transmission data and convert it into a data code based on the codec rules in the data correspondence table. The data code is sent to the root node GR1, which then transmits the data code to the corresponding target device via the network topology NT. This reduces the number of transmission packets and lowers the risk of data collisions.

[0039] To facilitate understanding, we will use "Data Mapping Table St" as an example for explanation. The following is an example of a codec format (packet format) included in Data Mapping Table St. [Table 1]

[0040] The table above defines each field in the code, and each field is listed in the code order of 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 Content field. The "Content field" corresponds to the remaining bytes after the second byte and records / indicates the content of the data actually being transmitted.

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

[0042] Here, using transmitted data as an example, the codec method in several embodiments of this disclosure will be described. Note that the codec method is also applicable when "compressing configuration data into configuration code." In this embodiment, the transmitted data contains two contents: "data source (id)" and "timestamp," which are in JSON format (referred to here as "source code").

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

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

[0045] Similarly, the 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 to a hexadecimal code (simply abbreviated here as "compression code") called "010204D202060123456789ab". This hexadecimal code can be interpreted according to the table above. The first code "01" records "category is id", and the next code "02" records "code length is 2 bytes (0x02)". The following code "04D2" records "id content (i.e., the content after converting 1234 to hexadecimal)".

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

[0048] In other words, when the root node GR1 or network nodes GN1-GN6 converts data code into transmission data (or restores configuration code Sc2 to configuration data Sc1), the root node GR1 or network nodes GN1-GN6 first identify 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 rules of the data correspondence table St. For example, 0x01 represents id. Next, based on the second byte (i.e., the code / byte corresponding to the length field in the compressed code), they identify the "number of bytes contained in the content field". For example, 0x02 represents 2 bytes. Finally, the root node GR1 or network nodes GN1-GN6 convert the "bytes belonging to the content field" to restore and identify the content transmitted by the source code (e.g., 1234).

[0049] In some embodiments, the controller 110 may generate or update configuration data Sc1 when a new external device is connected to the network topology NT. Specifically, as shown in Figure 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 configuration code Sc2 to the corresponding network node (i.e., GN3), and also controls the root node GR1 to send data correspondence table St to the corresponding network nodes on the routing path or to all network nodes so that the network node GN3 can correctly encode and decode it.

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

[0051] This section describes "(D) Data Backup" in the network management method relating to this disclosure. In some embodiments, the root node GR1 periodically backs up various network data received from network nodes GN1 to GN6 to its internal memory. Similarly, each network node GN1 to GN6 may periodically back up the network data it receives to its internal memory. "Network data" refers to any data transmitted by the network protocol, such as the configuration data / configuration code and transmission data / data code mentioned above.

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

[0053] Furthermore, the root node GR1 continuously checks the connection status with the controller 110 periodically. When the root node GR1 determines that the connection status with the controller 110 has been restored, the root node GR1 uploads the "transmit data that has not yet been uploaded to the controller 110" from its internal memory to the controller 110. In some embodiments, the root node GR1 may sequentially upload the transmit data to the controller 110 based on the time (i.e., the time of reception or the time of storage in internal memory).

[0054] Similarly, network nodes GN1 to GN6 can store received transmission data depending on the connection status. If network nodes GN1 to GN6 determine that the connection with root node GR1 has been lost, they record the last uploaded data they uploaded to root node GR1. While the connection between network nodes GN1 to GN6 and root node GR1 remains lost, network nodes GN1 to GN6 temporarily store transmission data (which may be compressed data code) sent from other network nodes or terminal devices (e.g., TD1) in their internal memory. If network nodes GN1 to GN6 determine that the connection with root node GR1 has been restored, they sequentially upload any "transmission data that has not yet been uploaded to root node GR1" from their internal memory to root node GR1.

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

[0056] This disclosure describes a network management method that allows for the association, synchronization, and backup of root node / network node information using limited network bandwidth. This management method does not require a complete firmware update on the root node / network node, thus improving management efficiency and ease of implementation.

[0057] The elements, method steps, or technical features in each of the embodiments described above may be combined with each other, and are not limited to the order in which they are described in the text or drawings in this disclosure.

[0058] While the embodiments of this disclosure have been disclosed as described above, the embodiments are not limiting, and those skilled in the art can make various modifications and alterations as long as they do not deviate from the spirit and scope of this disclosure. Accordingly, the scope of protection of this disclosure is based on the claims set forth below. [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 Correspondence Table TB routing table GR1 Root Node GR2 Root Node GN1-GN6 Network Nodes GNa~GNc Network Node TD1~TD3 Terminal Devices NT Network Spectrum

Claims

1. The root node and The network includes a plurality of network nodes that are communicably connected to the root node, form a network topology with the root node, and receive a data correspondence table from the root node, The aforementioned data correspondence table includes the codec format and codec rules of the received configuration data. The root node is configured to receive configuration data, identify the category code, data length, and data content of the data to be sent and received based on the codec format of the data correspondence table, generate a codec format (packet format), and compress the configuration data into a compressed code which is a configuration code by converting (encoding) the data content based on the category code and the corresponding codec rule, and then transmit the configuration code to the multiple network nodes. The plurality of network nodes are configured to convert the configuration code into the configuration data based on the data correspondence table and to adjust the communication connection with external devices based on the configuration data. Network management system.

2. The network management system according to claim 1, wherein the root node is used to convert the source code in the configuration data into compressed code based on the codec rules, and the number of bytes in the source code is greater than the number of bytes in the compressed code.

3. The network management system according to 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 the number of bytes contained in the content field.

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

5. The network management system according to claim 4, wherein the compression code is in hexadecimal format.

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

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

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

9. The network management system according to claim 8, wherein if the connection between the root node and the controller is disconnected, the root node records the last uploaded data uploaded to the controller and is used to store a plurality of transmitted data received from the plurality of network nodes in the root node's internal memory, and the reception time of the plurality of transmitted data is later than the reception time of the uploaded data.

10. The network management system according to claim 9, wherein the root node further determines the connection status between the root node and the controller, and when the root node restores the 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. A root node transmits a data mapping table to multiple network nodes, wherein the data mapping table includes the codec format and codec rules for the configuration data to be received, and the multiple network nodes are communicately connected to the root node and form a network topology with the root node. The root node identifies the category code, data length, and data content of the data to be received based on the codec format of the data correspondence table, generates a codec format (packet format), and compresses the configuration data into a compressed code which is a configuration code by converting (encoding) the data content based on the category code and the corresponding codec rule, and transmits the configuration code to the network node. The steps include: the plurality of network nodes converting the received configuration code into the configuration data based on the data correspondence table; The plurality of network nodes include the step of adjusting the communication connection between the plurality of network nodes and an external device based on the configuration data, Network management methods.

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

13. The network management method according to 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 the number of bytes contained in the content field.

14. The step of converting the received configuration code into the configuration data is: The step of identifying the category code, The network management method according to claim 13, comprising the steps of identifying the number of bytes contained in the content field based on the code in the compressed code corresponding to the length field, and converting the compressed code into the source code.

15. The network management method according to claim 14, wherein the compression code is in hexadecimal format.

16. The controller receives a routing table corresponding to the network topology from the root node, The network management method according to claim 11, further comprising the step of the controller generating the configuration data based on the routing table.

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

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

19. If the connection between the root node and the controller is disconnected, the root node records the last uploaded data uploaded to the controller. The network management method according to claim 18, further comprising the step of the root node storing a plurality of transmission data received from a plurality of network nodes in the root node's internal memory, wherein the reception time of the plurality of transmission data is later than the reception time of the upload data.

20. The root node determines the connection status between the root node and the controller, The network management method according to claim 19, further comprising the step of the root node uploading the plurality of transmission data stored in its internal memory to the controller once the root node has restored connection with the controller.

Images