A method, device, equipment and storage medium for verifying the mixed placement of objects

Abstract

An embodiment of the present invention discloses a method, device, equipment and storage medium for verifying the mixed placement of objects. The method includes: when a verification request for the mixed placement of objects is detected, identifying a service identifier corresponding to the verification request; if a target identifier corresponding to the service identifier exists in each of the configured identifiers that have been configured, obtaining a verification rule for the mixed placement of objects that has been configured and corresponds to the target identifier, including corresponding verification relationships and verification metadata; for the object to be verified and the objects that have been placed corresponding to the verification request, respectively identifying a first metadata value corresponding to the verification metadata of the object to be verified and a second metadata value corresponding to the verification metadata of the objects that have been placed; verifying the first metadata value and the second metadata value based on the verification relationship to determine whether to mix the object to be verified and the objects that have been placed. The technical solution of the embodiment of the present invention can respond to changes in verification requirements through automatically configured verification rules, and the research and development cost is relatively low.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer technology, and in particular, to a method, apparatus, device, and storage medium for verifying the mixed placement of objects. Background Art

[0002] A container is a core concept in the production process of a Warehouse Management System (WMS). It can be understood as a device for holding goods, such as pallets, turnover boxes, etc., and is applied in multiple links such as inbound inspection, in-warehouse transfer and relocation, and outbound picking.

[0003] In practical applications, the WMS needs to verify whether a certain good can be placed in a certain container, that is, to verify whether a certain good can be mixed with the goods already placed in a certain container, and then determine whether to continue the operation or replace the container according to the verification result. Most of the current in-warehouse verifications are implemented in the form of hard coding, which develops customized verification logics for different verification requirements.

[0004] In the process of implementing the present invention, the inventors found the following technical problems in the prior art: If the verification requirements change, at this time, developers need to manually modify the code. This implementation method of coping with the change of verification requirements through secondary development has a relatively high R & D cost. Summary of the Invention

[0005] The embodiments of the present invention provide a method, apparatus, device, and storage medium for verifying the mixed placement of objects, which solves the problem of relatively high R & D costs caused by coping with the change of verification requirements through secondary development.

[0006] In a first aspect, the embodiments of the present invention provide a method for verifying the mixed placement of objects, which may include:

[0007] When detecting a verification request for the mixed placement of objects, identify the service identifier corresponding to the verification request. If there is a target identifier corresponding to the service identifier among the configured identifiers that have been configured, obtain the configured verification rule for the mixed placement of objects corresponding to the target identifier. The verification rule includes verification metadata and a verification relationship, and the verification relationship corresponds to the verification metadata;

[0008] For the object to be verified and the objects already placed corresponding to the verification request, respectively identify the first metadata value corresponding to the verification metadata of the object to be verified and the second metadata value corresponding to the verification metadata of the objects already placed;

[0009] Verify the first metadata value and the second metadata value based on the verification relationship, and determine whether to mix the object to be verified and the objects already placed according to the verification result.

[0010] Optionally, identify the service identifier corresponding to the verification request, which may include:

[0011] Identify the service identifier key in the verification request and obtain the context corresponding to the verification request;

[0012] Send the service identifier key and the context to the reflector so that the reflector reflects the service identifier value corresponding to the service identifier key from the context;

[0013] Use the service identifier key and the service identifier value as the service identifier corresponding to the verification request.

[0014] On this basis, the above verification method for mixed placement of objects may further include:

[0015] Identify the configured identifier keys of each configured identifier from the service identifier center;

[0016] Send the configured identifier key and the context to the reflector so that the reflector reflects the configured identifier value corresponding to the configured identifier key from the context;

[0017] For the target identifier key corresponding to the service identifier key among the configured identifier keys, obtain the target identifier value corresponding to the target identifier key from each configured identifier value;

[0018] Compare the target identifier value with the service identifier value, and determine whether the configured identifier including the target identifier key and the target identifier value is the target identifier according to the comparison result.

[0019] Optionally, after obtaining the configured verification rule for mixed placement of objects corresponding to the target identifier, the above verification method for mixed placement of objects may further include:

[0020] Parse the verification rule to obtain abstract elements representing the verification logic for mixed placement of objects, where the abstract elements include verification metadata;

[0021] Identify the first metadata value of the object to be verified corresponding to the verification metadata, which may include:

[0022] Send the verification metadata and the context to the reflector so that the reflector reflects the first metadata value of the object to be verified corresponding to the verification metadata from the context.

[0023] On this basis, optionally, the abstract elements further include prompt information indicating the failure of mixed placement of objects, and the above verification method for mixed placement of objects may further include:

[0024] If it is determined according to the verification result that the object to be verified and the placed object cannot be mixed, give a prompt based on the prompt information.

[0025] Optionally, validating the first metadata value and the second metadata value based on a validation relationship may include:

[0026] Obtain a validator that matches the validation relationship;

[0027] If the validator includes an equivalence validator, validate whether the first metadata value and the second metadata value are equal based on the equivalence validator; and / or,

[0028] If the validator includes a non-equivalence validator, validate whether the first metadata value and the second metadata value are not equal based on the non-equivalence validator.

[0029] Optionally, the above method for validating object mixing may further include:

[0030] When a configuration request for a validation rule is detected, obtain a to-be-configured identifier and to-be-configured rule details from the configuration request, parse the to-be-configured rule details to obtain to-be-configured validation metadata and a to-be-configured validation relationship, and use the to-be-configured identifier, the to-be-configured validation metadata, and the to-be-configured validation relationship as to-be-configured rule information;

[0031] Configure the validation rule corresponding to the to-be-configured identifier based on the to-be-configured rule information.

[0032] On this basis, optionally, configuring the validation rule corresponding to the to-be-configured identifier based on the to-be-configured rule information may include:

[0033] Obtain a rule configuration method corresponding to the configuration request;

[0034] If the rule configuration method includes a performance priority method, cache the to-be-configured rule information, and configure the validation rule corresponding to the to-be-configured identifier based on the cached to-be-configured rule information at a preset time point; and / or,

[0035] If the rule configuration method includes a real-time priority method, configure the validation rule corresponding to the to-be-configured identifier based on the to-be-configured rule information at the current time point.

[0036] In a second aspect, an embodiment of the present invention further provides a validation device for object mixing, which may include:

[0037] A validation rule acquisition module, configured to, when a validation request for object mixing is detected, identify a service identifier corresponding to the validation request, and if there is a target identifier corresponding to the service identifier among the configured identifiers that have been configured, obtain the configured validation rule for object mixing corresponding to the target identifier, where the validation rule includes validation metadata and a validation relationship, and the validation relationship corresponds to the validation metadata;

[0038] A metadata value identification module, configured to respectively identify a first metadata value corresponding to the verification metadata of the object to be verified and a second metadata value corresponding to the verification metadata of the placed object, for the object to be verified and the placed object corresponding to the verification request;

