Data validation methods and systems, and edge end devices

Abstract

The present disclosure relates to a data verification method and system, and an edge end device, and also relates to the technical field of computers. The data verification method includes: receiving, by an edge end device, cloud end data issued by a cloud end device and terminal data collected by a terminal device; verifying, by the edge end device, the cloud end data and the terminal data according to a service processing logic; and sending, by the edge end device, a verification result to at least one of the cloud end device or the terminal device.

Description

Technical Field

[0001] Cross - reference to Related Applications This disclosure claims priority based on Chinese Patent Application No. 202110737908.0 filed on June 30, 2021, and the disclosure of that application is incorporated herein by reference in its entirety.

[0002] This disclosure relates to the field of computer technology, and in particular, to data verification methods, data verification systems, edge devices, and non - volatile computer - readable storage media.

Background Art

[0003] In recent years, radio frequency identification (RFID) has been widely adopted by various businesses and warehouses due to its advantages such as non - contact, batch reading, and easy inventory (count).

[0004] In related technologies, verification calculations can be performed based on terminals such as RFID readers / writers or based on cloud devices.

Summary of the Invention

Means for Solving the Problems

[0005] According to some embodiments of this disclosure, a data verification method is provided, including steps of: receiving, by an edge device, cloud data issued by a cloud device and terminal data collected by a terminal device; verifying, by the edge device, the cloud data and the terminal data based on business process logic; and transmitting, by the edge device, the result of the verification to at least one of the cloud device or the terminal device.

[0006] In some embodiments, the data validation method further includes the steps of: the edge device sending a validation activation request to the cloud device before receiving cloud data and terminal data; and the edge device receiving an activation response returned from the cloud device, wherein the activation response includes relevant information about business process logic.

[0007] In some embodiments, the verification activation request includes version information of the edge software currently deployed on the edge device, and the activation response includes update information for the edge software.

[0008] In some embodiments, the step of validating cloud data and terminal data based on business process logic includes, by an edge device, matching terminal data with cloud data and determining whether the validation passed based on the matching result, or by an edge device validating terminal data based on cloud data.

[0009] In some embodiments, the step of validating cloud data and terminal data based on business process logic includes the step of the edge device determining whether the terminal data contains abnormal data, and the step of the edge device determining whether the validation has passed based on the result of the determination and the result of the comparison.

[0010] In some embodiments, the cloud data is checklist data including item tag data, and the step of determining whether the terminal data contains abnormal data includes the step of the edge device determining whether the terminal data contains abnormal data based on at least one of item location information or tag data status information.

[0011] In some embodiments, the cloud data includes item tag data, and the step of verifying the cloud data and terminal data based on business process logic includes the step of the edge device determining whether the terminal data matches the location where the terminal device is located, and if the terminal data does not match the location, the step of the edge device reporting the terminal data to the cloud device so that the cloud device can determine whether the terminal data is abnormal data.

[0012] In some embodiments, the step of an edge device receiving cloud data issued by a cloud device and terminal data collected by a terminal device includes the step of the edge device receiving a check request issued by a cloud device, wherein the check request includes a list of radio frequency identification (RFID) data to be checked as cloud data, and the step of the edge device receiving RFID data collected by a terminal device as terminal data.

[0013] In some embodiments, the step of transmitting the verification results to at least one of a cloud device or a terminal device includes: the edge device transmitting terminal data that does not match the cloud data to the cloud device; the edge device transmitting to the terminal device the results of filtering the abnormal data and the verification performed by the cloud device on the non-matching terminal data; the edge device receiving check completion information returned from the terminal device, wherein the check completion information includes a checklist number; and the edge device transmitting the check completion information to the cloud device, wherein the check completion information includes a checklist number, a list of checked RFID data, and registration information about the abnormal condition.

[0014] In some embodiments, the step of an edge device receiving RFID data collected by a terminal device as terminal data includes the step of the edge device receiving a verification request sent from the terminal device based on an edge location address issued by a cloud device, the verification request including a verification sheet number; the step of the edge device sending verification confirmation information to the terminal device, the verification confirmation information including a verification sheet number; and the step of the edge device receiving RFID data collected by the terminal device as terminal data.

[0015] In some embodiments, the step of an edge device receiving cloud data issued by a cloud device and terminal data collected by a terminal device includes the step of the edge device sending a check request sent from the terminal device to the cloud device, wherein the check request includes information about the location of item data to be checked; the step of the edge device sending a check response returned from the cloud device to the terminal device, wherein the check response includes a list of RFID data to be checked as cloud data; and the step of the edge device receiving RFID data collected by the terminal device as terminal data.

[0016] In some embodiments, the step of an edge device receiving cloud data issued by a cloud device and terminal data collected by a terminal device includes the step of the edge device receiving a count request issued by a cloud device, wherein the count request includes a list of data to be checked as cloud data, and the step of the edge device receiving count data collected by a terminal device as terminal data.

[0017] In some embodiments, the step of sending the verification result to at least one of a cloud device or a terminal device includes, by an edge device, the step of sending the verification result to a terminal device, and, after receiving the count completion information returned from the terminal device, the step of sending the count result data to a cloud device.

[0018] In some embodiments, the step of an edge device receiving cloud data issued by a cloud device and terminal data collected by a terminal device includes the step of the edge device sending a check request sent from the terminal device to the cloud device, wherein the check request includes information about the warehouse area where the item data to be checked is located; the step of the edge device sending a check response returned from the cloud device to the terminal device, wherein the check response includes a list of RFID data to be checked as cloud data; and the step of the edge device receiving the collected RFID data returned from the terminal device as terminal data.

