Receptacle for detecting delivery and retrieval events

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

0001Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57. This application is a continuation of U.S. application Ser. No. 15/466,475, filed on Mar. 22, 2017, which claims the benefit of priority to U.S. Provisional Patent Application No. 62/312,323, filed on Mar. 23, 2016, the entire contents of which are herein incorporated in their entirety.

BACKGROUND

Field

0002This disclosure relates to the field of transportation, delivery, and/or receipt of one or several items and to the field of communication, tracking, and control of the transportation, delivery, and/or receipt of one or several items. This disclosure also relates to an item receptacle for detecting when a delivery and/or a pick-up have occurred, to further actions to be taken upon delivery or pick-up confirmation, and interactions with physical items, such as mailpieces.

Description of the Related Technology

0003An item sender may wish to know when a sent item is delivered to a recipient and/or when an item has been picked up. A recipient may also wish to know when an item has been delivered and is available for pick-up. Systems and methods described herein relate to receptacles and accompanying systems to facilitate these notifications.

SUMMARY

0004In one aspect described herein, an item receptacle comprises a plurality of sides enclosing an internal volume; a door moveably connected to one of the plurality of sides, the door configured to open and close to allow access to the internal volume; a door sensor configured to detect when the door is opened; a processor in communication with the door sensor, the processor configured to receive a signal corresponding to a change in state of the door sensor; a communication device in communication with the processor, the communication device configured to communicate with a central hub; and wherein the processor is configured to store a change in state of the door sensor and transmit, via the communication device, the change in state of the door sensor to the central hub.

0005In some embodiments, the item receptacle further comprises an item sensor disposed within the internal volume, the item sensor comprising an emitter adapted to emit a beam and a detector to detect the beam, and to identify a change in state of the beam, the item sensor in communication with the processor.

0006In some embodiments, the processor is further configured to identify whether a delivery or pick-up event has occurred based on the change of state of the door sensor and the change of state of the item sensor.

0007In some embodiments, the processor is configured to store a change in state of the beam and to transmit the change in state of the beam to the central hub.

0008In some embodiments, the item receptacle further comprises a scanner connected to one of the plurality of sides, and disposed within the internal volume, the scanner in communication with the processor, the scanner configured to read a computer readable code on an item within the internal volume.

0009In some embodiments, the processor is configured to instruct the scanner to scan the internal volume to read the computer readable code on the item disposed within the internal volume.

0010In some embodiments, the processor is further configured to identify whether a delivery or pick-up even has occurred based on the change of state of the door sensor and the reading of the computer readable code by the scanner.

0011In some embodiments, the processor is configured to transmit a signal indicative of the computer readable code to the central hub.

0012In some embodiments, the item receptacle further comprises a wireless communication device configured to communicate with an identifier tag on an item disposed within the mailbox.

0013In some embodiments, the item receptacle further comprises a power supply connected to the processor and the door sensor, the power supply comprising a solar panel attached to an external surface of the item receptacle.

0014In another aspect described herein, a method for using an item receptacle comprises, detecting, in a processor, a signal from an item sensor located on an item receptacle, wherein the item receptacle comprises: a plurality of sides enclosing an internal volume; a door comprising a door state sensor; and an item sensor; the method further comprising detecting, in a processor, a door open signal from the door state sensor; determining, in a processor, whether an item delivery or pick up event has occurred based on the detected door open signal and the detected item sensor signal; and causing a notification of a delivery event to be sent to a recipient of an item.

0015In some embodiments, the method further comprises causing a notification of a pick up event to be sent to a sender of the item or to a recipient of the item.

0016In some embodiments, the item sensor comprises an emitter configured to emit a beam of electromagnetic radiation and a detector, and the signal comprises a change in state of the beam.

0017In some embodiments, an item delivery event is determined when the beam changes from an uninterrupted state prior to a door open event to an interrupted state following a door open event.

0018In some embodiments, an item pickup event is determined when the beam changes from an interrupted state prior to a door open event to an uninterrupted state following a door open event.

0019In some embodiments, the item sensor comprises a scanner configured to read a computer readable code on an item within the internal volume, and wherein the signal comprises information indicative of the computer readable code read by the scanner.

0020In some embodiments, a delivery event is determined when the scanner reads no computer readable code prior to a door open signal is received, and reads a computer readable code after the door open signal is received.

0021In some embodiments, a pick-up event is determined when the scanner reads the computer readable code prior to a door open signal is received, and reads no computer readable code after the door open signal is received.

0022In some embodiments, the method further comprises receiving, at the processor, location and time information from a delivery device associated with a delivery resource assigned to deliver an item, detecting a time of the door open signal; determining that a delivery event occurred based on the location and time information from the delivery device and the time of the door open signal.

0023In another aspect, a system comprises an item receptacle comprising: a plurality of sides enclosing an internal volume; a door configured to open and close to allow and deny access to the internal volume; means for detecting a change in state of the door; means for sensing the presence of an item; means for detecting a signal from an item sensor located on an item receptacle, wherein means for determining whether an item delivery or pick up event has occurred based on the detected change in state of the door and the detected item presence; and means for causing a notification of a delivery event to be sent to a recipient of an item.

BRIEF DESCRIPTION OF THE DRAWINGS

0024The foregoing and other features of the present disclosure will become more fully apparent from the following description and appended claims, taken in conjunction with the accompanying drawings. Understanding that these drawings depict only several embodiments in accordance with the disclosure and are not to be considered limiting of its scope, the disclosure will be described with additional specificity and detail through use of the accompanying drawings.

0025<figref idref="DRAWINGS">FIG. <b>1</b></figref> is a block diagram of an embodiment of a system for facilitating delivery and pick-up actions.

0026<figref idref="DRAWINGS">FIG. <b>2</b></figref> is a perspective view of an embodiment of a receptacle to facilitate delivery and pick-up actions.

0027<figref idref="DRAWINGS">FIG. <b>3</b></figref> is a front view of an embodiment of plurality of receptacles for facilitating delivery and pick-up actions.

0028<figref idref="DRAWINGS">FIG. <b>4</b>A</figref> is a process flow diagram for an embodiment of a delivery and pick-up system.

0029<figref idref="DRAWINGS">FIG. <b>4</b>B</figref> is a process flow diagram for and embodiment of a pick-up and delivery system.

0030<figref idref="DRAWINGS">FIG. <b>5</b></figref> is a flow chart depicting an embodiment of a process for gathering sensor data from a receptacle.

0031<figref idref="DRAWINGS">FIG. <b>6</b></figref> is a flow chart depicting an embodiment of a process for determining whether an event was a delivery or pick-up event.

0032<figref idref="DRAWINGS">FIG. <b>7</b></figref> is a process flow diagram of exception handling for a receptacle door that is not closed.

0033<figref idref="DRAWINGS">FIG. <b>8</b></figref> is a process flow diagram of IR beam exception handling.

DETAILED DESCRIPTION

0034In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the Figures, may be arranged, substituted, combined, and designed in a wide variety of different configurations, all of which are explicitly contemplated and make part of this disclosure.

0035Some embodiments disclosed herein relate generally to an item receptacle for use in confirming delivery and pick-up of items. The item receptacle can include sensors to determine when a receptacle door is opened, when an item is placed in or taken out of the receptacle, and when a receptacle door is closed. The item receptacle can be in communication with a central server or central database and be able to transmit and receive information related to the delivery and pick-up of items at the receptacle.

0036In some embodiments, the item receptacle may be part of a plurality of item receptacles in a common location. The plurality of item receptacles can share a common communication link. The item receptacle or plurality of item receptacles are in communication with a processing unit that controls scanners, detectors, sensors, and communication links for the item receptacle.

0037In some embodiments, an item can be a “smart” item, such as a “smart mailpiece.” A smart mailpiece can have hardware and/or software embedded in the mailpiece itself, in the contents of a mailpiece, and the like. A recipient of the mailpiece, or any user, may be able to interact with the mailpiece, with additional content, and the like using a computing device.

0038<figref idref="DRAWINGS">FIG. <b>1</b></figref> depicts a block diagram of a system for facilitating delivery and pick-up actions and other notifications. The system <b>100</b> comprises a central hub <b>110</b>, a sender interface <b>120</b>, an item tracking system <b>130</b>, an item intake system <b>140</b>, a receptacle interface <b>150</b>, and a delivery device <b>160</b>. The system <b>100</b> can be part of a distribution network, such as the United States Postal Service (USPS). The distribution network may own any or all of the components of the system <b>100</b>, or may provide instructions, such as an API or the like to allow other entities to access the central hub <b>110</b> to either provide instructions, identify items, or obtain information about items. In some embodiments, the central hub <b>110</b> can be a single computer, a network of computers, a server, and the like. in some embodiments, the central hub <b>110</b> can be a software program that runs on a computer, a network, a server, and the like.

