CN113283914A

CN113283914A - Virtual asset checking method and device, electronic equipment and storage medium

Info

Publication number: CN113283914A
Application number: CN202010099619.8A
Authority: CN
Inventors: 熊彦儒
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2020-02-18
Filing date: 2020-02-18
Publication date: 2021-08-20

Abstract

The invention discloses a virtual asset checking method and device, electronic equipment and a storage medium, and relates to the technical field of computers. One embodiment of the method comprises: receiving asset information corresponding to a virtual asset to be used, wherein the asset information comprises service information, a use limit type and a parameter set to be verified, and the parameter set to be verified comprises a parameter identifier to be verified and a parameter value of the parameter identifier to be verified; screening a target verification rule corresponding to the asset information according to the use limit type and the service information, wherein the target verification rule comprises a target verification parameter identifier and a parameter value of the target verification parameter identifier; and determining a verification result of the virtual asset according to the parameter set to be verified and the target verification rule. The embodiment can ensure the accuracy of virtual asset use in electronic consumption.

Description

Virtual asset checking method and device, electronic equipment and storage medium

Technical Field

The invention relates to the technical field of computers, in particular to a virtual asset checking method, a virtual asset checking device, electronic equipment and a storage medium.

Background

With the development of network technology, electronic consumption has become a way of daily consumption, and virtual assets, such as electronic coupons, have also been applied more and more widely. However, at present, the types of virtual assets are various, and how to ensure the accuracy of the virtual assets in use becomes an important issue in electronic consumption.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method, an apparatus, a system and a storage medium for checking a virtual asset, which can ensure accuracy of virtual asset usage in electronic consumption.

To achieve the above object, according to an aspect of an embodiment of the present invention, a virtual asset checking method is provided.

The virtual asset checking method provided by the embodiment of the invention comprises the following steps: receiving asset information corresponding to a virtual asset to be used, wherein the asset information comprises service information, a use limit type and a parameter set to be verified, and the parameter set to be verified comprises a parameter identifier to be verified and a parameter value of the parameter identifier to be verified; screening a target verification rule corresponding to the asset information according to the use limit type and the service information, wherein the target verification rule comprises a target verification parameter identifier and a parameter value of the target verification parameter identifier; and determining a verification result of the virtual asset according to the parameter set to be verified and the target verification rule.

In one embodiment, the service information includes a service type and a batch identifier to which the virtual asset belongs;

the screening of the target verification rule corresponding to the asset information according to the usage restriction type and the service information includes:

acquiring a check rule corresponding to the asset information according to the use limit type, the service type and the batch identifier respectively;

and screening the target verification rule according to the set-top state and the last modification time of the verification rule.

In another embodiment, the determining the verification result of the virtual asset according to the parameter set to be verified and the target verification rule includes:

judging whether the number of the parameter identifications to be verified is smaller than that of the target verification parameter identifications;

if yes, determining that the virtual asset can be used;

if not, determining the verification result of the virtual asset according to the parameter value of the parameter identifier to be verified and the parameter value of the target verification parameter identifier.

In yet another embodiment, the target verification rule includes whether a forward parameter;

the determining a verification result of the virtual asset according to the parameter value of the parameter identifier to be verified and the parameter value of the target verification parameter identifier includes:

judging whether the parameter value of the parameter identifier to be verified is matched with the parameter value of the target verification parameter identifier;

if yes, determining that the virtual asset can be used if the forward direction parameter is yes, and otherwise determining that the virtual asset cannot be used;

if not, determining that the virtual asset can not be used if the forward direction parameter is yes, and otherwise determining that the virtual asset can be used if the forward direction parameter is not yes.

In yet another embodiment, the service information includes a service type;

before receiving the asset information corresponding to the virtual asset to be used, the method further comprises the following steps:

establishing a corresponding relation between a verification parameter name and a verification parameter identifier for the service type;

and setting rule information of the check rule for the check rule corresponding to the service type, wherein the rule information comprises use limit information, a check parameter identifier and a parameter value of the check parameter identifier, and the use limit information comprises a use limit type and use limit content.

In another embodiment, after the setting of the rule information of the check rule, the method further includes:

setting a cache identifier of the check rule according to the rule information and a preset format, wherein the cache identifier comprises the service type and the use limit information of the check rule;

and storing the check rule according to the cache identification.

To achieve the above object, according to another aspect of the present invention, there is provided a virtual asset checking apparatus.

