WO2023029509A1

WO2023029509A1 - Dynamic service publishing method and apparatus, and electronic device and storage medium

Info

Publication number: WO2023029509A1
Application number: PCT/CN2022/087814
Authority: WO
Inventors: 秦露光
Original assignee: 康键信息技术（深圳）有限公司
Priority date: 2021-08-30
Filing date: 2022-04-20
Publication date: 2023-03-09
Also published as: CN113704665B; CN113704665A

Abstract

The present method relates to the field of Internet development, and further relates to the field of artificial intelligence. Disclosed is a dynamic service publishing method, comprising: receiving a service publishing request transmitted by a client, querying service data of the service publishing request, and recognizing a service function of the service publishing request (S1); calling a functional component that runs the service function, recognizing a flow relationship of the functional component, creating a publishing node of the service publishing request according to the flow relationship and the functional component, and constructing a publishing template of the service publishing request in the publishing node (S2); loading the service data into the publishing template, so as to generate a publishing file of the service publishing request (S3); and uploading the publishing file to a server which corresponds to the client, so as to execute the service publishing of the service publishing request by using the server (S4). In addition, a service publishing request may be a medical service publishing request. By means of the present method, the dynamic service publishing can be realized, thereby improving the efficiency of service publishing.

Description

Dynamic service publishing method, device, electronic device and storage medium

This application claims the priority of the Chinese patent application with the application number 202111000944.5 filed on August 30, 2021, and the title of the invention is "Dynamic Service Publishing Method, Device, Electronic Equipment, and Storage Medium", the entire content of which is incorporated by reference incorporated in this application.

technical field

The present application relates to the field of Internet development, and in particular to a dynamic service publishing method, device, electronic equipment and computer-readable storage medium.

Background technique

Service publishing can be understood as publishing the data resource service of the business provider to a local or remote server, and meeting resource sharing needs in the form of a Web network. Common services include order query service, page search service, and information query service.

At present, service publishing is usually to compile the program code of the service to be released by the developer, and release the compiled program code to the server to realize the data sharing of the service to be released, but the inventor realizes that publishing the service in this way will involve A complete set of complex processes (such as pre-forwarding load balancing, domain name application, system construction, monitoring configuration, etc.), when there are a large number of services to be released, it is necessary to configure the process of the services to be released one by one, which will lead to service release. less efficient.

technical solution

In order to achieve the above purpose, this application provides a method for publishing dynamic services, including:

Receive the service release request transmitted by the client, query the service data of the service release request, and identify the service function of the service release request;

Invoking the functional component that runs the service function, and identifying the flow relationship of the functional component, creating the publishing node of the service publishing request according to the process relationship and the functional component, and constructing the publishing node in the publishing node release template for the service release request;

Loading the service data into the release template to generate a release file of the service release request;

uploading the release file to the server corresponding to the client, so as to execute the service release requested by the service release through the server.

The present application also provides a dynamic service release device, which includes:

The service request preprocessing module is used to receive the service release request transmitted by the client, query the service data of the service release request, and identify the service function of the service release request;

A release template generation module, configured to call the functional components that run the service functions, identify the flow relationship of the functional components, create a release node for the service release request according to the process relationship and the functional components, and Constructing a publishing template of the service publishing request in the publishing node;

a release file generation module, configured to load the service data into the release template to generate a release file for the service release request;

A service release module, configured to upload the release file to a server corresponding to the client, so as to execute the service release requested by the service release through the server.

The present application also provides an electronic device, the electronic device comprising:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to implement the dynamic service publishing method as follows:

The present application also provides a computer-readable storage medium, wherein at least one computer program is stored in the computer-readable storage medium, and the at least one computer program is executed by a processor in an electronic device to implement dynamic service publication as described below method:

Description of drawings

FIG. 1 is a schematic flowchart of a dynamic service publishing method provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of modules of a dynamic service release device provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of the internal structure of an electronic device implementing a method for publishing a dynamic service provided by an embodiment of the present application;

The realization, functional features and advantages of the present application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Embodiments of the present invention

It should be understood that the specific embodiments described here are only used to explain the present application, and are not intended to limit the present application.

