CN118644371A - Digital government affairs operating system, service process construction method, equipment and media - Google Patents

Abstract

The disclosure provides a digital government operating system, a method, equipment and a medium for constructing a service flow, wherein the system comprises: the system comprises a resource management module and a task management module, wherein the resource management module is used for generating a business service flow and a service flow file and a parameter form corresponding to the business service flow according to a service resource API selected by a user, one service resource API is used as one service flow node in the business service flow, and the service flow file records the node information of each service flow node in the business service flow and the sequence relation between the service flow nodes; and the task management module is used for acquiring API call parameters filled in the parameter form by the user when the user calls the business service flow, and calling the service resource API based on the API call parameters and the service flow file. The scheme realizes cross-platform and cross-system data integration, breaks the data island and realizes information sharing.

Description

Digital government affairs operating system, service process construction method, equipment and media

Technical Field

The present disclosure relates to the field of computer technology, and in particular to a digital government affairs operating system, a method for constructing a service process, a device and a medium.

Background Art

At present, most local government services adopt a combination of online and offline methods. When using online platforms for services, it is necessary to build service processes through coding. The process construction is difficult, and the built service process is fixed. When faced with policy changes or process adjustments, coding level modifications are required, resulting in an inability to respond in a timely manner. In addition, each department has certain service resources, but the service resources of each department are not interoperable, making it difficult to support cross-departmental service matters, and there is a "data island" phenomenon.

Summary of the invention

In order to solve the above technical problems or at least partially solve the above technical problems, the embodiments of the present disclosure provide a method, device and medium for constructing a digital government affairs operating system and service process.

According to one aspect of the present disclosure, there is provided a digital government affairs operating system, comprising: a resource management module and a task management module;

The resource management module is used to generate a business service process and a service process file and parameter form corresponding to the business service process according to the service resource API selected by the user. A service resource API is used as a service process node in the business service process. The service process file records the node information of each service process node in the business service process and the sequential relationship between the service process nodes;

The task management module is used to obtain the API call parameters filled in by the user in the parameter form when the user calls the business service process, and call the service resource API based on the API call parameters and the service process file.

According to another aspect of the present disclosure, a method for constructing a service process is provided, which is applied to the digital government affairs operating system as described in the above aspect, and the method includes:

Receiving a service resource API selected by a user through an operation page of the digital government affairs operating system;

Taking one of the service resource APIs as a service process node, generating a business service process and a service process file and a parameter form corresponding to the business service process, wherein the service process file records the node information of each service process node in the business service process and the sequence relationship between the service process nodes;

When the user calls the business service process, obtaining the API call parameters filled in by the user in the parameter form;

A service resource API is called based on the API call parameters and the service process file.

According to another aspect of the present disclosure, there is provided an electronic device, comprising:

Processor; and

Memory for storing programs,

The program includes instructions, which, when executed by the processor, enable the processor to execute the method for constructing the service process according to the aforementioned aspect.

According to another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable the computer to execute the method for constructing a service process according to the aforementioned aspect.

According to another aspect of the present disclosure, a computer program product is provided, including a computer program, wherein the computer program implements the method for constructing a service process described in the aforementioned aspect when executed by a processor.

One or more technical solutions provided in the embodiments of the present disclosure are as follows: the resource management module generates a business service process and a service process file and a parameter form corresponding to the business service process according to the service resource API selected by the user; a service resource API is used as a service process node in the business service process; the service process file records the node information of each service process node in the business service process and the sequential relationship between the service process nodes; when the user calls the business service process, the task management module obtains the API call parameters filled in by the user in the parameter form, and calls the service resource API based on the API call parameters and the service process file. By adopting the solution of the present disclosure, by uniformly encapsulating different government service resources into a service resource API, cross-platform and cross-system data integration is realized, the interconnection between different service systems is facilitated, the data island is broken, and information sharing is realized, and the user only needs to select the required service resource API to build the business service process, which reduces the difficulty of process construction. When the service process needs to be modified, only the service resource API needs to be adjusted, and there is no need to modify the underlying coding, which reduces the difficulty and time cost of process modification and is conducive to speeding up business response.

BRIEF DESCRIPTION OF THE DRAWINGS

Further details, features and advantages of the present disclosure are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:

FIG1 shows a schematic diagram of the structure of a digital government affairs operating system according to an exemplary embodiment of the present disclosure;

FIG2 shows a schematic structural diagram of a digital government affairs operating system according to another exemplary embodiment of the present disclosure;

FIG3 is a schematic diagram of the architecture of a digital government affairs operating system provided by a specific embodiment of the present disclosure;

