CN109801029B - Cross-node service cooperation system and method - Google Patents

Abstract

The embodiment of the application provides a cross-node service cooperation system and method, which are applied to a network architecture comprising a central end and a plurality of node ends, mainly comprises a cooperative business execution flow template and the service type of the node end, when receiving the execution request of the cooperative business, the cooperative business flow template for executing the cooperative business is called, so that the central terminal sends the cooperative service to each node terminal in sequence according to the execution steps in sequence included in the cooperative service execution flow template to complete the processing of each execution step, thereby completing the execution request of the cooperation service through the mutual cooperation of the node end and the center end, and monitoring the execution process of the cooperative business to generate monitoring data, thereby providing a reliable process management mechanism and a reliable monitoring mechanism of the cross-node cooperative business.

Description

Cross-node service cooperation system and method

Technical Field

The embodiment of the application relates to the field of electronic information automated processing, in particular to a cross-node service cooperation system and a cross-node service cooperation method.

Background

At present, a cooperation mode adopted by cross-system and cross-node business cooperation is related, one mode is to use RPC technology to call service to complete cooperation, and the other mode is to use a data transmission platform to realize database synchronization and file exchange to complete cooperation.

However, the above-mentioned collaboration mechanism lacks a management and monitoring mechanism for the collaboration process of the service, and cannot explain the problem of the duplicate data row in the transmission platform database, and cannot monitor the status in the collaboration.

Therefore, how to provide a reliable cross-node service cooperation mechanism to overcome the above problems in the prior art is a technical subject to be solved by the present application.

Disclosure of Invention

In view of this, embodiments of the present invention mainly aim to provide a cross-node service cooperation system and method, which can implement a service cooperation process between each node and a central end to provide a reliable cooperation service process management mechanism.

Another object of the embodiments of the present invention is to provide a cross-node service collaboration system and method, which can provide a monitoring mechanism for collaboration services, and monitor processing flow and processing time of the collaboration services, so that each party participating in the collaboration services can determine processing progress of each collaboration service, thereby improving processing efficiency of the collaboration services.

Another objective of the embodiments of the present invention is to provide a cross-node service collaboration system and method, which can provide a reliable data transmission mechanism by providing an identity verification mechanism for a central end and a node end participating in a collaboration service, and connecting the central end and each node end through a middleware system.

A first embodiment of the present application provides a cross-node service collaboration system, which is applied to a network architecture, where the network architecture includes a central node and a plurality of node nodes connected to the central node, respectively, where the node nodes are configured to provide services, and the cross-node service collaboration system includes: a setting database, configured to store a collaborative business execution flow template and a service type of the service provided by the node, where the collaborative business execution flow template includes at least one execution step arranged in sequence, and each execution step is used to execute one service type; the monitoring database is used for storing monitoring data; a cooperative service execution module, configured to receive an execution request of a cooperative service, retrieve the cooperative service flow template for executing the cooperative service from the set database, so that the central end sequentially sends the cooperative service to each node end according to the execution steps in sequence included in the cooperative service execution flow template, so as to complete processing of each execution step in the cooperative service execution flow template by each node end, and complete the execution request of the cooperative service through mutual cooperation between the node end and the central end; and the cooperative business monitoring module is used for monitoring the execution process of the cooperative business execution module on the cooperative business to generate monitoring data and storing the monitoring data into the monitoring database.

Optionally, in any embodiment of the present application, the system further includes: a node management module, configured to set the service type, the attribution unit, and a service ID of the service provided by the node, where the service ID is used to identify the service type and the attribution unit of the service provided by the node, and store the service type, the attribution unit, and the service ID of the node into the setting database; the collaboration business execution flow template is used for executing the collaboration business execution flow template, and generating a corresponding template ID and a step ID, wherein the template ID is an identification number of the collaboration business execution flow template, the step ID refers to the execution steps in the collaboration business execution flow template, the execution steps comprise the service types executed by the execution steps and the execution sequence of the service types, and the collaboration business execution flow template, the template ID and the step ID are stored in the setting database; the cooperative service execution module further receives an execution request of the cooperative service, allocates a cooperative ID to the cooperative service, queries a template ID for executing the cooperative service from the set database, and sequentially sends the cooperative service to each node end by the center end according to each step ID included in the template ID to execute processing, wherein the cooperative service execution module queries the service ID responsible for executing the step ID from the set database by analyzing the service type executed by the step ID to be currently executed and analyzing the affiliation unit corresponding to the cooperative service, so that the center end sends the cooperative service to the node end corresponding to the service ID to execute processing; and the cooperative business monitoring module also records data materials generated by the cooperative business execution module in the execution process of the cooperative business, including recording the cooperation ID of the cooperative business, the template ID called in the process of executing the cooperative business, the step ID and the service ID, and stores the data materials into the monitoring database.

