MX2007014061A - Method and apparatus for arming a multi-layered security system - Google Patents

Abstract

A system monitors the condition of a container. A container security device secures the container. The container security device is programmably armed to implement the securing. The container security device is adapted to sense at least one condition of the container, transmit information relative to the at least one sensed condition to a location outside the container, and interpret the at least the condition. A remote arming plug is adapted to be removably coupled to the container security device. The remote arming plug has a unique identifier to be communicated to the container security device to initiate an arming sequence of the container security device. The remote arming plug is adapted to be applied as an integrated deployable seal to at least one sealing location to physically secure the container.

Description

METHOD AND SYSTEM TO ASSEMBLE A MULTI-LAYER SECURITY SYSTEM Cross References with Related Requests This application claims the priority benefit of the US Provisional Patent Application No. 60 / 681,105 published May 13, 2005, the contents of which are hereby incorporated by reference in their entirety as fully set forth herein. This Application relates to Patent Application Serial No. 11 / 099,831, entitled "Method and System for Arming a Container Security Device without the Use of an Electronic Reader", published on April 6, 2005, the description of which is incorporates as reference in the present. This Application also relates to Patent Application Serial No. 10 / 847,185, entitled "Method and System for Using Multiple Sensors to Monitor the Security, Content and Condition of Containers", published on May 17, 2004, the description of which is incorporated herein as a reference. FIELD OF THE INVENTION The present invention relates to a method and system for assembling a container security device with a remote arming contact and, after arming, using the remote arming contact as a physical (mechanical or electronic) seal. , which complies with the ISO standard for high security seals, ISO 17172. Background of the Invention The vast majority of merchandise transported throughout the world is transported through what is known as intermodal cargo containers. As used herein, the term "containers" includes any container (whether with adapted or non-adapted tires) that is not transparent to radio frequency signals, including, but not limited to, intermodal cargo containers. Intermodal cargo containers are known as ISO intermodal dry containers (International Organization for Standardization), which means that they meet certain specific dimension, mechanical and other standards issued by ISO to facilitate global trade by encouraging the development and use of compatible standardized containers, handling equipment, sea vessels, railway equipment and road equipment worldwide for all modes of transportation of merchandise. Currently there are more than 19 million such containers in active circulation around the world as well as many specialized containers such as refrigerated containers that transport perishable items. Only the United States receives around 10 million containers with cargo per year, or more than 25,000 per day, representing nearly half of the total value of all goods received each year. Because approximately 90% of all goods transported internationally move in containers, the transportation of containers has become the backbone of the global economy. The absolute volume of containers transported worldwide makes individual physical inspection impractical, and only about 5% of containers entering the United States are physically inspected. The risk of introducing a biological, radiological or explosive terrorist device through a cargo container is high, and the consequences for the international economy of such an event would be catastrophic, in view of the importance of containers in world trade. Even if sufficient resources were allocated in an effort to perform physical inspections of all containers, such action would result in serious economic consequences. Only the delay of time, for example, could cause the closing of factories and undesirable and expensive delays in the shipment of goods to customers. Current container designs do not provide adequate mechanisms to establish and monitor the safety of containers or their contents. A typical container includes one or more door latch mechanisms that allow the insertion of an indicative "seal" of plastic or metal or a conventional "seal" of a barrier to secure the doors of the container. The door latch mechanisms that are normally used are very easy to deactivate, for example, when drilling a bolt securing the bolt of a door to which the bolt is fastened. The conventional seals that are currently used are also very easy to deactivate by using a common cutting tool and replacing it with an easily duplicated seal. However, there are other, safer sealing locations (according to the US Customs and Border Protection Office) that could potentially be used to apply the mechanical seal. Various different container door locations known in the industry for coupling mechanical seals include "Pardo Hole", "Enhanced Lock Device" by P &; O Nedlloyd, and "SecureCam". A more advanced solution recently proposed is known as an "electronic seal" ("e-stamp"). E-seals are equivalent to traditional door seals and are applied to containers through the same door latch mechanism, albeit weak, as an accessory to the container, but include an electronic device such as a radio or reflector device radio that can transmit the serial number of the e-seal and a signal if the e-seal is cut or broken after it is installed. However, an e-stamp is not able to communicate with the interior or contents of the container and does not transmit the information related to the interior or content of the container to another device. E-seals could also weaken security since they will not be physically inspected. For example, there is no way to verify that an e-seal is actually securing the container door. It could be attached to any other side of the container and read remotely. A container security device, as described in US Pat. Serial No. 10 / 667,282, entitled "Method and System for Monitoring Containers to Maintain Safety of the Same", published on September 17, 2003, must be assembled in order to be able to monitor the integrity of the container doors while the container is in transit. However, one of the challenges of implementing a global transit security system for cargo containers is to properly distribute the global reading infrastructure in order to be able to assemble the container security device on demand anywhere in the world, ie , download to any container security device a coded arming key that has been issued by an authorized arming server. There are hundreds of thousands of cargo container carriers in more than 130 countries that would potentially need to use a certain type of reading device in order to carry out such assembly transactions. This need for reading devices means a problem when the carrier does not regularly transfer and / or does not have an account with the transporter, since it is problematic to distribute the readers. In addition, it is not unusual for some carriers to have their locations in remote locations (eg, inland China, Africa or Latin America), where there is limited wireless public network coverage or Internet access, or where such IT capabilities are very expensive In such cases, which are not expected to be unusual or rare in terms of the number of locations, but rather predominant, it could be very difficult to distribute readers and thus implement a global transit security system. It would therefore be advantageous to provide a method and system for assembling a container security device without the use of a reading device while maintaining a very high security process and security authentication. It would also be advantageous to use a device for remotely assembling the container safety device to be used as part of a mechanical seal to physically secure the container doors after completing the assembly process. In addition, after receiving the container, cutting the mechanical seal, and opening the doors, it would be advantageous to verify that the device on the mechanical seal is the same device that was originally placed at the sealing point of the container. Finally, it would be useful to use the same device to download a diary from the path of the container security device, take it back to a personal computer, and automatically authenticate the entire trajectory as well as load the information journal. Brief Description of the Invention These and other disadvantages are overcome by the embodiments of the present invention, which provides a method of and a system for efficiently and reliably monitoring a container and its contents as well as maintaining the safety thereof. More particularly, one embodiment of the invention includes a system for monitoring the condition of a container. A container safety device secures the container. The container security device is programmably armed to implement security. The container security device is adapted to detect at least one condition of the container, transmit information related to at least one detected condition to the location outside the container, and interpret the at least one condition. A remote arming contact is adapted to be removably attached to the container safety device. The remote arming contact has a unique identifier to communicate with the container security device to initiate a reinforcement sequence of the container security device. The remote arming contact is applied as a drop-down seal integrated to at least one sealing location to physically secure the container. The remote arming contact forms a seal that complies with ISO 17172. Another embodiment of the invention relates to a method for monitoring the condition of a container. The container is secured with a container safety device. The container security device is adapted to detect at least one condition of the container, transmit information related to the at least one detected condition to a location outside the container, and interpret the at least one condition. An arming sequence of the container security device is initiated in response to a movement of a remote arming contact related to the container security device. The remote arming contact has a unique identifier for communicating with the container security device and initiating an arming sequence of the container security device. The remote arming contact is applied as a drop-down seal integrated to at least one sealing location to physically secure the container. A further embodiment of the invention relates to a remote arming contact for storing a unique identifier that will communicate with a security device for container of a container to initiate a sequence of arming of the container security device. The remote arming contact includes a communication element for communicating with a unique identifier to the security device for a container, and a receiving opening for receiving a fixing element. The fastener applies the remote arming contact as a pull-out seal integrated to at least one sealing location to physically secure the container. Another embodiment of the invention relates to a method for monitoring the condition of a container. An insured container with a container safety device is received. The container security device is adapted to detect at least one condition of the container, transmit information related to at least one condition to a location outside the container, and interpret the at least one condition. A unique identifier of a remote armed contact is verified. During container shipping, the remote arming contact is applied as a pull-out seal integrated to at least one location to physically secure the container. The shipment information is downloaded from the container security device to the remote armed contact. Another embodiment of the invention relates to a system for monitoring the condition of a container. A container security device secures at least one container door. The container safety device is programmably assembled to implement the fastener. The container security device is adapted to detect at least one condition of the container, to transmit information related to at least one detected condition to a location outside the container, and interpret the at least one condition. A witness authenticates a person authorized to assemble the container safety device. The token communicates a unique identifier to the container security device to initiate a reinforcement sequence of the container security device. A remote arming contact is adapted to be removably attached to the core. The remote armed contact has the unique identifier to communicate with the witness. The remote arming contact is adapted to be applied as a pull-out seal integrated to at least one sealing location to physically secure the container.