The invention relates to a virtual asset checking device, comprising: the system comprises a receiving unit, a verification unit and a verification unit, wherein the receiving unit is used for receiving asset information corresponding to a virtual asset to be used, the asset information comprises service information, a use limit type and a parameter set to be verified, and the parameter set to be verified comprises a parameter identifier to be verified and a parameter value of the parameter identifier to be verified; the screening unit is used for screening a target verification rule corresponding to the asset information according to the use limit type and the service information, wherein the target verification rule comprises a target verification parameter identifier and a parameter value of the target verification parameter identifier; and the determining unit is used for determining the verification result of the virtual asset according to the parameter set to be verified and the target verification rule.

the screening unit is specifically configured to:

In another embodiment, the determining unit is specifically configured to:

if yes, determining that the virtual asset can be used;

the determining unit is specifically configured to:

In yet another embodiment, the service information includes a service type;

the device further comprises:

the establishing unit is used for establishing a corresponding relation between the verification parameter name and the verification parameter identifier for the service type;

and the setting unit is used for setting the rule information of the check rule for the check rule corresponding to the service type, wherein the rule information comprises use limit information, a check parameter identifier and a parameter value of the check parameter identifier, and the use limit information comprises a use limit type and use limit content.

In another embodiment, the setting unit is further configured to set a cache identifier of the check rule according to the rule information and a preset format, where the cache identifier includes a service type and usage restriction information of the check rule;

the device further comprises:

and the storage unit is also used for storing the check rule according to the cache identification.

To achieve the above object, according to still another aspect of an embodiment of the present invention, there is provided an electronic apparatus.

An electronic device of an embodiment of the present invention includes: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the verification method of the virtual assets provided by the embodiment of the invention.

To achieve the above object, according to still another aspect of an embodiment of the present invention, there is provided a computer-readable medium.

A computer-readable medium of an embodiment of the present invention stores thereon a computer program, and when the computer program is executed by a processor, the computer program implements a virtual asset verification method provided by an embodiment of the present invention.

One embodiment of the above invention has the following advantages or benefits: in the embodiment of the invention, the corresponding target verification rule is screened according to the asset limit type and the service information of the virtual asset, so that the virtual asset can be used based on different service scenes and use limit types. In addition, in the embodiment of the invention, the verification parameter identification included in the verification rule can be set in an individualized way, so that the setting of the virtual assets can meet the requirements of individuation and fine granularity in various service scenes.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

FIG. 1 is a schematic diagram of an architecture of a validation system for virtual assets, according to an embodiment of the invention;

FIG. 2 is a schematic diagram of a rule edit page in accordance with an embodiment of the invention;

FIG. 3 is a schematic diagram of one principal flow of a method of verifying a virtual asset according to an embodiment of the invention;

FIG. 4 is a schematic diagram of yet another major flow of a method for verification of a virtual asset according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of the main elements of a validation apparatus for virtual assets, according to an embodiment of the present invention;

FIG. 6 is a diagram of yet another exemplary system architecture to which embodiments of the present invention may be applied;

FIG. 7 is a schematic block diagram of a computer system suitable for use in implementing embodiments of the present invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.

The embodiment of the invention provides a virtual asset checking method, which is used for a scene in which virtual assets are used. Specifically, the virtual asset verification system provided in the embodiment of the present invention implements a virtual asset verification method through the virtual asset verification system. The virtual asset may be an electronic coupon, a coupon, or the like used in a scenario such as network consumption, and the like, in the embodiment of the present invention, the virtual asset is taken as an example for description, and fig. 1 is a schematic diagram of a verification system of a virtual asset in the embodiment of the present invention.

As shown in fig. 1, the verification system for virtual assets includes a management side, a data storage, and an SOA (Service-Oriented Architecture). The management terminal is mainly used for setting and managing the check rule and comprises a service type management module and a rule management module. The business type management is mainly used for maintaining business information and establishing a corresponding relation between the name of the checking parameter and the identification of the checking parameter in different business line types, and the rule management is used for maintaining the checking rule corresponding to each business type. The SOA can be used for providing coupon verification service, a verification interface can be arranged, the verification interface conducts verification and filtering on the coupons according to the verification rules configured by the management end, and the verification results of the coupons are output. The data storage is used for storing the data related to the check rule and the check rule setting. The data storage may include a Mysql database and a cache database, and the cache database may be specifically Redis. The Mysql is a persistent relational database, and the service type related data and the check rule related data configured in the management terminal can be stored in the Mysql and then stored in the Redis. Redis is a high-performance database, the reading speed is high, the stability of the system can be guaranteed, a large number of access requests can be borne, the required check rule can be directly read from Redis when the coupon check is carried out in the SOA, Mysql is accessed to obtain the required check rule when the required check rule does not exist in Redis, and the required check rule is loaded into Redis, so that the performance of the system can be improved. And the problem that a large number of requests for accessing mysql cause the database to be rushed is avoided.

