Method and system for arming a container security device without use of an electronic reader

The present invention relates to a method and system for remotely arming a container security device without using an electronic reader.

Most of the goods shipped around the world are shipped in what are called intermodal freight containers. As used herein, the term "container" includes any container (whether wheeled or not) that does not pass radio frequency signals, including, for example, intermodal cargo containers. The most common intermodal freight container is known as the International Organization for Standardization (ISO) dry intermodal container, which has been standardized worldwide for the transportation of all aspects of goods on the earth's surface. Specific dimensional, mechanical and other standards published by ISO to facilitate world trade by encouraging the development and use of containers, handling equipment, ocean-going vessels, rail and road transport equipment. Fulfill. There are more than 12 million such containers currently in circulation around the world, and more are special purpose containers (eg refrigerated containers) that carry fragile goods. The number of loaded containers received in the United States alone is nearly 6 million per year, or nearly 20,000 per day, which represents nearly half of the total value of all goods received each year.

Container transportation is the cornerstone of the global economy, as almost 90% of all internationally shipped goods are shipped in containers.

Due to the huge amount of containers shipped around the world, individual physical inspections are not feasible, and only 3-4% of the containers that actually enter the United States are physically inspected. I'm just there. There is a high risk of terrorists bringing in biological, radiation or explosive devices through containers, and the impact of such events on the international economy is significant given the importance of containers in world trade.

Even if sufficient resources were devoted to physical inspection of all containers, such work would have significant economic implications. For example, time delays alone can lead to factory closures and undesired costly delays in shipping goods to customers.

Current container designs do not provide a suitable mechanism for establishing and monitoring the security of containers or their contents. A typical container includes one or more stake mechanisms into which a plastic or metal instruction "seal" or the usual "seal" of a bolt barrier can be inserted to secure the container door. Commonly used door latch mechanisms are very easy to disable, for example, by breaking the latch mounting bolts from the door to which the latch is mounted with a drill. Also, the normal seal itself currently in use is extremely easy to invalidate by using a normal cutting tool and rather by replacing it with an easily duplicated seal.

A more advanced solution recently proposed is known as the "electronic seal (e-seal)". The e-seal is equivalent to a traditional door seal, and it is applied to the container as an accessory to the container via the same (but weaker) door latch mechanism, but like a radio or radio reflector. Including electronic devices. The electronic device can transmit the serial number of the e-seal and a signal as to whether the e-seal has been cut or destroyed after installation. However, the e-seal cannot communicate with the inside or contents of the container and does not transmit information related to the inside or contents of the container to another device. Container security devices must be armed to allow monitoring of container door integrity while the container is in transit. However, one of the challenges in implementing a global in-transit security system for freight containers is to be able to arm container security devices on demand anywhere in the world, ie, authorized arming. Properly distribute the global reading facility to download the encrypted arming key issued by the server to a given container security device. In over 130 countries, there are hundreds of thousands of freight container shippers who potentially need to use certain types of readers to carry out such arming transactions. ..

This need for readers creates problems when shipments by shippers are not regular and / or do not have an account with a carrier, making it difficult to distribute readers. In addition, some shippers may be in remote locations (China, Africa or), such as locations where wireless public network coverage or Internet capabilities are limited or absent, or where such IT capabilities are too expensive. It is not uncommon to have a location (inland in Latin America). If the number of such locations is not unusual or unusual, but rather seems to be a majority, it is very difficult to distribute readers to implement a global in-transport security system.<patcit num="1"><text>U.S. Pat. No. 6665585</text></patcit>

<p> Therefore, it would be advantageous to be able to provide a method and system for remotely arming container security devices without the use of readers, while maintaining a very high security and authentication process.</p>