BRIEF DESCRIPTION OF THE FIGURES A more complete understanding of the exemplary embodiments of the present invention can be achieved by reference to the following exemplary embodiments of the detailed description of the invention when taken in conjunction with the accompanying figures, in which: Figure 1A is a diagram illustrating a container in accordance with an embodiment of the invention; Figure 1B illustrates a flow of a supply chain by way of example; Figure 1C illustrates a system for preloading keys in the container security device in accordance with one embodiment of the invention; Figure 2 is a block diagram of electrical components of the container security device; Figures 3A-D illustrate various views of a container security device and a remote assembly contact in accordance with one embodiment of the invention; Figure 4 illustrates the remote assembly process of a container security device in accordance with one embodiment of the invention; and Figure 5 illustrates the remote assembly system that includes the carrier in communication with the authentication server and a user server; and Figures 6A-D illustrate containers having different locations to secure the mechanical seal that has a remote arming contact; and Figure 7 illustrates a method for using the remote arming contact as part of a mechanical seal and for monitoring the transportation of a container. Figures 8A-B illustrate a token for coupling with the remote arming contact. Figure 9 illustrates a security device for container, a witness and a remote arming contact in accordance with an embodiment of the invention. Figure 10 illustrates a witness and a remote arming contact in accordance with another embodiment of the invention. Detailed Description of the Exemplary Modes of Ha Present Invention It has been found that a container safety device of the type that is set forth, shown and described below, can be placed and secured to a container for effective integrity monitoring with optional monitoring of the condition of it and the content of the container. The container security device has to be armed with a unique electronic arming key for authentication purposes. The container security device can be armed using a reading device, in which case the arming key is obtained and downloaded from an authentication server that issues the arming key.

Alternatively, in accordance with the embodiments of the present invention, a remote arming contact is initially coupled to the container security device. The assembly key is generated in the container safety device itself once the remote assembly contact has been disconnected and the container doors have been closed. Also, the container security device can be armed with a unique arming key without the use of a reading device. However, after the remote arming key has been generated, the remote arming key must be authenticated. As a subsequent entity in the transport chain that has a reader that interrogates the container security device, the assembly key in the container security device is authenticated by the authentication server. The container security device secures at least one container door. The container security device may be similar to that described in U.S. no. of series 10 / 667,282, published on September 17, 2003, the description of which is incorporated herein by reference. The container security device is armed with a unique, coded armed key that guarantees the security of the system. The container security device is adapted to detect at least one condition of the container, transmitting information related to at least one detected condition to a location outside the container, and interpreting the at least one detected condition. A central piece of the embodiments of the present invention consists of the so-called remote arming contact. The remote armed contact has a unique identifier such as a combination of unique key, serial number, etc., and a key for authentication. The remote arming contact communicates this unique identifier with the container security device through any suitable manner, e.g., infrared, wireless connection or a physical connection. The unique identifier can also communicate ultra-sonically. The connector can be an RS-232 (D-SUB) connector that can be connected to the data port on the back of the container security device, but can be any type of connector and connect to another part (s) of the device Security for container. The remote armed contact can have a unique physically marked serial number (written numbers or bar codes) on it, as well as programmed (once) in its electronic memory. The remote arming contact can include a bolt. When the remote arming contact initially engages with the container safety device, the bolt may initially adhere to the rear part of the remote arming contact. After the remote arming contact of the container safety device is removed and the container safety device is activated, the container doors are closed. The pin of the remote arming contact is then removed. The remote arming contact is typically placed on or near the doors of the container, and the bolt is inserted through a bolt on one of the doors and into a reception opening on the remote arming contact. Also, the remote arming contact and its bolt are used as a mechanical seal for the container to be transported. Alternatively, instead of a bolt seal, the seal can be a cable seal, e-seal, or any other seal that complies with the standard for ISO 17172 seals. The remote arming contact can also be used as part of the seal. an e-seal that complies with ISO 17172, instead of as a part of a mechanical seal. The remote arming contact can also be used as part of a seal that complies with ISO 17172 derivatives / improvements. When the container is received at a point during the supply chain, a serial number of the remote arming contact can be read manually of the or communicate by the remote armed contact. Figure 1A is a diagram illustrating a container 100 in accordance with one embodiment of the invention. The container 100 is filled with various materials to be transported by a carrier. The container 100 has doors 105 that open when the carrier initially fills the container 100. A container security device 110 secures the doors 105 of the container 100 once they have been closed and until the container security device 110 is disarmed suitably such as when, eg, the container 100 reaches its final destination and its doors 105 need to be opened to remove the contents of the container 100. The container security device 110 will activate an alarm when the doors 105 of the container 100 sen are opened disarm properly. The container security device 110 ensures that the container 100 has not been tampered with after the container 100 has been secured. The process for assembling the container security device 12 is described below with respect to Figures 3A-D. Figure 1B illustrates a flow 120 of an exemplary supply chain of points (A) to (I). With reference to the first (A), the container 100 is filled with cargo by the carrier or the like. In point (B), the loaded container 100 is transported to a ship port by motorway or rail transportation. At point (C), the container 100 is received at the loading port such as a marine shipyard. At point (D), the container 100 is loaded onto a ship operated by a carrier. At point (E), the container 100 is transported by the carrier. At point (F), the container 100 is unloaded from the ship. After unloading at point (F), container 100 is loaded onto a truck and then removed from the unloading port at point (G). At point (H), container 100 is transported by land to a desired location similar to point (B). At point (I), after reaching the desired location, the container 100 is unloaded by a consignee. As will be apparent to those skilled in the art, there are many moments within points of flow 120 where the security of container 100 could be compromised without visual detection or other conventional detection. In addition, the condition of the contents of the container 100 could be completely unknown to any of the parties involved in the flow 120 to the point (H) when the content of the container 100 is discharged. As discussed above, the container security device 110 is armed during transportation for security purposes. The security device for container 110 can be assembled without using an electronic reader. Also, a carrier that does not have readers can assemble the container 110 security device. Instead, the container security device can be armed by using a remote armed contact that has a unique serial number, provided that when (a) the container security device has been pre-loaded with at least one registered key, and the unique identifier of the armed contact relates to at least one armed key; (b) the unique identifier is read from the remote arming contact and used in the container security device to calculate a unique arming key; or (c) the security device for container acquires a key for arming the remote arming contact. Figure 1C illustrates a system for preloading keys in the container security device 110 in accordance with one embodiment of the invention. The system includes an authentication server 140. The authentication server 140 generates keys and can transmit the keys to a factory 145, in which the container 110 security devices are produced. Also, the new keys could be stored directly in the devices of security for newly manufactured container 110 before container security devices 110 are used in the field. A security device for container 110 that is already in use can be refilled with additional keys in the field. For example, authentication server 140 may transmit additional keys to a computer 150, such as a laptop. The computer 150 can transmit the keys to a portable electronic device in communication with the security device for container 110 to be filled, such as a telephone 155 or personal digital assistance ("PDA") 160. Each key can be a unique number , and a different key can be used each time the container security device 110 is armed and a container 100 having the container security device 110 is transported. Figure 2 is a block diagram of electrical components of the security device. for container 110. The container security device 110 includes an antenna 200, a baseband / RF unit 205, a microprocessor (MCU) 210, a memory 215, and a door sensor 220. The security device for container 110 further includes an interface 229 for coupling additional sensors to monitor various internal conditions of the container such as, for example, temperature, vibration, dioactivity, gas detection, and motion movement. A remote arming contact can be coupled to the interface 229 to arm the container security device 110, as described but not limited with respect to Figures 3A-D.

