Business implementation method, device, system, computer equipment and storage medium

Abstract

The embodiments of the present application provide a service implementation method, apparatus, system, computer equipment and storage medium, which relate to the field of Internet technology, can greatly shorten the delivery cycle of CDN service providers, realize standardized management of personalized CDN services, and bring convenience to the operation and maintenance work of personalized CDN services after they are launched. It includes: the configuration server obtains standard configuration information through the configuration interface, and sends configuration update instructions or service execution logic generated based on the standard configuration information to the edge server. The edge server receives the configuration update instruction sent by the configuration server, generates the service execution logic according to the standard configuration information in the configuration update instruction, or receives the service execution logic sent by the configuration server. When the edge server receives a user request corresponding to the service execution logic, it executes the service execution logic to process the user request.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a service implementation method, device, system, computer equipment and storage medium. Background Art

[0002] Content delivery network (CDN) is a network built on the Internet. The basic principle of CDN is to widely use various cache servers and distribute them to areas or networks where user access is relatively concentrated. When a user visits a website, global load balancing technology is used to direct the user's access to the nearest cache server, which responds to the user's request.

[0003] CDN services involve the use of various virtualized resources, such as content storage, content distribution, etc. With the promotion of CDN services, in addition to traditional service content, various personalized customized CDN service needs have also emerged.

[0004] At present, in order to respond to the new personalized service needs of users, the developers of CDN service providers develop new sub-services based on the service needs of users and write implementation codes for the new sub-services. Since the logical relationship between the sub-services is serial, it may be necessary to modify the logic of the underlying framework to support the newly launched sub-services.

[0005] Due to the inconsistent business configuration of new and old functions and the personalized characteristics of business needs, on the one hand, business management is relatively chaotic, and on the other hand, the delivery cycle of CDN service providers is long and they cannot respond to customer needs in a timely manner. In addition, the traditional way of launching new services also brings certain adverse effects to the operation and maintenance work after the new services are launched. Summary of the invention

[0006] The embodiments of the present application provide a service implementation method, apparatus, system, computer equipment and storage medium, which can greatly shorten the delivery cycle of CDN service providers, realize standardized management of personalized CDN services, and bring convenience to the operation and maintenance work of personalized CDN services after they are launched.

[0007] In a first aspect, a service implementation method is provided, which is used to configure a server, comprising:

[0008] Obtaining standard configuration information through the configuration interface, the standard configuration information is used to represent the relationship between the execution conditions of the changed function and the execution operation;

[0009] Sending a configuration update instruction to the edge server so that the edge server generates a service execution logic, wherein the configuration update instruction includes the standard configuration information; or sending the service execution logic generated based on the standard configuration information to the edge server.

[0010] In combination with the first aspect, in a possible implementation manner of the first aspect, the changed function includes: a changed function of an original function, a function added based on the original function, or a newly added function;

[0011] The changed function includes at least one of the following: a function after deleting the original function of the edge server, a function after modifying the original function of the edge server, and a sub-function added to the original function of the edge server.

[0012] In combination with the first aspect, in a possible implementation of the first aspect, the configuration interface includes a configuration interface, and obtaining the standard configuration information includes:

[0013] Obtain the business content currently input into the configuration interface and determine the standard configuration information based on the business content.

[0014] In combination with the first aspect, in a possible implementation manner of the first aspect, the standard configuration information includes a configuration text.

[0015] In combination with the first aspect, in a possible implementation manner of the first aspect, the configuration interface includes configurable items for standardizing business content.

[0016] In combination with the first aspect, in a possible implementation manner of the first aspect, the configuration interface includes one or more of configurable items for executing operations, configurable items for executing conditions, and logic code input items.

[0017] In combination with the first aspect, in a possible implementation manner of the first aspect, if the business content includes a logic code of a changed function, the method further includes:

[0018] Parse the logic code of the changed function, obtain the execution conditions and execution operations contained in the logic code, and add the execution conditions and execution operations contained in the logic code to the configuration interface;

[0019] Or, add the logic code of the changed function to the configuration interface.

[0020] In combination with the first aspect, in a possible implementation of the first aspect, the configuration interface also includes nesting level prompt information; the nesting level prompt information is used to indicate the limit value of the number of execution logics that can be nested under a single execution operation.

[0021] In combination with the first aspect, in a possible implementation manner of the first aspect, the method further includes:

[0022] Get the number of nested execution logics under the current single execution operation;

[0023] If the number of nested execution logics under a single execution operation exceeds the quantity limit, adjustment information is output; the adjustment information is used to instruct the user to adjust the number of nested execution logics.

[0024] In conjunction with the first aspect, in a possible implementation of the first aspect, determining the specification configuration information according to the service content includes:

[0025] Performing logic identification processing on the business content to obtain the execution conditions and execution operations of the changed function, or obtaining the execution operations of the changed function;

[0026] Based on the execution condition and execution operation of the changed function, or the execution operation of the changed function is obtained, an association relationship structure of the changed function is generated.

[0027] In a second aspect, a service implementation method is provided, the method comprising:

[0028] Receive a configuration update instruction sent by a configuration server, and generate a business execution logic according to the standard configuration information in the configuration update instruction; or, receive a business execution logic sent by a configuration server, where the business execution logic is generated by the configuration server according to the standard configuration information; the standard configuration information is used to characterize the association between the execution conditions of the changed function and the execution operation;

[0029] When a user request corresponding to the service execution logic is received, the service execution logic is executed to process the user request.

[0030] In conjunction with the second aspect, in a possible implementation of the second aspect, generating service execution logic according to the specification configuration information includes:

[0031] Parse the configuration text in the specification configuration information, and generate business execution logic according to the execution conditions and execution operations obtained from the parsing; or,

[0032] The configuration text in the standard configuration information is parsed, and the business execution logic is generated according to the execution operation obtained by the parsing.

[0033] In conjunction with the second aspect, in a possible implementation of the second aspect, generating service execution logic according to the specification configuration information includes:

[0034] Generate business execution logic based on the standard configuration information and the service layer logic code of the existing functions of the edge server.

[0035] In conjunction with the second aspect, in a possible implementation of the second aspect, executing the service execution logic to process the user request includes:

[0036] Determine whether the user request matches the execution conditions in the business execution logic;

[0037] If the user request matches the target execution condition in the business execution logic, the user request is processed according to the target execution operation associated with the target execution condition.

[0038] In conjunction with the second aspect, in a possible implementation of the second aspect, if a sub-execution logic is nested under the target execution operation, the sub-execution logic includes a sub-execution condition and a sub-operation;

[0039] Then, the user request is processed according to the execution operation associated with the target execution condition, including:

[0040] A target sub-execution condition matching the user request is determined, and the user request is processed according to a sub-operation associated with the target sub-execution condition.

[0041] In combination with the second aspect, in a possible implementation manner of the second aspect, the business execution logic specifically includes description information of each execution operation; the description information includes: an execution operation identifier and / or a sub-execution logic.

[0042] In a third aspect, a service implementation device is provided, including:

[0043] The processing unit is used to obtain the standard configuration information through the configuration interface, and the standard configuration information is used to represent the association between the execution condition of the changed function and the execution operation;

[0044] The communication unit is used to send a configuration update instruction to the edge server so that the edge server generates a service execution logic; or send the service execution logic generated based on the specification configuration information to the edge server.

[0045] In a fourth aspect, a service implementation device is provided, including:

[0046] A processing unit, configured to receive a configuration update instruction sent by a configuration server through a communication unit, and generate a business execution logic according to the standard configuration information in the configuration update instruction; or, to receive a business execution logic sent by a configuration server through a communication unit, where the business execution logic is generated by the configuration server according to the standard configuration information; the standard configuration information is used to characterize the association between the execution condition of the changed function of the edge server and the execution operation;

[0047] The processing unit is also used to, when receiving a user request corresponding to the service execution logic, execute the service execution logic to process the user request.

[0048] In a fifth aspect, a business implementation system is provided, including:

[0049] Configuration management platform, which includes configuration interface and configuration server;

[0050] Configuration interface, used to perform configuration operations to generate standard configuration information;

[0051] The configuration server is used to obtain the standard configuration information through the configuration interface, and the standard configuration information is used to represent the association between the execution condition of the changed function and the execution operation; the configuration server is also used to send a configuration update instruction to the edge server;

[0052] The edge server is used to receive the configuration update instruction sent by the configuration server, and generate the business execution logic according to the standard configuration information in the configuration update instruction; or, receive the business execution logic sent by the configuration server, and the business execution logic is generated by the configuration server according to the standard configuration information; the edge server is also used to, when receiving a user request corresponding to the business execution logic, execute the business execution logic to process the user request.

[0053] In a sixth aspect, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the method that may be implemented in any of the first aspect or the second aspect are implemented.

[0054] In a seventh aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method that may be implemented in any of the first aspect or the second aspect are implemented.