FIG. 4 is a flow chart of a method for constructing a service process provided by an exemplary embodiment of the present disclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and/or in parallel. In addition, the method embodiments may include additional steps and/or omit the steps shown. The scope of the present disclosure is not limited in this respect.

The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below. It should be noted that the concepts of "first", "second", etc. mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

Before explaining the digital government affairs operating system, service process construction method, device and medium disclosed in the present invention, the Chinese and English terms that may be involved in the present invention are explained as follows:

API: Application Programming Interface, the full name in English is Application Programming Interface. API acts as a bridge between software components, allowing different programs or services to interact with each other. Application resources related to external services need to be encapsulated into APIs and connected to the digital government operating system of the disclosed solution to achieve unified resource management.

XML: Extensible Markup Language, also known as Extensible Markup Language, is a markup language used to store and transmit data, similar to HTML. The disclosed solution defines the data structure of business service processes and service resource API nodes and the sequential relationship between APIs through XML mode, and each business service process corresponds to an XML file.

At present, most local government services adopt a combination of online and offline methods. Each service item on the online platform has a fixed service process, which requires manual sorting of the event list. In addition, when faced with policy changes or process adjustments, coding-level modifications are required, and the system process cannot respond quickly and timely. In addition, the process arrangement of the existing system is not highly intelligent, and a large amount of manual intervention is required to realize the construction of service processes and business processing. The service resources of various departments are not interoperable, making it difficult to support cross-departmental service items. There is a phenomenon of data islands, tight coupling of data and applications, insufficient release of data value, and the development of data security capabilities needs innovative breakthroughs.

Based on the above problems, the present disclosure provides a method for constructing a digital government affairs operating system and service process, which can realize the customized orchestration and intelligent construction of service processes, reduce manual participation, and improve the responsiveness of the system. The digital government affairs operating system provided by the embodiment of the present disclosure maps the resource management, information management, task management and resource scheduling capabilities in the traditional operating system to the government affairs service scenario, and constructs a software system to realize the unified access and management of the underlying business resources, data resources, network computing and other basic resources in government affairs services in the form of API or SDK, so as to realize global resource scheduling and multi-task collaboration. The digital government affairs operating system is based on the Spring Cloud microservice framework, and is built using frameworks and technologies such as SpringBoot, SpringCloudHoxton, and MybatisPlus, and performs service discovery, configuration and management through the service registration center Nacos. The kernel of the digital government affairs operating system consists of three main functional modules: task management, process management, and resource management. It also includes service governance functions such as service monitoring and service analysis to build a closed-loop path for government affairs services. Among them,

Task management is responsible for request reception, task determination and the flow of a single task in each node, including how to create tasks, delete tasks, change task priorities, suspend and resume tasks in the user's application, and obtain information about tasks; users can initiate tasks for specified business process scenarios through the task management module to complete the corresponding process and task processing. Task management includes task lists, task schedulers, aspect processors, task health managers and task security audits. Among them, the task list is used to make preliminary judgments on tasks when multiple tasks arrive, including task priority determination and regular/unconventional request determination. The main functions include task reception, task priority management, queue strategy configuration, task statistics analysis, etc. The task scheduler is used to coordinate the execution process of different tasks. The main functions include asynchronous processing, synchronous processing, concurrent controllers, batch processors, interrupt processing, dynamic agents, etc. The aspect processor is responsible for completing the parameters required for tasks when scheduling services. The main functions include pre-processing, post-processing, exception processing, return processing, and surround processing. The task health manager is responsible for real-time monitoring, analysis and reporting of the status and performance of a system, application or service, so as to timely discover problems, quickly locate and solve problems, and ensure the high availability and stability of the system. The main functions include fault location and monitoring alarm; task safety audit is used to review and count log records for security, and its main functions include log management, security correlation analysis, and data collection and analysis.

Process management is responsible for the flow scheduling during the execution of multiple subtasks, mainly including process intervention and process error correction. The process intervention is responsible for intervening in the execution order and status of multiple subtasks, and its main functions include process monitoring, process suspension, process termination and process regulation, etc. The process error correction is responsible for handling when abnormalities occur in the execution of subtasks, and its main functions include process abnormality identification and process abnormality handling, etc. Through process management, users can view the processes in the system, judge the health status of the server, and intervene in the execution order and status of multiple subtasks.