The security device for container 110 may also include an optional power source 230 (e.g., battery); however, other power arrangements that are separable or remotely located may also be used by the container security device 110. When the power source 230 includes a battery (as shown herein), the inclusion of the power source 230 in the container safety device 110 can help to extend the life of the battery by subjecting the power source 230 to smaller temperature fluctuations in view of the fact that the power source 230 is inside the container 100. The presence of the power source 230 within the container 100 is advantageous as it reduces the ability to alter or damage the power source 230. The container security device 110 may also optionally include a connector for interfacing directly with an electronic reader. For example, a connector may be located on an exterior wall of the container 100 to be accessed by the reader. Although not required to assemble the container security device 110, the reader can be connected through a cable or other direct interface to download information from the security device for container 110. The microprocessor 210 (equipped with an internal memory) distinguishes events with door 105 of door sensor 230, including, for example, dismantling requirements of the container, and security verifications of the container. Events with the door also include security failures that can compromise the contents of the container 100, such as an opening of a door 105 after the container 100 has been secured. Events with the door can be stamped for a time or stored in the door. the memory 215 for transmission to the reader. Events with the door can be transmitted immediately, periodically, or in response to an interrogation of the reader. The door sensor 230 shown here is of the variety of pressure sensitivity, although it may be, for example, an alternative contact sensor, a proximity sensor, or any other suitable type of sensor that detects movement. relative between two surfaces. The term "pressure sensor" as used herein includes, but is not limited to, these other sensor varieties. Antenna 200 is provided for data exchange with the reader. In particular, various information may be exchanged, such as, for example, status and control information. The microprocessor 210 can be programmed with a code that uniquely identifies the container 100. The code can be, for example, an identification code for container that complies with the International Standardization Organization (ISO). The microprocessor 210 may also store other logistics information, such as Bill of Lading (B / L), a mechanical seal number, a reader identification with a time-stamp, etc. A special log file can be generated, whereby the history of events can be retrieved with gate 105. The code can also be transmitted from the security device 110 to the reader for identification purposes. The RF / baseband unit 205 converts the microprocessor signals from the baseband to the RF for transmission to the reader. The security device for container 110 can, through the antenna 200, receive an integrity request from the reader. In response to integrity inquiry, the microprocessor 210 can access the memory 215 to extract, for example, door-related events, temperature readings, security failures, or other stored information in order to send the extracted information the reader. The reader can also send a disarmament request to the container 110 security device. When the container 100 is armed, the memory 215 of the container security device 110 can be programmed to emit an audible or visual alarm when the door sensor 230 detects a material change in pressure after the container 100 is secured. The container security device 110 it can also register the security failure in the memory 24 for transmission to the reader. If the reader sends a disarmament request to the container security device 110, the microprocessor 210 can be programmed to disconnect from the events of the door register 105 or receive signals from the door sensor 230 or other sensors which are interoperatively connected to the device. container security 110. The carrier can assemble a container security device 110 having a pre-loaded security key, and the container security device 110 can then be authenticated by another entity (eg, another entity within the supply chain) checking the security device for container 110 with a reader. In order to assemble the security device for container 110 without the use of a reader, a remote arming contact is required. Figure 3 A illustrates a security device for container 110 and a remote arming contact 300 in accordance with an embodiment of the invention. The container security device 110 is mounted on the door frame 105 of the container 100, as shown in Figure 1. The carrier may have previously purchased a plurality of remote mounting contacts 300. When the carrier wishes to assemble a security device for container 110 before transporting a container 100, the carrier selects one of the remote arming contacts 300 and then manually inserts remote arming contact 300 into interface 229 of container security device 110. Alternatively, instead of manually inserting the remote arming contact 300 into the interface 229, a contact or wireless connection can be made between the remote arming contact 300 and the container security device 110. The interface 229 can include a female connector, and the contact Remote Arming 300 can include a male connector, and the combination of the active pins of the armed contact Remote 300 can be used to uniquely identify the remote arming contact 300. The remote arming contact 300 may also include a serial number written on some part of its body. As shown, the remote arming contact 300 may include a bolt 305 housed within a bolt sheath 310. The bolt 305 is used to secure the remote arming contact 300 to the doors of the container 105, as discussed below with respect to to Figures 6A-D. The remote arming contact 300 also includes a reception opening 315 for receiving the bolt 305 when the remote arming contact 300 is used as a mechanical seal. Bolt 305 is typically used only in the event that the mechanical seal is a bolt seal. However, in a modality in which the seal is an e-seal, a cable seal, or any other type of seal that complies with ISO 17172, bolt 305 was not necessary. Figure 3B illustrates the remote arming contact 300 after the bolt 305 has been removed from the bolt sheath 310. When the carrier has filled a container 100 and is ready to assemble the security device for container 110, the carrier inserts the male end 320 of the remote arming contact on the interface 229 of the container security device 110. Once inserted, an indicator 325 on the remote arming contact 300 intuitively indicates whether the remote arming contact 300 is in communication with the security device for container 110. In other modalities, an indicator 325 is not needed. Indicator 325 may include, eg, a Light Emitting Diode ("LED"), a Liquid Crystal Display ("LCD"), an element that emits audible sounds, a vibrating element, or any other type of light element that flashes, varies a flashing index, etc., to indicate a condition of the remote arming contact 300. For example, the indicator 325 may include an LED that begins to flash green light when communication between the remote arming contact 300 and the remote arming contact 300 is successfully established. security device for container 110. While the indicator 325 flashes green light, the serial number or any other unique identifier of the remote arming contact 300 is loaded to the security device for container 110. The security device for container 110 receives the number standard ugh its interface 229 which is in communication with the male end 320 of the remote arming contact 300. Alternatively, the security device for container 110 can receive the serial number via infrared, ultrasonic communication, wireless, magnetic communication, or any other suitable way. Once the serial number has been successfully loaded and the assembly process is initiated in the container security device 110, the indicator 325 will display this status intuitively. For example, the indicator 325 may display a solid green color, instead of a blinking green color, to indicate that the remote arming contact 300 may be removed from the security device for container 110. Once removed, an activation router is activated. of arming for the security device for container 110. Alternatively, if there is no indicator present in the remote arming contact, the arming activation router starts automatically after the serial number of the remote arming contact 300 It has been loaded successfully. After the remote arming contact 300 has been removed, the doors of the container 105 are closed, and the bolt 305 can be inserted into the reception opening 315 to close the doors of the container 105 as part of the mechanical seal. Figure 3 C illustrates the remote arming contact 300 when the bolt has been inserted into the reception opening 315. The remote arming contact 300 can be formed of a hard plastic having a metal portion placed therein, and the pin 305 can be formed of a metal. In practice, the security device for container 110 is mounted in the frame of the container door 100, as shown in Figure 3D. Once the container 100 is completely filled, the male end 320 of the remote arming contact 300 is initially inserted in the interface 229. To arm the security device for the container 110, the remote arming contact 300 is removed from the interface 229. The remote arming contact 300 can be manually removed from the security device for container 110. After a short delay such as, eg, 30 or 60 seconds, the security device for container 110 is armed. Alternatively, after uncoupling from the interface 229, the remote arming contact 300 may be in communication with other parts connected in some part of the container security device 110 and may become part of the mechanical seal that is used to physically seal the container door 105. When the remote arming contact 300 is initially removed, the container security device 110 enters a pre-armed state and then when the doors 105 are closed, and after a count, the container security device 110 enters an armed state. The doors 105 of the container security device 110 are closed, and counting begins when a sensor detects that the magnetic flux density is proportional to the gap between the doors 105 and the door frame (ie, by measuring the effect of Hall). Alternatively, when the pressure of the door seal 105 reaches the adequate limit for the assembly of the security device for container 110, counting begins. The bolt 305 and the remote arming contact 300 can be coupled together around a bolt in the container door, as described with respect to Figures 6A-D. The unique identifier of the remote arming contact 300 can communicate its identity to the security device for the container 110, and the security device for the container 110 will start its counting timer. The container security device 110 has the instructions necessary to read the unique identifier of the remote arming contact 300 and initiate the arming process. If the doors 105 are opened during counting, the arming of the container security device 110 fails. If all assembly criteria are met, the container security device 110 automatically arms itself and thereby consumes one of the preloaded keys. Also, the container security device 110 is now in an armed condition, which is identical to what would have happened if a reader had armed the container security device 110. If the doors 105 were opened after the device was armed, the device 110 security device for container 110, an alarm would be activated. The remote arming contact 300 is for single use or disposable (i.e., only for a trip - (an "armed" and a "disarmed" of the security device for HO container)). The remote arming contact 300 can be observed as the physical mode of an arming key that can also be used as a mechanical seal that complies with ISO 17172, or as a seal that complies with any of the derivatives / improvements of ISO 17172. remote arming device 300 can be physically connected to the security device for container 110, eg, (but not limited to) by the data port connector of interface 229. Remote arming contact 300 is registered and linked to a transporter / user certificate on a user server when purchased. It is possible to cross reference the carrier in a manifest so that unauthorized users of remote armed contacts 300 are avoided. The unique serial number is the ID of the remote armed contact. The unique serial number is issued by the authentication server and there is no way to duplicate it. As discussed previously, the serial number can be physically written or marked (eg bar code) on the remote arming contact 300, and programmed into an internal computer memory of the remote arming contact 300. The contact ID of the remote arming is read and programmed into the security device for container 110 once the security device for container 110 is armed. The security device for container 110 uses the ID of the remote arming contact to calculate the unique arming key . In some embodiments, the remote arming contact 300 is combined with the mechanical seal, in which case the ID of the remote arming contact is the ID of the mechanical seal. The ID of the remote arming contact can be read manually, wirelessly (e.g., via RFID or Bluetooth), ultrasonically or infrared, or by means of contact. The remote arming contact 300 can be distributed to the carrier who fills and seals the container 100 in different ways. In a first form, the carrier uses an empty container 100 in which a security device for container 110 has already been installed. The remote assembly contact 300 would already be connected to the security device for container 110. In a second form, the remote arming contact 300 is distributed with the security device for container 110 when the security device for container 110 is being recycled. The remote arming contact 300 would already be connected to the security device for container 110. In a second form, the remote arming contact 300 is distributed in a "box" (as the mechanical seals are distributed), it is separated from the security device for container 110. Then the remote arming contact 300 has to be connected in the container security device 110 before assembly. Figure 4 illustrates the remote assembly process of a container security device 110 in accordance with one embodiment of the invention. First, in step 400, the container 100 in which the container security device 110 is located is filled with the items that will be transported. Initially, the remote arming contact 300 and the security device for the container 110 are physically separate devices. Then, in step 405, the remote arming contact 300 is coupled to the security device for container 110. Specifically, the remote arming contact 300 is physically connected to the security device for container 110 by a connector (eg, the connector it can be done without using the RS-232 data port). Alternatively, the remote arming contact 300 may be in communication with the container security device 110 via a wireless connection or a contact. The security device for container 110 can be distributed to a carrier. As described above with respect to Figures 3A-C, the remote arming contact includes an indicator 325 which indicates intuitively when the remote arming contact 300 is first coupled to the security device for container 110. After the unique identifier of the remote armed contact has been communicated to the security device for container 300, this status is shown by indicator 325. For example, if indicator 325 is an LED, the LED can become a solid red color. In other modalities, LED colors other than red or green may be used. In addition, a different LED indicator 325 may be used. In step 410 of the process shown in Figure 4, the carrier waits for the LED indicator 325 to indicate that the unique identifier has been successfully communicated. In step 415 the carrier disconnects the remote arming contact 300 from the container security device 110. When the security device for container 110 detects that the doors 105 are closed and that a remote arming contact 300 is present, the security device container security 110 triggers its assembly sequence by first reading the ID of the remote arming contact outside the remote arming contact memory. The container security device 110 generates a coded arming key by combining the remote arming contact ID and the secret tag key (this process can only occur once per ID of the remote arming contact, which means that a false remote arming contact with an identical remote arming contact can not trigger the security device for container 110 to arm it again). The ID of the remote arming contact is programmed into the memory of the security device for container 110 as the load ID (mechanical ID). The security device for container 110 is now armed. If the doors 105 are opened in the future, the assembly key is deleted, which blocks the security device for container 110 from being armed with the same ID of the remote armed contact. , as described previously. The carrier closes the doors of the container 105 in step 420. In step 425 the bolt 305 is removed from the bolt cover 310. The hauler then places the remote arming contact 300 near the handle of the doors of the container 105 in step 430. In step 435, the carrier inserts the bolt 305 into the receiving opening 315 of the remote arming contact 300. When the remote arming contact 300 is removed from the container 100, it can be used as part of the mechanical seal and therefore used to physically seal the doors of the container 105 (or discarded). In the event that the remote arming contact 300 becomes a part of the mechanical seal after the security device for container 110 has been armed, the ID of the remote arming contact, which can be read from the outside, now becomes in the mechanical ID, which in turn will be marked in the manifest (bill of lading). The manifest information together with the ID of the remote armed contact and the ID of the ID container etc. it is sent or transmitted to a user server, who verifies that the carrier is authorized, i.e., compares the ID of the remote armed contact with that user (ID). If they are not equal, then this shipment must be identified. The transporter moves the container 100 in step 440. Finally, the carrier authenticates the container security device 110 and the remote assembly contact 300 in step 445. In other embodiments, an e-seal, a cable seal, or Any other seal that complies with ISO 17172 can be used instead of a bolt seal. The container security device 110 is interrogated by a reader (portable or fixed) along the supply chain, and the container security device 110 is authenticated with the authentication server 140 (using the question / answer method). ). Both the container security device 110 and the remote assembly contact 300 are registered in the authentication server 140. Because the container security device 110 and the authentication server 140 are using the same algorithm to calculate the authentication key. armed with the ID of the remote armed contact, the arming key on the security device for container 110 could be matched with the armed key on the authentication server 140 (this is the same question / answer method used for security devices for container 110 that "regularly" have been armed with a reader). Another thing that must happen when the container 100 passes a reader, is that the ID of the container security device 110 that was used to assemble this remote arming contact 300 must be reported to the user's server. Once both the ID of the container security device has been reported by a reader, and the manifest has been entered, a comparison must be made with the container ID declared in the manifest and the reported ID to verify that they are the same. If they are not the same, then this shipment will be identified. If a manifest has been entered for a security device for container 110 that is armed with a remote armed contact 300, and this manifest does not contain the ID of the remote armed contact, then this shipment will be identified. At the receiving end, when the mechanical seal is cut and the container doors are opened (without disarming the container safety device 110 with a reader), the assembly key is erased and the security device of the container 110 will record a alarm. However, the physical part of the mechanical seal that is the remote arming contact 300 (not the bolt), can be used to verify that it is the same ID of the remote arming contact as that used to assemble the container security device. 110 at the filling point and if it is, this can cancel the alarm of the container safety device 110, ie, cause the alarm to be disarmed. This is done simply by connecting the remote arming contact 300 back into the security device for container 110. This can only be done once and only with the doors open (and to be kept open for at least 30 seconds). This can only be done if the security device of the container 110 has been armed with this ID of the remote armed contact, and depends on this sequence in specific i.e. Arming and closing with the same remote armed contact 300 (which means that one will not succeed if one tries to disarm twice).