An embodiment of the present application provides a method for publishing a dynamic service. The execution subject of the dynamic service publishing method includes but is not limited to at least one of electronic devices such as a server and a terminal that can be configured to execute the method provided by the embodiment of the present application. In other words, the dynamic service publishing method can be executed by software or hardware installed on the terminal device or server device, and the software can be a block chain platform. The server includes, but is not limited to: a single server, a server cluster, a cloud server or a cloud server cluster, and the like. The server can be an independent server, or it can provide cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, content distribution network (ContentDelivery Network) , CDN), and cloud servers for basic cloud computing services such as big data and artificial intelligence platforms.

Furthermore, a method for publishing dynamic services provided by the present application can be used in many general-purpose or special-purpose computer system environments or configurations, such as: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, Microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like. A dynamic service publishing method of the present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules, generally, the program modules include routines that perform specific tasks or implement specific abstract data types, The programs, objects, components, data structures, etc., can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. Wherein, in the distributed computing environment, the program modules may be located in local and remote computer storage media including storage devices.

Referring to FIG. 1 , it is a schematic flowchart of a method for publishing a dynamic service provided by an embodiment of the present application. In the embodiment of this application, the dynamic service publishing method includes:

S1. Receive a service release request transmitted by a client, query service data of the service release request, and identify a service function of the service release request.

The client (Client), or client, refers to a program that corresponds to the server and provides local services for the client. In this application, the client is used to transmit a service release request to the server to realize service delivery. Publishing, the service publishing request is generated based on different user needs, such as user A's demand for publishing information query service, and user B's demand for publishing order query service.

It should be understood that there will be corresponding service data and service functions in the service publishing request to ensure the normal access of the subsequently released services. The service data refers to the application data that loads the service publishing request, such as page data , configuration data, etc., and the service function refers to an access function for implementing the service release request, such as a data query function, a data interaction function, and the like.

As an embodiment of the present application, the querying the service data of the service release request includes: obtaining the service object of the service release request and the requirement document of the service release request, and converting the service object into an object field, and query the service data of the object field from the requirement document.

Wherein, the service object refers to the page object that needs to be loaded in the service publishing request, such as page elements, page forms, etc., and the requirement document refers to the configuration file constructed before publishing the service, which can represent the service The data resources required for publishing the request, such as system architecture, compilation environment, etc. Optionally, the service data query of the object field can be implemented through query statements, such as SQL statements.

As an embodiment of the present application, the identifying the service function of the service publishing request includes: querying the service event of the service publishing request according to the service object of the service publishing request, and identifying the publishing effect of the service event , and use the release effect as the service function of the service release request.

Wherein, the service event is used to characterize the service type existing in the service release request, such as login event, verification event, etc., and the release effect can be understood as the effect that can be achieved when the service event goes online, If the publishing effect of the verification event can be to verify the legitimacy of the user identity, then the service function of the verification event can be user identity verification.

Based on the acquisition of the service data and service functions, it can be guaranteed that the subsequent service release request corresponds to the access premise of the service to be released.

S2. Invoking the functional component that runs the service function, and identifying the flow relationship of the functional component, creating a publishing node for the service publishing request according to the process relationship and the functional component, and in the publishing node A publishing template of the service publishing request is constructed.

In the embodiment of the present application, the functional component refers to the running component used to guarantee the service function. If the service function is a data asynchronous processing function, then the functional component of the data asynchronous processing function can be an MQ component. If the service function is an interface call function, then the functional component of the interface call function can be a Dubbo component, and the transfer relationship refers to the sequence to be followed when the service is launched in the called function components, such as the MQ component and the Dubbo component The transfer relationship can be as follows: the interface call of the Dubbo component is called first, and then the data of the MQ component is asynchronously processed.

Optionally, the invocation of the functional component can be obtained by accessing the open-source database of the functional component through the URL address, and the creation of the publishing node of the service publishing request can be implemented in a streaming form. The publishing node can be understood as a working node that loads the service publishing request, such as a page configuration node, an interface calling node, and a gateway node. Further, the embodiment of the present application establishes the publishing node of the service publishing request to determine The operation process of the service function in the service release request described later.

