Method, system and apparatus for recovering label positions

Abstract

A method of recovering label positions in an imaging controller includes: receiving (i) a definition of a plane containing edges of the shelf, and (ii) a plurality of initial label indicators having locations on the plane; assigning the initial label indicators among a plurality of candidate subsets each representing a single physical label; for each candidate subset of initial indicators: generating, for each of a plurality of projection depths relative to the plane, a set of projections of the initial indicators in the candidate subset; determining an aggregate surface area for each set of projections; selecting, as a recovered depth for the candidate subset, one of the projection depths corresponding to the minimum aggregate surface area; and generating a recovered position for the candidate subset based on the recovered depth; and storing the recovered positions.

Description

BACKGROUND

Environments in which inventories of objects are managed, such as products for purchase in a retail environment, may be complex and fluid. For example, a given environment may contain a wide variety of objects with different attributes (size, shape, price and the like). Further, the placement and quantity of the objects in the environment may change frequently. Still further, imaging conditions such as lighting may be variable both over time and at different locations in the environment. These factors may reduce the accuracy with which information concerning the objects may be collected within the environment. Certain objects, such as labels, may be particularly difficult to detect accurately due to their small size and placement on or near other structures such as shelf edges.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views, together with the detailed description below, are incorporated in and form part of the specification, and serve to further illustrate embodiments of concepts that include the claimed invention, and explain various principles and advantages of those embodiments.

FIG. 1 is a schematic of a mobile automation system.

FIG. 2A depicts a mobile automation apparatus in the system of FIG. 1.

FIG. 2B is a block diagram of certain internal hardware components of the mobile automation apparatus in the system of FIG. 1.

FIG. 3 is a block diagram of certain internal components of the server of FIG. 1.

FIG. 4 is a flowchart of a method of recovering label positions.

FIG. 5A depicts an example shelf arrangement.

FIG. 5B depicts captured data and initial label indicators corresponding to the shelf of FIG. 5A.

FIG. 6 depicts the initial label indicators of FIG. 5B in greater detail.

FIG. 7 is a flowchart of a method of assigning the label indicators to candidate subsets.

FIGS. 8A and 8B illustrate an example performance of the method of FIG. 7.

FIGS. 9A to 9D illustrate an example performance of block 420 of the method of FIG. 4.

FIG. 10 is a flowchart of a method of refining projection depth for use in the method of FIG. 4.

FIGS. 11A and 11B illustrate example inputs and results, respectively, of the performance of the method of FIG. 4.

Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.

The apparatus and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

DETAILED DESCRIPTION

Examples disclosed herein are directed to a method of recovering label positions in an imaging controller, the method comprising: receiving (i) a definition of a plane containing edges of a support structure, and (ii) a plurality of initial label indicators having locations on the plane; assigning the initial label indicators among a plurality of candidate subsets of label indicators, each candidate subset representing a single physical label; for each candidate subset of initial label indicators: generating, for each of a plurality of projection depths relative to the plane, a set of projections of the initial label indicators in the candidate subset; selecting, as a recovered depth for the candidate subset, one of the projection depths based on the sets of projections; and generating a recovered position for the candidate subset based on the recovered depth; and storing the recovered positions.

Additional examples disclosed herein are directed to a computing device for recovering label positions, comprising: a memory; and an imaging controller connected to the memory, the imaging controller configured to: receive (i) a definition of a plane containing edges of a support structure, and (ii) a plurality of initial label indicators having locations on the plane; assign the initial label indicators among a plurality of candidate subsets of label indicators, each candidate subset representing a single physical label; for each candidate subset of initial label indicators: generate, for each of a plurality of projection depths relative to the plane, a set of projections of the initial label indicators in the candidate subset; select, as a recovered depth for the candidate subset, one of the projection depths based on the sets of projections; and generate a recovered position for the candidate subset based on the recovered depth; and the imaging controller further configured to store the recovered positions in the memory.

FIG. 1 depicts a mobile automation system 100 in accordance with the teachings of this disclosure. The system 100 includes a server 101 in communication with at least one mobile automation apparatus 103 (also referred to herein simply as the apparatus 103) and at least one client computing device 105 via communication links 107, illustrated in the present example as including wireless links. In the present example, the links 107 are provided by a wireless local area network (WLAN) deployed within the retail environment by one or more access points (not shown). In other examples, the server 101, the client device 105, or both, are located outside the retail environment, and the links 107 therefore include wide-area networks such as the Internet, mobile networks, and the like. The system 100 also includes a dock 108 for the apparatus 103 in the present example. The dock 108 is in communication with the server 101 via a link 109 that in the present example is a wired link. In other examples, however, the link 109 is a wireless link.

The client computing device 105 is illustrated in FIG. 1 as a mobile computing device, such as a tablet, smart phone or the like. In other examples, the client device 105 is implemented as another type of computing device, such as a desktop computer, a laptop computer, another server, a kiosk, a monitor, and the like. The system 100 can include a plurality of client devices 105 in communication with the server 101 via respective links 107.

