WO2016062144A1

WO2016062144A1 - Application node management method, system, and aggregation node

Info

Publication number: WO2016062144A1
Application number: PCT/CN2015/085458
Authority: WO
Inventors: 卞登奎; 邓爱华
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-10-24
Filing date: 2015-07-29
Publication date: 2016-04-28
Also published as: CN105589889A

Abstract

Disclosed is an application node management method, the method comprising: transmitting a first message to an application node, the first message being used for obtaining data of the application node; receiving and storing data transmitted by the application node; receiving a first data request transmitted by a user equipment, and according to the stored data and the first data request, transmitting data corresponding to the first data request to the user equipment. Also disclosed are an aggregation node and a system for managing an application node, thus reducing frequent interaction between the aggregation node and the application node, and enabling the aggregation node to save data of the application node, and avoiding the influence of other factors during a user query.

Description

Method, system and summary node for managing application nodes

Technical field

The present invention relates to the field of communications, and in particular, to a method, system, and summary node for managing an application node.

Background technique

In general, the interaction between the application node and the summary node mostly uses Representational State Transfer (REST) message communication. When the network is interrupted or the application node stops working, the summary data displayed by the summary node may be lacking or directly lost; when some REST message queries take a long time, the user experience may not be ideal; Most of the data synchronization processing will adopt the mechanism of timing synchronization, but if the amount of data is large, it will cause great pressure on the system, and at the same time, many message interactions are wasted.

Summary of the invention

The embodiment of the invention provides a method, a system and a summary node for managing an application node, and aims to at least solve the technical problem of a large number of interaction information between the application node and the summary node.

To achieve at least the above object, an embodiment of the present invention provides a method for managing an application node, where the method includes:

Sending a first message to the application node, where the first message is used to acquire data of the application node;

Receiving data sent by the application node, and storing the data;

Receiving a first data request sent by the user equipment, and sending, according to the stored data and the first data request, data corresponding to the first data request to the user equipment.

After the data request sent by the user equipment is sent to the user equipment according to the stored data and the data request, the method further includes:

Determining whether the stored data is the latest data according to a preset time;

Sending, to the application node, a second message, where the stored data is not the latest data, where the second message is used to obtain latest data of the application node;

Receiving the latest data sent by the application node and storing the latest data.

The method further includes:

Receiving a second data request sent by the user equipment, and sending the second data request to the application node;

Receiving data corresponding to the second data request sent by the application node, and sending the data corresponding to the second data request to the user equipment.

The summary node sends a first message to the application node, where the first message is used to obtain data of the application node;

The summary node receives data sent by the application node, and stores the data;

The summary node receives the first data request sent by the user equipment, and sends the data corresponding to the first data request to the user equipment according to the stored data and the first data request.

After the summary node receives the data request sent by the user equipment, and after sending the data to the user equipment according to the stored data and the data request, the summary node further includes:

Determining, by the summary node, whether the stored data is the latest data according to a preset time;

If the stored data is not the latest data, the summary node sends a second message to the application node, where the second message is used to obtain the latest data of the application node;

The summary node receives the latest data sent by the application node and stores the latest data.

The method further includes:

Receiving, by the user equipment, a second data request sent by the user equipment to access the application node, and sending the second data request to the application node;

Sending, by the application node, data to the summary node according to the second data request;

The summary node receives the data and transmits the data to the user equipment.

In order to achieve at least the foregoing, the embodiment of the present invention provides a summary node, where the summary node includes:

a first sending unit, configured to send a first message to the application node, where the first message is used to acquire data of the application node;

a first receiving unit, configured to receive data sent by the application node, and store the data;

The second receiving unit is configured to receive the first data request sent by the user equipment, and send the data corresponding to the first data request to the user equipment according to the stored data and the first data request.

The summary node further includes:

And an update unit, configured to determine, according to a preset time, whether the stored data is the latest data; if the stored data is not the latest data, send a second message to the application node, where the second message is used to obtain The latest data of the application node; receiving the latest data sent by the application node, and storing the latest data.

The summary node further includes a third receiving unit and a second sending unit;

The third receiving unit is configured to receive a second data request sent by the user equipment;

The second sending unit is configured to send the second data request to the application node;

