A cross-domain handling method and support system based on government affairs collaboration technology

Abstract

The present invention provides a cross-domain one-stop service method and support system based on government affairs business collaboration technology. The cross-domain one-stop service method includes establishing collaborative capability rules, integrating the capabilities of the local business system into the cross-domain one-stop service support system, docking the local business system, configuring collaborative routing according to the dimension of government affairs service matters, opening collaborative routing or service applications according to different depths of the one-stop service, and applying for different local open content according to their own needs by the agency and completing the docking and document distribution. The cross-domain one-stop service method and support system provided by the present invention can realize the cross-domain and cross-departmental one-stop service of government affairs services based on the collaboration between the existing business system systems of different regions and departments, and can provide different docking methods and docking contents according to different depths of cross-domain one-stop service, providing more diverse choices for the agency, while lowering the construction cost and reducing the cost of familiarizing the agency’s comprehensive window personnel with and using multiple acceptance systems.

Description

Technical Field

[0001] The present invention relates to the field of e-government technology, and in particular to a cross-domain processing method and supporting system based on government business collaboration technology. Background Art

[0002] In the current process of standardizing, regularizing, and facilitating government service reforms, government service centers are required to establish "cross-provincial" and "intra-provincial" service windows to provide remote services to businesses and the public. Since government service systems, especially window acceptance systems, are typically built separately and regionally, and the systems used vary significantly, the difficulty of cross-regional service lies in leveraging established local government service systems to conveniently provide services to other regions.

[0003] Currently, the National Integrated Government Service Platform provides a unified, standardized cross-provincial support system, which, together with the provincial government service platform's cross-provincial support system, forms the National Integrated Government Service Platform's cross-provincial support system. However, this solution requires a significant reorganization of existing transaction data and the redevelopment of multiple systems, including the aforementioned national and provincial government service platform cross-provincial support systems, as well as data aggregation, transfer, and distribution systems. This represents a significant development effort and is unable to support cross-domain services between different cities and counties within a province.

[0004] To this end, patent documents with application numbers CN202010847177.0, CN202110814272.5 and CN201911054535.6 all disclose plans to build a unified one-stop system and allow the agency to use the one-stop system to register and accept business. However, the economic cost of building a unified one-stop system and the communication costs of various regions and departments are huge. It also increases the burden of familiarizing the agency’s comprehensive window personnel with different systems. It is also inconvenient for the agency’s government service management department to summarize and count the local processing and pending business volume.

[0005] For example, the patent document with application number CN202111318721.3 proposes a method of embedding the receiving page of the local comprehensive acceptance system into the comprehensive acceptance system of the agency, and connecting the user systems of the local and agency comprehensive acceptance systems to achieve cross-provincial and intra-provincial cross-domain handling modes. However, this solution is only applicable to the case where the front-ends of the local and agency comprehensive acceptance systems are developed using the same language; otherwise, they cannot be nested, and the solution does not provide specific instructions for the docking of the user system. In actual use, since the user systems of the local and agency comprehensive acceptance systems are also built in isolation, many problems may be encountered in the process of docking the user systems. Summary of the Invention

[0006] The purpose of the present invention is to provide a cross-domain handling method and support system based on government business collaboration technology, so as to form a feasible method that can be widely applied to cross-provincial, intra-provincial and other cross-domain handling modes, relying on the government service system already established in the local and agency places, to reduce the construction cost of the cross-domain handling system and conveniently provide services to other regions.

[0007] The purpose of the present invention is achieved through the following technical solutions:

[0008] In one aspect, the present invention provides a cross-domain processing method based on government affairs collaboration technology, comprising the following steps:

[0009] Step S1. Establish collaborative capability rules, dividing the local and agency e-government systems into two types of business systems based on business type: acceptance system and processing system, and define the capabilities required for the two types of business systems to work together;

[0010] Step S2. The capabilities of the local business system are incorporated into the cross-domain support system. The developer of the local business system incorporates the capabilities according to the collaborative capability rules. When each capability is incorporated, the capability address, interface parameters, configuration of which collaborative capability rule or rules it belongs to, which government services it applies to, and the network environment in which it operates are entered.

[0011] Step S3. The developer of the local business system applies for the ability of other business systems to connect with their own system.

[0012] Step S4. Configure collaborative routing based on the government service item dimension. Collaborative routing is the system that carries the acceptance and processing links required to complete a government service item. Multiple collaborative routings can be configured for a government service item.

[0013] Step S5. Local authorities open collaborative routing or service applications according to different service depths. Service depths are divided into display mode, collection mode, and acceptance mode.

[0014] Step S6. The agency applies for different territorial open content based on its own needs for the depth of the integrated service and completes the connection;

[0015] Step S7. Case distribution: when a government service case task is generated, the case is distributed according to different depths of handling.

[0016] In some possible embodiments, in step S1, the capabilities required for the two types of business systems to work together as defined by the collaboration capability rule include interfaces and pages adapted to different terminal forms;

[0017] At the same time, the collaborative capability rules also define: the calling relationships between the various capabilities of the business system; the unified interface structure and unified HTTP message header parameter names for the business system to connect to the cross-domain support system; and the collaborative docking mode of the business system. The collaborative docking mode is divided into the following two types:

[0018] One-way collaboration mode: The interface applicant calls the unified push interface of the cross-domain support system to push business data to each connected business system, and the connected business system receives the business data through the established interface;

