CN107038042B

CN107038042B - Service execution method and device

Info

Publication number: CN107038042B
Application number: CN201710067297.7A
Authority: CN
Inventors: 孙思哲; 廉洁; 徐峥; 谢斌; 穆毅鹏
Original assignee: Alibaba Group Holding Ltd
Current assignee: Advanced New Technologies Co Ltd; Advantageous New Technologies Co Ltd
Priority date: 2017-02-07
Filing date: 2017-02-07
Publication date: 2020-08-28
Anticipated expiration: 2037-02-07
Also published as: CN107038042A

Abstract

The embodiment of the application discloses a method and a device for executing a service, wherein in the method, a client can generate a corresponding service execution request according to service operation executed by a user and send the service execution request to a server, and the server can return corresponding service execution information to the client according to the service execution request, so that the client executes the service according to the service execution information. Because the service developer does not need to perform specific configuration work on the service in the client in the service development process, the service development work can be completed only by configuring different service configuration contents set for different services in the server, the cost and time consumed in service development are greatly reduced, and the service development efficiency is improved.

Description

Service execution method and device

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for executing a service.

Background

At present, a service platform generally provides multiple services of the same type for a user, so that the user can select a service suitable for the user according to the user's own requirements, and the diversified requirements of the user on the service are met.

In practical applications, in the process of developing each service, an operation and maintenance person usually needs to develop different service contents such as different service flows and different service page layouts according to the characteristics of each service, so that each time the operation and maintenance person newly develops a service, the operation and maintenance person needs to re-develop the service contents such as the service flows and the service page layouts, and thus, a great development cost and time are consumed in the development of the service, and therefore, the problem that the development efficiency is low exists in the process of developing the service by the current operation and maintenance person, and how to effectively reduce the development cost and time of the service and improve the development efficiency of the service is a problem to be solved urgently.

Disclosure of Invention

The embodiment of the application provides a method for executing a service, which is used for solving the problems of excessive cost and time consumed by service development and low service development efficiency in the prior art.

The embodiment of the application provides a method for executing a service, which comprises the following steps:

generating a corresponding service execution request according to the service operation executed by the user;

sending the service execution request to a server so that the server returns corresponding service execution information according to the service execution request;

determining service components corresponding to the service component identifications from a preset service component library according to the service component identifications contained in the service execution information;

and executing the service according to the determined service components and the configuration information of the service components contained in the service execution information.

The embodiment of the application provides a device for executing a service, which is used for solving the problems of excessive cost and time consumed by service development and low service development efficiency in the prior art.

The embodiment of the application provides a device for executing a service, which comprises:

the generating module generates a corresponding service execution request according to the service operation executed by the user;

the sending module is used for sending the service execution request to a server so that the server returns corresponding service execution information according to the service execution request;

the determining module is used for determining the service components corresponding to the service component identifications from a preset service component library according to the service component identifications contained in the service execution information;

and the service execution module executes the service according to the determined service components and the configuration information of the service components contained in the service execution information.

receiving a service execution request sent by a client;

generating service execution information corresponding to the service execution request according to the service execution request;

and returning the service execution information to the client so that the client executes the service according to the service component corresponding to each service component identifier contained in the service execution information and each configuration information of each service component contained in the service execution information.

the receiving module is used for receiving a service execution request sent by a client;

the information generation module generates service execution information corresponding to the service execution request according to the service execution request;

and the information returning module returns the service execution information to the client so that the client executes the service according to the service component corresponding to each service component identifier contained in the service execution information and each configuration information of each service component contained in the service execution information.

The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:

in the embodiment of the present application, the client includes each service component required for service execution, and during the service execution process, the client can configure the corresponding service component according to the service execution information issued by the server, so as to perform service execution through the service components, in other words, in the service development process, a service developer does not need to arrange the actual service flow, service page, and other service contents of the service during execution in the client, but only needs to set the service component identifier and the configuration information of the service component required in the service execution process in the server, which is equivalent to that the service developer only develops the configuration information of each service component required for service execution in the server during the service development process, but does not develop the client for the service, so that during the service execution process, the server issues the service component identifications and the configuration information of the service components required in the service execution process to the client in the form of service execution information, and the client can determine the service contents such as the service flow, the service page and the like required in the service execution process according to the service execution information, so that the cost and the time of service development are greatly reduced, and the service development efficiency is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic diagram of a service execution process provided in an embodiment of the present application;

fig. 2A and 2B are schematic diagrams of two pages to be displayed in a service execution process provided in the embodiment of the present application;

fig. 3 is a schematic diagram of another service execution process provided in the embodiment of the present application;