As an embodiment of the present application, the calling the functional component running the service function includes: obtaining the address of the external system running the service function, and identifying the interface of the external system running the service function, according to the The address of the external system is used to call the external system interface to obtain the functional component running the service function.

Wherein, the external system address refers to the URL address where the functional component exists, and the external system interface refers to the connection entry provided by the external system to the third-party platform to call the functional component, such as an API interface. Optionally, the calling of the external system interface may be implemented through a window function.

As an embodiment of the present application, the identification of the flow relationship of the functional components includes: acquiring the functional attributes of the functional components, determining the dependency relationship of the functional components according to the functional attributes, and The relationship serves as the flow relationship of the functional components.

Wherein, the functional attribute refers to the functional information used to characterize the functional component. According to the functional attribute, the dependency relationship between the functional components can be clarified, and the dependency relationship includes a parallel relationship, an inclusion relationship, and a dependency relationship. .

Further, in the embodiment of the present application, the creating the publishing node of the service release request according to the process relationship and the functional components includes: connecting the functional components in series according to the process relationship to obtain the The workflow node of the functional component is used as the publishing node of the service publishing request. Wherein, the series connection of the functional components can be compiled by scripting language, such as JavaScript scripting language.

Further, in the embodiment of the present application, by constructing the publishing template of the service publishing request in the publishing node to determine the loading method and loading rules of the service data in the service publishing request, it is possible to make the publishing with the same underlying logic code Services use the same set of publishing templates, reducing the underlying logic configuration of multiple publishing services and improving service publishing efficiency.

As an embodiment of the present application, the constructing the publishing template of the service publishing request in the publishing node includes: defining the publishing logic and publishing method of the service publishing request in the publishing node, according to the The publishing logic and the publishing method create a publishing template of the service publishing request on the publishing node.

Wherein, the publishing logic refers to the data rule that the service data needs to follow when publishing, and the publishing method refers to the method adopted when the service data is released.

In the embodiment of this application, the release logic is set based on different business scenarios. For example, in the login release node, the release logic can be set as follows: the user's login password must be in three different combinations, and the password length must be greater than ten digits , the publishing method includes stopping immediately when an error occurs and continuing publishing without stopping when an error occurs, and the creation of the publishing template can be compiled by Java language.

S3. Load the service data into the publishing template to generate a publishing file of the service publishing request.

It should be understood that there are only publishing rules (publishing logic and publishing methods) and publishing nodes of the service publishing request in the publishing template, and there is no specific publishing data. Therefore, the embodiment of the present application uses the service data Loaded into the release template to generate the release file of the service release request, so as to ensure the online access of the subsequent service release request corresponding to the service to be released.

As an embodiment of the present application, the loading of the service data into the publishing template to generate the publishing file of the service publishing request includes: combining the service data with the publishing node in the publishing template Matching is performed, and a preset loading function is used to transmit the successfully matched service data to the publishing node, so as to obtain the publishing file of the service publishing request.

Wherein, the matching between the service data and the publishing nodes in the publishing template can be realized through a character matching algorithm, such as a naive algorithm, and the preset loading function can be a load() function.

Further, in the embodiment of the present application, the published file can be stored in the BPMN file format, so as to realize the visual display of the published file and help users better update or modify the data in the published file.

Further, in order to ensure the privacy and security of the published files, the published files can also be stored in a block chain node.

S4. Upload the release file to the server corresponding to the client, so as to execute the service release requested by the service release through the server.

In this embodiment of the present application, by uploading the release file to the server corresponding to the client to execute the release of the service corresponding to the service release request, the data access and data sharing of the service to be released in the service release request can be realized. Optionally, the uploading of the release file may be implemented through a release machine, such as a Tomcat machine.

It should be noted that, in this embodiment of the application, the service release request may be a medical service release request, and the medical service release request may be an online medical appointment registration release request, an online medical consultation release request, and an online medical payment payment request. post requests etc.