[0019] Two-way collaborative mode: The applicant who calls the interface calls the unified push interface of the cross-domain support system to push business data to each connected business system. At the same time, the applicant of the interface needs to settle in the data feedback interface and connect the data feedback interface from the application interface. When the application interface feeds back data to the applicant, the cross-domain support system calls the data feedback interface settled by the applicant.

[0020] In some possible embodiments, in step S3, the application and connection of capabilities are performed as follows:

[0021] Step S31. The capabilities applied for by the applicant are related to the type of their own system, specifically, whether the application acceptance system is connected to the processing system, or vice versa.

[0022] Step S32. After the docking application is reviewed, the applicant is issued with the address of all the entry capabilities of the applied system after the cross-domain support system network proxy is passed to the applicant according to the network environment in which the applicant's system operates. This enables each business system to dock with business systems in other network environments in its own network environment;

[0023] Step S33. After the applicant obtains the authorized capability address, it independently develops and debugs the connection between its own business system and the capability address. If the collaborative capability rule defines the collaborative connection mode of the authorized capability as a two-way collaborative mode, the applicant also needs to configure a data feedback interface for its own business system.

[0024] Step S34. One business system of the applicant can be connected to multiple business systems at the same time.

[0025] In some possible embodiments, in step S5,

[0026] The proxy display mode is to open the local service application at the local level. The local service application includes the window registration and receipt page and the correction and completion page, and is connected to the collaborative routing. The service data is stored in the local government service platform or system.

[0027] The collection mode is a local open collaborative routing, providing the local acceptance system's application and material receiving interface, acceptance progress query interface, matter service guide query interface, material sharing interface, and material verification interface in the collaborative routing;

[0028] The agency acceptance mode is the local open processing system's processing submission interface, processing progress query interface, matter service guide query interface, material sharing interface, and material verification interface;

[0029] In step S6,

[0030] When the depth of the service is in the agent display mode, the agent applies for the URL of the local service application and mounts the link in its own acceptance system;

[0031] When the depth of the cross-service is the agency collection mode, the agency creates a service application and enters the basic information of the service application, network environment and page URL. The cross-domain cross-service support system issues a docking key to the agency's service application. Based on the created service application, the agency applies for the local acceptance system's application and material receiving interface, acceptance progress query interface, matter service guide query interface, material sharing interface and material verification interface in the collaborative routing, and completes the docking with the receipt page of its own acceptance system;

[0032] When the depth of the cross-domain processing is the agency acceptance mode, the agency will integrate the capabilities of the agency acceptance system into the cross-domain cross-domain processing support system, and at the same time apply for the capabilities of the local processing system and complete the connection with the local processing system. The local area configures the collaborative routing from the agency acceptance system to the local processing system. The agency will complete the connection of the receiving page of its own acceptance system with the collaborative routing from the agency acceptance system to the local processing system according to the method described in the agency collection mode.

[0033] In some possible embodiments, in step S7,

[0034] When the depth of the government service is in the agent display mode, all government service tasks are collaboratively distributed within the local business system;

[0035] When the depth of the integrated service is in the agency collection mode, the collection page developed by the agency will query the service guide information through the service guide query interface of the local acceptance system and display it to the government service recipient. The government service recipient will select the government service item to be handled and enter the business data. According to the collaborative routing configured for the local area, the government service processing tasks will be collaboratively distributed between the local acceptance system and the local processing system defined in the collaborative routing;

[0036] When the depth of the integrated service is in the agency acceptance mode, the receiving page developed by the agency will query the service guide information through the service guide query interface of the local handling system and display it to the government service recipient. The government service recipient will select the government service item to be handled and enter the business data. According to the collaborative routing configured by the locality, the government service processing tasks will be collaboratively distributed between the agency acceptance system and the local handling system defined in the collaborative routing;

[0037] Among them, during collaborative distribution, the source system calls the capability address of the network agent of the cross-domain support system, and transmits the source system ID, unified matter code, collaborative rule code, case serial number and business data according to the definition of the unified HTTP message header.

[0038] In some possible embodiments, in step S4, one acceptance system and one or more processing systems are configured in a collaborative route. When there are multiple processing systems, it is necessary to specify which processing item each processing system handles, and define the series, parallel or integrated relationship between the processing systems.

[0039] On the other hand, the present invention provides a cross-domain inter-service support system based on government affairs and business collaboration technology, which is used to implement the cross-domain inter-service method described above. The cross-domain inter-service support system is divided into functional modules, including:

[0040] The collaborative capability rule configuration module is used to configure the capability usage, capability form, collaborative call relationship, collaborative docking mode, and whether the local business system and the agency business system must be settled;

[0041] The capability registration module is used for business system registration and capability registration. Business system registration includes entering basic system information, system type, and the network environment in which the system operates, and issuing a connection key to the registered system. Capability registration involves calling up the collaborative capability rules for the system type based on whether the business system is an acceptance system or a processing system. The developer of the business system enters the capabilities of their own system according to the collaborative capability rules.

[0042] The collaborative docking module is used to display the system set that can be docked, review the docking application, and issue the address of all the entry capabilities of the applied system to the applicant after the docking application is approved through the cross-domain support system network proxy;

[0043] The collaborative routing configuration module is used to configure collaborative routing based on the dimension of government service items and configure multiple collaborative routes for each government service item;

[0044] The cross-domain docking module is used to display local open content and connect with the agency. The displayed content includes service applications based on the implementation list of government service items, collaborative routing, and various interfaces of local business systems. The agency can apply for different local open content for docking based on its own different needs for the depth of cross-service.