The system 100 is deployed, in the illustrated example, in a retail environment including a plurality of support structures such as shelf modules 110-1, 110-2, 110-3 and so on (collectively referred to as shelves 110, and generically referred to as a shelf 110—this nomenclature is also employed for other elements discussed herein). Each shelf module 110 supports a plurality of products 112. Each shelf module 110 includes a shelf back 116-1, 116-2, 116-3 and a support surface (e.g. support surface 117-3 as illustrated in FIG. 1) extending from the shelf back 116 to a shelf edge 118-1, 118-2, 118-3. In other examples, the environment can include additional support structures (e.g. tables, pegboards and the like) in addition to or instead of the shelf modules 110.

The shelf modules 110 are typically arranged in a plurality of aisles, each of which includes a plurality of modules 110 aligned end-to-end. In such arrangements, the shelf edges 118 face into the aisles, through which customers in the retail environment as well as the apparatus 103 may travel. As will be apparent from FIG. 1, the term “shelf edge” 118 as employed herein, which may also be referred to as the edge of a support surface (e.g., the support surfaces 117) refers to a surface bounded by adjacent surfaces having different angles of inclination. In the example illustrated in FIG. 1, the shelf edge 118-3 is at an angle of about ninety degrees relative to each of the support surface 117-3 and the underside (not shown) of the support surface 117-3. In other examples, the angles between the shelf edge 118-3 and the adjacent surfaces, such as the support surface 117-3, is more or less than ninety degrees.

The apparatus 103 is deployed within the retail environment, and communicates with the server 101 (e.g. via the link 107) to navigate, autonomously or partially autonomously, along a length 119 of at least a portion of the shelves 110. The apparatus 103 is configured to perform such navigation relative to a frame of reference 102 established within the retail environment.

The apparatus 103 is equipped with a plurality of navigation and data capture sensors 104, such as image sensors (e.g. one or more digital cameras) and depth sensors (e.g. one or more Light Detection and Ranging (LIDAR) sensors, one or more depth cameras employing structured light patterns, such as infrared light, or the like), and is further configured to employ the sensors 104 to capture shelf data. In the present example, the apparatus 103 is configured to capture image data and depth measurements (defining a distance from a depth sensor on the apparatus 103 to a point on the shelf 110, such as a product 112, a shelf back 116 or the like) corresponding to the shelves 110.

The server 101 includes a special purpose imaging controller, such as a processor 120, specifically designed to control the mobile automation apparatus 103 to capture data (e.g. the above-mentioned images and depth measurements). The processor 120 is further configured to obtain the captured data via a communications interface 124 and store the captured data in a repository 132 in a memory 122 connected with the processor 120. The server 101 is further configured to perform various post-processing operations on the captured data, which can include registering the captured data to the frame of reference 102 based on recorded data indicating positions of the apparatus 103 at the time of capture, as well as on calibration data defining relationships between image and depth sensors on the apparatus 103. The process of registering the captured data to the frame of reference is referred to herein as back-projecting. As will be discussed below in greater detail, the post-processing functions performed by the server 101 include the recovery of positional data corresponding to labels placed on the shelves 110 from the captured data.

The server 101 can also be configured to determine product status data (e.g. to detect gaps on the shelves 110), and to transmit status notifications (e.g. notifications indicating that products are out-of-stock, low stock or misplaced) to the client device 105 responsive to the determination of product status data. The client device 105 includes one or more controllers (e.g. central processing units (CPUs) and/or field-programmable gate arrays (FPGAs) and the like) configured to process (e.g. to display) notifications received from the server 101.

The processor 120 is interconnected with a non-transitory computer readable storage medium, such as the above-mentioned memory 122, having stored thereon computer readable instructions for executing control of the apparatus 103 to capture data, as well as the above-mentioned post-processing functionality, discussed in further detail below. The memory 122 includes a combination of volatile (e.g. Random Access Memory or RAM) and non-volatile memory (e.g. read only memory or ROM, Electrically Erasable Programmable Read Only Memory or EEPROM, flash memory). The processor 120 and the memory 122 each comprise one or more integrated circuits. In some embodiments, the processor 120 is implemented as one or more central processing units (CPUs) and/or graphics processing units (GPUs).

The server 101 also includes the above-mentioned communications interface 124 interconnected with the processor 120. The communications interface 124 includes suitable hardware (e.g. transmitters, receivers, network interface controllers and the like) allowing the server 101 to communicate with other computing devices—particularly the apparatus 103, the client device 105 and the dock 108—via the links 107 and 109. The links 107 and 109 may be direct links, or links that traverse one or more networks, including both local and wide-area networks. The specific components of the communications interface 124 are selected based on the type of network or other links that the server 101 is required to communicate over. In the present example, as noted earlier, a wireless local-area network is implemented within the retail environment via the deployment of one or more wireless access points. The links 107 therefore include either or both wireless links between the apparatus 103 and the mobile device 105 and the above-mentioned access points, and a wired link (e.g. an Ethernet-based link) between the server 101 and the access point.