This sequence will erase the ID of the remote arming contact in the security device for container 110, which will be registered in the security device for container 110, so that there is no way in which the security device for container 110 can "unlock". arm "in this way and" rearm "by placing a" false "remote arming contact 300 again with an identical remote arming contact ID.

After the container security device 110 has been activated, the carrier has to transmit the serial number of the remote arming contact 300 to the authentication server 140 so that the container security device 110 can be authenticated by the next entity in the transportation chain that has a reader. The carrier maintains a shipping manifest that lists everything that has been loaded into a particular container 100. The carrier also includes the serial number of the remote armed contact 300 on the transportation manifest. The carrier marks the ID of the assembly pin on the transportation manifest. The bill of lading communicates with the authentication server 140 in some form (e.g., via e-mail, fax, etc.) before the authentication process is carried out. The authentication process is carried out the next time the container 100 passes a reader that is in line with the authentication server 140. As shown in figure 5, the carrier 500 is in communication with the authentication server 140 and a user server 505. The communication links can be through the Internet or a secure telephone call. Alternatively, communication links may occur through fax, email, or any other appropriate means. The user server 505 allocates remote armed contact IDs. Specifically, when the carrier buys a remote arming contact 300, the user server assigns the ID, and the remote arming contact 300 is sent to the carrier 500. The carrier could have its own user identification number ("user ID"). ") that identifies it uniquely. The user server 505 transmits the ID of the remote arming contact and the user ID to the authentication server 140. The user ID and ID of the remote arming contact ID are sent so that the authentication server 140 can associate the ID of the remote armed contact with a particular carrier. Once the container 100 has been loaded and its container security device 110 is armed, the serial number of the remote assembly contact 300 is sent from the carrier 400 to the authentication server 140 so that the contact serial number of the contact can be registered. remote armed 300. The carrier also sends the user ID to the authentication server 140. The user server 505 contains a list of all registered carriers. In case the ID of a user does not match any of the user IDs previously stored in the user server, an error could occur and an alarm be triggered in the container security device 110 when someone in the supply chain tries eventually authenticate the security device for container 110 with a reader. After the security device for container 110 is armed and the serial number of the remote arming contact 300 has been registered with the authentication server 140, the security device for container 110 must still be authenticated at the same point by the server 140. authentication 110. A reader can be used for this authentication. For example, after the container 100 is transported, a subsequent entity in the supply chain can use a reader to authenticate the key in the container security device 110.