fig. 4 is a schematic diagram of service execution between a client and a server according to an embodiment of the present application;

fig. 5 is a schematic diagram of a service execution apparatus according to an embodiment of the present application;

fig. 6 is a schematic diagram of another service execution apparatus according to an embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is a schematic diagram of a service execution process provided in an embodiment of the present application, which specifically includes the following steps:

s101: and generating a corresponding service execution request according to the service operation executed by the user.

In practical application, a client generally includes multiple services, different services generally have respective service contents such as service flows, service pages, and the like, and for the services in the client, required service components are often the same in the process of executing the services, for example, for each service in the client, before the service is executed, the service operation executed by a user may need to be pre-checked by a pre-checking component, and only the pre-checking modes of the services may be different; for another example, during the execution of these services, the password authentication component may be required to perform password authentication, and the manner of password authentication may be the same for each service; alternatively, these services may all need to show some pages during execution, and the page layout frames of the pages may all be substantially the same for each page, but the contents of the pages shown in the pages are different from each other.

As can be seen from the above description, for each service contained in the client, the execution of these services is actually similar, so in order to improve the development efficiency of the services and save the cost and time consumed by the development of the services, in the embodiment of the present application, a service developer can extract the common point of each service and develop a service component for the common point, and further configure the developed service components in the client, and the configuration information of each service component is correspondingly configured in the server, which is equivalent to configuring a set of common code execution framework (the code execution framework mentioned here is a service component) in the client, and for different services, configuring the corresponding configuration information of the service component required by the service can implement the execution of the service, and how to distinguish each service, the configuration information of each service component corresponding to each service component identifier and each service component identifier issued by the server.

Based on this, in the embodiment of the present application, since the service developer has configured each service component required by each service in the client in advance, in the process of executing the service, the client can determine the service logic code of the service by determining each service component required for executing the service and the configuration information of each service component through the service execution information returned by the server, in other words, the client can determine the service flow of the service according to the service execution information issued by the server, so that the client can execute the service according to the service flow (i.e., the service logic code).

When a client executes a service, a corresponding service execution request needs to be generated according to a service operation executed by a user, wherein when the client monitors that the user executes a specified service operation on a service page of a certain service, the client determines that the service needs to be executed, and then generates the corresponding service execution request according to a service identifier of the service. For example, when the user clicks an execution control in a service a page of the client, it is determined that the service a needs to be executed, and then a corresponding service execution request is generated according to the service identifier of the service a.

S102: and sending the service execution request to a server so that the server returns corresponding service execution information according to the service execution request.

In this embodiment of the present application, after the server generates a corresponding service execution request according to a service operation executed by a user, the server needs to send the service execution request to the server, so that the server can return corresponding service execution information to the client according to the service execution request, where the service execution information includes identifiers of service components required by the client to execute the service, and configuration information of the service components corresponding to the identifiers of the service components. The specific process of the server determining the service execution information according to the service execution request sent by the client is specifically described in the subsequent step S302.

S103: and determining the service components corresponding to the service component identifications from a preset service component library according to the service component identifications contained in the service execution information.

After receiving the service execution information returned by the server, the client can determine the service component identifications contained in the service execution information, and further determine the service components required by the client to execute the services according to the service component identifications, wherein the service components required by the services are configured in the service component library of the client in advance by service developers, so that the client can determine the service components corresponding to the service component identifications from the preset service component library according to the service component identifications contained in the service execution information.

For example, suppose that a client determines that a service a needs to be executed according to a service operation of a user, and further generates a service execution request corresponding to the service a, after the client sends the service execution request to a server, the server determines that a pre-check component, a password verification component, and a risk evaluation component are needed when the client executes the service a, so that the server can include identifiers of the three service components in service execution information and issue the service execution information to the client, and the client, in receiving the service execution information, can determine, according to the three service component identifiers included in the service execution information, that service components needed when the client executes the service a from a preset service component library are: the system comprises a pre-verification component, a password verification component and a risk evaluation component, and further executes the service A through the three service components in the subsequent process.

S104: and executing the service according to the determined service components and the configuration information of the service components contained in the service execution information.

The client determines each service component from the preset service component library, which is actually only a code frame, and if there is no code for service execution in the code frame, the client cannot support service execution, so that the client needs to configure each configuration information issued by the server into each service component, so that each service component that originally has no service execution capability has a function of executing a service.

Therefore, in the embodiment of the present application, after the client determines each service component required for executing the service through the service execution information issued by the server, the client needs to further determine the configuration information corresponding to each service component through the service execution information, and further configure each determined configuration information into each corresponding service component, so that each service component has the capability of executing the service.