The memory 122 stores a plurality of applications, each including a plurality of computer readable instructions executable by the processor 120. The execution of the above-mentioned instructions by the processor 120 configures the server 101 to perform various actions discussed herein, including the above-mentioned recovery of label positions. The applications stored in the memory 122 include a control application 128, which may also be implemented as a suite of logically distinct applications. In general, via execution of the control application 128 or subcomponents thereof and in conjunction with the other components of the server 101, the processor 120 is configured to implement various functionality. The processor 120, as configured via the execution of the control application 128, is also referred to herein as the controller 120. As will now be apparent, some or all of the functionality implemented by the controller 120 described below may also be performed by preconfigured hardware elements (e.g. one or more FPGAs and/or Application-Specific Integrated Circuits (ASICs)) rather than by execution of the control application 128 by the processor 120.

Turning now to FIGS. 2A and 2B, the mobile automation apparatus 103 is shown in greater detail. The apparatus 103 includes a chassis 201 containing a locomotive mechanism 203 (e.g. one or more electrical motors driving wheels, tracks or the like). The apparatus 103 further includes a sensor mast 205 supported on the chassis 201 and, in the present example, extending upwards (e.g., substantially vertically) from the chassis 201. The mast 205 supports the sensors 104 mentioned earlier. In particular, the sensors 104 include at least one imaging sensor 207, such as a digital camera, as well as at least one depth sensor 209, such as a 3D digital camera. The apparatus 103 also includes additional depth sensors, such as LIDAR sensors 211. In other examples, the apparatus 103 includes additional sensors, such as one or more RFID readers, temperature sensors, and the like.

In the present example, the mast 205 supports seven digital cameras 207-1 through 207-7, and two LIDAR sensors 211-1 and 211-2. The mast 205 also supports a plurality of illumination assemblies 213, configured to illuminate the fields of view of the respective cameras 207. That is, the illumination assembly 213-1 illuminates the field of view of the camera 207-1, and so on. The sensors 207 and 211 are oriented on the mast 205 such that the fields of view of each sensor face a shelf 110 along the length 119 of which the apparatus 103 is travelling. The apparatus 103 is configured to track a location of the apparatus 103 (e.g. a location of the center of the chassis 201), for example in the frame of reference 102 previously established in the retail facility, permitting data captured by the mobile automation apparatus to be registered to the frame of reference 102.

The mobile automation apparatus 103 includes a special-purpose controller, such as a processor 220, as shown in FIG. 2B, interconnected with a non-transitory computer readable storage medium, such as a memory 222. The memory 222 includes a combination of volatile (e.g. Random Access Memory or RAM) and non-volatile memory (e.g. read only memory or ROM, Electrically Erasable Programmable Read Only Memory or EEPROM, flash memory). The processor 220 and the memory 222 each comprise one or more integrated circuits. The memory 222 stores computer readable instructions for execution by the processor 220. In particular, the memory 222 stores a control application 228 which, when executed by the processor 220, configures the processor 220 to perform various functions related to the navigation of the apparatus 103 (e.g. by controlling the locomotive mechanism 203) and the collection of data (e.g. image data and/or depth measurements) representing the shelves 110. The application 228 may also be implemented as a suite of distinct applications in other examples.

The processor 220, when so configured by the execution of the application 228, may also be referred to as a controller 220. Those skilled in the art will appreciate that the functionality implemented by the processor 220 via the execution of the application 228 may also be implemented by one or more specially designed hardware and firmware components, such as FPGAs, ASICs and the like in other embodiments.

The memory 222 may also store a repository 232 containing, for example, a map of the environment in which the apparatus 103 operates, for use during the execution of the application 228. The apparatus 103 may communicate with the server 101, for example to receive instructions to initiate data capture operations, via a communications interface 224 over the link 107 shown in FIG. 1. The communications interface 224 also enables the apparatus 103 to communicate with the server 101 via the dock 108 and the link 109.

In the present example, as discussed below, one or both of the server 101 (as configured via the execution of the control application 128 by the processor 120) and the mobile automation apparatus 103 (as configured via the execution of the application 228 by the processor 220), are configured to process image and depth data captured by the apparatus 103 to recover label positions (e.g. in the frame of reference 102) from the captured data. The label positions may be stored for use in downstream processing, such as price verification, product status detection (e.g. to detect a product 112 that does not match a nearby label), and the like.

In further examples, the data processing discussed below may be performed on a computing device other than the server 101 and the mobile automation apparatus 103, such as the client device 105. The data processing mentioned above will be described in greater detail in connection with its performance at the server 101, via execution of the application 128.

Turning now to FIG. 3, before describing the operation of the application 128 to correct translucency artifacts in depth data captured by the apparatus 103, certain components of the application 128 will be described in greater detail. As will be apparent to those skilled in the art, in other examples the components of the application 128 may be separated into distinct applications, or combined into other sets of components. Some or all of the components illustrated in FIG. 3 may also be implemented as dedicated hardware components, such as one or more ASICs or FPGAs.

The control application 128 includes a candidate subset generator 300 configured to obtain input data including initial label indicators. The initial label indicators indicate the positions of labels in the frame of reference 102, but may be affected by various sources of error. Further, each physical label on the shelves 110 may be depicted by more than one initial lab el indicator, for captured in successive frames of image and depth data. The candidate subset generator 300 is configured to assign the initial label indicators into candidate subsets each representing a single physical label on the shelves 110.

