Storage management method and related device

Abstract

The embodiment of the invention provides a warehouse management method, and the method comprises the steps: obtaining label data collected by a triggering operation from an adaptive data channel in response to the triggering operation of radio frequency identification equipment in a target warehouse; then determining a product identification code indicated by the label data, and configuring a target task based on cargo information indicated by the product identification code; the target task is input into the task queue, an inventory management process corresponding to the target warehouse is executed based on the execution parameters corresponding to the task queue, and the inventory management process is used for updating cargo information corresponding to the target warehouse. Therefore, the batch management process of the radio frequency identification devices of different specifications is realized, the data channel is established by dynamically matching the cargo owner code and the communication protocol, the complex interface adaptation process is avoided, batch execution is performed through the task queue, the data requirements of the radio frequency identification devices of different models can be concurrently processed, and the management efficiency is improved. Therefore, the updating efficiency of the cargo information in the warehouse management process is improved.

Description

Technical Field

[0001] This specification relates to the field of computer application technology, specifically to warehouse management technology within the field of computer application technology, and more specifically to warehouse management methods and related devices. Background Technology

[0002] In logistics and warehousing systems, RFID is a commonly used tag reading method and a crucial data source for inventory management. However, RFID typically supports only a single communication protocol, resulting in poor system scalability. Furthermore, RFID readers often employ a single-tag reading mode, leading to inefficiency and operational bottlenecks when handling large volumes of goods entering and leaving the warehouse. The polling-based data acquisition method causes delays in inventory status updates, failing to meet the real-time requirements of modern warehouse management. Additionally, the varying interfaces of different RFID brands make system integration difficult, increasing the complexity and cost of warehouse automation upgrades and impacting the efficiency and convenience of updating goods information during warehouse management. Summary of the Invention

[0003] This specification provides warehousing management methods and related devices, which improve the efficiency and convenience of updating cargo information during warehousing management.

[0004] To achieve the above technical objectives, the embodiments of this specification provide the following technical solutions: Firstly, one embodiment of this specification provides a warehouse management method, comprising: In response to a trigger operation on an RFID device in a target warehouse, the tag data collected by the trigger operation is acquired. The tag data is accessed through a target data channel associated with the RFID device. The target data channel is established using a communication protocol matched with the RFID device. The communication protocol is determined based on the cargo owner code corresponding to the RFID device. The target warehouse contains RFID devices with different cargo owner codes, and the RFID devices include multiple data access methods. Determine the product identification code indicated by the label data, and configure the target task based on the goods information indicated by the product identification code; The target task is input into the task queue, and the inventory management process corresponding to the target warehouse is executed based on the execution parameters corresponding to the task queue. The inventory management process is used to update the goods information corresponding to the target warehouse.

[0005] Secondly, one embodiment of this specification provides a warehouse management device, comprising: The acquisition unit is used to acquire tag data collected by the triggering operation in response to a triggering operation of an RFID device in a target warehouse. The tag data is accessed through a target data channel associated with the RFID device. The target data channel is established using a communication protocol matched with the RFID device. The communication protocol is determined based on the cargo owner code corresponding to the RFID device. The target warehouse contains RFID devices with different cargo owner codes, and the RFID devices include multiple data access methods. A determining unit is configured to determine the product identification code indicated by the label data and configure a target task based on the goods information indicated by the product identification code. The management unit is used to input the target task into the task queue, and to execute the inventory management process corresponding to the target warehouse based on the execution parameters corresponding to the task queue. The inventory management process is used to update the goods information corresponding to the target warehouse.

[0006] Optionally, in one possible implementation, the acquisition unit is specifically used to acquire the access request of the RFID device in the target warehouse through the RFID intermediate layer, and determine the access method information corresponding to the RFID device; The acquisition unit is specifically used to configure a communication protocol based on the access method information, so as to establish a target data channel between the radio frequency identification intermediate layer and the warehouse management system using the communication protocol; The acquisition unit is specifically used to associate the target data channel with the cargo owner code corresponding to the radio frequency identification device; The acquisition unit is specifically used to respond to a trigger operation for a radio frequency identification (RFID) device in the target warehouse, triggering the RFID intermediate layer to determine the target data channel based on the cargo owner code, and to acquire the tag data collected by the trigger operation through the target data channel.

[0007] Optionally, in one possible implementation, the determining unit is specifically used to determine the data stream corresponding to the tag data; The determining unit is specifically used to perform deduplication processing on the identification information contained in the data stream to obtain the product identification code; The determining unit is specifically used to configure the target task based on the cargo information indicated by the product identification code.

[0008] Optionally, in one possible implementation, the determining unit is specifically used to determine the quantity and status of goods corresponding to the product identification code, so as to configure the goods information; The determining unit is specifically used to perform information verification based on the cargo information to obtain a verification result; The determining unit is specifically used to configure the target task corresponding to the product identification code according to the quantity of goods and the status of goods if the verification result indicates that the verification is passed.

[0009] Optionally, in one possible implementation, the management unit is specifically used to input the target task into the task queue and determine the priority parameter corresponding to the target task; The management unit is specifically used to obtain batch execution values ​​in response to the input of the execution parameters; The management unit is specifically configured to configure the execution sequence corresponding to the task queue according to the priority parameter, and to perform batch processing on the tasks in the execution sequence through the batch execution value, so as to execute the inventory management process corresponding to the target warehouse.

