Container merging method, container merging device, electronic equipment and storage medium

Abstract

The invention provides a container merging method, a container merging device, electronic equipment and a storage medium, and belongs to the technical field of data processing. The method comprises the steps of obtaining container inventory data of a plurality of to-be-merged containers in a target storage area; dividing the plurality of to-be-combined containers according to the container inventory data to obtain a same-dimension container set and a mixed-dimension container set; traversing and merging the same-dimension container groups in the same-dimension container set according to the container inventory data to obtain same-dimension container merged data; after the to-be-merged containers in the same-dimension container group are merged, traversing and merging the to-be-merged containers in the mixed-dimension container set according to the container inventory data to obtain mixed-dimension container merged data; and generating a target tallying list according to the same-dimension container merged data and the mixed-dimension container merged data. According to the embodiment of the invention, the container merging efficiency and accuracy can be improved, so that the overall warehouse storage efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a container merging method, a container merging device, an electronic device and a storage medium. BACKGROUND

[0002] In an automated warehousing project, a container is a storage unit that can store one or more batches of goods. For example, in the sorting scenario in the logistics field, the container can be used as the basic unit for automated operation, that is, one container can store one or more batches (such as goods of the same production cycle or purchased at the same time) of goods. Currently, when storing based on containers, the containers are usually put into the warehouse and placed on the shelves at a designated location, and then subsequent picking operations are performed until the inventory of the container is finally consumed, and the container can be released.

[0003] However, in batch operations, due to the consumption of different container picking operations, there will be many scattered inventories that do not have much inventory but still occupy containers. At this time, if this part of data is not sorted, it will reduce the efficiency of container-based storage. Based on this, the related art usually uses manual sorting to screen the corresponding containers, combines the screened containers, and transports the containers to the workstation in the order of the containers by the transportation equipment, so as to find and locate the target container by manual selection to combine. However, this way of manually selecting and locating the combined containers is inefficient and has large errors. SUMMARY

[0004] The main purpose of the embodiments of the present application is to provide a container merging method, a container merging device, an electronic device and a storage medium, which can improve the efficiency and accuracy of container merging, thereby improving the efficiency of overall warehouse storage.

[0005] To achieve the above purpose, a first aspect of the embodiments of the present application provides a container merging method, which comprises: obtaining container inventory data of a plurality of to-be-merged containers in a target warehousing area, the container inventory data being used to indicate current storage information in the corresponding to-be-merged container; performing container division on the plurality of to-be-merged containers according to the container inventory data to obtain a same-dimension container set and a mixed-dimension container set, the same-dimension container set comprising a same-dimension container group, and the to-be-merged containers in the same same-dimension container group having the same inventory dimension information; performing traversal merging on the same-dimension container groups in the same-dimension container set according to the container inventory data to obtain same-dimension container merging data; after the to-be-merged containers in the same-dimension container group are merged and processed, performing traversal merging on the to-be-merged containers in the mixed-dimension container set according to the container inventory data to obtain mixed-dimension container merging data; and generating a target sorting list according to the same-dimension container merging data and the mixed-dimension container merging data.

[0006] To achieve the above object, a second aspect of the embodiment of the present application provides a container merging device, which comprises: an acquisition module, configured to acquire container inventory data of a plurality of to-be-merged containers in a target storage area, the container inventory data being used to indicate current inventory information stored in the corresponding to-be-merged container; a container division module, configured to divide the plurality of to-be-merged containers according to the container inventory data, to obtain a same-dimension container set and a mixed-dimension container set, the same-dimension container set comprising a same-dimension container group, and the to-be-merged containers in the same same-dimension container group corresponding to the same inventory dimension information; a first merging module, configured to perform iterative merging on the same-dimension container groups in the same-dimension container set according to the container inventory data, to obtain same-dimension container merging data; a second merging module, configured to perform iterative merging on the to-be-merged containers in the mixed-dimension container set according to the container inventory data after the to-be-merged containers in the same-dimension container groups are merged, to obtain mixed-dimension container merging data; and a generation module, configured to generate a target inventory list according to the same-dimension container merging data and the mixed-dimension container merging data.

[0007] To achieve the above object, a third aspect of the embodiment of the present application provides an electronic device, which comprises a memory and a processor, the memory storing a computer program, and the processor implementing the method of any one of the above-mentioned first aspect embodiments when executing the computer program.

[0008] To achieve the above object, a fourth aspect of the embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the computer program implements the method of any one of the above-mentioned first aspect embodiments when executed by a processor.

[0009] The container merging method, the container merging device, the electronic device and the storage medium provided by the embodiment of the present application can first divide the plurality of to-be-merged containers according to the container inventory data when performing container merging on the plurality of to-be-merged containers in the target storage area, to obtain the same-dimension container set and the mixed-dimension container set, and then perform differential merging analysis based on the same-dimension container set and the mixed-dimension container set. Further, the embodiment of the present application can first perform iterative merging on the same-dimension container groups in the same-dimension container set according to the container inventory data to obtain the same-dimension container merging data, and then perform iterative merging on the to-be-merged containers in the mixed-dimension container set according to the container inventory data to obtain the mixed-dimension container merging data, so as to generate the target inventory list containing the merging operation of the plurality of to-be-merged containers according to the same-dimension container merging data and the mixed-dimension container merging data. In this way, the embodiment of the present application can improve the efficiency and accuracy of container merging by performing separate iterative merging on the container groups of different dimension types, thereby improving the efficiency of overall warehouse storage. BRIEF DESCRIPTION OF DRAWINGS

[0010] Figure 1is a process schematic diagram of the container merging in the way of the manual container handling adopted by the related art; Figure 2 is a first flowchart of the container merging method provided by the embodiment of the present application; Figure 3 is Figure 2 is a flowchart of step S230 in Figure 4 is a flowchart of determining the current container to be merged and other containers of the same dimension provided by the embodiment of the present application; Figure 5 is a flowchart of determining the first merging detection data corresponding to the current container to be merged provided by the embodiment of the present application; Figure 6 is a specific flowchart of the traversal merging of the same dimension container group in the same dimension container set provided by the embodiment of the present application; Figure 7 is Figure 2 is a flowchart of step S240 in Figure 8 is a specific flowchart of the traversal merging of the container to be merged in the mixed dimension container set provided by the embodiment of the present application; Figure 9 is Figure 2 is a flowchart of step S250 in Figure 10 is a flowchart of the container delivery provided by the embodiment of the present application; Figure 11 is a specific flowchart of the workstation allocation based on the target container provided by the embodiment of the present application; Figure 12 is a structural schematic diagram of the container merging device provided by the embodiment of the present application; Figure 13 is a hardware structural schematic diagram of the electronic device provided by the embodiment of the present application. DETAILED DESCRIPTION

[0011] In order to make the purpose, technical scheme and advantages of the present application more clear, the present application is further described in detail below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