The control application 128 also includes a depth optimizer 304 configured to select a recovered depth for each of the candidate subsets of initial label indicators. The recovered depth seeks to mitigate or eliminate some of the above-mentioned sources of error and thus represent a more accurate depth for the underlying physical label than that defined by the initial label indicators.

The control application 128 also includes a position generator 308, configured to generated recovered positions for each of the candidate subsets of initial label indicators. The recovered positions may be stored in the repository 132 for further processing. For example, the recovered positions may be provided to a further application at the server 101, for assessing planogram compliance (e.g. whether the labels are in positions complying with a planogram stored in the repository 132).

The functionality of the control application 128 will now be described in greater detail. Turning to FIG. 4, a method 400 of recovering label positions in captured data depicting the shelves 110 is shown. The method 400 will be described in conjunction with its performance on the system 100, and specifically with reference to the components of the server 101 illustrated in FIG. 3.

At block 405, the server 101, and in particular the candidate subset generator 300 of the application 128 (as executed by the processor 120), is configured to obtain the input data employed through performance of the method 400 to generate recovered label positions. The input data includes a representation of a shelf plane. The shelf plane is a plane containing shelf edges (e.g. the edges 118 shown in FIG. 1), and may be generated by a shelf plane detector executed by the processor 120 itself or by another computing device. An example shelf plane detector can be configured to process depth measurements of the modules 110 or 510 (e.g. captured by the apparatus 103 with the depth sensor 209) to select a subset of the depth measurements indicative of shelf edges (e.g. indicative of substantially vertical surfaces), and to fit a shelf plane to the selected depth measurements. The plane definition obtained at block 405 can include an equation, a set of vectors or the like defining the plane, for example according to the frame of reference 102.

The server 101 is also configured to obtain, at block 405, a plurality of initial label indicators indicating the position of labels detected in the data captured by the apparatus 103 depicting the shelves 110. Each initial label indicator includes at least a location (e.g. in the frame of reference 102). Each initial label indicator can also include data decoded or otherwise retrieved from the label, such as a string decoded from a barcode printed on the corresponding label, a price recognized (e.g. via optical character recognition, OCR) from the label, and the like. The initial label indicators may be previously generated via the execution of a label detector by the server 101 or another computing device. An example label detector can be configured to process images of the modules 110 or 510 (e.g. captured by the apparatus 103 with the cameras 207) to generate a feature mask indicating locations in the images that contain certain predefined features (e.g. barcodes, blocks of text or the like). The label detector can then be configured to identify locations within the feature mask that match predefined label templates, indicating the likely presence of a label. Label indicators can then be generated from the above-mentioned locations, for example as bounding boxes.

As will be seen below in greater detail, at block 405 the server 101 can also be configured to obtain data indicating the locations of shelf edges (e.g. the edges 118). The locations of the shelf edges are, in the present example, obtained as bounding boxes (e.g. defined by coordinates in the frame of reference 102 and falling within the plane mentioned above). The shelf edge locations may be previously generated via the execution of a shelf structure detector by the server 101 or another computing device. An example shelf edge detector can, for example, process images of the modules 110 or 510 (e.g. captured by the apparatus 103 with the cameras 207) to identify intensity transitions (transitions from light to dark and from dark to light) indicative of shelf edges, which are indicative of shelf edges. The shelf edge detector can produce bounding boxes corresponding to the regions (i.e. the likely shelf edges) bounded by such transitions.

As noted above, example processes for the generation of the above-mentioned data are set out in Applicant's co-pending applications, and are therefore not discussed in detail herein. In the present example performance of the method 400, the server 101 performs block 405 by retrieving the shelf plane, initial label indicators, and optionally the shelf edge indicators, from the repository 132, the input data having been previously stored in the repository following upstream processing of data captured by the apparatus 103.

Although the generation of the above-mentioned input data is not discussed in detail, a brief summary of an example mechanism for generation of the input data from data captured by the apparatus 103 is provided with reference to FIGS. 5A and 5B.

Turning to FIG. 5A, an example shelf module 510 is illustrated. The module 510 includes a shelf back 516 extending between a pair of support surfaces 517-1 and 517-2 (and also above the support surface 517-2). The support surfaces 517 include respective edges 518-1 and 518-2. The support surface 517-2 is shown supporting a plurality of objects 512, such as products in a retail environment. Although the support surface 517-1 is shown as not directly supporting any objects, the shelf back 516 supports a plurality of pegs 520, each of which may support additional products 512 above the support surface 517-1.

The module 510 includes a plurality of labels, each corresponding to a portion of the products 512. In the illustrated example, the pegs 520 bear respective labels 522, 524 and 526. In addition, the shelf edge 518-2 bears labels 528, 530, 532 and 534. The data capture apparatus 103 can be configured (e.g. via instructions issued from the server 101) to traverse the module 510 and capture a plurality of images of the module 510. Two examples portions of the module 510 captured by respective image frames are illustrated as frames 536 and 540 in FIG. 5A. As seen in FIG. 5A, the frames 536 and 540 overlap, and each portion of the module 510 is therefore depicted in more than one frame captured by the apparatus 103. The apparatus 103 is also configured to capture depth measurements while traversing the module 510.