[0019] In some embodiments, the step of an edge device receiving cloud data issued by a cloud device and terminal data collected by a terminal device includes the steps of: the edge device receiving a check request issued by a cloud device, wherein the check request issued by the cloud device includes a list of RFID data to be checked as cloud data; the edge device receiving a check request sent from a terminal device, wherein the check request sent from the terminal device includes information about the warehouse area where the item data to be checked is located; the edge device sending a check response to the terminal device; and the edge device receiving the collected RFID data returned from the terminal device as terminal data.

[0020] In some embodiments, the step of an edge device receiving cloud data issued by a cloud device and terminal data collected by a terminal device includes the step of the edge device receiving a list of RFID data to be checked, issued by the cloud device and transferred by the terminal device, as cloud data, wherein the cloud data is issued from the cloud device to the terminal device in response to a check request sent from the terminal device, and the step of the edge device receiving collected RFID data sent from the terminal device as terminal data.

[0021] In some embodiments, the step of an edge device receiving cloud data issued by a cloud device and terminal data collected by a terminal device includes the step of the edge device receiving, as cloud data, a list of RFID data of items to be placed on a shelf, issued by the cloud device and transferred by the terminal device, wherein the cloud data is issued from the cloud device to the terminal device in response to a shelf-placement request sent from the terminal device, and the step of the edge device receiving collected RFID data sent from the terminal device as terminal data.

[0022] In some embodiments, the terminal device is a portal frame hardware device, the cloud device is an inventory management system, the cloud data is checklist data, the terminal data is RFID data, and the step of validating the cloud data and terminal data based on business process logic includes the step of validating the check data by an edge device, and the step of sending the validation result to at least one of the cloud device or terminal device includes the step of sending the validation result of the check data to an application on the inventory management system and sending the check status to a display device.

[0023] According to a further embodiment of the present disclosure, there is provided an edge device comprising a receiver for receiving cloud data issued by a cloud device and terminal data collected by a terminal device, a processor for verifying the cloud data and the terminal data based on business process logic, and a transmitter for transmitting the result of the verification to at least one of the cloud device or the terminal device.

[0024] According to some other embodiments of the present disclosure, there is provided a data verification system comprising an edge device for implementing a data verification method according to any one of the above embodiments, a cloud device for issuing cloud data, and a terminal device for collecting terminal data.

[0025] According to a further embodiment of the present disclosure, there is provided an edge device comprising a memory and a processor coupled to the memory, wherein the processor is configured to execute a data verification method according to any one of the above embodiments based on instructions stored in the memory.

[0026] According to still other embodiments of the present disclosure, there is provided a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, executes a data verification method according to any one of the above embodiments.

[0027] In the above embodiments, the verification calculation tasks are distributed to the edge device, and as a result, the terminal cost and power consumption can be reduced. In addition, the verification can be performed on the edge device instead of the cloud device, which can improve the processing efficiency, reduce the network load, and thus improve the verification efficiency.

[0028] The accompanying drawings, which are incorporated herein and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0029] This disclosure will be more clearly understood from the following detailed description when reference is made to the accompanying drawings.

Brief Description of the Drawings

[0030] [Figure 1] It is a flowchart of some embodiments of the data verification method according to this disclosure. [Figure 2] It is a schematic diagram showing some embodiments of the initialization configuration of an edge device according to this disclosure. [Figure 3a] It is a schematic diagram showing some embodiments of edge device-cloud device collaborative verification according to this disclosure. [Figure 3b] It is a schematic diagram showing some other embodiments of edge device-cloud device collaborative verification according to this disclosure. [Figure 3c] It is a schematic diagram showing some embodiments of inventory verification according to this disclosure. [Figure 3d] It is a schematic diagram showing some embodiments of check verification according to this disclosure. [Figure 3e] It is a schematic diagram showing some other embodiments of check verification according to this disclosure. [Figure 3f] It is a schematic diagram showing still other embodiments of check verification according to this disclosure. [Figure 3g] It is a schematic diagram showing further embodiments of check verification according to this disclosure. [Figure 3h] It is a schematic diagram showing some embodiments of warehousing and receipt verification according to this disclosure. [Figure 3i] It is a schematic diagram showing some embodiments of the data verification method according to this disclosure. [Figure 4] It is a block diagram showing some embodiments of an edge device according to this disclosure. [Figure 5] It is a block diagram showing some other embodiments of an edge device according to this disclosure. [Figure 6] It is a block diagram showing still other embodiments of an edge device according to this disclosure. [Figure 7]This block diagram shows several embodiments of the data validation system described herein. [Modes for carrying out the invention]

[0031] Next, various exemplary embodiments of this disclosure will be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the relative arrangements of components and steps, formulas, and numerical values ​​described in these examples do not limit the scope of the invention.

[0032] At the same time, please understand that, for the sake of clarity, the dimensions of the various parts shown in the drawings are not drawn to their actual proportions.

[0033] The following description of at least one exemplary embodiment is illustrative in practice and is not intended to limit the invention, its application, or use in any way.

[0034] Techniques, methods, and apparatus known to those skilled in the art may not be discussed in detail, but where appropriate, these techniques, methods, and apparatus should be considered part of this specification.

[0035] Of all the examples shown and discussed herein, any particular values ​​should be interpreted as illustrative only and not limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0036] Please note that similar reference numbers and letters are indicated similarly in the attached drawings, and therefore, once an article is defined in a drawing, it does not need to be discussed further in the attached drawings.