[0045] Collaborative gateway module, used for Nginx load cluster proxy; deploy Nginx load cluster simultaneously in the government Internet zone and the e-government extranet zone, and configure two clusters for bidirectional cross-network configuration, used for reverse proxy cross-network calls of on-site capabilities, and cross-domain one-stop support system, so that modules deployed in the government Internet zone and the e-government extranet zone can access each other.

[0046] In some possible embodiments, when the capability registration module registers the capabilities of a business system, if the interface capability of the business system includes an interface document, the developer of the business system can also upload the document; if the interface capability of the business system includes a dial test channel, the developer can also enter a dial test sample.

[0047] After the collaborative docking application is approved, the applicant can also download the interface document uploaded by the applied system when the capability is registered. If the collaborative docking mode of the authorized capability is defined as bidirectional collaboration by the collaborative capability rule, the applicant also needs to configure a data feedback interface for its own business system to receive feedback data.

[0048] The collaborative gateway module can also perform collaborative authentication, receive call applications from the business source system, and verify the business source system docking key; the collaborative gateway module can also perform collaborative target addressing, receive call applications from the business source system, and search for the collaborative route of the corresponding matter in the collaborative routing configuration module according to the unified matter code passed in the call application, and search for the original address of the collaborative target system in the collaborative route; the collaborative gateway module can also perform collaborative distribution. During collaborative distribution, the source system calls the capability address of the network agent of the cross-domain support system, and passes the source system ID, unified matter code, collaborative rule code, case serial number and business data according to the definition of the unified HTTP message header.

[0049] In some possible embodiments, the cross-domain service support system further includes:

[0050] The capacity monitoring module is used to configure the capacity inspection plan and inspect all the capabilities of the business system according to the capacity inspection plan to obtain the inspection report;

[0051] The collaborative monitoring module is used to record the capability call information between all business source systems and business target systems to form a collaborative log. It also summarizes the collaborative log based on the case serial number and collaboratively monitors the progress of the case task in the collaborative routing.

[0052] The government service item monitoring and notification module is used to monitor whether government service items are abolished or newly added. When a government service item that has been configured with collaborative routing is abolished, a notification is sent to the local user who configured the collaborative routing for the government service item, the developer of the business system that carries each node of each collaborative routing, and the user at the agency, reminding them that the government service item has been abolished and the collaborative routing has become invalid. When a new government service item is added, the user of the government service management department is notified to configure collaborative routing for the new government service item.

[0053] At this point, the cross-domain handling method also includes the following steps:

[0054] Step S8. Perform inspections on all the capabilities of the business system at designated times through the capability monitoring module;

[0055] Step S9. The collaborative monitoring module records the capability call information between all business source systems and business target systems and forms a collaborative log;

[0056] Step S10. Monitor whether government service items are abolished or newly added through the government service item change monitoring and notification module.

[0057] In some possible embodiments, when the capability monitoring module performs capability inspections, the interface capability is called according to the dialing test sample entered when the capability is registered, and the page capability is accessed according to the page address entered when the capability is registered, and the inspection results are returned. After obtaining the inspection report, the capability monitoring module outputs the inspection report according to the user dimension of the cross-domain inter-service support system, outputs the inspection report of the registered capability to the developer of the business system, and outputs the inspection report of the capability within the management authority of the cross-domain inter-service support system operation and maintenance user or the government service management department user.

[0058] During the collaborative monitoring process, the collaborative monitoring module marks the collaborative routing nodes that are completed, in progress, not yet reached, and do not need to be passed through with different colors. The call status of the capability can also be viewed in each collaborative routing node.

[0059] The technical solutions of the embodiments of the present invention have at least the following advantages and beneficial effects:

[0060] 1. The cross-domain handling method and support system provided by the present invention can realize cross-domain and cross-departmental handling of government services based on the collaboration between existing business system systems in different regions and departments. It is widely applicable to cross-domain handling between different regional levels and different department levels, and effectively solves the reform demand of "one-window acceptance and one-network handling" of the integrated government service platform.

[0061] 2. The cross-domain handling method and support system provided by the present invention can provide different docking methods and docking contents according to different cross-domain handling depths, providing more diverse choices for the agency, so that the agency can achieve cross-domain docking with different handling depths according to its own situation.

[0062] 3. Unlike the existing technology that requires the construction of a unified cross-domain one-stop service acceptance system, the present invention only requires the construction of a cross-domain one-stop service support system based on government service collaborative technology to enable the business systems of the local and agency locations to be connected, resulting in lower construction costs. At the same time, when the local location is building the cross-domain one-stop service support system, it can further reduce construction costs by sharing the same functional modules with the local government service business collaborative system.

[0063] 4. When carrying out specific government service processing tasks, the present invention is carried out in the agency acceptance system that the agency users are accustomed to using, avoiding the process of agency window personnel familiarizing themselves with and using multiple acceptance systems, and reducing the cost of agency window personnel familiarizing themselves with and using multiple acceptance systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 A flowchart of a cross-domain processing method based on government affairs collaboration technology provided by an embodiment of the present invention;

[0065] Figure 2 A schematic diagram of the process of capability application and docking rules provided in an embodiment of the present invention;

[0066] Figure 3 This is a structural block diagram of the cross-domain government affairs support system based on government affairs collaboration technology provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0067] Please refer to Figure 1 This embodiment provides a cross-domain processing method based on government affairs collaboration technology, which specifically includes the following steps:

[0068] Step S1. Establish collaborative capability rules, dividing the local and agency e-government systems into two types of business systems based on business type: acceptance system and processing system, and define the capabilities required for the two types of business systems to work together;

[0069] In step S1, the capabilities that the two types of business systems defined by the collaborative capability rules need to have in place for collaborative work include interfaces and pages that adapt to different terminal forms. For example, the capabilities of the local acceptance system include an application and material receiving interface, an acceptance progress query interface, a service guide query interface, a material sharing interface, and a material verification interface, etc. The capabilities of the local service system include a processing submission interface, a processing progress query interface, a service guide query interface, a material sharing interface, and a material verification interface, etc. The capabilities of the agency acceptance system include a receiving page, a data feedback interface, etc.

[0070] At the same time, the collaborative capability rules also define the calling relationship between the various capabilities of the business system. For example, the application and material receiving interface, acceptance progress query interface, matter service guide query interface, material sharing interface and material verification interface of the local acceptance system are called by the acceptance system of the agency; the processing submission interface, processing progress query interface, matter service guide query interface, material sharing interface and material verification interface of the local processing system are called by the acceptance system of the agency.

[0071] Secondly, the collaborative capability rules also define the unified interface structure and unified HTTP message header parameter name for the business system to connect to the cross-domain support system.

[0072] In addition, the collaborative capability rules also define the collaborative docking mode of business systems, which are divided into the following two modes:

[0073] One-way collaboration mode: The interface applicant calls the unified push interface of the cross-domain support system to push business data to each connected business system, and the connected business system receives the business data through the established interface;

[0074] Two-way collaborative mode: The applicant who calls the interface calls the unified push interface of the cross-domain support system to push business data to each connected business system. At the same time, the applicant of the interface needs to settle in the data feedback interface and connect the data feedback interface from the application interface. When the application interface feeds back data to the applicant, the cross-domain support system calls the data feedback interface settled by the applicant to receive the data.

[0075] Step S2. The capabilities of the local business system (i.e., the acceptance system and the processing system) are incorporated into the cross-domain support system. The developer of the local business system incorporates the capabilities according to the collaborative capability rules. When each capability is incorporated, the capability address, interface parameters, configuration of which one or more collaborative capability rules it belongs to, which government service items it is applicable to, and which network environment it runs in are entered.

[0076] Step S3. Local business system connection. The developer of the local business system applies for the ability to connect other business systems with their own system. For details, please refer to Figure 2 , the application and connection of capabilities are carried out in the following ways:

[0077] Step S31. The capabilities applied for by the applicant are related to the type of their own system, specifically, whether the application acceptance system is connected to the processing system, or vice versa.

[0078] Step S32. After the connection application is reviewed and approved, the applicant is issued the addresses of all the capabilities of the system being applied for, after being proxied by the cross-domain support system, based on the network environment in which the applicant's system operates. This allows each business system in its own network environment to connect with business systems in other network environments. In other words, cross-network connection is achieved between business systems in different network environments, reducing the difficulty of connecting different business systems across network environments.

[0079] For example, when the applicant system defines itself as running on the e-government extranet, and the requested capability runs on the Internet, the cross-domain support system authorizes the applicant system with the capability address of the requested capability in the e-government extranet environment after passing through the network proxy.

[0080] Step S33. After obtaining the authorized capability address, the applicant independently develops and debugs the connection between its own business system and the capability address. If the collaborative capability rule defines the collaborative connection mode for the authorized capability as bidirectional, the applicant also needs to configure a data feedback interface for its business system to receive feedback data through the data feedback interface.

[0081] Step S34. One business system of the applicant can be connected to multiple business systems at the same time.

[0082] Step S4. The locality configures collaborative routing according to the dimension of government service items. Collaborative routing is a system that carries the acceptance and processing links required to complete a government service item after receipt. Multiple collaborative routes are configured for one government service item. The specific collaborative routing through which the government service item is transferred can be determined by the receipt page of the acceptance system of the agency.

[0083] It should be noted that in step S4, one collaborative route is configured with one acceptance system and one or more processing systems. When there are multiple processing systems, it is necessary to specify which processing item (i.e., government service item) each processing system is responsible for, and define the series, parallel, or integrated relationship between each processing system. Preferably, when developing the collaborative route configuration module of the cross-domain processing support system, the collaborative routes for intra-domain services and the collaborative routes for cross-domain processing can be managed in a unified manner, and the collaborative routes for intra-domain services and cross-domain processing are not distinguished at the system function level, so that government service items in different scenarios are all determined by the receipt page of the agency acceptance system to determine which collaborative route to use for data flow, thereby achieving the same standard flow for intra-domain services and cross-domain processing, reducing the overall construction cost.

[0084] Step S5. The locality opens collaborative routing or service applications according to different service depths. The service depths are divided into display mode, collection mode and acceptance mode.

[0085] Specifically, in step S5, the display mode is to open the local service application in the local area. The local service application includes a window registration and receipt page and a correction and completion page, and is connected with the collaborative routing to realize the complete service process of government service matters, and the case data can be stored in the local government service platform or system; specifically, the window operator uses the local user system, and uses user names or other identifiers to distinguish between self-handled cases within the local area and cases handled by other places. The government service objects (that is, the people who come to do business) check the progress of the case in the personal center of the local government service network.

[0086] The agency collection mode is an open collaborative routing for the local area, which provides interfaces such as the application and material receiving interface, acceptance progress query interface, matter service guide query interface, material sharing interface and material verification interface of the local acceptance system in the collaborative routing, so as to facilitate the docking of the receipt page of the agency acceptance system with the above interfaces.