Optionally, in any embodiment of the present application, the cooperative service monitoring module further analyzes whether an actual execution processing sequence of the cooperative service executed by the cooperative service execution module matches the cooperative service execution flow template stored in the setting database, and outputs a prompt message when an analysis result is that the actual execution processing sequence does not match the cooperative service execution flow template stored in the setting database.

Optionally, in any embodiment of the present application, the cooperative service management module further includes a preset execution time limit corresponding to the step ID, and the preset execution time limit is stored in the setting database.

Optionally, in any embodiment of the present application, the cooperative service monitoring module further records an actual execution time of each step ID of the cooperative service executed by the cooperative service execution module, determines whether the actual execution time limit matches the preset execution time limit stored in the setting database, and outputs the prompt information when determining that the actual execution time exceeds the preset execution time limit.

Optionally, in any embodiment of the present application, the cooperative service management module further includes a node end configured to feed back an execution result of the cooperative service to the center end, where the center end and the node end are in communication connection with each other through a middleware system, and the center end and the node end are in communication connection by using a message queue asynchronous mechanism or a message queue synchronous mechanism.

Optionally, in any embodiment of the present application, the system further includes an access management module, configured to provide authorization processes for the central node and the node respectively to generate corresponding authorization information, and store the authorization information in the setting database; and the identity authentication module is used for receiving the access requests of the central terminal and the node terminal, authenticating the identities of the central terminal and the node terminal according to the authorization information stored in the setting database, and providing the central terminal and the node terminal to access the cross-node service collaboration system to execute the collaboration service after the authentication is passed.

A second embodiment of the present application provides a cross-node service cooperation method, which is applied to a network architecture, where the network architecture includes a center end and a plurality of node ends respectively connected to the center end, where the node ends are used to provide services, and the cross-node service cooperation method includes: establishing a setting database for setting and storing a cooperative business execution flow template and a service type of the service provided by the node side, wherein the cooperative business execution flow template comprises at least one execution step arranged in sequence, and each execution step is respectively used for executing one service type; receiving an execution request of a cooperative service, so as to invoke the cooperative service flow template for executing the cooperative service from the set database, and enabling the center end to sequentially send the cooperative service to each node end according to the execution steps in sequence included in the cooperative service execution flow template, so as to complete the processing of each execution step in the cooperative service execution flow template by each node end; and monitoring the execution process of the cooperation business to generate monitoring data, and storing the monitoring data into a monitoring database.

Optionally, in any embodiment of the present application, the method further includes: setting the service type, a home unit and a service ID of the service provided by the node end, wherein the service ID is used for identifying the service type and the home unit of the service provided by the node end; setting a template ID and a step ID corresponding to the cooperative business execution flow template, wherein the template ID is an identification number of the cooperative business execution flow template, and the step ID refers to the execution steps in the cooperative business execution flow template and comprises the service types executed by the execution steps and an execution sequence thereof; and storing the setting data in the setting database.

Optionally, in any embodiment of the present application, the method further includes: receiving an execution request of a cooperation service, distributing a cooperation ID for the cooperation service, and inquiring a template ID for executing the cooperation service from the set database; analyzing the service type executed by the step ID to be executed currently and analyzing the attribution unit corresponding to the cooperative service according to the step ID contained in the template ID, so as to inquire the service ID responsible for executing the step ID from the setting database, and enabling the central terminal to send the cooperative service to the node terminal corresponding to the service ID for executing processing, so as to complete the execution request of the cooperative service through mutual cooperation of the node terminal and the central terminal; and recording data information generated in the execution process of the collaboration service, including recording the collaboration ID of the collaboration service, the template ID called by the execution of the collaboration service, the step ID and the service ID, and storing the data information into the monitoring database.

Optionally, in any embodiment of the present application, the method further includes analyzing whether the step IDs executed by the collaborative business and the processing order of each step ID match the collaborative business execution flow template stored in the setting database, and outputting a prompt message when the analysis result is that the step IDs do not match the collaborative business execution flow template.

Optionally, in any embodiment of the present application, the method further includes setting a preset execution time limit corresponding to the step ID, and storing the preset execution time limit in the setting database; and recording the actual execution time of each step ID of the cooperative service, judging whether the actual execution time exceeds the preset execution time limit stored in the set database, and outputting the prompt message when judging that the actual execution time exceeds the preset execution time limit.