The third receiving unit is further configured to receive data corresponding to the second data request sent by the application node;

The second sending unit is further configured to send the data corresponding to the second data request to the user equipment.

In order to achieve at least the above object, an embodiment of the present invention provides a system for managing an application node, where the system includes a summary node and at least one application node, and the summary node and the application node transfer a REST interface through a representational state. Connected, the summary node includes the summary node described above.

In the embodiment of the present invention, the first message is sent to the application node, where the first message is used to acquire data of the application node; the data sent by the application node is received, and the data is stored; and the first message sent by the user equipment is received. Data request, sending data corresponding to the first data request to the user equipment according to the stored data and the first data request, thereby reducing frequent interaction between the summary node and the application node, and the summary node may save The data of the application node can be affected by other factors when the user queries.

DRAWINGS

1 is a schematic flowchart of a first embodiment of a method for managing an application node according to the present invention;

2 is a schematic flowchart diagram of a second embodiment of a method for managing an application node according to the present invention;

3 is a schematic flowchart of a third embodiment of a method for managing an application node according to the present invention;

4 is a schematic diagram of a method for managing an application node provided by the present invention;

FIG. 5 is a schematic flowchart diagram of a fourth embodiment of a method for managing an application node according to the present invention;

FIG. 6 is a schematic flowchart diagram of a fifth embodiment of a method for managing an application node according to the present invention;

FIG. 7 is a schematic flowchart diagram of a sixth embodiment of a method for managing an application node according to the present invention;

FIG. 8 is a schematic diagram of functional modules of a first embodiment of a summary node according to the present invention; FIG.

FIG. 9 is a schematic diagram of functional modules of a second embodiment of a summary node according to the present invention; FIG.

FIG. 10 is a schematic diagram of functional modules of a third embodiment of a summary node according to the present invention; FIG.

FIG. 11 is a schematic diagram of functional modules of a system for managing an application node according to the present invention.

The implementation, functional features, and advantages of the present invention will be further described in conjunction with the embodiments.

detailed description

It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The present invention provides a method of managing an application node.

Referring to FIG. 1, FIG. 1 is a schematic flowchart diagram of a first embodiment of a method for managing an application node according to the present invention.

In the first embodiment, the method for managing an application node includes:

Step 101: Send a first message to an application node, where the first message is used to obtain data of the application node.

Specifically, when the system is initialized, the summary node first sends a message to each application node, requests to query the latest data of each application node, and summarizes the data information of each application node and the basic data information of each application node service or other data information of each application node. .

Step 102: Receive data sent by the application node, and store the data.

Specifically, after the data information is returned, the summary node saves the data information in a database, so that the user can request to view data information of each application node.

Step 103: Receive a first data request sent by the user equipment, and send data corresponding to the first data request to the user equipment according to the stored data and the first data request.

Specifically, when the user equipment requests the summary node to view data of each application node, the user equipment sends a data request to the summary node.

The summary node obtains corresponding data from a pre-stored database and sends the data to the user equipment in the form of a page.

Traditional summary nodes do not retain any data, and all data is directly obtained through the Representational State Transfer (REST) interface. If some REST interfaces take a long time, the user experience is not good. When the network is unstable or the application node stops, the display may be lacking or the data cannot be queried, and each visit requires frequent message interaction. The advantage is that the acquired data is real-time data. If the summary node keeps the data in the database, the summary node periodically acquires the data of the application node. The disadvantage of this method is that the real-time performance is not good, and the message is a lot of waste. First, if you need to obtain a large number of messages, it may be quite troublesome to obtain data at regular intervals. If there are fewer types of messages, the messages will be wasted. For example, if the normal summary node does not view the data, timing synchronization is also required. The advantages of this method Because the data has been saved to the summary node, the query is not affected by other factors.

Referring to FIG. 2, FIG. 2 is a schematic flowchart diagram of a second embodiment of a method for managing an application node according to the present invention. On the basis of the first embodiment, step 103 further includes steps 104-106;

Step 104: Determine, according to a preset time, whether the stored data is the latest data;

Specifically, the summary node checks whether the result of the application node N is the latest one. If 30 minutes is a preset time, it can be checked whether the acquired data of the application node N is within 30 minutes.