0039The central hub <b>110</b> is in communication with the sender interface <b>120</b>, the item tracking system <b>130</b>, the item intake system <b>140</b>, the receptacle <b>150</b> and the delivery device <b>160</b>. This communication can be wired or wireless communication. The central hub <b>110</b> comprises a memory <b>112</b> for storing information regarding items, including distribution items. The information stored can be that which was received from any of the other components of the system. The central database can also comprise a processor <b>114</b> configured to interface with the memory <b>112</b> and other components of the system <b>100</b>, and to analyze the information in the memory <b>112</b> to generate notifications and cause further actions to occur based on the information in the memory <b>112</b>.

0040The sender interface <b>120</b> is in electronic communication with the central hub <b>110</b> in order to transmit and receive item information and item notifications. The sender interface <b>120</b> can be embodied in a mobile computing device, a desktop computing device, can be an application running on a computing platform, a web interface, or a dedicated interface with the central hub <b>110</b>. The sender interface <b>120</b> is configured to receive sender input regarding items to be sent, including an item identifier, a delivery point, and any other desired information. In some embodiments, the sender interface <b>120</b> receives item information from a sender, shipper, or mailer, the information identifying the mailpiece, and/or a unique identifier to be stored in an identifier tag, such as a RFID tag, Bluetooth low energy tag, and the like, that is located on or in the item or an identifier associated with the identifier tag. In some embodiments, including special handling instructions such as delivery times, request for delivery and pick-up confirmation, and the like. The sender interface <b>120</b> is further configured to receive additional information or content, such as a video, a coupon, an offer, an internet link, or any other additional or supplemental information. The sender interface <b>120</b> can provide the additional information to be associated with the unique identifier so a user can access the additional information from the item when it is delivered. The association between the additional information and the unique identifier of the item can be stored in the central hub <b>110</b>.

0041The item tracking system <b>130</b> can comprise a memory and a processor, or may be a network or server, or may run as a program on another processor within the system <b>100</b>. The item tracking system <b>130</b> comprises processing equipment, scanners, and databases configured to track the delivery status of each item in the distribution network. The item tracking system receives item tracking information for items moving throughout the distribution network including every scan or read of the items, to track the status, location, or position of each item in the distribution network. The item tracking system <b>130</b> sends item tracking information to the central hub <b>110</b> to update the central hub <b>110</b> regarding the delivery progress of items whose information is stored in the central hub <b>110</b>.

0042The item intake system <b>140</b> may be a component of the item tracking system, or it may be its own system, comprising a memory and a processor and item scanning equipment. The item intake system is in communication with the sender interface <b>120</b> and can receive information regarding the induction of items from the sender into the distribution network, including when items will be physically supplied to the distribution network for induction. The item intake system <b>140</b> also communicates with the central hub <b>110</b> to inform the central database when an item is going to be, or has been, physically inducted into the distribution network. The item intake system <b>140</b> comprises item processing equipment, sorting equipment, an imager and/or a scanner, and the like. The information regarding the destination of an item can be obtained from the item using the imager and/or the scanner to read, scan, or interpret a destination or computer readable code on the item.

0043The receptacle <b>150</b> comprises a communication link to communicate receptacle and item status to the central database. The receptacle can comprise a control unit <b>152</b>. The receptacle <b>150</b> will be described in greater detail below.

0044The delivery device <b>160</b> can be physically located with or associated with a delivery resource, such as a carrier, vehicle, and the like. The delivery device <b>160</b> can comprise a scanner <b>162</b> configured to read a computer readable code on an item to be delivered to the receptacle <b>150</b>. The scanner can be a camera <b>162</b>, a barcode scanner, an IR detector, a Bluetooth-enabled scanner, or a combination of the above. The delivery device <b>160</b> also comprises a location sensor <b>164</b> configured to provide the real-time geographic location of the delivery device <b>160</b> and to track and store the path of the delivery device <b>160</b>, the data comprising information such as breadcrumb data. The location sensor <b>164</b> provides a geographic location using a global positioning system (GPS), a cellular signal, a Wi-Fi signal, or the like. The delivery device <b>160</b> is in wired or wireless electronic communication with the receptacle <b>150</b> and the central hub <b>110</b>. The delivery device <b>160</b> provides delivery status information to the central hub <b>110</b>. The delivery device <b>160</b> can also communicate and receive receptacle status information from the receptacle <b>150</b>, including position or location information.

0045<figref idref="DRAWINGS">FIG. <b>2</b></figref> depicts an embodiment of an item receptacle <b>200</b>. The item receptacle <b>200</b> is depicted having one transparent side and a transparent top for ease of illustration. The item receptacle can be similar to the receptacle <b>150</b> described above, including having similar electronic communication configurations and capabilities. The item receptacle <b>200</b> comprises an external surface <b>210</b> and an interior volume <b>220</b> enclosed by the external surface. A portion of the external surface <b>210</b> is shown transparent for ease of discussion and illustration.

0046The interior volume <b>220</b> can enclose a processor <b>222</b>, a power supply <b>224</b>, and a wireless communication device <b>226</b>. In some embodiments, the processor <b>222</b> comprises a memory containing instructions to control the processor and the other electrical components of the item receptacle <b>200</b> as will be described below. The processor <b>222</b> memory can also store information received from electronic components described herein. These components can be configured as a single unit, or can be discrete components. In some embodiments, these components can be external to the interior volume <b>220</b>, and can be in a weatherproof enclosure. The power supply <b>224</b> can be connected to a solar panel <b>228</b>. The solar panel <b>228</b> can be attached the top of the item receptacle <b>200</b>, or can be attached to a support remote from the item receptacle <b>200</b>, which is wired to the power supply <b>224</b> so as to transmit electricity to the power supply <b>224</b>. The power supply <b>224</b> is in electrical connection with the processor <b>222</b> and the wireless communication device <b>226</b>, as well as with other electrical components that will be described below.

0047In some embodiments, the power supply <b>224</b> is connected to a source of power, such as a transmission line, a plug, a building electrical system, or any other power source, as desired. For example, where the item receptacle is installed in an apartment building or the like, the power supply <b>224</b> can be connected to the building's power supply. In a remote setting, the power supply <b>224</b> can be connected to the solar panel <b>228</b>. In some embodiments, such as with a cluster box unit (CBU) a common power supply <b>224</b> and processor <b>222</b> can be used for multiple item receptacles <b>200</b> or multiple internal volumes <b>220</b>.

0048The item receptacle further comprises a door <b>230</b>. The door <b>230</b> is openable to provide access to the interior volume <b>220</b>. The door <b>230</b> comprises a securement feature <b>236</b>, such as a lock, latch, or the like, which can securely maintain the door <b>230</b> in the closed position, and which can selectively allow access to the interior volume <b>220</b> of the item receptacle <b>200</b>. The door <b>230</b> comprises a status sensor comprising a first sensor <b>232</b> disposed on an inner surface <b>231</b> of the door <b>230</b> and a second sensor <b>234</b> disposed within the interior volume <b>220</b> of the item receptacle <b>200</b>. The status sensor detects the status of the door, such as whether the door is open, closed, unlocked, partially closed, left open, or other desired status. The first and second sensors <b>232</b> and <b>234</b> can be electrically powered and can return or provide an electronic signal corresponding to the door status. In some embodiments the first sensor <b>232</b> and the second sensor <b>234</b> are a magnetic sensor configured to sense whether the door <b>230</b> is open or closed depending on the magnetic coupling between the first sensor <b>232</b> and the second sensor <b>234</b>. In some embodiments, the first sensor <b>232</b> and the second sensor <b>234</b> can be an electromagnetic sensing system which detects an interruption or continuity of an optical, IR, microwave, radio, or other electromagnetic signal to determine the position of the door <b>230</b>.

0049In some embodiments, the first sensor <b>232</b> and/or the second sensor <b>234</b> are light sensors that detect light in the internal volume of the item receptacle <b>200</b>. The light sensor can operate by sensing an increase in ambient light within the internal volume <b>220</b> of the item receptacle <b>200</b> that would occur when the door <b>230</b> is opened. In some embodiments, where one of the first sensor <b>232</b> and the second sensor <b>234</b> is a light sensor, the item receptacle <b>200</b> need not have another sensor. In some embodiments, the first and second sensors <b>232</b>, <b>234</b> can act as a main light sensor and a backup light sensor. In some embodiments, the item receptacle has first and second sensors <b>232</b>, <b>234</b> configured as magnetic sensors, and also has a light sensor.

0050The first and/or the second sensors <b>232</b>, <b>234</b> are in electrical contact with the power supply <b>224</b>, and in electronic communication with the processor <b>222</b> and/or the wireless communication device <b>226</b>. The first sensor <b>232</b> and the second sensor <b>234</b> can communicate a status signal, such as a door open signal, door closed signal, or door cycle signal, including current door status signal, to the processor <b>222</b>. The processor can send the signals received from the first and second sensor <b>232</b>, <b>234</b> to the central hub <b>110</b> via the wireless communications device <b>226</b>.

