CN108140163B

CN108140163B - Notification based on active device management delivery method

Info

Publication number: CN108140163B
Application number: CN201680056326.3A
Authority: CN
Inventors: R·S·拉奥; C·H·布哈格瓦特; A·齐普斯特; P·K·米什拉; D·穆克赫吉; T·M·赖尔
Original assignee: Amazon Technologies Inc
Current assignee: Amazon Technologies Inc
Priority date: 2015-09-29
Filing date: 2016-09-29
Publication date: 2022-11-29
Anticipated expiration: 2036-09-29
Also published as: EP3357014A1; AU2016330891B2; CN108140163A; WO2017059112A1; AU2016330891A1

Abstract

Techniques for managing notifications may be described. In an example, the notification can relate to an item and can be provided to a user device. An active device may be associated with the item. The active device may store a token for communicating with a local area network associated with a location. Based on the communication, it may be determined that the item is likely located near the location. A corresponding notification may be sent to the user equipment.

Description

Notification based on active device management delivery method

Background

More and more users are turning to network-based resources, such as web-based resources that may utilize the internet, to order items (e.g., goods and/or services). Network-based resources may provide a user experience that is incomparable with more traditional physical stores. For example, web-based resources may provide a greater number and diversity of item selections. Further, for some projects, there may be multiple sellers offering different discounts. In this way, the customer not only has access to a rich selection of items, but also has access to the items at the most convenient discount.

Typically, a user device and a network-based resource may interact to exchange information about an item. The interaction may include a notification provided to the user device. The notification may be related to the item, such as the delivery status of the item. The number, content, and time of notifications may affect user experience, network bandwidth, processing of network-based resources, and/or processing of user devices.

Brief Description of Drawings

Various embodiments according to the present disclosure will be described with reference to the accompanying drawings, in which:

FIG. 1 illustrates an exemplary computing environment in which notifications may be transmitted, according to particular embodiments;

FIG. 2 illustrates an exemplary computing environment that can utilize a destination delivery management device, according to particular embodiments;

FIG. 3 illustrates an exemplary notification that may be obtained from a computing environment utilizing a destination delivery management device, in accordance with certain embodiments;

FIG. 4 illustrates an exemplary computing environment that can utilize active devices, in accordance with certain embodiments;

FIG. 5 illustrates an exemplary notification that may be obtained from a computing environment utilizing an active device, in accordance with certain embodiments;

FIG. 6 illustrates an exemplary flow for providing notifications, according to particular embodiments;

FIG. 7 illustrates an exemplary flow for providing notifications in a computing environment utilizing a destination delivery management device, in accordance with certain embodiments;

FIG. 8 illustrates another exemplary flow for providing notifications in a computing environment utilizing a destination delivery management device, in accordance with certain embodiments;

FIG. 9 illustrates an exemplary flow for providing notifications in a computing environment utilizing active devices, in accordance with certain embodiments;

FIG. 10 illustrates another exemplary flow for providing notifications in a computing environment utilizing active devices, according to particular embodiments; and

fig. 11 illustrates an exemplary end-to-end architecture for facilitating an electronic marketplace, according to certain embodiments.

Detailed Description

In the following description, various embodiments will be described. For purposes of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the embodiments. It will be apparent, however, to one skilled in the art that embodiments may be practiced without the specific details. In addition, well-known features may be omitted or simplified in order not to obscure the described embodiments.

Embodiments herein relate to managing notifications within a computing environment. In an example, a computing environment may include network-based resources accessible to a user device over a network. The network-based resource may be configured to provide a notification to the user device. The notification may relate to an item. Unlike many conventional computing environments, notifications may be provided in real-time based on a trigger (e.g., within a short period of time after the trigger occurs). Exemplary triggers may include a status or a change in status of an item. Another exemplary trigger may include a request from a user device. Regardless of the trigger, the notification can be based on real-time data about the item. Because of the real-time data, notifications can provide meaningful information about the item rather than outdated or stale information. Furthermore, due to the trigger, only the necessary or desired number of notifications may be provided to the user equipment, rather than a large set of unnecessary or unwanted notifications. Thus, the user experience may be enhanced, while also reducing the use of computing resources and the use of network bandwidth within the computing environment. To trigger a real-time notification, an item may be associated with a notification device (such as a tag that enables data exchange). The association may include a direct physical attachment between the item and the notification device or an indirect attachment through an intermediate holder. In turn, the notification device may be configured to connect to a network through various computing devices. Communication with the computing device may trigger a notification in real-time.

To illustrate, consider a first example of an electronic marketplace. A user may operate a user device to order (such as rent or purchase) an item. Items may be delivered from a source to a destination by a delivery vehicle. A holder, such as a package, can hold items for delivery. A passive Radio Frequency Identification (RFID) tag may be attached to the package and may uniquely identify the order. The handheld device may read the RFID tag when the item is loaded onto the delivery vehicle. The handheld device may be connected to a computer system of the electronic marketplace over a network. Reading of the RFID tag may identify the item, causing the handheld device to indicate to the computer system that loading has occurred. In response, the computer system may send a notification to the user device to begin delivery. While the item is en route, the user device may access the computer system to request location information about the item. In response, the computer system may use Global Positioning System (GPS) data of the handheld device and/or delivery truck to estimate and provide location information to the user device. Upon reaching the destination, a computing device located at the destination may connect to the handheld device and/or read the RFID tag. The computing device may also be connected to a computer system over a network and may access information about the order. Thus, the computing device may authorize the handheld device to offload items at a destination, and may cause a notification to be sent to the user device regarding the offloading. Further, the computing device may be configured to determine movement and/or pickup of the item. In this way, when an item has been unloaded, any movement and/or pick-up of the item may trigger a corresponding notification to be sent to the user device.

In another illustration, consider a second example of the same or different electronic marketplace. In this example, active 802.11RFID tags may be utilized instead of or in addition to passive RFID tags. Upon arrival, the active 802.11RFID tag may connect to a computing node (e.g., an access point or an intermediate computing device) of the destination's local area network. The active 802.11RFID tag and the computing node may utilize a token to establish communication. The token may be based on an order for the item. Similarly, a handheld device may communicate with a computing node. Based on the communication of the handheld device and/or the active 802.11RFID tag with the computing node, the uninstallation may be determined and a corresponding notification may be sent to the user device. After offloading, the communication between the active 802.11RFID tag and the computing node may be utilized to determine movement and/or pick-up of the item and thus send a corresponding notification to the user device.

For clarity of explanation, embodiments may be described herein in connection with the electronics market. However, the embodiments may not be limited thereto. Rather, embodiments may be similarly applied to any computing environment that may generate and provide notifications. For example, embodiments may be similarly applied to inventory systems, tracking systems, and/or any other environment in which notifications may be provided from computing resources to user devices (such as from a server to a client).

Turning to FIG. 1, the figure illustrates an exemplary computing environment for providing notifications. In particular, the computing environment may include a computer system 110 and a user device 120 that exchange information about an item 130 over a network 140. In an example, the computer system 110 can facilitate functionality of an electronic marketplace that provides the project 130. The user device 120 may access the computer system 110 to order the item 130. Different order types may be supported, such as purchasing, renting, selling, and/or refunding items 130. The delivery of items from the source 112 to the destination 150 may be performed based on the order. Delivery may utilize delivery vehicle 160. Notifications 122 regarding the item 130, such as notifications related to orders and deliveries, may be provided to the user device 120. The notification 122 may be triggered by and/or may utilize real-time data. Each of these components is described herein below.

For clarity of explanation, embodiments of the present disclosure may be described in connection with delivery from source 112 to destination 150. This may correspond to, for example, purchasing the item 130 for delivery to the destination 150. However, embodiments are not so limited. Rather, embodiments may be similarly applied to delivery from destination 150 to source 112. This may correspond to, for example, returning or selling the item 130 for delivery to the source 112.

In an illustrative example, the source 112 may represent a fulfillment center (f.c.) associated with an electronic marketplace. A fulfillment center may include a warehouse, a storage facility, or some other source from which items may be obtained or to which items may be returned. In general, the electronic marketplace may provide and facilitate orders for items (or units thereof) and delivery of items (or units thereof) from and to the source 112.

The destination 150 may represent a location to which the item 130 may be delivered (or conversely from which the item 130 may be picked). For example, destination 150 may represent a house, a store, a street intersection, or other delivery location. Further, destination 150 may comprise a local area network of one or more computing nodes, which in turn may be connected to computer system 110 through network 140.

The computer system 110 may include a plurality of computing resources (such as servers or server farms) configured to facilitate the functionality of an electronic marketplace. For example, computer system 110 may host an electronic platform. The electronic platform may include a front-end system (such as a website for an electronic marketplace) to provide the project and different delivery methods. A user operating a user device may interact with the front-end system to order available items and select a delivery method. The electronic platform may also include a backend system to process and manage the delivery of the items.

User device 120 may include any suitable computing device capable of communicating with computer system 110 over network 140. For example, the user device 120 may include a plurality of general purpose personal computers, such as desktop or laptop computers running a standard operating system, as well as cellular devices, wireless devices, and handheld devices running mobile software and capable of supporting a plurality of networking protocols and messaging protocols.

Network 140 may include any one or combination of many different types of networks. For example, the network 140 may include any of a wireless network, a wired network, a cellular network, a radio network, the internet, and other private and/or public networks.

Items 130 may be obtained from an electronic marketplace and may include tangible items (e.g., physical items such as cameras or multimedia files) or intangible items (e.g., services to be provided at destination 150). As part of delivery, items 130 may be held in a holder (such as in a suitable package). Suitable packaging exemplified by item 130 can include a box, a case, a tote bag, a bag, or another container of the proper construction and materials.

Delivery vehicle 160 may represent a vehicle for delivering item 130 from source 112 to destination 150. The delivery vehicle 160 may be manually, remotely, semi-autonomously, or autonomously operated, and may include ground, air, and/or water based vehicles. Further, the delivery vehicle 160 may be connected to the computer system 110, the user device 120, and/or the destination 150 (e.g., a computing node at the destination 150) through the network 140.

Further, delivery device 162 may be associated with the delivery vehicle or an operator of the delivery vehicle. For example, delivery device 162 may be integrated with delivery vehicle 160, or may be a handheld device that may be stored at delivery vehicle 160 and used in conjunction with delivery vehicle 160. Delivery device 162 may include a computing device that may be connected to computer system 110, user device 120, and/or destination 150 (e.g., a computing node at destination 150) over network 140. Further, delivery device 162 may include different interfaces related to the delivery of item 130. One exemplary interface may include a reader for accessing information about the item 130 (e.g., a reader that can interact with a tag attached to a holder of the item). Another example interface may include an interface configured to provide (such as display to an operator and/or transmission to delivery vehicle 160) delivery instructions and receive responses to the delivery instructions from the operator and/or delivery vehicle 160.

