An e-government business cooperation method and system

Abstract

The application discloses an e-government service cooperation method and system, the service cooperation method comprises the following steps: establishing a cooperation capability rule, registering a service capability to an e-government service cooperation system, calling a capability application and docking, configuring a cooperation route and cooperation distribution according to a government service matter dimension. The e-government service cooperation method and system can realize cross-network cooperation by reducing the docking work between various service systems, realize real-time cooperation distribution to various service systems, realize online and offline handling of matters and applications, realize cross-domain and cross-department handling of government services through cooperation between service systems of different departments, and realize full-process and full-life-cycle docking of systems and various government service systems, so that service supply is more diversified, service operation is more efficient, and service acquisition is more economical, thereby simplifying the docking process between various e-government service systems and reducing the docking difficulty.

Description

Technical Field

[0001] This invention relates to the field of e-government technology, specifically to an e-government business collaboration method and system. Background Technology

[0002] In the current process of standardizing, regulating, and facilitating government services, government service centers need to set up comprehensive service windows and gradually integrate the service windows set up separately by industry departments. Following the model of "comprehensive acceptance at the front desk, classified approval at the back office, and issuance of documents through the comprehensive window," the goal is to achieve "one-window acceptance and comprehensive service." To avoid staff at the comprehensive service windows operating multiple traditional e-government service systems, government service centers are gradually starting to build a unified comprehensive acceptance system.

[0003] However, the processing and approval of government services are still carried out in the business systems of various industry departments. This requires the comprehensive acceptance system to be technically connected with the processing systems of all industry departments one by one. With each additional comprehensive acceptance system or processing system, all relevant parties in the system need to carry out their own system modifications and mutual connections again, which is time-consuming and labor-intensive.

[0004] Furthermore, the network environments in which the various systems operate differ, including e-government intranets, e-government extranets, and the Internet. Some systems even operate in multiple network environments, making cross-network system integration difficult and complex. These two issues have already created obstacles to the reform of integrated government services. Summary of the Invention

[0005] (a) Technical problems to be solved

[0006] To address the aforementioned shortcomings of existing technologies, this invention provides an e-government business collaboration method and system. The business collaboration method includes establishing collaboration capability rules, integrating business capabilities into the e-government business collaboration system, requesting and connecting to capability calls, configuring collaboration routes and distributing collaboration based on the dimensions of government service items. The e-government business collaboration method and system proposed in this invention reduces the work required for connecting various business systems, achieving cross-network collaboration and real-time collaborative distribution to various business systems. This enables online and offline processing of items and applications. Furthermore, through collaboration between business systems belonging to different departments, it achieves cross-domain and cross-departmental access to government services, as well as full-process and full-lifecycle integration of the system and various government service business systems. This makes service supply more diverse, service operation more efficient, and service acquisition more economical, thereby simplifying the connection process between various e-government business systems and reducing the difficulty of connection. It solves the problem of high difficulty and complexity in system connection across network environments.

[0007] (II) Technical Solution

[0008] To achieve the above objectives, the present invention provides the following technical solution:

[0009] A method for collaborative e-government services includes the following steps:

[0010] Step S1: Establish collaborative capability rules, classify e-government business systems into three categories according to business type: receiving system, acceptance system, and processing system, and define the onboarding capabilities required for each of the three categories of systems to work collaboratively;

[0011] Step S2: Integrate business capabilities into the e-government business collaboration system. Developers of the three types of systems integrate capabilities according to the collaboration capability rules. When integrating each capability, enter the original official address, the original test address, configure which one or more collaboration capability rules it belongs to, which government service items it is applicable to, and the network environment in which it operates.

[0012] Step S3: Capability application and integration. The developer of the business system applies for the capabilities that other business system developers have already implemented and integrates them with their own system.

[0013] Step S4: Configure collaborative routes according to the dimension of government service items. Collaborative routes are the systems that carry out the three stages of receiving, accepting and processing a government service item. Multiple collaborative routes can be configured for a government service item, but only one route can be active at a time.