Step 105: If the stored data is not the latest data, send a second message to the application node, where the second message is used to obtain latest data of the application node;

Specifically, if the data of the application node N is not the latest data, the summary node sends a message to the application node N to request the latest data.

Step 106: Receive latest data sent by the application node, and store the latest data.

Specifically, after the latest message is returned, the summary node saves the latest data in a database.

Referring to FIG. 3, FIG. 3 is a schematic flowchart diagram of a third embodiment of a method for managing an application node according to the present invention. Based on the first embodiment or the second embodiment, steps 107-108 are further included.

Step 107: Receive a second data request sent by the user equipment, and send the second data request to the application node.

Specifically, in a case that the user requests to view basic information of each application node, the user equipment sends a data request to the summary node; the summary node forwards the data request to the application node, and requests to query the application node. The latest data. Receiving data corresponding to the second data request sent by the application node, and sending the data corresponding to the second data request to the user equipment.

In the case that the application node returns a data message, the application node sends the data information to the summary node, so that the summary node directly sends the data message to the user equipment, and does not save the database; The data message is sent to the user equipment in the form of a page.

Referring to FIG. 4, FIG. 4 is a schematic diagram of a method for managing an application node provided by the present invention.

Step 401: When the system is initialized, the summary node first sends a message to each application node, requests to query the latest data of each application node, and summarizes the data information of each application node and the basic data information of each application node service or other data information of each application node. ;

Step 402: After the data information is returned, the summary node saves the data information in a database, so that the user can request to view data information of each application node.

Step 403: When the user equipment requests the summary node to view data of each application node, the user equipment sends a data request to the summary node.

Step 404: The summary node acquires corresponding data from a pre-stored database and sends the data to the user equipment in the form of a page.

Step 405: The summary node checks whether the result of the application node N is the latest one, and assumes that 30 minutes is a preset time, and can check whether the acquired data of the application node N is within 30 minutes;

Step 406: If the data of the application node N is not the latest data, the summary node sends a message to the application node N to request the latest data.

Step 407: After the latest message is returned, the summary node saves the latest data in a database;

Step 408: When the user requests to view basic information of each application node, the user equipment sends a data request to the summary node.

Step 409: The summary node forwards the data request to the application node, and requests to query the latest data of the application node.

Step 410: In the case that the application node returns a data message, the application node sends the data information to the summary node, so that the summary node directly sends the data message to the user equipment, and does not save the database.

Step 411: The summary node sends the data message to the user equipment in the form of a page.

The solution provided by the embodiment of the present invention is to provide a mechanism for combining real-time messages and databases, and the information of the summary class and the information that takes a long time are saved in the database after querying the REST interface, and automatically synchronize the latest data after a fixed time. Other basic information is queried through real-time messages. The advantage of this approach is that it reduces message interaction, and there is no message interaction when the user is not using the summary node. After the user queries the data for the first time, the data is not up to date, and the latest data is automatically synchronized. At this time, the latest data is sent to the user, and the user does not need to wait for synchronization. At the same time, the update time is set so that the user can see the next visit. The latest data for the application node. When the application node stops running or the network is interrupted, it does not affect the access of the summary node because some summary information is stored in the database.

Referring to FIG. 5, FIG. 5 is a schematic flowchart diagram of a fourth embodiment of a method for managing an application node according to the present invention.

In a fourth embodiment, the method for managing an application node includes:

Step 501: The summary node sends a first message to the application node, where the first message is used to obtain data of the application node.

Step 502: The summary node receives data sent by the application node, and stores the data.

Step 503: The user equipment sends a first data request to the summary node.

Step 504: The summary node receives the first data request sent by the user equipment, and sends data corresponding to the first data request to the user equipment according to the stored data and the first data request.

Specifically, the summary node acquires corresponding data from a pre-stored database and sends the data to the user equipment in the form of a page.

Referring to FIG. 6, FIG. 6 is a schematic flowchart diagram of a fifth embodiment of a method for managing an application node according to the present invention. On the basis of the fourth embodiment, step 504 further includes steps 505-507;

Step 505: The summary node determines, according to a preset time, whether the stored data is the latest data.