[0037] As mentioned above, RFID-based warehousing operations face several new challenges. Specifically, warehousing operations often involve tag or barcode verification, including receiving, inventory counting, and outbound checks, to ensure the integrity of goods. RFID batch recognition-based warehousing operations require a massive number of simultaneous processes for verification, creating challenges for both terminal-based and cloud-based verification.

[0038] For example, in the case of an RFID warehouse management system based on RFID reader / writer terminal verification calculations, many verification calculations will be distributed across terminals, including several sites in the form of fixed RFID readers / writers, taking into account uncontrollable factors of the on-site network.

[0039] This verification method has the following problems: It requires terminals with powerful memory and computing capabilities, which increases power consumption and costs for both the terminals and individual nodes. Terminals or nodes with insufficient capabilities may cause system lag, slow response times, and other issues that could affect user experience and productivity. Furthermore, transmitting large amounts of verification data to fully distributed terminals can pose potential data security risks.

[0040] For example, in the case of an RFID warehouse management system based on cloud-based verification calculations, the cloud has enormous storage and computing capabilities, which can reduce the computing and storage load on terminals. However, long cloud chains can cause significant delays in system response, and response failures may occur if the network is unstable. Real-time uploads of large amounts of data also present even greater challenges to the network.

[0041] In other words, in the case of warehouse management, batch RFID data collection and verification based on terminals or the cloud cannot achieve an effective balance between terminal costs, data security, and rapid task response.

[0042] All stages of warehouse management—receiving, inventory counting, and shipping—involve batch RFID data collection and verification. The experience and cost savings gained from using RFID in these stages directly improve the ROI (Return on Investment) of RFID applications, including reduced terminal costs and improved operational experience and efficiency.

[0043] The inventors of this disclosure found that the following problems existed in the related technology, namely, the inability to achieve a balance between equipment cost, verification efficiency, and other factors, resulting in a reduction in verification effectiveness.

[0044] In light of this, this disclosure proposes a technical solution for data verification that can reduce equipment costs, improve verification efficiency, and thereby improve verification effectiveness. The technical solution of this disclosure can be implemented in the following embodiments to address the above technical problems.

[0045] Figure 1 shows flowcharts of several embodiments of the data validation method according to this disclosure.

[0046] As shown in Figure 1, in step 110, the edge device receives cloud data issued by the cloud device and terminal data collected by the terminal device.

[0047] For example, terminal devices may include RFID readers / writers including handheld readers / writers, PDAs (personal digital assistants) that support RFID collection, fixed and mounted RFID readers / writers (including access doors, etc.), read-only RFID collection devices, and separate RFID collection devices that perform RFID excitation and receive collected data.

[0048] For example, an RFID reader / writer can connect to an edge device via a local area connection such as Wi-Fi (Wireless Fidelity), wired, or USB (Universal Serial Bus) connection, or via a cellular network.

[0049] For example, edge devices and RFID readers / writers can have a one-to-one or one-to-many relationship. From a job scheduling perspective, edge devices and RFID readers / writers can also have a many-to-many relationship, allowing load balancing scheduling to be achieved across multiple edge devices.

[0050] In some embodiments, a cloud device may actively push data to be verified (cloud data) to an edge device in response to the triggering of an appropriate event. For example, after a picking task or a converging process is completed, a WMS (Warehouse Management System) may, as a cloud device, send a checklist containing an RFID list to the warehouse edge device corresponding to the picking task.

[0051] For example, a cloud device could be an inventory management system. An inventory management system could be a WMS, a store system, an asset management system, etc., and the items could include pallets, bins, goods stored in a warehouse, etc.

[0052] In some embodiments, when a task terminal device initiates a check request, the cloud device may push the data to be validated to the edge device, or the data to be validated may be transferred to the edge device via the terminal device.

[0053] In some embodiments, prior to step 110, the verification method further includes the steps of: the edge device sending a verification activation request to the cloud device; and the edge device receiving an activation response returned from the cloud device, wherein the activation response includes relevant information about the business process logic.

[0054] For example, a verification activation request might include version information for the edge software currently deployed on the edge device, and an activation response might include update information for the edge software. The edge software may be associated with business process logic.

[0055] For example, a validation activation request may include a validation activation update request.

[0056] In some embodiments, a cloud device sends a verification activation request or verification activation update to an edge device, and the cloud device receives an activation response returned from the edge device, wherein the activation response includes confirmation of the verification activation or verification activation update.

[0057] For example, a verification activation update might include version information for edge software related to business process logic currently supported by the cloud device. The activation response might include a download confirmation and link request for the edge software.

[0058] In some embodiments, verification software, including business process logic, may be pre-deployed on edge devices. For example, the business process logic may include a verification sheet number parsing method, verification rules and algorithms, as well as a verification input data format, a verification output data format, an event-driven interaction method, and so on.

[0059] For example, business process logic may be shown in the table below.

[0060] [Table 1]

[0061] For example, the status information in tag data includes the status of the product in the associated warehouse, and the product status could be Initialization (printed, not yet on the shelf), Inbound (successfully placed on the shelf), Outbound (checked for delivery), Picked (to be checked), etc.

[0062] For example, anomaly data detection may include, during the checking process, identifying a large number of tags for a particular storage location in a checklist; recognizing, based on auxiliary information (such as a map of storage locations), that some of these tags belong to goods stored near the check area and were not pulled to the warehouse check platform; and determining that this portion of the tag data is anomaly data and that the anomaly data is tag data resulting from storage drift (misidentification) near the check area.

[0063] In some embodiments, an initialization configuration may be performed on the edge device according to the embodiment shown in Figure 2.

[0064] Figure 2 is a schematic diagram showing several embodiments of the initialization configuration of an edge device according to this disclosure.