Optionally, in any embodiment of the present application, the method further includes performing authorization processing on the central terminal and the node terminal to generate corresponding authorization information, and storing the authorization information in the setting database; and when receiving the access request of the central terminal and/or the node terminal, verifying the identity of the central terminal and/or the node terminal according to the authorization information stored in the setting database, and after the verification is passed, providing the access of the central terminal and/or the node terminal to execute the cooperative service.

As can be seen from the above, the cross-node service cooperation system and method provided in the embodiments of the present application can implement a service cooperation process between each node end and a center end, and can make different cooperation service execution process templates for cross-node cooperation services according to service requirements, so as to provide a reliable process management mechanism for the cross-node cooperation services.

In addition, the cross-node service cooperation system and method can also monitor the whole execution process of the cooperation service, and output corresponding prompt information when the actual execution flow of the analysis cooperation service is not consistent with the preset execution flow or the actual operation time of the cooperation service exceeds the preset time limit, so that the processing efficiency of the cooperation service is improved.

Moreover, the cross-node service cooperation system and the cross-node service cooperation method carry out identity authentication aiming at the central end and the node end which participate in the cooperation service, and the central end and the node end are mutually connected and communicated through the middleware system, so that asynchronous transmission or synchronous transmission of messages is realized according to actual scene requirements, and a reliable data transmission mechanism is provided.

Drawings

Some specific embodiments of the present application will be described in detail hereinafter by way of illustration and not limitation with reference to the accompanying drawings. The same reference numbers in the drawings identify the same or similar elements or components. Those skilled in the art will appreciate that the drawings are not necessarily drawn to scale. In the drawings:

fig. 1A is a schematic diagram of a basic architecture of a cross-node service collaboration system according to an embodiment of the present application;

FIG. 1B is a schematic diagram illustrating an embodiment of the cross-node business collaboration system shown in FIG. 1A;

fig. 2A and 2B are schematic diagrams illustrating a network architecture suitable for the cross-node service cooperation system of fig. 1;

FIG. 3 is a schematic diagram showing another embodiment of the cross-node business collaboration system of FIG. 1A; and

fig. 4 is a flowchart illustrating basic steps of a cross-node service cooperation method according to another embodiment of the present application.

Detailed Description

It is not necessary for any particular embodiment of the invention to achieve all of the above advantages at the same time.

In order to make those skilled in the art better understand the technical solutions in the embodiments of the present invention, the technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention shall fall within the scope of the protection of the embodiments of the present invention.

The following further describes specific implementation of the embodiments of the present invention with reference to the drawings.

Fig. 1A is a schematic diagram of a basic architecture of a cross-node service collaboration system according to an embodiment of the present application; fig. 1B is a schematic diagram of an embodiment of the cross-node service collaboration system of fig. 1A. The cross-nodeservice cooperation system 100 of the present application can implement a service cooperation process between thenode end 12 and thecenter end 11, and can provide accurate remote cooperation information.

Please refer to fig. 2A, which is a schematic diagram of an embodiment of anetwork architecture 10 to which the cross-nodeservice cooperation system 100 of the present application is applied. As shown in the figure, thenetwork architecture 10 includes acentral node 11 and a plurality ofnode nodes 12a to 12f respectively connected to thecentral node 11, wherein thecentral node 11 and thenode nodes 12a to 12f adopt a star deployment architecture, which enables thecentral node 11 to have the capability of cooperative service supervision and mastering, in this embodiment, thenode nodes 12a to 12f are used for providing services, and thecentral node 11 has the functions of monitoring information recording, authorization checking and message distribution. It should be noted that the number of thenode terminals 12 in thenetwork architecture 10 is not limited to that shown in fig. 2A, and the number of the node terminals may be arbitrarily increased or decreased according to actual service requirements.

Referring to fig. 1A and fig. 1B, a cross-nodeservice cooperation system 100 of the present application includes aconfiguration database 101, amonitoring database 102, a cooperationservice execution module 105, and a cooperationservice monitoring module 106.

Themonitoring database 102 is used for storing monitoring data.

Thesetting database 101 is configured to store a collaborative business execution flow template and a service type of a service provided by the node, where the collaborative business execution flow template includes at least one execution step arranged in sequence, and each execution step is used to execute one service type.

In an embodiment of the present application, the cross-nodeservice collaboration system 100 further includes anode management module 103 and a collaborationservice management module 104.