<p> These and other drawbacks are overcome by various embodiments of the invention. The present invention provides a method and system for efficiently and reliably monitoring a container and its contents and tracking the container to maintain its security. More specifically, the present invention includes, on the one hand, a system for monitoring the condition of a container. The container security device secures at least one door of the container. The container security device is programmatically armed (set to security monitoring state) to achieve this fixation. The container security device is to detect at least one state of the container, transmit information related to the at least one detected state to a location outside the container, and interpret the at least one detected state. It is configured. A remote arming plug is coupled to the container security device. The remote arming plug has a unique identifier, or arming key, or other data associated with the arming key that must be communicated to the container security device to initiate the arming sequence of the container security device. The remote arming plug can be used as part of the mechanical seal.</p><p> In another aspect, the invention relates to a method for monitoring the condition of a container. At least one door of the container is secured by the container security device. The container security device is to detect at least one state of the container, transmit information related to the at least one detected state to a location outside the container, and interpret the at least one detected state. It is configured. In response to the movement of the remote arming plug, the container security device arming sequence is initiated. The remote arming plug has a unique identifier that must be communicated to the container security device to initiate the arming sequence of the container security device.</p><p> In another aspect, the present invention relates to a system for monitoring the condition of a container, which has a container security device for fixing at least one door of the container. The user server remembers the list of authorized users and issues a remote arming plug ID for the remote arming plug attached to the container security device. In response to the movement of the remote arming plug, the container security device arming sequence is initiated. The remote arming plug is coupled to the container security device. The remote arming plug has a unique identifier that must be communicated to the container security device to initiate the arming sequence of the container security device.</p><p> A more complete understanding of the exemplary embodiments of the invention can be achieved by reference to the following detailed description of the exemplary embodiments of the invention, along with the accompanying drawings.</p>

The types of container security devices featured here, illustrated and detailed below shall be positioned and secured within the container for effective monitoring of the integrity and condition of the container and its contents. Turned out to be possible. Container security devices must be armed with a unique electronic arming key for authentication purposes. The container security device can be armed using a reader, in which case the arming key is retrieved and downloaded from the authentication server that issues the arming key.

As an alternative, according to an embodiment of the invention, the remote arming plug is first coupled to the container security device. Once the remote arming plug is removed and the container door is closed, an arming key is created inside the container security device itself. As a result, the container security device can be armed with a unique arming key without using a reader. However, after the remote arming key is created, the remote arming key must then be authenticated. When a subsequent entity in the transport chain with the reader queries the container security device, the arming key in the container security device is authenticated by the authentication server.

The container security device secures at least one door of the container. The container security device may be similar to that disclosed in US Patent Application No. 10/667282 (filed September 1, 2003), the contents of which are incorporated herein by reference. The container security device is armed with a unique encrypted arming key, which ensures the security of the system. The container security device is configured to detect at least one state of the container, transmit information related to the at least one detected state to a location outside the container, and interpret the at least one detected state. Has been done. The corner member of the embodiment of the present invention is composed of a so-called remote arming plug. Remote arming plugs have unique identifiers such as unique pin combinations, serial numbers, and so on. The remote arming plug transmits this unique identifier to the container security device via any suitable means, such as infrared, wireless or physical connection. The connector can be an RS-232 connector (D-SUB) that can be connected to the data port on the back of the container security device, or it can be any other type of connector, and can also be. It can also be connected to other parts of the container security device. The remote arming plug can have a unique serial number programmed (once) in its electronic memory along with a physically marked (printed number or barcode) on it.

FIG. 1A is a schematic diagram illustrating a container 100 according to an embodiment of the present invention. The container 100 is loaded with various substances to be transported by the shipper. Container 100 has door 105, which is opened when the shipper first loads the load into container 100. The container security device 110 secures the door 105 of the container 100 after it is closed, and, for example, opens the door 105 in order for the container 100 to reach its final destination and retrieve the contents of the container 100. It remains locked until the container security device 110 is properly unarmed, such as when it needs to be opened. The container security device 110 issues an alarm when the door 105 of the container 100 is opened without being properly unarmed. The container security device 110 ensures that the container 100 is not compromised after it has been fixed. The process for arming the container security device 110 will be described later with reference to FIGS. 3A to 3F.

FIG. 1B is a schematic diagram illustrating a typical supply chain flow 120 from points (A) to (I). First, the point (A) will be explained. Cargo is loaded into the container 100 by the shipper or the like. At point (B), the loaded container 100 is transported to the shipping port by road or rail transport. At point (C), container 100 enters the gate to a shipping port, such as a seaside shipping yard.

At point (D), container 100 is loaded onto a vessel operated by a shipping company. At point (E), container 100 is shipped by sea to the landing port by a shipping company. At point (F), container 100 is unloaded from the vessel. Following the landing at point (F), container 100 is loaded onto the truck and exits the gate from the landing port at point (G). At point (H), container 100 is transported by land to a desired location in a manner similar to point (B). At point (I), the container 100 is unloaded by the consignee when it arrives at the desired location.