[0012] It should be noted that although the functional modules are divided in the device schematic diagram, and the logical sequence is shown in the flowchart, in some cases, the steps shown or described can be performed in a manner different from the module division in the device or the sequence in the flowchart. The terms "first", "second", and the like in the specification and claims and the above-described drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as understood by those skilled in the art to which the present application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0013] In an automated warehousing project, a container is a storage unit that can store one or more batches of goods. For example, in the sorting scenario in the logistics field, the container can be used as the basic unit for automated operation, that is, one container can store one or more batches (such as goods of the same production cycle or purchased at the same time) of goods. Currently, when storing based on containers, the container is usually put into storage on the shelf at a designated location, and then subsequent picking operations are performed until the container is finally consumed, and the container can be released.

[0014] However, in batch operations, due to the consumption of different container picking operations, there will be many scattered inventories that do not have much inventory but still occupy containers. At this time, if this part of the data is not combined through inventory, the efficiency of container-based storage will be reduced. Container combination refers to the process of combining containers with low inventory occupancy. Inventory refers to the combination of containers with low inventory occupancy to achieve this. By combining containers with low storage rates during idle time, containers and storage locations are released, which can improve warehouse storage capacity and reduce the number of equipment transfers, thereby improving overall efficiency and storage.

[0015] Therefore, the related art usually adopts a manual inventory method, that is, manually exporting inventory data, filtering according to quantity information, selecting corresponding containers, combining the selected containers, and transporting the containers to the workstation by the transportation device according to the order of the containers, and selecting containers with the same batch of goods and less quantity for combination. The device executes according to the order of the containers, and after arriving at the station, the operator needs to find the containers and manually combine the corresponding containers. As shown in Figure 1 , it is a process schematic diagram of the container combination by the manual inventory method adopted by the related art. Specifically, the related art selects containers that need to be combined (such as containers 1 to 3 shown in Figure 1 ) by manual selection, and then estimates the data by manually selecting the inventory to achieve manual combination to obtain the combined container 1 as shown in the figure.

[0016] However, this way of manually selecting the container and positioning the merging container needs manual selection of the inventory and estimation of data, which is prone to inaccurate data estimation and low efficiency of manual searching for goods. Therefore, the container merging method adopted by the related art has low efficiency and large error.

[0017] Therefore, embodiments of the present application provide a container merging method, a container merging device, an electronic device and a storage medium, which can improve the efficiency and accuracy of container merging, thereby improving the efficiency of overall warehouse storage.

[0018] The container merging method provided by the embodiments of the present application relates to the technical field of data processing and warehouse storage. The container merging method provided by the embodiments of the present application can be applied to a terminal, can be applied to a server end, and can also be software running in the terminal or the server end. In some embodiments, the terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, etc. The server end can be configured as a stand-alone physical server, can be configured as a server cluster or a distributed system composed of multiple physical servers, can also be configured as a cloud server providing basic cloud computing services such as cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, content delivery network (CDN), and big data and artificial intelligence platform, etc. The software can be an application that implements the container merging method, but is not limited to the above forms.

[0019] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network personal computers (PCs), minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in a distributed computing environment, in which tasks are performed by remote processing devices connected by a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0020] Please refer to Figure 2 , Figure 2is an optional flowchart of the container merging method provided by the embodiment of the present application. In some embodiments of the present application, the method can specifically include but is not limited to steps S210 to S250, which are described below in combination with Figure 2 The five steps are described in detail.

[0021] Step S210, obtaining container inventory data of a plurality of to-be-merged containers in a target storage area; Step S220, performing container division on the plurality of to-be-merged containers according to the container inventory data, to obtain a same-dimension container set and a mixed-dimension container set, and the same-dimension container set includes a same-dimension container group; Step S230, performing traversal merging on the same-dimension container group in the same-dimension container set according to the container inventory data, to obtain same-dimension container merging data; Step S240, after the to-be-merged containers in the same-dimension container group are merged, performing traversal merging on the to-be-merged containers in the mixed-dimension container set according to the container inventory data, to obtain mixed-dimension container merging data; Step S250, generating a target inventory list according to the same-dimension container merging data and the mixed-dimension container merging data.

[0022] In step S210 of some embodiments, the target storage area refers to a specific warehouse area that needs to be operated, which can be a specific shelf area, a temporary storage area, or a surrounding area of a pallet station, etc. The to-be-merged container refers to a storage unit that needs to be merged, including a box, a pallet, a material box, etc., which can have an identifier (such as a barcode, an RFID), and the merging can be triggered by space optimization, order integration, or inventory adjustment requirements. The to-be-merged container in the embodiment of the present application refers to a container that can be merged after being selected by a preset screening condition. It can be understood that the embodiment of the present application can screen the containers containing inventory data according to the configuration information such as manually selected different information and merging mode, and select the to-be-merged containers meeting the conditions.

[0023] The container inventory data is a multi-dimensional information set for indicating the current inventory information stored in the corresponding to-be-merged container, which is structured data describing the details of goods in the container, and can generally include SKU code (i.e., product code, indicating the minimum inventory unit, and a SKU can be used to uniquely identify a saleable product), product name, batch number, production date, expiration date, quantity, storage requirements (such as temperature and humidity), and the like. The embodiments of the present application can collect the container inventory data of all to-be-merged containers in the target storage area in real time through the database interface of the Internet of Things sensing device (such as a UHF RFID reader, a two-dimensional code scanning gun, etc.) or a warehouse execution system (WES). In implementation, the RFID tags of the pallets can be read in batches by a fixed reader, or the data can be obtained by scanning the two-dimensional code of the box container by the AGV robot carrying a vision sensor, and after cleaning (removing duplicate and error data) and formatting (unifying units and code conversion), all data are stored in a time series database (such as InfluxDB) or a distributed database (such as HBase) for subsequent analysis, to ensure the real-time and accuracy of the data.

[0024] It should be noted that the preset screening condition for screening the container in the embodiments of the present application refers to a condition for screening based on the related information of the inventory goods in the container, and can specifically include the type, batch, and product volume of the inventory goods contained in the merged container. For example, as shown in Table 1 below, rules for the volume of the containers contained in different types of merged containers are set.

[0025] Table 1

[0026] In Table 1, the first column indicates different types of containers, such as "two-in-one", which means two containers are merged into one container. The second column indicates the minimum value of the volume that each container contained in the merged container can occupy, and the unit is %, which represents the proportion of the entire merged container. The third column indicates the maximum value of the volume that each container contained in the merged container can occupy, and the unit is %, which represents the proportion of the entire merged container. The third column indicates the number of containers that can be merged in the merged container, N1 represents the number of containers that can be contained, and N1 is a positive integer greater than 4.

[0027] For example, as shown in Table 2 below, rules for the volume of different types of containers are set.

[0028] Table 2

[0029] In Table 2, the first column indicates the number of product categories (inventory types) that can be contained in a container, N2 indicates the number of product categories that can be contained, and N2 is a positive integer greater than 2. The second column indicates the proportion of the container volume that can be used in a combined container to the entire container volume. For example, when the product category is 1, it means that only one kind of product is stored in the container, and the container volume utilization rate can reach 95%, i.e., 95% of the container volume can be used; when the product category is 2, the container volume utilization rate is only 90%.