Resource management is responsible for the access, adaptation, registration, management and scheduling of business services, data services and resource services, mainly including filing service center, directory manager, resource pool virtualizer, dynamic loader, service driver and network communication management. Among them, the filing service center is responsible for the registration, adaptation, access, scheduling, monitoring, statistical analysis and performance management of all business services, data services and basic resource services. The main functions include service filing, service registration, service flow control, service authentication, service performance, service standards, service list, service review, service publishing and service monitoring, etc. The directory manager is responsible for generating the corresponding directory of the service list, and managing, modifying, reviewing and publishing the corresponding directory, so as to realize the user and The interaction of various service items, the main functions include catalog combing, distribution management, catalog review and published catalogs, etc.; the resource pool virtualizer is responsible for the dynamic creation and release of resources required for the service, the main functions include resource pool creation, resource pool destruction, resource pool configuration and resource pool automatic expansion and contraction, etc.; the dynamic loader is responsible for activating the service image and providing service operation efficiency, the main functions include panoramic image, image destruction and image recovery; the service driver is responsible for the adaptation of various services when they are connected to the filing service center, mainly including service adapters and service interfaces; network communication management is responsible for realizing the distributed deployment of the digital government operating system; the data cache disk is responsible for generating cache resources for various commonly used data and improving the access efficiency of commonly used data. Resource management provides an API configuration entry for service providers, allowing the interface name, interface address, interface description, interface request type, interface protocol type, interface encoding method, request parameters, response parameters and other information to be used as input to register the corresponding service content to the digital government operating system; it also supports service process orchestration, and users can view the connected API nodes on the page, and edit the sequence, series and parallel relationships, parameter settings and other information between nodes by dragging and dropping. After the configuration is completed, the service filing is saved. After the filed service is reviewed by the administrator, the current service can be published and called by users.

The service governance function is used to provide a data dashboard, displaying system service call information from different dimensions such as interfaces and services, and providing statistical data for different time periods to support data analysis.

This solution encapsulates different service resources into API form by formulating unified service interfaces and protocols. API service resource standardization realizes cross-platform and cross-system data integration, breaks down data silos, facilitates interconnection between different service systems, and realizes information sharing. This solution provides custom process orchestration and service resource management. For accessed API-type service resources, it allows users to build business service processes on the page manually or through intelligent assistance, which enhances the standardization of the process, reduces repeated entry and manual processing, and can cope with complex business scenarios and provide package-based service processes.

The following describes the digital government affairs operating system, service process construction method, device and medium provided by the present disclosure with reference to the accompanying drawings. Figure 1 shows a schematic diagram of the structure of a digital government affairs operating system according to an exemplary embodiment of the present disclosure, which can be integrated in electronic devices, including computers, mobile phones, tablet computers and other devices.

As shown in Figure 1, the digital government operation system 10 includes a resource management module 110 and a task management module 120, wherein the resource management module 110 is used to generate a business service process and a service process file and parameter form corresponding to the business service process according to the service resource API selected by the user, wherein a service resource API serves as a service process node in the business service process, and the service process file records the node information of each service process node in the business service process and the sequential relationship between the service process nodes; the task management module 120 is used to obtain the API call parameters filled in by the user in the parameter form when the user calls the business service process, and call the service resource API based on the API call parameters and the service process file.

In this embodiment, for government service resources (such as application resources, data resources, intelligent model resources, etc.) provided by various types of users, these government service resources can be uniformly encapsulated into the form of APIs based on the Swagger specification to achieve standardization of service resources. In other words, one service resource is encapsulated into a service resource API. By encapsulating service resources into APIs, clear interface specifications are defined for service resources, including request methods, Uniform Resource Locators (URLs), request parameters, request headers, request bodies, and response formats. By defining a unified service resource standard, the problem of data non-interoperability between departments is solved so that services can be correctly called after being connected to the system.

For the encapsulated service resource API, in this embodiment, the service resource API can be registered in the digital government operating system through the resource management module 110. The resource management module 110 is responsible for the access, adaptation, registration, management and scheduling of the encapsulated business services, data services and resource services. The digital government operating system 10 can provide an operation page for the user to operate. The user selects the service resource API in the operation page to build the service process. The resource management module 110 determines the association relationship and call sequence between the service resource APIs according to the service resource API selected by the user and the connection relationship between each service resource API, generates a business service process, and stores the arranged business service process in a preset format (such as XML format), and generates a corresponding service process file. The service process file records the node information of each service process node (i.e., service resource API) in the business service process and the sequential relationship between the service process nodes. The node information includes, for example, the resource name, node ID, node type, etc. of the service process node. The sequential relationship between the service process nodes can be reflected by recording the next node ID associated with the current node, or by other recording methods. The present disclosure does not limit this. In addition, the resource management module 110 generates a corresponding parameter form based on the relevant information of each service resource API, such as interface name, interface address, interface description, interface request type, interface protocol type, interface encoding method, request parameters, response parameters, etc., which are stored in the corresponding table of the system database. One business service process corresponds to one parameter form, and the parameter form records the above-mentioned relevant information of each service process node (i.e., service resource API) in the business service process. When the service resource API is called, the code logic is used to retrieve and automatically fill in the information in the above parameter form to initiate an interface call request, thereby realizing the call to the service resource API.