[0010] Optionally, in one possible implementation, the management unit is specifically configured to configure the execution sequence corresponding to the task queue according to the priority parameter; The management unit is specifically used to determine the cargo owner code corresponding to each task in the execution sequence, so as to merge the tasks in the execution sequence based on the cargo owner code; The management unit is specifically used to batch process the tasks in the execution sequence after merging tasks using the batch execution values, so as to execute the inventory management process corresponding to the target warehouse.

[0011] Optionally, in one possible implementation, the management unit is specifically used to acquire corresponding inventory change information and abnormal information in the inventory management process; The management unit is specifically used to classify the inventory change information according to the owner code and display it in the first area corresponding to the owner code; The management unit is specifically used to determine the cause of the abnormality corresponding to the abnormal information, so as to associate the abnormal goods corresponding to the abnormal information with the cause of the abnormality, and display them in the second area.

[0012] Thirdly, one embodiment of this specification also provides a computing device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the warehouse management method described above.

[0013] Fourthly, one embodiment of this specification also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the warehouse management method described above.

[0014] Fifthly, embodiments of this specification provide a computer program product or computer program, the computer program product including a computer program that can be stored in a computer-readable storage medium or in the cloud; the processor of the computer device reads the computer program, and when the processor executes the computer program, it implements the steps of the above-described warehouse management method.

[0015] As can be seen from the above technical solution, the warehouse management method provided in this specification, in response to a trigger operation on an RFID device in the target warehouse, acquires the tag data collected by the trigger operation. This tag data is accessed through a target data channel associated with the RFID device, and the target data channel is established using a communication protocol matched with the RFID device. The communication protocol is determined based on the owner code corresponding to the RFID device. The target warehouse contains RFID devices with different owner codes, and the RFID devices include multiple data access methods. Then, the product identification code indicated by the tag data is determined, and a target task is configured based on the goods information indicated by the product identification code. The target task is then input into a task queue, and the inventory management process corresponding to the target warehouse is executed based on the execution parameters corresponding to the task queue. This inventory management process is used to update the goods information corresponding to the target warehouse. This achieves batch management of RFID devices of different specifications. By dynamically matching the owner code and establishing a data channel with the communication protocol, the complex interface adaptation process is avoided. Furthermore, batch execution through the task queue can concurrently process the data requirements of different models of RFID devices, thereby improving the efficiency and convenience of updating goods information in the warehouse management process. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this specification. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0017] Figure 1 This is a network architecture diagram for the operation of the warehouse management system.

[0018] Figure 2 This is a flowchart illustrating the process architecture of warehouse management as provided in an embodiment of this application.

[0019] Figure 3 This is a flowchart illustrating a warehouse management method provided as one embodiment of this specification.

[0020] Figure 4 This is a schematic diagram illustrating a storage management method provided as one embodiment of this specification.

[0021] Figure 5 This is a schematic diagram illustrating another warehouse management method provided as one embodiment of this specification.

[0022] Figure 6 This is a schematic diagram of the functional modules of a warehouse management device provided for one embodiment of this specification.

[0023] Figure 7 This is a schematic diagram of the structure of a computing device provided for one embodiment of this specification. Detailed Implementation

[0024] Unless otherwise defined, the technical or scientific terms used in the embodiments of this specification shall have the ordinary meaning understood by one of ordinary skill in the art to which this specification pertains. The terms "first," "second," and similar terms used in the embodiments of this specification do not indicate any order, quantity, or importance, but are merely used to avoid confusion of constituent elements.

[0025] Unless the context otherwise requires, throughout this specification, "a plurality of" means "at least two," and "including" is interpreted as open-ended or encompassing, that is, "including, but not limited to." In the description of this specification, terms such as "one embodiment," "some embodiments," "exemplary embodiment," "example," "specific example," or "some examples" are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this specification. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example.

[0026] Below, we will explain the terms that may appear in the instruction manual.

[0027] Radio Frequency Identification (RFID): A technology that uses wireless radio frequency signals to read and write tags without contact. It consists of a reader, electronic tags, and a back-end system. Data interaction is achieved through electromagnetic induction or backscattering. It can be used for logistics tracking, access control, and retail payments.

[0028] Electronic Product Code (EPC): Stored in RFID tags, it contains information such as manufacturer, product category, and serial number. Data is parsed through the Savant network to achieve "one item, one code", supporting cross-enterprise data sharing and anti-counterfeiting.

[0029] Warehouse Management System (WMS): A management system that integrates functions such as inbound operations, outbound operations, warehouse transfers, inventory transfers, and virtual warehouse management, as well as batch management, material matching, inventory counting, quality inspection management, virtual warehouse management, and real-time inventory management. It effectively controls and tracks the entire process of logistics and cost management in warehouse operations, and realizes or improves the enterprise's warehouse information management.