[0030] It should be noted that the embodiments of the present application can filter the inventory data that meets the conditions according to the preset screening conditions (i.e., screening rules) proposed in the above embodiments and the data information selected by manual order building. If the corresponding information is manually specified, the merging is limited to the screening within the manually filled content, and if no filling is performed, all data is screened. Specifically, the product information, batch information (if the product is empty or the batch is empty, it is ignored), length, width, height, and number A1 to An of different products in the container (n is the product number in a container) can be filled to determine whether they meet the configuration conditions with the volume of the combined container. For example, for a two-in-one type of combined container, B*25%<=A1+...+An<=B*50%, only the containers that meet the conditions are selected as the containers to be combined. In step S220 of some embodiments, this step is an intelligent classification of the disordered containers to be combined based on preset rules and algorithms, i.e., by dividing the containers into the same dimension container set or mixed dimension container set through the inventory dimension information in the container inventory data. The same dimension container set refers to a set composed of multiple same dimension container groups, and the inventory dimension information of the containers to be combined in the same same dimension container group is the same. The same dimension container group is a core concept, which specifically refers to all the containers to be combined in the group having only one same inventory (e.g., all containers containing the same SKU and requiring the same temperature layer). The mixed dimension container set contains all containers with different dimensions that cannot be classified into any same dimension container group. It can be understood that if the number of product categories in a container is greater than 1, it will be classified into the mixed dimension container set.

[0031] It should be noted that the embodiments of the present application can first extract the dimension feature vector corresponding to the inventory dimension information of each container to be combined, and then use a clustering algorithm (such as K-means or DBSCAN) for rapid preliminary screening. For clear and discrete dimensions (such as SKU codes themselves), accurate matching based on rules can be used for review and grouping to output a container list with clear grouping labels (such as same dimension container group A, same dimension container group B, and mixed dimension group M), which lays a foundation for subsequent differentiated merging strategies.

[0032] In step S230 of some embodiments, after the same-dimension container set and the mixed-dimension container set are divided, the same-dimension container groups in the same-dimension container set can be traversed and merged first, which means that WES automatically processes each same-dimension container group in the set in sequence. For each same-dimension container group, the algorithm provided by the embodiments of the present application can aggregate the inventory information of all containers in each same-dimension container group, and calculate the optimal merging scheme according to the set algorithm rule, and output the same-dimension container merging data. The same-dimension container merging data records the merging recommendation result of each same-dimension container group, for example, "merge containers C1, C2, C3 in group A to a new container T1".

[0033] Please refer to Figure 3 , Figure 3 is a flowchart of step S230 provided by the embodiments of the present application. In some embodiments, the specific process of step S230 can include but is not limited to steps S310 to S360, which will be described in detail below in combination with Figure 3 the six steps.

[0034] Step S310, determining a current same-dimension container group from the same-dimension container set, and extracting first inventory attribute data from the container inventory data corresponding to the to-be-merged containers of the current same-dimension container group; Step S320, determining a current to-be-merged container and other same-dimension containers from the current same-dimension container group, and performing container merging detection on the current to-be-merged container and the other same-dimension containers according to the first inventory attribute data and the first preset merging rule, to obtain first merging detection data corresponding to the current to-be-merged container; Step S330, updating the current to-be-merged container and the other same-dimension containers according to the first merging detection data and the current same-dimension container group, and determining first merging detection data corresponding to the updated current to-be-merged container; Step S340, performing data merging on the first merging detection data corresponding to all to-be-merged containers in the current same-dimension container group, to obtain same-dimension container merging sub-data corresponding to the current same-dimension container group; Step S350, updating the current same-dimension container group according to the same-dimension container set, and determining same-dimension container merging sub-data corresponding to the updated current to-be-merged container; Step S360, performing data merging on the same-dimension container merging sub-data corresponding to all same-dimension container groups in the same-dimension container set, to obtain same-dimension container merging data.

[0035] In step S310 of some embodiments, the embodiments of the present application can first determine a current same-dimension container group from the same-dimension container groups of the same-dimension container set (a set composed of same-dimension containers to be merged with all inventory dimension information being completely same and only one kind of inventory), the current same-dimension container group refers to the same-dimension container group that is currently being processed. Further, the corresponding first inventory attribute data is extracted from the container inventory data of each container to be merged in the current same-dimension container group. The first inventory attribute data refers to the key inventory feature information used to judge the feasibility of container merging, which can include inventory volume sub-data and inventory type sub-data. The inventory volume sub-data is used to represent the container volume occupied by the inventory contained in each container to be merged in the current same-dimension container group. The inventory type sub-data is used to represent the type and quantity of the inventory contained in each container to be merged in the current same-dimension container group. The embodiments of the present application can better guarantee the accuracy of container merging by accurately identifying and extracting the core attributes that affect the merging decision.

[0036] In step S320 of some embodiments, the embodiments of the present application can distinguish the current container to be merged and other same-dimension containers from the current same-dimension container group. The current container to be merged refers to the container to be merged as the starting point or current focus of the merging operation, and the other same-dimension containers refer to all other containers in the current same-dimension container group except the current container to be merged. The first preset merging rule refers to a set of logical conditions configured in advance for judging whether the same-dimension containers can be merged, such as remaining capacity check, quantity summation, state compatibility, etc.

[0037] The first preset merging rule can include a first merging category limiting rule, a first merging volume limiting rule, and a first merging container quantity limiting rule. The first merging category limiting rule refers to a limiting condition about the category of goods contained in the container when the containers in the same dimension container group are merged, that is, the number of categories of goods contained in the merged container needs to be less than the limited number of categories of goods. In this way, it can be ensured that the merged container is compatible in nature, avoiding quality problems, management confusion, or violation of safety standards that may be caused by mixing different characteristics of goods. The first merging volume limiting rule specifies that the total capacity or total carrying capacity of the merged container cannot exceed its physical limit or the safety threshold set by WES. In this way, it can be ensured that the merged container is physically feasible and safe to operate. The first merging volume limiting rule includes that the sum of the volumes of the goods after merging is less than or equal to the volume ratio of the container (see the table above), and the volume of the single batch of goods contained therein needs to be less than the volume ratio of a single compartment. The volume ratio of a single compartment refers to the volume ratio of each container in the container, for example, when 3 types of goods can be placed in the merged container, the container can be divided into 3 parts, and each type of goods can occupy only 1 / 3 of the whole. The first merging container quantity limiting rule specifies that the maximum number of containers receiving goods from the to-be-merged containers in a merging operation. In this way, the complexity of the merging operation can be controlled, and efficiency and risk can be balanced.

[0038] It should be noted that the specific rules included in the first preset merging rule can be flexibly set according to actual needs. For example, if the number of containers is simply selected, only the corresponding number of containers can be merged according to the number of containers.

[0039] The first merging detection data refers to structured data containing detection results, which can include the labels corresponding to the to-be-merged containers that can be merged in the current same dimension container group, the labels corresponding to the to-be-merged containers that cannot be merged, and the warning or error information that can be triggered. It should be noted that the to-be-merged containers that do not meet the same dimension merging condition can be added to the mixed dimension container set.