0051In some embodiments, for example, where a number of item receptacles <b>200</b> are located at a common place, such as at a CBU, or in an apartment building, the door <b>230</b> may be a rear door which provides a carrier access to all of the item receptacles <b>200</b> in the CBU.

0052The item receptacle <b>200</b> or cabinet <b>300</b> can comprise a scanner <b>240</b> disposed on or mounted on an inner surface of the item receptacle <b>200</b> as described elsewhere herein. The scanner <b>240</b> can be connected to with the power supply <b>224</b> and the processor <b>222</b>. The scanner <b>240</b> is positioned to be able to scan a computer readable code <b>204</b> located on an item <b>202</b> disposed in the internal volume <b>220</b> of the item receptacle <b>200</b>. The scanner can be an optical scanner, a barcode scanner, a RFID reader, near field communication, such as Bluetooth®, transceiver, and the like. In some embodiments, the scanner <b>240</b> emits electromagnetic radiation <b>242</b>, such as a laser, LED light, and the like, to read the computer readable code <b>204</b> on the item and transmits the computer readable code <b>204</b>, or the information encoded within the computer readable code <b>204</b> to the control unit <b>150</b>. In some embodiments, more than one scanner <b>240</b> or type of scanner <b>240</b> can be positioned within the interior volume <b>220</b> of the item receptacle <b>200</b> to ensure that a computer readable code <b>204</b> can be read regardless of the orientation of the item <b>202</b> within the item receptacle <b>200</b>.

0053The item receptacle <b>200</b> can further comprise an item sensor <b>250</b>. The item sensor <b>250</b> can comprise an emitter to emit a beam <b>252</b>, such as an infrared signal, a reflector, and/or a sensor to detect a reflected beam <b>252</b>. The item detector can be positioned near a bottom interior surface of the item receptacle <b>200</b>. In some embodiments, the item sensor <b>250</b> can be positioned on a top and/or bottom interior surface of the item receptacle <b>200</b>, near the door <b>230</b>. This positioning allows the item sensor <b>250</b> to detect the presence of the item <b>202</b> when the item <b>202</b> is placed or inserted into the item receptacle <b>220</b>. The item <b>202</b> will interrupt the beam <b>252</b> between the emitter and the reflector and produce a signal indicative of the presence of the item <b>202</b>. The item sensor <b>250</b> receives power from the power supply <b>224</b>, and communicates signals indicative of the presence or absence of the item <b>202</b> to the processor <b>222</b>. In some embodiments, the item sensor <b>250</b> is disposed on the side wall, back wall, or door of the receptacle such that as an item is inserted into the receptacle <b>200</b>, the item will break or interrupt the beam <b>252</b>, but that once the item is inserted into the receptacle <b>200</b>, the item will move out of the path of the beam <b>252</b>, and the beam <b>252</b> will be restored. This can happen, for example, when an item such as a mail piece is inserted at an orientation interrupting the beam <b>252</b>, which item will then fall or lay flat on the bottom of the receptacle <b>200</b>, out of the path of the beam <b>252</b>.

0054The wireless communication device <b>226</b> can send information and signals to the central hub <b>110</b>, such as through a cellular, WiFi, Bluetooth, or other wireless communication protocol.

0055In some embodiments, the components of the item receptacle, including the processor <b>222</b>, the power supply <b>224</b>, the wireless communication device <b>226</b>, the solar panel <b>228</b>, the first and second sensors <b>232</b>, <b>234</b>, the sensor <b>240</b>, and the item sensor <b>250</b>, or any combination of these components, can be provided as a kit for a retrofit of an existing item receptacle <b>200</b>. For example, a user having an existing mailbox, can obtain a kit comprising these components, sized, shaped, and designed to fit a standard or custom—type mailbox, including adhesive, attachment devices, screws, cables, wires, and the like, needed for the retrofit. For example, the processor <b>222</b>, the power supply <b>224</b>, and the wireless communication device <b>226</b> can be a computing unit, such as a raspberry pi 3, or other similar device.

0056<figref idref="DRAWINGS">FIG. <b>3</b></figref> depicts a front view of an embodiment of a plurality of item receptacles <b>200</b> in a common location, such as in a CBU. A cabinet <b>300</b> comprises a plurality of item receptacles <b>200</b>. The cabinet <b>300</b> has a control unit <b>352</b> disposed thereon. The control unit <b>352</b> comprises a power source <b>353</b>, a communication feature <b>354</b>, a processor <b>356</b>, and a memory <b>358</b> in communication with each other. The power source <b>353</b> provides power to the control unit <b>352</b> and to the sensors and detectors on the item receptacle <b>200</b>. The power source <b>353</b> can be a solar panel, a battery, or a combination of both. In some embodiments, the power source <b>353</b> can be an attachment to a power grid, generator, or other power source. The control unit <b>352</b> can be similar to the processor <b>222</b>, power supply <b>224</b>, and wireless communication device <b>226</b> described above, and these terms can be used interchangeably without departing from the scope of the present disclosure. Although the embodiments of <figref idref="DRAWINGS">FIG. <b>2</b></figref> and <figref idref="DRAWINGS">FIG. <b>3</b></figref> are different, a person of skill in the art, guided by this disclosure, will understand that the features of each can be interchanged, or referred to interchangeably, or that features described with regard to either <figref idref="DRAWINGS">FIG. <b>2</b></figref> or <figref idref="DRAWINGS">FIG. <b>3</b></figref> can be applied to the other figure.

0057The processor <b>354</b> is configured to control the operation of the sensors and detectors on the item receptacles <b>200</b>, to receive the signals from the various sensors and detectors on the item receptacles <b>200</b>, and to store the received signals in the memory <b>356</b>. The memory <b>356</b> can also store operation instructions for directing the operation of the processor <b>354</b>. The processor <b>354</b> also controls the operation of the communication feature <b>358</b>.

0058The communication feature <b>358</b> can be a wired or wireless communication device for sending and receiving signals associated with the item receptacles <b>200</b> in the cabinet <b>300</b>. The communication feature <b>358</b> can communicate via cellular 3G, 4G, LTE, or other networks. The communication feature <b>358</b> can communicate via LAN, WAN, Wi-Fi, near field communication, or any other desired method or protocol. The communication feature <b>358</b> can communicate with the central hub <b>110</b> and with the delivery device <b>160</b>. In some embodiments, the control unit <b>352</b> can be similar to

0059An exemplary embodiment of the operation of system <b>100</b> and its components will now be described with reference to <figref idref="DRAWINGS">FIG. <b>4</b>A</figref>. <figref idref="DRAWINGS">FIG. <b>4</b>A</figref> depicts an embodiment of a process flow diagram for the pick-up and delivery system. <figref idref="DRAWINGS">FIG. <b>4</b>A</figref> depicts operation of the system using the USPS and a mailpiece as an example. It will be understood that the USPS example does not limit the present disclosure. As used herein, the term mailpiece can be synonymous with the term item, and can be used interchangeably therewith.

0060The process begins when a mailpiece <b>410</b> is generated. The mailpiece <b>410</b> is generated by a sender, shipper, or mailer. The sender creates an electronic record of the mailpiece <b>410</b>. The electronic record of the mailpiece <b>410</b> includes information regarding the mailpiece including shipper ID, recipient, destination, service class, and other information. The shipper ID, recipient, destination, service class, and other information created by the sender can be encoded in a computer readable code on the mailpiece <b>410</b>. The electronic record of the mailpiece <b>410</b> is submitted to the distribution network, and to the central hub <b>110</b> via the sender interface <b>120</b>. The electronic record can contain a field or data entry indicating that the mailpiece <b>410</b> is to be tracked for delivery and pick-up. In some embodiments, the indication that the mailpiece <b>410</b> should be tracked for delivery and pick-up can be provided by associating an existing field in the electronic record, such as shipper identification, with the desired service in the central hub <b>110</b>. Thus, the electronic record would not need to have a specific field indicating tracking delivery and pick-up is desired, but that the electronic record would include a shipper identifier which the central hub <b>110</b> recognizes as requesting delivery and tracking pick-up as described herein. In some embodiments, the computer readable code on the mailpiece can indicate that delivery and pick-up notifications are requested. This can be included in a service class or other value within the computer readable code.

0061The sender interface <b>120</b> can also send a signal to the item intake system <b>140</b>, via the central hub <b>110</b>, or directly, indicating when (day, time, etc.) the physical mailpiece <b>410</b> will be provided to a location in the distribution network, such as when the mailpiece <b>410</b> will be delivered to a post office for induction into the mailstream. The item intake system <b>140</b> communicates the intended time for delivery of the mailpiece <b>410</b> to the central hub <b>110</b>. This communication can instruct the processor <b>114</b> to commence an algorithm or routine to analyze incoming data from the item tracking system <b>130</b> to identify when the mailpiece <b>410</b> is scanned on processing equipment.

