Detailed Description
In order to better understand the technical solutions described above, the technical solutions of the embodiments of the present specification are described in detail below through the accompanying drawings and the specific embodiments, and it should be understood that the specific features of the embodiments of the present specification and the specific features of the embodiments of the present specification are detailed descriptions of the technical solutions of the embodiments of the present specification, and not limit the technical solutions of the present specification, and the technical features of the embodiments of the present specification may be combined without conflict.
In a first aspect, an embodiment of the present disclosure 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 disclosure, where the method includes the following steps:
step S11: acquiring an electronic resource template, wherein a target business 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 contains a mapping relation between the service scene and the service rule;
step S13: and marking the scene identification of the target business scene on the electronic resource template, and marking the scene identification of the target business scene on the electronic resource when the electronic resource is issued through the marked electronic resource template.
The electronic resource processing method in the embodiment of the present disclosure may be applied to a user terminal or a server, for example, in a server that issues an electronic resource platform, for example, when the electronic resource platform is Shang Ping, the server is a server of an e-commerce platform. For convenience of explanation, the electronic resource processing method provided in the embodiment of the present specification will be described in detail below by taking a server applied to an e-commerce platform as an example.
In this embodiment of the present disclosure, the preconfigured configuration file includes a mapping relationship between a service scenario and a service rule, where 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 recharging scenario, and so on. The configuration file may contain one service scene or multiple service scenes.
For each service scenario, a corresponding service rule may be set, 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 the e-commerce platform. When the service scenario is a recharging scenario, the corresponding service rule may include bank card recharging, balance recharging, and the like. A business scenario may correspond to one or more business rules, 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 recharging scenario corresponds to the recharging rule.
The configuration file may include other information besides the mapping relationship between the service scenario and the service rule, for example, environment information and file information to be loaded for completing the service request, which is not limited herein. The created configuration file may 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 electronic resources, and the electronic resources may be electronic red packages, electronic coupons, electronic currencies, and the like. In step S11, the obtained electronic resource template may be any electronic resource template, and for convenience of explanation, in this embodiment of the present disclosure, the electronic resource is taken as an electronic red envelope, and then the obtained electronic resource template may be correspondingly taken as an electronic red envelope template for issuing the electronic red envelope.
It should be understood that the electronic resources issued by the electronic resource templates are all in use, and the electronic resources correspond to the service scenes used and the service rules used. 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 a bank card transfer transaction in a transfer scene, and when the electronic resource template is a template for issuing a bank card recharging red packet, the red packet issued by the template can only be used in a bank card recharging transaction in a recharging scene.
The electronic resource template can be preconfigured, 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 an 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 purse used for bank card transfer needs to be issued, a bank card transfer rule needs to be added in an electronic purse template, and when an electronic purse used for balance transfer needs to be issued, a balance transfer rule needs to be added in the electronic purse template. The target business rule may be added in one or more, and is not limited herein. In general, when an electronic resource template is configured, the added target business rule belongs to the same business scene.
In the embodiment of the specification, the target service scene corresponding to the target service rule can be determined through the configuration file and the target service rule in the electronic resource template. Different service scenes can be configured with different scene identifications, the scene identifications can be set according to actual needs, for example, the scene identifications are randomly distributed for all the service scenes, and the scene identifications of the different service scenes are different; or setting scene identifications for each of the traffic scenes in a predetermined order.
After determining the scene identification of the target service scene, 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 electronic resource template after marking is used for issuing the electronic resource, the issued electronic resource is marked, and the scene identification 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, and 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 the embodiment of the present specification, the configuration file may be created in the following manner: setting one or more business scenes in the configuration file; for each service scenario, configuring a request parameter value for identifying the service scenario; and setting one or more business rules in the business scenes aiming at each business scene so as to establish a mapping relation between the business scenes and the business rules.
In the embodiment of the present disclosure, one or more service scenarios in the configuration file may be set according to actual needs, for example, setting according to a scenario involved in a service request. The service request may be a user initiated request, for example, the service request may be a transfer transaction request, a refill transaction request, or the like. Therefore, a transfer scenario, a recharge scenario, etc. may be configured in the configuration file, and of course, the business 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 the configuration file may be configured, where in this embodiment of the present specification, the request parameter value may be a parameter value corresponding to a request parameter in the service request. Because there are many parameters included 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. The business scenario may thus be set by: { "scene name": "transfer scene", "request parameter": "bizType", "parameter value of request parameter": "transfer" }.
Next, a business rule needs to be set for each business scenario. Because a service scenario may include a plurality of service rules, for example, a bank card transfer, balance transfer, etc. may be included in a transfer scenario, and different transfer modes correspond to different service rules, in this embodiment of the present disclosure, the service rules need to be associated with the service scenario, and a mapping relationship between the service scenario and the service rules needs to be established.
The business rules may be preset or selected from a preset rule base. Business rules may include rule names and rule content. Taking the above account of the account transfer scenario as an example, if the account transfer scenario includes a bank card account transfer rule and a balance account transfer rule, the relationship between the business scenario and the business rule may be associated by: { "scene name": "transfer scene", "request parameter": "bizType", "parameter value of request parameter": "transfer", "business rule name": "bankCardTransfer, bandacransfer" }. Thus, when the configuration file is operated, each business rule is traversed through the name of the business rule, and the content of the business rule is loaded.
In addition, when a new service scenario is accessed, the configuration file may be updated by: 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. In other words, by defining the new service scene in the configuration file and adding the mapping relation between the new service scene and the service rule in the above manner, the electronic resource template can be associated to the new service scene through the configuration file, and further, the electronic resource under the new service scene can be issued.
In summary, the electronic resource may be issued through a pre-configured configuration file and an electronic resource template, and in order to better understand the electronic resource issuing process in the embodiment of the present disclosure, please refer to fig. 2, which is a flowchart for electronic resource issuing provided in the embodiment of the present disclosure, including the following steps.
Step S21, defining a service scene;
step S22, configuring a mapping relation between a service scene and a 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 the step S25, and if not, executing the step S26;
Step S25: marking scene identification of a business scene on the electronic resource template;
step S26: issuing electronic resources through an electronic resource template;
step S27: judging whether the electronic resource template is marked with a scene identifier or not, if so, executing a step S28;
step S28: and marking a scene identifier on the electronic resource.
In the above process, the creation of the configuration file 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 of a transfer electronic resource needs to be created, a corresponding transfer rule needs to be added to the template. In step S24, according to the target service rule in the electronic resource template and the mapping relation in the pre-configured configuration file, it is determined whether there is a service scene matching with the target service rule, if so, the electronic resource template is marked with the scene identifier of the service scene. Further, when the electronic resource is issued, whether the electronic resource is marked with a scene identifier is judged, if so, 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, so the method provided by the embodiment of the present disclosure further includes the following steps after marking the scene identifier of the target service scene on the issued electronic resource: when a target service request initiated by a target account is detected, N issued electronic resources of the target account are acquired, wherein N is a positive integer; and determining target electronic resources applicable to the service scene corresponding to the target service request from the N issued electronic resources.
It should be appreciated that the target account may be an account created by a registration operation using a user who issues an electronic resource platform, for example, when the electronic resource platform is Shang Ping, the target account may be any account on the e-commerce platform. For a target account, there may be N electronic resources issued in the account, N being a positive integer. Taking electronic resources as electronic red packages as an example, there may be one or more electronic red packages in the account.
It should be noted that the electronic resource that has been issued may be an electronic resource that is 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, the electronic red envelope template may be triggered to issue an electronic red envelope into the account of the user when the user clicks the get button on the electronic red envelope get interface through the electronic device. Or when the e-commerce platform develops the preferential activity, the time for issuing the electronic red package can be set, for example, the electronic red package is automatically issued to the account of each user of the e-commerce platform in the early morning of new year through the electronic red package template. The issued electronic resources may include various types of electronic resources, such as electronic resources suitable for a transfer scenario, electronic resources suitable for a recharging 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 consumer transaction request, etc. When the target service request is received, whether the issued electronic resource exists in the target account or not can be determined, if so, whether the target electronic resource applicable to the service scene of the current request exists in the issued electronic resource or not is further determined.
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 issued electronic resource in the N issued electronic resources and a second scene identifier of a service scene corresponding to the target service request; and respectively matching each acquired first scene identifier with the second scene identifier, and taking the issued electronic resource corresponding to the successfully matched first scene identifier as the target electronic resource.
In the implementation process, when a target service request is detected, a target request parameter value in the request is acquired first, wherein the target request parameter is consistent with a request parameter used for setting a service scene in a configuration file. For example, the request parameter used by the service scenario is set to be bizType, and then the parameter value corresponding to the 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 so, further determining whether target electronic resources suitable for the service scene exist in the N issued electronic resources. In the 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 and the second scene identifier of the service scene are matched one by one, and if the matching is successful, the electronic resource is identical to the scene identifier of the service scene, and the electronic resource is the electronic resource suitable for the service scene.
For example, taking the example above, the scene name in the configuration file is the transfer scene, the target request parameter is bizType, and the target request parameter value is transfer. If the request parameter value of the bizType obtained in the target service request is also "transfer", the service scenario corresponding to the target service request is the transfer scenario. Assuming that a second scene identifier of the transfer scene is 0001, matching the second scene identifier with a first scene identifier marked on the issued electronic resource, and taking the issued electronic resource marked with 0001 as a target electronic resource applicable to the transfer service scene.
It should be noted that the issued electronic resource may include an electronic resource marked with the first scene identifier, or may include an electronic resource not marked with any scene identifier. That is, the electronic resources that have been issued may include electronic resources that have been issued by the electronic resource template after the marking, or may include electronic resources that have been issued by the electronic resource template that has not been marked. Therefore, in the embodiment of the present disclosure, after acquiring N issued electronic resources, the electronic resources marked with the scene identifiers may be further acquired, and the scene identifiers of the electronic resources are acquired to be matched with the second scene identifier.
In the embodiment of the present specification, after determining the target electronic resource, the following steps may be further performed: and determining available electronic resources applicable to the target service request from the target electronic resources based on the usage rules of the target electronic resources and parameters associated with the usage rules in the target service request.
It should be understood that, the target electronic resource has a specific usage rule, taking the target electronic resource as an electronic red packet suitable for the account transfer service scenario as an example, the usage rule of the electronic red packet may include a usage period of the electronic red packet, an amount of deduction of the electronic red packet, a full-subtraction 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 the transaction amount parameter. When the above-mentioned related parameters meet the rule of using electronic resource, the electronic resource is the available electronic resource. Along the above example, if the usage rule of the target electronic resource is that the target electronic resource is used when the transaction is full of 500 yuan, and the transaction amount parameter in the target transaction request is greater than or equal to 500 yuan, the target electronic resource is an available electronic resource.
In order to better understand the use process of the electronic resource in the embodiment of the present disclosure, please refer to fig. 3, which is a flowchart for using the electronic resource provided in the embodiment of the present disclosure, and includes the following steps.
Step S31: detecting a target service request initiated by a target account;
step S32: acquiring issued electronic resources of a target account;
step S33: determining whether a service scene corresponding to the target service request exists, if so, executing step S34, and if not, executing step S35;
step S34: determining whether the first scene identifier on the issued electronic resource is matched with the second scene identifier of the service scene, if so, executing the step S35, otherwise, executing the step S37;
step S35: judging whether the issued usage rule of the electronic resource is applicable to the target service request, if so, executing the step S36, and if not, executing the 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 use process of the issued electronic resources, when a target service request initiated by a target account is detected, the issued electronic resources of the target account are firstly obtained, and if the issued electronic resources do not exist in the target account, the subsequent steps are not required to be executed. When the issued electronic resources exist in the target account, whether the target service request hits the service scene set in the configuration file is further judged. 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 the first scenario identifier on the electronic resource is consistent with the 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 can be further determined, that is, whether the 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 be an electronic resource applicable to the target service request, so that it may be determined whether the usage rule of the issued electronic resource is applicable to the target service request one by one at this time, if so, it indicates that the electronic resource is an available electronic resource, otherwise, it is an unavailable electronic resource.
In step S35, when the electronic resource is an electronic resource suitable for the service scenario, it is possible 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, and the electronic resources used in the transfer scenario include an electronic resource used by transfer full 200 and an electronic resource used by transfer full 500, and if the transfer amount requested by the target service is 300, only the electronic resource used by transfer full 200 is an available electronic resource, and the electronic resource used by transfer full 500 is an unavailable electronic resource.
In summary, in the solution in the embodiment of the present disclosure, the mapping relationship between the service scenario and the service rule is set by using the pre-configured configuration file, so that the association between the electronic resource template and the service scenario is established in a configured manner, and 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 implementing the directional issue of the electronic resource through the development, test and issue procedures, saving the computer resource, and improving the efficiency of accessing the electronic resource into the service scenario. Meanwhile, when a new service scene is accessed, only the mapping relation between the new service scene and the service rule is required to be set in the configuration file, so that the development cost for the new service scene is reduced.
In a second aspect, embodiments of the present disclosure provide an electronic resource processing method, referring to fig. 4, 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 electronic resources of the target account, and determining target electronic resources applicable to the service scene from the N issued electronic resources based on the scene identification of the service scene, wherein N is a positive integer;
wherein at least one electronic resource of the N issued electronic resources is issued by the method provided in the first aspect.
In this embodiment of the present disclosure, the target account may include an electronic resource issued through the marked electronic resource template, that is, an electronic resource directed to the business scenario. When the target account initiates a target service request, a target electronic resource which is oriented to the service scene can be determined from 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 embodiment of the present disclosure, and will not be described herein again.
In an alternative implementation, the configuration file is created by:
setting one or more business scenes in the configuration file;
for each service scenario, configuring a request parameter value for identifying the service scenario;
and setting one or more business rules in the business scenes aiming at 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, where the determining 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 acquiring N issued electronic 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 the N issued electronic resources includes:
acquiring first scene identifiers marked on M issued electronic resources in the N issued electronic resources and second scene identifiers of service scenes corresponding to the target service requests, wherein M is a positive integer smaller than or equal to N;
And respectively matching each acquired first scene identifier with the second scene identifier, 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 scene identifiers (i.e., electronic resources issued through the marked electronic resource templates), and may also include electronic resources without scene identifiers. In this embodiment, for the marked M electronic resources, a first scene identifier of each electronic resource in the M electronic resources may be obtained, and one-to-one matching is performed with a second scene identifier of the service scene, and the electronic resource successfully matched is taken as the target electronic resource.
For the untagged electronic resource, whether the untagged electronic resource is suitable for the current service scene can be further judged, for example, through the use rule of the untagged electronic resource, and if the use rule of the untagged electronic resource meets the target service request, the untagged electronic resource can also be used as the target electronic resource.
In an optional implementation manner, after determining the target electronic resource applicable to the service scenario from the N issued electronic resources, the method further includes:
and determining available electronic resources applicable to the target service request from the target electronic resources based on the usage rules of the target electronic resources and parameters associated with the usage rules in the target service request.
With respect to the above 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 will not be described in detail herein.
In a third aspect, based on the same inventive concept, an embodiment of the present disclosure provides an electronic resource processing device, referring to fig. 5, including:
the acquiring module 51 is configured to acquire an electronic resource template, where a target business rule is configured in the electronic resource template;
the scene determining module 52 is configured to determine a target service scene corresponding to the target service rule according to a pre-configured configuration file, where the configuration file includes a mapping relationship between the service scene and the service rule;
And 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 electronic resource when the electronic resource is issued by the marked electronic resource template.
In an alternative implementation, the configuration file is created by:
setting one or more business scenes in the configuration file;
for each service scenario, configuring a request parameter value for identifying the service scenario;
and setting one or more business rules in the business scenes aiming at 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 target electronic resources applicable to the 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 issued electronic resource in the N issued electronic resources and a second scene identifier of a service scene corresponding to the target service request;
and respectively matching each acquired first scene identifier with the second scene identifier, 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 applicable to the target service request from the target electronic resources based on the use rules of the target electronic resources and parameters associated with the use rules in the target service request.
With respect to the above 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 described in detail herein.
In a fourth aspect, based on the same inventive concept, an embodiment of the present disclosure provides an electronic resource processing device, please refer to fig. 6, including:
the scene determining module 61 is configured to determine, when a target service request initiated by a target account is detected, a service scene corresponding to the target service request according to a configuration file configured in advance;
the processing module 62 is configured to obtain N issued electronic resources of the target account, determine, based on a scene identifier of the service scene, a target electronic resource applicable to the service scene from the N issued electronic resources, where N is a positive integer;
wherein at least one electronic resource 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 business scenes in the configuration file;
for each service scenario, configuring a request parameter value for identifying the service scenario;
And setting one or more business rules in the business scenes aiming at each business scene so as to establish a mapping relation between the business scenes and the business rules.
In an alternative implementation, the scene 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 electronic resources in the N issued electronic resources and second scene identifiers of service scenes corresponding to the target service requests, wherein M is a positive integer smaller than or equal to N;
and respectively matching each acquired first scene identifier with the second scene identifier, 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 applicable to the target service request from the target electronic resources based on the use rules of the target electronic resources and parameters associated with the use rules in the target service request.
With respect to the above 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 described in detail herein.
In a fifth aspect, based on the same inventive concept as the electronic resource processing method in the foregoing embodiment, the present embodiment further provides 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 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), bus 400 may comprise 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. Bus 400 may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., as are well known in the art and, therefore, will not be described further herein. Bus interface 406 provides an interface between bus 400 and 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 to store 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 having stored thereon a computer program which, when executed by a processor, implements the steps of any of the methods based on the electronic resource processing method as described above.
The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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. It is therefore intended that the following claims be interpreted as including the 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 modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.