[0040] Please refer to Figure 4 , Figure 4 is a flowchart provided by the embodiment of the present application for determining the current to-be-merged container and other same dimension containers. In some embodiments, the specific process of determining the current to-be-merged container and other same dimension containers from the current same dimension container group can include but is not limited to steps S410 to S420, which will be described in detail below Figure 4 The two steps will be described in detail.

[0041] In step S410, the to-be-merged containers in the current same dimension container group are arranged in ascending order according to the inventory volume sub-data, and a same dimension container sequence is obtained. Step S420, taking the first to-be-merged container in the same-dimension container sequence as the current to-be-merged container and the remaining to-be-merged containers as other same-dimension containers.

[0042] In step S410 and step S420 of some embodiments, the embodiments of the present application can sort the to-be-merged containers in the current same-dimension container group in ascending order of volume. It should be noted that the container volumes of the to-be-merged containers in the embodiments of the present application are the same. Further, the to-be-merged container with the smallest inventory volume can be merged first, which is taken as the current to-be-merged container, and the remaining to-be-merged containers are taken as other same-dimension containers, and the largest container combination that can be merged with the current to-be-merged container is found through traversal comparison.

[0043] Please refer to Figure 5 , Figure 5 is a flowchart provided by the embodiments of the present application for determining the first merging detection data corresponding to the current to-be-merged container. In some embodiments, the specific process of determining the first merging detection data corresponding to the current to-be-merged container can include but is not limited to steps S510 to S530, which will be described below in combination with Figure 5 The three steps will be described in detail.

[0044] Step S510, obtaining the first volume data corresponding to the current to-be-merged container and the second volume data corresponding to the other same-dimension containers according to the first inventory attribute data; Step S520, selecting a candidate to-be-merged container from the other same-dimension containers according to the volume sum of the first volume data and the second volume data; Step S530, performing container merging detection on the current to-be-merged container and the candidate to-be-merged container according to the first merging type limitation rule, the first merging volume limitation rule, and the first merging container number limitation rule, to obtain the first merging detection data corresponding to the current to-be-merged container.

[0045] In step S510 of some embodiments, the inventory volume sub-data corresponding to the current to-be-merged container can be named as the first volume data, and the inventory volume sub-data corresponding to the other same-dimension containers can be named as the second volume data.

[0046] In step S520 of some embodiments, when traversing the current same-dimension container group in which the current to-be-merged container is located, the to-be-merged container with the largest inventory volume in the same-dimension container sequence can be compared with the current to-be-merged container for container merging detection first, and the comparison can be performed in reverse order. This way of combining the to-be-merged container with smaller inventory volume with the to-be-merged container with larger inventory volume can make the number of combined containers more balanced, and because if the containers are combined in ascending order, the to-be-merged container with larger inventory volume will have fewer combined containers, resulting in unbalanced container combination.

[0047] Further, when selecting a candidate container to be merged that can be merged with the current container to be merged, the first merging volume limiting rule needs to be met first. At this time, the first merging volume limiting rule includes: (1) the volume addition (i.e. the container sum between the two containers currently being judged) is less than or equal to the maximum volume allowed by the merging container; (2) the volume addition is greater than the sum of the volumes of the current container to be merged and other containers of the same dimension. This process is equivalent to the first round of rough screening of the container merging operation, which can be based on the most core physical capacity constraint for fast matching, greatly reducing the range of subsequent fine detection and improving the overall processing efficiency.

[0048] In step S530 of some embodiments, after determining the candidate container to be merged, the embodiments of the present application can further perform container merging detection on the current container to be merged and the candidate container to be merged according to the first merging category limiting rule, the first merging volume limiting rule and the first merging container quantity limiting rule, i.e. judging whether the total number of goods categories of the current container to be merged and the candidate container to be merged is less than or equal to the upper limit of the number of goods categories specified by the merging container, whether the volume sum of the current container to be merged and the candidate container to be merged is less than or equal to the volume ratio requirement specified by the merging container (see the table above for the ratio relationship), and whether the volume of a single good after merging is less than the volume ratio of a single compartment specified by the merging container; whether the number of containers after merging the current container to be merged and the candidate container to be merged is less than or equal to the upper limit of the number of containers in the same group specified by the merging container, to determine whether the current container to be merged and the candidate container to be merged can be merged. Further, if the current container to be merged and the candidate container to be merged can meet the above limiting rules, the current container to be merged and the candidate container to be merged can be merged, and the first merging detection data of the current container to be merged with respect to the current candidate container to be merged is obtained.

[0049] In the above embodiments, the embodiments of the present application provide intelligent, multi-dimensional feasibility detection and decision-making before the merging operation of containers with the same inventory dimension information in WES. The dynamic volume data of the containers is accurately calculated to lay a quantitative foundation for the physical feasibility of merging, and then the calculation efficiency and accuracy of the container merging are improved through fast rough screening based on the volume sum.

[0050] In step S330 of some embodiments, after determining the first merging detection data of the current container to be merged with respect to the current candidate container to be merged, if the first merging detection data indicates that the candidate container to be merged can be merged with the current container to be merged, the information of the candidate container to be merged after being merged with the current container to be merged can be taken as a new current container to be merged, and a judgment of merging the new current container to be merged with the next candidate container to be merged can be performed. If the first merging detection data indicates that the candidate container to be merged cannot be merged with the current container to be merged, a judgment of merging the current container to be merged with the next candidate container to be merged can be performed. When all candidate containers to be merged related to the latest current container to be merged are judged, the first merging detection data corresponding to the latest current container to be merged can be obtained, that is, the information of the container to be merged with the current container to be merged is determined. Further, after the container merging detection of the current container to be merged is completed, the next container to be merged in the current same-dimension container group can be selected as the current container to be merged based on the ascending order of the same-dimension container sequence, the other same-dimension containers are updated, and the first merging detection data corresponding to the updated current container to be merged is determined according to the above container merging detection process.

[0051] It should be noted that if the container to be merged in the current same-dimension container group is not assigned to a mergable container, the container to be merged can be added to the mixed-dimension container set, so as to facilitate subsequent mixed goods merging judgment.

[0052] In step S340 of some embodiments, the above steps are an iterative and optimization process. After obtaining the first merging detection data corresponding to all containers to be merged in the current same-dimension container group, the data can be combined to obtain the same-dimension container merging sub-data corresponding to the current same-dimension container group, so as to ensure the real-time and accuracy of the merging detection.

[0053] In step S350 of some embodiments, the current same-dimension container group can be updated according to the processing state of the entire same-dimension container set (i.e., the collection of all same-dimension container groups to be processed), for example, after the current same-dimension container group is processed, the current same-dimension container group is marked as “processed”, and the next unprocessed same-dimension container group in the same-dimension container set is selected as a new current same-dimension container group. Further, the above steps S320 to S340 can be performed according to the updated current same-dimension container group, so as to obtain the same-dimension container merging sub-data corresponding to each same-dimension container group in the same-dimension container set.

