Detailed Description
In order to better understand the technical solutions, the technical solutions of the embodiments of the present specification are described in detail below with reference to the drawings and specific embodiments, and it should be understood that the specific features of the embodiments and embodiments of the present specification are detailed descriptions of the technical solutions of the embodiments of the present specification, and are not limitations of the technical solutions of the present specification, and the technical features of the embodiments and embodiments of the present specification may be combined with each other without conflict.
In a first aspect, an embodiment of the present specification provides an electronic resource processing method, as shown in fig. 1, which is a flowchart of the electronic resource processing method provided in the embodiment of the present specification, and the method includes the following steps:
step S11: acquiring an electronic resource template, wherein a target service rule is configured in the electronic resource template;
step S12: determining a target service scene corresponding to the target service rule according to a pre-configured configuration file, wherein the configuration file comprises a mapping relation between the service scene and the service rule;
step S13: and marking the scene identification of the target service scene on the electronic resource template, and marking the scene identification of the target service scene on the issued electronic resource when the electronic resource is issued through the marked electronic resource template.
The electronic resource processing method in this embodiment may be applied to a user terminal, and may also be applied to a server, for example, in a server for issuing an electronic resource platform, for example, when the electronic resource platform is an e-commerce platform, the server is a server of the e-commerce platform. For convenience of description, the electronic resource processing method provided in the embodiments of the present specification is described in detail below by taking a server applied to an e-commerce platform as an example.
In the embodiment of the present specification, the pre-configured configuration file includes a mapping relationship between a service scenario and a service rule, the service scenario may be set according to actual needs, and the service scenario may be a scenario involved in an e-commerce platform, for example, the service scenario may be a transfer scenario, a payment scenario, a recharge scenario, and the like. The configuration file may include one service scenario or may include a plurality of service scenarios.
For example, when the service scenario is a transfer scenario, the corresponding service rule may include a bank card transfer rule and a balance transfer rule of an e-commerce platform. When the business scenario is a recharge scenario, the corresponding business rules may include bank card recharge, balance recharge, and the like. A business scenario may correspond to one or more business rules, which are not limited herein. It should be noted that the service rule needs to be matched with the service scenario, that is, the transfer scenario corresponds to the transfer rule, and the recharge scenario corresponds to the recharge rule.
The configuration file may include, in addition to the mapping relationship between the service scenario and the service rule, other information, for example, environment information and file information to be loaded to complete the service request, which is not limited herein. The created configuration file can be saved and run in a server of the e-commerce platform.
In the embodiment of the present disclosure, the electronic resource template may be used to issue an electronic resource, and the electronic resource may be an electronic red packet, an electronic card ticket, electronic money, or the like. In step S11, the obtained electronic resource template may be any electronic resource template, and for convenience of description, in this embodiment of the present specification, the electronic resource is taken as an example of an electronic red envelope, and then the obtained electronic resource template may correspond to an electronic red envelope template for issuing an electronic red envelope.
It should be understood that the electronic resources issued by the electronic resource template are all usage-conditional, and the electronic resources all correspond to the usage business scenario and the usage business rule. For example, when the electronic resource template is a template for issuing a bank card transfer red packet, the red packet issued by the template can only be used in bank card transfer transactions in a transfer scene, and when the electronic resource template is a template for issuing a bank card recharge red packet, the red packet issued by the template can only be used in bank card recharge transactions in a recharge scene.
The electronic resource template can be configured in advance, the configuration of the electronic resource template comprises the configuration of the target business rule, and the use condition of the electronic resource is determined through the configured business rule. Taking the electronic red envelope template as an example, when the electronic red envelope template is configured, a target business rule of the electronic red envelope needs to be added. Specifically, when an electronic red envelope used for bank card transfer needs to be issued, bank card transfer rules need to be added in an electronic red envelope template, and when an electronic red envelope used for balance transfer needs to be issued, balance transfer rules need to be added in the electronic red envelope template. The added target business rule may be one or more, and is not limited herein. Generally speaking, when the electronic resource template is configured, the added target business rule belongs to the same business scenario.
In the embodiment of the present specification, a target service scenario corresponding to a target service rule can be determined by configuring a file and the target service rule in an electronic resource template. Different service scenes can be configured with different scene identifiers, and the scene identifiers can be set according to actual needs, for example, the scene identifiers are randomly allocated to all the service scenes, and the scene identifiers of the different service scenes are different; or setting a scene identification for each service scene in a predetermined order.
After the scene identification of the target service scene is determined, marking the current electronic resource template by using the scene identification, namely adding the scene identification of the target service scene to the electronic resource template. Furthermore, when the marked electronic resource template is used for issuing the electronic resource, the issued electronic resource is marked, and the scene mark of the target service scene is marked, so that the electronic resource can be ensured to be used only in the target service scene.
By the method, the mapping relation between the service scene and the service rule is established through the configuration file, when a new service scene is accessed, the electronic resource issued by the electronic resource template can be oriented to the electronic resource used in the new service scene only by setting the mapping relation between the new service scene and the service rule in the configuration file and matching with the target service rule configured in the electronic resource template, so that the development cost is effectively reduced, and the computer resource is saved.
In this embodiment of the present specification, the configuration file may be created in the following manner: setting one or more service scenes in the configuration file; for each service scene, configuring a request parameter value for identifying the service scene; and setting one or more business rules under each business scene so as to establish a mapping relation between the business scenes and the business rules.
In this embodiment of the present specification, one or more service scenarios in the configuration file may be set according to actual needs, for example, according to a scenario related to a service request. The service request may be a user initiated request, for example, the service request may be a transfer transaction request, a recharge transaction request, or the like. Therefore, a transfer scenario, a recharge scenario, and the like may be configured in the configuration file, and certainly, the service scenario may also include other scenarios, which are not limited herein.
For each service scenario, a request parameter value for identifying the service scenario from a configuration file may be configured, and in this embodiment of the present specification, the request parameter value may be a parameter value corresponding to a request parameter in a service request. Because there are many parameters contained in the service request, the request parameters can be set according to actual needs. In one embodiment, the request parameter may be a bizType parameter, and the service scenario may be configured by a parameter value of the bizType parameter. For example, for a service scenario being a transfer scenario, a parameter value of a bizType parameter configured to identify the transfer scenario is transfer. Thus, the service scenario can be set in the following way: { "scene name": "transfer scene", "request parameter": bizType "," parameter value for request parameter ": transfer" }.
Next, the business rules in each business scenario need to be set. In the embodiment of the present specification, the business rules need to be associated with the business scenario to establish a mapping relationship between the business scenario and the business rules.
The business rules may be preset or selected from a preset rule base. The business rules may include rule names and rule contents. Still taking the above transfer scenario as an example, if the transfer scenario includes a bank card transfer rule and a balance transfer rule, the relationship between the business scenario and the business rule may be associated in the following manner: { "scene name": "transfer scene", "request parameter": bizType "," parameter value for request parameter ": transfer", "business rule name": bankcardransfer, balanceTransfer "}. Thus, when the configuration file is operated, each business rule is traversed through the business rule name, and the content of the business rule is loaded.
In addition, after a new service scene is accessed, the configuration file can be updated in the following way: and when a new service scene is added, updating the configuration file according to the request parameter value corresponding to the new service scene and the service rule corresponding to the new service scene. Namely, by defining a new service scene in the configuration file and a mapping relationship between the newly added service scene and the service rule in the manner described above, the electronic resource template can be associated to the new service scene through the configuration file, and the electronic resource can be further distributed in the new service scene.
In summary, the electronic resource can be issued through the pre-configured configuration file and the electronic resource template, and for better understanding of the electronic resource issuing process in the embodiment of the present specification, please refer to fig. 2, which is a flowchart of the electronic resource issuing provided in the embodiment of the present specification, and includes the following steps.
Step S21, defining a service scene;
step S22, configuring the mapping relation between the service scene and the service rule;
step S23, creating an electronic resource template;
step S24: determining whether the electronic resource template is matched with the service scene, if so, executing step S25, otherwise, executing step S26;
step S25: printing a scene identifier of a service scene on the electronic resource template;
step S26: issuing the electronic resource through the electronic resource template;
step S27: judging whether the electronic resource template is marked with a scene identifier, if so, executing the step S28;
step S28: and printing scene identification on the electronic resource.
In the above process, the creation of the profile is completed through steps S21 and S22. In step S23, the configuration of the electronic resource template may be completed by adding the target business rule. For example, when a template for transferring electronic resources needs to be created, corresponding transfer rules need to be added to the template. In step S24, it is determined whether a service scenario matching the target service rule exists according to the target service rule in the electronic resource template and the mapping relationship in the pre-configured configuration file, and if so, a scenario identifier of the service scenario is printed on the electronic resource template. Further, when the electronic resource is issued, whether the electronic resource is marked with the scene identification is judged, if yes, the electronic resource is marked and issued, and if not, the electronic resource is directly issued without marking, so that the issuing process of the electronic resource is completed.
Further, after the electronic resource is issued to the user, the user may use the electronic resource in a subsequent transaction, and therefore, the method provided in this specification further includes the following steps after the scene identifier of the target service scene is marked on the issued electronic resource: when a target service request initiated by a target account is detected, acquiring N issued sub-resources of the target account, wherein N is a positive integer; and determining a target electronic resource suitable for the service scene corresponding to the target service request from the N issued electronic resources.
It should be understood that the target account may be an account created through a registration operation by a user using the issuing electronic resource platform, for example, when the issuing electronic resource platform is an e-commerce platform, the target account may be any account on the e-commerce platform. For a target account, there may be N released electronic resources in the account, where N is a positive integer. Taking an electronic resource as an example of an electronic red envelope, one or more electronic red envelopes may exist in the account.
It should be noted that the issued electronic resource may be an electronic resource issued through each electronic resource template, and the electronic resource template may issue the electronic resource by detecting a user operation, or may actively issue the electronic resource according to a preset instruction. For example, when the electronic resource template is an electronic red envelope template, and a user clicks a pickup button on an electronic red envelope pickup interface through the electronic device, the electronic red envelope template may be triggered to issue an electronic red envelope to an account of the user. Alternatively, when the e-commerce platform carries out the preferential event, the time for issuing the electronic red envelope can be set, for example, the electronic red envelope is automatically issued to the accounts of the users of the e-commerce platform through the electronic red envelope template in the early morning of the new year. The issued electronic resources may include various types of electronic resources, such as electronic resources suitable for a money transfer scenario, electronic resources suitable for a recharge scenario, and the like.
The target service request may be any service request initiated by the target account, such as a transfer transaction request, a consumption transaction request, and the like. When a target service request is received, it may be determined whether an issued electronic resource exists in the target account, and if so, it may be further determined whether a target electronic resource applicable to a currently requested service scenario exists in the issued electronic resources.
In the embodiment of the present specification, the target electronic resource may be determined by: acquiring a target request parameter value in the target service request; identifying a service scene corresponding to the target service request based on the pre-configured configuration file and the target request parameter value; acquiring a first scene identifier marked on each of the N issued sub-resources and a second scene identifier of a service scene corresponding to the target service request; and matching each acquired first scene identifier with the second scene identifier respectively, and taking the issued electronic resource corresponding to the successfully matched first scene identifier as the target electronic resource.
In the specific implementation process, when a target service request is detected, a target request parameter value in the request is obtained first, where the target request parameter is consistent with a request parameter used for setting a service scenario in a configuration file. For example, if the request parameter used by the service scenario is set to bizType, the parameter value corresponding to bizType is obtained in the target service request as the target request parameter value.
And then, searching whether a service scene corresponding to the target request parameter value exists in the configuration file, and if the service scene corresponding to the target request parameter value exists, further determining whether a target electronic resource suitable for the service scene exists in the N issued electronic resources. In the specific implementation process, the first scene identifier of each electronic resource in the issued electronic resources needs to be determined, the first scene identifier of each electronic resource is matched with the second scene identifier of the service scene one by one, if the matching is successful, the electronic resources are consistent with the scene identifiers of the service scene, and the electronic resources are the electronic resources suitable for the service scene.
For example, following the above example, the scenario name in the configuration file is the transfer scenario, the target request parameter is bizType, and the target request parameter value is transfer. And if the acquired bizType request parameter value in the target service request is also 'transfer', the service scene corresponding to the target service request is the transfer scene. Assuming that the second scenario identifier of the transfer scenario is 0001, matching the second scenario identifier with the first scenario identifier marked on the issued electronic resource, and taking the issued electronic resource marked with 0001 as a target electronic resource suitable for the transfer service scenario.
It should be noted that the sent electronic resource may include an electronic resource marked with the first scene identifier, and may also include an electronic resource not marked with any scene identifier. That is, the issued electronic resources may include electronic resources issued by marked electronic resource templates, or may include electronic resources issued by unmarked electronic resource templates. Therefore, in this embodiment of the present specification, after the N discharged electronic resources are obtained, the electronic resources marked with the scene identifiers may be further obtained, and the scene identifiers of the electronic resources are obtained to be matched with the second scene identifier.
In this embodiment of the present specification, after determining the target electronic resource, the following steps may be further performed: and determining available electronic resources suitable for the target service request in the target electronic resources based on the usage rule of the target electronic resources and the parameters associated with the usage rule in the target service request.
It should be understood that the target electronic resource has specific usage rules, and taking the target electronic resource as an electronic red packet suitable for a transfer service scenario as an example, the usage rules of the electronic red packet may include a usage period of the electronic red packet, a deduction amount of the electronic red packet, a deduction rule, and the like. The usage rule of the target electronic resource may be associated with a parameter in the target service request, for example, if the usage rule of the target electronic resource is used when the transaction is 500 yuan full, the parameter associated with the usage rule in the target service request is a transaction amount parameter. When the associated parameters satisfy the usage rules of the electronic resource, the electronic resource is an available electronic resource. Following the above example, if the usage rule of the target electronic resource is used when the transaction is 500 yuan full, and the transaction amount parameter in the target transaction request is 500 yuan or more, the target electronic resource is an available electronic resource.
In order to better understand the usage process of the electronic resource in the embodiment of the present specification, please refer to fig. 3, which is a flow chart of the usage of the electronic resource provided for the embodiment of the present specification, and includes the following steps.
Step S31: detecting a target service request initiated by a target account;
step S32: acquiring the released electronic resources of the target account;
step S33: determining whether a service scene corresponding to the target service request exists, if so, executing step S34, otherwise, executing step S35;
step S34: determining whether the first scene identification on the issued electronic resource is matched with the second scene identification of the service scene, if so, executing step S35, otherwise, executing step S37;
step S35: judging whether the usage rule of the issued electronic resource is suitable for the target service request, if so, executing step S36, otherwise, executing step S37;
step S36: determining that the issued electronic resource is available;
step S37: it is determined that the issued electronic resource is not available.
In the using process of the issued electronic resource, when a target service request initiated by a target account is detected, the issued electronic resource of the target account is obtained first, and if the issued electronic resource does not exist in the target account, the subsequent steps do not need to be executed. And when the issued electronic resources exist in the target account, further judging whether the target service request hits a service scene set in the configuration file. Specifically, the service scenario may be determined according to the target request parameter value, if the service scenario is hit, all issued electronic resources owned by the target account need to be traversed, whether a first scenario identifier on the electronic resource is consistent with a second scenario identifier of the hit service scenario is determined, if so, it is indicated that the electronic resource is an electronic resource applicable to the service scenario, whether the electronic resource can be used may be further determined, that is, whether a usage rule of the electronic resource is applicable to the target service request, and if so, it is determined that the electronic resource is an available electronic resource.
In addition, when the target service request does not hit the service scenario in the configuration file, there may also be an electronic resource applicable to the target service request, and therefore, at this time, it may be determined one by one whether the usage rule of the issued electronic resource is applicable to the target service request, and if so, it indicates that the electronic resource is an available electronic resource, otherwise, it is an unavailable electronic resource.
In step S35, if the electronic resource is an electronic resource suitable for the service scenario, there is a possibility that the usage rule of the electronic resource is not suitable for the target service request. For example, the service scenario is a transfer scenario, the electronic resources used in the transfer scenario include electronic resources used for transfer full 200 and electronic resources used for transfer full 500, and if the transfer amount of the target service request is 300, only the electronic resources used for transfer full 200 are available, and the electronic resources used for transfer full 500 are unavailable.
To sum up, in the scheme in the embodiment of the present specification, the mapping relationship between the service scenario and the service rule is set through the pre-configured configuration file, and the association between the electronic resource template and the service scenario is established in a configured manner, so that when the electronic resource template is used to issue the electronic resource, the issued electronic resource can be associated with the specific service scenario, thereby avoiding the implementation of the directional issue of the electronic resource through the processes of development, testing and issuance, saving the computer resource, and improving the efficiency of accessing the electronic resource to the service scenario. Meanwhile, when a new service scene is accessed, only the mapping relation between the new service scene and the service rule needs to be set in the configuration file, so that the development cost for the new service scene is reduced.
In a second aspect, an embodiment of the present specification provides an electronic resource processing method, please refer to fig. 4, where the method includes:
step S41: when a target service request initiated by a target account is detected, determining a service scene corresponding to the target service request according to a pre-configured configuration file;
step S42: acquiring N issued sub-resources of the target account, and determining a target electronic resource suitable for the service scene in the N issued sub-resources based on the scene identifier of the service scene, wherein N is a positive integer;
wherein at least one of the N issued electronic resources is issued by the method provided in the first aspect.
In this embodiment of the present specification, the target account may include an electronic resource issued through the marked electronic resource template, that is, an electronic resource directed to a service scenario. When a target service request is initiated by a target account, a target electronic resource oriented to a service scene can be determined from the N issued electronic resources. The specific implementation process has been described in detail in the electronic resource processing method provided in the first aspect of the embodiments of the present specification, and is not described here again.
In an alternative implementation, the configuration file is created by:
setting one or more service scenes in the configuration file;
for each service scene, configuring a request parameter value for identifying the service scene;
and setting one or more business rules under each business scene so as to establish a mapping relation between the business scenes and the business rules.
In an optional implementation manner, when a target service request initiated by a target account is detected, determining a service scenario corresponding to the target service request according to a pre-configured configuration file includes:
acquiring a target request parameter value in the target service request;
and identifying a service scene corresponding to the target service request based on the pre-configured configuration file and the target request parameter value.
In an optional implementation manner, the obtaining N issued sub-resources of the target account, and determining, based on the scene identifier of the service scene, a target electronic resource applicable to the service scene from among the N issued sub-resources includes:
acquiring first scene identifiers marked on M issued sub-resources in the N issued sub-resources and second scene identifiers of a service scene corresponding to the target service request, wherein M is a positive integer less than or equal to N;
and matching each acquired first scene identifier with the second scene identifier respectively, and taking the issued electronic resource corresponding to the successfully matched first scene identifier as the target electronic resource.
Specifically, the N issued electronic resources of the target account may include electronic resources with a scene identifier (i.e., electronic resources issued through the electronic resource template with a scene identifier), and may also include electronic resources without a scene identifier. In this embodiment, for the marked M electronic resources, the first scene identifier of each electronic resource in the M electronic resources may be obtained, and the obtained first scene identifiers are matched with the second scene identifiers of the service scene one by one, and the electronic resource successfully matched is used as the target electronic resource.
For the untagged electronic resource, it may further be determined whether the untagged electronic resource is suitable for the current business scenario, for example, the untagged electronic resource is determined according to the usage rule of the untagged electronic resource, and if the usage rule of the untagged electronic resource meets the target business request, the untagged electronic resource may also be used as the target electronic resource.
In an optional implementation manner, after determining, from the N sent electronic resources, a target electronic resource applicable to the service scenario, the method further includes:
and determining available electronic resources suitable for the target service request in the target electronic resources based on the usage rule of the target electronic resources and the parameters associated with the usage rule in the target service request.
With regard to the above-mentioned apparatus, the specific implementation of each step has been described in detail in the embodiment of the electronic resource processing method provided in the first aspect of the embodiment of the present specification, and a detailed description will not be made here.
In a third aspect, based on the same inventive concept, an embodiment of the present specification provides an electronic resource processing apparatus, please refer to fig. 5, including:
an obtaining module 51, configured to obtain an electronic resource template, where a target service rule is configured in the electronic resource template;
a scene determining module 52, configured to determine, according to a pre-configured configuration file, a target service scene corresponding to the target service rule, where the configuration file includes a mapping relationship between the service scene and the service rule;
the processing module 53 is configured to mark the electronic resource template with the scene identifier of the target service scene, and mark the scene identifier of the target service scene on the issued electronic resource when the electronic resource is issued through the marked electronic resource template.
In an alternative implementation, the configuration file is created by:
setting one or more service scenes in the configuration file;
for each service scene, configuring a request parameter value for identifying the service scene;
and setting one or more business rules under each business scene so as to establish a mapping relation between the business scenes and the business rules.
In an alternative implementation, the apparatus further includes:
and the updating module is used for updating the configuration file according to the request parameter value corresponding to the new service scene and the service rule corresponding to the new service scene when the new service scene is added.
In an alternative implementation, the apparatus further includes:
the electronic resource acquisition module is used for acquiring N issued electronic resources of a target account when a target service request initiated by the target account is detected, wherein N is a positive integer;
and the first electronic resource determining module is used for determining a target electronic resource suitable for a service scene corresponding to the target service request from the N issued electronic resources.
In an alternative implementation, the first electronic resource determination is configured to:
acquiring a target request parameter value in the target service request;
identifying a service scene corresponding to the target service request based on the pre-configured configuration file and the target request parameter value;
acquiring a first scene identifier marked on each of the N issued sub-resources and a second scene identifier of a service scene corresponding to the target service request;
and matching each acquired first scene identifier with the second scene identifier respectively, and taking the issued electronic resource corresponding to the successfully matched first scene identifier as the target electronic resource.
In an alternative implementation, the apparatus further includes:
and the second electronic resource determining module is used for determining available electronic resources suitable for the target service request from the target electronic resources based on the usage rule of the target electronic resources and the parameters associated with the usage rule in the target service request.
With regard to the above-mentioned apparatus, the specific functions of the respective modules have been described in detail in the embodiments of the electronic resource processing method provided in the embodiments of the present specification, and will not be elaborated herein.
In a fourth aspect, based on the same inventive concept, an embodiment of the present specification provides an electronic resource processing apparatus, please refer to fig. 6, including:
the scene determining module 61 is configured to, when a target service request initiated by a target account is detected, determine a service scene corresponding to the target service request according to a pre-configured configuration file;
the processing module 62 is configured to obtain N issued sub-resources of the target account, and determine, based on the scene identifier of the service scene, a target electronic resource applicable to the service scene from the N issued sub-resources, where N is a positive integer;
wherein at least one of the N issued electronic resources is issued by the method provided in the first aspect.
In an alternative implementation, the configuration file is created by:
setting one or more service scenes in the configuration file;
for each service scene, configuring a request parameter value for identifying the service scene;
and setting one or more business rules under each business scene so as to establish a mapping relation between the business scenes and the business rules.
In an alternative implementation, the scenario determination module 61 is configured to:
acquiring a target request parameter value in the target service request;
and identifying a service scene corresponding to the target service request based on the pre-configured configuration file and the target request parameter value.
In an alternative implementation, the processing module 62 is configured to:
acquiring first scene identifiers marked on M issued sub-resources in the N issued sub-resources and second scene identifiers of a service scene corresponding to the target service request, wherein M is a positive integer less than or equal to N;
and matching each acquired first scene identifier with the second scene identifier respectively, and taking the issued electronic resource corresponding to the successfully matched first scene identifier as the target electronic resource.
In an alternative implementation, the apparatus further includes:
and the updating module is used for determining available electronic resources suitable for the target service request in the target electronic resources based on the usage rule of the target electronic resources and the parameters associated with the usage rule in the target service request.
With regard to the above-mentioned apparatus, the specific functions of the respective modules have been described in detail in the embodiments of the electronic resource processing method provided in the embodiments of the present specification, and will not be elaborated herein.
In a fifth aspect, based on the same inventive concept as the electronic resource processing method in the foregoing embodiments, embodiments of the present specification further provide a server, as shown in fig. 7, including a memory 404, a processor 402, and a computer program stored on the memory 404 and executable on the processor 402, where the processor 402 implements the steps of any one of the foregoing electronic resource processing methods when executing the program.
Where in fig. 7 a bus architecture (represented by bus 400) is shown, bus 400 may include any number of interconnected buses and bridges, with bus 400 linking together various circuits including one or more processors, represented by processor 402, and memory, represented by memory 404. The bus 400 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 406 provides an interface between the bus 400 and the receiver 401 and transmitter 403. The receiver 401 and the transmitter 403 may be the same element, i.e., a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 402 is responsible for managing the bus 400 and general processing, while the memory 404 may be used for storing data used by the processor 402 in performing operations.
In a sixth aspect, based on the inventive concept based on the electronic resource processing method as in the previous embodiments, the present specification further provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of any one of the methods based on the electronic resource processing method as described above.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. 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.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.