As will be apparent to those skilled in the art, within various points of the flow 120, there are many times that the security of the container 100 can be compromised without normal visual detection. Moreover, the state of the contents of the container 100 is completely unknown to any trader involved in the flow 120 to the point (H) where the contents are unloaded.

As mentioned earlier, the container security device 110 is armed in transit for security purposes. The container security device 110 can be armed without using an electronic reader. Therefore, a shipper who does not have any reading device can arm the container security device 110. Instead, the container security device (a) is preloaded with at least one registered key in the container security device and has a unique identifier for the arming plug in at least one arming key. One is related, (b) a unique identifier is read from the remote arming plug and used by the container security device to calculate a unique arming key, or (c) a container. -Arming can be performed by using a remote arming plug with a unique serial number, provided that the security device obtains an arming key from the remote arming plug.

FIG. 1C is a schematic diagram illustrating a system for pre-loading a key into the container security device 110 according to the embodiment of the present invention. This system includes an authentication server 140. The authentication server 140 creates a key and transmits the key to the factory 145 that manufactures the container security device 110. Therefore, the newly manufactured container security device 110 can directly store the new key before using the container security device 110 in the field. The container security device 110 that is already in use can also be replenished with additional keys in the field. For example, the authentication server 140 can transfer additional keys to a computer 150, such as a portable laptop computer. The computer 150 can transmit the key to a portable electronic device that is in communication with the replenishing container security device 110, such as a telephone 155 or a personal digital assistant (PDA) 160. Each key may be a unique number, and a different key may be used each time the container security device 110 is armed and the container 100 with the container security device 110 is shipped.

FIG. 2 is a block diagram of the container security device. The container security device 110 includes an antenna 200, an RF / baseband unit 205, a microprocessor (MCU) 210, a memory 215, and a door sensor 220. The container security device 110 further includes an interface 229 for mounting additional sensors to monitor various internal conditions of the container such as temperature, vibration, radioactivity, gas detection and motion. A remote arming plug can be coupled to interface 229 to arm the container security device 110, as described later, but not exclusively, with reference to FIGS. 3A-3F.

The container security device 110 can also include a power supply 230 (eg, a storage battery), at its discretion. However, other removable or remotely located power supplies can also be utilized by the container security device 110. When the power supply 230 contains a storage battery (as shown in the figure), providing the power supply 230 in the container security device 110 means that the temperature fluctuation received by the power supply 230 due to the power supply 230 being inside the container 100 is relative. As it becomes smaller, it helps to extend the life of the storage battery. Providing the power supply 230 inside the container 100 is advantageous because it reduces the possibility of tampering with or damaging the power supply 230. The container security device 110 can also optionally include a connector for direct connection to the electronic reader. For example, a connector can be placed on the outer wall of container 100 for access by a reader. Although not required to arm the container security device 110, the reader can be connected via a cable or other direct interface to download information from the container security device 110.

The microprocessor 210 (with internal memory) recognizes events from the door sensor 220 on the door 105, including, for example, a container arming release request and a container security check. Perceived door events also include security breaches that can compromise the contents of the container 100, such as opening the door 105 after fixing the container 100. Door events can be timed and stored in memory 215 for transmission to the reader device. Door events can be transmitted immediately, periodically, or in response to inquiries from the reader. The door sensor 220 shown is of pressure sensing type, but instead is, for example, a contact sensor, an proximity sensor, or any other type of sensor that detects relative movement between two surfaces. Good. Therefore, the term "pressure sensor" used in this document is not limited to this, but includes such other types of sensors.

The antenna 200 is provided for exchanging data with the reader. Specifically, various information such as status / state and control data can be exchanged. The microprocessor 210 can be programmed with code that uniquely identifies the container 100. The code can be, for example, an International Organization for Standardization (ISO) container identification code. The microprocessor 210 can also store other physical distribution data such as bills of lading (B / L), mechanical seal numbers, time-recorded read identification numbers, and so on. A special record file can be created so that the tracking history can be recovered with the events at Door 105. The code can also be transmitted from the container security device 110 to the reader for identification purposes. The RF / baseband unit 205 translates the microprocessor signal upward frequency from baseband to RF for transmission to the reader.