Turning to FIG. 5B, a point cloud 550 obtained from the above-mentioned depth measurements is illustrated. In addition to the point cloud, a shelf plane 554 (e.g. generated by the above-mentioned shelf plane detector) is illustrated, as well as shelf edge indicators 558-1 and 558-2 indicating the detected location of the shelf edges 518-1 and 518-2 in the plane 554. Also shown in FIG. 5B are a plurality of initial label indicators referenced generally by the numeral 560 (more detailed discussion of the label indicators will be provided below).

As will be apparent to those skilled in the art, the initial label indicators 560 are greater in number than the physical labels present on the module 510, as shown in FIG. 5A. In the present example, the initial label indicators are detected from image data captured by the apparatus 103. As noted above, the image frames captured by the apparatus 103 overlap, and therefore each of the labels 522 to 534 is typically detected in more than one image. All label detections are stored in the repository 132, and thus each label is represented in the input data obtained at block 405 by a plurality of initial label indicators.

As will also be apparent to those skilled in the art, the label indicators include various positional errors. Such errors arise from variations in image quality between the above-mentioned image frames, variations in label detection accuracy, and the like. In addition, the initial label indicators 560 corresponding to the labels 522, 524 and 526 include additional positional errors resulting from their placement on the plane 554 (when the labels 522, 524 and 526 themselves are not at the same depth as the shelf edges 518). The erroneous placement of such label indicators may result from an assumption taken by the label detector noted above that all labels are in the same plane as the shelf edges 518. Such assumptions may result from the difficult of accurately detecting the true depth of the labels from the depth measurements captured by the apparatus 103, due to the small size of the labels. In other words, rather than attempting to detect a depth for the labels, the label detector may operate solely on image data, and the two-dimensional positions of detected labels within each image frame is transformed into a three-dimensional position in the frame of reference 102 by back-projecting the two-dimensional positions onto the plane 554. The back-projection is based, in the present example, on the stored location of the apparatus 103 at the time of capture of each image frame, as well as on

Performance of the remainder of the method 400 permits the server 101 to recover unique label positions for each physical label, that may have greater accuracy than the initial indicators shown in FIG. 5B.

Turning to FIG. 6, the input data obtained at block 405 is shown in greater detail. In particular, the plane 554 is shown, as well as the shelf edge indicators 558-1 and 558-2. The initial label indicators 560 shown in FIG. 5B are also illustrated in greater detail. In particular, initial label indicators 622-1 and 622-2 correspond to the physical label 522 (although that fact is not currently known to the server 101). In addition, the label indicators 624-1 and 624-2 correspond to the label 524; the label indicators 626-1 and 626-2 correspond to the label 526; the label indicators 628-1, 628-2 and 628-3 correspond to the label 528; the label indicators 630-1 and 630-2 correspond to the label 530; the label indicators 632-1 and 632-2 correspond to the label 532; and the label indicators 634-1, 634-2 and 634-3 correspond to the label 534.

Returning to FIG. 4, at block 410 the server 101, and in particular the candidate subset generator 300, is configured to assign the initial label indicators to candidate subsets. Each candidate subset corresponds to a single physical label on the shelf module 510. In other words, each candidate subset of initial label indicators contains all of the detections (from multiple image frames) of a given label shown in FIG. 5A.

The assignment of initial label indicators to candidate subsets includes, in some examples, assigning each initial label indicator to a candidate subset based on decoded data included in the label indicator. As mentioned above, each label indicator can include data decoded or otherwise extracted from the portion of the image in which the label was detected. The labels may include barcodes encoding product identifiers, price information and the like. The assignment of each initial label indicator to a candidate subset may therefore include retrieving the decoded data contained in the label indicator (e.g. stored as metadata in association with the coordinates of the label indicator) and assigning the label indicator to a candidate subset corresponding to the decoded data. Thus, each initial label indicator having the same decoded data (e.g. the same product identifier) is assigned to the same candidate subset.

In some examples, however, more than one label may appear on the shelf 510 having the same barcode. In such examples, assigning initial label indicators to candidate subsets based on decoded data alone may incorrectly assign indicators corresponding to different labels to the same candidate subset. The server 101 is therefore configured, in some examples, to assign the initial label indicators to candidate subsets based both on the above-mentioned decoded data and on relative positions of the initial label indicators.

Turning to FIG. 7, a method 700 of assigning the label indicators to candidate subsets (i.e. of performing block 410 of the method 400) is shown. At block 705, the candidate subset generator 300 is configured to determine whether each initial label indicator overlaps with a shelf edge indicator. Any initial label indicators for which the determination at block 705 is negative are assigned to candidate subsets at block 710 based on decoded label data as mentioned above. Thus, the label indicators 622, 624 and 626 shown in FIG. 6 are assigned to candidate subsets based solely on the decoded data they each contain. In the present example it is assumed that the indicators 622 contain first decoded data, that the indicators 624 contain second decoded data, and that the indicators 626 contain third decoded data. The above-mentioned indicators are therefore assigned to three candidate subsets, with the indicators 622-1 and 622-2 corresponding to the label 522, and so on. Following generation of the above-mentioned candidate subsets, the candidate subset generator 300 is configured to return the subsets for further processing (e.g. by the depth optimizer 304) at block 715.