[0087] The agency acceptance mode provides interfaces such as the local open processing system's processing submission interface, processing progress query interface, matter service guide query interface, material sharing interface, and material verification interface, so as to facilitate the docking of the agency acceptance system's receiving page with the above interfaces.

[0088] Step S6. The agency applies for different territorial open content according to its own different needs for the depth of the integrated service and completes the connection.

[0089] Specifically, in step S6, when the depth of the general service is in the agent display mode, the agent applies for the URL of the local service application and mounts the link in its own acceptance system;

[0090] When the depth of the cross-service is the collection mode, the agency creates a service application and enters the basic information of the service application, network environment and page URL. The cross-domain cross-service support system issues a docking key to the agency's service application. The agency applies for the application and material receiving interface, acceptance progress query interface, matter service guide query interface, material sharing interface and material verification interface of the local acceptance system in the collaborative routing based on the created service application, and completes the docking with the receiving page of its own acceptance system, thereby realizing the docking of the agency's acceptance system and the local acceptance system. It should be noted that if the collaborative docking mode of each interface of the local acceptance system defined by the collaborative capability rule is a two-way collaborative mode, the agency's acceptance system also needs to configure a data feedback interface to receive feedback data.

[0091] When the depth of the cross-domain processing is the agency acceptance mode, the agency shall install the capabilities of the agency acceptance system in the cross-domain cross-domain processing support system according to steps S2 and S3, and at the same time apply for the capabilities of the local processing system and complete the connection with the local processing system. The locality shall configure the collaborative routing from the agency acceptance system to the local processing system according to step S4. The agency shall complete the connection of the receiving page of its own acceptance system with the collaborative routing from the agency acceptance system to the local service system according to the method described in the agency collection mode, thereby realizing the connection between the agency acceptance system and the local processing system.

[0092] For example, when the business system of the contemporary office is connected with the service guide query interface of the territorial business system, it can achieve the effect of agency service based on the territorial service standards; when the business system of the contemporary office is connected with the material sharing interface or material verification interface of the territorial business system, it can achieve the effect of reducing the paper materials submitted by the government service objects or the agency can verify the authenticity of the materials submitted by the government service objects by itself.

[0093] S7. Case distribution: When a government service case task is generated, the case will be distributed according to the different depths of the case.

[0094] Specifically, in step S7, when the depth of the unified service is in the agent display mode, all government service processing tasks are collaboratively distributed within the local business system; that is, the government service recipient selects the government service item to be processed from the local developed receipt page and enters the business data. The local developed service application connects to the corresponding collaborative routing, and the government service processing tasks are collaboratively distributed between the local acceptance system and the local processing system defined by the collaborative routing;

[0095] When the depth of the integrated service is in the agency collection mode, the collection page developed by the agency will query the service guide information through the service guide query interface of the local acceptance system and display it to the government service recipient. The government service recipient will select the government service item to be handled and enter the business data. According to the collaborative routing configured for the local area, the government service processing tasks will be collaboratively distributed between the local acceptance system and the local processing system defined in the collaborative routing;

[0096] When the depth of the general service is in the agency acceptance mode, the receiving page developed by the agency queries the service guide information through the service guide query interface of the local processing system and displays it to the government service object. The government service object selects the government service item to be processed and enters the business data. According to the collaborative routing configured by the local area, the government service processing tasks are collaboratively distributed between the agency acceptance system and the local processing system defined by the collaborative routing.

[0097] Among them, during collaborative distribution, the source system calls the capability address of the network agent of the cross-domain support system, and transmits the source system ID, unified matter code, collaborative rule code, case serial number and business data according to the definition of the unified HTTP message header.

[0098] At the same time, the cross-domain one-stop service support system uses the matter code to query the collaborative route where the government service matter is effective, finds the collaborative target system defined by the collaborative route, and then uses the calling relationship defined by the collaborative rule code. The cross-domain one-stop service support system calls the original address of the target system and transmits the business data.

[0099] Furthermore, the cross-domain handling method provided in this embodiment further includes the following steps:

[0100] Step S8. Perform inspections on all the capabilities of the business system at designated times through the capability monitoring module;

[0101] Step S9. The collaborative monitoring module records the capability call information between all business source systems and business target systems and forms a collaborative log;

[0102] Step S10. Monitor whether government service items are abolished or newly added through the government service item change monitoring and notification module.

[0103] On the other hand, please refer to Figure 3 This embodiment also provides a cross-domain one-stop service support system based on government affairs business collaboration technology, which is used to implement the cross-domain one-stop service method described above, and splits the cross-domain one-stop service support system into functional modules, including a collaborative capability rule configuration module, a capability entry module, a collaborative docking module, a collaborative routing configuration module, a cross-domain docking module, a collaborative gateway module, a capability monitoring module, a collaborative monitoring module, and a government affairs service matters monitoring and notification module.

[0104] The collaborative capability rule configuration module is used to configure the capability usage, capability form (i.e. interface or page adapted to different terminal forms), collaborative call relationship, collaborative docking mode, and whether it is required to be settled in the local business system and the agency business system.