It can be understood that some known information (interface name, interface address, etc.) of each service resource API in the parameter form can be filled in when the parameter form is generated. Since the same service resource API may require different parameters in different businesses, in this embodiment, some parameters required to call the service resource API (such as request parameters, response parameters, etc.) can be filled in by the user when the user initiates a call to the business service process.

In the disclosed embodiment, the task management module 120 is responsible for request reception, task determination, and the flow of a single task at each node. When a user (the public or a government service personnel) calls a business service process, it is necessary to fill in the call parameters required for all service resource APIs in the business service process in the corresponding parameter form, and initiate a process call request after completing the form. After receiving the process call request, the digital government operating system 10 determines through the task management module 120 whether the parameters of the service resource API filled in by the user meet the process running conditions, and when the running conditions are met, fill in the parameters filled in by the user according to the node order of the service resource API recorded in the service process file to call the service resource API and advance the service process.

In the digital government affairs operating system of the disclosed embodiment, the resource management module generates a business service process and a service process file and a parameter form corresponding to the business service process according to the service resource API selected by the user. A service resource API is used as a service process node in the business service process, and the service process file records the node information of each service process node in the business service process and the sequential relationship between the service process nodes; when the user calls the business service process, the task management module obtains the API call parameters filled in by the user in the parameter form, and calls the service resource API based on the API call parameters and the service process file. The scheme disclosed in the present invention is adopted to realize cross-platform and cross-system data integration by uniformly encapsulating different government service resources into service resource APIs, facilitate the interconnection between different service systems, break the data island, realize information sharing, and users only need to select the required service resource API to build a business service process, which reduces the difficulty of process construction. When the service process needs to be modified, only the service resource API needs to be adjusted, and there is no need to modify the underlying coding, which reduces the difficulty and time cost of process modification and is conducive to accelerating business response speed.

A business service process usually includes the start and end of the process. In order to avoid the situation where the business service process fails to be constructed due to the user not selecting the service start node and the service end node, in an optional implementation of the present disclosure, the resource management module 110 can automatically generate the service start node and the service end node when creating the process, so that the user does not need to manually add these two nodes. Therefore, in this embodiment, the resource management module 110 is also used to automatically add the service start node to the canvas after receiving the process creation request, and monitor in real time whether the user has performed a drag operation on the displayed service resource API. When receiving the user's add operation of dragging the service resource API to the canvas, the resource management module 110 obtains the order of adding the service resource API. After receiving the process end instruction, the resource management module 110 generates the business service process and the corresponding service process file according to the service start node, the order of adding the service resource API, and the service end node, and generates a parameter form according to the service resource API.

The resource management module 110 supports users to customize the arrangement of service processes. For API resources that have been entered into the system, they can be added to the canvas as service process nodes by dragging and dropping in the operation page, and the association relationship and calling order between nodes can be determined. The arranged process is stored in the form of a service process file (such as a file in XML format). The service process file saves the resource name, node ID, node type, and next node ID of each node in the current process, thereby saving the order relationship between nodes. When creating a process, a service start node is automatically generated. The service start node may include but is not limited to preset identity authentication, service availability check, and resource allocation logic, etc. The service resource API added by the user is added as a service process node after the service start node; when the process needs to be ended, the user can manually add a service end node or the resource management module 110 can automatically add a service end node. The service end node may include but is not limited to result return, resource release, and logging logic, etc.

The digital government affairs operating system provided by the embodiment of the present disclosure also supports intelligent auxiliary arrangement based on a big model and a knowledge graph. The big model generates and outputs a business reference process template by searching in the knowledge graph. Government service personnel and other users can make subsequent adjustments based on the template according to the actual situation to obtain the required business service process. Therefore, in an optional implementation of the present disclosure, the resource management module 110 is also used to receive the business description information input by the user, input the business description information into the pre-trained process prediction big model, and the process prediction big model generates and outputs a business reference process template based on the business description information and the preset knowledge graph. The resource management module 110 can display the business reference process template to the user through the operation page, and the user can adjust the business reference process template according to his own needs. After that, the resource management module 110 generates the business service process and the corresponding service process file and parameter form according to the user's adjustment operation on the business reference process template.