[0014] Step S5: Collaborative distribution. When a government service application task is generated, the government service recipient selects the government service item to be processed from the application receiving system, enters the business data, and the government service application business data is collaboratively distributed through the application receiving system, the acceptance system, or the processing system.

[0015] Furthermore, in step S1, the onboarding capability includes an interface and pages adapted to different terminal forms;

[0016] The onboarding capabilities of the document receiving system include the onboarding application page, the interface for receiving acceptance results, the interface for receiving processing results, and the interface for receiving processing progress.

[0017] The system's onboarding capabilities include an application receiving interface, an application result details query page, and an interface for receiving and forwarding processing results.

[0018] The system's onboarding capabilities include an interface for receiving application submissions, an interface for pushing processing results, and a page for querying processing result details.

[0019] Furthermore, the collaborative capability rules also define the calling relationships between various capabilities;

[0020] The application receiving system provides an interface for receiving documents; the document processing system provides an interface for receiving documents.

[0021] The collaborative capability rules also define a unified interface structure and unified HTTP message header parameter names for the three types of systems to connect with e-government business collaborative systems.

[0022] The aforementioned e-government business collaboration methods and collaboration capability rules also define three types of system collaboration and integration modes, which are divided into the following two:

[0023] One-way collaboration mode: The applicant of the interface calls the unified push interface of the e-government business collaboration system to push business information data to each access business system, and the access business system receives the data through the interface that has been registered.

[0024] Two-way collaboration mode: The applicant of the interface calls the unified push interface of the e-government business collaboration system to push business information data to various access business systems. At the same time, the applicant of the interface must be registered with the interface and connect to the data feedback interface from the application interface. When the application interface feeds back data to the applicant, the e-government business collaboration system calls the data feedback interface registered by the applicant.

[0025] Furthermore, in step S3, the application and connection of capabilities are carried out in the following manner:

[0026] Step S31: The applicant's application capabilities are related to the capabilities of their own system. Specifically, the application receiving system is connected to the application processing system; the application processing system is connected to both the application receiving system and the processing system; and the application processing system is connected to the application processing system.

[0027] Step S32: After the application for connection is approved, the address of all the capabilities of the applied system after passing through the network proxy of the e-government business collaboration system is issued to the applicant according to the network environment of the applicant's system. This enables each business system to connect with business systems in other network environments in its own network environment.

[0028] Step S33: After obtaining the authorized capability address, the applicant shall complete the development and debugging of its own business system to connect with it. If the collaborative capability rule defines the collaborative connection mode of the authorized capability as a two-way collaborative mode, the applicant shall also configure the interface for receiving data feedback in its own system.

[0029] Step S34: One of the applicant's business systems can simultaneously connect with multiple business systems.

[0030] Preferably, in step S4, one receiving system, one acceptance system, and one or more processing systems are configured in one route; when there are multiple processing systems, it is necessary to specify which list item each processing system handles, and define the serial, parallel, or integrated relationship between the processing systems.

[0031] In step S5, the data of government service application is distributed bidirectionally between the receiving system and the acceptance system, or between the acceptance system and the processing system. During collaborative distribution, the source system calls the capability address of the network proxy of the e-government business collaboration system and transmits the unified item code, application serial number and business data according to the unified HTTP message header definition.

[0032] An e-government business collaboration system is provided to implement the above-mentioned e-government business collaboration method. The e-government business collaboration system is divided into functional modules, including a collaboration capability rule configuration module, a capability entry module, a collaboration connection module, a routing configuration module, a collaboration gateway module, a capability monitoring module, a collaboration monitoring module, and a government service item change monitoring and notification module.

[0033] The e-government business collaboration method also includes the following steps:

[0034] Step S6: Conduct a routine inspection of all onboarded capabilities at a specified time using the capability monitoring module;

[0035] Step S7: Record the capability call information between all business source systems and business target systems through the collaborative monitoring module, and form a collaborative log;

[0036] Step S8: Monitor whether government service items have been abolished or added through the government service item change monitoring and notification module.