User device 120 may receive notification 122 from computer system 110, destination 150 (e.g., a computing node at destination 150), delivery vehicle 160, and/or delivery device 162 over network 140 (or some other network). Generally, the notification 122 can provide information about the item 130 (such as an order and/or delivery for the item). In an example, the notification can include information about the location of the item, a time associated with the location of the item, a status of the item, an order, and/or a delivery. Some of the notifications 122 may be triggered by changes in the status, order, and/or delivery of the item 130. The user device 120 can request the other notifications 122 from the computer system 110, the destination 150 (e.g., a computing node at the destination 150), the delivery vehicle 160, and/or the delivery device 162. Fig. 1 shows five notifications 122, although there may be a different number of notifications 122. Each of the five notifications 122 may have been provided to the user device 120 in real-time (e.g., within a short period of time after the respective trigger occurs). The first notification may correspond to the arrival of the item 130 at location "a" (such as when the item 130 may have been loaded onto the delivery vehicle 160, which may indicate the start of delivery). The second notification may correspond to unloading the item at the destination 150. The third notification may describe that the item 130 may have moved due to the uninstall. The fourth notification may describe the environmental conditions at the destination 150 and may recommend a corresponding action related to the delivery (e.g., move the item 130 due to rain). The fifth notification may indicate that the item 130 may have been picked up.

To provide the notification 122, a tag may be attached to the item 130 and/or a holder of the item 130. The proximity of the label to the delivery device 162 and/or the destination 150 (e.g., a computing node of the destination 150) may trigger the notification. In an example, proximity may be based on wired, wireless, radio Frequency (RF), optical, and/or other types of communication between the tag, delivery device 162, and/or destination 150.

Different embodiments of the tag may be implemented. In general, embodiments may balance the cost, processing power, and/or power consumption of the tag with the cost and/or processing power of the delivery device 162 and/or the computing nodes of the destination 150. Fig. 2 shows an example of a tag as a passive device, where the cost, processing power and power consumption of the passive device can be reduced. Rather, the notification-related processing may be pushed to delivery device 162 and/or the computing nodes of destination 150. In contrast, fig. 4 shows an example of an active device as an implementation of a tag. In this example, some of the cost, processing, and/or power may be pushed to the active device.

An example of a passive device is shown in fig. 2. In particular, the passive device 210 may be attached to the holder 212 of the item (or the item itself) by adhesion or some other attachment means. The passive device 210 may represent a printable passive RFID tag (such as a unique identifier) that may encode information about the item, the delivery of the item (e.g., the delivery location and/or delivery instructions), and/or the order. Other types of passive devices may be used. For example, one-dimensional or two-dimensional barcodes may be used.

A computer system 220, similar to computer system 110 of fig. 1, may provide instructions for configuring passive devices 210 according to an order for an item. The instructions may include information to be encoded in the passive device 210. When configured (e.g., printed in the case of printable passive RFID tags), the passive device 210 may be attached to a holder 212. Further, computer system 220 may provide some or all of the encoded information to delivery device 230 and/or destination 240 (e.g., a computing node thereof). Delivery device 230 and destination 240 may be similar to delivery device 162 and destination 150, respectively, of fig. 1. The information may be pushed or transmitted over the network 250 upon request.

Destination 240 may include a local area network 242, such as a wireless local area network that interconnects various computing nodes located at destination 240 (e.g., within or within a geo-fence of destination 240). Local network 242 may also be connected to network 250 such that communication paths may exist between the computing nodes and computer system 220, delivery device 230, and/or user device 260. These computing nodes may include, for example, access points, routers, and/or other computing resources. Further, the computing node may include a delivery management device 244. Delivery management device 244 may represent a computing device that may be configured to manage a portion of the delivery of items to and/or from destination 240 (e.g., the offloading and/or picking at destination 240).

In an example, the delivery management device 244 may include a processor, memory, and other computing components implemented in hardware and software. These computing components may include, for example, a GPS receiver, a Radio Frequency (RF) transceiver, a wireless or wired data interface, a user interface, a weight sensor, a pressure sensor, an optical sensor, an environmental sensor (e.g., a rain sensor), and/or a delivery management module. The delivery management module may be configured to request and/or store information about the passive device 210, the computer system 220, the item, the delivery device 230, and/or the user device 260, and manage interactions with the passive device 210, the computer system 220, the delivery device 230, and/or the user device 260. These interactions may use various components of the delivery management device 244.

Other configurations of the delivery management device 244 may be used. For example, some components (whether hardware or software) may be pushed to other computing nodes of a local area network or to computer system 220. For example, delivery management device 244 may include an interface for interfacing with delivery device 230 (e.g., RFID tag, barcode, etc.), processor, memory, and wireless transceiver to interface with local area network 242. In this configuration, delivery management device 244 may facilitate data exchange between delivery device 230 and the computing nodes of local area network 242. As such, much of the processing may be distributed between the delivery device 230 and the compute nodes, rather than being performed locally by the delivery management device 244.

In operation, various notifications may be generated based on the proximity of different components. These notifications may relate to events associated with delivery. For example, the notification may include information about different delivery events (including the start of delivery, the unloading of the item, the movement of the item, and/or the pick up of the item) as such events occur.

At the beginning of delivery, the delivery device 230 may interact with the passive device 210 to receive information therefrom. The interaction may depend on the implementation of the passive device 210. For example, the delivery device 230 may radiate a passive RFID tag using RF energy and receive an RF signal from the passive RFID tag in response. In an example, upon interacting with the passive device 210, the delivery device 230 can send information included in the RF signal to the computer system 220, which computer system 220 can then send a notification to the user device 260 regarding the start of delivery. In another example, delivery device 230 may send a notification to user device 260 independently of computer system 220.

While en route to destination 240, computer system 220 may receive the GPS location of passive device 210 and/or delivery device 230 and may provide such information to user device 260. Upon reaching destination 240, delivery device 230 may access the GPS location of delivery management device 244, allowing delivery device 230 to move into proximity of delivery management device 244.

When in proximity, various types of notifications may be generated based on the interaction of delivery management device 244 with passive device 210, holder 212, and/or delivery device 230. The interaction may be triggered by a request from the delivery device 230 to the delivery management device 244. In another example, the interaction may be triggered by the computer system 220. For example, computer system 220 can determine that delivery device 230 can be within the geofence of destination 240. Accordingly, computer system 220 may instruct delivery management device 244 to send a ping (ping) to passive device 210 (e.g., radiate a passive RFID tag with RF energy) and/or establish a communication link with delivery device 230. Instead of using the location information, computer system 220 may estimate a time window within which delivery device 230 may reach destination 240, and may accordingly instruct delivery management device 244 to initiate the interaction. In yet another example, the delivery management device 244 may trigger interactions independent of the computer system. For example, delivery management device 244 may repeatedly generate ping instructions. Following the response to the ping instruction from passive device 210, delivery management device 244 may establish a communication link with delivery device 230.

When interaction is possible, different notifications may be generated. In an example, the notification may be generated by delivery management device 244 and/or delivery device 230. In another example, a notification can be generated by the computer system 220 in response to the interaction. When generated, the notification may be provided to the user device 260. In an example, computer system 220 can send a notification to user device 260. In another example, delivery management device 244 and/or delivery device 230 may send notifications to user device 260 independently of computer system 220.

The notification may include authorization for the uninstallation of the item (or holder 212), information about the uninstallation, the non-uninstallation, and/or information about a virtual signature associated with the uninstallation. In an example, the delivery management device 244 may access information from the passive device 210 (e.g., by reading a passive RFID tag). In another example, delivery management device 244 may receive information over a communication link with delivery device 230. The information may identify orders, items, passive devices 210, delivery devices 230, and/or delivery management devices 244. In turn, the delivery management device 244 (e.g., its delivery management module) may access the delivery information from the computer system 220 or from the user device 260 (e.g., from a previous push or based on a request). The delivery information may similarly identify the order, item, passive RFID tag, and/or delivery device 230, and may include delivery instructions (e.g., any required user signature, delivery time window, special instructions, etc.). Based on the comparison, delivery management device 244 may authorize (or deny) the delivery and thus transmit instructions to delivery device 230. In response, the delivery device 230 may display the authorization (or lack thereof) and any delivery instructions to the operator, or may provide such information to a computing device associated with the delivery vehicle.

The delivery instructions may provide information regarding the delivery of the item at destination 240. Computer system 220 and/or user device 260 may provide delivery instructions to delivery management device 244 and/or delivery device 230. There may be different types of delivery instructions. In an example, the delivery instructions may be defined at the user account level. For example, user device 260 may be associated with a user account. As part of establishing or updating the delivery management device 244 and/or the user account, delivery instructions may be defined. In this example, the delivery instruction will apply to all deliveries unless otherwise indicated. In another example, the delivery instructions may be defined at the project level. For example, the user may specify that the delivery instructions are to be automatically applied whenever an item is ordered. In yet another example, the delivery instructions may be defined at the order level. For example, each time an order is generated, specific delivery instructions may be defined for the order.

Further, delivery management device 244 and/or computer system 220 may update delivery instructions over time. In an example, the update may be based on an analysis of the delivery history. The analysis may include optimization of one or more delivery-related parameters. For example, the analysis may consider the history to determine a time range for unloading the item and/or a location at the destination 240. The time frame and/or location may reduce the risk of theft, loss, or damage to the item, increase the likelihood of a quick pick, and/or increase the likelihood of the user appearing while unloading. To illustrate, if the history indicates that a first unloading location within a first time range may result in theft of a past delivery, but a second unloading location within a second time range may result in a successful delivery, the delivery instructions may be updated to schedule the following deliveries: the delivery may avoid the first unloading location and the first time range and may utilize the second unloading location and the second time range. Similarly, if the history indicates that delivery within a particular time range has resulted in a quick pickup or that the user may have appeared at destination 240 relative to other time ranges, the delivery instructions may be updated to use the particular time range.

In another example, the update of the delivery instructions may also or alternatively be based on an analysis of the delivery history, the history of the delivery instructions, or the delivery pattern within the area that may include the delivery location. The region may correspond to a location within a predetermined distance (e.g., relative to a threshold value, such as one block, one hundred yards, etc.) from the delivery location. For example, if the history indicates that a theft exists in the area, the delivery instructions may require a signature of a person at the delivery location, provide information about a different, more secure unloading location, and/or deny delivery. Similarly, when it is not feasible or safe to complete a delivery with respect to a delivery location, the delivery instructions may default to delivering the item to that location if a predefined delivery bin is located in the area.

Further, delivery management device 244 and/or computer system 220 may update the delivery instructions based on the parameters of the current delivery. For example, if the current delivery is unsuccessful (e.g., the item is not unloaded or the item is stolen), the delivery instructions may be automatically updated to reschedule another delivery. In an example, the update may be based on a delivery history as described herein above. In another example, the update may be based on settings or preferences of the user account.

The detection of the uninstallation may use the proximity of the delivery management device 244 to the passive device 210 and/or the delivery device 230. In an example, delivery management device 244 may increase the RF ping rate. The offloading may have occurred when an RF response is received from the passive device 210 within a predefined time period (e.g., within five minutes). In another example, a weight sensor and/or a pressure sensor may sense the retainer 212, which may indicate that unloading may have occurred. In another example, an input indicating unloading may be received at a user interface of the delivery management device 244. This input may be provided by an operator of delivery device 230. In another example, the user interface (or some other interface) of delivery device 230 may receive an indication of the uninstallation (from the operator or from the delivery vehicle) and may send this indication to delivery management device 244. In yet another example, delivery management device 244 may detect the uninstallation by detecting the proximity of the passive device (e.g., based on an RF ping instruction or sensor) and by establishing communication with delivery device 230.