[0030] It should be understood that the warehouse management method provided in this application can be applied to systems or programs that include warehouse management functions in terminal devices, such as warehouse management applications. Specifically, the warehouse management system can run on systems such as... Figure 1 In the network architecture shown, such as Figure 1 The diagram shown is a network architecture diagram of the warehouse management system. As can be seen, the warehouse management system can provide warehouse management processes with multiple information sources. That is, through the configuration operations on the terminal side, data channels are established for different types of RFID devices, thereby realizing a warehouse management process with dynamic allocation of data channels. It can be understood that... Figure 1 The document illustrates various terminal devices, which can be computer devices. In real-world scenarios, more or fewer types of terminal devices may participate in the warehouse management process. The specific number and types depend on the actual scenario and are not limited here. Additionally, Figure 1 The example shows one server, but in real-world scenarios, multiple servers can be involved, especially in multidisciplinary output scenarios. The specific number of servers depends on the actual scenario.

[0031] In this embodiment, the server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, and the terminal and server can be connected to form a blockchain network; this application does not impose any restrictions.

[0032] It is understandable that the aforementioned warehouse management system can run on personal mobile terminals, such as as a warehouse management application, or it can run on a server, or it can run on third-party devices to provide warehouse management and obtain the warehouse management and processing results of information sources. Specifically, the warehouse management system can run as a program on the aforementioned devices, or it can run as a system component of the aforementioned devices, or it can run as a cloud service program. The specific operating mode depends on the actual scenario and is not limited here.

[0033] In logistics and warehousing systems, RFID is a commonly used tag reading method and a crucial data source for inventory management. However, RFID typically supports only a single communication protocol, resulting in poor system scalability. Furthermore, RFID readers often employ a single-tag reading mode, leading to inefficiency and operational bottlenecks when handling large volumes of goods entering and leaving the warehouse. The polling-based data acquisition method causes delays in inventory status updates, failing to meet the real-time requirements of modern warehouse management. Additionally, the varying interfaces of different RFID brands make system integration difficult, increasing the complexity and cost of warehouse automation upgrades and impacting the efficiency and convenience of updating goods information during warehouse management.

[0034] To address the aforementioned problems, this application proposes a warehouse management method, which is applied to... Figure 2 In the warehouse management process framework shown, such as Figure 2 The diagram shown is a process architecture diagram for warehouse management provided in an embodiment of this application. Through the configuration operation of the terminal, data channels for different types of RFID devices are established, thereby accurately obtaining the product identification code during the process of RFID devices reading tag data, in order to execute the warehouse management process. This solves the technical problems existing in the current RFID warehouse system, such as poor protocol compatibility, low batch processing efficiency, and insufficient data real-time performance, and provides an efficient and flexible multi-protocol compatible RFID warehouse inbound and outbound management method.

[0035] It is understood that the warehouse management method provided in this application can be a program written as processing logic in a hardware system, or it can be a warehouse management device that implements the above processing logic in an integrated or external manner. As one implementation, the warehouse management device, in response to a trigger operation on an RFID device in the target warehouse, acquires tag data collected by the trigger operation. This tag data is accessed through a target data channel associated with the RFID device, and the target data channel is established using a communication protocol matched with the RFID device. The communication protocol is determined based on the owner code corresponding to the RFID device. The target warehouse contains RFID devices with different owner codes, and the RFID devices include multiple data access methods. Then, the product identification code indicated by the tag data is determined, and a target task is configured based on the cargo information indicated by the product identification code. The target task is then input into a task queue to execute the inventory management process corresponding to the target warehouse based on the execution parameters corresponding to the task queue. This inventory management process is used to update the cargo information corresponding to the target warehouse. This enables batch management of RFID devices of different specifications. By dynamically matching the owner's code and communication protocol to establish a data channel, the complex interface adaptation process is avoided. Furthermore, batch execution through task queues can concurrently process the data requirements of different RFID devices, thereby improving the efficiency and convenience of updating cargo information in the warehouse management process.

[0036] Based on the above process architecture, the warehouse management method in this application will be described below. Please refer to [link / reference]. Figure 3 , Figure 3 A flowchart illustrating a warehouse management method provided in this application embodiment, which includes at least the following steps: 301. In response to a trigger operation on an RFID device in the target warehouse, acquire the tag data collected by the trigger operation. The tag data is accessed through the target data channel associated with the RFID device. The target data channel is established using a communication protocol that matches the RFID device. The communication protocol is determined based on the cargo owner code corresponding to the RFID device. The target warehouse contains RFID devices with different cargo owner codes. The RFID devices include multiple data access methods.

[0037] In this embodiment, the target warehouse can be a logistics warehouse, which may provide services to multiple "cargo owners" (customers). Different cargo owners may use different RFID devices, and even the same cargo owner may use different devices in different warehouse areas. Since the hardware brands and models of RFID devices may be different, different RFID readers may provide different access methods (USB serial port, network API, WebSocket, etc.).

[0038] Specifically, the cargo owner code can be used as a key identifier to dynamically select the communication protocol and parameters (such as USB port number, IP address, WebSocket URL, etc.) that the device corresponding to the cargo owner should use. In determining the target data channel for the RFID device using the cargo owner code, the cargo owner code can contain different levels of representation. For example, cargo owner A might use HTTP protocol access in area 1 and USB serial communication in area 2. In this case, after determining that the cargo owner code corresponds to cargo owner A, it is also necessary to identify the area identifier contained in the cargo owner code to call the corresponding target data channel, thereby ensuring the matching degree between the target data channel and the RFID device.

