Method, system and apparatus for mitigating data capture light leakage

Abstract

A mobile automation apparatus includes: a chassis supporting a locomotive assembly and an illumination assembly configured to emit light over a field of illumination (FOI); a navigational controller connected to the locomotive assembly and the illumination assembly, the navigational controller configured to: obtain a task definition identifying a region in a facility; generate a data capture path traversing the region from an origin location to a destination location, the data capture path including: (i) an entry segment beginning at the origin location and defining a direction of travel angled away from a support structure in the region such that a lagging edge of the FOI intersects with the support structure; and (ii) an exit segment defining a direction of travel angled towards the support structure and terminating at the destination location such that a leading edge of the FOI intersects with the support structure.

Description

BACKGROUND

Environments in which objects are managed, such as retail facilities, warehousing and distribution facilities, and the like, may store such objects in regions such as aisles of shelf modules or the like. For example, a retail facility may include objects such as products for purchase, and a distribution facility may include objects such as parcels or pallets.

A mobile automation apparatus may be deployed within such facilities to perform tasks at various locations. For example, a mobile automation apparatus may be deployed to capture data representing an aisle in a retail facility for use in identifying products that are out of stock, incorrectly located, and the like. The dynamic nature of environments such as the retail facility may complicate data capture. For example, to avoid interfering with customers, staff or the like within the facility, the mobile apparatus may begin data capture inside the aisle. However, this may lead to incomplete capture of the aisle.

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. 2 depicts a mobile automation apparatus in the system of FIG. 1.

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

FIG. 4 is a flowchart of a method of mitigating data capture light leakage in the system of FIG. 1.

FIG. 5 is a diagram of a data capture path resulting in light leakage beyond the end of an aisle.

FIG. 6 is a diagram illustrating operational constraints employed during generation of a data capture path in the method of FIG. 4.

FIG. 7 is a diagram illustrating a data capture path mitigating light leakage according to the method of FIG. 4.

FIG. 8 is a diagram illustrating another data capture path mitigating light leakage according to the method of FIG. 4.

FIG. 9 is a diagram illustrating a determination of a minimum orientation for the apparatus of FIG. 1 in an entry segment generated in the method of FIG. 4.

FIG. 10 is a diagram illustrating a determination of a maximum orientation for the apparatus of FIG. 1 in an exit segment generated in 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 mobile automation apparatus including: a chassis supporting a locomotive assembly and an illumination assembly configured to emit light over a field of illumination (FOI); a navigational controller connected to the locomotive assembly and the illumination assembly, the navigational controller configured to: obtain a task definition identifying a region in a facility; generate a data capture path traversing the region from an origin location to a destination location, the data capture path including: (i) an entry segment beginning at the origin location and defining a direction of travel angled away from a support structure in the region such that a lagging edge of the FOI intersects with the support structure; and (ii) an exit segment defining a direction of travel angled towards the support structure and terminating at the destination location such that a leading edge of the FOI intersects with the support structure.

Additional examples disclosed herein are directed to a method in a navigational controller, the method comprising: obtaining a task definition identifying a region in a facility; generating a data capture path for a mobile automation apparatus to traverse the region from an origin location to a destination location, the data capture path including: (i) an entry segment beginning at the origin location and defining a direction of travel angled away from a support structure in the region such that a lagging edge of the FOI intersects with the support structure; and (ii) an exit segment defining a direction of travel angled towards the support structure and terminating at the destination location such that a leading edge of the FOI intersects with the support structure.

Further examples disclosed herein are directed to a non-transitory computer-readable medium storing computer-readable instructions for execution by a navigational controller, wherein execution of the computer-readable instructions configures the navigational controller to: obtain a task definition identifying a region in a facility; generate a data capture path for a mobile automation apparatus to traverse the region from an origin location to a destination location, the data capture path including: (i) an entry segment beginning at the origin location and defining a direction of travel angled away from a support structure in the region such that a lagging edge of the FOI intersects with the support structure; and (ii) an exit segment defining a direction of travel angled towards the support structure and terminating at the destination location such that a leading edge of the FOI intersects with the support structure.

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 104 via communication links 105, illustrated in the present example as including wireless links. In the present example, the links 105 are provided by a wireless local area network (WLAN) deployed via one or more access points (not shown). In other examples, the server 101, the client device 104, or both, are located remotely (i.e. outside the environment in which the apparatus 103 is deployed), and the links 105 therefore include wide-area networks such as the Internet, mobile networks, and the like. The system 100 also includes a dock 106 for the apparatus 103 in the present example. The dock 106 is in communication with the server 101 via a link 107 that in the present example is a wired link. In other examples, however, the link 107 is a wireless link.