Among them, the knowledge graph is pre-built, and the knowledge graph stores the relevant information of each service resource API and the relationship between each service resource API and other service resource APIs. As a kind of persistent storage, the knowledge graph can be based on the service events manually sorted out by government service personnel. The technical personnel can standardize the service process in the form of API relationship according to the nodes in advance, build a database that can display the relationship between service resource APIs, form a knowledge graph, and establish a mapping relationship between service resource APIs and business process descriptions. The process prediction big model is pre-trained. The process prediction big model performs semantic analysis on the input business description information, obtains the corresponding process information through semantic analysis, and then queries the mapping relationship between the service resource API and the business process description according to the process information, determines all service resource APIs matching the process information, and then retrieves the relationship between these service resource APIs in the knowledge graph, obtains the service resource API associated with the process information, the relevant information of each service resource API and the relationship between the APIs, and automatically creates and outputs the business reference process template by reconstructing the process and adjusting the node order, so as to realize the automatic matching of the big model according to the business description semantics, thereby realizing the automatic generation of the API business chain template (i.e., the business reference process template).

The resource management module 110 can display the business reference process template generated by the process prediction big model to the user, and the user can adjust the business reference process template according to his own needs. After the user completes the adjustment, the required business service process is obtained, and then the resource management module 110 generates the corresponding service process file according to the adjusted business service process, and generates a parameter form according to the relevant information of the service process node contained in the adjusted business service process. By using the big model and knowledge graph to generate the business reference process template to assist users in building business service processes, the difficulty of service process arrangement is simplified, the time consumption of manual event combing is reduced, and the efficiency of process construction is improved.

In an optional implementation of the present disclosure, the arranged business service process can be published after passing the review, and the process in the published state can be called by the user. Therefore, in this embodiment, the resource management module 110 is also used to publish the business service process for user call. The task management module 120 is also used to respond to receiving a user's click operation on the target business service process in the published state, obtain the target parameter form corresponding to the target business service process, and display the target parameter form to the user so that the user can fill in the target parameter form; respond to receiving a process call request of the target business service process, based on the API call parameters filled in the target parameter form and the service process file corresponding to the target business service process, call the service resource API.

It can be understood that the user in this embodiment can be a person who builds a business service process or other person. The built business service process is in a published state after being published. There can be one or more business service processes in the published state.

Exemplarily, when publishing a business service process, the user who builds the business service process can set a process name for it. The business service process in the publishing state is named with the process name and corresponds to a process entrance. When the user clicks on the process entrance, it is equivalent to clicking on the corresponding business service process. After that, the task management module 120 obtains the parameter form (for the convenience of description and distinction, referred to as the target business service process) corresponding to the business service process clicked by the user (for the convenience of description and distinction, referred to as the target parameter form), and displays the target parameter form to the user, for example, the filling interface of the target parameter form can be displayed in the form of a pop-up window, so that the user can fill in the API call parameters in the target parameter form. When the user has completed the filling, for example, the user clicks the "Save" button displayed in the filling interface of the target parameter form, it is determined that the user has completed the filling, and the process call request is triggered and sent to the digital government operation system 10. After receiving the process call request, the task management module 120 obtains the corresponding API call parameters from the target parameter form according to the service process node and the corresponding call sequence recorded in the service process file corresponding to the target business service process, and initiates the call of the service resource API.

In an optional implementation of the present disclosure, as shown in FIG2, based on the embodiment shown in FIG1, the digital government affairs operating system 10 of the present disclosure may also include a process management module 130, which is used to track the call information of each service resource API in the business service process during the call process of the business service process, and after the business service process call is completed, generate a business call log according to the call information of each service resource API, and send the business call log to the centralized log association system. In this way, the call status monitoring of the business service process is realized, thereby ensuring the complete call of the business service process in the government affairs scenario.