In the embodiment of the present application, the configuration information not only enables each service component that originally does not have the capability of executing the service to have the service execution function, but also distinguishes the key of each service, because after the configuration information is configured to the corresponding service component, how each service component plays a role in the service execution process is determined.

For example, it is assumed that pre-check is required in the service execution process of service a and service B, that is, both services need support of a pre-check component in the service execution process, but the pre-check may further include two layers of checks, namely, user level check and user binding check, for the pre-check of service a, the user level check is required first, and then the user binding check is performed, and for the pre-check of service B, the user binding check is required first, and then the user level check is performed, which means that although the pre-check exists in the execution process of both services, the pre-check modes of both services are different, and therefore, in the embodiment of the present application, the configuration information of each service component included in the service execution information issued by the server, the specific implementation mode of each service component in the service execution process is determined, and therefore the services are distinguished.

It should be noted that, in practical applications, the service flows of different services during execution are usually different, where the service flow mentioned herein can be understood as the execution sequence of each service component during execution of the service, for example, when the service a is executed, it is necessary to perform pre-verification, then perform password verification, and finally perform risk assessment, so as to say, for the service a, the service flow of the service may be represented as: pre-verification, password verification and risk assessment, and when the service B is executed, password verification is required to be performed first, then pre-verification is performed, and finally risk assessment is performed, so for the service B, the service flow of the service can be expressed as follows: password verification-pre-verification-risk assessment.

It can be seen from the service flows of the two services that the service flows of different services in the execution process may be different, and the service flows of each service are actually determined by the service characteristics of each service, so in this embodiment of the present application, the service execution information sent by the server needs to include the sequence of each service component during service execution in addition to the service component identifier and the configuration information of each service component corresponding to each service component identifier, and the client determines the specific implementation form of a service through the sequence of each service component in the service execution information and the configuration information of each service component.

Therefore, in the application embodiment, the client needs to further determine an order of each service component included in the service execution information in the service execution process, and sort each service component configured with each configuration information according to the order to obtain the service logic code, where the service logic code mentioned here may be understood as: the service logic code represents a specific execution process of the service, and the client can implement execution of each stage of the service through the service logic code, for example, assuming that an actual service execution process of the service a is as follows: the pre-verification, the password verification and the risk assessment are performed first, so that when the client executes the business logic code of the business a, the business logic code mentioned here is equivalent to the business process mentioned above, and only the business logic code is described from the perspective of actually performing the business process at the client, and the business process is described by the execution sequence of each stage shown in the business process.

After the client obtains the service logic code, the service can be executed according to the service logic code, different service logic codes realize different service execution processes, in other words, different service logic codes realize the differentiation of different services, and the generation of the service logic code is determined by the configuration information of each service component issued by the server and the sequencing of each service component in the service execution process.

Therefore, in the embodiment of the present application, a service developer only needs to configure each service component required in a service execution process in a client and endow the client with a capability of configuring configuration information issued by a server into each service component, so as to complete the development of a service on a client level, and for the actual execution of the service, the service developer only needs to configure service execution information required by each service into the server, and when the client executes the service, the corresponding service execution information is issued to the client, so that the specific execution of the service is realized. Therefore, the development cost and time of the service are greatly saved, and the development efficiency of the service is improved.

It should be noted that, in practical applications, a page display process is usually involved in the service execution process, for example, it is assumed that, in the service a execution process, it is necessary to perform pre-verification and then password verification, and then perform page display to the user.

Although the content of the page displayed by each service is different, the essence of the page is composed of a plurality of view components, and the view components on different pages are often the same, except that the arrangement of the view components on different pages and the content rendered in each view component are different. In other words, the view components constituting each page are often uniform, but the essence of determining the difference between pages is the arrangement of the view components in each page and the page content displayed in the page.

Because the view components of each page are often unified, for the page to be displayed in the service execution process, the specific construction of the page can be usually realized according to the service execution information issued by the server, and the page to be displayed in the service execution process does not need to be constructed in advance, so that the development efficiency of the service is further improved.

Specifically, in the embodiment of the present application, the service execution information sent by the server may further include page configuration contents such as identifiers of the view components, a splicing sequence of the view components when constructing a page, and page contents to be displayed, in addition to the service configuration contents such as the service component identifiers of the service components, the sequence of the service components in the service execution process, and the configuration information of the service components described above. Therefore, when the server determines that the client needs to perform the page display in the service execution process according to the received service execution request, the server can further determine the identifiers of the view components, the splicing sequence of the view components and the content of the page to be displayed, which are required when the client displays the page, and carry the page configuration content in the service execution information and send the page configuration content to the client.