0062The mailpiece is delivered to a post office or induction facility of the distribution network, and the mailpiece is scanned on mail processing equipment <b>420</b> where data for mailpiece <b>410</b> is captured. The data can include a computer readable code, such as an intelligent mail barcode (IMb). The captured data is stored in the memory of the item tracking system, and is sent to the central hub <b>110</b>. The processor <b>114</b> analyzes the captured data and compares the captured data to the item information received from the sender interface <b>120</b>. If the processor <b>114</b> identifies that the captured data corresponds to a mailpiece <b>410</b> whose item information was provided, or is intended for delivery and pick-up tracking, the captured data is stored in the memory <b>114</b>. This process can repeat for each scan event on the item intake system <b>140</b>, and on subsequent scans, sorting, or processing on mail processing equipment throughout the distribution network, as the mailpiece <b>410</b> moves from induction point to its intended destination. While or after being processed on the mail processing equipment <b>420</b>, item information, including item induction information, can be sent to the mailer or sender who generated or is associated with the mailpiece <b>410</b>.

0063The mailpiece <b>410</b> will arrive at a delivery hub, or at a unit or local delivery facility prior to being sent out for delivery to the final destination. The delivery hub or local delivery facility can be a local postal facility, such as where a carrier collects items for delivery along the carrier's assigned route. As the mailpiece <b>410</b> moves to the delivery hub and/or is sorted prior to going out for delivery, it is scanned by the item tracking system <b>130</b>. At the delivery hub, a final sorting of the mailpiece <b>410</b> can occur. When the final sort is identified by the item tracking system <b>130</b>, the tracking information is sent to the central hub <b>110</b>, where the central database identifies that the mailpiece <b>410</b> is out for delivery. The central hub <b>110</b> can store the identity of all the receptacles <b>150</b> in the distribution network. When the final sort or scan identifies the mailpiece <b>410</b> is out for delivery, this can trigger the processor <b>114</b> to look for signals from the receptacle <b>150</b>, via the wireless communication device <b>226</b>, or the control unit <b>352</b> for the item receptacle <b>200</b> for which the mailpiece <b>410</b> is intended.

0064The mailpiece <b>410</b> is placed on or in a delivery resource <b>430</b>, such as a vehicle, a carrier, and the like, and a record is created in the central hub <b>110</b> that the item is out for delivery. The delivery resource <b>430</b> carries the mailpiece <b>410</b> to a receptacle <b>200</b>.

0065At the receptacle <b>200</b>, the delivery resource <b>430</b> places the mailpiece <b>410</b> into the receptacle <b>200</b>. the receptacle <b>200</b> will record the events associated with operating the receptacle <b>200</b> and communicate the signals to the central hub <b>110</b>. The central database will then analyze the signals from the receptacle to identify whether the signals indicate a delivery. This process is described in greater detail below. The receptacle <b>200</b> or cabinet <b>300</b> sends a signal to the central hub <b>110</b> regarding delivery or pick-up of the mailpiece <b>410</b>. The central hub <b>110</b> stores the signals regarding delivery or pick-up of the mailpiece <b>410</b>, and stores additional information, such as date and time of pick-up, how much time elapsed between delivery of the mailpiece <b>410</b> and pick-up of the mailpiece <b>410</b> by the recipient, and the like.

0066In the case where a delivery event is detected, the central hub <b>110</b> can generate and send a message to a recipient <b>470</b> that the mailpiece <b>410</b> has been delivered. The message can include additional information, such as the time of delivery, place of delivery, if different from a standard address (e.g., a P.O. box, a parcel locker, and the like), or any other information the distribution network or sender would like to communicate to the recipient. The message can be sent via an email, text, phone call, via a notification from an application on a smartphone, a social media alert or update, or any other desired method.

0067The central hub <b>110</b> also sends information to a sender, mailer, and/or the generator <b>460</b> of the item <b>410</b>. This information can include delivery confirmation, delivery date and time, delivery location, and the like.

0068When the receptacle or cabinet <b>300</b> detects a pick-up event, as will be described in greater detail below, the central hub <b>410</b> can send a message to the recipient <b>470</b> that the mailpiece <b>410</b> was picked up. This can be a security measure, or information to multiple residents of a household that the mail has been collected. In some embodiments, the central hub <b>410</b> can send messages to more than one person associated with a delivery location, such as one or more of the residents at a particular delivery location or address.

0069The central hub <b>110</b> can also send pick-up confirmation or information to the sender <b>460</b> of the mailpiece <b>410</b>. In some embodiments, the central hub <b>110</b> can prepare reports for all mailpieces <b>410</b> associated with a particular mailer or sender <b>460</b>. The reports can include time from induction of the mailpiece <b>410</b> to delivery and pick-up, and other desired information.

0070<figref idref="DRAWINGS">FIG. <b>4</b>B</figref> depicts an embodiment of a process flow diagram for the pick-up and delivery system. The embodiment of <figref idref="DRAWINGS">FIG. <b>4</b>B</figref> is similar to that depicted in <figref idref="DRAWINGS">FIG. <b>4</b>A</figref>. The mailpiece <b>410</b> is inducted into the mailstream or the distribution network via the mail processing equipment <b>420</b>, or the item intake system <b>140</b>. In some embodiments, the mail processing equipment <b>420</b> is the item intake system <b>140</b> or is similar to the item intake system <b>140</b>.

0071In some embodiments, the mailpiece <b>410</b> can comprise an identifier tag <b>412</b>, such as an RFID tag, a Bluetooth tag, or other similar hardware. The identifier tag <b>412</b> stores or encodes a unique identifier, such as an alphanumeric string, a particular frequency, a Bluetooth identifier, or any other identifier. The unique identifier is associated with the mailpiece <b>410</b>. The sender or mailer can supply this number to the distribution network, such as to the central hub <b>110</b>. This can occur when an electronic manifest is provided to the distribution network, or can be supplied via the sender interface <b>120</b> when the mailpiece <b>410</b> is registered. In some embodiments, the item intake system <b>140</b>, or the mail processing equipment <b>420</b> can read the unique identifier, and associate the unique identifier with the mailpiece <b>410</b>. The association can be stored in the memory <b>112</b> to be accessed as will be described later. The mailer or sender can, via the sender interface <b>120</b>, add additional content associated with the unique identifier, as will be described elsewhere herein.

0072After the carrier delivers the mailpiece <b>440</b> as described above, the mailpiece <b>410</b> is deposited into the item receptacle <b>200</b>. In some embodiments, the mailpiece <b>410</b>, within the item receptacle <b>200</b>, is in proximity to the wireless communication device <b>226</b>. The wireless communication device can read an RFID tag, form a Bluetooth connection, a near field communication (NFC) link, or other similar communication. In some embodiments, the mailpiece <b>410</b> interacts with the wireless communication device <b>226</b>. When the wireless communication device <b>226</b> detects the mailpiece <b>410</b>, the wireless communication device <b>226</b> receives the unique identifier from the identifier tag <b>412</b>, the wireless communication device <b>226</b>, together with the processor <b>222</b>, sends a signal confirming delivery of the mailpiece <b>410</b>. Similarly, after the connection with the mailpiece <b>410</b> is made, and the mailpiece <b>410</b> is removed from the item receptacle <b>200</b>, the wireless communication device <b>226</b> loses the connection with the mailpiece <b>410</b>. The processor <b>222</b> and the wireless communication device <b>226</b> determine that the mailpiece <b>410</b> has been removed from the item receptacle <b>200</b>, or, in other words, that the mailpiece <b>410</b> has been picked up. The delivery and pickup determinations or detections can be transmitted to the central hub <b>110</b>, can be transmitted to the recipient <b>470</b>, and transmitted to the sender <b>460</b>.

0073In some embodiments, when the recipient <b>470</b> picks up a mailpiece <b>410</b>, the identifier tag <b>412</b> can interact with the recipient's mobile computing device <b>472</b>. The mobile computing device can be, for example, a Bluetooth enabled smartphone. When the identifier tag <b>412</b> connects to the mobile computing device <b>472</b>, such as via NFC, or Bluetooth, including Bluetooth 5.0 protocol, the identifier tag <b>412</b> can provide a user additional content. For example, the identifier tag <b>412</b> can provide exclusive video content, such as via an internet link, an application on the mobile computing device <b>412</b>, and the like. In some embodiments, the identifier tag <b>412</b> can transmit a coupon or offer to the mobile computing device <b>472</b>, or can provide a link to a website or other location where a coupon or offer can be downloaded to the mobile computing device <b>472</b>. The coupon or offer can be for a company, service, or other entity associated with the mailpiece <b>410</b>, or can be associated with the mailer or sender <b>460</b>. In some embodiments, the recipient <b>470</b> can place the mobile computing device <b>472</b> on the mailpiece <b>410</b>, and the mobile computing device <b>472</b> will display a website, a video, or other content associated with the identifier tag <b>412</b>.