[0054] In step S360 of some embodiments, by traversing all homodimensional container groups (i.e., all container groups with the same inventory dimension information) in the homodimensional container set respectively generated homodimensional container merging sub-data (i.e., the result data obtained after independent intra-group merging of each homodimensional container group), and performing integration and data merging operations on all these merging sub-data, homodimensional container merging data corresponding to the homodimensional container set can be obtained. Data merging is a data aggregation calculation, such as summation, averaging, list merging, etc., rather than the merging of physical containers. Homodimensional container merging data refers to a data set that finally represents the overall result of the merging operation in the entire homodimensional container set, including inventory total amount summary after merging of all homodimensional container groups, list of all new container numbers involved, status report of the overall merging task, etc.

[0055] For example, refer to Figure 6 , Figure 6 is a specific flowchart provided by the embodiments of the present application for traversing and merging homodimensional container groups in a homodimensional container set. The process of traversing and merging homodimensional container groups in the homodimensional container set can specifically include but is not limited to the following steps S601 to S613: Step S601, grouping and merging the selected multiple containers to obtain a homodimensional container set and a mixed-dimension container set.

[0056] In WES, the embodiments of the present application can group and merge the selected containers into different groups according to the same commodity and batch dimension, and add the containers that cannot be merged into the mixed-dimension container set. If the selected containers themselves have more than one commodity type (statistical inventory number), they can be directly added to the mixed-dimension container set.

[0057] Step S602, grouping and merging according to the same commodity and batch dimension; Step S603, for each homodimensional container group, sorting the same commodity and batch according to volume from small to large.

[0058] In the embodiments of the present application, container merging detection can be performed on each homodimensional container group in the homodimensional container set, and the containers can be sorted according to "commodity allocation + volume" from small to large to obtain the corresponding homodimensional container sequence, i.e., adjacent in the sorting of the same commodity batch, and then sorted according to container volume (i.e., the volume of the commodity in the container) from small to large in the adjacent commodity batch.

[0059] Step S604, traversing and merging homodimensional container groups in the homodimensional container set; Step S605, obtaining the container with the smallest inventory volume and the container with the largest inventory volume in the current homodimensional container group. That is, comparing the container of sorting 1 with the container of sorting 1.

[0060] Step S606, judge whether the sum of the volumes of the containers is less than the volume limit data of the preset merged container, the sum of the types of the containers is less than the type limit value, and the number of the containers is less than the number limit value; if yes, execute step S607; if no, execute step S608.

[0061] In the embodiment, the rule of judging whether two containers are merged can be flexibly set. The volume of the container refers to the volume of the goods contained in the container. The volume limit data can be determined according to the type of the preset merged container and the preset volume proportion limit. In step S606, the rule of judging whether two containers are merged is required to meet the requirements of volume, type and number of containers, but in fact, the rule can be flexibly set according to the requirement, for example, only judging volume and number of containers.

[0062] Step S607, add the container with the largest inventory volume to the same group set of the container with the smallest inventory volume, and combine the containers as the current to-be-merged container.

[0063] At this time, the combined container actually becomes a new sorting 1 container, that is, (container with the smallest inventory volume, container with the largest inventory volume).

[0064] Step S608, judge whether there is still inventory of the same goods and batch, if yes, execute step S609, if no, execute step S610.

[0065] The judgment of whether there is still inventory of the same goods and batch refers to selecting another container in the same dimension container sequence which has not been judged, for example, the sorting 2 container. For example, the sorting 1 container and the sorting 2 container are grouped, that is, they can be merged, and thus do not need to be removed to the mixed dimension container set. If the sorting 3 container is not grouped with other containers, it is removed to the mixed dimension container set.

[0066] Step S609, compare the current to-be-merged container with the next container in the same dimension container sequence, and execute step S606. For example, compare the new sorting 1 container with the sorting 2 container.

[0067] Step S610, add the container in the current same dimension container group which has not been allocated to the mixed dimension container set. At this time, the mixed dimension container set is a mixed goods set.

[0068] Step S611, judge whether there is still ungrouped container in the current same dimension container group, if yes, repeat step S606 according to the ungrouped container, if no, execute step S612.

[0069] That is, if the volume proportion of the container reaches the upper limit after the current merging, or the number of containers reaches the upper limit, this group of merging ends, and the next group is searched for, and if the upper limit is not reached, the merging continues as a whole, and the logic is the same as above. If the containers of sorting 1 and sorting 2 cannot be merged, the merging of the containers of sorting 1 and sorting 3 is judged; if the containers of sorting 1 are still not found after the end of the sorting 1 traversal, the containers of sorting 1 are added to the container set of mixed goods; when the group of the same goods of the same batch is executed, the next group is executed until all the groups are executed.

[0070] Step S612, judging whether the goods of other same goods of the same batch are not completed, if yes, repeating step S604 according to the untraversed same dimension container group, if no, executing step S613.

[0071] At this time, step S612 represents updating the current same dimension container group according to the same dimension container set to obtain the same dimension container merging sub-data corresponding to each same dimension container group in the same dimension container set.

[0072] Step S613, the same dimension container set is traversed.

[0073] In step S240 of some embodiments, after the merging processing of the to-be-merged containers in the same dimension container group is completed, the to-be-merged containers in the mixed dimension container set can be traversed and merged according to the container inventory data, so as to complete the judgment of all to-be-merged containers.

[0074] Please refer to Figure 7 , Figure 7 is a flowchart of step S240 provided by the embodiments of the present application. In some embodiments, the specific process of step S240 can include but is not limited to steps S710 to S750, which will be described below in combination with Figure 7 The five steps will be described in detail.

[0075] Step S710, obtaining a second preset merging rule corresponding to the mixed dimension container set; Step S720, when the second merging category limiting rule indicates that the inventory category to be merged is greater than a preset value, determining a current mixed dimension container and other mixed dimension containers from the mixed dimension container set, and extracting second inventory attribute data corresponding to the current mixed dimension container and third inventory attribute data corresponding to the other mixed dimension containers according to the container inventory data; Step S730, performing container merging detection on the current mixed dimension container and the other mixed dimension containers according to the second inventory attribute data, the third inventory attribute data and the second preset merging rule, to obtain second merging detection data corresponding to the current mixed dimension container; Step S740, updating the current mixed-dimension container and other same-dimension containers according to the second merging detection data, and determining second merging detection data corresponding to the updated current mixed-dimension container; Step S750, performing data merging on the second merging detection data corresponding to all the to-be-merged containers in the mixed-dimension container set to obtain mixed-dimension container merging data.

[0076] In step S710 and step S720 of some embodiments, the second preset merging rule refers to a set of business rules configured in advance and specially used to guide the mixed-dimension container merging operation, which is similar to the first preset merging rule and will not be described herein. The second preset merging rule defines a preset value corresponding to the inventory category in the merged container, and the preset value represents the upper limit value of the inventory category, such as 1. At this time, if the second merging category limitation rule indicates that the merged inventory category is greater than the preset value, the subsequent traversal merging operation can be performed, and if the second merging category limitation rule indicates that the merged inventory category is less than or equal to the preset value, such as 1, it indicates that the merged container is limited to the same-dimension container, and therefore the mixed-dimension container merging cannot be performed.