After receiving the service execution information, the client determines each view component required for constructing the page from a preset view component library through each view component identifier contained in the service execution information, and configures page contents to be displayed contained in the service execution information in each view component, wherein different view components correspond to different page contents.

After the client configures the page content to be displayed to each view component, each view component configured with the page content can be placed in a designated position of the page according to the splicing sequence of each view component included in the service execution information, so that the page is constructed and displayed, as shown in fig. 2A and 2B.

Fig. 2A and 2B are schematic diagrams of two pages to be displayed in a service execution process provided in the embodiment of the present application.

Fig. 2A shows a service introduction page of a service, where an access control enabling the client to execute the service is shown in the page, and when the user clicks the access control shown in fig. 2A, the client generates a corresponding service execution request according to the service operation executed by the user. The client can send the service execution request to the server, so that the server returns corresponding service execution information to the client according to the service execution request.

After receiving the service execution information issued by the server, the client determines that the client needs to implement the execution work of the service only through the pre-verification component and the password verification component according to the pre-verification component identifier and the password verification component identifier included in the service execution information, so that the client can call the pre-verification component and the password verification component from a preset service component library and correspondingly configure the configuration information of each service component included in the service execution information in the two service components respectively. Then, the client may sequence the pre-check components and the password check components configured with the configuration information according to the sequence of each service component included in the service execution information in the service execution process (i.e., for the service, pre-check is required first, and then password check is performed), so as to obtain the service logic code, that is, the above-mentioned service flow, and then execute the service according to the service flow (i.e., the service logic code).

When the server receives a service execution request sent by the client, it is determined that the client passes the pre-check and the password check according to the service identifier included in the service execution request, and it is determined that the user can perform service processing through the service, and the page shown in fig. 2B needs to be displayed to the user through the client, so that when the server receives the service execution request sent by the client, it is necessary to further determine the labels of the view components, the splicing sequence of the view components, and the page content to be displayed in the page shown in fig. 2B, which are required when the client displays the page shown in fig. 2B, according to the service identifier included in the service execution request, and carry the page configuration content in the service execution information and send the page configuration content to the client.

And when the client determines that the user can process the service through the service by executing the pre-verification and the password verification, the client determines corresponding view components from a preset view component library according to the view component identifiers (the service information input component identifier, the service detail display component identifier, the service rule display component identifier and the operation area component identifier) included in the service execution information issued by the server, and configures the page content included in the service execution information in the view components.

The client can further determine page content to be rendered by each view component according to the corresponding relation between each sub-page content and each view component contained in the service execution information, and then render each view component corresponding to each sub-page content.

For example, for the service detail displaying component in fig. 2B, after receiving a service execution request sent by the client, the server may determine sub-page contents to be displayed in the service detail displaying component according to a service identifier included in the service execution request, and similarly, the server may sequentially determine sub-page contents to be displayed by each view component in the same manner, and further carry a corresponding relationship between each sub-page content and each view component in service execution information issued to the client.

After receiving the service execution information sent by the server, the client may configure each part of the page content included in the service execution information in each corresponding view component for rendering according to the corresponding relationship between each view component and each sub-page content included in the service execution information, so as to obtain the page shown in fig. 2B.

It should be noted that the pre-verification and the password verification mentioned in the above example are performed by the client in the background, the user cannot see the verification processes, and the user actually sees the page shown in fig. 2B in the process of executing the service, so for the above example, the pre-verification, the password verification and the page display form a service flow of the service, and the client can perform the execution of the service according to the service flow.

It can be seen from the above method that, because the client pre-stores the service components and the view components required for executing the service, no matter the process of the service is constructed and the page displayed in the service execution process is constructed, the client can construct the corresponding service process and service page for different services through the pre-stored service components and view components only according to the service execution information issued by the server, the service developer does not need to perform specific configuration work on the service in the client in the service development process, but extracts common points (i.e. the service components and the view components) of each service, configures the common points in the service in the client in the form of the service components and the view components in the client, and then only needs to combine the service components and the view components in the client according to the configuration information configured in the server for each service in advance, different services can be formed, so that the cost and time consumed during service development are greatly reduced, and the service development efficiency is improved.

Since the service developer configures the configuration information corresponding to each service in the server in advance, when the server receives a service execution request sent by the client, according to the service identifier included in the service execution request, it needs to determine each service component identifier corresponding to the service identifier, each view component identifier, the sequence of each service component during service execution, the splicing sequence of each view component in the page, the content of the page to be displayed, and the configuration information of each service component, and further carry the service configuration content and the page configuration content in the service execution information, so that the client can perform service execution through the service execution information. To further explain the business implementation process of the present application, the present application will be described in detail below from the perspective of a server.