[0055] The embodiment of the present application provides a service implementation method, device, system, computer equipment and storage medium, which supports CDN users or platform operation and maintenance personnel to use the configuration interface to change the function of the edge server. Obtain the standard configuration information through the application program interface or the graphical user interface, send the configuration update instruction to the edge server, and instruct the edge server to generate the service execution logic according to the standard configuration information. The edge server can generate the service execution logic according to the standard configuration information, and after receiving the corresponding user request, execute the service execution logic to process the user request. The standardized configuration and standardized management of the CDN service customization service are realized through the standardized configuration information, which also brings convenience to the operation and maintenance work after the personalized CDN service is launched. In addition, after the configuration server receives the sent configuration update instruction, it can automatically and quickly generate the service execution logic according to the standard configuration information in the instruction, without modifying the logic of the underlying framework, and also avoids the online delay caused by the inconsistent service configuration of the new and old functions when configuring new functions, which greatly shortens the long delivery cycle of the CDN service provider, and improves the scalability of the service, and can realize the rapid launch of various changed functions. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 A system architecture diagram provided for an embodiment of the present application;

[0057] Figure 2 A flowchart of a method for implementing a service provided in an embodiment of the present application;

[0058] Figure 3 A schematic diagram of the configuration interface provided in the embodiment of the present application;

[0059] Figure 4 A schematic diagram of another configuration interface provided in an embodiment of the present application;

[0060] Figure 5 Another flowchart of the service implementation method provided in the embodiment of the present application;

[0061] Figure 6 to Figure 9 A schematic diagram of another configuration interface provided in an embodiment of the present application;

[0062] Fig.10 Another flowchart of the service implementation method provided in the embodiment of the present application;

[0063] Fig.11 A schematic diagram of another configuration interface provided in an embodiment of the present application;

[0064] Fig.12 Another flowchart of the service implementation method provided in the embodiment of the present application;

[0065] Fig.13Another flowchart of the service implementation method provided in the embodiment of the present application;

[0066] Fig.14 Another flowchart of the service implementation method provided in the embodiment of the present application;

[0067] Fig.15 A structural block diagram of a service implementation device provided in an embodiment of the present application;

[0068] Fig.16 Another structural block diagram of the service implementation device provided in an embodiment of the present application;

[0069] Fig.17 A structural block diagram of a computer device provided in an embodiment of the present application;

[0070] Fig.18 Another structural block diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0072] Figure 1 This is a system architecture diagram applicable to the embodiments of this application. Figure 1 The system includes an edge server 10, a configuration management platform 20, and a user terminal 30. The configuration management platform 20 includes a configuration server 201 and a configuration interface 202. CDN users or operation and maintenance personnel of the configuration management platform 20 can access the configuration server 201 through the configuration interface 202. The configuration interface 202 includes a graphical user interface (GUI) or an application programming interface (API). The GUI can be a configuration interface.

[0073] In addition, the user end 30 is a terminal used by a user corresponding to the CDN user. After the CDN user subscribes to the cloud service, in the scenario where the edge server 10 provides the CDN user with the cloud service, the user request from the user end 30 is sent to the edge server 10 for processing. The CDN user in the embodiment of the present application may be a user of the configuration interface, for example, the CDN user described above or the operation and maintenance personnel of the configuration management platform 20. In the following embodiments, the CDN user is taken as an example to illustrate the various technical solutions provided in the embodiments of the present application.

[0074] The business scenarios to which the embodiments of the present application are applicable include, but are not limited to, CDN services, and may also be applied to business scenarios such as edge cloud computing, distributed cloud services, or other multiple scenarios to which this technical architecture is applicable.

[0075] Taking CDN service as an example, the edge server 10 is a device of the CDN service provider, which can provide various network acceleration services based on the distributed network. The edge server can be a computing node deployed close to the user end, with the ability to cache data, calculate data, etc.

[0076] For example, when website A subscribes to the CDN service, user requests initiated by users of website A will be sent to the edge server, and the edge server will quickly respond to the user requests, thereby speeding up access.

[0077] Currently, when CDN users put forward personalized service requirements, the developers of CDN service providers need to formulate sub-services according to the service requirements of CDN users, write the implementation code of sub-services, and launch them online after a period of time. However, due to the existence of the R&D cycle, there is a certain upper limit delay in service requirements, and the delivery cycle of CDN service providers is relatively long. In addition, due to the inconsistent business configuration of new and old functions and the personalized characteristics of business requirements, business management is relatively chaotic.

[0078] Based on this, the embodiment of the present application provides a business implementation method, which can realize the standardized management of CDN service customization business, shorten the online delay of customized CDN service, is conducive to the development of personalized customization business based on CDN service, and greatly improves the scalability of platform services.

[0079] refer to Figure 2 The execution subject of this method can be Figure 1 The configuration server in the system shown specifically includes the following steps:

[0080] 201. Obtaining standard configuration information through a configuration interface, where the standard configuration information is used to represent the association between the execution condition of the changed function and the execution operation;

[0081] In the embodiment of the present application, in order to standardize the management of personalized customization services based on CDN services, a configuration interface for CDN users can be provided, through which CDN users can input configuration information of various functions to realize personalized CDN function customization on edge servers or load balancing servers. Taking the function change of edge servers as an example, when CDN users need to change the functions of edge servers, CDN users can input the configuration information of the changed functions through the configuration interface (e.g., configuration interface). After the CDN user completes the configuration, he clicks the confirmation control on the configuration interface, and the configuration server can confirm the standard configuration information.

[0082] In another embodiment, the platform operation and maintenance personnel or a party authorized by the CDN user can also use the configuration interface to customize the functions of the configuration management platform. It should be noted that the configuration management platform can be provided to CDN users, or used by the operation and maintenance personnel of the CDN service provider, or used by a party authorized by the CDN user.

[0083] In a possible implementation, the standard configuration information is the result of standardizing the information input by the CDN user through the configuration interface. In a specific implementation, the configuration server can identify the execution logic represented by the information input by the CDN user to obtain the above-mentioned standard configuration information. Among them, the execution logic can be the association relationship between the execution condition and the execution operation.

[0084] Exemplarily, the specification configuration information is used to characterize the association between the execution conditions of the changed function and the execution operation. The execution condition can be considered as one or more conditional rules, referred to as ACL; the execution operation is the underlying operation specifically performed when implementing a certain function (or business), and the execution operation can be referred to as OP (operation).

[0085] In a possible implementation, the association between the execution condition and the execution operation can be understood as: the execution operation is executed under the premise of satisfying the execution condition. Exemplarily, the execution condition is "the destination IP address is 111.00.10.11", and the execution operation associated with it is "forbidden access", that is, when the IP address accessed by the user terminal 30 is 111.00.10.11, the edge server 10 prohibits the user terminal 30 from accessing and rejects the access request of the user of the user terminal 30.

[0086] It should be noted that the specification configuration information can be an association relationship structure (including one or more association relationship lists, which can be called an action list in this embodiment), or it can be other information used to characterize the relationship between execution conditions and execution operations. For example, the specification configuration information can be text information used to describe execution conditions, execution operations, and the relationship between the two. The specification configuration information can also be an execution file of the changed function. The embodiments of the present application do not limit the specific implementation of the specification configuration information, and any information that can characterize the execution conditions, execution operations, and the relationship between the two belongs to the protection scope of the embodiments of the present application.

[0087] 202. Send a configuration update instruction to the edge server so that the edge server generates a service execution logic; or send the service execution logic generated based on the specification configuration information to the edge server.

[0088] In a specific implementation, the configuration server may perform protocol adaptation on the standard configuration information and encapsulate the standard configuration information into a configuration update instruction. The protocol adaptation on the standard configuration information may be to perform protocol adaptation on the standard configuration information according to the communication protocol between the configuration server and the edge server. The configuration update instruction includes the standard configuration information, so that the edge server can generate business execution logic based on the standard configuration information.

[0089] Alternatively, the configuration server generates the service execution logic locally based on the specification configuration information, and sends the generated service execution logic to the edge server.

[0090] It should be noted that the business execution logic is used to implement various customized functions of CDN, and can be the implementation code of various functions provided by CDN users. For example, the customized functions that CDN can provide include: access control and user authentication, then the CDN user's execution file includes the execution code of the "access control" function and the execution code of the "user authentication" function, and the execution codes of these two functions can be logically coupled or decoupled, and the embodiments of the present application do not limit this.

[0091] Figure 2 In the embodiment shown, a standardized configuration interface is provided for CDN users, and CDN users are supported to change functions in the configuration interface. Obtaining standardized configuration information through the configuration interface can realize standardized configuration and standardized management of CDN service customization business, and also bring convenience to the operation and maintenance work after the personalized CDN service is launched, which is conducive to the development of personalized customization business based on CDN service.

[0092] It should be noted that the above-mentioned configuration update instructions or business execution logic can be periodically pulled from the configuration server by the edge server; in another possibility, the CDN user enters the standard configuration information in the configuration interface, and actively submits it to the configuration server after reviewing the standard configuration information. The configuration server actively generates updated configuration instructions or business execution logic based on the standard configuration information, and actively sends updated configuration instructions or business execution logic.

[0093] In the above embodiment, the configuration server can obtain the execution conditions and execution operations of the changed function. In this embodiment, several possible function changes are provided. Exemplarily, the changed functions mentioned above include: the changed functions of the original functions, the functions added based on the original functions, or the newly added functions.

[0094] The changed function includes at least one of the following: a function after deleting the original function of the edge server, a function after modifying the original function of the edge server, and a sub-function added to the original function of the edge server.

[0095] It should be noted that the functions after deleting the original functions of the edge server are the functions supported by the edge server after deleting some of the functions currently supported by the edge server. For example, the edge server currently supports the "authentication" and "precise access control" functions. The CDN user can delete the "authentication" function in the configuration interface, and the changed function is "precise access control".