Thenode management module 103 is configured to set a service type, a home unit, and a service ID of thenode 12, and store the set service type, home unit, and service ID of the service provided by thenode 12 in theconfiguration database 101. Specifically, the service type is an attribute definition for a service, and is a type definition for the same type of service, anddifferent node sides 12 corresponding to the same service type can register the service type of the type. In addition, eachdifferent node 12 also has a corresponding home unit, for example, the home unit of thenode 12a responsible for managing the resident identification card service of the beijing domicile is "the office of the beijing domicile bureau", the home unit of thenode 12b responsible for managing the resident identification card service of the shanghai domicile is "the office of the shanghai domicile bureau", and the home unit of thenode 12c responsible for managing the resident identification card service of the guangzhou domicile is "the office of the guangzhou domicile bureau". The service ID is used to identify a service type and a home unit of a service provided by thenode 12, that is,different node 12 may belong to the same service type, but the home units are different from each other, and the service ID is also different.

The collaborationservice management module 104 is configured to set a collaboration service execution flow template, and generate a corresponding template ID and a step ID, where the collaboration service execution flow template, the template ID, and the step ID are also stored in thesetting database 101. In this embodiment, the set collaboration execution flow template and the corresponding template ID and step ID thereof are also packaged into a "configuration file" form in advance to be issued to thecentral node 11 and eachnode 12, so that when thecentral node 11 and eachnode 12 execute collaboration, the template ID can be directly obtained from the locally stored configuration file.

Specifically, the collaboration business execution flow template is formed by combining a plurality of service types according to a preset execution sequence, that is, the collaboration business execution flow template can be regarded as a standard collaboration flow formed by combining a plurality of service types according to a certain sequence according to business requirements, and the set collaboration business execution flow template can automatically generate a corresponding template ID to serve as an identification number of the collaboration business execution flow template.

The step ID is used to refer to each execution step in the collaborative business execution flow template, and includes the service type executed by the execution step and the execution order thereof, for example, if the collaborative business execution flow template with a template ID of 10 includes four execution steps in total, the step ID may be referred to as step 1, step 2, step 3, and step 4, respectively, and the service type executed by the execution step is recorded in the step ID.

For example, the business process of the collaboration business set for the business type "identity card remote acceptance business" may roughly include the following execution steps, step 1 "business acceptance"; step 2, the household registration place accepts, audits and issues; step 3, "making ID card"; 4 'ID card receiving and issuing information recording'. The collaborationservice execution module 105 is responsible for executing processing operations of the collaboration service. The method comprises the steps of receiving an execution request of a cooperative service, calling a cooperative service flow template for executing the cooperative service from thesetting database 101, so that a central terminal 11 sequentially sends the cooperative service to eachnode terminal 12 according to the execution steps in sequence included in the cooperative service execution flow template, and processing each execution step in the cooperative service execution flow template by eachnode terminal 12, so that the execution request of the cooperative service is completed through mutual cooperation of the node terminals and the central terminal.

Specifically, the collaborationservice execution module 105 is configured to receive a request for executing a collaboration service, and in general, the request for executing the collaboration service is received by anynode 12. In detail, in thenetwork architecture 10 shown in fig. 2A, each node 12A to 12f may further be connected to at least one service system, and the service system may be configured to provide a user operation interface for a user to input a request for executing a collaboration service, and transmit the input request for executing the collaboration service to thenode 12 connected to the service system through the service system. When the cooperativeservice execution module 105 receives the execution request of the cooperative service, it allocates a cooperation ID for the cooperative service, that is, when a user initiates an execution request of a cooperative service through any one of thenode terminals 12a to 12f, the cooperativeservice execution module 105 allocates a corresponding cooperation ID for the initiated cooperative service, where each cooperative service has only one cooperation ID, and the cooperation ID can act on the process global and is used to serially execute all the execution steps of the cooperative service.

Then, the cooperativeservice execution module 105 queries a template ID corresponding to the cooperative service from theconfiguration database 101, that is, queries a cooperative service execution flow template for executing the cooperative service from theconfiguration database 101, and sequentially sends the cooperative service to each of the node ends 12 by thecentral end 11 according to the step ID included in the template ID to execute processing.

Specifically, the cooperativeservice execution module 105 first determines the service type corresponding to the step ID to be executed currently according to the step ID included in the template ID, and analyzes the attribution unit corresponding to the cooperative service, so as to query the service ID responsible for executing the step ID from thesetting database 101 according to the analyzed service type and attribution unit, and enable thecentral node 11 to send the cooperative service to thenode 12 corresponding to the service ID for executing the processing. In addition, the cooperativeservice management module 104 further causes thenode 12 to feed back the execution result of the cooperative service to thecentral end 11, that is, after thenode 12 completes the processing corresponding to the step ID, the processing result of the cooperative service is fed back to thecentral end 11, and then the cooperativeservice execution module 105 determines the step ID to be executed next according to the step ID included in the template ID, and repeats the above operations until all the step IDs in the template ID are completed.