[0037] Furthermore, in the aforementioned e-government business collaboration system, the collaboration capability rule configuration module is used to configure the capability purpose, capability form, collaboration call relationship, collaboration mode, and whether the document receiving system, acceptance system, and processing system must be registered.

[0038] The capability entry module is used for system entry, including entering basic system information, system type, and network environment in which the system operates. The e-government business collaboration system issues a docking key to the system entering the system.

[0039] The collaborative docking module includes a display of connectable system sets. The applicant selects its own system type, and the collaborative docking module filters out the systems that can be docked with the applicant from the business systems that have been registered in the e-government business collaboration system. The applicant selects one or more systems to initiate a docking application. After the docking application is submitted, it is reviewed by the respondent. The application information displays the applicant's business system information. After the docking application is approved, the respondent grants the applicant all the registration capabilities of the respondent system according to the applicant's system operating network environment.

[0040] The routing configuration module is based on the list of government service items. Each government service item can be configured with multiple collaborative routes, but only one route can be active at a time.

[0041] The collaborative gateway module includes an Nginx load balancing cluster, which is deployed in both the government internet zone and the e-government extranet zone. The two clusters are configured for bidirectional cross-network access, which is used for cross-network calls of onboarding capabilities and bidirectional proxy for mutual access between modules of the e-government business collaboration system deployed in the government internet zone and the e-government extranet zone.

[0042] The capability monitoring module includes a capability inspection plan configuration, which configures the inspection of all onboard capabilities at a specified time, including by hour, day, week or month, and the number of inspections within the time period.

[0043] The collaborative monitoring module records the capability call information between all business source systems and business target systems, and forms a collaborative log. Based on the case serial number, the collaborative log is summarized to monitor the progress of case tasks in the collaborative routing.

[0044] The government service item change monitoring and notification module monitors whether government service items are abolished or added. When a government service item with configured routes is abolished, a notification is sent to the user who configured the routes under the government service item and the developer of the business system that carries each route and node, indicating that the government service item has been abolished and the route has become invalid. When a new government service item is added, the government service management department is notified to configure routes for the new government service item.

[0045] Furthermore, when the capability entry module is used to enter capabilities into the system, it retrieves the collaborative capability rules of the system based on whether the business system is a receiving system, acceptance system, or processing system. The developer of the business system then enters the capabilities of its own system according to the collaborative capability rules. If the interface capability has interface documentation, the developer of the business system can also upload the documentation; if the interface capability has a testing channel, testing samples can also be entered.

[0046] During collaborative integration, if the requested capability uploaded its interface documentation during onboarding, the applicant can still download it. If the collaborative capability rules define the collaborative integration mode of the authorized capability as a two-way collaborative mode, the applicant must also configure its own system's interface for receiving data feedback.

[0047] When the collaborative monitoring module records information, completed, in progress, not yet arrived, and no need to pass through routing nodes are marked with different colors. The call status of capabilities can also be viewed in each routing node.

[0048] Furthermore, the collaborative gateway module can perform collaborative authentication, receive call requests from business source systems, verify the business source system's interface key, and perform collaborative target addressing. It receives call requests from business source systems, searches for the corresponding route in the routing configuration module according to the unified encoding of the items passed in the call request, searches for the original address of the collaborative target system in the route, and performs collaborative distribution. The collaborative gateway module then calls the original address of the collaborative target system and transmits business data.

[0049] The capability monitoring module performs capability inspections according to the configuration of the capability inspection plan. Interface capabilities are called according to the test samples entered when the capability is added, and page capabilities are accessed according to the page addresses entered when the capability is added, and the inspection results are returned.

[0050] After the inspection, the capability monitoring module also generates an inspection report, and outputs inspection reports according to the user dimension of the e-government business collaboration system. It outputs inspection reports on the capabilities of the business system developers and inspection reports on the capabilities within the management authority of the e-government business collaboration system operation and maintenance users or government service management department users.