[0096] The function after modifying the original function of the edge server is the function supported by the edge server after modifying the function currently supported by the edge server. Exemplarily, the edge server currently supports the "access control" function, and the function can be modified so that the edge server supports more accurate access control.

[0097] The sub-function added to the original function of the edge server is to add the sub-function to the function currently supported by the edge server. For example, the edge server currently supports the "authentication" function, and the edge server can add a sub-function to the "authentication" function, for example, adding the "account authentication" function.

[0098] In addition, the functions added based on the original functions can be new functions added based on the functions currently supported by the edge server. For example, the edge server currently supports the "authentication" function, and the edge server can add the "access control" function. The changed functions include "authentication" and "access control".

[0099] Alternatively, the changed function may also be a new function added to the edge server. For example, a CDN user may add various new functions in the configuration interface according to actual business needs.

[0100] The embodiment of the present application provides several possibilities for changing the edge server function. Of course, the change of the edge server function is not limited to the possibilities described above, and the embodiment of the present application does not limit this. Through this embodiment, CDN users are supported to complete various personalized service changes locally through the configuration interface.

[0101] In the above embodiment, after the configuration server responds to the configuration instruction on the configuration interface, it can obtain the standard configuration information of the changed function. In another embodiment of the present application, a technical solution of how the configuration server obtains the standardized configuration information based on the configuration interface is specifically introduced. Exemplarily, the specific implementation method of "obtaining the standard configuration information of the changed function" in step 201 is as follows:

[0102] The business content currently input into the configuration interface is obtained, and the standard configuration information is determined according to the obtained business content.

[0103] In a possible implementation, the configuration interface includes configurable items, which are used to normalize the business content input by the CDN user. For example, the configuration interface includes one or more of configurable items for executing operations, configurable items for executing conditions, and logical code input items. The configurable items for executing operations can be selection items for executing operations and / or input items for executing operations, and the configurable items for executing conditions can be selection items for executing conditions and / or input items for executing conditions.

[0104] Exemplarily, the configurable item may be an option. The option supports the CDN user to select the service content in the drop-down menu of the option according to the actual service requirements (for example, the service requirements in the CDN service scenario). The service content selected by the CDN user may be an execution condition and an execution operation, and the execution condition and the execution operation selected by the CDN user are used to implement the function to be updated. The service content selected by the CDN user may also not include the execution condition, but only include the execution operation, that is, any user request corresponding to the edge server executes the execution operation unconditionally without matching the execution condition.

[0105] In a specific implementation, after a CDN user selects execution conditions and execution operations through selection items in a configuration interface, the configuration server can obtain the execution conditions and execution operations selected by the CDN user through the selection items, and generate standard configuration information according to the execution conditions and execution operations selected by the CDN user.

[0106] This application embodiment provides a possible configuration interface. Figure 3 , the configuration interface may include options for execution conditions and options for execution operations. Of course, the configuration interface may also not include options for execution conditions, or the optional content of the options for execution conditions may include "any", which is used to indicate that any user request corresponding to the edge server executes the execution operation unconditionally without matching the execution conditions. The user can add multiple execution conditions by triggering the "Add" control on the configuration interface. The options for execution conditions may include type options for execution conditions, logical options for execution conditions, and parameter options for execution conditions. Among them, the type option for execution conditions includes multiple optional condition types, and the condition type is used to describe the applicable objects of the execution condition. For example, the type of execution condition can be Figure 3 The execution condition logic options include multiple optional conditional logics, which are used to describe the judgment logic that the execution condition meets. For example, the execution logic can be Figure 3Of course, according to the actual situation of the execution condition, the execution condition can also be "greater than", "less than", "greater than or equal to", "less than or equal to", "belongs to", "does not belong to", "contains", "does not contain", etc. The parameter option of the execution condition is used to enter the input parameters of the execution condition. CDN users can enter the input parameters of the execution condition in the parameter option according to actual business needs. Among them, the input parameter is the reference standard when judging (or detecting) a certain object according to the conditional logic. For example, the input parameter can be Figure 3 The execution operation options include multiple optional execution operations, which are used to represent the operations to be performed after the execution conditions are met. For example, the execution operation can be Figure 3 The configuration interface includes an "add" control. CDN users can click the "add" control to continue selecting execution conditions or execution operations. The configuration interface also includes a "confirm" control. After the CDN user finishes selecting execution conditions and execution operations, he clicks the "confirm" control to trigger the configuration instructions of the service to be updated.

[0107] by Figure 3 Taking the configuration interface shown (which can be called the basic configuration interface) as an example, the business content obtained by the configuration server is as follows:

[0108] Execution condition ACL1: The request URL contains " / user", that is, it is determined whether the request URL sent by the user of the client 30 contains the string " / user";

[0109] Execution condition ACL2: The requested configuration server IP is "172.16.1.1", that is, whether the IP address of the configuration server that sends the request message is "172.16.1.1";

[0110] Execute operation OP1: Block for 10 seconds at the access control layer.

[0111] The standardized configuration information obtained by the configuration server based on the obtained business content can represent the association between the execution condition ACL1, the execution condition ACL2 and the execution operation OP, that is, if the execution condition ACL1 and the execution condition ACL2 are met, the above-mentioned execution operation OP1 is executed. The embodiment of the present application abstracts all configurations into execution conditions ACL, execution actions OP and associations. The unified configuration of all CDN users greatly facilitates subsequent maintenance work.

[0112] In another possible implementation, the above configurable items may also be input items. The input items may be input boxes, which support CDN users to input business content in the input items according to actual business needs. The business content input by the CDN user may be a CDN user-defined logic code, which is used to implement the function to be updated on the edge server. Among them, the CDN user-defined logic code may also be called a custom function. The execution condition in the custom function follows the interface specification of the ACL, and may be an ACL function customized by the CDN user. Among them, the interface specification is related to constraints and actual business. The constraints of the execution condition include: whether the execution condition is satisfied or not is represented by "true" or "false", then the interface specification of the execution condition may be: the return value of the execution condition is "true" or "false". The execution action in the custom function is strongly related to the business, and the CDN user customizes the execution actions associated with various execution conditions according to actual business needs. For example, in the access control business, the execution operation may be "allow access", "prohibit access" or "ban for a period of time".

[0113] Specifically, after the CDN user inputs the custom logic code through the input item of the configuration interface, the configuration instruction is triggered. In response to the configuration instruction, the configuration server obtains the logic code input by the CDN user through the input item and generates standard configuration information according to the logic code input by the CDN user.

[0114] The present application embodiment also provides a possible configuration interface. Figure 4 The configuration interface (which may be called the advanced configuration interface) includes a logic code input item. CDN users can enter custom logic codes in the input items according to actual business needs. After the configuration server obtains the logic code entered by the CDN user, it generates standardized configuration information based on the logic code entered by the CDN user. The configuration interface also includes a "confirm" control. After the CDN user enters the custom code logic of the service to be updated, click the "confirm" control to trigger the configuration instructions of the service to be updated. Figure 4 The interface shown can also display the association structure generated by the configuration server, referred to as the actions list.

[0115] For example, a CDN user defines an anti-hotlink function access_check, and the CDN user-defined logic code may include an actions list. The judgment condition of the first action in the actions list is any, indicating that any user request needs to execute the anti-hotlink logic, which is written by the CDN user according to his own business needs.

[0116] In the embodiment of the present application, the configuration management platform can provide CDN users with a configuration method for CDN services through the configuration interface, supporting personalized customization of CDN services. In addition, the business content received by the configuration interface is standardized, and standardized configuration information of the changed function can be obtained to support the background implementation of the changed function. The embodiment of the present application supports CDN users to select the execution conditions and execution operations of the changed function in the basic configuration interface, and also supports CDN users to enter custom functions in the advanced configuration interface to expand and implement personalized business needs, thereby improving the flexibility of CDN cloud service personalized customization business.

[0117] At the same time, by separating the execution conditions and execution operations, configuration reuse at the execution operation granularity or at the execution condition granularity can be achieved, providing a more fine-grained configuration reuse solution. In addition, the business execution logic is automatically and quickly generated according to the standard configuration information in the configuration update instruction, which can achieve the reuse of configuration information and the consistency of new and old functional business configurations, thereby improving the scalability of the business.

[0118] In the above embodiment, the configuration management platform determines the standardized configuration information according to the business content input by the CDN user in the configuration interface. In another embodiment of the present application, the configuration server can perform logic identification processing on the business content and generate the above-mentioned standardized configuration information based on the result of the logic identification processing. For example, the specific implementation steps of determining the standardized configuration information according to the business content mentioned above are as follows: Figure 5 As shown:

[0119] 501. Perform logic identification processing on the business content to obtain the execution condition and / or execution operation of the changed function;

[0120] The logic identification process is to identify the execution conditions, execution operations and the association between the execution conditions and execution operations represented by the business content input by the CDN user.

[0121] It should be noted that the execution condition is a pre-check condition for the execution operation. The underlying implementation first determines whether the execution condition is met, and only when the execution condition is met will the associated execution operation be executed. For example, some basic verification functions are provided as optional execution conditions through the configuration interface, which can be string comparison, numeric comparison, regular expression matching, keyword recognition, etc. CDN users can set the execution condition based on actual business needs (for example, business needs in CDN service scenarios).