For example, if the king of the Shanghai nationality needs to handle the "remote acceptance service of the ID card" in Beijing, the execution request of the "remote acceptance service of the ID card" can be submitted through an acceptance window (for example, thenode 12a) located in Beijing, the collaborationservice execution module 105 firstly enables thenode 12a to transmit the execution request of the "remote acceptance service of the ID card" to thecentral terminal 11, and thecentral terminal 11 firstly calls the collaboration service execution flow template and the corresponding template ID for processing the "remote acceptance service of the ID card" and the step IDs included in the template IDs from the matching configuration file stored locally, and executes the step IDs in sequence. For example, when the central terminal 11 determines that the current execution is step 1, it can query the configuration file that the service type executed correspondingly in step 1 is "business acceptance", the attribution unit executed correspondingly is "central acceptance of public security department", and the service ID of the service type "business acceptance" and the attribution unit is "central acceptance of public security department" is searched from the setting database 101, and the node terminal 12e is queried to correspond to the service ID, the central terminal 11 will send the execution request of "remote business acceptance" to the node terminal 12e to execute the processing operation of "business acceptance", after the node terminal 12e completes the processing of "business acceptance", an execution record of acceptance record will be generated, and the service ID corresponding to the next step ID (i.e. step 2) will be automatically determined according to the configuration file stored locally, the information is packaged and fed back to the central terminal 11, so that the central terminal 11 can read the information conveniently; when the central node 11 receives the "record of acceptance record" and the "service ID corresponding to the next step ID" in the packet information fed back by the node 12e, the central node then sends the collaboration service to the node 12 (e.g., the node 12c) corresponding to the service ID to execute the step ID, so as to complete the request for executing the collaboration service through mutual collaboration between the node 12 and the central node 11.

The cooperativeservice monitoring module 106 is configured to monitor the execution process of the cooperativeservice execution module 105 on the cooperative service to generate monitoring data, and store the monitoring data in themonitoring repository 102.

Specifically, the cooperativeservice monitoring module 106 is configured to record all data materials generated by the cooperativeservice execution module 105 in the execution process of the cooperative service, including the cooperation ID of the cooperative service, the template ID called in the execution process of the cooperative service, the step ID, and the service ID, and store the data materials in themonitoring database 102, so as to achieve the purpose of monitoring the execution process of the cooperative service.

Themonitoring database 102 may be disposed at thecentral terminal 11 for being queried by each party participating in the collaboration service, but not limited thereto, themonitoring database 102 may also be disposed in the electronic devices of any third party other than thecentral terminal 11 and thenode terminal 12.

In an embodiment, the cooperativeservice monitoring module 106 is further configured to analyze whether the actual execution processing sequence of the cooperative service executed by the cooperativeservice execution module 105 for the cooperative service matches with the cooperative service execution flow template stored in theconfiguration database 101, and output a prompt message if the analysis result indicates that the actual execution processing sequence of the cooperative service does not match with the cooperative service execution flow template stored in theconfiguration database 101. For example, the cooperativeservice monitoring module 106 analyzes that the template ID includes three step IDs according to the template ID called for executing the cooperative service, and then determines whether the cooperativeservice execution module 105 completely executes the three step IDs and whether the executed sequence is consistent with the set sequence, and if any one of the three step IDs is found not to be consistent with the set sequence, the related prompt information may be output.

In another embodiment, the collaborationservice management module 104 may further configure a preset execution time limit for the step ID, and associate the step ID and the corresponding preset execution time limit to store in theconfiguration database 101. Correspondingly, the cooperativeservice monitoring module 106 may further record an actual execution time of each step ID of the cooperative service executed by the cooperativeservice execution module 105, determine whether an actual execution time limit for the cooperativeservice execution module 105 to execute the step ID matches a preset execution time limit for the step ID stored in thesetting database 101, and output the prompt information when the actual execution time exceeds the preset execution time limit.

Referring to fig. 2B, in another embodiment of the present application, amiddleware system 13 is further built between thecentral end 11 and the node ends 12, so as to provide mutual communication between thecentral end 11 and eachnode end 12 through themiddleware system 13, and thecentral end 11 and the node ends 12 can perform communication connection through a message queue asynchronous mechanism or a message queue synchronous mechanism according to an actual usage scenario through themiddleware system 13.

Referring to fig. 3, in another embodiment of the present application, the cross-nodeservice cooperation system 100 further provides an authentication mechanism. The system composition architecture of the cross-nodeservice cooperation system 100 shown in fig. 3 is basically the same as that shown in fig. 1A and 1B, but the difference is that the cross-nodeservice cooperation system 100 in this embodiment further includes anaccess management module 107 and anidentity verification module 108.