It can be seen that this application can firstly identify the service data and service functions of the service release request transmitted by the client to ensure that the subsequent service release request corresponds to the access premise of the service to be released, and create the service release request in combination with the service function The release node of the service release request can determine the operation process of the service function in the subsequent service release request, and construct the release template of the service release request in the release node, and can determine the loading method and the method of service data in the service release request. The loading rules can make publishing services with the same underlying logic code use the same set of publishing templates, reduce the underlying logic configuration of multiple publishing services, and improve service publishing efficiency; secondly, the embodiment of this application loads the service data into the publishing In the template, the release file of the service release request is generated, and the release file is uploaded to the server corresponding to the client to execute the service release of the service release request, which can realize that the service release request corresponds to the service to be released online access, so that the data access and data sharing of the service to be released requested by the service release can be realized. Therefore, a dynamic service release method proposed in this application can realize the dynamic release of services and improve the efficiency of service release.

As shown in FIG. 2 , it is a functional block diagram of the dynamic service release device of the present application.

The dynamic service publishing apparatus 100 described in this application can be installed in an electronic device. According to the realized functions, the dynamic service publishing apparatus may include a service request preprocessing module 101 , a publishing template generating module 102 , a publishing file generating module 103 and a service publishing module 104 . The module described in this application can also be called a unit, which refers to a series of computer program segments that can be executed by the processor of the electronic device and can complete fixed functions, and are stored in the memory of the electronic device.

In this embodiment, the functions of each module/unit are as follows:

The service request preprocessing module 101 is configured to receive a service release request transmitted by a client, query service data of the service release request, and identify a service function of the service release request.

As an embodiment of the present application, the querying of the service data of the service publishing request is performed by the service request preprocessing module 101 in the following manner: obtaining the service object of the service publishing request, and the service object of the service publishing request convert the service object into an object field, and query the service data of the object field from the requirement document.

As an embodiment of the present application, the service function of identifying the service publishing request is executed by the service request preprocessing module 101 in the following manner: querying the service publishing request according to the service object of the service publishing request The service event of the service event, identifying the publishing effect of the service event, and using the publishing effect as the service function of the service publishing request.

The release template generating module 102 is configured to call the functional components that run the service functions, identify the flow relationship of the functional components, and create the release node of the service release request according to the process relationship and the functional components , and construct the publishing template of the service publishing request in the publishing node.

As an embodiment of the present application, when calling the functional component that runs the service function, the publishing template generation module 102 executes in the following manner: obtain the address of the external system that runs the service function, and identify the function component that runs the service function The external system interface of the service function is called, and the external system interface is called according to the external system address to obtain the functional component running the service function.

As an embodiment of the present application, the identifying the flow relationship of the functional components, the release template generating module 102 executes in the following manner: acquire the functional attributes of the functional components, and determine the The dependency relationship of the functional components is used as the flow relationship of the functional components.

Further, in the embodiment of the present application, the publishing node of the service publishing request is created according to the process relationship and the functional components, and the publishing template generation module 102 is executed in the following manner: according to the process relationship , connecting the functional components in series to obtain a workflow node of the functional component, and using the workflow node as an issuing node of the service publishing request. Wherein, the series connection of the functional components can be compiled by scripting language, such as JavaScript scripting language.

As an embodiment of the present application, the publishing template of the service publishing request is constructed in the publishing node, and the publishing template generation module 102 is executed in the following manner: defining the service publishing in the publishing node The release logic and release method of the request, according to the release logic and the release method, create the release template of the service release request on the release node.

The release file generating module 103 is configured to load the service data into the release template, so as to generate the release file of the service release request.

As an embodiment of the present application, the loading of the service data into the release template to generate the release file of the service release request, the release file generation module 103 is executed in the following manner: the The service data is matched with the publishing nodes in the publishing template, and the service data that is successfully matched is transmitted to the publishing node by using a preset loading function, so as to obtain the publishing file of the service publishing request.

The service release module 104 is configured to upload the release file to a server corresponding to the client, so as to execute the service release requested by the service release through the server.