[0051] (III) Beneficial Effects

[0052] This invention provides a method and system for collaborative e-government operations. Compared with existing technologies, it has the following advantages:

[0053] (1) The e-government business collaboration method and system, through the technical methods and systems provided by the present invention, can reduce the docking work between various business systems, realize cross-network collaboration, receive and process business information of various systems, and distribute it to various business systems in real time, so as to realize online and offline processing of matters and applications.

[0054] (2) The e-government business collaboration method and system can realize cross-regional and cross-departmental government services through the collaboration between business systems of different departments, and solve the reform needs of "one-window acceptance and one-network processing" of the integrated government service platform.

[0055] (3) This e-government business collaboration method and system, through the full-process and full-lifecycle integration and docking of the system provided by this invention with various e-government service business systems, makes service supply more diversified, service operation more efficient, and service acquisition more economical, simplifies the docking process between various e-government business systems, and reduces docking difficulty. It solves the problem of high difficulty and complexity in system docking across network environments. Attached Figure Description

[0056] Figure 1 This is a flowchart illustrating the e-government business collaboration method proposed in this invention;

[0057] Figure 2 This is a schematic diagram of the call capability application and connection rule process proposed in this invention;

[0058] Figure 3 This is a structural block diagram of the e-government business collaboration system proposed in this invention. Detailed Implementation

[0059] The technical solutions in the embodiments of the present invention have been clearly and completely described. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0060] Please see Figure 1 This invention provides a technical solution: an e-government business collaboration method, specifically including the following steps:

[0061] Step S1: Establish collaborative capability rules, classify e-government business systems according to business type into: receiving system, acceptance system, and processing system, and define the onboarding capabilities required for each of the three types of systems to work collaboratively.

[0062] The onboarding capabilities include interfaces and pages adapted to different terminal formats;

[0063] Among them: the onboarding capabilities of the receiving system include the onboarding application page, the acceptance result receiving interface, the processing result receiving interface, and the processing progress receiving interface, etc.

[0064] The system's onboarding capabilities include an application receiving interface, an application result details query page, and an interface for receiving and forwarding processing results.

[0065] The system's onboarding capabilities include an interface for receiving application submissions, an interface for pushing processing results, and a page for querying processing result details.

[0066] The collaborative capability rules also define the calling relationships between various capabilities.

[0067] The application receiving interface provided by the acceptance system is for the receiving system to call; the application processing receiving interface provided by the processing system is for the acceptance system to call.

[0068] The collaborative capability rules also define a unified interface structure and unified HTTP message header parameter names for three types of systems to connect with e-government business collaborative systems;

[0069] Furthermore, the collaborative capability rules also define three types of system collaborative interface modes, which are divided into the following two:

[0070] One-way collaboration mode: The applicant of the interface calls the unified push interface of the e-government business collaboration system to push business information data to each access business system, and the access business system receives the data through the interface that has been registered.

[0071] Two-way collaboration mode: The applicant of the interface calls the unified push interface of the e-government business collaboration system to push business information data to each access business system. At the same time, the applicant of the interface must be registered with the interface and connect to the data feedback interface from the application interface. When the application interface feeds back data to the applicant, the e-government business collaboration system calls the data feedback interface registered by the applicant.

[0072] Step S2: Integrate business capabilities into the e-government business collaboration system. Developers of the three types of systems shall integrate capabilities according to the collaboration capability rules. When integrating each capability, the original official address, the original test address, the configuration of which one or more collaboration capability rules it belongs to, the applicable government service items, and the network environment in which it operates, etc.

[0073] Step S3: Capability Application and Integration. The developer of the business system applies for capabilities already registered with other business system developers to integrate with their own system. The capability application and integration process is as follows: Figure 2 As shown.

[0074] Step S31: The applicant's application capabilities are related to the capabilities of their own system. Specifically, the application receiving system is connected to the application processing system; the application processing system is connected to both the application receiving system and the processing system; and the application processing system is connected to the application processing system.