FIG3 is a schematic diagram of the architecture of a digital government operating system provided by a specific embodiment of the present disclosure. As shown in FIG3, the digital government operating system includes: a task and process management module composed of a task process microservice, a resource management module composed of a resource management microservice, and an extended service module composed of an extended microservice, wherein the resource management module implements the functions of the above resource management module, allowing users to use the interface resources that have been connected to the system to perform process orchestration and task creation; the task and process management module implements the functions of the above task management module and process management module, and the extended service module is used as a backup to facilitate subsequent expansion of new functions. Users (such as government service personnel) use their own computers to send requests (such as process creation requests, process call requests) to the digital government operating system through the Hypertext Transfer Protocol Secure (HTTPS) through the gateway in the gateway cluster. The gateway in the gateway cluster is also used to provide access authentication services to ensure that users accessing the digital government operating system are legal and to ensure the security of the digital government operating system. The digital government operating system registers services with a service registration center (such as Nacos), and the service registration center returns the service to the digital government operating system after service discovery. The digital government operating system stores the relevant information of the service resource API discovered, such as interface name, interface address, interface description, interface request type, interface protocol type, interface encoding method, request parameters, response parameters, etc., in the corresponding table of the database. After the digital government operating system receives the process call request sent by the gateway, the task process microservice determines whether the API call parameters filled in by the user meet the process running conditions. If they meet, the task process microservice fills in the parameters filled in by the user according to the API node call sequence recorded in the XML file (service process file) to make an API call and advance the service process. The function of the task process microservice also includes service status monitoring, including process monitoring, process suspension, process termination, process regulation, and process exception correction. For each API call in the process, including detailed information of the request, response result, call time, etc., the call log is sent to a centralized log management system, such as EFK (Elasticsearch, Filebeat, Kibana), and link tracking is implemented using tools such as Zipkin and Jaeger, generating a unique tracking ID for each service process to track the entire call chain. Users can view and intervene in the status of the initiated process through the process management module to better understand the service call and system performance.

In summary, the digital government operating system provided by the present disclosure, by encapsulating various resources into a unified API form, for the service resources of the connected API type, government service personnel can add API service process nodes to the canvas by dragging and dropping through the page, and determine the order and concurrency relationship between the nodes, and generate a parameter form. When a user initiates a process, he only needs to fill in the API parameter form to initiate a call to the created process; at the same time, the big model is used to realize the intelligent auxiliary construction of the process under the support of the government knowledge graph. The user only needs to adjust the nodes and determine the order relationship according to business needs based on the template generated by the big model, thereby reducing the workload of process construction. The solution disclosed in the present disclosure can be applied to government service scenarios, providing government service personnel with a process orchestration method, and accelerating the business response speed in the face of a large number of third-party service resources.

The present disclosure also provides a method for constructing a service process, which is applied to the digital government affairs operating system as described in the aforementioned embodiment.

FIG4 is a flow chart of a method for constructing a service process provided by an exemplary embodiment of the present disclosure. As shown in FIG4 , the method for constructing a service process may include the following steps:

Step 201, obtain the service resource API selected by the user through the operation page of the digital government operating system, take a service resource API as a service process node, generate a business service process and the service process file and parameter form corresponding to the business service process, and the service process file records the node information of each service process node in the business service process and the sequential relationship between the service process nodes.

In the embodiment of the present disclosure, when a user enters the digital government operation system, the service resource API that has been entered into the digital government operation system will be displayed in the operation page of the digital system operation system. The operation page is a page for users to operate, and users can interact with the digital government operation system through the operation page. When building a service process, the user can select the required service resource API through the operation page according to their own needs. For each service resource API selected by the user, the digital government operation system can obtain the service resource API selected by the user, and use a service resource API as a service process node to generate a business service process, and generate a service process file and parameter form corresponding to the business service process. The service process file records the node information of each service process node (i.e., service resource API) in the business service process and the sequential relationship between the service process nodes. The node information includes, for example, the resource name, node ID, node type, etc. of the service process node. The sequential relationship between the service process nodes can be reflected by recording the next node ID associated with the current node, or by other recording methods. The present disclosure does not limit this. The parameter form records the relevant information of each service resource API in the business service process, including but not limited to the interface name, interface address, interface description, interface request type, interface protocol type, interface encoding method, request parameters, response parameters, etc.

It should be noted that in this embodiment, the digital government affairs operating system can determine the order between nodes according to the order in which users select service resource APIs, and can also determine the calling order and association relationship between nodes according to the connection relationship configured by users for the selected service resource APIs, and then generate a business service process based on the calling order and association relationship.

In an optional implementation of the present disclosure, the operation page provided by the digital government operating system may include two areas, one area is used to display all the service resource APIs that have been entered for user selection, and the other area is a canvas for receiving the service resource API currently selected by the user, and the user can drag the service resource API to the canvas by dragging. The user initiates a process creation request through the operation page. When the digital government operating system receives the process creation request initiated by the user, it automatically adds a service start node to the canvas, and then the user can drag the required service resource API to the canvas. In response to receiving the user's adding operation of dragging the service resource API to the canvas, the digital government operating system obtains the service resource API dragged by the user and the order of adding the service resource API, and when receiving the process end instruction, generates a business service process and a corresponding service process file according to the service start node, the service resource API selected by the user and its order of adding, and the service end node, and generates a parameter form according to the service resource API.