The detection of non-uninstallation may also use the proximity of the delivery management device 244 to the passive devices 210 and/or the delivery device 230. In an example, delivery management device 244 may send an RF ping instruction based on the proximity of delivery management device 244 to delivery device 230. If a response is not received from the passive device 210, the delivery management device 244 may detect that no offloading has occurred. Thus, a notification may be generated that no offloading has occurred. Further, in this case, the delivery management device 244 may perform an automatic action. Such an action may be defined in the delivery instruction. For example, the delivery management device 244 may reorder the items, reschedule the delivery, or request a refund with an expedited delivery method.

The virtual handover may be detected based on the interaction between the delivery management device 244 and the delivery device 230. For example, delivery device 230 may request a virtual signature from delivery management device 244. Upon detecting the uninstallation, the delivery management device 244 may respond with a virtual signature. In another example, upon detecting the uninstallation and upon termination of communication with the delivery device 230 (e.g., due to physical distance), the delivery management device 244 may determine that a virtual handover may have occurred.

After delivery device 230 leaves destination 240 and/or any communication with delivery management device 244 is terminated, a notification may be provided regarding the movement, lack of movement, relevant environmental conditions, and/or pickup of the item (or holder 212). In an example, the delivery management device 244 may generate these notifications. In another example, the delivery management device 244 may provide relevant information to the computer system 220 to generate the notification. When generated, the user device 260 may receive notifications from the computer system 220 and/or from the delivery management device 244 independent of the computer system 220.

Various techniques may be used to detect movement of an item. In an example, RF ranging may be used. For example, delivery management device 244 may estimate a proximity (e.g., reach) to passive device 210 based on the response to the RF ping instruction. Movement may be detected if the proximity varies between two RF ping instructions (e.g., based on the signal strength of the RF signal response from passive device 210). Further, if the RF response is no longer received, the delivery management device 244 may detect that the item may have left the geofence of the destination 240 (unless a pickup may have occurred). In another example, weight and/or pressure sensors may be used to detect movement of items. For example, any change in the sensed data (e.g., no more pressure is sensed) may indicate that the item may have moved.

In addition to movement, no movement may also be determined as a delivery event. A corresponding notification may be provided to the user device 260. For example, if an item is not picked up within a time period after uninstalling, a notification may be generated. The time period may be defined based on different parameters. Exemplary parameters may include the item itself. For example, if the item is a grocery item (e.g., ice cream, frozen entree, or milk), the time frame may be short relative to other types of items. Similarly, if the value of an item exceeds a threshold, the time range may be shorter relative to less valuable items.

Similarly, various techniques may be used to detect environmental conditions that may affect an item. In an example, an environmental sensor (e.g., a rain or moisture sensor, a humidity sensor, a temperature sensor, a light sensor, an optical sensor, etc.) of the delivery management apparatus 244 can detect the environmental condition. In another example, the delivery management device 244 may access environmental information regarding the location of the delivery management device 244 from a website over the network 250 to determine the environmental condition. If this condition is detected prior to the pick-up, the delivery management device 244 may access (locally or remotely from the computer system 220) recommendations related to the delivery of the item to be provided to the user device 260 (e.g., recommendations to pick up within a time frame, move the item to a covered area, etc.).

Various techniques may also be used to detect pickups. In one example, the indication of the pickup may be received at a user interface of the delivery management device 244 or remotely from the user device 260. In another example, the pickup may be determined based on the proximity between the delivery management device 244 and the user device 260. For example, computer system 220 may detect proximity based on GPS locations of delivery management device 244 and user device 260. Additionally or alternatively, the delivery management device 244 may receive the GPS location of the user device 260 from the computer system 220 or from the user device 260 independently of the computer system 220. Based on the proximity and movement of the item, the delivery management device 244 may determine that a pickup may have occurred.

The delivery management device 244 may also include or interface with an optical sensor. The optical sensor may form an imaging device. Delivery management device 244 and/or computer system 220 may trigger the imaging device to generate an image when a different delivery event is detected. For example, upon detecting an unload, an image may be generated that the item is unloading. Similarly, upon movement or pickup, a corresponding image may be generated. Such images may be stored locally at delivery management device 244 and/or transmitted to computer system 220 and/or user device 260. For example, images may be added to the notifications.

When an optical sensor is used, various image recognition techniques (such as face recognition techniques) may optionally be implemented. Such techniques may be implemented at delivery management device 244 and/or computer system 220. The images may be analyzed using facial recognition techniques to detect success or failure of the delivery event. For example, the delivery management device 244 may access the user's image through, for example, a user account. At the time of pickup, the delivery management device 244 may analyze the corresponding image, detect the face of the individual picking up the item, and compare the detected face with the known image of the user. If there is a match, the delivery management device 244 may determine that the pickup may have been successful; otherwise, a failure may be determined. A notification of success or failure may be provided to the user equipment 260.

As such, passive device 210 may be used in conjunction with delivery management device 244 and/or delivery device 230 to facilitate various notifications to user device 260. These notifications may span the entire delivery process (such as from the beginning of delivery to picking up the item at destination 240) and may include information about different delivery events.

In addition to interfacing with the computer system 220, the delivery device 230, and/or the user equipment 260, the delivery management device 244 may also interface with other nodes of the local area network 242 of the destination 240. These nodes may include various automation devices installed at destination 240, such as connected or intelligent devices or appliances. For example, the nodes may include a smart switch for turning lights on and off, a smart switch for turning ovens on and off, or other automated equipment. Upon occurrence of a delivery event, the delivery management device 244 may indicate the delivery event to one or more automation devices via the local area network 242. In response, the automation device may initiate an action at destination 240. The action may be predefined by the user. For example, upon uninstalling a freeze main menu, the delivery management device 244 may identify an item (e.g., a freeze main menu) based on the order and access instructions (e.g., a cooking temperature) from a remote computing resource (e.g., from the computer system 220) for preparing the item. The delivery management device 244 may notify the intelligent switch about the unloading and some instructions for preparing the item (e.g., cooking temperature). The switch may then turn on the oven and set the baking temperature according to the information received from the delivery management device 244.

Generally, the delivery process may include multiple stages. At each stage, interaction between different components may be possible, resulting in different notifications. FIG. 3 provides an illustrative table summarizing the phases, interactive components, and resulting notifications. Some interactions or information thereof may be tracked by a computer system and used to generate notifications by the computer system and/or by one or more interactive components. As such, the computer system may involve various stages, but for clarity of explanation it is not shown in FIG. 3.

As shown, the delivery process may include four phases 310: prepare 312, en route 314, unload 316, and pick up 318. Other stages and/or combinations of stages are also possible. At each stage, one or more interactive components 320 may be involved. The interaction may result in one or more end user notifications 330 and/or one or more delivery device notifications 340. End user notification 330 may be provided to a user device (such as user device 260 of fig. 2). In contrast, delivery notification 340 may be provided to a delivery device (such as delivery device 230 of fig. 2).

In the preparation phase 312, an order for the item may have been received and may be processed in preparation for delivery. The computer system may provide instructions for the passive device to include the order or item. As such, the interactive component 320 may comprise a passive device. End user notification 330 and delivery device notification 340 may describe: the order may be in progress.

While in the in-transit phase 314, delivery may have begun, but unloading may not have occurred. For example, the item may have been loaded onto a delivery vehicle, and the delivery vehicle may be en route to a destination. As such, the interactive component 320 may include a passive device and a delivery device. Thus, while en route, the end user notification 330 may indicate the start of delivery and provide the location of the item. In contrast, delivery device notification 340 may include a delivery instruction.

In the unloading stage 316, the delivery device and the passive device may have reached the destination. The resulting interaction with the delivery management device may result in offloading. As such, the interaction component 320 can include a passive device, a delivery device, and a delivery management device. End user notification 330 may indicate the completion and time of the offload. The end user notification 330 may also describe the location of the item (e.g., the unload location) and any environmental conditions (including relevant recommendations). In contrast, the delivery device notification 340 may include delivery instructions, such as the location of the delivery management device and any offload authorization therefrom. The delivery device notification 340 may also include information about the virtual handover.

In the pick-up stage 318, the delivery device may have left the destination. However, additional interactions may occur between the passive device, the delivery management device, and/or the user device until a pickup may have been detected. As such, the interaction component 320 may include a passive device, a delivery management device, and a user device. Thus, end user notification 330 may indicate movement, non-movement (e.g., based on an elapsed period of time), and/or pickup of the item. The end user notification 330 may also describe the location of the item (e.g., the unload location) and any environmental conditions (including relevant recommendations). In contrast, delivery device notifications 340 may similarly provide information regarding movement, pick-up, and/or environmental conditions. There may also be interactions with and notifications to other devices. For example, the delivery management device may notify an automation device at the destination of the unloading, moving, and/or picking of the item.

In this way, meaningful notifications can be provided to the respective devices throughout different phases of delivery. Thus, the parties involved may have access to recent and up-to-date information about the item (or its delivery). Further, because notifications can be specifically tailored based on interaction, a sufficient or desired amount of notifications can be generated and transmitted, which can optimize the use of various computing resources.

Fig. 4 illustrates another embodiment for providing notifications. In this embodiment, instead of passive devices, active devices may be used. Being in an active state may reflect an implementation in which the device may be self-powered and capable of performing various operations based on the local processor and memory. For example, an active device may represent a computing device having a suitable form factor for attaching to a holder of an item and for use in the delivery of the item. By using an active device, most of the functionality of the delivery management device can be pushed to the active device. Depending on the implementation of the active device, the delivery management device may not even be needed.

As shown in fig. 4, a user device 410 may interact with a computing system 420 of an electronic marketplace over a network 430 to order an item for delivery to a destination 440. Notifications regarding items, orders, and/or deliveries may be provided to the user device 410. As part of the delivery, the holder 450 may hold the item. Active device 452 may be attached to the holder. Active device 452 may interact with delivery device 460 and local area network 442 (or a computing node of such a network). The interaction may result in a notification to the user device 410.

In an example, the active device 452 can include a processor, memory, a wireless or wired interface, and a power source to facilitate notification. For example, active device 452 may include an active 802.11RFID tag. Other configurations of active device 452 may be used. For example, active device 452 may include additional hardware and/or software components, such as a GPS receiver, various sensors, and/or a delivery management module. Further, the active device 452 may include an interface for attachment to the holder 450, such as an interface that may use adhesive surfaces, magnets, hook and loop fasteners, and/or other attachment means.

Local area network 442 may communicatively connect various computing nodes located at destination 440 (e.g., within or within a geofence of destination 440). Local network 442 may also be connected to network 430 such that communication paths may exist between computing nodes and computer system 420, user device 410, and/or delivery device 460. These computing nodes may include, for example, access points, routers, intermediate computing devices capable of connecting external computing devices (e.g., active device 452) to local network 442, automation devices, imaging devices, and/or other computing resources.

To facilitate interaction and thereby provide notification, various tokens may be used between the active device 452, the local area network 442 (e.g., a computing node of the local area network 442), and the delivery device 460. In general, a token may represent a secret that may be shared between computing devices to facilitate communication between the computing devices. The token may be revocable, facilitating management of the communication. For example, a token may expire after a certain period of time or after multiple uses (e.g., a single use). As such, the token may no longer be available while the delivery may be complete.