[0077] Further, when the second merging category limitation rule indicates that the merged inventory category is greater than the preset value, the current mixed-dimension container and other mixed-dimension containers can be determined from the mixed-dimension container set, and the second inventory attribute data corresponding to the current mixed-dimension container and the third inventory attribute data corresponding to the other mixed-dimension containers can be extracted according to the container inventory data. The second inventory attribute data and the third inventory attribute data have the same meaning as the first inventory attribute data in the above embodiments and will not be described herein. These inventory attribute data can include corresponding inventory volume sub-data and inventory category sub-data.

[0078] In step S730 of some embodiments, step S730 to step S750 are similar to step S320 to step S340 of the above embodiments, except that the corresponding containers in the process are different. In order to save space, they will not be described herein.

[0079] For example, please refer to Figure 8 , Figure 8 is a specific flowchart provided by the embodiments of the present application for performing traversal merging on the to-be-merged containers in the mixed-dimension container set. The process of performing traversal merging on the to-be-merged containers in the mixed-dimension container set can include but is not limited to the following steps S801 to S809: Step S801, judge whether the number of combined inventory categories is greater than 1, if yes, execute step S802, if not, execute step S808. For example, the embodiment of the application can judge whether the number of batches of goods inventory in two containers is less than or equal to the preset number of categories of goods, and if the same batch of goods exists in two containers, it is counted only once. For example, container 1 has A and B two kinds of goods, and container 2 has B and C two kinds of goods, and there are a total of 3 kinds of categories.

[0080] Step S802, sort the to-be-merged containers in the mixed-dimension container set in ascending order according to the inventory volume, and traverse the sorted mixed-dimension container set; Step S803, get the container with the smallest inventory volume and the container with the largest inventory volume in the mixed-dimension container set. That is, compare the container sorted 1 with the container sorted last 1.

[0081] Step S804, judge whether the following conditions are true: the sum of the volumes of the containers is less than the volume limit data of the preset merged container, the volume of the single batch of goods combined is less than the volume proportion of the single compartment, the sum of the types of goods in the containers is less than the preset type category limit value, and the upper limit of the number of containers is less than the preset number of container limit value; if yes, execute step S805, if not, execute step S806. For example, assuming that it is a 20L turnover box, and container 1 and container 2 have 2 batches of goods of the same owner, then one batch of goods of the same owner can occupy a volume of 8L at most, and the volume of the two containers after merging must be less than 16L.

[0082] Step S805, add the container with the largest inventory volume to the same group set of the container with the smallest inventory volume, and combine the containers after grouping as the current to-be-merged container; Step S806, judge whether there are other container inventories, if yes, execute step S807, if not, execute step S808; Step S807, compare the current to-be-merged container with the next container in the same dimension container sequence, and execute step S804. For example, compare the new container sorted 1 with the container sorted 2.

[0083] Step S808, add the container without allocation to the rejection group; Step S809, end the traversal, add the grouped containers to the tally sheet, create a bill according to the data, and match the engine.