[0039] As can be seen, this embodiment is compatible with HTTP / WebSocket protocol and USB serial communication, and supports RFID batch inbound and outbound operations. It is applied to a warehouse management system, where the system performs batch inbound and outbound operations based on tag data collected by RFID devices.

[0040] In one possible scenario, the correspondence between the cargo owner code and the target data channel can be established in real time during the RFID device access process, or it can be a correspondence that has been established and stored historically.

[0041] Specifically, the process of establishing the correspondence between cargo owner codes and target data channels can be carried out through an RFID middleware layer, such as... Figure 4 As shown, Figure 4 This diagram illustrates a scenario of a warehouse management method provided as one embodiment of this specification. As a configuration service, it can be quickly configured within an existing WMS system to achieve batch management of multiple RFID devices of different models. First, the RFID middleware layer obtains access requests from RFID devices in the target warehouse and determines the access method information corresponding to the RFID devices. Then, based on the access method information, a communication protocol is configured to establish a target data channel between the RFID middleware layer and the warehouse management system. The target data channel is then associated with the owner's code corresponding to the RFID device. Furthermore, during the identification of RFID tags, in response to trigger operations (scanning, reading, identification, etc.) targeting RFID devices in the target warehouse, the RFID middleware layer is triggered to determine the target data channel based on the owner's code and obtain the tag data collected by the trigger operation through the target data channel.

[0042] Optionally, to maintain the correspondence between cargo owner codes and target data channels, a device configuration table will be maintained in the system configuration or database, which associates information such as cargo owner codes, device models, communication protocol types, and connection parameters, in order to improve data persistence.

[0043] Therefore, in the aforementioned dynamic adaptation process, when the WMS system initiates a device access request, the tag data carries the cargo owner's code. The backend service queries the configuration table based on this code, dynamically loads the corresponding communication protocol driver, and initializes the device connection using the stored connection parameters. This system is highly flexible and can smoothly connect RFID devices of different ages and brands; it achieves hardware-level configurability, reducing implementation and maintenance costs.

[0044] 302. Determine the product identification code indicated by the label data, and configure the target task based on the cargo information indicated by the product identification code.

[0045] In this embodiment, the tag data is the data obtained after reading the RFID tag, which corresponds to the goods / products. Therefore, it is necessary to determine the product identification code corresponding to the goods / products, such as EPC, which is stored in the RFID tag and contains information such as manufacturer, product category, and serial number. By parsing the data through the Savant network, "one item, one code" can be achieved to improve the accuracy of inventory information.

[0046] It is understandable that tag data can be acquired in real time in batches. That is, in the target warehouse, there may be multiple concurrent reading operations of different models of RFID devices. Therefore, through EPC conversion, real-time data stream processing can be realized, and a real-time data pipeline from hardware to software can be established to ensure that data can be captured quickly.

[0047] In one possible scenario, due to the repetitive polling nature of RFID readers, they may read the same tag multiple times within a very short period, generating a large amount of duplicate data. Directly reporting this raw data to the business system is useless. Therefore, data cleaning (deduplication) is necessary. This involves first determining the data stream corresponding to the tag data; then deduplicating the identification information contained in the data stream to obtain the product identification code; and finally configuring the target task based on the goods information indicated by the product identification code.

[0048] Specifically, for the data deduplication process, a data listening thread / coroutine can be started to continuously read the raw data stream from the target data channel. Alternatively, a hash set can be used to temporarily store the collected EPC codes in memory. The characteristic of a Set data structure is automatic deduplication; any duplicate EPC codes cannot be added again.

[0049] Optionally, a "collection time window" (e.g., 2 seconds) can be set to continuously collect and deduplicate data within this window. After the window ends, the final deduplicated set will be sent to the next step of processing.

[0050] Through the data cleaning and deduplication process, the raw and redundant RFID data stream is transformed into a clean and unique list of items, providing accurate basic data for subsequent business logic.

[0051] In addition, during the process of configuring target tasks based on cargo information indicated by product identification codes, cargo information can be verified. That is, due to the high concurrency of RFID reading operations in the target warehouse, it is necessary to avoid data flow errors and ensure the accuracy of the tag data read by RFID.

[0052] Specifically, the process begins by determining the quantity and status of goods corresponding to the product identification code to configure the goods information. Then, information verification is performed based on this information to obtain the verification result. If the verification result indicates successful verification, the target task corresponding to the product identification code is configured according to the quantity and status of the goods. Quantity verification is typically used for outbound operations. For example, if the system requires the outbound shipment of 100 items of product A, but only 95 of the scanned EPC codes belong to product A, the verification fails. Inventory status verification confirms the inbound and outbound status of items. For outbound verification, it checks whether the scanned product EPC is indeed "in stock" in the system, whether it is locked by other orders, and whether it has already been picked. If a product not belonging to the current order or not in an available state is scanned, it is considered abnormal. For inbound verification, it checks whether the scanned product EPC is the product the system expects to receive and whether it is already in stock (to prevent duplicate entries). This is done by interacting with the inventory database to query the real-time inventory status.