Specifically, the reader reads the key of the security device for container 110 and transmits the key to the security device for the container server 140. In order to authenticate the security device for container 110, the original carrier and serial number of the remote arming contact 300 should be stored in the authentication server 140. The next entity in the transport chain having a reader can authenticate the security device for container 110. The next entity can be located, eg, in a distribution center or marine terminal. If the security device for container 110 has not been pre-registered properly or the assembly key is authenticated by the authentication server, an alarm will be generated. During the authentication process, the container security device 110 is matched with the serial number of the remote arming contact 300 and the user ID. There are several locations where a mechanical seal can be located on the container doors. Figures 6A-D illustrate containers having different locations for securing the mechanical seal having remote arming contact 300. Figure 6A illustrates an embodiment in which the mechanical seal is coupled with an "Enhanced Lock Device" by P &Or Nedlloyd. As shown, the container 100 may include a number of vertical rods 600 that extend upwardly below the doors of the container 105. In an area approximately one-half the vertical rods 600, a bolt 605 is located coupled to the vertical rod 600. In the event that the mechanical seal is a bolt seal, the bolt 305 can be inserted through the bolt 605 and coupled to the remote arming contact. Figure 6B illustrates a mode in which the mechanical seal is coupled to a "SecureCam". As shown, the container 100 includes a number of vertical rods 600 that extend along the top of the doors of the container 105. In an area near the lower end of one of the vertical rods 600, a bolt 615 is located. which is fixed to a vertical rod. The mechanical seal is used to secure one of the vertical rods 600 to a lower portion 610 of the container 100 so that the doors of the container 105 can not be opened without breaking the mechanical seal. In the case where the mechanical seal is a bolt seal, the bolt 305 can be inserted through the bolt 615 and coupled to the remote arming contact 300. Figure 6C illustrates an embodiment in which the mechanical seal is coupled to a "Pardo Hole". As shown, one of the vertical rods 600 is coupled with a lower rod 625 by the mechanical seal. The lower rod 625 can be coupled to the lower part 610 of the container 100. When sealed, the doors of the container 105 can not be opened without breaking the mechanical seal. Figure 6D illustrates one embodiment in which the mechanical seal is coupled to a door handle 630 of the container 100. As shown, one of the vertical rods 600 is coupled to the door handle 630. A bolt 635 is placed by above the middle part of the handle 630. In case the mechanical seal is a bolt seal, the bolt 305 can be inserted through the bolt 635 and coupled to the remote arming contact 300, so that the handle 630 is secured. When sealed, the handle 630 can not move to open the doors of the container 105 without breaking the mechanical seal. Figures 6A-D illustrate only four of the different possible locations for attaching a mechanical seal to the container 100. In other embodiments, the mechanical seal can be located in any suitable part on the container 100 to secure the doors of the container 105. In others For example, a cable seal, an e-seal, or other seal complying with ISO 17172 may be used. Figure 7 illustrates a method for using the remote arming contact 300 as part of a mechanical seal and for monitoring a shipment of a container 100. First, after the container 100 has been received at its final destination, the bolt 305 of the remote arming contact 300 is cut in step 700. Then, in step 705, the doors 105 of the container 100 are opened. The remote arming contact 300 is inserted into the container security device 110 in step 710. The user then waits for an indication of the indicator 325 in step 715. The remote arming contact 300 is connected to the container security device 110 to verify that the unique identifier of the remote arming contact 300 (to ensure that the remote arming contact 300 is the same as the one initially assembled by the security device for container 110). An alarm of the security device for container 110 is canceled in the case that the unique identifier is the same. A record of the shipment of the container 100 can be downloaded from the remote arming contact 300. Finally, in step 720, the remote arming contact 300 can be connected to a personal computer so that the record can be sent to a server for analysis. The remote arming contact 300 may be coupled to the security device for container 110 to download the record through an RS-232 connector. Alternatively, the container security device 110 can transmit the record to the remote arming contact 300 via infrared, contact, l-button, ultrasonic, a magnetic method, or any other suitable way of transmitting data. In other embodiments, instead of the remote arming contact 300 directly connected to the security device for container 110, the remote arming contact 300 may be coupled to a sensor bus that is in communication with the security device for container 110, so that the remote arming contact is indirectly connected to the container security device 110. Figures 8A-B illustrate a witness device 800 for coupling with the remote arming contact. (The doors 105 of the container 100 are omitted in Figures 8A and 8B for illustrative purposes). When the remote arming contact 300 is secured to the container door through the bolt 305, the male end 320 of the remote arming contact is not used. Also, an entity in the supply chain can couple the male end 320 of the remote arming contact 300 to the token 800 to read the unique identifier of the remote arming contact 300. Alternatively, the remote arming contact 300 may contain an element of infrared or wireless transmission, such as an RFID chip or a Bluetooth element for wirelessly communicating the unique identifier of the remote arming contact 300 to the warning light 800 or some other device. Also, both the unique identifier of the remote arming contact and the arming key of the container security device can be used for authentication purposes. As shown in Figure 8B, the warning light 800 may include a display 805 and a connector 810. The connector 810 is adapted to be connected to the male connector of the remote arming contact 300. The warning light 800 can verify that the remote arming contact contains the correct unique identifier (ie, the token 800 can authenticate the remote arming contact 300). The token 800 can also authenticate the user of the remote arming contact 300 who initially armed the container security device 110 with the remote arming contact 300. The user authentication can be formed in accordance with the method described above with respect to the Figure 4. In some embodiments, in addition to the armed contact 300, a witness is required to complete the assembly process. The witness is used so that the identity of the person / entity sealing the container 100 is known with certainty. One reason for using the token is in the event that a remote armed contact 300 is stolen, so that if the thief is discovered in time, it will be detected by a reader or the witness 800 described above in connection with figures 8A- B. The witness makes it impossible for someone not authorized to seal a container 100 to arm the container security device 110 unless they also have the token. Only authorized persons will have access to said witness. In some modalities, the token requires biometric authentication before being used. In other modalities, the person / entity must enter a password. The token is used to ensure that only the person / entity that purchased the remote arming contact 300 can use the remote arming contact 300. The token can be authorized only for a limited period of time. After the time period expires, the witness can no longer participate in the assembly process. Alternatively, instead of using a token, the person / entity may locate a specific container 100.