Fig. 3 is a schematic diagram of another service execution process provided in the embodiment of the present application, which specifically includes the following steps:

s301: receiving a service execution request sent by a client, wherein the service execution request is used for the client to acquire service execution information required by service execution.

When a user executes a service operation in a client, for example, clicking an access control shown in fig. 2A, the client generates a corresponding service execution request according to the service operation executed by the user, and then sends the service execution request to a server, and after receiving the service execution request sent by the client, the server can issue service execution information required by the client to the client in a subsequent process, so that the client can execute the service through the service execution information.

S302: and generating service execution information corresponding to the service execution request.

For each service, different services have respective service logic, service flow and service page, so that when a service developer develops the service, the service developer needs to configure different service component identifiers, configuration information corresponding to the service components, service configuration contents such as page contents and the like and page configuration contents in the server, so that the server can subsequently issue corresponding service configuration contents and page configuration contents to the client after receiving a service execution request sent by the client.

Therefore, after receiving a service execution request sent by the client, the server can determine, according to the service identifier included in the service execution request, a service component identifier matched with the service identifier, a sequence of each service component in a service execution process, and configuration information of each service component, and further generate corresponding service execution information according to the service configuration contents.

For example, after receiving a service execution request sent by a client, a server may determine that the service execution request includes a service identifier of a service a, and further determine a pre-verification component identifier, a password verification component identifier, and a risk assessment component identifier that are required by the service a in an execution process, where the service components respectively correspond to configuration information, and the service components are according to the following steps in the execution process of the service a: the pre-verification, risk evaluation and password verification are carried out in sequence, so that the server can generate corresponding service execution information according to the determined service configuration content aiming at the service A.

In this embodiment of the application, when the server determines that the client needs to show an assigned page to the user in the process of executing the service according to the service execution request sent by the client, the server may further determine, according to the service identifier included in the service execution request, identifiers of view components corresponding to the service identifier, a splicing sequence of the view components in the page, and page content to be shown in the page, and send the page configuration content to the client with the service execution information, so that the client may execute the service according to the service execution information sent by the server, and show the page to the user in the process of executing the service.

S303: and returning the service execution information to the client so that the client executes the service according to the service component corresponding to each service component identifier contained in the service execution information and each configuration information of each service component contained in the service execution information.

After the server generates corresponding service execution information according to the service execution request sent by the client, the server can return the service execution information to the client, so that the client generates a corresponding service flow and a service page according to the service execution information, and executes the service according to the service flow. The process of performing the service by the client according to the service execution information sent by the server is specifically referred to the contents in the above steps S103 to S104, and is not described in detail herein.

It should be noted that, in the step S302, after receiving the service execution request sent by the client, the server may need to perform corresponding service execution processing on the service execution request, and carry the obtained service execution result in the service execution information and send the service execution result to the client.

For example, in fig. 2B, when a user inputs a piece of service information in a service information input interface (i.e., an interface corresponding to a service information input component), and clicks a certain execution, the client generates a corresponding service execution request according to the specified operation executed by the user, and sends the service execution request to the server. After receiving the service execution request sent by the client, the server needs to perform service execution processing on the service execution request and obtain a service execution result, and then the server needs to carry the service execution result in the service execution information, so that after receiving the service execution information, the client displays the service execution result as page content in a corresponding page, where a construction process of the page is the same as the manner in the step S104, and details are not described here.

In practical application, different businesses have different business processing modes, for example, in financial management, transaction processing modes of financial products such as funds, gold, futures and the like have certain differences, so different transaction systems need to be set for different financial products, when a server receives a financial transaction request sent by a user through a client, a transaction system matched with a financial product identifier needs to be determined according to the financial product identifier (such as a financial name) contained in the financial transaction request, and then the financial transaction request is processed through the determined transaction system, so that a reasonable transaction result is obtained.

Therefore, in the embodiment of the present application, in the process of performing service execution processing on the service execution request, the server needs to determine, according to the service identifier included in the service execution request, a service system matched with the service identifier, so as to send the service execution request to the service system for processing, and further receive a reasonable service execution result returned by the service system after processing the service execution request.

It should be noted that, in step S104, after the user clicks the access control in fig. 2A, the client generates a corresponding service execution request according to the service operation executed by the user, and completes the service execution process corresponding to the service execution request through the service execution information returned by the server according to the service execution request, the pre-check, the password check, and the display page shown in fig. 2B.

And when the user inputs corresponding service information in fig. 2B and clicks the confirmation execution control, the client further generates a corresponding service execution request again and sends the service execution request to the server, the server performs corresponding service execution processing on the service execution request according to the service execution request, and carries an obtained service execution result in the service execution information in the step S303 and issues the service execution result to the client, and the client completes a service execution process after clicking the confirmation execution control by the user according to the service execution information through the constructed risk assessment and display service execution result page.

