BACKGROUND

Field of the Invention

[0001] The present disclosure relates to autonomous vehicles, and more

specifically, to autonomous vehicles performing inventory management.

Related Art

[0002] Detecting and counting items in large warehouses or storage yards may be important to maintaining an inventory. Initially, related art systems have relied on manual inspection of pallet stacks or shelves to determine supplies. More recently, sensors, such as RFID tags, or bar codes have been integrated to increase the speed or accuracy of manual inspection. However, such systems still do not allow for continuous monitor or updating of inventory levels within the warehouse without requiring sensors be placed on every item or pallet. Existing systems do not provide an autonomous vehicle surveying the warehouse or storage yard in a continuous manner to update inventory levels.

SUMMARY OF DISCLOSURE

[0003] Aspects of the present application may include an inventory management system for managing a plurality of inventory items stored in a storage area. The inventory management system may include an autonomous vehicle configured to move within the storage area and a computing device communicatively coupled to the autonomous vehicle. The autonomous vehicle may include a beacon configured to facilitate detection of a current position of the autonomous vehicle based on signal tri angulation, a sensor configured to detect information indicative of a number of inventory items at the current position of the autonomous vehicle, and a wireless data link configured to transmit a signal indicative of the number of inventory items. The computing device being configured to facilitate detection of a position of the autonomous vehicle based on the beacon, and update an inventory of the storage area based on the signal indicative of the number of inventory items.

[0004] Additional aspects of the present application may include an autonomous vehicle for moving within a storage area and provide updated counts of inventor items within the storage area. The autonomous vehicle may include a beacon configured to facilitate detection of a current position of the autonomous vehicle based on signal tri angulation, at least one sensor configured to detect information indicative of a number of inventory items at the current position of the autonomous vehicle, and a wireless data link configured to transmit a signal indicative of the number of inventory items to a computing device communicatively coupled to the autonomous vehicle configured to update an inventory of the storage area based on the signal indicative of the number of inventory items.

[0005] Aspects of the present application may also include a method of performing an inventory of items stored within a storage area using an autonomous vehicle moving within the storage area. The method may include detecting a position of the autonomous vehicle within the storage area, measuring an altitude of autonomous vehicle and a distance between the autonomous vehicle and a stack of items stored within the storage area, calculating a number of items in the stack of items based on the measured altitude, the measured distance and the detected position of the autonomous vehicle, and updating inventory records based on the calculated number of items in the stack.

[0006] Further aspects of the present application may include an inventory management system for managing a plurality of inventory items stored in a storage area. The inventory management system may include an autonomous vehicle configured to move within the storage area and computing means communicatively coupled to the autonomous vehicle. The autonomous vehicle may include means detection of a current position of the autonomous vehicle based on signal tri angulation, means for detecting information indicative of a number of inventory items at the current position of the autonomous vehicle, and means for transmit a signal indicative of the number of inventory items. The computing means may include be means for detecting a position of the autonomous vehicle based on the beacon, and means for updating an inventory of the storage area based on the signal indicative of the number of inventory items.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 illustrates a schematic representation of an inventory management system in accordance with example implementations of the present application.

[0008] FIG. 2 illustrates another schematic representation of the inventory management system illustrated in FIG. 1.

[0009] FIG. 3 illustrates another schematic representation of the inventory management system illustrated in FIGS. 1 and 2. [0010] FIG. 4 illustrates a schematic representation of an unmanned aerial system in accordance with example implementations of the present application.

[0011] FIG. 5 illustrates an overhead map of an inventory management system in accordance with example implementations of the present application.

[0012] FIG. 6 illustrates another overhead map of an inventory management system in accordance with example implementations of the present application.

[0013] FIG. 7 illustrates an overhead inventory map of an inventory management system in accordance with example implementations of the present application.

[0014] FIG. 8 illustrates a flowchart of a process for updating an inventory in accordance with example implementations of the present application.

[0015] FIG. 9 illustrates an example computing environment with an example computer device suitable for controlling an inventory management system in accordance with some example implementations.

DETAILED DESCRIPTION

[0016] The following detailed description provides further details of the figures and example implementations of the present application. Reference numerals and descriptions of redundant elements between figures are omitted for clarity. Terms used throughout the description are provided as examples and are not intended to be limiting. For example, the use of the term "automatic" may involve fully automatic or semiautomatic implementations involving user or operator control over certain aspects of the implementation, depending on the desired implementation of one of ordinary skill in the art practicing implementations of the present application.