Step 202: When a user calls a business service process, obtain the API call parameters filled in by the user in the parameter form.

For the completed business service process, it can be published after passing the review, and the business service process in the published state can be called by the user. For example, the published business service process can be displayed in the process display page, which displays all available business service processes. The user can initiate a call to the business service process by clicking on a business service process. After that, the digital government operating system obtains the API call parameters of each service resource API in the parameter form corresponding to the business service process.

As an example, when a user clicks on a business service process, the digital government operating system displays the parameter form corresponding to the business service process to the user. The user fills in the API call parameters of each service resource API in the parameter form. After the user completes the filling, the digital government operating system can obtain the API call parameters of each service resource API in the business service process.

Step 203: Call the service resource API based on the API call parameters and the service process file.

In the disclosed embodiment, after the digital government affairs operating system obtains the API call parameters filled in by the user in the parameter form, it can call the service resource API according to the API call parameters and the service process file.

Exemplarily, the digital government affairs operating system can initiate calls to each service resource API in sequence according to the calling order of the service process nodes recorded in the service process file. When calling, it obtains the corresponding API call parameters from the parameter form and fills them in to call the service resource API, thereby advancing the business service process.

The service process construction method of the disclosed embodiment receives the service resource API selected by the user through the operation page of the digital government operating system, takes a service resource API as a service process node, generates a business service process and a service process file and parameter form corresponding to the business service process, and when the user calls the business service process, obtains the API call parameters filled in by the user in the parameter form, and then calls the service resource API based on the API call parameters and the service process file. In this way, the data barriers between departments are broken through by standardizing the service resources into the form of API, providing government service personnel with an efficient process orchestration method, and accelerating the business response speed in the face of a large number of third-party service resources.

In an optional embodiment of the present disclosure, the service process construction method of the present disclosure also includes: receiving business description information input by a user, inputting the business description information into a pre-trained process prediction model, and having the process prediction model generate and output a business reference process template based on the business description information and a preset knowledge graph, and then generating a business service process and corresponding service process files and parameter forms based on the user's adjustment operations on the business reference process template.

Among them, the knowledge graph is pre-built, and the knowledge graph stores the relevant information of each service resource API and the relationship between each service resource API and other service resource APIs. As a kind of persistent storage, the knowledge graph can be based on the service events manually sorted out by government service personnel. The technical personnel can standardize the service process in the form of API relationship according to the nodes in advance, build a database that can display the relationship between service resource APIs, form a knowledge graph, and establish a mapping relationship between service resource APIs and business process descriptions. The process prediction big model is pre-trained. The process prediction big model performs semantic analysis on the input business description information, obtains the corresponding process information through semantic analysis, and then queries the mapping relationship between the service resource API and the business process description according to the process information, determines all service resource APIs matching the process information, and then retrieves the relationship between these service resource APIs in the knowledge graph, obtains the service resource API associated with the process information, the relevant information of each service resource API and the relationship between the APIs, and automatically creates and outputs the business reference process template by reconstructing the process and adjusting the node order, so as to realize the automatic matching of the big model according to the business description semantics, thereby realizing the automatic generation of the API business chain template (i.e., the business reference process template).

In this embodiment, the process construction can also be assisted based on the pre-trained big model and the constructed knowledge graph. In this scenario, the user is required to input the business description information. The business description information is used to indicate the business requirements, the functions to be implemented by the process to be built, and other information. The digital government operating system inputs the business description information entered by the user into the process prediction big model. The process prediction big model performs semantic analysis on the business description information and searches the knowledge graph to generate and output a business reference process template. The digital government operating system displays the business reference process template output by the process prediction big model to the user. The user checks whether the business reference process template can meet his or her own needs, and can adjust the business reference process template if it cannot. The digital government operating system generates a business service process and corresponding service process files and parameter forms based on the business reference process template adjusted by the user.

In this embodiment, by using a large model and knowledge graph to generate a business reference process template to assist users in building business service processes, the difficulty of service process orchestration is simplified, the time consumption of manual event sorting is reduced, and the efficiency of process construction is improved.

The exemplary embodiment of the present disclosure also provides an electronic device, comprising: at least one processor; and a memory connected to the at least one processor in communication. The memory stores a computer program that can be executed by the at least one processor, and when the computer program is executed by the at least one processor, the electronic device executes the method for constructing a service flow according to the embodiment of the present disclosure.