The client computing device 104 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 104 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 104 in communication with the server 101 via respective links 105.

The system 100 is deployed, in the illustrated example, in a retail facility including a plurality of support structures such as shelf modules 110-1, 110-2, 110-3 and so on (collectively referred to as shelf modules 110 or shelves 110, and generically referred to as a shelf module 110 or 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.

The shelf modules 110 (also referred to as sub-regions of the facility) are typically arranged in a plurality of aisles (also referred to as regions of the facility), 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 facility, 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 the support surface 117-3 and to 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 equipped with a plurality of navigation and data capture sensors 108, 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). The apparatus 103 is deployed within the retail facility and, via communication with the server 101 and use of the sensors 108, navigates autonomously or partially autonomously along a length 119 of at least a portion of the shelves 110.

While navigating among the shelves 110, the apparatus 103 can capture images, depth measurements and the like, representing the shelves 110 (generally referred to as shelf data or captured data). Navigation may be performed according to a frame of reference 102 established within the retail facility. The apparatus 103 therefore tracks its pose (i.e. location and orientation) in the frame of reference 102. The apparatus 103 can navigate the facility by generating paths from origin locations to destination locations. For example, to traverse an aisle while capturing data representing the shelves 110 of that aisle, the apparatus 103 can generate a path that traverses the aisle. As will be discussed in greater detail below, the path generated by the apparatus enables data capture while also mitigating light leakage from an illumination assembly of the apparatus into portions of the facility outside the target aisle, where such light may interfere with customers, another apparatus 103, or the like.

The server 101 includes a special purpose controller, such as a processor 120, specifically designed to control and/or assist the mobile automation apparatus 103 to navigate the environment and to capture data. The processor 120 is interconnected with a non-transitory computer readable storage medium, such as a memory 122, having stored thereon computer readable instructions for performing various functionality, including control of the apparatus 103 to navigate the modules 110 and capture shelf data, as well as post-processing of the shelf data. The memory 122 can also store data for use in the above-mentioned control of the apparatus 103, such as a repository 123 containing a map of the retail environment and any other suitable data (e.g. operational constraints for use in controlling the apparatus 103, data captured by the apparatus 103, and the like).