[0065] As shown in Figure 2, in the edge device registration process, the edge device downloads the edge SDK (Software Development Kit) and certificates to be deployed in advance, the edge device sends a registration request to the cloud device, the registration request including the certificate, the cloud device performs authentication and activation processing, and the cloud device returns a registration response to the edge device, the registration response including the edge device's serial number and token.

[0066] During the edge device update process, the cloud device sends a device update request to the edge device, the cloud device generates a new token for the edge device, and the edge device returns device update confirmation information.

[0067] During the software synchronization process, the edge device sends an RFID verification activation request to the cloud device, which includes information about the currently deployed software version. The cloud device then returns an activation response.

[0068] For example, the activation response includes activation confirmation information or software update information, which may include business process logic (such as validation sheet number rules, validation rules, validation algorithms, validation input data formats, validation output data formats, and event-driven interaction methods).

[0069] During long-term connectivity processes, edge devices and cloud devices can reduce response latency by transmitting continuous heartbeat signals.

[0070] After receiving data from the cloud device and the terminal device, processing can proceed to the remaining steps in Figure 1.

[0071] In step 120, the edge device validates cloud data and device data based on business process logic.

[0072] In some embodiments, verification in a warehouse storage environment may include RFID validity verification for batch warehouse storage of warehouse goods, RFID inventory count verification for goods placed in the warehouse, RFID verification for batch delivery of goods, RFID check verification, and so on.

[0073] For example, in a warehouse asset scenario, the verification process described above may be used to count RFID assets such as pallets. The verification process described above can also be used in scenarios such as batch receiving and batch settlement verification in stores.

[0074] In some embodiments, the edge device compares terminal data with cloud data, and the edge device determines whether the verification passed based on the comparison results. For example, the edge device determines whether the terminal data contains abnormal data, and the edge device determines whether the verification passed based on the determination results and the comparison results.

[0075] For example, after determining whether terminal data is abnormal, it may be further determined whether the item's location is abnormal.

[0076] In some embodiments, the cloud data is checklist data including item tag data. The edge device determines whether the terminal data contains abnormal data based on at least one of item location information or tag data status information. For example, the item could be goods placed in a warehouse. For example, the item location information could be information about the storage location of the item within the warehouse.

[0077] In some embodiments, the cloud data includes item tag data. The edge device determines whether the terminal data matches the warehouse area where the terminal device is located. If the terminal data does not match the warehouse area, the edge device reports the terminal data to the cloud device, which can then determine whether the terminal data is abnormal.

[0078] For example, in addition to matching warehouse area information, in the case of a store scenario, the location information of the goods may also be matched.

[0079] In some embodiments, the edge device receives a check request issued by a cloud device, the check request includes a list of RFID data to be checked as cloud data, and the edge device receives RFID data collected by a terminal device as terminal data.

[0080] In step 130, the edge device sends the verification results to at least one of the cloud device or terminal device.

[0081] In some embodiments, the edge device synchronizes the verification results directly or indirectly with a task terminal (which may be integrated with an RFID reader / writer), the cloud, or an available display, thereby achieving business status synchronization.

[0082] For example, after verification is complete on the edge device, the task terminal may be notified to complete the interaction between the task terminal and the cloud device, or after verification is complete on the edge device, the cloud device may be notified to synchronize with the task terminal or associated display, or the edge device may directly synchronize the verification results with the task terminal, the cloud device, and other displays.

[0083] In the above embodiment, the cloud device transmits business data that needs to be verified by an RFID reader / writer (terminal device) to the edge device. After the RFID reader / writer collects the RFID data, the RFID data is verified by the edge device. The edge device then directly or indirectly synchronizes the verification results with a task terminal (which may be integrated with the RFID reader / writer), a cloud device, or an available display, thereby achieving business status synchronization.

[0084] In this way, verification calculations are introduced on the RFID edge side, and general memory and computing devices are provided to RFID readers / writers (terminal devices) located nearby. As a result, power consumption and costs of the readers / writers are reduced, and real-time computation responses are provided.

[0085] In some embodiments, collaborative verification can be performed by edge devices and cloud devices. This avoids the need to send large amounts of data to edge devices, which would otherwise place a heavy load on them, and also improves data security.

[0086] For example, during an inventory counting process, an edge device may receive data to be verified from two adjacent tunnels, and if there is RFID data collected by terminals in three or more tunnels, this situation is reported to a cloud device. The cloud device determines whether the working data is abnormal. Abnormal data can be caused by tags that have drifted over long distances or by tags that are not in inventory. In this way, the edge device does not need to consider the status of abnormal tags, and as a result, its processing load can be reduced.

[0087] For example, during the checking process, edge devices validate based on a list of data to be checked, filtering batches of anomalous inventory data from the same storage location, reporting anomalous RFID tag data to a cloud device, and the data filtering is confirmed by the cloud device based on a larger amount of data.

[0088] This collaborative validation between edge devices and cloud devices is suitable for inventory counting scenarios where very large amounts of data are validated locally, as well as for check scenarios where cloud-assisted anomaly data filtering is required when the surrounding environment is not clean.

[0089] In this way, cloud devices can support edge devices in anomaly detection based on larger amounts of data.

[0090] Figure 3a is a schematic diagram illustrating several embodiments of edge device-cloud device collaborative verification according to this disclosure.

[0091] As shown in Figure 3a, the edge device receives a check request issued by a cloud device (such as an RFID engine server or WMS), which includes a list of RFID data to be checked as cloud data, as well as a checklist number, etc., and the edge device returns request confirmation information.

