KR20010094095A - A method of management data synchronization for web based data transmission equipment - Google Patents

Abstract

PURPOSE: A method for synchronizing management data of a web-based transmission equipment is provided to reduce a traffic of a system by generating a check-sum identifying the generation of a data updating. CONSTITUTION: A web server composes transmitted management data to a tree structure of a leaf node and transmits it to a client(S110). The web server creates periodically a check-sum indicating a update of corresponding leaf node data and compares it with an old check-sum(S120). The client compares the received check-sum to the old check-sum and requires updated location information of corresponding leaf management data by using a request datagram to the web server(S130). The web server searches a data corresponding to the location information of the request datagram and transmits it to the corresponding client by using a response datagram. In case that an error is occurred in the location information of the request datagram, the web server demands a re-transmission of leaf node location information to the client by using an error datagram. In case that the client receives updated data with the response datagram, the client updates the corresponding leaf node data. In case that the client receives the re-transmission of the leaf node location information with the error datagram, the client determines as to whether the client transfers it, or receives the data tree according to the state of an error.

Description

A METHOD OF MANAGEMENT DATA SYNCHRONIZATION FOR WEB BASED DATA TRANSMISSION EQUIPMENT}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an efficient synchronous of data transmitted in a web environment consisting of a server and a client managing communication system equipment or transmission system equipment. The present invention relates to a method for quickly synchronizing data even when there is little traffic transmitted.

Communication or transmission system equipment is a fast and accurate exchange of information between remote users, the wider the service area and the more subscribers, the greater the number of relay transmission system equipment or terminal transmission system equipment, each system equipment as described above Since information is transmitted and received by interaction, when a failure or error occurs in a particular system equipment, the functions of other system equipment are affected.

By managing the operation information or management data of the above system equipment in the web server, not only can be centrally managed, but also the maintenance and operation manager can access the designated web server even when moving to a specific area using the client terminal. Therefore, maintenance and operation management data of the relevant system equipment and related system equipment can be checked or searched.

Therefore, the shared data between the client and the web server should be quickly synchronized with the latest data.

Hereinafter, a method of synchronizing management data of a web-based transmission device according to the prior art will be described with reference to the accompanying drawings.

1 is a functional configuration diagram of a general web-based transmission equipment management system.

Referring to the accompanying drawings as described above, a general Web (Based) transmission equipment management system, communication or multiple transmission system equipment 10 for transmitting and receiving data or information between the remote subscriber, and

Dedicated network 20 that is a path or line for transmitting and receiving transmission data and operation management data between the transmission system maintenance 10,

A web server connected to the dedicated network 20 and including a management processor of server (MPS) 35 for transmitting and receiving and managing operation management information and control information of each transmission system equipment 10 ( 30) and,

A general communication public network 40 connected to the web server 30,

A management processor (MPC) connected to the web server 30 through the public network 40 and processing management data while moving by the maintenance and operation manager of the transmission system equipment 10. It consists of a client (50) comprising a (55).

Hereinafter, a method of synchronizing operation management data of a transmission system device or a transmission device using a general web-based configuration as described above will be described in detail with reference to the accompanying drawings.

The plurality of transmission devices 10 transmits and receives communication data to and from another transmission device 10, and simultaneously manages all of the hardware and software configuration, current operation status, system capacity, and failure status of each transmission device 10. Data is transmitted to the web server 30 through the dedicated network 20 and the necessary control signal is applied.

The MPS 35, which is a processor of the web server 309, processes and stores management data applied from the plurality of transmission devices 10, and updates old management data with new management data. .

The maintenance and operation management personnel of the transmission equipment 10 as described above are for the management of transmission equipment 10 scattered locally or for management data on the current operating state of all transmission equipment 10 in a specific region. You can check or search.

As described above, the terminal device used for checking and searching may be a portable computer or a notebook computer. The terminal device is called a client 50 and has a client processor (MPC) 55 therein.

The client 50 is connected to the web server 30 through the public network 40, and performs the synchronization of the management data in order to maintain the same as the common management data of the web server 30. .