[0053] Therefore, the data verification process significantly reduces error rates such as incorrect shipments, incorrect receipts, and repetitive operations, improving the accuracy of warehousing operations. Furthermore, problems are detected in real-time at the operational site, allowing operators to correct them immediately, rather than waiting until later stages, thus saving costs.

[0054] 303. Input the target task into the task queue, and execute the inventory management process corresponding to the target warehouse based on the execution parameters corresponding to the task queue. The inventory management process is used to update the goods information corresponding to the target warehouse.

[0055] In this embodiment, due to the need for batch RFID tag reading in the target warehouse, high concurrency may occur; and while RFID acquisition and data verification may be very fast, subsequent database updates (inventory increases and decreases) are relatively slow I / O operations. Using a queue decouples "acquisition and verification" from "data persistence," preventing front-end acquisition from being blocked by the back-end database, thereby improving the overall system throughput and response speed.

[0056] Therefore, the task queue management process can be configured, which involves first inputting the target task into the task queue and determining the priority parameter corresponding to the target task; then, in response to the input of the execution parameter, obtaining the batch execution value; configuring the execution sequence corresponding to the task queue according to the priority parameter, and batch processing the tasks in the execution sequence through the batch execution value to execute the inventory management process corresponding to the target warehouse.

[0057] The priority parameter can be set on the fly or it can be a bid document for the task itself. A priority queue can handle business scenarios such as prioritizing urgent orders. The execution parameter indicates the mode of concurrent task processing. It can be a per-item mode, where the inventory is updated after each tag (or a small batch) is processed. This offers high real-time performance but puts significant pressure on the database. Alternatively, it can be a batch mode, where all validated data within a collection window (e.g., 2 seconds) is stored as a task in a queue, and then the database is updated in batches. This is more efficient and puts less pressure on the database.

[0058] Specifically, the task queue can be configured as a message queue middleware, such as RabbitMQ, Kafka, or Redis List / Stream. Its task message body includes: owner information, operation type (inbound / outbound), a list of verified EPCs, priority identifier, etc. This allows the WMS backend to configure a dedicated consumer service to retrieve tasks from the queue and execute the actual database inventory update operation.

[0059] Furthermore, considering the existence of multiple cargo owners in the target warehouse, RFID reading operations for the same cargo owner can be performed simultaneously to ensure consistency in the data verification process. Specifically, the execution sequence corresponding to the task queue is first configured according to priority parameters; then, the cargo owner code corresponding to each task in the execution sequence is determined, and the execution sequence is merged based on the cargo owner code; finally, batch processing of the tasks in the merged execution sequence is performed using batch execution values ​​to execute the inventory management process corresponding to the target warehouse.

[0060] The execution process of the task queue described above makes the WMS system more stable and resilient to pressure, preventing it from crashing due to short-term large data volumes. Furthermore, the task processing flow is clearer, supporting complex task scheduling strategies.

[0061] In another possible scenario, the information from the execution or verification process of the aforementioned task queue can be displayed as either abnormal or normal data. Specifically, first, the corresponding inventory change and abnormal information from the inventory management process is obtained; the inventory change information is categorized according to the owner's code and displayed in the first area corresponding to that code; then, the cause of the abnormal information is determined, and the abnormal goods and their causes are associated, which is then displayed in the second area.

[0062] Specifically, for the normal data displayed in the first area, items are dynamically added to the "Scanned" list on the UI, or the success count is updated. For the abnormal data displayed in the second area, the specific error reasons (such as "Product Not Found," "Quantity Incorrect," "Status Unavailable") are displayed in a prominent manner (e.g., red font, pop-up prompts, audible alarms). This improves operator efficiency and experience, allows for immediate error correction, and ensures the accuracy of data collection, thus enabling warehousing digitization and automation.

[0063] The above embodiments described the execution process based on RFID middleware. The following explanation, in conjunction with the interaction process between the RFID middleware and WMS, will illustrate this further. Figure 5 As shown, Figure 5 A schematic diagram illustrating another warehouse management method provided in one embodiment of this specification; the diagram shows the following steps: 501. The process of establishing a channel between the RFID middleware and the WMS front end.

[0064] In this embodiment, the channel establishment process involves responding to a device access request, dynamically matching the communication protocol based on the cargo owner code, and establishing a data channel. For details, please refer to the description of step 301, which will not be repeated here.

[0065] The WMS front-end provides the user interface (UI), serving as the entry point for operator interaction. Specifically, it displays the operational interface (such as "Inbound" and "Outbound" buttons, and a list of scanned data). It also initiates device control commands (such as "Start Scan" and "Stop Scan"). Furthermore, it receives and displays real-time collected data and processing results pushed by the RFID middleware service.

[0066] In addition, the RFID middleware maintains a "device configuration library" that records the communication protocol (USB / HTTP / WebSocket), parameters (COM port, IP address, port), model instruction set, etc., for each device (associated with the owner and storage location). For protocol adaptation, it has built-in drivers for multiple communication protocols. When it receives a request from the WMS frontend, it queries the configuration of the required device based on the "owner code" and dynamically calls the corresponding driver to establish a connection with the physical device. After establishing the connection, the RFID middleware continuously collects raw data from the physical reader, performs preliminary processing, and then actively pushes the processed data to the WMS frontend via WebSocket or other methods. Simultaneously, it also receives control commands from the frontend and forwards them to the physical devices. Furthermore, it manages multiple concurrent device connections, maintains stability, and handles abnormal situations such as disconnection and reconnection.

