WO2015172512A1 - 数据获取方法、装置及系统 - Google Patents

数据获取方法、装置及系统 Download PDF

Info

Publication number
WO2015172512A1
WO2015172512A1 PCT/CN2014/088777 CN2014088777W WO2015172512A1 WO 2015172512 A1 WO2015172512 A1 WO 2015172512A1 CN 2014088777 W CN2014088777 W CN 2014088777W WO 2015172512 A1 WO2015172512 A1 WO 2015172512A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
management server
network management
data
network element
Prior art date
Application number
PCT/CN2014/088777
Other languages
English (en)
French (fr)
Inventor
郭跃山
丁辉
谢婷婷
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP14892142.2A priority Critical patent/EP3145120B1/en
Publication of WO2015172512A1 publication Critical patent/WO2015172512A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/021—Ensuring consistency of routing table updates, e.g. by using epoch numbers

Definitions

  • the present invention relates to the field of communications, and in particular to a data acquisition method, apparatus, and system.
  • the present invention provides a data acquisition method, apparatus, and system for solving the above problems, in view of the problem that the data transmission in the related art congests the message channel and affects the stability of the system.
  • a data acquisition method including: receiving, by a second network management server corresponding to the second network element, a first message sent by the first network management server corresponding to the first network element, where The first message carries a first event number; the second network management server searches for a pre-configured message distribution, and acquires a first message processing method corresponding to the first event number, where the message is published.
  • the second network management server obtains a data transmission method from another network element; the second network management server executes the first message processing method, and requests and acquires data from the network management server of the other network element.
  • the method further includes: the second network management server processes the requested data, and then performs a warehousing operation on the processed data.
  • the method further includes: determining, by the second network management server, whether there is a next process in the message distribution, if any And the second network management server obtains, by the message distribution, the receiving network element identifier of the second message in the next process and the second event number of the second message processing method to be executed; the second network management server The corresponding network management server that receives the identifier of the network element sends the second message, where the second message carries the second event number.
  • the method further includes: the second network management server receives a third message carrying a third event number; the second network management server searches for the message, and obtains a third event number.
  • the third message processing method wherein the third message processing method includes a method of synchronizing data requested by the second network management server to the second network element; and the second network management server executes the third The message processing method synchronizes the requested data to the second network element.
  • the method includes: the second network management server querying a correspondence between the pre-configured exception code and the event number And acquiring a fourth event number corresponding to the exception code of the abnormality; the second network management server sends a message carrying the fourth event number.
  • the method further includes: receiving an operation instruction for configuring the message sub-publishing; configuring the message sub-publishing according to each parameter input, wherein the message processing method in the message sub-publishing conforms to a preset The message processing specification; the message that the loading configuration is completed is published.
  • the method further includes: receiving an operation instruction for modifying the message sub-publishing; modifying, according to the input parameter, a corresponding entry in the message sub-publishing, wherein the modified message is in a sub-publishing
  • the message processing method conforms to a preset message processing specification; the message after the modification is loaded is published.
  • a data acquisition apparatus which is located in a second network management server corresponding to a second network element, and the apparatus includes: a first receiving module, configured to receive a corresponding to the first network element a first message sent by the first network management server, where the first message carries a first event number; the first acquiring module is configured to search for a pre-configured message sub-publishing, and obtain a corresponding to the first event number.
  • a first message processing method wherein each step of the message for recording data transmission in the message sub-publishing, a message processing method to be executed in each step of the process, a message receiver in the next process, and the message receiver need to be processed
  • the event number, in the first message processing method, the transmission side of the second network management server acquiring data from other network elements is customized.
  • an execution module configured to execute the first message processing method, requesting and acquiring data from a network management server of the other network element.
  • the method further includes: a determining module, configured to determine whether there is a next step in the message sub-publishing, if yes, triggering a second acquiring module; and the second obtaining module is configured to divide from the message The second event number of the receiving network element identifier of the second message in the next process and the second message processing method to be executed is obtained in the publication; the sending module is configured to send the the network management server to the corresponding network management server a second message, wherein the second message carries the second event number.
  • the first receiving module is further configured to receive a third message carrying a third event number, where the first obtaining module is further configured to search for the message sub-publishing, and obtain the third event number corresponding to the message.
  • the third message processing method wherein the third message processing method includes a method of synchronizing data requested by the second network management server to the second network element; the device further includes: a synchronization module, configured to Performing the third message processing method to synchronize the requested data to the second network element.
  • the method further includes: an exception processing module, configured to query a correspondence between the pre-configured exception code and the event number when an abnormality occurs in the process of executing the first message processing method, and acquire the abnormal code of the abnormality Corresponding fourth event number, and then sending a message carrying the fourth event number.
  • an exception processing module configured to query a correspondence between the pre-configured exception code and the event number when an abnormality occurs in the process of executing the first message processing method, and acquire the abnormal code of the abnormality Corresponding fourth event number, and then sending a message carrying the fourth event number.
  • the method further includes: a second receiving module, configured to receive an operation instruction for configuring the message to be published; and a configuration module, configured to configure the message to be published according to each input parameter, where the message is published
  • the message processing method in accordance with the preset message processing specification; loading the module, loading the configuration completed message is published.
  • the second receiving module is further configured to receive an operation instruction for modifying the message sub-publishing;
  • the configuration module is further configured to modify a corresponding entry in the message sub-publishing according to the input parameter, where The message processing method in the modified message sub-publishing conforms to a preset message processing specification;
  • the loading module is further configured to load the modified message sub-publishing.
  • a data acquisition system including: a network element and a network management server corresponding to the network element, wherein the network management server includes the foregoing apparatus, and is configured to request from other network elements.
  • the obtained data is synchronized to the network element; the network element is configured to receive data transmitted by the network management server.
  • a message is transmitted between network management servers, and a method for transmitting data is indicated by an event number.
  • the receiver obtains data by executing a message processing method indicated by an event number, and separates the message channel from the data channel, and the user can customize the specific processing of the message.
  • Method data transmission between the network management server (that is, the background communication driver network). Therefore, the data transmission does not cause the message channel to be congested, which improves the stability of the system, and
  • the pipe server transmits data, thereby avoiding the problem that the data is not complete when the data is not completely transmitted and the network is faulty.
  • FIG. 1 is a flowchart of a data acquisition method according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a data acquisition apparatus according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a data acquisition apparatus according to an alternative embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a data acquisition system according to an embodiment of the present invention.
  • Figure 5 is a schematic structural diagram of a system according to an alternative embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a data transmission module according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of an abnormality distribution in an alternative embodiment of the present invention.
  • FIG. 9 is a flow diagram of the internal system of data backup in an alternative embodiment of the present invention.
  • the embodiment of the present invention provides a communication scheme between multiple network elements.
  • a dual channel transmission mode in which messages and data are separated is used, and a message is used.
  • the user can customize the data transmission mode, and the technical solution provided by the embodiment of the present invention supports dynamic loading, and supports different network element types and large data volume information transmission.
  • FIG. 1 is a flowchart of a data acquisition method according to an embodiment of the present invention. As shown in FIG. 1 , the method mainly includes the following steps:
  • Step S102 the second network management server corresponding to the second network element receives the first message sent by the first network management server corresponding to the first network element, where the first message carries the first event number;
  • a communication process may be initiated by the network management client, or a scheduled task may be set by the user, and the network management server periodically initiates the process.
  • the processing method corresponding to the event number of the initiator for example, the first network management server corresponding to the first network element in step S102
  • the message is sent according to the sequence configured in the message distribution.
  • the network management server for example, the second network server in step S102
  • sent to the network element corresponding to the next event number continues processing.
  • Step S104 the second network management server searches for a pre-configured message sub-publishing, and acquires a first message processing method corresponding to the first event number, where the second network management is customized in the first message processing method.
  • the message distribution may be a two-dimensional mapping table, and includes four key information: an event number, a message processing method, a receiving network element number, and a sending event number.
  • Table 1 is an example of a message distribution.
  • Event number Message processing method Receiving network element Send event number 1 Begin 13 2 2 2 Event 1 11 100 100 Event 2 13 101 101 End 11 200 200 End 0 0
  • the message distribution can be stored in the network management server in the form of a file or a database.
  • Step S106 The second network management server executes the first message processing method, and requests and acquires data from the other network element.
  • the second network management server may process the requested data, and then perform the storage operation on the processed data.
  • the second network management server may set a process in the message distribution to instruct the second network management server to synchronize the requested data to the first
  • the method may further include: the second network management server receives the third message carrying the third event number; the second network management server searches for the message, and obtains the third event.
  • the second network management server may determine whether there is a next step in the message distribution. a flow, if yes, the second network management server obtains, by the message distribution, the receiving network element identifier of the second message in the next process and the second event number of the second message processing method to be executed; The second network management server sends the second message to the corresponding network management server that is configured to receive the network element, where the second message carries the second event number.
  • exceptions can also be handled. If the second network management server is abnormal in the process of executing the first message processing method, the second network management server queries the corresponding relationship between the pre-configured exception code and the event number (ie, the abnormality is published), and acquires The fourth event number corresponding to the abnormal exception code is sent, and then the message carrying the fourth event number is sent to perform an exception processing flow.
  • the exception processing method may be configured in the network management server, that is, the correspondence between the exception code and the event number of the message processing method corresponding to the exception code is configured. When an exception occurs, the corresponding error code is obtained. The event number, and then the message is sent, and the network management server that receives the message obtains the entry corresponding to the event number from the message sub-publishing, and performs the entry corresponding to the fourth event number according to the message sub-publishing. deal with.
  • the user may configure the message distribution, and the network management server receives the operation instruction for configuring the message distribution, and then configures the message distribution according to the input parameters, wherein
  • the message processing method in the message sub-publishing conforms to a preset message processing specification (which may be defined by a dedicated interface (for example, a message processing interface)), and then the message-completed publication of the loading configuration is completed.
  • the user may also modify the configured message sub-publishing.
  • the network server receives an operation instruction for modifying the message sub-publishing, and then modifies the corresponding entry in the message sub-publishing according to the input parameter, where the modified message is published.
  • the message processing method conforms to a preset message processing specification, and finally the modified message is published.
  • the message distribution can be dynamically configured, that is, the dynamic configuration data transmission process.
  • a data acquisition apparatus is further provided, where the apparatus is located in a second network management server corresponding to the second network element, and is configured to implement the foregoing data method.
  • the apparatus mainly includes: a first receiving module 210, configured to receive a first network management server corresponding to the first network element. a message, wherein the first message carries a first event number; the first obtaining module 220 is configured to search for a pre-configured message sub-publishing, and acquire a first message processing method corresponding to the first event number, The method for transmitting data from the other network element by the second network management server is customized in the first message processing method; the executing module 230 is configured to execute the first message processing method, from the other network element The network management server requests and obtains data.
  • the apparatus may further include: a determining module 240, configured to determine whether there is a next step in the message distribution, and if so, triggering the second obtaining module 250;
  • the second obtaining module 250 is configured to obtain, from the message sub-publishing, a receiving network element identifier of the second message in the next process and a second event number of the second message processing method to be executed;
  • the sending module 260 is configured to The corresponding network management server that receives the identifier of the network element sends the second message, where the second message carries the second event number.
  • the first receiving module 210 is further configured to receive a third message that carries a third event number.
  • the first obtaining module 220 is further configured to: search for the message, publish, and obtain the third event.
  • the third message processing method corresponding to the number, wherein the third message processing method includes a method of synchronizing data requested by the second network management server to the second network element.
  • the apparatus may further include: a synchronization module 270 configured to execute the third message processing method to synchronize the requested data to the second network element.
  • the apparatus may further include: an exception processing module 280 configured to query a correspondence between the pre-configured exception code and the event number when an abnormality occurs in the process of executing the first message processing method The relationship acquires a fourth event number corresponding to the abnormal code of the abnormality, and then sends a message carrying the fourth event number to enter an exception processing flow.
  • an exception processing module 280 configured to query a correspondence between the pre-configured exception code and the event number when an abnormality occurs in the process of executing the first message processing method The relationship acquires a fourth event number corresponding to the abnormal code of the abnormality, and then sends a message carrying the fourth event number to enter an exception processing flow.
  • the device may further include: a second receiving module, configured to receive an operation instruction for configuring the message to be published; and a configuration module, configured to configure the message distribution according to each input parameter, where the The message processing method in the message distribution conforms to a preset message processing specification; the loading module loads the configuration completion message and publishes the message.
  • a second receiving module configured to receive an operation instruction for configuring the message to be published
  • a configuration module configured to configure the message distribution according to each input parameter, where the The message processing method in the message distribution conforms to a preset message processing specification
  • the loading module loads the configuration completion message and publishes the message.
  • the second receiving module is further configured to receive an operation instruction for modifying the message sub-publishing;
  • the configuration module is further configured to modify a corresponding entry in the message sub-publishing according to the input parameter, where The message processing method in the modified message sub-publishing conforms to a preset message processing specification;
  • the loading module is further configured to load the modified message sub-publishing.
  • a data acquisition system is also provided.
  • FIG. 4 is a schematic structural diagram of a data acquisition system according to an embodiment of the present invention.
  • the system mainly includes: a network element 40 and a network management server 42 corresponding to the network element.
  • the network management server 42 can include The data acquisition device is configured to synchronize the requested data to the network element 40, and the network element 40 is configured to receive the data transmitted by the network management server 42.
  • a new module (ie, the foregoing device) may be added to the network management server.
  • the module is referred to as a data transmission module, and the data transmission module may be In addition to the above-mentioned functional structure, other functional structure implementations can also be employed.
  • a data transmission module 105 is added to the network management server.
  • the network management server includes: a message communication module 103, a transmission module 102 between the network management server and the network element, and a data transmission service (such as sftp, http, etc.) module 104 at the bottom of the system.
  • a data transmission service such as sftp, http, etc.
  • the foreground network element 101 (ie, the above-mentioned network element) is a network element unit that bears a certain service function and is the core of the communication system.
  • the transmitting module 102 is responsible for transmitting the data of the network management server to the foreground network element 102, which is the only channel in the front and back.
  • the message communication module 103 is a module provided for the existing network management system and configured to be a message communication. In the embodiment of the present invention, the message is sent by the module.
  • the data transmission service module 104 is a file-based transmission channel that is provided by the network management server and is further encapsulated by the network management server. In this embodiment of the present invention, data is transmitted through the module.
  • the data transmission module 105 is a core module added in the embodiment of the present invention, and its structure is as shown in FIG. 6.
  • FIG. 6 is a schematic structural diagram of a data transmission module according to an embodiment of the present invention.
  • the data transmission module mainly includes: a message distribution 201, a message processing interface 301, a message monitoring device 401, and a dynamic loading device 501.
  • the message sub-publish 201 can be a two-dimensional mapping table.
  • the event sub-components 202, the message processing method 203, the receiving network element 204, and the transmission event number 205 are four sub-components, that is, the event number 202, the message processing method 203, the receiving network element 204, and the transmission event number 205 are recorded. relationship.
  • the event number is the primary key of the message distribution, and the requirement is unique, and there is no order requirement;
  • the message processing method is a method for processing the received message by the user-defined local network element, and the method must meet the specification requirements of the message processing interface;
  • the receiving network element is the target network element number to be sent after the message is processed. According to the actual situation, the value is a positive integer.
  • the sending event number is the event number to be processed by the target network element. If the field is configured as the ending flag ( Generally indicated by 0, other agreed values can also be used to indicate the end of the message flow.
  • the message sub-publish 201 can be stored in the form of a file, a database, or the like.
  • the message processing interface 301 is arranged to define a generic message processing specification.
  • the interface is generally implemented by the recipient network element of the message to customize its own message processing method.
  • the interface only defines specifications so that the message listening device 401 can correctly monitor that each message processing method configured in the message distribution 201 is a specific implementation of the interface.
  • the message monitoring device 401 is responsible for receiving, processing, and transmitting the local network element message.
  • the message monitoring device 401 may include: a message receiver 402 configured to listen to and receive a message sent to the local network element (ie, the network management server corresponding to the network element); the message processor 403 is configured to be configured according to the message distribution 201
  • the message processing method is used to process the message, and the exception processing is performed according to the abnormality distribution;
  • the message sender 404 is configured to send the message to the next network element according to the configuration of the message distribution after the message processing is completed; In the processing mode when the configuration encounters a specific exception, the exception sub-publishes two key fields including the exception code and the transmission event number.
  • the message monitoring module 401 is responsible for monitoring messages sent by the network management server corresponding to other network elements to the network management server corresponding to the network element.
  • the message receiver in the device is responsible for receiving the message. And find the message processing method corresponding to the event number in the message sub-publishing, and then the method is executed by the message processor and the exception processing is performed. After the execution is completed, the message sender sends the message to the next network element according to the data configured in the message distribution.
  • the role of the abnormality sub-publishing 405 is to determine the sending direction of the message if some abnormality occurs during the processing of the message processor. That is to say, in the event of an abnormality, the transmission event number configured by the message distribution 201 does not function, and is replaced by the event number configured in the exception distribution 405.
  • Table 2 is an example of an anomaly publication.
  • the specific meaning corresponding to the exception code is defined internally by the system.
  • the abnormality distribution presentation shown in Table 2 indicates that if an exception condition with the code number 120001 is sent during the processing, the event number 4001 is processed. If 120006 is encountered, go to 4002 for processing, where 4001 and 4002 must also be configured and implemented in the message distribution.
  • the dynamic loading device 501 is configured to load the message sub-published after the user configuration or modification message sub-publishing, and execute the dynamic loading device 501, so that the message sub-publishing can take effect immediately.
  • the dynamic loading device 501 is configured to perform parsing and loading of message sub-publishing. After the user implements or modifies the content of the message distribution list, the dynamic loading device 501 is executed first, so that the content of the message distribution list is valid, and the normal operation of the server and the normal operation of the network element are not affected.
  • the dynamic loading device the flexibility and application range of the data transmission are improved, for example, the monitoring of a specific network element, the collection of specific information, and the like can be realized without the user's knowledge.
  • the one-time communication process may be initiated by the network management client, or the timed task may be set by the user, and the network management server periodically initiates.
  • the message monitoring device 401 first executes the initiator. After the processing is completed, the message is sent to the network element corresponding to the next event number to continue processing according to the order configured in the message distribution.
  • a network element needs to request data of other network elements, it can be implemented in the message processing method.
  • the customized method is used to download data prepared by other network elements.
  • the network management server processes the requested data, it can perform operations such as warehousing.
  • the message is sent to the next network element to continue processing. If there is no next process, the communication ends, and the transmitting module 102 synchronizes the data changed after the communication to the corresponding Network element.
  • the network management server corresponding to the network element No. 11 first initiates a session (which network element side first initiates and is not reflected in the message distribution, which is triggered by the client or the timing task, etc.) Execute the [Begin] method, and then send the event number 2 to the network management server corresponding to the network element 13 through the message; after receiving the message, the network management server corresponding to the network element 13 executes the method corresponding to the event number 2 [Event 1], and executes After the event number 100 is sent back to the network management server corresponding to the network element No.
  • the network management server corresponding to the network element 11 after receiving the message, the network management server corresponding to the network element 11 executes [Event 2], and sends 101 to the network management server corresponding to the 13th network element.
  • the network management server corresponding to the network element 13 receives the message, executes the [End] method, and then sends a message to the network management server corresponding to the network element No. 11, the event number is 200, wherein the event number 200 corresponds to the [End] method;
  • the network management server corresponding to the network element No. 11 executes the [End] method, and the execution is here.
  • the receiving network element and the sending event number are both 0, indicating that the process is finished.
  • each message contains only two integer values of the receiving network element number and the sending event number, and the message body is very small, thus ensuring the reliability and security of the transmission.
  • the data transmission is implemented in the message processing method, such as [Event 1] or [Event 2]. Users can customize any transmission mode, relying on the mature solution of the underlying system. For example, the encrypted sftp service can be used, and the format of the data itself can be compressed or encrypted by a user.
  • the application is very flexible.
  • all the intermediate processes of data transmission are performed on the background network management server, and the network element is unaware of the data of the network management only when the data is changed after the data transmission ends.
  • the transfer function ie, the above transfer module
  • the message channel and the data channel are separated, and the user can customize the specific method of message processing according to the specification of the message processing interface, and drive the data transmission between the networks by the background communication. Therefore, it has the beneficial effects of being safe, concealed, flexible in use, and supporting large data volume transmission.
  • 51, 52 are the primary network elements
  • 61 is the standby network element
  • 51 network elements are the initiators of the message
  • the data of the 51 and 52 network elements needs to be backed up to 61 network elements.
  • message sub-publishing and abnormal sub-publishing are configured in the corresponding network management servers of the respective network elements according to FIG. 7 and FIG. 8, and the message processing method configured in the message sub-publishing is implemented, and then dynamic loading is performed.
  • FIG. 9 is a flowchart of the internal system for performing data backup in the embodiment.
  • the left dotted line box indicates the normal flow, the right side indicates the abnormal flow, and only the abnormal code 14001 processing flow is shown, and other abnormal processing processes are similar. Multiple steps in the normal process may be abnormal and go to the abnormal process, which is marked with a dotted line.
  • the backup of the data of the 51 and 52 network elements to the 61 network element mainly includes the following steps:
  • Step 901 The network management server corresponding to the network element 51 initiates a dual-homing request, and the specified event number is 1001.
  • Step 902 The message monitoring device of the network management server corresponding to the network element 51 receives the message with the event number 1001, and executes the message processing method (Begin) corresponding to the event number. After the execution is complete, the message is sent to the 51 and 52 network elements.
  • the corresponding network management server, the event number is 1002.
  • sending a message in the network management server is also supported.
  • Step 903 The network management server corresponding to the network elements 51 and 52 receives the message at the same time, and executes the event 1002 (the data verification of the active end is performed. If the verification fails, the automatic process is automatically transferred to the abnormal process, the same below), and then the message is sent.
  • Step 904 The network management server corresponding to the network element 61 executes the event 2001 (executing the backup data check), and sends a message to the network management server corresponding to the network elements 51 and 52.
  • Step 905 The network management server corresponding to the network elements 51 and 52 simultaneously executes the event 1003 (the data is used by the primary end to perform data export), and then sends a message to the network management server corresponding to the network element 61.
  • Step 906 The network management server corresponding to the network element 61 executes the event 2002 (data is obtained from the primary network elements 51 and 52, and is processed and imported). After the completion, the message is sent to the network management server corresponding to the network element 51.
  • the network management server corresponding to the network element 51 is the initiator, the implementation is notified to the initiator, and the network management server corresponding to the network element 52 is not required to be notified.
  • Step 907 The network management server corresponding to the network element 51 executes the event 1004 (the progress of the report is reported to the user that the network element has successfully obtained the data), and the message is sent to the network management server corresponding to the network element 61.
  • Step 908 The network management server corresponding to the network element 61 receives the message, and executes the event 2003 (transmitting the data, that is, notifying the changed network data to the foreground network element. Because only the data of the 61th network element changes in the process, only the number 61 is changed. The network management server corresponding to the NE needs to transmit data. The event number sent in the message distribution is 0, indicating the end of the process.
  • Step 909 Determine whether the abnormal code is 14001. If yes, go to the abnormal processing flow 910, otherwise, go to the processing flow of other abnormalities (omitted). In the above steps, if an abnormality occurs in any step, go to this step.
  • Step 910 According to the abnormality distribution, find the event number 4000 corresponding to 14001, change the sending event number of the message to 4000, and the transmitted network element does not change, and send the message.
  • Step 911 The receiving network element receives the 4000 message and performs exception processing (that is, the message processing method Error handler1 corresponding to the event number 4000 in the message sub-publishing).
  • exception processing that is, the message processing method Error handler1 corresponding to the event number 4000 in the message sub-publishing.
  • Step 912 The abnormally processed network element sends a message to all network elements (51, 52, 61) carrying the event number 5000.
  • Step 913 All network elements receive the message of event number 5000, perform after-care processing, and terminate the process.
  • Step 914 The process ends.
  • the message channel and the data channel are separated.
  • Each message contains only two integer values of the receiving network element number and the sending event number, and the message body is very small, thus ensuring the reliability and security of the transmission.
  • the user can customize any transmission mode, relying on the mature scheme of the underlying system, for example, the encrypted sftp service can be utilized, and the data format itself can be compressed or encrypted by the user in a customized manner.
  • the application is very flexible.
  • all the intermediate processes of data transmission are performed on the background network management server, and the network element is unaware of the data of the network management only when the data is changed after the data transmission ends.
  • the transfer function ie, the above transfer module
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or separate them into individual integrated circuit modules, or Multiple of these modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • a message is transmitted between network management servers, and a method for transmitting data is indicated by an event number, and the receiver obtains data by executing a message processing method indicated by an event number, and separates the message channel from the data channel.
  • Users can customize the specific method of message processing and data transmission between the network management server (that is, the background communication driver network). Therefore, the data transmission does not cause the message channel to be congested, which improves the stability of the system, and because the data is transmitted through the network management server, the problem that the data is incomplete when the network failure occurs without the complete transmission of the data is avoided.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明公开了一种数据获取方法、装置及系统。其中，该数据获取方法包括：与第二网元对应的第二网管服务器接收与第一网元对应的第一网管服务器发送的第一消息，其中，第一消息中携带有第一事件号；第二网管服务器查找预先配置的消息分发表，获取与第一事件号对应的第一消息处理方法，其中，消息分发表中用于记录数据传输的各步流程以及各步流程中需要执行的消息处理方法、下一步流程中的消息接收方和该消息接收方需要处理的事件号，第一消息处理方法中定制了第二网管服务器从其他网元获取数据的传输方法；第二网管服务器执行第一消息处理方法，从其它网元的网管服务器请求并获取数据。

Description

数据获取方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种数据获取方法、装置及系统。
背景技术
在通讯网络中，为了实现特定的功能，经常需要在多个网元之间进行数据传输，在需要传输的数据量较大时，现有的传输方式容易造成通讯信道拥塞、系统不稳定、及数据丢包等问题。
例如，为了提高系统的容灾能力，需要在多个网元之间进行数据互备，当其中一个网元发生故障时，其他网元的备用数据可以立即启用。采用这种数据备份方案，需要在多个网元之间进行频繁的数据交互，数据量可达数百兆，其中还要进行复杂的数据校验和转换。采用现有的数据传输方式不仅容易使消息通道拥塞，影响系统稳定性，而且对数据的纠错能力也达不到要求，如果数据传输了一半而出现网络故障导致数据不完整可能会出现灾难性后果。
因此需要一种可靠的数据获取方案，在确保系统稳定和数据安全的前提下，实现高性能的数据传输。
发明内容
针对相关技术中数据传输使消息通道拥塞，影响系统稳定性的问题，本发明提供了一种数据获取方法、装置及系统，以至少解决上述问题。
根据本发明的一个实施例，提供了一种数据获取方法，包括：与第二网元对应的第二网管服务器接收与第一网元对应的第一网管服务器发送的第一消息，其中，所述第一消息中携带有第一事件号；所述第二网管服务器查找预先配置的消息分发表，获取与所述第一事件号对应的第一消息处理方法，其中，所述消息分发表中用于记录数据传输的各步流程以及各步流程中需要执行的消息处理方法、下一步流程中的消息接收方和该消息接收方需要处理的事件号，所述第一消息处理方法中定制了所述第二网管服务器从其他网元获取数据的传输方法；所述第二网管服务器执行所述第一消息处理方法，从所述其它网元的网管服务器请求并获取数据。
可选地，在从所述其它网元请求并获取数据之后，所述方法还包括：所述第二网管服务器对请求到的数据进行处理，然后对处理后的数据进行入库操作。
可选地，在所述第二网管服务器从所述其它网元获取到数据之后，所述方法还包括：所述第二网管服务器判断所述消息分发表中是否还有下一步流程，如果有，则所述第二网管服务器从所述消息分发表中获取下一步流程中第二消息的接收网元标识及需要执行的第二消息处理方法的第二事件号；所述第二网管服务器向所述接收网元标识的对应的网管服务器发送所述第二消息，其中，所述第二消息中携带有所述第二事件号。
可选地，所述方法还包括：所述第二网管服务器接收携带有第三事件号的第三消息；所述第二网管服务器查找所述消息分发表，获取与所述第三事件号对应的第三消息处理方法，其中，所述第三消息处理方法包括将所述第二网管服务器请求到的数据同步到所述第二网元的方法；所述第二网管服务器执行所述第三消息处理方法，将请求到的数据同步到所述第二网元。
可选地，如果所述第二网管服务器在执行所述第一消息处理方法的过程中出现异常，则所述方法包括：所述第二网管服务器查询预先配置的异常码与事件号的对应关系，获取与本次异常的异常码对应的第四事件号；所述第二网管服务器发送携带第四事件号的消息。
可选地，所述方法还包括：接收配置所述消息分发表的操作指令；根据输入的各个参数，配置所述消息分发表，其中，所述消息分发表中的消息处理方法符合预先设定的消息处理规范；加载配置完成的所述消息分发表。
可选地，所述方法还包括：接收修改所述消息分发表的操作指令；根据输入的参数，修改所述消息分发表中对应的表项，其中，修改后的所述消息分发表中的消息处理方法符合预先设定的消息处理规范；加载修改后的所述消息分发表。
根据本发明的另一个实施例，提供了一种数据获取装置，位于与第二网元对应的第二网管服务器，所述装置包括：第一接收模块，设置为接收与第一网元对应的第一网管服务器发送的第一消息，其中，所述第一消息中携带有第一事件号；第一获取模块，设置为查找预先配置的消息分发表，获取与所述第一事件号对应的第一消息处理方法，其中，所述消息分发表中用于记录数据传输的各步流程以及各步流程中需要执行的消息处理方法、下一步流程中的消息接收方和该消息接收方需要处理的事件号，所述第一消息处理方法中定制了所述第二网管服务器从其他网元获取数据的传输方 法；执行模块，设置为执行所述第一消息处理方法，从所述其它网元的网管服务器请求并获取数据。
可选地，还包括：判断模块，设置为判断所述消息分发表中是否还有下一步流程，如果有，则触发第二获取模块；所述第二获取模块，设置为从所述消息分发表中获取下一步流程中第二消息的接收网元标识及需要执行的第二消息处理方法的第二事件号；发送模块，设置为向所述接收网元标识的对应的网管服务器发送所述第二消息，其中，所述第二消息中携带有所述第二事件号。
可选地，所述第一接收模块还设置为接收携带有第三事件号的第三消息；所述第一获取模块还设置为查找所述消息分发表，获取与所述第三事件号对应的第三消息处理方法，其中，所述第三消息处理方法包括将所述第二网管服务器请求到的数据同步到所述第二网元的方法；所述装置还包括：同步模块，设置为执行所述第三消息处理方法，将请求到的数据同步到所述第二网元。
可选地，还包括：异常处理模块，设置为在执行所述第一消息处理方法的过程中出现异常时，查询预先配置的异常码与事件号的对应关系，获取与本次异常的异常码对应的第四事件号，然后发送携带所述第四事件号的消息。
可选地，还包括：第二接收模块，设置为接收配置所述消息分发表的操作指令；配置模块，设置为根据输入的各个参数，配置所述消息分发表，其中，所述消息分发表中的消息处理方法符合预先设定的消息处理规范；加载模块，加载配置完成的所述消息分发表。
可选地，所述第二接收模块还设置为接收修改所述消息分发表的操作指令；所述配置模块还设置为根据输入的参数，修改所述消息分发表中对应的表项，其中，修改后的所述消息分发表中的消息处理方法符合预先设定的消息处理规范；所述加载模块还设置为加载修改后的所述消息分发表。
根据本发明的又一个实施例，提供了一种数据获取系统，包括：网元和与所述网元对应的网管服务器，其中，所述网管服务器包括上述装置，设置为将从其他网元请求到的数据同步到所述网元；所述网元，设置为接收所述网管服务器传输的数据。
通过本发明，在网管服务器之间传输消息，通过事件号指示传输数据的方法，接收方通过执行事件号指示的消息处理方法获取数据，将消息通道和数据通道分离，用户可以定制消息处理的具体方法，在网管服务器(即后台通讯驱动网)间的数据传输。从而使得数据传输不会使消息通道拥塞，提高了影响系统稳定性，并且，由于通过网 管服务器传输数据，从而也避免了数据没有传输完全而出现网络故障时导致数据不完整的问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的数据获取方法的流程图；
图2是根据本发明实施例的数据获取装置的结构示意图；
图3是根据本发明可选实施例的数据获取装置的结构示意图；
图4是根据本发明实施例的数据获取系统的结构示意图；
图5是本发明可选实施例的系统结构示意图；
图6是本发明实施例的数据传输模块的结构示意图；
图7是本发明可选实施例中的消息分发表的示意图；
图8是本发明可选实施例中的异常分发表的示意图；
图9是本发明可选实施例中的数据备份的系统内部流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
针对相关技术中数据传输存在的上述问题，本发明实施例提供了一种多个网元之间的通讯方案，在本发明实施例中，采用消息和数据分离的双通道传输方式，以消息来驱动数据传输，用户可以定制数据传输方式，并且，本发明实施例提供的技术方案支持动态加载，支持不同网元类型和大数据量信息传输。
图1为根据本发明实施例的数据获取方法的流程图，如图1所示，该方法主要包括以下步骤：
步骤S102，与第二网元对应的第二网管服务器接收与第一网元对应的第一网管服务器发送的第一消息，其中，所述第一消息中携带有第一事件号；
在本发明实施例的具体实施过程中，一次通讯过程可以由网管客户端发起，也可以由用户设定好定时任务，由网管服务器定时发起。在通讯发起后，首先执行发起方(例如，步骤S102中的第一网元对应的第一网管服务器)的事件号对应的处理方法，处理完成后，根据消息分发表中配置的顺序，将消息发送到下一个事件号对应的网元的网管服务器(例如，步骤S102中的第二网络服务器)继续处理。
步骤S104，所述第二网管服务器查找预先配置的消息分发表，获取与所述第一事件号对应的第一消息处理方法，其中，所述第一消息处理方法中定制了所述第二网管服务器从其他网元获取数据的传输方法；
在本发明实施例的一个可选实施方式中，消息分发表可以为一个二维映射表，包含：事件号、消息处理方法、接收网元号以及发送事件号四个关键信息。表1为消息分发表的一个示例。
表1.
事件号 消息处理方法 接收网元 发送事件号
1 Begin 13 2
2 Event 1 11 100
100 Event 2 13 101
101 End 11 200
200 End 0 0
其中，消息分发表可以以文件、数据库等方式存储在网管服务器中。
步骤S106，所述第二网管服务器执行所述第一消息处理方法，从所述其它网元请求并获取数据。
在本发明实施例的可选实施方案中，第二网管服务器在从其它网元请求并获取到数据后，可以对请求到的数据进行处理，然后对处理后的数据进行入库操作。
在一个可选的实施方案中，第二网管服务器在从其它网元请求并获取数据后，可以在消息分发表中设置一个流程，指示第二网管服务器将将请求到的数据同步到所述第二网元，因此，该方法还可以包括：所述第二网管服务器接收携带有第三事件号的第三消息；所述第二网管服务器查找所述消息分发表，获取与所述第三事件号对应的第三消息处理方法，其中，所述第三消息处理方法包括将所述第二网管服务器请求到的数据同步到所述第二网元的方法；所述第二网管服务器执行所述第三消息处理方法， 将请求到的数据同步到所述第二网元。通过该可选实施方式，避免了数据直接传输到网元，在数据没有传输完全时，传输中断而导致第二网元中的数据不可用的问题。
在本发明实施例的一个可选实施方式中，在所述第二网管服务器从所述其它网元获取到数据之后，所述第二网管服务器可以判断所述消息分发表中是否还有下一步流程，如果有，则所述第二网管服务器从所述消息分发表中获取下一步流程中第二消息的接收网元标识及需要执行的第二消息处理方法的第二事件号；所述第二网管服务器向所述接收网元标识的对应的网管服务器发送所述第二消息，其中，所述第二消息中携带有所述第二事件号。
在一个可选实施方式中，还可以对异常情况进行处理。如果所述第二网管服务器在执行所述第一消息处理方法的过程中出现异常，则所述第二网管服务器查询预先配置的异常码与事件号的对应关系(即异常分发表)，获取与本次异常的异常码对应的第四事件号，然后发送携带第四事件号的消息，进行异常处理流程。在该可选实施方式中，可以在网管服务器中配置异常处理方法，即配置异常码与处理该异常码对应的消息处理方法的事件号的对应关系，发生异常时，获取与该异常码对应的事件号，然后发送消息，接收到该消息的网管服务器，从消息分发表中获取与该事件号对应的表项，并按照所述消息分发表中与所述第四事件号对应的表项进行处理。
在本发明实施例的一个可选实施方式中，用户可以对消息分发表进行配置，网管服务器接收配置所述消息分发表的操作指令，然后根据输入的各个参数，配置所述消息分发表，其中，所述消息分发表中的消息处理方法符合预先设定的消息处理规范(可以通过一个专用接口(例如，消息处理接口)来定义)，然后，加载配置完成的所述消息分发表。
另外，在本发明实施例的另一个可选实施方式中，用户还可以修改配置好的消息分发表。在该可选实施方式中，网络服务器接收修改所述消息分发表的操作指令，然后根据输入的参数，修改所述消息分发表中对应的表项，其中，修改后的所述消息分发表中的消息处理方法符合预先设定的消息处理规范，最后加载修改后的所述消息分发表。通过该可选实施方式，可以动态的配置消息分发表，即动态的配置数据传输过程。
根据本发明实施例，还提供了一种数据获取装置，该装置位于与第二网元对应的第二网管服务器，设置为实现上述的数据方法。
图2为根据本发明实施例的数据获取装置的结构示意图，如图2所示，该装置主要包括：第一接收模块210，设置为接收与第一网元对应的第一网管服务器发送的第 一消息，其中，所述第一消息中携带有第一事件号；第一获取模块220，设置为查找预先配置的消息分发表，获取与所述第一事件号对应的第一消息处理方法，其中，所述第一消息处理方法中定制了所述第二网管服务器从其他网元获取数据的传输方法；执行模块230，设置为执行所述第一消息处理方法，从所述其它网元的网管服务器请求并获取数据。
可选地，如图3所示，该装置还可以包括：判断模块240，设置为判断所述消息分发表中是否还有下一步流程，如果有，则触发第二获取模块250；所述第二获取模块250，设置为从所述消息分发表中获取下一步流程中第二消息的接收网元标识及需要执行的第二消息处理方法的第二事件号；发送模块260，设置为向所述接收网元标识的对应的网管服务器发送所述第二消息，其中，所述第二消息中携带有所述第二事件号。可选地，所述第一接收模块210还设置为接收携带有第三事件号的第三消息；所述第一获取模块220还设置为查找所述消息分发表，获取与所述第三事件号对应的第三消息处理方法，其中，所述第三消息处理方法包括将所述第二网管服务器请求到的数据同步到所述第二网元的方法。则，如图3所示，该装置还可以包括：同步模块270，设置为执行所述第三消息处理方法，将请求到的数据同步到所述第二网元。
可选地，如图3所示，该装置还可以包括：异常处理模块280，设置为在执行所述第一消息处理方法的过程中出现异常时，查询预先配置的异常码与事件号的对应关系，获取与本次异常的异常码对应的第四事件号，然后发送携带第四事件号的消息，进入异常处理流程。
可选地，该装置还可以包括：第二接收模块，设置为接收配置所述消息分发表的操作指令；配置模块，设置为根据输入的各个参数，配置所述消息分发表，其中，所述消息分发表中的消息处理方法符合预先设定的消息处理规范；加载模块，加载配置完成的所述消息分发表。
可选地，所述第二接收模块还设置为接收修改所述消息分发表的操作指令；所述配置模块还设置为根据输入的参数，修改所述消息分发表中对应的表项，其中，修改后的所述消息分发表中的消息处理方法符合预先设定的消息处理规范；所述加载模块还设置为加载修改后的所述消息分发表。
根据本发明实施例，还提供了一种数据获取系统。
图4为根据本发明实施例的数据获取系统的结构示意图，如图4所示，该系统主要包括：网元40及与该网元对应的网管服务器42。其中，网管服务器42可以包括上 述的数据获取装置，设置为将请求到的数据同步到网元40，网元40设置为接收网管服务器42传输的数据。
在具体实施过程中，可以通过在网管服务器中加入一个新的模块(即上述装置)，在本发明实施例的一个可选实施方案中，将该模块称为数据传输模块，数据传输模块除了可以采取上述的功能结构形式之外，还可以采用其它的功能结构实现方式。
例如，在图5所示的系统中，网管服务器中增加了一个数据传输模块105。其中，在图5所示的系统中，网管服务器包括：消息通讯模块103、网管服务器和网元间的传送模块102以及系统底层的数据传输服务(如sftp,http等)模块104。
在图5中，前台网元101(即上述的网元)为承担一定业务功能的网元单元，为通讯系统的核心。传送模块102负责将网管服务器的数据传送到前台网元102，是前后台的唯一通道。消息通讯模块103，为现有网管系统提供的设置为消息通讯的模块，在本发明实施例中通过该模块发送消息。数据传输服务模块104，为底层系统提供的，网管服务器进一步封装的基于文件的传输通道，本发明实施例中通过该模块进行数据传输。数据传输模块105为本发明实施例增加的核心模块，其结构如图6所示。
图6为本发明实施例的数据传输模块的结构示意图，如图6所示，该数据传输模块主要包括：消息分发表201、消息处理接口301、消息监听装置401和动态加载装置501。
消息分发表201可以为一个二维映射表。其中包括事件号202、消息处理方法203、接收网元204、及发送事件号205四个子组件，即其记载了事件号202、消息处理方法203、接收网元204、及发送事件号205的对应关系。其中，事件号是消息分发的主键，要求是唯一的，没有顺序要求；消息处理方法是用户自定义的本网元对接收到的消息的处理方法，该方法必须符合消息处理接口的规范要求；接收网元是本消息处理完成后，将要发送消息的目标网元号，根据实际情况定义，该值是正整数；发送事件号是目标网元将要处理的事件号，该字段如果配置为结束标志(一般用0表示，也可以使用其他约定的数值)，表示消息流程结束。消息分发表201可以以文件、数据库等方式存储。
消息处理接口301，设置为定义通用的消息处理规范。该接口一般由消息的接收方网元来实现，以定制自己的消息处理方法。该接口只定义规范，以便消息监听装置401能够正确监听到，消息分发表201中配置的每个消息处理方法都是本接口的一个具体实现。
消息监听装置401，负责本网元消息的接收、处理和发送。其中，消息监听装置401可以包括：消息接收器402，设置为监听并接收发往本网元(即网元对应的网管服务器)的消息；消息处理器403，设置为根据消息分发表201中配置的消息处理方法来处理消息，并根据异常分发表进行异常处理；消息发送器404，设置为消息处理完成后，根据消息分发表的配置，将消息发往下一个网元；异常分发表405用于配置遇到特定异常时的处理方式，异常分发表包括异常码和发送事件号两个关键字段。
在本实施例中，消息监听模块401负责监听其他网元对应的网管服务器发送到本网元对应的网管服务器的消息，当监听到有消息过来时，本装置中的消息接收器负责接收消息，并查找消息分发表中事件号对应的消息处理方法，然后由消息处理器执行该方法和进行异常处理。执行完成后，根据消息分发表中配置的数据，由消息发送器将消息发送到下一个网元。
在本发明实施例中，异常分发表405的作用是在消息处理器处理的过程中，如果发生某种异常，决定消息的发送方向。也就是说，在发生异常的情况下，消息分发表201配置的发送事件号就不起作用了，由异常分发表405中配置的事件号来取代。表2是一个异常分发表的示例。
表2.
异常码 发送事件号
120001 4001
120006 4002
在具体实施过程中，异常码对应的具体含义是系统内部定义的，表2所示的异常分发表指示在处理过程中如果发送了代号为120001的异常情况，则转到事件号4001来处理，如果遇到120006，则转到4002来处理，这里的4001和4002也必须在消息分发表中配置并实现。
动态加载装置501设置为加载消息分发表在用户配置或修改消息分发表后，执行动态加载装置501，从而使得消息分发表可以立即生效。在本实施例中，动态加载装置501，用来完成消息分发表的解析和加载。用户实现或修改了消息分发列表的内容后，首先执行动态加载装置501，即可使消息分发列表的内容生效，不影响服务器的正常运行和网元的正常工作。通过动态加载装置，提高了数据传输的灵活性和适用范围，例如可以在用户不知情的情况下，实现对特定网元的监听，对特定信息的收集等。
在本发明实施例中，一次通讯过程可以由网管客户端发起，也可以由用户设定好定时任务，由网管服务器定时发起。通讯发起后，消息监听装置401首先执行发起方 的事件号对应的处理方法，处理完成后，根据消息分发表中配置的顺序，将消息发送到下一个事件号对应的网元继续处理。
如果某网元需要请求其他网元的数据，可以在消息处理方法中实现，使用定制的方法下载其他网元准备好的数据，网管服务器对请求到的数据进行处理后可以进行入库等操作，这时，如果消息分发表中还有下一步流程，则将消息发到下一网元继续处理，如果没有下一步流程，则本次通讯结束，传送模块102将通讯后变化的数据同步到对应网元。
以表1所示的消息分发表为例，11号网元对应的网管服务器首先发起会话(哪个网元侧首先发起并不在消息分发表中体现，是由客户端或定时任务等触发的)，执行【Begin】方法，然后通过消息把事件号2发给13号网元对应的网管服务器；13号网元对应的网管服务器收到消息后，执行事件号2对应的方法【Event 1】，执行完后，把事件号100发回11号网元对应的网管服务器；11号网元对应的网管服务器收到消息后，执行【Event 2】，完成后发101给13号网元对应的网管服务器；13号网元对应的网管服务器接收到消息，执行【End】方法，然后发消息给11号网元对应的网管服务器，事件号是200，其中，事件号200对应的也是【End】方法；11号网元对应的网管服务器执行【End】方法，执行到这里，接收网元和发送事件号都是0，表示流程结束了。
从上述示例中可以看出，在数据传输过程中，消息通道和数据通道是分离的。每个消息中仅仅包含接收网元号和发送事件号两个整型数值，消息体非常小，这样保证了传输的可靠和安全。
在上述示例中并不能直接看出数据是如何传输的，数据传输是在消息处理方法中实现的，如【Event 1】或【Event 2】。用户可以定制任意的传输方式，依靠系统底层的成熟方案进行，例如可以利用加密的sftp服务，而数据的格式本身，用户可以使用自定义的方式进行压缩或加密，应用非常灵活。
并且，在本发明实施例中，所有数据传输的中间过程都是在后台网管服务器上进行的，网元毫不知情，只有在数据传输结束后，发生数据改变的情况下，才由网管的数据传送功能(即上述传送模块)通知网元更新状态。传输过程中如果发生任何网络故障等问题，可以安全的结束本次会话，而不影响网元的工作状态。
通过本发明实施例提供的上述技术方案，将消息通道和数据通道分离，用户可以安照消息处理接口的规范定制消息处理的具体方法，以后台通讯驱动网间的数据传输。因此，具有安全、隐蔽、使用灵活、支持大数据量传输等有益效果。
下面以图7所示的消息分发表及图8所示异常分发表来实现双归属容灾备份为例，对本发明实施例提供的技术方案作进一步说明。其中51、52是主用网元，61是备用网元，51网元是消息的发起方，需要把51和52网元的数据备份到61网元。
在实施时，按照图7和图8在各个网元的对应网管服务器中配置消息分发表和异常分发表，同时实现消息分发表中配置的消息处理方法，然后执行动态加载即可。
图9为本实施例中执行数据备份的系统内部流程图，左边虚线框中表示的是正常流程，右边表示异常流程，仅表示了异常码14001的处理流程，其他异常处理流程类似。正常流程中的多个步骤都可能出现异常而转到异常流程，图中用虚线做了标示。
如图9所示，将51和52网元的数据备份到61网元主要包括以下步骤：
步骤901：网元51对应的网管服务器发起双归属请求，指定事件号是1001。
步骤902:网元51对应的网管服务器的消息监听装置收到事件号为1001的消息，并执行该事件号对应的消息处理方法(Begin)，执行完成后，将消息发送到51和52网元对应的网管服务器，事件号是1002。
说明，在本实施例中，本网管服务器内发送消息也是支持的。
步骤903：网元51、52对应的网管服务器同时收到消息，并执行事件1002(进行主用端的数据校验，如果校验不通过，会自动转到异常流程，下同)，然后发消息到网元61对应的网管服务器。
步骤904：网元61对应的网管服务器执行事件2001(执行备用端数据校验)，完成后发消息给网元51、52对应的网管服务器。
步骤905：网元51、52对应的网管服务器同时执行事件1003(主用端进行数据导出)，完成后发消息给网元61对应的网管服务器。
步骤906：网元61对应的网管服务器执行事件2002(从主用网元51、52获取数据，并处理后导入)，完成后发消息给网元51对应的网管服务器。说明：因为网元51对应的网管服务器是发起方，要把执行情况告知发起方，而不需要通知网元52对应的网管服务器。
步骤907：网元51对应的网管服务器执行事件1004(上报进度，告知用户对方网元已经成功获取数据)，完成后发消息给网元61对应的网管服务器；
步骤908：网元61对应的网管服务器收到消息，执行事件2003(传送数据，即把变化的数据通知前台网元。因为流程中，只有61号网元的数据发生了变化，所以只有61号网元对应的网管服务器需要传送数据)，消息分发表中发送事件号是0，表示流程结束。
步骤909：判断异常码是否是14001，如果是，转到本异常的处理流程910，否则，转到其他异常的处理流程(略)。在上述步骤中，如果任何一步发生异常，即转到本步骤。
步骤910：根据异常分发表，找到14001对应的事件号4000，将消息的发送事件号改为4000，发送的网元不变，发送消息。
步骤911：接收方网元收到4000的消息，进行异常处理(即执行消息分发表中事件号4000对应的消息处理方法Error handler1)。
步骤912：处理异常的网元发送消息到所有网元(51、52、61)，携带事件号5000。
步骤913：所有网元接收到事件号5000的消息，进行善后处理，终止流程。
步骤914：流程结束。
从以上的描述中，可以看出，本发明实施例在数据传输过程中，消息通道和数据通道是分离的。每个消息中仅仅包含接收网元号和发送事件号两个整型数值，消息体非常小，这样保证了传输的可靠和安全。并且，在本发明实施例中，用户可以定制任意的传输方式，依靠系统底层的成熟方案进行，例如可以利用加密的sftp服务，而数据的格式本身，用户可以使用自定义的方式进行压缩或加密，应用非常灵活。另外，在本发明实施例中，所有数据传输的中间过程都是在后台网管服务器上进行的，网元毫不知情，只有在数据传输结束后，发生数据改变的情况下，才由网管的数据传送功能(即上述传送模块)通知网元更新状态。传输过程中如果发生任何网络故障等问题，可以安全的结束本次会话，而不影响网元的工作状态。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，在网管服务器之间传输消息，通过事件号指示传输数据的方法，接收方通过执行事件号指示的消息处理方法获取数据，将消息通道和数据通道分离，用户可以定制消息处理的具体方法，在网管服务器(即后台通讯驱动网)间的数据传输。从而使得数据传输不会使消息通道拥塞，提高了影响系统稳定性，并且，由于通过网管服务器传输数据，从而也避免了数据没有传输完全而出现网络故障时导致数据不完整的问题。

Claims (14)

  1. 一种数据获取方法，包括：
    与第二网元对应的第二网管服务器接收与第一网元对应的第一网管服务器发送的第一消息，其中，所述第一消息中携带有第一事件号；
    所述第二网管服务器查找预先配置的消息分发表，获取与所述第一事件号对应的第一消息处理方法，其中，所述消息分发表中用于记录数据传输的各步流程以及各步流程中需要执行的消息处理方法、下一步流程中的消息接收方和该消息接收方需要处理的事件号，所述第一消息处理方法中定制了所述第二网管服务器从其他网元获取数据的传输方法；
    所述第二网管服务器执行所述第一消息处理方法，从所述其它网元的网管服务器请求并获取数据。
  2. 根据权利要求1所述的方法，其中，在从所述其它网元的网管服务器请求并获取数据之后，所述方法还包括：所述第二网管服务器对请求到的数据进行处理，然后对处理后的数据进行入库操作。
  3. 根据权利要求1所述的方法，其中，在所述第二网管服务器从所述其它网元获取到数据之后，所述方法还包括：
    所述第二网管服务器判断所述消息分发表中是否还有下一步流程，如果有，则所述第二网管服务器从所述消息分发表中获取下一步流程中第二消息的接收网元标识及需要执行的第二消息处理方法的第二事件号；
    所述第二网管服务器向所述接收网元标识的对应的网管服务器发送所述第二消息，其中，所述第二消息中携带有所述第二事件号。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第二网管服务器接收携带有第三事件号的第三消息；
    所述第二网管服务器查找所述消息分发表，获取与所述第三事件号对应的第三消息处理方法，其中，所述第三消息处理方法包括将所述第二网管服务器请求到的数据同步到所述第二网元的方法；
    所述第二网管服务器执行所述第三消息处理方法，将请求到的数据同步到所述第二网元。
  5. 根据权利要求1至4中任一项所述的方法，其中，如果所述第二网管服务器在执行所述第一消息处理方法的过程中出现异常，则所述方法包括：
    所述第二网管服务器查询预先配置的异常码与事件号的对应关系，获取与本次异常的异常码对应的第四事件号；
    所述第二网管服务器发送携带第四事件号的消息。
  6. 根据权利要求1至4中任一项所述的方法，其中，所述方法还包括：
    接收配置所述消息分发表的操作指令；
    根据输入的各个参数，配置所述消息分发表，其中，所述消息分发表中的消息处理方法符合预先设定的消息处理规范；
    加载配置完成的所述消息分发表。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    接收修改所述消息分发表的操作指令；
    根据输入的参数，修改所述消息分发表中对应的表项，其中，修改后的所述消息分发表中的消息处理方法符合预先设定的消息处理规范；
    加载修改后的所述消息分发表。
  8. 一种数据获取装置，位于与第二网元对应的第二网管服务器，所述装置包括：
    第一接收模块，设置为接收与第一网元对应的第一网管服务器发送的第一消息，其中，所述第一消息中携带有第一事件号；
    第一获取模块，设置为查找预先配置的消息分发表，获取与所述第一事件号对应的第一消息处理方法，其中，所述消息分发表中用于记录数据传输的各步流程以及各步流程中需要执行的消息处理方法、下一步流程中的消息接收方和该消息接收方需要处理的事件号，所述第一消息处理方法中定制了所述第二网管服务器从其他网元获取数据的传输方法；
    执行模块，设置为执行所述第一消息处理方法，从所述其它网元的网管服务器请求并获取数据。
  9. 根据权利要求8所述的装置，其中，还包括：
    判断模块，设置为判断所述消息分发表中是否还有下一步流程，如果有，则触发第二获取模块；
    所述第二获取模块，设置为从所述消息分发表中获取下一步流程中第二消息的接收网元标识及需要执行的第二消息处理方法的第二事件号；
    发送模块，设置为向所述接收网元标识的对应的网管服务器发送所述第二消息，其中，所述第二消息中携带有所述第二事件号。
  10. 根据权利要求8所述的装置，其中，
    所述第一接收模块还设置为接收携带有第三事件号的第三消息；
    所述第一获取模块还设置为查找所述消息分发表，获取与所述第三事件号对应的第三消息处理方法，其中，所述第三消息处理方法包括将所述第二网管服务器请求到的数据同步到所述第二网元的方法；
    所述装置还包括：同步模块，设置为执行所述第三消息处理方法，将请求到的数据同步到所述第二网元。
  11. 根据权利要求8至10中任一项所述的装置，其中，还包括：
    异常处理模块，设置为在执行所述第一消息处理方法的过程中出现异常时，查询预先配置的异常码与事件号的对应关系，获取与本次异常的异常码对应的第四事件号，然后发送携带所述第四事件号的消息。
  12. 根据权利要求8至10中任一项所述的装置，其中，还包括：
    第二接收模块，设置为接收配置所述消息分发表的操作指令；
    配置模块，设置为根据输入的各个参数，配置所述消息分发表，其中，所述消息分发表中的消息处理方法符合预先设定的消息处理规范；
    加载模块，加载配置完成的所述消息分发表。
  13. 根据权利要求12所述的装置，其中，
    所述第二接收模块还设置为接收修改所述消息分发表的操作指令；
    所述配置模块还设置为根据输入的参数，修改所述消息分发表中对应的表项，其中，修改后的所述消息分发表中的消息处理方法符合预先设定的消息处理规范；
    所述加载模块还设置为加载修改后的所述消息分发表。
  14. 一种数据获取系统，包括：网元和与所述网元对应的网管服务器，其中，
    所述网管服务器包括权利要求8至13中任一项所述装置，设置为将从其他网元请求到的数据同步到所述网元；
    所述网元，设置为接收所述网管服务器传输的数据。
PCT/CN2014/088777 2014-05-13 2014-10-16 数据获取方法、装置及系统 WO2015172512A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP14892142.2A EP3145120B1 (en) 2014-05-13 2014-10-16 Data acquisition method, device and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410202112.5A CN105099738B (zh) 2014-05-13 2014-05-13 数据获取方法、装置及系统
CN201410202112.5 2014-05-13

Publications (1)

Publication Number Publication Date
WO2015172512A1 true WO2015172512A1 (zh) 2015-11-19

Family

ID=54479255

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/088777 WO2015172512A1 (zh) 2014-05-13 2014-10-16 数据获取方法、装置及系统

Country Status (3)

Country Link
EP (1) EP3145120B1 (zh)
CN (1) CN105099738B (zh)
WO (1) WO2015172512A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111049762A (zh) * 2019-12-23 2020-04-21 上海金仕达软件科技有限公司 数据采集方法、装置、存储介质及交换机
CN111314139A (zh) * 2020-02-19 2020-06-19 北京安帝科技有限公司 一种工控环境下数据采集中设备和事件的标识方法
CN112994917A (zh) * 2019-12-17 2021-06-18 华为技术有限公司 网络管理方法和网络管理装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101789963A (zh) * 2010-01-05 2010-07-28 深圳中兴网信科技有限公司 数据同步系统
CN102523605A (zh) * 2011-12-13 2012-06-27 华为技术有限公司 一种通信方法及设备
WO2013121399A1 (en) * 2012-02-15 2013-08-22 Renesas Mobile Corporation Method and apparatus for allocating discovery resources for device to device communications
CN103563430A (zh) * 2012-11-13 2014-02-05 华为技术有限公司 获取报文信息的方法及网元

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6430188B1 (en) * 1998-07-08 2002-08-06 Broadcom Corporation Unified table for L2, L3, L4, switching and filtering
CN101772007B (zh) * 2008-12-31 2012-10-10 中兴通讯股份有限公司 一种改进的全网信令跟踪系统及方法
US8793539B2 (en) * 2012-06-13 2014-07-29 International Business Machines Corporation External settings that reconfigure the error handling behavior of a distributed PCIe switch

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101789963A (zh) * 2010-01-05 2010-07-28 深圳中兴网信科技有限公司 数据同步系统
CN102523605A (zh) * 2011-12-13 2012-06-27 华为技术有限公司 一种通信方法及设备
WO2013121399A1 (en) * 2012-02-15 2013-08-22 Renesas Mobile Corporation Method and apparatus for allocating discovery resources for device to device communications
CN103563430A (zh) * 2012-11-13 2014-02-05 华为技术有限公司 获取报文信息的方法及网元

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112994917A (zh) * 2019-12-17 2021-06-18 华为技术有限公司 网络管理方法和网络管理装置
CN111049762A (zh) * 2019-12-23 2020-04-21 上海金仕达软件科技有限公司 数据采集方法、装置、存储介质及交换机
CN111314139A (zh) * 2020-02-19 2020-06-19 北京安帝科技有限公司 一种工控环境下数据采集中设备和事件的标识方法

Also Published As

Publication number Publication date
EP3145120A4 (en) 2018-01-03
CN105099738A (zh) 2015-11-25
CN105099738B (zh) 2019-08-02
EP3145120B1 (en) 2019-04-10
EP3145120A1 (en) 2017-03-22

Similar Documents

Publication Publication Date Title
CN102385582B (zh) 生产测试数据处理方法、服务器及系统
US11520808B2 (en) System and method for synchronizing data between communication devices in a networked environment without a central server
US10680874B2 (en) Network service fault handling method, service management system, and system management module
US10103940B2 (en) Local network and method of updating a device in a local network
WO2019061720A1 (zh) 一种数据同步的方法和系统
CA2896865C (en) Method and system for using a recursive event listener on a node in hierarchical data structure
US11741075B2 (en) Methods and system of tracking transactions for distributed ledger
US20200327045A1 (en) Test System and Test Method
US20230254377A1 (en) Establishment of operational status of a machine-to-machine device
CN105052076B (zh) 一种基于云计算的网元管理系统及网元管理方法
WO2017071337A1 (zh) 管理数据库表数据的方法、装置及系统
US20160344582A1 (en) Call home cluster
WO2015172512A1 (zh) 数据获取方法、装置及系统
WO2017071384A1 (zh) 报文处理的方法及装置
CN112417255A (zh) 在线状态的接收方法及装置、存储介质、电子装置
WO2016074412A1 (zh) 基于网络配置协议进行兼容管理的方法、存储介质及设备
WO2022062661A1 (zh) 操作通知方法和装置、存储介质和电子装置
US20240054054A1 (en) Data Backup Method and System, and Related Device
US20240039782A1 (en) Computer network troubleshooting and diagnostics using metadata
US11792095B1 (en) Computer network architecture mapping using metadata
US9300438B2 (en) Method and system for transmitting large object
US10674337B2 (en) Method and device for processing operation for device peripheral
PH12015500675B1 (en) Method and system for transmission management of full configuration synchronization between eml-nml.
CN105991316B (zh) 一种传输网资源数据的实时管理方法和装置
WO2013000287A1 (zh) 小区参数的配置方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14892142

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014892142

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014892142

Country of ref document: EP