The management system based on the Web configuration as described above is configured to synchronize the data as described above between the processor MPS 35 of the web server 30 and the processor MPC 55 of the client 50. (Synchronous) is required, and there are two methods for synchronizing data, polling and event handling.

In the polling processing method, the MPC 55 of the client 50 periodically requests synchronization data to the MPS 35 of the web server 30, and downloads it from the MPS 35. When the MPC 55 is updated using the received data, there is a problem that traffic occurs even when there is no data to be updated.

As another embodiment of the polling processing method as described above, in the MPC 55, when the operator needs to process new data, such as for maintenance management purposes or routine data retrieval, data is transmitted to the MPS 35. By making a request, management data in the MPS 35 is downloaded whether or not there is newly updated data.

Therefore, the polling data processing scheme as described above unilaterally downloads data from the MPC 55 regardless of whether management data has been updated in the MPS 35, resulting in a congestion of traffic. In a traffic congestion situation, there is a problem that the necessary data is not received at the required time and delayed, and the performance of the web management system is degraded.

In addition, in the event processing method, when management data is changed or updated in the MPS 35 of the web server 30, the MPS 35 updates the MPC 55 by itself. By transmitting data or all of the corresponding data, the MPC 55 downloads the management data received from the MPS 35 and downloads the changed part or the whole part.

However, in the event processing method as described above, if an error occurs while downloading the update data transmitted from the MPS 35 from the MPC 55 or the MPC 55 does not receive it. Since it cannot be confirmed by the MPS 35, there is a problem in that synchronization of management data to be managed in common (Synchronous) is difficult or difficult.

According to the present invention, a web server for intensively managing data periodically checks whether data update has occurred, and generates and transmits checksum information indicating update of data to the client when data update occurs. It is an object of the present invention to provide a data synchronization method for downloading data requiring updating by determining and comparing checksum information with existing checksum information and transmitting location information of data to be updated to the web server only in other cases.

The present invention has been made in order to achieve the above object, in the management data synchronization system of the web-based transmission device consisting of a web server and a client, the web server by grouping the transmitted management data in a tree structure of leaf nodes A first step of transmitting to the client, and the web server periodically generating a checksum indicative of an update of the corresponding leaf node data, and in comparison with the previous checksum, transferring the newly generated checksum of the leaf node to the client. And a second step of the client, comparing the authorized checksum with the previous checksum, and in other cases, requesting the web server to update the location information of the leaf management data using the request datagram. The web server uses the location information of the request datagram requested for the update. The fourth step of retrieving the data to be transmitted and using the response datagram to the corresponding client; and if an error occurs in the location information of the request datagram requested for the update in the above step, the leaf node is transmitted to the client using the error datagram. A fifth step of requesting retransmission of the location information, and when the client receives the update data in the response datagram, the client updates the data of the corresponding leaf node and an error in the case of requesting retransmission of the leaf node location information in the error datagram And a sixth process of determining and performing whether to retransmit or to receive the data tree again according to the state of the management system.

1 is a functional configuration diagram of a general web-based transmission equipment management system,

2 is a structural diagram of a data tree according to an embodiment of the present invention;

3 is a structural diagram of each datagram used according to an embodiment of the present invention;

4 is a flowchart for synchronizing management data in a web server according to an embodiment of the present invention;

5 is a flowchart for synchronizing management data in a client according to an embodiment of the present invention.

** Explanation of symbols on the main parts of the drawing **

10: transmission equipment 20: transmission network

30: Web Servo 35: MPS

40: public network 50: client

55: MPC 60: Root

62: parent node 64: leaf node

Hereinafter, with reference to the accompanying drawings will be described a management data synchronization method of a web-based transmission equipment according to the technology of the present invention.

FIG. 2 is a structural diagram of a data tree according to an embodiment of the present invention, FIG. 3 is a structural diagram of each datagram used according to an embodiment of the present invention, and FIG. 4 is an embodiment of the present invention. 5 is a flowchart for synchronizing management data in a web server, and FIG. 5 is a flowchart for synchronizing management data in a client according to an embodiment of the present invention.