0074In some embodiments, the location of additional content is stored in the identifier tag <b>412</b> itself, which communicates the location to the mobile computing device <b>472</b>. In some embodiments, the mobile computing device <b>472</b> detects or receives an identifier from the identifier tag <b>412</b>, and the mobile computing device <b>472</b> communicates with the central hub <b>110</b>, provides the identifier from the identifier tag <b>412</b>, and the central hub <b>110</b> provides the additional content associated with the mailpiece <b>410</b>.

0075In some embodiments, the mailpiece <b>410</b> can be contained within a sleeve (not shown), such as a faraday envelope, that shields the identifier tag <b>412</b> from connecting to a nearby Bluetooth, RF, NFC, or other similar device. When the recipient <b>470</b> removes the mailpiece <b>410</b> from the shield sleeve, the identifier tag <b>410</b> can be enabled to interact with the mobile computing device <b>472</b>.

0076In some embodiments, the identifier tag <b>412</b> can interact with an in-home communications device <b>474</b>, such as Amazon Echo with Alexa, Google Home, Ski, Cortana, and the like. For example, the identifier tag <b>412</b> can encode a command for the in-home communications device <b>474</b> which can order an item associated with the mailpiece, provide a coupon or discount for an order, or which will cause the in-home communications device <b>474</b> to call up websites, audio, and the like. in some embodiments, the mailpiece <b>410</b> can have printed thereon a custom phrase useable with an in-home communication device <b>474</b> that the recipient <b>470</b> can speak or input to the in-home communication device <b>474</b> to obtain a discount, coupon, promotion, or other benefit from a supplier associated with the mailpiece <b>410</b>.

0077In some embodiments, the mailpiece <b>410</b> and the identifier tag <b>412</b> can communicate with the in-home communications device to provide offers, services, and the like. For example, a merchant can send a Bluetooth enabled mailpiece <b>410</b> to a recipient. When the mailpiece <b>410</b> having the Bluetooth identifier tag <b>412</b> come into the recipient's home, the identifier tag <b>412</b> can communicate with an in-home communications device <b>474</b>. When the recipient is shopping on-line for merchandise, goods, or services provided by the merchant who sent the mailpiece <b>410</b>, the identifier tag <b>412</b> can provide a signal to the in-home communications device <b>474</b> to provide a discount for the merchant's products, goods, or services. This can occur when the device used for on-line shopping, computer, tablet computer, smartphone, etc., is connected to the same home network as the in-home communications device <b>474</b>. The in-home communication device <b>474</b> can provide a code or identifier from the identifier tag <b>412</b> to a merchant's website or another website to provide the offer or discount.

0078In some embodiments, the identifier tag <b>412</b> can navigate the mobile computing device <b>472</b> to a website to order an item advertised on the mailpiece <b>410</b>. The actions taken by the recipient <b>470</b> and/or the mobile computing device <b>472</b> can be recorded and stored at the central hub <b>110</b>, and/or can be transmitted to or accessed by the sender <b>460</b>.

0079In some embodiments, the identifier tag <b>412</b> can operate with Bluetooth low energy (BLE) can be used to connect to the mobile computing device <b>472</b> without the need to pair or download any additional content. In some embodiments, the identifier tag <b>412</b> can provide reminders, add calendar dates, contact information, and the like to the mobile computing device <b>472</b>. For example, in some embodiments, the identifier tag <b>412</b> can create a calendar appointment corresponding to a sale or special offer, upcoming product release, or other event associated with the content of the mailpiece <b>410</b>. In some embodiments, the identifier tag can cause a contact, such as an address and phone number corresponding to an advertised business or service to be saved to the mobile computing device <b>472</b>.

0080<figref idref="DRAWINGS">FIG. <b>5</b></figref> is a flowchart depicting an embodiment of an exemplary process that occurs when the mailpiece <b>410</b>, or any item, is delivered to the receptacle <b>200</b>. A process <b>500</b> can be used to identify an event at the item receptacle <b>200</b> as a delivery or pick-up event. The process <b>500</b> begins with the door <b>230</b> of the receptacle <b>200</b> in a closed position and the first sensor <b>232</b> and the second sensor <b>234</b> are in proximity to each other to signal that the door <b>230</b> is in a closed position. The control unit <b>352</b> senses or receives a door closed signal and a signal from the item sensor <b>250</b>. In the case where the receptacle <b>200</b> is empty, the item sensor <b>250</b> will detect that the signal is uninterrupted, indicating that there is nothing in the receptacle. The control unit <b>352</b> can sample the first and second sensor <b>232</b>, <b>234</b> output at a desired frequency and record door status and item status at a desired frequency and generate a record to store in the memory <b>356</b>. In some embodiments, the control unit <b>352</b> or processor <b>222</b> waits for a change in the door status or item status signals before recording or storing a change in door status. That is, the control unit <b>352</b> updates a door status record or table in the memory <b>356</b> only when the first and second sensors <b>232</b> and <b>234</b> change state of such as changing from coupled to uncoupled. The first and second sensors <b>232</b>, <b>235</b> can also send a door status signal, such as a closed or open signal. The door status can also be recorded in the memory <b>356</b> along with a time the event or door <b>230</b> status was sensed or transmitted.

0081The process <b>500</b> moves to decision state <b>520</b>, where the control unit <b>352</b> looks for a signal indicating a change in door status. If no change in the door status is sensed, the process <b>500</b> returns to block <b>510</b>.

0082If a change in door status is sensed, the process <b>500</b> continues to block <b>530</b>, where the door open status is recorded along with a time at which the door open signal was sensed. For example, when the delivery resource <b>430</b> opens the door <b>230</b> of the receptacle <b>200</b>, the first sensor <b>232</b> and the second sensor <b>234</b> are moved out of alignment or proximity, are magnetically decoupled, or an IR, laser, photoelectric, or other signal is interrupted. The first and second sensor <b>232</b>, <b>234</b> detect the door <b>230</b> is open, and transmit the door open signal to the control unit <b>352</b>. The transmission of the door open signal indicates that a change in door status has been detected. The control unit <b>352</b> can record a change in door status, and can also record a door status, either open or closed, and an associated time.

0083The process then moves to decision state <b>540</b> wherein the control unit <b>352</b> determines whether there has been a change in item status as indicated by the item sensor <b>250</b>. If the item sensor <b>250</b> detects a change in item status, such as due to changing the state of the item sensor <b>250</b>, as can happen as when an item interrupts the item sensor <b>250</b>, the item sensor generates a signal and transmits the signal to the control unit <b>352</b> indicating the change in state of the item sensor <b>250</b>. The item sensor <b>250</b> can also send a signal whether the item sensor <b>250</b> signal was interrupted, indicating the presence of an item in the receptacle <b>200</b>, or whether the signal is uninterrupted, indicating the absence of an item in the receptacle <b>200</b>. If a change in state of the item sensor <b>250</b> occurs, the process <b>500</b> moves to block <b>550</b> wherein the control unit records the change in state of the item sensor <b>250</b> for the receptacle <b>200</b> and the associated time. The presence or absence of an item and the time of the event can be recorded in the control unit <b>352</b>.

0084For example, and as will be described in greater detail below, a delivery event can be identified when a door open signal is detected, and thereafter an interruption in an item sensor <b>250</b> signal is detected, and the interrupted signal remains interrupted. This indicates that an item <b>202</b> is in the item receptacle <b>200</b>. A pick-up event can be identified when a door open signal is detected, and thereafter an interrupted item sensor <b>250</b> signal is removed, and the item status sensor signal returns to an uninterrupted state. This indicates an item <b>202</b> has been removed from the item receptacle <b>200</b>.

0085If no change in state of the item sensor <b>250</b> is detected in decision state <b>540</b>, then the process moves to decision state <b>560</b>, wherein the control unit <b>352</b> looks to see whether there has been another change in the door status. The determination of a change in door status, or an indication of door status as being either open or closed can be similar to that described above with regard to block <b>520</b>.

0086If no change in door status is detected, the process returns to decision state <b>540</b> and awaits a change in item status. If a change in door status is detected in decision state <b>560</b>, such as a closed signal is sensed following the open signal, the process <b>500</b> moves to block <b>580</b>, wherein the scanner <b>240</b> activates to scan the item in the receptacle <b>200</b>. The scanner <b>240</b> scans the item and reads a computer readable code or takes an optical image of the item, and transmits the information encoded in the computer readable code or the image of the item to the control unit <b>352</b>. In some embodiments, in state <b>540</b> the item sensor <b>250</b> may not detect an item in the receptacle <b>200</b>, and thus, the scanner need not be activated to scan the receptacle <b>200</b>. In some embodiments, the receptacle may not comprise an item sensor <b>250</b>, and the scanner <b>240</b> is activated following each open and close cycle of the door to detect whether an item is in the receptacle <b>200</b>.

0087If the scanner <b>240</b> newly detects an item after an interruption in the item sensor <b>250</b>, a delivery event can be identified. If, after an interruption in the item sensor <b>250</b>, the scanner <b>240</b> is activated, but no item <b>202</b> is identified in the item receptacle <b>200</b>, a pick-up event can be identified, as will be described in detail below with regard to <figref idref="DRAWINGS">FIG. <b>6</b></figref>.