[0105] The capability entry module is used for business system entry and capability entry. Among them, business system entry includes entering the basic information of the system, the system type, and the network environment in which the system operates, and issuing a docking key to the entry system. It should be noted that, under normal circumstances, local users can enter the acceptance system and the processing system, while users in the agency area can only enter the acceptance system. Capability entry includes calling out the collaborative capability rules of such systems based on whether the business system is an acceptance system or a processing system. The developer of the business system enters the capabilities of its own system according to the collaborative capability rules; as a preferred option, when the capability entry module is entering the capabilities of the business system, if the interface capability has an interface document, the developer of the business system can also upload the document; if the interface capability has a dial-up test channel, the developer of the business system can also enter the dial-up test sample. In addition, the capability entry module can also configure the capability library to store and manage all settled business systems and capabilities through the capability library.

[0106] The collaborative docking module is used to display the system set that can be docked, review the docking application, and issue the address of all the entry capabilities of the applied system to the applicant after the docking application is reviewed and approved through the cross-domain support system network proxy.

[0107] Among them, for the display of the system set that can be connected, the applicant selects the type of its own business system, and the collaborative connection module selects the systems that can be connected to the applicant's business system from the business systems that have been settled in the cross-domain support system. The applicant can choose one or more systems to initiate a connection application. The applicant will review the connection application, and the application information will display the applicant's business system information. When the connection application is approved, the address of all the settled capabilities of the applied system after passing through the cross-domain support system network agent will be issued to the applicant based on the network environment in which the applicant's business system operates. It should be noted that if the applied system uploaded the interface document when the capability was settled, the applicant can also download it. If the collaborative connection mode of the authorized capability defined by the collaborative capability rule is two-way collaboration, the applicant also needs to configure a data feedback interface for its own business system to receive feedback data.

[0108] The collaborative routing configuration module is used to configure collaborative routing based on government service items. Multiple collaborative routes can be configured for each government service item. Specifically, a collaborative route is configured with one acceptance system and one or more processing systems in the form of a topology diagram. When there are multiple processing systems, it is necessary to specify which processing item each processing system handles and define the series, parallel, or integrated relationships between the processing systems. In addition, the collaborative routing configuration module can also configure a collaborative routing library to store and manage the collaborative routes of all government service items.

[0109] The cross-domain docking module is used to display local open content and connect with agencies. Displayed content includes service applications based on the implementation list of government service items, collaborative routing, and various interfaces of local business systems. Agencies can apply for different local open content for docking based on their own needs for the depth of cross-service handling.

[0110] Collaborative gateway module, used for Nginx load cluster proxy; deploy Nginx load cluster simultaneously in the government Internet zone and the e-government extranet zone, and configure two clusters for bidirectional cross-network configuration, used for reverse proxy cross-network calls of on-site capabilities, and cross-domain one-stop support system, so that modules deployed in the government Internet zone and the e-government extranet zone can access each other.

[0111] At the same time, the collaborative gateway module can also perform collaborative authentication, receive call applications from the business source system, and verify the business source system docking key; the collaborative gateway module can also perform collaborative target addressing, receive call applications from the business source system, and search for the collaborative route of the corresponding matter in the collaborative routing configuration module according to the unified matter code passed in the call application, and search for the original address of the collaborative target system in the collaborative route; the collaborative gateway module can also perform collaborative distribution. During collaborative distribution, the source system calls the capability address of the network agent of the cross-domain support system, and passes the source system ID, unified matter code, collaborative rule code, case serial number and business data according to the definition of the unified HTTP message header.

[0112] The capability monitoring module is used to configure the capability inspection plan and inspect all the capabilities of the business system according to the capability inspection plan to obtain an inspection report. Specifically, the capability inspection plan may include the time period for the inspection and the number of inspections within a single time period. For example, the time period can be configured by hour, day, week or month. At the same time, when the capability monitoring module conducts capability inspection according to the capability inspection plan, the interface capability is called according to the dialing sample entered when the capability is stationed, and the page capability is accessed according to the page address entered when the capability is stationed, and the inspection results are returned; after the capability monitoring module obtains the inspection report, it outputs the inspection report according to the user dimension of the cross-domain support system, specifically, outputs the inspection report of the stationed capability to the developer of the business system, and outputs the inspection report of the capabilities within the management authority of the cross-domain support system operation and maintenance users or government service management department users.

[0113] The collaborative monitoring module is used to record all capability call information between business source systems and business target systems to form a collaborative log. This log is then aggregated based on the case number and collaboratively monitors the progress of task processing within the collaborative routing. Preferably, during the collaborative monitoring process, the collaborative monitoring module marks collaborative routing nodes that are completed, in progress, not yet reached, and not required to be traversed with different colors. The capability call status can also be viewed within each collaborative routing node.

[0114] The Government Service Monitoring and Notification Module is used to monitor the abolition or addition of new government service items. Specifically, when a government service item with a collaborative route is abolished, a notification is sent to the local user who configured the collaborative route for the government service item, the developer of the business system that hosts each node of the collaborative route, and the user at the agency, notifying them of the abolition of the government service item and the invalidation of the collaborative route. When a new government service item is added, the user at the government service management department is notified to configure a collaborative route for the new government service item.

[0115] In addition, it should be noted that if the local government has built its own government service business collaboration system, during the specific construction, the collaboration capability rule configuration module, capability entry module, collaboration docking module, collaboration routing configuration module, collaboration gateway module, capability monitoring module, collaboration monitoring module and government service matters monitoring and notification module of the above-mentioned cross-domain support system can share the same functional modules with the local government service business collaboration system used by the local government within the local area. At this time, it is only necessary to mark in the specific collaboration route whether it is a collaboration route within the territory or a collaboration route for cross-domain handling, and only display the collaboration route for cross-domain handling in the cross-domain docking module, thereby further reducing the cost of building a cross-domain support system.