Theaccess management module 107 is configured to provide authorization processing for thecentral node 11 and eachnode 12 to generate corresponding authorization information, and store the authorization information of thecentral node 11 and thenode 12 in theconfiguration database 101. That is, theaccess management module 107 is configured to provide registration and authorization processes for accessing thecentral node 11 and the node 12 (including the service system connected to the node 12) of the cross-nodeservice cooperation system 100, and assign a corresponding authorization code.

Theidentity verification module 108 is configured to, when receiving the access requests of thecentral end 11 and thenode end 12, verify the identities of thecentral end 11 and thenode end 12 according to the authorization information stored in theconfiguration database 101, and after the verification is passed, enable thecentral end 11 and thenode end 12 to access the cross-nodeservice cooperation system 100 of the present application to execute related service processing. For example, after thenode end 12 receives the execution request of the cooperative service, that is, the execution request of the cooperative service and the authorization code of thenode end 12 are transmitted to thecenter end 11 together, the cross-nodeservice cooperation system 100 checks the authorization code of thenode end 12, and after the check is passed, thecenter end 11 receives the execution request of the cooperative service transmitted by thenode end 12 and executes corresponding processing; if the verification result is that the authorization code is not authorized or the service called by thenode 12 does not conform to the authorization range, the execution request of the collaboration service transmitted by thenode 12 is discarded, and the related information of the failure of calling the collaboration service is fed back to thenode 12 to stop collaboration.

Please refer to fig. 4, which is a flowchart illustrating basic steps of a cross-node service cooperation method according to another embodiment of the present application. The cross-node service cooperation method of the present application is applied to a network architecture 10 (please refer to fig. 2A), where thenetwork architecture 10 includes a central end and a plurality of node ends respectively connected to the central end, so as to implement a service cooperation process between the node ends and the central end 1. As shown in the figure, the cross-node service cooperation method mainly includes the following processing steps:

step S41, a setting database is established for setting and storing a collaborative business execution flow template and a service type of the service provided by the node, wherein the collaborative business execution flow template includes at least one execution step arranged in sequence, and each execution step is respectively used for executing one service type.

In an embodiment of the present application, the step 41 further includes providing a user to set a home unit and a service ID of the service provided by the node, and to set a template ID and a step ID corresponding to the collaborative business execution flow template, and storing the setting data in a setting database. In this embodiment, the service ID is used to identify the service type and the attribution unit of the service provided by the node, the template ID is an identification number of the collaborative business execution flow template, and the step ID refers to the execution step in the collaborative business execution flow template, including the service type executed by the execution step and the execution sequence thereof.

Step S42, receiving an execution request of a collaboration service, so as to retrieve the collaboration service flow template for executing the collaboration service from a configuration database.

In an embodiment of the present application, the step S42 further includes allocating a collaboration ID to the collaboration service, and querying and calling a collaboration service execution flow template for executing the collaboration service and a corresponding template ID from theconfiguration database 101. Specifically, when a user initiates an execution request of a collaboration service through any one node, a corresponding collaboration ID is allocated to the collaboration service, wherein each collaboration service only has one collaboration ID, and the collaboration ID can act on the process global and is used for serially connecting all execution steps of the collaboration service.

Step S43, enabling the central end to sequentially send the collaboration services to each node end according to the execution steps in the collaboration service execution flow template that are arranged in order, so as to complete the processing of each execution step.

Specifically, the central node analyzes the service type corresponding to the step ID to be executed currently and the attribution unit corresponding to the cooperative service according to the step ID included in the template ID, queries the service ID responsible for executing the step ID from a set database, and sends the cooperative service to the node corresponding to the service ID to execute the execution step corresponding to the step ID. Preferably, after the node end completes executing the executing step corresponding to the current step ID, the executing result of the cooperative service may be fed back to the center end.

It should be noted that, during the execution of step 43, the monitoring operation of step S431 may be executed synchronously to record the data generated during the execution of the collaboration service, including recording the collaboration ID of the collaboration service, the template ID, the step ID and the service ID called by the execution of the collaboration service, and storing the data in the monitoring database.

In an embodiment, the step S431 further includes analyzing whether the step IDs executed by the collaborative business and the processing sequence of each step ID match the collaborative business execution flow template stored in the configuration database, and outputting a prompt message when the analysis result is that the step IDs do not match the collaborative business execution flow template.

In another embodiment, step S41 may further include setting a preset execution time limit corresponding to the step ID, and storing the preset execution time limit in a setting database, and correspondingly, step S431 further includes recording an actual execution time of each step ID of the collaboration service, and determining whether the actual execution time limit exceeds the preset execution time limit stored in thesetting database 101, and outputting the prompt message when the actual execution time limit exceeds the preset execution time limit.