0088The process <b>500</b> moves to block <b>590</b>, wherein event information is transmitted to the central hub <b>110</b>. In some embodiments, the control unit <b>352</b> transmits information about the door status and changes, the item status, and information obtained from the scanner <b>240</b>. The control unit <b>352</b> can also transmit a unique serial number or unique identifier corresponding to the cabinet <b>300</b> on which the control unit <b>352</b> is located. Where a cabinet <b>300</b> comprises a plurality of receptacles <b>200</b>, each receptacle <b>200</b> can be assigned a unique identifier that is recorded in the control unit <b>352</b> along with any status signals from sensors in that receptacle <b>200</b>. The unique identifier of the receptacle <b>200</b> is transmitted with the door status, item status, and scanner information to identify the receptacle <b>200</b> for which the door status and item status have been transmitted. In some embodiments, the item sensor <b>250</b>, the first sensor <b>232</b>, the second sensor <b>234</b>, and/or the scanner <b>240</b> can each be assigned or associated with a unique identifier, such as a serial number, which can be transmitted together with the door status, item status, and scanner information. This enables the central hub <b>110</b> to identify which receptacle the sensor information is received from, as the central hub <b>110</b> has a record of the unique identifiers for the item sensor <b>250</b>, the first sensor <b>232</b>, the second sensor <b>234</b>, and/or the scanner <b>240</b>, and associates these unique identifiers with a particular receptacle <b>200</b>, or with a particular delivery point, such as an address.

0089The central hub <b>110</b> can receive the information and process the information as will be described elsewhere herein. The process <b>500</b> then ends at block <b>595</b>.

0090In some embodiments, the event information is transmitted to the central hub <b>110</b> as soon as it is received. For example, as soon as the door is detected as being opened, the door open signal and change in status can be transmitted or sent to the central database. In some embodiments, the control unit <b>352</b> is configured to communicate or transmit signals over a shorter range. For example, the control unit <b>352</b> is configured to transmit information to the delivery device <b>160</b> when the delivery device <b>160</b> is within a communication range of the control unit <b>352</b>. In some embodiments, the control unit <b>352</b> and the delivery device <b>160</b> can communication via a Bluetooth, NFC, or any other wireless communication protocol or method. In this case, when the delivery device <b>160</b> is within the communication range of the control unit <b>352</b>, the control unit <b>352</b> identifies a signal from the delivery device <b>160</b> and initiates communication. The control unit <b>352</b> may be awakened by a signal from the delivery device <b>160</b> such that the delivery device <b>160</b> initiates the communication. The control unit <b>352</b> transmits the recorded event data for a specific time period, such as from the time of the last communication with a delivery device <b>160</b>, or for the last 24 hours, or for any other desired time period.

0091In the case of the USPS, a delivery device <b>160</b> is likely to be at the receptacle <b>200</b> or cabinet <b>300</b> once a day. Thus, the control unit <b>352</b> may communicate or transmit data once a day, when the delivery device <b>160</b> is in range. The delivery device <b>160</b> can be configured to communicate the information it receives from the control unit over a cellular or wireless network connection. In some embodiments, the delivery device <b>160</b> can store the received information and transmit the received information to the central hub <b>110</b> when the delivery device <b>160</b> returns to the post office and is connected to a network, server, or other wired or wireless connection.

0092In some embodiments, rather than communicating item sensor and door status signals to the central database, the control unit <b>352</b> may communicate door and item status information and/or scanner information to a receiver within a residence, place of business, or other location associated with the receptacle <b>200</b>. The receiver can be configured by a user, business, consumer, subscriber, or other party to send notifications via SMS, email, or other communication method when an item status changes, such as when the item status on the receptacle <b>200</b> changes. If the item status changes from an item present to an item being absent, the receiver, or the control unit <b>352</b>, or the central database can communicate to a user, consumer, or subscriber that an item has been retrieved from the receptacle <b>200</b> along with a time of the event. If the item status changes from no item present to detecting an item, then the receiver, or the control unit <b>352</b>, or the central database can communicate to a user, consumer, or subscriber that an item has been placed in the receptacle <b>200</b> along with a time of the event.

0093The central hub <b>110</b> uses the event information regarding door status, item status, and scanner information to determine what types of events have taken place and what further actions should be taken, including sending notifications.

0094<figref idref="DRAWINGS">FIG. <b>6</b></figref> depicts a flowchart of an embodiment of a process for determining what type of event, e.g., delivery or pick-up, has occurred at a receptacle <b>200</b>.

0095Process <b>600</b> begins in block <b>610</b> wherein the central database identifies a door open signal, or a change in door status from closed to open for a receptacle <b>200</b>.

0096The process <b>600</b> moves to decision state <b>620</b>, wherein the central database determines whether the opened receptacle <b>200</b> is associated with any items for which delivery and pick-up confirmation is requested. The central hub <b>110</b> has stored item information for items for which delivery and pick-up confirmations have been requested. The central hub <b>110</b> compares door status information for the particular receptacle <b>200</b>, as identified by the unique identifier of the sensors or the receptacle <b>200</b>, with stored associations between unique identifiers and delivery points to identify the delivery point, such as the address, of the receptacle whose door status has changed. The central hub <b>110</b> then queries the item information for items, received from the sender interface <b>120</b>, for which delivery and pick-up confirmation is requested, to determine whether the delivery point whose door status has been changed is scheduled to receive an item, or has an item intended for delivery to the delivery point.

0097The central hub <b>110</b> can also take into account the timing of intake of the item. for example, a certain delivery point may have 2 items intended for delivery to the delivery point, only one of which has requested confirmation of pick-up or delivery. In this case, the central hub <b>110</b> can look at the location of the receptacle <b>200</b>, the location of the intake point of the item for which delivery and pick-up confirmation is requested, and information about the item location in the item tracking system <b>130</b>. If the receptacle whose door status has changed is scheduled to receive an item for which confirmation of delivery or pick-up has been requested, but the item tracking system <b>130</b> shows that the item is not yet out for delivery by a delivery resource, or that the item for which delivery or pick-up confirmation was requested could not logistically be at the delivery point yet, then the central hub <b>110</b> can determine that the door open event is not associated with the item for which delivery or pick-up confirmation has been requested. In this case, the process will move to block <b>630</b> and end.

0098If the central hub <b>110</b> does not find an item for which delivery or pick-up confirmation has been requested intended for the receptacle, the process also moves to block <b>630</b> and ends.

0099If the central hub <b>110</b> identifies an item for which delivery or pick-up confirmation has been requested, and the item tracking system <b>130</b> shows that the item has been sent with the carrier or the delivery resource <b>430</b>, or is out for delivery, then the process <b>600</b> moves to decision state <b>640</b>.

0100In decision state <b>640</b> the central hub <b>110</b> analyzes the item status from the item sensor <b>250</b> for the receptacle <b>200</b> whose door <b>230</b> has been opened. The central hub <b>110</b> can look at the item sensor <b>250</b> status from a time before the door open signal and from a time after the door open signal was received. If the information from the item sensor <b>250</b> shows no item in the receptacle <b>200</b> before the time of the door open signal, and shows a change in the item sensor <b>250</b> state (to sensing an item) at a time after the door open signal and before the door close signal was received, then the process <b>600</b> moves to block <b>650</b> and indicates that a delivery event has occurred.

0101After it has been determined that a delivery event or a pick-up event has occurred, the determination is stored or recorded in blocks <b>650</b> and <b>670</b>, the process <b>600</b> moves to block <b>680</b> wherein the central hub <b>110</b> sends notifications regarding the delivery event or the pick-up event. The item information received from the sender interface <b>120</b> can identify the sender and the recipient and can provide a notification preference for notifying the sender and the recipient of the delivery or pick-up event. The central database can notify the sender or recipient of the occurrence of delivery or pick-up and the time of the delivery or pick-up via a telephone call, an SMS text message, an email, a social media notification, a notification on an application on a computing device, such as a personal computer or smartphone, or the like, according to the sender and recipients preferences. The central hub <b>110</b> can provide real-time notifications to senders and recipients where the control unit <b>352</b> provides real-time information regarding door and item sensor status. In some embodiments, the central hub <b>110</b> provides batch information or notifications, such as where the control unit <b>352</b> transmits door and items sensor information in batches. Following notifications, the process <b>600</b> moves to block <b>690</b> and ends.

0102The central hub <b>110</b> can also compile data regarding delivery and pick-up times and compile service and performance metrics. The central hub <b>110</b> can also analyze delivery and pick-up times to determine when the best time to reach a recipient, or to find a recipient at home may be.

0103The following examples show how it can be determined whether an event is a delivery or pickup event. The events below can be similar to the process depicted in <figref idref="DRAWINGS">FIG. <b>6</b></figref>. For example, the first and second sensor <b>232</b> and <b>234</b> or the item sensor <b>250</b> or both can be assigned serial no. 23190367765 which is known to be associated with 12 Happy Valley Ct., Plano Tex.