In an example, a token may be generated and distributed to the correct computing device according to an order for the item. For example, the token may be generated by computer system 420, user device 410, and/or a computing node of local area network 442. The same token, portions of the token, or different tokens may be sent to active device 452, local area network 442 (e.g., a computing node thereof), and/or delivery device 460. As shown in fig. 4, the received token may be stored as token 444 at local network 442, as token 454 at active device 452, and as token 462 at delivery device 460. Tokens 444, 454, 462 may be copies of the same token, different tokens, or portions of the same token.

In operation, tokens 444 and 454 may be generated and distributed according to an order for an item. Tokens 462 may be similarly generated and distributed, or may be predefined tokens independent of the order. The token may be used to determine proximity between different components. Notifications (including notifications regarding delivery events) may be generated based on proximity. Further, delivery instructions may be provided from computer system 420 and/or user device 410 to computing nodes of active device 452, delivery device 460, and/or local area network 442 via network 430. The delivery instruction may be similar to the delivery instruction described in connection with fig. 2.

At the beginning of delivery, the delivery device 460 may interact with the active device (e.g., read an RFID tag or exchange information over a communication link). Tokens 454 and 462 may, but need not, be used to authorize the start of delivery. If the delivery device 460 does not have delivery instructions, such instructions may be provided from the active device 452. Further, a notification regarding the start of delivery may be generated and provided to the user device 410. In an example, the active device 452 and/or the delivery device 460 can generate a notification. In another example, communication between active device 452 and delivery device 460 may trigger computer system 420 to generate a notification. When generated, the notification may be sent to the user device 410 over the network 430. In an example, computer system 420 can send a notification. In another example, active device 452 and/or delivery device 460 may send notifications independently of computer system 420.

En route, communication between the active device 452 and the delivery device 460 may be maintained. For example, one or both of device 452 and device 460 may send ping instructions to each other and thus determine that communication may still exist and that the two devices may be in proximity to each other. Based on this proximity, a notification may be provided to the user device 410. The notification may indicate that the item may be en route and may show the geographic location of the item based on the location of the active device 452, the delivery device 460, and/or the delivery vehicle. Active device 452, delivery device 460, and/or computer system 420 may generate and send notifications to user device 410 over network 430.

Upon reaching the destination 440 (e.g., upon entering the geofence of the destination 440), the proximity between the local area network 442, the active device 452, and/or the delivery device 460 may be determined. These proximities may be used to authorize the offloading, provide delivery instructions, detect offloading, detect that offloading has not occurred, and/or complete the virtual handover. Proximity may be based on interactions between local area network 442 (or its computing node), active device 452, and/or delivery device 460. These interactions may be facilitated through communications that may use tokens 444, 454, and 462. Upon any of these events (e.g., authorization, offloading, and/or virtual handoff), information regarding the event may be provided to computing system 420 from local area network 442 (or a computing node thereof), active device 452, and/or delivery device 460. A corresponding notification may also be sent to the user device 410 by the computer system 420 or independent of the computer system 420 (e.g., by the local area network 442 (or a computing node thereof), the active device 452, and/or the delivery device 460).

In an example, the active device 452 and the local area network 442 (or computing nodes thereof) can establish a communication link based on the tokens 454 and 444. Similarly, delivery device 460 and/or local network 442 (or computing nodes thereof) may establish a communication link based on tokens 462 and 444. Further, a communication link may exist or be established between the active device 452 and the delivery device 460. This communication link may, but need not, use tokens 454 and 462. Upon establishing communication with local area network 442, active device 452 may determine whether offloading is likely to occur based on pre-stored delivery instructions or any other instructions received over the communication link (e.g., whether the correct item is in delivery, the time of delivery, any special offloading instructions, etc.). If so, the active device 452 may authorize the delivery device 460 to offload and provide the relevant delivery instructions. Otherwise, the unloading may be denied.

Detection of offloading may use various proximity or interaction-based rules. In an example, offloading may be determined if local area network 442 (or a computing node thereof) and active device 452 remain in communication for a predefined period of time (e.g., five minutes). In another example, the user interface (or some other interface) of the delivery device 460 may receive an indication of the offloading (from an operator or from a delivery vehicle) and may send this indication to the local area network 442 (or a computing node thereof) and/or the active device 452. In yet another example, a rule may specify that offloading may have occurred if communication between local network 442 (or a computing node thereof) and active device 452 is maintained while communication of local network 442 (or a computing node thereof) and/or active device 452 with delivery device 460 is terminated.

Various proximity may also be used to detect that no offloading is taking place. In an example, local area network 442 (or a computing node thereof) may detect that no offloading has occurred if local area network 442 (or a computing node thereof) is proximate to delivery device 460 but not sufficiently proximate between local area network 442 (or a computing node thereof) and active device 452. Thus, a notification may be generated that no offloading has occurred. Further, in this case, local network 442 (or its compute node) may perform automatic actions. Such an action may be defined in the delivery instruction. For example, the local area network 442 (or its computing nodes) may reorder items, reschedule delivery, or request a refund with an expedited delivery method.

Virtual handoff may be detected based on interaction of active device 452 and/or local network 442 (or computing nodes thereof) with delivery device 460. For example, delivery device 460 may request a virtual signature from active device 452 and/or local area network 442 (or a computing node thereof). Upon detecting the offload, the active device 452 and/or the local area network 442 (or computing nodes thereof) may respond with a virtual signature. In another example, upon detecting the offloading and upon termination of communication with delivery device 460 (e.g., due to physical distance), delivery device 460, active device 452, and/or local area network 442 (or a computing node thereof) may determine that a virtual handoff may have occurred.

After delivery device 460 leaves destination 440 and/or any communication with active device 452 and/or local network 442 (or computing nodes thereof) is terminated, a notification may be provided regarding movement of the item, lack of movement (e.g., based on an elapsed period of time as described in connection with fig. 2), related environmental conditions, and/or pickup. Upon any of these events (e.g., movement, environmental conditions, pickup), information regarding the event can be provided to the computing system 420 from the local area network 442 (or computing node thereof) and/or the active device 452. A corresponding notification may also be sent to user device 410 by computer system 420 or independent of computer system 420 (e.g., by local area network 442 (or a computing node thereof) and/or active device 452).

Various techniques may be used to detect movement of an item. In an example, RF ranging may be used. For example, the active device 452 and/or the local area network 442 (or computing nodes thereof) may estimate proximity (e.g., distance) based on the communication between the two and the strength of the RF signal. If the proximity changes, movement may be detected. Additionally, if the communication is terminated, the active device 452 and/or the local area network 442 (or computing nodes thereof) may detect that the item may have left the geofence of the destination 440 (unless a pickup may have occurred). In yet another example, movement may be determined from a GPS location of active device 452. For example, if the active device 452 includes a GPS receiver and the corresponding GPS data indicates a change in location, movement may be detected.

Similarly, various techniques may be used to detect environmental conditions that may affect an item. In an example, the active device 452 may include one or more environmental sensors (e.g., rain sensors). These sensors may detect environmental conditions. In another example, local area network 442 (or a computing node thereof) or computer system 420 can access environmental information about destination 440 from a website over network 430 to determine environmental conditions. If this condition is detected prior to the pick-up, the computer system 420, active device 452, and/or local network 442 may provide a recommendation to the user device 410 regarding the environmental condition (e.g., recommending that the item be picked up within a time frame, moved to a covered area, etc.).

Various techniques may also be used to detect pickups. In one example, the indication of the pickup may be received at a user interface of active device 452 (when the device includes such an interface) or remotely from user device 410. In another example, the pickup may be determined based on the proximity of the user device 410 to the active device 452 and/or the local area network 442 (or computing nodes thereof). For example, computer system 420 may detect proximity based on a corresponding GPS location. Additionally or alternatively, the active device 452 and/or the local area network 442 (or computing nodes thereof) may receive the GPS location of the user device 410 from the computer system 420 or from the user device 410 independent of the computer system 420. Based on proximity and movement of the item, pickup may be detected.

Destination 440 may also include various optical sensors. The optical sensor may form an imaging device. Local network 442 (or a computing node thereof) and/or computer system 420 can trigger an imaging device to generate an image upon detecting a different delivery event including an unload, move, not move, and/or pick up. Such images may be stored locally at local network 442 and/or transmitted to computer system 420 and/or user device 410. For example, images may be added to the notifications.

When an optical sensor is used, various image recognition techniques (such as face recognition techniques) may optionally be implemented. Such techniques may be implemented at local network 442 (or a computing node thereof) and/or computer system 420. The images may be analyzed using facial recognition techniques to detect success or failure of the delivery event. For example, computer system 420 may access the user's image through, for example, a user account. At pickup time, the computer system 420 may analyze the corresponding image, detect the face of the individual picking up the item, and compare the detected face to the known image of the user. If there is a match, computer system 420 may determine that the pick may have been successful; otherwise, a failure may be determined. A notification of success or failure may be provided to the user device 410.

As such, the active device 452 may be used in conjunction with the local area network 442 and/or the delivery device 460 to facilitate various notifications to the user device 410. These notifications may span the entire delivery process (such as from the beginning of the delivery to picking up the item at the destination 440).

In addition to interfacing with local area network 442, computer system 420, delivery device 460, and/or user device 410, active device 452 may interact with other nodes of local area network 442 through local area network 442. These nodes may include various automation devices installed at the destination 440. For example, the nodes may include a smart switch for turning lights on and off, a smart switch for turning ovens on and off, or other automated equipment. Upon occurrence of a delivery event, the active device 452 (or a computing node of the local area network 442) may indicate the delivery event to one or more automation devices via the local area network 442. In response, the automation device may initiate an action at destination 440, such as, for example, turning on the oven based on the unloading of the frozen main menu.

Fig. 5 provides an explanatory table summarizing the different phases, interactive components and resulting notifications when using an active device. Some interactions or information thereof may be tracked by a computer system and used to generate notifications by the computer system and/or by one or more interactive components. As such, the computer system may involve various stages, but for clarity of explanation it is not shown in FIG. 5.

As shown, the delivery process may include four phases 510: prepare 512, en route 514, unload 516, and pick 518. Other stages and/or combinations of stages are also possible. At each stage, one or more interactive components 520 may be involved. The interaction may result in one or more end user notifications 530 and one or more delivery device notifications 540. End user notification 530 may be provided to a user device (such as user device 410 of fig. 4). In contrast, delivery notification 540 may be provided to a delivery device (such as delivery device 460 of fig. 4).

In the preparation phase 512, an order for the item may have been received and may be processed in preparation for delivery. The computer system may provide instructions for causing the active device to include the order or item. The instructions may relate to delivery and may include a token that may be used by the active device to access a local area network at the destination. As such, the interaction component 520 may include an active device, and the end user notification 430 and the delivery device notification 440 may describe that the order may be in process. In this stage, the same or different token may be provided to the delivery device for accessing the local area network 442 and/or the active device 452.

While in the in-transit stage 514, delivery may have begun, but unloading may not have occurred. The interactive component 520 may include an active device and a delivery device. While en route, the end user notification 530 may indicate the start of the delivery and provide the location of the item. In contrast, delivery device notification 540 may include a delivery instruction. If no token may have been provided to the delivery device in the preparation stage 512, such a token may be provided to the delivery device from the active device or computer system in the en-route stage 514.