Referring to the accompanying drawings and the functional configuration of the general web-based transmission equipment management system as described above, the management data synchronization method of the web-based transmission equipment according to the technology of the present invention, generated in the communication equipment or transmission equipment (10) Management data is received from the web server 30 and processed by the MPS 35, which is a processor of the web server 30, as an embodiment of the leaf node illustrated in FIG. The first process of the first step (S110) of configuring the management data in a tree structure,

The MPS 35 of the web server 30 generates a check-sum that indicates an update status such as generation time or version of leaf node management data having the tree structure. Step S120; A third step (S130) of determining whether a request has been made for the tree structure of data from the client (50) and if not requesting again; A fourth step (S140) of transmitting the tree structure of the data to the corresponding client (50) when the tree structure of the management data is requested in the step (S130); A fifth step (S150) of the subroutine for performing the operation requested by the client 50; A sixth step (S160) of driving a timer that counts a time at a predetermined period set by the MPS 35 of the web server 30; A seventh step (S170) of determining whether or not the timer has elapsed by a predetermined cycle by the step (S160); An eighth step (S180) of generating a second check (S180) by updating the checksum of the corresponding management data generated in the second step (S120) when the timer reaches the set period of time in the step (S170); A ninth step (S190) of feeding back to the sixth step (S160) if it is determined whether the checksum values generated in the second step (S120) and the eighth step (S180) are different from each other; If the checksum of the previous period is different from the current updated checksum in step S190, a second process including a tenth step S200 of delivering the updated checksum to the corresponding client 50;

An eleventh step (S210) of determining whether the client 50 has requested the corresponding tree structure of management data from the web server 30, and if not, if the client 50 has requested again; In step S210, if the tree structure of management data is requested to the web server 30, the tree structure is received and the management data is received from the web server 30 using the location information by the corresponding leaf node. S220); A thirteenth step S230 of checking leaf node management data of the client 50 to generate a checksum; A fourteenth step S240 in which it is determined whether the updated checksum is received from the web server 30 and if not, the determination is again made; A fifteenth step (S250) of comparing the checksums of the client (50) with the update checksums received from the web server (30) if the updated checksum is received in the step (S240); If there is another checksum value in the step S250, as an example, as shown in FIG. 3, as shown in FIG. 3, a request datagram including a location information of management data requiring retransmission is generated (S260). ; A third process comprising a seventeenth step S270 of transmitting the request datagram according to the step S260 to the web server 30;

The web server 30, upon receiving the request datagram from the client 50, determining, by the subroutine of the fifth step S150, whether the request datagram has been received (S151); A 52nd step (S152) of analyzing the request datagram received by the above step (S151) and analyzing the location information; A fifty-third step S153 of searching for leaf nodes corresponding to the position information interpreted by the step S152; A fifty-fifth step (S155) of generating a response datagram as shown in FIG. 3 if the corresponding leaf node is found in the step (S153); A fourth process comprising a 56th step (S156) of terminating and transmitting the response datagram generated by the above-described step (S155) to the corresponding client 50;

If the leaf node corresponding to the location information of the request datagram received in the 53 th step S153 of the fourth process is not searched, an error datagram as shown in FIG. A fifty-fourth step S154; A fifth step (56) (S156) of transmitting the error datagram generated by the step (S154) to the corresponding client 50 and ending;

An eighteenth step (S280), wherein the corresponding client (50) determines whether a response datagram has been received by the third process; A 20th step (S300) of changing the management data of the corresponding leaf node and feeding back to the fifteenth step (S250) of the third process if the response datagram is received in the step (S280); In step S280, if the response datagram is not received, the status value of the received error datagram is determined and the request datagram is retransmitted. A sixth process comprising a nineteenth step (S290) that feeds back to step S270 and feeds back to the twelfth step (S220) of the third step if the tree structure of the management data is re-requested. It consists of.

Hereinafter, a method of synchronizing management data of a web-based transmission device according to the present invention having the above configuration will be described in detail as an embodiment with reference to the accompanying drawings.

Web server 30 which is a central management device for management data for operating the communication or transmission device 10 is shown in Figure 2 the corresponding management data applied from the transmission device 10 by the MPS (35) A tree structure of a root 60, a parent node 62, and a multi-level leaf node 64 is configured as the management data (first process).

