Detailed Description
The embodiment of the application provides a method, a device, a server and a system for processing a bill service.
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.
The following describes specific implementations of embodiments of the present application in detail with reference to several specific examples.
The following first introduces an embodiment of a method for processing a billing service according to the present application. Fig. 1 is a flow diagram of an embodiment of a method for processing billing services provided herein, which provides the method steps as described in the embodiment or flow diagram, but may include more or less steps based on conventional or non-inventive labor. 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. In actual implementation, the system or client product may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures. Specifically, as shown in fig. 1, the method may include:
s110: and the third-party platform stores the bill data which is obtained from the business service platform in advance into a preset bill database.
In practical application, when a user needs to pay a certain bill through a third-party platform, the third-party platform usually obtains corresponding bill data from the service platform after the user triggers the inquiry of the bill, and if the service platform is in a non-service state (i.e. a state that the service platform is unavailable) due to reasons such as insufficient concurrency capability of a system of the service platform, the third-party platform cannot inquire the bill data of the user, and the user cannot directly complete the payment. In the embodiment of the application, the third-party platform can store the bill data acquired from the business service platform to the preset bill database, so that the bill data can be directly acquired locally once the user needs to perform bill business processing on the third-party platform, and the success rate of bill business processing is greatly increased.
Specifically, in this embodiment of the present application, the third party platform may include a processing platform corresponding to any mechanism that can provide processing such as inquiry and payment of a bill service. The service platform may include a processing platform corresponding to any mechanism that can provide a certain service for a user.
FIG. 2 is a schematic flow chart illustrating an embodiment of storing billing data previously obtained from a business service platform into a preset billing database according to the present application; specifically, as shown in fig. 2, the method may include:
s111: and determining the charge-out rule information of the business service platform corresponding to the bill data of the user according to the historical bill data.
In practical application, a third-party platform accumulates a large amount of bill data through long-time bill business processing, and meanwhile, the charge-out time of some service organizations per se has certain rules, such as being concentrated in days every month; and the charge-out time of a specific user has certain regularity. Therefore, the third-party platform can be combined with a clustering analysis processing method to mine the charge-off rule information of a large amount of accumulated bill data, and determine the charge-off rule information of each user for a certain type of bills.
Specifically, the billing data may include user account information (e.g., a payment account number), a billing type (e.g., the billing type is a water bill), a service organization (e.g., suzhou water limited), a billing amount (e.g., a payment amount), a billing date (e.g., the billing is 2017 for 3 months), and the like. In this embodiment, the historical billing data may include billing data processed by the third party platform. The historical billing data may be stored in a corresponding database or other memory. Specifically, the charge-out rule information may include charge-out time information identified by the user account information and the service organization.
S112: and acquiring bill data from a corresponding business service platform based on the charge-out rule information.
Specifically, the acquiring of the bill data from the corresponding service platform based on the charge-out rule information may include determining a time period for acquiring the bill data from the service platform according to the charge-out rule information, and then acquiring the bill data from the service platform in the determined time period.
In a specific embodiment, assuming that the charge-out rule information of a certain user includes that the water charge-out time of the user is No. 2 or No. 3, which is generally monthly, No. 4 per month can be selected to obtain the water charge bill data of the user from the business service platform.
S113: and storing the bill data into a preset bill database.
Specifically, after acquiring the billing data, the third party platform may store the acquired billing data in a preset billing database. Specifically, the preset bill database may include a pre-established database for storing bill data, and the bill database may be a local database of the third party platform.
In practical applications, when a large number of requests of the service platform need to be responded at a certain time, the service platform may be in a non-service state due to insufficient concurrency capability of its own system, and to avoid this, the third party platform may select to query the bill data at idle time (that is, when the current concurrency capability of the service platform is strong), and accordingly, in some embodiments, before acquiring the bill data from the corresponding service platform based on the information of the billing rule in step S112, the method may further include:
s114: and acquiring the upper limit value of the concurrency number of the service platform.
In practical application, pressure test can be performed on each service platform in advance to obtain the upper limit of the concurrency capability (i.e. the upper limit of the number of concurrencies) of the service platform.
S115: and acquiring the current concurrency number of the service platform.
In the embodiment of the application, when a third-party platform needs to acquire bill data from a certain service platform, the current concurrency number of the service platform can be acquired by inquiring the current access data of the service platform.
S116: and judging whether the sum of the concurrency number corresponding to the acquired bill data and the current concurrency number is less than or equal to the upper limit value of the concurrency number.
Specifically, after the upper limit value of the concurrency number and the current concurrency number of the service platform are obtained, whether the current concurrency capability of the service platform can meet the concurrency capability required by a third-party platform for inquiring the bill data can be judged by judging whether the sum of the obtained concurrency number corresponding to the bill data and the current concurrency number is less than or equal to the upper limit value of the concurrency number.
Specifically, when the judgment result is yes, the current concurrency capability of the service platform can meet the concurrency capability required by the third-party platform for inquiring bill data; correspondingly, the step S112 of acquiring the bill data from the corresponding business service platform based on the charge-out rule information may be executed; otherwise, when the judgment result is negative, the current concurrency capability of the service platform cannot meet the concurrency capability required by the third-party platform for inquiring the bill data; step S115 may be executed at preset intervals until the current concurrency number of the service platform is obtained, and if the result of the determination in step S116 is yes, it is determined that the sum of the concurrency number corresponding to the obtained bill data and the current concurrency number is less than or equal to the upper limit value of the concurrency number.
In some embodiments, after obtaining billing data, the method may further comprise:
and storing the bill data as historical bill data.
Specifically, the bill data is stored as historical bill data, so that a data base in the process of mining the information of the charge-out rule can be increased. The information of the expenditure presentation rule can be better determined.
S120: and responding to a bill inquiry instruction of a user, and inquiring whether bill data corresponding to the bill inquiry instruction exists in the bill database by the third-party platform.
In the embodiment of the application, in response to a bill query instruction of a user, the third-party platform may directly query whether bill data corresponding to the bill query instruction exists in the bill database.
Specifically, the bill inquiry command may include that the user triggers by clicking a preset bill inquiry button, and the bill inquiry command may include data that may reflect specific information of bill data, such as user account information, bill type, service organization, and bill date. Correspondingly, the bill data can be inquired by combining the user account information, the bill type, the service mechanism, the bill date and the like, which can reflect the specific information of the bill data.
Specifically, when the query result is yes, that is, the corresponding billing data is obtained from the local billing database of the third party platform, step S130 may be executed; conversely, in some cases, the result of the query may be negative, that is, the corresponding bill data is not obtained in the bill database local to the third-party platform, and the obtained bill data may be queried from the service platform.
S130: and when the inquiry result is yes, the third-party platform creates a bill according to the bill data.
Specifically, after the corresponding bill data is obtained in the local bill database, the third party platform may create a bill according to the bill data, and specifically, creating the bill according to the bill data may include displaying a preset bill form of the bill data according to the bill data, so that the user can pay based on the bill.
In practical applications, the bill data obtained by the third party platform from the service platform has a certain validity period, and thus, there may be a case where the bill data is out of date, for example, the water fee in 2017, month 2 of the user a is 50 yuan, the billing date is 2017, month 3, day 3, the third party platform has stored the water fee bill data in the bill database in 2017, month 3 and day 4, and if the validity period of the water fee bill is one month from the billing date, a late fee is generated after one month of the out date (the late fee is 1 yuan every month after the late fee is exceeded, and the late fee is calculated by one month after the late fee is exceeded), correspondingly, if the user triggers the bill query command in 4 and 10 months in 2017, the water fee amount is 50 yuan inaccurate, and accordingly, the bill created based on the bill data is in error, so as to avoid the above-mentioned case where the error of the bill data is caused by out of date, in some embodiments. Before creating a bill from the bill data at step S130, the method may include:
and judging whether the bill data is within a preset validity period or not.
Specifically, when the determination result is yes, that is, when the billing data is determined to be within the preset validity period, the step S130 of creating a bill according to the billing data may be executed; otherwise, if the result of the judgment is negative, that is, the bill data is judged not to be within the preset validity period, and correspondingly, the latest bill data can be obtained again from the service platform.
Specifically, the preset validity period may be set in combination with the validity period of the bill in actual application.
In another embodiment, in order to avoid the above situation that the bill acquired by the user is incorrect due to the out-of-date bill data, the method may further include:
setting the validity time limit of the bill data in the bill database;
and when the bill data reaches the validity time limit, deleting the bill data reaching the validity time limit from the bill database.
Specifically, the validity period may be set in combination with the validity period of the bill in actual application.
S140: and the third-party platform responds to a payment instruction of the user based on the bill, and sends an account cancellation request of the user to the business service platform in a service state before the business cut point of the business service platform corresponding to the bill data.
In this embodiment of the application, after the user triggers a corresponding payment instruction based on the created bill, the third party platform may respond to the payment instruction based on the bill, and may send an account cancellation request of the user to the service platform in a service state (i.e., a state in which the service platform is available) before the service cut point of the service platform corresponding to the bill data.
Specifically, the payment instruction may include that the user triggers by clicking a preset bill payment button and the like, and the cancellation request may include data that may reflect specific information of bill data that needs to be cancelled, such as user account information, a bill type, a service organization, a bill date, a bill amount, and the like.
In practical applications, the business cut point may be a daily cut point, that is, a business service platform uses a day as a business processing period, for example, a business service platform is a business period from 10:00 am to 10:00 am every second day, and then 10:00 am is the daily cut point of the organization. In addition, it should be noted that the service tangent point may also be set as a circle tangent point or other points in combination with the actual application situation, and the embodiment of the present application is not limited to the above.
Fig. 3 is a schematic flow chart of an embodiment of sending an account cancellation request of the user to a business service platform in a service state before a business cut point of the business service platform corresponding to the billing data according to the present application, and specifically, as shown in fig. 3, the flow chart may include:
s310: and judging whether the current time reaches the service tangent point of the service platform corresponding to the bill data.
In practical application, once a business cut point of a business service platform is reached, the account checking processing of the account cancellation information in a period (in a time period) corresponding to the business cut point is directly performed between the business service platform and a third-party platform. Therefore, it is necessary to first determine whether the current time reaches the service tangent point of the service platform corresponding to the billing data. If the result of the determination is negative, that is, the current time does not reach the service tangent point of the service platform corresponding to the billing data, step S320 may be executed; otherwise, when the judgment result is yes, that is, the current time reaches the service tangent point of the service platform corresponding to the bill data, step S150 may be directly executed.
S320: and when the judgment result is negative, inquiring whether the service platform is in a service state currently.
Specifically, when the result of the determination in step S310 is negative, it is required to query whether the service platform is currently in a service state. When the query result is yes, that is, the service platform is currently in the service state, step S330 may be executed; otherwise, when the query result is negative, that is, the service platform is currently in the non-service state, step S310 may be executed before the service cut point until the service platform is currently in the service state, that is, before the service cut point is reached, the step of querying whether the service platform is currently in the service state is executed until the query result is positive.
S330: and when the query result is that the service platform is in the service state currently, sending an account cancellation request of the user to the service platform.
Therefore, when the business service platform is in the non-service state, the service state query of the business service platform can be continuously initiated to attempt to sell accounts, once the business service platform is in the service state, an account selling request can be immediately sent to complete the account selling, and even if the business service platform is in the non-service state and cannot complete the account selling before the business is cut off, the bill can be guaranteed to be completed through subsequent account checking.
S150: and after the business tangent point of the business service platform is reached, the third-party platform and the business service platform carry out account checking processing on the account cancellation information in the time period corresponding to the business tangent point.
In practical application, the reconciliation processing of the account cancellation information in each period of the business service platform is performed between the business service platform and the third party platform after the business cut point of the business service platform in the period, so as to ensure the accuracy of the bill business processed in the period.
Specifically, the cancellation information may include a cancellation request and processing result information of the cancellation request.
Therefore, the embodiment of the bill service processing method can ensure that the related bill data can be directly obtained from the bill database when the bill service of the user to the service platform is subsequently processed by storing the bill data obtained from the service platform into the preset bill database, can avoid the problem that the bill data of the user cannot be obtained due to the non-service state of the service platform, greatly increases the success rate of bill service processing, and meanwhile, after the user finishes the bill payment on the third-party platform, for the condition that the service platform is in the non-service state, the service state can be continuously inquired to the service platform to try to sell the bill, once the service platform is inquired to be in the service state, the bill selling request can be immediately sent to finish the bill selling, and even if the business service platform is in a non-service state before the business is cut off and cannot complete the account cancellation, the bill can be guaranteed to be completed through subsequent account checking. Compared with the prior art, the technical scheme provided by the application can solve the problem that the third-party platform is limited by the service platform when processing the bill service, improves the stability of the third-party platform when processing the bill service, meets the payment requirement of a user, and improves the user experience.
Considering a third party platform as an executing subject, another embodiment of the method for processing a billing service according to the present application is described below. Fig. 4 is a flow diagram of an embodiment of a method for processing billing services provided herein, which provides the method steps as described in the embodiments or flow diagrams, but may include more or less steps based on conventional or non-inventive labor. 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. In actual implementation, the system or client product may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures. Specifically, as shown in fig. 4, the method may include:
s410: and storing the bill data acquired from the business service platform in advance into a preset bill database.
Specifically, the storing the bill data acquired from the business service platform in advance into the preset bill database may include:
determining the charge-out rule information of the business service platform corresponding to the bill data of the user according to the historical bill data;
acquiring bill data from a corresponding business service platform based on the charge-out rule information;
and storing the bill data into a preset bill database.
In some embodiments, before obtaining billing data from a corresponding business service platform based on the charge-out rule information, the method may further include:
acquiring a concurrency number upper limit value of a service platform;
acquiring the current concurrency number of a service platform;
judging whether the sum of the concurrency number corresponding to the acquired bill data and the current concurrency number is less than or equal to the upper limit value of the concurrency number or not;
and when the result of the judgment is yes, executing the step of acquiring bill data from the corresponding business service platform based on the charge-out rule information.
In some embodiments, the method may further comprise:
and when the judgment result is negative, executing the step of acquiring the current concurrency number of the service platform at intervals of preset time until the sum of the concurrency number corresponding to the acquired bill data and the current concurrency number is judged to be less than or equal to the upper limit value of the concurrency number.
In some embodiments, after obtaining billing data, the method may further comprise:
and storing the bill data as historical bill data.
S420: responding to a bill query instruction of a user, and querying whether bill data corresponding to the bill query instruction exists in the bill database;
s430: and when the query result is yes, creating a bill according to the bill data.
In some embodiments, prior to creating a bill from the billing data, the method may further comprise:
judging whether the bill data is within a preset validity period or not;
and when the judgment result is yes, executing the step of creating the bill according to the bill data.
In some embodiments, the method may further comprise:
setting the validity time limit of the bill data in the bill database;
and when the bill data reaches the validity time limit, deleting the bill data reaching the validity time limit from the bill database.
S440: responding to a payment instruction of a user based on the bill, and sending an account cancellation request of the user to a business service platform in a service state before a business tangent point of the business service platform corresponding to the bill data;
s450: and after the business tangent point of the business service platform is reached, the account cancellation information in the time period corresponding to the business tangent point is subjected to account cancellation processing by the business service platform.
In some embodiments, the sending the cancellation request of the user to the business service platform in the service state before the business tangent point of the business service platform corresponding to the billing data includes:
judging whether the current time reaches a business tangent point of a business service platform corresponding to the bill data;
when the judgment result is negative, inquiring whether the service platform is in a service state currently;
and when the query result is that the service platform is in the service state currently, sending an account cancellation request of the user to the service platform.
In some embodiments, the method may further comprise:
and when the query result is that the service platform is currently in the non-service state, executing the step of querying whether the service platform is currently in the service state until the query result is yes before the service tangent point is reached.
Therefore, the third party platform of the bill service processing method can store the bill data acquired from the service platform in advance into the preset bill database, ensure that the related bill data can be directly acquired from the bill database when the bill service of the user to the service platform is subsequently processed, avoid the problem that the bill data of the user cannot be acquired because the service platform is in the non-service state, greatly increase the success rate of bill service processing, meanwhile, after the user finishes the bill payment on the third party platform, for the condition that the service platform is in the non-service state, the third party platform can continuously initiate the inquiry of the service state to the service platform to attempt to sell the bill, and can immediately send the bill selling request once the service platform is in the service state, and the account cancellation is completed, and even if the business service platform is always in a non-service state before the business is cut off and the account cancellation cannot be completed, the bill can be ensured to be completed through subsequent account checking. Compared with the prior art, the technical scheme provided by the application can solve the problem that the third-party platform is limited by the service platform when processing the bill service, improves the stability of the third-party platform when processing the bill service, meets the payment requirement of a user, and improves the user experience.
In another aspect of the present application, a processing apparatus for a billing service is further provided, fig. 5 is a schematic structural diagram of an embodiment of the processing apparatus for a billing service provided in the present application, and as shown in fig. 5, the apparatus 500 may include:
a bill data storage module 510, which may be configured to store bill data obtained from the business service platform in advance into a preset bill database;
a query module 520, configured to query whether bill data corresponding to a bill query instruction exists from the bill database in response to the bill query instruction of a user;
a bill creating module 530, configured to create a bill according to the bill data when the result of the query by the response query module is yes;
the cancellation request processing module 540 may be configured to, in response to a payment instruction of a user based on the bill, send a cancellation request of the user to a business service platform in a service state before a business tangent point of the business service platform corresponding to the bill data;
the reconciliation processing module 550 may be configured to, after the business cut point of the business service platform is reached, perform reconciliation processing on the account cancellation information in the time period corresponding to the business cut point by the business service platform.
In another aspect, the present application further provides a billing service processing server, including a processor and a memory, where the memory stores computer program instructions executed by the processor, and the computer program instructions include:
storing bill data acquired from a business service platform in advance into a preset bill database;
responding to a bill query instruction of a user, and querying whether bill data corresponding to the bill query instruction exists in the bill database;
when the query result is yes, creating a bill according to the bill data;
responding to a payment instruction of a user based on the bill, and sending an account cancellation request of the user to a business service platform in a service state before a business tangent point of the business service platform corresponding to the bill data;
and after the business tangent point of the business service platform is reached, the account cancellation information in the time period corresponding to the business tangent point is subjected to account cancellation processing by the business service platform.
Specifically, in the embodiment of the present application, the processor may include a Central Processing Unit (CPU), and may also include other single-chip microcomputers, logic gates, integrated circuits, and the like with logic processing capability, or a suitable combination thereof. The memory may include a non-volatile memory or the like.
In another embodiment, the storing the billing data obtained from the business service platform in advance to the preset billing database includes:
determining the charge-out rule information of the business service platform corresponding to the bill data of the user according to the historical bill data;
acquiring bill data from a corresponding business service platform based on the charge-out rule information;
and storing the bill data into a preset bill database.
In another embodiment, before obtaining billing data from the corresponding business service platform based on the charge-out rule information, the processor executing the computer program instructions may further implement:
acquiring a concurrency number upper limit value of a service platform;
acquiring the current concurrency number of a service platform;
judging whether the sum of the concurrency number corresponding to the acquired bill data and the current concurrency number is less than or equal to the upper limit value of the concurrency number or not;
and when the result of the judgment is yes, executing the step of acquiring bill data from the corresponding business service platform based on the charge-out rule information.
In another embodiment, execution of the computer program instructions by the processor may further result in:
and when the judgment result is negative, executing the step of acquiring the current concurrency number of the service platform at intervals of preset time until the sum of the concurrency number corresponding to the acquired bill data and the current concurrency number is judged to be less than or equal to the upper limit value of the concurrency number.
In another embodiment, after obtaining billing data, execution of the computer program instructions by the processor may further result in:
and storing the bill data as historical bill data.
In another embodiment, prior to creating a bill from the billing data, execution of the computer program instructions by the processor may further result in:
judging whether the bill data is within a preset validity period or not;
and when the judgment result is yes, executing the step of creating the bill according to the bill data.
In another embodiment, execution of the computer program instructions by the processor may further result in:
setting the validity time limit of the bill data in the bill database;
and when the bill data reaches the validity time limit, deleting the bill data reaching the validity time limit from the bill database.
In another embodiment, the sending the cancellation request of the user to the business service platform in the service state before the business tangent point of the business service platform corresponding to the billing data may include:
judging whether the current time reaches a business tangent point of a business service platform corresponding to the bill data;
when the judgment result is negative, inquiring whether the service platform is in a service state currently;
and when the query result is that the service platform is in the service state currently, sending an account cancellation request of the user to the service platform.
In another embodiment, execution of the computer program instructions by the processor may further result in:
and when the query result is that the service platform is currently in the non-service state, executing the step of querying whether the service platform is currently in the service state until the query result is yes before the service tangent point is reached.
Another aspect of the present application further provides a system for processing a billing service, which may include:
the third-party platform can be used for storing the bill data acquired from the business service platform in advance into a preset bill database; and the bill database is used for responding to a bill query instruction of a user and querying whether bill data corresponding to the bill query instruction exists or not from the bill database; and when the result of the query is yes, the third-party platform creates a bill according to the bill data; the bill data processing system is used for responding to a payment instruction of a user based on the bill and sending an account cancellation request of the user to a business service platform in a service state before a business tangent point of the business service platform corresponding to the bill data; the account cancellation processing module is used for carrying out account cancellation processing on account cancellation information in a time period corresponding to the business tangent point by the business service platform after the business tangent point of the business service platform is reached;
a billing database operable to store billing data;
the business service platform can be used for sending bill data to the third-party platform in advance, processing an account cancellation request of the third-party platform, and after the business cut-off point is reached, carrying out account cancellation processing on account cancellation information in a time period corresponding to the business cut-off point by the third-party platform.
In another aspect, the present application further provides a computer storage medium having a computer program stored thereon, which when executed by a processor, performs the steps of:
storing bill data acquired from a business service platform in advance into a preset bill database;
responding to a bill query instruction of a user, and querying whether bill data corresponding to the bill query instruction exists in the bill database;
when the query result is yes, creating a bill according to the bill data;
responding to a payment instruction of a user based on the bill, and sending an account cancellation request of the user to a business service platform in a service state before a business tangent point of the business service platform corresponding to the bill data;
and after the business tangent point of the business service platform is reached, the account cancellation information in the time period corresponding to the business tangent point is subjected to account cancellation processing by the business service platform. Therefore, the embodiment of the method, the device, the server or the system for processing the bill service can ensure that the related bill data can be directly obtained from the bill database when the bill service of the service platform is subsequently processed by the user by storing the bill data obtained from the service platform into the preset bill database, can avoid the problem that the bill data of the user cannot be obtained due to the fact that the service platform is in a non-service state, greatly increases the success rate of bill service processing, meanwhile, after the user finishes the bill payment on a third-party platform, for the condition that the service platform is in the non-service state, the service state can be continuously inquired to the service platform to try to sell the bill, once the service platform is inquired to be in the service state, the bill selling request can be immediately sent, and the account cancellation is completed, and even if the business service platform is always in a non-service state before the business is cut off and the account cancellation cannot be completed, the bill can be ensured to be completed through subsequent account checking. Compared with the prior art, the technical scheme provided by the application can solve the problem that the third-party platform is limited by the service platform when processing the bill service, improves the stability of the third-party platform when processing the bill service, meets the payment requirement of a user, and improves the user experience.
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 Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (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 apparatuses, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or implemented by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, apparatus 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 apparatus and computer storage medium embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference may be made to some descriptions of the method embodiments for relevant points.
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.