[0067] 502. Data input process between WMS front-end and WMS back-end.

[0068] In this embodiment, the data input process includes data deduplication and data verification. For data deduplication, RFID tag data is collected in real time through a selected protocol, and the collected EPC data is stored in the deduplication set; for data verification, the collected data is verified to check whether the quantity and inventory status match.

[0069] 503. Task execution process of WMS front-end and WMS back-end.

[0070] In this embodiment, the task execution process involves storing the verification results into a dynamic task queue according to priority, supporting both piece-by-piece and batch modes. Additionally, the processing results can be fed back, displaying updates for normal data and providing alerts for abnormal data.

[0071] As can be seen, by dynamically matching the owner's code and communication protocol through the interaction process between RFID middleware and WMS, a data channel is established, real-time collection and deduplication of EPC data is performed, and data accuracy is ensured by combining inventory status and quantity verification. Tasks are dynamically scheduled and processed through priority task queues, and finally, normal data is updated in real time and abnormal data is reported back, which significantly improves warehousing efficiency, reduces labor costs, and ensures the flexibility of device access and system stability through multi-protocol compatibility and hybrid communication architecture.

[0072] In summary, this embodiment, in response to a trigger operation on an RFID device in the target warehouse, acquires the tag data collected by the trigger operation. This tag data is accessed through a target data channel associated with the RFID device, and the target data channel is established using a communication protocol matched to the RFID device. The communication protocol is determined based on the owner code corresponding to the RFID device. The target warehouse contains RFID devices with different owner codes, and the RFID devices have multiple data access methods. Then, the product identification code indicated by the tag data is determined, and a target task is configured based on the cargo information indicated by the product identification code. The target task is then input into a task queue, and the corresponding inventory management process for the target warehouse is executed based on the execution parameters corresponding to the task queue. This inventory management process is used to update the cargo information for the target warehouse. This achieves batch management of RFID devices of different specifications. By dynamically matching the owner code and communication protocol to establish a data channel, complex interface adaptation processes are avoided. Furthermore, batch execution through a task queue can concurrently process the data requirements of different models of RFID devices, thereby improving the efficiency and convenience of updating cargo information during warehouse management.

[0073] It should be noted that the various embodiments described in this specification emphasize the parts that differ from other embodiments, and the embodiments can be explained by comparison with each other. Any combination of the various embodiments described in this specification based on general technical knowledge is covered within the scope of this specification.

[0074] In one exemplary embodiment of this specification, a warehouse management device 600 is also provided, such as... Figure 6 As shown, Figure 6 A functional module diagram of a warehouse management device provided according to one embodiment of this specification, the management device 600 includes: The acquisition unit 601 is used to acquire tag data collected by the triggering operation in response to a triggering operation of an RFID device in a target warehouse. The tag data is accessed through a target data channel associated with the RFID device. The target data channel is established using a communication protocol matched with the RFID device. The communication protocol is determined based on the cargo owner code corresponding to the RFID device. The target warehouse contains RFID devices with different cargo owner codes, and the RFID devices include multiple data access methods. The determining unit 602 is used to determine the product identification code indicated by the label data, and configure the target task based on the goods information indicated by the product identification code; The management unit 603 is used to input the target task into the task queue, and to execute the inventory management process corresponding to the target warehouse based on the execution parameters corresponding to the task queue. The inventory management process is used to update the goods information corresponding to the target warehouse.

[0075] Optionally, in one possible implementation, the acquisition unit 601 is specifically used to acquire the access request of the RFID device in the target warehouse through the RFID intermediate layer, and determine the access method information corresponding to the RFID device; The acquisition unit 601 is specifically used to configure a communication protocol based on the access method information, so as to establish a target data channel between the radio frequency identification intermediate layer and the warehouse management system using the communication protocol; The acquisition unit 601 is specifically used to associate the target data channel with the cargo owner code corresponding to the radio frequency identification device; The acquisition unit 601 is specifically used to respond to a trigger operation for a radio frequency identification (RFID) device in the target warehouse, trigger the RFID intermediate layer to determine the target data channel based on the cargo owner code, and acquire the tag data collected by the trigger operation through the target data channel.

[0076] Optionally, in one possible implementation, the determining unit 602 is specifically used to determine the data stream corresponding to the tag data; The determining unit 602 is specifically used to perform deduplication processing on the identification information contained in the data stream to obtain the product identification code; The determining unit 602 is specifically used to configure the target task based on the cargo information indicated by the product identification code.

[0077] Optionally, in one possible implementation, the determining unit 602 is specifically used to determine the quantity and status of goods corresponding to the product identification code, so as to configure the goods information; The determining unit 602 is specifically used to perform information verification based on the cargo information to obtain a verification result; The determining unit 602 is specifically used to configure the target task corresponding to the product identification code according to the quantity of goods and the status of goods if the verification result indicates that the verification is passed.