This can be done, eg, before the container 100 is transported, by connecting the remote armed contact 300 on a personal computer, accessing a website, and entering the container 100 for which the remote armed contact 300 and boarding are intended . The remote arming contact 300 could be programmed with a special code that can only be used by a particular container 100. Also, if the remote armed contact 300 is stolen, it would not serve to arm a container 100 except for the one that the user / entity wishes to arm for boarding. There are several ways in which the transporter / user can be authenticated. One way to authenticate a carrier is after the container security device 110 has been armed. First, the container security device 110 is coupled to the remote arming contact 300 to arm the container security device 110. During arming, a unique identifier for the remote arming contact 300 is communicated to the container security device 110. Similarly, a security device for container ID of the container security device 110 can communicate with the remote assembly contact 300 .. The carrier removes or breaks a portion of the remote assembly contact 300. The rest of the assembly contact Remote 300 can then be used as part of the mechanical seal. The removed part of the remote armed contact has the same unique identifier / serial number as that transmitted to the security device for container 110. The carrier carries the removed part of the contact to a personal computer, or any other device having the ability to communicate with a secondary system. For example, the removed part of the remote arming contact 300 may have a USB adapter, a serial port adapter, or have the ability to communicate wirelessly or in any other way the unique identifier to the personal computer. The carrier can then be connected to effectively declare that the remote arming contact 300 was used to assemble a security device for a particular container 110. An ID of the container 100 can also be related to the remote arming contact 300 and the container security device 110. Another way to authenticate the carrier is before the container security device 110 is armed. First, the carrier couples the remote arming contact 300 to the personal computer and connects to indicate that you want to arm a particular container 100. . Then a unique identifier is dropped in the remote arming contact 300 that is specifically intended for that container 100. This ensures that someone can not steal the remote arming contact 300 and uses it to arm a different container 100. An additional way to authenticate the carrier is while the container security device 110 is being armed. A token, such as an electronic device having a keyboard, is placed in communication with the container security device 110 and the remote arming contact 300. They can communicate wirelessly, or through the contact, in some embodiments. Alternatively, the remote arming contact 300 may be connected to the toggle which in turn is connected to the security device for container 110. The token is used to authenticate the transporter. For example, the carrier may be required to enter a PIN code in the witness. Once the PIN code has been acquired, the token can communicate and provide its unique ID to the security device for container 110. Later, when the security device for container 110 is read by a reader, the unique ID of the user is reported. witness. The token can be assigned to the carrier, in which a PIN code is stored in the token, and it is the one that verifies the PIN Code. In the course of time, the PIN code needs to be removed, and the witness updated. For example, a witness of type variable RSA. Also, the token identifier changes periodically. The carrier can connect to a Virtual Private Network ("VPN"). The carrier enters the carrier ID, the PIN code, and the current value displayed by the witness. The PIN code is for the remote armed contact 300, not for the carrier. In the end, the system knows that the witness was assigned to a particular carrier and can prove that the current holder of that witness is the correct person since at that time the appropriate number was displayed on the witness. The witness can provide power for the arming operation so that it is not possible to arm the security device for container 110 without it. The witness can also be used to disarm the container 100. The use of the witness to disarm the container provides certainty as to who disarmed the container 100. The witness can read the unique identifier from the mechanical seal, eg, via RFID, code bars, etc. This will allow all active electronics to be removed from the seal. The witness can also work with electronics on the seal. The witness can download the container safety device log as part of the disassembly process. There are cost and reliability advantages to using the token instead of the remote arming contact 300 for unloading. For example, someone who disarms 10-20 containers in a retail store can take the contacts to a personal computer for download. It is advantageous to spend money to add this skill to the witness and not to the contact. The user interface can also be the ID of the container security device. The witness may require that certain user income be useful. The witness could "make sure" in the sense that it identifies the carrier by the simple fact that the carrier has possession of the witness. Likewise, the witness may require a PIN code to activate, a fingerprint, other biomorphic information, or some other means to identify the carrier. The token can have a limited lifetime of a certain type with either a periodic update capability or created as one of the smart tokens that was used for the VPN logical access with variable codes. In that case, one would need the date / time of the transaction, the value of the witness at that time, and a PIN code of the carrier. This will provide a factor 2 security level without the need for the token to expire. Figure 9 illustrates a security device for container 900, a token 905 and a remote arming contact 910 in accordance with another embodiment of the invention. The token 905 has a unique ID (user) and is issued by, e.g., an authentication server. The token 905 is used to remotely authenticate the security device for container 900 and validate an arming performed by a remote arming contact 910. It can also be used as a general ID ID required to identify an individual when performing other transactions and procedures related to the container security such as those of the US government program, the Customs-Trade Against Terrorism Association ("C-TPAT"). As shown, the remote arming contact 910 is in communication with a bolt 925. At the time a container is filled, the warning light 905 is first connected to the security device for container 900. Then the token 905 authenticates the security device. security for container 900 and download the security device number for container 900 and other data (eg, the container number) stored in the security device for container 900. Next, token 905 uploads its unique user ID to the device security for container 900. Remote arming contact 910 is subsequently connected to warning light 905. Remote arming contact 910 charges its unique identifier to container security device 900 through token 905. Token 905 is in communication with the device of security for container 900 through the communication interface 930. When an indicator 915 on the witness 905 shows the color "green", the remote arming contact 910 can be disconnected from the security device for container 900. This activates the arming sequence and the generation of the arming key in the security device for container 900. The token 905 is also removed from the security device for container 900. As shown, the screws 920 hold the warning light 905 to the container security device 900. The user subsequently takes the remote arming contact 910 and the warning light 905 and closes the doors of the container 105. The security device for Container 900 is now armed. The user applies the remote arming contact 910 to a sealing location to physically seal the container 100. As another optional step, the user takes the witness 905 back to his office and connects the warning light 905 to a computer (via an RS232 connector). or any other connection) and upload information about the newly completed assembly transaction. If the user has an Internet connection, the user can upload this information to a server. At the receiving end, the container security device 900 is disarmed. The bolt 925 is cut and the doors are opened, and the base of the remote arming contact 910 is intact. The user then takes his individual token 905 and connects it to the security device for container 900. The token 905 authenticates the security device for container 900, and vice versa. The remote arming contact 910 is then connected to the warning light 905. The security device for the container 900 verifies that it is the same remote arming contact 910 that was used during the arming. The "green light" is subsequently displayed in the indicator 915 of the warning light 905. Then, the warning light 905 downloads the data of the security device for the container 900 and data recording. As another optional step, the token 905 can be removed and then taken back to the user's office to upload the transaction information to the server. In some embodiments, the witness 905 discussed above may include a screen with a variable code number that the user could use to connect to a shipment tracking server. In addition, in some embodiments, the container security device 900 authenticates the token 905. Also, the token 905 can use RF to communicate with the container security device 900 so that the doors of the container 105 can be closed when the assembly is complete. . In addition, when the witness 905 has information to transmit to the server, this communication could be made directly by the witness himself if he has a General Packet Radio Service ("GPRS") or another form of connectivity (e.g., BlueTooth, etc.). Figure 10 illustrates a token 1000 and a remote arming contact 1005 in accordance with another embodiment of the invention. As shown, the remote arming contact 1005 can be coupled to a bolt 1010. The token includes various indicating elements which may be, eg, LEDs, including a green indicator element 1015, a red indicating element 1020, and a valid indicating element 1025 The token 1000 can be attached to a container safety device to secure the container 100 transported. Although the embodiments of the present invention have been illustrated in the accompanying figures and described in the detailed description, it should be understood that the present invention is not limited to the presented mode (s), but is capable of have numerous provisions, modifications and substitutions without departing from the invention defined by the following claims.