[0116] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. A cross-domain handling method based on government affairs and business collaboration technology, characterized in that: The following steps are involved: Step S1. Establish collaborative capability rules, dividing the local and agency e-government systems into two types of business systems based on business type: acceptance system and processing system, and define the capabilities required for the two types of business systems to work together; Step S2. The capabilities of the local business system are incorporated into the cross-domain support system. The developer of the local business system incorporates the capabilities according to the collaborative capability rules. When each capability is incorporated, the capability address, interface parameters, configuration of which collaborative capability rule or rules it belongs to, which government services it applies to, and the network environment in which it operates are entered. Step S3. The developer of the local business system applies for the ability of other business systems to connect with their own system. Step S4. Configure collaborative routing based on the government service item dimension. Collaborative routing is the system that carries the acceptance and processing links required to complete a government service item. Multiple collaborative routings can be configured for a government service item. Step S5. Local authorities open collaborative routing or service applications according to different service depths. Service depths are divided into display mode, collection mode, and acceptance mode. Step S6. The agency applies for different territorial open content based on its own needs for the depth of the integrated service and completes the connection; Step S7. When a government service task is generated, the task is distributed according to the depth of the task; In step S7, When the depth of the government service is in the agent display mode, all government service tasks are collaboratively distributed within the local business system; When the depth of the integrated service is in the agency collection mode, the collection page developed by the agency will query the service guide information through the service guide query interface of the local acceptance system and display it to the government service recipient. The government service recipient will select the government service item to be handled and enter the business data. According to the collaborative routing configured for the local area, the government service processing tasks will be collaboratively distributed between the local acceptance system and the local processing system defined in the collaborative routing; When the depth of the integrated service is in the agency acceptance mode, the receiving page developed by the agency will query the service guide information through the service guide query interface of the local handling system and display it to the government service recipient. The government service recipient will select the government service item to be handled and enter the business data. According to the collaborative routing configured by the locality, the government service processing tasks will be collaboratively distributed between the agency acceptance system and the local handling system defined in the collaborative routing; Among them, during collaborative distribution, the source system calls the capability address of the network agent of the cross-domain support system, and transmits the source system ID, unified matter code, collaborative rule code, case serial number and business data according to the definition of the unified HTTP message header.

2. The cross-domain handling method based on government affairs and business collaboration technology according to claim 1 is characterized in that: In step S1, the collaborative capability rules define the capabilities that must be implemented by the two types of business systems for them to work together, including interfaces and pages that adapt to different terminal forms. At the same time, the collaborative capability rules also define: the calling relationships between the various capabilities of the business system; the unified interface structure and unified HTTP message header parameter names for the business system to connect to the cross-domain support system; and the collaborative docking mode of the business system. The collaborative docking mode is divided into the following two types: One-way collaboration mode: The interface applicant calls the unified push interface of the cross-domain support system to push business data to each connected business system, and the connected business system receives the business data through the established interface; Two-way collaborative mode: The applicant who calls the interface calls the unified push interface of the cross-domain support system to push business data to each connected business system. At the same time, the applicant of the interface needs to settle in the data feedback interface and connect the data feedback interface from the application interface. When the application interface feeds back data to the applicant, the cross-domain support system calls the data feedback interface settled by the applicant.

3. The cross-domain handling method based on government affairs and business collaboration technology according to claim 2 is characterized in that: In step S3, the application and connection of capabilities are carried out as follows: Step S31. The capabilities applied for by the applicant are related to the type of their own system, specifically, whether the application acceptance system is connected to the processing system, or vice versa. Step S32. After the docking application is reviewed, the applicant is issued with the address of all the entry capabilities of the applied system after the cross-domain support system network proxy is passed to the applicant according to the network environment in which the applicant's system operates. This enables each business system to dock with business systems in other network environments in its own network environment; Step S33. After the applicant obtains the authorized capability address, it independently develops and debugs the connection between its own business system and the capability address. If the collaborative capability rule defines the collaborative connection mode of the authorized capability as a two-way collaborative mode, the applicant also needs to configure a data feedback interface for its own business system. S34. An applicant's business system can be connected to multiple business systems simultaneously.

4. The cross-domain handling method based on government affairs and business collaboration technology according to claim 1 is characterized in that: In step S5, The proxy display mode is to open the local service application at the local level. The local service application includes the window registration and receipt page and the correction and completion page, and is connected to the collaborative routing. The service data is stored in the local government service platform or system. The collection mode is a local open collaborative routing, providing the local acceptance system's application and material receiving interface, acceptance progress query interface, matter service guide query interface, material sharing interface, and material verification interface in the collaborative routing; The agency acceptance mode is the local open processing system's processing submission interface, processing progress query interface, matter service guide query interface, material sharing interface, and material verification interface; In step S6, When the depth of the service is in the agent display mode, the agent applies for the URL of the local service application and mounts the link in its own acceptance system; When the depth of the cross-service is the agency collection mode, the agency creates a service application and enters the basic information of the service application, network environment and page URL. The cross-domain cross-service support system issues a docking key to the agency's service application. Based on the created service application, the agency applies for the local acceptance system's application and material receiving interface, acceptance progress query interface, matter service guide query interface, material sharing interface and material verification interface in the collaborative routing, and completes the docking with the receipt page of its own acceptance system; When the depth of the cross-domain processing is the agency acceptance mode, the agency will integrate the capabilities of the agency acceptance system into the cross-domain cross-domain processing support system, and at the same time apply for the capabilities of the local processing system and complete the connection with the local processing system. The local area configures the collaborative routing from the agency acceptance system to the local processing system. The agency will complete the connection of the receiving page of its own acceptance system with the collaborative routing from the agency acceptance system to the local processing system according to the method described in the agency collection mode.