That is to say, after the user clicks the entry control in fig. 2A and clicks the confirmation execution control in fig. 2B, the client actually performs two service executions, the former service execution is performed for the user clicking the entry control in fig. 2A, and the latter service execution is performed for the confirmation execution control in fig. 2B clicked by the user. Although the client performs the service execution process twice, the service execution processes are substantially the same, that is, the service execution information issued by the server determines the service components required in the service execution process, the sequence of the service components in the service execution process, the configuration information of the service components, the view components, the splicing sequence of the view components, and the page content to be displayed, and then performs the service execution according to the determined service configuration content and page configuration content, and displays the corresponding page in the process.

Of course, the two service execution processes related to fig. 2A and fig. 2B may also be combined into one service execution process, that is, after the client sends the service execution request generated by clicking the access control of fig. 2A by the user to the server, the server may carry the service configuration content and the page configuration content related to fig. 2A in the service execution information, and may also carry the service configuration content and the page configuration content related to fig. 2B in the service execution information, and further issue the service execution information to the client together, so that the client may continuously perform the service execution related to fig. 2A and fig. 2B by using the service execution information, and does not need to send a service execution request to the server after the service execution related to fig. 2A is finished.

It should be further noted that, in the embodiment of the present application, during the process of performing service execution by the client, only a page display process may be involved, so for this case, the service execution information sent by the server to the client will also be the service execution information only including the page configuration content, and the client may construct and display a corresponding page in the process of performing service according to the page configuration content (such as the identifier of each view component, the splicing sequence of each view component in the page, and the page content to be displayed) included in the service execution information. Similarly, when the client performs the service execution process and does not relate to the page display, the service execution information sent by the server to the client may only include the service configuration content (such as the identifier of each service component, the sequence of each service component in the service execution process, and the configuration information of each service component).

The service execution process provided by the present application, which is described in detail above from both sides of the client and the server, will be described in the following as a whole for further description of the present application, as shown in fig. 4.

Fig. 4 is a schematic diagram of service execution between a client and a server according to an embodiment of the present application.

In fig. 4, the client supports the execution of the services through the service layout engine, the service component library and the configuration manager deployed by the service developer at the client, and after receiving the service execution information sent by the server, corresponding business components can be determined from the business component library through the business component identifications contained in the business execution information, and the configuration information of each service component contained in the service execution information is distributed and configured in each determined service component through a configuration manager, then, through the service layout engine, the service components configured with the configuration information are sequenced according to the sequence of the service components contained in the service execution information in the service execution process, so as to obtain a service flow, namely a service logic code, required during service execution.

In fig. 4, the client further includes a security protection component, a network connection component, and a data monitoring component, which do not affect the service execution of each service, that is, these components can be understood as additional actions that need to be performed by the client during the service execution process, for example, for the network connection component, the component is responsible for information interaction between the client and the server, so that for each service, only one network connection component needs to be set, and the information sending and information receiving requirements of all services can be met; for another example, for a data monitoring component, after each service is executed, the counted service execution status needs to be reported to the server periodically, so that, for all services, only one data monitoring component may be set, and the requirement that all services report the service execution status to the server may be met.

For the server, the service routing, the configuration information management system and the component configuration information are arranged in the server, the service routing is responsible for determining a service system required by the service execution request for performing service execution processing according to the service execution request sent by the client, the configuration information management system is used for determining configuration information of each service component corresponding to the service identifier and page content of a page to be displayed when the client executes the service according to the service identifier contained in the service execution request sent by the client, the component configuration system is responsible for following the service identifier contained in the service execution request and determining each service component identifier, each view component identifier, the sequence of each service component in the service execution process and the splicing sequence of each view component corresponding to the service identifier. The service portal system shown in fig. 4 is configured to receive a service execution request sent by a client through a network connection component, and issue service execution information corresponding to the service execution request to the client.

It should be noted that, in the Service execution process of the financial product described above, a payment process is usually involved, and the technology carriers involved in the payment process in the embodiment of the present application may include Near Field Communication (NFC), WIFI, 3G/4G/5G, POS machine card swiping technology, two-dimensional code scanning technology, barcode scanning technology, bluetooth, infrared, Short Message Service (SMS), Multimedia Message (MMS), and the like.

It should be noted that, in practical applications, different services may include multiple pages, and in these pages, most of the pages may be closely related to the service itself, that is, have a larger difference with pages of other services, and have fewer common points, so that the page construction mentioned in the embodiment of the present application does not involve the page construction. However, for different services in the same client, even if there is a large difference between the services, there is a large commonality between some pages in the pages included in the services.