[0084] It should be noted that the number of outer containers in a group of inventory data must be less than the upper limit. For example, if the upper limit for the number of containers is 3, then a maximum of 3 containers can be merged into a group. If the above condition is met, merging can be performed. After merging, containers sorted 1 and 2 are treated as a whole. If the volume ratio of the containers or the number of containers reaches the upper limit after merging, this group merging ends, and the search for the next group continues. If the upper limit is not reached, it continues to merge as a whole, with the same logic as above. If containers sorted 1 and sorted 2 cannot be merged, then a merging judgment is made between containers sorted 1 and sorted 3, with the same logic as above. Finally, if no container is found after traversing sorted 1, the container of sorted 1 is removed from the inventory list. After the traversal is completed, a target container is selected for each group, sorted by the container volume (container's product length * width * height * quantity). The container with the highest volume is selected as the target container for this group, and containers that meet the conditions are added to the inventory list.

[0085] In this embodiment of the application, after traversing and merging the containers to be merged in the mixed-dimensional container set, mixed-dimensional container merge data can be obtained, and a target inventory list can be generated based on the same-dimensional container merge data and the mixed-dimensional container merge data. The document creation and matching engine are used to facilitate subsequent container retrieval equipment in knowing which containers to merge and where.

[0086] In step S250 of some embodiments, the target inventory list is the final output of the entire method, a detailed and executable work instruction. This target inventory list is not merely a table, but a dynamic set of operations. In practice, the system can transform all the merged data generated in the preceding steps into specific, serialized operation instructions, such as "transfer 15 items of product A from container A001 to container B035" or "move the merged container B035 to shelf location S02-05." The target inventory list can also include priority indicators, suggesting which merges should be prioritized to release empty containers as quickly as possible. Furthermore, the target inventory list can be integrated with the control system of automated equipment (such as AGVs and robotic arms) to directly issue task instructions to implement the specific operations of container merging. Simultaneously, the target inventory list can generate picking lists and location adjustment orders for personnel use, and update inventory records and location status in the WMS to achieve real-time consistency of container information.

[0087] Please refer to Figure 9 , Figure 9 This is a flowchart of step S250 provided in an embodiment of this application. In some embodiments, the specific process of step S250 may include, but is not limited to, steps S910 to S940, as described below. Figure 9 These four steps will be explained in detail.

[0088] Step S910, determining a merging container group according to the same dimension container merging data and the mixed dimension container merging data; Step S920, arranging the to-be-merged containers in the same merging container group in descending order according to the container inventory volume, to obtain a merging container sequence corresponding to the merging container group; Step S930, taking the first to-be-merged container in the merging container sequence as a target container corresponding to the merging container group; Step S940, generating a target inventory list according to all the merging container groups and the corresponding target containers.

[0089] In step S910 of some embodiments, the embodiments of the present application can determine a merging container group according to the same dimension container merging data and the mixed dimension container merging data, that is, determine a logically divided container group, which clearly indicates which inventory items in the to-be-merged containers will be finally merged into which unified and specific target container. Each merging container group clearly defines all the source containers (i.e. to-be-merged containers) it contains and a unique target container, providing direct input for subsequent sorting and inventory list generation.

[0090] In step S920 of some embodiments, for each merging container group, the embodiments of the present application can extract the container inventory volume (which refers to the total volume of the items currently contained in the container, which is a dynamically calculated value depending on the number of each commodity in the container multiplied by its single volume, reflecting the physical space size occupied by the container at the current time) of each to-be-merged container in the group, and arrange all the to-be-merged containers in the same merging container group in descending order according to the container inventory volume, to finally obtain a merging container sequence corresponding to the merging container group. The merging container sequence is an ordered list, and the elements in the list are the to-be-merged containers in the merging container group, arranged in descending order according to the inventory volume of each container.

[0091] In step S930 of some embodiments, the first to-be-merged container in the merged container sequence (i.e., the container with the largest current inventory volume in the merged container group) can be designated as the target container corresponding to the merged container group. The target container refers to the container that will serve as the destination for the inventory items of other containers in the final physical merging operation. In this way, the embodiments of the present application can maximize the use of existing containers and reduce the use of empty containers. Because the container with the largest current inventory volume means that it has a relatively small possibility of having sufficient space to accommodate the items of other containers, selecting it as the target container can reduce the probability of needing to allocate an entirely new empty container due to insufficient space in the target container, thereby saving container resources and reducing the operational complexity of replacing the target container. Once determined, the target container will be used to guide the movement of all other to-be-merged containers (i.e., the containers that follow in the sequence) in the merged container group (i.e., transporting the source containers to the workstation or consolidation site where the target container is located for physical item merging operations through AGV, forklift, or manual handling, etc.).

[0092] In step S940 of some embodiments, the embodiments of the present application can summarize all the merged container groups and their corresponding target container information to generate a final target inventory list (which details all the merging operation instructions to be executed, including the number of each target container, its corresponding list of source containers, the specific items and quantities in each source container that need to be transferred to the target container, the recommended consolidation site or workstation location, and the expected operation sequence, etc.).

[0093] In the above embodiments, the embodiments of the present application can effectively integrate and globally optimize the results of pre-stage same-dimension merging and mixed-dimension merging, and form merged container groups that can directly guide on-site operations through intelligent grouping. By using a descending order sorting strategy based on container inventory volume, the execution order of the merging operation is optimized, with large-capacity containers being processed first to quickly release valuable storage space, thereby improving space utilization and operational efficiency. By selecting the container with the largest content volume as the target container, the use of existing container resources is maximized, the need for new empty containers is reduced, and the cost of container use is reduced. Ultimately, a detailed, accurate, and executable target inventory list is automatically generated. In this way, the overall planning level, execution efficiency, and resource utilization of the warehouse container merging operation can be significantly improved, manual decision-making and intervention can be reduced, the error rate and cost of operations can be reduced, and key technical support is provided for the fine management of modern intelligent warehouses.

[0094] Please refer to Figure 10 , Figure 10is a flowchart of container delivery provided by an embodiment of the present application. In some embodiments, after step S250, the specific process of the container merging method provided by an embodiment of the present application can include but is not limited to steps S1010 to S1030, which are described below in combination with Figure 10 The three steps are described in detail.

[0095] In step S1010, container position information of the target container is obtained, and a target cargo survey workstation corresponding to the merging container group is determined according to the container position information. In step S1020, workstation position information of the target cargo survey workstation is obtained, and a container moving device is controlled to carry containers according to the workstation position information, so as to move all the containers to be merged in the merging container group to the target cargo survey workstation. In step S1030, all the containers to be merged in the merging container group are merged at the target cargo survey workstation.

[0096] In steps S1010 to S1030 of some embodiments, for the containers of the same merging container group, an embodiment of the present application can assign a terminal point to the target container, that is, determine the workstation for merging according to the container position information of the target container, and follow the target container to the same terminal point (i.e., the workstation) with the remaining containers. It should be noted that when the target container finds the terminal point, it is determined that the terminal point (i.e., the workstation) is occupied by the merging container group corresponding to the current target container, and other containers in the same group and the current target container simultaneously send a carrying task to the device to move all the containers to be merged in the merging container group to the target cargo survey workstation.

[0097] For example, refer to Figure 11 , Figure 11 is a process diagram for assigning a workstation based on a target container provided by an embodiment of the present application. The process of assigning a workstation based on a target container can include but is not limited to the following steps S1101 to S1104: Step S1101 starts the assignment. In step S1102, the workstations that can support cargo survey are queried, and a target cargo survey workstation corresponding to the merging container group is determined according to the container position information. In step S1103, it is determined whether the target cargo survey workstation is available. If yes, it means that the workstation is empty, and step S1104 is executed. If no, it means that the workstation is occupied, and step S1102 is re-executed. In step S1104, an available target cargo survey workstation is assigned to the target container.

[0098] The container merging method provided by the embodiments of the present application constructs an automatic and intelligent warehouse container merging management method, which can significantly improve the utilization rate of warehouse space, and effectively reduce the number of containers occupied by precisely merging containers with highly repeated or complementary contents. Specifically, the embodiments of the present application can quickly find the optimal container merging group in a complex inventory structure through system screening and grouping algorithms, save manpower, and release more storage locations and storage capacity to improve the overall warehouse storage efficiency; and based on the container usage rate and discount ratio of the container, the container merging is more accurate and more precise than manual judgment, thereby improving the rationality of container merging; in addition, the merging calculation can be based on the existing manual merging and extended to automatic cargo handling of automatic equipment, and through the combination of system and equipment, a more efficient and accurate cargo handling mode is achieved. Therefore, the embodiments of the present application can improve the efficiency and accuracy of container merging by separately traversing and merging container groups of different dimensions, thereby improving the efficiency of overall warehouse storage.

[0099] Referring to Figure 12 The container merging device 1200 provided by the embodiments of the present application comprises: The acquisition module 1210 is configured to acquire container inventory data of a plurality of to-be-merged containers in a target warehouse area, wherein the container inventory data is used to indicate the current inventory information stored in the corresponding to-be-merged container. The container division module 1220 is configured to divide the plurality of to-be-merged containers according to the container inventory data to obtain a same-dimension container set and a mixed-dimension container set, wherein the same-dimension container set comprises a same-dimension container group, and the to-be-merged containers in the same same-dimension container group correspond to the same inventory dimension information. The first merging module 1230 is configured to traverse and merge the same-dimension container groups in the same-dimension container set according to the container inventory data to obtain same-dimension container merging data. The second merging module 1240 is configured to, after the to-be-merged containers in the same-dimension container group are merged and processed, traverse and merge the to-be-merged containers in the mixed-dimension container set according to the container inventory data to obtain mixed-dimension container merging data. The generation module 1250 is configured to generate a target cargo handling list according to the same-dimension container merging data and the mixed-dimension container merging data.

[0100] It should be noted that the container merging device provided by the embodiments of the present application is used to implement the container merging method provided by the above embodiments, and the specific implementation process corresponds to the container merging method of the above embodiments. For details, refer to the foregoing container merging method, which will not be described here.

[0101] The embodiment of the present application further provides an electronic device (namely, a computer device), which comprises a memory and a processor, the memory stores a computer program, and the processor can realize the container merging method of any one of the above-mentioned embodiments when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a vehicle-mounted computer and the like.

[0102] Please refer to Figure 13 , Figure 13 The hardware structure of an electronic device of another embodiment is illustrated, which comprises: The processor 1310 can be implemented in the form of a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute related programs to realize the technical solutions provided by the embodiments of the present application; The memory 1320 can be implemented in the form of a read only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM). The memory 1320 can store an operating system and other application programs, and when the technical solutions provided by the embodiments of the present application are implemented by software or firmware, the related program codes are stored in the memory 1320 and are called and executed by the processor 1310 to realize the container merging method of the embodiments of the present application; The input / output interface 1330 is used to realize information input and output; The communication interface 1340 is used to realize the communication interaction between the device and other devices, and can realize communication through a wired manner (for example, a USB, a network cable and the like) or a wireless manner (for example, a mobile network, WIFI, Bluetooth and the like); The bus 1350 is used to transmit information between various components (for example, the processor 1310, the memory 1320, the input / output interface 1330 and the communication interface 1340) of the device; The processor 1310, the memory 1320, the input / output interface 1330 and the communication interface 1340 are connected to each other through the bus 1350 to realize the communication connection between them in the device.