It is evident from FIG. 6 that for the remaining initial label indicators, the determination at block 705 is affirmative. Therefore, the candidate subset generator 300 proceeds to block 720 for those initial label indicators. At block 720, the generator 300 is configured to place the initial label indicators into sets based on decoded label data, as described above. Taking the initial label indicators 632 and 634, it is assumed in the present example that they all contain the same decoded data, and therefore are all placed in the same set. FIG. 8A illustrates the set resulting from the performance of block 720. As will be apparent, the set shown in FIG. 8A corresponds not to a single physical label, but to two labels, and must therefore be further subdivided.

At block 725, for each set the generator 300 determines the mean location in the frame of reference 102 (i.e. on the plane 554) of the label indicators in the set. FIG. 8A illustrates the mean location 800 of the set of label indicators that include the indicators 632 and 634. The generator 300 is also configured to determine the distance from the mean 800 to each initial label indicator (e.g. to the center of each label indicator). The above-mentioned distances are shown as dashed lines in FIG. 8A.

At block 730, the generator 300 is configured to place the initial label indicators of each set into candidate subsets based on the above-mentioned distances. For example, the generator 300 may be configured to group the initial label indicators in the set based on a threshold distance. FIG. 8B illustrates the application of a threshold distance (illustrated as a circle) to the distances determined in FIG. 8A, to divide the set into two candidate subsets 832 and 834 (corresponding to the initial label indicators 632 and 634, respectively). As is evident from FIG. 8B, the distances for each candidate subset 832, 834 are separated from each other by distances smaller than the threshold, but any individual member of one subset is separated from any member of the other subset by a distance greater than the threshold.

As will now be apparent to those skilled in the art, the process set out in connection with blocks 720 to 730 may not be suitable for label indicators that do not overlap with a shelf edge indicator, because such label indicators may correspond to labels mounted on pegs 520 or other structures whose actual depth deviates substantially from the depth of the plane 554. As a result, the positions of such label indicators on the plane 554 may be too inaccurate to employ mean locations and distances to assign the label indicators to subsets.

Following the performance of block 730, the generator 300 is configured to repeat the above process for each set generated at block 720 (via block 735). When each set has been subdivided into candidate subsets, the candidate subsets are returned for further processing at block 715. It is possible that a candidate subset generated via the performance of blocks 725 and 730 is identical to the set initially generated at block 720. For example, in the case of the initial label indicators 628 (which are presumed to each contain the same decoded data, different from the decoded data of any other indicators shown in FIG. 6), the above-mentioned distances may all fall within the threshold, and the initial indicators 628 are therefore assigned to a single candidate sub set.

Returning to FIG. 4, at block 415 the depth optimizer is configured to select a candidate subset for further processing. Having selected a candidate subset, the depth optimizer is configured to determine a recovered depth for the candidate subset. As noted above, the depth of all initial label indicators is the depth of the shelf plane 554. However, the actual labels represented by the initial label indicators are not necessarily at the same depth as the plane 554. As noted earlier, the depth of the peg-mounted labels 522, 524 and 526 may vary significantly from the depth of the shelf edges 518. Further, the plane 554 itself may not represent an exact fit with the shelf edges 518, and thus the depth assigned to the initial label indicators may not be accurate even for initial label indicators representing labels placed on the shelf edges 518.

The depth optimizer is configured to determine a recovered depth for each candidate subset beginning at block 420, by generating a plurality of projection sets. Each projection set includes a back-projection of each initial label indicator in the candidate subset to a different depth than the depth of the shelf plane 554. Each projection set is generated for a different one of a series of predetermined depths. For example, the series of predetermined depths may begin at the depth of the shelf plane 554 and increase in increments of 1 mm until a depth equal to the (previously known or detected from captured depth measurements) depth of the shelf back 516. A variety of other depth increments may also be contemplated, depending on the size of the shelf 510, the desired accuracy of the recovered depth, and the like.

Turning to FIGS. 9A-9D, the initial label indicators 622-1 and 622-2 (both members of a single candidate subset) are shown in FIG. 9A. FIGS. 9B, 9C and 9D show successive projection sets 900-1 and 900-2, 904-1 and 904-2, and 908-1 and 908-2. Each projection set 900, 904 and 908 results from the back-projection of the label indicators 622 to a greater depth than the previous projection set (that is, the set 908 is at a greater depth than the set 904). Example projection depths, relative to the depth of the plane 554, are listed in each of FIGS. 9A-9D.

As shown in FIGS. 9A-9D, as the depth of projection increases, the projections of the indicators 622-1 and 622-2 begin to overlap. That is, the projections begin to occupy the same three-dimensional space in the frame of reference 102, which is to be expected as both indicators 622 represent the same physical label. Thus, the projection set with the greatest degree of overlap is most likely to reflect a correct depth for the indicators 622.