[0092] The edge device receives check requests sent from terminal devices (such as PDAs), where the check request includes the platform number of the cargo area to be checked, and the edge device returns a check response. The edge device receives RFID data collected by terminal devices as terminal data and provides real-time verification feedback.

[0093] The edge device returns RFID verification feedback to the terminal device, and returns unrecognized RFID collected data (terminal data that does not match cloud data) to the cloud device. After filtering and verifying this collected data, the cloud device returns RFID verification feedback.

[0094] The edge device sends to the terminal device the results of filtering out abnormal data and verification performed by the cloud device on mismatched terminal data (such as data resulting from picking more items), the edge device receives check completion information returned from the terminal device, the check completion information including the checklist number, and the edge device sends the check completion information to the cloud device, the check completion information including the checklist number, a list of checked RFID data, and registration information about the abnormal situation.

[0095] Figure 3b is a schematic diagram illustrating some other embodiments of edge device-cloud device collaborative verification according to this disclosure.

[0096] As shown in Figure 3b, the edge device transmits a check request from the terminal device to the cloud device, the check request including information about the warehouse area where the item data to be checked is located (such as the platform number); the edge device transmits the check response returned from the cloud device to the terminal device, the check response including a list of RFID data to be checked as cloud data; and the edge device receives the RFID data collected by the terminal device as terminal data.

[0097] Figure 3c is a schematic diagram illustrating several embodiments of inventory verification according to this disclosure.

[0098] As shown in Figure 3c, the edge device receives a count request issued by the cloud device, and the count request includes a list of data to be checked as cloud data, and returns a count task response. For example, count area identification information may also be returned.

[0099] The edge device assigns counting tasks to terminal devices and receives the counting data collected by the terminal devices as terminal data for verification. For example, inventory data may include a list of RFID data.

[0100] The edge device sends the verification results to an end device capable of displaying the results visually. After receiving the count completion information returned from the end device, the edge device sends the count result data to the cloud device.

[0101] For example, the count result data includes at least one of the count data list or the validation results.

[0102] Figure 3d is a schematic diagram illustrating several embodiments of the check and verification described herein.

[0103] As shown in Figure 3d, the terminal device sends a check request to the server device, which includes a checklist number (such as the platform number and identification information of the storage location awaiting check). The server device returns check confirmation information, which includes the edge location address pointing to the edge device corresponding to the checklist number, as well as the verification sheet number.

[0104] The edge device receives a verification request sent from the terminal device based on an edge location address issued by the cloud device, which includes a verification sheet number. The edge device then sends verification confirmation information to the terminal device, which includes a verification sheet number. The edge device also receives RFID data collected by the terminal device as terminal data.

[0105] Figure 3e is a schematic diagram illustrating some other embodiments of the check and verification described herein.

[0106] As shown in Figure 3e, the edge device transmits a check request from the terminal device to the cloud device, the transmit being a check request that includes information about the warehouse area where the item data to be checked is located; the edge device transmits a check response returned from the cloud device to the terminal device, the transmit being a check response that includes a list of RFID data to be checked as cloud data; and the edge device receives the collected RFID data returned from the terminal device as terminal data.

[0107] Figure 3f is a schematic diagram illustrating yet another embodiment of the check and verification described herein.

[0108] As shown in Figure 3f, the edge device receives a check request issued by the cloud device, the check request issued by the cloud device includes a list of RFID data to be checked as cloud data; the edge device receives a check request sent from the terminal device, the check request sent from the terminal device includes information about the warehouse area where the item data to be checked is located; the edge device sends a check response to the terminal device; and the edge device receives the collected RFID data returned from the terminal device as terminal data.

[0109] Terminal devices may send abnormal registration information and check completion information to edge devices, and edge devices send abnormal registration information and check completion information to cloud devices.

[0110] Figure 3g is a schematic diagram illustrating a further embodiment of the check and verification described herein.

[0111] As shown in Figure 3g, the terminal device sends a check request to the cloud device, the check request including the platform number where the item to be checked is located, and the cloud device returns a check response including a list of RFID data to be checked.

[0112] The edge device receives a list of RFID data to be checked, issued by the cloud device and transferred by the terminal device, as cloud data. The cloud data is issued and received from the cloud device to the terminal device in response to a check request sent from the terminal device, and the edge device receives the collected RFID data sent from the terminal device as terminal data.

[0113] Figure 3h is a schematic diagram illustrating several embodiments of receiving and verification of goods in possession according to this disclosure.

[0114] As shown in Figure 3h, the terminal device sends a shelf-loading request to the cloud device, the shelf-loading request including the container number of the goods to be loaded onto the shelf, and the cloud device returns a shelf-loading response including a list of RFID data (of the items) to be loaded onto the shelf.

[0115] The edge device receives, as cloud data, a list of RFID data (of items) to be placed on shelves, issued by the cloud device and transferred by the terminal device. The cloud data is issued and received from the cloud device to the terminal device in response to shelf-placement requests sent from the terminal device, and the edge device receives the collected RFID data sent from the terminal device as terminal data.

[0116] The edge device sends information that collection is complete to the terminal device, and the terminal device sends a list of RFID data for the items that should be placed on the shelf to the cloud device.

[0117] Figure 3i is a schematic diagram illustrating several embodiments of the data validation method according to this disclosure.

[0118] As shown in Figure 3i, the terminal device is a portal frame hardware device, the cloud device is a WMS, the cloud data is checklist data, and the terminal data is RFID data.

[0119] The edge device receives checklists (check tasks) sent from the WMS and RFID data (read and write data) sent from the portal frame hardware device, and then performs check data verification.

[0120] The edge device sends the results of the check data validation to the WMS application and the check status to the terminal device's display device.