Taking a financial product as an example, a client may include a plurality of financial products, each of which may include a plurality of pages, most of the pages are designed for the financial product, i.e. have no major connection with other financial products, whatever financial product, however, will involve a buy page and a deal result display page, wherein, for the purchase page, the purchase page of each financing product comprises the contents of a purchase financing input part, a settlement rule introduction part and the like, therefore, for such pages with great commonality, the corresponding pages can be constructed and displayed to the user through the service execution mode described above, therefore, the cost and time consumed by service development are reduced to a certain extent, and the service development efficiency is improved.

Based on the same idea, the service execution method provided in the embodiment of the present application further provides two service execution apparatuses, as shown in fig. 5 and 6.

Fig. 5 is a schematic diagram of a service execution apparatus provided in an embodiment of the present application, which specifically includes:

a generating module 501, configured to generate a corresponding service execution request according to a service operation executed by a user;

a sending module 502, configured to send the service execution request to a server, so that the server returns corresponding service execution information according to the service execution request;

a determining module 503, configured to determine, according to each service component identifier included in the service execution information, a service component corresponding to each service component identifier from a preset service component library;

the service execution module 504 executes the service according to the determined service components and the configuration information of the service components included in the service execution information.

The service execution module 504 is configured to configure each configuration information corresponding to each service component in each service component; sequencing the service components configured with the configuration information according to the sequence of the service components contained in the service execution information to obtain service logic codes; and executing the service according to the service logic code.

The service execution information also comprises identifiers of all view components, a splicing sequence of all view components and page contents to be displayed;

the device further comprises:

a presentation module 505, configured to determine, according to each view component identifier included in the service execution information, a view component corresponding to each view component identifier from a preset view component library; constructing a page to be displayed when the service is executed according to the determined view components, the splicing sequence of the view components contained in the service execution information and the content of the page to be displayed; and displaying the page when the service is executed.

Fig. 6 is a schematic diagram of another service execution apparatus provided in the embodiment of the present application, which specifically includes:

a receiving module 601, configured to receive a service execution request sent by a client;

an information generating module 602, configured to generate service execution information corresponding to the service execution request according to the service execution request;

the information returning module 603 returns the service execution information to the client, so that the client executes a service according to the service component corresponding to each service component identifier included in the service execution information and each configuration information of each service component included in the service execution information.

The information generating module 602 determines the service identifier included in the service execution request; determining service component identifications required by the service corresponding to the service identification, the sequence of the service components corresponding to the service component identifications when the client executes the service and configuration information corresponding to the service components according to the service identification; and generating service execution information corresponding to the service execution request according to the service component identifications, the sequence of the service components when the client executes the service and the configuration information.

The information generating module 602 determines, according to the service identifier included in the service execution request, page content of a page to be displayed when the client executes a service; determining each view component identification required by the client side when the page content is displayed and the splicing sequence of each view component corresponding to each view component identification according to the service identification; and generating service execution information corresponding to the service execution request according to the identifier of each view component, the splicing sequence of each view component and the page content.

The information generating module 602 processes the service execution request to obtain a corresponding service execution result; determining each view component identifier required by the client when displaying the service execution result and the splicing sequence of each view component corresponding to each view component identifier according to the service execution result; and generating service execution information according to the identifier of each view component, the splicing sequence of each view component and the service execution result.

The information generating module 602 determines a service system for processing the service execution request according to the service identifier included in the service execution request; and sending the service execution request to the service system, and receiving a service execution result returned after the service system processes the service execution request.

In the embodiment of the application, the client can generate a corresponding service execution request according to the service operation executed by the user, and send the service execution request to the server, and the server can return corresponding service execution information to the client according to the service execution request, so that the client executes the service according to the service execution information. The client side only needs to construct corresponding business processes and business pages for different businesses according to business execution information sent by the server, and the client side can construct corresponding business processes and business pages for different businesses through the business components and the view components which are preserved in advance, so that business developers do not need to perform specific configuration work on the business in the client side in the business development process, and only need to configure different business configuration contents set for different businesses in the server to complete the business development work, thereby greatly reducing the cost and time consumed in business development and improving the business development efficiency.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

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

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

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

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

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

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

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method of service execution, comprising:

sending the service execution request to a server so that the server returns corresponding service execution information according to the service execution request, wherein the service execution information comprises service component identifications and configuration information of service components;

2. The method of claim 1, wherein executing the service according to the service components and the configuration information of the service components included in the service execution information specifically includes:

respectively configuring the configuration information corresponding to each service component in each service component;