[0017] As the market of unmanned aerial systems (UAS) (e.g., drones) has expanded, cheaper models, such as those controlled by smartphones, have become available by many commercial avenues allowing amateur pilots to own what once only belonged to professional companies. These cheaper models may have an elevated level of automation that may allow these vehicles to be capable of flying autonomously. By integrating these UASs with a real-time location system (RTLS), a UAS may be able to navigate indoor facilities with high precision.

[0018] As discussed below with respect to the example implementations below, merging a UAS with an RTLS and additional sensors, it may be possible to create a system where automated drones may navigate autonomously inside a warehouse or storage yard. The additional sensors onboard the drones may collect data about the position and quantity of pallets or boxes inside the warehouse or storage yard. Inventory software may then receive this data and generates a report containing the quantity and position of the products in the warehouse.

[0019] For example, an inventory management system (IMS) may manage data exchanged with the drone to generate a waypoint list where the drone needs to fly over. While the drone is flying, the IMS may receive the drone location from the RTLS system. Height data from an altitude sensor and the distance data measured by a range finder may be sent from the drone. The IMS may calculate the stack height based on the difference between the altitude and measured distance. In some example implementations, the drone can also do this calculation internally and send the stack height directly to the IMS.

Additional specifics of example implementations are discussed in greater detail below with respect to the provided figures.

[0020] FIG. 1 illustrates a schematic representation of an inventory management system (IMS) 100 in accordance with example implementations of the present application. The IMS 100 may be illustrated within a warehouse or other large building in FIG. 1. However, example implementations are not limited to this configuration and may be implemented in other environments as may be apparent to a person of ordinary skill in the art. For example, the IMS 100 may be used in open air stock yards such as lumber yards, junk yards, mineral yards, etc. In other example implementations, the IMS 100 may be used in vehicle storage or sale yards (e.g., car dealerships, car rental facilities, boat sales yards, recreational vehicle (RV) dealerships, or any other facility that might be apparent to a person of ordinary skill in the art).

[0021] Example implementations may also be used as part of attendance monitoring systems or site inspection systems. For example, implementations may be used to monitor attendance of a theme park, sports venue, concert venue, or other venue large numbers of people may be present. Additionally, example implementations may be used to inspect transportation infrastructure such as roads, rail lines, etc. to detect interruptions through height changes in the infrastructure.

[0022] As illustrated in FIGS. 1, the IMS 100 has been installed in a warehouse 10 having a floor 15 and a ceiling 20. In some example implementations, the warehouse may not have a ceiling 20 and may be an open air storage environment, such as a lumber yard, storage yard, vehicle dealership, or other open air storage facility that might be apparent to a person of ordinary skill in the art. [0023] Within the warehouse 10, a plurality of inventory items 25, 30 may be stored. The inventory items 25, 30 may be pallets, boxes, storage container or any other inventory storage structure that might be apparent to a person of ordinary skill in the art. The inventory items 25, 30 may also be an actual piece of inventory without a separate storage structure (e.g., a piece of equipment, vehicle, or other piece of inventory that might be apparent to a person of ordinary skill in the art).

[0024] The inventory items 25 may be positioned in stacks 35 with a standardized height (H _S i) and the inventory items 30 may be positioned in stacks 40 with a standardized height (¾ ₂ ). In some example implementations, the inventory items 25, 30 may be of two or more sizes allowing uniform standardized stacking heights (e.g., Hsi=Hs ₂ ). For example, inventory item 25 is illustrated as being larger than inventory item 30 such that stack 35 of two inventory items 25 is the same standardized height (H _S i) as a stack 40 of four inventory items 30 (!½). In other example implementations, the inventory items 25, 30 may be positioned in stacks 35, 40 having different standardized heights (e.g.,

Hsi≠Hs ₂ ).

[0025] A stack 35, 40 may be considered a standardized stack of the maximum number of inventory items 25, 30 typically stored. In other words, the stack 35, 40 may be a standardized stack representing the maximum stack height before a new stack is started. The standardized height (HSI, Hs ₂ )of the stack 35, 40 may be determined based on the maximum number (Nmaxi, N _ma x2) of inventory items 25, 30 that may be safely stacked and the size (S ₂₅ , S ₃₀ ) of each inventory item 25, 30 in the stack 35, 40 using equations 1 and 2 below:

x S ₂₅ (Equation 1) x S ₃₀ (Equation 2)

[0026] As illustrated, in some example implementations the size (S ₂₅ , S ₃₀ ) may correspond to a unit height associated of each inventory item 25, 30. However, in other example implementations, the size (S ₂₅ , S ₃₀ ) may correspond to a unit width, a unit volume or any other unit dimension associated with each inventory item 25, 30 that might be apparent to a person of ordinary skill in the art.