In the offload phase 516, the delivery device and the active device may have reached the destination. The resulting interaction with the local area network (or its compute nodes) may result in offloading. As such, the interaction component 520 may include an active device, a delivery device, and a local area network (or computing node thereof). End user notification 530 may indicate the completion and time of the offload. The end user notification 530 may also describe the location of the item (e.g., based on the active device's GPS receiver (when using the active device's GPS receiver) or based on the user-entered unload location at the delivery device) and any environmental conditions (including relevant recommendations). In contrast, the delivery device notification 540 may include delivery instructions, such as the location of the delivery management device and any offload authorization therefrom. The delivery device notification 540 may also include information about the virtual handover.

In the pick-up phase 518, the delivery device may have left the destination. However, interaction may occur between the active device, the local area network (or its computing node), and/or the user device until a pickup may have been detected. As such, the interaction component 520 may include an active device, a local area network (or computing node), and a user device. The end user notification 530 may indicate movement, non-movement (e.g., based on an elapsed period of time), and/or pickup of the item. The end user notification 530 may also describe the location of the item (e.g., the unload location) and any environmental conditions (including relevant recommendations). In contrast, the delivery device notification 540 may similarly provide information regarding movement, pickup, and/or environmental conditions. There may also be interactions with and notifications to other devices. For example, the active device and/or the local area network (or computing nodes thereof) may notify an automation device item located at the destination of the uninstallation, movement, and/or pickup.

Turning to fig. 6-10, these figures illustrate exemplary flows for managing notifications. FIG. 6 illustrates an exemplary high-level flow for generating and transmitting notifications. Fig. 7 and 8 illustrate exemplary flows that a computer system and a delivery management device, respectively, may be implemented to manage notifications in a computing environment that may include passive devices. In contrast, fig. 9 and 10 illustrate exemplary flows that a computer system and an active device, respectively, may be implemented to manage notifications in a computing environment that may include active devices. Some operations of the exemplary flows of fig. 6-10 may be similar. For clarity of explanation, such similarities are not repeated here.

Further, in illustrative operations, some operations or functions may be embodied in, and automated in whole or in part by, modules executed by one or more processors. Further, while the operations are shown in a particular order, it should be understood that no particular order is required and that one or more operations may be omitted, skipped, and/or reordered.

The example flow of FIG. 6 may begin at operation 602, where an order for an item may be received. For example, a user may operate a user device to access an electronic marketplace that provides items over a network. A computer system that facilitates functionality of an electronic marketplace may receive an order for an item from a user device. The computer system may also receive a description of the destination, such as an address, for delivery of the item.

At operation 604, delivery of the item may be prepared. For example, the computer system may provide instructions regarding delivery. According to an implementation, instructions may be used to configure a passive device and/or an active device that may be attached to a holder that holds an item for delivery. Configuring the passive device may include storing information about the order, the item, the destination, and/or the delivery instruction in the passive device or in association with an identifier stored in the passive device. For example, a passive RFID tag that can print encoded information. Configuring the active device may include storing similar information at the active device or in association with an identifier stored in the active device. Further, a token for accessing the local area network associated with the destination may be stored in the active device or in association with an identifier stored in the active device. An exemplary active device may include an active 802.11RFID tag.

At operation 606, a notification regarding the start of delivery may be provided to the user device. For example, the delivery device may interact with the passive device and/or the active device. The delivery device may be associated with a delivery vehicle. The interaction may depend on the implementation of such devices. For example, RF-based communication may be used. Upon interaction, the computer system may receive an indication of the interaction from the delivery device and/or the active device over the network. This indication may indicate the start of delivery. Further, the computer system, the active device, and/or the delivery device may send a notification to the user device based on the interaction.

At operation 608, the location data may be provided to the user device throughout the delivery process until the destination is reached. For example, the passive devices, active devices, delivery devices, and/or delivery vehicles may include position location devices (such as GPS receivers). The local positioning device may provide the location data to the computer system. In turn, the computer system can facilitate the user device to access the location data.

At operation 610, a notification may be sent to a user device regarding the uninstallation of the item at the destination. If passive devices are used, the delivery management device may be located at the destination. Interaction of the delivery management device with the passive device and/or the delivery device may result in detection of the offload. In contrast, if an active device is used, a computing node of the local area network at the destination may interact with the active device and/or the delivery device. The interaction may be used to determine offloading. In both cases, the computer system may receive an indication of offloading from a delivery management device, a delivery device, a computing node of a local area network, and/or an active device. Further, the computer system, the delivery management device, the delivery device, the computing node of the local area network, and/or the active device may send a corresponding notification to the user device.