The container security device 110 can receive an integrity inquiry from the reader via the antenna 200. In response to a query about integrity, the microprocessor 210 accesses memory 215 to extract, for example, door events, temperature readings, security breaches, or other stored information, and these extracted information. Can be transferred to the reader. The reader can also send a dearming request to the container security device 110. When the container 100 is armed, the memory 215 of the container security device 110 issues a sonic or visual alarm when the door sensor 220 detects a substantial change in pressure after the container 100 is locked. Can be programmed to do. The container security device 110 can also record a security breach in memory 215 for transmission to the reader. If the reader sends an unarming request to the container security device 110, the microprocessor 210 either ceases to record the event at door 105 or is connected to the container security device 110 to interact. It can be programmed to stop receiving signals from the door sensor 220 or other sensors.

The shipper can arm the container security device 110 with a pre-loaded security key, and the container security device 110 is another entity that inspects the container security device 110 by a reader. It can be authenticated later (for example, another entity along the supply chain).

A remote arming plug is required to arm the container security device 110 without using a reader. FIG. 3A illustrates a container security device 110 and a remote arming plug 300 according to an embodiment of the present invention. When the container security device 110 is mounted / coupled to the wall or door 105 of the container 100, the remote arming plug 300 is initially inserted into interface 229. The interface 229 can include a female connector, the remote arming plug 300 can include a male connector, and the combination of active pins of the remote arming plug 300 is used to make the remote arming plug 300 unique. Can be identified. The remote arming plug 300 can also include a serial number written on any of its bodies, as shown in FIGS. 3B and 3C.

In practice, the container security device 110 is mounted on the wall of the container 100, as shown in FIG. 3D. After the container 100 is fully loaded, the door 105 is closed and the male end 305 of the remote arming plug 300 is initially inserted into the interface 229. To arm the container security device 110, the remote arming plug 300 is removed from interface 229. As shown in FIGS. 3E and 3F, the remote arming plug 300 can be manually removed from the container security device 110. After a short delay, for example 30 or 60 seconds, the container security device 110 is armed. As an alternative, after being separated from interface 229, the remote arming plug 300 can communicate with other components connected anywhere on the container security device 110, and the container door 105. Can be part of a mechanical seal used to physically seal the door.

As shown in FIGS. 3E and 3F, when the remote arming plug 300 is first removed, the container security device 110 goes into arming ready, then after the door 105 is closed and counted down. , The container security device 110 enters the armed state. In an alternative embodiment, the remote arming plug 300 can remain attached to the container security device 110 as part of the mechanical seal of the container security device 110. Then, when the door 105 of the container security device 110 is closed and the pressure from the gasket of the door 105 reaches the appropriate limit for arming the container security device 110, a countdown (eg, 60 seconds) will occur. Start.

The unique identifier of the remote arming plug 300 conveys its identity to the container security device 110, which initiates its countdown timer. The container security device 110 reads the unique identifier from the remote arming plug 300 and has the necessary instructions to start the arming process.

If door 105 is opened during the countdown, arming of container security device 110 will fail. Otherwise, if all of the arming criteria are met, the container security device 110 automatically armes itself, thereby consuming one of the pre-loaded keys. Therefore, the container security device 110 is in the armed state at this time, which is the same as what happens when the reading device armed the container security device 110. If the door 105 is opened after the container security device 110 has been armed, an alarm is raised.

The remote arming plug 300 is disposable (ie, valid for one trip (one "arming" and one "unarming" of container security device 110)). The remote arming plug 300 can be considered as a physical embodiment of the arming key and can also be used as an ISO 17172 compliant mechanical seal. The remote arming plug 300 is physically connected to the container security device 110, for example, through the data port connector of interface 229 (but not exclusively). The remote arming plug 300 is registered at the time of purchase and linked to an authorized shipper / user within the user server. It is possible to cross-test shippers on the cargo inventory to prevent unauthorized users of the remote arming plug 300. The unique serial number is the remote arming plug ID. The unique serial number is issued by the authentication server and there is no way to duplicate it. As mentioned earlier, the serial number is physically written or marked (eg, barcode) on the remote arming plug 300 and programmed into the internal computer memory of the remote arming plug 300. Once the container security device 110 is armed, the remote arming plug ID is read by the container security device 110 and programmed within the container security device 110. The container security device 110 uses the remote arming plug ID to calculate a unique arming key. In some embodiments, the remote arming plug 300 is combined with a mechanical seal, in which case the remote arming plug ID is the mechanical seal ID. The remote arming plug ID can be read manually, wirelessly (eg, RFID or Bluetooth), via infrared or via contacts.