[0039] An object mixed placement verification module, configured to verify the first metadata value and the second metadata value based on a verification relationship, and determine whether to mix the object to be verified and the placed object according to the verification result.

[0040] In a third aspect, an embodiment of the present invention further provides a verification device for object mixed placement, which may include:

[0041] One or more processors;

[0042] A memory, configured to store one or more programs;

[0043] When the one or more programs are executed by the one or more processors, the one or more processors implement the object mixed placement verification method provided by any embodiment of the present invention.

[0044] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the object mixed placement verification method provided by any embodiment of the present invention is implemented.

[0045] In the technical solution of the embodiment of the present invention, by identifying the service identifier corresponding to the verification request mixed with the detected object, it can be determined whether there is a target identifier corresponding to the service identifier among the configured identifiers that have been configured. If so, it indicates that there is a configured verification rule for object mixing that can implement the verification request of the business party to which the service identifier belongs. Obtain the verification rule, which can be a rule obtained by abstracting the verification logic corresponding to the verification requirements of the business party, and it can reflect the service identifier, verification metadata, and verification relationship. Among them, the verification metadata and verification relationship can be understood as an abstract representation of the verification logic; for the object to be verified and the placed object corresponding to the verification request, the first metadata value corresponding to the verification metadata of the object to be verified and the second metadata value corresponding to the verification metadata of the placed object can be respectively identified; since the verification relationship can represent the numerical relationship between the first metadata value and the second metadata value when the object to be verified and the placed object can or cannot be mixed, the two metadata values can be verified based on the verification relationship, and it can be determined whether the two objects can be mixed according to the verification result. In the above technical solution, the mixing verification is performed through the configured verification rule of the business party to which the object to be verified belongs. Since the verification rule can reflect the abstract verification logic through the verification metadata and the verification relationship, when the verification logic changes, the verification device can directly abstract the verification logic to obtain the changed verification rule without the need for R & D personnel to perform secondary development, thereby achieving the effect of reducing the R & D cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 is a flowchart of a method for verifying object mixing in an embodiment of the present invention;

[0047] Figure 2 is a flowchart of another method for verifying object mixing in an embodiment of the present invention;

[0048] Figure 3 is a flowchart of still another method for verifying object mixing in an embodiment of the present invention;

[0049] Figure 4 is a schematic diagram of a configuration center in still another method for verifying object mixing in an embodiment of the present invention;

[0050] Figure 5 is a flowchart of an optional example in still another method for verifying object mixing in an embodiment of the present invention;

[0051] Figure 6 is a schematic diagram of a verification rule in still another method for verifying object mixing in an embodiment of the present invention;

[0052] Figure 7It is a structural block diagram of a verification device for object mixed placement in an embodiment of the present invention;

[0053] Figure 8 It is a structural schematic diagram of a verification device for object mixed placement in an embodiment of the present invention. Specific implementation manners

[0054] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present invention, rather than limiting the present invention. Additionally, it should be noted that for the sake of description, only parts related to the present invention are shown in the accompanying drawings, rather than all the structures.

[0055] Before introducing the embodiments of the present invention, an exemplary description of the application scenarios of the embodiments of the present invention will be given: Continuing with the container described in the background art, there is a verification logic for whether goods of different document types, different stock keeping units (SKUs), etc. can be mixed in the same container. However, the actual requirements of different merchants for this verification logic are not unified. For example: different document types cannot be mixed, different owners cannot be mixed, different suppliers cannot be mixed, etc. Moreover, the actual requirements of the same merchant may also change frequently. For example: the merchant requires this time that goods of different owners cannot be mixed, and after a period of time, it requires again that documents of different suppliers cannot be mixed.

[0056] On this basis, if it is implemented in the hard - coded form described above, it means that if the actual requirements (i.e., verification requirements) of the merchant change, at this time, developers need to manually modify the code. This modification process can be understood as adding new code to deal with newly added verification logic, modifying the original code to deal with newly modified verification logic, deleting the original code to deal with newly deleted verification logic, etc. Obviously, in addition to the problem of relatively high R & D costs brought by secondary development, the above - mentioned implementation scheme may also have the following problems: First, in order to implement the latest verification logic, it requires a very long life cycle: raising requirements, review, design, development, testing, verification, going live, etc., which is time - consuming and laborious. Moreover, after several versions of iteration, the system becomes more and more cumbersome, and at the same time, the cost of change is getting higher and higher, and the difficulty is getting greater. Second, the code for different application scenarios such as *** storage locations / areas / lanes cannot be mixed, *** cannot merge documents, etc. is written in their respective application scenarios. This is inflexible for the business level, has no extensibility for the system level, and customers cannot actively select and configure the corresponding verification logic, and is passive and cumbersome for the verification method of the operating system.

[0057] Figure 1It is a flowchart of a method for verifying the mixed placement of objects provided in an embodiment of the present invention. This embodiment is applicable to the situation of verifying whether two certain objects can be mixed and placed together, especially applicable to the situation of verifying whether two objects that can be verified by the configured verification rules for mixed placement of objects can be mixed and placed together based on the configured verification rules for mixed placement of objects. This method can be executed by the verification device for mixed placement of objects provided in the embodiment of the present invention. The verification device can be implemented in software and / or hardware, and the verification device can be integrated on the verification device for mixed placement of objects. The verification device can be various user terminals or servers.

[0058] See Figure 1 , the method of the embodiment of the present invention specifically includes the following steps:

[0059] S110. When a verification request for mixed placement of objects is detected, identify the service identifier corresponding to the verification request. If there is a target identifier corresponding to the service identifier among the configured identifiers, obtain the configured verification rule for mixed placement of objects corresponding to the target identifier. The verification rule includes verification metadata and a verification relationship, and the verification relationship corresponds to the verification metadata.

[0060] Among them, the verification request can be a request to verify whether a certain object to be verified can be mixed and placed together with the placed object already placed in a certain target, that is, a request to verify whether the object to be verified and the placed object can be placed in the target at the same time. On this basis, the objects mentioned above can be physical objects such as goods and commodities, or virtual objects such as currency and documents, which are not specifically limited here; the targets mentioned above can be storage locations, areas, aisles, documents, etc. There are various possible triggering methods for the verification request, such as being triggered when a goods receiver scans a certain good into a certain container, being triggered when a currency input operator inputs a certain currency amount onto a certain document, etc., which are not specifically limited here.

[0061] Since each object to be verified comes from a certain business party. For example, a certain good comes from a certain merchant, a certain monetary amount comes from a certain enterprise, etc. Therefore, when a verification request is detected, the business identifier corresponding to the verification request can be identified, that is, the business identifier of the business party to which the object to be verified corresponding to the verification request belongs. This business identifier can be understood as an identifier that can identify the identity of business data (such as the object to be verified, the business party to which the object to be verified belongs), and it can also be simply referred to as business identity. In practical applications, optionally, this business identifier can be an identifier of business identities such as warehouse, consignor, document type, etc. The consignor can be understood as the owner of a certain good, such as a manufacturer, a supplier, a distributor, etc. It should be noted that business parties with different business identifiers may set the same or different verification logics. The above verification device can abstract these verification logics and configure them as verification rules. The specific verification logic can be reflected in the rule details in the verification rules. Exemplarily, referring to Table 1 below, a business identifier is uniquely determined by a warehouse, a consignor, and a document type. The rule details are the verification logics set by the business party with the corresponding business identifier.