[0078] Optionally, in one possible implementation, the management unit 603 is specifically used to input the target task into the task queue and determine the priority parameter corresponding to the target task; The management unit 603 is specifically used to obtain batch execution values ​​in response to the input of the execution parameters; The management unit 603 is specifically used to configure the execution sequence corresponding to the task queue according to the priority parameter, and to perform batch processing on the tasks in the execution sequence through the batch execution value, so as to execute the inventory management process corresponding to the target warehouse.

[0079] Optionally, in one possible implementation, the management unit 603 is specifically configured to configure the execution sequence corresponding to the task queue according to the priority parameter; The management unit 603 is specifically used to determine the cargo owner code corresponding to each task in the execution sequence, so as to merge the tasks in the execution sequence based on the cargo owner code; The management unit 603 is specifically used to perform batch processing on the tasks in the execution sequence after merging tasks using the batch execution values, so as to execute the inventory management process corresponding to the target warehouse.

[0080] Optionally, in one possible implementation, the management unit 603 is specifically used to acquire corresponding inventory change information and abnormal information in the inventory management process; The management unit 603 is specifically used to classify the inventory change information according to the owner code and display it in the first area corresponding to the owner code; The management unit 603 is specifically used to determine the cause of the abnormality corresponding to the abnormal information, so as to associate the abnormal goods corresponding to the abnormal information with the cause of the abnormality and display them in the second area.

[0081] Specifically, the acquisition unit and management unit in this embodiment can correspond to physical components. For example, the processing unit can be a processing module such as a CPU, GPU, or FPGA. The specific physical component can be any component or combination of components with the above functions. The specific method depends on the actual scenario and is not limited here.

[0082] The aforementioned management device, in response to a trigger operation on an RFID device in the target warehouse, acquires the tag data collected by the trigger operation. This tag data is accessed through the target data channel associated with the RFID device, and the target data channel is established using a communication protocol matched with the RFID device. The communication protocol is determined based on the owner code corresponding to the RFID device. The target warehouse contains RFID devices with different owner codes, and the RFID devices support multiple data access methods. Then, the device determines the product identification code indicated by the tag data and configures a target task based on the cargo information indicated by the product identification code. The target task is then input into a task queue, and the corresponding inventory management process for the target warehouse is executed based on the execution parameters corresponding to the task queue. This inventory management process is used to update the cargo information for the target warehouse. This enables batch management of RFID devices of different specifications. By dynamically matching the owner code and communication protocol to establish a data channel, complex interface adaptation processes are avoided. Furthermore, batch execution through the task queue allows for concurrent processing of data requests from different models of RFID devices, thereby improving the efficiency and convenience of updating cargo information during warehouse management.

[0083] Specific limitations regarding the warehouse management device can be found in the limitations regarding warehouse management methods described above, and will not be repeated here. Each unit module in the aforementioned warehouse management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0084] Another embodiment of this application also proposes a computing device, see [link to relevant documentation] Figure 7 As shown, an exemplary embodiment of this specification also provides a computing device, including: a memory and a processor, the memory storing a computer program, the processor executing the computer program to perform the steps in the warehouse management method according to various embodiments of this specification described above.

[0085] The internal structure of the computing device can be as follows: Figure 7 As shown, the computing device includes a processor, memory, network interface, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it follows the steps of the warehouse management method according to various embodiments of this specification as described in the above embodiments.

[0086] The processor may include the main processor, as well as baseband chips, modems, etc.

[0087] The memory stores a program that executes the technical solution of this invention, and may also store an operating system and other critical business functions. Specifically, the program may include program code, which includes computer operation instructions. More specifically, the memory may include read-only memory (ROM), other types of static storage devices capable of storing static information and instructions, random access memory (RAM), other types of dynamic storage devices capable of storing information and instructions, disk storage, flash memory, etc.

[0088] The processor can be a general-purpose processor, such as a general-purpose central processing unit (CPU), a microprocessor, etc., or an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present invention. It can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0089] Input devices may include devices that receive data and information input by the user, such as keyboards, mice, cameras, scanners, light pens, voice input devices, touch screens, pedometers, or gravity sensors.

[0090] Output devices may include devices that allow information to be output to the user, such as displays, printers, speakers, etc.

[0091] The communication interface may include any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0092] The processor executes programs stored in memory and calls other devices, which can be used to implement various steps of any of the warehouse management methods provided in the above embodiments of this application.

[0093] The computing device may also include a display component and a voice component. The display component may be a liquid crystal display screen or an e-ink display screen. The input device of the computing device may be a touch layer covering the display component, or a button, trackball or touchpad set on the casing of the computing device, or an external keyboard, touchpad or mouse, etc.

[0094] Those skilled in the art will understand that Figure 7 The structures shown are merely block diagrams of some structures related to the solutions in this specification and do not constitute a limitation on the computing devices on which the solutions in this specification are applied. Specific computing devices may include more or fewer components than those shown in the figures, or combine certain components, or have different component arrangements.

[0095] In addition to the methods and devices described above, the warehouse management methods provided in the embodiments of this specification can also be computer program products, which include computer programs that, when run by a processor, cause the processor to perform the steps in the warehouse management methods according to various embodiments of this specification as described in the "Exemplary Methods" section above.

[0096] The computer program product described herein can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments described herein. These programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0097] Furthermore, embodiments of this specification also provide a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor of the steps in the warehouse management method according to various embodiments of this specification as described in the "Exemplary Methods" section above.