It can be seen that this application can firstly identify the service data and service functions of the service release request transmitted by the client to ensure that the subsequent service release request corresponds to the access premise of the service to be released, and create the service release request in combination with the service function The release node of the service release request can determine the operation process of the service function in the subsequent service release request, and construct the release template of the service release request in the release node, and can determine the loading method and the method of service data in the service release request. The loading rules can make publishing services with the same underlying logic code use the same set of publishing templates, reduce the underlying logic configuration of multiple publishing services, and improve service publishing efficiency; secondly, the embodiment of this application loads the service data into the publishing In the template, the release file of the service release request is generated, and the release file is uploaded to the server corresponding to the client to execute the service release of the service release request, which can realize that the service release request corresponds to the service to be released online access, so that the data access and data sharing of the service to be released requested by the service release can be realized. Therefore, the device for publishing a dynamic service proposed in this application can realize the dynamic publishing of services and improve the efficiency of service publishing.

As shown in FIG. 3 , it is a schematic structural diagram of an electronic device 1 implementing a method for publishing a dynamic service in the present application.

The electronic device 1 may include a processor 10, a memory 11, a communication bus 12, and a communication interface 13, and may also include a computer program stored in the memory 11 and operable on the processor 10, such as a dynamic service publishing program.

Wherein, the processor 10 may be composed of integrated circuits in some embodiments, for example, may be composed of a single packaged integrated circuit, or may be composed of multiple integrated circuits with the same function or different functions packaged, including one or A combination of multiple central processing units (Central Processing unit, CPU), microprocessors, digital processing chips, graphics processors and various control chips, etc. The processor 10 is the control core (Control Unit) of the electronic device 1, and uses various interfaces and lines to connect various components of the entire electronic device 1, and runs or executes programs or modules stored in the memory 11 ( For example, executing a dynamic service publishing program, etc.), and calling the data stored in the memory 11 to execute various functions of the electronic device 1 and process data.

The memory 11 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (for example: SD or DX memory, etc.), magnetic memory, magnetic disk, optical disk, etc. , the computer-readable storage medium may be non-volatile or volatile. The storage 11 may be an internal storage unit of the electronic device 1 in some embodiments, such as a mobile hard disk of the electronic device 1 . The memory 11 can also be an external storage device of the electronic device 1 in other embodiments, such as a plug-in mobile hard disk equipped on the electronic device 1, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital , SD) card, flash memory card (Flash Card), etc. Further, the memory 11 may also include both an internal storage unit of the electronic device 1 and an external storage device. The memory 11 can not only be used to store application software and various data installed in the electronic device 1 , such as the code of the dynamic service publishing program, but also can be used to temporarily store data that has been output or will be output.

The communication bus 12 may be a peripheral component interconnection standard (peripheral component interconnect (PCI) bus or extended industry standard structure (extended industry standard architecture, referred to as EISA) bus, etc. The bus can be divided into address bus, data bus, control bus and so on. The bus is configured to realize connection and communication between the memory 11 and at least one processor 10 and the like.

The communication interface 13 is used for communication between the electronic device 1 and other devices, including a network interface and an employee interface. Optionally, the network interface may include a wired interface and/or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which are generally used to establish a communication connection between the electronic device 1 and other electronic devices 1 . The employee interface may be a display (Display) or an input unit (such as a keyboard (Keyboard)). Optionally, the employee interface may also be a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode, organic light-emitting diode) touch device, and the like. Wherein, the display may also be appropriately called a display screen or a display unit, and is used for displaying information processed in the electronic device 1 and for displaying a visualized employee interface.

Figure 3 only shows an electronic device 1 with components, and those skilled in the art can understand that the structure shown in Figure 3 does not constitute a limitation to the electronic device 1, and may include fewer or more components than those shown in the illustration. components, or combinations of certain components, or different arrangements of components.

For example, although not shown, the electronic device 1 may also include a power supply (such as a battery) for supplying power to various components. Preferably, the power supply may be logically connected to the at least one processor 10 through a power management device, so that through power management The device implements functions such as charge management, discharge management, and power consumption management. The power supply may also include one or more DC or AC power supplies, recharging devices, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components. The electronic device 1 may also include various sensors, bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

It should be understood that the embodiments are only for illustration, and are not limited by the structure in the scope of the patented invention.

