Sensor based logistics system
Systems, methods, and computer program products are provided for tracking one or more items. In one exemplary embodiment, there is provided a method for tracking one or more items. The method may include periodically detecting, by a sensor device, sensor information of the one or more items, and periodically transmitting, by the sensor device, the sensor information. The method may also include determining if the one or more parties is authorized to receive the sensor information. The method may also include transmitting the sensor information to the one or more authorized parties. The method may further include determining if the one or more parties is authorized to receive the sensor information and the periodically transmitting the sensor information to the one or more authorized parties based on a set of one or more permissions that grants or restricts access of the one or more parties to the sensor information based on the set of one or more permissions.
Latest FedEx Corporate Services, Inc. Patents:
- Systems and methods for securely monitoring a shipping container for an environmental anomaly
- Systems and methods for improved automatic chocking of a cargo dolly
- Apparatus, systems, and methods for performing a dispatched logistics operation for a deliverable item from a hold-at-location logistics facility using a modular autonomous bot apparatus assembly, a dispatch server and an enhanced remotely actuated logistics receptacle apparatus
- METHODS, SYSTEMS, AND DEVICES FOR DETECTING AND RESOLVING RISKS ASSOCIATED WITH SHIPPED OBJECTS
- Multi-entity management of a node in a wireless node network
The present invention generally relates to systems and methods for tracking items. More particularly, the present invention relates to systems and methods for tracking items using a sensor device.
BACKGROUNDAsset management has always been an important part of commerce. For example, tracking packages is important to organizations of all kinds, whether it be a company keeping track of inventory to be sold in its stores, or a package delivery provider keeping track of packages being transported through its delivery network. To provide quality service, an organization typically creates and maintains a highly organized network for tracking its packages. Effective management of such networks allows lower cost, reduced delivery time, and enhanced customer service.
In addition to tracking packages, parties that ship and receive packages may also need information regarding the conditions of the packages, such as the temperature and humidity of the package. For example, a customer that has ordered a box of wine may want to monitor the temperature of the contents of the box to determine if the temperature and/or humidity goes above or below a set range. Likewise, the party that ships the package may also want to monitor the conditions of the package to ensure that the content arrives in the proper condition.
Technological advances have enabled items to be tracked in ways that far exceed the functionality of a simple list. A rich information framework now can be applied to describe the item's interaction with its surroundings, such as transportation and custodial handoffs.
Bar codes are one way organizations keep track of items. A retailer, for example, may use bar codes on items in its inventory. For example, items to be sold in a retailer's store may each be labeled with a different bar code. In order to keep track of inventory, the retailer typically scans the bar code on each item. In addition, when an item is sold to a consumer, the bar code for that item is scanned.
Similarly, a package delivery provider may utilize bar codes by associating a bar code with packages to be delivered to a recipient. For example, a package may have a bar code corresponding to a tracking number for that package. Each time the package goes through a checkpoint (e.g., the courier taking initial control of the package, the package being placed in a storage facility, the package being delivered to the recipient, etc.), the package's bar code may be scanned. Bar codes, however, have the disadvantage that personnel must manually scan each bar code on each item in order to effectively track the items.
Radio-frequency identification (RFID) tags are an improvement over typical bar codes. RFID tags do not require manual scanning that is required by typical bar codes. For example, in a retail context, an RFID tag on an inventory item may be able to communicate with an electronic reader that detects items in a shopping cart and adds the cost of each item to a bill for the consumer. RFID tags have also been used to track things such as livestock, railroad cars, trucks, and even airline baggage. These tags typically only allow for basic tracking and do not provide a way to improve asset management using information about the environment in which the items are tracked.
Sensor-based tracking systems are also known which can provide more information than RFID systems. Such systems, however, can be expensive, and may provide extraneous and redundant item information.
Shippers, carriers, recipients, and other parties often wish to know the location, condition, and integrity of shipments before, during, and after transport to satisfy quality control goals, meet regulatory requirements, and optimize business processes. To address these requirements, a system is needed that may monitor data regarding shipments and present this data to a user in real-time or near real-time. Shippers, carriers, recipients, and other parties may have similar information needs during shipment, but the parties may have privacy or regulatory requirements that prevent them from sharing all of the information available from a monitoring system. To address these requirements, a system is needed that allows parties to specify what information they will share with other parties, including the frequency and timeliness of information updates. The system should compare information requirements from parties involved in a shipment and notify parties when conflicts exist and allow parties to adjust information sharing policies to address these conflicts.
SUMMARYIn one exemplary embodiment, there is provided a method for tracking one or more items. The method may include periodically detecting, by a sensor device, sensor information of the one or more items, and periodically transmitting, by the sensor device, the sensor information. The method may also include determining if the one or more parties is authorized to receive the sensor information. The method may also include transmitting the sensor information to the one or more authorized parties. The method may further include determining if the one or more parties is authorized to receive the sensor information and the periodically transmitting the sensor information to the one or more authorized parties based on a set of one or more permissions that grants or restricts access of the one or more parties to the sensor information based on the set of one or more permissions.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments and aspects of the present invention. In the drawings:
The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar parts. While several exemplary embodiments and features are described herein, modifications, adaptations and other implementations are possible, without departing from the spirit and scope of the invention. For example, substitutions, additions or modifications may be made to the components illustrated in the drawings, and the exemplary methods described herein may be modified by substituting, reordering or adding steps to the disclosed methods. Accordingly, the following detailed description does not limit the invention. Instead, the proper scope of the invention is defined by the appended claims.
System Architecture
By way of a non-limiting example,
Network 106 provides communications between the various entities depicted in system 100. Network 106 may be a shared, public, or private network and may encompass a wide area or local area. Network 106 may be implemented through any suitable combination of wired and/or wireless communication networks (including Wi-Fi networks, GSM/GPRS networks, TDMA networks, CDMA networks, Bluetooth networks, or any other wireless networks). By way of example, network 106 may be implemented through a wide area network (WAN), local area network (LAN), an intranet, and/or the Internet. Further, the entities of system 100 may be connected to multiple networks 106, such as, for example, to a wireless carrier network, a private data network, and the public Internet.
Sensor devices 102a-102n may be devices for use in tracking various items, and may be attached to or included in the items that are to be tracked. For example, sensor device 102a may be attached to or enclosed in a package that is being sent to a recipient using a delivery service such as Federal Express Corporation, (“FedEx”). Alternatively, sensor device 102a may be attached to or enclosed in a container holding inventory being delivered to a retailer. The aforementioned items are exemplary and may comprise any deliverable elements.
Sensor device 102a may store information associated with an item tracking number for a corresponding item. The item tracking number may be a FedEx tracking number or similar tracking number. Sensor device 102a may also store information indicative of other sensor devices which are currently within a given proximity. For example, when an item with a corresponding sensor device 102a is placed inside a vehicle or storage facility that includes at least one other sensor device 102n, sensor device 102a may sense that another sensor device 102n is within a proximity that indicates that the corresponding item is now in the vehicle or storage facility. Information reflecting an association between sensor device 102a and sensor device 102n may then be stored in a memory located at one or more of sensor device 102a, sensor device 102n, and/or tracking center 104.
In one embodiment, sensor device 102a may be capable of measuring or detecting one or more conditions such as location, temperature, light level, motion, pressure, humidity, acceleration, gas level, airflow, vibration, or other environmental conditions. Sensor device 102a may also have the ability to directly transmit and receive information to/from tracking center 104 via network 106 by, for example, wireless communications. For example, sensor device 102a may be implemented using a wireless sensor available from Crossbow Technology. One of ordinary skill in the art will appreciate that alternative sensor devices may be used.
Tracking center 104 may provide a platform for tracking items being delivered to a recipient. Tracking center 104 may be implemented using a combination of hardware, software, and/or firmware, and may be operable to receive and store sensor data from various sensor devices 102a-102n. For example, sensor device 102a may periodically send tracking center 104 sensor data reflecting conditions measured or detected by sensor device 102a. Such sensor data may include location, temperature, light level, motion, pressure, humidity, gas level, airflow, vibrations, or other environmental conditions.
Tracking center 104 is also operable to respond to requests for sensor data. For example, a customer may use client 108a to enter a request for sensor data stored at tracking center 104. The request may include one or more triggering parameters, which can be used to find the requested sensor data. Exemplary triggering parameters may include a sensor identification number, item tracking number, location, temperature, light level, humidity, acceleration, pressure, gas level, airflow, vibrations, etc. Accordingly, by way of example, a customer may request temperature measurements within a certain range of a specific location. The distance from the specific location is the triggering parameter in that case.
When tracking center 104 receives a request for sensor data from client 108a, tracking center 104 may search a database resident at tracking center 104 and return the requested sensor data, if found. Access to the sensor data may be managed or open. For example, if access is managed, client 108a and/or the customer would need to be authenticated before sensor data is made available to client 108a and/or the customer. In addition to or instead of searching a database for sensor data, tracking center 104 may request sensor data directly from the relevant sensor device 102a.
Tracking center 104 may also provide updated and/or new programming for sensor device 102a. Programming, for example, may specify the manner in which a device senses environmental conditions. Programming of the aforementioned device may be altered, for example, by storing new or modified instructions in a memory (not shown) located at the respective device. Programming changes may be made arbitrarily (e.g., at the discretion of a programmer) or in response to a detected condition. For example, suppose sensor device 102a detects a temperature above a certain level. When sensor device 102a reports the temperature level to tracking center 104, an alarm or alert may be triggered to bring this information to the attention of personnel associated with tracking center 104. Tracking center 104, in turn, may alter the programming of sensor device 102a to check the temperature more frequently. One of ordinary skill in the art will appreciate that other parameters can be used as the basis for altering programming.
Clients 108a-108n provide users with an interface to network 106. By way of example, clients 108a-108n may be implemented using any device capable of accessing a data network, such as a general purpose computer or personal computer equipped with a modem or other network interface. Clients 108a-108n may also be implemented in other devices, such as a Blackberry™, Ergo Audrey™, mobile phones (with data access functions), Personal Digital Assistant (“PDA”) with a network connection, IP telephony phone, or generally any device capable of communicating over a data network.
Clients 108a-108n may be utilized by users to request sensor data from tracking center 104. For example, a user may subscribe to a service that allows the user to access up-to-date information about one or more sensors. Alternatively, a subscription to a service is not necessary to access the information. In order to request sensor data, the user may enter information on client 108a indicative of the desired sensor data. For example, the user may enter information requesting the current location and temperature of all sensors within a certain radius of a specified sensor. After the customer enters this information, client 108a may send a request to tracking center 104, which in turn may search its database or request the information directly from the sensors. When tracking center 104 finds the requested information, it may send the information back to client 108a.
Sensor device 102a may be operable to periodically determine whether there are any sensor devices 102n within a certain proximity of sensor device 102a. When sensor device 102a determines that sensor device (e.g. sensor device 102n) is within its range, sensor device 102a may store information indicative of an association between the two devices. Sensor device 102a may also send this information to tracking center 104 via network 106. When sensor device 102a determines that sensor device 102n is no longer within its range, it may update the stored information resident at sensor device 102a and tracking center 104 to reflect that the devices are no longer associated with each other.
Communication server 202 may be a web server that provides functionality for receiving traffic over a network, such as the internet. For example, communication server 202 may be a standard web server that a user may access at client 108a using a web browser program, such as Safari, Internet Explorer, or Netscape Communicator. Communication server 202 is operable to receive requests for sensor data from clients, and pass the requests on to databases 204-216, certificate server 218, and/or rules engine 220 for processing. Communication server 202 may also send and receive messages for configuration, management, and monitoring of sensor devices 102a-102n.
User management database 204 may maintain a list of users of the system, user profiles, roles and permissions within the system, user organizations, and the relationship between users and/or other parties.
Sensor device management database 206 may maintain a per-party inventory of sensor devices 102a-102n used to provide monitoring information. Sensor device management database 206 may also store sensor data received from various sensor devices 102a-102n. Sensor device management database 206 may also store association information indicative of associations between sensor devices 102a-102n.
For example, sensor device 102a may periodically send sensor data to tracking center 104, where it is stored in sensor device management database 206. Exemplary sensor data may include location, temperature, light level, motion, pressure, humidity, acceleration, gas level, airflow, vibrations, or other environmental conditions. Sensor data that is transmitted to sensor device management database 206 may be accompanied by information identifying the sensor device 102a-102n that detected the sensor data.
Association data stored by sensor device management database 206 may also be periodically sent by sensor devices 102a-102n. For example, when an activated sensor device 102a becomes positioned within a predetermined proximity of another sensor device 102n, sensor device 102a and/or sensor device 102n may locally store information reflecting this proximity association. Sensor device 102a may then send tracking center 104 information indicative of the association. Additionally or alternatively, sensor device 102n may send tracking center 104 information indicative of the association.
When tracking center 104 receives a request for sensor data from client 108a, sensor device management database 206 may be searched for the requested data. If that data is found, it may be sent back to client 108a.
Shipment management database 208 may contain configuration parameters for one or more shipments. Data management database 210 may contain data generated by the monitoring of the shipments. This data may be augmented by other systems such as third-party package tracking systems and border-crossing systems (not shown).
Analysis database 212 may contain an aggregation of all system information for use in analyzing past activities, adjusting configuration parameters, defining new monitoring activities, and predicting future trends. Audit database 214 may contain information that allows parties to review the monitoring of shipments for conformance to regulations and quality metrics. Archive database 216 may contain information that provides long-term storage and access of historical data, and a communication sub-system that sends and receives messages for configuration, management, and monitoring to sensor devices 102a-102n and network 106.
Certificate server 218 may be operable to control access to data resident in sensor device management database 206. For example, client 108a or a user of client 108a may only be authorized to receive sensor data that corresponds to sensor devices 102a-102n. When that user requests a set of sensor data that includes data for which the client or user has no authorization to access, certificate server 218 recognizes the lack of authorization and only allows tracking center 104 to send the client or user the portion of the requested sensor data for which the client or user has authorization.
Rules engine 220 may be operable to, among other things, send queries to sensor device management database 206 based on requests for sensor data from client 108a, send requested sensor data to clients 108a-108n after receiving it from sensor device management database 206, process sensor data received from sensor devices 102a-102n, request sensor data from sensor devices 102a-102n, and alter the programming of sensor devices 102a-102n.
For example, client 108a may include components such as a central processing unit (CPU) 310, a memory 320, an input/output (I/O) device(s) 330, an application programming interlace (API) 340, and a database 350 that can be implemented in various ways. For example, an integrated platform (such as a workstation, personal computer, laptop, etc.) may comprise CPU 310, memory 320, I/O devices 330, API 340, and database 350, interconnected by a local bus 335. In such a configuration, components 310, 320, 330, 340, and 350 may connect through a local bus interface.
CPU 310 may be one or more known processing devices, such as a microprocessor from the Pentium family manufactured by Intel™ or a mainframe-class processor. Memory 320 may be one or more storage devices configured to store information used by CPU 310 to perform certain functions, operations, and steps related to embodiments of the present invention. Memory 320 may be a magnetic, semiconductor, tape, optical, or other type of storage device. In one embodiment, memory 320 includes one or more software application programs 325 that, when executed by CPU 310, perform various processes consistent with the present invention.
Methods, systems, and articles of manufacture consistent with the present invention are not limited to programs configured to perform dedicated tasks. For example, memory 320 may be configured with a program 325 that performs several functions consistent with the invention when executed by CPU 310. Alternatively, CPU 310 may execute one or more programs located remotely from client 108a. For example, client 108a may access one or more remote programs that, when executed, perform functions related to embodiments of the present invention. The configuration and number of programs implementing processes consistent with the invention are not critical to the invention.
Memory 320 may be also be configured with an operating system (not shown) that performs several functions well known in the art when executed by CPU 310. By way of example, the operating system may be Microsoft Windows™, Unix™, Linux™, an Apple™ operating system such as MAC OSX™, Personal Digital Assistant operating system such as Microsoft CE™, or other operating system. The choice of operating system, and even the use of an operating system, is not critical to the invention.
I/O device(s) 330 may comprise one or more input/output devices that allow data to be received and/or transmitted by client 108a. For example, I/O device 330 may include one or more input devices, such as a network connection, keyboard, touch screen, mouse, microphone, disk reader, and the like, that enable data to be input or received from a user. Further, I/O device 330 may include one or more output devices, such as a network connection, display screen, printer, speaker devices, and the like, that enable data to be output or presented to a user. The configuration and number of input and/or output devices incorporated in I/O device 330 are not critical to the invention.
API 340 is an interface used by client 108a to execute user requests. API 340 may be used in conjunction with I/O device 330 to define, for example, monitoring parameters, events, and notifications with respects to shipments. In addition, API 340 may query and receive information regarding shipments in response to information received at I/O device 330. API 340 may also update information stored in databases 204-216.
Database 350 may comprise one or more databases that store information and are accessed and managed through system 100. By way of example, database 350 may be an Oracle™ database, a Sybase™ database, or other relational database. As illustrated in
Parties
According to one embodiment, a “party” may refer to an individual, a group, a division, a company, or any combination of individuals, groups, divisions, or companies. For example, when a user sends or receives a shipment, the user may join system 100. When the user joins, the user may enter his company name, and a party corresponding to the company may be created. After creation of the party, the user may be assigned to the party. When other users that belong to the same company join system 100, they may also be added to the party.
A party may use system 100 to collaborate with other business partners. To do so, the party may either identify other parties already present in the system via a search feature, or they can invite users into system 100. New parties may create collaboration profiles that specify their default policies for sharing information and access to their sensor devices. In addition, parties may also change their profiles at any time. For example, a party may change their profile on a per-shipment basis or may create profiles specific to one or more business partners. Collaboration profiles contain rules that may be invoked against a permission mechanism to enable and restrict access by business partners to information defined or created by other parties.
For example, a party may choose to make information about all of their monitored shipments available to all other parties in the system. Conversely, a party may restrict access to each monitored shipment to only the parties participating in the shipment (e.g. recipient and carrier). This may prevent other parties from accessing the information. The system also contains a mechanism used to govern the amount and level of detail of information access on a per-user basis; this mechanism is discussed further in this document.
The system may also allow the creation of communities of parties which cross organizational boundaries. To do so, users may search for other parties by name, description, or by settings in their collaboration profile that may indicate organizations willing to cooperate in fulfilling some need, such as providing intervention services to assure shipment integrity. To aid the collaborative process, party profiles may include information about the duration of a party's membership in the system and reputation information as expressed by their fellow members. The party profiles may also include operational information, such as the certificates or other configuration information necessary to leverage their telecommunications or computer networks. By granting access to their networks, a party may allow other parties to use them to transmit and receive monitoring and system data.
Permissions
System 100 may also include a permission mechanism that may be used to implement a set of permissions that grant or deny parties the ability to perform actions related to sensor devices 102a-102n and databases 204-216. The permission mechanism may be implemented by certificate server 218. For example, each party may have access to administrative functions that may include defining new parties in the system, adding or removing sensor devices 102a-102n, and/or the restricting or permitting access to party shipment information by other parties. Accordingly, permissions may allow a party to grant administrative functions to other parties, such that a party can, for instance, define a set of parties and restrict their ability to view, create, or update sensor devices 102a-102n, or to create, view, or update one or more shipments or sets of shipments.
This permission mechanism may be used to implement a set of collaboration policies within the system. Organizations, users, devices, shipments, and information stored within the system are created, viewed, modified, and deleted according to rules that take into account the object of the action and the entity performing the action. Rather than exhaustively specify the ability or inability of all other parties to perform such actions, these permissions can refer to roles that imply group membership (e.g. the set of all users belonging to a certain organization, all members of all organizations, all shipments in which a particular organization is a party, etc.). This system allows shared access to information and enables parties to act on this information. Parties collaborate by either actively seeking permission to access and act on data or by being passively granted permission by default. Collaboration policies specify what the default roles and permissions are for entities in the system.
Sensor Device
As previously stated, sensor device 102a may be placed inside a package with the contents of the package. Sensor device 102a may measure or detect one or more conditions such as location, temperature, light level, motion, pressure, humidity, gas level, airflow, vibrations, or other environmental conditions.
Sensor device 102a may report data in several different ways. For example, sensor device 102a may report data based on measurements of at least one of physical quantities (e.g. temperature of 72° F.), qualitative assessments (e.g. “hot”), relative observations based on a predetermined threshold (e.g. greater than 85° F.), a calculated threshold (e.g. average greater than 80° F.), and business-events provided by third-party systems (e.g. proof-of-delivery of a shipment). This data may be correlated with the shipment and may be used to report any changes in shipment status or a lack of changes in the status.
Depending upon the capabilities of sensor device 102a, these measurements may be calculated directly by sensor device 102a. However, other measurements may be calculated based on party requirements entered at I/O device 330 and processed by API 340. According to one embodiment, all observations are confirmed by API 340 because different measurements may be of interest to different parties. For example, a shipping party may wish to know when sensor device 102a measures the presence of 50% relative humidity. However, a receiving party may wish to know when sensor device 102a measures the presence of 80% relative humidity. If sensor device 102a cannot be configured to report against multiple measurement thresholds, then API 340 may be responsible for performing these calculations.
Parties with sufficient permission can define new sensor devices 102a-102n within the system by creating a sensor profile. A sensor profile may include a list of monitoring capabilities of sensor device 102a that may describe the conditions that sensor device 102a may observe (e.g. temperature, humidity, location, movement, etc.), the frequency that sensor device 102a may make observations, and the frequency that sensor device 102a reports the observations.
Sensor device 102a may be “owned” by a party because a party may govern access to data even if access is currently unrestricted. For example, some websites may publish weather information by ZIP code. This weather information may be correlated with temperature readings from another sensor device 102a to warn one or more parties of weather conditions. In this example, access may simply be the availability of the website to respond to requests.
In another embodiments, sensor device 102a may be “owned” by a party to the shipping process (e.g. a shipper, recipient, carrier, or logistics provider). In this embodiment, the sensor profile would indicate sensor device 102a ownership and allow that ownership to transfer to a different party upon completion of use. For example, a shipper might use sensor device 102a to assure the integrity of a high-value merchandise to a recipient. Upon proof of delivery to the recipient, the shipper may automatically transfer ownership of sensor device 102a to the recipient. Conversely, a different shipper might want retain ownership of sensor device 102a and this shipper may not transfer ownership of sensor device 102a to the recipient. A shipper may not transfer ownership so that the shipper would be able to use sensor device 102a to aid in a return of defective merchandise.
Some sensor devices 102a-102n may support inter-device communication using short-range communication mechanisms such as ZigBee. These sensor devices 102a-102n may use this capability to support business-level activities, such as ensuring the integrity of a set of shipments by mutual visibility and communication. Sensor device 102a owners may also allow shared access to this feature by other sensor devices 102n, particularly sensor devices that are owned by other parties. Sensor devices 102a-102n with networking capability may also transmit their observations using other sensor devices as communication gateways.
The system may also support profiles describing static (e.g. fixed) and configurable sensor devices 102a-102n. Via API 340, the system may define mechanisms and messages that may be used to configure sensor devices 102a-102n. These messages may include information used to identify the sensor device 102a that is the subject of the message and parameters to define thresholds for measuring observations, reporting observations, and reporting frequency.
Whenever possible, sensor profiles include a description of the power requirements over time of particular monitoring functions, such as the use of a GPS sensor to determine location. When provided, this information can be used to estimate the total power usage over a set of monitoring functions, and this information may be used to estimate the maximum duration of monitoring by sensor device 102a and may be used to assist a party in defining monitoring parameters. If this information cannot be provided, but sensor device 102a can provide diagnostic information specifying the power usage or level over time, historical data may be used to estimate the power requirements for particular sets of commonly used monitoring parameters.
Depending upon the capabilities of sensor device 102a, additional messages can be sent to sensor device 102a providing power and cost management information. This information may include time or location-based periods during which sensor device 102a functions may be reduced in frequency or idled, or during which communication can be restricted or switched to lower cost channels.
These messages may be sent during the initial receipt and setup of sensor device 102a as part of an inventory management function. These messages may also be sent during configuration of sensor device 102a dedicated to a specific kind of transport, storage, value chain production, or other logistics function. Sensor device 102a configuration can be a one-time activity or real-time, dynamic activity reflecting changing conditions or needs of system users or in response to system calculations.
Sensor Device Configuration
The permission mechanism may govern access to particular sensor devices 102a-102n on a per-user basis, and the permission mechanism may also provide the ability to configure sensor devices 102a-102n. This configuration information may consist of specifying which capabilities should be used in monitoring information of a particular shipment (e.g. movement, temperature, and humidity) in addition to the actual observation and reporting frequency to employ when providing information. This configuration information may be transmitted to sensor devices 102a-102n via a device configuration system (not shown). Device configuration system may use an intermediate communication gateway as needed to communicate with sensor devices 102a-102n. Alternatively, sensor devices 102a-102n may be configured by a plug-in connection to a programming device, such as a PC having a computer-readable media reader.
After configuration, sensor device 102a may transmit information to a data receiving system which may record the data and make that data available to parties with sufficient permission to view the data. The data may also be passed to a notification system that may compare the data against monitoring parameters. The notification system may also perform further actions, as needed, based on the result of the comparison. These actions may include triggering external system activities, performing calculations that result in new configuration information being sent to sensor device 102a, performing calculations that result in new configuration information for use in further monitoring, and correlating data from sensor devices 102a-102n or historical data. The system may also supplement data provided by sensor devices 102a-102n with information provided by the carrier or other external systems, either by receiving messages via the API or by querying these systems for data. This information may be viewed as third-party information and it may be combined with the sensor information and presented to the appropriate parties.
In addition to configuring a single sensor device 102a, the system may also transmit future configuration parameters for storage on sensor device 102a based on the capabilities of sensor device 102a. For example, if the monitoring frequency of sensor device 102a should change during shipment to allow more precise monitoring of its location as it nears a destination of the recipient, these parameters may be sent to sensor device 102a and sensor device 102a may automatically modify the reporting configuration.
Sensor device 102a configuration and access to data may be defined either collaboratively or on a per shipment basis. For example, in a particular shipment, both the shipper and the receiver may want to define monitoring parameters that may not be consistent. One way to accomplish this may be to use two sensor devices 102a and 102b, where sensor device 102a provides data to the shipper and sensor device 102b provides data to the receiver. However, using two sensor devices is not efficient. Therefore, rather than using two sensor devices to monitor and transmit data, the shipper and the receiver may share a single sensor device 102a.
Rules may be defined within the system that limit or force the shipper and the receiver to negotiate the implemented monitoring configuration parameters. The system can allow the shipper and the receiver to be effectively unaware that sensor device 102a is being shared. This may be accomplished by restricting the data available to the shipper and the receiver by events and thresholds defined by each party. For example, a receiver may desire location reporting at city-level at half-hour intervals, and the shipper may desire address-level reporting at hourly intervals. Sensor device 102a may be configured to report address-level reporting at half-hour intervals, but each party would only see information at the requested level (e.g. address vs. city) and requested frequency (e.g. half-hour vs. hour).
According to another embodiment, a shipper may define the reporting configuration of sensor device 102a to restrict the receiver from viewing data regarding the shipment to certain locations or during certain times. In addition, the configuration of sensor device 102a may also permit the receiver to view all data of the shipment once it has entered within a certain radius of the delivery location.
As previously stated, parties may define a shipment within the system. Examples of shipments may include the delivery of goods, the return shipment of any sensor device 102a and/or goods to the shipment origin or other location, the shipment of multiple items from a common origin through common intermediate points to multiple independent destinations, the aggregation of multiple shipments from separate origins to a common destination, and combinations of these scenarios.
These events may range from simple matching (e.g. the temperature of sensor device 102a has reached a certain threshold) to complex chains of independent or related events (e.g. a shipment has moved after 5 PM on certain day and the temperature and humidity have not exceeded a certain threshold after 20 minutes of movement). Since the specification of these events may be limited based on the capabilities of sensor device 102a, the system may prevent parties from attempting to specify events that cannot be provided by sensor device 102a. A party that owns sensor device 102a may modify the device's profile to limit the volume of monitoring observations provided to other parties. The party may also limit the specificity of data provided and the frequency of data reporting by specifying a delay before another party may view or interact with data from sensor device 102a.
A party may also only partially specify the configuration information for later use. This configuration information may act as a template where certain values may be specified, such as the origin of the shipment, the type of sensor device 102a to use for monitoring the shipment, and the type and frequency of monitoring data to collect. While this information may be specified during configuration, one of ordinary skill would appreciate that this information may be modified by the party during shipping.
Parties may also define relationships between shipments, such that two or more shipments originating from different locations and traveling to a common destination may be defined and queried by API 340 and viewed via UI 330 as a group. Likewise, multiple shipments traveling together from an origin to destination may be similarly grouped, and multiple shipments starting from a common point but ultimately arriving at more than one destination may be similarly grouped. This association of shipments may allow the party to define common configuration parameters across the group and may also simplify viewing, updating, and other operations. Multiple shipments may also be aggregated to provide a “safety net” feature. A “safety net” feature may be preferable when tracking shipments because this feature may reflect multiple activities, locations, and other monitoring data. Moreover, too great a variance in any of these data parameters could be used by a party to determine an error in the logistics process.
For example, a shipment of goods may be sent from three different plants A, B, and C and may all travel to a common intermediate point D (e.g. an assembly plant). Intermediate point D may ship the entire shipment of goods to a distributor E, and distributor E may separate the goods into three different shipments sending the goods to a return location F, a warehouse G, and a warehouse H. After return location F, warehouse G, and warehouse H receive the appropriate shipments, return location F may send the shipment back to plant A. In addition, warehouse G may send the shipment to a retailer I, and warehouse H may keep the shipment.
When defining common destination of multiple shipments, the system may optimize the use of sensor devices 102a-102n to meet the monitoring requirements of different parties while also minimizing the number of sensor devices 102a-102n in use. Optimizing the use of sensor devices 102a-102n may also minimize the overall power used by sensor devices 102a-102n and the aggregate number of communications required to report the status of the shipments. While the above examples have explained the use of a single sensor device 102a to monitor several shipments, one of ordinary skill would appreciate that a party may choose to monitor a single shipment using multiple sensor devices 102a-102n to ensure monitoring parameters by calculating information from each of sensor devices 102a-102n or performing more sophisticated analysis based on known capabilities, accuracy, and precision of sensor devices 102a-102n.
According to another embodiment, sensor devices 102a-102n may each be placed in separate packages for shipping and may travel together when each of the packages is transported as a group (e.g. cartons on a pallet). In this embodiment, sensor devices 102a-102n may be configured to determine a master sensor device 102a that may receive information from other sensor devices. Based on this configuration, sensor devices 102a-102n may all communicate with each other, but only sensor device 102a transmits information to tracking center 104.
Sensor devices 102a-102n may also be configured to opportunistically take advantage of third-party communication networks, such as WiFi networks. Sensor devices 102a-102n may sense and report third-party communication networks that may provide compatible communication channels during transport back to tracking center 104. If these channels are open for communication, sensor devices 102a-102n may use them if other preferred channels are not open or if they can be used to reduce power consumption and/or cost. If these networks belong to parties in system 100, a party with sufficient permission may view these networks and obtain appropriate credentials to enable the use of these networks. If the credentials are approved, the information regarding these networks may be sent and downloaded by sensor devices 102a-102n.
Databases 204-216 may act as a feedback mechanism for sensor devices 102a-102n. Based on data transmitted from sensor devices 102a-102n to the databases 204-216, information derived from sensor devices 102a-102n either alone or in combination with information from other sensor devices 102a-102n, information derived from third party systems, or historical information from sensor devices 102a-102n used in monitoring similar shipments (e.g. matching the origin and destination of a current shipment or matching the shipper and recipient), system 100 may transmit new or updated configuration parameters to sensor devices 102a-102n.
For example, if system 100 notices that the temperature reported by a sensor device 102a is trending upward, system 100 may reconfigure sensor device 102a to increase the rate and/or precision of temperature measurement and reporting based on the capabilities of sensor device 102a. This ability to reconfigure sensor device 102a is especially important if a party indicated that the temperature should be monitored and sensor device 102a should provide information if the temperature is approaching a critical threshold. System 100 may also use historical measurements to detect anomalous events. For example, an average transit time from origin to a particular mid-point may be 15 hours with a standard deviation of an hour based on historical data. However, a particular shipment may taking longer (e.g. 17 hours). If this occurs, parties monitoring the shipment may be alerted even though the parties had not requested notification of such an event in advance. Historical data may also be used to determine unusual data, such as delays in movement that might be the result of an accident.
Sensor device 102a may also transmit other data to system 100 even though this data might not be individually identifiable or actionable. For example, sensor device 102a may report the number and type of observations they have made using standard or custom units of measure (e.g. observations per hour). This data may be transmitted in the same manner as other sensor data. However, the party that currently “owns” sensor device 102a (e.g. the party that is authorized to control sensor device 102a) may choose whether this data is stored with the other data. If it is, the party may, based on the party profile, make this data available to other parties both during shipment and afterwards as historical data.
Parties may record information about communication networks, such as WiFi or other wireless networks, for use by sensor device 102a for sending and receiving monitoring and other system information. This information may include the location of wireless access points or other communication gateway devices, security credentials, certificates, and other security information necessary to use the network. This information may also include specifications regarding limits on the amount of data that can be transferred by parties over the network, the duration of use within certain timeframes, and other information necessary to ensure proper use.
For system 100 to report the information about a shipment, an association may be made between the sensor device 102a that is monitoring the shipment and a shipment identifier. This would typically be done at the time the shipment is created when a tracking number for the shipment is generated and the package is ready to be sealed. This process may occur at I/O 330 where the party may input or select a unique sensor identifier and a shipment identifier. The sensor identifier can be any unique number such as the hardware ID, SIM card number, or the device phone number. The shipment identifier can be the tracking number, freight shipment number, customer order number, or any unique identifier for that package. A sensor device 102a may also be associated with groups of individual shipments or consolidated packages traveling together under one shipment, such as a pallet. Likewise, multiple sensors devices 102a-102n may be associated to a single shipment if, for example, battery life of one of sensors devices 102a-102n is inadequate to cover the entire route.
The association may also take place prior to the time a shipment is ready to be sent. This may occur if the shipper wants to monitor conditions during manufacturing or assembly but shipment details for the product have not been determined yet. In this example, the association could be between at least one of sensors devices 102a-102n and the shipper's internal order identifier. After the order has been completed and prepared for shipment, the shipment number could be added to the shipment to complete the associations. A similar process may also occur when monitoring a product after the end of a shipment.
The shipper may also define a termination point of the shipment (e.g. at the recipient). When the shipment arrives at the termination point, the association between sensor device 102a and the shipment identifier would cease. At this time, sensor device 102a may be available to be associated with another shipment. One of ordinary skill would appreciate that the termination point may be negotiable between the shipper and recipient if the detailed information about the shipment is of interest to both parties.
Real-Time Monitoring
After an association occurs, sensor device 102a may report data on a periodic basis, and this data may be available to the appropriates parties via I/O 330. This data is presented as a set of information about that shipment and may include, for example, multiple environmental elements, location, progress of the shipment, and overall status. This information may be presented graphically, in table format, or via a map view.
The timeliness of the data is contingent both on network availability and latency. When cellular backhaul is the sole communication method, data availability may be impacted by network conditions. Short range communication options such as WiFi and Zigbee are also a possibility and may be used as either a primary transmission method or a secondary transmission method. When communication with a network is not possible, the data received by sensor device 102a may be logged and stored in sensor device 102a and transmitted when communication is available.
In addition to specified monitoring parameters (e.g. location, temperature, and humidity), sensor device 102a may also transmit other data as part of the monitoring information. This data may be transmitted to system 100 via messages, and the message formats and receiving mechanisms may be specified by API 340 via I/O) 330. This data is stored as part of the monitoring information and is accessible to all parties having access to the shipment data.
The monitoring frequency may be determined by the party at the start of the shipment and may differ from the communication frequency. These frequencies may also be altered during the shipment if two-way communication with sensor device 102a is available. During monitoring, if sensor device 102a recognizes that its data storage space is limited, sensor device 102a may be configured to cease monitoring, reduce the frequency of observation, begin overwriting past observations, calculate new observations that attempt to summarize the values of previous observations (e.g. the average temperature over multiple observations and location based on a set of latitude/longitude locations), or any combination.
Parties may also choose to view the information generated during the monitoring of a shipment using filters that limit or narrow the type and number of observations presented. For example, a party may choose to view information generated or calculated during a specific time period, or a party may chose to only view information that meets criteria such as a measurement being above a threshold value. Moreover, parties may also view lists of shipments, inventory, or other monitored goods using these same criteria. Parties may sort and filter these lists, which may provide for separate viewing of information regarding, for example, shipments that are in motion and shipments that have generated a notification.
Sensor device 102a may also be used to observe the status of a package both before and after the shipping process. For example, sensor device 102a may monitor the status of a package stored in a warehouse after manufacture or in a distribution center after delivery. This is useful for performing asset or inventory management. Monitoring a package after shipment may require additional configuration parameters, such as a delivery event notification via a third party API or manual intervention by the third party to determine when the monitoring period begins.
For example, a third party system may be a warehouse management system that tracks the arrival or departure of shipments from a facility. This information may be used as another source of shipment status (e.g. shipped, received) or as indication of location if GPS or other location sensors could not work due to building interference or other factors. Another example of a third party system may be a temperature monitoring system within a building that provides an network-accessible source of information regarding the temperature and humidity status of a room. This information may provide additional information (e.g. ambient environmental condition) or as a correlation factor in confirming the condition of a shipment.
When a third party system is used to provide monitoring information, this information must be correlated with other monitoring information and/or the shipment. For example, if the shipper uses a carrier with shipment tracking service, the tracking service may report information based on a shipment tracking number, rather than sensor device 102a. Accordingly, when a third party system is used as a data source to provide additional information, the information may be transmitted to system 100 along with the shipment tracking number so that the information from the third party system may be correlated with the shipment.
Events and Notification
As appreciated by those of skill in the art, the monitoring process may include an active notification of parties or systems in response to a change in the status of a shipment. Notifications may be generated by system 100 based on the information collected by the sensor devices 102a-102n or based on non-sensor activities. These notifications may include a notification of new data that may include a signal indicating an alert condition (e.g. change in light, temperature, humidity). The timely departure from pre-defined location may generate a geofence notification (e.g. movement in or out of a specified area) whereas a temperature sensor reading exceeding the defined thresholds may trigger an environmental alert. These messages may be transmitted to the appropriate party or parties using multiple methods depending on the severity of the message. Notifications may be presented to the appropriate party or parties via email, Short Message Service (SMS), display on I/O 330, and presentation to a third party system via mechanisms specified by the appropriate party.
When defining a shipment, a party may specify start, intermediate, and end points based on either static or dynamic criteria. For example, a recipient may define the origin of a shipment as an address or a geofence boundary enclosing a particular area. In addition, the recipient may define the destination as the region “30 minutes” from a delivery address, where the “30 minute” boundary would be determined during shipment by the speed of sensor device 102a, a vehicle containing the shipment, or some other mechanism. Start, intermediate, and end points may be defined using simple criteria, such as a reading from a clock, or by combining multiple criteria in complex ways. For example, the start of a shipment may be described as the movement of sensor device 102a after a certain time. The definition of any of these conditions may be specified as requiring all of them (a logical AND), any one of them (logical OR), as following a pre-defined sequence of occurrence, or as the lack of an occurrence within a specified time window (logical NOT). The intermediate points may represent logistics process steps, such as distribution or manufacturing locations, or time periods where particular readings are expected.
Arbitrary regions may be also be defined by applying restrictions on shipment data visibility. For example, a carrier may wish to restrict visibility to its shipping network. Therefore, the carrier may define regions covering its facilities or time periods covering modes of shipment. These regions may be defined independent of any particular shipment and may then be applied to individual shipments or set as a default setting applying to all shipments that meet certain criteria.
Environmental thresholds and location boundaries may also be stored on sensor device 102a and would not require activity from system 100. Sensor device 102a may also alter its monitoring or reporting activity based on sensor data or location information. Other triggers for alerts may include movement as detected by sensor device 102a, a schedule as calculated by system 100, or carrier information.
Alert settings for an individual shipment may be applied at the beginning of shipment and may be modified remotely by the party or automatically adjusted based on conditions detected by sensor device 102a. System 100 may use these alerts to control monitoring as well. For instance, if a shipment is received at a customs clearing location and requires additional confirmation, sensor device 102a may detect that the shipment is not moving and may transmit that information to system 100. Based on this information, system 100 may re-configure the sensor device 102a to reduce power consumption, thus extending the monitoring ability of sensor device 102a in an effort to guarantee that sensor device 102a can still fulfill monitoring requirements once the shipment passes customs. If other shipments have sensor devices 102a-102n that monitor the package through customs, historical monitoring data may be used to estimate the duration of this period. This may result in a more accurate reconfiguration and may provide interested parties with information to better describe the logistics process.
Alert notifications to parties and system 100 may be configured to require an acknowledgement of receipt. Notifications that are not acknowledged within a pre-configured timeframe may automatically transition their recipient to other parties or trigger other actions such as executing rules, generating other notifications, and sending messages to other systems.
Data
Aside from monitoring data, parties can choose to store other unstructured data in data management database 210. This data may include documents representing agreements between parties, reports covering shipments, shipment documents such as bills or proof of delivery, sensor device 102a proof of ownership, and other information useful in the logistics process. This data is subject to the same collaborative sharing access rules as other information stored in data management database 210.
Archive
The information gathered and calculated during the monitoring of shipments (e.g. historical data) may be available to the party that configured the monitoring parameters for a configurable period after the monitoring ends. The duration of the configurable period is set by a party in system 100 with sufficient administrative permission. If multiple parties are collaborating in the monitoring of a shipment, all parties can view and interact with this information for the defined period. At the end of the defined period, the information may be archived in archive database 216. When the information is archived, the shipment information and its associated data does not appear in any lists presented by I/O 330. Accordingly, archived data may be considered hidden from view. Parties may choose to prevent one or more shipments from being archived. In addition, parties may manually choose to archive shipments before system 100 would automatically archive the information or after having chosen previously to not archive the information. Archive database 216 may also aggregate all archived data for use in analysis by parties.
Historical data may also be used to create shipment “templates.” For example, when a shipper is configuring a shipment, the shipper may input numerous data elements (e.g. destination, carrier, etc.). However, some data elements may not be known until the shipping order is created (e.g. tracking number or date specific service levels like Saturday delivery). Accordingly, the shipment template, which is a named shipment configuration that has at least one of the shipment configuration elements input, may be missing data elements. Rather that spending the time and resources to recreate a shipment template, it may be easier to start with the configuration of a past, successful shipment and adjust or remove data elements as appropriate to adjust for other shipments that fit the intended profile. Alternatively, an automated process could cluster past, successful shipments based on configuration similarities to the shipment selected and assist the party by flagging the configuration values that are likely to require attention for a particular shipment.
By way of example, a shipper may notice that most shipments to a receiver are almost identical, and a data element corresponding to the carrier may depend on how quickly the receiver requires the shipment. Therefore, the shipper may create an shipment template based on a previous shipment, and the shipper may flag the carrier as unspecified in the shipment template so that the shipper may be required to set the carrier when he creates a new shipment.
According to another example, a shipper may have a new employee that may create a new shipment template for a shipment to a receiver. The employee may choose the wrong carrier. System 100 may access the historical data stored in archive database 216, and system 100 may notice that this shipment template is very similar to previous shipments, but the carrier has never been used before for this type of shipment. The shipper may then be prompted for confirmation that the carrier is correct. In response, the shipper may correct the mistake or, if he decides that the carrier is correct, he could confirm the selection.
In addition, access to historical data provides parties with the opportunity to detect deviations from specified monitoring parameters and to infer and suggest better parameters, such as more precise thresholds or more accurate location and time values. For example, a receiver may notice that a geofence describing the delivery destination encloses his entire distribution center, an area covering 15 acres. The historical data may indicate that the monitoring of the shipments ends within a much smaller area (e.g. several hundred square feet). The receiver may then update the parameters used to create new shipments with this smaller region. In addition, the carrier for these shipments may also realize that all shipments delivered to a particular address end up being delivering to a particular receiving dock location. The carrier may update their parameters to reflect this information.
Having access to historical data allows the opportunity to characterize recurring problems in similar shipments either by manual inspection or automatic data mining. For example, if a shipper is examining past shipments, he may discover that the percentage of packages above a predetermined temperature threshold increases during a certain time of year for ground shipments but not for express shipments. This information may alert the shipper to, for example, investigate if seasonal packaging with additional insulation is cheaper than simply switching the service level to express.
Analysis
In addition to viewing party data, sensor device 102a, and shipment data, parties may also have access to historical data stored in analysis database 212. Subject to access permissions, parties may analyze current and historical data. For example, parties may view an aggregate depiction all of their organization's shipments. When other organizations create and monitor shipments, this data is also available for analysis, although these organizations may specify that their data is not identifiable. This may result in analysis database 212 replacing organization names and other identifiers with unique, generic values.
In addition to using GPS technology, the parties may also use Assisted GPS (A-GPS). A-GPS enhances the startup performance of a GPS satellite-based positioning system. In order to take advantage of A-GPS services, a receiver needs to have a general idea of its current position and a confidence interval that describes the confident the receiver has in knowing its current position. This allows the A-GPS service to determine what satellites the GPS receiver should be able to see, thereby allowing the receiver to avoid wasting resources searching the spectrum for satellites that are not currently visible to its location. Whenever a sensor device 102a sends a GPS position to an application, a cell base station that is associated with sensor device 102a is recorded along with identifying information for any other cell base station that is “visible” to, that is within some of sensor device 102a. Since the upper limit on cell size is known, it is possible for the application to calculate positions and confidence intervals for sensor device 102a using historical position data.
In order for this to occur, the application may build a graph using previously seen cell sites as points (nodes) and creates edges (lines) between points that have been reported as visible to sensor device 102a at the same time. For example, if sensor device 102a is associated with cell A but can also see cells B, C, and D, then the points for A, B, C, and D are all connected to each other by graph edges. Once the graph is created, a table may be created by visiting each point in the graph and determining how many edges must be traveled from the given point to the nearest point that has had a valid GPS reading associated with it. The confidence interval may then be calculated by adding one half to the number of edges traversed and multiplying the result by the expected cell diameter. If multiple GPS associated points are equidistant from the current point, the GPS readings may be averaged.
When sensor device 102a first connects to the application, the application may access the information based on the cell sites currently visible to the sensor device 102a. If any of the visible cell sites have been previously seen and associated with a GPS reading, the application may use the calculated position and confidence interval as the seed position and confidence interval required by the A-GPS service.
Flowchart
One or more sensor devices 102a-102n are set up based on the requirements of a shipper (step 410). For example, a party may require specific programming (specifying, for example, the manner in which a device detects environmental conditions) for sensor devices 102a-102n that are to be associated with items to be sent to recipients. Alternatively, sensor devices 102a-102n may be configured based on default programming. A shipper who desires to send an item to a recipient may purchase or otherwise acquire one or more sensor devices 102a-102n to be attached to or placed in an item to be shipped. A shipper, for example, may be an item delivery company such as FedEx, a retailer, or a manufacturer that makes its own deliveries. One of ordinary skill in the art will appreciate that it is possible that the customer and the shipper are the same entity.
Sensor devices 102a-102n may be activated and associated with the item(s) being shipped (step 420). For example, a courier or other employee of the shipper may turn on sensor device 102a and place it in or attach it to packaging associated with a corresponding item. The courier or other employee may also associate sensor device 102a with an item tracking number. For example, the courier or other employee may cause information to be stored at tracking center 104 that specifies that the item tracking number is currently assigned to an identification number for the item tracking device. Alternatively, no item tracking number is associated with sensor device 102a.
As noted above with reference to
When tracking center 104 receives sensor data, if that data is indicative of a predetermined condition, tracking center 104 may trigger an appropriate alarm (step 440). For example, suppose sensor device 102a detects a temperature above a certain level. When sensor device 102a reports the temperature level to tracking center 104, an alarm or alert may be triggered to bring this information to the attention of personnel associated with tracking center 104. Personnel may then monitor the situation more closely or take another appropriate action. Alternatively or additionally, the pertinent courier or other party may be notified of the alarm condition via sensor device 102a.
Tracking center 104 may also alter the programming of sensor device 102a if necessary or desired (step 450). In the example of sensor device 102a detecting a temperature above a certain level, tracking center 104 may, in turn, alter the programming of sensor device 102a to check the temperature more frequently. One of ordinary skill in the art will appreciate that other parameters can be used as the basis for altering programming. Moreover, one of ordinary skill in the art will appreciate that programming may be altered for reasons other than the detection of predetermined conditions, and that the programming of the aforementioned devices may be altered without the intervention of tracking center 104.
Finally, when an item reaches its final destination (e.g., delivered to the recipient), the courier removes and may deactivate sensor device 102a (step 460).
“Opt-In” Process
As previously stated, a party may use system 100 to collaborate with other parties. Within system 100, an application may provide the platform to allow parties that participate in the shipment of a package to control access to information in an automated way to meet the needs of each of the parties. The application may be stored on a computer-readable medium at, for example, tracking center 104. For example, parties may want to receive information regarding location, temperature, light level, motion, pressure, humidity, gas level, airflow, vibrations, or other environmental conditions at desired intervals (e.g. every hour). In addition to receiving information during the actual shipping of the package, parties may also want to receive information regarding the integrity of the package before and/or after the package is shipped. For example, the shipping party may want to receive information regarding the integrity of the package while the package is located in a warehouse before shipment. Moreover, the receiving party may want to receive information regarding the integrity of the package while the package is located in a warehouse after shipment.
Accordingly, parties may want to receive information during the entire journey of the package (e.g. before, during, and after shipment). Therefore, a party to a journey of a package (e.g. the shipper) may need to determine what type of information it wants to share with the other parties to the journey (e.g. the receiver). The parties may determine this information by negotiation with the other parties. Based on the negotiation, the parties may determine how the information is collected and what information is collected. The parties may also determine what information is available to them and what information is available to the other parties.
This agreement may be viewed as a collection of three, separate agreements that are part of the overall agreement. These three, separate agreements may be viewed as three layers. In the top layer, the agreement may contain constraints that generally cannot be negotiated by the parties. These constraints may be based on hardware, software, and/or legal constraints. Legal constraints may include, for example, information based on requirements of different countries and/or regions of the world. The restraints cannot change and may be viewed as a central base logistic system agreement that provides the parties with the ability to use the application.
The second layer may contain information sharing agreements between the parties. These agreements provide the ability for certain types of information to flow between the parties. The information sharing agreements are explained in greater detail below. The third layer may contain the journey agreement. This agreement may provide templates for the journey, such as filter, reporting, and/or alerts for a specific package (e.g. a pharmaceutical product). These three layers of agreements are all part of an overall agreement that governs how information is collected, reported, and shared with the parties.
In order to provide the “opt-in” ability, the parties may first determine their profiles. These profiles may be called a Sensor Information Sharing Profile (SISP), and the SISP may represent the information each party may share with the other parties in a journey. A party may create one or more than one SISP based on the role of the party in the journey (e.g. shipper, transporter, or receiver). In addition to creating one or more than one SISP for each role, a party may create more than one SISP for the same role (e.g. shipper). The SISP is used to create an Information Sharing Agreement (ISA). The ISA is contained within the second layer.
An SISP may be viewed as a default setting that specifies information, such as the conditions or circumstances that information is shared with other parties. This information may include both conditional settings and information availability settings. Examples of conditional settings may be origin region, destination region, the mode of transportation (e.g. land, sea, and/or air), container, and duration. Examples of information availability settings may be location, temperature, light level, motion, pressure, humidity, gas level, airflow, vibrations, or other environmental conditions. One of ordinary skill in the art will appreciate that other parameters can be used as the basis for providing conditional settings and information availability settings.
For example, the sending party may have an SISP created for land shipments, air shipments, and sea shipments. In addition, a receiving party may also have an SISP created for land shipments, air shipments, and sea shipments. Moreover, the parties may also have more than one SISP created for land, air, and/or sea shipments. Within each SISP, each party may also determine other settings listed above. When each party determines the settings for each SISP, each party may indicate if each setting is required.
For example, a shipper may want to provide only location and temperature information to the receiver. However, while the shipper may want to provide location and temperature information, the shipper may agree to also provide humidity information. Accordingly, providing humidity information is not required. A setting that is not required may be viewed as an allowed setting. Therefore, while the shipper may want to provide only location and temperature information, the shipper may agree to provide humidity information. Therefore, the setting selected by the shipper to provide humidity information is an allowed, but not required, setting.
Conversely, the shipper may want to only provide location and temperature information. However, the receiver may want to receive location, temperature, and humidity information, and the receiver may indicate that humidity temperature information is a required setting. One of ordinary skill in the art would appreciate that any party in the journey may create required settings in that party's one or more SISPs.
While an ISA may be generated using an SISP of each party, and SISP is not required. For example, one or more of the parties to a journey may not have an SISP. According to this example, an ISA could not be automatically created because one or more of the parties does not have an SISP. However, the parties may still negotiate the terms of the journey and create a corresponding ISA as described above.
Based on the settings contained in the SISP(s) of the each party, the SISP(s) may contain similar settings or may contain one or more different settings. If all settings match, there is no conflict between the SISP(s) of the each party. Therefore, an ISA may be automatically generated between the parties.
If one or more of the settings of the SISP(s) of the parties are not similar, a conflict exists, and an ISA cannot be automatically created. For example, a shipper of a package may indicate that it does not want to provide humidity information. This setting may be considered a required setting. However, the receiver may want to receive humidity information. This setting may also be considered a required setting. Therefore, a conflict exists, and the ISA cannot be automatically created. Because each party to the journey may have more than one SISP with different required settings, it may be difficult for the parties to determine which SISP to use to begin the negotiation process.
For example, if each SISP contains twenty settings, and each company has five SISPs, the conflicts between SISPs may vary depending on the different combinations. Accordingly, the application may use an algorithm to determine which SISP of each party to use to begin the negotiation process.
The algorithm may first determine the number of total matches. For example, if the SISP(s) of each party contains twenty settings, the algorithm may compare each SISP of each party to determine the SISP of each party that has the most settings is common. These SISPs may be viewed as the SISPs with the highest number of matches.
Next, the algorithm may determine the number of required settings of each SISP that match. As explained above, each party may determine any number of required settings within each SISP. In addition, each party may also determine any number of settings that are allowed, but not required. Based on the number of required settings of each SISP, the algorithm may determine the SISP from each party that contains the most number of required setting matches.
Next, the algorithm may determine a popularity. The popularity corresponds to the number of previously created ISAs for each SISP. As stated above, each party may create one or more SISP. Each SISP may be used to create one or more ISAs. Therefore, the algorithm may determine the number of ISA(s) that have been previously created for each SISP.
Finally, the algorithm may determine a date that was last utilized in an ISA that was part of a journey. Based on these four steps, the algorithm may determine the best SISP match.
After the best SISP match is determined for each of the parties, the parties may view the SISP from each other party that the algorithm determines is the best match to create the ISA. Based on the number of different setting requirements for each SISP, each party may need to negotiate with the other one or more parties to agree on an ISA. This negotiation may include updating the corresponding SISP or creating a new SISP so each party can agree on an ISA. If each party to a journey does not agree, an ISA cannot be created, and the journey cannot occur.
If the parties do agree to modify their SISP or create a new SISP, an ISA may be created. At this time, the parties seeking to “opt-in” to the agreement may negotiate changes to the conflicting setting(s). For example, if the shipper indicates that not reporting humidity information is a required setting, and the receiver indicates that humidity information is a required setting, the two parties may agree to report humidity information. Therefore, the shipper SISP that indicates that not reporting humidity information minutes is a required setting may be updated to indicate that reporting humidity information is not required, or allowed. One of ordinary skill would appreciate that one or more of the parties to a journey may modify its existing SISP or may create a new SISP based on the conflicts.
After each party to the journey agrees on each setting of its SISP, an ISA may be created. The ISA is a collection of two or more SISPs, and it sets the legal terms of the information that can be viewed across parties. Upon creation of the ISA, each party may receive and view the agreed information during the agreed interval(s).
The creation and agreement of an ISA occurs at the second layer of the overall agreement. At the third level, the parties may agree on a specific journey agreement. For example, the ISA in the second layer may indicate the rights for certain types of information to flow between parties (e.g. conditional settings, information availability settings, etc.). In the journey layer, corresponding to the third layer, the parties may determine templates for a specific journey. For example, if the shipper agrees to provide the receiver with temperature, light, and humidity information, the receiver may indicate that it wants to receive this information every thirty minutes. The shipper may agree to this reporting interval, or the shipper may propose a different reporting interval (e.g. every hour). One of ordinary would appreciate that each party may agree on numerous different settings as stated above and numerous different reporting intervals.
While the above example provides the ability for the parties to indicate specific parameters for a journey, the application may also provide these parameters within the SISP of each party. Therefore, if each party agrees to the parameters, and an ISA is created, the parties may create a journey without determining specific templates for the journey because this information is already contained in the agreed upon ISA.
In addition, it is possible for two or parties to agree and create and ISA, but not agree on the template for the journey. For example, if a receiver is receiving a medical device, the receiver may want to receive location information every thirty minutes during transportation until the device is within five miles of the receiver. At this time, the receiver may want to receive real-time location information. However, if the ISA that the receiver and shipper agreed upon does not provide for real-time location information reporting, the receiver may not be able to receive this location information. Accordingly, even though the parties agreed to an ISA, the journey template conflicts with the ISA. This conflict may be viewed as “out-of-bounds.” If desired information is “out-of-bounds” from the ISA (e.g. reporting location information real-time), the parties of the journey may need to create a new ISA that allows for real-time location information reporting. If the shipper agrees to provide real-time location information within five miles of the receiver location, the parties may agree to a new ISA. If the shipper does not agree to provide real-time location information within five miles of the receiver location, a new ISA will not be created and the journey will not occur.
If the parties agree to create a new ISA, the parties may agree on each of the parameters of the journey. Upon agreement, the parties have now agreed to the agreements on each of the three layers. Therefore, the journey of the package may begin at a desired time, and each of the parties to the agreement have agreed to “opt-in” to the agreement and they may receive the agreed upon information during to the journey of the package.
Documentation
During a journey, the information received and transmitted to the authenticated parties of the agreement may be stored in data management database 210 as stated above. As the information is stored in data management database 210, an application, that may be stored on a computer-readable medium at, for example, tracking center 104, may also present this information to the parties as a journey document related to the journey. As the information regarding the journey is updated, journey document objects related to each piece of information may be versioned to show an audit trail of any changes that may have been made as the package continues along the journey.
Journey document objects may include documentation that describes the object being shipped, the shipping transaction, the shipper, the carrier, and the receiver. In addition, the journey document may be in the form of an imaged journey document, electronically provided shipping information, and historical shipment data. Changes to the journey document may be made based on the role (e.g. shipper, carrier, receiver) and authorization of the party in the journey.
As a party uses the application over time, the application may monitor previous journey documents and may ensure that previous errors are not duplicated. The application may alert the party of previous errors or possible errors as described above. Accordingly, the system may monitor previous errors and create dynamic communities to improve journey documents.
While certain features and embodiments of the invention have been described, other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments of the invention disclosed herein. Furthermore, although aspects of embodiments of the present invention have been described as being associated with data stored in memory and other storage mediums, one skilled in the art will appreciate that these aspects can also be stored on or read from other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or a CD-ROM, or other forms of RAM or ROM. Further, the steps of the disclosed methods may be modified in various ways, including by reordering steps and/or inserting or deleting steps, without departing from the principles of the invention.
It is intended, therefore, that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims and their full scope of equivalents.
Claims
1. A computer-implemented method for managing information regarding shipments, the method comprising the steps of:
- periodically receiving from sensor devices condition information associated with shipments, the condition information detected by each sensor device and selected based on a device profile;
- associating a sensor information sharing profile with each of a plurality of parties; and
- periodically transmitting selected condition information from the sensor devices to select parties based on the sensor information sharing profile associated with each party.
2. The method of claim 1, wherein receiving condition information comprises receiving information regarding at least one of location information, temperature information, or humidity information.
3. The method of claim 1, further comprising triggering an alarm in response to the condition information.
4. The method of claim 3, wherein the triggering comprises triggering the alarm when the sensor devices detect condition information that exceed one or more threshold conditions.
5. A non-transitory computer-readable medium containing instructions which when executed on a processor performs a method for managing information regarding shipments, the method comprising:
- periodically receiving from sensor devices condition information associated with shipments, the condition information detected by each sensor device and selected based on a device profile;
- associating a sensor information sharing profile with each of a plurality of parties; and
- periodically transmitting selected condition information from the sensor devices to select parties based on the sensor information sharing profile associated with each party.
6. The computer-readable medium of claim 5, wherein receiving condition information comprises receiving information regarding at least one of location information, temperature information, or humidity information.
7. The computer-readable medium of claim 5, further comprising triggering an alarm in response to the condition information.
8. The computer-readable medium of claim 7, wherein the triggering comprises triggering the alarm when the sensor devices detect condition information that exceed one or more threshold conditions.
9. A system for managing information regarding shipments, comprising:
- at least one sensor device for detecting condition information associated with the shipments;
- a receiver for receiving the condition information from the at least one sensor device; and
- a processor for storing the received condition information, wherein the processor: associates a sensor information sharing profile with each of a plurality of parties; and periodically transmits selected condition information from the sensor devices to select parties based on the sensor information sharing profile associated with each party.
10. The system of claim 9, wherein the condition information includes information regarding at least one of location information, temperature information, or humidity information.
11. The system of claim 9, further comprising an alarm unit which is triggered in response to the received condition information.
12. The system of claim 11, wherein the alarm unit is triggered when the sensor devices detect condition information that exceed one or more threshold conditions.
| 5223844 | June 29, 1993 | Mansell et al. |
| 5347274 | September 13, 1994 | Hassett |
| 5389934 | February 14, 1995 | Kass |
| 5400020 | March 21, 1995 | Jones et al. |
| 5461365 | October 24, 1995 | Schlager et al. |
| 5491486 | February 13, 1996 | Welles, II et al. |
| 5512902 | April 30, 1996 | Guthrie et al. |
| 5515858 | May 14, 1996 | Myllymaki |
| 5528247 | June 18, 1996 | Nonami |
| 5539748 | July 23, 1996 | Raith |
| 5541845 | July 30, 1996 | Klein |
| 5550551 | August 27, 1996 | Alesio |
| 5568119 | October 22, 1996 | Schipper |
| 5570412 | October 29, 1996 | LeBlanc |
| 5576716 | November 19, 1996 | Sadler |
| 5588005 | December 24, 1996 | Ali et al. |
| 5592173 | January 7, 1997 | Lau et al. |
| 5608412 | March 4, 1997 | Welles, II et al. |
| 5623260 | April 22, 1997 | Jones |
| 5627517 | May 6, 1997 | Theimer et al. |
| 5629678 | May 13, 1997 | Gargano et al. |
| 5631827 | May 20, 1997 | Nicholls et al. |
| 5648770 | July 15, 1997 | Ross |
| 5652570 | July 29, 1997 | Lepkofker |
| 5686888 | November 11, 1997 | Welles, II et al. |
| 5691980 | November 25, 1997 | Welles, II et al. |
| 5710551 | January 20, 1998 | Ridgeway |
| 5712619 | January 27, 1998 | Simkin |
| 5731757 | March 24, 1998 | Layson, Jr. |
| 5742233 | April 21, 1998 | Hoffman et al. |
| 5751245 | May 12, 1998 | Janky et al. |
| 5771001 | June 23, 1998 | Cobb |
| 5771455 | June 23, 1998 | Kennedy, III et al. |
| 5774876 | June 30, 1998 | Woolley et al. |
| 5797091 | August 18, 1998 | Clise et al. |
| RE35920 | October 13, 1998 | Sorden et al. |
| 5826195 | October 20, 1998 | Westerlage et al. |
| 5835907 | November 10, 1998 | Newman |
| 5841352 | November 24, 1998 | Prakash |
| 5844862 | December 1, 1998 | Cocatre-Zilgien |
| 5850196 | December 15, 1998 | Mowers |
| 5869819 | February 9, 1999 | Knowles et al. |
| 5889770 | March 30, 1999 | Jokiaho et al. |
| 5892441 | April 6, 1999 | Woolley et al. |
| 5917433 | June 29, 1999 | Keillor et al. |
| 5948043 | September 7, 1999 | Mathis |
| 5959575 | September 28, 1999 | Abbott |
| 5963130 | October 5, 1999 | Schlager et al. |
| 6002363 | December 14, 1999 | Krasner |
| 6002982 | December 14, 1999 | Fry |
| 6009319 | December 28, 1999 | Khullar et al. |
| 6013007 | January 11, 2000 | Root et al. |
| 6014080 | January 11, 2000 | Layson, Jr. |
| 6014090 | January 11, 2000 | Rosen et al. |
| 6023241 | February 8, 2000 | Clapper |
| 6032051 | February 29, 2000 | Hall et al. |
| 6034622 | March 7, 2000 | Levine |
| 6054928 | April 25, 2000 | Lemelson et al. |
| 6064336 | May 16, 2000 | Krasner |
| 6067044 | May 23, 2000 | Whelan et al. |
| 6072396 | June 6, 2000 | Gaukel |
| 6078290 | June 20, 2000 | McBurney et al. |
| 6083248 | July 4, 2000 | Thompson |
| 6083353 | July 4, 2000 | Alexander, Jr. |
| 6094168 | July 25, 2000 | Duffett-Smith et al. |
| 6094642 | July 25, 2000 | Stephenson et al. |
| 6121922 | September 19, 2000 | Mohan |
| 6131067 | October 10, 2000 | Girerd et al. |
| 6141570 | October 31, 2000 | O'Neill, Jr. et al. |
| 6144303 | November 7, 2000 | Federman |
| 6148280 | November 14, 2000 | Kramer |
| 6163696 | December 19, 2000 | Bi et al. |
| 6171264 | January 9, 2001 | Bader |
| 6172640 | January 9, 2001 | Durst et al. |
| 6175616 | January 16, 2001 | Light et al. |
| 6198390 | March 6, 2001 | Schlager et al. |
| 6198431 | March 6, 2001 | Gibson |
| 6198930 | March 6, 2001 | Schipper |
| 6199045 | March 6, 2001 | Giniger et al. |
| 6220509 | April 24, 2001 | Byford |
| 6226622 | May 1, 2001 | Dabbiere |
| 6231519 | May 15, 2001 | Blants et al. |
| 6232916 | May 15, 2001 | Grillo et al. |
| 6236358 | May 22, 2001 | Durst et al. |
| 6238337 | May 29, 2001 | Kambhatla et al. |
| 6243039 | June 5, 2001 | Elliot |
| 6243660 | June 5, 2001 | Hsu et al. |
| 6246376 | June 12, 2001 | Bork et al. |
| 6255942 | July 3, 2001 | Knudsen |
| 6263280 | July 17, 2001 | Stingone, Jr. |
| 6278936 | August 21, 2001 | Jones |
| 6281797 | August 28, 2001 | Forster et al. |
| 6292687 | September 18, 2001 | Lowell et al. |
| 6292724 | September 18, 2001 | Apsell et al. |
| 6292784 | September 18, 2001 | Martin et al. |
| 6298306 | October 2, 2001 | Suarez et al. |
| 6300875 | October 9, 2001 | Schafer |
| 6304856 | October 16, 2001 | Soga et al. |
| 6314308 | November 6, 2001 | Sheynblat et al. |
| 6317049 | November 13, 2001 | Toubia et al. |
| 6323807 | November 27, 2001 | Golding et al. |
| 6324213 | November 27, 2001 | Harrison |
| 6327533 | December 4, 2001 | Chou |
| 6331817 | December 18, 2001 | Goldberg |
| 6339397 | January 15, 2002 | Baker |
| 6340928 | January 22, 2002 | McCurdy |
| 6349257 | February 19, 2002 | Liu et al. |
| 6353390 | March 5, 2002 | Beri et al. |
| 6353798 | March 5, 2002 | Green et al. |
| 6356841 | March 12, 2002 | Hamrick et al. |
| 6362778 | March 26, 2002 | Neher |
| 6363254 | March 26, 2002 | Jones et al. |
| 6363323 | March 26, 2002 | Jones |
| 6377810 | April 23, 2002 | Geiger et al. |
| 6388612 | May 14, 2002 | Neher |
| 6404352 | June 11, 2002 | Ichikawa et al. |
| 6407698 | June 18, 2002 | Ayed |
| 6411892 | June 25, 2002 | van Diggelen |
| 6411899 | June 25, 2002 | Dussell et al. |
| 6421538 | July 16, 2002 | Byrne |
| 6426719 | July 30, 2002 | Nagareda et al. |
| 6427120 | July 30, 2002 | Garin et al. |
| 6429810 | August 6, 2002 | De Roche |
| 6430602 | August 6, 2002 | Kay et al. |
| 6433732 | August 13, 2002 | Dutta et al. |
| 6435018 | August 20, 2002 | Murakami et al. |
| 6441778 | August 27, 2002 | Durst et al. |
| 6442380 | August 27, 2002 | Mohindra |
| 6445937 | September 3, 2002 | daSilva |
| 6452572 | September 17, 2002 | Fan et al. |
| 6453237 | September 17, 2002 | Fuchs et al. |
| 6459365 | October 1, 2002 | Tamura |
| 6463272 | October 8, 2002 | Wallace et al. |
| 6463420 | October 8, 2002 | Guidice et al. |
| 6469639 | October 22, 2002 | Tanenhaus et al. |
| 6471087 | October 29, 2002 | Shusterman |
| 6478736 | November 12, 2002 | Mault |
| 6480108 | November 12, 2002 | McDonald |
| 6484079 | November 19, 2002 | Buckelew et al. |
| 6496695 | December 17, 2002 | Kouji et al. |
| 6496775 | December 17, 2002 | McDonald, Jr. et al. |
| 6496777 | December 17, 2002 | Tennison et al. |
| 6512478 | January 28, 2003 | Chien |
| 6513532 | February 4, 2003 | Mault et al. |
| 6522871 | February 18, 2003 | Patrick et al. |
| 6522889 | February 18, 2003 | Aarnio |
| 6529164 | March 4, 2003 | Carter |
| 6544193 | April 8, 2003 | Abreu |
| 6552652 | April 22, 2003 | Beken |
| 6559620 | May 6, 2003 | Zhou et al. |
| 6559802 | May 6, 2003 | Goto et al. |
| 6569094 | May 27, 2003 | Suzuki et al. |
| 6579231 | June 17, 2003 | Phipps |
| 6611755 | August 26, 2003 | Coffee et al. |
| 6625437 | September 23, 2003 | Jampolsky et al. |
| 6640085 | October 28, 2003 | Chatzipetros et al. |
| 6650907 | November 18, 2003 | Kamperschroer et al. |
| 6656125 | December 2, 2003 | Misczynski et al. |
| 6721542 | April 13, 2004 | Anttila et al. |
| 6747675 | June 8, 2004 | Abbott et al. |
| 6748318 | June 8, 2004 | Jones |
| 6772130 | August 3, 2004 | Karbowski et al. |
| 6801850 | October 5, 2004 | Wolfson |
| 6804606 | October 12, 2004 | Jones |
| 6812840 | November 2, 2004 | Gehlot et al. |
| 6847892 | January 25, 2005 | Zhou et al. |
| 6856804 | February 15, 2005 | Ciotta |
| 6924750 | August 2, 2005 | Flick |
| 6952645 | October 4, 2005 | Jones |
| 6975941 | December 13, 2005 | Lau et al. |
| 6976007 | December 13, 2005 | Boucher et al. |
| 7002451 | February 21, 2006 | Freeman |
| 7034683 | April 25, 2006 | Ghazarian |
| 7035856 | April 25, 2006 | Morimoto |
| 7113784 | September 26, 2006 | Fujiwara et al. |
| 7174173 | February 6, 2007 | Needham et al. |
| 7187278 | March 6, 2007 | Biffar |
| 7202801 | April 10, 2007 | Chou |
| 7212829 | May 1, 2007 | Lau et al. |
| 7243080 | July 10, 2007 | Bhadra |
| 7253731 | August 7, 2007 | Joao |
| 7258276 | August 21, 2007 | Linton et al. |
| 7512515 | March 31, 2009 | Vock et al. |
| 7552031 | June 23, 2009 | Vock et al. |
| 7627666 | December 1, 2009 | DeGiulio et al. |
| 7791455 | September 7, 2010 | MacLean, III et al. |
| 7836850 | November 23, 2010 | Pratt |
| 8019740 | September 13, 2011 | Weng et al. |
| 8037846 | October 18, 2011 | Pratt |
| 20010020204 | September 6, 2001 | Runyon et al. |
| 20010028304 | October 11, 2001 | I'Anson et al. |
| 20010044299 | November 22, 2001 | Sandegren |
| 20010047244 | November 29, 2001 | Harrison et al. |
| 20010052849 | December 20, 2001 | Jones, Jr. |
| 20020000930 | January 3, 2002 | Crowson et al. |
| 20020014955 | February 7, 2002 | Klitsgaard |
| 20020016171 | February 7, 2002 | Doganata et al. |
| 20020027507 | March 7, 2002 | Yarin et al. |
| 20020038182 | March 28, 2002 | Wong et al. |
| 20020050945 | May 2, 2002 | Tsukishima et al. |
| 20020057192 | May 16, 2002 | Eagleson et al. |
| 20020061758 | May 23, 2002 | Zarlengo et al. |
| 20020070856 | June 13, 2002 | Wolfe |
| 20020077080 | June 20, 2002 | Greene |
| 20020087260 | July 4, 2002 | Hancock et al. |
| 20020087619 | July 4, 2002 | Tripathi |
| 20020111171 | August 15, 2002 | Boesch et al. |
| 20020111819 | August 15, 2002 | Li et al. |
| 20020115453 | August 22, 2002 | Poulin et al. |
| 20020119789 | August 29, 2002 | Friedman |
| 20020120475 | August 29, 2002 | Morimoto |
| 20020143670 | October 3, 2002 | Cushing et al. |
| 20020165638 | November 7, 2002 | Bancroft et al. |
| 20020175805 | November 28, 2002 | Armstrong et al. |
| 20020187025 | December 12, 2002 | Speasl et al. |
| 20020193121 | December 19, 2002 | Nowak et al. |
| 20030001742 | January 2, 2003 | Eshelman et al. |
| 20030003943 | January 2, 2003 | Bajikar |
| 20030004403 | January 2, 2003 | Drinan et al. |
| 20030061176 | March 27, 2003 | Hoar |
| 20030069002 | April 10, 2003 | Hunter et al. |
| 20030069759 | April 10, 2003 | Smith |
| 20030084005 | May 1, 2003 | Wong et al. |
| 20030115978 | June 26, 2003 | Moehnke et al. |
| 20030151507 | August 14, 2003 | Andre et al. |
| 20030204452 | October 30, 2003 | Wheeler |
| 20040034470 | February 19, 2004 | Workman |
| 20040046637 | March 11, 2004 | Wesby Van Swaay |
| 20040117108 | June 17, 2004 | Nemeth |
| 20050071258 | March 31, 2005 | Kumakawa |
| 20050250440 | November 10, 2005 | Zhou et al. |
| 20060173444 | August 3, 2006 | Choy et al. |
| 20060187026 | August 24, 2006 | Kochis |
| 20070229350 | October 4, 2007 | Scalisi et al. |
| 20070290836 | December 20, 2007 | Ainsworth et al. |
| 20080021953 | January 24, 2008 | Gil |
| 20080186166 | August 7, 2008 | Zhou et al. |
| 20090150114 | June 11, 2009 | Vock et al. |
| 20090292682 | November 26, 2009 | Robbins |
| 20100332284 | December 30, 2010 | Hilbush et al. |
| 1 037 447 | September 2000 | EP |
| 1189163 | March 2002 | EP |
| 2329491 | September 1997 | GB |
| WO 97/41654 | November 1997 | WO |
| WO 98/01769 | January 1998 | WO |
| WO 98/16045 | April 1998 | WO |
| WO 00/51391 | August 2000 | WO |
| WO 01/50151 | July 2001 | WO |
| WO 01/65444 | September 2001 | WO |
| WO 01/75700 | October 2001 | WO |
| WO 01/97167 | December 2001 | WO |
| WO 02/42979 | May 2002 | WO |
| WO 02/084618 | October 2002 | WO |
| WO 02/101505 | December 2002 | WO |
| WO 03/012720 | February 2003 | WO |
- International Search Report for related PCT Application No. PCT/US2010/048454 dated Sep. 2, 2011 (10 pages).
- CrossCheck™ AMPS with IQ Event Engine™ Firmware Operation Manual, Trimble Navigation Limited, Nov. 1998.
- CrossCheck® GSM Mobile Unit Operation Manual, Trimble, Jul. 2001.
- TAIP/IQEvent Engine Reference, Trimble Navigation Limited, Aug. 1999.
- Venable LLP, Homeland Security Alert, Maritime Transportion Security Act of 2002, Dec. 2002.
- Frittelli, Port and Maritime Security: Background and Issues for Congress, CRS Report for Congress, updated May 27, 2005.
- Environmental Cyberinfrastructure Needs for Distributed Sensor Networks, A Report From a National Science Foundation Sponsored Workshop, Scripps Institute of Oceanography, Aug. 2003.
- Ruiz-Garcia et al., “Monitoring Cold Chain Logistics by means of RFID,” from Sustainable Radio Frequency Identification Solutions, Book edited by Cristina Turcu, Feb. 2010.
- Shirley et al., “Mars Rovers: Past, Present and Future,” Princeton Space Studies Institute's 20th Anniversary Conference, May 1997.
- Culler et al, “MICA: The Commercialization of Microsensor Motes” Sensors, Apr. 2002.
- Kahn et al., “Next Century Challenges: Mobile Networking for ‘Smart Dust,’” 1999, found online at http://ksuseer1.ist.psu.edu/viewdoc/summary?doi=10.1.1.35.8873.
- Wolfe, “Electronic Cargo Seals: Context, Technologies, and Marketplace,” Jul. 2002.
- Maestas, “Demonstration of the Radio Frequency Identification Transportation Security and Safety System,” Oct. 15, 2003.
- Horton et al., “MICA The Commercialization of Microsensor Motes,” Sensor Technology and Design, Apr. 2002.
- System Planning Corp. helps evaluate seamless container-security system, The Journal of Commerce. May 2005.
- Prasad et al., “Application of Shape Analysis to domestic and international security,” Institute of Nuclear Materials Management Conference 2002, Orlando, Florida, Jun. 2002.
- Hill “A Software Architecture Supporting Networked Sensors,” Dept. of Electrical Engineering and Computer Sciences, U.C. Berkeley, Fall 2000.
- Akyildiz et al., “Wireless Sensor Networks: a Survey,” Computer Networks, 38 (2002), pp. 393-422, found online at http://impact.asu.edu/˜mcn/papers/sensorpapers/wsn.pdf.
Type: Grant
Filed: Sep 25, 2009
Date of Patent: Oct 30, 2012
Patent Publication Number: 20110074587
Assignee: FedEx Corporate Services, Inc. (Collierville, TN)
Inventors: Mark D. Hamm (Germantown, TN), James B. Greer (Memphis, TN), Daniel A. Ost (Germantown, TN), Miley E. Ainsworth (Hernando, MS), William S. Murphy (Germantown, TN), Zachary S. Perry (Chicago, IL), Ole Petter Skaaksrud (Germantown, TN), Kenneth L. Milman (Memphis, TN), Michael R. West (Memphis, TN), James Randy Jacobs (Collierville, TN)
Primary Examiner: Van T. Trieu
Attorney: Finnegan, Henderson, Farabow, Garrett & Dunner, LLP
Application Number: 12/566,883
International Classification: G08B 1/08 (20060101);