Step 506: If the stored data is not the latest data, the summary node sends a second message to the application node, where the second message is used to obtain the latest data of the application node.

Step 507: The summary node receives the latest data sent by the application node, and stores the latest data.

Referring to FIG. 7, FIG. 7 is a schematic flowchart diagram of a sixth embodiment of a method for managing an application node according to the present invention. Based on the fourth embodiment or the fifth embodiment, step 508-step 511 is further included.

Step 508: The user equipment sends a second data request for accessing the application node to the summary node.

Specifically, in a case that the user requests to view basic information of each application node, the user equipment sends a data request to the summary node.

Step 509: The summary node receives the second data request, and sends the second data request to the application node.

Specifically, the summary node forwards the data request to the application node, and requests to query the latest data of the application node.

Step 510: The application node sends data to the summary node according to the second data request.

Specifically, in a case that the application node returns a data message, the application node sends the data information to the summary node, so that the summary node directly sends the data message to the user equipment, and does not save the database.

Step 511: The summary node receives the data, and sends the data to the user equipment.

Specifically, the summary node sends the data message to the user equipment in the form of a page.

The embodiment of the invention further provides a summary node.

Referring to FIG. 8, FIG. 8 is a schematic diagram of functional modules of a first embodiment of a summary node according to the present invention.

In the first embodiment, the summary node includes:

The first sending unit 801 is configured to send a first message to the application node, where the first message is used to acquire data of the application node;

The first receiving unit 802 is configured to receive data sent by the application node, and store the data;

The second receiving unit 803 is configured to receive a first data request sent by the user equipment, and send data corresponding to the first data request to the user equipment according to the stored data and the first data request.

Specifically, when the user equipment requests the summary node to view data of each application node, the user equipment sends a data request to the summary node;

Traditional summary nodes do not retain any data, and all data is directly obtained through the Representational State Transfer (REST) interface. If some REST interfaces take a long time, the user experience is not good. When the network is unstable or the application node stops, the display may be lacking or the number of queries may be insufficient. According to this, and each visit requires frequent message interaction, the advantage of this method is that the acquired data is real-time data. If the summary node keeps the data in the database, the summary node periodically acquires the data of the application node. The disadvantage of this method is that the real-time performance is not good, and the message is a lot of waste. First, if you need to obtain a large number of messages, it may be quite troublesome to obtain data at regular intervals. If there are fewer types of messages, the messages will be wasted. For example, if the normal summary node does not view the data, timing synchronization is also required. The advantages of this method Because the data has been saved to the summary node, the query is not affected by other factors.

Referring to FIG. 9, FIG. 9 is a schematic diagram of functional modules of a second embodiment of a summary node according to the present invention. On the basis of the first embodiment, the summary node further includes an update unit 804;

The updating unit 804 is configured to determine, according to a preset time, whether the stored data is the latest data; if the stored data is not the latest data, send a second message to the application node, the second message And acquiring latest data of the application node; receiving latest data sent by the application node, and storing the latest data.

Specifically, the summary node checks whether the result of the application node N is the latest one, and assumes that 30 minutes is a preset time, and can check whether the acquired data of the application node N is within 30 minutes;

If the data of the application node N is not the latest data, the summary node sends a message to the application node N to request the latest data;

After the latest message is returned, the summary node saves the latest data in a database.

Referring to FIG. 10, FIG. 10 is a schematic diagram of functional modules of a third embodiment of a summary node according to the present invention. On the basis of the first embodiment or the second embodiment, a third receiving unit 805 and a second transmitting unit 806 are further included.

The third receiving unit 805 is configured to receive a second data request sent by the user equipment;

The second sending unit 806 is configured to send the second data request to the application node;

The third receiving unit 805 is further configured to receive data corresponding to the second data request sent by the application node;

The second sending unit 806 is further configured to send the data corresponding to the second data request to the user equipment.

Embodiments of the present invention provide a system for managing an application node.

Referring to FIG. 11, FIG. 11 is a schematic diagram of functional modules of a system for managing an application node according to the present invention.

In the first embodiment, the system for managing an application node includes:

The system includes a summary node 1101 and at least one application node 1102, and the summary node 1101 and the application node 1102 are connected by a representational state transition REST interface, and the summary node 1101 includes the summary described in FIGS. 8-10. Node 1101.

