U.S. patent application number 17/355216 was filed with the patent office on 2021-11-11 for automated delivery device and method for delivering a package.
The applicant listed for this patent is Intel Corporation. Invention is credited to Johannes BERG, Adoni Mohammed GHOUSE, Ariel MALAMUD, Tamir Damian MUNAFO, Alex NAYSHTUT.
Application Number | 20210350320 17/355216 |
Document ID | / |
Family ID | 1000005726591 |
Filed Date | 2021-11-11 |
United States Patent
Application |
20210350320 |
Kind Code |
A1 |
MUNAFO; Tamir Damian ; et
al. |
November 11, 2021 |
AUTOMATED DELIVERY DEVICE AND METHOD FOR DELIVERING A PACKAGE
Abstract
A ground transporter transports a package to a package recipient
location and receives a token from a token recipient, wherein
receiving the token represents a verification that the ground
transporter has moved to the package recipient location. The ground
transporter is configured, if the token is received, to deliver the
package at the package recipient location.
Inventors: |
MUNAFO; Tamir Damian;
(Naale, IL) ; GHOUSE; Adoni Mohammed; (Folsom,
CA) ; MALAMUD; Ariel; (Jerusalem, IL) ; BERG;
Johannes; (Detmold, DE) ; NAYSHTUT; Alex; (Gan
Yavne, IL) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Intel Corporation |
Santa Clara |
CA |
US |
|
|
Family ID: |
1000005726591 |
Appl. No.: |
17/355216 |
Filed: |
June 23, 2021 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16143534 |
Sep 27, 2018 |
11074542 |
|
|
17355216 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
B64C 2201/145 20130101;
G08G 5/0026 20130101; B64F 1/32 20130101; G06Q 10/0833 20130101;
B64C 2201/127 20130101; G08G 5/0069 20130101; B64F 1/00 20130101;
B64C 39/024 20130101; B64C 2201/128 20130101; G05D 1/0022 20130101;
G08G 5/0013 20130101 |
International
Class: |
G06Q 10/08 20060101
G06Q010/08; B64C 39/02 20060101 B64C039/02; G08G 5/00 20060101
G08G005/00; B64F 1/00 20060101 B64F001/00; B64F 1/32 20060101
B64F001/32 |
Claims
1. A ground transporter, configured to: transport a package to a
package recipient location; receive a token from a token recipient,
wherein receiving the token represents a verification that the
ground transporter has moved to the package recipient location; and
wherein the ground transporter is configured, if the token is
received, to deliver the package at the package recipient
location.
2. The ground transporter of claim 1, wherein the ground
transporter is configured to authenticate the recipient using the
token.
3. The ground transporter of claim 2, wherein authenticating the
device using the token comprises the ground transporter comparing
the token to a predetermined token.
4. The ground transporter of claim 1, wherein the ground
transporter is an autonomous vehicle.
5. The ground transporter of claim 1, wherein the token is a
passphrase.
6. The ground transporter of claim 1, wherein the token is a
previously negotiated token, and wherein ground transporter is
further configured to verify that the ground transporter has moved
to the correct package recipient location based on a verification
that the recipient has possession of the token.
7. The ground transporter of claim 1, wherein the ground
transporter is configured to receive the token from a recipient
device using a Secure Wireless Protocol.
8. The ground transporter of claim 7, wherein the Secure Wireless
Protocol is a Secure Authentication of Equals Protocol according to
the Wi-Fi Alliance.
9. The ground transporter of claim 1, wherein delivering the
package at the package recipient location comprises leaving the
package at the package receipt location.
10. The ground transporter of claim 1, wherein the ground
transporter comprises a camera system, configured to obtain an
image of the delivered package.
11. The ground transporter of claim 10, wherein the ground
transporter is further configured to control the transmitter to
wirelessly send the image of the delivered package.
12. A non-transitory computer readable medium, comprising
instructions, which, if executed cause one or more processors to:
control a ground transporter to transport a package to a package
recipient location; receive a token from a recipient, wherein
receipt of the token represents a verification that the ground
transporter has moved to the package recipient location; and if the
ground transporter receives the token, control the ground
transporter to deliver the package at the package recipient
location.
13. The non-transitory computer readable medium of claim 12,
wherein the instructions are further configured to cause the one or
more processors to authenticate the recipient using the token.
14. The non-transitory computer readable medium of claim 13,
wherein authenticating the recipient using the token comprises
comparing the token to a predetermined token.
15. The non-transitory computer readable medium of claim 12,
wherein the ground transporter is an autonomous vehicle.
16. The non-transitory computer readable medium of claim 12,
wherein the token is a passphrase.
17. The non-transitory computer readable medium of claim 12,
wherein the token is a previously negotiated token, and wherein the
instructions are further configured to cause the one or more
processors to verify that the ground transporter has moved to the
correct package recipient location based on a verification that the
recipient has possession of the previously negotiated token.
18. The non-transitory computer readable medium of claim 12,
wherein the instructions are further configured to cause the one or
more processors to control a transceiver to receive the token from
a recipient device using a Secure Wireless Protocol.
19. The non-transitory computer readable medium of claim 18,
wherein the Secure Wireless Protocol is a Secure Authentication of
Equals Protocol according to the Wi-Fi Alliance.
20. The non-transitory computer readable medium of claim 12,
wherein delivering the package at the package recipient location
comprises leaving the package at the package receipt location.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. application Ser.
No. 16/143,534, filed on Sep. 27, 2018, the entirety of which is
incorporated herein by reference.
TECHNICAL FIELD
[0002] Exemplary implementations described herein generally relate
to automated delivery devices and methods for delivering a
package.
BACKGROUND
[0003] Today, package delivery goes largely untrusted. Manual
delivery methods take on at least two forms: a recipient needs to
be present at the time of delivery to sign and receive the package
or a package can be delivered unattended to a specified location
such as at the doorstep or to a designated neighbor, all based on
recipient's instructions.
[0004] The highest level of trust attained in these scenarios are
basically a physical signature collected by the shipper, which goes
generally unchecked. At most, the signature is scanned and stored
in the shipper's database.
[0005] Others methods include designated private `delivery boxes`
provided to the recipient by a shipper accessible by key, or a
delivery box at the local post office accessible by a
smartcard.
[0006] With the huge success of online ordering of products,
shippers consider the usage of automated delivery of packages, for
example by drones (e.g. Unmanned Aerial Vehicles (UAVs)). An issue
that arises in this context is that shippers need to prove that a
package has been successfully delivered to a customer. While human
delivery personnel (e.g. a mailman) can testify that he has
delivered a package, an automated delivery device such as a drone
cannot do this. Accordingly, approaches are desirable which allow
verification of delivery.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] In the drawings, like reference characters generally refer
to the same parts throughout the different views. The drawings are
not necessarily to scale, emphasis instead generally being placed
upon illustrating the principles of the invention. In the following
description, various aspects are described with reference to the
following drawings, in which:
[0008] FIG. 1 shows a package ordering and delivery
arrangement.
[0009] FIG. 2 shows an arrangement at a recipient's house according
to various examples.
[0010] FIG. 3 illustrates a flow for establishing a digital trust
relationship between seller, shipper and recipient according to an
example.
[0011] FIG. 4 illustrates a flow for establishing a digital trust
relationship between seller, shipper and recipient according to
another example.
[0012] FIG. 5 illustrates a flow for establishing a digital trust
relationship between seller, shipper and recipient according to
another example.
[0013] FIG. 6 shows an arrangement for trusted delivery of
packages.
[0014] FIG. 7 illustrates an example of the approach of
establishing a digital trust relationship of FIG. 5.
[0015] FIG. 8 shows an automated delivery device.
[0016] FIG. 9 shows a flow diagram illustrating a method for
delivering a package, for example performed by an automated
delivery device.
[0017] FIG. 10 shows an automated delivery device 1000 according to
various examples.
[0018] FIG. 11 shows a flow diagram 1100 illustrating a method for
delivering a package, for example performed by an automated
delivery device.
DESCRIPTION OF EXEMPLARY IMPLEMENTATIONS
[0019] The following detailed description refers to the
accompanying drawings that show, by way of illustration, specific
details and aspects of this disclosure in which the invention may
be practiced. Other aspects may be utilized and structural,
logical, and electrical changes may be made without departing from
the scope of the invention. The various aspects of this disclosure
are not necessarily mutually exclusive, as some aspects of this
disclosure can be combined with one or more other aspects of this
disclosure to form new aspects.
[0020] Exemplary embodiments of the present disclosure can be
realized by one or more computers (or computing devices) reading
out and executing computer-executable instructions recorded on a
storage medium (e.g., non-transitory computer-readable storage
medium) to perform the functions of one or more of the
herein-described embodiment(s) of the disclosure. The computer(s)
may include one or more of a central processing unit (CPU), a
microprocessing unit (MPU), or other circuitry, and may include a
network of separate computers or separate computer processors. The
computer-executable instructions may be provided to the computer,
for example, from a network or the storage medium. The storage
medium may include, for example, one or more of a hard disk, a
random-access memory (RAM), a read-only memory (ROM), a storage of
distributed computing systems, an optical disk (such as a compact
disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD), a
flash memory device, a memory card, and the like. By way of
illustration, specific details and embodiments in which the
invention may be practiced are described in the following.
[0021] FIG. 1 shows a package ordering and delivery arrangement
100.
[0022] A user (customer) 101 living in this house 102 uses his
computer 103 to connect to the server 104 of a seller 105.
Typically, the server 104 hosts a website accessible via the
Internet 110 to which the user 101 may connect using his computer
103 and where he may select a product and place an order for the
product. The product is packed into a package 106 which is given to
a shipper 107 which is tasked to deliver the package 106 to the
user 101. The shipper 107 uses automated delivery by means of an
automated delivery device 108, e.g. a drone, to deliver the package
106 to the user's doorstep 109.
[0023] The shipper 107, on behalf of the seller 105, can deliver
the package 106 to the correct address of the user's house 102 even
in an unattended scenario when using an autonomous system (i.e. the
automated delivery device 108) delivering the package 106 to the
customer's front door (doorstep 109) when the user (customer) 101
is not present to receive it.
[0024] However, this unattended delivery method is typically not
trusted by either side. Neither the sender (shipper 107) nor the
recipient (user 101) can positively identify each other. This can
cause liability issues when, for example, the package 106 is
delivered to the wrong location and/or the wrong recipient, or it
is stolen or arrives damaged. In such cases whenever the delivery
is unattended, it would be difficult to determine who is at
fault--the shipper 107 or the customer 101. This can also cause
shipper's reputation to be negatively affected.
[0025] According to various examples, a method and apparatus for
trusted and reliable delivery are provided. A dispatching device
(i.e. an automated delivery device 108) may be configured upon
arrival to a drop-off point (e.g. doorstep 109), to collect
evidence of delivery such as GPS location or photo (image), and to
timestamp at the time and place of delivery and submit it to a
delivery tracking system. A secure engine based on hardware (such
as SGX (Software Guard Extensions), Trustzone, and a co-processor)
may be used that collects the data directly from the sensor and
signs it thus creating trust between the parties.
[0026] This digital trust approach allows securely authenticating
two parties (delivery device and recipient) and may be used to
establish a trusted relationship between seller 105, shipper 107
and recipient 101. The receiving side (user 101) is, in case of an
issue, able to open a dispute and use the same approach for
providing evidence of non-delivery, a broken package, etc. The
digital trust approach can be used by both sides to ascertain and
validate each side to ensure the intended and accurate origin and
destination of the package. This allows fully automating the
delivery process by utilizing an unmanned autonomous (or
semi-autonomous) delivery system such as a drone, a robot, an
automated smart car or combinations.
[0027] FIG. 2 shows an arrangement 200 at the recipient's house
according to various examples.
[0028] An automated delivery device (dispatching device) 201, e.g.
corresponding to automated delivery device 108 of FIG. 1, delivers
a package 202 to a drop-off point, e.g. a doorstep 203 of a
customer's house 204 corresponding to the doorstep 109 of FIG.
1.
[0029] The dispatching device 201 may be configured to travel to a
location associated with a customer, e.g. a customer's house or
residence 204. The dispatching device 201, upon arrival at the drop
point 203, is further configured to collect evidence of the
delivery of the package 202 such as GPS location and a timestamp at
the time of delivery. The dispatching device 201 may collect the
evidence electronically using hardware, software or both, e.g.
using a GPS receiver and a clock. The dispatching device 201 may
further be equipped with a camera 205 and be configured to take one
or more photos (e.g., digital image(s)) of the delivered package
202. The dispatching device 201 is configured to deliver the
evidence or data thereof, (possibly including the photo(s)/digital
image(s)) through any suitable means (e.g., wireless
communications) to a server 206 of the provider of the digital
trust service.
[0030] The trust is gained by a secure engine 214 of the
dispatching device which may be based on hardware (such as SGX,
Trustzone, secure co-processor) that is configured to collect the
evidence data directly from the corresponding sensors (GPS receiver
209, camera 205, timer 209) and signs it, e.g. using EPID (Enhanced
Privacy ID).
[0031] The receiving side, i.e. the customer 101 can, in case of an
issue, open a dispute and use a similar method for providing
evidence of non-delivery or a broken package, etc. For this, the
house 204 may be provided with a camera 207 configured to take a
picture of the delivered package.
[0032] According to various examples, the camera 207 is used by the
dispatching device 201 to strengthen the evidence that it gathers
and provides to the server 206: A controller 210 of the dispatching
device 201 may send a command via a transmitter 211 of the
dispatching device 201 and a receiver 212 of the camera 207 which
instructs the camera 207 to take a photo of the delivered package
202. The controller 210 may further instruct the camera 207 to
upload this photo to the server 206 or to provide it to the
dispatching device 201. In the latter case, the dispatching device
201 may itself upload the photo to the server 206. The controller
210 may for example include one or more microprocessors,
microcontrollers or an FPGA (Field Programmable Gate Array) and may
be configured to execute program instructions and operatively
communicate with other components.
[0033] At the customer's location, there may also be provided a
wireless ranging device 213 (e.g. a beacon device) that transmits a
wireless beacon signal that allows the delivery device 201 to more
accurately find the drop-off location 203. That is, the delivery
device 201 may be configured to receive a signal from the beacon
device in order to find the correct drop-off location.
[0034] Approaches according to various examples such as described
with reference to FIG. 2 allow establishing a digital trust
relationship between 105 seller, shipper 107 and recipient 101.
[0035] FIG. 3 illustrates a flow for establishing a digital trust
relationship between seller, shipper and recipient according to an
example.
[0036] In 301, the recipient 101 orders a product from the seller
105.
[0037] In 302, the seller 105 dispatches the product via the
shipper 107.
[0038] In 303, the shipper 107 sends package with the product via
the automated delivery device 108, e.g. a UAV (unmanned aerial
vehicle).
[0039] In 304, the delivery device 108 approaches the recipient's
location (e.g. the customer's house 102) via GPS.
[0040] In 305, the delivery device 108 performs the package
drop-off and authentication process. In this example, it is assumed
that there is no active device (such as camera 112) at the
recipient's house 102. The process of 305 includes 306 to 309 as
follows:
[0041] In 306, the delivery device 108 identifies precise drop-off
location (more precise than GPS, e.g. the customer's doorstep 109)
using, for example, optical recognition (e.g. based on a QR) or a
camera-based identification of physical premises (building, patio,
yard, etc.) based on one or more recipient-provided reference
images. The delivery device may also identify the precise drop-off
location (more precise than GPS, e.g. the doorstep 203) using the
wireless ranging device 213.
[0042] In 307, the delivery device 108 drops off the package (e.g.
a parcel) 106.
[0043] In 308, the delivery device 108 takes a picture of the
package 106 by means of its camera 205. The image or picture, in
addition to capturing the package, may capture other identifiable
aspects associated with the address or residence of the
recipient.
[0044] In 309, the delivery device 108 digitally signs the picture
and timestamp information of the delivery time (e.g. using EPID as
a key to encrypt) and uploads it through any suitable communication
means to server 206 (e.g. in a cloud).
[0045] FIG. 4 illustrates a flow for establishing a digital trust
relationship between seller, shipper and recipient according to
another example.
[0046] In this example, it is assumed that both the delivery device
201 and the drop-off location 204 have their own camera 205, 212,
i.e. there is also an on-premise camera.
[0047] The following may be carried out in addition to 301 to 309
of FIG. 3.
[0048] In 401, at the time of the order, the recipient 101
specifies a way for the delivery device 108 to communicate with the
camera 212 at the recipient's location. For example, such a
mechanism could use a Bluetooth device address to identify the
camera 212. Alternatively, Infrared communication may be used.
[0049] In 402, when the delivery device 108 has dropped-off the
package 106, it signals the recipient's camera 212.
[0050] In 403, the recipient's camera 212, in response, also takes
a picture of the delivered package, digitally signs the picture and
timestamp information specifying the time of the picture and
uploads it to the server 206.
[0051] FIG. 5 illustrates a flow for establishing a digital trust
relationship between seller, shipper and recipient according to
another example.
[0052] In this example, a full mutual authentication is carried
out.
[0053] In 501, the recipient 101 orders a product from the seller
105.
[0054] In 502, the seller 105 dispatches the product via the
shipper 107.
[0055] In 503, the shipper 107 sends package via the automated
delivery device 108, 201, e.g. a UAV.
[0056] In 504, the delivery device 201 identifies the precise
drop-off location (more precise than GPS, e.g. the doorstep 203)
using the wireless ranging device 213. The customer may provide
information identifying the wireless ranging device 213 at the time
of order in 501. That is, the customer may electronically transmit
the information identifying the wireless ranging device 213 which
is electronically communicated to the delivery device 201.
[0057] For example, the delivery device 201 may use Wi-Fi based FTM
(Fine Timing Measurement) according to IEEE, with the delivery
device 201 being the initiator, and one or more responders located
at the recipient's site (corresponding to one or more wireless
ranging devices 213). In this case, the information identifying the
wireless ranging device 213 would e.g. be the BSSID (Basic Service
Set Identifier) and/or the SSID (Service Set Identifier).
[0058] In 505, the delivery device 201 and the wireless ranging
device 213 mutually authenticate each other using a trust
relationship established at the time of sale or shipment, for
example. For example, at the time of sale 501, a token (such as a
random passphrase) is assigned for this transaction and distributed
to both the delivery device 201 and the wireless ranging device
213, e.g. by the server 206. For example, the delivery device 201
and the wireless ranging device 213 can mutually verify this token
using the SAE (Secure Authentication of Equals) Wi-Fi protocol.
Both can verify each other's possession of the Token, and can also
use it to exchange temporal keys for further secure communications
if necessary. An authentication handshake can use the same Wireless
Radio used for the Wireless Ranging of 504. For example, in the
case of Wi-Fi based FTM, the delivery device 201 could use the same
FTM responder's Wi-Fi radio for communication.
[0059] It should be noted that a continuous output of the wireless
ranging device 213 can be used to geo-fence the authentication to
prevent a situation where the delivery device 201 is in wireless
range of the wireless ranging device 213 but in the wrong location
or too far away from the recipient due to errors or attacks in 504.
For example, an attacker could fake an unauthenticated high-power
ranging signal and turn it off with the beginning of authentication
in 505, resulting in authentication succeeding with the correct
wireless ranging device 213 within wireless range but in a
different unintended drop-off location.
[0060] In 506, the delivery device 201 drops off the package 202 at
the precise intended and authenticated location.
[0061] In 507, optionally, one or both sides take one or more
pictures of the delivered package 202, embed the ranging
information and authentication results into the picture's metadata,
and send it to the server 206 (e.g. acting as a Trusted Electronic
Notary) as proof of delivery and damage identification. On the
customer's side, this may be performed by a system including the
camera 212 and/or the wireless ranging device 213.
[0062] The delivery device 201 and the customer's system may would
follow the processing of SGX (Trusted Execution Environment) as
illustrated in FIG. 6 to sign the picture, timestamp and location
information to securely communicate with the server 206.
[0063] FIG. 6 shows an arrangement 600 for trusted delivery of
packages.
[0064] The arrangement 600 includes a recipient device 601, for
example corresponding to the customer's system including camera 212
and wireless ranging device 213, a dispatching device 602, for
example corresponding to the delivery device 201, a service
provider's server 603, for example corresponding to the server 206
and a verification authority 604.
[0065] The recipient device 601 has a camera 605 and a positioning
device 606 providing its location. Further, the recipient device
601 has a TEE (Trusted Execution Environment) attestation engine
607 and a delivery verifier 608.
[0066] The camera 605 provides an image of a delivered package to
the TEE attestation engine 607 and the positioning device 606 gives
an indication of the position of the recipient device 601 at the
time of taking the image to the TEE attestation engine 607.
[0067] The TEE attestation engine 607 checks and validates the
delivery verifier 608, e.g. software running on the recipient
device 601 implementing the delivery verifier 608, and the delivery
verifier 608 transmits the image and the indication of the position
of the recipient device 601 to the service provider 603. The TEE
attestation engine 607 may be implemented by a secure root of the
TEE attestation engine 607 which may be verified by the
verification authority 604.
[0068] Similarly, the dispatching device 602 has a camera 609, a
positioning device 610 providing its location, a TEE (Trusted
Execution Environment) attestation engine 611 and a delivery
confirmation agent 612. Furthermore, the dispatching device 602 has
in this example a timer 113.
[0069] The camera 609 provides an image of a delivered package to
the TEE attestation engine 611 and the positioning device 610 gives
an indication of the position of the recipient device 602 at the
time of taking the image to the TEE attestation engine 611. The
timer provides an indication of this time to the TEE attestation
engine 611.
[0070] The TEE attestation engine 611 checks and validates the
delivery confirmation agent 612, e.g. software running on the
recipient device 602 implementing the delivery confirmation agent
612, and the delivery confirmation agent 612 transmits the image
and the indications of the position of the recipient device 601 and
the time to the service provider 603.
[0071] FIG. 7 illustrates an example of the approach of
establishing a digital trust relationship of FIG. 5.
[0072] The example involves a user 701 having a computer 702, a
recipient device 703 and a home 704, a service provider 705, a
shipper 706 and a delivery device 707. In this example, the service
provider 705 providing the service of establishing trust of
delivery is also the seller.
[0073] In 708, the user 701 orders a package from the service
provider 705 (seller).
[0074] In 709, the service provider 705 confirms the order and
generates a token (e.g. a random passphrase).
[0075] In 710 the user's computer 702 and the service provider 705
share details about the token as well as about the recipient device
703 (e.g. its support of WiFi based FTM and corresponding
details).
[0076] In 711, the user 701 approves or sets the recipient and
package delivery details and configures the recipient device 703
accordingly.
[0077] In 712, the recipient device 703 constantly monitors changes
in the shipment or updates package delivery information for any
changes or re-scheduling.
[0078] In 713, the service provider provides package details (such
as delivery address) to the delivery device 707 by means of the
shipper 706.
[0079] In 714, the delivery device 707 identifies the precise
drop-off location (with higher precision than provided by GPS)
using a wireless ranging system (such as WiFi based FTM).
[0080] In 715, the delivery device 707 and the recipient device 703
mutually authenticate themselves using the token assigned with the
order.
[0081] In 716, the shipper leaves the package at the drop-off
location.
[0082] In 717, the delivery device 707 and the recipient device 703
take a photo of the delivered package and send it to a cloud-based
E-notary (e.g. provided by the service provider 705) which
timestamps and digitally signs the pictures for proof of
delivery.
[0083] In summary, according to various examples, an automated
delivery device is provided as illustrated in FIG. 8.
[0084] FIG. 8 shows an automated delivery device 800.
[0085] The automated delivery device 800 includes a transportation
system 801 configured to move a package to a package recipient
location and a package drop-off mechanism 802 configured to drop
off the package at the package recipient location.
[0086] Further, the automated delivery device 800 includes a
communication system 803 configured to communicate with a recipient
camera device at the package recipient location and a controller
804 configured to instruct the recipient camera device via the
transceiver to verify package delivery based on an image of the
delivered package.
[0087] According to various examples, in other words, an automated
(and typically unmanned) delivery device, such as a drone or
generally a robot, instructs a camera at a drop-off point to take a
photo of the delivered package (i.e. package) to verify delivery of
the package. The camera at the drop-off point may electronically
provide the photo to the automated delivery device or may itself
electronically provide the photo to a delivery verification entity
such as a server of a service provider providing a delivery
verification service.
[0088] The transportation system may include one or more rotors,
wheels, tracks etc.
[0089] The components of the automated delivery device (e.g. the
communication system, and the controller) may for example be
implemented by one or more processors. A "processor" may be
understood as any kind of a logic implementing entity, which may be
special purpose circuitry or a processor executing software stored
in a memory, firmware, or any combination thereof. Thus a
"processor" may be a hard-wired logic processor or a programmable
logic processor such as a programmable processor, e.g. a
microprocessor. A "processor" may also be a processor executing
software, e.g. any kind of computer program. Any other kind of
implementation of the respective functions which will be described
in more detail below may also be understood as a "processor". The
communication system may for example be at least partially be
implemented by a transceiver which may for example be at least
partially implemented by a modem, a baseband processor or other
transceiver components or also by an application processor.
[0090] FIG. 9 shows a flow diagram 900 illustrating a method for
delivering a package, for example performed by an automated
delivery device.
[0091] In 901, the automated delivery device moves a package to a
package recipient location.
[0092] In 902, the automated delivery device drops off the package
at the package recipient location.
[0093] In 903, the automated delivery device communicates with a
recipient camera device at the package recipient location.
[0094] In 904, the automated delivery device instructs the
recipient camera device to verify package delivery based on an
image of the delivered package.
[0095] FIG. 10 shows an automated delivery device 1000 according to
various examples.
[0096] The automated delivery device 1000 includes a transportation
system 1001 configured to move a package to a package recipient
location and a communication system 1002 configured to communicate
with a recipient ranging device at the package recipient
location.
[0097] The automated delivery device 1000 further includes a
controller 1003 configured to verify that the automated delivery
device has moved to the correct package recipient location based on
data received by the communication system from the recipient
ranging device.
[0098] Further, the automated delivery device 1000 includes a
package drop-off mechanism 1004 configured to drop off the package
at the package recipient location if the automated delivery device
has moved to the correct package recipient location.
[0099] FIG. 11 shows a flow diagram 1100 illustrating a method for
delivering a package, for example performed by an automated
delivery device.
[0100] In 1101, the automated delivery device moves a package to a
package recipient location.
[0101] In 1102, the automated delivery device communicates with a
recipient ranging device at the package recipient location.
[0102] In 1103, the automated delivery device verifies that the
automated delivery device has moved to the correct package
recipient location based on data received by the communication
system from the recipient ranging device.
[0103] In 1004, the automated delivery device drops off the package
at the package recipient location if the automated delivery device
has moved to the correct package recipient location.
[0104] The following examples pertain to further exemplary
implementations.
[0105] Example 1 is an automated delivery device as illustrated in
FIG. 8.
[0106] In Example 2, the subject-matter of Example 1 may optionally
include a further camera system configured to obtain a further
image of the delivered package.
[0107] In Example 3, the subject-matter of Example 2 may optionally
include the controller being configured to upload the further image
to a delivery verification server.
[0108] In Example 4, the subject-matter of any one of Examples 2-3
may optionally include the controller being configured to upload
the further image to a delivery verification server with a
timestamp of the drop off of the package.
[0109] In Example 5, the subject-matter of any one of Examples 1-4
may optionally include the communication system being radio
system.
[0110] In Example 6, the subject-matter of any one of Examples 1-5
may optionally include the communication system being configured to
communicate with a recipient ranging device and the controller
being configured to verify that the automated delivery device has
moved to the correct package recipient location based on data
received by the communication system from the recipient ranging
device.
[0111] In Example 7, the subject-matter of Example 6 may optionally
include the recipient ranging device being a beacon device.
[0112] In Example 8, the subject-matter of any one of Examples 1-7
may optionally include the communication system being configured to
communicate with a recipient authentication device and the
controller being configured to verify that the automated delivery
device has moved to the correct package recipient location based on
data received by the communication system from the recipient
authentication device.
[0113] In Example 9, the subject-matter of Example 8 may optionally
include the controller being configured to verify that the
automated delivery device has moved to the correct package
recipient location based on a verification that the recipient
authentication device has possession about a previously negotiated
token.
[0114] In Example 10, the subject-matter of any one of Examples 1-9
may optionally include the controller being configured to instruct
the recipient camera device to obtain the image of the delivered
package and upload it to a delivery verification server.
[0115] In Example 11, the subject-matter of any one of Examples
1-10 may optionally include the controller being configured to
instruct the recipient camera device to obtain the image of the
delivered package and transmit it to the automated delivery
device.
[0116] In Example 12, the subject-matter of any one of Examples
1-11 may optionally include the delivery device being an unmanned
aerial vehicle.
[0117] In Example 13, the subject-matter of any one of Examples
1-12 may optionally include the controller being implemented by a
secure embedded controller.
[0118] Example 14 is a method for delivering a package as
illustrated in FIG. 9.
[0119] In Example 15, the subject-matter of Example 14 may
optionally include the package being moved to the package recipient
location by means of an automated delivery device and obtaining a
further image of the delivered package by means of a camera of the
automated delivery device.
[0120] In Example 16, the subject-matter of Example 15 may
optionally include uploading the further image to a delivery
verification server.
[0121] In Example 17, the subject-matter of any one of Examples
15-16 may optionally include uploading the further image to a
delivery verification server with a timestamp of the drop off of
the package.
[0122] In Example 18, the subject-matter of any one of Examples
14-17 may optionally include communicating with the recipient
camera device by means of a radio system.
[0123] In Example 19, the subject-matter of any one of Examples
14-18 may optionally include communicating with a recipient ranging
device and verifying that the package has been moved to the correct
package recipient location based on data received by the
communication system from the recipient ranging device.
[0124] In Example 20, the subject-matter of Example 19 may
optionally include the recipient ranging device being a beacon
device.
[0125] In Example 21, the subject-matter of any one of Examples
14-20 may optionally include communicating with a recipient
authentication device and verifying that the package has been moved
to the correct package recipient location based on data received by
the communication system from the recipient authentication
device.
[0126] In Example 22, the subject-matter of Example 21 may
optionally include verifying that the package has been moved to the
correct package recipient location based on a verification that the
recipient authentication device has possession about a previously
negotiated token.
[0127] In Example 23, the subject-matter of any one of Examples
14-22 may optionally include instructing the recipient camera
device to obtain the image of the delivered package and upload it
to a delivery verification server.
[0128] In Example 24, the subject-matter of any one of Examples
14-23 may optionally include the package being moved to the package
recipient location by means of an automated delivery device and
instructing the recipient camera device to obtain the image of the
delivered package and transmit it to the automated delivery
device.
[0129] In Example 25, the subject-matter of any one of Examples
14-24 may optionally include the package being moved to the package
recipient location by means of an unmanned aerial vehicle.
[0130] In Example 26, the subject-matter of any one of Examples
14-25 may optionally include instructing of the recipient camera
device to verify package delivery based on an image of the
delivered package being performed by a secure embedded
controller.
[0131] Example 27 is an automated delivery device as illustrated in
FIG. 10.
[0132] In Example 28, the subject-matter of Example 27 may
optionally include the communication system being radio system.
[0133] In Example 29, the subject-matter of any one of Examples
27-28 may optionally include the recipient ranging device being a
beacon device.
[0134] In Example 30, the subject-matter of any one of Examples
27-29 may optionally include the recipient ranging device
comprising a recipient authentication device and the controller
being configured to verify that the automated delivery device has
moved to the correct package recipient location based on a
verification that the recipient authentication device has
possession about a previously negotiated token.
[0135] In Example 31, the subject-matter of any one of Examples
27-30 may optionally include the delivery device being an unmanned
aerial vehicle.
[0136] In Example 32, the subject-matter of any one of Examples
27-31 may optionally include the controller being implemented by a
secure embedded controller.
[0137] Example 33 is a method for delivering a package as
illustrated in FIG. 11.
[0138] In Example 34, the subject-matter of Example 33 may
optionally include communicating with the recipient ranging device
by means of a radio system.
[0139] In Example 35, the subject-matter of any one of Examples
33-34 may optionally include the recipient ranging device being a
beacon device.
[0140] In Example 36, the subject-matter of any one of Examples
33-35 may optionally include the recipient ranging device
comprising a recipient authentication device and verifying that the
automated delivery device has moved to the correct package
recipient location based on a verification that the recipient
authentication device has possession about a previously negotiated
token.
[0141] In Example 37, the subject-matter of any one of Examples
33-36 may optionally include the package being moved to the package
recipient location by means of an unmanned aerial vehicle.
[0142] In Example 38, the subject-matter of any one of Examples
33-37 may optionally include the verifying being performed by a
secure embedded controller.
[0143] It should be noted that one or more of the features of any
of the examples above may be combined with any one of the other
examples.
[0144] While specific aspects have been described, it should be
understood by those skilled in the art that various changes in form
and detail may be made therein without departing from the spirit
and scope of the aspects of this disclosure as defined by the
appended claims. The scope is thus indicated by the appended claims
and all changes which come within the meaning and range of
equivalency of the claims are therefore intended to be
embraced.
* * * * *