The memory 122 includes a combination of volatile memory (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 a 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 104 and the dock 106—via the links 105 and 107. The links 105 and 107 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 facility via the deployment of one or more wireless access points. The links 105 therefore include either or both wireless links between the apparatus 103 and the mobile device 104 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 processor 120 can therefore obtain data captured by the apparatus 103 via the communications interface 124 for storage (e.g. in the repository 123) and subsequent processing (e.g. to detect objects such as shelved products in the captured data, and detect status information corresponding to the objects). The server 101 may also transmit status notifications (e.g. notifications indicating that products are out-of-stock, in low stock or misplaced) to the client device 104 responsive to the determination of product status data. The client device 104 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.

Turning now to FIG. 2, the mobile automation apparatus 103 is shown in greater detail. The apparatus 103 includes a chassis 201 containing a locomotive assembly 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 108 mentioned earlier. In particular, the sensors 108 include at least one imaging sensor 207, such as a digital camera. In the present example, the mast 205 supports seven digital cameras 207-1 through 207-7 oriented to face the shelves 110.

The mast 205 also supports at least one depth sensor 209, such as a 3D digital camera capable of capturing both depth data and image data. The apparatus 103 also includes additional depth sensors, such as LIDAR sensors 211. In the present example, the mast 205 supports two LIDAR sensors 211-1 and 211-2. As shown in FIG. 2, the cameras 207 and the LIDAR sensors 211 are arranged on one side of the mast 205, while the depth sensor 209 is arranged on a front of the mast 205. That is, the depth sensor 209 is forward-facing (i.e. captures data in the direction of travel of the apparatus 103), while the cameras 207 and LIDAR sensors 211 are side-facing (i.e. capture data alongside the apparatus 103, in a direction perpendicular to the direction of travel). In other examples, the apparatus 103 includes additional sensors, such as one or more RFID readers, temperature sensors, and the like.

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 cameras 207 and lidars 211 are oriented on the mast 205 such that the fields of view of the sensors each face a shelf 110 along the length 119 of which the apparatus 103 is traveling. As noted earlier, the apparatus 103 is configured to track a pose of the apparatus 103 (e.g. a location and orientation of the center of the chassis 201) in the frame of reference 102, permitting data captured by the apparatus 103 to be registered to the frame of reference 102 for subsequent processing.

Referring to FIG. 3, certain components of the mobile automation apparatus 103 are shown, in addition to the cameras 207, depth sensor 209, lidars 211, and illumination assemblies 213 mentioned above. The apparatus 103 includes a special-purpose controller, such as a processor 300, interconnected with a non-transitory computer readable storage medium, such as a memory 304. The memory 304 includes a suitable combination of volatile memory (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 300 and the memory 304 each comprise one or more integrated circuits. The memory 304 stores computer readable instructions for execution by the processor 300. In particular, the memory 304 stores a localization application 308 which, when executed by the processor 300, configures the processor 300 to perform various functions related to generating data capture paths that mitigate light leakage from the illumination assemblies outside the target aisle.

The processor 300, when so configured by the execution of the application 308, may also be referred to as a navigational controller 300. Those skilled in the art will appreciate that the functionality implemented by the processor 300 via the execution of the application 308 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 304 may also store a repository 312 containing, for example, a map of the environment in which the apparatus 103 operates, for use during the execution of the application 308 (i.e. during the generation of data capture paths). The apparatus 103 also includes a communications interface 316 enabling the apparatus 103 to communicate with the server 101 (e.g. via the link 105 or via the dock 106 and the link 107), for example to receive instructions to navigate to specified locations and initiate data capture operations.

In addition to the sensors mentioned earlier, the apparatus 103 includes a motion sensor 318, such as one or more wheel odometers coupled to the locomotive assembly 203. The motion sensor 318 can also include, in addition to or instead of the above-mentioned wheel odometer(s), an inertial measurement unit (IMU) configured to measure acceleration along a plurality of axes.

The actions performed by the apparatus 103, and specifically by the processor 300 as configured via execution of the application 308, to generate data capture paths mitigating illumination leakage will now be discussed in greater detail with reference to FIG. 4. FIG. 4 illustrates a method 400 of mitigating light leakage outside a target aisle from the illumination assemblies 213 during data capture tasks. The method 400 will be described in conjunction with its performance in the system 100, and in particular by the apparatus 103, with reference to the components illustrated in FIGS. 2 and 3. As will be apparent in the discussion below, in other examples, some or all of the processing performed by the server 101 may be performed by the apparatus 103, and some or all of the processing performed by the apparatus 103 may be performed by the server 101.

Beginning at block 405, the apparatus 103 obtains a task definition, for example by receiving the task definition from the server 101 over the link 107. The task definition identifies a region of the facility. In the present example, the region is an aisle composed of a set of contiguous shelf modules 110 (i.e. sub-regions), and the task definition may also identify the individual modules 110. The task definition, in other words, instructs the apparatus 103 to travel to the identified aisle and capture data representing that aisle. Responsive to receiving the task definition, the apparatus 103 navigates to the identified aisle (e.g. to one end of the aisle, specified in the task definition). Navigation to the aisle can be accomplished through the implementation of any of a variety of path planning and navigational algorithms by the apparatus, with or without the assistance of the server 101, as will be understood by those skilled in the art.

To capture the data, the apparatus 103 travels along the aisle (as noted in connection with the length 119 in FIG. 1). During the traverse of the target aisle, the apparatus 103 captures images, depth measurements and the like with the sensors 108 (e.g. the cameras 207 and lidars 211). In addition, the apparatus 103 typically activates the illumination assemblies throughout the traverse of the target aisle, to illuminate the shelf modules 110.

Turning to FIG. 5, an example aisle 500 including modules 504-1, . . . , 504-5, which may each have similar structural features to the modules 110 discussed in connection with FIG. 1. In order to capture data representing the modules 504, the apparatus 103 may travel along a path 508 extending from an initial position (in which the apparatus 103 is shown in dashed lines) to a final position (in which the apparatus 103 is shown in solid lines). As seen in FIG. 5, the initial position and the final position are outside the ends 512-1 and 512-2 of the aisle 500 (the extents of which are indicated by dashed lines). As a result, a field of illumination (FOI) 516 of the illumination assemblies 213 extends beyond the ends 512 of the aisle 500, and illuminates areas 520 of the facility that may contain customers, another apparatus 103, or the like. In other words, the edges of the FOI do not intersect with the aisle. Instead, at the initial position, a lagging edge 524 of the FOI 516 does not intersect with the aisle 500, and at the final position a leading edge 528 of the FOI 516 does not intersect with the aisle 500. As will be apparent to those skilled in the art, the edges 524 and 528 of the FOI 516 have fixed angles, e.g. relative to a forward direction 532 of the apparatus 103, as a result of position of the illumination assemblies 213 being fixed on the mast 205.

Returning to FIG. 4, the apparatus 103, via performance of the method 400, generates a path that, in contrast with the path 508 shown in FIG. 5, reduces or eliminates the areas 520 of light leakage. At block 410 the apparatus 103 retrieves operational constraints applying to travel along the aisle identified in the task definition from block 405. Operational constraints include, in the present example, an optimal distance from the shelf modules 110 (or, more specifically, from a plane containing the shelf edges 118, referred to herein as the shelf plane or support structure plane) for data capture. The operational constraints can also include an optimal data capture angle, defined as an angle between the orientation of the apparatus and the shelf plane. Typically, the optimal data capture angle is zero (i.e. such that the apparatus 103 travels parallel to the shelf plane).

The operational constraints can also include minimum and maximum permissible data capture distances, defined relative to the shelf plane, as well as distances from the ends 512 of the aisle 500 at which the data capture path begins and ends (i.e. specifying how far outside the aisle 500 the data capture operation must begin and end). Various other operational constraints may also be retrieved at block 410, such as minimum and/or maximum travel speeds for the apparatus 103, maximum angular changes between poses in the navigational path to be generated as discussed below, and the like.

Referring to FIG. 6, the aisle 500 is shown in full, including the end modules 504-1 and 504-5 as well as intermediate modules 504-2, 504-3 and 504-4. FIG. 6 also illustrates certain examples of operational constraints retrieved at block 410. For example, FIG. 6 illustrates an optimal distance D1 between a shelf plane 600 and the apparatus 103 for data capture. FIG. 6 also illustrates a distance D2 beyond each end 512 of the aisle at which the path the apparatus 103 travels is to begin and end. Further, it is assumed that the operational constraints include an optimal data capture angle of zero degrees. In other words, according to the operational constraints, the optimal path travelled by the apparatus 103 is the path 508, mentioned earlier, which begins at the distance D2 outside the first end 512-1 of the aisle 500, travels parallel to the shelf plane 600 at a distance D1 from the shelf plane 600, and terminates at a distance D1 outside the second end 512-2 of the aisle 500. As seen in connection with FIG. 5, however, such a path results in illumination leakage beyond the ends of the aisle 500.

Returning to FIG. 4, at block 415, having retrieved the operational constraints, the apparatus 103 therefore generates a data capture path that includes angled entry and exit segments. An example data capture path 700 is shown in FIG. 7. The path 700 includes a sequence of poses 704-1, . . . , 704-n, each defining a location (e.g. according to the frame of reference 102) and an orientation. The orientation of each pose, in the present example, is defined as an angle between the forward direction 532 of the apparatus 103 and the shelf plane 600.

As seen in FIG. 7, the path 700 includes an entry segment 708 defining a travel direction that is initially angled away from the shelf plane 600, before returning towards the shelf plane 600. The path 700 also includes an exit segment 712 that defines a travel direction that is angled towards the shelf plane 600 as the apparatus approaches the destination location (i.e. the pose 704-n). An initial portion of the exit segment 712 angles away from the shelf plane. As will be apparent in the discussion below, however, in some embodiments the portion of the entry segment angled towards the shelf plane 600 can be omitted, as can the portion of the exit segment angled away from the shelf plane 600.

Additionally, the path 700 includes a main, or central, segment 716 that defines a travel direction substantially parallel to the shelf plane 600. In some embodiments (e.g. depending on the length of the aisle 500) the main segment 716 can be omitted, and the path 700 can consist solely of an entry segment 708 and an exit segment 712. In the illustrated example, the origin location (i.e. the location of the pose 704-1) and the destination (i.e. the location of the pose 704-n) are at the optimal distance D1 from the shelf plane 600. The main segment 716 also places the apparatus 103 at the optimal distance D1 from the shelf plane 600. The outwardly angled (i.e. away from the shelf plane 600) portion of the entry segment guides the apparatus 103 away from the optimal distance, and therefore the entry segment also includes an inwardly angled portion to return to the optimal distance and begin the main segment 716. Likewise, in order to travel angled towards the shelf plane 600 and arrive at the destination pose 704-n, the apparatus 103 is required to depart from the optimal distance, and the exit segment 712 therefore includes an outwardly angled portion immediately following the main segment 716.

As is evident from FIG. 7, the lagging edge 524 of the FOI 516 intersects the aisle boundary (in particular, the end 512-1 of the aisle) at a point 720 when the apparatus 103 is at the pose 704-1. The lagging edge 524 of the FOI 516 for subsequent poses in the entry segment 708 also intersects with the aisle 500 at various other points. In other words, the outward angles of the poses of the entry segment mitigate or eliminate light leakage outside the aisle during execution of the path 700. Similarly, at the destination pose 704-n the leading edge 528 of the FOI 516 intersects the aisle boundary at a point 724 on the second end 512-2 of the aisle 500.

As noted above, in other embodiments the entry and exit segments define only travel directions angled away from and towards, respectively, the shelf plane 600. That is, the inwardly-angled portion of the entry segment and the outwardly-angled portion of the exit segment can be omitted. Turning to FIG. 8, an example path 800 is illustrated, including an entry segment 808, an exit segment 812, and a main segment 816. The entry and exit segments 808 and 812, as seen in FIG. 8, are outwardly angled and inwardly angled, respectively. The entry segment 808 begins (at an origin pose 804-1) closer to the shelf plane 600 than the optimal distance, and therefore terminates at the optimal distance without the need to return towards the shelf plane 600. The exit segment 812 therefore begins (at the end of the main segment 816) at the optimal distance, and simply angles inwards towards the shelf plane, to terminate at the destination pose 804-n. As also seen in FIG. 8, the path 800 results in the lagging edge 524 intersecting with a boundary of the aisle 500 (specifically, the end

Various other configurations of paths will now occur to those skilled in the art. The apparatus 103 can implement any of a variety of suitable path generation mechanisms for generating the poses 704 and 804 of the paths 700 and 800. During such path generation, the apparatus 103 may apply an additional orientation constraint beyond those noted earlier, such as minimum and maximum permissible data capture distances and the like. The constraint applied to the orientation of each pose in the entry segment (e.g. 708, 808) and exit segment (e.g. 712, 812) defines a threshold beyond which light leakage outside the aisle 500 may occur. Determination of the above-mentioned constraint may be performed as discussed below, in connection with FIGS. 9 and 10.

FIG. 9 illustrates the apparatus 103 along with the FOI 516 (including the edges 524 and 528 noted above). An angle 900 between the forward direction 532 and the lagging edge 524 is stored in the memory 304, as is an angle 904 between the forward direction 532 and the leading edge 528.

FIG. 9 also illustrates the module 504-1 of the aisle 500, and a location 908 of a pose to be generated for a data capture path. To determine a minimum orientation required to prevent light leakage during an entry segment of the path, the apparatus 103 identifies a lagging aisle boundary 912, defined as the furthest extent of the aisle 500 that is visible from the pose location 908 in the lagging direction (i.e. further from the destination of the path than any other portion of the aisle 500 visible from the pose location 908). The boundary may be detected, for example, from the map stored in the repository 312, based on the pose location 908. For example, the apparatus 103 can identify the boundary 912 (and other boundaries mentioned herein) by determining each point on the module 504-1 to which the pose location 908 has line-of-sight, and selecting the point at the greatest distance from the pose location 908.

The lagging boundary 912, in the present example, is a corner of the module 504-1. Based on an angle 916 between the shelf plane 600 (or more specifically, a plane 920 parallel to the shelf plane 600) and the boundary 912, and on the angle 900 mentioned above, a minimum orientation 924 can be determined. That is, the apparatus 103 can assign, e.g. based on other constraints such as the optimal distance and the like, any orientation for the pose location 908 that does not fall below (i.e. closer to the plane 920) the minimum orientation 924.

FIG. 10 illustrates the determination of a maximum orientation for a pose 1000 relative to the module 504-n. In particular, the apparatus 103 identifies a leading boundary 1004 of the aisle 500 (in this case, a corner of the module 504-n), and determines an angle 1008 between the plane 920 and the leading boundary 1004. The leading boundary 1004, in contrast to the lagging boundary discussed above, is a point on the aisle 500 visible from the pose location 1000 that is closer to the destination of the path than any other visible point on the aisle 500.

Based on the angle 1008 and the known angle 904 of the leading edge 528 of the FOI, the apparatus 103 determines a maximum orientation 1012 for the pose location 1000. That is, to prevent light leakage beyond the boundary 1004, the orientation of the apparatus 103 at the pose location 1000 must remain below (i.e. inclined towards the shelf plane 600) the orientation 1012.

Referring briefly again to FIG. 4, at block 420 the processor 300 controls the apparatus 103 (e.g. the locomotive assembly 203) to travel along the path generated at block 415. During traversal of the aisle 500, the processor 300 also controls the illumination assemblies 213 to illuminate the aisle 500, and one or more of the data capture sensors (e.g. the cameras 207 and lidars 211) to capture images, depth measurements and the like representing the aisle 500.

Variations to the above systems and methods are contemplated. For example, in some embodiments, entry and exit path segments can be predefined and stored in the memory 304. The apparatus 103 can then, at block 415, retrieve the entry and exit path segments from the memory 304 rather than generating the segments.

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 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 mobile automation apparatus, comprising: a chassis supporting (i) a locomotive assembly, (ii) a data capture sensor facing outward from a first side of the chassis, and (iii) an illumination assembly configured to emit light over a field of illumination (FOI) facing outward from the first side of the chassis;a navigational controller connected to the locomotive assembly and the illumination assembly, the navigational controller configured to: obtain a task definition identifying a region in a facility, the region containing a support structure;generate a data capture path traversing the region from an origin location to a destination location, the data capture path including: (i) an entry segment beginning at the origin location and defining a first direction of travel configured to position the support structure on the first side of the chassis and to angle the chassis away from the support structure such that a lagging edge of the FOI intersects with the support structure; and(ii) an exit segment defining a second direction of travel configured to position the support structure on the first side of the chassis and to angle the chassis towards the support structure, the exit segment terminating at the destination location such that a leading edge of the FOI intersects with the support structure.

2. The mobile automation apparatus of claim 1, wherein the navigational controller is further configured to control the locomotive assembly to traverse the region according to the data capture path.

3. The mobile automation apparatus of claim 2, wherein the navigational controller is further configured, while traversing the region according to the data capture path, to: (i) control the illumination assembly to illuminate the support structure, and (ii) control the data capture sensor to capture data representing the support structure.

4. The mobile automation apparatus of claim 1, wherein the navigational controller is further configured to generate the data capture path including the entry segment, the exit segment and a main segment between the entry segment and the exit segment.

5. The mobile automation apparatus of claim 4, wherein the main segment defines a third direction of travel parallel to the support structure.

6. The mobile automation apparatus of claim 1, wherein the entry segment includes a sequence of poses, and wherein the navigational controller is further configured, in order to generate each pose of the entry segment, to: determine a pose location for the pose; andidentify a lagging support structure boundary based on the pose location.

7. The mobile automation apparatus of claim 6, wherein the navigational controller is further configured, in order to generate each pose of the entry segment, to: determine a minimum orientation relative to a support structure plane based on (i) an angle of the lagging edge of the FOI and (ii) an angle between the support structure plane and the lagging support structure boundary.

8. The mobile automation apparatus of claim 1, wherein the exit segment includes a sequence of poses, and wherein the navigational controller is further configured, in order to generate each pose of the exit segment, to: determine a pose location for the pose; andidentify a leading support structure boundary based on the pose location.

9. The mobile automation apparatus of claim 8, wherein the navigational controller is further configured, in order to generate each pose of the exit segment, to: determine a maximum orientation relative to a support structure plane based on (i) an angle of the leading edge of the FOI and (ii) an angle between the support structure plane and the leading support structure boundary.

10. A method in a navigational controller, the method comprising: obtaining a task definition identifying a region in a facility, the region containing a support structure;generating a data capture path for a mobile automation apparatus to traverse the region from an origin location to a destination location, the mobile automation apparatus including a chassis supporting (i) a locomotive assembly, (ii) a data capture sensor facing outward from a first side of the chassis, and (iii) an illumination assembly configured to emit light over a field of illumination (FOI) facing outward from the first side of the chassis;wherein generating the data capture path includes generating: (i) an entry segment beginning at the origin location and defining a first direction of travel configured to position the support structure on the first side of the chassis and to angle the chassis away from the support structure in the region such that a lagging edge of the FOI intersects with the support structure; and(ii) an exit segment defining a second direction of travel configured to position the support structure on the first side of the chassis and to angle the chassis towards the support structure, the exit segment terminating at the destination location such that a leading edge of the FOI intersects with the support structure.

11. The method of claim 10, further comprising: controlling a locomotive assembly of the mobile automation apparatus to traverse the region according to the data capture path.

12. The method of claim 11, further comprising, while traversing the region according to the data capture path: controlling an illumination assembly of the mobile automation apparatus to illuminate the support structure; andcontrolling a data capture sensor of the mobile automation apparatus to capture data representing the support structure.

13. The method of claim 10, wherein generating the data capture path comprises generating the data capture path including the entry segment, the exit segment and a main segment between the entry segment and the exit segment.

14. The method of claim 13, wherein the main segment defines a third direction of travel parallel to the support structure.

15. The method of claim 10, wherein the entry segment includes a sequence of poses, and wherein generating each pose of the entry segment comprises: determining a pose location for the pose; andidentifying a lagging support structure boundary based on the pose location.

16. The method of claim 15, wherein generating each pose of the entry segment further comprises determining a minimum orientation relative to a support structure plane based on (i) an angle of the lagging edge of the FOI and (ii) an angle between the support structure plane and the lagging support structure boundary.

17. The method of claim 10, wherein the exit segment includes a sequence of poses, and wherein generating each pose of the exit segment comprises: determining a pose location for the pose; andidentifying a leading support structure boundary based on the pose location.

18. The method of claim 17, wherein generating each pose of the exit segment further comprises determining a maximum orientation relative to a support structure plane based on (i) an angle of the leading edge of the FOI and (ii) an angle between the support structure plane and the leading support structure boundary.

19. A non-transitory computer-readable medium storing computer-readable instructions for execution by a navigational controller, wherein execution of the computer-readable instructions configures the navigational controller to: obtain a task definition identifying a region in a facility;generate a data capture path for a mobile automation apparatus to traverse the region from an origin location to a destination location, the mobile automation apparatus including a chassis supporting (i) a locomotive assembly, (ii) a data capture sensor facing outward from a first side of the chassis, and (iii) an illumination assembly configured to emit light over a field of illumination (FOI) facing outward from the first side of the chassis;wherein generation of the data capture path includes generation of: (i) an entry segment beginning at the origin location and defining a first direction of travel configured to position the support structure on the first side of the chassis and to angle the chassis away from the support structure in the region such that a lagging edge of the FOI intersects with the support structure; and(ii) an exit segment defining a second direction of travel configured to position the support structure on the first side of the chassis and to angle the chassis towards the support structure, the exit segment terminating at the destination location such that a leading edge of the FOI intersects with the support structure.