Aiming at the personalized requirements of different service types and in order to better perform data isolation and ensure that the verification rules configured by different service types do not influence each other, in the system in fig. 1, the embodiment of the invention can be provided with a service type management module to manage different service lines and maintain the personalized configurations of different service lines.

Specifically, in the embodiment of the present invention, by setting several fields of the service type number, the service type name, and the service model, the relevant data of the service line corresponding to each service type is managed, which may be specifically shown in table 1.

TABLE 1

Field(s)	Name (R)	Type (B)	Remarks for note
				biz_type	Service type numbering	Int
biz_name	Name of service type	Varchar
				biz_model	Business model	Varchar	Json format

Wherein, the biz _ type field represents the service type number, and the data type is Int; the biz _ name field represents the name of the service type, and the data type is Varchar; the biz _ model represents a service model with a data type of Varchar and a format of Json format. The biz _ type field and the biz _ name field are used for describing service types, and the biz _ model field is used for setting a corresponding relation between a verification parameter name and a verification parameter identifier, namely establishing a corresponding relation between the verification parameter name and the verification parameter identifier for each service model.

The business model may include a plurality of verification parameters, each verification parameter being used to verify the setting of the rule. In the service model, three attributes, namely modelKeySeq, modelKey and modelKeyName, are set for each verification parameter, wherein the modelKeySeq represents a verification parameter identifier, the modelKey represents an English name of the verification parameter, and the modelKeyName represents a Chinese name of the verification parameter. The corresponding relation between the verification parameter identification and the verification parameter name can be established through the three attributes.