Claims (37)

1. A system for monitoring the condition of a container, the system comprises: a container safety device to secure the container; wherein the container security device is programmably armed to implement security, the container security device is adapted to detect at least one condition of the container, to transmit information related to at least one detected condition to the location outside the container. container, and interpret the at least one condition; a remote arming contact is adapted to be removably attached to the container safety device; and wherein the remote arming contact has a unique identifier for communicating with the container security device to initiate a sequence of arming of the container security device, the remote arming contact is applied as a pull-out seal integrated at less a sealing location to physically secure the container. The system according to claim 1, wherein the communication of the unique identifier to the container security device is at least one indirect, through a sensor bus connected to the container security device, and direct from the remote armed contact to the container safety device. 3. The system according to claim 1, wherein the seal is a seal that complies with ISO 17172 and a seal derived from ISO 17172, the seal of compliance of ISO 17172 is selected from the group consisting of: a mechanical seal , a cable seal, and an e-seal. The system according to claim 1, wherein the remote arming contact includes a receiving opening for receiving a seal member to physically seal the container in the at least one sealing location. The system according to claim 4, wherein the remote arming contact is distributed as part of a seal, the seal has a bolt seal form factor, and the unique identifier of the remote arming contact is visible , and the remote arming contact is coupled to a bolt having a unique identifier representation, and after assembling the container security device, the bolt and the remote arming contact are detached from each other and the bolt is inserted into the reception opening in the remote assembly contact to seal the container. The system according to claim 4, wherein the remote arming contact is distributed as part of a seal, the seal has a cable seal form factor, the unique identifier of the remote arming contact is visible, and the remote arming contact is coupled to a cable, in which after arming the container security device, the cable is inserted into the reception opening in the remote arming contact to seal the container. The system according to claim 2, wherein the unique identifier is read from the remote assembly contact while in communication with the container security device and is used in the container security device to calculate a key of armed only. The system according to claim 1, wherein the remote arming contact includes an indicating element to indicate whether the unique identifier has successfully communicated with the container security device. The system according to claim 8, wherein the indicating element provides a conspicuous and intuitive user interface, the indicating element is selected from the group consisting of an LED, an LCD screen, a device that emits an audible sound , and a vibratory device. The system according to claim 1, wherein at the end of container loading, the remote arming contact is in communication with the container security device to disarm the container security device, cancel an alarm, verify the unique identifier of the remote armed contact and download the shipment information. The system according to claim 10, wherein the communication is at least one indirect, through a sensor bus connected to the security device for container, and direct from the remote armed contact to the security device for container. 1