[0062] Table 1 Binding of Business Identifier and Rule Details

[0063]

[0064]

[0065] On this basis, the configured identifier can be a configured business identifier, that is, a verification rule corresponding to this business identifier is configured in the verification device. Therefore, after identifying the business identifier corresponding to the verification request, it can first be determined whether there is a target identifier corresponding to this business identifier among the configured identifiers, such as a target identifier that is the same as or similar to this business identifier. If it exists, it means that there is a configured verification rule in the verification device that can implement this verification request, and thus the verification rule corresponding to this target identifier can be obtained. It should be noted that the verification rule can include verification metadata and verification relationships. Among them, the verification relationship can be a relationship used to verify each metadata value under the verification metadata, that is, the verification relationship corresponds to the verification metadata. The meanings of the verification metadata and the verification relationship are elaborated in detail in the next step.

[0066] S120. For the object to be verified and the placed object corresponding to the verification request, respectively identify the first metadata value of the object to be verified corresponding to the verification metadata, and the second metadata value of the placed object corresponding to the verification metadata.

[0067] Among them, since the verification rule corresponding to the target identifier can be a rule obtained by abstracting the verification logic configured for the business party with the business identifier corresponding to the target identifier, this verification rule can reflect the business identifier, the verification logic, etc. On this basis, in order to improve the scalability at the system level, the verification logic can be represented based on verification metadata and verification relationships. This verification metadata can be understood as a data intermediary, that is, data used to describe data. Its setting allows the verification device to determine which aspects of verification logic are configured by the business party, such as shipper, supplier, commodity grade, special attributes, document type, batch, etc. It should be noted that the above examples are for the business party, and they can be reflected as codes (i.e., keys) in the verification device. For example, SKU for the business party can be reflected as sku in the verification device, and the supplier for the business party can be reflected as supplier in the verification device. In other words, this verification metadata undertakes the actual needs of the business party, and based on this verification metadata, the fields of the corresponding data in the database can be determined, that is, specific data can be obtained from the database based on this verification metadata. This verification relationship can also be called a rule expression, which is used to describe the numerical relationship between two metadata values, such as equal [=], not equal [! =], greater than [>], less than [<], etc. Among them, the metadata value can be the value of the data described by the verification metadata. For example, sku: "001", where sku is the verification metadata and 001 is the metadata value, and they are equivalent to a key-value pair. Thus, when representing the verification logic based on verification metadata and verification relationships, the verification logic can be abstracted, and the abstracted verification rule can be applied to any verification logic in any application scenario, with high scalability and flexibility.

[0068] The first metadata value can be the metadata value corresponding to the verification metadata of the object to be verified, and the second metadata value can be the metadata value corresponding to the verification metadata of the configured object. In other words, this verification metadata and the first metadata value can be a key-value pair matching the object to be verified, and this verification metadata and the second metadata value can be a key-value pair matching the configured object.

[0069] S130. Verify the first metadata value and the second metadata value based on the verification relationship, and determine whether to mix the object to be verified and the placed object according to the verification result.

[0070] Among them, since the verification relationship describes the numerical relationship between the first metadata value and the second metadata value when the object to be verified and the configured object can or cannot be placed together, the first metadata value and the second metadata value can be verified based on the verification relationship, and it can be determined whether the object to be verified and the placed object can be placed together according to the verification result. Exemplarily, assume that the verification relationship describes the numerical relationship between the first metadata value and the second metadata value when the object to be verified and the configured object cannot be placed together. Then, when these two metadata values satisfy the verification relationship, these two objects cannot be placed together, otherwise they can be placed together. It should be noted that in practical applications, optionally, there may be multiple verification rules that meet the verification request. When the verification rule describes a non-mixing rule, it can be considered that when the object to be verified does not meet all the verification rules (or when these two metadata values do not meet all the verification relationships), these two objects can be placed together.

[0071] In the above technical solution, when the verification requirements of the business party change, the verification device can abstract the verification logic corresponding to the changed verification requirements submitted by the business party to obtain a verification rule, and then verify the object to be verified belonging to the business party according to this verification rule. That is to say, developers do not need to perform secondary development for this verification requirement, and the R & D cost is relatively low; moreover, the implementation of this verification requirement does not need to go through multiple links such as review, design, development, testing, verification, and online, and the implementation efficiency is relatively high. In addition, because the verification rule can be an abstract verification logic that can reflect the service identifier, verification metadata, and verification relationship, it can be adapted to various service scenarios and has better adaptability, scalability, flexibility, readability, and reusability.

[0072] In the technical solution of the embodiment of the present invention, by identifying the service identifier corresponding to the verification request mixed with the detected object, it can be determined whether there is a target identifier corresponding to the service identifier among the configured identifiers that have been configured. If so, it indicates that there is a configured verification rule for object mixing that can implement the verification request of the business party to which the service identifier belongs. Obtain the verification rule, which can be a rule obtained by abstracting the verification logic corresponding to the verification requirements of the business party. It can reflect the service identifier, verification metadata, and verification relationship, where the verification metadata and verification relationship can be understood as an abstract representation of the verification logic; for the object to be verified and the placed object corresponding to the verification request, the first metadata value corresponding to the verification metadata of the object to be verified and the second metadata value corresponding to the verification metadata of the placed object can be identified respectively; since the verification relationship can represent the numerical relationship between the first metadata value and the second metadata value when the object to be verified and the placed object can or cannot be mixed, the two metadata values can be verified based on the verification relationship, and it can be determined whether the two objects can be mixed according to the verification result. In the above technical solution, the mixing verification is performed through the configured verification rule of the business party to which the object to be verified belongs. Since the verification rule can reflect the abstract verification logic through the verification metadata and the verification relationship, when the verification logic changes, the verification device can directly abstract the verification logic to obtain the changed verification rule without the need for R & D personnel to perform secondary development, thereby achieving the effect of reducing the R & D cost.

[0073] An optional technical solution for verifying the first metadata value and the second metadata value based on the verification relationship may include: obtaining a verifier that matches the verification relationship; if the verifier includes an equivalence verifier, verifying whether the first metadata value and the second metadata value are equal based on the equivalence verifier; and / or, if the verifier includes a non-equivalence verifier, verifying whether the first metadata value and the second metadata value are not equal based on the non-equivalence verifier. Among them, since the numerical relationship between the two metadata values described by the verification relationship can include two cases: equality and non-equality, a verifier that matches the verification relationship can be obtained. The verifier may be an equivalence verifier that can implement equivalence (i.e., equality) verification, that is, a verifier that can verify whether the first metadata value and the second metadata value are equal; or it may be a non-equivalence verifier that can implement non-equivalence (i.e., non-equality) verification, that is, a verifier that can verify whether the first metadata value and the second metadata value are not equal. Further, the verification between the two metadata values can be performed based on the obtained verifier, thereby achieving the effect of accurate verification in various cases.

