Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 4 is a flowchart of a method according to an embodiment of a method for processing service data according to the present application. Although the present application provides the method operation steps or apparatus structures as shown in the following embodiments or figures, more or less operation steps or module units after partial combination may be included in the method or apparatus based on conventional or non-inventive labor. In the case of steps or structures which do not logically have the necessary cause and effect relationship, the execution sequence of the steps or the module structure of the apparatus is not limited to the execution sequence or the module structure shown in the embodiment or the drawings of the present application. When the described method or module structure is applied to a practical device or an end product, the method or module structure according to the embodiment or the figures may be executed sequentially or executed in parallel (for example, in the environment of parallel processors or multi-thread processing, or even in the environment of distributed processing).
For clarity, the following description will use service data processing of the system when an external job call is used in a specific system modification process as an application scenario. However, those skilled in the art will appreciate that the substantial spirit of the present solution can be applied to other scenarios where external applications invoke system internal data for consumption when the system internal logic or storage method is modified. In other words, in the process of logic and storage transformation of the system based on the distributed transaction, the data double writing is realized by designing the internal two-stage transaction engine, so that the high availability of the service data is ensured, the third-party system services such as report forms of consumption data, file generation and the like are continuously available, the reliability of the service system is improved, and the transformation risk, difficulty and implementation cost are reduced.
Specifically, as shown in fig. 4, in an embodiment of a method for processing service data provided by the present application, the method may include:
s1: and sending a resource preparation request to the old service logic and the set new service logic based on the received service processing request, so that the old service logic and the new service logic prepare the processing resource corresponding to the resource preparation request.
In the application scenario of this embodiment, the service system under modification and upgrade can still normally receive the service processing request for external other data consumption. If the report application can use the business system to generate the report operation, the business system receives the processing request of the operation business, and then the business system can submit the operation after internal processing, and the report formed after completion is returned to the report application outside the business system.
In the embodiment of the application, when the service system is upgraded and modified, the old service logic processed by the service system or the old database storing the old data format can be kept and continuously used. The upgrading and modifying of the service system may include modifying service data processing logic inside the service system, or modifying and migrating data storage format/mode/database type. Of course, the upgrade may also include implementation scenarios of both logic changes and data storage changes of the system. For example, in this embodiment, the old service logic for processing the service data of the original service system, the type a relational database storing the data format, is modified and changed to use the new service logic to process the service data, and the type B relational database storing the new data format is used to store the service data.
In the specific implementation process, because the service system maintains two new and old service implementation logics, after receiving a service processing request, resource preparation requests can be respectively sent to the old service logic and the new service logic used for modification and upgrade, so that participants of service processing of the old service logic and the new service logic in the service system can prepare processing resources corresponding to the services. The old service logic and the new service logic may be understood as a processing method/steps/execution actions and sequences for processing the service data element, which are designed in advance, may include a data processing and/or data storage (data reading and writing or storage mode/data format control) stage, and may be implemented by computer executable codes or other logic circuits.
The embodiment of the application utilizes a distributed transaction processing mechanism, the business implementation logic is regarded as a participant of a transaction in the business system, and a transaction engine can be set in the business system to be responsible for the management of the transaction service (equivalent to a transaction initiator in the distributed transaction mechanism). In the process of modifying the service system, for an external request, the inside of the service system can coordinate the new service and the old service through a transaction engine to realize logic execution. The described distributed transaction process generally includes the following two phases:
stage one:
1. the transaction initiator (transaction manager) sends a resource preparation request to the enrollee;
2. after receiving the resource preparation request, the participant performs preparation operation and replies whether the initiator is successful in preparation.
Correspondingly, in the application scenario of this embodiment, a transaction engine may be provided, which is responsible for transaction management such as resource allocation in the service data processing. Upon receiving a service processing request for an external job, a resource preparation request may be sent to participants (i.e., the old service logic and the new service logic described in this embodiment) to prepare processing resources for processing the service.
S2: and after receiving a first message that the processing resource preparation returned by the old service logic is successful and a second message that the processing resource preparation returned by the new service logic is successful, sending a submission request of the service to the old service logic and the new service logic.
In the embodiment of the application, service data are written in the databases before and after the modification, or the new and old two sets of services are used for realizing logic processing of the service data before and after the modification, so that the third party application such as report generation and file generation can continuously read data from the database of the service system or realize service logic in the process of upgrading and modifying the service system, and the third party application service is not influenced. In this embodiment, the old service logic and the new service logic may prepare processing resources required for processing service data, and if the processing resources are successfully prepared, a message that the processing resources are successfully prepared may be returned to the transaction engine (transaction initiator). For example, when the old service logic is successfully written into the old database in the old data format, a first message that the old service logic processing resource is successfully prepared can be returned; when the new service logic is successfully used for writing in the information database in the new data format, a second message that the new service logic processing resource is successfully prepared can be returned. The processing request to submit the job may then be sent after it is determined that the processing resources of the business of all the transaction participants (i.e., the old business logic and the new business logic in the application scenario of the present embodiment) are ready to succeed.
The above processing confirms that receiving the first message that the processing resource preparation returned by the old service logic is successful and the second message that the processing resource preparation returned by the new service logic is successful is equivalent to phase two in a distributed transaction, and the transaction initiator initiates a commit request to all participants after receiving replies that all participants are successful in preparation.
S3: and after receiving a third message that the service submission returned by the old service logic is successful and a fourth message that the service submission returned by the new service logic is successful, confirming that the service submission is successful.
After the service is submitted for processing, the new service logic and the old service logic in the service system can process the service at the same time. And generating an old service report by using the data in the old database and the old service implementation logic and generating a new service report by using the medium data of the new data and the old service implementation logic simultaneously. And after the successful message of the service submission processing based on the received new and old service logic services, confirming that the service submission processing of the current processing is successful. Of course, in some implementation scenarios, data double-writing or combining two business implementation logics may generate the results of two business submission processes, such as generating two reports.
Generally, two logic distributions inside the system, namely new logic distribution and old logic distribution, submit external jobs, and one result can be respectively corresponding to the two logic distributions. But there is usually only one output to the party consuming the service data externally. Therefore, in the present embodiment, one of the results may be processed and then output as an external output result. In this way, the outside of the system only senses whether the job processing inside the system is successful, and how to execute, whether to execute the old logic and the new logic inside the system and the like are not concerned by the externally called application. By using the embodiment of the application, the reliable use of data in the system transformation and upgrade process can be effectively guaranteed, for example, in the system A transformation process, other external applications B, C, D depending on the system A data are not affected as if A has never been changed. So that B, C, D functionality is still available during system a retrofit. This avoids B, C, D being forced to be modified at the same time by the change of A, which avoids enlarging the modification range and reducing the modification risk.
The invention is based on a distributed transaction mechanism, and the business implementation logic is taken as a transaction participant in the application, and a transaction engine is designed in the application to be responsible for transaction management (a transaction initiator). And for an external request service, the internal part of the system coordinates the new service and the old service through a transaction engine to realize logic execution. Due to the fact that the databases of the new logic operation and the old logic operation are different, double writing of data is achieved. Therefore, during the system transformation, the third-party systems such as the report forms and the file generation of the consumption business data can continuously acquire the data from the original database, and the problem of high availability of the data in the system transformation process is solved. Meanwhile, the risk of the system modification is controlled within the scope of the modified single system, and the stability of a business system and even external application depending on the system data is guaranteed.
Fig. 5 is an implementation schematic diagram of a scenario of another embodiment of a service data processing method provided by the present application. In fig. 5, although the new type B relational database is used, since business data is written in the type a database before and after transformation, third-party systems such as report generation and file generation can continuously read data from the type a relational database without being affected in the process of transformation of the business system, thereby ensuring that other data consuming applications outside the system normally use the services of the original business system.
In a specific example, the processing flow of the external request by the medium service system provided by the present application may include two stages. For example, fig. 6 is a schematic processing flow diagram of a distributed transaction phase one in an example provided in the present application, and fig. 6 is a schematic processing flow diagram of the distributed transaction phase one, where a writing sequence of the old database and the new database in fig. 6 may be changed, and in this embodiment, it may be only necessary to ensure that all the old database and the new database are successfully written. In another embodiment of the method provided by the present application, the preparing, by the old service logic and the new service logic, a processing resource corresponding to the resource preparation request may include:
s101: according to the resource preparation request, using an old service logic to write the service data of the service into an old database according to an old data format; and the number of the first and second groups,
s102: and writing the service data of the service into a new database according to a new data format by using a new service logic according to the resource preparation request.
Fig. 7 is a schematic method flow diagram of another embodiment of the method for processing service data provided in the present application, in another embodiment, if an abnormal condition occurs when the service system processes a service request, such as no response from a participant has been received or a failed response has been received, a rollback request is initiated to all participants, so that the service system returns to a state of correctly processing the service data last time. Therefore, in another embodiment of the method provided in the present application, the method may further include:
s4: when any one of the following conditions is met, sending a processing resource rollback request of the service to the old service logic and the new service logic:
receiving the first message and the second message within a predetermined response time;
receiving a reply message from at least one of the old business logic and the new business logic that the processing resource failed to prepare.
In another implementation, further, after receiving a fifth message that the processing resource rollback success returned by the old service logic and a sixth message that the processing resource rollback success returned by the new service logic are successful, the service system may confirm that the processing resource rollback success of the service is successful. In the process of logic and storage transformation of the system based on distributed transaction, data double writing is realized by designing an internal two-stage transaction engine, and high availability of service data is guaranteed.
In the embodiment, when any one of the old service logic and the new service logic used by the service system fails to process, the service system points to the resource rollback, so that the reliability of the service system is guaranteed, and the risk of the reconstruction of the service system is reduced. In addition, in an implementation manner, in the rollback processing process, it may be set that the rollback processing success of the service system is confirmed only after all the logic units are successfully rolled back. Otherwise, a warning prompt can be sent out or other preset processing measures can be executed to ensure the safety and reliability of the system.
Fig. 8 is a schematic method flow diagram of another embodiment of the service data processing method provided in the present application. As shown in fig. 8, in another embodiment of the method provided by the present application, the method may further include:
s5: starting a timing task configured to resend the service submission request to the old service logic and the new service logic after a predetermined delay time if any of the following conditions is met:
receiving the third message and the fourth message within a predetermined response time;
receiving a reply message of the service submission failure sent by at least one of the old service logic and the new service logic.
Fig. 9 is a process flow diagram of a distributed transaction phase two in one example provided herein. Fig. 10 is a schematic diagram of a rollback processing flow of a distributed transaction phase two in an application scenario of another embodiment of the method provided by the present application. The transaction engine receives feedback of two successful submitting jobs, and then the transaction engine confirms that the whole distributed transaction is successful only when both of the two successful submitting jobs are received.
If there is a failure, the transaction engine will return a commit failure, and in one embodiment may set that no rollback operation will be performed. Because this is the case for "distributed transaction phase two commit," the transaction engine may wait for the timed task inside the distributed transaction initiator to re-invoke the transaction engine to commit until successful.
In other embodiments of the method provided in the present application, after receiving the service processing request, the method further includes:
initializing the running records of the old service logic and the new service logic;
correspondingly, the sending resource preparation request comprises: and sending the resource preparation request after determining that the operation records of the old service logic and the new service logic are initialized successfully.
Because of the two-phase transaction, it can be simply understood that the processing of the two-phase transaction is completed by two independent requests. In this embodiment, the operation record is initialized, that is, what operation i do is recorded in the first request process. When the second request comes, the record stored in the first request is inquired, so that what the previous request does is known, and then the processing can be continued, and the processing efficiency is improved and guaranteed.
In other embodiments of the method provided in the present application, before sending the request for submitting the service, the method further includes:
checking the operation records of the old service logic and the new service logic;
correspondingly, the sending the submission request of the service includes: and sending the service submission request after the running records of the old service logic and the new service logic are determined to be successfully verified.
In other embodiments of the method provided in the present application, before sending the processing resource rollback request of the service, the method further includes:
checking the operation records of the old service logic and the new service logic;
correspondingly, the sending the processing resource rollback request of the service includes: and sending a resource rollback processing request after the running records of the old service logic and the new service logic are successfully verified.
The above embodiments apply the implementation shown in the scenario, by designing the transaction engine inside the system, e.g., system a, the scope of modification and risk are minimized and only addressed internally. In the worst case, if the system a is modified to be a problem, the system a can be rolled back quickly instead of rolling back a series of peripheral B, C, D systems in conjunction with the conventional scheme, which results in the unusable effect of large-area products. Meanwhile, after the system A is modified, other external applications B, C, D that depend on the data of the system A are not affected as if A has never been changed. Thereby ensuring the stability of the whole product line.
According to the business data processing method, the data double writing is realized by designing the internal two-stage transaction engine in the process of carrying out logic and storage transformation on the system based on the distributed transaction. Since the service data are written in the type databases before and after the transformation, third-party systems such as report forms, file generation and the like can continuously read data from the type relation database in the transformation process of the service system without being influenced, the high availability of the service data is ensured, the reliability of the service system is improved, and the transformation risk, the transformation difficulty and the implementation cost are reduced. Meanwhile, the risk of the system reconstruction can be controlled in the range of a single reconstructed system, and the stability of a service system and even external application depending on the system data is guaranteed.
Based on the business data processing method, the application also provides a business data processing device. Fig. 11 is a schematic block diagram of an embodiment of a service data processing apparatus provided in the present application, and as shown in fig. 11, the apparatus may include:
a resource preparation module 101, configured to send a resource preparation request to an old service logic and a set new service logic based on a received processing request of a service, so that the old service logic and the new service logic prepare processing resources corresponding to the resource preparation request;
a submission processing module 102, configured to send a submission request of the service to the old service logic and the new service logic after receiving a first message that the processing resource preparation returned by the old service logic is successful and a second message that the processing resource preparation returned by the new service logic is successful;
the result processing module 103 may be configured to, after receiving a third message that the service submission returned by the old service logic is successful and a fourth message that the service submission returned by the new service logic is successful, confirm that the service submission is successful.
According to the business data processing device, during logic and storage transformation of a system, double writing of data is achieved by designing an internal two-stage transaction engine. Since the service data are written in the type databases before and after the transformation, third-party systems such as report forms, file generation and the like can continuously read data from the type relation database in the transformation process of the service system without being influenced, the high availability of the service data is ensured, the reliability of the service system is improved, and the transformation risk, the transformation difficulty and the implementation cost are reduced. Meanwhile, the risk of the system reconstruction can be controlled in the range of a single reconstructed system, and the stability of a service system and even external application depending on the system data is guaranteed.
Fig. 12 is a schematic block diagram of a service data processing apparatus according to another embodiment of the present disclosure. As mentioned above, in another embodiment of the apparatus, the apparatus may further include:
the rollback processing module 104 may be configured to send a processing resource rollback request of the service to the old service logic and the new service logic when any one of the following conditions is satisfied:
receiving the first message and the second message within a predetermined response time;
receiving a reply message from at least one of the old business logic and the new business logic that the processing resource failed to prepare.
Fig. 13 is a schematic block diagram of a service data processing apparatus according to another embodiment of the present disclosure. As mentioned above, in another embodiment of the apparatus, the apparatus may further include:
a re-submission module 105, configured to start a timing task when any one of the following conditions is met, where the timing task is configured to re-send the service submission request to the old service logic and the new service logic after a predetermined delay time:
receiving the third message and the fourth message within a predetermined response time;
receiving a reply message of the service submission failure sent by at least one of the old service logic and the new service logic.
The specific implementation logic implementation manner of the apparatus is similar to that of the method, and reference may be made to the description related to the method, which is not repeated herein.
According to the business data processing device, data double writing is achieved by designing an internal two-stage transaction engine in the process of carrying out logic and storage transformation on a system based on distributed transactions. Since the service data are written in the type databases before and after the transformation, third-party systems such as report forms, file generation and the like can continuously read data from the type relation database in the transformation process of the service system without being influenced, the high availability of the service data is ensured, the reliability of the service system is improved, and the transformation risk, the transformation difficulty and the implementation cost are reduced. Meanwhile, the risk of the system reconstruction can be controlled in the range of a single reconstructed system, and the stability of a service system and even external application depending on the system data is guaranteed.
The method or the device can be used for various business systems in the upgrading and reconstruction process to ensure high availability of business data during modification and upgrading of internal logic or data storage structures of the business systems, so that third-party system business consuming data is continuously available, the reliability of the business systems is improved, and the risk, difficulty and implementation cost of reconstruction are reduced. Therefore, the present application further provides a service system, including: a memory, a processor, and computer instructions stored on the memory and executable on the processor,
the computer instructions when executed by a processor implement the steps of:
sending a resource preparation request to an old service logic and a set new service logic based on a received processing request of a service, so that the old service logic and the new service logic prepare processing resources corresponding to the resource preparation request;
after receiving a first message that the processing resource preparation returned by the old service logic is successful and a second message that the processing resource preparation returned by the new service logic is successful, sending submission requests of the services to the old service logic and the new service logic;
and after receiving a third message that the service submission returned by the old service logic is successful and a fourth message that the service submission returned by the new service logic is successful, confirming that the service submission is successful.
The application also provides another business system, which comprises an old business logic implementation module, an old data storage module, a new business logic implementation module, a new data storage module, a processor and a memory for storing executable instructions of the processor,
the processor is configured to, when a processing request of a received service is available, read data from an old database according to an old data format set in an old data storage module, prepare an old service logic processing resource corresponding to the service, and read data from a new database according to a new data format set in a new data storage module, prepare a new service logic processing resource corresponding to the service; the system is also used for submitting the service by using the old service logic implementation module and the new service logic implementation module after the old service logic processing resource and the new service logic processing resource are confirmed to be prepared successfully; and the service logic implementation module is also used for confirming that the service is successfully submitted after the service is successfully submitted in the old service logic implementation module and the new service logic implementation module.
FIG. 14 is a block diagram illustrating an architecture of an embodiment of a business system provided by the present application.
The application aims to provide a method, a device and a system for processing business data, which can ensure high availability of the business data of a business system in the process of modifying the business system, so that third-party system services such as reports and file generation of consumption data can be continuously available, the reliability of the business system is improved, and the modification risk, difficulty and implementation cost are reduced.
Although the description of designing the implementation logic of the new and old services, confirming the message based on the response, verifying and initializing the logic operation record, defining different things participants such as double writing of the new and old databases, implementing the service processing logic, exchanging information, calculating, judging and the like is mentioned in the content of the application, the application is not limited to the case of conforming to the industry communication standard, the standard data/function structure, the standard design language processing method or the embodiment of the application. Certain industry standards, or implementations modified slightly from those described using custom modes or examples, may also achieve the same, equivalent, or similar, or other, contemplated implementations of the above-described examples. The embodiments obtained by applying the modified or transformed data definition, storage, judgment, setting mode, etc. may still fall within the scope of the alternative embodiments of the present application.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Although the present application provides method steps as described in an embodiment or flowchart, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, in implementing the present application, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of a plurality of sub-modules or sub-units, and the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may therefore be considered as a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.