[0122] The execution operation is the operation actually performed after the associated execution conditions are met. Exemplarily, for CDN service scenarios, the execution operation may include access control OP, header control OP, URL control OP, request parameter control OP, control OP, and cache control OP, etc. Each control OP specifies the corresponding input parameters, which can also be called the description information of the control OP, which is used to characterize what the control OP is. Exemplarily, the input parameter of the control OP can be a certain value or object, or it can point to a custom function. For example, the control OP is "add a request header", and the input parameter of the control OP can be a certain value or an object, or it can point to a custom function, which can execute the actual logic of adding the request header and finally return a string as the added request header.

[0123] It should be noted that the implementation code of the function may include execution conditions and execution operations. The business content entered by the CDN user in the configuration interface may represent the execution conditions and execution operations. Therefore, the configuration server performs logical identification processing on the business content to obtain the execution conditions and execution operations. In addition, the implementation code of the function may not include execution conditions, but only include execution operations. The business content entered by the CDN user in the configuration interface may represent the execution operation. Therefore, the configuration server performs logical identification processing on the business content to obtain the execution operation of the changed function.

[0124] 502 : Generate standard configuration information of the changed function based on the execution condition and / or execution operation of the changed function, or generate standard configuration information based on the execution operation of the changed function.

[0125] The standard configuration information includes a configuration text. The configuration file may be a text containing the standardized configuration information. Specifically, the configuration server may precompile the standard configuration information to generate an execution file for executing various functions of the edge server, and the edge server may load the execution file to process the user request.

[0126] Figure 5 The method shown provides a possible implementation method for generating standardized configuration information based on the business content input by CDN users. Specifically, the configuration server can generate an association relationship structure, so that the edge server can generate an execution file of the edge server based on the association relationship structure generated by the configuration server, thereby realizing the rapid launch of personalized customization functions in CDN service scenarios.

[0127] In the above-mentioned embodiment, the configuration server can generate the service execution logic based on the standard configuration information. In another embodiment, the configuration server identifies the service content received by the configuration interface and generates the service execution logic based on the identification result.

[0128] In the specific implementation, the configuration server can generate the business execution logic of the changed function based on the identified execution conditions and / or execution operations of the changed function, or generate the business execution logic based on the execution operation of the changed function.

[0129] The business execution logic may be an association relationship structure or an execution file generated according to execution operations and execution conditions.

[0130] In a possible implementation, the association structure may be an association list, which may be called an actions list in this implementation, or may be called any list used to express associations. The actions list includes multiple actions, each of which includes an execution condition and an execution operation associated with the execution condition. The logical relationship between multiple actions in the actions list may be serial or parallel, and the logical relationship between multiple execution conditions included in the same action may be serial or parallel.

[0131] In a possible implementation, an action is generated according to the execution condition and the execution operation associated with the execution condition. The action includes a logical relationship keyword, which is used to characterize the logical relationship between the various execution conditions in the action. For example, the logical relationship between multiple execution conditions included in the same action can be characterized by keywords such as "and" and "or".

[0132] Based on this, multiple actions can be generated, and then based on the logical relationship between the multiple actions, an actions list is constructed according to the generated multiple actions, that is, the association relationship structure mentioned above. The actions list includes logical relationship keywords, which are used to represent the logical relationship between multiple actions in the actions list.

[0133] For example, the logical relationship between multiple actions in the actions list can be represented by keywords such as "and", "or", etc., and the logical relationship between multiple execution conditions included in the same action can be represented by keywords such as "and", "or", etc.

[0134] In the above embodiment, a technical solution is involved for implementing personalized changes of functions in the configuration management platform by inputting business content through a configuration interface. In this embodiment, the configuration server may also record the historical configuration of the CDN user so that the CDN user can subsequently select the historical configuration to change the function. Exemplarily, the method described above also includes: generating configuration record information based on the currently input business content, and the configuration record information is used to provide a reference for the next configuration. The configuration record information may be an execution condition previously selected by the CDN user, an execution operation previously selected by the CDN user, or a logic code previously input by the CDN user.

[0135] Exemplary, reference Figure 6 In the configuration interface, the drop-down menu of the execution condition selection item includes the execution conditions historically selected by the CDN user, and the drop-down menu of the execution operation selection item includes the execution operations historically selected by the CDN user.

[0136] refer to Figure 7 When the CDN user moves the cursor to the logic code input item, the configuration interface of the configuration management platform can display the logic code historically input by the CDN user, and prompt the CDN user whether to reuse the logic code historically input.

[0137] In the embodiment of the present application, the reuse of CDN user configuration is supported, the flexibility of the configuration management platform function personalized customization service is improved, and the matching degree between the configuration service and the CDN user needs is improved.

[0138] The above embodiment involves a technical solution of receiving a CDN user-defined logic code through a configuration interface. In another embodiment of the present application, the configuration interface can also be updated based on the CDN user-defined logic code to add some CDN user-defined execution conditions and execution operations. Figure 2 The method shown also includes: parsing the logic code of the changed function, obtaining the execution conditions and execution operations contained in the logic code, and adding the execution conditions and execution operations contained in the logic code to the configuration interface; or, adding the logic code of the changed function to the configuration interface.

[0139] In a specific implementation, after the configuration server receives the CDN user-defined logic code through the configuration interface, it can also identify the execution conditions, execution operations, and the relationship between the two from the logic code. Furthermore, the options for these execution conditions and these execution operations can be added on the configuration interface, and the CDN user can also select the newly added execution conditions and execution operations on the configuration interface according to business needs. Alternatively, the configuration server also supports the overall reuse of the CDN user-defined logic code. For example, the CDN user inputs the customized logic code through the logic code input item to implement the addition of function A. When the CDN user logs in to the configuration management platform again, the configuration interface of the configuration management platform can display the logic code of function A. If the execution logic of the new function to be added by the CDN user is the same as function A, the CDN user can reuse the execution logic of function A and modify the code-related parameters (for example, input parameters, etc.).

[0140] This application can realize the reuse of CDN user-defined logic code, while realizing personalized customization of services, improving the matching degree between configuration services and CDN user needs.

[0141] In the above embodiment, a configuration interface is provided for CDN users to receive the business content of the changed function through the configuration interface. In another embodiment, the configuration server can also prompt CDN users to avoid too much nesting of execution logic through the configuration interface to further standardize the configuration behavior of CDN users. Exemplarily, the configuration interface described above also includes nesting level prompt information. The nesting level prompt information is used to indicate the limit of the number of nested execution logics under a single execution operation.

[0142] It should be noted that the limit value of the number of execution logics that can be nested under a single execution operation is used to characterize the maximum number of execution logics that can be nested under a single execution operation. Exemplarily, the execution logic is used to characterize the association between the execution condition and the execution operation, and the execution logic can be characterized by an action or an actions list, and the limit value of the number of execution logics that can be nested under a single execution operation can be the number of actions that can be nested under a single execution operation.

[0143] In a possible implementation, the configuration server may perform nesting level detection on the business content input by the CDN user, and output nesting level prompt information in real time during the CDN user input process based on the detection result. Specifically, when the number of execution logics that the CDN user has nested under a certain execution operation OP reaches the above-mentioned number limit, the nesting level prompt information is output to prompt the CDN user to stop adding execution logic under the execution operation, or to delete part of the execution logic that has been added under the execution operation.

[0144] Exemplary, reference Figure 8, the execution logics added by the CDN user under the execution operation "redirect" include action1, action2, action3 and action4. Assuming that the limit of the number of nested execution logics under a single execution operation is 4, it indicates that the currently nested execution logic under the execution operation "redirect" has reached the limit. When the CDN user clicks the "Add" control, the configuration interface can display the nesting level prompt information: "The nested execution logic under the current OP has reached the upper limit, please save the current configuration". It should be noted that the above information is only a possible implementation of the nesting level prompt information. The embodiment of the present application does not limit the specific text content contained in the nesting level prompt information. Any information that can prompt the nesting level belongs to the protection scope of the embodiment of the present application.

[0145] In another possible implementation, the configuration interface includes a fixed display area for nesting level prompt information, and when the CDN user logs into the configuration management platform, the configuration interface presents the nesting level prompt information. Fig. 9 , "The number of nested execution logics under a single OP cannot exceed 5" is displayed at the top of the display interface. The number of nested execution logics under the execution operation selected by the CDN user on the configuration interface cannot exceed 5, or the number of nested execution logics under a single execution operation in the logic code entered by the CDN user on the configuration interface cannot exceed 5.

[0146] In the above embodiment, the configuration server can provide a configuration interface for the CDN user to receive the service content of the changed function through the configuration interface. In another embodiment, the configuration server can also detect the service content input by the CDN user after the CDN user completes the configuration of the changed function, so as to avoid the CDN user from nesting too much execution logic under a single execution operation, so as to further standardize the configuration behavior of the CDN user. For example, refer to Fig.10 The method described in the embodiment of the present application further includes the following steps:

[0147] 1001. Get the number of nested execution logics under the current single operation;

[0148] It should be noted that the current single operation may be a single execution operation selected by the CDN user in the configuration interface, or may be a single execution operation in a custom logic code input by the CDN user.

[0149] In a specific implementation, obtaining the number of nested execution logics under the current single operation may be to parse the content input by the CDN user in the configuration interface to determine the number of nested execution logics under the single execution logic.