At operation 612, a notification may be sent to the user device regarding moving the item at the destination. If a passive device is used, the delivery management device may determine that the proximity between the delivery management device and the passive device may have changed. Such a change may correspond to a movement. The proximity determination may use different techniques, such as RF ranging (using an RF transceiver of the delivery management device), optical ranging (using an optical sensor of the delivery management device), and/or sensing weight and/or pressure changes (using a weight and/or pressure sensor of the delivery management device). If an active device is used, a computing node of the local area network may determine that the proximity between the computing node and the active device may have changed. Such changes may correspond to movement. Proximity determination may use different techniques, such as RF ranging (using the computing node's RF transceiver) and/or using a location fix (e.g., GPS data for an active device). The computer system may receive an indication of movement from a delivery management device, a delivery device, a computing node of a local area network, and/or an active device. Further, the computer system, the delivery management device, the delivery device, the computing node of the local area network, and/or the active device may send a corresponding notification to the user device.

At operation 614, a notification may be sent to the user device regarding picking up the item at the destination. Different techniques may be used to determine pickup. In an example, proximity may be used. For example, a proximity between the user device and a delivery management device and/or a computing node of a local area network may be determined (e.g., based on GPS data, RF ranging, etc.). This proximity may be compared to the proximity of the user device, the delivery management device, and/or the computing node of the local area network to the passive device and/or the active device. Pickup may be determined based on the comparison. For example, if the comparison indicates that the user device is in a close location to the passive device and/or the active device, a pickup may have occurred. The computer system may receive an indication of pickup from a delivery management device, a delivery device, a computing node of a local area network, and/or an active device. Further, the computer system, the delivery management device, the delivery device, the computing node of the local area network, and/or the active device may send a corresponding notification to the user device.

Turning to fig. 7, the figure illustrates an exemplary flow that a computer system may implement to manage notifications using a passive device. The exemplary flow may begin at operation 702, where a computer system may provide instructions related to a passive device for item delivery. The instructions may be used, for example, to store information about the delivery at the passive device or in association with an identifier stored in the passive device. If passive RFID tags are used, instructions may be used to print such tags.

At operation 704, the computer system may receive an indication of an interaction between the passive device and the delivery device. For example, the delivery device may read, scan, or radiate the passive device with an RF signal, and may thus transmit an indication to the computer system. At operation 706, the computer system may determine a start of delivery based on the received indication. Further, the computer system may transmit a notification to the user device regarding the start.

At operation 708, the computer system may provide the delivery instructions to the delivery management device. Similar instructions may also be provided to the delivery device. In an example, the user device may also specify specific instructions regarding delivery of the item (e.g., a particular location at the destination, a delivery time, a requested signature, etc.) according to the order for the item. In response, the computer system may generate and send delivery instructions to the delivery management device and/or the delivery device.

At operation 710, the computer system may receive an indication of an interaction between a delivery management device and a passive device. For example, the delivery management device may send an indication to the computer system that the passive device may be in proximity to the delivery management device. Further, the computer system may receive a similar indication from the delivery device (or delivery management device) regarding proximity to the delivery management device (or delivery device).

At operation 712, the computer system may determine that an offload may have occurred at the destination. Such a determination may be based on one or more received indications. For example, the computer system may determine that a potential offload may have occurred based on the proximity of the delivery management device and the passive device. The computer system may use various techniques to confirm this potential uninstallation. For example, after a predefined period of time, if the proximity is maintained (e.g., based on another indication received from the delivery management device), a confirmation may be made. In another example, the confirmation may be based on an indication of proximity of the delivery device and the delivery management device. In yet another example, the computer system may receive an indication of proximity between the delivery management device, the delivery device, and the passive device. The confirmation may be made if the delivery device is no longer in proximity to the delivery management device after a predefined period of time. The computer system may thus send a notification to the user device regarding the uninstallation.

At operation 714, the computer system may receive a change in proximity between the passive device and the delivery management device. For example, the delivery management device may detect the change and send an indication of the change to the computer system. At operation 716, the computer system may determine movement of the item based on the change. The computer system may thus send a notification to the user device about the movement.

At operation 718, the computer system may determine the pick of the item. For example, the computer system may receive an indication of pickup from the user device. In another example, the proximity of the delivery management device, the passive device, and the user device may be used to detect pickup. For example, the computer system may access the location locations (e.g., GPS data) of the user device and the delivery management device. If the two devices are likely to be in proximity to each other, the computer system may access (e.g., request and receive or automatically receive) an indication of item movement from the delivery management device. The computer system may detect the pickup based on such proximity and movement.

Turning to fig. 8, the figure illustrates an exemplary flow that a delivery management device may implement to manage notifications when using passive devices. The exemplary flow may begin at operation 802, where a delivery management device may receive a delivery instruction associated with an order for an item. The delivery instructions may be received from the computer system and/or the user device and may provide information about the order. For example, the information may include a unique identifier associated with the order.

At operation 804, the delivery management device may determine a proximity to the passive device. This proximity may be determined based on interaction with the passive device and/or the delivery device. The interaction may include, for example, receiving information about the order from the passive device, or based on information stored in association with an identifier in the passive device.

At operation 806, the delivery management device may authorize the uninstallation of the item. For example, the delivery management device may compare information received from the passive device and/or the delivery device with information received from the computer system and/or the user device. If an acceptable match is found (e.g., the unique identifiers associated with the orders are the same), then the offload may be authorized. The delivery instructions may also include, for example, a delivery time range and/or environmental conditions (e.g., unloading occurs when there is no rain). The delivery management device may further authorize the offloading based on the delivery time range and/or the environmental condition. When authorized, the delivery management device may send an indication of the authorization to the computer system and/or the delivery device. Further, the delivery management device and/or the computer system may send a corresponding notification to the user device.

At operation 808, the delivery management device may provide a portion of the delivery instructions to the delivery device. For example, the delivery instructions may include a specific location for unloading the item at that location. In this way, the delivery management device may identify this location to the delivery device.

At operation 810, the delivery management device may determine completion of the offloading. Such a determination may be made based on the proximity of the delivery management device to the passive device and/or the delivery device. For example, if the passive device remains near the delivery management device for a predefined period of time, completion of the offloading may be detected. In another example, completion of the offloading may be detected if the delivery device is no longer in proximity to the delivery management device.

At operation 812, the delivery management device may provide information regarding the completion of the offload to the computer system, the delivery device, and/or the user device. For example, the delivery management device may send an indication of the completion of the uninstallation to the computer system and/or the delivery device. Further, the delivery management device and/or the computer system may send a corresponding notification to the user device.

At operation 814, the delivery management device may determine a change in proximity between the delivery management device and the passive device. At operation 816, the delivery management device may determine movement of the item based on the change in proximity. The delivery management device may send an indication of the movement to the computer system. Further, the delivery management device and/or the computer system may send a corresponding notification to the user device.

At operation 818, the delivery management device may determine a pick of the item. Pick-up may be determined based on proximity (or lack thereof) to the passive device. For example, if the passive device is no longer located at a location proximate to the delivery management device, a pickup may be determined. Further, the pickup may be determined based on proximity to the user device. For example, the delivery management device may determine a location of the user device (e.g., based on GPS data of the user device, where the GPS data may be received from the user device or the computer system). Pick-up may be detected if the user device and the passive device are in proximity to the delivery management device at a point in time after which both devices are no longer in proximity to the delivery management device. The delivery management device may send an indication of the pickup to the computer system. Further, the delivery management device and/or the computer system may send a corresponding notification to the user device.

Turning to FIG. 9, the figure illustrates an exemplary flow that a computer system may implement to manage notifications using an active device. The exemplary flow may begin at operation 902, where a computer system may provide a token for storage at an active device. The token may be generated by a computing node of a local area network of the computer system, the user device, and/or the destination based on the order for the item.

At operation 904, the computer system may receive an indication of an interaction between the active device and the delivery device. For example, the delivery device may read, scan, or establish data communication with the active tag, and may therefore transmit an indication to the computer system. At operation 906, the computer system may determine a start of delivery based on the received indication. Further, the computer system may transmit a notification to the user device regarding the start.

At operation 908, the computer system may provide the delivery instructions to the delivery device. At operation 910, the computer system may receive an indication from a computing node of a local area network regarding communication with an active device. The communication may be based on a token. For example, the computing node may receive a token from the active device and authenticate the active device accordingly. The computing node may send an indication of the communication to the computer system. Further, the computer system may receive an indication of communication between the delivery device and the compute node. Such communication may also be based on the same or different tokens. The indication of the communication may be received from a delivery device and/or a computing node.

At operation 912, the computer system may determine that an offload may have occurred at the destination. Such a determination may be based on one or more received indications. For example, the computer system may determine that a potential offload may have occurred based on the communications of the compute node and the active device. The computer system may use various techniques to confirm this potential uninstallation. For example, the offloading may be confirmed based on communication between the delivery device and the computing node or based on termination of such communication (which may be received in another indication from the delivery device and/or the computing node). In another example, offloading may be determined based on proximity of the active device to the destination. For example, the computer system may receive location information (e.g., GPS data) of the active device and may compare the location information to one of the destinations. Offloading may have occurred if the active device remains within the destination's geofence for a predefined period of time. In yet another example, the offloading may be determined based on a proximity of the delivery device to the destination. For example, the computer system may receive location information (e.g., GPS data) of the delivery device and may compare the location information to one of the destinations. The offloading may be complete if the delivery device enters and then leaves the geofence while communication between the compute node and the active device continues.

At operation 914, the computer system may receive a change in proximity between the active device and the delivery management device. For example, the computer system may receive location information (e.g., GPS data) of the active device and may compare the location information to one of the destinations. If there is a change in location information, the change may correspond to a change in proximity. At operation 916, the computer system can determine movement of the item based on the change. The computer system may thus send a notification to the user device about the movement.

At operation 918, the computer system may determine a pick of the item. For example, the computer system may receive an indication of pickup from the user device. In another example, the proximity of the computing node, the active device, and the user device may be used to detect the pickup. For example, the computer system may access location information (e.g., GPS data) of the computing node, active devices, and user devices to determine proximity and thus detect pickup.

Turning to fig. 10, the figure illustrates an exemplary flow that an active device may implement to manage notifications. The exemplary flow may begin at operation 1002, where an active device may store a token associated with item delivery. The token may be received from a computer system, a computing node of a local area network of the destination, and/or a user device.

At operation 1004, the active device may establish communication with the delivery device. At operation 1006, the active device may cause an indication of the start of delivery. For example, the communication may cause the delivery device and/or the active device to send an indication to the computer system. Further, the computer system, delivery device, and/or active device may send a corresponding notification to the user device.

At operation 1008, the active device may establish communication with a computing node of the local area network. Such communication may be established based on authentication of the active device using the token.

At operation 1010, the active device may cause a determination to be made of the uninstallation of the item. Offloading may be determined based on proximity of the active device to the computing node and/or the delivery device. Based on this proximity, the active device, the computing node, the delivery device, and/or the computer system may determine that an offload may have occurred. A corresponding notification may be sent to the user device and/or the delivery device. In an example, the active device may provide its location information (e.g., GPS data) to the computer system and/or computing node, or may receive location information for the destination. Based on the comparison of the location information, proximity may be determined. In another example, a computing node and/or active device may use RF ranging to detect proximity. This proximity may be used with other factors to determine the completion of the offloading. For example, if the active device and the compute node remain close for a predefined period of time, the offload may be complete. In another example, if the delivery device is no longer located near the active device, the offloading may be complete.

At operation 1012, the active device may cause a determination of movement of the item. Movement may be determined based on proximity of the active device to the computing node. Based on this proximity, the active device, computing node, and/or computer system may determine that movement may have occurred. A corresponding notification may be sent to the user device. In an example, a change in location information of the active device relative to the destination may indicate a movement of the item. In another example, RF ranging may be applied based on communication between an active device and a compute node. RF ranging may indicate a change in the reach between an active device and a compute node. Such changes may correspond to movement of the item.

At operation 1014, the active device may cause a pick of the item to be determined. Pickup may be determined based on proximity between active devices, computing nodes, and/or user devices. Based on this proximity, the active device, computing node, and/or computer system may determine that a pickup may have occurred. A corresponding notification may be sent to the user device. In an example, if the user device moves to a location proximate to the active device, a pickup may be determined.

Turning to FIG. 11, the figure illustrates an exemplary end-to-end computing environment for managing notifications in conjunction with an electronic marketplace. In this example, the service provider may implement a notification manager to manage notifications. The notification may be related to an item purchased from an electronic marketplace. Items may be listed for supply by the seller 1110 and/or service provider and available for ordering by the customer 1160.

In a basic configuration, a vendor 1110 may utilize a vendor device 1112 to access local applications, web service applications 1120, vendor accounts accessible through the web service applications 1120, web sites, or any other network-based resource through one or more networks 1180. In some aspects, the web service application 1120, website, and/or vendor account may be hosted, managed, and/or otherwise provided by one or more computing resources of the service provider (such as by utilizing one or more service provider devices 1130). The seller 1110 may use a native application and/or a web services application 1120 to interact with the service provider's network-based resources and perform seller-related transactions. These transactions may include, for example, providing the item for sale.

In some instances, vendor device 1112 may be any type of computing device, such as, but not limited to: mobile phones, smart phones, personal Digital Assistants (PDAs), laptop computers, thin client devices, tablet PCs, and the like. In one illustrative configuration, the vendor device 1112 may contain a communication connection that allows the vendor device 1112 to communicate with a stored database, another computing device or server, a vendor terminal, and/or other devices on the network 1180. Vendor device 1112 may also include input/output (I/O) devices and/or ports, such as for enabling connection to a keyboard, mouse, pen, voice input device, touch input device, display, speakers, printer, and the like.

The vendor device 1112 may also include at least one or more processing units (or processor devices) 1114 and at least one memory 1116. Processor device 1114 may be suitably implemented in hardware, computer-executable instructions, firmware, or a combination thereof. The computer-executable instructions or firmware implementations of processor device 1114 may include computer-executable or machine-executable instructions written in any suitable programming language for performing the various functions described.

Memory 1116 may store program instructions that are loadable and executable on the processor device 1114, as well as data generated during execution of these programs. Depending on the configuration and type of vendor device 1112, memory 1116 may be volatile (such as Random Access Memory (RAM)) and/or non-volatile (such as Read Only Memory (ROM), flash memory, etc.). Vendor device 1112 may also include additional storage devices, which may include removable storage devices and/or non-removable storage devices. Additional storage devices may include, but are not limited to, magnetic storage devices, optical disks, and/or tape storage devices. The disk drives and their associated computer-readable media may provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computing device. In some implementations, the memory 1116 may include a variety of different types of memory, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), or ROM.

Turning in more detail to the contents of memory 1116, the memory may include an operating system (O/S) 1118 and one or more application programs or services (including web services application 1120) for implementing the features disclosed herein. In some examples, vendor device 1112 may communicate with service provider device 1130 via network 1180 or via other network connections. The network 1180 may include any one or combination of many different types of networks, such as a wired network, the internet, a wireless network, a cellular network, and other private and/or public networks. Although the illustrated example represents a vendor 1110 accessing a web services application 1120 via a network 1180, the described techniques may be equally applicable to the following: wherein the vendor 1110 interacts with the service provider device 1130 through a landline telephone, through a kiosk, or in any other manner through the vendor device 1112. It should also be noted that the described techniques may be applied in other client/server arrangements (e.g., set-top boxes, etc.) as well as non-client/server arrangements (e.g., locally stored applications, peer-to-peer systems, etc.).

Similarly, the customer 1160 may utilize a customer device 1162 to access local applications, a web services application 1170 (or some other mobile application such as a "mobile application" purchased from an application store), a customer account accessible through the web services application 1170, a website, or any other network-based resource via the network 1180. In some aspects, the web services application 1170, website, and/or user account may be hosted, managed, and/or otherwise provided by the service provider device 1130 and may be similar to the web services application 1120, website accessed by the computing device 1112, and/or vendor account, respectively.

The customer 1160 may use a local application and/or a web services application 1170 to conduct transactions with the service provider's network-based resources. These transactions may include, for example, browsing items, viewing items, ordering items, checking items, returning items, receiving notifications, viewing notifications, canceling notifications, and/or other transactions.

In some examples, the customer device 1162 may be configured similarly to the vendor device 1112 and may include at least one or more processing units (or processor devices) 1164 and at least one memory 1166. Similar to the processor device 1114, the processor device 1164 may be suitably implemented in hardware, computer-executable instructions, firmware, or a combination thereof. Similarly, memory 1166 may also be configured similarly to memory 1116 and may store program instructions that are loaded into and executed by processor device 1164, as well as data that is generated during the execution of these programs. For example, memory 1166 may include an operating system (O/S) 1168 and one or more application programs or services for implementing the features disclosed herein, including a web services application 1170.

As briefly described above, web service applications 1120 and 1170 may allow a vendor 1110 and a customer 1160, respectively, to interact with a service provider device 1130 to conduct transactions involving items. Service provider device 1130, which may be disposed in a server cluster or as a server farm, may host web service applications 1120 and 1170. These servers may be configured to host websites (or combinations of websites) viewable through

computing devices

1112 and 1162. Other server architectures may also be used to host web service applications 1120 and 1170. The web service applications 1120 and 1170 may be capable of processing requests from a number of vendors 1110 and customers 1160, respectively, and in response, provisioning various interfaces (such as, but not limited to, websites) that may be presented at the

computing devices

1112 and 1162. Web service applications 1120 and 1170 may interact with any type of website that supports interaction, including social networking websites, electronic retailers, information sites, blog sites, search engine sites, news and entertainment sites, and the like. As noted above, the described techniques may similarly be implemented outside of web service applications 1120 and 1170, such as using other applications running on

computing devices

1112 and 1162, respectively.