For example, taking the service type as the air ticket service as an example, firstly, a service type number is set for the air ticket service, the service type name is the air ticket service, and the service model can be as follows: [ { "model KeySeq": key1"," model Key ": VenderId", "model KeyName": Merchant ID "}, {" model KeySeq ":" key2"," model Key ": AirCode", "model KeyName": navigation master "}, {" model KeySeq ":" key3"," model Key ": AirLine", "model KeyName": AirLine "}, {" model KeySeq ": model KeyName": flight "}, {" model KeyName ": 2", "model KeyKey": model KeyName "}," }.

The merchant ID, the navigation, the airline, the flight and the space are Chinese names of the check parameters, the personalized check parameter names aiming at specific service types, and the corresponding keys 1, 2, 3, 4 and 5 are check parameter identifiers and are generalized identifiers. In the embodiment of the invention, the corresponding relation between the verification parameter identification and the verification parameter name is established through the setting of the service model, and the specific personalized parameter is mapped to the generalized identification so as to facilitate the setting of the inspection rule and the verification of the virtual asset.

Through the service type management, the corresponding relation between the verification parameter identification and the verification parameter name can be established for each service type, and the rule management module can be used for setting the verification rule based on the verification parameter identification.

The rule management module can provide a rule list page and a rule editing page, so that a user can set a verification rule through the rule list page and the rule editing page. The rule list page is used for displaying all the verification rules, and meanwhile, the verification rules can be set to be effective/invalid, set to the top and the like. The rule editing page can comprise two parts, namely basic information setting and personalized information setting, wherein the basic information can comprise rule names, use limit types and forward parameters, and the personalized information comprises parameter value setting of verification parameter identification in the service model. Fig. 2 is a schematic diagram of a rule editing page.

And the rule name in the basic information is the name of the check rule, and the limit type is used for representing the virtual asset to which the check rule is applicable. Since the coupon is usually issued with the usage mode set, the verification rule also needs to set the applicable virtual asset. In the embodiment of the present invention, the usage restriction types may be set to include a full batch, a limited batch, a full class and a limited class, the full batch indicates that the check rule is applicable to all batches of virtual assets, the limited batch indicates that the check rule is applicable to limited batches of virtual assets, the full class indicates that the check rule is applicable to all classes of virtual assets, the limited class indicates that the check rule is applicable to limited classes of virtual assets, in the basic information shown in fig. 2, the limited coupon type indicates the full class and the limited class, when the usage restriction type is set, if the usage restriction type is a limited batch or limited coupon type, a limited batch number or a limited coupon type corresponding identifier needs to be set, and the limited coupon type corresponding identifier generally sets a full class identifier as 1 and a limited class identifier as 2. And whether the forward parameters in the basic information indicate whether the virtual assets matched with the verification rules are available or not. If the forward parameter is yes, the verification result of the virtual asset matched with the verification rule is unusable and needs to be intercepted, and the verification result of the virtual asset not matched with the verification rule is usable; if the forward parameter is not, the verification result of the virtual asset matched with the verification rule is usable, and the verification result of the virtual asset not matched with the verification rule is unusable.

The personalized information is set as parameter value setting of check parameter identification in a service model of a service type to which the check rule belongs, the check parameter identifications included in the service model are mutually independent, logic AND and logic OR combination can be carried out among the check parameter identifications, and each check parameter identification can be provided with a plurality of parameter values. The same service type can be configured with a plurality of different types of check rules, and the same type of check rule can also be configured with a plurality of check rules. The rules may be stored after the rule is checked for settings by the fields shown in table 2.

TABLE 2

In table 2, biz _ type indicates a service type number of a service type to which the check rule belongs, rule _ key indicates personalization information of the set check rule, status indicates whether the check rule is in an effective state, relationship _ type indicates a usage restriction type of the check rule, relationship _ data indicates a corresponding restricted content when the relationship _ type is a restricted lot or a restricted coupon type, and top _ status indicates whether the check rule is in an execution state.

The rule _ key of the check rule is personalized information of the check rule, and the specific mode can be that, for each check parameter in the service model of the service type to which the check rule belongs, two attributes of relationship and value are added in addition to the three attributes of modelKeySeq, modelKey and modelKeyName included in the service model. The relationship is used for representing the logical relationship between the verification parameter and other verification parameters, and represents "and" when the value is 1, and represents "or" when the value is 2. value is a specific value set by a user for the verification parameter, and the specific value is a plurality of values, so that the step of dividing is performed.

For example, taking the air ticket service as an example, the rule _ key example data set is as follows:

[ { "modelKey": VenderId "," modelKeyName ": Merchant ID", "modelKeySeq": key1"," relationship ": 1", "value": 1001,1002"}, {" modelKey ": "AirCode", "model KeyName": "navigation", model KeySeq ":" key2"," relationship ":2," value ":" AAA, BBB "}, {" model Key ":" AirLine "," model KeyName ":" lane "," model KeySeq ":" key3"," relationship ":1," value ":" AirLine01, AirLine02"}, {" model KeyName ":" model KeySeq ":" key4"," relationship ":2," value ": F1001, F1002" }, { "model Key": "model KeyName": "key bit 5": model KeySeq ": model KeySealq": 1 ".

In the above example, the parameter values for key1 are: the logical relationship with other verification parameters is and, the specific values are 1001, 1002; the parameter values for key2 are: the logic relation with other checking parameters is or, the specific value is AAA, BBB; the parameter values for key3 are: the logic relation with other checking parameters is and, the specific value is AirLine01, AirLine 02; the parameter values for key4 are: the logical relationship with other checking parameters is OR, and the specific values are F1001 and F1002; the parameter values for key5 are: the logical relationship with other verification parameters is and the specific value is null.

The check rules need to be stored in the database after being set, each check rule can be stored in a rule type of the check rule, and each rule type can correspond to a plurality of check rules.

Because the rules stored in the cache database are used for verifying the virtual assets, and when the virtual assets are required to be verified, one verification rule with the highest priority is screened from the verification rules matched with the rules to be verified, so that in order to reduce the data volume stored in the cache database, only one verification rule with the highest priority can be stored in the cache database for each rule type.

In the cache database, the manner that the cache key represents the rule type may be used in various ways, for example, the rule id may be used as the cache key for checking rule query, and a combination of a service type, a usage restriction type, and the like may also be used as the cache key, so as to facilitate quick query of the checking rule meeting the specified condition during virtual asset checking.

Specifically, in the embodiment of the present invention, a service type, a usage restriction type, a batch number, and an identifier combination manner of a coupon type may be used as a cache key, and as shown in table 3, the cache key is in a cache key format.

TABLE 3

In the cache key format of table 3, rule _ batch id represents a check rule for a batch number; rule _ type represents a check rule for a class of items; bizType is the service type number to which the check rule belongs, for example, 35; the batch Id represents a batch number corresponding to the check rule, if the usage limit type of the check rule is a limited batch, the batch Id is the limited batch number (for example, 173048150), and if the usage limit type of the check rule is a full batch, the batch Id is all, which represents all the batches; the limiType represents a limited coupon type identifier corresponding to the verification rule, if the usage limit type of the verification rule is a full type, the limiType is 1, and if the usage limit type of the verification rule is a limited type, the limiType is 2.

Taking the cache key format shown in table 3 as an example, multiple check rules may exist for each cache key, and at this time, in order to reduce the number stored in the cache database, the highest check rule of the priority level corresponding to each cache key may be stored in the cache database. In the embodiment of the invention, the priority of the check rule is determined by the set-top state and the last modification time, so that for the check rule corresponding to each cache key, if the check rule in the set-top state exists, the check rule in the set-top state and the last modification time is taken as the check rule with the highest priority corresponding to the cache key; and if the verification rule in the set-top state does not exist, taking the verification rule with the maximum modification time as the verification rule with the highest priority corresponding to the cache key. And then storing each caching key and the check rule with the highest priority corresponding to the caching key in a caching database.

The management end usually has operations of adding, modifying, setting to take effect or fail, setting to set top or canceling top for the check rule, and because these operations will affect the priority of the check rule, after the check rule is subjected to the above operations each time, not only the operation information needs to be updated to the database, but also the operation information needs to be subjected to priority comparison with the check rule of the cache key corresponding to the operated check rule stored in the cache database. And if the cache key corresponding to the operated check rule is called a target cache key, the cache rule corresponding to the target cache key stored in the cache is the check rule with the highest priority corresponding to the target cache key before the operation is executed, and after the operation is executed, the priority between the check rule corresponding to the target cache key stored in the cache and the operated check rule is judged again. If the priority of the check rule which is stored in the cache and corresponds to the target cache key is higher than the operated check rule, keeping the data in the cache unchanged; and if the priority of the check rule stored in the cache and corresponding to the target cache key is lower than the operated check rule, updating the check rule in the cache and corresponding to the target cache key into the operated check rule.

Through the process, a verification system of the virtual assets can be established and operated, and the SOA can be used for verifying the virtual assets so as to determine whether the virtual assets can be used.

An embodiment of the present invention provides a virtual asset verification method, which may be executed by an SOA in a system architecture shown in fig. 1, as shown in fig. 3, and includes the following steps.

S301: and receiving asset information corresponding to the virtual assets to be used.

The asset information comprises service information, a use limit type and a parameter set to be verified, wherein the parameter set to be verified comprises a parameter identifier to be verified and a parameter value of the parameter identifier to be verified.

In the embodiment of the present invention, the usage restriction types include a limited batch, a full class, and a limited class, and when the usage restriction types are a limited batch and a full batch, the asset information may not include the usage restriction types. The service information includes a service type to which the virtual asset belongs and a batch identifier, and the batch identifier may be a batch number. The identification of the parameter to be verified in the parameter set to be verified is a verification parameter identification included in the service model of the service type to which the virtual asset belongs, and the parameter value of the parameter identification to be verified is a parameter value when the parameter identification to be verified corresponds to the virtual asset.

For example, taking the virtual asset as a coupon as an example, the specific content of the asset information can be as shown in table 4.

TABLE 4

In table 4, bizType indicates a service class code of a service type to which the virtual asset belongs. The modelKeyMap represents a parameter set to be verified, where the parameter to be verified may be in a key-value format, the key is a parameter identifier to be verified, that is, a verification parameter identifier in a service model of a service type to which the virtual asset belongs, and the value is a parameter value of the parameter identifier to be verified. The couponInfoSet represents specific coupon information for the virtual asset and may include three parameters, batchId, count, and limitType, respectively. batchId represents the batch number of the virtual asset, and the type is Int; discount represents the preferential amount of the virtual asset, and the type is BigDecimal; the limitType is a checking limitation type of the virtual asset, the type is Int, and the specific value can be a full class or a limit class.

The virtual assets to be used may include a plurality of virtual assets, and since the virtual assets are all used for the same product or service and belong to the same service type, the modelKeyMap is the same, but the couponInfoSet is different, so the couponInfoSet may include coupon information of the plurality of virtual assets.

It should be noted that, after the interface of the SOA receives the call request, the library first performs non-empty check of the interface entry parameter, and if the interface entry parameter has an empty parameter, the failure may be directly returned.

S302: and screening a target verification rule corresponding to the asset information according to the use limit type and the service information.

The target verification rule comprises a target verification parameter identifier and a parameter value of the target verification parameter identifier.

The database may store a plurality of verification rules corresponding to the usage restriction types and the service information, and in this step, one verification rule needs to be screened out as a target verification rule to verify the virtual asset, and usually the selected verification rule with the highest priority is the most target verification rule. The personalized information of each check rule is provided with a check parameter identifier and a parameter value of the check parameter identifier, so that the check parameter identifier in the target check rule can be used as the target check parameter identifier, and the parameter value of the check parameter identifier in the target check rule can be used as the parameter value of the target check parameter identifier.

In an implementation manner of the embodiment of the present invention, the service information includes a service type and a batch identifier. Then, in this step, according to the service type, the limited number, the limited coupon type, and the limited use type of the whole batch are combined, the corresponding check rule is obtained from the buffer database, and then the check rule with the high priority is screened as the target check rule. If the verification rule is not acquired from the cache database, the default verification is passed, and the virtual asset can be used.

Specifically, this step may be specifically executed as: acquiring a verification rule corresponding to the asset information according to the use limit type, the service type and the batch identifier; and screening the target verification rule according to the top setting state and the final modification time of the verification rule corresponding to the asset information.

And in this step, the check rule corresponding to the asset information can be obtained according to the use limit type, the service type and the batch identifier, and then the target check rule with the highest priority is screened out according to the set-top state and the final modification time of the check rule.

For example, taking the case that the verification rule is stored in the cache database according to the cache key format shown in table 3 as an example, according to the service type of the virtual asset, the rule type may be determined to be the service type — full batch of cache keys, and then the verification rule corresponding to the cache key is obtained; according to the service type and the batch number of the virtual asset, the cache key with the rule type of service type _ limited batch can be determined, and a check rule corresponding to the cache key is further obtained; if the verification limit type of the virtual asset is the limit coupon type, according to the service type and the use limit type of the virtual asset, the cache key of which the rule type is the service type _ full class and/or the service type _ limit class can be determined, and the verification rule corresponding to the cache key is further obtained; if the verification limit type of the virtual asset is limited batch or full batch, according to the service type of the virtual asset, the rule types can be determined to be the service type _ full class and the service type _ limited class, and then the verification rule corresponding to the cache key is obtained.

After various verification rules are obtained in the above mode, the target verification rule with the highest priority is screened out according to the set-top state and the last modification time of the obtained verification rules.

It should be noted that, if the check rule corresponding to the asset information, which is obtained according to the usage restriction type, the service type, and the batch identifier, is empty, that is, there is no check rule corresponding to the asset information, it may be directly determined that the check result of the virtual asset is usable.

S303: and determining a verification result of the virtual asset according to the parameter set to be verified and the target verification rule.

After the target verification rule is determined, the parameter value of the parameter identifier to be verified in the parameter set to be verified can be matched with the parameter value of the target verification parameter identifier in the parameter set to be verified of the target verification rule. And then determining a verification result of the virtual asset according to the matching result.

After the verification result of the virtual asset is determined, the result may be returned. The return parameter may be set to checkResult, and the type is HashMap < String, Boolean >, and the format may be key-value format, the key is batchId, that is, the batch number of the virtual asset, and the value is the check result. In the embodiment of the invention, the checking result can be true or false, true represents that the virtual asset can be used, and false represents that the virtual asset cannot be used. If the number of the virtual assets is multiple, whether the virtual assets can be used or not can be sequentially returned according to the batch number.

In the embodiment of the invention, the corresponding target verification rule is screened according to the asset limit type and the service information of the virtual asset, so that the virtual asset can be set and used based on different service scenes and use limit types. In addition, in the embodiment of the invention, the verification parameter identification included in the verification rule can be set in an individualized way, so that the virtual asset can meet the individualized requirements in various service scenes.

Step S303 in the embodiment of the present invention is specifically described below with reference to the system architecture shown in fig. 1 and the embodiment shown in fig. 3, taking the verification result as an example of whether the verification result is usable or unusable. As shown in fig. 4, the method includes the following steps.

S401: judging whether the number of the parameter identifications to be verified is smaller than that of the target verification parameter identifications, if not, executing a step S402; if so, the virtual asset may be used.

Under normal conditions, the number of the parameter identifications to be verified is the same as that of the target verification parameter identifications, and when the number of the parameter identifications to be verified is smaller than that of the target verification parameter identifications, the received data is incomplete, an accurate verification result cannot be obtained for the virtual assets, so that the virtual assets can be directly defaulted to use. If the number of the to-be-verified parameter identifications is not less than the number of the target verification parameter identifications, step S402 may be performed.

Specifically, the step is to compare whether the number of keys included in the modelKeyMap of the asset information is smaller than the number of keys in the rule _ key parameter of the target check rule, if so, the received data is incomplete, and the virtual asset can be used by default.

S402: judging whether the parameter value of the parameter identifier to be verified is matched with the parameter value of the target verification parameter identifier, if not, executing the step S403; if yes, go to step S404.

And judging whether the parameter value of the parameter identifier to be verified is matched with the parameter value of the target verification parameter identifier, namely, whether the value corresponding to the key in the modelKeyMap of the asset information is matched with the value corresponding to the same key in the rule _ key parameter of the target verification rule.

In this step, the parameter value and the name of the parameter identifier to be verified are sequentially compared with the parameter value of the target verification parameter identifier having the same parameter identifier to be verified. And if the parameter values and the names of all the parameter identifications to be verified are matched with the parameter values of the target verification parameter identifications with the same names of the parameter identifications to be verified, determining that the parameter values of the parameter identifications to be verified are matched with the parameter values of the target verification parameter identifications, and otherwise, determining that the parameter values of the parameter identifications to be verified are not matched with the parameter values of the target verification parameter identifications.

The specific manner may be that the parameter value of the target verification parameter identifier includes a logical relationship and a specific value, and the logical relationship represents a logical relationship between the target verification parameter and another target verification parameter. The logical relationship includes "and" or ", and the target verification parameters can be divided into" and "or" types according to the logical relationship.

For the 'and' type target verification parameters, if the parameter value of one parameter identifier to be verified is different from the value of the target verification parameter identifier with the same name, determining that the parameter value of the parameter identifier to be verified is not matched with the parameter value of the target verification parameter identifier for the 'and' type target verification parameters; and if the parameter values of all the parameter identifications to be verified are the same as the values of the target verification parameter identifications with the same names, determining that the parameter values of the parameter identifications to be verified are matched with the parameter values of the target verification parameter identifications for the 'and' type target verification parameters.

That is to say, for a "and" type of key, if there is a key whose value corresponding to modelKeyMap is not the same as the value corresponding to rule _ key parameter of the target verification rule, it is determined that the parameter value identified by the parameter to be verified is not matched with the parameter value identified by the target verification parameter, and it is further determined that the result of this step is not matched; if the values of all keys in the modelKeyMap are the same as the values corresponding to the rule _ key parameter of the target verification rule, confirming that the parameter value identified by the parameter to be verified is not matched with the parameter value identified by the target verification parameter, and further determining that the result of the step is matched.

For the target verification parameters of the type "or", if the parameter value of one parameter identifier to be verified is the same as the value of the target verification parameter identifier with the same name, determining that the parameter value of the parameter identifier to be verified is matched with the parameter value of the target verification parameter identifier for the target verification parameters of the type "or"; and if the parameter values of all the parameter identifications to be verified are different from the values of the target verification parameter identifications with the same names, determining that the parameter values of the parameter identifications to be verified are not matched with the parameter values of the target verification parameter identifications for the target verification parameters of the type of OR.

For the or type of key, if a value of the key corresponding to the modelKeyMap is the same as a value corresponding to the rule _ key parameter of the target verification rule, determining that the parameter value of the parameter identifier to be verified is matched with the parameter value of the target verification parameter identifier; and if the values of all keys in the modelKeyMap are different from the values corresponding to the rule _ key parameters of the target verification rule, determining that the parameter value identified by the parameter to be verified is not matched with the parameter value identified by the target verification parameter.

If the judgment result of the target verification parameter of the OR type is matching and the judgment result of the target verification parameter of the OR type is matching, judging that the judgment result is matching; if the judgment result of the target verification parameter of the or type is not matched, or the judgment result of the target verification parameter of the or type is not matched, the judgment result of the step is not matched.

S403: judging whether the forward parameter is yes or not, and if not, the virtual asset cannot be used; if so, the virtual asset may be used.

After determining that the parameter value identified by the parameter to be verified is not matched with the parameter value identified by the target verification parameter, determining whether the virtual asset can be used by combining with whether the forward parameter is available.

If the forward parameter is yes, determining that the parameter value of the parameter identifier to be verified is not matched with the parameter value of the target verification parameter identifier, which means that the virtual asset can be used, namely, the result is true; and if the forward parameter is not, determining that the parameter value of the parameter identifier to be verified is not matched with the parameter value of the target verification parameter identifier, which means that the virtual asset cannot be used, namely, the result is false.

S404: judging whether the forward parameter is yes or not, and if not, enabling the virtual asset to be used; if so, the virtual asset may not be used.

After determining that the parameter value of the parameter identifier to be verified is matched with the parameter value of the target verification parameter identifier, determining whether the virtual asset can be used by combining with whether the forward parameter is available.

If the forward parameter is yes, determining that the parameter value of the parameter identifier to be verified and the parameter value of the target verification parameter identifier are matched to indicate that the virtual asset cannot be used, namely, the result is false; and if the forward parameter is not, determining that the parameter value of the parameter identifier to be checked and the parameter value of the target check parameter identifier are matched to indicate that the virtual asset can be used, namely, the result is true.

Through the process of the embodiment of the invention, whether the virtual assets can be used or not can be judged to obtain the judgment result.

In order to solve the problems in the prior art, an embodiment of the present invention provides an apparatus 500 for verifying a virtual asset, as shown in fig. 5, where the apparatus 500 includes:

a receiving unit 501, configured to receive asset information corresponding to a virtual asset to be used, where the asset information includes service information, a usage restriction type, and a parameter set to be verified, and the parameter set to be verified includes a parameter identifier to be verified and a parameter value of the parameter identifier to be verified;

a screening unit 502, configured to screen a target verification rule corresponding to the asset information according to the usage restriction type and the service information, where the target verification rule includes a target verification parameter identifier and a parameter value of the target verification parameter identifier;

a determining unit 503, configured to determine a verification result of the virtual asset according to the parameter set to be verified and the target verification rule.

It should be understood that the manner of implementing the embodiment of the present invention is the same as the manner of implementing the embodiment shown in fig. 2, and the description thereof is omitted.

In an implementation manner of the embodiment of the present invention, the service information includes a service type and a batch identifier to which the virtual asset belongs;

the screening unit 502 is specifically configured to:

In another implementation manner of the embodiment of the present invention, the determining unit 503 is specifically configured to:

if yes, determining that the virtual asset can be used;

In another implementation manner of the embodiment of the present invention, the target verification rule includes whether a forward parameter is included;

the determining unit 503 is specifically configured to:

In another implementation manner of the embodiment of the present invention, the service information includes a service type;

the apparatus 500 further comprises:

In another implementation manner of the embodiment of the present invention, the setting unit is further configured to set a cache identifier of the check rule according to the rule information and a preset format, where the cache identifier includes a service type and usage restriction information of the check rule;

the apparatus 500 further comprises:

The invention also provides an electronic device and a readable storage medium according to the embodiment of the invention.

The electronic device of the present invention includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform a method for verifying a virtual asset provided by an embodiment of the present invention.

Fig. 6 illustrates an exemplary system architecture 600 of a virtual asset validation method or virtual asset validation apparatus to which embodiments of the present invention may be applied.

As shown in fig. 6, the system architecture 600 may include

terminal devices

601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the

terminal devices

601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

A user may use the

terminal devices

601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. The

terminal devices

601, 602, 603 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The

terminal devices

601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the

terminal devices

601, 602, 603. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, product information — just an example) to the terminal device.

It should be noted that the verification method for the virtual asset provided by the embodiment of the present invention is generally executed by the server 605, and accordingly, the verification device for the virtual asset is generally disposed in the server 605.

It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 7, a block diagram of a computer system 700 suitable for use in implementing embodiments of the present invention is shown. The computer system illustrated in FIG. 7 is only an example and should not impose any limitations on the scope of use or functionality of embodiments of the invention.

As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a unit, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present invention may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a receiving unit, a screening unit, and a determining unit. Where the names of these elements do not in some cases constitute a limitation of the element itself, for example, a receiving element may also be described as "an element of the function of the receiving element".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to perform the method for verifying a virtual asset provided by the present invention.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for verifying a virtual asset, comprising:

receiving asset information corresponding to a virtual asset to be used, wherein the asset information comprises service information, a use limit type and a parameter set to be verified, and the parameter set to be verified comprises a parameter identifier to be verified and a parameter value of the parameter identifier to be verified;

screening a target verification rule corresponding to the asset information according to the use limit type and the service information, wherein the target verification rule comprises a target verification parameter identifier and a parameter value of the target verification parameter identifier;

and determining a verification result of the virtual asset according to the parameter set to be verified and the target verification rule.

2. The method of claim 1, wherein the service information comprises a service type and a batch identifier to which the virtual asset belongs;

3. The method according to claim 1, wherein the determining the verification result of the virtual asset according to the parameter set to be verified and the target verification rule comprises:

if yes, determining that the virtual asset can be used;

4. The method of claim 3, wherein the target verification rule includes whether a forward parameter;

5. The method of claim 1, wherein the traffic information comprises a traffic type;

6. The method according to claim 5, wherein after the setting of the rule information of the check rule, the method comprises:

and storing the check rule according to the cache identification.

7. A virtual asset verification apparatus, comprising:

the system comprises a receiving unit, a verification unit and a verification unit, wherein the receiving unit is used for receiving asset information corresponding to a virtual asset to be used, the asset information comprises service information, a use limit type and a parameter set to be verified, and the parameter set to be verified comprises a parameter identifier to be verified and a parameter value of the parameter identifier to be verified;

the screening unit is used for screening a target verification rule corresponding to the asset information according to the use limit type and the service information, wherein the target verification rule comprises a target verification parameter identifier and a parameter value of the target verification parameter identifier;

and the determining unit is used for determining the verification result of the virtual asset according to the parameter set to be verified and the target verification rule.

8. The apparatus according to claim 7, wherein the service information includes a service type and a lot identifier to which the virtual asset belongs;

the screening unit is specifically configured to:

9. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-6.

10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.