Patent Document

This application is a continuation of non-provisional patent application Ser. No. 13/031,497, filed Feb. 21, 2011 (now U.S. Pat. No. 8,242,904), which is a continuation of non-provisional patent application Ser. No. 12/465,892, filed May 14, 2009 (now U.S. Pat. No. 7,898,411), which is a continuation of non-provisional patent application Ser. No. 11/834,052, filed Aug. 6, 2007 (now U.S. Pat. No. 7,545,266), which is a continuation of non-provisional patent application Ser. No. 11/005,307, filed Dec. 7, 2004 (now U.S. Pat. No. 7,265,668), which claims priority to provisional application No. 60/528,780, filed Dec. 12, 2003. The above-identified applications and patents are each incorporated herein by reference in its entirety. 
    
    
     This invention was made with Government support under contract DTMA1G02001 awarded by the United States Maritime Administration. The Government has certain rights in the invention. 
    
    
     BACKGROUND 
     1. Field of the Invention 
     The present invention relates generally to monitoring and tracking and, more particularly, to a system and method for asset tracking and monitoring. 
     2. Introduction 
     Security from terrorist actions has taken on an increased level of prominence in the United States. These terrorist threats can arise from internal sources or from external sources. With regard to external borne threats, one concern is the tracking and monitoring of semi-trailers, rail cars, and related shipping industry assets in the container arena as they cross into United States territory. Unless these assets can be secured and tracked prior to and subsequent to entry into the United States, the risk of terrorist activities will be significant. What is needed therefore is a system and method for global container tracking 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       In order to describe the manner in which the above-recited and other advantages and features of the invention can be obtained, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which: 
         FIG. 1  illustrates an embodiment of a system of the present invention; 
         FIG. 2  illustrates a flowchart of a process of the present invention; and 
         FIG. 3  illustrates an embodiment of a local network portion of the present invention. 
     
    
    
     DETAILED DESCRIPTION 
     Various embodiments of the invention are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the invention. 
     As noted, one of the security issues that has faced increased scrutiny is the risks associated with assets (e.g., containers, deployments, shipments, trailers, heavy equipment, vehicles, and other mobile assets) that cross U.S. borders. Security for these assets is a natural hazard due to the inherent inability to control access to these assets along their entire journey into and through a U.S. port. Typically, these assets are brought to a foreign port, loaded onto a ship, transported to a U.S. port, and loaded onto rail or semi-trailer transport to a domestic destination. Throughout this journey, the asset is susceptible to potential terrorist elements that seek to subvert the asset shipment to their own purposes. Securing and tracking these assets throughout their journey into the U.S. is therefore a necessary task in reducing the likelihood of asset-borne security threats. 
     In this environment, maintaining continuous tracking and monitoring visibility of an asset is of paramount importance. A loss of visibility provides terrorist elements with an unchecked opportunity to access and subvert an asset. Thus, one of the objectives of the present invention is to provide a framework that enables an asset to be tracked and monitored whether or not the asset is sitting in a rail or ship yard, or sitting on a train or ship during transport. As would be appreciated, each of these environments can present their own challenges in providing proper communication facilities that enable real-time or near real-time reporting of position, status, and alert information from the asset. 
     In designing a proper security framework where it is possible to maintain contact with an asset during all phases of shipment from origin to destination, it has become apparent that a single monitoring mechanism may not be sufficient to satisfy the security objectives. In accordance with the present invention, a multi-mode asset monitoring capability is envisioned to provide high-availability coverage over a range of transport phases. 
     For example, satellite-based communications and positioning means operate with relatively small link margins and can therefore require relatively unimpaired paths from the terminal to the satellite. Such paths, however, may not be available within container yards, where assets are often stacked. This problem can also exist in those asset environments where assets are stored within the bowels of a ship. 
     Terrestrial mode communications also have their limitations. For example, cellular systems offer much better link margins than satellite communications means except in fringe and shadowed areas. However, once out of cellular coverage terrestrial mode communications does not work. The unfortunate consequence is that terrestrial mode communications would not supply coverage over many rail routes, and certainly not on offshore shipping routes. 
     Notwithstanding the limitations of satellite and terrestrial communication systems, it is recognized that local monitoring networks seem to offer strengths precisely where satellite networks fall short (i.e., in relatively confined yard and shipboard environments). Here, local monitoring networks can represent those networks that are largely directed to the operating area of the supported operation, such as in a marine terminal, a truck terminal, aboard a ship, on a train, in a rail yard, in a shipping depot, in a tunnel, etc. In one embodiment, the local network collects information from terminals scattered within the local area, processes and screens the data, and presents it to a communications node within the local area for routing to a remote central data collection facility. In this manner, a local wireless network simplifies the communications problem at the operating site (i.e., yard or ship) by enabling a single, central communications means from the site to the central facility. In various embodiments, this could be done by Internet, leased line, wireless telephone or data services (e.g., PCS), another satellite network, or a combination of the above. 
     It is a feature of the present invention that a local monitoring network can be used in combination with a wide area monitoring network (e.g., satellite) to produce a multi-mode solution. This multi-mode solution would facilitate complete coverage across an asset&#39;s international route. In this framework, the local monitoring network can be used to report tracking and monitoring information to a central facility when out of contact with a satellite network, while the wide area satellite network can be used to report tracking and monitoring information to a central facility when out of contact with a local monitoring network. Here, each mode would use a different communications network to report asset position, status, and alert information. As would be appreciated, the various communications networks would have different performance characteristics, to thereby complement each other for a particular monitoring application. 
     Thus, in accordance with the present invention, distinct modes of network communications can be used to monitor assets. In one embodiment, complementary modes of communication can also be used simultaneously or in sequence when multiple modes are available. Further, in one embodiment, one network&#39;s availability can preempt report via another network, thereby increasing efficiency in communications network use. In another embodiment, each network could be used to provide reports whenever available regardless of the status of another network, thereby providing improved reliability through redundancy. In general, any one network could facilitate control operations in another network, or for configuration of devices in another network. 
     Information from the various monitoring networks can then be combined or otherwise integrated at a remote central information processing and delivery facility to produce a continuous tracking and monitoring log during the asset&#39;s entire international journey. 
     To illustrate the features of the security framework of the present invention, reference is now made to the system diagram of  FIG. 1 . As illustrated, the security framework includes asset  111  that is contained within a local area  110  (e.g., ship, ship yard, rail yard, or the like). Position, status, and alert information can be communicated to service operations center (SOC)  140  via satellite  120  and antenna  130 . 
     In one embodiment, SOC  140  is built around a relational data base managing all relevant system, user, terminal, and transaction data. Several back end servers manage internal system functions, such as terminal and protocol management and position solving, while front-end servers manage applications and web delivery. SOC  140  can deliver information to customers in a number of ways, including by web account, URL query, XML data delivery (including the XML trailer tracking standard), email, and file transfer protocol (FTP). 
     As further illustrated in  FIG. 1 , asset  111  can include sensors  114  that are used to detect various conditions at asset  111 . In various examples, sensors  114  can be used to detect intrusion, light, movement, heat, radiation, or any other characteristic that would bear on the container&#39;s security. Events detected by sensors  114  are communicated to service operations center  140  using mobile terminal (MT)  112  and/or local network terminal (LNT)  113 . It should be noted that while MT  112  and LNT  113  are illustrated as separate devices, they can be combined into a single multi-mode device. More generally, the multi-mode device can be designed to communicate in any number of modes dictated by a particular implementation. 
     In general, MT  112  can be used to communicate tracking and monitoring information to SOC  140  directly via satellite  120 . LNT  113 , on the other hand, can be used to communicate tracking and monitoring information to SOC  140  through local area terminal (LAT)  116 . In the embodiment illustrated in  FIG. 1 , LAT  116  would forward information communicated by LNT  113  to SOC  140  through satellite  120 . In an alternative embodiment, LAT  116  can communicate information to SOC  140  using a leased line, Internet or other land-based connection scheme. The operation of the alternative communication paths reflected by MT  112  and LNT  113  will now be described in greater detail with reference to the flowchart of  FIG. 2 . 
     As illustrated, the flowchart of  FIG. 2  begins with the detection by sensor  114  of an event. As noted, sensor  114  can be designed to detect various conditions such as intrusion (e.g., door sensor), light, heat, motion, radiation, or the like. As would be appreciated, asset  111  can be configured to include any number or combination of sensors depending on the particular application and level of security desired. Once sensor  114  detects an event, it would then alert at least one of MT  112  and LNT  113  at step  204 . 
     In various embodiments, sensors  114  can be coupled directly to MT  112  and/or LNT  113 . For example, if sensors  114  are coupled directly only to MT  112 , then a connection may also be established between MT  112  and LNT  113 , to thereby facilitate an effective connection between LNT  113  and sensors  114 . 
     After MT  112  and/or LNT  113  has been alerted to the detected event, MT  112  and/or LNT  113  would then proceed to communicate the detected event information to SOC  140 . Considering first MT  112 , when any of sensors  114  activates, sensor  114  awakens MT  112  and causes it to enter a mode to report immediately on sensor status and activation. This process is represented by step  206  where MT  112  would attempt to report the event to SOC  140  through a direct connection to satellite  120 . 
     In one embodiment, MT  112  is represented by the MT developed by SkyBitz, Inc. for use in their Global Locating System (GLS). The SkyBitz MT is built to Mil-Std 810F and SAE-J1077 environmental specifications, and is built as a software-configurable radio. Eight AA lithium batteries give it a battery lifetime of 4500 position reports combined with a shelf-life of over 10 years. 
     The combination of the protocol and mobile terminal design enables the mobile terminal to support position reports, MT paging (unscheduled requests for information from the MT), event reports (unscheduled, real time reporting of events detected by the MT), and low bandwidth data traffic. The MT can accommodate multiple simultaneous assignments, and can be configured remotely over the air. It also automatically adapts to changes in the network, and roams automatically among beams within a satellite footprint and among satellites. The GLS system is configured to use transponding satellites using the international geostationary L-band mobile satellite allocation. 
     The MT supports a number of local interfaces through a single weather-tight, triply-sealed connector. Through this connector the MT can monitor two simple contact closure sensors and operates two internal switches to control local external devices. It accepts external power and uses it when present in preference to internal batteries. And it controls an RS-485 data bus, enabling communications with up to six simultaneously connected intelligent devices. 
     Referring back to  FIG. 2 , if MT  112  determines that satellite  120  is not in view, it would then set a timer at step  210  for a short delay (e.g., seconds to minutes), go back to sleep, and reawaken when the timer expires to try again. When the timer has expired, the process would continue back to step  208 , where MT  112  would again determine if satellite  120  is in view. This process will repeat until it is successful. In one embodiment, timer intervals will increase with successive failures to receive the satellite signal in order to conserve battery when blocked from satellite  120  for an extended period. 
     If MT  112  determines at step  208  that the satellite is in view, then MT  112  would then proceed to report the event to SOC  140  through satellite  120 . In one embodiment, MT  112  reports the event by seeking an event timeslot or otherwise unoccupied timeslot (as evidenced by the forward link on that timeslot), and transmits a position and sensor status report over the corresponding return timeslot. It then proceeds to a slightly later timeslot to receive an acknowledgement. MT  112  will retry if it receives no acknowledgement. 
     As  FIG. 2  further illustrates, a sensor alert provided to LNT  113  will also cause LNT  113  to report the event to SOC  140 . This process is represented by step  214  where LNT  113  reports the event using a local area network. In one embodiment, LNT  113  receives the alert by sensor  114  directly. In another embodiment, LNT  113  is awakened by MT  112 . Here, when MT  112  initially awakens due to a sensor alert, it can be designed to also close an appropriate contact controlling LNT  113  to alert LNT  113  as well of the event. In one embodiment, LNT  113  can then send “blinks”, or brief emissions, on an ongoing basis at regular settable intervals (e.g., up to four minutes) between blinks If a sensor contact is closed, LNT  113  can immediately send a set of blinks with the change in status. 
     As illustrated in  FIG. 1 , LNT  113  can be generally designed to communicate with LAT  116  via a local network connection. LAT  116  can then proceed to communicate information generated by LNT  113  to SOC  140  via satellite  120 . In one embodiment, LAT  116  is embodied as a similar unit to MT  112 . In this embodiment, the primary difference between LAT  116  and MT  112  would be the item to which the units are fixed. MT  112  would be fixed to an asset being tracked and monitored, while LAT  116  would be fixed to an element within local area  110 . 
     As would be appreciated, the specific method by which LNT  113  would communicate with LAT  116  would be implementation dependent. One embodiment of a communication mechanism between LNT  113  and LAT  116  is illustrated in  FIG. 3 . In this embodiment, location sensor  320  is operative to listen to emissions by tags  310 , which are individually fixed to the plurality of container assets that are distributed in a local area  110 . Location sensor  320  would then report inform server  330  of the presence and status of tags  310  in local area  110 . Any location sensor  320  able to hear tag  310  in turn reports the change in tag status to server  330 . In one embodiment, several sensors  320  can be arranged around a local area  110  (e.g., ship yard, rail yard, ship, or the like) to locate each tag  310  using time difference of arrival techniques. 
     One example of tags  310  and location sensor  320  are the tags and location sensors manufactured by WhereNet, Inc. In general, WhereNet&#39;s local wireless locating and monitoring system has been used for locating and monitoring tags within a yard, depot, or plant environment. WhereNet&#39;s WhereTags operate in the 2.4 Ghz Industrial, Scientific, and Medical band, and can be set up to emit periodically from every few seconds to every few minutes. Tag emissions are spread spectrum, spread across 30 megahertz, and operate either at 2.5 milliwatts or 50 milliwatts, depending on the model. Each emission contains data on tag identity, tag state, the state of various sensor inputs, and other information. Emissions last only several milliseconds each, permitting very long battery life, up to seven years depending on type and report rate. 
     After server  330  collects reported information from tags  310 , server  330  would then proceed to report this information back to SOC  140 . In the illustrated embodiment, server  330  communicates with MT  340 , which is operative to transmit information to the SOC via satellite  350 . 
     In one embodiment, communication between server  330  and MT  340  is enabled using the local RS-485 data bus of MT  340 . In general, the RS-485 data bus supports among other things an RS-485 interface to local digital devices. In this embodiment, the RS-485 interface is used to transport packets from server  330  to the SOC using satellite  350 . Here, a software application hosted on server  330  extracts data from the database on server  330 , formats it, adds the necessary RS-485 communications protocol layers, and deliver it to MT  340 . At the SOC, application software would then extract the data from the incoming packets. 
     It will be appreciated by those skilled in the art that the system and method of the present invention can be used in environments other than those disclosed herein. It will thus be appreciated by those skilled in the art that other variations of the present invention will be possible without departing from the scope of the invention as disclosed. 
     These and other aspects of the present invention will become apparent to those skilled in the art by a review of the preceding detailed description. Although a number of salient features of the present invention have been described above, the invention is capable of other embodiments and of being practiced and carried out in various ways that would be apparent to one of ordinary skill in the art after reading the disclosed invention, therefore the above description should not be considered to be exclusive of these other embodiments. Also, it is to be understood that the phraseology and terminology employed herein are for the purposes of description and should not be regarded as limiting.

Technology Category: 3