In some instances, service provider device 1130 may provide network-based resources such as, but not limited to: applications for purchase and/or download, websites, website hosting, client entities, data storage, data access, management, virtualization, etc. Service provider device 1130 may also operate to provide vendor 1110 and customer 1160 with website hosting, computer application development and/or implementation platforms, or combinations of the foregoing.

Service provider device 1130 may be any type of computing device, such as but not limited to: mobile phones, smart phones, personal Digital Assistants (PDAs), laptop computers, desktop computers, server computers, thin client devices, tablet PCs, and the like. The service provider device 1130 may also contain communication connections that allow the service provider device 1130 to communicate with stored databases, other computing devices or servers, vendor terminals, and/or other devices on the network 1180. Service provider device 1130 may also include input/output (I/O) devices and/or ports, such as for enabling connection to a keyboard, mouse, pen, voice input device, touch input device, display, speakers, printer, etc.

Additionally, in some embodiments, service provider device 1130 may be executed by one or more virtual machines implemented in a hosted computing environment. The managed computing environment may include one or more rapidly provisioned and released network-based resources. Such network-based resources may include computing, networking, and/or storage devices. The managed computing environment may also be referred to as a cloud computing environment. In some examples, service provider device 1130 may communicate with

computing devices

1112 and 1162 through network 1180 or through other network connections. Service provider device 1130 may include one or more servers, possibly arranged in a cluster, or as individual servers not associated with each other.

In one illustrative configuration, service provider device 1130 may include at least one or more processing units (or processor devices) 1132 and at least one memory 1134. Processor device 1132 may be suitably implemented in hardware, computer-executable instructions, firmware, or a combination thereof. The computer-executable instructions or firmware implementations of processor device 1132 may include computer-executable or machine-executable instructions written in any suitable programming language for performing the various functions described.

Memory 1134 may store program instructions that may be loaded and executed on processor device 1132, as well as data generated during the execution of such programs. Depending on the configuration and type of service provider device 1130, memory 1134 may be volatile (such as Random Access Memory (RAM)) and/or non-volatile (such as Read Only Memory (ROM), flash memory, etc.). Service provider device 1130 may also include additional removable and/or non-removable storage devices including, but not limited to, magnetic, optical, and/or tape storage devices. The disk drives and their associated computer-readable media may provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computing device. In some implementations, the memory 1134 may include a variety of different types of memory, such as Static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), or ROM.

Additionally, computer storage media described herein can include computer-readable communication media (such as computer-readable instructions, program modules, or other data transmitted within a data signal, such as a carrier wave, or other transmission). Such a transmission signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any combination thereof. However, as used herein, computer-readable media does not include computer-readable communication media.

Turning in more detail to the contents of memory 1134, the memory may include an operating system (O/S) 1136, code for the electronic marketplace 1138, and code for the notification manager 1140. The notification manager 1140 may be configured to provide notification functionality to the seller device 1112 and the customer device 1162. These functions may be based on interactions with delivery devices, active devices, passive devices, delivery management devices, and/or computing nodes of the local area network.

The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. However, it will be apparent that: various modifications and changes may be made thereto without departing from the broader spirit and scope of the disclosure as set forth in the claims.

Other variations are within the spirit of the present disclosure. Accordingly, while the disclosed technology is susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the disclosure to the specific form or forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the disclosure, as defined in the appended claims.

The use of the terms "a" and "an" and "the" and similar referents in the context of describing the disclosed embodiments (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms "comprising", "having", "including" and "containing" are to be construed as open-ended terms (i.e., meaning "including, but not limited to,") unless otherwise noted. The term "connected" should be construed as partially or fully inclusive, attached, or joined together, even if intervening elements are present. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., "such as") provided herein, is intended merely to better illuminate embodiments of the disclosure and does not pose a limitation on the scope of the disclosure unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the disclosure.

Unless specifically stated otherwise, disjunctive language such as included in the phrase "X, Y or at least one of Z" is understood in the context of what is commonly used to describe an item, etc. may be X, Y or Z or any combination thereof (e.g., X, Y and/or Z). Thus, such disjunctive language is generally not intended and should not imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to be present each.

Preferred embodiments of this disclosure are described herein, including the best mode known to the inventors for carrying out the disclosure. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. The inventors expect skilled artisans to employ such variations as appropriate, and the inventors intend for the disclosure to be practiced otherwise than as specifically described herein. Accordingly, this disclosure includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.

Examples of embodiments of the present disclosure may be described in view of the following clauses:

clause 1. A system, comprising: a computer system associated with an electronic marketplace, the computer system configured to provide notifications to a user device regarding delivery of items to a destination associated with the user device, the items purchased from the electronic marketplace; and an active tag configured to attach to a holder of the item for the delivery, the active tag storing a token associated with the delivery, the token configured to facilitate communication between the active tag and a node of a local area network associated with the destination, wherein: the computer system generates a first notification for the user device regarding loading of the item on a delivery vehicle, the first notification based at least in part on a first communication of the active tag with a delivery device associated with the delivery vehicle, and generates a second notification for the user device regarding unloading of the item at the destination, the second notification based at least in part on a second communication of the active tag with the node of the local area network, the second communication utilizing the token.

The system of claim 1, wherein the computer system is configured to provide the token to the active tag based at least in part on an order for the item at the electronic marketplace.

The system of claim 1, wherein the second notification regarding the offloading is further based at least in part on a third communication of the delivery device with the node of the local area network.

The system of claim 1, wherein the computer system generates a third notification for the user device regarding movement of the item at the destination, the third notification based at least in part on a change in proximity between the active tag and the node.

Article 5. An apparatus associated with delivering an item to or from a location associated with a local area network, the apparatus comprising: an interface configured to attach the device to at least one of the item or a holder of the item; a processor; and a memory comprising computer readable instructions that, when executed with the processor, cause the device to: receiving a token associated with the local area network, the token received from a computer system based at least in part on an order for the item processed at the computer system;

storing the token; establishing communication with a node of the local area network based at least in part on the token; and cause an indication of an event associated with the delivery based at least in part on the communication with the node.

The apparatus of claim 5, wherein the event comprises unloading the item at the location, wherein the item is ordered from an electronic marketplace by a user device, wherein the computer system is associated with the electronic marketplace, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to provide the indication of the unloading to the computer system, and wherein the indication causes the computer system to provide a notification regarding the unloading to the user device.

The apparatus of claim 5, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to provide the indication of the event to a user equipment through the node of the local area network.

The apparatus of claim 5, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to: establishing other communications with a delivery device associated with a delivery vehicle, the other communications established prior to establishing the communication with the node; causing a notification regarding the start of delivery to be transmitted to a user device based, at least in part, on the other communication with the delivery device.

The apparatus of claim 8, wherein the item is purchased from an electronic marketplace, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to: receiving instructions associated with the delivery from a computer system associated with the electronic marketplace; and providing at least a portion of the instruction to the delivery device based at least in part on the other communication with the delivery device, wherein the indication of the event is based at least in part on the instruction.

The apparatus of claim 8, wherein the event comprises unloading the item at the location, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to: receiving instructions associated with the delivery from the node of the local area network; and authorize the offload to the delivery device based at least in part on the instruction, wherein the instruction is based on at least one of: a history of past deliveries to the location or delivery patterns associated with other locations within a predetermined distance from the location.

The apparatus of claim 5, wherein the apparatus comprises an active Radio Frequency Identification (RFID) tag configured for wireless communication with the nodes of the local area network, and wherein the token is configured for expiration based at least in part on one or more of: a pick up of the item or a predefined period of time from the time of unloading the item.

The apparatus of claim 12, further comprising a positioning device configured to determine a geographic location of the apparatus, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to provide the geographic location to a user equipment through the node of the local area network.

The apparatus of claim 5, further comprising a sensor configured to sense an environmental condition associated with the location, and wherein the computer readable instructions, when executed with the processor, further cause the apparatus to provide a recommendation to the node of the local area network regarding pickup of the item, the recommendation causing the node to provide the recommendation to a user device associated with the local area network.

Clause 14. A computer-implemented method, comprising: providing, by a computer system, a token associated with delivery of an item to or from a location to an active device configured to attach to at least one of the item or a holder of the item for the delivery; receiving, by the computer system, an identifier associated with the active device from a delivery device associated with a delivery vehicle based at least in part on a proximity of the active device and the delivery device; determining, by the computer system, a start of the delivery based at least in part on receiving the identifier; providing, by the computer system, information regarding the beginning of the delivery to a user device associated with the delivery; receiving, by the computer system, an indication from a node of a local area network associated with the location of an event associated with the delivery at the location, the indication based at least in part on communication between the active device and the node with the token; and providing, by the computer system, information about the event to the user device associated with the delivery.

The computer-implemented method of claim 14, wherein the event comprises an uninstall, and the method further comprises: receiving a second indication of the unloading from the delivery device; and determining completion of the offloading based at least in part on the indication from the node of the local area network and the second indication from the delivery device.

The computer-implemented method of claim 14, wherein the event comprises at least one of: offload, not offload, move, not move, or pick up, and the method further comprises determining completion of the event based at least in part on a set of rules associated with communication between the active device, the node of the local area network, and the delivery device.

The computer-implemented method of claim 14, further comprising:

receiving an image associated with an event; determining completion of the event based at least in part on the image; and providing, by the computer system, information regarding the completion of the event including the image to the user device associated with the delivery.

The computer-implemented method of claim 14, further comprising: determining movement of the item based at least in part on a change in proximity between the active device and the node of the local area network, the proximity based at least in part on the communication between the active device and the node of the local area network.

The computer-implemented method of claim 14, further comprising determining the pick up of the item based at least in part on one or more of: user input received by the user device or proximity between the user device and the active device.

The computer-implemented method of claim 14, further comprising: providing, by the computer system, instructions to the node of the local area network or other nodes of the local area network based at least in part on the event, wherein the instructions cause the node or the other nodes to initiate an action of an automation device associated with the location, wherein the action is based at least in part on the item.

Clause 1. A system, comprising: a computer system associated with an electronic marketplace, the computer system configured to provide notifications to a user device regarding delivery of items to a destination associated with the user device, the items purchased from the electronic marketplace; a passive tag configured to attach to a holder of the item for the delivery, the passive tag encoding an identifier associated with the item; and a delivery management device located at the destination and configured to communicate with the computer system over a data network, wherein: the computer system generates a first notification for the user device regarding loading of the item on a delivery vehicle, the first notification based at least in part on a first communication of the passive tag with a delivery device associated with the delivery vehicle, the delivery management device generates a first indication for the computer system regarding arrival of the item at the destination, the first indication based at least in part on a second communication of the passive tag with the delivery management device, the first indication causing a second notification to the user device regarding arrival of the item at the destination, and the delivery management device generates a second indication for the computer system regarding movement of the item at the destination, the second indication causing a third notification to the user device regarding the movement of the item at the destination.

The system of claim 1, wherein the computer system receives instructions from the user device regarding the delivery of the item, wherein the computer system provides a first portion of the instructions to the delivery device and a second portion of the instructions to the delivery management device, and wherein the delivery management device authorizes the delivery of the item to the delivery device based at least in part on the second portion of the instructions.

The system of claim 1, wherein the delivery management device generates the first indication of the arrival of the item based at least in part on a third communication between the delivery management device and the delivery device.