[0074] Figure 2It is a flowchart of another method for verifying object mixed placement provided in an embodiment of the present invention. This embodiment is optimized based on the above technical solutions. In this embodiment, optionally, identifying a service identifier corresponding to a verification request may include: identifying a service identifier key in the verification request and obtaining a context corresponding to the verification request; sending the service identifier key and the context to a reflector so that the reflector reflects a service identifier value corresponding to the service identifier key from the context; using the service identifier key and the service identifier value as the service identifier corresponding to the verification request. The explanations of the same or corresponding terms in the above embodiments are not repeated here.

[0075] See Figure 2 , the method of this embodiment may specifically include the following steps:

[0076] S210. When detecting a verification request for object mixed placement, identify the service identifier key in the verification request and obtain the context corresponding to the verification request.

[0077] Among them, since the verification rule can be a rule obtained by abstracting the verification logic set by the service party, that is, the R & D personnel do not know what kind of service party (i.e., the service party with which service identifier) will set what kind of verification logic in the future during R & D. Therefore, when the service identifier key is identified from the verification request, the service identifier value corresponding to the service identifier key can be obtained through reflection technology. It should be noted that the service identifier key can be understood as the key of the service identifier, and the service identifier value can be understood as the value of the service identifier. Exemplarily, assuming that the service identifier of the service party setting the verification logic is shipper A, then at this time, the key is owner and the value is A. Among them, shipper can be understood as the rendering result displayed to the service party corresponding to owner, and owner can be understood as the specific code of the shipper in the verification device.

[0078] Specifically, in order to obtain the service identifier value corresponding to the service identifier key, the context corresponding to the verification request can be obtained first. The context can be understood as the full - volume parameter context, that is, all the data related to the current verification request can be obtained at one time, rather than obtaining one data at a time, thereby improving the data acquisition efficiency. The above context may include the service identifier value corresponding to the service identifier key, the metadata value corresponding to the verification metadata, etc., which are not specifically limited here.

[0079] S220. Send the service identifier key and the context to the reflector so that the reflector reflects the service identifier value corresponding to the service identifier key from the context, and use the service identifier key and the service identifier value as the service identifier corresponding to the verification request.

[0080] Among them, the reflector can be a tool supported by high-performance reflection technologies such as ASM byte stream technology. In practical applications, optionally, it can be code used to reflect the service identification value corresponding to the received service identification key from the received context. After obtaining the service identification value reflected by the reflector, the service identification value and the previously identified service identification key can be used as the service identification.

[0081] S230. If there is a target identification corresponding to the service identification among the configured identifications that have been configured, obtain the verification rule for the mixed placement of the configured object corresponding to the target identification. The verification rule includes verification metadata and a verification relationship, and the verification relationship corresponds to the verification metadata.

[0082] S240. For the object to be verified and the placed object corresponding to the verification request, respectively identify the first metadata value corresponding to the verification metadata of the object to be verified and the second metadata value corresponding to the verification metadata of the placed object.

[0083] S250. Verify the first metadata value and the second metadata value based on the verification relationship, and determine whether to mix the object to be verified and the placed object according to the verification result.

[0084] The technical solution of the embodiment of the present invention fully considers that the R & D personnel do not know during R & D what kind of verification logic is set for what kind of business party by the subsequent configured verification rule after abstraction. Therefore, a technical means is proposed to send the service identification key in the identified verification request and the obtained context corresponding to the verification request to the reflector, so that the reflector reflects the service identification value corresponding to the service identification key from the context, thereby achieving the effect of effectively obtaining the service identification value.

[0085] On this basis, an optional technical solution for the above verification method of object mixed placement may further include: identifying the configured identification keys of each configured identification from the service identification center; sending the configured identification key and the context to the reflector so that the reflector reflects the configured identification value corresponding to the configured identification key from the context; for the target identification key corresponding to the service identification key among each configured identification key, obtaining the target identification value corresponding to the target identification key from each configured identification value; comparing the target identification value with the service identification value, and determining whether the configured identification including the target identification key and the target identification value is the target identification according to the comparison result. Among them, the service identification center can be a data storage center for storing the configured identification keys that have been configured, such as a queue, a stack, a database, etc. The configured identification key can be a part of the configured identification, and thus each configured identification key can be identified from this service identification center. Furthermore, as mentioned above, when developers are developing, they do not know what kind of service parties will set what kind of verification logic in the future. Therefore, the configured identification values corresponding to each configured identification key can be obtained through reflection technology. In practical applications, optionally, in order to avoid the problem of performance bottleneck caused by frequent calls, the above service identification center can be stored in a local cache such as a JVM cache. Further, obtain the target identification key corresponding to the service identification key from each configured identification key, and then compare the target identification values corresponding to the target identification key in each configured identification value. If the two are consistent, it means that the target identification including the target identification key and the target identification value is the configured identification corresponding to the service identification.

[0086] In practical applications, optionally, another implementation manner of the above technical solution may be to identify the configured identification keys of each configured identification from the service identification center; if there is a target identification key corresponding to the service identification key among each configured identification key, send the target identification key and the context to the reflector so that the reflector reflects the target identification value corresponding to the target identification key from the context; compare the target identification value with the service identification value, and determine whether the configured identification including the target identification key and the target identification value is the target identification according to the comparison result. That is to say, all the configured identification keys can be sent to the reflector for reflecting the configured identification values first, and then the target identification value can be determined from these configured identification values; or only the target identification key can be sent to the reflector for reflecting the target identification value; and so on, which is not specifically limited here.

[0087] Another alternative technical solution is that, after obtaining the verification rule for the configured objects mixed with the target identifier, the above object mixing verification method may further include: parsing the verification rule to obtain an abstract element representing the verification logic for object mixing, and the abstract element includes verification metadata; correspondingly, identifying the first metadata value of the object to be verified corresponding to the verification metadata may include: sending the verification metadata and context to a reflector so that the reflector reflects from the context the first metadata value of the object to be verified corresponding to the verification metadata. Among them, since the verification rule is a rule obtained by abstracting the verification logic, this abstraction process can be understood as a process of abstracting the verification logic set by the business party into verification metadata and verification relationships. Exemplarily, assuming that the verification logic includes that different suppliers with the same SKU cannot be in the same container, the verification metadata can be sku and supplier, and the verification relationships can be [=] and [!=]. Its specific presentation form can be verification metadata (verification relationship): sku(=), supplier(!=). Therefore, after obtaining the verification rule, it can be parsed to obtain an abstract element representing this verification logic, and the abstract element can include verification metadata and verification relationships, and may also include the business identifier of the business party that sets this verification logic, etc., which are not specifically limited here. In practical applications, optionally, the parsed verification metadata can be stored in a metadata center, and the specific forms of this metadata center and the business identifier center can be the same or different, which are not specifically limited here.