The optimizer 304 is therefore configured, at block 420, to also determine the aggregate surface area of each projection set (i.e. the total surface area of the projection set). At block 425, the optimizer 304 is configured to select the projection depth of the projection set with the smallest aggregate surface area. Returning to FIGS. 9A-9D, it is evident that the final projection set (FIG. 9D) has the smallest aggregate surface area among those illustrated. The optimizer 304 is therefore configured to select the depth at which the projection set 908 was generated (i.e. 30 cm beyond the depth of the plane 554, in this example).

As will now be apparent to those skilled in the art, a significant number of projection sets may be required to traverse a sufficient range of depths to identify a recovered depth that is likely to reflect the true depth of a given label. For example, using projection depths at increments of 1 mm as mentioned above, three hundred projection sets are required to arrive at the projection set 908 shown in FIG. 9D. Therefore, the optimizer 304 is configured, in some examples, to employ both coarse and fine depth increments to generate the projection sets.

Turning to FIG. 10, a method 1000 of refining projection depth is shown, for performance prior to block 420. In particular, at block 1005 the optimizer 304 is configured in some examples to generate a plurality of coarse projection sets and determine the aggregate surface area of each projection set. The generation of projection sets is as described above in connection with block 420, except that the depth increments separating each projection sets are larger than those employed at block 420. For example, when an increment of 1 mm is employed at block 420, an increment of 2 cm may be employed at block 1005.

At block 1010, the optimizer 308 is configured to select the depth of the coarse projection set having the smallest aggregate surface area, and at block 1015 the optimizer 304 is configured to determine the series of depths to be employed at block 420 according to the coarse depth selected at block 1010. For example, if the coarse depth selected was 24 cm relative to the plane 554, at block 1015 the optimizer 304 can be configured to generate a series of projection depths at increments of 1 mm centered at a depth of 24 cm. In some examples, the method 1000 can be employed only for certain candidate subsets. For example, the optimizer may be configured to perform the method 1000 prior to block 420 for any label indicators that do not overlap with the shelf edge indicators 568 (i.e. label indicators likely to correspond to peg-mounted labels).

Returning to FIG. 4, at block 430 the position generator 308 is configured to generate one recovered position for the candidate subset selected at block 415, based on the recovered depth. For example, the position generator 308 can be configured to generate a recovered position including the recovered depth (i.e. along the Z axis of the frame of reference 102) as well as the coordinates (e.g. along the X and Y axes of the frame of reference 102) of the center of the aggregate surface area of the projection set selected at block 425. Turning to FIG. 11A, portions of the plane 554 and shelf edge indicator 558-1 are shown along with the label indicators 622, 624 and 626. FIG. 11B, meanwhile, illustrates back-projections 1122, 1124 and 1126 corresponding to the indicators 622, 624 and 626 respectively. The position of each back-projection 1122, 1124 and 1126 includes the depth at which each projection was generated, as well as the illustrated center of the back-projection. As is evident from a comparison of FIG. 11B with FIGS. 5A and 5B, the recovered positions of the back-projections 1122, 1124 and 1126 correspond more accurately to the positions of the labels 522, 524 and 526 respectively than do the initial label indicators 560.

Returning to FIG. 4, at block 435 the server 101 determines whether any candidate subsets remain to be processed. When the determination at block 435 is affirmative, the performance of blocks 415 to 430 are repeated for each remaining candidate subset. When the determination at block 435 is negative, the performance of method 400 proceeds to block 440, at which the recovered positions generated at block 430 are stored, for example in the repository 132.

The recovered positions may be stored, for example, in final label indicators that include not only the recovered positions, but also the decoded data mentioned above and any other data extracted from the images captured by the apparatus 103 (e.g. price information and the like). The final label indicators can include a plurality of decoded data strings, prices and the like (e.g. one for each initial label indicator from which the final label indicator was generated).

Variations to the above systems and methods are contemplated. For example, the depth optimizer 304 is configured, in some examples, to dynamically determine minimum and maximum depths for which to generate projection sets at block 420. For example, the depth optimizer can be configured to retrieve an expected actual size for a label based on the decoded data. The depth optimizer can further be configured, based on the retrieved size and the size of the initial label indicator, to determine an approximate depth error (e.g. the two sizes may indicate that the depth of the initial label indicator is likely to be about 20 cm above or below the actual depth of the label). The depths employed at block 420 (or via the method 1000) can be determined to traverse the depth so determined.

In the foregoing specification, specific embodiments have been described. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present teachings.

The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.

Moreover in this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms “comprises,” “comprising,” “has”, “having,” “includes”, “including,” “contains”, “containing” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by “comprises . . . a”, “has . . . a”, “includes . . . a”, “contains . . . a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms “a” and “an” are defined as one or more unless explicitly stated otherwise herein. The terms “substantially”, “essentially”, “approximately”, “about” or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within 10%, in another embodiment within 5%, in another embodiment within 1% and in another embodiment within 0.5%. The term “coupled” as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is “configured” in a certain way is configured in at least that way, but may also be configured in ways that are not listed.

It will be appreciated that some embodiments may be comprised of one or more generic or specialized processors (or “processing devices”) such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used.

Moreover, an embodiment can be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.

The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.

Claims