0104The door open data may show events at: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0105">12:30:56</li><li id="ul0001-0002" num="0106">15:12:12</li><li id="ul0001-0003" num="0107">18:32:21</li><li id="ul0001-0004" num="0108">06:32:23</li></ul>

0109The central hub <b>110</b> would know that the delivery resource delivered at 12:30:56 due to other systems or delivery device <b>160</b> GPS breadcrumb data (as described below), and that the recipient picked up the item at 15:12:12 on the previous day.

0110For a cabinet <b>300</b> comprising multiple receptacles <b>200</b>, the data for the cabinet <b>300</b> may show the following times associated with sensors having serial numbers as shown below: <ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0111">231907907—23:12:32, 08:59:02</li><li id="ul0002-0002" num="0112">376918662—18:07:12, 08:59:02</li><li id="ul0002-0003" num="0113">918269901—15:06:34, 08:59:02</li><li id="ul0002-0004" num="0114">129846919—14:17:08, 12:37:21, 08:59:02</li><li id="ul0002-0005" num="0115">219836989—09:03:21, 08:59:02,</li><li id="ul0002-0006" num="0116">437312908—08:59:02</li></ul>

0117Because multiple item receptacles <b>200</b> have door open signals at the same time, the central hub <b>110</b> can determine that the delivery resource <b>430</b> delivered items to the cabinet at 08:59:02. The central database <b>100</b> can also determine that the other times can be when recipient picked up the items, or that the items have not yet been picked-up, for example, sensor ID 437312908 shows only the delivery time, and no subsequent door open time. In some embodiments, the item sensor <b>250</b> information need not be analyzed, and the central database can analyze only door status information to determine delivery and pick-up events as described herein.

0118In some embodiments, the cabinet <b>300</b> may be accessible by a delivery resource <b>430</b> using a common door which allows access to all receptacles <b>200</b> in the cabinet <b>300</b>. For example, the cabinet <b>300</b> may have a rear door which allows access to the rear of each receptacle. This door can have a door status sensor that indicates that the rear door is opened, and can record a door open event for each of the plurality of receptacles <b>200</b> in the cabinet <b>300</b>. The central hub <b>110</b> can examine such an event and determine that only a delivery resource can open the rear door, and so this event must be a delivery event. Also, the central hub <b>110</b> can identify that an item sensor <b>250</b> status change occurring soon after this door open event indicates a delivery.

0119If the receptacle <b>200</b> does not have an item sensor <b>250</b>, or if the information from the item sensor <b>250</b> is inconclusive, defective, missing, or otherwise not useable, and if the receptacle <b>200</b> comprises an item scanner <b>240</b>, then the process moves to block <b>660</b>, wherein it is determined whether the scanner <b>240</b> detected and scanned an item in the receptacle. The central hub <b>110</b> analyzes the information from the scanner <b>240</b> to determine whether an item was scanned, and what the item information for the scanned item is. If the item scanner detects an item, then the process <b>600</b> moves to block <b>650</b>, wherein it is determined that a delivery event has occurred. In some embodiments, the scanner <b>240</b> can operate in conjunction with the item sensor <b>250</b>.

0120In some embodiments, where the item sensor <b>250</b> information is not available, such as where an item sensor <b>250</b> is not installed, or is defective, or simply in addition to the item sensor <b>250</b> information, a delivery event of the item <b>202</b> can be confirmed by analyzing the information from the delivery device <b>160</b>, such as GPS location data, time data, item scan data, and the like, in conjunction with the door open signal. To illustrate, the delivery device <b>160</b> provides location data, which can be called GPS breadcrumb, and can show the path taken by the carrier with the delivery device <b>160</b>. On a door open signal from a particular receptacle, the central hub <b>110</b> determines the identity of the delivery device <b>160</b> which is assigned to deliver items to the particular receptacle <b>200</b> for which the door open signal has been received. The central hub <b>110</b> accesses the location data or breadcrumb data for that delivery device <b>160</b>, and identifies the time at which the delivery device was in a geographic vicinity of the receptacle <b>200</b> for which the door open signal was received. If the time of the door open signal is within a time window, or corresponds to a time that the delivery device <b>160</b> was at or near the receptacle <b>200</b>, the central hub <b>110</b> can determine that a delivery event has taken place.

0121In some embodiments, the delivery device <b>160</b> can scan an item prior to depositing the item <b>202</b> in the receptacle <b>200</b>. The GPS location of the delivery device <b>160</b> at the time of the scan of the item intended for delivery to a particular item receptacle <b>200</b> can be stored at the delivery device, transmitted to the control unit <b>352</b> and/or the central hub <b>110</b>. The scan event and the GPS data, in combination with a door open signal, an item status signal, or any combination of the above can be interpreted as a delivery event, because the GPS location and the item scan are indicative of a carrier in the vicinity of the receptacle <b>200</b>, and the door open event and the item sensor <b>250</b> signal are within a time window of the item scan event by the delivery device <b>160</b>.

0122If the breadcrumb data for the delivery device <b>160</b> shows that the delivery device <b>160</b> was at or near the receptacle at a time before the time of the door open signal, and if there was an item for delivery to that receptacle on that day, then the central hub <b>110</b> can determine that the door open event was a pick-up event.

0123Breadcrumb data can be used in conjunction with item sensor <b>250</b> information. For example, if the breadcrumb data from the delivery device <b>160</b> shows that the delivery device <b>160</b> was in a specific geographic area, such as a geofence, associated with the receptacle <b>200</b>, or was near the receptacle <b>200</b> at a time corresponding to when the receptacle <b>200</b> detected an item via item sensor <b>250</b>, or detected a change in state of the item sensor <b>250</b>, then a delivery can be confirmed.

0124In some embodiments, the scanner <b>240</b> information can be used in lieu of information from the item sensor <b>250</b> and the door sensor. For example, if the central hub <b>110</b> receives scan information for an item from a scanner <b>240</b> in a receptacle <b>200</b>, the item information from the scanner <b>240</b> is compared to the item information for items for which delivery and pick-up confirmation has been requested. If the item information from the scanner <b>240</b> matches an item for which delivery or pick-up confirmation is requested, the central database can determine that a delivery event has taken place, without analyzing door open data and item sensor <b>250</b> data.

0125If the item sensor does not indicate the presence of an item, or if the scanner <b>240</b> does not detect an item, the central processor can evaluate the item sensor <b>250</b> status at a point before the time of the door open signal and at a time after the time of the door open signal. If the item sensor <b>250</b> indicated that an item was present in the receptacle <b>200</b> before the time of the door open signal, and that the item sensor <b>250</b> status changed after the time of the door open signal and before the time of a door closed signal, the process <b>600</b> can move to block <b>670</b>, wherein the central hub <b>110</b> determines that a pick-up event has occurred.

0126In some embodiments, the delivery resource <b>430</b> will scan the computer readable code on an item using the delivery device <b>160</b> prior to placing the item in the receptacle <b>200</b>. The central hub <b>110</b> will process the item information from scanned computer readable code from the delivery device <b>160</b> and cross reference the item information with the information from the receptacle regarding the opening of the door <b>230</b> of the receptacle <b>200</b>. If the processor <b>114</b> identifies an open signal from the receptacle <b>200</b> to which the item was to be delivered at or near the same time as a scan signal from the delivery device <b>160</b> of the delivery resource <b>430</b> to which the item had been assigned, then the processor <b>114</b> and the central hub <b>110</b> identifies that the item was delivered. In this instance, the central hub <b>110</b> will identify that a delivery event has occurred.

0127<figref idref="DRAWINGS">FIG. <b>7</b></figref> illustrates an embodiment of a process flow diagram for a delivery and pick-up at a receptacle. In a process <b>700</b>, data flows and communications regarding an exception for a door <b>230</b> not being closed are depicted. The process <b>700</b> begins in step <b>702</b>, wherein the first and second sensors <b>232</b>, <b>234</b> indicate that the door <b>230</b> on the item receptacle <b>200</b> has been opened. The processor <b>222</b>, or the control unit <b>352</b> starts a timer, or periodically checks the door status. For ease of discussion, control unit <b>352</b> will be referred to in this and subsequent figures, but it is understood that the functionality of the control unit <b>352</b> can be provided by the processor <b>222</b> and its related components.