[0150] 1002. If the number of nested execution logics under a single execution operation exceeds the quantity limit, output adjustment information; the adjustment information is used to instruct the CDN user to adjust the number of nested execution logics.

[0151] The quantity limit may be the maximum number of nested execution logics under a single execution operation. To avoid excessive code nesting and affecting the executability of the code, when the number of currently nested execution logics exceeds the quantity limit, adjustment information may be output to instruct the CDN user to adjust the number of nested execution logics.

[0152] Exemplary, reference Fig.11 After the CDN user selects the execution condition and executes the operation in the configuration interface, he clicks the "Confirm" control. If the configuration server of the configuration management platform determines that there is an execution operation with a nested level exceeding the limit, it outputs the adjustment information "Please modify the nested execution logic under OP, the number cannot exceed 5". The embodiment of the present application does not limit the specific text content contained in the adjustment information, and any information that can prompt the CDN user to adjust the nested level belongs to the protection scope of the embodiment of the present application.

[0153] The present application also provides a method for implementing a service, which is applicable to Figure 1 The edge servers in the system shown. Fig.12 , the method comprises the following steps:

[0154] 1201. Receive a configuration update instruction sent by a configuration server, and generate a service execution logic according to the standard configuration information in the configuration update instruction; or, receive a service execution logic sent by a configuration server, where the service execution logic is generated by the configuration server according to the standard configuration information; the standard configuration information is used to characterize the association between the execution condition of the changed function and the execution operation;

[0155] That is, the edge server can receive the service execution logic generated by the configuration server, or can generate the service execution logic based on the standard configuration information sent by the configuration server, wherein the standard configuration information can be a configuration text.

[0156] In a specific implementation, the configuration update instruction is an instruction obtained by the configuration server after encapsulating the standard configuration information of the changed function, and is used to instruct the edge server to add functions to the edge server according to the CDN user configuration.

[0157] In addition, the specification configuration information is used to represent the execution logic of the changed function. For example, the specification configuration information may be used to represent the association between the execution condition of the changed function and the execution operation.

[0158] In a possible implementation, the association between the execution condition and the execution operation can be understood as: the execution operation is executed under the premise that the execution condition is met. Exemplarily, the execution condition is "the destination IP address is 111.00.10.11", and the execution operation associated with it is "forbidden access", that is, when the IP address accessed by the user of the user terminal 30 is 111.00.10.11, the edge server prohibits the user of the user terminal 30 from accessing.

[0159] It should be noted that the specification configuration information can be an association structure (action) or other information used to characterize the relationship between the execution conditions and the execution operations. For example, the specification configuration information can be text information used to describe the execution conditions, the execution operations, and the association between the two. The embodiments of the present application do not limit the specific implementation of the specification configuration information, and any information that can characterize the execution conditions, the execution operations, and the relationship between the two belongs to the protection scope of the embodiments of the present application.

[0160] In one possible implementation, the business execution logic may include execution codes of various functions of the edge server, supporting the background implementation of various functions provided by the edge server. Since the standard configuration information can represent the execution logic of the changed function, the edge server generates an execution file of the edge server based on the standard configuration information, which can support the normal launch of the changed function.

[0161] In a specific implementation, the standard configuration information may include a configuration text, and the edge server may perform text parsing on the standard configuration information, identify the execution logic of the changed function, and support the background implementation of the changed function based on the business execution logic of the changed function, so as to achieve the rapid launch of the changed function. Exemplarily, the edge server may pre-code the configuration text and generate the business execution logic.

[0162] Alternatively, after obtaining the business content, the configuration server generates business execution logic according to the business content and sends the business execution logic to the edge server. The edge server can use the business execution logic sent by the configuration server as the business execution logic after the edge server changes its function.

[0163] 1202. When receiving a user request corresponding to the above-mentioned business execution logic, execute the business execution logic to process the user request.

[0164] The user request corresponding to the execution service execution logic may be the user request sent by the user terminal 30. When the edge server receives the user request corresponding to the service execution logic, it may determine whether the user request matches the execution condition in the service execution logic, and process the user request based on the matching result.

[0165] Fig.12 In the method shown, the edge server receives the standardized configuration information of the changed function and can automatically and quickly generate the execution file corresponding to the edge server, without modifying the logic of the underlying framework, and avoiding the online delay caused by the inconsistent business configuration of the new and old functions when configuring new functions, greatly shortening the online delay of personalized CDN services, and improving the scalability of the business, so as to realize the rapid online of the changed business on the edge server. By shortening the online delay of the business, the problem of serious limitation of the development of personalized customization of CDN services is solved, which is generally conducive to the development of personalized customization business based on CDN services.

[0166] In the above-mentioned embodiments, a technical solution for generating business execution logic according to standard configuration information is involved. In another embodiment, a specific implementation scheme for generating business execution logic by a server is provided. Exemplarily, the above-mentioned server generates business execution logic according to standard configuration information, including:

[0167] Parse the configuration text in the standard configuration information, and generate the business execution logic according to the execution conditions and execution operations obtained by the analysis; or parse the configuration text in the standard configuration information, and generate the business execution logic according to the execution operations obtained by the analysis.

[0168] It should be noted that when the configuration server normalizes the business content obtained from the configuration interface, it can generate configuration text or business execution logic. The edge server can receive the business execution logic sent by the configuration server as the business execution logic after the edge server function is changed. The edge server may also parse the configuration text from the configuration update instruction, and identify the configuration text to obtain the execution conditions and execution operations, thereby generating the business execution logic based on the obtained execution conditions and execution operations. Of course, if the function of the edge server is to perform certain execution operations under any conditions, parsing the configuration text may not obtain the execution conditions, but only the execution operations, and the edge server can generate the business execution logic based on the obtained execution operations.

[0169] In the embodiment described above, the edge server can generate the business execution logic according to the specification configuration information. In another embodiment, the edge server can generate the business execution logic according to the specification configuration information and the service layer logic code of the existing functions of the edge server. The edge server can integrate the service layer logic code of the existing functions of the edge server and the execution logic of the changed functions to generate a corresponding business execution logic (for example, an association relationship structure actions list) as the execution file of the edge server to support the background implementation of various functions of the edge server.

[0170] In a possible implementation, the business execution logic is generated according to the specification configuration information and the service layer logic code of the existing functions of the edge server, including:

[0171] Parse the service layer logic code and the configuration text in the specification configuration information, and generate the business execution logic according to the execution conditions and execution operations obtained by the analysis; or generate the business execution logic according to the execution operations obtained by the analysis.

[0172] That is to say, if the standard configuration information is a configuration text, the edge server can parse the configuration text and the logic code of the existing function, and generate the business execution logic based on the execution conditions and execution operations obtained by the parsing. The edge server is supported to integrate the business execution logic of various functions, and the business execution logic on the edge server side is updated as a whole, making the business execution logic of the edge server more unified and simple.

[0173] In another possible implementation, the edge server may generate the business execution logic according to the service layer logic code and the business execution logic sent by the configuration server.

[0174] That is to say, if the configuration server generates the business execution logic after receiving the business content input by the user, the edge server can generate the business execution logic after the edge server function is changed based on the business execution logic of the existing functions of the edge server and the business execution logic sent by the configuration server. It supports the independent maintenance of the existing functions and the changed functions of the edge server, and also reduces the processing load on the edge server side.

[0175] In the specific implementation, the edge server integrates the service layer logic code of the existing functions and the execution logic of the changed functions, and generates an association structure (for example, an actions list) corresponding to the edge server as the execution file of the edge server to support the background implementation of various functions of the edge server.

[0176] The above embodiment involves a technical solution for generating a new execution file of the edge server based on the standard configuration information and the logic code of the existing functions of the edge server. In another embodiment, the standard configuration information and the existing service layer logic code can be parsed respectively, and the execution file of the edge server can be generated according to the execution conditions and execution actions obtained by the parsing.

[0177] Specifically, the specification configuration information is parsed to obtain a plurality of first execution conditions and a plurality of first execution operations; the service layer logic code is parsed to obtain a plurality of second execution conditions and a plurality of second execution operations;

[0178] An execution file is generated according to the plurality of first execution conditions, the plurality of first execution operations, the plurality of second execution conditions, and the plurality of second execution operations.

[0179] It should be noted that the above analysis process can be a logic identification process for identifying execution conditions and execution operations associated with the execution conditions. In addition, the standard configuration information carried by the business implementation instruction can be an association structure (including one or more actions) or other information representing the execution logic.

[0180] In the method provided in the embodiment of the present application, the edge server can generate an execution file of the edge server based on the standard configuration information sent by the configuration server and the logic code of the existing functions. Without modifying the underlying code of the edge server, the grayscale time caused by modifying the underlying code is avoided, and the new functions can be quickly launched.

[0181] In the above embodiment, the edge server can parse the execution conditions and execution operations according to the specification configuration information and the logic code of the existing functions to generate the business execution logic of the edge server. In another embodiment, the edge server can generate the association relationship structure corresponding to the newly added function and the existing function respectively, which constitutes the business execution logic of the edge server and supports the background implementation of the changed function and the existing function. Exemplarily, the above-mentioned generation of the business execution logic according to multiple first execution conditions, multiple first execution operations, multiple second execution conditions and multiple second execution operations includes:

[0182] Generate a first association relationship structure according to a plurality of first execution conditions and a first execution operation corresponding to each first execution condition; generate a second association relationship structure according to a plurality of second execution conditions and a second execution operation corresponding to each second execution condition;

[0183] Generate business execution logic according to the first association relationship structure and the second association relationship structure.

[0184] In a specific implementation, for each first execution condition, an action is generated according to the execution condition and the execution operation associated with the execution condition. Based on the logical relationship between the actions corresponding to the first execution conditions, a first association relationship structure can be generated. The logical relationship between the actions corresponding to the first execution conditions can be represented by keywords such as and or or.

[0185] Accordingly, for each second execution condition, an action is generated according to the execution condition and the execution operation associated with the execution condition. Based on the logical relationship between the actions corresponding to the second execution conditions, a second association relationship structure can be generated. The logical relationship between the actions corresponding to the second execution conditions can be represented by keywords such as and or or.

[0186] The business execution logic of the edge server can also be generated according to the logical relationship between the first association relationship structure and the second association relationship structure. Exemplarily, if the logical relationship between the existing function and the changed function is a series logic, "and" can be used in the business execution logic to represent the logical relationship between the first association relationship structure and the second association relationship structure. The execution result of one of the existing functions and the changed function is the input parameter of the execution code of the other function, and the functions of the edge server are logically coupled. Alternatively, if the logical relationship between the existing function and the changed function is a parallel logic, "or" can be used in the business execution logic to represent the logical relationship between the first association relationship structure and the second association relationship structure. The existing function and the changed function are executed in parallel, and the logic is decoupled.

[0187] The embodiment of the present application provides an implementation method for an edge server to generate the business execution logic of the edge server according to standard configuration information and logic codes of existing functions, while realizing standardized management of personalized customization of CDN cloud services, supporting the background implementation of existing functions and changed functions of the edge server.

[0188] In the above embodiment, the server parses execution conditions and execution operations according to the standard configuration information and the logic code of the existing functions, and generates the business execution logic of the edge server. In another embodiment, the standard configuration information from the configuration server is an association structure (for example, a first association structure), and the edge server can generate a second association structure according to the logic code of the existing functions of the edge server, and generate the business execution logic of the edge server based on the first association structure and the second association structure. Exemplarily, the business execution logic is generated according to the standard configuration information and the service layer logic code of the existing functions of the edge server, including:

[0189] The service layer logic code is parsed to obtain multiple execution conditions and multiple execution operations of the existing functions, and a second association relationship structure is generated according to the multiple execution conditions and multiple execution operations of the existing functions; and business execution logic is generated according to the first association relationship structure and the second association relationship structure.

[0190] The first association relationship structure is generated by the configuration server according to the business content input in the configuration interface. An implementation method is provided for the edge server to generate the business execution logic of the edge server according to the standard configuration information and the logic code of the existing functions, while realizing the standardized management of the personalized customization of the CDN cloud service, and supporting the background implementation of the existing functions and changed functions of the edge server.

[0191] In the above embodiment, a technical solution is provided for generating the business execution logic of the edge server based on the standardized configuration of the configuration server, or updating the business execution logic of the edge server. In another embodiment, a technical solution is also provided for processing user requests based on the business execution logic of the edge server. Exemplarily, the "executing the business execution logic to process the user request" involved in step 1203 above specifically includes:

[0192] The edge server can determine the matching result between the user request and the execution logic in the service execution logic, and process the target service according to the matching result.

[0193] The user request is a request initiated by the user terminal 30.

[0194] In a possible implementation, the edge server determines whether the user request matches each execution logic in the service execution logic, and determines how to process the user request based on the matching result, for example, rejecting the service request or responding to the service request. Exemplarily, the service execution logic includes the execution logic corresponding to "authentication" and the execution logic corresponding to "URL control". If the data access request matches the execution logic corresponding to "authentication" and the execution logic corresponding to "URL control", the data access request is responded to and the requested data is returned to the configuration server; if the data access request does not match the execution logic corresponding to "authentication" or the execution logic corresponding to "URL control", the data access service requested by the user terminal 30 is rejected.

[0195] The embodiment of the present application provides a specific implementation scheme for processing business requests based on the business execution logic of the edge server, supporting the practical application of various functions of the edge server.

[0196] In the above embodiment, the edge server receives the service execution logic. In another embodiment, a technical solution for processing a user request based on the execution logic in the service execution logic is also provided. Exemplarily, the above-mentioned processing of the user request according to the matching result includes: determining whether the user request matches the execution condition in the service execution logic;

[0197] If the user request matches the target execution condition in the business execution logic, the user request is processed according to the target execution operation associated with the target execution condition.

[0198] In the specific implementation, the execution logic in the business execution logic is traversed, and the user request is matched with the execution conditions in the execution logic one by one. If the user request matches an execution condition, the user request is processed according to the execution operation associated with the execution condition.

[0199] For example, the user request may be a data access request, assuming that the IP address of the user terminal 30 is 111.00.10.11. After receiving the data access request from the user terminal 30, the edge server determines that the execution condition matching the data access request is ACL1 "IP address is 111.00.10.11", and then processes the data access service requested by the user terminal 30 according to the OP associated with ACL1. For example, access is prohibited, or access is delayed.

[0200] The embodiment of the present application provides an implementation scheme for edge server functions, which can control user requests based on execution logic, and realize the control of user requests while realizing standardized management of personalized customization of CDN cloud services.

[0201] In an embodiment of the present application, nested sub-execution logic is allowed under a single execution operation. The following provides a specific solution for how to process user requests in a scenario where sub-execution logic is nested under a single execution operation. Exemplarily, sub-execution logic can be nested under a target operation matched by a user request, and the sub-execution logic includes sub-execution conditions and sub-operations. The specific implementation of processing user requests according to the target operation in the target execution logic involved in the foregoing includes: determining the target sub-execution condition that matches the user request, and processing the user request according to the sub-operation associated with the target sub-execution condition.

[0202] In the specific implementation, all sub-execution logics under the target operation are traversed, and the business request message is matched with the execution conditions in the execution logic one by one. If the business request message matches an execution condition, the user request is processed according to the execution operation associated with the execution condition.

[0203] The embodiment of the present application also provides a specific implementation of the business execution logic. Specifically, the business execution logic specifically includes description information of the execution operation under each execution logic. The description information includes: execution operation identifier and / or sub-execution logic.

[0204] That is to say, the execution operation can be a specific underlying operation. For example, the description information of the execution operation in the business execution logic is "test". If the execution conditions in the execution logic are met, "test" is executed. Of course, it is allowed to nest sub-execution logic under a single execution operation, that is, the description information of the execution operation can be an "association relationship structure", that is, the description information of the execution operation is used to indicate the sub-execution logic nested under a single execution operation. It should be noted that multiple sub-execution logics nested under a single execution operation can be called a block data body (block), and the block nested under a single OP is called the sub-execution logic nested under the OP.

[0205] The embodiments of the present application can implement the functions of the edge server based on logically nested codes, thereby improving the diversity of the implementation of the edge server functions.

[0206] In the above embodiment, the edge server can generate the business execution logic of the edge server based on the standardized configuration information sent by the configuration server. In another embodiment, the edge server can also control the nesting level of the business execution logic to avoid too many sub-execution logics being nested under a single execution operation, resulting in the problem of excessive execution complexity of the business execution logic. Exemplarily, after the edge server generates the business execution logic, the method also includes: determining the nesting level of each execution operation in the business execution logic. If there is an abnormal operation whose nesting level exceeds the limit, adjustment information is sent to the monitoring server (also referred to as a monitoring platform); the adjustment information is used to instruct the monitoring server to notify the CDN user to adjust the nesting level of the abnormal operation.

[0207] The nesting level is used to characterize the number of nested execution logics under the execution operation, and may be a preset value to avoid too many nested sub-execution logics under a single execution operation.

[0208] In the embodiment of the present application, after the new function of the edge server is launched, the edge server can control the nesting level and instruct the CDN user to adjust the nesting level through the monitoring platform. The edge server controls the nesting level through the monitoring platform, which can greatly reduce the processing load of the server while realizing standardized personalized business customization.

[0209] Taking the execution condition as ACL, the execution operation as OP, and the execution logic as action as an example, the edge server can match the user request sent by the edge server based on the actions list sent by the configuration server (i.e., the business execution logic described above) to process the business requested by the user according to the matching result. Fig.13 , the specific steps are as follows:

[0210] 1301. Traverse each action in the actions list and execute each action in the list.

[0211] Among them, action can be considered as the execution logic described in the embodiment of the present application, including the execution condition ACL and the execution operation OP associated with the execution condition ACL.

[0212] 1302. For the currently executed action, traverse each ACL in the executed action to determine the execution result.

[0213] If the execution result is "false", the OP in the action is not executed, and step 1305 is executed; if the execution result is "true", step 1303 is executed.

[0214] It should be noted that the execution logic of the ACL in the action can be and, or, or not. The execution result of the action is determined to be "true" or "false" based on the execution results of each ACL and the execution relationship of the ACL. For example, the action includes ACL1, ACL2, and ACL3, and the execution logic of the three is "and". If the execution results of ACL1, ACL2, and ACL3 are all "true", the execution result of the action is "true". If ACL1, ACL2, and ACL3 have an execution condition with an execution result of "false", the execution result of the action is "false".