1. A method of recovering label positions in an imaging controller, the method comprising: receiving (i) a definition of a plane containing edges of a support structure, and (ii) a plurality of initial label indicators having locations on the plane, where an initial label indicator indicates a single physical label in one image frame of a plurality of image frames;assigning the plurality of initial label indicators among a plurality of candidate subsets of initial label indicators, each candidate subset of initial label indicators representing the single physical label;for each candidate subset of initial label indicators: generating, for each of a plurality of projection depths relative to the plane, a set of projections of the initial label indicators in the candidate subset of initial label indicators;selecting, as a recovered depth for the candidate subset of initial label indicators, one of the projection depths based on the sets of projections; andgenerating a recovered position for the candidate subset of initial label indicators based on the recovered depth; andstoring the recovered positions.

2. The method of claim 1, wherein each initial label indicator includes decoded data; and wherein assigning the initial label indicators among a plurality of candidate subsets of initial label indicators comprises assigning each initial label indicator to one of the candidate subsets of initial label indicators based on the decoded data.

3. The method of claim 2, further comprising receiving an edge indicator defining a location of an edge of the support structure in the plane; wherein assigning the initial label indicators among a plurality of candidate subsets of initial label indicators further comprises: for initial label indicators that overlap with the edge indicator, assigning each initial label indicator to one of the candidate subsets of initial label indicators based on the decoded data.

4. The method of claim 3, wherein the edge indicator is a shelf edge indicator.

5. The method of claim 3, wherein assigning the initial label indicators among a plurality of candidate subsets of initial label indicators further comprises, for initial label indicators that do not overlap with the edge indicator: assigning the initial label indicators to one of a plurality of sets based on the decoded data;determining a mean position of the initial label indicators within each set; andassigning the initial label indicators within each set to the candidate subsets of initial label indicators based on a distance from each of the initial label indicators to the mean position.

6. The method of claim 1, further comprising: determining an aggregate surface area for each set of projections; andselecting, as the recovered depth, the one of the projection depths corresponding to a minimum aggregate surface area.

7. The method of claim 1, further comprising, prior to generating the sets of projections: generating, for each of a plurality of coarse projection depths relative to the plane, a set of coarse projections of the initial label indicators in the candidate subset of initial label indicators;selecting one of the coarse projection depths; andgenerating the plurality of projection depths based on the selected coarse projection depth.

8. The method of claim 7, wherein generating the plurality of projection depths includes adding a predetermined increment to the selected coarse projection depth.

9. The method of claim 1, wherein the support structure is one of a shelf and a table.

10. A computing device for recovering label positions, comprising: a memory; andan imaging controller connected to the memory, the imaging controller configured to:receive (i) a definition of a plane containing edges of a support structure, and (ii) a plurality of initial label indicators having locations on the plane, where an initial label indicator indicates a single physical label in one image frame of a plurality of image frames;assign the plurality of initial label indicators among a plurality of candidate subsets of initial label indicators, each candidate subset of initial label indicators representing the single physical label;for each candidate subset of initial label indicators: generate, for each of a plurality of projection depths relative to the plane, a set of projections of the initial label indicators in the candidate subset of initial label indicators;select, as a recovered depth for the candidate subset of initial label indicators, one of the projection depths based on the sets of projections; andgenerate a recovered position for the candidate subset of initial label indicators based on the recovered depth; andthe imaging controller further configured to store the recovered positions in the memory.

11. The computing device of claim 10, wherein each initial label indicator includes decoded data; and wherein the imaging controller is further configured to assign the initial label indicators among a plurality of candidate subsets of initial label indicators by assigning each initial label indicator to one of the candidate subsets based on the decoded data.

12. The computing device of claim 11, wherein the imaging controller is further configured to: receive an edge indicator defining a location of an edge of the support structure in the plane;assign the initial label indicators among a plurality of candidate subsets of initial label indicators further by: for initial label indicators that overlap with the edge indicator, assigning each initial label indicator to one of the candidate subsets of initial label indicators based on the decoded data.

13. The computing device of claim 12, wherein the edge indicator is a shelf edge indicator.

14. The computing device of claim 12, wherein the imaging controller is further configured to assign the initial label indicators among a plurality of candidate subsets of initial label indicators by, for initial label indicators that do not overlap with the edge indicator: assigning the initial label indicators to one of a plurality of sets based on the decoded data;determining a mean position of the initial label indicators within each set; andassigning the initial label indicators within each set to the candidate subsets of initial label indicators based on a distance from each of the initial label indicators to the mean position.

15. The computing device of claim 10, wherein the imaging controller is further configured to: determine an aggregate surface area for each set of projections; andselect, as the recovered depth, the one of the projection depths corresponding to a minimum aggregate surface area.

16. The computing device of claim 10, wherein the imaging controller is further configured to, prior to generating the sets of projections: generate, for each of a plurality of coarse projection depths relative to the plane, a set of coarse projections of the initial label indicators in the candidate subset of initial label indicators;select one of the coarse projection depths; andwherein the imaging controller is further configured to generate the plurality of projection depths based on the selected coarse projection depth.

17. The computing device of claim 16, wherein the imaging controller is further configured to generate the plurality of projection depths by adding a predetermined increment to the selected coarse projection depth.

18. The computing device of claim 10, wherein the support structure is one of a shelf and a table.