In the leaf node 64 of the multi-stage configured in the above process, the lower leaf node 64 may be reconfigured according to the characteristics of the management data, and the final leaf node 64 contains the corresponding management data.

The MPS 35 of the web server 30 processes the management data of the leaf node 64 to generate a checksum value such as a generation time or a version (S120), and the client 50. The MPC 55 determines whether there is a transmission request of a tree structure (S130), if there is a transmission request, transmits the tree structure (S140), determines whether to process a subroutine (S150), or otherwise, drives a timer. Thus, the predetermined time is counted (S160).

When the timer reaches the set time (S170), the checksum is regenerated (S18) to check whether there is a new update to the management data of the corresponding leaf node (S18), and it is determined whether it is different from the previous checksum (S190). In operation S200, the updated checksum value is transmitted to the corresponding client 50.

Since the client 50 receives the management data only after receiving the tree structure from the web server 30, the client 50 determines whether the tree structure is requested and requests the tree structure if the request is not requested (S210).

Upon receiving the tree structure from the web server 30 (S220), the checksum for management data of the leaf node is generated (S230) and the checksum as shown in FIG. 3 attached to the web server 30 from the web server 30. In operation S240, it is determined whether updated checksums by the checksum datagram 70 have been received. In operation S250, it is determined whether the received checksums are different from the current checksums.

As a result of the determination, if there are other checksums, a request datagram 80 as shown in FIG. 3 is generated (S260) and transmitted to the web server 30 (S270) (third step).

When the web server 30 receives the request datagram from the client 50 by the subroutine S150 (S151), the web server 30 analyzes the position information of the leaf node by analyzing the information (S152). The position of the node is searched (S153).

After retrieving the location of the leaf node, a response datagram 90 as shown in FIG. 3 is generated (S155), the datagram is transmitted to the client 50 (S156), and then terminated. (Step 4).

If the web server 30 fails to search for the location of the node in step 53 (S153), after generating an error datagram 100 as shown in FIG. 3 (S154), The transmission is sent to the corresponding client 50 (S156).

When the client 50 receives the response datagram 90 from the web server 30 (S280), the client 50 extracts the corresponding data from the response datagram 90 as shown in FIG. After updating the management data of the node with the new management data (S300), the process proceeds to the fifteenth step S250, and if the response datagram 90 is not received (S280) from the web server 30. It is determined whether the status value of the received error datagram is a re-request of the tree structure (S290). If it is a re-request, it is fed back to the twelfth step 220, otherwise, the seventeenth step (S270) Feedback to send the request datagram 80 again.

According to the present invention having the above-described configuration, since the traffic is not excessively congested as in the polling or event data synchronization according to the prior art, and the necessary data is not received, the management data is updated at regular intervals. By generating and transmitting a checksum confirming whether or not it has occurred, there is an effect that the update data can be quickly transmitted without causing traffic congestion.

In addition, when an error occurs, by requesting retransmission using an error datagram, accurate data can be transmitted.

In addition, by reducing the traffic of the system and transmitting fast and accurate management data, it is possible to speed up the maintenance of the transmission equipment, and there is an industrial and industrial use effect of improving the reliability of the system.

Claims (1)

In the management data synchronization system of a web-based transmission device comprising a web server and a client, The web server comprises the first step of grouping the transmitted management data in a tree structure of the leaf node to the client, The web server periodically generating a checksum indicative of an update of the corresponding leaf node data, and comparing the previous checksum with another to deliver a checksum of the newly generated leaf node to the client; A third step of, when the client compares the authorized checksum with a previous checksum and requests update of the location information of the leaf management data to the web server by using a request datagram; A fourth step of the web server searching for data corresponding to the location information of the requested request datagram and transmitting the corresponding data to the corresponding client using the response datagram; A fifth step of requesting retransmission of the leaf node location information to the corresponding client by using the error datagram when an error occurs in the location information of the request datagram requested to be updated in the above step; When the client receives the update data in the response datagram, the client updates the data of the leaf node. If the client is requested to retransmit the leaf node location information in the error datagram, the client retransmits the data or retransmits the data tree. Method of synchronizing management data of the web-based transmission device, characterized in that consisting of a sixth process of determining and performing the transmission.