The dynamic service publishing program stored in the memory 11 in the electronic device 1 is a combination of multiple computer programs, and when running in the processor 10, it can realize:

Specifically, for a specific implementation method of the above computer program by the processor 10, reference may be made to the description of relevant steps in the embodiment corresponding to FIG. 1 , and details are not repeated here.

Further, if the integrated modules/units of the electronic device 1 are realized in the form of software function units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium. The computer-readable storage medium may be volatile or non-volatile. For example, the computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, removable hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory).

The present application also provides a computer-readable storage medium, the readable storage medium stores a computer program, and when the computer program is executed by the processor of the electronic device 1, it can realize:

In the several embodiments provided in this application, it should be understood that the disclosed devices, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules is only a logical function division, and there may be other division methods in actual implementation.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software function modules.

It will be apparent to those skilled in the art that the present application is not limited to the details of the exemplary embodiments described above, but that the present application can be implemented in other specific forms without departing from the spirit or essential characteristics of the present application.

Therefore, the embodiments should be regarded as exemplary and not restrictive in all points of view, and the scope of the application is defined by the appended claims rather than the foregoing description, and it is intended that the scope of the present application be defined by the appended claims rather than by the foregoing description. All changes within the meaning and range of equivalents of the elements are embraced in this application. Any reference sign in a claim should not be construed as limiting the claim concerned.

The blockchain referred to in this application is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain (Blockchain), essentially a decentralized database, is a series of data blocks associated with each other using cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify its Validity of information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

The embodiments of the present application may acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results. .

In addition, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or devices stated in the system claims may also be realized by one unit or device through software or hardware. Secondary terms are used to denote names without implying any particular order.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application without limitation. Although the present application has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present application can be Make modifications or equivalent replacements without departing from the spirit and scope of the technical solutions of the present application.

Claims

A method for publishing a dynamic service, wherein the method includes:

Receive the service release request transmitted by the client, query the service data of the service release request, and identify the service function of the service release request;

Invoking the functional component that runs the service function, and identifying the flow relationship of the functional component, creating the publishing node of the service publishing request according to the process relationship and the functional component, and constructing the publishing node in the publishing node release template for the service release request;

Loading the service data into the release template to generate a release file of the service release request;

uploading the release file to the server corresponding to the client, so as to execute the service release requested by the service release through the server.
The dynamic service release method according to claim 1, wherein said querying the service data of the service release request comprises:

Obtaining the service object of the service release request and the requirement document of the service release request;

The service object is converted into an object field, and the service data of the object field is queried from the requirement document.
The dynamic service publishing method according to claim 1, wherein said identifying the service function of said service publishing request comprises:

Querying the service event of the service publishing request according to the service object of the service publishing request;

A publishing effect of the service event is identified, and the publishing effect is used as a service function of the service publishing request.
The method for publishing dynamic services according to claim 1, wherein said invoking a functional component running said service function comprises:

Obtaining the address of the external system running the service function, and identifying the interface of the external system running the service function;

According to the external system address, the external system interface is invoked to obtain a functional component running the service function.
The dynamic service publishing method according to claim 1, wherein said creating the publishing node of the service publishing request according to the process relationship and the functional components comprises:

According to the process relationship, the functional components are connected in series to obtain a workflow node of the functional component, and the workflow node is used as the publishing node of the service publishing request.
The method for publishing a dynamic service according to any one of claims 1 to 5, wherein said constructing the publishing template of said service publishing request in said publishing node includes:

Define the release logic and release method of the service release request in the release node;

Create a publishing template of the service publishing request on the publishing node according to the publishing logic and the publishing method.
The dynamic service publishing method according to claim 6, wherein said loading said service data into said publishing template to generate a publishing file of said service publishing request comprises:

matching the service data with the release nodes in the release template;

The service data that is successfully matched is transmitted to the publishing node by using a preset loading function, so as to obtain the publishing file of the service publishing request.
A device for publishing dynamic services, wherein the device includes:

The service request preprocessing module is used to receive the service release request transmitted by the client, query the service data of the service release request, and identify the service function of the service release request;