[0027] The standardized heights (¾ι, ¾ ₂ ), inventory item sizes (S ₂₅ , S ₃₀ ), and maximum number of safely stacked items (Nmaxi, Nmax2) associated with the position of each stack 35, 40 may be stored in a central database of a computing device (such as computing device 905 of computing environment 900 of FIG. 9) of the IMS 100. Alternatively or additionally, the standardized heights (¾i, ¾ ₂ ), inventory item sizes (S ₂ 5, S ₃₀ ), and maximum number of safely stacked items (Nmaxi, max2) may be encoded on a marker (e.g., a bar code, RFID tag, or other marker) located at or adjacent to, the position of each stack 35, 40 within the warehouse 10 and read by a UAS 105 circulating within the warehouse 10 under the control of the IMS 100.

[0028] As illustrated, the IMS 100 may include a UAS 105 configured to move within the warehouse 10 and a real-time location system (RTLS) 130 configured to track the UAS 105. The UAS 105 is not particularly limited and may include a fixed wing drone, a quadcopter, hexacopter, octocopter, or any other UAS device that might be apparent to a person of ordinary skill in the art. Additionally, though the IMS 100 includes a UAS 105, example implementations are not limited to flying drones and may also include a ground-based drones (e.g., crawling drones, tracked drones, wheeled drones, or other ground-based drones that might be apparent to a person of ordinary skill in the art) and water-based drones (e.g., swimming drones, floating drones, submersible drones or other water-based drones that might be apparent to a person of ordinary skill in the art). In some example implementations, the drones may also serve other dual purposes such as moving stacks like forklifts or pallet carriers, in addition to performing inventory management functions. Additional aspects of the UAS 105 are discussed in greater detail below.

[0029] The UAS 105 may be configured to measure a current height Hi or altitude of the UAS 105 relative to the ground 15 in real time. The altitude may be measured using onboard sensors such as Radio Direction and Ranging (RADAR), Light Detection and Ranging (LIDAR), Ultrasound, Stereo-metric cameras, Barometric altimeter, Global Positioning System (GPS) or any other altitude measuring system that might be apparent to a person of ordinary skill in the art. The UAS 105 may relay the measured height Hi to a centralized computing device (such as computing device 905 of computing environment 900 of FIG. 9). Alternatively, the height Hi or altitude may be measured using the RTLS 130 as discussed below and the measured height Hi may be relied to the centralized computing device by the RTLS 130.

[0030] The RTLS 130 may include a plurality of antennas 110, 115, 120 distributed around the warehouse 10 to track and communicate with the UAS 105. In some example implementations, upper antennas 110 may be placed at a position above the top of stacks 35, 40 of inventory items 25, 30, such that the UAS 105 may pass below the upper antennas 110. In example implementations having a ceiling 20, the upper antennas 110 may be placed near the ceiling 20 of the warehouse 10.

[0031] Additionally, lower antennas 115 may be placed at a position near the ground 15 of the warehouse 10 such that the UAS 105 may pass over the lower antennas 115 in some example implementations. Further, intermediate antennas 120 may be placed at an intermediate position between the upper antennas 110 and the lower antennas 115. By providing a plurality of upper antennas 110, lower antennas 115, and intermediate antennas 120 distributed around the warehouse 10, the position of the UAS 105 may be tracked within the 3-dimensional volume of the warehouse 10 in real-time.