[0121] For example, the check status may also be sent to a cloud device or a display device at a warehouse location.

[0122] In the above embodiment, the cost and power consumption of RFID collection devices can be reduced, RFID verification responses can be accelerated, the business experience can be improved, and system security can be improved through collaboration between terminal devices and cloud devices, collaboration between terminal devices and edge devices, and on-demand control of the distribution of verification data.

[0123] Figure 4 is a block diagram showing several embodiments of the edge device according to this disclosure.

[0124] As shown in Figure 4, the edge device 4 includes a receiver 41 for receiving cloud data issued by a cloud device and terminal data collected by a terminal device, a processor 42 for verifying the cloud data and terminal data based on business process logic, and a transmitter 43 for transmitting the verification results to at least one of the cloud device or terminal device.

[0125] In some embodiments, the transmitter 43 sends a verification activation request to a cloud device, and the receiver 41 receives an activation response returned from the cloud device, wherein the activation response includes relevant information about the business process logic.

[0126] In some embodiments, the verification activation request includes version information of the edge software currently deployed on the edge device, and the activation response includes update information for the edge software.

[0127] In some embodiments, the processor 42 compares terminal data with cloud data, and the processor 42 determines whether the verification has passed based on the results of the comparison.

[0128] In some embodiments, the processor 42 determines whether the terminal data contains abnormal data, and the processor 42 determines whether the verification has passed based on the result of the determination and the result of the comparison.

[0129] In some embodiments, the cloud data is checklist data including item tag data, and the processor 42 determines whether the terminal data includes abnormal data based on at least one of item location information or tag data status information.

[0130] In some embodiments, the cloud data includes item tag data, the processor 42 determines whether the terminal data matches the location of the terminal device, and if there is a mismatch between the terminal data and the location, the transmitter 43 reports the terminal data to the cloud device so that the cloud device can determine whether the terminal data is abnormal data.

[0131] In some embodiments, the receiver 41 receives a check request issued by a cloud device, wherein the check request includes a list of RFID data to be checked as cloud data, and receives RFID data collected by a terminal device as terminal data.

[0132] In some embodiments, the transmitter 43 transmits terminal data that does not match the cloud data to the cloud device, transmits the results of filtering abnormal data and verification performed by the cloud device on the non-matching terminal data to the terminal device, receives check completion information returned from the terminal device, wherein the check completion information includes a checklist number, and transmits the check completion information to the cloud device, wherein the check completion information includes a checklist number, a list of checked RFID data, and abnormal status registration information.

[0133] In some embodiments, the receiver 41 receives a verification request from a terminal device based on an edge location address issued by a cloud device, the verification request including a verification sheet number, the transmitter 43 transmits verification confirmation information to the terminal device, the verification confirmation information including a verification sheet number, and the receiver 41 receives the RFID data collected by the terminal device as terminal data.

[0134] In some embodiments, the transmitter 43 transmits a check request sent from a terminal device to a cloud device, wherein the check request includes information about the location of the item data to be checked; and transmits a check response returned from the cloud device to the terminal device, wherein the check response includes a list of RFID data to be checked as cloud data; and the receiver 41 receives the RFID data collected by the terminal device as terminal data.

[0135] In some embodiments, the receiver 41 receives a count request issued by a cloud device, wherein the count request includes a list of data to be checked as cloud data, and the receiver 41 receives the count data collected by the terminal device as terminal data.

[0136] In some embodiments, the transmitter 43 sends the verification result to the terminal device, and after the receiver 41 receives the count completion information returned from the terminal device, the transmitter 43 sends the count result data to the cloud device.

[0137] In some embodiments, the transmitter 43 transmits a check request sent from a terminal device to a cloud device, wherein the check request includes information about the warehouse area where the item data to be checked is located; and transmits a check response returned from the cloud device to the terminal device, wherein the check response includes a list of RFID data to be checked as cloud data; and the receiver 41 receives the collected RFID data returned from the terminal device as terminal data.

[0138] In some embodiments, the receiver 41 receives a check request issued by a cloud device, the check request being received by the cloud device, which includes a list of RFID data to be checked as cloud data; and receives a check request sent from a terminal device, the check request being received by the terminal device, which includes information about the warehouse area where the item data to be checked is located; the transmitter 43 sends a check response to the terminal device; and the edge device receives the collected RFID data returned from the terminal device as terminal data.

[0139] In some embodiments, the receiver 41 receives a list of RFID data to be checked as cloud data, which is issued by a cloud device and transferred by a terminal device, and the cloud data is issued from the cloud device to the terminal device in response to a check request sent from the terminal device, and the receiver 41 receives the collected RFID data sent from the terminal device as terminal data.

[0140] In some embodiments, the receiver 41 receives as cloud data a list of RFID data of items to be placed on shelves, issued by a cloud device and transferred by a terminal device, wherein the cloud data is issued from the cloud device to the terminal device in response to a shelf-placement request sent from the terminal device, and the receiver 41 receives the collected RFID data sent from the terminal device as terminal data.

[0141] In some embodiments, the terminal device is a portal frame hardware device, the cloud device is an inventory management system, the cloud data is checklist data, the terminal data is RFID data, the processor 42 performs check data verification, the transmitter 43 transmits the check data verification results to an application on the inventory management system, and transmits the check status to a display device.

[0142] Figure 5 is a block diagram showing some other embodiments of the edge device according to this disclosure.

[0143] As shown in Figure 5, the edge device 5 of this embodiment comprises a memory 51 and a processor 52 coupled to the memory 51, and the processor 52 is configured to execute a data verification method according to any one of the embodiments of this disclosure based on instructions stored in the memory 51.