The remote arming plug 300 can be distributed differently to shippers who load and seal the container 100. In the first method, the shipper utilizes an empty container 100 in which the container security device 110 is already installed. The remote arming plug 300 is already plugged into the container security device 110.

In the second method, the remote arming plug 300 is distributed with the container security device 110 when the container security device 110 is being recycled. The remote arming plug 300 is already plugged into the container security device 110.

In the third method, the remote arming plug 300 is distributed in a "box" separate from the container security device 110 (similar to the mechanical seal being distributed). The remote arming plug 300 must then be plugged into the container security device 110 prior to arming.

FIG. 4 is a flow chart illustrating a remote arming process of a container security device according to an embodiment of the present invention. Initially, the remote arming plug 300 and the container security device 110 are physically separate devices. At stage 400, the remote arming plug 300 is coupled to the container security device 110. Specifically, the remote arming plug 300 is physically plugged into the container security device 110 by a connector (eg, a connector that can be connected without using an RS-232 data port). The container security device 110 can be distributed to the shipper.

At stage 405, load into container 100. After loading into container 100, at step 410, the remote arming plug 300 is separated from the container security device 110, and a few seconds later the container door 105 is closed. When the container security device 110 detects that the door 105 is closed and the remote arming plug 300 is present, the container security device 110 starts its arming sequence, first from the memory of the remote arming plug. Read the remote arming plug ID. The container security device 110 creates a unique encrypted arming key by combining the remote arming plug ID with the secret tag key (this process occurs only once for the remote arming plug ID. This means that a fake remote arming plug with the same remote arming plug ID cannot trigger container security device 110 to arm again). The remote arming plug ID is programmed in the memory of the container security device 110 as a load ID (mechanical ID). Here, the container security device 110 is armed. Subsequent opening of the door 105 erases the arming key, which prevents the container security device 110 from being armed with the same remote arming plug ID as previously mentioned.

The remote arming plug 300 can be used as part of the mechanical seal when removed from the container 100 and therefore can be used to physically seal the container door 105 (otherwise discarded). To do). After the container security device 110 is armed, the remote arming plug 300 is mechanically<u style="single">sticker</u>If it becomes part of, the externally readable remote arming plug ID then becomes the mechanical ID, which is then marked on the bill of lading. The cargo catalog information is sent or transmitted to the user server together with the remote arming plug ID, the container ID, etc., and the user server is authorized by the shipper, that is, the remote arming plug ID is the user (ID). ) Is verified. If they are not the same, this shipment should be targeted.

Container 100 is shipped in stage 415. At stage 420, container security device 110 is queried by a reader (handheld or stationary) along the supply chain, and container security device 110 is queried by authentication server 140 (using a call / response method). Be authenticated. Both the container security device 110 and the remote arming plug 300 are registered in the authentication server 140. Since the container security device 110 and the authentication server 140 use the same algorithm to calculate the arming key from the remote arming plug ID, the arming key in the container security device 110 is the arming in the authentication server 140. It can match the key (this is the same call / response method used for container security device 110 that is armed "regularly" by the reader). Another thing that needs to happen when container 100 passes through the reader is to report the ID of the container security device 110 armed with this remote arming plug 300 to the user server. .. Once the container security device ID is reported by the reader and the inventory is presented, a comparison is made between the container ID declared in the inventory and the reported ID to show that they are the same. Should be verified. If they are not the same, this shipment should be targeted. If an inventory is presented for the container security device 110 armed by the remote arming plug 300 and this inventory does not include the remote arming plug ID, then this shipment should be targeted.

At the receiving end, the arming key is erased and the container is erased when the mechanical seal is cut and the container door is open on the recipient's side (without unarming the container security device 110 by the reader). -The security device 110 records the alarm. However, the physical part of the mechanical seal, which is the remote arming plug 300 (not the bolt), can be used again to actually "unarm" the container security device 110 to cancel the alarm. This is done by simply plugging the remote arming plug 300 back into the container security device 110. This can only be done once if the door is open (and stays open for at least 30 seconds). This can only be done if the container security device 110 is armed with this remote arming plug ID and relies on this particular sequence, arming and closing with the same remote arming plug 300. Yes (this means that if you try to unarm twice, you won't succeed). This sequence erases the remote arming plug ID in the container security device 110, which is recorded in the container security device 110, thus "unarming" the container security device 110 and the same. There is no way to "re-arm" by reverting a "fake" remote arming plug 300 with a remote arming plug ID.