The exemplary embodiments of the present disclosure also provide a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to execute a method for constructing a service flow according to an embodiment of the present disclosure.

The exemplary embodiments of the present disclosure further provide a computer program product, including a computer program, wherein when the computer program is executed by a processor of a computer, the computer is used to enable the computer to execute the method for constructing a service flow according to the embodiment of the present disclosure.

The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, implements the functions/operations specified in the flow chart and/or block diagram. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

As used in this disclosure, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and/or data to a programmable processor.

To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

A computer system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.

Claims (10)

1. A digital government operating system, comprising: a resource management module and a task management module;

The resource management module is used for generating a business service flow and a service flow file and a parameter form corresponding to the business service flow according to a service resource API selected by a user, wherein one service resource API is used as one service flow node in the business service flow, and the service flow file records the node information of each service flow node in the business service flow and the sequence relation between the service flow nodes;

And the task management module is used for acquiring API calling parameters filled in the parameter form by the user when the user calls the business service flow, and calling a service resource API based on the API calling parameters and the service flow file.

2. The digital government operating system of claim 1 wherein said resource management module is further operative to:

After receiving the flow creation request, adding a service start node into the canvas;

Acquiring an adding sequence of the service resource API in response to receiving an adding operation of the user dragging the service resource API to the canvas;

After receiving the flow ending instruction, generating the business service flow and the corresponding service flow file according to the service starting node, the adding sequence of the service resource API and the service ending node, and generating a parameter form according to the service resource API.

3. The digital government operating system of claim 1 wherein said resource management module is further operative to:

Receiving the service description information input by the user;

inputting the service description information into a pre-trained flow prediction large model, generating a service reference flow template by the flow prediction large model according to the service description information and a preset knowledge graph, and outputting the service reference flow template;

and generating a business service flow and a corresponding service flow file and a parameter form according to the adjustment operation of the user on the business reference flow template.

4. The digital government operating system of claim 1 wherein,

The resource management module is further configured to: releasing the business service flow for the user to call;

The task management module is further configured to: responding to the click operation of a user on a target business service flow in a release state, acquiring a target parameter form corresponding to the target business service flow, and displaying the target parameter form to the user so as to fill in the target parameter form by the user; and responding to the received flow call request of the target business service flow, and calling a service resource API based on the API call parameters filled in the target parameter list and the service flow file corresponding to the target business service flow.

5. The digital government operating system of any of claims 1-4, further comprising: a process management module;

the process management module is used for tracking the calling information of each service resource API in the business service flow in the calling process of the business service flow, generating a business calling log according to the calling information of each service resource API after the business service flow is called, and sending the business calling log to the centralized log correlation system.

6. A method for constructing a service flow, applied to the digital government operating system according to any one of claims 1-5, the method comprising:

Acquiring a service resource API selected by a user through an operation page of the digital government operation system, taking one service resource API as a service flow node, and generating a business service flow, a service flow file and a parameter form corresponding to the business service flow, wherein the service flow file records the node information of each service flow node in the business service flow and the sequence relation between the service flow nodes;

When the user calls the business service flow, acquiring API call parameters filled in the parameter form by the user;

and calling a service resource API based on the API calling parameter and the service flow file.

7. The method for constructing a service flow according to claim 6, wherein the method further comprises:

Receiving the service description information input by the user;

inputting the service description information into a pre-trained flow prediction large model, generating a service reference flow template by the flow prediction large model according to the service description information and a preset knowledge graph, and outputting the service reference flow template;

and generating a business service flow and a corresponding service flow file and a parameter form according to the adjustment operation of the user on the business reference flow template.

8. The method for constructing a service flow according to claim 6, wherein the step of obtaining the service resource API selected by the user through the operation page of the digital government operating system, using one of the service resource APIs as a service flow node, and generating a business service flow and a service flow file and a parameter form corresponding to the business service flow includes:

After receiving the flow creation request, adding a service start node into the canvas;

Acquiring an adding sequence of the service resource API in response to receiving an adding operation of the user dragging the service resource API to the canvas;

After receiving the flow ending instruction, generating the business service flow and the corresponding service flow file according to the service starting node, the adding sequence of the service resource API and the service ending node, and generating a parameter form according to the service resource API.

9. An electronic device, comprising:

a processor; and

A memory in which a program is stored,

Wherein the program comprises instructions which, when executed by the processor, cause the processor to perform the method of constructing a service flow according to any one of claims 6-8.

10. A non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the construction method of the service flow according to any one of claims 6 to 8.