Step S44, determining whether all step IDs included in the called template ID have been executed, if not, executing step S45, and if the determination result is that all step IDs have been executed, indicating that the collaboration service has been executed, then ending the step.

And step S45, inquiring and calling the ID of the next step to be executed in the template ID, and returning to execute step S43.

In another embodiment of the present application, the method further includes an authorization verification step, which specifically includes:

and executing authorization processing aiming at the central terminal and the node terminal to be accessed to generate corresponding authorization information, and storing the authorization information into the setting database.

When receiving an access request of the central terminal and/or the node terminal, verifying the identity of the central terminal and/or the node terminal according to the authorization information stored in the set database, and after the verification is passed, providing the central terminal and/or the node terminal access to execute the cooperative service.

For example, in an embodiment, when the node receives the execution request of the collaboration service, the node transmits the corresponding authorization information, the service ID, the collaboration ID, and the execution request of the collaboration service to the center to request collaboration, after receiving the data information transmitted by the node, the center performs identity verification on the authorization information of the node, if the identity verification passes, the center responds to the execution request of the collaboration service transmitted by the node to execute corresponding service processing, and if the identity verification fails, the node discards the execution request of the collaboration service transmitted by the node and returns information of the response failure to the node. Meanwhile, the center terminal can also analyze the service ID, the cooperation ID and the cooperation service aiming at the authorization information transmitted by the node terminal, record the actual operation time of the cooperation service, and write the data into the monitoring database so as to generate a cooperation record corresponding to the cooperation service in the monitoring database, thereby achieving the purpose of monitoring the processing flow of the cooperation service.

In summary, the cross-node service cooperation system and method provided by the embodiment of the present application can implement a service cooperation process between each node and a center, can provide accurate remote cooperation information, and can get through the same cooperation ID to string up all cooperation processing steps by assigning a cooperation ID to each cooperation service, and can make clear the execution progress of the cooperation process through the recorded cooperation information.

In addition, the cross-node service cooperation system and method provided by the embodiment of the application are suitable for a network architecture adopting a star deployment mode, so that a central end has powerful cooperative service supervision and control capacity.

In addition, by setting the cooperative service execution flow template, a standard service flow specification is formed conveniently, a flexible and changeable cooperative service execution flow template can be set according to actual service requirements, the condition that service processing flows of all node ends are inconsistent can be avoided, and the processing efficiency of the cooperative service is improved.

In addition, the method and the device also aim at verifying the identities of the central end and the node end which are accessed to participate in the cooperative service, and provide data communication service between the central end and the node end by using a middleware system so as to realize asynchronous transfer or synchronous transfer of messages according to actual scene requirements, thereby providing a reliable data transmission mechanism.

The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions and/or portions thereof that contribute to the prior art may be embodied in the form of a software product that can be stored on a computer-readable storage medium including any mechanism for storing or transmitting information in a form readable by a computer (e.g., a computer). For example, a machine-readable medium includes Read Only Memory (ROM), Random Access Memory (RAM), magnetic disk storage media, optical storage media, flash memory storage media, electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), and others, and the computer software product includes instructions for causing a computing device (which may be a personal computer, server, or network device, etc.) to perform the methods described in the various embodiments or portions of the embodiments.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the embodiments of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus (device), or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Claims (10)

1. A cross-node service cooperation system is applied to a network architecture, the network architecture comprises a center end and a plurality of node ends respectively connected to the center end, wherein the node ends are used for providing services, and the cross-node service cooperation system comprises:

a setting database for storing setting data;

the monitoring database is used for storing monitoring data;

a node management module, configured to set the service type, the attribution unit, and a service ID of the service provided by the node, where the service ID is used to identify the service type and the attribution unit of the service provided by the node, and store the service type, the attribution unit, and the service ID of the node as the setting data in the setting database;

a collaboration service management module, configured to set a collaboration service execution flow template, and generate a corresponding template ID and a step ID, where the template ID is an identification number of the collaboration service execution flow template, the step ID refers to an execution step in the collaboration service execution flow template, includes the service type executed by the execution step and an execution sequence thereof, and stores the collaboration service execution flow template, the template ID, and the step ID as the setting data in the setting database;

a collaboration service execution module for receiving an execution request of a collaboration service, assigning a collaboration ID to the collaboration service, and the template ID for executing the cooperation service is queried from the provisioning repository, and according to each step ID contained in the template ID, the central terminal sequentially sends the cooperative service to each node terminal to execute processing, wherein the cooperative service execution module analyzes the service type executed by the step ID to be executed currently and analyzes the attribution unit corresponding to the cooperative service, to query the service ID responsible for executing the step ID from the configuration database, and the central terminal is enabled to send the cooperation service to the node terminal corresponding to the service ID to execute processing, the node end and the center end cooperate with each other to complete the execution request of the cooperation service; and

