• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    LOAD MONITORING METHOD AND SYSTEM AND RELATED COMPUTER-READABLE NON-TRANSITORY MEDIA Improved methods and systems for securing and monitoring cargo are described. Some examples provide a cargo monitoring system ("CMS") that is configured to track, identify and report on anomalous conditions or events related to cargo transfers. The CMS may include a software system that receives condition information from electromechanical locks that secure a load. The locks include data terminals that facilitate near-real-time load monitoring. Electromechanical locks are installed on bars or other mechanisms (eg, door rings) that lock the doors of a cargo container, train car, van door, or the like. Data terminals include logic that is configured to transmit information about current conditions to the CMS, such as location, temperature, lock status (eg, open or closed), tampering attempts, and the like. The load monitoring system interprets the information received and performs various actions based on it, such as transmitting alerts if anomalous conditions are detected.
    公开号:BR112015017999B1
    申请号:R112015017999-1
    申请日:2014-01-28
    公开日:2022-02-01
    发明作者:Mauricio Lloreda；Ivan Lopez；Daniel Herrera
    申请人:Commercial Finance Corporation, Sa De Panama；
    IPC主号:
    专利说明:

    TECHNICAL FIELD
    [001] The present disclosure concerns methods, techniques, and systems for monitoring cargo that is protected by smart locks, such as tracking and identifying anomalous conditions related to cargo. BRIEF DESCRIPTION OF THE DRAWINGS
    [002]Figure 1A is an example block diagram of a load monitoring system according to an exemplary embodiment.
    [003]Figure 1B is an example block diagram showing logical elements of a load monitoring system according to an exemplary embodiment.
    [004]Figure 2A and 2B are user interface screens provided according to an exemplary embodiment.
    [005]Figures 3A - 3E are example views of smart locks according to exemplary embodiments.
    [006]Figures 4.1 - 4.13 are flowcharts of load monitoring processes performed by the exemplary modalities.
    [007]Figure 5 is a block diagram of an exemplary computing system for implementing a load monitoring system according to an exemplary embodiment.
    [008] Figure 6 is a block diagram showing components of an exemplary smart lock according to an exemplary embodiment. DETAILED DESCRIPTION
    [009] Modalities described here provide improved methods and systems to secure and monitor cargo. The described techniques applied to units of cargo, including cargo containers, reefer containers (“refrigerators”, vans, cars or railroad cars, air cargo containers, and the like.
    [010]Some modalities provide a cargo monitoring system that is configured to track, identify, and report on anomalous conditions or events related to cargo transfer.
    [011]The load monitoring system may be or include a software system that receives condition information from the electromechanical locks that protect the load. The locks include data terminals that facilitate real-time (or near real-time) monitoring of the load. Electromechanical locks (sometimes also referred to as “smart locks”) are installed on bars or other mechanisms (e.g. door rings) that lock the doors of a freight container, train car, van door , or similar. The data terminals include logic that is configured to provide (e.g., transmit, send, load) information from the load monitoring system about current conditions, including one or more of location, temperature, lock status (e.g. e.g. open, closed), tampering attempts, and the like. Information provided to the cargo monitoring system by a data terminal can be transmitted in a variety of ways, such as satellite, cellular network, local area network (e.g., Wi-Fi access point), short-band (eg Bluetooth), or similar. The cargo monitoring system interprets the information received and performs various actions based on it, such as transmitting alerts if anomalous conditions are detected. System Overview
    [012]Figure 1A is an exemplary block diagram of a load monitoring system according to an exemplary embodiment. Figure 1a shows a cargo monitoring system (“CMS”) 100 that is configured to track the movement of cargo, determine if cargo has been shipped or diverted from a specific route, and transmits notifications regarding such deviations or other conditions. In the illustrated example, a truck 102 loads a cargo container 104 which is locked with a smart lock 101. The smart lock 101 determines its current location based on a signal obtained from a GPS satellite 110. The smart lock 101 may also or rather determine its location based on other information, such as cellular network location information, wireless network location information, roadside beacons, or the like. Smart lock 101 then transmits condition information (including an indication of its current location) via cellular equipment 112 and a corresponding network 45 to system 100. Smart lock 101 may also or instead use network facilities such as Wi-Fi. Fi, Bluetooth, or similar. The condition information transmitted by the smart lock 101 may include other information, including lock status, temperature, acceleration, position, tilt, and the like.
    [013]The CMS 100 performs functions such as those described below with respect to Figures 4*. In general, as further described below, the CMS 100 detects, identifies or determines anomalous conditions or events based on condition information received from the smart locks. Such events may include deviations from a planned or planned route of travel, the occurrence of a U-turn, an intrusion of the lock, an attempt to remove a door (from a container), excessive speed, stopping at known hazardous locations, and the like. When such events/conditions are identified by the CMS 100, the CMS transmits notifications, which may include messages, alarms, alerts, or the like. The CMS 100 can provide a hierarchy or escalation structure of notifications or actions that are taken in response to detected anomalous conditions, such as using text messaging to transmit informational messages and initiating telephone calls to transmit warnings or alarms (e.g., for detected intrusions).
    [014]Figure 1B is an exemplary block diagram showing logical elements of a load monitoring system according to an exemplary embodiment. Figure 1B shows a load monitoring system ("CMS") 100 comprising a location tracker 120, a route manager 122, a load monitor 124, and a data store 126. The CMS 100 interacts with a customer device 130 operated by a user 106. The CMS 100 also receives information from one or more smart locks 101 and maps information sources 131. Next, the CMS 100 is for convenience and readability sometimes described as receiving information about or from a cargo unit (eg a container, truck, van, or the like), when actually information is received from a smart lock associated with the cargo unit.
    [015]Location tracker 120 tracks the location of cargo units based on information received from smart locks 101. Location tracker 120 receives condition information from smart lock 101, and stores the received information in the data store 126 for use by the other components of the CMS 100. The received condition information typically includes a lock identifier and at least an indication of the current location of the smart lock. Other condition information may include temperature, acceleration, slope, and the like.
    [016]Route manager 122 manages load routes. In some embodiments, route manager 122 may provide an interactive user interface (e.g., a mapping interface) that may be displayed on client device 130 and used by user 106 to interactively establish a route. The route may be drawn or otherwise indicated on a map by the user 106. Map information may be initially obtained from map information sources 131, which include any map or geographic information source, including public or private mapping systems. , GIS systems, or the like. Having established a route, the route can be named and stored in data store 126 so that it can then be associated with one or more freight transports. A route can be represented in various ways, such as a sequence of road segments, points, lines, areas/regions, or the like, through which a given unit of load must travel.
    [017]Load monitor 124 monitors load units as they travel their associated routes. For each load unit and corresponding smart lock 101, load monitor 124 accesses data store 126 to obtain condition information received from smart lock 101 and route information associated with smart lock 101. Load monitor 124 cross-references the current location of the smart lock 101 against the route, in order to determine if the cargo unit has been diverted from the route. The load monitor 124 may also or instead check other condition information to determine if other anomalous conditions are present, including temperatures (e.g., too high or too low), over-speed, over-throttle/tilt. , or similar.
    [018]Load monitor 124 may send alerts and other types of reports to client device 130. For example, deviations from a designated route or other anomalous conditions may result in an alert being transmitted by load monitor 124. As another example , load monitor 124 can provide location update or general conditions in response to specific conditions/triggers, such as time-based trigger (e.g., every hour), distance-based trigger (e.g., every 50 km travelled), location-based trigger (eg when a specific city or town is reached), or similar. Alerts and reports can be transmitted using various mechanisms, including email, text message, automated phone call, web page refresh, or the like.
    [019] In some embodiments, the charge monitor is initially provided with (1) a photograph of a properly installed smart lock, taken and sent via the internet or other mechanism to the CMS, and (2) a corresponding activation signal sent by the smart lock once it is installed. Having received this information the load monitor 124 begins monitoring the progress of the lock along its assigned route.
    [020] The load monitor 124 may also or instead be able to detect, interpret, and correspondingly transmit an alert if the load unit is still stationary or “walking around” before entering the road network to take part and form the route. Also, since the cargo unit does not enter the chosen road from the beginning of such a route, the CMS transmits an alert about the actual start of the monitored trip. Once the cargo unit travels the entire programmed route (eg reaches the destination), the CMS transmits a corresponding alert to all interested parties.
    [021]The load monitor 124 may also or instead support concepts such as rest areas, authorized stops/walking zones, and/or hazardous areas. For example, a route may specify specific areas in which a cargo unit may stop, or may stop for up to a specified, predetermined, or configured period of time, so that a safe rest area or supply facility is available. An authorized ride zone can be specified to a given load unit driver some freedom in selecting the best route based on site conditions and knowledge. For example, a ride area can be specified at the beginning of a route, to give the driver freedom to select the best route for the entrance or the road or other main thoroughfare along which the route travels. Maximum times can be assigned within walking zones, in order to guarantee the cargo unit to leave the walk zone and re-route within a limited amount of time. A route may also or instead specify particular areas in which the cargo unit must not stop, or must not stop for more than some time. If a load unit is determined to have to stop at a hazardous one, load monitor 124 can transmit an alert.
    [022]Load monitor 124 may also or instead track speed of the load unit, such as detecting excessive speeds. A route may include associated speed limits, possibly on a segment-by-segment basis. By tracking location reports provided by the smart lock, load monitor 124 can determine an average speed across two or more location reports. If the speed exceeds a specified maximum, load monitor 124 may transmit an alert. Speed limits can be manually applied and/or obtained from map information sources 131.
    [023]The load monitor 124 may also or instead determine an estimated time of arrival. Estimated arrival time can be determined based on current position, current speed, information from nearby road conditions, and the like. Load monitor 124 may transmit the estimated time of arrival as part of a status report or other communication.
    [024]The load monitor 124 may also or instead determine a direction of travel and/or whether a U-turn has been performed. Direction of travel can be determined by reference to various types of information, such as compass information provided by the smart lock, successive GPS coordinates, distance to/from destination or other route marker, or the like. For example the load monitor 124 can detect that the distance between the load unit and the destination is increased (rather than decreased), thus indicating that the load unit is traveling away from the destination. If the load monitor 124 determines that the load unit has reversed course, it may transmit an alert.
    [025]Load monitor 124 can handle intermittent communication and/or other communication problems in various ways. Typically, load monitor 124 will transmit an alert when it has not received communication from a smart lock for a specific (or predetermined, configured, or otherwise designated) amount of time (e.g., 5 minutes, 10 minutes ). In some cases, specific portions of the route may be designated as regions of poor cell coverage. When a cargo unit enters such a portion of the route, the cargo monitor 124 may elect not to transmit any alerts (because miscommunication is expected), and may determine an estimated time when the cargo unit is expected to emerge from the area. and re-establish communication. If there is no communication at or after the estimated time, the load monitor may transmit an alert to indicate that no communication is being received from the load unit.
    [026]The CMS 100 provides alert level and/or scale functions. For example, messages sent by CMS 100 to client device 130 may be coded (eg, color coded) to indicate a level or type of message. For example, a green message might indicate a report/update of normal conditions. A yellow message may indicate a warning, such as a smart lock communication has ceased for more than 2 minutes but less than 5 minutes. A red message may indicate a critical warning, such as communication from a smart lock has ceased for more than 5 minutes.
    [027] In addition to messages coded to reflect the type or severity of the condition, the CMS 100 may utilize different communication channels depending on the type or level of condition. For example, critical notices can be transmitted by text message and by an automated telephone call, whereby information messages can be provided to a Web page, which can be verified when needed by the user 106. Different parties can also be specified. For example, pleasure or security services can be notified of critical conditions (eg, breach of lock), whereby a message indicating arrival at a destination can be transmitted only to transport and receive parts. 2. Example of User Interface Aspects
    [028]Figure 2A and 2B are user interface screens provided according to an exemplary embodiment. In particular, Figure 2A shows a user interface screen 200 that is configured to specify, design, or modify a load route. User interface screen 200 displays a map 201 of a road network connecting two cities, labeled City A and City B. The road network comprises multiple connected road segments, each segment connecting two arrival points labeled A-I. Thus, the illustrated road network includes road segments AB, BC, CD, DE, EF, BG, GJ, GH, GC, and CI. City A and City B are represented as shaded regions each containing a respective square-shaped point labeled Start and End. The Start and End points represent the start and end points of a route 202, discussed below.
    [029]The road network shown on map 201 is annotated with a load route 202, indicated as a dotted line connecting two points labeled Start and End, and passing along road segments AB, BC, CD, DE, and EF. The road segments of route 202 are the road segments along with the load unit that is expected to travel. Deviations from route 202 will cause the CMS to transmit an alert or other report indicating the deviation. For example, if the cargo unit travels through segments BG and BH to reach City B, CMS will transmit a report that the unit deviated from the requested route 202.
    [030] The user interface shown may be interactive, so that it can be configured to receive user input that specifies required road segments or other restrictions or properties of the route 202. In the illustrated example, the screen 200 includes a control of tool selection 208. Selection control 208 includes icons for selecting various interactive tools that can be used to select or modify route segments 200, design new segments, and specify constrained regions, as described further below.
    [031]Load route 202 is further annotated with regions 203-205 that are used to indicate areas associated with special conditions, triggers, or other handling or processing otherwise by the CMS. Regions 203205 can be specified by the user interface by selecting an appropriate tool from control 208, so that the user can select, draw or otherwise specify the shape and/or type of region. Different shapes can be supported, including circles, ellipses, rectangles, trapezoids, arbitrary polygons, or the like.
    [032]Region 203 is designated the “stop” or “rest” region, which has been identified as a safe place to stop the cargo unit for purposes such as driver rest, refueling, vehicle maintenance, or the like. In an exemplary embodiment, the default behavior of the CMS is to issue an alert if a load unit stops anywhere longer than a standard stop time (eg, 5 minutes). However, if the cargo unit stops its journey in region 203 for longer than the default allowable stop time, CMS will not issue an alert, as is expected and permitted for the cargo unit to rest its journey within of region 203. The user can also specify a maximum allowable stop time (eg 30 minutes) associated with region 203, so that CMS will issue an alert if the load unit stops longer than the time.
    [033]Region 204 is designated a “non-stopping” or “dangerous” region, which has been identified as a region in which the cargo unit is not allowed to stop. For example, region 204 may be associated with high crime, so that there is a substantial risk of the cargo unit being stolen or otherwise compromised, particularly if the cargo unit is stopped for a substantial period of time. If the cargo unit pauses its travel in this region 204 for any time (or longer than a specified, default, or specified time), the CMS will send an alert. The alert transmitted in this circumstance can also or instead be escalated, so that using different or multiple communication mechanisms (eg, placing a phone call instead of or in addition to sending a text message).
    [034]Region 205 is designated a “poor communication” region, which has been identified as a region in which cellular coverage and communication is poor, not possible, or otherwise degraded. As the load unit enters region 205, the CMS will estimate the time in which the load unit must leave region 205. During this time period, the CMS will not send alerts or warnings related to a lack of communication received from the unit. load, because such a miscommunication is expected. If the load unit does not resume communication at or around the expected exit time, the CMS will begin transmitting notifications of the fact, possibly on a scalar basis, based on the delay time.
    [035] In addition, the CMS can transmit a notification when the cargo unit enters region 205, so that an operator or other person is notified of this condition.
    [036]As discussed, the techniques described can support the concept of “walking”. In this example, route 202 provides the cargo unit with flexibility in terms of route decisions while the unit is within the boundaries of City A and City B. This allows the cargo unit to pick and choose the best or preferred route (p. .eg based on local conditions) between the Start point and point A (the beginning of the road segment AB) and between point F and the End point. Note that even then the cargo unit is allowed to roam between Cities A and B, and CMS will continue to monitor the unit's location and progress, so that anomalous conditions can still be detected, such as long stops, sudden accelerations, inclines. steep slopes, significant temperature changes, and the like.
    [037] Figure 2B shows a user interface screen 210 that is configured to display load tracked information. Screen 210 displays the map 201 and route 202 described with respect to Figure 2a, above. In addition, the map 201 is annotated with a truck indication 211 that reflects the current (or most recently reported) location of a tracked cargo unit. Map 201 is also annotated with markers 212, shown here as triangles (eg, marker 221a) and stars (eg, marker 212b).
    [038]A triangle-shaped marker such as a marker 212a indicates that a reported normal condition has been transmitted by a load unit (and received from) at or about the indicated location. In some embodiments, a user may click marker 212a to obtain additional information, such as GPS coordinates, temperature readings, and the like.
    [039]A star-shaped marker such as a marker 212b indicates that an alert has been transmitted by the cargo unit at or near the corresponding location. For example, the load unit may have stopped for longer than a standard stop time, an excessive temperature reading may have been obtained, excessive vibration or tilt may have been detected, or the like. The marker 212a may also be interactive, such that a mouse click or touch pad will result in the display of additional information about the alert.
    [040] In other embodiments, other or additional user interface techniques may be employed. For example, color coding can be used to reflect a severity grade, temperature readings, or the like. As another example, multiple load units can be tracked at the same time and through the same screen. Audit annotations may also be included. 3. Example of smart locks
    [041]Figures 3 A-3E show example of smart locks according to exemplary modalities. Figures 3A-3C are views of a first example of a smart lock 300 that is configured to secure a shipping container. In particular, Figure 3A is a front perspective view of the smart lock 300. Figure 3B is a rear perspective view of the smart lock 300. Figure 3C is an image showing the smart lock 300 as deployed to secure a shipping container.
    [042]The Illustrated Smart Lock 300 includes built-in electronic sensors designed and installed to detect the lock or opening of the unit by a “seal/lock” pattern. On detection, the unit reports installation or uninstallation. By means of this detection, the smart lock also reports it due to installation in the cargo unit (eg a shipping container). Similarly, the smart lock also detects when a seal is removed, generating the corresponding report. The smart lock also has built-in sensors configured to detect if the unit is removed from the container in an unconventional way, such as cutting off your arms. If such a violation is detected, the smart lock immediately triggers a corresponding alarm. The smart lock also includes self-calibrating electronic sensors that are configured to understand and report the spatial position in which the unit has been installed. If the unit leaves the position initially set by these sensors, the unit may trigger an alarm. The smart lock also detects changes in position or angle of container doors, door removal and unit removal.
    [043]The smart lock also includes a battery meter that monitors its battery level, reporting to CMS. The system has a pre-programmed set of patterns to determine when a battery is OK, when the battery is low, and when the battery enters an emergency state. A low battery level can also be programmed as an automatic report. In some modes, the smart lock supports three different types of energy consumption: “Deep economy”, “Medium economy” and “normal consumption”. These can be remotely configured and modified via a wireless command, according to need and corresponding travel demand, customer indications, and the like. The smart lock sends a report when it receives a command for economy mode, knowing the execution of the command.
    [044]The smart lock 300 can allow the addition of a second set of batteries. Providing extra space inside the lock for extra batteries increases the operational time frame for the lock, making it capable of operating on a global transport time scale, including lengthy sea voyages. The batteries in the smart lock can also be recharged from outside, thus eliminating the need to open or disconnect the smart lock in order to revive the batteries.
    [045]Smart lock 300 is also configured to transmit route restart notifications. In particular, the smart lock is configured to detect when it has been stopped for a specific period of time and once it detects movement again, it sends a report to alert on “return route” to the CMS.
    [046]Smart lock 300 can also be configured to vary its frequency report. For example, the CMS can transmit to the smart lock a signal, instruction, or other message that modifies a standard frequency interval report (eg every minute, every 5 minutes, every half hour). When the smart lock receives such an instruction, it can respond by transmitting to the CMS a message acknowledging receipt and execution of the instruction received.
    [047]Smart lock 300 is also configured to report temperature information. For example, the smart lock can periodically (or on demand) transmit a temperature value obtained from a temperature sensor that is part of the smart lock or that is contained within the cargo container. A minimum and maximum temperature range can be established and any deviation from the preset range is reported.
    [048]The smart lock 300 generally allows connections of different types of external cables and sensors to, for example, measurement of temperature in the load. Temperature sensors can be placed in direct contact with (or even inserted into) the contents of the load unit. In other contexts, temperature sensors can be deployed to measure the air temperature inside the load unit.
    [049] In some embodiments, the smart lock 300 is configured to transmit information via multiple communication mechanisms, including cellular (eg, 3G, 4G), ZigBee, Wi-Fi, and the like. The smart lock can use short-range communication (eg, ZigBee or Wi-Fi) to interact with other smart locks that are in its vicinity. Such local communication can be used to implement a point-to-point network of multiple smart locks that monitor each other and/or share a greater range (eg cellular) of communication services provided by one of the multiple smart locks.
    [050]The smart lock 300 can be configured to comply with global standards for container locks, so any customs authority can open and close the smart lock without needing a third party present.
    [051] Figures 3D-3E are views of a second example of a smart lock 310 that is configured to secure a cargo van. Figure 3D is a front perspective view of the smart lock 310. Figure 3E is an exploded rear perspective view of the smart lock 310. Generally, the lock 310 may include any one or more of the features described above with respect to the lock 300, or other locks. smarts described above.
    [052] The smart lock shown 310 in Figures 3D-3E includes an armored glass or equivalent surface 312 that provides for its security and closure while allowing full wireless communications to pass through it. The other sides of the smart lock are made of stainless steel so communications cannot go through it. Internally, cavities containing the electronic and mechanical parts (eg sensors, communication devices) are separated and each has its own drainage channels to prevent water accumulation.
    [053]The smart lock 310 secures a van by means of a scalable lock of a multi-stage type (or “ladder”), which allows the lock 310 to adapt to a substantial majority of vans on the market.
    [054]The 310 lock is configured to provide easy handling and installation by the end user. User can operate the lock with one hand, thus providing sufficient installation and removal in the context of urban delivery processes. The surface of the lock 310 may be covered in rubber to prevent damage to the van due to vibration while installed or impact.
    [055]Lock 310 includes sufficient battery power to transmit reports every 5 minutes for at least 8 days. Reports include at least GPS positions, but may include other data such as temperature readings, accelerometer readings, and the like.
    [056]Other types or configurations of smart locks can be provided. In particular, smart locks that include or exclude one or more of the above features can be employed to practice at least some of the techniques described. 4. Example of Processes
    [057]Figures 4.1 - 4.3 are exemplary flowcharts of the load monitoring processes performed by the exemplary modalities.
    [058]Figure 4.1 is an exemplary flowchart of exemplary logic for load monitoring. The logic illustrated in this and the following flowcharts can be realized by, for example, Load Monitoring System 100 described with respect to Figure 1, above. More particularly, Figure 4.1 illustrates a process 4100 that includes operations performed by or on subsequent blocks.
    [059]In block 4101, the process performs reception of condition information from a lock that protects load and which is configured to transmit condition information that includes an indication of a current location of the load. In some embodiments, the lock is configured to determine its location via GPS, and then transmits an indication of the process's location. Other condition information may be reported, including temperature, acceleration, slope, and the like. The lock secures cargo by securing doors and other access from a shipping container, van, or similar. In some embodiments of the smart lock, an accelerometer is included to provide measurement information related to acceleration, pitch, and the like.
    [060] In block 4102, the process performs reception of an indication of a route that is to be traveled by the load. In some embodiments, the route indication specifies road segments or portions that the cargo must travel. The route information may also indicate regions where stopping is or is not permitted, expected travel time through specific route segments, maximum travel speed during specified route segments, and the like. In some modalities, the route can be seen as a set of constraints (geographical, temporal, physical, temperature, humidity) that must be met by the cargo during its journey. If a restriction is not found, an alert or other notification will be indicated. Route information may be received from any of a number of sources, including those associated with a person or company responsible for transporting the cargo, truck, van, or the like, and through any method of communication including manual or electronic.
    [061]In block 4103, the process performs determine if the load has deviated from the route based on the current location of the load. The process can determine that the cargo has deviated from the route by comparing the current location of the cargo to the permitted (or planned or preferred) locations/segments identified by the route information. Such a comparison may indicate that the load is traveling in the wrong direction or has otherwise deviated from the permitted route.
    [062]In block 4104, the process performs transmission of a deviation notification when the load has deviated from the route. Various types of notification may be transmitted, including text messages, emails, automated or semi-automated phone calls (eg, to truck driver, police), or the like.
    [063]Figure 4.2 is an exemplary flowchart of exemplary logic illustrating an exemplary embodiment of the 4100 process of Figure 4.1. More particularly, Figure 4.2 illustrates a process 4200 that includes process 4100, and that further includes operations performed by or on subsequent blocks.
    [064]In block 4201, the process receives a photograph of the lock when it is installed to protect the load. The process can receive a photograph taken and sent by, for example, a smart phone.
    [065]In block 4202, the process performs in response, activation of the lock. In some embodiments, the process automatically responds to the photo received, while in other embodiments, the process waits for manual verification of the photo received. In some embodiments, the lock may include a machine-readable identifier (eg, bar code, QR code, digit sequence) that can be automatically recognized by the process to provide assurance that the photograph does indeed show a lock.
    [066]Figure 4.3 is an exemplary logic flowchart illustrating an exemplary embodiment of the 4100 process of Figure 4.1. More particularly, Figure 4.3 illustrates a process 4300 that includes process 4100, wherein receiving an indication of a route includes operations performed by or on one or more of the following blocks.
    [067]In block 4301, the process performs reception of an indication of a road segment that can be traversed by the load. A road segment can be indicated as one or more points, a region, a logical map segment (eg highway 20 between City A and City Y), or the like. Logical map segments can then be searched against GIS databases or other sources to obtain GPS (or other coordinates) that can be cross-referenced against location reports received from the lock to determine if the protected cargo is traveling the route. correct.
    [068]Figure 4.4 is an exemplary flowchart of exemplary logic illustrating an exemplary embodiment of the 4300 process of Figure 4.3. More particularly, Figure 4.4 illustrates a process 4400 that includes process 4300 in which determining whether the load deviates from the route includes operations performed by or on one or more of the following blocks.
    [069] At block 4401, the process makes a determination, based on the current location of the cargo, that the cargo container is no longer on the road segment. By comparing the current location to the locations associated with the road segment, the process can determine that the load is no longer on the road segment. Some modalities include an allowable threshold or deviation, in space and/or time, so that wrong report or subreport locations do not cause unnecessary alarms. For example, the process can tolerate a specified number (eg one or two) of reads that are off-route. As another example, the process can tolerate a position that is off-route by less than a specified threshold amount (eg, 50 meters). As another example, the process may receive and use error and uncertainty information provided by the lock's GPS sensor, so that a route deviation that is within a reported error radius will not be reported.
    [070]Figure 4.5 is an exemplary logic flowchart illustrating an exemplary embodiment of the 4300 process of Figure 4.3. More particularly, Figure 4.5 illustrates a process 4500 that includes process 4300, wherein determining whether the load diverted from the route includes operations performed by or on one or more of the following blocks.
    [071]In block 4501, the process makes a determination, based on the current location of the load, that the load is traveling in an impermissible direction along the road segment. Some modalities track the distance between the current load location and the end point of the road segment or some other point on the road. When this distance decreases, a U-turn may be indicated, resulting in a warning or other notification. The disallowed direction may be an incorrect or otherwise disallowed direction.
    [072]Figure 4.6 is an exemplary logic flowchart illustrating an exemplary embodiment of the 4300 process of Figure 4.3. More particularly, Figure 4.6 illustrates a process 4600 that includes process 4300, where determining whether the load has deviated from route includes operations performed by one or more of the following blocks.
    [073]In block 4601, the process makes a determination, based on the current location of the load, that a vehicle carrying the load has made a U-turn. Tracking distance between current location and some endpoint (eg, destination end, end of route segment, etc.) the process can identify U-turn when elapsed distance stops increasing and starts and decreases or when distance remains stopped decreasing and starts increasing. In some embodiments, U-turn can be detected by tracking a direction of travel (eg compass direction) based on multiple location reports (or a compass direction provided by the smart lock). When the direction of travel reverses (eg, rotates 180 degrees), a U-turn is typically indicated.
    [074]Figure 4.7 is an exemplary logic flowchart illustrating an exemplary embodiment of the 4300 process of Figure 4.3. More particularly, Figure 4.7 illustrates a process 4700 that includes process 4300, where determining whether the load has deviated from route includes operations performed by one or more of the following blocks.
    [075]In block 4701, the process performs determination, based on the current location of the load, at a current distance to the destination of the load. Some modalities control the distance between the current loading location and the final or intermediate destination. Distance can be measured as a straight line ("straight line") or as travel distance along the road network. Some modalities measure accumulated route distance and determine a percentage (complete and/or remaining). Using this information, the process can determine start route, destination proximity, route completion, estimated arrival times, and the like.
    [076]In block 4702, the process performs the determination that the current distance is greater than a previously determined distance to the destination. When cargo is moving away from its destination, this is often an indication that the cargo has deviated from its intended route.
    [077]Figure 4.8 represents an exemplary logic flowchart that illustrates an example of 4300 process modality Figure 4.3. More particularly, Figure 4.8 illustrates a process 4800 that includes process 4300, and that further includes operations performed by or with the next block(s).
    [078]In block 4801, the process receives an indication of the various road segments that the load is to traverse, the various road segments specified through an interactive mapping user interface. Some modalities provide an interactive mapping interface, so that a user can select or drag road segments that comprise an admissible route. In some embodiments, multiple routes may be specified, with the restriction that the cargo must travel at least one of the specified routes.
    [079]Figure 4.9 represents an exemplary logic flowchart that illustrates an example of the 4100 process modality of Figure 4.1. More particularly, Figure 4.9 illustrates a process 4900 that includes the process of 4100, wherein receiving an indication of a path includes operations performed by or with one or more of the following block(s).
    [080] In block 4901, the process receives an indication of a location or region where travel or stopping is or is not allowed. Some embodiments provide for the specification of "safe" or "hazardous" areas, so that notifications can be sent in response to cargo traveling or stopping in an area that is denoted as dangerous (or, alternatively, traveling or stopping in an area that is not denoted as safe).
    [081]Figure 4.10 is an exemplary flow diagram of exemplary logic illustrating an example of the 4100 process modality of Figure 4.1. More particularly, Figure 4.10 illustrates a process 41000 that includes process 4100, and that further includes operations performed by or with the next block(s).
    [082] In block 41001, the process performs the determination, based on the information of conditions, that a vehicle carrying the load travels before entering the route. The process can identify conditions such as a truck driving before entering the route, such as navigating a port facility or city streets before entering a highway system. Regions where walking is allowed can be specified through a UI or other mechanism. In some cases, a tour region may be associated with a time, so that a unit of cargo is allowed to roam within the region for the majority of the specified time before an alert or other notification is transmitted.
    [083]In block 41002, the process executes in response, transmitting a notification that the vehicle is driving. Additionally, once the process determines that the tour has completed (and the route has been entered) another notification can be broadcast to mark the start of the trip.
    [084]Figure 4.1 is a flow diagram of an example logic example illustrating an example of process 4100 modality of Figure 4.1. More particularly, Figure 4.11 illustrates a process of 41100, which includes the process of 4100, and which further includes operations performed by or with the next block(s).
    [085] In block 41 101, the process performs the determination, based on the condition information, a current average speed of a vehicle carrying the load. By tracking the location of the load, the process can determine the vehicle's speed.
    [086]In block 41 102, the process executes when the speed exceeds a specified threshold, transmitting a notification.
    [087]Figure 4.12 is an exemplary flow diagram of exemplary logic illustrating an example modality of the 4100 process of Figure 4.1. More particularly, Figure 4.12 illustrates a 41200 process that includes the 4100 process, and that further includes operations performed by or with the next block(s).
    [088]In block 41201, the process performs the determination that the information conditions were not received from the lock. In some embodiments, the process may determine that information conditions have not been received for more than a specified period of time (eg, five minutes). When this occurs, different actions can be taken depending on the circumstances. If the load is known to be in or near a region of poor communication, the process can determine a time when the load is expected to leave the region, and only sends an alert when no communication has been received for the specified time.
    [089]Figure 4.13 is an exemplary flow diagram of exemplary logic illustrating an example modality of the 4100 process of Figure 4.1. More particularly, Figure 4.13 illustrates a process of 41300 that includes process 4100, and that further includes operations performed by or with the next block(s).
    [090]In block 41301, the process executes by providing several levels of notification, including a first level for informational messages, a second level for warning messages, and a third level for severe alert messages. Some modalities provide for notification at scale, so that different types of conditions or events are reported to different parties or in different ways (eg, text message, email, phone call), depending on the severity.
    [091] For example, the process may initiate a text message for informational messages (e.g. cargo has entered the route), an email for warning messages (e.g. communication has expired by five minutes), or a phone call for serious alert (eg alarm) messages (eg intrusion detected, U-turn detected). 5. Example of Implementation Aspects
    [092] Figure 5 is a block diagram example of an example computer system for implementing a site-based Recommender System according to an exemplary embodiment. In particular, Figure 5 shows a computing system 10, which can be used to implement a CMS 100. Furthermore, at least some of the implementation techniques described below with respect to the CMS 100 can be used to implement other devices, systems, or modules described herein, including client logic 122 from client device 120.
    [093] Note that one or more general purpose or special purpose computing systems/devices may be used to implement CMS 100. In addition, computing system 10 may comprise one or more different computing systems/devices. computing and can span distributed locations. Furthermore, each displayed block may represent one or more blocks as appropriate for a specific modality or may be combined with other blocks. In addition, the CMS 100 can be implemented in software, hardware, firmware, or in some combination to achieve the capabilities described herein.
    [094] In the embodiment shown, the computing system 10 comprises a computer memory ("memory") 11, a display 12, one or more central processing units ("CPU") 13, input/output devices 14 (for (e.g. keyboard, mouse, CRT or LCD and the like), other computer readable media 15, and network connections 16. The CMS 100 is shown to be memory resident 11. In other embodiments, a portion of the content, some or all of the components of the CMS 100 may be stored on and/or transmitted via other computer readable media 15. The components of the CMS 100 preferably run on one or more CPUs 13 and perform the techniques described herein. Other program code 30 (e.g., an administration interface, a Web server, and the like) and potentially other data repositories, such as a data store 20, also reside in memory 11, and preferably run in one or more CPUs 13. Note that one or more of the components in Figure 5 cannot be present in any specific application. For example, some embodiments may not provide another computer readable media 15 or a display 12.
    [095]CMS 100 is shown running in memory 11 of computer system 10. Also included in memory is a user interface manager 41 and an application program interface ("API") 42. User 41 and API 42 are drawn in dashed lines to indicate that in other embodiments, the functions performed by one or more of these components may be performed externally to the CMS 100.
    [096]UI Manager 41 provides a player and controller that facilitate user interaction with CMS 100 and its various components. For example, the UL 41 manager can provide interactive access to the CMS 100, such that users can interact with the CMS 100, such as, specifying routes, tracking cargo, specifying contact information, notifications, and similar. Example user interface screens are shown with respect to Figures 2A and 2B, above. In some modalities, access to the functionality of the UI manager 41 can be provided through a server on the Network, possibly as an execution of other programs 30. In such modalities, a user operating a browser on the Network executes on one of the devices 55 that can interact with CMS 100 through the UL 41 manager.
    [097]API 42 provides programmatic access to one or more CMS 100 functions. For example, API 42 may provide a programming interface to one or more CMS 100 functions that can be requested by one of the other 30 programs or some another module. In this way, API 42 facilitates third-party software development, such as user interfaces, plug-ins, adapters (eg for integrating CMS 100 functions into Network applications), and the like.
    [098] In addition, API 42 may be in at least some modalities requested or accessed through remote entities, such as code running on one of the smart locks 101, information sources 60, and/or one of the security systems/devices. third parties 55, to access various functions of the CMS 100. For example, an information source 60 may relate map-information, bills of lading, cargo manifests, route information, or the like, to the CMS 100 through API 42 API 42 can also be configured to provide management widgets (e.g. code modules) that can be integrated into third party systems/devices 55 and that are configured to interact with CMS 100 to do at least some of the described features available in the context of other applications (eg mobile applications).
    [099]The CMS 100 interacts over the network 45 with smart locks 101, information sources 60, and third party systems/devices 55. The network 45 can be any combination of media (e.g. twisted pair, coaxial, fiber optic, radio frequency), hardware (e.g. routers, switches, repeaters, transceivers), and protocols (e.g. TCP/IP, UDP, Ethernet, Wi-Fi, WiMAX) that facilitate communication between humans and/or devices remotely situated. Third party systems/devices 55 may include any systems that provide the data, or use the data, to the CMS 100, including Web browsers, transport services, map services, notification services (e.g. for text messaging , emails, phone calls), and the like.
    [0100]In an example modality, at least some components/modules of CMS 100 are implemented using conventional programming techniques. For example, CMS 100 can be implemented as a "native" runtime executable of CPU 13, along with one or more static or dynamic libraries. In other embodiments, the CMS 100 may be implemented as instructions processed by a virtual machine that are executed as one of the other programs 30. In general, a range of programming languages known in the art may be used to implement these example embodiments, including representative implementations of various programming language paradigms, including but not limited to, (e.g., Java, C++, C#, Visual Basic.NET, Smalltalk, and the like), functional (e.g., ML, Lisp , Schema, and similar object-oriented), procedural (e.g., C, Pascal, Ada, Modula, and the like), scripting (e.g., Perl, Ruby, Python, JavaS-cript, VBScript, and the like), and declarative (e.g. SQL, Prolog, and the like).
    [0101]The modalities described above may also use synchronous or asynchronous or known or proprietary client-server computing techniques. In addition, the various components may be implemented using more monolithic programming techniques, for example as an executable execution on a single CPU computer system, or alternatively decomposed using a variety of structuring techniques known in the art, including but not limited to limited to, multiprogramming, multithreading, client-server, or peer-to-peer, running on one or more computer systems each with one or more CPUs. Some configurations may run concurrently and asynchronously and communicate using message passing techniques. Equivalent synchronous modalities are also supported. Furthermore, other functions can be implemented and/or executed by each module/components, and in different orders, and by different components/modules, and still achieve the described functions.
    [0102] In addition, programming interfaces to data stored as part of CMS 100, as in data stores 20, may be made available through conventional mechanisms, such as through C, C++, C#, and APIs Java; libraries to access files, databases or other data repositories; through scripting languages such as XML; or through Network servers, FTP servers, or other types of servers that provide access to stored data. The data store 20 may be implemented as one or more database systems, file systems, or any other technique for storing such information, or any combination of the foregoing, including implementations using distributed computing techniques.
    [0103] The different configurations and positions of programs and data are contemplated for use with the techniques described here. A variety of distributed computing techniques are suitable for implementing the components of the illustrated modalities in a distributed manner, including but not limited to TCP/IP sockets, RPC, RMI, HTTP, Network Services (XML-RPC, JAX-RPC). , SOAP, and the like). Other variations are possible. Also, other functionality may be provided by each module/component or existing functionality could be distributed among components/modules in different ways, but still achieving the functions described here.
    [0104] Figure 6 is a block diagram showing components of an example smart lock according to an exemplary embodiment. Figure 6 shows a smart lock 101 as described herein. The illustrated smart lock 101 includes a processor 600, an open/close sensor 601, a cut sensor 602, a motion sensor 603, a temperature sensor 604, a memory 605, auxiliary communication ports 606, I/O ports 607, a battery 608, a location module 609, and a wireless communication module 610.
    [0105] Processor 600 can be a standalone processor, a microcontroller, a system on a chip, or the like. The processor is in signal communication with components 601-610, such as through a data bus, dedicated data ports, or the like. The processor executes instructions that implement one or more of the techniques described here, such as battery monitoring, energy saving functions, communication functions, temperature monitoring, data storage, and so on. Instructions may be stored in form and loaded into memory 605 and/or into a memory (not shown) that is internal to processor 600. Processor 600 communicates with the illustrated components by polling, interrupts, message passing, or the like.
    [0106]Sensors 601 -604 monitor the status of the lock 101 and/or the load. Sensors provide control of information to processor 600, such as by raising interrupts, storing information directly in memory 604, or the like. Processor 600 may evaluate received information, such as determining whether data or measurement values are outside an acceptable range, and then transmit a notification to CMS 100.
    [0107]The 601 open/close sensor is responsible for monitoring the open/closed state of the lock, and notifying the processor of state changes. Cut sensor 602 monitors the mechanical integrity of the housing and/or the arms of the lock 101 in order to detect if the lock has been tampered with or the arms have been cut.
    [0108]The 603 motion sensor may include one or more than an accelerometer, inclinometer, vibration sensor or the like. Motion sensor 603 provides information about the movement of the lock to processor 600.
    [0109]The 604 temperature sensor monitors the internal and/or external temperature of the lock. In some embodiments, an external temperature sensor can be positioned inside the load unit. The 604 sensor can receive readings from an external temperature sensor through the 607 I/O ports.
    [0110]Memory 605 is responsible for storing data and/or instructions related to the operation of lock 101. Memory 605 may be or include one or more of volatile memory (e.g. RAM), non-volatile memory (e.g. example, ROM), flash memory, or the like. Memory 605 may serve as a buffer, plug, or through data values provided by sensor 601-604 or other components.
    [0111]Ports 606 and 607 allow lock 101 to communicate with external sensors, devices, or systems 631. For example, communication ports 606 may include USB ports, serial ports, Ethernet ports, or the like. As another example, I/O ports 607 can be wired to an external temperature or humidity sensor.
    [0112]Battery 608 supplies power to processor 608 and other components of the lock. Battery 608 is also in communication with signal processor 608 so that the battery level can be monitored and the battery function can be controlled. Battery 608 also includes an external port that can be connected to an external power supply 630, so that the lock 101 can be charged without opening it.
    [0113]Location module 609 obtains and supplies location information to lock 101. Location module 609 may include a GPS unit and the corresponding antenna configured to receive signals from one or more satellites 610.
    [0114]Wireless communication module 610 performs wireless communication functions for lock 101. Communication module 609 may include a radio, a modem, identity information (eg, SIM card), and the like, so as to communicate over a cellular network 112 with the load monitoring system 100. Other types of wireless communication may be supported, including Wi-Fi, satellite, or the like.
    [0115]At least some of the elements of the smart lock 101 can be implemented as software, using conventional programming techniques, such as those discussed with respect to the implementation of the CMS 100 in Figure 5, above. In addition, some embodiments of the smart lock 101 may include a greater or lesser number of components than those shown here. For example, some smart locks may not include a 602 cut sensor, relying only on a vibration sensor or other techniques to detect lock failures.
    [0116]Furthermore, in some embodiments, some or all of the components of the CMS 100 and/or the smart lock 101 may be implemented or provided in other ways, such as at least partially firmware and/or hardware, including but not limited to not limited to one or more application-specific integrated circuits ("ASICs"), conventional integrated circuits, controllers that execute appropriate instructions, including microcontrollers and/or embedded field programmable controllers, gate arrays ("FPGAs"), logic devices complex programmables ("CPLDs"), and the like. Some or all of the system components and/or data structures may also be stored as content (e.g., as executable or other machine-readable software instructions or structured data) on a computer-readable medium (e.g., as a disc memory; a computer network or cellular wireless network or other data transmission medium, or an article of portable media to be read by an appropriate unit or through a suitable connection system, such as a DVD device or flash memory) in order to enable or configure the reading medium computer and/or one or more associated computing systems or devices to execute or utilize or deliver the content to perform at least some of the techniques described. Some or all components and/or data structures may be stored on non-transient, tangible storage media. Some or all of the system components and data structures may also be stored as data signals (e.g. by being encoded as part of a carrier wave or as an integral part of a propagated analog or digital signal) over a variety of media. computer-readable transmission signals, which are then transmitted, including over wireless and wire-based/cable-based media, and can take a variety of forms (e.g., as part of a single analog or multiplexed signal, or as multiple discrete digital packages or frames). Such computer program products may also take other forms in other embodiments. Accordingly, embodiments of the present specification may be practiced with other computer system configurations.
    [0117]All U.S. patents above alternatives, US patent application publications, US patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in the Application Data Sheet, including but not limited to the Patent Application Provisional US No. 61/757,631 entitled "The systems, methods and devices for securing and monitoring loads PACKAGING", filed January 28, 2013, and US Provisional Patent No. 61 / 784,905, entitled "SYSTEMS, METHODS, AND DEVICES FOR SECURING AND MONITORING CARGO CONTAINERS," filed on March 14, 2013, is hereby incorporated by reference in its entirety.
    [0118]From the foregoing it will be appreciated that while specific embodiments have been described herein for purposes of illustration, various modifications may be made without departing from the spirit and scope of this description. For example, the methods, techniques and systems for controlling the load are applicable to other architectures or in other contexts. For example, instead of monitoring cargo, the techniques can be used to monitor people, vehicles in general, animals, or the like. Furthermore, the methods, techniques and systems discussed here are applicable to contexts, protocols, means of communication (optical, wireless, cable, etc.) and devices (such as cell phones, mobile communications devices, pagers, navigation devices such as the GPS differing receivers, etc).
    权利要求:
    Claims (15)
    [0001]
    1. Method for monitoring cargo, CHARACTERIZED by comprising: receiving condition information from sensors of an electromechanical lock that secures cargo by attaching to doors protecting the cargo and which is configured to transmit condition information that includes an indication of a current location load and at least one of an indication of whether the lock has been tilted and whether the doors protected by the lock have tilted, where received condition information indicates that the doors protected by the lock have tilted; receive an indication of a route that will be taken by the lock cargo; determine whether the cargo has deviated from the route based on the current location of the cargo; transmit a deviation notification when the cargo has deviated from the route; and transmit a notification that the cargo has been tampered with when the lock has been tilted or when the doors protected by the lock have tilted.
    [0002]
    2. Method according to claim 1, CHARACTERIZED by the fact that the received condition information indicates that the lock has been tilted.
    [0003]
    3. Method, according to claim 1, CHARACTERIZED by the fact that the lock protects a cargo container that includes the cargo and in which the cargo container has doors protected by the lock.
    [0004]
    4. Method, according to claim 1, CHARACTERIZED by the fact that the lock protects a van that includes the cargo and in which the van has doors protected by the lock.
    [0005]
    5. Method according to claim 1, CHARACTERIZED by the fact that the condition information also includes an indication of at least one acceleration detected by the lock by an accelerometer that is part of the electromechanical lock.
    [0006]
    6. Method according to claim 1, CHARACTERIZED in that the condition information also includes an indication of a battery level that is part of the electromechanical lock.
    [0007]
    7. Method, according to claim 1, CHARACTERIZED by the fact that receiving an indication of a route includes receiving an indication of multiple road segments that must be traveled by the cargo.
    [0008]
    8. Method according to claim 7, CHARACTERIZED by the fact that the multiple road segments were specified through an interactive mapping user interface.
    [0009]
    9. Method according to claim 1, CHARACTERIZED by the fact that receiving an indication of a route includes: receiving an indication of a location or region where stopping is permitted and receiving an indication of a location or region where travel or stop is explicitly prohibited.
    [0010]
    10. Method according to claim 9, CHARACTERIZED by the fact that the indicated location or region where travel or stopping is explicitly prohibited is a predetermined risk area and in which the indicated location or region where stopping is allowed is an area of determined rest.
    [0011]
    11. Method according to claim 9, CHARACTERIZED by the fact that receiving an indication of a location or region where stopping is allowed includes an indication of a time limit where stopping is allowed.
    [0012]
    12. Method, according to claim 1, CHARACTERIZED in that it further comprises: determining, based on the condition information, that a vehicle carrying the load is walking before entering the indicated route; and in response, transmit a notification that the vehicle is cruising before entering the indicated route.
    [0013]
    Method, according to claim 1, CHARACTERIZED in that it further comprises: determining, based on the condition information, an average speed of a vehicle carrying the load; and when the speed exceeds a specified limit, transmit a notification that the vehicle is exceeding the speed limit.
    [0014]
    14. Computer-readable non-transient media, CHARACTERIZED in that it includes content that is configured to, when executed, cause a computer system to execute a method for monitoring load, the method comprising: receiving condition information from sensors in a electromechanical lock that secures cargo by attaching to doors securing the cargo and that is configured to transmit condition information that includes an indication of a current location of the load and at least one of an indication of whether the lock has been tilted and whether the doors protected by the lock have tilted, where condition information received indicates that the doors protected by the lock have tilted; receive an indication of a route that the cargo will take; determine whether the cargo has deviated from the route based on the current location of the cargo; transmit a deviation notification when the load has deviated from the route; and transmit a notification that the cargo has been tampered with when the lock has been tilted or when the doors protected by the lock have tilted.
    [0015]
    15. System to monitor loads, CHARACTERIZED by comprising: a processor; a memory; and logic instructions stored in memory and configured to, when executed by the processor, perform a method comprising: receiving condition information from sensors of an electromechanical lock that secures a load by attaching to doors protecting the load and that is configured to transmit information from conditions that include an indication of a current location of the load and at least one of an indication of whether the lock has been tipped and whether the doors protected by the lock have tipped, where received condition information indicates that the doors protected by the lock have tipped; receive an indication of a route the cargo will take; determine whether the cargo has deviated from the route based on the current location of the cargo; transmit a notification of the deviation when the cargo has deviated from the route; and transmit a notification that the cargo has been tampered with when the lock has been tilted or when the doors protected by the lock have tilted.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112015017999B1|2022-02-01|Method and system for monitoring load and computer-readable non-transient media
    US10359782B1|2019-07-23|Facilitating safer vehicle travel utilizing telematics data
    US11068985B1|2021-07-20|Dynamic usage-based policies
    CN103646535B|2016-04-13|Driving behavior managing and control system
    BRPI0622216A2|2012-01-03|Method and system for controlling vehicles carrying hazardous materials
    US9472023B2|2016-10-18|Safety system for augmenting roadway objects on a heads-up display
    BRPI0712838A2|2012-12-18|method and provision for criminal risk reduction for land transport
    CN104408604A|2015-03-11|Intelligent logistics full-course sensing system
    US10733311B2|2020-08-04|Cognitive internet of things | gateways for data security and privacy protection in real-time context-based data applications
    CN107689161A|2018-02-13|The intelligent automobile Real-road Driving Cycle constructing system of people's car traffic interconnection
    Muragesh et al.2014|Automated internet of things for underground drainage and manhole monitoring system for metropolitan cities
    ES2866945T3|2021-10-20|Computer system and method of predicting the state of a traffic system
    KR101757750B1|2017-07-13|Unified notice method for congestion information of subway
    RU113396U1|2012-02-10|GLONASS / GPS SATELLITE TELEMATIC COMPLEX USING Inmarsat D + / GPRS COMMUNICATION CHANNELS
    BRPI1104677A2|2013-11-12|INTEGRATED ROAD TRANSPORT MANAGEMENT SYSTEM
    BR102014009746A2|2015-12-22|vehicle driver behavior analysis system
    CN111351492A|2020-06-30|Method and system for autonomous vehicle navigation
    JP5232634B2|2013-07-10|Car navigation system
    Montoya et al.2014|Inferring multimodal itineraries from rich smartphone data
    BR102013028660A2|2014-11-04|ELECTRONIC MODULE FOR GEO REFERENCE SYSTEM FOR SAFETY AND FAMILY GUIDANCE
    CZ19319U1|2009-02-16|Dynamic navigation communicator, particularly for motor vehicles in traffic telematic system
    BR102013021728A2|2015-11-10|electromechanical system for tipper operational safety
    BRPI1001208A2|2011-09-20|static speed recorder equipment and its traffic safety and surveillance system
    同族专利:
    公开号 | 公开日
    EP2948736A4|2016-10-26|
    US9260896B2|2016-02-16|
    US20160203718A1|2016-07-14|
    BR112015017999A2|2017-07-11|
    US9953530B2|2018-04-24|
    MX2015009743A|2016-04-28|
    US20140218218A1|2014-08-07|
    PE20160058A1|2016-01-28|
    EP2948736A1|2015-12-02|
    CA2899439A1|2014-07-31|
    HK1218155A1|2017-02-03|
    CA2899439C|2021-06-08|
    WO2014117180A1|2014-07-31|
    MX354083B|2018-02-09|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US6057779A|1997-08-14|2000-05-02|Micron Technology, Inc.|Method of controlling access to a movable container and to a compartment of a vehicle, and a secure cargo transportation system|
    US7783500B2|2000-07-19|2010-08-24|Ijet International, Inc.|Personnel risk management system and methods|
    US6847892B2|2001-10-29|2005-01-25|Digital Angel Corporation|System for localizing and sensing objects and providing alerts|
    US7848905B2|2000-12-26|2010-12-07|Troxler Electronic Laboratories, Inc.|Methods, systems, and computer program products for locating and tracking objects|
    US7714708B2|2001-12-28|2010-05-11|Brackmann Rogers F|Smart pallet-box cargo container|
    US7498938B2|2002-10-08|2009-03-03|Henry B. Ulrich|Security intelligence tracking anti-terrorist system|
    US20040113783A1|2002-12-11|2004-06-17|Millennium Information Systems, Llc|Container integrity management system|
    US6870476B2|2003-04-07|2005-03-22|Bulldog Technologies Inc.|Continuous feedback container security system|
    US8175587B2|2003-07-10|2012-05-08|Motorola Mobility, Inc.|Obtaining service when in a no-coverage area of a communication system|
    US7493103B2|2004-07-22|2009-02-17|International Business Machines Corporation|Method and apparatus to transfer data and detect weak signals|
    US7564348B2|2004-11-05|2009-07-21|Wirelesswerx International, Inc.|Method and system to monitor movable entities|
    WO2006116664A1|2005-04-26|2006-11-02|Rf Code, Inc.|Tamper monitoring system and method|
    US20080191867A1|2005-05-25|2008-08-14|Maor Markovich|Smart Case|
    US20090037089A1|2005-07-11|2009-02-05|Serhiy Tkachenko|Method for determining traffic information, and a device arranged to perform the method|
    US20070115101A1|2005-11-09|2007-05-24|Sapias, Inc.|Geospatially Aware Vehicle Security|
    US20090055091A1|2007-08-24|2009-02-26|Jeffery Scott Hines|Method, Apparatus, and Computer Program Product for Intelligently Selecting Between the Utilization of Geo-Fencing and Map Matching in a Telematics System|
    US9354077B2|2008-05-20|2016-05-31|Honeywell International Inc.|Navigation system|
    TWI361386B|2008-05-23|2012-04-01|Inst Information Industry|Method and system for analyzing signal data from electronic tags, and computer-readable storage medium thereof|
    US20100223090A1|2009-02-28|2010-09-02|John Lozito|Apparatus and method for end user freight transportation monitoring|
    US20110150272A1|2009-12-21|2011-06-23|Honeywell International Inc.|Systems and methods of tracking object paths|
    US20120144885A1|2010-12-12|2012-06-14|Ian Michael Mills|Fiber Optic Cable Lock System|
    US20120227450A1|2011-03-08|2012-09-13|Security Enhancement Systems, Llc|Lock|
    US9558468B2|2011-03-16|2017-01-31|Cubic Corporaton|Transportation route management|
    US8886216B1|2012-10-30|2014-11-11|Onasset Intelligence, Inc.|Method and apparatus for tracking a transported item while accommodating communication gaps|US9428202B2|2014-04-15|2016-08-30|Via Rail Canada Inc.|Train safety system|
    US10019878B2|2014-10-15|2018-07-10|Cross Road Centers, Llc|Method, apparatus and systems for tracking freight|
    US10134205B2|2016-08-18|2018-11-20|David Arena|Portable electronic wireless lock for efficiently managing and assuring the safety, quality and security of goods stored within a truck, tractor or trailer transported via a roadway|
    US10650621B1|2016-09-13|2020-05-12|Iocurrents, Inc.|Interfacing with a vehicular controller area network|
    US10204499B1|2016-09-23|2019-02-12|Symantec Corporation|Anomaly based geofencing leveraging location duration|
    US10803423B2|2016-09-29|2020-10-13|The Parking Genius, Inc.|System for managing parking of autonomous driving vehicles|
    US10299122B2|2016-11-23|2019-05-21|The Parking Genius, Inc.|User validation system utilizing symbolic or pictographic representations of validation codes|
    CN107644309B|2017-09-18|2021-04-02|深圳市易流科技股份有限公司|Cargo transportation monitoring method and system|
    US10446024B2|2017-09-21|2019-10-15|The Parking Genius, Inc.|Parking sensors capable of determining direction and speed of vehicle entering or leaving a parking lot|
    US10325497B2|2017-09-21|2019-06-18|The Parking Genius, Inc.|Parking sensors capable of determining direction and speed of vehicle entering or leaving a parking lot using magnetic signature recognition|
    DE102018201076A1|2018-01-24|2019-07-25|Robert Bosch Gmbh|System and method for checking the admissibility of at least one tractor-trailer combination|
    US11263582B2|2018-07-10|2022-03-01|Accenture Global Solutions Limited|Distributed ledger system for material monitoring|
    CN111882793A|2020-07-24|2020-11-03|雷沃工程机械集团有限公司|Anti-theft system and method for excavator|
    法律状态:
    2018-11-13| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2018-11-21| B08F| Application dismissed because of non-payment of annual fees [chapter 8.6 patent gazette]|Free format text: REFERENTE A 5A ANUIDADE. |
    2019-03-19| B08G| Application fees: restoration [chapter 8.7 patent gazette]|
    2019-11-26| B08F| Application dismissed because of non-payment of annual fees [chapter 8.6 patent gazette]|Free format text: REFERENTE A 6A ANUIDADE. |
    2020-03-10| B08G| Application fees: restoration [chapter 8.7 patent gazette]|
    2020-04-07| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2021-12-14| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2022-02-01| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 28/01/2014, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US201361757631P| true| 2013-01-28|2013-01-28|
    US61/757,631|2013-01-28|
    US201361784905P| true| 2013-03-14|2013-03-14|
    US61/784,905|2013-03-14|
    PCT/US2014/013443|WO2014117180A1|2013-01-28|2014-01-28|Systems, methods, and devices for securing cargo|
    [返回顶部]