[0144] Memory 51 may include, for example, system memory, a fixed non-volatile storage medium, etc. System memory stores, for example, the operating system, applications, boot loader, database, and other programs.

[0145] Figure 6 is a block diagram showing yet another embodiment of the edge device according to the present disclosure.

[0146] As shown in Figure 6, the edge device 6 of this embodiment comprises a memory 610 and a processor 620 coupled to the memory 610, and the processor 620 is configured to execute a data verification method according to any one of the embodiments of this disclosure based on instructions stored in the memory 610.

[0147] Memory 610 may include, for example, system memory, a fixed non-volatile storage medium, etc. System memory stores, for example, the operating system, application programs, a boot loader, and other programs.

[0148] The edge device 6 may further include an input / output interface 630, a network interface 640, a storage interface 650, and the like. These interfaces 630, 640, 650, memory 610, and processor 620 may be connected, for example, via a bus 660. The input / output interface 630 provides a connection interface for input / output devices such as displays, mice, keyboards, touchscreens, microphones, and loudspeakers. The network interface 640 provides a connection interface for various networked devices. The storage interface 650 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0149] Figure 7 is a block diagram showing several embodiments of the data validation system according to this disclosure.

[0150] As shown in Figure 7, the data verification system 7 includes an edge device 71 for implementing a data verification method according to any one of the embodiments described above, a cloud device 72 for issuing cloud data, and a terminal device 73 for collecting terminal data.

[0151] Those skilled in the art will understand that embodiments of the present disclosure may be provided as methods, systems, or computer program products. Accordingly, embodiments of the present disclosure may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments that include both hardware and software elements. Furthermore, the present disclosure may take the form of a computer program product that is implemented on one or more computer-readable non-temporary storage media (including, but not limited to, disk storage, CD-ROMs, optical memory, etc.) in which computer-readable program code is embodied.

[0152] Up to this point, the data verification methods, data verification systems, edge devices, and non-volatile computer-readable storage media described herein have been described in detail. Some details known in the art have not been described in order to avoid obscuring the concepts of this disclosure. Based on the above description, those skilled in the art will be able to understand how to implement the technical solutions disclosed herein.

[0153] The methods and systems of this disclosure can be implemented in many ways. For example, the methods and systems of this disclosure can be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The sequence of steps of the method described above is illustrative only, and the steps of the method of this disclosure are not limited to the specific order described above unless otherwise specified. In addition, in some embodiments, this disclosure can also be implemented as a program recorded on a recording medium, which includes machine-readable instructions for implementing the method according to this disclosure. Thus, this disclosure also covers recording mediums that store a program for performing the method according to this disclosure.

[0154] While several specific embodiments of this disclosure have been described in detail as examples, those skilled in the art will understand that the above examples are illustrative only and are not intended to limit the scope of this disclosure. Those skilled in the art will understand that the above embodiments can be modified without departing from the scope and spirit of this disclosure. The scope of this disclosure is defined by the following claims: [Explanation of symbols]

[0155] 4 Edge devices 41 Receiver 42 processors 43 Transmitters 5 Edge devices 51 memory 52 processors 6 Edge devices 610 memory 620 processor 630 Input / Output Interface 640 network interfaces 650 storage interfaces 66 Service Bus 7. Data Verification System 71 Edge devices 72 Cloud Devices 73 Terminal devices

Claims

1. A step of receiving cloud data issued by a cloud device and terminal data collected by a terminal device using an edge device, wherein the cloud data includes item tag data, The edge device performs the steps of verifying the cloud data and the terminal data based on business process logic, The edge device transmits the verification results to at least one of the cloud device or the terminal device. Includes, The step of verifying the cloud data and terminal data based on business process logic, The edge device determines whether the terminal data matches the location where the terminal device is located. If the terminal data does not match the location, the edge device reports the terminal data to the cloud device so that the cloud device can determine whether the terminal data is abnormal. Data validation methods, including those mentioned above.

2. Prior to the step of receiving cloud data and terminal data, The edge device sends a verification activation request to the cloud device, The step of receiving an activation response returned from the cloud device by the edge device, wherein the activation response includes relevant information about the business process logic. The data verification method according to claim 1, further comprising:

3. The data verification method according to claim 2, wherein the verification activation request includes version information of the edge software currently deployed on the edge device, and the activation response includes update information of the edge software.

4. The step of verifying the cloud data and terminal data based on business process logic, The edge device compares the terminal data with the cloud data and determines whether the verification has passed based on the results of the comparison, or The edge device verifies the terminal data based on the cloud data. The data verification method according to claim 1, including the method described in claim 1.

5. The step of verifying the cloud data and terminal data based on business process logic, The edge device determines whether the terminal data contains abnormal data, The edge device performs the step of determining whether the verification has passed based on the result of the determination and the result of the matching. The data verification method according to claim 4, including the method described in claim 4.

6. The aforementioned cloud data is checklist data including item tag data, The step of determining whether the terminal data includes abnormal data, The edge device determines whether the terminal data contains abnormal data based on at least one of the following: item location information or tag data status information. The data verification method according to claim 5, including the method described in claim 5.

7. The step of receiving cloud data issued by a cloud device and terminal data collected by a terminal device by an edge device is, The edge device receives a check request issued by the cloud device, wherein the check request includes a list of radio frequency identification (RFID) data to be checked as cloud data. The edge device receives the RFID data collected by the terminal device as terminal data. A data verification method according to any one of claims 1 to 6, including the method described in any one of claims 1 to 6.