[0088] On this basis, optionally, the abstract element may further include a prompt message indicating that object mixing fails. The above object mixing verification method may further include: if it is determined according to the verification result that the object to be verified and the placed object cannot be mixed, then a prompt is made based on the prompt message, and the specific content of this prompt message can be set by the business party when setting the verification logic. Exemplarily, continuing with the above example where the verification logic includes that different suppliers with the same SKU cannot be in the same container, the prompt message at this time can be "Different suppliers with the same SKU cannot be mixed in the same container. Please change the container!"

[0089] Figure 3It is a flowchart of yet another method for verifying object mixing provided in an embodiment of the present invention. This embodiment is optimized based on the above-mentioned various technical solutions. In this embodiment, optionally, the above method for verifying object mixing may further include: when detecting a configuration request for a verification rule, obtaining a to-be-configured identifier and to-be-configured rule details from the configuration request, parsing the to-be-configured rule details to obtain to-be-configured verification metadata and to-be-configured verification relationships, and using the to-be-configured identifier, the to-be-configured verification metadata, and the to-be-configured verification relationships as to-be-configured rule information; configuring the verification rule corresponding to the to-be-configured identifier based on the to-be-configured rule information. Among them, the explanations of the same or corresponding terms as those in the above-mentioned various embodiments will not be elaborated here.

[0090] See Figure 3 , the method of this embodiment may specifically include the following steps:

[0091] S310. When detecting a configuration request for a verification rule, obtain a to-be-configured identifier and to-be-configured rule details from the configuration request, parse the to-be-configured rule details to obtain to-be-configured verification metadata and to-be-configured verification relationships, and use the to-be-configured identifier, the to-be-configured verification metadata, and the to-be-configured verification relationships as to-be-configured rule information.

[0092] Among them, the configuration request may be a request triggered by the business party for configuring the verification rule, or a request triggered by the business party for abstracting the verification logic set by itself and configuring it as a verification rule. From this configuration request, the to-be-configured identifier and to-be-configured rule details can be obtained. The to-be-configured identifier may represent the business identifier of the business party, and the to-be-configured rule details may represent the verification logic set by the business party. Further, parse the to-be-configured rule details to obtain to-be-configured verification metadata and to-be-configured verification relationships. The to-be-configured verification metadata may be the verification metadata in the verification rule configured this time, and the to-be-configured verification relationship may be the verification relationship in the verification rule configured this time. Then, use the to-be-configured identifier, the to-be-configured verification metadata, and the to-be-configured verification relationship as to-be-configured rule information, which is important information in the process of configuring the verification rule. It should be noted that the natures of the above to-be-configured identifier and target identifier may be the same. Only different names are used here to distinguish the configuration stage or the verification stage.

[0093] In practical applications, optionally, the business party may configure the to-be-configured identifier and to-be-configured rule details in the configuration center. Exemplarily, see Figure 4 , where the rule condition is equivalent to the to-be-configured identifier, and the rule details are equivalent to the to-be-configured rule details. When the business party fills in and submits these options, the verification device can detect the corresponding configuration request.

[0094] S320. Configure the verification rule for the mixed placement of the object corresponding to the to-be-configured identifier based on the to-be-configured rule information.

[0095] Among them, the process of configuring the verification rule based on the to-be-configured rule information can be understood as modifying or deleting the original configuration rule, or generating a new verification rule, etc. This mainly depends on the specific content of the to-be-configured rule information, and no specific limitation is made here.

[0096] S330. When detecting a verification request for object mixed placement, identify the service identifier corresponding to the verification request. If there is a target identifier corresponding to the service identifier among the configured identifiers that have been configured, obtain the configured verification rule for object mixed placement corresponding to the target identifier. The verification rule includes verification metadata and a verification relationship, and the verification relationship corresponds to the verification metadata.

[0097] S340. For the to-be-verified object and the placed object corresponding to the verification request, respectively identify the first metadata value corresponding to the verification metadata of the to-be-verified object and the second metadata value corresponding to the verification metadata of the placed object.

[0098] S350. Verify the first metadata value and the second metadata value based on the verification relationship, and determine whether to mix the to-be-verified object and the placed object according to the verification result.

[0099] In the technical solution of the embodiment of the present invention, by obtaining the to-be-configured identifier and the to-be-configured rule details from the detected configuration request of the verification rule, and then parsing the to-be-configured rule details to obtain the to-be-configured verification metadata and the to-be-configured verification relationship, and combining the three as the to-be-configured rule information, the verification rule can be configured based on the to-be-configured rule information subsequently. The above technical solution allows the business party to customize and set the to-be-configured rule details corresponding to its own to-be-configured identifier, thereby increasing the initiative of the business party's operating system and the flexibility of verification rule configuration, and being able to freely handle the actual requirements of verification logic modification without secondary development by R & D personnel.

[0100] To better understand the convenience brought by the above technical solution, the following is an exemplary description of it with specific examples. Exemplarily, Consignor A requests this time: Different suppliers cannot be mixed, and the custom prompt message msg is "Different suppliers cannot be mixed in the same container. Please change the container!"; After a period of time, it is requested again: The same SKU and different suppliers cannot be mixed, and the custom prompt message msg is "The same SKU and different suppliers cannot be mixed in the same container. Please change the container!".

[0101] On this basis, the verification rule corresponding to this request can be (service identifier: Consignor A)

[0102]

[0103] The verification rule corresponding to the re - request can be (business identifier: A shipper)

[0104]

[0105]

[0106] Thus, when new verification logic appears, the verification device can automatically configure new verification rules, with strong operation convenience.

[0107] An optional technical solution is to configure the verification rule corresponding to the to - be - configured identifier based on the to - be - configured rule information, which may include: obtaining the rule configuration method corresponding to the configuration request; if the rule configuration method includes the performance - priority method, caching the to - be - configured rule information, and configuring the verification rule corresponding to the to - be - configured identifier based on the cached to - be - configured rule information at a preset time point; and / or, if the rule configuration method includes the real - time - priority method, configuring the verification rule corresponding to the to - be - configured identifier based on the to - be - configured rule information at the current time point. Among them, when configuring the verification rule based on the to - be - configured rule information, there can be two rule configuration methods: the performance - priority method and the real - time - priority method. The performance - priority method can mainly ensure verification performance and does not require real - time update of verification rules; the real - time - priority method can mainly ensure the immediate effectiveness of the newly configured verification rules and does not require the stability of verification performance. Therefore, for the performance - priority method, the to - be - configured rule information can be cached first, and the verification rule corresponding to the to - be - configured identifier can be configured based on the cached to - be - configured rule information at a preset time point; or, the newly configured verification rule can also be cached first, and the existing verification rules can be updated based on the cached verification rules at a preset time point. This improves verification performance through caching, uses high performance to replace real - time performance, thereby ensuring the smoothness of mixed - placement verification. For the real - time - priority method, the verification rule corresponding to the to - be - configured identifier can be configured based on the to - be - configured rule information at the current time point, that is, after obtaining the to - be - configured rule information, the verification rule is immediately configured and updated, thereby ensuring the real - time performance of mixed - placement verification. The above - mentioned technical solution gives two rule configuration methods, namely performance - priority and real - time - priority, which can meet the actual needs of different business parties, thereby improving the user experience.