2. The system according to claim 10, wherein the remote arming contact transmits information to a computer. 1

3. The system according to claim 1, wherein a token is used to complete the arming sequence, the token being unique to a particular person. 1

4. The system according to claim 13, wherein the information of a shipment from the container is downloaded to the control. The system according to claim 13, wherein the token includes an indicator element to indicate whether the unique identifier has communicated successfully with the container security device. 16. The system according to claim 13, wherein the witness is only issued to an authorized person, the witness being used to authenticate the authorized person. The system according to claim 13, wherein the token requires biometric authorization before being used, and the token is used to authenticate an authorized person. 18. The system according to claim 13, wherein the token is authorized for a period of time, and in response to the limited expiration time period, the witness has to be reauthorized to participate in the arming process. The system according to claim 1, wherein the carrier authentication occurs after the container security device has been armed, and a portion of the remote assembly contact is removed and subsequently communicates with a server. authentication, the unique identifier and the authentication information related to the carrier, the unique identifier and the authentication information are used to authenticate the carrier. The system according to claim 1, wherein before being placed in communication with the container safety device, the remote assembly contact is placed in communication with a computer and a carrier is connected to indicate that the container must be armed, and the unique identifier is downloaded to the remote arming contact to allow the remote arming contact to arm the container security device of only the container. The system according to claim 1, wherein while the remote arming contact is in communication with the container security device, a token transmits a unique token ID to the container security device in response to a transporter that enters a default PIN code in the token, the token is used to authenticate the carrier. 22. The system according to claim 21, wherein in response to the fact that a reader reads the container security device, the witness ID is reported. The system according to claim 1, wherein the unique identifier includes: a code visibly printed on the outside of the remote arming contact, and an information element stored in the remote arming contact that is used to arm the safety device for container; in which the visible number serves as the seal serial number, the information element is selected from the group consisting of: an assembly key and used to calculate an assembly key, and the information element is authenticated by the security device for container. 24. A method to monitor the condition of a container, the method consists of: securing the container with a container safety device, the container safety device is adapted to detect at least one condition of the container, transmitting information related to the minus one condition detected to a location outside the container, and interpret the at least one condition; initiating, in response to a movement of a remote armed contact related to the container security device, a sequence of assembly of the container security device, in which the remote armed contact has a unique identifier to communicate with the device of security for container to initiate a sequence of assembly of the safety device for container; and applying the remote arming contact as a pull-down seal integrated to at least one sealing location to physically secure the container. 2

5. The method according to claim 24, wherein the communication of the unique identifier to the container security device is at least one indirect, through a sensor bus connected to the container security device, and direct from the container. remote armed contact to the container safety device. The method according to claim 24, wherein the unique identifier is read from the remote arming contact and used in the container security device to calculate a unique arming key, a way to read the unique identifier of the remote arming contact is at least one indirect, through a sensor bus connected to the container security device, and direct from the remote arming contact to the container security device. The method according to claim 24, wherein the remote arming contact includes an indicating element to indicate whether the unique identifier has communicated with the container security device. 28. A remote arming contact that stores a unique identifier to communicate to a security device for a container container to initiate a sequence of arming of the container security device, the remote arming contact consisting of: a communication element to transmit a unique identifier for the container security device; and a receiving opening for receiving a security element, wherein the security element applies the remote arming contact as a pull-out seal integrated to at least one location to physically secure the container. 29. The remote arming contact according to claim 28, wherein the security element is selected from the group consisting of a cable, a bolt, and an element that complies with ISO 17172. 30. The remote arming contact according to claim 28, wherein the communication element is transmitted through at least one connection by infrared, wireless, ultrasonic, physical contact, and magnetic. 31. The remote arming contact according to claim 28, further including an indicator element to indicate whether the unique identifier has communicated with the container security device. 32. The remote arming contact according to claim 31, wherein the indicating element is selected from the group consisting of an LED, an LCD screen, a vibrating element, and a device that emits an audible sound. 33. The remote arming contact according to claim 28, wherein the remote arming contact is marked with the unique identifier. 34. A method for monitoring the condition of a container, the method consists of: receiving a container insured with a container safety device, the container safety device is adapted to detect at least one condition of the container, transmitting related information to at least one condition to a location outside the container, and interpret the at least one condition; verifying a unique identifier of a remote arming contact, in which during transportation of the container the remote arming contact is applied as a pull-out seal integrated to at least one sealing location to physically secure the container; and download, to the remote armed contact, the transportation information from the container security device. 35. The method according to claim 34, which further includes transmitting the information from the remote armed contact to a computer. 3

6. The method according to claim 34, wherein a token is used to complete a sequence of assembly of the container, the data information is downloaded to the witness, the token transmits the data directly to a computer. 3

7. A system for monitoring the condition of a container, the system consists of: a container safety device to secure at least one container door, in which the container safety device is programmably assembled to implement safety , the container security device is adapted to detect at least one condition of the container, transmit information related to at least one detected condition to a location outside the container, and interpret the at least one condition; a token for authenticating a person authorized to assemble the container security device, the token communicates a unique identifier to the container security device to initiate a sequence of assembly of the container security device; and a remote arming contact adapted to be removably attached to the token, in which the remote arming contact has a unique identifier to communicate with the witness, the remote arming contact is adapted to be applied as a pull-out seal integrated at less a sealing location to physically secure the container.