The system of claim 1, wherein the computer system: receiving location information of at least one of the delivery vehicle or the delivery device, providing the user device access to the location information, and providing the user device access to tracking of the item between arrival of the item at the destination and movement of the item at the destination based at least in part on the second communication of the passive tag with the delivery management device.

Clause 5. A device located at a location associated with delivery of an item, the device comprising: a processor; and a memory comprising computer readable instructions that, when executed with the processor, cause the device to: receiving an identifier associated with a passive device based at least in part on a proximity of the passive device and the apparatus, the passive device associated with the item; cause information regarding an event associated with delivering the item to or from the location to be provided to a delivery device associated with a delivery vehicle, the information based at least in part on the identifier; determining completion of the event at the location based at least in part on the proximity of the passive device and the apparatus; causing information regarding the completion of the event to be provided to a user device associated with the location; determining other events associated with the delivery of the item based at least in part on a change in the proximity of the passive device and the apparatus; and causing information about the other events to be provided to the user equipment.

The apparatus of claim 5, wherein the event comprises an uninstallation of the item, wherein the other event comprises a movement of the item at the location, wherein the item is purchased from an electronic marketplace, wherein causing information regarding the event to be provided to the delivery device comprises providing an indication of the uninstallation to a computer system associated with the electronic marketplace, and wherein the computer system is configured to provide the information regarding the uninstallation to the delivery device based at least in part on the indication.

The apparatus of claim 5, wherein causing the information regarding the event to be provided to the delivery device comprises transmitting the information regarding the event to the delivery device, and wherein the computer readable instructions, when executed with the processor, further cause the apparatus to: analyzing a history of deliveries to or from the location;

generating delivery instructions based at least in part on the history; and providing the delivery instructions to the delivery device.

The apparatus of claim 5, further comprising a positioning device configured to determine a geographic location of the apparatus, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to transmit the geographic location to a computer system, and wherein the computer system is configured to provide delivery instructions to the delivery device based at least in part on the geographic location.

The apparatus of claim 5, wherein the event comprises an uninstallation of the item, wherein the other event comprises a movement of the item, wherein the apparatus further comprises one or more of: a weight sensor or a pressure sensor, and wherein one or more of the proximity of the passive device, the unloading of the item, or the moving of the item is based at least in part on the one or more of the weight sensor or the pressure sensor.

The apparatus of claim 5, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to: accessing an image associated with the event; analyzing the image to determine the completion of the event; and generating a notification regarding the completion of the event, the notification including the image.

The apparatus of claim 5, wherein the other event comprises movement of the item, wherein the passive device comprises a passive Radio Frequency Identification (RFID) tag, wherein the apparatus comprises a Radio Frequency (RF) transceiver, wherein receiving the identifier comprises receiving a response from the passive RFID tag based at least in part on an RF signal transmitted from the RF transceiver, and wherein detecting the movement comprises detecting that no response was received from the passive RFID tag based at least in part on another RF signal transmitted from the RF transceiver.

The apparatus of claim 11, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to: determining that the delivery device is located within a geofence of the location; and transmitting the RF signal from an RF transceiver based at least in part on the delivery device being located within the geofence.

The apparatus of claim 11, wherein the event comprises an uninstall of the item, wherein determining the completion of the event comprises: transmitting RF signals from the RF transceiver at a first rate; receiving the response from the passive RFID tag based at least in part on at least one of the RF signals transmitted at the first rate; transmitting RF signals from the RF transceiver at a second rate based at least in part on the response, the second rate being higher than the first rate; receiving a plurality of responses from the passive RFID tag based at least in part on the RF signal transmitted at the second rate, the plurality of responses received during a period of time; and determining that the period of time exceeds a threshold.

The apparatus of claim 5, wherein the event comprises an uninstall, wherein the computer readable instructions, when executed with the processor, further cause the apparatus to: providing a recommendation to the user device regarding pickup of the item, the recommendation provided based at least in part on the completion of the event and an environmental condition detected by a sensor associated with the apparatus; or providing instructions to an automated device located at the location over a local area network of the location based at least in part on the completion of the event, wherein the instructions are based at least in part on the item.

Clause 15. A computer-implemented method associated with delivering items to or from a location, comprising: receiving, by a computer system, an identifier associated with a passive device from a delivery device associated with a delivery vehicle based at least in part on a proximity of the passive device to the delivery device, the passive device associated with the item; determining, by the computer system, a start of the delivery based at least in part on receiving the identifier; providing, by the computer system, information regarding the beginning of the delivery to a user device associated with the delivery; receiving, by the computer system, a first indication of an event associated with the delivery at the location from the delivery device;

receiving, by the computer system, a second indication of the event from a delivery management device located at the location, the second indication based at least in part on a proximity of the passive device and the delivery management device; determining, by the computer system, a completion of the event based at least in part on the first indication and the second indication; and providing, by the computer system, information regarding the completion of the event to the user device associated with the delivery.

The computer-implemented method of claim 15, further comprising determining pickup of the item at the location based at least in part on a proximity of the user device and the delivery management device and based at least in part on a third indication of a change in the proximity between the passive device from the delivery management device and the delivery management device.

The computer-implemented method of claim 15, wherein the event comprises an uninstallation of the item, and the method further comprises: providing, by the computing system, a delivery instruction to the delivery management device, wherein the delivery instruction causes the delivery management device to authorize offloading the item at the location.

The computer-implemented method of claim 15, wherein the event comprises an uninstallation of the item, and the method further comprises: providing, by the computing system, a delivery instruction to the delivery device, wherein the delivery instruction includes location information of the delivery management device.

The computer-implemented method of claim 15, wherein the event comprises an uninstallation of the item, wherein receiving the second indication of the event is based at least in part on detecting the uninstallation through the delivery management device, the method further comprising: receiving a third indication from the delivery management device regarding movement of the item, wherein the third indication is received based at least in part on detecting the movement by the delivery management device, and wherein the detection of the unloading and the detection of the movement are based at least in part on a weight sensor or a pressure sensor of the delivery management device.

The computer-implemented method of claim 15, wherein the first indication of the event is based at least in part on termination of a communication link between the delivery management device and the delivery device, and the second indication of the event is continued for a period of time exceeding a threshold based at least in part on the proximity of the passive device and the delivery management device.

Claims

1. A system, comprising:

a computer system associated with an electronic marketplace, the computer system configured to provide notifications to user devices regarding delivery of items to destinations associated with the user devices, the items purchased from the electronic marketplace; and

an active tag configured to attach to a holder of the item for the delivery, the active tag storing a token associated with the delivery, the token configured to facilitate communication between the active tag and a node of a local area network associated with the destination, wherein:

the computer system generates a first notification for the user device regarding loading of the item on a delivery vehicle based at least in part on a first communication of the active tag with a delivery device associated with the delivery vehicle, and

the computer system generates a second notification for the user device regarding offloading of the item at the destination, the second notification based at least in part on a second communication of the active tag with the node of the local area network established based at least in part on the transmission of the token to the node by the active tag and an authentication of the active tag by the node, the authentication utilizing the token, and determining that the second communication is maintained for a predetermined period of time.

2. The system of claim 1, wherein the computer system is configured to provide the token to the active tag based at least in part on an order for the item at the electronic marketplace.

3. The system of claim 1, wherein the second notification of the offloading is further based at least in part on a third communication of the delivery device with the node of the local area network.

4. The system of claim 1, wherein the computer system generates a third notification for the user device regarding movement of the item at the destination, the third notification based at least in part on a change in proximity between the active tag and the node.

5. A computer-implemented method, comprising:

providing, by a computer system, a token associated with delivery of an item to or from a location to an active device configured to attach to at least one of the item or a holder of the item for the delivery;

receiving, by the computer system, an identifier associated with the active device from a delivery device associated with a delivery vehicle based at least in part on a proximity of the active device and the delivery device;

determining, by the computer system, a start of the delivery based at least in part on receiving the identifier;

providing, by the computer system, information regarding the beginning of the delivery to a user device associated with the delivery;

receiving, by the computer system, an indication from a node of a local area network associated with the location of an event associated with the delivery at the location, the indication based at least in part on utilizing the token for communication between the active device and the node established based at least in part on transmitting the token to the node by the active device and an authentication of the active device by the node, the authentication utilizing the token, and determining that the communication is maintained for a predetermined period of time; and

providing, by the computer system, information about the event to the user device associated with the delivery.

6. The computer-implemented method of claim 5, wherein the event comprises an uninstall, and the method further comprises:

receiving a second indication of the unloading from the delivery device; and

determining completion of the offloading based, at least in part, on the indication from the node of the local area network and the second indication from the delivery device.

7. The computer-implemented method of claim 5, wherein the event comprises at least one of: offload, not offload, move, not move, or pick up, and the method further comprises determining completion of the event based at least in part on a set of rules associated with communication between the active device, the node of the local area network, and the delivery device.

8. The computer-implemented method of claim 5, further comprising:

receiving an image associated with an event;

determining completion of the event based at least in part on the image; and

providing, by the computer system, information about the completion of the event including the image to the user device associated with the delivery.

9. The computer-implemented method of claim 5, further comprising determining pickup of the item based at least in part on one or more of: user input received by the user device or proximity between the user device and the active device.

10. The computer-implemented method of claim 5, further comprising:

providing, by the computer system, instructions to the node of the local area network or other nodes of the local area network based at least in part on the event, wherein the instructions cause the node or the other nodes to initiate an action of an automation device associated with the location, wherein the action is based at least in part on the item.

11. A computer-implemented method associated with delivering items to or from a location, comprising:

receiving, by a computer system, an identifier associated with a passive device from a delivery device associated with a delivery vehicle based at least in part on a proximity of the passive device and the delivery device, the passive device associated with the item;

receiving, by the computer system, a first indication of an event associated with the delivery at the location from the delivery device;

receiving, by the computer system, a second indication regarding the event from a delivery management device located at the location, the second indication sent from the delivery management device based at least in part on determining, by the delivery management device, that communication between the delivery management device and the delivery device was established and maintained for a predetermined period of time while proximity of the passive device and the delivery management device was detected;

determining, by the computer system, a completion of the event based at least in part on the first indication and the second indication; and

providing, by the computer system, information regarding the completion of the event to the user device associated with the delivery.

12. The computer-implemented method of claim 11, further comprising determining pickup of the item at the location based at least in part on a proximity of the user device and the delivery management device and based at least in part on a third indication of a change in the proximity between the passive device from the delivery management device and the delivery management device.

13. The computer-implemented method of claim 11, wherein the event comprises an uninstallation of the item, and the method further comprises: providing, by the computing system, a delivery instruction to the delivery management device, wherein the delivery instruction causes the delivery management device to authorize unloading the item at the location.

14. The computer-implemented method of claim 11, wherein the event comprises an uninstallation of the item, and the method further comprises: providing, by the computing system, a delivery instruction to the delivery device, wherein the delivery instruction includes location information of the delivery management device.

15. The computer-implemented method of claim 11, wherein the event comprises an uninstallation of the item, wherein the second indication is received regarding the event based at least in part on detecting the uninstallation through the delivery management device, the method further comprising: receiving a third indication from the delivery management device regarding movement of the item, wherein the third indication is received based at least in part on detecting the movement by the delivery management device, and wherein the detection of the unloading and the detection of the movement are based at least in part on a weight sensor or a pressure sensor of the delivery management device.