[0108] It should be noted that the specific implementation steps of the above technical solutions can be encapsulated in components, and corresponding component interfaces are provided. Thus, when the verification device detects a verification request, it can complete the verification function by calling the component interface. At this time, the input data can be the object to be verified and the configured object, and the output data can be whether the verification is passed, custom prompt information, etc. Such components are plug-and-play and can be adapted to different application scenarios, with good scalability.

[0109] To better understand the specific implementation process of the above steps, below, taking whether two goods in the background technology can be mixed in the same container as an example, an exemplary description of the verification method for object mixing in each embodiment will be given. Exemplarily, as Figure 5 shown:

[0110] 1. The implementer / business party (white little person) configures the verification rules in the Figure 4 displayed configuration center according to the business identity. For example, for shipper A -> different suppliers with the same SKU cannot be mixed, then the rule conditions: shipper A; b) rule details: different suppliers with the same SKU cannot be in the same container; c) custom prompt information: different suppliers with the same SKU cannot be mixed in the same container, please change the container! The above configuration center supports the business party to customize and configure verification rules according to different business identities, and then after parsing the verification rules, obtain the business identity + verification metadata + rule expression + prompt information, and can provide the output of the verification rules configured by the business party in the component, which helps developers determine which business party configured what kind of verification rules. Furthermore, the configuration center can store the parsed business identity in the business identity queue. Assuming that the encoding of the shipper in the configuration device is owner, then owner: A can be stored in the business identity queue. Moreover, to avoid performance bottleneck problems caused by frequent calls, the business identity queue can be cached in the JVM cache; at the same time, the parsed verification metadata + rule expression + prompt information can be stored in the rule parser.

[0111] In practical applications, optionally, the specific content of the verification rules configured in this step can be referred to Figure 6, which shows the specific content of each item, where the name can be the rendering result shown to the business side, and the encoding can be the recording result in the verification device; the rule condition can be the combination relationship of multiple business identities. Optionally, if the real-time requirement for the verification rule is not high, that is, it can accept that the configured verification rule does not take effect immediately, then the verification rule can be stored in the redis cache first, and then the component can be automatically updated according to the verification rule in the redis cache at a preset time point. Thus, the performance can be improved through caching, using high performance to replace real-time. Of course, if the real-time requirement for the verification rule is high, the component can be automatically updated immediately based on the newly configured verification rule, thus ensuring the real-time nature of the verification rule. However, at this time, the fluency of the mixed placement verification may be affected.

[0112] 2. The receiver (black little figure) starts receiving goods, scans the goods into a certain container, and calls the component interface through the triggered verification request to execute the verification function.

[0113] 3. Based on the business identity key (such as owner) identified in the verification request by the recognizer and each business identity key in the business identity queue (i.e., the configured identification key), send the owner and the parameter context to the reflector so that it can reflect the business identity value (such as A) corresponding to the owner; similarly, send each configured identification key and the parameter context to the reflector so that it can reflect the configured identification values corresponding to these configured identification keys respectively from the JVM cache. Furthermore, if there is an owner among the configured identification keys, determine whether the configured identification value corresponding to the owner is A. If so, it means that the business identity in the verification request is the target identity with the configured identification key as owner and the configured identification value as A among the configured identifications, that is, the verification request conforms to the current business identity. At this time, the verification rule corresponding to the target identity can be sent to the rule parser to complete the parsing function of the verification rule; if not, it means that the verification request does not conform to the current business identity, and at this time, the component can be exited.

[0114] 4. When the rule parser receives the verification rule, it indicates that the verification request has been determined to match the current business identity. Then, the verification rule can be parsed to obtain the abstract elements therein: verification metadata metadate + rule expression expressions + prompt message msg. For example, continuing with the verification rule configured in step 1, the parsing result can be the verification metadata (rule expression): SKU(=), Supplier(!=), and the prompt message: Goods with the same SKU but different suppliers cannot be mixed in the same container. Please change the container! In practical applications, optionally, the parsed verification metadata can be stored in the metadata queue so that the reflector can reflect the metadata values corresponding to each verification metadata respectively. For example, sku = "001", supplier = "S1", where sku and supplier are verification metadata, and 001 and S1 are metadata values.

[0115] 5. According to the rule expression, the validator can be divided into a) same equivalence validator [=], which is used to verify whether all metadata values are equal; b) different non - equivalence validator [! =], which is used to verify whether all metadata values are not equal. Thus, batch verification of the metadata values reflected by the reflector can be performed based on each validator. Exemplarily, the configured goods in the container are: sku: "001", supplier: "S2", and the goods to be verified this time are: sku: "001", supplier: "S1". Then both the equivalence validator and the non - equivalence validator pass the verification, which conforms to the configured verification rule (the verification rule in this example is reverse verification, that is, *** cannot be mixed, which is consistent with the configuration direction). This means that the goods to be verified and the goods already placed cannot be mixed. At this time, the prompt message can be output based on the prompter; of course, if the verification fails, it means that the two can be mixed, and no prompt message needs to be given at this time.

[0116] It should be noted that the recognizer, reflector, prompter, validator, etc. described in the above examples can be tools capable of implementing the corresponding functions, or codes, functions, methods, etc. capable of implementing the corresponding functions. No specific limitation is made here.

[0117] Figure 7 This is the structural block diagram of the verification device for object mixing provided by the embodiment of the present invention. This verification device is used to execute the verification method for object mixing provided in any of the above embodiments. This verification device and the verification method for object mixing in the above embodiments belong to the same inventive concept. For the details not described in detail in the embodiments of this verification device, reference can be made to the embodiments of the verification method for object mixing above. See Figure 7, the verification device may specifically include: a verification rule acquisition module 410, a metadata value identification module 420, and a verification module 430 for mixed placement of objects. Among them,

[0118] The verification rule acquisition module 410 is configured to, when detecting a verification request for mixed placement of objects, identify the service identifier corresponding to the verification request. If there is a target identifier corresponding to the service identifier among the configured identifiers that have been configured, obtain the configured verification rule for mixed placement of objects corresponding to the target identifier. The verification rule includes verification metadata and a verification relationship, and the verification relationship corresponds to the verification metadata;