[0098] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this specification can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0099] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0100] The embodiments described above are merely illustrative of several implementation methods outlined in this specification. While the descriptions are specific and detailed, they should not be construed as limiting the scope of the solutions provided in this specification. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this specification, and these all fall within the scope of protection of this specification. Therefore, the scope of protection for this patent should be determined by the appended claims.

Claims

1. A method of managing a warehouse, characterized by, The application relates to a warehouse management method and device. In response to a trigger operation on a radio frequency identification device in a target warehouse, label data collected by the trigger operation is acquired through a target data channel associated with the radio frequency identification device, the target data channel is established by using a communication protocol matched with the radio frequency identification device, the communication protocol is determined based on a cargo owner code corresponding to the radio frequency identification device, the target warehouse contains radio frequency identification devices with different cargo owner codes, and the radio frequency identification devices contain multiple data access modes. A product identification code indicated by the label data is determined, and a target task is configured based on cargo information indicated by the product identification code. The target task is input into a task queue, and an inventory management process corresponding to the target warehouse is executed based on execution parameters corresponding to the task queue, the inventory management process being used for updating cargo information corresponding to the target warehouse.

2. The method of claim 1, wherein, In response to a trigger operation on a radio frequency identification device in a target warehouse, label data collected by the trigger operation is acquired through a target data channel associated with the radio frequency identification device, the target data channel is established by using a communication protocol matched with the radio frequency identification device, the communication protocol is determined based on a cargo owner code corresponding to the radio frequency identification device, the target warehouse contains radio frequency identification devices with different cargo owner codes, and the radio frequency identification devices contain multiple data access modes. The application relates to a warehouse management method and device. Access request of radio frequency identification device in target warehouse is acquired through radio frequency identification intermediate layer, and access mode information corresponding to the radio frequency identification device is determined. A communication protocol is configured based on the access mode information, so that a target data channel between the radio frequency identification intermediate layer and a warehouse management system is established by using the communication protocol. The target data channel is associated with the cargo owner code corresponding to the radio frequency identification device.

3. The method of claim 1, wherein, In response to a trigger operation on a radio frequency identification device in a target warehouse, label data collected by the trigger operation is acquired through a target data channel associated with the radio frequency identification device, the target data channel is established by using a communication protocol matched with the radio frequency identification device, the communication protocol is determined based on a cargo owner code corresponding to the radio frequency identification device, the target warehouse contains radio frequency identification devices with different cargo owner codes, and the radio frequency identification devices contain multiple data access modes. The application relates to a warehouse management method and device. Data flow corresponding to the label data is determined. Redundancy processing is performed on identification information contained in the data flow, so that the product identification code is obtained.

4. The method of claim 3, wherein, A target task is configured based on cargo information indicated by the product identification code. The application relates to a warehouse management method and device. The target task is input into a task queue, and a priority parameter corresponding to the target task is determined. In response to input of the execution parameter, a batch execution value is acquired.

5. The method of claim 1, wherein, An execution sequence corresponding to the task queue is configured according to the priority parameter, and tasks in the execution sequence are batch processed through the batch execution value, so that the inventory management process corresponding to the target warehouse is executed. ​ ​ ​ 6. The method of claim 5, wherein, The execution sequence corresponding to the task queue is configured according to the priority parameter, and the tasks in the execution sequence are batch processed through the batch execution value to execute the inventory management process corresponding to the target warehouse, including: The execution sequence corresponding to the task queue is configured according to the priority parameter; The owner code corresponding to each task in the execution sequence is determined to merge tasks in the execution sequence based on the owner code; The tasks in the execution sequence after merging are batch processed through the batch execution value to execute the inventory management process corresponding to the target warehouse.

7. The method according to any one of claims 1 to 6, characterized in that, The method further comprises: Obtaining the corresponding inventory change information and abnormal information in the inventory management process; Classifying the inventory change information according to the owner code and displaying it in the first area corresponding to the owner code; Determine the abnormal reason corresponding to the abnormal information, and associate the abnormal goods corresponding to the abnormal information with the abnormal reason and display it in the second area.

8. A management device for warehousing, characterized by, Comprise: An acquisition unit is configured to, in response to a trigger operation for a radio frequency identification device in a target warehouse, acquire tag data collected by the trigger operation, the tag data being accessed through a target data channel associated with the radio frequency identification device, the target data channel being established using a communication protocol matching the radio frequency identification device, the communication protocol being determined based on the owner code corresponding to the radio frequency identification device, the target warehouse containing radio frequency identification devices with different owner codes, and the radio frequency identification device containing multiple data access modes; A determination unit is configured to determine a product identification code indicated by the tag data and configure a target task based on the product information indicated by the product identification code; A management unit is configured to input the target task into a task queue to execute an inventory management process corresponding to the target warehouse based on the execution parameters corresponding to the task queue, the inventory management process being used to update the product information corresponding to the target warehouse.

9. A computing device, comprising: A computer program is stored on the memory and executable on the processor, and the processor executes the computer program to implement the warehouse management method of any one of claims 1-7.

10. A computer program product, characterised in that, Comprise: A computer program is stored on the memory and executable on the processor, and the processor executes the computer program to implement the warehouse management method of any one of claims 1-7.

Images