After the container security device 110 is activated, the consignor by sending the serial number of the remote arming plug 300 to the authentication server 140, the next container security device 11 by an entity in the transportation chain with reader 0 Must be able to authenticate. The shipper maintains a shipping inventory that lists everything loaded into a particular container 100. The shipper also includes the serial number of the remote arming plug 300 on the shipping inventory. The shipper marks the arming plug ID on the shipping inventory. The shipping inventory can be communicated to the authentication server 140 in some way (eg, via email, fax, etc.) and then the authentication process can be performed. The authentication process then takes place the next time container 100 passes through authentication server 140 and a reader that is online.

As shown in FIG. 5, the shipper 500 is in communication with the authentication server 140 and the user server 505. The communication link may be by calling the Internet or a telephone with an eavesdropping prevention function. Alternatively, the communication link can be generated by facsimile, email, or in any other suitable manner. User server 505 assigns a remote arming plug ID. Specifically, when the shipper purchases the remote arming plug 300, the user server assigns its ID and the remote arming plug 300 is sent to the shipper 500. The shipper can have its own user identification number (user ID) that uniquely identifies it. The user server 505 transmits the remote arming plug ID and the user ID to the authentication server 140. Both the user ID and the remote arming plug ID are sent so that the authentication server 140 can associate the remote arming plug ID with one particular shipper.

When the container 100 is loaded and the container security device 110 is armed, the serial number of the remote arming plug 300 is sent from the shipper 500 to the authentication server 140, and the serial number of the remote arming plug 300 is sent. To be able to register. The shipper also sends the user ID to the authentication server 140. User server 505 contains a list of all registered shippers. If the user ID does not match any of the previously stored user IDs in the user server, an error can occur and someone in the supply chain will eventually get the container security device 110 by the reader. The container security device 110 can issue an alarm when trying to authenticate.

After the container security device 110 is armed and the serial number of the remote arming plug 300 is registered by the authentication server 140, the container security device 110 still needs to be authenticated by the authentication server 140 at some point. A reader can be used for this authentication. For example, after container 100 is shipped, subsequent entities in the supply chain can use the reader to authenticate the key in container security device 110. More specifically, the reader reads the key from the container security device 110 and transmits the key to the authentication server 140. In order to authenticate the container security device 110, the original shipper and the serial number of the remote arming plug 300 must be stored in the authentication server 140.

The next entity in the transport chain that has a reader can authenticate container security device 110. The following entities may be located, for example, in a distribution center or maritime cargo depot. An alarm is raised if the container security device 110 is not properly pre-registered, or if the arming key is authenticated by the authentication server. During the authentication process, the container security device 110 matches the serial number and user ID of the remote arming plug 300.

Although the embodiments of the present invention have been described by way of exemplifying the drawings, the present invention is not limited to the embodiments disclosed by the present invention, and a large number of rearrangements, modifications and substitutions are made without departing from the invention defined by the claims. Will be understood that can be done.

<figref num="1A">It is a schematic diagram which illustrates the container by one Embodiment of this invention.</figref><figref num="1B">It is a schematic diagram illustrating a typical supply chain flow.</figref><figref num="1C">It is a schematic diagram which illustrates the system for preliminarily charging the key into the container security device by one Embodiment of this invention.</figref><figref num="2">It is a block diagram of a container security device.</figref><figref num="3A">It is a schematic diagram which illustrates the container security device and the remote arming plug by one Embodiment of this invention.</figref><figref num="3B">FIG. 5 is another schematic illustrating a container security device and a remote arming plug according to an embodiment of the present invention.</figref><figref num="3C">FIG. 5 is another schematic illustrating a container security device and a remote arming plug according to an embodiment of the present invention.</figref><figref num="3D">FIG. 5 is another schematic illustrating a container security device and a remote arming plug according to an embodiment of the present invention.</figref><figref num="3E">FIG. 5 is another schematic illustrating a container security device and a remote arming plug according to an embodiment of the present invention.</figref><figref num="3F">FIG. 5 is another schematic illustrating a container security device and a remote arming plug according to an embodiment of the present invention.</figref><figref num="4">It is a flow chart which illustrates the remote arming process of the container security apparatus by one Embodiment of this invention.</figref><figref num="5">It is a schematic diagram illustrating a remote arming system including a shipper who has a communication relationship with an authentication server and a user server.</figref>

Code description

100 containers 105 door 110 Container security device 120 Supply chain flow 300 remote arming plug 305 Male end