[0119] The metadata value identification module 420 is configured to, for the object to be verified and the placed object corresponding to the verification request, respectively identify the first metadata value corresponding to the verification metadata of the object to be verified and the second metadata value corresponding to the verification metadata of the placed object;

[0120] The verification module 430 for mixed placement of objects is configured to verify the first metadata value and the second metadata value based on the verification relationship, and determine whether to mix the object to be verified and the placed object according to the verification result.

[0121] Optionally, the verification rule acquisition module 410 may include:

[0122] A context acquisition unit configured to identify the service identifier key in the verification request and obtain the context corresponding to the verification request;

[0123] A service identifier value reflection unit configured to send the service identifier key and the context to a reflector, so that the reflector reflects the service identifier value corresponding to the service identifier key from the context;

[0124] A service identifier obtaining unit configured to use the service identifier key and the service identifier value as the service identifier corresponding to the verification request.

[0125] On this basis, optionally, the above verification device may further include:

[0126] A configured identifier key identification module configured to identify the configured identifier keys of the configured identifiers from the service identifier center;

[0127] A configured identifier value reflection module configured to send the configured identifier key and the context to a reflector, so that the reflector reflects the configured identifier value corresponding to the configured identifier key from the context;

[0128] A target identifier value acquisition module configured to, for the target identifier key corresponding to the service identifier key among the configured identifier keys, obtain the target identifier value corresponding to the target identifier key from the configured identifier values;

[0129] A target identifier determination module, configured to compare the target identifier value with the service identifier value, and determine whether the configured identifier including the target identifier key and the target identifier value is the target identifier according to the comparison result.

[0130] Optionally, the above verification device may further include:

[0131] An abstract element obtaining module, configured to, after obtaining the verification rules mixed with the configured completed object corresponding to the target identifier, parse the verification rules to obtain abstract elements representing the verification logic of the object mixing, where the abstract elements include verification metadata;

[0132] Correspondingly, the metadata value recognition module 420 may include:

[0133] A first metadata value reflection unit, configured to send the verification metadata and the context to a reflector, so that the reflector reflects a first metadata value corresponding to the verification metadata of the object to be verified from the context.

[0134] On this basis, optionally, the abstract element further includes a prompt message indicating that the object mixing fails, and the above verification device may further include:

[0135] An information prompt module, configured to, if it is determined according to the verification result that the object to be verified and the placed object cannot be mixed, perform a prompt based on the prompt message.

[0136] Optionally, the verification module 430 for object mixing may include:

[0137] A validator obtaining unit, configured to obtain a validator matching the verification relationship;

[0138] An equivalence verification unit, configured to, if the validator includes an equivalence validator, verify whether the first metadata value is equal to the second metadata value based on the equivalence validator; and / or,

[0139] A non-equivalence verification unit, configured to, if the validator includes a non-equivalence validator, verify whether the first metadata value is not equal to the second metadata value based on the non-equivalence validator.

[0140] Optionally, the above verification device may further include:

[0141] A to-be-configured rule information obtaining module, configured to, when detecting a configuration request for the verification rule, obtain a to-be-configured identifier and to-be-configured rule details from the configuration request, parse the to-be-configured rule details to obtain to-be-configured verification metadata and to-be-configured verification relationships, and use the to-be-configured identifier, the to-be-configured verification metadata, and the to-be-configured verification relationships as to-be-configured rule information;

[0142] The verification rule configuration module is used to configure the verification rules corresponding to the to-be-configured identifier based on the to-be-configured rule information.

[0143] On this basis, optionally, the verification rule configuration module may include:

[0144] The rule configuration method acquisition unit is used to acquire the rule configuration method corresponding to the configuration request;

[0145] The first verification rule configuration unit is used to cache the to-be-configured rule information if the rule configuration method includes the performance priority method, and configure the verification rules corresponding to the to-be-configured identifier based on the cached to-be-configured rule information at a preset time point; and / or,

[0146] The second verification rule configuration unit is used to configure the verification rules corresponding to the to-be-configured identifier based on the to-be-configured rule information at the current time point if the rule configuration method includes the real-time priority method.

[0147] The verification device for object mixed placement provided by the embodiments of the present invention can identify the service identifier corresponding to the verification request for the detected object mixed placement through the verification rule acquisition module, and determine whether there is a target identifier corresponding to the service identifier among the configured identifiers that have been configured. If so, it means that there is a configured verification rule for object mixed placement that can implement the verification request for the service party to which the service identifier belongs, and obtain the verification rule. It can be a rule obtained by abstracting the verification logic corresponding to the verification requirements of the service party, which can reflect the service identifier, verification metadata, and verification relationship. The verification metadata and verification relationship can be understood as an abstract representation of the verification logic; through the metadata value identification module, for the to-be-verified object and the placed object corresponding to the verification request, the first metadata value corresponding to the verification metadata of the to-be-verified object and the second metadata value corresponding to the verification metadata of the placed object can be respectively identified; since the verification relationship can represent the numerical relationship between the first metadata value and the second metadata value when the to-be-verified object and the placed object can or cannot be mixed, the verification module for object mixed placement can verify these two metadata values based on the verification relationship, and determine whether these two objects can be mixed according to the verification result. The above device performs mixed placement verification through the configured verification rules of the service party to which the to-be-verified object belongs. Since the verification rules can reflect the abstract verification logic through the verification metadata and the verification relationship, when the verification logic changes, the verification device can directly abstract the verification logic to obtain the changed verification rule without the need for R & D personnel to perform secondary development, thereby achieving the effect of reducing R & D costs.

[0148] The verification device for object misplacement provided by the embodiments of the present invention can execute the verification method for object misplacement provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method.

[0149] It should be noted that in the embodiments of the above verification device for object misplacement, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of the functional units are only for the convenience of mutual distinction and do not limit the protection scope of the present invention.

[0150] Figure 8 FIG. is a schematic structural diagram of a verification device for object misplacement provided by an embodiment of the present invention. As Figure 8 shown, the verification device includes a memory 510, a processor 520, an input device 530, and an output device 540. The number of processors 520 in the verification device can be one or more. Figure 8 Here, one processor 520 is taken as an example; the memory 510, processor 520, input device 530, and output device 540 in the verification device can be connected through a bus or other means. Figure 8 Here, connection through the bus 550 is taken as an example.

[0151] The memory 510, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the verification method for object misplacement in the embodiments of the present invention (for example, the verification rule acquisition module 410, metadata value identification module 420, and object misplacement verification module 430 in the verification device for object misplacement). The processor 520 executes various functional applications and data processing of the verification device by running the software programs, instructions, and modules stored in the memory 510, that is, realizes the above verification method for object misplacement.

[0152] The memory 510 may mainly include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created according to the use of the verification device. In addition, the memory 510 may include a high-speed random access memory, and may further include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some instances, the memory 510 may further include a memory remotely set relative to the processor 520, and these remote memories can be connected to the device through a network. Examples of the above network include but are not limited to the Internet, an enterprise internal network, a local area network, a mobile communication network, and their combinations.