[0215] 1303. Determine whether the type of OP in action is block (block execution logic).

[0216] If yes, then execute step 1304; if no, then execute the action corresponding to OP. The corresponding action can be OP input by the CDN user on the configuration interface, or it can be a custom function input by the CDN user on the configuration interface.

[0217] 1304. Traverse all actions lists in the block and execute each action in the actions list.

[0218] In the specific implementation, when the OP type is block, it indicates that actions logic is nested under the OP. The nested actions list under the OP will be traversed to traverse and execute each action logic in the list. For specific implementation, refer to 1302 to 1305.

[0219] 1305. End the current action logic, traverse the next action, and repeat 1302.

[0220] It should be noted that the nested actions list under OP can support various logical combinations. However, the number of nested actions lists under OP, that is, the number of nesting levels, cannot exceed the preset limit to avoid infinite nested loops in the code and improve the feasibility of business execution logic.

[0221] The embodiment of the present application also provides a service implementation method, which involves the interaction between the edge server, the configuration server and the user terminal mentioned above. Fig.14 , the method comprises the following steps:

[0222] 1401. The configuration server obtains standard configuration information through the configuration interface, where the standard configuration information is used to represent the association between the execution condition of the changed function and the execution operation;

[0223] 1402a. The configuration server sends a configuration update instruction to the edge server; the configuration update instruction includes standard configuration information;

[0224] 1402b. The configuration server sends the service execution logic to the edge server; the service execution logic is generated according to the specification configuration information;

[0225] 1403a. The edge server receives the configuration update instruction sent by the configuration server and generates the service execution logic according to the standard configuration information;

[0226] 1403b. The edge server receives the service execution logic sent by the configuration server;

[0227] 1404. The user terminal sends a user request to the edge server;

[0228] 1405. The edge server receives the user request sent by the user terminal, and processes the user request based on the business execution logic.

[0229] 1406. The edge server sends the processing result of the user request to the user terminal.

[0230] It should be noted that Fig.14 The specific implementation of each step in the method shown is referred to the above description, and will not be repeated here. 1402a and 1402b can be executed at one, and 1403a and 1403b are also executed at one. When 1402a is executed, 1403a is executed, and when 1402b is executed, 1403b is executed.

[0231] The embodiment of the present application also provides a service implementation system, the system structure is as follows Figure 1 shown.

[0232] Specifically, the configuration management platform includes a configuration interface and a configuration server; the configuration interface is used to provide CDN users or platform operation and maintenance personnel with configuration operations to generate standardized configuration information;

[0233] The configuration server is used to obtain the standard configuration information through the configuration interface, and the standard configuration information is used to represent the association between the execution condition of the changed function and the execution operation; the configuration server is also used to send a configuration update instruction to the edge server;

[0234] The edge server is used to receive the configuration update instruction sent by the configuration server, and generate the business execution logic according to the standard configuration information in the configuration update instruction; or, receive the business execution logic sent by the configuration server, and the business execution logic is generated by the configuration server according to the standard configuration information; the edge server is also used to, when receiving a user request corresponding to the business execution logic, execute the business execution logic to process the user request.

[0235] The present application also provides a service implementation device, referring to Fig.15 , the device includes: a processing unit 1501 and a communication unit 1502.

[0236] The processing unit 1501 is used to obtain the standard configuration information through the configuration interface, where the standard configuration information is used to represent the association between the execution condition of the changed function and the execution operation;

[0237] The communication unit 1502 is used to send a configuration update instruction to the edge server; the configuration update instruction includes standard configuration information, and the configuration update instruction is used to instruct the edge server to generate a service execution logic according to the standard configuration information.

[0238] In one embodiment, the changed function includes: a changed function of an original function, a function added based on the original function, or a newly added function;

[0239] The changed function includes at least one of the following: deleting the function after configuring the original function of the edge server, modifying the function after configuring the original function of the edge server, and adding a sub-function to the original function of the edge server.

[0240] In one embodiment, the configuration interface includes a configuration interface, and the processing unit 1501 is specifically configured to obtain the business content currently input to the configuration interface of the configuration edge server, and determine the standard configuration information according to the business content.

[0241] In one embodiment, the processing unit 1501 is specifically used to perform logic identification processing on the business content to obtain the execution condition and / or execution operation of the changed function;

[0242] Generate the specification configuration information based on the execution condition and execution operation of the changed function; or generate the specification configuration information based on the execution operation of the changed function.

[0243] In one embodiment, the specification configuration information includes configuration text.

[0244] In one embodiment, the configuration interface includes configurable items for standardizing business content.

[0245] In one embodiment, the configuration interface includes one or more of configurable items for executing operations, configurable items for executing conditions, and logic code input items.

[0246] In one embodiment, the processing unit 1501 is further used to generate configuration record information according to the currently input service content, and the configuration record information is used to provide a reference for the next configuration.

[0247] In one embodiment, if the business content includes the logic code of the changed function, the processing unit 1501 is also used to parse the logic code of the changed function, obtain the execution conditions and execution operations contained in the logic code, and add the execution conditions and execution operations contained in the logic code to the configuration interface; or, add the logic code of the changed function to the configuration interface.

[0248] In one embodiment, the configuration interface further includes nesting level prompt information; the nesting level prompt information is used to indicate the limit value of the number of execution logics that can be nested under a single execution operation.

[0249] In one embodiment, the processing unit 1501 is further used to obtain the number of nested execution logics under the current single execution operation;

[0250] If the number of nested execution logics under a single execution operation exceeds the quantity limit, adjustment information is output; the adjustment information is used to instruct the CDN user to adjust the number of nested execution logics.

[0251] The present application also provides a service implementation device, such as Fig.16 As shown, the device includes: a communication unit 1601 and a processing unit 1602.

[0252] The communication unit 1601 is used to receive a configuration update instruction sent by the configuration edge server, where the configuration update instruction includes standard configuration information; the standard configuration information is used to characterize the association between the execution condition and the execution operation of the changed function of the configuration edge server;

[0253] The processing unit 1602 is used to generate a service execution logic according to the specification configuration information; when the communication unit 1601 receives a user request corresponding to the service execution logic, the service execution logic is executed to process the user request.

[0254] In one embodiment, the processing unit 1602 is specifically configured to parse the configuration text in the standard configuration information, and generate the business execution logic according to the execution conditions and execution operations obtained by the parsing; or

[0255] The configuration text in the standard configuration information is parsed, and the business execution logic is generated according to the execution operation obtained by the parsing.

[0256] In one embodiment, the processing unit 1602 is specifically configured to generate service execution logic according to the specification configuration information and the service layer logic code of the existing functions of the edge server.

[0257] In one embodiment, the processing unit 1602 is specifically used to parse the configuration text and service layer logic code in the standard configuration information, and generate business execution logic according to the execution conditions and execution operations obtained by the analysis; or generate business execution logic according to the execution operations obtained by the analysis.

[0258] In one embodiment, the processing unit 1602 is specifically configured to generate a service execution logic after the function of the edge server is changed according to the service layer logic code and the service execution logic sent by the edge server.

[0259] In one embodiment, the processing unit 1602 is specifically used to determine whether the user request matches the execution condition in the service execution logic;

[0260] If the user request matches the target execution condition in the business execution logic, the user request is processed according to the target execution operation associated with the target execution condition.

[0261] In one embodiment, if sub-execution logic is nested under the target execution operation, the sub-execution logic includes sub-execution conditions and sub-operations; the processing unit 1602 is specifically used to determine the target sub-execution condition that matches the user request, and process the user request according to the sub-operation associated with the target sub-execution condition.

[0262] In one embodiment, the service execution logic specifically includes description information of each execution operation; the description information includes: an execution operation identifier and / or sub-execution logic.

[0263] In one embodiment, the processing unit 1602 is further used to determine the nesting level of each execution operation in the service execution logic; the nesting level is used to represent the number of service execution logics nested under the execution operation;

[0264] If there is an abnormal operation whose nesting level exceeds the limit, adjustment information is sent to the monitoring edge server through the communication unit 1602; the adjustment information is used to instruct the monitoring edge server to notify the configuration edge server to adjust the nesting level of the abnormal operation.

[0265] The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the business implementation method described above is implemented.

[0266] An embodiment of the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the service implementation method described above when executing the computer program.

[0267] In a possible implementation, the computer device may be a server. For example, Figure 1 The server 10 in the system shown in FIG. Fig.17 As shown. The computer device includes a processor, a memory and a network interface connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device can store configuration information, permission information, etc. The network interface of the computer device is used to communicate with an external terminal via a network connection.

[0268] In another possible implementation, the computer device may be a terminal device, for example, Figure 1The configuration server 20 in the system shown in the figure may have an internal structure diagram as shown in 18. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a configuration method for an application package described in an embodiment of the present application is implemented. The display screen of the computer device may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device may be a touch layer covered on the display screen, or a button, a trackball or a touchpad provided on the housing of the computer device, or an external keyboard, touchpad or mouse, etc.