[0032] However, example implementations of the RTLS 130 may not require antennas 110, 115, 120 vertically offset at different heights within the warehouse 10. For example, antennas may be placed at a single height to allow tracking of the lateral position of the UAS 105 in two-dimensions, and the onboard sensors (e.g., RADAR, LIDAR, Ultrasound, Barometric altimeter, GPS or any other altitude measuring system) of the UAS 105 may provide the vertical (e.g., altitude (Hi). After the UAS 105 has been calibrated with a height Hi or altitude relative to the ground 15, the UAS 105 may then measure the height of the stacks 35, 40 as discussed below.

[0033] FIG. 2 illustrates another schematic representation of the inventory management system (IMS) 100 illustrated in FIG. 1. In FIG. 2, the UAS 105 has been repositioned above the stack 35 of the inventory items 25 without changing the altitude or height of the UAS 105 relative to the ground 15. Once repositioned, the UAS 105 may use a range finding sensor (e.g., a RADAR sensor, a LIDAR sensor, an ultrasound sensor, stereo metric cameras, or other range finding sensor) to measure the UAS 105 height H ₂ or vertical position above the stack 35 of inventory items 25.

[0034] The UAS 105 may relay the measured height H ₂ to the centralized computing device (such as computing device 905 of computing environment 900 of FIG. 9). Based on the measured UAS 105 height H ₂ above the stack 35 and the measured UAS 105 height Hi (e.g., altitude) above the ground 15, a measured height H _m i of the stack 35 may be determined using equation 3 below.

H _M i=Hi-H ₂ (equation 3)

[0035] Once the measured height H _M i of the stack 35 has been determined, the measured height H _M i of the stack 35 may be compared to the standardized height ¾i of the stack 35 to determine if the stack 35 contains the maximum number (N _M A _XI ) of inventory items 25 associated with the stack 35. The standardized height ¾i may be determined from information stored in the centralized computing device (e.g., computing device 905 of computing environment 900 of FIG. 9) based on the position of the UAS 105 within the warehouse 10 detected by the RTLS 130. For example, the IMS 100 may use the RTLS 130 to triangulate the position of the UAS 105 within the warehouse 10 and use information from an overhead inventory map, such as FIG. 5 discussed below, to identify the standardized height ¾i associated with the UAS's 105 measured position.

[0036] If the measured height H _M i is substantially equal to (within an tolerance range associated with the accuracy of the range finding sensor, for example), the standardized height Hsi associated with the UAS' s 105 position, the number of items in the stack 35 is determined to be the maximum number of safely stacked items (e.g., m _ax i). By having the UAS 105 fly within the warehouse 10 along a predefined route (e.g., FIG. 5), the FMS 1 10 may count the number of full stacks (N _s ) having a standardized height and determine an amount inventory items in the standardized stacks based on the known number of items that may be safely stacked (N _max ) and the number of full stacks (N _s ) counted. The IMS 1 10 may also detect and count partial stacks as illustrated in FIG. 3.

[0037] FIG. 3 illustrates another schematic representation of the inventory management system (IMS) 100 illustrated in FIGS. 1 and 2. In FIG. 3, the UAS 105 has been repositioned above the stack 40 of the inventory items 30 without changing the altitude or height (Hi) of the UAS 105 relative to the ground 15. Additionally, one of the inventory items 30 has been removed as indicated by broken line box 3 OA. Once repositioned, the UAS 105 may use a range finding sensor (e.g., a RADAR sensor, a LIDAR sensor, an ultrasound sensor, stereo metric cameras, or other range finding sensor) to measure the UAS 105 height H ₃ or vertical position above the stack 40 of inventory items 30.

[0038] The UAS 105 may relay the measured height H ₃ to the centralized computing device (such as computing device 905 of computing environment 900 of FIG. 9). Based on the measured UAS 105 height H ₃ above the stack 40 and the measured UAS 105 height Hi (e.g., altitude) above the ground 15, a measured height H _M 2 of the stack 40 may be determined using equation 4 below.

H _M 2=Hi-H ₃ (equation 4) [0039] Once the measured height H _M2 of the stack 40 has been determined, the measured height H _M2 of the stack 40 may be compared to the standardized height ¾ ₂ of the stack 40 to determine if the stack 40 contains the maximum number of inventory items 30 associated with the stack 40. The standardized height H _S2 may be determined from information stored in the centralized computing device (e.g., computing device 905 of computing environment 900 of FIG. 9) based on the position of the UAS 105 within the warehouse 10 detected by the RTLS 130. For example, the IMS 100 may use the RTLS 130 to triangulate the position of the UAS 105 within the warehouse 10 and use information from an overhead inventory map, such as FIG. 5 discussed below, to identify the standardized height H _s2 associated with the UAS's 105 measured position.

[0040] If the measured height Η _Μ2 is not substantially equal to (by an amount greater than a tolerance range associated with the accuracy of the range finding sensor, for example) the standardized height !½ associated with the UAS's 105 position, the number of items (Ns ₂ ) in the stack 35 may be determined based on the standard size (S ₃₀ ) associated with inventory item 30 using Equation 5 below.

(equation 5)

[0041] By having the UAS 105 fly within the warehouse 10 along a predefined route (e.g., FIG. 5), the FMS 110 may count the number of inventory items in partial stacks. The number of inventory items in partial stacks may be combined with the number of inventory items in complete stacks by the IMS 110 to determine a complete inventory of the warehouse 110.

[0042] FIG. 4 illustrates a schematic representation of the UAS 105 in accordance with example implementations of the present application. As discussed above, the UAS 105 may include a fixed wing drone, a quadcopter, hexacopter, octocopter, or any other UAS device that might be apparent to a person of ordinary skill in the art. Additionally, though the FMS 100 includes a UAS 105, example implementations are not limited to flying drones and may also include a ground-based drones (e.g., crawling drones, tracked drones, wheeled drones, or other ground-based drones that might be apparent to a person of ordinary skill in the art) and water-based drones (e.g., swimming drones, floating drones, submersible drones or other water-based drones that might be apparent to a person of ordinary skill in the art).

[0043] As illustrated, the UAS 105 includes a propulsion system 405 configured to generate lift and allow the UAS 105 to maneuver within an warehouse 10 as illustrated in FIGS. 1-3 above. In some, implementations, the propulsion systems 405 may include one or more variable pitch propellers configured to provide vertical thrust and/or horizontal thrust sufficient to lift the UAS 105 off of the ground and maneuver within the warehouse 10. In other example implementations, the propulsion systems 405 may include a turbine thruster or other propulsion mechanism that might be apparent to a person of ordinary skill in the art. Additionally, the propulsion system may also be coupled with wings to assist in lift generation.

[0044] The UAS 105 may also include a wireless data link 410 configured to allow data transfer between the UAS 105 and a central computing device (e.g., computing device 905 of computing environment 900 of FIG. 9) of the IMS 100. The wireless data link 410 may be a cellular transceiver, a WI-FI transceiver, a Bluetooth transceiver, or any other type of data link that might be apparent to a person of ordinary skill in the art. The Wireless data link 410 may allow the central computing device (e.g., computing device 905 of computing environment 900 of FIG. 9) to communicate with the central processor 412 that provides the onboard autonomous control and calculations for the UAS 105.

[0045] The UAS 105 may also include a RTLS beacon 415 configured to interact with the antennas 110, 115, 120 of the RTLS 130 illustrated in FIGS. 1-3. The RTLS beacon 415 may communicate with the antennas 110, 115, 120 to allow the RTLS 130 to triangulate the UAS's 105 position within the warehouse 10. In some example

implementations, the RTLS 130 may use a Time Different of Arrival Technique (TDOA) to determine the beacon location. Using this technique, each antenna 110, 115, 120 may compare the differences in time-stamps received at each antenna to draw distance radials and where the distance radials intersect, the beacon 415 may be located. In other example implementations, the RTLS 130 may use an angle of arrival technique. In this technique, one or more antennas 110, 115,120 may be directional antennas capable of detecting an angle from which a signal was received. The intersection point of angles detected by multiple directional antennas may be the detected location of beacon 415. In some example implementations, the beacon 415 may transmit a signal received by one or more of the antennas 110, 115, 120. In other example implementations, the beacon 415 may receive a signal transmitted by one or more of the antennas 110, 115, 120.

[0046] The UAS 105 also includes a pair of sensors 420, 425 that may be used to determine the altitude of the UAS 105 and distance from the UAS 105 to a structure beneath the UAS 105. In some example implementations, the sensor 420 may be an absolute altitude sensor such as a barometric altimeter, GPS sensor, or other sensor configured to detect an absolute altitude of the UAS 105 with respect to the ground. In these example implementations, the sensor 425 may be a range finding sensor, such as a RADAR range finder, a LIDAR range finder, an ultrasonic range finder or any other range finding sensors that might be apparent to a person of ordinary skill in the art, that can measure a distance between the UAS 105 and a structure below the UAS 105.

[0047] In other example implementations, the sensors 420, 425 may be separate range finding sensors (e.g., RADAR range finders, LIDAR range finders, ultrasonic range finders or any other range finding sensors that might be apparent to a person of ordinary skill in the art) offset at different angles to allow both altitude from ground and distance from a structure beneath the UAS 105 to be detected. In some example implementations, one or both of the sensors 420, 425 may be scanning range finders (e.g., RADAR range finders, LIDAR range finders, ultrasonic range finders or any other range finding sensors that might be apparent to a person of ordinary skill in the art) configured to scan in broad angles (e.g., 90° sweep, 180° sweep, 270° sweep, 360° sweep).

[0048] In some example implementations, the UAS 105 may also include an imaging device 430 such as a bar code reader, a video camera, a still camera or any other imaging device that might be apparent to a person of ordinary skill in the art. The imaging device 430 may be used to perform object recognition techniques to detect information associated with the inventory items. For example, the imaging device 430 may be used to perform character recognition to read labels or bar codes attached to inventory items to allow for item identification. The imaging device 430 may also perform object recognition to identify the inventory items based on a stored library of previously identified potential inventory items. The imaging device 430 may also include stereo metric cameras configured for performing volumetric measurements of inventory items and stacks of inventory items.

[0049] FIG. 5 illustrates an overhead map 500 of an IMS 100 in accordance with an example implementation of the present application. As illustrated, the overhead map 500 includes a plurality of rows 510 representing the rows of the stacks of the inventory goods found throughout the warehouse. Within each row 510, a plurality of stacks may be provided. For each stack in each row, a standardized height value may be stored to distinguish a full or complete stack from a partial or incomplete stack, as discussed in greater detail above. [0050] On the overhead map 500, a circuitous path 515 illustrates a flight path of the UAS 105 over the rows 510. The circuitous path 515 may be programmed into the UAS 105 to be followed on a regular schedule while the UAS 105 takes continuous range measurements using one or more of the sensors 420, 425 to determine the height of each of the stacks within each row 510 as the flight path 515 is followed.

[0051] FIG. 6 illustrates another overhead map 600 of the EVIS 100 in accordance with an example implementation of the present application. Similar to the overhead map 500 of FIG. 5, FIG. 6 illustrates that the overhead map 600 includes a plurality of rows 510 representing the rows of the stacks of the inventory goods found throughout the warehouse. Fig 6 also illustrates a smoothed flight route, as the RTLS may include some noise in the location readings. Therefore, the system may perform filtering to remove the noise readings and keep only the "good readings" (as defined by an error threshold).

[0052] Again, within each row 510, a plurality of stacks may be provided and a standardized height value may be stored for each stack in each row 510. The standard height value may be used to distinguish a full or complete stack from a partial or incomplete stack, as discussed in greater detail above.

[0053] In FIG. 6, the circuitous path 515 representing the flight path of the UAS

105 over the rows 510 has been replaced by a series of grey and black dots 615. The grey and black dots 615 represent range measurements taken over the stacks within each row 510 using the one or more of sensors 420, 425 of the UAS 105. By capturing these range measurements during its flight path, the UAS 105 may determine the height of each of the stacks within each row 510 as the flight path 515 (of FIG. 5) is followed.

[0054] FIG. 7 illustrates an overhead inventory map 700 of the IMS 100 in accordance with an example implementation of the present application. As with FIGS. 5 and 6, FIG. 7 illustrates that the overhead inventory map 700 includes a plurality of rows 510 representing the rows of the stacks of the inventory goods found throughout the warehouse. In FIG. 7, the range measurements 615 illustrated in FIG. 6 have been used to calculate stack heights and are illustrated by shaded squares 705. Each of the shaded squares 705 corresponds to one of the stacks in each row 510. The darkness of the square 705 may correspond to a height of the corresponding stack in each row. For example, a darker square 705 may represent a lower height and a smaller number of inventory items in that stack. Similarly, a lighter square 705 may represent a greater height and a larger number of inventory items in that stack. [0055] FIG. 8 illustrates flowchart of a process 800 for updating an inventory in accordance with example implementations of the present application. The process 800 may be performed using an IMS (such as IMS 100) featuring a UAS (such as UAS 105). In the process 800, the position of the UAS is detected at 805. The position of the UAS may be detected using an RTLS to triangulate the position of the UAS within a warehouse or other inventory storage area. The position of the UAS may also be detected using an onboard position sensor such as a GPS sensor or other positional sensor that might be apparent to a person of ordinary skill in the art.

[0056] In parallel with 805, the altitude (e.g., height above ground (Hi in FIGS. 1-

3) of the UAS and range (e.g., distance (H ₂ , H ₃ in FIGS. 2-3)) from the UAS to the top of a stack may be determined at 810. In some example implementations, the altitude (e.g., Hi in FIGS. 1-3) may be detected using an absolute altitude sensor such as a GPS sensor, barometric pressure sensor, or other altitude sensor. Additionally, the range (e.g., H ₂ , H ₃ in FIGS. 2-3) to the top of the stack may be detected using a range sensor such as a RADAR sensor, LIDAR sensor, ultrasonic sensor, stereo metric sensor or other range sensor that might be apparent to a person of ordinary skill in the art. In other example implementations, the altitude (e.g., Hi in FIGS. 1-3) and the range (e.g., H ₂ , H ₃ in FIGS. 2- 3) may be both calculated using a two or more range sensors RADAR sensor, LIDAR sensor, ultrasonic sensor, stereo metric sensor or other range sensor that might be apparent to a person of ordinary skill in the art offset at a defined angle. For example, a first LIDAR or RADAR sensor may pointed down to identify stack height and a second LIDAR or RADAR pointed around 30° off the stack height pallet height to get also the UAS altitude. If the UAS is flying over a stacked row, but next to a corridor, the 30 degree off-set sensor will point to the corridor, and by the triangle formula it allow calculation of the drone height without relying on an altitude sensor.

[0057] After 805 and 810, a standardized height (e.g., H _S i, H _S2 in FIGS. 1-3) associated with a stack of inventory items located at the detected position of the UAS 105 is determined at 815. In some example implementations, the standardized height (e.g., Hsi, H _S2 in FIGS. 1-3) may be determined by reading, by the UAS 105, a marker located at the detected position of the UAS 105. For example, an RFID tag, bar code, text panel, or other marker associated with the stack may be read by the UAS 105. In other example implementations, the standardized height (e.g., ¾ι, ¾ ₂ ίη FIGS. 1-3) may be determined by consulting a database of stored standardized heights for all stacks within the warehouse cross-referenced with the address or position of each stack. In some example

implementations, a size (e.g., S25, S ₃₀ in FIGS. 1-3) of inventory items may also be determined at 815. The standard size (e.g., S25, S ₃₀ in FIGS. 1-3) of inventory items may also be determined by reading a marker located at the detected position of the UAS 105, or consulting a database of stored inventory item sizes. Alternatively, the standard size (e.g., S25, S ₃ o in FIGS. 1-3) of the inventory items may be measured using stereo metric cameras mounted on the UAS 105, or any other size determination process that might be apparent to a person of ordinary skill in the art.

[0058] At 820, the number of items in the stack is calculated based on the determined standardized height (e.g., !½, Ife in FIGS. 1-3) of the stack, the measured altitude (Hi in FIGS. 1-3) of the UAS and the measured range (H ₂ , H ₃ in FIGS. 2-3) between the top of the stack and the UAS. For example, the actual height of the stack (e.g., H _MI , H _M 2) may be calculated using equation 3 (e.g., Η _ΜΙ =Η _Ι -Η ₂ ) or equation 4 (e.g., H _M 2=H _I -H ₃ ). The calculated actual height of the stack (e.g., H _M i, H _M 2) may be compared to the standardized height (e.g., !½, !½ in FIGS. 1-3) of the stack to determine if the stack contains the maximum number of inventory items associated with the stack.

[0059] If the actual height is substantially equal to (within an tolerance range associated with the accuracy of the range finding sensor, for example) the standardized height (e.g., !½, !½) associated with the UAS's position (such as H _M i illustrated in FIG. 2), the number of items in the stack may be determined to be the maximum number of safely stacked items (e.g., N _max i _; N _maX 2 discussed above). The maximum number of safely stacked inventory items (e.g., Nmaxi, _m ax2) may also be determined by reading a marker located at the detected position of the UAS 105, or consulting a database of stored inventory item sizes.

[0060] Conversely, if the actual height is not substantially equal to (by an amount greater than a tolerance range associated with the accuracy of the range finding sensor, for example) the standardized height (e.g., !½, !½) associated with the UAS's position (such as H _M 2 illustrated in FIG. 3), the number of items in the stack may be calculated based on the standard size standard size (e.g., S ₂₅ , S ₃₀ in FIGS. 1-3) associated with inventory items in the stack. For example, equation 5 (e.g., discussed above may be used to calculate the number of inventory items in the stack.

[0061] Once the number of items in the stack is calculated, the inventory may be updated to reflect the calculated number of items in the stack at 825 and the process may end. In some example implementations, the process 800 may be repeated for every stack in a warehouse to determine a full inventory of warehouse.

[0062] EXAMPLE COMPUTING ENVIRONMENT

[0063] FIG. 9 illustrates an example computing environment 900 with an example computer device 905 suitable for controlling an IMS in accordance with some example implementations. Computing device 905 in computing environment 900 can include one or more processing units, cores, or processors 910, memory 915 (e.g., RAM, ROM, and/or the like), internal storage 920 (e.g., magnetic, optical, solid state storage, and/or organic), and/or I/O interface 925, any of which can be coupled on a communication mechanism or bus 930 for communicating information or embedded in the computing device 905.

[0064] Computing device 905 can be communicatively coupled to input/user interface 935 and output device/interface 940. Either one or both of input/user interface 935 and output device/interface 940 can be a wired or wireless interface and can be detachable. Input/user interface 935 may include any device, component, sensor, or interface, physical or virtual, which can be used to provide input (e.g., buttons, touchscreen interface, keyboard, a pointing/cursor control, microphone, camera, braille, motion sensor, optical reader, and/or the like). Output device/interface 940 may include a display, television, monitor, printer, speaker, braille, or the like. In some example

implementations, input/user interface 935 and output device/interface 940 can be embedded with, or physically coupled to, the computing device 905. In other example implementations, other computing devices may function as, or provide the functions of, an input/user interface 935 and output device/interface 940 for a computing device 905.

[0065] Examples of computing device 905 may include, but are not limited to, highly mobile devices (e.g., smartphones, devices in vehicles and other machines, devices carried by humans and animals, and the like), mobile devices (e.g., tablets, notebooks, laptops, personal computers, portable televisions, radios, and the like), and devices not designed for mobility (e.g., desktop computers, server devices, other computers, information kiosks, televisions with one or more processors embedded therein and/or coupled thereto, radios, and the like).

[0066] Computing device 905 can be communicatively coupled (e.g., via I/O interface 925) to external storage 945 and network 950 for communicating with any number of networked components, devices, and systems, including one or more computing devices of the same or different configuration. Computing device 905 or any connected computing device can be functioning as, providing services of, or referred to as a server, client, thin server, general machine, special-purpose machine, or another label.

[0067] I/O interface 925 can include, but is not limited to, wired and/or wireless interfaces using any communication or I/O protocols or standards (e.g., Ethernet, 802.1 lx, Universal System Bus, WiMAX, modem, a cellular network protocol, and the like) for communicating information to and/or from at least all the connected components, devices, and network in computing environment 900. Network 950 can be any network or combination of networks (e.g., the Internet, local area network, wide area network, a telephonic network, a cellular network, satellite network, and the like).

[0068] Computing device 905 can use and/or communicate using computer-usable or computer-readable media, including transitory media and non-transitory media.

Transitory media includes transmission media (e.g., metal cables, fiber optics), signals, carrier waves, and the like. Non-transitory media included magnetic media (e.g., disks and tapes), optical media (e.g., CD ROM, digital video disks, Blu-ray disks), solid state media (e.g., RAM, ROM, flash memory, solid-state storage), and other non-volatile storage or memory.

[0069] Computing device 905 can be used to implement techniques, methods, applications, processes, or computer-executable instructions in some example computing environments. Computer-executable instructions can be retrieved from transitory media, and stored on and retrieved from non-transitory media. The executable instructions can originate from one or more of any programming, scripting, and machine languages (e.g., C, C++, C#, Java, Visual Basic, Python, Perl, JavaScript, and others).

[0070] Processor(s) 910 can execute under any operating system (OS) (not shown), in a native or virtual environment. One or more applications can be deployed that include logic unit 955, application programming interface (API) unit 960, input unit 965, output unit 970, UAS position determination unit 975, Stack height calculation unit 980,

Inventory update unit 985, and inter-unit communication mechanism 995 for the different units to communicate with each other, with the OS, and with other applications (not shown). For example, UAS position determination unit 975, Stack height calculation unit 980, and Inventory update unit 985 may implement the process shown in FIG. 8. The described units and elements can be varied in design, function, configuration, or implementation and are not limited to the descriptions provided. [0071] In some example implementations, when information or an execution instruction is received by API unit 960, it may be communicated to one or more other units (e.g., logic unit 955, input unit 965, UAS position determination unit 975, Stack height calculation unit 980, and Inventory update unit 985). For example, the UAS position determination unit 975 may determine the UAS position (both lateral and vertical positions relative to ground and one or more stacks) and provide UAS position information to the Stack height calculation unit 980. Additionally, the Stack height calculation unit 980 may calculate a number of items in the stack based on the UAS position information and provide the number of items to the Inventory update unit 985. The Inventory update unit 985 may then update a warehouse inventory based on the number of items in the stack.

[0072] In some instances, the logic unit 955 may be configured to control the information flow among the units and direct the services provided by API unit 960, input unit 965, output unit 970, UAS position determination unit 975, Stack height calculation unit 980, and Inventory update unit 985 in some example implementations described above. For example, the flow of one or more processes or implementations may be controlled by logic unit 955 alone or in conjunction with API unit 960.

[0073] Although a few example implementations have been shown and described, these example implementations are provided to convey the subject matter described herein to people who are familiar with this field. It should be understood that the subject matter described herein may be implemented in various forms without being limited to the described example implementations. The subject matter described herein can be practiced without those specifically defined or described matters or with other or different elements or matters not described. It will be appreciated by those familiar with this field that changes may be made in these example implementations without departing from the subject matter described herein as defined in the appended claims and their equivalents.