[0153] The input device 530 can be used to receive input digital or character information and generate key signal inputs related to the user settings and function controls of the device. The output device 540 can include display devices such as a display screen.

[0154] An embodiment of the present invention provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute a verification method for object mixing when executed by a computer processor, and the method includes:

[0155] When a verification request for object mixing is detected, identify the service identifier corresponding to the verification request. If there is a target identifier corresponding to the service identifier among the configured identifiers that have been configured, obtain the verification rule for object mixing that has been configured and corresponds to the target identifier. The verification rule includes verification metadata and a verification relationship, and the verification relationship corresponds to the verification metadata;

[0156] For the object to be verified and the placed object corresponding to the verification request, respectively identify the first metadata value corresponding to the verification metadata of the object to be verified and the second metadata value corresponding to the verification metadata of the placed object;

[0157] Verify the first metadata value and the second metadata value based on the verification relationship, and determine whether to mix the object to be verified and the placed object according to the verification result.

[0158] Certainly, the computer-executable instructions of a storage medium provided by an embodiment of the present invention are not limited to the method operations described above, and can also execute related operations in the verification method for object mixing provided by any embodiment of the present invention.

[0159] Through the above description of the embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software and necessary general-purpose hardware. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as a floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk, or optical disc of a computer, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present invention.

[0160] Note that the above is only a preferred embodiment of the present invention and the technical principles applied. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, re-adjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments. Without departing from the concept of the present invention, more other equivalent embodiments can be included, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for verifying the mixed placement of objects, characterized in that, it includes: When detecting a verification request for the mixed placement of objects, identifying the service identification key in the verification request and obtaining the context corresponding to the verification request; Sending the service identification key and the context to a reflector so that the reflector reflects a service identification value corresponding to the service identification key from the context; Taking the service identification key and the service identification value as the service identification corresponding to the verification request, where the service identification is the identification of the business party to which the object to be verified corresponding to the verification request belongs; If there is a target identification corresponding to the service identification among the configured identifications that have been configured, obtaining the verification rule for the mixed placement of objects that has been configured and corresponds to the target identification, where the verification rule is a rule obtained by abstracting the verification logic set for the business party, and the verification rule includes verification metadata and a verification relationship, and the verification relationship corresponds to the verification metadata; For the object to be verified and the placed objects corresponding to the verification request, respectively identifying a first metadata value corresponding to the verification metadata of the object to be verified and a second metadata value corresponding to the verification metadata of the placed objects; Verifying the first metadata value and the second metadata value based on the verification relationship, and determining whether to mix the object to be verified and the placed objects according to the verification result.

2. The method according to claim 1, characterized in that, it further includes: Identifying the configured identification keys of the configured identifications from a service identification center; Sending the configured identification key and the context to a reflector so that the reflector reflects a configured identification value corresponding to the configured identification key from the context; For the target identification key corresponding to the service identification key among the configured identification keys, obtaining a target identification value corresponding to the target identification key from the configured identification values; Comparing the target identification value and the service identification value, and determining whether the configured identification including the target identification key and the target identification value is the target identification according to the comparison result.

3. The method according to claim 1, characterized in that, after obtaining the verification rule for the mixed placement of objects that has been configured and corresponds to the target identification, it further includes: Parsing the verification rule to obtain abstract elements for representing the verification logic of the mixed placement of objects, where the abstract elements include the verification metadata; The identifying the first metadata value corresponding to the verification metadata of the object to be verified includes: sending the verification metadata and the context to the reflector so that the reflector reflects the first metadata value corresponding to the verification metadata of the object to be verified from the context.

4. The method according to claim 3, characterized in that, the abstract elements further include a prompt message for indicating the failure of the mixed placement of objects, and the method further includes: If it is determined according to the verification result that the object to be verified and the placed object cannot be mixed, a prompt is made based on the prompt information.

5. The method according to claim 1, wherein, the verifying the first metadata value and the second metadata value based on the verification relationship includes: obtaining a verifier that matches the verification relationship; if the verifier includes an equivalence verifier, verifying whether the first metadata value and the second metadata value are equal based on the equivalence verifier; and / or, if the verifier includes a non-equivalence verifier, verifying whether the first metadata value and the second metadata value are not equal based on the non-equivalence verifier.

6. The method according to claim 1, wherein, it further includes: when a configuration request for the verification rule is detected, obtaining a to-be-configured identifier and to-be-configured rule details from the configuration request, parsing the to-be-configured rule details to obtain the to-be-configured verification metadata and the to-be-configured verification relationship, and using the to-be-configured identifier, the to-be-configured verification metadata, and the to-be-configured verification relationship as to-be-configured rule information; configuring the verification rule corresponding to the to-be-configured identifier based on the to-be-configured rule information.

7. The method according to claim 6, wherein, configuring the verification rule corresponding to the to-be-configured identifier based on the to-be-configured rule information includes: obtaining a rule configuration method corresponding to the configuration request; if the rule configuration method includes a performance priority method, caching the to-be-configured rule information, and configuring the verification rule corresponding to the to-be-configured identifier based on the cached to-be-configured rule information at a preset time point; and / or, if the rule configuration method includes a real-time priority method, configuring the verification rule corresponding to the to-be-configured identifier based on the to-be-configured rule information at the current time point.

8. An object mixing verification device, wherein, it includes: a verification rule acquisition module, configured to, when a verification request for object mixing is detected, identify a service identifier corresponding to the verification request, and if a target identifier corresponding to the service identifier exists among the configured identifiers that have been configured, obtain the configured verification rule for object mixing corresponding to the target identifier, where the verification rule includes verification metadata and a verification relationship, and the verification relationship corresponds to the verification metadata; a metadata value identification module, configured to respectively identify a first metadata value corresponding to the verification metadata of the object to be verified and a second metadata value corresponding to the verification metadata of the placed object for the object to be verified and the placed object corresponding to the verification request; an object mixing verification module, configured to verify the first metadata value and the second metadata value based on the verification relationship, and determine whether to mix the object to be verified and the placed object according to the verification result; wherein, the verification rule acquisition module includes: A context acquisition unit, configured to identify a service identification key in the verification request and acquire a context corresponding to the verification request; A service identification value reflection unit, configured to send the service identification key and the context to a reflector, so that the reflector reflects a service identification value corresponding to the service identification key from the context; A service identification obtaining unit, configured to use the service identification key and the service identification value as a service identification corresponding to the verification request, where the service identification is an identification of a service party to which the object to be verified belongs, and the verification rule is a rule obtained by abstracting a verification logic set for the service party.

9. A verification device for object mixed placement, characterized in that, it includes: one or more processors; a memory, configured to store one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors implement the object mixed placement verification method according to any one of claims 1-7.

10. A computer-readable storage medium, on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the object mixed placement verification method according to any one of claims 1-7 is implemented.

Images