[0269] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0270] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0271] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A service implementation method, characterized in that: Used to configure the server, including: Obtaining specification configuration information through a configuration interface, wherein the specification configuration information is used to characterize the association between the execution condition of the changed function and the execution operation, wherein the execution condition is a pre-check condition of the execution operation, and the associated execution operation is executed only when the execution condition is met, and the execution condition is a built-in encapsulated ACL condition, or the execution condition is customized based on the ACL interface specification; Sending a configuration update instruction to an edge server so that the edge server generates a service execution logic, the configuration update instruction includes the specification configuration information; or, sending the service execution logic generated based on the specification configuration information to the edge server, the service execution logic includes: an actions list, the actions list includes multiple actions, each action includes the execution condition and the execution operation associated with the execution condition, the logical relationship between the multiple actions in the actions list includes serial or parallel, and the logical relationship between the multiple execution conditions included in the same action includes: serial or parallel; The configuration interface includes a configuration interface, and the obtaining of standard configuration information includes: Acquire the business content currently input into the configuration interface, and determine the standard configuration information according to the business content; The determining the standard configuration information according to the business content includes: Performing logic identification processing on the business content to obtain the execution condition and execution operation of the changed function, or obtaining the execution operation of the changed function; Based on the execution condition and execution operation of the changed function, or the execution operation of the changed function, an association relationship structure of the changed function is generated.

2. The method according to claim 1, characterized in that: The changed functions include: changed functions of original functions, functions added based on original functions, or newly added functions; The changed function includes at least one of the following: a function after deleting the original function of the edge server, a function after modifying the original function of the edge server, and a sub-function added to the original function of the edge server.

3. The method according to claim 1, characterized in that The specification configuration information includes configuration text.

4. The method according to claim 1, characterized in that: The configuration interface includes configurable items for standardizing the business content.

5. The method according to claim 4, characterized in that The configuration interface includes one or more of configurable items for executing operations, configurable items for executing conditions, and logic code input items.

6. The method according to claim 1, characterized in that If the business content includes the logic code of the changed function, the method further includes: Parsing the logic code of the changed function, obtaining the execution conditions and execution operations contained in the logic code, and adding the execution conditions and execution operations contained in the logic code to the configuration interface; Or, add the logic code of the changed function to the configuration interface.

7. The method according to claim 1, characterized in that The configuration interface also includes nesting level prompt information; the nesting level prompt information is used to indicate the limit value of the number of execution logics that can be nested under a single execution operation.

8. The method according to claim 7, characterized in that The method further comprises: Get the number of nested execution logics under the current single execution operation; If the number of nested execution logics under the single execution operation exceeds the quantity limit, adjustment information is output; the adjustment information is used to instruct the user to adjust the number of nested execution logics.

9. A service implementation method, characterized in that: The method comprises: Receive a configuration update instruction sent by a configuration server, and generate a business execution logic according to the standard configuration information in the configuration update instruction; or, receive the business execution logic sent by the configuration server, the business execution logic is generated by the configuration server according to the standard configuration information; the standard configuration information is used to characterize the association between the execution condition of the changed function and the execution operation, the execution condition is the pre-check condition of the execution operation, and the associated execution operation is executed only when the execution condition is met, the execution condition is a built-in encapsulated ACL condition, or the execution condition is customized based on the interface specification of the ACL; When receiving a user request corresponding to the service execution logic, executing the service execution logic to process the user request, the service execution logic comprising: an actions list, the actions list comprising multiple actions, each action comprising the execution condition and the execution operation associated with the execution condition, the logical relationship between the multiple actions in the actions list comprising serial or parallel, and the logical relationship between the multiple execution conditions included in the same action comprising: serial or parallel; Among them, the standard configuration information is determined by the configuration server according to the business content input into the configuration interface, and the determination process of the standard configuration information includes: performing logical identification processing on the business content to obtain the execution conditions and execution operations of the changed function, or obtain the execution operations of the changed function; based on the execution conditions and execution operations of the changed function, or the execution operations of the changed function, generate an association relationship structure of the changed function.

10. The method according to claim 9, characterized in that The generating of the business execution logic according to the specification configuration information includes: Parsing the configuration text in the specification configuration information, and generating the business execution logic according to the execution conditions and execution operations obtained by the parsing; or, The configuration text in the standard configuration information is parsed, and the business execution logic is generated according to the execution operation obtained by the parsing.

11. The method according to claim 9, characterized in that The generating of the business execution logic according to the specification configuration information includes: The business execution logic is generated according to the specification configuration information and the service layer logic code of the existing functions of the edge server.

12. The method according to claim 9, characterized in that The executing the service execution logic to process the user request includes: Determining whether the user request matches the execution condition in the service execution logic; If the user request matches the target execution condition in the service execution logic, the user request is processed according to the target execution operation associated with the target execution condition.

13. The method according to claim 12, characterized in that If the target execution operation is nested with sub-execution logic, the sub-execution logic includes sub-execution conditions and sub-operations; Then, processing the user request according to the execution operation associated with the target execution condition includes: A target sub-execution condition matching the user request is determined, and the user request is processed according to a sub-operation associated with the target sub-execution condition.

14. The method according to any one of claims 9 to 13, characterized in that: The business execution logic specifically includes description information of each execution operation; the description information includes: an execution operation identifier and / or a sub-execution logic.

15. A service implementation device, characterized in that: include: A processing unit, configured to obtain specification configuration information through a configuration interface, wherein the specification configuration information is used to characterize the association between the execution condition of the changed function and the execution operation, wherein the execution condition is a pre-check condition of the execution operation, and the associated execution operation is executed only when the execution condition is met, and the execution condition is a built-in encapsulated ACL condition, or the execution condition is customized for an interface specification based on the ACL; A communication unit, configured to send a configuration update instruction to an edge server so that the edge server generates a service execution logic; or, to send the service execution logic generated based on the specification configuration information to the edge server, wherein the service execution logic includes: an actions list, wherein the actions list includes multiple actions, each action includes the execution condition and the execution operation associated with the execution condition, wherein the logical relationship between the multiple actions in the actions list includes serial or parallel, and the logical relationship between the multiple execution conditions included in the same action includes: serial or parallel; The configuration interface includes a configuration interface, and the processing unit obtains standard configuration information, including: Acquire the business content currently input into the configuration interface, and determine the standard configuration information according to the business content; The determining the standard configuration information according to the business content includes: Performing logic identification processing on the business content to obtain the execution condition and execution operation of the changed function, or obtaining the execution operation of the changed function; Based on the execution condition and execution operation of the changed function, or the execution operation of the changed function, an association relationship structure of the changed function is generated.

16. A service implementation device, characterized in that: include: A processing unit, configured to receive a configuration update instruction sent by a configuration server through a communication unit, and generate a service execution logic according to the standard configuration information in the configuration update instruction; or, receive the service execution logic sent by the configuration server through the communication unit, the service execution logic is generated by the configuration server according to the standard configuration information; the standard configuration information is used to characterize the association relationship between the execution condition of the changed function of the edge server and the execution operation, the execution condition is a pre-check condition of the execution operation, and the associated execution operation is executed only when the execution condition is met, the execution condition is a built-in encapsulated ACL condition, or the execution condition is customized for the interface specification based on the ACL; The processing unit is further configured to, when receiving a user request corresponding to the service execution logic, execute the service execution logic to process the user request, the service execution logic comprising: an actions list, the actions list comprising a plurality of actions, each action comprising the execution condition and the execution operation associated with the execution condition, the logical relationship between the plurality of actions in the actions list comprising serial or parallel, and the logical relationship between the plurality of execution conditions included in the same action comprising: serial or parallel; Among them, the standard configuration information is determined by the configuration server according to the business content input into the configuration interface, and the determination process of the standard configuration information includes: performing logical identification processing on the business content to obtain the execution conditions and execution operations of the changed function, or obtain the execution operations of the changed function; based on the execution conditions and execution operations of the changed function, or the execution operations of the changed function, generate an association relationship structure of the changed function.

17. A business implementation system, characterized in that: include: Configuration management platform, including configuration interface and configuration server; The configuration interface is used to perform configuration operations to generate standard configuration information; The configuration server is used to obtain the standard configuration information through the configuration interface, where the standard configuration information is used to represent the association between the execution condition of the changed function and the execution operation; The configuration server is further used to send a configuration update instruction to the edge server, the execution condition is a pre-check condition of the execution operation, and the associated execution operation is executed only when the execution condition is met, and the execution condition is a built-in encapsulated ACL condition, or the execution condition is customized for an interface specification based on the ACL; The edge server is configured to receive the configuration update instruction sent by the configuration server, and generate a service execution logic according to the standard configuration information in the configuration update instruction; or receive the service execution logic sent by the configuration server, where the service execution logic is generated by the configuration server according to the standard configuration information; The edge server is further used to, when receiving a user request corresponding to the service execution logic, execute the service execution logic to process the user request, the service execution logic comprising: an actions list, the actions list comprising multiple actions, each action comprising the execution condition and the execution operation associated with the execution condition, the logical relationship between the multiple actions in the actions list comprising serial or parallel, and the logical relationship between the multiple execution conditions included in the same action comprising: serial or parallel; The configuration interface includes a configuration interface, and the obtaining of standard configuration information includes: Acquire the business content currently input into the configuration interface, and determine the standard configuration information according to the business content; The determining the standard configuration information according to the business content includes: Performing logic identification processing on the business content to obtain the execution condition and execution operation of the changed function, or obtaining the execution operation of the changed function; Based on the execution condition and execution operation of the changed function, or the execution operation of the changed function, an association relationship structure of the changed function is generated.

18. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 14 are implemented.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 14 are implemented.

Images