In the embodiment of the present invention, the first message is sent to the application node, where the first message is used to acquire data of the application node; the data sent by the application node is received, and the data is stored; and the first message sent by the user equipment is received. a data request, sending the first to the user equipment according to the stored data and the first data request The data requests the corresponding data, thereby reducing the frequent interaction between the summary node and the application node, and the summary node can save the data of the application node, and the user can be influenced by other factors when querying.

The above are only the preferred embodiments of the present invention, and are not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the present invention and the drawings are directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present invention.

Industrial applicability

As described above, the method, system, and summary node for managing an application node provided by the embodiment of the present invention have the following beneficial effects: the first message is used to obtain the application node by sending a first message to the application node. And receiving the data sent by the application node, and storing the data; receiving a first data request sent by the user equipment, and sending the first message to the user equipment according to the stored data and the first data request. The data requests the corresponding data, thereby reducing the frequent interaction between the summary node and the application node, and the summary node can save the data of the application node, and the user can be influenced by other factors when querying.

Claims

A method of managing an application node, the method comprising:

Sending a first message to the application node, where the first message is used to acquire data of the application node;

Receiving data sent by the application node, and storing the data;

Receiving a first data request sent by the user equipment, and sending, according to the stored data and the first data request, data corresponding to the first data request to the user equipment.
The method of claim 1, wherein the receiving a data request sent by the user equipment, after transmitting the data to the user equipment according to the stored data and the data request, further comprising:

Determining whether the stored data is the latest data according to a preset time;

Sending, to the application node, a second message, where the stored data is not the latest data, where the second message is used to obtain latest data of the application node;

Receiving the latest data sent by the application node and storing the latest data.
The method of claim 1 or 2, wherein the method further comprises:

Receiving a second data request sent by the user equipment, and sending the second data request to the application node;

Receiving data corresponding to the second data request sent by the application node, and sending the data corresponding to the second data request to the user equipment.
A method of managing an application node, the method comprising:

The summary node sends a first message to the application node, where the first message is used to obtain data of the application node;

The summary node receives data sent by the application node, and stores the data;

The summary node receives the first data request sent by the user equipment, and sends the data corresponding to the first data request to the user equipment according to the stored data and the first data request.
The method of claim 4, wherein the summary node receives the data request sent by the user equipment, and after the data is sent to the user equipment according to the stored data and the data request, the summary node further includes:

Determining, by the summary node, whether the stored data is the latest data according to a preset time;

If the stored data is not the latest data, the summary node sends a second message to the application node, where the second message is used to obtain the latest data of the application node;

The summary node receives the latest data sent by the application node and stores the latest data.
The method of claim 4 or 5, wherein the method further comprises:

Receiving, by the user equipment, a second data request sent by the user equipment to access the application node, and sending the second data request to the application node;

Sending, by the application node, data to the summary node according to the second data request;

The summary node receives the data and transmits the data to the user equipment.
A summary node, the summary node includes:

a first sending unit, configured to send a first message to the application node, where the first message is used to acquire data of the application node;

a first receiving unit, configured to receive data sent by the application node, and store the data;

The second receiving unit is configured to receive the first data request sent by the user equipment, and send the data corresponding to the first data request to the user equipment according to the stored data and the first data request.
The summary node of claim 7, wherein the summary node further comprises:

And an update unit, configured to determine, according to a preset time, whether the stored data is the latest data; if the stored data is not the latest data, send a second message to the application node, where the second message is used to obtain The latest data of the application node; receiving the latest data sent by the application node, and storing the latest data.
The summary node according to claim 7 or 8, wherein the summary node further comprises a third receiving unit and a second sending unit;

The third receiving unit is configured to receive a second data request sent by the user equipment;

The second sending unit is configured to send the second data request to the application node;

The third receiving unit is further configured to receive data corresponding to the second data request sent by the application node;

The second sending unit is further configured to send the data corresponding to the second data request to the user equipment.
A system for managing an application node, the system comprising a summary node and at least one application node, the summary node and the application node being connected by a representational state transfer REST interface, the summary node comprising claims 7-9 A summary node as described in any of the items.