Disclosure of Invention
In view of the foregoing, it is desirable to provide a flexible and efficient service processing method, apparatus, computer device and storage medium.
A method of traffic processing, the method comprising:
receiving service data, and acquiring call chain configuration data corresponding to the service data;
generating a call chain for the instantiated nodes in the service flow corresponding to the service data according to the call chain configuration data;
sequentially executing each node in the call chain;
aiming at the nodes of the abnormal interrupt link, waiting for the asynchronous task to pull up the abnormal interrupt link again, and aiming at the nodes which are processed normally and failed in processing, storing the generated data into a result data pool;
and acquiring a service object result template, filling data in the result data pool into the service object result template to obtain a service processing result, and feeding back the service processing result to a service object.
In one embodiment, the receiving the service data and acquiring the call chain configuration data corresponding to the service data includes:
receiving service data;
performing standard structuralization processing on the service data to obtain service data with a standard structure;
preprocessing the service data of the standard structure to generate data required by a call chain;
and generating calling chain configuration data according to the data required by the calling chain.
In one embodiment, the performing standard structured processing on the service data to obtain service data with a standard structure includes:
acquiring a preset data conversion configuration table;
and carrying out standard structuralization processing on the service data according to the data conversion configuration table to obtain service data with a standard structure.
In one embodiment, the generating call chain configuration data according to the data required by the call chain includes:
acquiring service timeliness corresponding to the service data;
if the service timeliness is low, generating asynchronous calling chain configuration data according to the data required by the calling chain;
and if the service timeliness is high, generating synchronous call chain configuration data according to the data required by the call chain.
In one embodiment, the node for the abort link waits for the asynchronous task to pull up the abort link again, and for the nodes which process normal and fail to process, saving the generated data to the result data pool includes:
if the next node is normally and continuously executed aiming at the non-tail node in the call chain, storing the data generated by the current node into a result data pool, and entering the next node processing step; if the exit fails, storing the data generated by the current node into a result data pool; and if the link is abnormally interrupted, waiting for the asynchronous task to pull up the abnormally interrupted link again.
In one embodiment, the node for the abort link waits for the asynchronous task to pull up the abort link again, and for the nodes which process normal and fail to process, saving the generated data to the result data pool includes:
for the tail node in the call chain, identifying a return mode when the call chain is normally exited or unsuccessfully exited, wherein the return mode comprises synchronous return or asynchronous return;
if the result is synchronous return, directly entering the step of obtaining the service object result template;
and if the result is asynchronous return, waiting for the result notification of the associated system or the notification of the asynchronous task to be pulled up so as to enter the step of acquiring the result template of the business object.
In one embodiment, the service processing method further includes:
and when the service data is received, executing an instantiation node task, and instantiating a node in the service flow corresponding to the service data in a Spring bean form.
A traffic processing apparatus, the apparatus comprising:
the configuration data acquisition module is used for receiving the service data and acquiring the call chain configuration data corresponding to the service data;
a calling chain generating module, configured to generate a calling chain for a node instantiated in a service flow corresponding to the service data according to the calling chain configuration data;
the execution module is used for sequentially executing each node in the call chain;
the processing module is used for waiting for the asynchronous task to pull up the abnormal interrupt link again aiming at the node of the abnormal interrupt link, and storing the generated data to a result data pool aiming at the node which is processed normally and processed unsuccessfully;
and the feedback module is used for acquiring a business object result template, filling the data in the result data pool into the business object result template to obtain a business processing result, and feeding the business processing result back to the business object.
A computer device comprising a memory storing a computer program and a processor implementing the steps of the method as described above when executing the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method as described above.
The service processing method, the service processing device, the computer equipment and the storage medium acquire the call chain configuration data corresponding to the service data, generate a call chain aiming at an instantiation node in a service flow based on the call chain configuration data, the method comprises the steps of flexibly constructing a call chain aiming at service data, avoiding processing node repetition and wasting meaningless service processing resources, sequentially executing each node in the call chain, waiting for an asynchronous task to pull up an abnormal interrupt link aiming at the node of the abnormal interrupt link, storing generated data to a result data pool aiming at the nodes which are processed normally and processed unsuccessfully, obtaining a service object result template, filling data in the result data pool to the service object result template to obtain a service processing result, and feeding back the service processing result to a service object, thereby realizing flexible and efficient processing of the service data.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The service processing method provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The terminal 102 uploads the service data to the server 104, and the server 104 receives the service data and acquires call chain configuration data corresponding to the service data; generating a call chain for nodes instantiated in a business process corresponding to business data according to call chain configuration data; sequentially executing each node in the call chain; aiming at the nodes of the abnormal interrupt link, waiting for the asynchronous task to pull up the abnormal interrupt link again, and aiming at the nodes which are processed normally and failed in processing, storing the generated data into a result data pool; and acquiring a service object result template, filling data in the result data pool into the service object result template to obtain a service processing result, and feeding back the service processing result to the terminal 102. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In an embodiment, as shown in fig. 2, a service processing method is provided, which is described by taking the application of the method to the server in fig. 1 as an example, and includes the following steps:
s100: and receiving the service data and acquiring the call chain configuration data corresponding to the service data.
The service data is uploaded to the server by the terminal, and the service data specifically comprises application type service data, processing type service data, access type service data and the like. For example, when an application scenario is applied for a merchant credit granting, the merchant operates the merchant terminal and sends a merchant credit granting application to the server, the merchant credit granting application is service data, and the server executes subsequent service processing operation for the merchant credit granting application. The call chain configuration data corresponding to the service data may be obtained from a preset call chain configuration database, or may be generated in real time according to the received service data. Specifically, the obtaining from the preset call chain configuration database specifically includes extracting feature information including a service object identifier (merchant number), a channel identifier (channel code), a service type (service scene code), an entry identifier, and the like from service data, storing the feature information and corresponding call chain configuration data in the preset call chain configuration database, extracting feature information corresponding to current service data when the service data is received, and searching the corresponding call chain configuration data in the preset call chain configuration database through the extracted feature information.
S200: and generating a call chain for the instantiated nodes in the business process corresponding to the business data according to the call chain configuration data.
And after receiving the service data, the server executes a node instantiation task to obtain instantiated nodes, and generates a call chain for the instantiated nodes in the service flow corresponding to the service data according to the call chain configuration data.
S300: each node in the call chain is executed in turn.
The call chain comprises a plurality of nodes, the nodes can be mainly divided into non-end nodes and end nodes, when the end nodes are executed, the completion of the successful execution of the whole call chain is indicated, and the execution result can be fed back. Nodes above the tail node are all non-tail nodes, and in the execution process of the call chain, situations of execution failure or abnormal interruption may occur in a certain non-tail node, and the server needs to further process the situations.
S400: and aiming at the nodes of the abnormal interruption link, waiting for the asynchronous task to pull up the abnormal interruption link again, and aiming at the nodes which are processed normally and failed in processing, storing the generated data into a result data pool.
When a calling chain is executed to a certain node (for example, an X node), if an abnormal interrupt condition occurs, the X node is a node of an abnormal interrupt link, and for such a node, it is necessary to wait for an asynchronous task to pull up the abnormal interrupt link again, that is, it is necessary for a system or a related system to pull up the interrupt link again to continue execution. The abnormally interrupted node may be caused by a running exception, which includes an exception in the internal processing hardware of the server and an exception in the running environment outside the server, such as a common power failure, a network failure, and the like. For nodes which are processed normally and failed in processing, data grown by the nodes need to be stored in a result data pool, the result data pool can be understood as a database similar to a node operation log, operation conditions of the nodes and correspondingly generated data are recorded in the result data pool, and then the data can be directly extracted from the result data pool to generate a processing result which is fed back to a business object.
S500: and acquiring a service object result template, filling data in the result data pool into the service object result template to obtain a service processing result, and feeding back the service processing result to the service object.
The business object result template can be obtained from a preset result template database, the result template is associated with the business object, data generated by execution of one node in the whole call chain is collected in a result data pool, the data in the result data pool is filled to the corresponding position in the business object result template to obtain a business processing result, and the business processing result is fed back to the business object to complete the whole business processing flow. Specifically, some specific data that needs to be written into the object result template is recorded in the result data pool, for example, a client number is generated at a registration node of a certain service, such data needs to be filled into the service object result template, and specifically, which data needs to be written, based on a setting or historical experience manner, a corresponding filling tag is added to the data generated by the node processing, where the filling tag is used to represent that the part of data needs to be filled into the service object result template, and further, tags corresponding to different positions filled into the service object result template may be different, so as to implement efficient and accurate data filling.
The service processing method includes the steps of obtaining call chain configuration data corresponding to service data, generating a call chain aiming at instantiated nodes in a service flow based on the call chain configuration data, flexibly constructing the call chain aiming at the service data, avoiding processing node repetition and wasting meaningless service processing resources, sequentially executing each node in the call chain, waiting for an asynchronous task to pull up an abnormal interrupt link aiming at the node of the abnormal interrupt link, storing the generated data into a result data pool aiming at the node which is processed normally and processed unsuccessfully, obtaining a service object result template, filling the data in the result data pool into the service object result template to obtain a service processing result, and feeding back the service processing result to a service object, so that flexible and efficient processing of the service data is achieved.
As shown in fig. 3, in one embodiment, step S100 includes:
s120: and receiving service data.
S140: and carrying out standard structuralization processing on the service data to obtain the service data with the standard structure.
S160: and preprocessing the service data with the standard structure to generate data required by a call chain.
S180: and generating calling chain configuration data according to the data required by the calling chain.
In this embodiment, call chain configuration data is generated in an instant generation manner for newly received service data. And performing standard structuralization processing on the received service data to obtain service data with a standard structure, preprocessing the service data with the standard structure to generate data required by a call chain, and generating call chain configuration data according to the data required by the call chain. Specifically, the standard structuring process may be to obtain a preset data conversion configuration table; and performing standard structuring processing on the service data according to the data conversion configuration table to obtain the service data with a standard structure. The purpose of the preprocessing is to generate data required by the call chain, and the data required by the call chain specifically comprises basic data required by a product corresponding to business processing, internally circulated user data and database persistent object data.
In one embodiment, generating the call chain configuration data according to the data required by the call chain includes: acquiring service timeliness corresponding to the service data; if the service timeliness is low, generating asynchronous calling chain configuration data according to the data required by the calling chain; and if the service timeliness is high, generating synchronous call chain configuration data according to the data required by the call chain.
Aiming at low-timeliness business, the time consumption is long, multiple-aspect data feedback aggregation is often needed, in order to ensure that the business process can continue to be normally carried out, asynchronous calling is arranged to be carried out, and asynchronous calling chain configuration data are generated. Aiming at the services with high timeliness, the time consumption is short, the required data can be collected in a short time in the service processing process and can be synchronously processed, so that the service flow is ensured to be processed as soon as possible, and the synchronous call chain configuration data is generated. In practical application, in an application scenario of credit granting by a merchant, the time consumption of a credit granting process is long, the time-efficiency level requirement is low, asynchronous execution can be realized, and asynchronous call chain configuration data are generated; the registration process has high timeliness and is synchronously executed
In one embodiment, for a node of an abort link, waiting for an asynchronous task to pull up the abort link again, and for a node which processes normal and fails, saving generated data to a result data pool includes:
for a non-tail node in the call chain, if the next node is normally executed continuously, storing data generated by the current node into a result data pool, and entering the next node processing step; if the exit fails, storing the data generated by the current node into a result data pool; and if the link is abnormally interrupted, waiting for the asynchronous task to pull up the abnormally interrupted link again.
In short, two types of nodes are included in the nodes of the whole call chain, wherein one type of node is a tail node; the other is a node other than the end node, i.e., a non-end node. And aiming at a non-tail node in the call chain, if the current node can be normally executed, entering next node processing according to the flow of the call chain, storing data generated by the current node into a result data pool, if the current node fails to execute and exits, storing the data generated by the current node into the result data pool, if the current node is abnormally interrupted in the corresponding operation, judging that the current call chain is an abnormally interrupted link, and waiting for the asynchronous task to pull up the abnormally interrupted link again.
In one embodiment, for a node of an abort link, waiting for an asynchronous task to pull up the abort link again, and for a node which processes normal and fails, saving generated data to a result data pool includes:
for a tail node in the call chain, identifying a return mode when the call chain is normally exited or failed to be exited, wherein the return mode comprises synchronous return or asynchronous return; if the result is synchronous return, directly entering the step of obtaining a business object result template; and if the result is asynchronous return, waiting for the result notification of the associated system or the notification of the asynchronous task to be pulled up so as to enter the step of obtaining the result template of the business object.
For the tail node in the call chain, adopting different modes to enter the step of obtaining the business object result template aiming at the asynchronous return and synchronous return conditions, and if the synchronous return indicates that the next processing stage needs to be immediately added, directly entering the step of obtaining the business object result template; if the task is asynchronous return, the step of waiting for the other associated tasks, the notification of the associated system or the pulling-up of the notification of the asynchronous task is described, and the step of obtaining the business object result template is entered.
In one embodiment, the service processing method further includes:
and when the service data is received, executing an instantiation node task, and instantiating the node in the service flow corresponding to the service data in a Spring bean form.
The nodes in the service flow corresponding to the service data can be instantiated efficiently and conveniently by adopting the Spring bean form.
To explain the technical solution of the service processing method of the present application in further detail, the following takes an FCP (Financial collaboration Platform) application access system to give credit to a merchant for service processing as a specific example, and with reference to fig. 4, the whole process is described in detail, which specifically includes the following steps:
1. the merchant transmits data to the server;
2. and the server converts the merchant data into data in a standard format according to a data conversion configuration table mode.
3. Preprocessing data in a standard format to generate data required by a call chain including basic data, internally circulated user data, database persistent objects and the like;
4. the server needs synchronous execution or asynchronous execution according to the service timeliness, and if synchronous execution is needed, synchronous call chain configuration data are generated; if asynchronous execution is carried out, generating asynchronous execution call chain configuration data;
5. the server reads the call chain configuration data generated in the step 4, executes the call chain configuration operation and generates a call chain;
6. sequentially executing each node in the call;
7. the non-end node comprises three returns, normal processing continues to the next node, failure exits from the execution link, and abnormal processing interrupts the link to wait for the asynchronous task to pull up the link again. And the nodes with normal processing and failed processing place the generated data into the data pool. The tail node comprises three returns, and if the link is abnormally exited in normal processing and failure execution, the link is interrupted to wait for the asynchronous task to pull up the link again. And the normal exit call link or the failure exit call link comprises a synchronous return mode and an asynchronous return mode. And directly obtaining the result template of the merchant in a synchronous return mode, and returning the result template to the merchant after filling data according to the result template of the merchant. And in the asynchronous return mode, the result notice of the associated system or the notice of the asynchronous task is pulled up, and the result template of the merchant is filled with data and then returned to the merchant.
It should be understood that although the various steps in the flow charts of fig. 2-3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
As shown in fig. 5, a service processing apparatus includes:
a configuration data obtaining module 100, configured to receive the service data and obtain call chain configuration data corresponding to the service data;
a call chain generation module 200, configured to generate a call chain for an instantiated node in a service flow corresponding to the service data according to call chain configuration data;
an execution module 300, configured to sequentially execute each node in the call chain;
a processing module 400, configured to wait for the asynchronous task to pull up the abort link again for the node of the abort link, and store the generated data to the result data pool for the node that is processing normal and processing failed;
the feedback module 500 is configured to obtain a service object result template, fill data in the result data pool into the service object result template to obtain a service processing result, and feed back the service processing result to the service object.
The service processing device acquires call chain configuration data corresponding to service data, generates call chains aiming at instantiated nodes in a service flow based on the call chain configuration data, flexibly constructs the call chains aiming at the service data, avoids processing node repetition and waste of meaningless service processing resources, sequentially executes each node in the call chains, waits for an asynchronous task to pull up an abnormally interrupted link aiming at a node of the abnormally interrupted link, stores the generated data into a result data pool aiming at nodes which are processed normally and processed unsuccessfully, acquires a service object result template, fills the data in the result data pool into the service object result template to obtain a service processing result, and feeds back the service processing result to a service object, so that flexible and efficient processing of the service data is realized.
In one embodiment, the configuration data obtaining module 100 is further configured to receive service data; performing standard structuralization processing on the service data to obtain service data with a standard structure; preprocessing the service data of the standard structure to generate data required by a call chain; and generating calling chain configuration data according to the data required by the calling chain.
In one embodiment, the configuration data obtaining module 100 is further configured to obtain a preset data conversion configuration table; and performing standard structuring processing on the service data according to the data conversion configuration table to obtain the service data with a standard structure.
In one embodiment, the configuration data obtaining module 100 is further configured to obtain a service aging corresponding to the service data; if the service timeliness is low, generating asynchronous calling chain configuration data according to the data required by the calling chain; and if the service timeliness is high, generating synchronous call chain configuration data according to the data required by the call chain.
In one embodiment, the processing module 400 is configured to, for a non-end node in the call chain, if the next node is normally executed continuously, store data generated by the current node in the result data pool, and perform the next node processing step; if the exit fails, storing the data generated by the current node into a result data pool; and if the link is abnormally interrupted, waiting for the asynchronous task to pull up the abnormally interrupted link again.
In one embodiment, the processing module 400 is configured to identify, for a last node in the call chain, a return mode when the call chain is normally exited or failed to be exited, where the return mode includes a synchronous return or an asynchronous return; if the result is synchronous return, directly entering the operation of obtaining a business object result template; and if the result is asynchronous return, waiting for the result notification of the associated system or the notification of the asynchronous task to be pulled up so as to enter the operation of obtaining the result template of the business object.
In one embodiment, the service processing apparatus further includes an instantiation module, configured to execute an instantiation node task when receiving service data, and instantiate a node in a service flow corresponding to the service data in a Spring bean form.
For the specific definition of the service processing device, reference may be made to the above definition of the service processing method, which is not described herein again. The modules in the service processing device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 6. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile 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 an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing preset database data or historical record data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business process method.
Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
receiving service data, and acquiring call chain configuration data corresponding to the service data;
generating a call chain for nodes instantiated in a business process corresponding to business data according to call chain configuration data;
sequentially executing each node in the call chain;
aiming at the nodes of the abnormal interrupt link, waiting for the asynchronous task to pull up the abnormal interrupt link again, and aiming at the nodes which are processed normally and failed in processing, storing the generated data into a result data pool;
and acquiring a service object result template, filling data in the result data pool into the service object result template to obtain a service processing result, and feeding back the service processing result to the service object.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
receiving service data; carrying out standard structuralization processing on the service data to obtain service data with a standard structure; preprocessing the service data with the standard structure to generate data required by a call chain; and generating calling chain configuration data according to the data required by the calling chain.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring a preset data conversion configuration table; and performing standard structuring processing on the service data according to the data conversion configuration table to obtain the service data with a standard structure.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring service timeliness corresponding to the service data; if the service timeliness is low, generating asynchronous calling chain configuration data according to the data required by the calling chain; and if the service timeliness is high, generating synchronous call chain configuration data according to the data required by the call chain.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
for a non-tail node in the call chain, if the next node is normally executed continuously, storing data generated by the current node into a result data pool, and entering the next node processing step; if the exit fails, storing the data generated by the current node into a result data pool; and if the link is abnormally interrupted, waiting for the asynchronous task to pull up the abnormally interrupted link again.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
for a tail node in the call chain, identifying a return mode when the call chain is normally exited or failed to be exited, wherein the return mode comprises synchronous return or asynchronous return; if the result is synchronous return, directly entering the step of obtaining a business object result template; and if the result is asynchronous return, waiting for the result notification of the associated system or the notification of the asynchronous task to be pulled up so as to enter the step of obtaining the result template of the business object.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
and when the service data is received, executing an instantiation node task, and instantiating the node in the service flow corresponding to the service data in a Spring bean form.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
receiving service data, and acquiring call chain configuration data corresponding to the service data;
generating a call chain for nodes instantiated in a business process corresponding to business data according to call chain configuration data;
sequentially executing each node in the call chain;
aiming at the nodes of the abnormal interrupt link, waiting for the asynchronous task to pull up the abnormal interrupt link again, and aiming at the nodes which are processed normally and failed in processing, storing the generated data into a result data pool;
and acquiring a service object result template, filling data in the result data pool into the service object result template to obtain a service processing result, and feeding back the service processing result to the service object.
In one embodiment, the computer program when executed by the processor further performs the steps of:
receiving service data; carrying out standard structuralization processing on the service data to obtain service data with a standard structure; preprocessing the service data of the standard structure to generate data required by a call chain; and generating calling chain configuration data according to the data required by the calling chain.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring a preset data conversion configuration table; and performing standard structuring processing on the service data according to the data conversion configuration table to obtain the service data with a standard structure.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring service timeliness corresponding to the service data; if the service timeliness is low, generating asynchronous calling chain configuration data according to the data required by the calling chain; and if the service timeliness is high, generating synchronous call chain configuration data according to the data required by the call chain.
In one embodiment, the computer program when executed by the processor further performs the steps of:
for a non-tail node in the call chain, if the next node is normally executed continuously, storing data generated by the current node into a result data pool, and entering the next node processing step; if the exit fails, storing the data generated by the current node into a result data pool; and if the link is abnormally interrupted, waiting for the asynchronous task to pull up the abnormally interrupted link again.
In one embodiment, the computer program when executed by the processor further performs the steps of:
for a tail node in the call chain, identifying a return mode when the call chain is normally exited or failed to be exited, wherein the return mode comprises synchronous return or asynchronous return; if the result is synchronous return, directly entering the step of obtaining a business object result template; and if the result is asynchronous return, waiting for the result notification of the associated system or the notification of the asynchronous task to be pulled up so as to enter the step of obtaining the result template of the business object.
In one embodiment, the computer program when executed by the processor further performs the steps of:
and when the service data is received, executing an instantiation node task, and instantiating the node in the service flow corresponding to the service data in a Spring bean form.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.