[0075] Step S32: After the application for connection is approved, the address of all the capabilities of the applied system after passing through the network proxy of the e-government business collaboration system is issued to the applicant according to the network environment of the applicant's system. This enables each business system to connect with business systems in other network environments in its own network environment.

[0076] For example, if the applicant system defines itself as running on the e-government extranet when it joins the system, and the requested capability runs on the Internet, then the e-government business collaboration system authorizes the applicant system with the capability address of the requested capability under the e-government extranet environment after being proxied by the network.

[0077] Step S33: After obtaining the authorized capability address, the applicant shall complete the development and debugging of its own business system to connect with it. If the collaborative capability rule defines the collaborative connection mode of the authorized capability as a two-way collaborative mode, the applicant shall also configure the interface for receiving data feedback in its own system.

[0078] Step S34: One of the applicant's business systems can simultaneously connect with multiple business systems;

[0079] Step S4: Configure collaborative routes according to the dimension of government service items. Collaborative routes refer to the systems involved in the three stages of receiving, accepting, and processing a government service item. Multiple collaborative routes can be configured for a government service item, but only one route can be active at a time. Each route is configured with one receiving system, one accepting system, and one or more processing systems. When there are multiple processing systems, it is necessary to specify which list item each processing system handles and define the serial, parallel, or integrated relationships between the processing systems.

[0080] Step S5: Collaborative distribution. When a government service application task is generated, the government service recipient selects the government service item to be processed from the application receiving system, enters the business data, and the government service application business data is collaboratively distributed through the application receiving system, the acceptance system, or the processing system.

[0081] Specifically, government service application data is distributed bidirectionally between the receiving system and the acceptance system, or between the acceptance system and the processing system. During collaborative distribution, the source system calls the capability address proxied by the e-government business collaboration system network proxy, and transmits the unified item code, application serial number, and business data according to the unified HTTP message header definition.

[0082] Furthermore, it also includes the following steps:

[0083] Step S6: Conduct a routine inspection of all onboarded capabilities at a specified time using the capability monitoring module;

[0084] Step S7: Then, the collaborative monitoring module records the capability call information between all business source systems and business target systems, and forms a collaborative log;

[0085] Step S8: Finally, monitor whether any government service items have been abolished or added through the government service item change monitoring and notification module.

[0086] The e-government business collaboration system uses the item code to query the effective collaboration route of the government service item, finds the collaboration target system defined by the collaboration route, and then calls the original address of the target system according to the calling relationship defined by the collaboration capability rules to transfer business data.

[0087] This invention also provides a technical solution: an e-government business collaboration system, which is divided into functional modules, such as... Figure 3 As shown, it includes a collaborative capability rule configuration module, a capability entry module, a collaborative connection module, a routing configuration module, a collaborative gateway module, a capability monitoring module, a collaborative monitoring module, and a government service item change monitoring and notification module.

[0088] The collaborative capability rule configuration module is used to configure the capability purpose, capability form, collaborative call relationship, collaborative mode, and whether onboarding is mandatory for each system. The systems referred to are the receiving system, acceptance system, and processing system mentioned earlier.

[0089] The capability entry module is used for system entry, including entering basic system information, system type (receiving / accepting / processing), and the network environment in which the system operates. The e-government business collaboration system issues a docking key to the system entering the system.

[0090] For capability onboarding, the collaborative capability rules for that type of business system (receiving system, acceptance system, or processing system) are retrieved based on the system's classification. The business system's developer then enters the capabilities of their system according to these collaborative capability rules. If the interface capability has interface documentation, the business system's developer can also upload the documentation; if the interface capability has a testing channel, testing samples can also be entered.

[0091] The collaborative docking module includes a display of connectable system sets. The applicant selects its own system type, and the collaborative docking module filters out systems that can dock with the applicant from the business systems already registered in the e-government business collaboration system. The applicant selects one or more systems to initiate a docking application. After the docking application is submitted, it is reviewed by the respondent. The application information displays the applicant's business system information. After the docking application is approved, the system issues all the registered capabilities of the requested system to the applicant based on the applicant's system's operating network environment. The address is after passing through the network proxy of the e-government business collaboration system. If the requested capability uploaded interface documents during registration, the applicant can also download them. If the collaborative capability rules define the collaborative docking mode of the authorized capability as a two-way collaborative mode, the applicant must also configure its own system's interface for receiving data feedback.