5. The cross-domain handling method based on government affairs and business collaboration technology according to claim 1 is characterized in that: In step S4, one collaborative route is configured with one acceptance system and one or more processing systems. When there are multiple processing systems, it is necessary to specify which processing item each processing system handles, and define the series, parallel or integrated relationship between the processing systems.

6. A cross-domain service support system based on government affairs and business collaboration technology, used to implement the cross-domain service method according to any one of claims 1 to 5, characterized in that: The cross-domain support system is divided into functional modules, including: The collaborative capability rule configuration module is used to configure the capability usage, capability form, collaborative call relationship, collaborative docking mode, and whether the local business system and the agency business system must be settled; The capability registration module is used for business system registration and capability registration. Business system registration includes entering basic system information, system type, and the network environment in which the system operates, and issuing a connection key to the registered system. Capability registration involves calling up the collaborative capability rules for the system type based on whether the business system is an acceptance system or a processing system. The developer of the business system enters the capabilities of their own system according to the collaborative capability rules. The collaborative docking module is used to display the system set that can be docked, review the docking application, and issue the address of all the entry capabilities of the applied system to the applicant after the docking application is approved through the cross-domain support system network proxy; The collaborative routing configuration module is used to configure collaborative routing based on the dimension of government service items and configure multiple collaborative routes for each government service item; The cross-domain docking module is used to display local open content and connect with the agency. The displayed content includes service applications based on the implementation list of government service items, collaborative routing, and various interfaces of local business systems. The agency can apply for different local open content for docking based on its own different needs for the depth of cross-service. Collaborative gateway module, used for Nginx load cluster proxy; deploy Nginx load cluster simultaneously in the government Internet zone and the e-government extranet zone, and configure two clusters for bidirectional cross-network configuration, used for reverse proxy cross-network calls of on-site capabilities, and cross-domain one-stop support system, so that modules deployed in the government Internet zone and the e-government extranet zone can access each other.

7. The cross-domain support system based on government affairs and business collaboration technology according to claim 6 is characterized in that: When the capability entry module is entering business system capabilities, if the interface capability of a business system includes interface documents, the developer of the business system can also upload documents. If the interface capability of a business system includes a dial-test channel, the developer can also enter dial-test samples. After the collaborative docking application is approved, the applicant can also download the interface document uploaded by the applied system when the capability is registered. If the collaborative docking mode of the authorized capability is defined as bidirectional collaboration by the collaborative capability rule, the applicant also needs to configure a data feedback interface for its own business system to receive feedback data. The collaborative gateway module can also perform collaborative authentication, receive call requests from the business source system, and verify the business source system docking key; The collaborative gateway module can also perform collaborative target addressing, receive call applications from the business source system, search for the collaborative route of the corresponding matter in the collaborative routing configuration module according to the unified matter code passed in the call application, and search for the original address of the collaborative target system in the collaborative route; the collaborative gateway module can also perform collaborative distribution. During collaborative distribution, the source system calls the capability address of the network agent of the cross-domain support system, and passes the source system ID, unified matter code, collaborative rule code, case serial number and business data according to the definition of the unified HTTP message header.

8. The cross-domain support system based on government affairs and business collaboration technology according to claim 6 is characterized in that: The cross-domain support system also includes: The capacity monitoring module is used to configure the capacity inspection plan and inspect all the capabilities of the business system according to the capacity inspection plan to obtain the inspection report; The collaborative monitoring module is used to record the capability call information between all business source systems and business target systems to form a collaborative log. It also summarizes the collaborative log based on the case serial number and collaboratively monitors the progress of the case task in the collaborative routing. The government service item monitoring and notification module is used to monitor whether government service items are abolished or newly added. When a government service item that has been configured with collaborative routing is abolished, a notification is sent to the local user who configured the collaborative routing for the government service item, the developer of the business system that carries each node of each collaborative routing, and the user at the agency, reminding them that the government service item has been abolished and the collaborative routing has become invalid. When a new government service item is added, the user of the government service management department is notified to configure collaborative routing for the new government service item. At this point, the cross-domain handling method also includes the following steps: Step S8. Perform inspections on all the capabilities of the business system at designated times through the capability monitoring module; Step S9. The collaborative monitoring module records the capability call information between all business source systems and business target systems and forms a collaborative log; Step S10. Monitor whether government service items are abolished or newly added through the government service item change monitoring and notification module.

9. The cross-domain support system based on government affairs and business collaboration technology according to claim 8 is characterized in that: When the capability monitoring module performs capability inspection, the interface capability is called according to the dial test sample entered when the capability is registered, and the page capability is accessed according to the page address entered when the capability is registered, and the inspection results are returned; After receiving the inspection report, the capability monitoring module outputs the inspection report according to the user dimension of the cross-domain support system. For the developer of the business system, the inspection report of its entry capability is output. For the operation and maintenance user of the cross-domain support system or the user of the government service management department, the inspection report of the capability within their management authority is output. During the collaborative monitoring process, the collaborative monitoring module marks the collaborative routing nodes that are completed, in progress, not yet reached, and do not need to be passed through with different colors. The call status of the capability can also be viewed in each collaborative routing node.

Images