Methods and apparatus for deploying a plurality of pickup entities for a node-enabled logistics receptacle
Methods, computer-readable medium, and apparatus are described for deploying a plurality of pickup entities to a node-enabled logistics receptacle in a wireless node network. A server in the network receives a message from a node-enabled logistics receptacle. The message identifies a plurality of packages currently maintained within the node-enabled logistics receptacle ready for pickup. In response, the server accesses shipping information from a server memory storage, where the shipping information is related to the identified plurality of packages currently maintained with the node-enabled logistics receptacle. The server then identifies which of the plurality of pickup entities need to be deployed to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.
1. A method for deploying one or more of a plurality of shipping courier pickup entities to a node-enabled logistics receptacle in a wireless node network, the method comprising:
receiving, by a server in the wireless node network, a message from the node-enabled logistics receptacle, the message identifying a plurality of packages currently maintained within the node-enabled logistics receptacle ready for pickup;
accessing, by the server, shipping information from a server memory storage, the shipping information being related to the identified plurality of packages currently maintained with the node-enabled logistics receptacle, wherein the shipping information indicates which of the plurality of shipping courier pickup entities that are independent of a destination of the package as specified in destination shipping information are the appropriate pickup entity to provide pickup services for each of the identified plurality of packages, where the server memory storage includes the destination shipping information for each of the identified plurality of packages that is distinct from the shipping information that indicates which of the plurality of shipping courier pickup entities are the appropriate pickup entity to provide pickup services for each of the identified plurality of packages;
identifying, by the server, which of the plurality of shipping courier pickup entities need to be deployed to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information;
causing, by the server, the identified ones of the plurality of shipping courier pickup entities to provide the one or more pickup services at the node-enabled logistics receptacle;
determining, by the server, that a previously scheduled one of the pickup entities is not one of the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle; and
notifying, by the server, the previously scheduled one of the shipping courier pickup entities when the server has determined the previously scheduled one of the pickup entities is not one of the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle.
2. The method of claim 1 , wherein the causing step further comprises transmitting a pickup request over a communication interface to the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle.
3. The method of claim 1 further comprising updating historic data for the node-enabled logistics receptacle related to the identified ones of the shipping courier pickup entities, the historic data comprising information on which shipping courier pickup entities are needed for packages historically deposited in the node-enabled logistics receptacle.
4. The method of claim 3 further comprising predicting a future pickup schedule for the node-enabled logistics receptacle based upon the updated historic data, the future pickup schedule being for at least one of the shipping courier pickup entities.
5. The method of claim 4 further comprising transmitting the future pickup schedule to those of the shipping courier pickup entities having a predicted pickup service in the future pickup schedule for the node-enabled logistics receptacle.
6. The method of claim 2 , wherein the transmitting step further comprises:
accessing an existing pickup schedule maintained in the server memory storage, the existing pickup schedule comprising one or more existing scheduled pickup services to be performed by one or more of the shipping courier pickup entities at the node-enabled logistics receptacle; and
notifying one of the shipping courier pickup entities that is on the existing pickup schedule but that is not identified as one of the plurality of shipping courier pickup entities that they do not need to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.
7. The method of claim 6 further comprising revising the existing pickup schedule based on the identified ones of the plurality of shipping courier pickup entities that need to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.
8. A non-transitory computer-readable medium containing instructions which when executed on a processor performs a method for deploying one or more of a plurality of shipping courier pickup services to a node-enabled logistics receptacle in a wireless node network, the method comprising:
receiving, by a server in the wireless node network, a message from the node-enabled logistics receptacle, the message identifying a plurality of packages currently maintained within the node-enabled logistics receptacle ready for pickup;
accessing, by the server, shipping information from a server memory storage, the shipping information being related to the identified plurality of packages currently maintained with the node-enabled logistics receptacle, wherein the shipping information indicates which of the plurality of shipping courier pickup entities that are independent of a destination of the package as specified in destination shipping information are the appropriate pickup entity to provide pickup services for each of the identified plurality of packages, where the server memory storage includes the destination shipping information that specifies a destination for each of the identified plurality of packages that is distinct from the shipping information that indicates which of the plurality of shipping courier pickup entities are the appropriate pickup entity to provide pickup services for each of the identified plurality of packages;
identifying, by the server, which of the plurality of shipping courier pickup entities need to be deployed to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information;
causing, by the server, the identified ones of the plurality of shipping courier pickup entities to provide the one or more pickup services at the node-enabled logistics receptacle; and
notifying, by the server, a previously scheduled one of the shipping courier pickup entities when the server has determined the previously scheduled one of the pickup entities is not one of the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle.
9. The non-transitory computer-readable medium of claim 8 , wherein the causing step further comprises transmitting a pickup request over a communication interface to the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle.
10. The non-transitory computer-readable medium of claim 8 further comprising updating historic data for the node-enabled logistics receptacle related to the identified ones of the shipping courier pickup entities, the historic data comprising information on which shipping courier pickup entities are needed for packages historically deposited in the node-enabled logistics receptacle.
11. The non-transitory computer-readable medium of claim 10 further comprising predicting a future pickup schedule for the node-enabled logistics receptacle based upon the updated historic data, the future pickup schedule being for at least one of the shipping courier pickup entities.
12. The non-transitory computer-readable medium of claim 11 further comprising transmitting the future pickup schedule to those of the shipping courier pickup entities having a predicted pickup service in the future pickup schedule for the node-enabled logistics receptacle.
13. The non-transitory computer-readable medium of claim 9 , wherein the transmitting step further comprises:
accessing an existing pickup schedule maintained in the server memory storage, the existing pickup schedule comprising one or more existing scheduled pickup services to be performed by one or more of the shipping courier pickup entities at the node-enabled logistics receptacle; and
notifying one of the shipping courier pickup entities that is on the existing pickup schedule but that is not identified as one of the plurality of shipping courier pickup entities that they do not need to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.
14. The non-transitory computer-readable medium of claim 13 further comprising revising the existing pickup schedule based on the identified ones of the plurality of shipping courier pickup entities that need to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.
15. A server apparatus in a wireless node network for deploying one or more of a plurality of shipping courier pickup entities to a node-enabled logistics receptacle, comprising:
at least one server processing unit;
at least one server memory storage coupled to the server processing unit, the server memory storage maintaining code for execution by the server processing unit, destination shipping information, and shipping information about a plurality of packages currently maintained within the node-enabled logistics receptacle ready for pickup, wherein the shipping information indicates which of the plurality of shipping courier pickup entities that are independent of a destination of the package as specified in the destination shipping information are the appropriate pickup entity to provide pickup services for each of the plurality of packages, wherein the destination shipping information specifies a destination for each of the identified plurality of packages and is distinct from the shipping information that indicates which of the plurality of shipping courier pickup entities are the appropriate pickup entity to provide pickup services for each of the identified plurality of packages;
a communication interface coupled to the server processing unit, the communication interface being collectively operative to communicate with at least the node-enabled logistics receptacle in the wireless node network; and
wherein the server processing unit, when executing the code maintained on the server memory storage, is operative to
receive a message from the node-enabled logistics receptacle over the communication interface, the message identifying the plurality of packages currently maintained within the node-enabled logistics receptacle ready for pickup,
access the server memory storage to obtain the shipping information related to the identified plurality of packages currently maintained with the node-enabled logistics receptacle, wherein the shipping information for each of the identified plurality of packages indicates which of the plurality of shipping courier pickup entities are the appropriate pickup entity to provide pickup services for a particular one of the identified plurality of packages,
identify which of the plurality of pickup entities need to be deployed to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information,
cause the communication interface to transmit a pickup request to the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle, the transmitted pickup request causing the identified ones of the plurality of shipping courier pickup entities to provide the one or more pickup services at the node-enabled logistics receptacle, and
notify a previously scheduled one of the pickup entities over the communications interface when the server processing unit has determined the previously scheduled one of the shipping courier pickup entities is not one of the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle.
16. The server apparatus of claim 15 , wherein the server processing unit is further operative to:
update historic data for the node-enabled logistics receptacle related to the identified ones of the shipping courier pickup entities, the historic data comprising information on which shipping courier pickup entities are needed for packages historically deposited in the node-enabled logistics receptacle; and
store the updated historic data in the server memory storage.
17. The server apparatus of claim 16 , wherein the server processing unit is further operative to predict a future pickup schedule for the node-enabled logistics receptacle based upon the updated historic data, the future pickup schedule being for at least one of the shipping courier pickup entities.
18. The server apparatus of claim 17 , wherein the server processing unit is further operative to cause the future pickup schedule to be transmitted over the communication interface to those of the shipping courier pickup entities having a predicted pickup service in the future pickup schedule for the node-enabled logistics receptacle.
19. The server apparatus of claim 15 , wherein the server processing unit is further operative to cause the communication interface to transmit the pickup request by being operative to:
access an existing pickup schedule maintained in the server memory storage, the existing pickup schedule comprising one or more existing scheduled pickup services to be performed by one or more of the shipping courier pickup entities at the node-enabled logistics receptacle; and
notify, over the communication interface, one of the shipping courier pickup entities that is on the existing pickup schedule but that is not identified as one of the plurality of shipping courier pickup entities that they do not need to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.
20. The server apparatus of claim 19 , wherein the server processing unit is further operative to revise the existing pickup schedule based on the identified ones of the plurality of shipping courier pickup entities that need to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.
21. A system in a wireless node network for deploying one or more of a plurality of shipping courier pickup entities, comprising:
a node-enabled logistics receptacle that maintains a plurality of packages ready for pickup; and
a server in communication with the node-enabled logistics receptacle and operative to communication with the plurality of shipping courier pickup entities, the server further comprising,
at least one server processing unit;
at least one server memory storage coupled to the server processing unit, the server memory storage maintaining code for execution by the server processing unit, destination shipping information, and shipping information about the plurality of packages currently maintained within the node-enabled logistics receptacle ready for pickup, wherein the shipping information indicates which of the plurality of shipping courier pickup entities that are independent of a destination of the package as specified in destination shipping information are the appropriate pickup entity to provide pickup services for each of the plurality of packages, and wherein the destination shipping information specifies a destination for each of the identified plurality of packages and is distinct from the shipping information that indicates which of the plurality of shipping courier pickup entities are the appropriate pickup entity to provide pickup services for each of the identified plurality of packages;
a communication interface coupled to the server processing unit, the communication interface being collectively operative to communicate with at least the node-enabled logistics receptacle in the wireless node network and the plurality of shipping courier pickup entities; and
wherein the server processing unit, when executing the code maintained on the server memory storage, is operative to
receive a message from the node-enabled logistics receptacle over the communication interface, the message identifying the plurality of packages currently maintained within the node-enabled logistics receptacle ready for pickup,
access the server memory storage to obtain the shipping information related to the identified plurality of packages currently maintained with the node-enabled logistics receptacle, wherein the shipping information for each of the identified plurality of packages indicates which of the plurality of shipping courier pickup entities are the appropriate pickup entity to provide pickup services for a particular one of the identified plurality of packages,
identify which of the plurality of pickup entities need to be deployed to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information,
cause the communication interface to transmit a pickup request to the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle, the transmitted pickup request causing the identified ones of the plurality of shipping courier pickup entities to provide the one or more pickup services at the node-enabled logistics receptacle, and
notify a previously scheduled one of the pickup entities over the communications interface when the server processing unit has determined the previously scheduled one of the shipping courier pickup entities is not one of the identified ones of the shipping courier pickup entities regarding the one or more pickup services to be performed at the node-enabled logistics receptacle.
22. The system of claim 21 , wherein the server processing unit is further operative to:
update historic data for the node-enabled logistics receptacle related to the identified ones of the shipping courier pickup entities, the historic data comprising information on which shipping courier pickup entities are needed for packages historically deposited in the node-enabled logistics receptacle; and
store the updated historic data in the server memory storage.
23. The system of claim 22 , wherein the server processing unit is further operative to predict a future pickup schedule for the node-enabled logistics receptacle based upon the updated historic data, the future pickup schedule being for at least one of the shipping courier pickup entities.
24. The system of claim 23 , wherein the server processing unit is further operative to cause the future pickup schedule to be transmitted over the communication interface to those of the shipping courier pickup entities having a predicted pickup service in the future pickup schedule for the node-enabled logistics receptacle.
25. The system of claim 22 , wherein the server processing unit is further operative to cause the communication interface to transmit the pickup request by being operative to:
access an existing pickup schedule maintained in the server memory storage, the existing pickup schedule comprising one or more existing scheduled pickup services to be performed by one or more of the shipping courier pickup entities at the node-enabled logistics receptacle; and
notify, over the communication interface, one of the shipping courier pickup entities that is on the existing pickup schedule but that is not identified as one of the plurality of shipping courier pickup entities that they do not need to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.
26. The system of claim 25 , wherein the server processing unit is further operative to revise the existing pickup schedule based on the identified ones of the plurality of shipping courier pickup entities that need to provide one or more pickup services at the node-enabled logistics receptacle based upon the shipping information.