[0092] The routing configuration module is based on the list of government service items. Each government service item can be configured with multiple collaborative routes, but only one route can be active at a time. A route can be configured in the form of a topology graph, including one receiving system, one acceptance system, and one or more processing systems. When there are multiple processing systems, it is necessary to specify which list item each processing system handles and define the serial, parallel, or integrated relationships between the processing systems.

[0093] For example, when a government service recipient applies for the "one-stop service for opening a restaurant," the routing system should be configured as follows: "Individual business registration (filing)" and "employee health certificate (food) processing" are linked in parallel, and then linked in series with "food service license processing," with the processing systems of the market supervision department, health administration department, and market supervision department respectively handling the processing.

[0094] The collaborative gateway module includes an Nginx load balancing cluster, which is deployed in both the government internet zone and the e-government extranet zone. The two clusters are configured for bidirectional cross-network access, which is used for cross-network calls of onboarding capabilities and bidirectional proxy for mutual access between modules of the e-government business collaboration system deployed in the government internet zone and the e-government extranet zone.

[0095] The collaborative gateway module can perform collaborative authentication, receive call requests from business source systems, verify the business source system's interface key, and perform collaborative target addressing. It receives call requests from business source systems, finds the corresponding route in the routing configuration module according to the unified encoding of the items passed in the call request, finds the original address of the collaborative target system in the route, and performs collaborative distribution. The collaborative gateway module then calls the original address of the collaborative target system to transmit business data.

[0096] The capability monitoring module includes a capability inspection plan configuration, which configures the inspection of all onboard capabilities at a specified time, including by hour, day, week or month, as well as the number of inspections within the time period.

[0097] The capability monitoring module performs capability inspections according to the configured capability inspection plan. For interface capabilities, it calls the interface capabilities based on the test samples entered during capability registration; for page capabilities, it accesses the page capabilities based on the page addresses entered during capability registration, and returns the inspection results.

[0098] After the inspection, the capability monitoring module also generates an inspection report, and outputs the inspection report according to the user dimension of the e-government business collaboration system. It outputs an inspection report on the capabilities of the business system developers, and an inspection report on the capabilities within the management authority of the e-government business collaboration system operation and maintenance users or government service management department users.

[0099] The collaborative monitoring module records capability call information between all source and target systems and generates a collaborative log. Based on the task serial number, the collaborative log is aggregated to monitor the progress of tasks within the collaborative routing. Completed, in progress, not yet arrived, and unnecessary routing nodes are marked with different colors. The capability call status can also be viewed within each routing node.

[0100] The government service item change monitoring and notification module monitors whether government service items are abolished or added. When a government service item with configured routes is abolished, a notification is sent to the user who configured the routes under the government service item and the developer of the business system that carries each route and node, indicating that the government service item has been abolished and the route has become invalid. When a new government service item is added, the government service management department is notified to configure routes for the new government service item.

[0101] Furthermore, any content not described in detail in this specification is existing technology known to those skilled in the art.