[0103] The embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is used to make a computer execute the container merging method in the above-mentioned embodiments.

[0104] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0105] This invention also provides a computer program product that stores program instructions, which, when executed by a computer, cause the computer to implement the container merging method described in any of the above embodiments.

[0106] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0107] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0108] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0109] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0110] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0111] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0112] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0113] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0114] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0115] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0116] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A container merging method characterized by, The method comprises: obtaining container inventory data of a plurality of to-be-merged containers in a target storage area, the container inventory data being used to indicate inventory information currently stored in the corresponding to-be-merged containers; container dividing the plurality of to-be-merged containers according to the container inventory data, to obtain a same-dimension container set and a mixed-dimension container set, the same-dimension container set comprising same-dimension container groups, the to-be-merged containers in a same same-dimension container group corresponding to same inventory dimension information; iterative merging the same-dimension container groups in the same-dimension container set according to the container inventory data, to obtain same-dimension container merging data; after the to-be-merged containers in the same-dimension container groups are merged, iteratively merging the to-be-merged containers in the mixed-dimension container set according to the container inventory data, to obtain mixed-dimension container merging data; generating a target inventory list according to the same-dimension container merging data and the mixed-dimension container merging data.

2. The method of claim 1, wherein, The iterative merging the same-dimension container groups in the same-dimension container set according to the container inventory data, to obtain same-dimension container merging data, comprises: determining a current same-dimension container group from the same-dimension container set, and extracting first inventory attribute data from the container inventory data corresponding to the to-be-merged containers of the current same-dimension container group; determining a current to-be-merged container and other same-dimension containers from the current same-dimension container group, and performing container merging detection on the current to-be-merged container and the other same-dimension containers according to the first inventory attribute data and a first preset merging rule, to obtain first merging detection data corresponding to the current to-be-merged container; updating the current to-be-merged container and the other same-dimension containers according to the first merging detection data and the current same-dimension container group, and determining first merging detection data corresponding to the updated current to-be-merged container; performing data merging on the first merging detection data corresponding to all the to-be-merged containers in the current same-dimension container group, to obtain same-dimension container merging sub-data corresponding to the current same-dimension container group; updating the current same-dimension container group according to the same-dimension container set, and determining same-dimension container merging sub-data corresponding to the updated current to-be-merged container; performing data merging on the same-dimension container merging sub-data corresponding to all the same-dimension container groups in the same-dimension container set, to obtain same-dimension container merging data.

3. The method of claim 2, wherein, The first inventory attribute data comprises inventory volume sub-data and inventory category sub-data, and the first preset merging rule comprises a first merging category limiting rule, a first merging volume limiting rule, and a first merging container quantity limiting rule. The container merging detection on the current to-be-merged container and the other same-dimension containers according to the first inventory attribute data and a first preset merging rule, to obtain first merging detection data corresponding to the current to-be-merged container, comprises: obtaining first volume data corresponding to the current to-be-merged container and second volume data corresponding to the other same-dimension containers according to the first inventory attribute data; selecting, from the other same-dimension containers, a candidate to-be-merged container according to a volume sum of the first volume data and the second volume data; performing container merging detection on the current to-be-merged container and the candidate to-be-merged container according to the first merging category limitation rule, the first merging volume limitation rule and the first merging container number limitation rule, to obtain first merging detection data corresponding to the current to-be-merged container.

4. The method of claim 3, wherein, The determining, from the current same-dimension container group, a current to-be-merged container and other same-dimension containers comprises: performing ascending arrangement on the to-be-merged containers in the current same-dimension container group according to the inventory volume sub-data, to obtain a same-dimension container sequence; taking a first to-be-merged container in the same-dimension container sequence as the current to-be-merged container, and taking the remaining to-be-merged containers as the other same-dimension containers.

5. The method according to any one of claims 1 to 4, characterized in that, The performing traversal merging on the to-be-merged containers in the mixed-dimension container set according to the container inventory data to obtain mixed-dimension container merging data comprises: obtaining a second preset merging rule corresponding to the mixed-dimension container set, the second preset merging rule comprising a second merging category limitation rule; when the second merging category limitation rule indicates that a merged inventory category is greater than a preset value, determining a current mixed-dimension container and other mixed-dimension containers from the mixed-dimension container set, and extracting second inventory attribute data corresponding to the current mixed-dimension container and third inventory attribute data corresponding to the other mixed-dimension containers according to the container inventory data; performing container merging detection on the current mixed-dimension container and the other mixed-dimension containers according to the second inventory attribute data, the third inventory attribute data and the second preset merging rule, to obtain second merging detection data corresponding to the current mixed-dimension container; updating the current mixed-dimension container and the other same-dimension containers according to the second merging detection data, and determining second merging detection data corresponding to the updated current mixed-dimension container; performing data merging on the second merging detection data corresponding to all the to-be-merged containers in the mixed-dimension container set, to obtain mixed-dimension container merging data.

6. The method according to any one of claims 1 to 4, characterized in that, The generating a target inventory list according to the same-dimension container merging data and the mixed-dimension container merging data comprises: determining a merging container group according to the same-dimension container merging data and the mixed-dimension container merging data, the merging container group being used to indicate all the to-be-merged containers to be merged into one container; performing descending arrangement on the to-be-merged containers in a same merging container group according to container inventory volume, to obtain a merging container sequence corresponding to the merging container group; taking a first to-be-merged container in the merging container sequence as a target container corresponding to the merging container group, the target container being used to guide container movement of all the to-be-merged containers included in the merging container group; generating a target inventory list according to all the merging container groups and corresponding target containers.

7. The method of claim 6, wherein, After the generating a target inventory list according to the same-dimension container merging data and the mixed-dimension container merging data, the method further comprises: Obtain container position information of the target container, and determine a target inventory work station corresponding to the merged container group according to the container position information; Obtain work station position information of the target inventory work station, and control a container moving device to carry containers according to the work station position information, so as to move all the to-be-merged containers in the merged container group to the target inventory work station; Merge all the to-be-merged containers in the merged container group at the target inventory work station.

8. A container merging apparatus characterized by comprising: The device comprises: An obtaining module, configured to obtain container inventory data of a plurality of to-be-merged containers in a target storage area, the container inventory data being used to indicate inventory information currently stored in the corresponding to-be-merged containers; A container division module, configured to divide the plurality of to-be-merged containers according to the container inventory data, to obtain a same-dimension container set and a mixed-dimension container set, the same-dimension container set comprising same-dimension container groups, the to-be-merged containers in a same same-dimension container group corresponding to the same inventory dimension information; A first merging module, configured to perform iterative merging on the same-dimension container groups in the same-dimension container set according to the container inventory data, to obtain same-dimension container merging data; A second merging module, configured to perform iterative merging on the to-be-merged containers in the mixed-dimension container set according to the container inventory data after the to-be-merged containers in the same-dimension container groups are merged, to obtain mixed-dimension container merging data; A generating module, configured to generate a target inventory list according to the same-dimension container merging data and the mixed-dimension container merging data.

9. An electronic device, comprising: The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the method in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 9. The computer program is executed by the processor to implement the method in any one of claims 1 to 7.

Images