EP3357014A1 - Managing notifications of a delivery method based on an active device - Google Patents
Managing notifications of a delivery method based on an active deviceInfo
- Publication number
- EP3357014A1 EP3357014A1 EP16784628.6A EP16784628A EP3357014A1 EP 3357014 A1 EP3357014 A1 EP 3357014A1 EP 16784628 A EP16784628 A EP 16784628A EP 3357014 A1 EP3357014 A1 EP 3357014A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- delivery
- item
- computer system
- drop
- active
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
Definitions
- FIG. 1 illustrates an example computing environment where notifications may be transmitted, according to a particular embodiment
- FIG. 3 illustrates example notifications available from a computing environment utilizing a destination delivery management device, according to particular embodiments
- FIG. 6 illustrates an example flow for providing notifications, according to a particular embodiment
- FIG. 7 illustrates an example flow for providing notifications in a computing environment utilizing a destination delivery management device, according to a particular embodiment
- FIG. 8 illustrates another example flow for providing notifications in a computing environment utilizing a destination delivery management device, according to a particular embodiment
- the notifications may provide meaningful information about the item, rather than outdated or stale information.
- the triggers only the necessary or desired number of notifications may be provided to the user device, rather than a flood of unnecessary or unwanted notifications. Accordingly, the user experience may be enhanced while also the usage of computing resources within the computing environment and the usage of the network bandwidth may be reduced.
- the item may be associated with a notification device, such as a label capable of data exchange.
- the association may include a direct physical attachment between the item and the notification device or an indirect attachment through an intermediary holder.
- the notification device may be configured to connect to the network through various computing devices. Communications with the computing devices may trigger the notifications in real-time.
- a user may operate a user device to order, such as for rent or purchase, an item.
- the item may be delivered from a source to a destination via a delivery vehicle.
- a holder such as a package, may retain the item for the delivery.
- a passive radio frequency identification (RFID) tag may be attached to the package and may uniquely identify the order.
- RFID radio frequency identification
- a handheld device When loading the item onto the delivery vehicle, a handheld device may read the RFID tag.
- the handheld device may be connected over a network to a computer system of the electronic marketplace. The reading of the RFID tag may identify the item causing the handheld device to indicate to the computer system that the loading has occurred.
- the computer system may send a notification about a start of the delivery to the user device.
- embodiments may similarly apply to a delivery from the destination 150 to the source 1 12. This may correspond to, for example, a return or a sale of the item 130 for delivery to the source 1 12.
- the user device 120 may include any suitable computing device capable of communicating with the computer system 110 over the network 140.
- the user device 120 may include a number of general purpose personal computers, such as desktop or laptop computers running a standard operating system, as well as cellular, wireless, and handheld devices running mobile software and capable of supporting a number of networking and messaging protocols.
- the network 140 may include any one or a combination of many different types of networks.
- the network 140 may include any of wireless networks, cable networks, cellular networks, radio networks, the Internet, and other private and/or public networks.
- the item 130 may be available from the electronic marketplace and may include a tangible item (e.g., a physical item such as a camera or a multimedia file) or an intangible item (e.g., a service to be provided at the destination 150). As part of the delivery, the item 130 may be held in a holder, such as in a suitable package. Suitable packages exemplified by item 130 may include a box, a bin, a tote, a bag, or another receptacle of proper structure and material.
- the delivery vehicle 160 may represent a vehicle for delivering the item 130 from the source 112 to the destination 150.
- the delivery vehicle 160 may be manually, remotely, semi-autonomously, or autonomously operated and may include a ground, air, and/or water- based vehicle.
- the delivery vehicle 160 may connect to the computer system 110, the user device 120, and/or the destination 150 (e.g., a computing node at the destination 150) over the network 140.
- the user device 120 may receive the notification(s) 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 over the network 140 (or some other network).
- the notifications 122 may provide information about the item 130, such as about the order and/or the delivery thereof.
- a notification may include information about a location of the item, a time associated with the location of the item, a state of the item, the order, and/or delivery. Some of the notifications 122 may be triggered by a change of the state of the item 130, the order, and/or the delivery.
- a third notification may describe that the item 130 may have been moved since the drop-off
- a fourth notification may describe an environment condition at the destination 150 and may recommend a corresponding action related to the delivery (e.g., to move the item 130 because of rain).
- a fifth notification may indicate that the item 130 may have been picked up.
- a tag may be attached to the item 130 and/or to the holder of the item 130.
- a proximity of the tag with the delivery device 162 and/or the destination 150 may trigger the notifications.
- the proximity may be based on wired, wireless, radio frequency (RF), optical, and/or other type of communications between the tag, the delivery device 162, and/or the destination 150.
- RF radio frequency
- FIG. 2 illustrates an example of a tag as a passive device, where the cost, processing capabilities, and power consumption of the passive device may be reduced. Instead, processing related to the notifications may be pushed to the delivery device 162 and/or the computing node of the destination 150.
- FIG. 4 illustrates an example of an active device as an implementation of the tag. In this example, some of the cost, processing, and/or power may be pushed to the active device.
- a passive device 210 may be attached, via adhesion or some other attachment means, to a holder 212 of an item (or to the item itself).
- the passive device 210 may represent a printable passive RFID tag that may encode information, such as a unique identifier(s), about the item, the delivery (e.g., delivery location and/or delivery instructions), and/or an order of the item.
- Other types of passive devices may be used. For example, one or two dimensional barcodes may be used.
- the delivery device 230 may interact with the passive device 210 to receive information therefrom. The interaction may depend on the
- the delivery device 230 may radiate a passive RFID tag with RF energy and receive an RF signal in response from the passive RFID tag.
- the delivery device 230 may send the information included in the RF signal to the computer system 220 that may, in turn, send a notification about the start of the delivery to the user device 260.
- the delivery device 230 may send the notification to the user device 260
- various types of notifications may be generated based on the interactions of the delivery management device 244 with the passive device 210, the holder 212, and/or the delivery device 230.
- the interactions may be triggered by a request from the delivery device 230 to the delivery management device 244.
- the interactions may be triggered by the computer system 220.
- the computer system 220 may determine that the delivery device 230 may be within a geographical fence of the destination 240. Accordingly, the computer system 220 may instruct the delivery
- the delivery management device 244 to ping the passive device 210 (e.g., radiate a passive RFID tag with RF energy) and/or establish a communication link with the delivery device 230.
- the computer system 220 may estimate a time window within which the delivery device 230 may arrive to the destination 240 and may accordingly instruct the delivery management device 244 in order to initiate the interaction.
- the delivery management device 244 may trigger the interactions independently of the computer system. For instance, the delivery management device 244 may repeatedly generate a ping. Upon a response to a ping from the passive device 210, the delivery management device 244 may establish a communication link with the delivery device 230.
- notifications may be generated.
- the notifications may be generated by the delivery management device 244 and/or the delivery device 230.
- the notifications may be generated by the computer system 220 in response to the interactions. Once generated, the notifications may be provided to the user device 260.
- the computer system 220 may send the notifications to the user device 260.
- the delivery management device 244 and/or the delivery device 230 may send the notifications to the user device 260
- the notifications may include an authorization of a drop-off of the item (or the holder 212), information about the drop-off, a lack of the drop-off, and/or information about a virtual signature related to the drop-off.
- the delivery management device 244 may access information from the passive device 210 (e.g., by reading the passive RFID tag).
- the delivery management device 244 may receive the information over a communication link with the delivery device 230. The information may identify the order, the item, the passive device 210, the delivery device 230, and/or the delivery management device 244.
- the delivery instructions may provide information about the delivery of the item at the destination 240.
- the computer system 220 and/or the user device 260 may provide the delivery instructions to the delivery management device 244 and/or the delivery device 230.
- Different types of delivery instructions may exist.
- the delivery instructions may be defined at a user account level.
- the user device 260 may be associated with a user account.
- the delivery instructions may be defined.
- the delivery instructions would apply to all deliveries unless indicated otherwise.
- the delivery instructions may be defined at an item level.
- the user may specify that for any time the item is ordered, the delivery instructions would be automatically applied.
- the delivery instructions may be defined at an order level. For instance, each time an order is made, specific delivery instructions may be defined for that order.
- the delivery management device 244 and/or the computer system 220 may update the delivery instructions over time.
- the update may be based on an analysis of the history of deliveries.
- the analysis may include an optimization over one or more delivery -related parameters. For instance, the analysis may consider the history to determine a time frame and/or location at the destination 240 for dropping off the item.
- the update to the delivery instructions may also or alternatively be based on an analysis of a history of deliveries, a history of delivery instructions, or delivery patterns within an area that may include the delivery location.
- the area may correspond to locations within a predetermined distance (e.g., relative to a threshold, such as a block, a hundred yards, etc.) from the delivery location.
- a threshold such as a block, a hundred yards, etc.
- the delivery instructions may necessitate a signature of a person at the delivery location, provide information about a different, more secure location for the dropoff, and/or reject the delivery.
- the delivery instructions may default to delivering the item to that location if it is not possible or not safe to complete the delivery with respect to the delivery location.
- the delivery management device 244 and/or the computer system 220 may update the delivery instructions based on parameters of a current delivery. For example, if the current delivery was not successful (e.g., the item was not dropped-off or the item was stolen), the delivery instructions may be automatically updated to reschedule another delivery.
- the update may be based on the history of deliveries as described herein above. In another example, the update may be based on settings or preferences of the user account.
- the detection of a drop-off may use the proximity of the delivery management device 244 to the passive device 210 and/or the delivery device 230.
- the delivery management device 244 may increase the RF ping rate.
- a drop-off may have occurred.
- the weight sensor and/or the pressure sensor may sense the holder 212, which may indicate that a drop-off may have occurred.
- an input indicating a drop-off may be received at a user interface of the delivery management device 244. This input may be provided by an operator of the delivery device 230.
- a user interface (or some other interface) of the delivery device 230 may receive an indication of the drop-off (from the operator or from the delivery vehicle) and may send this indication to the delivery management device 244.
- the delivery management device 244 may detect the drop-off
- the detection of a lack of a drop-off may also use the proximity of the delivery management device 244 to the passive device 210 and/or the delivery device 230.
- the delivery management device 244 may send an RF ping. If no response from the passive device 210 is received, the delivery management device 244 may detect that no dropoff has occurred. Accordingly, a notification about the lack of drop-off may be generated.
- the delivery management device 244 may perform an automatic action. Such an action may be defined in the delivery instructions. For example, the delivery management device 244 may re-order the item with an expedited ship method, reschedule a delivery, or request a refund.
- the virtual handoff may be detected based on interactions between the delivery management device 244 and the delivery device 230.
- the delivery device 230 may request a virtual signature from the delivery management device 244.
- the delivery management device 244 may respond with the virtual signature.
- the delivery management device 244 may determine that the virtual handoff may have occurred.
- notifications about movement, lack of movement, relevant environmental conditions, and/or a pick-up of the item (or the holder 212) may be provided.
- the delivery management device 244 may generate these notifications.
- the delivery management device 244 may provide relevant information to the computer system 220 to generate the notifications.
- the user device 260 may receive the notifications from the computer system 220 and/or from the delivery management device 244 independently of the computer system 220.
- RF ranging may be used.
- the delivery management device 244 may estimate a proximity (e.g., a distance range) to the passive device 210 based on a response to an RF ping. If that proximity changes between two RF pings (e.g., based on signal strength of the RF signal response from the passive device 210), the movement may be detected. In addition, if an RF response is no longer received, the delivery management device 244 may detect that the item may have departed from the geographical fence of the destination 240 (unless a pickup may have occurred).
- the weight and/or pressure sensors may be used to detect movement of the item. For instance, any change in the sensed data (e.g., pressure no longer sensed) may indicate that the item may have been moved.
- various techniques may be used to detect an environmental condition that may impact the item.
- environmental sensors e.g., rain or moisture sensors, humidity sensors, temperature sensors, light sensors, optical sensors, etc.
- the delivery management device 244 may access environmental information about the location of the delivery management device 244 from a web site over the network 250 to determine the environmental condition. If this condition is detected prior to a pick-up, the delivery management device 244 may access (locally or remotely from the computer system 220) a recommendation related to the item delivery to be provided to the user device 260 (e.g., a recommendation for a pick-up within a time frame, to move the item to a covered area, etc.).
- An image may be analyzed using facial recognition techniques to detect a success or a failure of a delivery event.
- the delivery management device 244 may have access to an image of the user from, for example, the user account. Upon pick-up, the delivery management device 244 may analyze the corresponding image, detect a face of the individual who picked up the item, and compare the detected face to the known image of the user. If there is a match, the delivery management device 244 may determine that the pick-up may have been successful; otherwise, failure may be determined. A notification about the success or the failure may be provided to the user device 260.
- the passive device 210 may be used in conjunction with the delivery management device 244 and/or the delivery device 230 to facilitate various notifications to the user device 260. These notifications may span the entire delivery process, such as from the start of the delivery to the pick-up of the item at the destination 240, and may include information about different delivery events.
- the delivery management device 244 may interface with other nodes of the local area network 242 of the destination 240. These nodes may include various automation devices, e.g., connected or smart devices or appliances, installed at the destination 240. For example, the nodes may include a smart switch for turning on and off a light, a smart switch for turning on and off an oven, or other automation device.
- the delivery management device 244 may indicate the delivery event to the one or more of the automation devices over the local area network 242.
- an automation device may initiate an action at the destination 240. The action may be predefined by the user.
- the delivery management device 244 may identify the item (e.g., the frozen entree) based on the order and access instructions for preparing the item (e.g., cooking temperature) from a remote computing resource (e.g., from the computer system 220).
- the delivery management device 244 may inform a smart switch about the drop-off and some of the instructions for preparing the item (e.g., the cooking temperature).
- the switch may turn on an oven and set the bake temperature according to the information received from the delivery management device 244.
- the delivery process may include multiple phases. At each phase, interactions between different components may be possible, thereby resulting in different notifications.
- FIG. 3 provides an illustrative table summarizing the phases, the interacting components, and the resulting notifications. Some of the interactions or information thereof may be tracked by a computer system and used to generate the notifications by the computer system and/or by one or more of the interacting components. As such, the computer system may be involved in the various phases but is not shown in FIG. 3 in the interest of clarity of explanation.
- an order for an item may have been received and may be processed to prepare for the delivery.
- the computer system may provide instructions for including a passive device with the order or item.
- the interacting components 320 may include the passive device.
- the end user notifications 330 and the delivery device notification 340 may describe that the order may be under processing.
- the delivery may have started but a drop-off may not have occurred yet.
- the item may have been loaded onto a delivery vehicle and the delivery vehicle may be in-route to a destination.
- the interacting components 320 may include the passive device and the delivery device.
- the end user notifications 330 may indicate a start of the delivery and provide the location of the item while in-route.
- the delivery device notifications 340 may include delivery instructions.
- the delivery device and the passive device may have arrived to the destination. Resulting interactions with a delivery management device may have resulted in a drop-off.
- the interacting components 320 may include the passive device, the delivery device, and the delivery management device.
- the end user notifications 330 may indicate a completion and a time of drop-off
- the end user notifications 330 may also describe a location of the item (e.g., the drop-off location) and any environmental conditions (including relevant recommendations).
- the delivery device notifications 340 may include delivery instructions, such as the location of the delivery management device and any authorization therefrom for the drop-off
- the delivery device notifications 340 may also include information about a virtual handoff.
- the delivery device may have departed the destination. However, additional interactions may occur between the passive device, the delivery management device, and/or the user device until a pick-up may have been detected.
- the interacting components 320 may include the passive device, the delivery management device, and the user device.
- the end user notifications 330 may indicate a movement, a lack of movement (e.g., based on an elapsed time period), and/or a pick-up of the item.
- the end user notifications 330 may also describe a location of the item (e.g., the drop-off location) and any environmental conditions (including relevant recommendations).
- the delivery device notifications 340 may similarly provide information about the movement, pick-up, and/or environmental conditions. Interactions and notifications with other devices may also exist.
- the delivery management device may inform an automated device located at the destination of the drop-off, movement, and/or pick-up of the item.
- FIG. 4 illustrates another embodiment for providing notifications.
- an active device may be used instead of a passive device. Being active may reflect an implementation where the device may be self-powered and capable of performing various operations based on a local processor and memory.
- an active device may represent a computing device with a suitable form factor for attachment to a holder of the item and for usage in the delivery of the item. By using an active device, much of the functionalities of a delivery management device may be pushed to the active device. Depending on the implementation of the active device, the delivery management device may not be even needed.
- 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 about the item, the order, and/or the delivery may be provided to the user device 410. As part of the delivery, a holder 450 may hold the item. An active device 452 may be attached to the holder. The active device 452 may interact with a delivery device 460 and a local area network 442 (or a computing node of such network). The interactions may result in the notifications to the user device 410.
- the active device 452 may include a processor, memory, a wireless or wired interface, and a power source to facilitate the notifications.
- the active device 452 may include an active 802.1 1 RFID tag.
- Other configurations of the active device 452 may be used.
- the active device 452 may include additional hardware and/or software components, such as a GPS receiver, various sensors, and/or a delivery management module.
- the active device 452 may include an interface for attaching to the holder 450, such as an interface that may use adhesive surfaces, magnets, hook and loop fasteners, and/or other attachment means.
- 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.
- a token may represent a secret that may be shared between computing devices to facilitate communications between the computing devices.
- the token may be revocable to facilitate the management of the communications. For example, the token may expire after a period of time or after a number of usages (e.g., one usage). As such, once the delivery may be complete, the token may no longer be usable.
- the tokens 444 and 454 may be generated and distributed upon an order of an item.
- the token 462 may be similarly generated and distributed or may be a predefined token independently of the order.
- the tokens may be used to determine proximities between the different components. Notifications, including ones about delivery events, may be generated based on the proximities.
- delivery instructions may be provided from the computer system 420 and/or the user device 410 to the active device 452, the delivery device 460, and/or a computing node of the local area network 442 over the network 430.
- the delivery instructions may be similar to the ones described in connection with FIG. 2.
- proximities 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 a drop-off, provide delivery instructions, detect a drop-off, detect a lack of a dropoff, and/or complete a virtual handoff The proximities may be based on interactions between the local area network 442 (or a computing node thereof), the active device 452, and/or the delivery device 460. These interactions may be facilitated through communications that may use the tokens 444, 454, and 462.
- information about the event may be provided from the local area network 442 (or the computing node thereof), the active device 452, and/or the delivery device 460 to the computing system 420.
- a corresponding notification may also be sent to the user device 410 by the computer system 420 or independently of the computer system 420 (e.g., by the local area network 442 (or the computing node thereof), the active device 452, and/or the delivery device 460).
- the active device 452 and the local area network 442 may establish a communication link based on the tokens 454 and 444.
- the delivery device 460 and/or the local area network 442 may establish a communication link based on the tokens 462 and 444.
- 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 the tokens 454 and 462.
- the active device 452 may determine whether a drop-off may occur based on pre-stored delivery instructions or any other instructions received over the communication link (e.g., whether the correct item is in the delivery, the time of the delivery, any special drop-off instructions, etc.). If so, the active device 452 may authorize the drop-off for the delivery device 460 and provide relevant delivery instructions. Otherwise, the drop-off may be rejected.
- the detection of a drop-off may use various proximity or interaction-based rules.
- the drop-off may be determined.
- a user interface (or some other interface) of the delivery device 460 may receive an indication of the drop-off (from the operator or from the delivery vehicle) and may send this indication to the local area network 442 (or the computing node thereof) and/or the active device 452.
- the detection of a lack of a drop-off may also use the various proximities.
- the local area network 442 upon a proximity of the local area network 442 (or the computing node thereof) and the delivery device 460 but a lack of proximity between the local area network 442 (or the computing node thereof) and the active device 452 , the local area network 442 (or the computing node thereof) may detect that no drop-off has occurred. Accordingly, a notification about the lack of drop-off may be generated.
- the local area network 442 (or the computing node thereof) may perform an automatic action. Such an action may be defined in the delivery instructions. For example, the local area network 442 (or the computing node thereof) may re-order the item with an expedited ship method, reschedule a delivery, or request a refund.
- the delivery device 460, the active device 452, and/or the local area network 442 may determine that the virtual handoff may have occurred.
- notifications about movement, lack of movement e.g., based on an elapsed time period as described in connection with FIG. 2
- relevant environmental conditions e.g., based on an elapsed time period as described in connection with FIG. 2
- relevant environmental conditions e.g., relevant environmental conditions, and/or a pick-up of the item
- information about the event may be provided from the local area network 442 (or the computing node thereof) and/or the active device 452 to the computing system 420.
- the active device 452 and/or the local area network 442 may detect that the item may have departed from the geographical fence of the destination 440 (unless a pickup may have occurred).
- the movement may be determined on GPS location of the active device 452. For instance, if the active device 452 includes a GPS receiver and the corresponding GPS data indicates a location change, the movement may be detected.
- the active device 452 may include one or more environmental sensors (e.g., rain sensors). These sensors may detect the environmental condition.
- the local area network 442 (or the computing node thereof) or the computer system 420 may access environmental information about the destination 440 from a web site over the network 430 to determine the environmental condition. If this condition is detected prior to a pick-up, the computer system 420, the active device 452, and/or the local area network 442 may provide a recommendation to the user device 410 related to the environmental condition (e.g., a recommendation for a pick-up within a time frame, to move the item to a covered area, etc.).
- An image may be analyzed using facial recognition techniques to detect a success or a failure of a delivery event.
- the computer system 420 may have access to an image of the user from, for example, the user account.
- the computer system 420 may analyze the corresponding image, detect a face of the individual who picked up the item, and compare the detected face to the known image of the user. If there is a match, the computer system 420 may determine that the pick-up may have been successful; otherwise, failure may be determined.
- a notification about the success or the failure may be provided to the user device 410.
- 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 start of the delivery to the pick-up of the item at the destination 440.
- the active device 452 may interact with other nodes of the local area network 442 through the 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 on and off a light, a smart switch for turning on and off an oven, or other automation device.
- the active device 452 (or a computing node of the local area network 442) may indicate the delivery event to the one or more of the automation devices over the local area network 442.
- an automation device may initiate an action at the destination 440, such as for instance turning on an oven based on a drop-off of a frozen entree.
- FIG. 5 provides an illustrative table summarizing different phases, interacting components, and the resulting notifications when an active device is used. Some of the interactions or information thereof may be tracked by a computer system and used to generate the notifications by the computer system and/or by one or more of the interacting
- the delivery process may include four phases 510: preparation 512, in-route 514, drop-off 516, and pick-up 518. Other phases and/or combination of phases may also exist.
- one or more interacting components 520 may be involved.
- the interactions may result in one or more end user notifications 530 and one or more delivery device notifications 540.
- the end user notifications 530 may be provided to a user device, such as the user device 410 of FIG. 4.
- the delivery notifications 540 may be provided to a delivery device, such as the delivery device 460 of FIG. 4.
- an order for an item may have been received and may be processed to prepare for the delivery.
- the computer system may provide instructions for including an active device with the order or item. These instructions may relate to the delivery and may include a token usable by the active device to access a local area network at the destination.
- the interacting components 520 may include the active device, and the end user notifications 430 and the delivery device notifications 440 may describe that the order may be under processing.
- the same or a different token may be provided to the delivery device for accessing the local area network 442 and/or the active device 452.
- the delivery may have started but a drop-off may not have occurred yet.
- the interacting components 520 may include the active device and the delivery device.
- the end user notifications 530 may indicate a start of the delivery and provide the location of the item while in-route.
- the delivery device notifications 540 may include delivery instructions. If no token may have been provided to the delivery device in the preparation phase 512, such a token may be provided from the active device or the computer system to the delivery device in the in-route phase 514.
- the delivery device and the active device may have arrived to the destination. Resulting interactions with the local area network (or a computing node thereof) may have resulted in a drop-off
- the interacting components 520 may include the active device, the delivery device, and the local area network (or the computing node thereof).
- the end user notifications 530 may indicate a completion and a time of dropoff.
- the end user notifications 530 may also describe a location of the item (e.g., the drop-off location based on a GPS receiver of the active device if one is used or based on user input at the delivery device) and any environmental conditions (including relevant recommendations).
- the delivery device notifications 540 may include delivery instructions, such as the location of the delivery management device and any authorization therefrom for the drop-off
- the delivery device notifications 540 may also include information about a virtual handoff.
- the delivery device may have departed the destination. However, interactions may occur between the active device, the local area network (or the computing node thereof), and/or the user device until a pick-up may have been detected.
- the interacting components 520 may include the active device, the local area network (or the computing node), and the user device.
- the end user notifications 530 may indicate a movement, a lack of movement (e.g., based on an elapsed time period), and/or a pick-up of the item.
- the end user notifications 530 may also describe a location of the item (e.g., the drop-off location) and any environmental conditions (including relevant recommendations).
- the delivery device notifications 540 may similarly provide information about the movement, pick-up, and/or environmental conditions. Interactions and notifications with other devices may also exist.
- the active device and/or the local area network may inform an automated device located at the destination of the drop-off, movement, and/or pick-up of the item.
- FIGS. 6-10 those figures illustrate example flows for managing notifications.
- FIG. 6 illustrates an example high level flow for generating and transmitting notifications.
- FIGS. 7 and 8 illustrate example flows that a computer system and a delivery management device, respectively, may implement to manage notifications in a computing environment that may include a passive device.
- FIGS. 9 and 10 illustrate example flows that a computer system and an active device, respectively, may implement to manage notifications in a computing environment that may include the active device.
- Some of the operations of the example flows of FIGS. 6-10 may be similar. Such similarities are not repeated herein in the interest of clarity of explanation.
- the example flow of FIG. 6 may start at operation 602, where an order for an item may be received.
- a user may operate a user device to access an electronic marketplace offering the item over a network.
- a computer system facilitating functionalities of the electronic marketplace may receive an order for the item from the user device.
- the computer system may also receive a description, such as an address, of a destination for a delivery of the item.
- the delivery of the item may be prepared.
- the computer system may provide instructions about the delivery.
- the instructions may be used to configure a passive device and/or an active device that may be attached to a holder holding the item for the delivery.
- Configuring the passive device may include storing information about the order, the item, the destination, and/or the delivery instructions in the passive device, or in association with an identifier stored in the passive device.
- a passive RFID tag encoding the information may be printed.
- Configuring the active device may include storing similar information at the active device, or in association with an identifier stored in the active device.
- a token for accessing a 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 example active device may include an active 802.1 1 RFID tag.
- a notification about a start of the delivery may be provided to the user device.
- a delivery device may interact with the passive device and/or active device.
- the delivery device may be associated with a delivery vehicle.
- the interaction may depend on the implementation of such devices. For instance, RF-based communications may be used.
- the computer system may receive an indication of the interaction from the delivery device and/or the active device over a network. This indication may represent the start of the delivery.
- the computer system, the active device, and/or the delivery device may send the notification to the user device based on the interaction.
- location data may be provided to the user device throughout the delivery up to arrival to the destination.
- the passive device, the active device, the delivery device, and/or the delivery vehicle may include a location positioning device(s), such as a GPS receiver(s).
- the local positioning device(s) may provide the location data to the computer system.
- the computer system may facilitate access to the location data by the user device.
- a notification about a drop-off of the item at the destination may be sent to the user device.
- a delivery management device may be located at the destination. Interactions of the delivery management device with the passive device and/or the delivery device may result in detecting the drop-off
- a computing node of a local area network at the destination may interact with the active device and/or the delivery device. The interactions may be used to determine the drop-off
- the computer system may receive an indication of the drop-off from the delivery management device, the delivery device, the computing node of the local area network, and/or the active device.
- 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 the corresponding notification to the user device.
- a notification about movement of the item at the destination may be sent to the user device. If the 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. This change may correspond to the movement. The proximity
- the computer system may receive an indication of the movement from the delivery management device, the delivery device, the computing node of the local area network, and/or the active device.
- 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 the corresponding notification to the user device.
- a notification about a pick-up of the item at the destination may be sent to the user device.
- Different techniques may be used to determine the pick-up.
- proximities may be used. For instance, proximity between the user device and the delivery management device and/or the computing node of the 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 active device. The pick-up may be determined based on the comparison.
- the pick-up may have occurred.
- the computer system may receive an indication of the pick-up from the delivery management device, the delivery device, the computing node of the local area network, and/or the active device.
- 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 the corresponding notification to the user device.
- FIG. 7 the figure illustrates an example flow that the computer system may implement to manage the notifications when the passive device is used.
- the example flow may start at operation 702, where the computer system may provide instructions related to the passive device for the delivery of the item.
- the instructions may be used to, for instance, store the information about the delivery at the passive device, or in association with an identifier stored in the passive device. If a passive RFID tag is used, the instructions may be used to print such a tag.
- the computer system may receive an indication of an interaction between the passive device and the delivery device.
- the delivery device may read, scan, or radiate with RF signals the passive device and may accordingly transmit the indication to the computer system.
- the computer system may determine a start of the delivery based on the received indication. In addition, the computer system may transmit a notification about the start to the user device.
- the computer system may provide delivery instructions to the delivery management device. Similar instructions may also be provided to the delivery device.
- the user device may also specify particular instructions about the delivery of the item (e.g., specific location at the destination, delivery time, requested signatures, etc.).
- the computer system may generate and send the delivery instructions to the delivery management device and/or the delivery device.
- the computer system may determine that a drop-off may have occurred at the destination. This determination may be based on one or more of the received indications. For example, the computer system may determine that a potential drop-off may have occurred based on the proximity of the delivery management device and the passive device. The computer system may confirm this potential drop-off using various techniques. For example, after a predefined period of time, if that proximity is maintained (e.g., based on another indication received from the delivery management device), the confirmation may be made. In another example, the confirmation may be made based on the indication of the proximity of the delivery device and the delivery management device. In yet another example, the computer system may receive the indications of proximities between the delivery management device, the delivery device, and the passive device. If, after a predefined period of time, the delivery device is no longer located in proximity of the delivery management device, the confirmation may be made. The computer system may accordingly send a notification about the drop-off to the user device.
- the computer system may receive a change to the proximity between the passive device and the delivery management device.
- the delivery management device may detect the change and send an indication of the change to the computer system.
- the computer system may determine movement of the item based on the change. The computer system may accordingly send a notification about the movement to the user device.
- the computer system may determine a pick-up of the item. For example, the computer system may receive an indication from the user device of the pick-up. In another example, proximities of the delivery management device, the passive device, and the user device may be used to detect the pick-up. For example, the computer system may access the position location (e.g., GPS data) of the user device and the delivery management device. If the two devices may be proximate to each other, the computer system may access (e.g., request and receive or automatically receive) an indication from the delivery management device of movement of the item. The computer system may detect the pick-up based on such proximities and the movement.
- position location e.g., GPS data
- the delivery management device may determine a proximity to the passive device. This proximity may be determined based on interactions with the passive device and/or the delivery device. The interaction may include receiving information about the order, e.g., from the passive device, or based on information stored in association with an identifier in the passive device.
- the delivery management device may authorize a drop-off of the item. For example, the delivery management device may compare the information received from the passive device and/or the delivery device to the information received from the computer system and/or user device. If an acceptable match is found (e.g., the unique identifier associated with the order is the same), the drop-off may be authorized.
- the delivery instructions may also include, for instance, a delivery time frame and/or environmental conditions (e.g., drop-off to occur when there is no rain). The delivery management device may further authorize the drop-off based on the delivery time frame and/or the environmental conditions. Once authorized, the delivery management device may send an indication of the authorization to the computer system and/or the delivery device. In addition, the delivery management device and/or the computer system may send a corresponding notification to the user device.
- the delivery management device may provide a portion of the delivery instructions to the delivery device.
- the delivery instructions may include a specific location to drop-off the item at the location.
- the delivery management device may identify this location to the delivery device.
- the delivery management device may determine a completion of the drop-off This determination may be made based on proximity of the delivery
- the management device to the passive device and/or the delivery device. For example, if the passive device remains in proximity of the delivery management device for a predefined period of time, the completion of the drop-off may be detected. In another example, if the delivery device is no longer in proximity of the delivery management device, the completion of the drop-off may be detected.
- the delivery management device may provide information about the completion of the drop-off 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 drop-off to the computer system and/or the delivery device. In addition, the delivery management device and/or the computer system may send a corresponding notification to the user device.
- the delivery management device may determine a pick-up of the item.
- the pick-up may be determined based on the proximity (or lack thereof) to the passive device. For instance, if the passive device is no longer at a location proximate to the delivery management device, the pick-up may be determined. In addition, the pick-up may be determined based on the proximity to the user device. For example, the delivery management device may determine the 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).
- the pick-up may be detected.
- the delivery management device may send an indication of the pick-up to the computer system.
- the delivery management device and/or the computer system may send a corresponding notification to the user device.
- FIG. 9 the figure illustrates an example flow that the computer system may implement to manage the notifications when the active device is used.
- the example flow may start at operation 902, where the computer system may provide a token for storage at the active device.
- the token may be generated by the computer system, the user device, and/or a computing node of the local area network of the destination based on the order of the item.
- the computer system may provide delivery instructions to the delivery device.
- the computer system may receive an indication from the computing node of the local area network about the communication with the active device.
- the communication may be based on the token.
- the computing node may receive the token from the active device and, accordingly, authenticate the active device.
- the computing node may send an indication of the communication to the computer system.
- the computer system may receive an indication of a communication between the delivery device and the computing node. This communication may also be based on a same or a different token.
- the indication of the communication may be received from the delivery device and/or the computing node.
- the computer system may determine that a drop-off may have occurred at the destination. This determination may be based on one or more of the received indications. For example, the computer system may determine that a potential drop-off may have occurred based on the communication of the computing node and the active device. The computer system may confirm this potential drop-off using various techniques. For example, the drop-off may be confirmed based on the communication between the delivery device and the computing node, or based on the termination of such a communication (which may be received in another indication from the delivery device and/or the computing node). In another example, the drop-off may be determined based on the proximity of the active device to the destination.
- the computer system may receive the location information (e.g., GPS data) of the active device and may compare the location information to the one of the destination. If the active device remains within a geographical fence of the destination for a predefined period of time, the drop-off may have occurred. In yet another example, the drop-off may be determined based on the proximity of the delivery device to the destination. For instance, the computer system may receive the location information (e.g., GPS data) of the delivery device and may compare the location information to the one of the destination. If the delivery device enters and then leaves the geographical fence while the communication between the computing node and the active device persists, the drop-off may be complete.
- location information e.g., GPS data
- the computer system may receive a change to the proximity between the active device and the delivery management device.
- the computer system may receive the location information (e.g., GPS data) of the active device and may compare the location information to the one of the destination. If there is a change in the location information, that change may correspond to the proximity change.
- the computer system may determine movement of the item based on the change. The computer system may accordingly send a notification about the movement to the user device.
- the computer system may determine a pick-up of the item. For example, the computer system may receive an indication from the user device of the pick-up. In another example, proximities of the computing node, the active device, and the user device may be used to detect the pick-up. For example, the computer system may access the location information (e.g., GPS data) of the computing node, the active device, and the user device to determine the proximities and accordingly detect the pick-up.
- location information e.g., GPS data
- the active device may cause a determination of a drop-off of the item.
- the drop-off 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 the drop-off may have occurred.
- a corresponding notification may be sent to the user device and/or the delivery device.
- the active device may provide its location information (e.g., GPS data) to the computer system and/or the computing node or may receive the location information of the destination. Based on a comparison of the location information, the proximity may be determined.
- the computing node and/or the active device may use RF ranging to detect the proximity.
- This proximity may be used with other factors to determine a completion of the drop-off. For example, if the active device and the computing node remain in proximity for a pre-defined period of time, the drop-off may be complete. In another example, if the delivery device is no longer in proximity to the active device, the drop-off may be complete.
- the active device may cause a determination of a movement of the item.
- the movement may be determined based on proximity of the active device to the computing node. Based on this proximity, the active device, the computing node, and/or the computer system may determine that the movement may have occurred.
- a corresponding notification may be sent to the user device.
- a change in the location information of the active device relative to destination may indicate the movement of the item.
- RF ranging may be applied based on the communication between the active device and the computing node. The RF ranging may indicate a change in a distance range between the active device and the computing node. This change may correspond to the movement of the item.
- the seller device 11 12 may be any type of computing devices such as, but not limited to, a mobile phone, a smart phone, a personal digital assistant (PDA), a laptop computer, a thin-client device, a tablet PC, etc.
- the seller device 11 12 may contain communications connection(s) that allow the seller device 11 12 to communicate with a stored database, another computing device or server, seller terminals, and/or other devices on the networks 1180.
- the seller device 1 112 may also include input/output (I/O) device(s) and/or ports, such as for enabling connection with a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, speakers, a printer, etc.
- I/O input/output
- the seller device 1 112 may also include at least one or more processing units (or processor device(s)) 1 1 14 and at least one memory 1 1 16.
- the processor device(s) 1 114 may be implemented as appropriate in hardware, computer-executable instructions, firmware, or combinations thereof.
- Computer-executable instructions or firmware implementations of the processor device(s) 11 14 may include computer- executable or machine-executable instructions written in any suitable programming language to perform the various functions described.
- the memory 1 116 may store program instructions that are loadable and executable on the processor device(s) 11 14, as well as data generated during the execution of these programs.
- the memory 1 116 may be volatile (such as random access memory (RAM)) and/or non-volatile (such as readonly memory (ROM), flash memory, etc.).
- the seller device 1112 may also include additional storage, which may include removable storage and/or non-removable storage.
- the additional storage may include, but is not limited to, magnetic storage, optical disks, and/or tape storage.
- 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 devices.
- the memory 1116 may include multiple different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), or ROM.
- the memory may include an operating system (O/S) 1118 and the one or more application programs or services for implementing the features disclosed herein including the web service application 1120.
- the seller device 1112 may be in communication with the service provider devices 1130 via the networks 1180, or via other network connections.
- the networks 1180 may include any one or a combination of many different types of networks, such as cable networks, the Internet, wireless networks, cellular networks, and other private and/or public networks.
- the described techniques may equally apply in instances where the seller 1110 interacts with the service provider devices 1130 via the seller device 1112 over a landline phone, via a kiosk, or in any other manner. It is also noted that the described techniques may apply in other client/server arrangements (e.g., set-top boxes, etc.), as well as in non-client/server arrangements (e.g., locally stored applications, peer-to- peer systems, etc.).
- client/server arrangements e.g., set-top boxes, etc.
- non-client/server arrangements e.g., locally stored applications, peer-to- peer systems, etc.
- a customer 1160 may utilize customer device 1162 to access local applications, a web service application 1170 (or some other mobile application such as a
- mobile app available from an application store
- customer account accessible through the web service application 1170, a web site, or any other network-based resources via the networks 1180.
- the web service application 1170, the web site, and/or the user account may be hosted, managed, and/or otherwise provided by the service provider devices 1130 and may be similar to the web service application 1120, the web site accessed by the computing device 1112, and/or the seller account, respectively.
- the customer 1160 may use the local applications and/or the web service application 1170 to conduct transactions with the network-based resources of the service provider. These transactions may include, for example, browsing for items, viewing items, ordering items, reviewing items, returning items, receiving notifications, viewing notifications, dismissing notifications, and/or other transactions.
- the customer device 1162 may be configured similarly to the seller device 1112 and may include at least one or more processing units (or processor device(s)) 1164 and at least one memory 1166.
- the processor device(s) 1164 may be implemented as appropriate in hardware, computer-executable instructions, firmware, or combinations thereof similarly to the processor device(s) 1114.
- the memory 1166 may also be configured similarly to the memory 1116 and may store program instructions that are loadable and executable on the processor device(s) 1164, as well as data generated during the execution of these programs.
- the memory 1166 may include an operating system (O/S) 1168 and the one or more application programs or services for implementing the features disclosed herein including the web service application 1170.
- O/S operating system
- the web service applications 1120 and 1170 may allow the seller 1110 and customer 1160, respectively, to interact with the service provider devices 1130 to conduct transactions involving items.
- the service provider devices 1130 may host the web service applications 1120 and 1170. These servers may be configured to host a web site (or combination of web sites) viewable via the computing devices 1112 and 1162. Other server architectures may also be used to host the web service applications 1120 and 1170.
- the web service applications 1120 and 1170 may be capable of handling requests from many sellers 1110 and customers 1160, respectively, and serving, in response, various interfaces that may be rendered at the computing devices 1112 and 1162 such as, but not limited to, a web site.
- the web service applications 1120 and 1170 may interact with any type of web site that supports interaction, including social networking sites, electronic retailers, informational sites, blog sites, search engine sites, news and entertainment sites, and so forth. As discussed above, the described techniques may similarly be implemented outside of the web service applications 1120 and 1170, such as with other applications running on the computing devices 1112 and 1162, respectively.
- the service provider devices 1130 may, in some examples, provide network-based resources such as, but not limited to, applications for purchase and/or download, web sites, web hosting, client entities, data storage, data access, management, virtualization, etc.
- the service provider devices 1130 may also be operable to provide web hosting, computer application development, and/or implementation platforms, or combinations of the foregoing to the seller 1110 and customer 1160.
- the service provider devices 1130 may be any type of computing device such as, but not limited to, a mobile phone, a smart phone, a personal digital assistant (PDA), a laptop computer, a desktop computer, a server computer, a thin-client device, a tablet PC, etc.
- PDA personal digital assistant
- the service provider devices 1130 may also contain communications connection(s) that allow service provider devices 1130 to communicate with a stored database, other computing devices or servers, seller terminals, and/or other devices on the network 1 180.
- the service provider devices 1 130 may also include input/output (I/O) device(s) and/or ports, such as for enabling connection with a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, speakers, a printer, etc.
- I/O input/output
- the service provider devices 1130 may include at least one or more processing units (or processor devices(s)) 1 132 and at least one memory 1134.
- the processor device(s) 1 132 may be implemented as appropriate in hardware, computer-executable instructions, firmware, or combinations thereof.
- Computer-executable instruction or firmware implementations of the processor device(s) 1 132 may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described.
- the memory 1 134 may store program instructions that are loadable and executable on the processor device(s) 1132, as well as data generated during the execution of these programs.
- the memory 1 134 may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.).
- the service provider devices 1130 may also include additional removable storage and/or non-removable storage including, but not limited to, magnetic storage, optical disks, and/or tape storage.
- the disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computing devices.
- the memory 1134 may include multiple different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), or ROM.
- SRAM static random access memory
- DRAM dynamic random access memory
- ROM read-only memory
- the computer storage media described herein may 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.
- a transmitted signal may take any of a variety of forms including, but not limited to, electromagnetic, optical, or any combination thereof.
- computer- readable media does not include computer-readable communication media.
- the memory may include an operating system (O/S) 1136, code for an electronic marketplace 1138 and code for a notification manager 1140.
- the notification manager 1140 may be configured to provide notification functionalities to the seller device 1112 and the customer device 1162. These functionalities may be based on interactions with delivery devices, active devices, passive devices, delivery management devices, and/or computing nodes of local area networks.
- containing are to be construed as open-ended terms (i.e., meaning “including, but not limited to,”) unless otherwise noted.
- the term “connected” is to be construed as partly or wholly contained within, attached to, or joined together, even if there is something intervening. 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 may be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context.
- Disjunctive language such as that included in the phrase "at least one of X, Y, or Z," unless specifically stated otherwise, is otherwise understood within the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z each to be present.
- Clause 4 The system of claim 1 , wherein the computer system generates a third notification for the user device about a movement of the item at the destination, the third notification based at least in part on a change of a proximity between the active tag and the node.
- An apparatus associated with a delivery of an item to or from a location associated with a local area network comprising: an interface configured to attach the apparatus 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 apparatus to: receive a token associated with the local area network, the token received from a computer system based at least in part on an order of the item processed at the computer system;
- Clause 7 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 device via the node of the local area network.
- Clause 8 The apparatus of claim 5, wherein the computer-readable instructions, when executed with the processor, further cause the apparatus to: establish an other communication with a delivery device associated with a delivery vehicle, the other communication established prior to establishing the communication with the node; cause a notification about a start of the delivery to be transmitted to a user device based at least in part on the other communication with the delivery device.
- Clause 11 The apparatus of claim 5, wherein the apparatus comprises an active radio frequency identification (RFID) tag configured for wireless communication with the node 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 time period from a time of a drop-off of the item.
- RFID radio frequency identification
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Economics (AREA)
- Quality & Reliability (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Development Economics (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/869,117 US10592844B2 (en) | 2015-09-29 | 2015-09-29 | Managing notifications of a delivery method based on an active device |
US14/869,145 US11645608B2 (en) | 2015-09-29 | 2015-09-29 | Managing notifications of a delivery method based on a passive device |
PCT/US2016/054505 WO2017059112A1 (en) | 2015-09-29 | 2016-09-29 | Managing notifications of a delivery method based on an active device |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3357014A1 true EP3357014A1 (en) | 2018-08-08 |
Family
ID=57178488
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP16784628.6A Ceased EP3357014A1 (en) | 2015-09-29 | 2016-09-29 | Managing notifications of a delivery method based on an active device |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP3357014A1 (en) |
CN (1) | CN108140163B (en) |
AU (1) | AU2016330891B2 (en) |
WO (1) | WO2017059112A1 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200090259A1 (en) * | 2018-09-14 | 2020-03-19 | Blackberry Limited | Method and system for bulk asset leasing |
US20220391835A1 (en) * | 2019-11-15 | 2022-12-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and Device for Monitoring Delivery Process, Server and Method Therein |
US11321651B2 (en) | 2019-12-30 | 2022-05-03 | Coupang Corp. | Cycle and safety stock determination systems |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6975998B1 (en) * | 2000-03-01 | 2005-12-13 | Arrivalstar, Inc. | Package delivery notification system and method |
US20040186768A1 (en) * | 2003-03-21 | 2004-09-23 | Peter Wakim | Apparatus and method for initiating remote content delivery by local user identification |
US7333014B2 (en) * | 2004-11-04 | 2008-02-19 | International Business Machines Corporation | Notifying users of device events in a networked environment |
US20120158606A1 (en) * | 2009-02-27 | 2012-06-21 | Christopher Moudy | System for delivery of goods ordered via the internet |
US20090201198A1 (en) * | 2004-12-06 | 2009-08-13 | Christopher Moudy | System and method for delivery of goods ordered via the internet |
CN100375975C (en) * | 2006-04-26 | 2008-03-19 | 孟友新 | RFID device based on 802.11 b |
US7840340B2 (en) * | 2007-04-13 | 2010-11-23 | United Parcel Service Of America, Inc. | Systems, methods, and computer program products for generating reference geocodes for point addresses |
WO2011038018A1 (en) * | 2009-09-23 | 2011-03-31 | Earthsearch Communications International, Inc. | Device and process for monitoring secure storage and delivery of items |
WO2012129529A1 (en) * | 2011-03-24 | 2012-09-27 | Fedex Corporate Services, Inc. | Systems and methods for electronically signing for a delivered package |
WO2013063112A1 (en) * | 2011-10-25 | 2013-05-02 | Packtrak Llc | System and method for delivery transporter tracking and recipient notification |
CN102436596A (en) * | 2011-11-08 | 2012-05-02 | 北京博大光通国际半导体技术有限公司 | Commodity anti-counterfeiting traceability system and method based on active radio frequency identification (RFID) technology |
CN102801773B (en) * | 2012-03-09 | 2019-04-23 | 上海互惠信息技术有限公司 | Internet of things system and Item Information acquisition and monitoring method |
CN102938114A (en) * | 2012-09-20 | 2013-02-20 | 华东理工大学 | Food safety tracking system in cold-chain logistics based on radio frequency identification device (RFID) and data validation method of system |
CN103064371B (en) * | 2012-12-17 | 2016-03-02 | 陈坚 | A kind of unmanned formula self-aided terminal, Turnover Box and realize the method for accurate logistics |
-
2016
- 2016-09-29 EP EP16784628.6A patent/EP3357014A1/en not_active Ceased
- 2016-09-29 AU AU2016330891A patent/AU2016330891B2/en active Active
- 2016-09-29 CN CN201680056326.3A patent/CN108140163B/en active Active
- 2016-09-29 WO PCT/US2016/054505 patent/WO2017059112A1/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
AU2016330891A1 (en) | 2018-04-19 |
CN108140163A (en) | 2018-06-08 |
CN108140163B (en) | 2022-11-29 |
AU2016330891B2 (en) | 2020-04-02 |
WO2017059112A1 (en) | 2017-04-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11645608B2 (en) | Managing notifications of a delivery method based on a passive device | |
US11348059B2 (en) | Managing notifications of a delivery method based on an active device | |
KR102373427B1 (en) | Computerized systems and methods for assisted picking processes | |
US20230230148A1 (en) | Intelligent Item Tracking and Expedited Item Reordering by Stakeholders | |
US20160071056A1 (en) | Programmatically executing time compressed delivery | |
US20180365642A1 (en) | Systems and methods for facilitating parcel pickup | |
US20150012396A1 (en) | Transitioning items from a materials handling facility | |
US20140379529A1 (en) | Order fulfillment systems and methods with customer location tracking | |
US10380667B2 (en) | Collaborative delivery device | |
KR102275829B1 (en) | Systems and methods for simulation of package configurations for generating cost optimized configurations | |
AU2016330891B2 (en) | Managing notifications of a delivery method based on an active device | |
US20170352000A1 (en) | Managing delivery of environmentally sensitive products | |
KR20220051131A (en) | Centralized health monitoring in multi-domain networks | |
KR20220051129A (en) | A system and method for detecting errors in asynchronously queued requests | |
WO2020060807A1 (en) | Food and beverage item identification and tracking device and system for improving supply chain logistical operations and inventory management | |
KR20180085975A (en) | System and method for managing parcel delivery box using beacon | |
JP2023518987A (en) | Methods, apparatus, servers, computer readable media and computer programs for processing appliance demand information | |
US20210158461A1 (en) | System and Method of Order Fulfillment to Nonexclusive Delivery Locations Using Customer Location Tracking | |
JP2015153100A (en) | Refrigerator, management device and refrigerator order placement delivery system | |
US20180330426A1 (en) | Consolidation of personal items into gift orders | |
US10311397B1 (en) | Automatic discovery of endpoint devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20180430 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20190125 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20210125 |