[0102] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0103] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for collaborative e-government services, characterized in that, Includes the following steps: Step S1: Establish collaborative capability rules, classify e-government business systems into three categories according to business type: receiving system, acceptance system, and processing system, and define the onboarding capabilities required for each of the three categories of systems to work collaboratively; Step S2: Integrate business capabilities into the e-government business collaboration system. Developers of the three types of systems integrate capabilities according to the collaboration capability rules. When integrating each capability, enter the original official address, the original test address, configure which one or more collaboration capability rules it belongs to, which government service items it is applicable to, and the network environment in which it operates. Step S3: Capability application and integration. The developer of the business system applies for the capabilities that other business system developers have already implemented and integrates them with their own system. Step S4: Configure collaborative routes according to the dimension of government service items. Collaborative routes are the systems that carry out the three stages of receiving, accepting and processing a government service item. Multiple collaborative routes can be configured for a government service item, but only one route can be active at a time. Step S5: Collaborative distribution. When a government service application task is generated, the government service recipient selects the government service item to be processed from the document receiving system, enters the business data, and the government service application business data is collaboratively distributed through the document receiving system, the acceptance system, or the processing system. In step S3, the application and connection of capabilities are carried out in the following manner: Step S31: The applicant's application capabilities are related to the capabilities of their own system. Specifically, the application receiving system is connected to the application processing system; the application processing system is connected to both the application receiving system and the processing system; and the application processing system is connected to the application processing system. Step S32: After the application for connection is approved, the address of all the capabilities of the applied system after passing through the network proxy of the e-government business collaboration system is issued to the applicant according to the network environment of the applicant's system. This enables each business system to connect with business systems in other network environments in its own network environment. Step S33: After obtaining the authorized capability address, the applicant shall complete the development and debugging of its own business system to connect with it. If the collaborative capability rule defines the collaborative connection mode of the authorized capability as a two-way collaborative mode, the applicant shall also configure the interface for receiving data feedback in its own system. Step S34: One of the applicant's business systems can simultaneously connect with multiple business systems; In step S4, one receiving system, one acceptance system, and one or more processing systems are configured in one route; when there are multiple processing systems, it is necessary to specify which list item each processing system handles, and define the serial, parallel, or integrated relationship between the processing systems. In step S5, the data of government service application is distributed bidirectionally between the receiving system and the acceptance system, or between the acceptance system and the processing system. During collaborative distribution, the source system calls the capability address of the network proxy of the e-government business collaboration system and transmits the unified item code, application serial number and business data according to the unified HTTP message header definition.

2. The e-government business collaboration method according to claim 1, characterized in that, In step S1, the onboarding capability includes an interface and pages adapted to different terminal forms; The onboarding capabilities of the document receiving system include the onboarding application page, the interface for receiving acceptance results, the interface for receiving processing results, and the interface for receiving processing progress. The system's onboarding capabilities include an application receiving interface, an application result details query page, and an interface for receiving and forwarding processing results. The system's onboarding capabilities include an interface for receiving application submissions, an interface for pushing processing results, and a page for querying processing result details.

3. The e-government business collaboration method according to claim 2, characterized in that, The collaborative capability rules also define the calling relationships between various capabilities; The application receiving system provides an interface for receiving documents; the document processing system provides an interface for receiving documents. The collaborative capability rules also define a unified interface structure and unified HTTP message header parameter names for the three types of systems to connect with e-government business collaborative systems.

4. The e-government business collaboration method according to claim 3, characterized in that, The collaborative capability rules also define three types of system collaboration and integration modes, which are divided into the following two: One-way collaboration mode: The applicant of the interface calls the unified push interface of the e-government business collaboration system to push business information data to each access business system, and the access business system receives the data through the interface that has been registered. Two-way collaboration mode: The applicant of the interface calls the unified push interface of the e-government business collaboration system to push business information data to various access business systems. At the same time, the applicant of the interface must be registered with the interface and connect to the data feedback interface from the application interface. When the application interface feeds back data to the applicant, the e-government business collaboration system calls the data feedback interface registered by the applicant.

5. An e-government business collaboration system, used to implement the e-government business collaboration method according to any one of claims 1 to 4, characterized in that, The e-government business collaboration system is divided into functional modules, including a collaboration capability rule configuration module, capability entry module, collaboration connection module, routing configuration module, collaboration gateway module, capability monitoring module, collaboration monitoring module, and government service item change monitoring and notification module. The e-government business collaboration method also includes the following steps: Step S6: Conduct a routine inspection of all onboarded capabilities at a specified time using the capability monitoring module; Step S7: Record the capability call information between all business source systems and business target systems through the collaborative monitoring module, and form a collaborative log; Step S8: Monitor whether government service items have been abolished or added through the government service item change monitoring and notification module.

