Method and apparatus for journey detection in asset tracker
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- 捷奥泰普公司
- Filing Date
- 2024-11-06
- Publication Date
- 2026-06-09
Smart Images
Figure CN122180884A_ABST
Abstract
Description
[0001] Related applications
[0002] This application claims priority to U.S. Provisional Application No. 63 / 603,827, filed November 29, 2023, the contents of which are incorporated herein by reference in their entirety. Technical Field
[0003] This disclosure relates generally to asset tracking, and more specifically to methods and apparatus for trip detection in asset trackers. Background Technology
[0004] An asset tracker is an electronic device deployed on an asset to track its location and status. Asset trackers are typically part of an asset tracking system. An asset tracking system enables the tracking of the location and status of one or more assets. Assets can be vehicles, pieces of equipment, containers, trailers, tanks, or any other type of asset whose location and status should be tracked. Asset trackers are coupled to the asset and deployed in the field. Battery-powered asset trackers have limited power for operation. Summary of the Invention
[0005] In one aspect of this disclosure, a method for trip detection by an asset tracker is provided, the method comprising: operating the asset tracker in a transport state; switching the asset tracker to a motion detection state in response to an activation success event; and switching the asset tracker to a travel state in response to detecting motion.
[0006] In this method, operating the asset tracker in transit may include: entering a sleep mode, configuring the 3-axis accelerometer to detect activation triggering activity, and in response to detecting activation triggering activity: obtaining the first location of the asset tracker and generating an activation success event.
[0007] In this method, detecting motion may include measuring acceleration by a 3-axis accelerometer for a duration greater than a motion acceleration threshold and exceeding a motion detection duration threshold.
[0008] The method may also include, while in motion: obtaining a second location of the asset tracker, and when the distance between the second location and the first location is greater than a travel distance threshold: configuring a 3-axis accelerometer for impact detection, and reporting a travel start event when the trip has not yet started.
[0009] The method may further include, in the traveling state: obtaining a second location of the asset tracker, and when the distance between the second location and the first location is greater than a traveling distance threshold: when the trip has started: switching to the trip end state, reporting the trip end event, and switching to the traveling motion detection state after reporting the trip end.
[0010] The method may further include, in the traveling state: obtaining a second location of the asset tracker, and when the distance between the second location and the first location is less than a traveling distance threshold: when the journey has not yet started: switching back to the traveling motion detection state.
[0011] The method may also include, in the traveling state: in response to an impact detected by a 3-axis accelerometer: switching to an impact state.
[0012] The method may also include, while in motion: obtaining a second location of the asset tracker, and when the distance between the second location and the first location is greater than a travel distance threshold: configuring a 3-axis accelerometer for travel end detection, and reporting a travel start event when the trip has not yet started.
[0013] In this method, configuring a 3-axis accelerometer for end-of-stroke detection may include: configuring the 3-axis accelerometer to generate an event when the detected acceleration drop threshold reaches the end-of-stroke detection duration.
[0014] The method may further include, in the traveling state: obtaining a second location of the asset tracker, and when the distance between the second location and the first location is greater than a traveling distance threshold: when the trip has not yet started: configuring a 3-axis accelerometer for impact detection, configuring a 3-axis accelerometer for trip end detection, and reporting a trip start event.
[0015] In another aspect of this disclosure, an asset tracker is provided, comprising: a housing, a controller disposed within the housing, a positioning module disposed within the housing and coupled to the controller, a 3-axis accelerometer disposed within the housing and coupled to the controller, and a memory coupled to the controller. The memory stores machine-executable programming instructions that, when executed by the controller, configure the asset tracker to: operate the asset tracker in a transport state, switch the asset tracker to a motion detection state in response to an activation success event, and switch the asset tracker to a traveling state in response to the detection of traveling motion.
[0016] In an asset tracker, machine-executable programming instructions that configure the asset tracker to operate in a transport state may include machine-executable programming instructions that configure the asset tracker to: enter a sleep mode, configure the inertial measurement unit to detect activation triggering activity, and in response to detecting activation triggering activity: obtain the first position of the asset tracker, and generate an activation success event.
[0017] In an asset tracker, machine-executable programming instructions that configure the asset tracker to detect traveling motion may include machine-executable programming instructions that configure the asset tracker to measure acceleration greater than a traveling motion acceleration threshold for a duration exceeding a traveling motion detection duration threshold via a 3-axis accelerometer.
[0018] In the asset tracker, machine-executable programming instructions can also configure the asset tracker to: obtain a second position of the asset tracker while in motion, and when the distance between the second position and the first position is greater than a travel distance threshold; configure a 3-axis accelerometer for impact detection when the travel has not yet started; and report a travel start event.
[0019] In the asset tracker, machine-executable programming instructions can also configure the asset tracker to: obtain a second location of the asset tracker in the traveling state; and when the distance between the second location and the first location is greater than a traveling distance threshold: when the travel has started: switch to the travel end state, report the travel end, and switch to the traveling motion detection state after reporting the travel end event.
[0020] In the asset tracker, machine-executable programming instructions can also configure the asset tracker to: obtain a second location of the asset tracker in the moving state; and when the distance between the second location and the first location is less than the moving distance threshold: switch back to the moving motion detection state before the journey has started.
[0021] In the asset tracker, machine-executable programmable instructions can also configure the asset tracker, in motion, to switch to impact mode in response to an impact detected by a 3-axis accelerometer.
[0022] In the asset tracker, machine-executable programming instructions can also configure the asset tracker to: obtain a second location of the asset tracker while in motion, and when the distance between the second location and the first location is greater than a travel distance threshold; configure a 3-axis accelerometer for travel end detection and report a travel start event when the trip has not yet started.
[0023] In an asset tracker, machine-executable programming instructions for configuring a 3-axis accelerometer for end-of-stroke detection may include machine-executable programming instructions that configure the 3-axis accelerometer to generate an event when the detected acceleration drop threshold reaches the end-of-stroke detection duration.
[0024] In the asset tracker, machine-executable programming instructions can also configure the asset tracker to, in the traveling state: when the trip has not yet started: configure the 3-axis accelerometer for trip end detection, configure the 3-axis accelerometer for trip end detection, and report the trip start event. Attached Figure Description
[0025] Exemplary, non-limiting embodiments of this disclosure will be described with reference to the accompanying drawings, in which:
[0026] Figure 1 This is a schematic diagram of an asset tracking system that includes an asset tracker coupled to an engineless asset;
[0027] Figure 2 This is a perspective view of an exemplary battery-powered asset tracker;
[0028] Figure 3 This is a block diagram of an exemplary battery-powered asset tracker;
[0029] Figure 4 This is a state diagram illustrating the operational state of an exemplary battery-powered asset tracker according to an implementation of this disclosure;
[0030] Figure 5 This is a flowchart depicting the steps performed by an exemplary asset tracker in transit according to an embodiment of this disclosure;
[0031] Figure 6 This is a flowchart depicting the steps performed by an exemplary asset tracker in a motion detection state according to an embodiment of this disclosure;
[0032] Figure 7A This is a flowchart depicting the steps performed by an exemplary asset tracker in motion according to an embodiment of this disclosure;
[0033] Figure 7B This is a flowchart depicting steps performed by an exemplary asset tracker in motion, according to another embodiment of the present disclosure;
[0034] Figure 7C This is a flowchart depicting the steps performed by an exemplary asset tracker in motion, according to yet another embodiment of this disclosure;
[0035] Figure 8 This is a flowchart depicting the steps performed by an exemplary asset tracker in a trip-end state according to an embodiment of this disclosure; and
[0036] Figure 9 This is a flowchart depicting the steps performed by an exemplary asset tracker under impact conditions according to an embodiment of this disclosure. Detailed Implementation
[0037] This disclosure generally relates to asset tracking, and more specifically to apparatus and methods for activating an asset tracker. More specifically, this disclosure provides apparatus and methods for activating an asset tracker and enabling a motion detection mode on the asset tracker in response to an activation trigger activity.
[0038] An asset tracker is an electronic device deployed on an asset to track its location and status. Asset trackers are typically part of an asset tracking system. An asset tracking system allows administrators to track the location and status of one or more assets. Assets can be vehicles, pieces of equipment, containers, trailers, tanks, or any other type of asset whose location and status need to be tracked.
[0039] Asset trackers are typically battery powered. Some asset trackers are powered by rechargeable batteries coupled to an energy harvester (such as a solar panel). Other asset trackers are powered by non-rechargeable batteries. A non-rechargeable battery is a battery that cannot be recharged after it is depleted. Some common types of non-rechargeable batteries used in portable electronic devices such as asset trackers include zinc-carbon batteries and alkaline batteries. In this disclosure, "battery-powered asset tracker" refers to an asset tracker powered by a non-rechargeable and non-replaceable battery. Once a battery-powered asset tracker is deployed in the field, it relies on the non-rechargeable battery to operate until the non-rechargeable battery is depleted. Some asset trackers must pass protection rating certification, so it is preferable that such asset trackers have a sealed housing and that the battery is non-replaceable. Furthermore, non-replaceable batteries eliminate the need to construct battery compartments, battery contacts, etc., thereby reducing costs.
[0040] Asset tracking system
[0041] Asset tracking systems facilitate the tracking and monitoring of asset location, movement, and condition. An asset tracker is an electronic device coupled to an asset for this purpose. These may include a positioning module, an inertial measurement unit (IMU), and / or sensors. The positioning module determines the asset's location, the IMU detects motion and orientation, and the sensors determine the conditions experienced by the asset tracker. The asset tracker periodically transmits this information to a remote server, allowing for real-time or near-real-time tracking. To conserve power, the asset tracker captures location data in real-time but periodically reports location and other conditions. It can also identify and record trips, including start and end times.
[0042] Figure 1 A high-level block diagram of asset tracking system 101 is shown. Asset tracking system 101 includes asset trackers 200, network 50, asset tracking server 130, management terminal 140, and satellite 170 deployed in asset 100. Although a single instance of each element is shown for simplicity, multiple instances of each shown element are common in asset tracking systems.
[0043] Asset 100 shown is in the form of a container placed on trailer 105, which is coupled to tractor 110. Asset 100 can be a container, vehicle, industrial equipment, construction equipment, tanks containing chemicals, or any other asset whose location, movement, and / or status needs to be tracked. Asset 100 can be transported by the trailer 105 shown, or by ship, train, aircraft, or any other means of transport. Asset 100 can also be an industrial or construction piece of equipment, such as a generator, concrete mixer, compressor, etc. Such assets may have wheels and may be towed from one location to another.
[0044] Asset tracker 200 is an electronic device coupled to an asset (e.g., asset 100). Asset tracker 200 is configured to track the location, movement, and / or condition of asset 100.
[0045] In some implementations, asset tracker 200 is battery powered. In other implementations, asset tracker 200 is powered by a rechargeable battery and includes an energy harvester, such as a solar panel, for recharging the rechargeable battery. In the latter case, asset tracker 200 is an example of an electronic device powered by a rechargeable battery and an energy harvester. Asset tracker 200 utilizes a Global Navigation Satellite System (GNSS) to obtain its location. In the depicted embodiment, asset tracker 200 communicates with satellite 170 to obtain its location. Asset tracker 200 also includes an inertial measurement unit (IMU) and / or sensors, such as temperature sensors, light sensors, and pressure sensors. The combination of location data, movement, and sensor data is referred to as asset tracking data 112. Asset tracker 200 is connected to network 50, which allows asset tracker 200 to send asset tracking data 112 to a remote server, such as asset tracking server 130.
[0046] Network 50 can be a single network or a combination of networks such as data cellular networks, wide area networks, the Internet, and other network technologies. Network 50 provides connectivity between asset tracker 200 and asset tracking server 130, as well as connectivity between management terminal 140 and asset tracking server 130.
[0047] Within the asset tracking system 101, network 50 is capable of utilizing a variety of cellular technologies, including 2G, 3G, 4G, 5G, and NB-IoT.
[0048] Network 50 can use non-cellular WAN technologies, such as WiMAX. TM LoRaWAN TM And weightless technology.
[0049] In some implementations of the asset tracking system 101, when the asset tracker 200 is coupled to an asset providing a wired network connection, the network 50 uses wired network technology. Examples of wired network technologies include Ethernet, Fast Ethernet, and LocalTalk. TM Token Ring, Fiber Distributed Data Interface (FDDI), and Asynchronous Transfer Mode (ATM).
[0050] In some implementations, network 50 is a combination of the technologies specified above.
[0051] Asset tracking server 130 is an electronic device capable of receiving, storing, and analyzing asset tracking data 112. It can be implemented as a single computer system or a computer cluster using various operating systems or cloud computing platforms. Asset tracking server 130 is connected to network 50 and can receive data from asset tracker 200. It can perform data analysis and analytics to obtain useful asset information and store it in asset tracking database 132. Asset tracking server 130 can transmit asset tracking data 112 to management terminal 140.
[0052] Satellite 170 may be part of a Global Navigation Satellite System (GNSS), which provides positioning, navigation, and timing services globally. The four main operational GNSS systems are GPS, GLONASS, Galileo, and BeiDou. Positioning information can be processed by the positioning module on asset tracker 200 to provide positioning data indicating the location of the asset tracker and its coupled assets. In other implementations, the asset tracker may use other means to determine its location.
[0053] Management terminal 140 is an electronic device capable of connecting to asset tracking server 130 via network 50. The management terminal can be configured to: retrieve data and analysis related to one or more assets 100; receive alerts from asset tracking server 130 regarding one or more conditions on asset trackers 200; or issue commands to one or more asset trackers 200 via asset tracking server 130. Management terminal 140 is shown as a laptop computer; however, this is not necessarily the case. The management terminal can be a desktop computer, industrial human-machine interface (HMI), touchscreen panel, table, smartphone, augmented reality (AR) headset, or network operations center (NOC). Management terminal 140 can run a web browser or custom application that allows retrieval of data and analysis about one or more assets 100 from asset tracking server 130 via its network interface. Management terminal 140 can also be used to issue commands to one or more asset trackers 200 via asset tracking server 130. Administrator 11 can use management terminal 140 to communicate with asset tracking server 130. In addition to retrieving and analyzing data, the management terminal 140 allows the administrator 11 to set up alarms and geofences for purposes such as keeping track of the asset 100 and receiving delivery notifications.
[0054] In operation, asset tracker 200 is coupled to asset 100 to capture the asset's location, motion, and / or one or more conditions related to the asset. Location data is determined by a positioning module communicating with satellite 170. Motion data is determined by an inertial measurement unit (IMU), which is part of or coupled to asset tracker 200. One or more conditions are determined based on sensor data collected from sensors within asset tracker 200 or external sensors coupled to asset tracker 200. The combination of location data, motion data, and / or sensor data comprises asset tracking data 112. Asset tracker 200 transmits asset tracking data 112 to asset tracking server 130 via network 50. Asset tracking server 130 can process, aggregate, and analyze asset tracking data 112 to generate asset information about asset 100. Asset tracking server 130 can store asset tracking data 112 and / or the generated asset information in asset tracking database 132. Management terminal 140 can connect to asset tracking server 130 via network 50 to access asset tracking data 112 and / or generated asset information. Alternatively, asset tracking server 130 can push asset tracking data 112 and / or generated asset information to management terminal 140. Administrator 11 can use management terminal 140 to set alarms for certain activities related to asset 100. When alarm criteria are met, asset tracking server 130 sends a message to management terminal 140 to notify administrator 11. For example, when an asset is moved outside its service area, asset tracking server 130 can send an alarm message to management terminal 140. Administrator 11 can also use management terminal 140 to configure asset tracker 200 by issuing commands to asset tracker 200 via asset tracking server 130. For example, asset tracking server 130 can issue commands to asset tracker 200 in response to certain conditions to capture certain types of sensor data.
[0055] Asset tracker
[0056] Reference Figure 2 and Figure 3 Further details related to the asset tracker 200 are shown. Figure 2 This is a perspective view of a battery-powered asset tracker in the form of an asset tracker 200 according to an embodiment of this disclosure. The asset tracker 200 has a robust housing in the form of an asset tracker housing 202 for housing the internal components of the asset tracker 200. The asset tracker housing 202 includes fastening holes 205A and 205B for fastening the battery-powered asset tracker.
[0057] Figure 3This is a block diagram of an exemplary battery-powered asset tracker in the form of an asset tracker 200 according to an embodiment of this disclosure. The components of the exemplary battery-powered asset tracker are arranged... Figure 2 The asset tracker housing 202 is depicted.
[0058] Asset tracker 200 includes a controller 230. Multiple peripheral devices are coupled to controller 230 via different types of interfaces. These peripheral devices include a memory 240, a network interface 220, an IMU 290, a proximity sensor 250, a positioning module 280, an optical sensor 260, a touch sensor 270, and other sensors 275. Asset tracker 200 also includes a non-rechargeable battery in the form of a battery 210. Some of the peripheral devices shown are optional. For example, asset tracker 200 may not include proximity sensor 250, optical sensor 260, touch sensor 270, and / or other sensors 275.
[0059] The controller 230 can consist of various hardware components capable of executing machine-executable instructions. It can follow different architectures, such as von Neumann, Harvard, or modified Harvard. The controller 230 can be a Complex Instruction Set Computer (CISC) processor or a Reduced Instruction Set Computer (RISC) processor. It can have one or more processor cores and internal memory for storing and executing machine-executable programmable instructions.
[0060] Memory 240 is an electronic storage component that stores data and machine-executable programmable instructions. It can be a read-only memory (ROM), such as a programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. It can also be random access memory (RAM), such as static RAM (SRAM) and dynamic RAM (DRAM), or ferroelectric RAM (FRAM), magnetic random access memory (MRAM), or phase-change memory (PCM). Memory 240 is coupled to controller 230 via a bus, allowing the controller to execute instructions stored in the memory and access the data stored therein.
[0061] The positioning module 280 determines the location of the asset tracker 200. The positioning data can be in latitude and longitude form, using Universal Transverse Mercator (UTM) coordinates, or any other similar form.
[0062] In some implementations, the positioning module 280 is a GNSS transceiver supporting one or more of the aforementioned GNSS technologies. The positioning module 280 may be integrated into the controller 230 or coupled to the controller 230 via a serial interface, such as a Serial Peripheral Interface (SPI), Internal Integrated Circuit (I2C), Universal Asynchronous Receiver / Transmitter (UART), Universal Serial Bus (USB), and Secure Digital Input / Output (SDIO).
[0063] In other implementations, the positioning module 280 uses cellular tower triangulation to determine the location of the asset tracker 200 from the cellular network. In this case, the positioning module 280 is a firmware module that calculates the location based on information received from a network interface 220, which in this case is a cellular modem providing signal measurement results from multiple nearby cellular towers. The positioning module 280 uses the signal measurement results to estimate the location of the asset tracker 200. The location data determined by the positioning module 280 is then sent to the controller 230.
[0064] The proximity sensor 250 is an electronic component that detects the presence of a nearby object without any physical contact. In this disclosure, the proximity sensor 250 is used to determine whether the asset tracker 200 is in a shipping container or has been removed from it. In this disclosure, the proximity sensor 250 is a device for measuring magnetic fields, and the nearby object is a magnet deployed in the shipping container of the asset tracker 200. Examples of the proximity sensor 250 include Hall effect sensors, microelectromechanical systems (MEMS) magnetic field sensors, quantum sensors, and magnetic field sensors. The proximity sensor 250 can be integrated into the controller 230 or coupled to the controller 230 via a serial interface such as SPI, I2C, UART, USB, or SDIO.
[0065] Optical sensor 260 uses components such as photodiodes, phototransistors, and photoresistors to detect and measure light or other optical properties. Coupled to controller 230, optical sensor 260 indicates the presence or absence of light incident upon it.
[0066] Touch sensor 270 is a touch-sensitive input device. In some implementations, touch sensor 270 is a capacitive touch sensor. For example, a capacitive touch sensor operates by changing capacitance in response to being touched by a person's finger.
[0067] Other sensors 275 may be one or more of the following: temperature sensors, pressure sensors, optical sensors, humidity sensors, gas sensors, sound sensors, pH sensors, soil moisture sensors, or any other suitable sensors indicating the condition of the asset 100 coupled to the asset tracker 200. The sensors provide sensor data to the controller 230. Some controllers 230 may have some integrated sensors. In other cases, other sensors 275 are coupled to the controller using a serial interface such as SPI, I2C, UART, USB, or SDIO. Some asset trackers may not have any built-in sensors and may only provide location information and / or IMU information. Some asset trackers may have the ability to pair with external sensors via wired or wireless interfaces.
[0068] The IMU 290 is an inertial measurement unit. The IMU 290 is a device used to measure and provide information about the motion, orientation, and acceleration of an asset tracker. The IMU 290 may include several components that work together. For example, the IMU 290 may include one or more of the following: an accelerometer, a gyroscope, a magnetometer, and a barometer. An accelerometer measures linear acceleration on three axes (typically X, Y, and Z). In some implementations, the IMU 290 includes a 3-axis accelerometer. Such implementations are characterized by low power consumption because accelerometers consume less power than, for example, gyroscopes. A gyroscope measures the angular velocity or rate of rotation around each of the three axes. A magnetometer measures the strength and direction of a magnetic field and thus determines the heading or orientation relative to the Earth's magnetic field. A barometer measures atmospheric pressure and can be used to estimate changes in altitude. Some IMUs contain a microcontroller or processor that runs sensor fusion algorithms to combine and process data from the various sensors mentioned above. Some IMUs contain an embedded machine learning core (MLC). MLC is an in-sensor engine with a classification-based AI algorithm (decision tree), which can run different tasks while the sensor is detecting motion data. Examples of IMUs with MLC include those from STMicroelectronics. TM The iNEMO inertial module. Other IMUs include communication interfaces for interfacing with external microcontrollers or processors. Some asset trackers may not include an IMU unit and can report motion determined based on changes in positioning reported by the positioning module 280.
[0069] IMU 290 may have additional features, such as detecting taps, detecting orientation changes, and detecting free fall. For example, IMU 290 may be configured to detect a single tap or two taps and generate an interrupt signal to controller 230. Additionally, IMU 290 may be configured to detect orientation changes around any of the X, Y, and Z axes. When an orientation change of a specific magnitude (e.g., 60 degrees or 90 degrees) is detected, IMU 290 may generate an interrupt signal to controller 230. IMU 290 may be integrated into controller 230 or may be a separate component communicating with controller 230 via a serial communication interface (e.g., SPI, I2C, UART, USB, or SDIO). Controller 230 may configure IMU 290 by sending configuration commands to IMU 290. Additionally, controller 230 may query the status of IMU 290 generally or in response to receiving an interrupt signal from IMU 290. IMU 290 may have a low-power mode to extend the battery life of the asset tracker. For example, the low-power mode is characterized by a low output data rate (1 Hz to 200 Hz) for the accelerometer, and the current consumed by the IMU 290 is in the range of a fraction of a microamp to a few microamps.
[0070] For the purposes of this disclosure, IMU 290 includes at least one 3-axis accelerometer. The reference to "3-axis accelerometer" refers to the 3-axis accelerometer as a component of IMU 290.
[0071] Network interface 220 can use various cellular technologies, including 2G (GSM), 3G (UMTS), 4G (LTE), 5G, and NB-IoT. Each technology supports different data transmission protocols, such as GPRS, EDGE, HSPA, and LTE. NB-IoT is the low-power wide-area network technology component of the 3GPP standard.
[0072] Network interface 220 can use non-cellular WAN technologies, such as WiMAX. TM LoRaWAN TM And weightless technology.
[0073] In some implementations, when the asset tracker 200 is coupled to an asset that provides a wired network connection, the network interface 220 uses wired networking technology. Examples of wired networking technologies include Ethernet, Fast Ethernet, and LocalTalk. TM Token Ring, Fiber Distributed Data Interface (FDDI), and Asynchronous Transfer Mode (ATM).
[0074] Network interface 220 is used to send asset tracking data 112 to asset tracking server 130 via network 50. Network interface 220 can also be used to receive instructions from asset tracking server 130 for configuring asset tracker 200 in a specific mode and / or requesting specific types of asset tracking data 112 from asset 100. The network interface can be integrated into controller 230 or connected to controller 230 via a parallel or serial interface (e.g., SPI, I2C, UART, USB, or SDIO).
[0075] Battery 210 powers asset tracker 200. Battery 210 is a non-rechargeable battery, which can be a zinc-carbon battery or an alkaline battery. For asset trackers that are to be deployed in the field for many years, battery 210 is typically non-replaceable. This is especially true for asset trackers with a protection rating and typically a sealed housing.
[0076] In operation, controller 230 may receive one or more of the following: sensor data from other sensors 275, positioning data from positioning module 280, and motion or orientation data from IMU 290. In general, the collected data includes asset tracking data 112. Controller 230 transmits asset tracking data 112 to asset tracking server 130 via network interface 220 through network 50.
[0077] In some implementations, the asset tracker 200 receives commands from the asset tracking server 130 via network interface 220 through network 50. The received commands instruct the asset tracker 200 to be configured in a specific manner. For example, the received commands may configure the asset tracker 200 to collect asset tracking data 112 in a certain way, at a certain rate, or at a certain frequency.
[0078] Operating mode
[0079] Asset trackers typically have at least two operating modes. In motion detection mode, the asset tracker uses an IMU to determine whether the asset coupled to the asset tracker (and therefore the asset tracker itself) has been in continuous motion for a specific duration. In response to determining that the asset tracker has experienced continuous motion for the specific duration, the asset tracker switches to a walking mode. During walking mode, the asset tracker enables the positioning module 280 (i.e., powers on the positioning module 280) to track the location of the asset. To conserve battery power, the asset tracker does not keep the positioning module continuously powered during walking mode. Instead, the asset tracker periodically powers on the positioning module to obtain discrete locations of the asset. During walking mode, the asset tracker also periodically powers on the network interface and sends asset tracking data to a remote server, such as an asset tracking server. In some implementations, for longer battery life, the asset tracker reports asset tracking data over a longer period (e.g., 24 hours). Because the network interface 220 (e.g., a cellular modem) consumes more power than the positioning module (e.g., a GNSS transceiver), the asset tracker typically powers on the network interface and reports its location less frequently. When movement stops, the asset tracker switches back to motion detection mode.
[0080] One problem with operating an asset tracker in motion detection mode is that the tracker interprets any sustained motion for a certain duration as indicating that it is moving and its location needs to be tracked. Therefore, whenever sustained motion is detected for a certain duration or longer, the positioning module and / or network interface are powered on. However, there are situations where sustained motion may occur before the asset tracker is deployed in the field. For example, the asset tracker 200 may be en route to a customer. If the asset tracker is in motion detection mode, it unnecessarily switches to moving mode. Powering the positioning module 280 and / or network interface 220 consumes battery power. Since the battery is non-rechargeable and non-replaceable, the lifespan of the asset tracker 200 is shortened due to incorrect determination of movement and unnecessary switching to moving mode.
[0081] One solution to the above problem is to have an additional mode called transport mode, which is an ultra-low power mode. When in transport mode, most of the peripheral devices of the asset tracker 200 are powered off. The asset tracker only switches to motion detection mode in response to activation trigger activity. This... Figure 4 As shown in the image.
[0082] Figure 4This is a state diagram 400 depicting different operating states of the asset tracker 200 according to an embodiment of this disclosure. When the asset tracker 200 is out of production and ready to be shipped to a customer, the asset tracker 200 is in a transport state 410. In the transport state 410, the asset tracker 200 begins to enter a sleep mode. Figure 5 The various actions that occur in the asset tracker 200 when it is in transport state 410 are described. First, at step 510, the asset tracker 200 enters a sleep mode. In sleep mode, the asset tracker powers off most of its peripheral devices, except for one or more peripheral devices required to detect activation trigger activity. Examples of peripheral devices required to detect activation trigger activity include IMU 290, proximity sensor 250, optical sensor 260, and touch sensor 270.
[0083] At step 520, the asset tracker 200 checks whether it can detect activation triggering activities. Activation triggering activities depend on the implementation of the asset tracker 200.
[0084] In some implementations, the activation triggering activity includes tapping the asset tracker 200, such as tapping the top housing surface 203 of the asset tracker housing 202. In such an implementation, most peripheral devices are powered down, except for the IMU 290, which is configured to detect taps of a specific amplitude in a direction substantially perpendicular to the surface of the asset tracker housing 202 (e.g., the top housing surface 203). Similarly, in some implementations, the activation triggering activity includes at least one mid-air gesture performed by the asset tracker 200. In both of the above implementations, in step 510 (sleep mode), most peripheral devices are powered down, except for the IMU 290. In this implementation, the asset tracker 200 configures the IMU 290 to detect at least one mid-air gesture.
[0085] In some implementations, the activation trigger activity includes sensing a touch on the surface of the asset tracker housing 202. For example, the activation trigger activity may include sensing a touch on the top housing surface 203 for a sustained duration. In this implementation, in step 510 (sleep mode), most peripheral devices are powered off except for the touch sensor 270.
[0086] In some implementations, activating the trigger activity involves exposing the optical sensor to incident light. For example, the optical sensor 260 may be covered by a sticker to prevent ambient light from incident on it. The asset tracker 200 can then be activated by removing the sticker (which exposes the optical sensor 260). In this implementation, step 510 (entering sleep mode) involves powering off most peripheral devices except the optical sensor.
[0087] In some implementations, activating the triggering activity includes detecting a loss of proximity between the asset tracker's proximity sensor and a proximity object in the package of the asset tracker 200. For example, the asset tracker may include a proximity sensor 250, such as a Hall effect sensor or a reed switch. The asset tracker's package (e.g., a shipping case) contains a proximity object. When the asset tracker is placed in the package, the proximity object approaches the proximity sensor 250. In some implementations, the proximity sensor includes a Hall effect sensor, and the proximity object includes a magnet. In other implementations, the proximity sensor includes a reed switch, and the proximity object includes a magnet. In such an implementation, step 510 (entering sleep mode) includes powering off most peripheral devices except for the proximity sensor.
[0088] In various implementations described above, the peripheral device detecting activation activity is configured to notify the controller 230 of the activation trigger activity. For example, the IMU 290 can be configured to generate an interrupt signal when a change in activation orientation or a tap is detected. Similarly, the optical sensor 260 can be configured to generate an interrupt signal to notify the controller 230 that incident light has been detected on it. The touch sensor 270 can also be configured to generate an interrupt signal to notify the controller 230 that a touch has been detected. In implementations using proximity sensors (such as reed switches or Hall effect sensors), the sensor is configured to generate an interrupt signal to notify the controller 230 of a change in the proximity sensor's state.
[0089] When an interrupt signal is generated and detected by the controller 230, this constitutes a detected activation trigger activity. Control proceeds from step 520 to step 530. If no activation trigger activity is detected, control returns to step 510.
[0090] At step 530, the asset tracker 200 powers on the positioning module 280. In some implementations, the positioning module is a GNSS receiver, and powering on the positioning module 280 includes powering on the GNSS receiver and obtaining a GNSS positioning lock (i.e., positioning).
[0091] At step 540, the asset tracker 200 checks the health status of various components of the asset tracker 200. For example, the asset tracker 200 can execute firmware instructions (i.e., machine-executable programmable instructions) that verify the normal operation of various peripheral devices of the asset tracker 200. For example, the firmware instructions can write values to various registers of the peripheral devices and then read back those values. The firmware instructions can also read values from sensors and compare those values with expected values.
[0092] At step 550, asset tracker 200 powers on network interface 220 and verifies that asset tracker 200 can send and receive data. For example, asset tracker 200 verifies that asset tracking server 130 is reachable.
[0093] At step 560, the asset tracker 200 checks whether steps 530, 540, and 550 have been successful. Specifically, at step 560, the asset tracker 200 checks whether GNSS positioning lock has been obtained, whether a device health check indicates that peripheral devices are functioning correctly, and whether network interface 220 is functioning correctly. If the above conditions are met, activation is successful. Activation success event 415 causes the asset tracker to transition to motion detection state 420. If the above conditions are not met, activation is unsuccessful, and control returns to step 510. In the latter case, the asset tracker 200 remains in transport state 410.
[0094] Upon entering motion detection state 420, asset tracker 200 executes... Figure 6 Some of the actions depicted in the text.
[0095] At step 610, the asset tracker 200 configures the IMU 290 for travel motion detection. As discussed, in some implementations, the IMU 290 is a 3-axis accelerometer. Configuring the IMU 290 for travel motion detection includes configuring the 3-axis accelerometer to detect acceleration values greater than a travel motion acceleration threshold for a duration exceeding a travel motion detection duration threshold. For example, the IMU 290 may be configured to examine sustained acceleration for a duration exceeding a travel motion acceleration threshold (which exceeds 0.1 g or 0.3 g) for a travel motion detection duration threshold exceeding 2 minutes. In travel motion detection mode, the asset tracker 200 configures the IMU 290 to sample its built-in accelerometer at a low sampling rate (e.g., 1 Hz to 10 Hz). This is because, in travel motion detection state 420, the asset tracker 200 is examining sustained acceleration indicating travel. Additionally, in some implementations, the IMU 290 is configured for noise filtering to filter out high-frequency accelerations that may indicate vibration. For example, the asset tracker 200 can be deployed in a concrete mixer, generator, or any other equipment that experiences some degree of vibration during operation, even when the equipment is not in motion. To filter the noise, acceleration data is passed through a low-pass filter integrated into the IMU 290. Noise filtering is used to eliminate or at least reduce false positives that the IMU 290 may detect during operation.
[0096] When asset tracker 200 is in motion detection state 420, it is in sleep mode, where only IMU 290 is powered on and configured for motion detection as discussed above. In some implementations, the health status of the device and the communication health status of network interface 220 are checked periodically. To do this periodically, at step 620, asset tracker 200 is configured with a timer having a sleep duration. This timer can be a hardware timer as part of controller 230, a stand-alone hardware timer, or a software timer. Asset tracker 200 is configured with a timer having a sleep duration, which can be, for example, equal to 72 hours. This means that every 72 hours, the timer will expire and generate an event notification to controller 230.
[0097] At step 630, asset tracker 200 checks whether travel motion has been detected. The check for travel motion includes checking whether the acceleration measured by the 3-axis accelerometer of IMU 290 has exceeded a travel motion acceleration threshold for a duration exceeding a travel motion detection duration threshold. IMU 290 can be configured to generate an event, such as an interrupt, to controller 230 when the acceleration has exceeded the travel motion acceleration threshold for a duration exceeding the travel motion detection duration threshold. When travel motion is detected, travel motion detection 425 transitions asset tracker 200 to travel state 430. When no travel motion is detected, control proceeds to step 635.
[0098] At step 635, the asset tracker 200 checks whether the sleep duration has expired, and it is time to check the device health and the communication health of the network interface 220. If the sleep duration has not expired, control returns to step 635. If the sleep duration has expired, control proceeds to step 640.
[0099] Step 640 is the same as step 540 discussed above. Similarly, step 650 is similar to step 550 discussed above. After executing both steps 640 and 650, control proceeds to step 660.
[0100] At step 660, asset tracker 200 checks whether a pause command has been received from asset tracking server 130. If a pause command has been received, asset tracker 200 then... Figure 4 The transition 412 returns the system to the transport state. If no pause command is received, control returns to step 620 to restart another sleep duration.
[0101] At step 630, if travel motion has been detected, the asset tracker 200 transitions to the traveling state 430. In the traveling state 430, the asset tracker 200 executes a method comprising multiple steps. In some implementations, the asset tracker 200 uses the IMU 290 to perform end-of-travel detection. In other implementations, the asset tracker 200 uses a GNSS module to perform end-of-travel detection and uses the IMU 290 for impact detection. In still other implementations, the IMU 290 is used for both end-of-travel detection and impact detection.
[0102] First go to Figure 7A It describes method steps performed by the asset tracker 200 when the asset tracker 200 is in the traveling state 430, according to some implementations of this disclosure. Figure 7A In some implementations, a positioning module 280 of a GNSS transceiver is used to detect the start and end of the journey, while in others, a 3-axis accelerometer IMU 290 is configured for impact detection.
[0103] At step 702, the asset tracker 200 initiates a sleep duration, for example, by programming a timer. The travel state sleep duration differs from the sleep duration used in the travel detection state. As an example, the travel state sleep duration is shorter, such as 1 hour.
[0104] At step 704, the asset tracker 200 obtains a GNSS location lock and determines its current location.
[0105] At step 706, asset tracker 200 determines whether it has traveled a distance greater than a travel distance threshold. Specifically, if asset tracker 200 determines whether its current location is... Figure 5 The location difference determined in step 530 is greater than a travel distance threshold. For example, the travel distance threshold could be 200 m. In this case, if the asset coupled to asset tracker 200 has only moved 50 m since the previous GNSS location lock in step 530, asset tracker 200 does not consider itself to be in motion. For example, asset tracker 200 could be coupled to a concrete mixer or generator and simply move around within a construction site. When the location of asset tracker 200 has moved a distance greater than the travel distance threshold, control proceeds to step 708. When the location of asset tracker 200 has moved a distance less than the travel distance threshold, control proceeds to step 716.
[0106] At step 708, asset tracker 200 checks whether a trip start has been detected. This check is because steps 702 through 724 are repeated in the loop (indicated by the arrows returning from step 724 to step 702, as discussed below). Asset tracker 200 behaves differently based on whether an active trip has started. In the first iteration of the loop, no trip has started yet, and the change in location detected at step 706 serves as a trigger to start a trip. Therefore, in the first iteration of the loop, the test at step 708 is false, and control proceeds to step 710. In subsequent iterations of the loop, the test at step 708 is true, and control proceeds to step 720 (because steps 710 and 714 were performed in previous iterations).
[0107] At step 710, the asset tracker 200 configures the IMU 290 for impact detection. Specifically, the asset tracker 200 configures a 3-axis accelerometer to detect acceleration values exceeding an impact acceleration threshold. For example, the impact acceleration threshold could be between 1.5 g and 3 g. Configuring the IMU 290 for impact detection is to detect any unexpected events during the journey that has just begun due to the positioning change detected in step 706.
[0108] At step 714, asset tracker 200 reports the start of a process. For example, asset tracker 200 may power on network interface 220 and send a notification to asset tracking server 130 indicating that asset tracker 200 has started a process and is now in progress.
[0109] At step 720, asset tracker 200 determines whether an impact has been detected. In some implementations, IMU 290 generates an interrupt event detectable by controller 230, indicating that IMU 290 (or its 3-axis accelerometer) has detected an impact greater than an impact acceleration threshold. If an impact has been detected, the asset tracker transitions to impact state 440 due to the detection of impact event 445. If no impact has been detected, control proceeds to step 722.
[0110] At step 722, asset tracker 200 determines whether the sleep duration set in step 704 has expired. In some implementations, step 722 is a timer expiration event. If the sleep duration timer has expired, control proceeds to step 724, and the method continues there. If the sleep duration timer has not expired, asset tracker 200 enters sleep mode and remains in sleep mode until the sleep duration timer expires.
[0111] At step 724, the sleep duration has expired, and the asset tracker 200 wakes from sleep mode. At step 724, the asset tracker checks the health status of its peripheral devices and the network interface 220. Step 724 and... Figure 5 Steps 540 and 550 and Figure 6 Steps 640 and 650 are the same. After step 724, control returns to step 702.
[0112] At step 716, if the journey has begun and the asset tracker's location has not changed since the previous GNSS location lock, this indicates that the asset tracker 200 is in the process of travel and has stopped moving. In this implementation, the asset tracker 200 determines that the journey end event 435 has occurred. If the location has not changed since the previous GNSS location lock and the journey has not begun, then travel is not confirmed. In the latter case, a travel not confirmed event 426 is generated, which brings the asset tracker back to the travel motion detection state 420.
[0113] In some implementations, trip start and / or trip end reporting occurs only when the sleep duration expires. For example, in step 722, asset tracker 200 records the trip start time and location, and only reports it to the asset tracking server after the sleep duration has expired. In such an implementation, in step 724, trip start is reported while checking health status and communications. Similarly, in some implementations, in step 724, trip end is also reported while checking health status and communications.
[0114] exist Figure 7A In the implementation described above, IMU 290 is configured for impact detection, while trip end detection is performed solely by positioning module 280, which can be a GNSS transceiver. Advantageously, both trip end detection and impact detection are feasible. However, since GNSS positioning lock (step 704) only occurs every few sleep durations, reporting trip start and trip end can sometimes be delayed. Figure 7B The alternative implementation shown abandons impact detection and uses an IMU 290 for end-of-journey detection. One advantage of using an IMU 290 for end-of-journey detection is that the IMU 290 (especially if it only includes a 3-axis accelerometer) consumes significantly less power and can generate an interrupt event when conditions are met. GNSS transceivers consume more power and therefore cannot be continuously powered.
[0115] Figure 7B The steps of the method are basically similar Figure 7A The steps of the method are similar, but there are some significant differences as described below.
[0116] Steps 702 and 704 are the same as above. Figure 7A The corresponding steps described are unchanged.
[0117] At step 706, if the location has changed beyond the travel distance threshold, control proceeds to step 716 as before. If the location has not changed beyond the travel distance threshold, control proceeds to step 708.
[0118] At step 708, if no trip start is detected (and the location has not changed beyond the threshold from step 706), the trip is not confirmed. A trip not confirmed event 426 is generated, which brings the asset tracker back to the trip motion detection state 420.
[0119] At step 716, if the start of a stroke has been detected, control proceeds to step 722. If the start of a stroke has not been detected, control proceeds to step 711.
[0120] At step 711, asset tracker 200 configures IMU 290 for end-of-journey detection. Configuring IMU 290 for end-of-journey detection includes configuring a 3-axis accelerometer to generate an event when the detected acceleration decreases to an end-of-journey acceleration decrease threshold for a sustained duration. For example, the 3-axis accelerometer may detect acceleration in the x, y, and z directions. The 3-axis accelerometer may be configured to generate an end-of-journey interruption event to controller 230 when the combined acceleration in the x, y, and z directions decreases below the end-of-journey acceleration decrease threshold, reaches a lower acceleration value, and remains at a lower acceleration value for at least the end-of-journey detection duration.
[0121] At step 714, the trip is reported to have started as described above.
[0122] At step 721, if a trip end is detected, a trip end event 435 transitions the asset tracker 200 to the trip end state 450. If no trip end is detected, control proceeds to step 722.
[0123] The above has been referenced Figure 7A Steps 722 and 724 are described below.
[0124] Advantageously, Figure 7B The method captures the trip end event as soon as the IMU 290 detects it, thus reporting the trip end in real time, instead of reporting when the sleep duration expires and / or when a new GNSS positioning lock is obtained.
[0125] In another implementation, the asset tracker 200 utilizes the IMU 290 to detect both trip end events and input events. (See also...) Figure 7C This will be described.
[0126] Figure 7C Steps 702 and 704 in the text are similar to... Figure 7B The corresponding steps are the same.
[0127] At step 706, if the location has changed beyond the travel distance threshold, control proceeds to step 708. If the location has not changed beyond the travel distance threshold, control proceeds to step 716.
[0128] At step 716, if the journey has already started, control proceeds to step 720. If the journey has not yet started, the journey is not confirmed. Therefore, a journey not confirmed event 426 is generated, and the asset tracker 200 transitions back to the journey motion detection state 420.
[0129] At step 708, if the process has not yet started, control proceeds to step 710. If the process has already started, control proceeds to step 720.
[0130] Steps 710 and 711 are respectively with Figure 7A Steps 710 and Figure 7B Step 711 is the same. Therefore, if the 3-axis accelerometer detects an acceleration greater than the impact acceleration threshold, the IMU 290 can generate an interrupt event. Additionally, the IMU 290 can also generate an interrupt even if the 3-axis accelerometer detects a decrease in acceleration value greater than the end-of-stroke acceleration decrease threshold for a duration equal to or longer than the end-of-stroke threshold.
[0131] Step 720 and Figure 7A Step 720 is the same. If an impact is detected, the impact event 445 causes the asset tracker 200 to switch to impact state 440.
[0132] Step 721 and Figure 7B Step 721 is the same. If the trip is detected to be over, a trip over event 435 is generated, and the asset tracker 200 transitions to the trip over state 450.
[0133] Steps 722 and 724 are the same as the corresponding steps described above.
[0134] Figure 7C This method can be implemented using an asset tracker with an IMU 290, which can support the detection of both shocks and a decrease in acceleration values over a specified duration. Some IMU / 3-axis accelerometers support this feature. Advantageously, this is implemented while the asset tracker is in motion. Figure 7C The asset tracker can report trip end events and collision events in a timely manner.
[0135] Figure 8 The steps performed by asset tracker 200 when it is in the trip end state 450 are described. At step 810, the asset tracker powers on network interface 220. At step 820, asset tracker 200 reports a trip end event by sending a trip end indication to a remote entity, such as an asset tracking server, via network interface 220. At step 830, asset tracker 200 de-powers network interface 220 to conserve power. After de-powering the network interface, reporting the trip end event 455 causes asset tracker 200 to transition back to the motion detection state 420.
[0136] Figure 9 The steps performed by asset tracker 200 when in impact state 440 are described. At step 910, the asset tracker powers on network interface 220. At step 920, asset tracker 200 reports an impact event by sending an indication of the detected impact (e.g., its magnitude and timestamp) to a remote entity such as an asset tracking server via network interface 220. At step 930, asset tracker 200 de-powers network interface 220 to conserve power. After de-powering the network interface, reporting the impact event 465 causes asset tracker 200 to transition back to motion detection state 420.
[0137] Implementations of the technology in circuit systems and / or computer-executable instructions have been described. It should be understood that some implementations may take the form of methods or processes, and at least one example of such methods or processes has been provided. Actions performed as part of a method or process can be ordered in any suitable manner. Therefore, implementations can be constructed that perform actions in an order different from the order shown, which may include performing some actions simultaneously, even if they are shown as sequential actions in the illustrative embodiments. Various aspects of the above-described embodiments can be used individually, in combination, or in various arrangements not specifically discussed in the embodiments described above, and are therefore not limited in their application to the details and arrangements of the components set forth in the foregoing description or shown in the accompanying drawings. For example, aspects described in one embodiment can be combined in any way with aspects described in other embodiments.
Claims
1. An asset tracker, comprising: case; The controller is installed in the housing; A positioning module is disposed in the housing and coupled to the controller; A 3-axis accelerometer is housed in the housing and coupled to the controller; as well as A memory coupled to the controller stores machine-executable programming instructions that, when executed by the controller, configure the asset tracker to: The asset tracker is operated in transit, and in transit, the first location of the asset tracker is obtained by the positioning module. In response to a successful activation event, the asset tracker is switched to motion detection state; as well as In response to the detection of moving motion by the 3-axis accelerometer, the asset tracker is switched to a moving state.
2. The asset tracker according to claim 1, wherein, The machine-executable programming instructions that configure the asset tracker to operate in the transport state include machine-executable programming instructions that configure the asset tracker to perform the following operations: Enter sleep mode; Configure the 3-axis accelerometer to detect and activate trigger activities; as well as In response to the detection of the activation trigger activity: Obtain the first location of the asset tracker; as well as Generate the activation success event.
3. The asset tracker according to claim 1, wherein, The machine-executable programming instructions that configure the asset tracker to detect traveling motion include machine-executable programming instructions that configure the 3-axis accelerometer to measure acceleration for a duration greater than a traveling motion acceleration threshold exceeding a traveling motion detection duration threshold.
4. The asset tracker according to claim 1, wherein, The machine-executable programming instructions also configure the asset tracker to be in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is greater than the travel distance threshold: Before the trip begins: Configure the 3-axis accelerometer for impact detection, and Report the start of the trip.
5. The asset tracker according to claim 1, wherein, The machine-executable programming instructions also configure the asset tracker to be in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is greater than the travel distance threshold: When the journey has already begun: Switch to trip completion status; Report the end of the trip; and After reporting the trip completion event, the system transitions to the motion detection state.
6. The asset tracker according to claim 1, wherein, The machine-executable programming instructions also configure the asset tracker to be in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is less than the travel distance threshold: Before the trip begins: Switch back to the motion detection state.
7. The asset tracker according to any one of claims 1 to 6, wherein, The machine-executable programming instructions also configure the asset tracker to be in the traveling state: In response to the impact detected by the 3-axis accelerometer, the system switches to an impact state.
8. The asset tracker according to claim 1, wherein, The machine-executable programming instructions also configure the asset tracker to be in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is greater than the travel distance threshold: Before the trip begins: Configure the 3-axis accelerometer for end-of-stroke detection, and Report the start of the trip.
9. The asset tracker according to claim 8, wherein, The machine-executable programming instructions for configuring the 3-axis accelerometer for the end-of-stroke detection include machine-executable programming instructions that configure the 3-axis accelerometer to generate an event when the detected acceleration drop end-of-stroke drop threshold reaches the end-of-stroke detection duration.
10. The asset tracker according to claim 1, wherein, The machine-executable programming instructions also configure the asset tracker to be in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is greater than the travel distance threshold: Before the trip begins: The 3-axis accelerometer is configured for impact detection. Configure the 3-axis accelerometer for end-of-stroke detection, and Report the start of the trip.
11. A method for trip detection by an asset tracker, the method comprising: Operating the asset tracker in transit includes obtaining a first location of the asset tracker. In response to a successful activation event, the asset tracker is switched to motion detection state; as well as In response to the detection of movement, the asset tracker is switched to a moving state.
12. The method according to claim 11, wherein, Operating the asset tracker during the transport state includes: Enter sleep mode; Configure the inertial measurement unit to detect activation triggering activities; and In response to the detection of the activation trigger activity: Obtain the first location of the asset tracker; and Generate the activation success event.
13. The method according to claim 11 or claim 12, wherein, Detecting motion involves measuring accelerations exceeding a motion acceleration threshold for a duration exceeding the motion detection duration threshold using a 3-axis accelerometer.
14. The method according to any one of claims 11 to 13, further comprising, in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is greater than the travel distance threshold: Before the trip begins: Configure a 3-axis accelerometer for impact detection, and Report the start of the trip.
15. The method according to any one of claims 11 to 13, further comprising, in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is greater than the travel distance threshold: When the journey has already begun: Switch to trip completion status; Report the end of the trip; and After reporting the trip completion event, the system transitions to the motion detection state.
16. The method according to any one of claims 11 to 13, further comprising, in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is less than the travel distance threshold: Before the trip begins: Switch back to the motion detection state.
17. The method according to any one of claims 11 to 13, further comprising, in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is greater than the travel distance threshold: Before the trip begins: Configure a 3-axis accelerometer for end-of-stroke detection, and Report the start of the trip.
18. The method according to any one of claims 11 to 17, further comprising, in the traveling state: in response to an impact detected by the 3-axis accelerometer: Transition to impact state.
19. The method of claim 17, wherein, Configuring the 3-axis accelerometer for the end-of-journey detection includes: configuring the 3-axis accelerometer to generate an event when the detected acceleration drop threshold reaches the end-of-journey detection duration.
20. The method according to any one of claims 11 to 13, further comprising, in the traveling state: Obtain the second location of the asset tracker; and When the distance between the second location and the first location is greater than the travel distance threshold: Before the trip begins: Configure a 3-axis accelerometer for impact detection. Configure the 3-axis accelerometer for end-of-stroke detection, and Report the start of the trip.