8. The step of transmitting the results of the verification to at least one of the cloud device or the terminal device is, The edge device transmits the terminal data that does not match the cloud data to the cloud device. The edge device performs the filtering of abnormal data and transmits the results of the verification performed by the cloud device on the mismatched terminal data to the terminal device. The edge device receives check completion information returned from the terminal device, wherein the check completion information includes a checklist number. A step of transmitting check completion information from the edge device to the cloud device, wherein the check completion information includes the checklist number, the list of checked RFID data, and registration information about the abnormal status. The data verification method according to claim 7, including the method described in claim 7.

9. The step of receiving the RFID data collected by the terminal device as terminal data by the edge device is as follows: The edge device receives a verification request sent from the terminal device based on the edge location address issued by the cloud device, the verification request including a verification sheet number. The edge device transmits verification information to the terminal device, wherein the verification information includes a verification sheet number. The edge device receives the RFID data collected by the terminal device as terminal data. The data verification method according to claim 7, including the method described in claim 7.

10. The step of receiving cloud data issued by a cloud device and terminal data collected by a terminal device by an edge device is, The edge device transmits a check request sent from the terminal device to the cloud device, wherein the check request includes information about the location of item data to be checked. The edge device transmits a check response returned from the cloud device to the terminal device, wherein the check response includes a list of RFID data to be checked as cloud data. The edge device receives the RFID data collected by the terminal device as terminal data. A data verification method according to any one of claims 1 to 6, including the method described in any one of claims 1 to 6.

11. The step of receiving cloud data issued by a cloud device and terminal data collected by a terminal device by an edge device is, The edge device receives a count request issued by the cloud device, wherein the count request includes a list of data to be checked as cloud data. The edge device receives the count data collected by the terminal device as terminal data. A data verification method according to any one of claims 1 to 6, including the method described in any one of claims 1 to 6.

12. The step of transmitting the results of the verification to at least one of the cloud device or the terminal device is, The edge device transmits the results of the verification to the terminal device. After receiving the count completion information returned from the terminal device, the edge device transmits the count result data to the cloud device. The data verification method according to claim 11, including the method described in claim 11.

13. The step of receiving cloud data issued by a cloud device and terminal data collected by a terminal device by an edge device is, The edge device transmits a check request sent from the terminal device to the cloud device, wherein the check request includes information about the warehouse area where the item data to be checked is located. The edge device transmits a check response returned from the cloud device to the terminal device, wherein the check response includes a list of RFID data to be checked as cloud data. The edge device receives the collected RFID data returned from the terminal device as terminal data. A data verification method according to any one of claims 1 to 6, including the method described in any one of claims 1 to 6.

14. The step of receiving cloud data issued by a cloud device and terminal data collected by a terminal device by an edge device is, The step of receiving a check request issued by the cloud device on the edge device, wherein the check request issued by the cloud device includes a list of RFID data to be checked as cloud data; The edge device receives a check request transmitted from the terminal device, wherein the check request transmitted from the terminal device includes information about the warehouse area where the item data to be checked is located. The edge device sends a check response to the terminal device, The edge device receives the collected RFID data returned from the terminal device as terminal data. A data verification method according to any one of claims 1 to 6, including the method described in any one of claims 1 to 6.

15. The step of receiving cloud data issued by a cloud device and terminal data collected by a terminal device by an edge device is, The edge device receives, as cloud data, a list of RFID data to be checked, which has been issued by the cloud device and transferred by the terminal device, wherein the cloud data is issued from the cloud device to the terminal device in response to a check request sent from the terminal device. The edge device receives the collected RFID data transmitted from the terminal device as terminal data. A data verification method according to any one of claims 1 to 6, including the method described in any one of claims 1 to 6.

16. The step of receiving cloud data issued by a cloud device and terminal data collected by a terminal device by an edge device is, The edge device receives, as cloud data, a list of RFID data of items to be placed on a shelf, which has been issued by the cloud device and transferred by the terminal device, wherein the cloud data is issued from the cloud device to the terminal device in response to a shelf-placement request transmitted from the terminal device. The edge device receives the collected RFID data transmitted from the terminal device as terminal data. A data verification method according to any one of claims 1 to 6, including the method described in any one of claims 1 to 6.

17. The terminal device is a portal frame hardware device, the cloud device is an item management system, the cloud data is checklist data, and the terminal data is RFID data. The step of verifying the cloud data and terminal data based on business process logic, The edge device verifies the check data. Includes, The step of transmitting the results of the verification to at least one of the cloud device or the terminal device is, The steps include: transmitting the results of the verification of the check data to an application on the item management system, and transmitting the check status to a display device. A data verification method according to any one of claims 1 to 6, including the method described in any one of claims 1 to 6.

18. A receiver for receiving cloud data issued by a cloud device and terminal data collected by a terminal device, wherein the cloud data includes item tag data, A processor for verifying the cloud data and terminal data based on business process logic, A transmitter for transmitting the results of the verification to at least one of the cloud device or the terminal device. Equipped with, The aforementioned processor, Determine whether the terminal data matches the location of the terminal device. An edge device that, if the terminal data does not match the location, reports the terminal data to the cloud device so that the cloud device can determine whether the terminal data is abnormal data.

19. An edge device for carrying out the data verification method described in any one of claims 1 to 17, Cloud devices for publishing cloud data, Terminal devices for collecting terminal data and A data verification system equipped with the following features.

20. Memory and The processor coupled to the aforementioned memory and Equipped with, The processor is configured to execute the data verification method described in any one of claims 1 to 17 based on instructions stored in the memory. Edge devices.

21. A non-volatile computer-readable storage medium that stores a computer program, when executed by a processor, causes the processor to perform the data verification method described in any one of claims 1 to 17.

Images