6. The e-government business collaboration system according to claim 5, characterized in that: The collaborative capability rule configuration module is used to configure the capability purpose, capability form, collaborative call relationship, collaborative mode, and whether onboarding is required for the receiving system, acceptance system, and processing system. The capability entry module is used for system entry, including entering basic system information, system type, and network environment in which the system operates. The e-government business collaboration system issues a docking key to the system entering the system. The collaborative docking module includes a display of connectable system sets. The applicant selects its own system type, and the collaborative docking module filters out the systems that can be docked with the applicant from the business systems that have been registered in the e-government business collaboration system. The applicant selects one or more systems to initiate a docking application. After the docking application is submitted, it is reviewed by the respondent. The application information displays the applicant's business system information. After the docking application is approved, the respondent grants the applicant all the registration capabilities of the respondent system according to the applicant's system operating network environment. The routing configuration module is based on the list of government service items. Each government service item can be configured with multiple collaborative routes, but only one route can be active at a time. The collaborative gateway module includes an Nginx load balancing cluster, which is deployed in both the government internet zone and the e-government extranet zone. The two clusters are configured for bidirectional cross-network access, which is used for cross-network calls of onboarding capabilities and bidirectional proxy for mutual access between modules of the e-government business collaboration system deployed in the government internet zone and the e-government extranet zone. The capability monitoring module includes a capability inspection plan configuration, which configures the inspection of all onboard capabilities at a specified time, including by hour, day, week or month, and the number of inspections within the time period. The collaborative monitoring module records the capability call information between all business source systems and business target systems, and forms a collaborative log. Based on the case serial number, the collaborative log is summarized to monitor the progress of case tasks in the collaborative routing. The government service item change monitoring and notification module monitors whether government service items are abolished or added. When a government service item with configured routes is abolished, a notification is sent to the user who configured the routes under the government service item and the developer of the business system that carries each route and node, indicating that the government service item has been abolished and the route has become invalid. When a new government service item is added, the government service management department is notified to configure routes for the new government service item.

7. The e-government business collaboration system according to claim 6, characterized in that: When the capability entry module is used to enter capabilities into the system, it retrieves the collaborative capability rules of the system based on whether the business system is a receiving system, acceptance system, or processing system. The developer of the business system then enters the capabilities of its own system according to the collaborative capability rules. If the interface capability has interface documentation, the developer of the business system can also upload the documentation; if the interface capability has a testing channel, testing samples can also be entered. During collaborative integration, if the requested capability uploaded its interface documentation during onboarding, the applicant can still download it. If the collaborative capability rules define the collaborative integration mode of the authorized capability as a two-way collaborative mode, the applicant must also configure its own system's interface for receiving data feedback. When the collaborative monitoring module records information, completed, in progress, not yet arrived, and no need to pass through routing nodes are marked with different colors. The call status of capabilities can also be viewed in each routing node.

8. The e-government business collaboration system according to claim 6, characterized in that: The collaborative gateway module can perform collaborative authentication, receive call requests from business source systems, verify the business source system interface keys, and perform collaborative target addressing. It receives call requests from business source systems, finds the corresponding route in the routing configuration module according to the unified encoding of the items passed in the call request, finds the original address of the collaborative target system in the route, performs collaborative distribution, and the collaborative gateway module calls the original address of the collaborative target system and transmits business data. The capability monitoring module performs capability inspections according to the configuration of the capability inspection plan. Interface capabilities are called according to the test samples entered when the capability is added, and page capabilities are accessed according to the page addresses entered when the capability is added, and the inspection results are returned. After the inspection, the capability monitoring module also generates an inspection report, and outputs inspection reports according to the user dimension of the e-government business collaboration system. It outputs inspection reports on the capabilities of the business system developers and inspection reports on the capabilities within the management authority of the e-government business collaboration system operation and maintenance users or government service management department users.

Images