A release template generation module, configured to call the functional components that run the service functions, identify the flow relationship of the functional components, create a release node for the service release request according to the process relationship and the functional components, and Constructing a publishing template of the service publishing request in the publishing node;

a release file generation module, configured to load the service data into the release template to generate a release file for the service release request;

A service release module, configured to upload the release file to a server corresponding to the client, so as to execute the service release requested by the service release through the server.
An electronic device, wherein the electronic device includes:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores a computer program executable by the at least one processor, the computer program is executed by the at least one processor, so that the at least one processor can execute the dynamic service publishing method as follows:

Receive the service release request transmitted by the client, query the service data of the service release request, and identify the service function of the service release request;

Invoking the functional component that runs the service function, and identifying the flow relationship of the functional component, creating the publishing node of the service publishing request according to the process relationship and the functional component, and constructing the publishing node in the publishing node release template for the service release request;

Loading the service data into the release template to generate a release file of the service release request;

uploading the release file to the server corresponding to the client, so as to execute the service release requested by the service release through the server.
The electronic device according to claim 9, wherein the querying the service data of the service publication request comprises:

Obtaining the service object of the service release request and the requirement document of the service release request;

The service object is converted into an object field, and the service data of the object field is queried from the requirement document.
The electronic device according to claim 9, wherein the service function for identifying the service publishing request comprises:

Querying the service event of the service publishing request according to the service object of the service publishing request;

A publishing effect of the service event is identified, and the publishing effect is used as a service function of the service publishing request.
The electronic device according to claim 9, wherein said invoking a functional component for running said service function comprises:

Obtaining the address of the external system running the service function, and identifying the interface of the external system running the service function;

According to the external system address, the external system interface is invoked to obtain a functional component running the service function.
The electronic device according to claim 9, wherein, according to the process relationship and the functional components, creating the publishing node of the service publishing request comprises:

According to the process relationship, the functional components are connected in series to obtain a workflow node of the functional component, and the workflow node is used as the publishing node of the service publishing request.
The electronic device according to claim 9, wherein said constructing the release template of the service release request in the release node comprises:

Define the release logic and release method of the service release request in the release node;

Create a publishing template of the service publishing request on the publishing node according to the publishing logic and the publishing method.
A computer-readable storage medium, storing a computer program, wherein, when the computer program is executed by a processor, the following dynamic service publishing method is implemented:

Receive the service release request transmitted by the client, query the service data of the service release request, and identify the service function of the service release request;

Invoking the functional component that runs the service function, and identifying the flow relationship of the functional component, creating the publishing node of the service publishing request according to the process relationship and the functional component, and constructing the publishing node in the publishing node release template for the service release request;

Loading the service data into the release template to generate a release file of the service release request;

uploading the release file to the server corresponding to the client, so as to execute the service release requested by the service release through the server.
The computer-readable storage medium according to claim 15, wherein the querying the service data of the service publishing request comprises:

Obtaining the service object of the service release request and the requirement document of the service release request;

The service object is converted into an object field, and the service data of the object field is queried from the requirement document.
The computer-readable storage medium of claim 15, wherein the service function identifying the service publication request comprises:

Querying the service event of the service publishing request according to the service object of the service publishing request;

A publishing effect of the service event is identified, and the publishing effect is used as a service function of the service publishing request.
The computer-readable storage medium according to claim 15, wherein said invoking a functional component running said service function comprises:

Obtaining the address of the external system running the service function, and identifying the interface of the external system running the service function;

According to the external system address, the external system interface is invoked to obtain a functional component running the service function.
The computer-readable storage medium according to claim 15, wherein, according to the process relationship and the functional components, creating the publishing node of the service publishing request comprises:

According to the process relationship, the functional components are connected in series to obtain a workflow node of the functional component, and the workflow node is used as the publishing node of the service publishing request.
The computer-readable storage medium according to claim 15, wherein said constructing the publishing template of the service publishing request in the publishing node comprises:

Define the release logic and release method of the service release request in the release node;

Create a publishing template of the service publishing request on the publishing node according to the publishing logic and the publishing method.