and the cooperative service monitoring module is used for recording data information generated by the cooperative service execution module in the execution process of the cooperative service according to the execution result of the cooperative service fed back by each node end, wherein the data information comprises the cooperative ID of the cooperative service, the template ID called in the execution process of the cooperative service, the step ID and the service ID, and the data information is used as the monitoring information to be stored in the monitoring database.

2. The cross-node service collaboration system of claim 1, wherein the collaboration service monitoring module further analyzes whether an actual execution processing sequence of the collaboration service execution module for the collaboration service matches with the collaboration service execution flow template stored in the setting database, and outputs a prompt message indicating that the execution sequence does not match when the analysis result is that the execution processing sequence does not match.

3. The cross-node service collaboration system of claim 1, wherein the collaboration service management module further provides a preset execution time limit corresponding to the step ID, and stores the preset execution time limit in the setting database.

4. The system according to claim 3, wherein the collaboration service monitoring module further records an actual execution time of each step ID of the collaboration service executed by the collaboration service execution module, determines whether the actual execution time matches the preset execution time limit stored in the setting database, and outputs a prompt message indicating that the execution time is out when the actual execution time exceeds the preset execution time limit.

5. The cross-node service collaboration system of claim 3, wherein the central end and the node end are communicatively connected with each other through a middleware system, and the central end and the node end are communicatively connected by using a message queue asynchronous mechanism or a message queue synchronous mechanism.

6. The cross-node business collaboration system of claim 1, wherein the system further comprises:

the access management module is used for respectively providing authorization processing for the central terminal and the node terminal so as to generate corresponding authorization information and storing the authorization information into the setting database; and

and the identity verification module is used for receiving the access requests of the central end and the node end, verifying the identities of the central end and the node end according to the authorization information stored in the setting database, and providing the central end and the node end to access the cross-node service collaboration system to execute the collaboration service after the verification is passed.

7. A cross-node service cooperation method is applied to a network architecture, the network architecture comprises a center end and a plurality of node ends respectively connected to the center end, wherein the node ends are used for providing services, and the cross-node service cooperation method comprises the following steps:

establishing a setting database for setting and storing a template ID and a step ID corresponding to a cooperative business execution flow template, and a service type, an attribution unit and a service ID of the service provided by the node side, wherein the template ID is an identification number of the cooperative business execution flow template, and the step ID refers to an execution step in the cooperative business execution flow template and comprises the service type executed by the execution step and an execution sequence thereof; the service ID is used for identifying the service type and the home unit of the service provided by the node side;

receiving an execution request of a cooperative service, allocating a cooperative ID to the cooperative service, querying a template ID for executing the cooperative service from the setting database, analyzing the service type executed by the step ID to be executed currently and analyzing the attribution unit corresponding to the cooperative service according to the step ID contained in the template ID, so as to query the service ID responsible for executing the step ID from the setting database, and enabling the central terminal to send the cooperative service to the node terminal corresponding to the service ID for execution, so as to complete the execution request of the cooperative service through mutual cooperation of the node terminal and the central terminal;

and recording data information generated in the execution process of the cooperative business according to the execution result of the cooperative business fed back by each node end, wherein the data information comprises a cooperative ID of the cooperative business, the template ID called by the execution of the cooperative business, the step ID and the service ID, and the data information is stored into a monitoring data bank as monitoring information.

8. The cross-node business collaboration method of claim 7, wherein the method further comprises:

analyzing whether the executed step IDs of the cooperative business and the processing sequence of each step ID are matched with the cooperative business execution flow template stored in the set database or not, and outputting prompt information of unmatched execution sequence when the analysis result is unmatched.

9. The cross-node business collaboration method of claim 7, wherein the method further comprises:

setting a preset execution time limit corresponding to the step ID, and storing the preset execution time limit into a set database; and

recording the actual execution time of each step ID of the cooperative service, judging whether the actual execution time exceeds the preset execution time limit stored in the set database, and outputting prompt information of execution overtime when the actual execution time exceeds the preset execution time limit.

10. The cross-node business collaboration method of claim 7, wherein the method further comprises:

executing authorization processing aiming at the center end and the node end to generate corresponding authorization information, and storing the authorization information into the setting database; and

and when receiving the access request of the central terminal and/or the node terminal, verifying the identity of the central terminal and/or the node terminal according to the authorization information stored in the setting database, and after the verification is passed, providing the access of the central terminal and/or the node terminal to execute the cooperative service.

Images