sequencing the service components configured with the configuration information according to the sequence of the service components contained in the service execution information to obtain service logic codes;

and executing the service according to the service logic code.

3. The method according to claim 1, wherein the service execution information further includes identifiers of the view components, a splicing sequence of the view components, and page contents to be displayed;

the method further comprises the following steps:

determining a view component corresponding to each view component identifier from a preset view component library according to each view component identifier contained in the service execution information;

constructing a page to be displayed when the service is executed according to the determined view components, the splicing sequence of the view components contained in the service execution information and the content of the page to be displayed;

and displaying the page when the service is executed.

4. A method of service execution, comprising:

receiving a service execution request sent by a client;

generating service execution information corresponding to the service execution request according to the service execution request, wherein the service execution information comprises service component identifications and configuration information of service components;

5. The method of claim 4, wherein generating the service execution information corresponding to the service execution request specifically includes:

determining a service identifier contained in the service execution request;

determining service component identifications required by the service corresponding to the service identification, the sequence of the service components corresponding to the service component identifications when the client executes the service and configuration information corresponding to the service components according to the service identification;

and generating service execution information corresponding to the service execution request according to the service component identifications, the sequence of the service components when the client executes the service and the configuration information.

6. The method of claim 4, wherein generating the service execution information corresponding to the service execution request specifically includes:

determining the page content of a page to be displayed when the client executes the service according to the service identifier contained in the service execution request;

determining each view component identification required by the client side when the page content is displayed and the splicing sequence of each view component corresponding to each view component identification according to the service identification;

and generating service execution information corresponding to the service execution request according to the identifier of each view component, the splicing sequence of each view component and the page content.

7. The method of claim 4, wherein generating the service execution information corresponding to the service execution request specifically includes:

processing the service execution request to obtain a corresponding service execution result;

determining each view component identifier required by the client when displaying the service execution result and the splicing sequence of each view component corresponding to each view component identifier according to the service execution result;

and generating service execution information according to the identifier of each view component, the splicing sequence of each view component and the service execution result.

8. The method of claim 7, wherein processing the service execution request to obtain a corresponding service execution result specifically comprises:

determining a service system for processing the service execution request according to the service identifier contained in the service execution request;

and sending the service execution request to the service system, and receiving a service execution result returned after the service system processes the service execution request.

9. An apparatus for service execution, comprising:

the sending module is used for sending the service execution request to a server so that the server returns corresponding service execution information according to the service execution request, wherein the service execution information comprises service component identifications and configuration information of service components;

10. The apparatus of claim 9, wherein the service execution module configures each configuration information corresponding to each service component in each service component; sequencing the service components configured with the configuration information according to the sequence of the service components contained in the service execution information to obtain service logic codes; and executing the service according to the service logic code.

11. The apparatus of claim 9, wherein the service execution information further includes identifiers of the view components, a splicing sequence of the view components, and page contents to be displayed;

the device further comprises:

the display module is used for determining view components corresponding to the view component identifications from a preset view component library according to the view component identifications contained in the service execution information; constructing a page to be displayed when the service is executed according to the determined view components, the splicing sequence of the view components contained in the service execution information and the content of the page to be displayed; and displaying the page when the service is executed.

12. An apparatus for service execution, comprising:

the information generation module generates service execution information corresponding to the service execution request according to the service execution request, wherein the service execution information comprises service component identifications and configuration information of service components;

13. The apparatus of claim 12, wherein the information generating module determines a service identifier included in the service execution request; determining service component identifications required by the service corresponding to the service identification, the sequence of the service components corresponding to the service component identifications when the client executes the service and configuration information corresponding to the service components according to the service identification; and generating service execution information corresponding to the service execution request according to the service component identifications, the sequence of the service components when the client executes the service and the configuration information.

14. The apparatus according to claim 12, wherein the information generating module determines page content of a page to be displayed when the client executes a service, according to a service identifier included in the service execution request; determining each view component identification required by the client side when the page content is displayed and the splicing sequence of each view component corresponding to each view component identification according to the service identification; and generating service execution information corresponding to the service execution request according to the identifier of each view component, the splicing sequence of each view component and the page content.

15. The apparatus of claim 12, wherein the information generating module processes the service execution request to obtain a corresponding service execution result; determining each view component identifier required by the client when displaying the service execution result and the splicing sequence of each view component corresponding to each view component identifier according to the service execution result; and generating service execution information according to the identifier of each view component, the splicing sequence of each view component and the service execution result.

16. The apparatus of claim 15, wherein the information generating module determines a service system for processing the service execution request according to a service identifier included in the service execution request; and sending the service execution request to the service system, and receiving a service execution result returned after the service system processes the service execution request.