0128If the control unit <b>352</b> detects that the door <b>230</b> has been open for a specified period of time, or longer, such as 60 seconds, 2 minutes, 5 minutes, or any other desired time, the process <b>700</b> moves to step <b>704</b>, wherein the control unit <b>352</b> communicates to the central hub <b>110</b> that the door <b>230</b> has been open for the specified period of time. In some embodiments, the control unit <b>352</b> attempts to communicate with the delivery device <b>160</b> directly, or through the control hub <b>160</b> to notify the carrier that the door <b>230</b> has been left open. In some embodiments, this communication to the delivery device <b>160</b> can be sent when the control unit <b>352</b> or the central hub <b>110</b> has determined a delivery event has happened recently, such as within the last 5 minutes, the last 30 minutes, or any other desired time. In some embodiments, if the central hub <b>110</b> or the control unit <b>352</b> has determined that a pick-up event has just occurred, the central hub <b>110</b>, or the control unit <b>352</b>, or both communicate with the recipient, such as with the mobile communication device <b>472</b> that the door <b>230</b> is open. This can inform the recipient that he or she left the door <b>230</b> open, or that there is some problem with the door, and instruct the recipient to close the door <b>230</b>.

0129The process <b>700</b> moves to step <b>706</b>, wherein the recipient or the carrier or some other party closes the door <b>230</b> or attempts to close the door. In some embodiments, step <b>706</b> can be a predetermined wait time after communicating the door open status. For example, step <b>706</b> can be a 1 hour wait, a 2 hour wait, a 12 hour wait, a 24 hour wait, or any other desired time period. In some embodiments, the wait time can be adjusted according to the time of day when the door open signal was detected. After the wait period, another communication to the recipient or the carrier, or another party identified by the recipient is sent. If the door is left open at night, a repeat message can be sent sooner, so as to try and get the door <b>230</b> closed sooner. If the door <b>230</b> is left open in the morning, and the carrier is expected within an hour, or another time period, the control unit <b>352</b> or the central hub <b>110</b> may not send a repeat message, because the carrier will be along soon, and can shut the door <b>230</b>.

0130The process <b>700</b> moves to decision state <b>708</b> wherein it is determined if the door <b>230</b> is now closed. The first and second sensors <b>232</b>, <b>234</b> can be rechecked in a step <b>710</b> to determine if a door closed signal is present.

0131If the door <b>230</b> is detected as being closed, the process moves to step <b>712</b>, wherein the control unit <b>352</b> communicates the change to the central hub <b>110</b>, to the carrier, or both. The process <b>700</b> moves to step <b>714</b>, wherein the recipient is notified that the door <b>230</b> is now closed, and the process ends.

0132<figref idref="DRAWINGS">FIG. <b>8</b></figref> is a process flow diagram depicting an embodiment of a process of IR beam exception handling. The IR beam can refer to the beam <b>252</b> generated by the item sensor <b>250</b>. The process <b>800</b> begins when the control hub <b>352</b> identifies that the door <b>230</b> is closed, but that the beam <b>252</b> is broken. In some embodiments, the item sensor <b>250</b> is placed higher in the item receptacle so that the beam <b>252</b> is broken when an item <b>202</b> is inserted, such as a letter, but is not broken when the item <b>202</b> rests on a floor of the internal volume <b>220</b> of the item receptacle <b>200</b>. In this event, an indication that the beam <b>252</b> is broken but the door is closed can indicate that the recipient did not pick up everything from the item recieptacle <b>200</b>, that something is stuck or not properly within the item receptacle <b>200</b>.

0133The process <b>800</b> moves to step <b>802</b> wherein a message is sent regarding the broken beam <b>252</b>. In some embodiments, the message can be sent to the carrier, or to the recipient, or both. For example, if the carrier has recently been at the item receptacle <b>200</b>, as identified by GPS breadcrumbs from the delivery device <b>160</b>, or based on a scan event from the delivery device for an item <b>202</b> deposited into the item receptacle <b>200</b>, the message can be sent to the carrier, and not to the recipient. If a pick-up event has just occurred, as described elsewhere herein, the message can be sent to the recipient and not to the carrier.

0134In some embodiments, an item <b>202</b> can be large enough that the beam <b>252</b> will be broken by the item <b>202</b> while the item <b>202</b> awaits pickup. In this situation, the control unit <b>352</b> can determine that the reason the beam <b>252</b> is broken and the door is closed, is because a delivery event just occurred, or that the pickup event has not yet occurred. If the control unit <b>352</b> determines a specified pick-up time period has passed, such as 12 hours, one day, or more, the control unit <b>352</b>, and/or the control hub <b>110</b> can send a reminder to the recipient to pick up the item <b>202</b>, and the exception or error message will not be sent.

0135The process moves to step <b>806</b> wherein the carrier or the recipient investigates what is breaking the beam <b>252</b>. The step <b>806</b> may also be a wait time similar to step <b>706</b> described above. The process <b>800</b> moves to decision state <b>808</b>, wherein it is determined whether the beam <b>252</b> is now unbroken and the door <b>230</b> is closed.

0136If the beam <b>252</b> is unbroken and the door <b>230</b> is closed, the process moves to step <b>810</b> wherein the control unit sends a message to the control hub <b>110</b> that the beam exception or error is cleared. The process <b>800</b> moves to step <b>812</b> wherein the carrier and/or the recipient are notified that the beam exception or error is cleared, and the process <b>800</b> ends.

0137Those of skill will recognize that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, software stored on a computer readable medium and executable by a processor, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

0138The logical blocks, modules and flow chart sequences are illustrative only. A person of skill in the art will understand that the steps, decisions, and processes embodied in the flowcharts described herein may be performed in an order other than that described herein. Thus, the particular flowcharts and descriptions are not intended to limit the associated processes to being performed in the specific order described.

0139The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

0140The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor reads information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

0141While the above detailed description has shown, described, and pointed out novel features of the invention as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the device or process illustrated may be made by those skilled in the art without departing from the spirit of the invention. As will be recognized, the present invention may be embodied within a form that does not provide all of the features and benefits set forth herein, as some features may be used or practiced separately from others. The scope of the invention is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

0142A person skilled in the art will recognize that each of these sub-systems may be inter-connected and controllably connected using a variety of techniques and hardware and that the present disclosure is not limited to any specific method of connection or connection hardware.

0143The technology is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, a microcontroller or microcontroller based system, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

0144As used herein, instructions refer to computer-implemented steps for processing information in the system. Instructions may be implemented in software, firmware or hardware and include any type of programmed step undertaken by components of the system.

0145A microprocessor may be any conventional general purpose single- or multi-chip microprocessor such as a Pentium® processor, a multicore processor, a system on a chip, a Pentium® Pro processor, a 8051 processor, a MIPS® processor, a Power PC® processor, Alpha® processor, a microcontroller, an Intel CORE i7®, i5®, or i3® processor, an AMD Phenom®, A-series®, or FX® processor, or any other microprocessor or microprocessor array. In addition, the microprocessor may be any conventional special purpose microprocessor such as a digital signal processor or a graphics processor. The microprocessor typically has conventional address lines, conventional data lines, and one or more conventional control lines.

0146The system may be used in connection with various operating systems such as Linux®, UNIX® or Microsoft Windows®.

0147The system control may be written in any conventional programming language such as C, C++, BASIC, Pascal, .NET (e.g., C#), Java, HTML, or other programming language and run under a conventional operating system. C, C++, BASIC, Pascal, Java, and FORTRAN are industry standard programming languages for which many commercial compilers may be used to create executable code. The system control may also be written using interpreted languages such as Perl, Python or Ruby. Other languages may also be used such as PHP, JavaScript, and the like.

0148The foregoing description details certain embodiments of the systems, devices, and methods disclosed herein. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the systems, devices, and methods may be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the technology with which that terminology is associated.

0149It will be appreciated by those skilled in the art that various modifications and changes may be made without departing from the scope of the described technology. Such modifications and changes are intended to fall within the scope of the embodiments. It will also be appreciated by those of skill in the art that parts included in one embodiment are interchangeable with other embodiments; one or more parts from a depicted embodiment may be included with other depicted embodiments in any combination. For example, any of the various components described herein and/or depicted in the Figures may be combined, interchanged or excluded from other embodiments.

0150With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art may translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

0151It will be understood by those within the art that, in general, terms used herein are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to embodiments containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”

0152All references cited herein are incorporated herein by reference in their entirety. To the extent publications and patents or patent applications incorporated by reference contradict the disclosure contained in the specification, the specification is intended to supersede and/or take precedence over any such contradictory material.

0153The term “comprising” as used herein is synonymous with “including,” “containing,” or “characterized by,” and is inclusive or open-ended and does not exclude additional, unrecited elements or method steps.

0154All numbers expressing quantities of ingredients, reaction conditions, and so forth used in the specification and claims are to be understood as being modified in all instances by the term “about.” Accordingly, unless indicated to the contrary, the numerical parameters set forth in the specification and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by the present invention. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should be construed in light of the number of significant digits and ordinary rounding approaches.

0155The above description discloses several methods and materials of the present invention. This invention is susceptible to modifications in the methods and materials, as well as alterations in the fabrication methods and equipment. Such modifications will become apparent to those skilled in the art from a consideration of this disclosure or practice of the invention disclosed herein. Consequently, it is not intended that this invention be limited to the specific embodiments disclosed herein, but that it cover all modifications and alternatives coming within the true scope and spirit of the invention as embodied in the attached claims.