(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2012/0194679 A1
`Nehowig et al.
`(43) Pub. Date:
`Aug. 2, 2012
`
`US 20120194679A1
`
`(54)
`
`MULT-MODE VEHICLE COMPUTING
`DEVICE SUPPORTING IN-CAB AND
`STAND-ALONE OPERATION
`
`(76)
`
`Inventors:
`
`Kelly R. Nehowig, Maple Grove,
`MN (US); Ronald Edward
`Konezny, Shorewood, MN (US)
`
`(21)
`
`Appl. No.:
`
`13/361,184
`
`(22)
`
`Filed:
`
`Jan. 30, 2012
`
`(60)
`
`Related U.S. Application Data
`Provisional application No. 61/438,250, filed on Jan.
`31, 2011.
`
`Publication Classification
`
`(51) Int. Cl
`(2006.01)
`iouN 7/18
`(2006.01)
`G06F 3/00
`(2006.01)
`G06F 3/00
`(52) U.S. Cl. ... 348/148; 7.10/304; 710/16; 348/E07.085
`(57)
`ABSTRACT
`Techniques involving connecting an in-cab computing device
`to an onboard computing device mounted in a vehicle.
`Vehicle-related information may be communicated between
`the in-cab computing device and onboard computing device
`while the in-cab computing device is connected to the
`onboard computing device. Techniques involve facilitating
`disconnection of the in-cab computing device from the
`onboard computing device and operating the in-cab comput
`ing device in a stand-alone mode, and facilitating reconnec
`tion of the in-cab computing device to the onboard computing
`device to resume operations between the in-cab computing
`device and onboard computing device.
`
`:::: *
`
`*:
`
`
`
`*
`
`...
`- 8:
`(88088EC08:88 -
`{{80}
`:
`& FROCESSOR -
`
`
`
`
`
`
`
`ges&ECEER • 28
`
`38 * : 8888 & 8
`:g. E8 x 8
`
`&
`
`SE8(88
`
`
`
`i
`
`i
`
`- -
`2:8. “
`&
`388
`
`
`
`:
`:
`
`&8::::::
`M:
`8:38:
`
`.
`*
`Y-- 3:
`
`councan 8: o:
`
`^^^^^^^*
`
`
`
`---
`
`w :
`
`''''''''''''''''''''''''''''''''''''''''''
`
`38:::::
`
`.........................................................................
`
`DJI-1026
`IPR2023-01106
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 1 of 9
`
`US 2012/O194679 A1
`
`
`
`: :: k
`<x 3888.3:
`
`.....
`
`Cox PA8-8 |. 88:
`
`s:::::::::::::::::::::::s:'
`
`a's
`
`-
`
`
`
`4.i. s â
`
`:::::
`388883
`
`ass
`
`
`
`38::::::
`8:::::::
`
`
`
`
`
`
`
`as
`
`3888 & 8
`(e.g. Eck: B&is
`
`
`
`
`
`ONBoard court
`*
`W. Rocess 8 &M
`-
`8.
`s 3:388
`
`
`
`
`
`
`
`---
`
`8.338 :38:::::::::
`8:::
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 2 of 9
`
`US 2012/O194679 A1
`
`s
`
`^ -M
`
`s
`s
`
`Lasn :
`
`súsów
`
`****** · §§
`
`3 ***''''''''''''',
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 3 of 9
`
`US 2012/O194679 A1
`
`
`
`
`
`
`
`88:
`
`:::::f.
`FEMALE
`
`
`
`tit.
`FEMALE
`
`
`
`Ussport 2
`
`f.
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 4 of 9
`
`US 2012/O194679 A1
`
`:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
`
`X
`
`8.
`
`-
`- perect
`DiscONNECTION OF N-CAB Oc
`- COPING DECE -
`
`
`
`
`
`* *
`
`^
`
`No -1. PETEC, is
`&
`RECONNECT ON OF Ni-CAB
`>
`sco Pur NGBEvice
`
`a. s
`
`r *
`
`^--
`
`
`
`
`
`
`
`
`
`{{{{ kix :::S
`38: 888: 8: 8::::::::::::
`
`
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 5 of 9
`
`US 2012/O194679 A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`**~~~~~~.~~~~~ºº
`
`, 38,888 ?
`
`''''''''',
`
`''''''.
`
`&##$ $3
`
`*************************
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 6 of 9
`
`US 2012/O194679 A1
`
`
`
`s:
`
`
`
`?**********, g***********
`
`was assassissa
`
`&s
`
`
`
`********************* ***********************
`
`----------
`
`S.
`
`****
`
`**********,
`
`'X
`
`Xaa--------->
`
`-----------
`
`-a--------->
`
`-------------------.
`
`Le ,
`
`
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 7 of 9
`
`US 2012/O194679 A1
`
`ress,
`
`Six
`
`8x8
`
`*
`
`:
`8
`
`8xx 8-38.88.088 8888.088 x
`
`s: 8:3
`
`..
`
`.
`
`:
`:
`
`SYS
`
`
`
`:
`
`:
`
`s's
`
`88.888&
`
`...-:
`
`882 “I:-.
`- 88s
`(88&E
`*:::::
`
`388x
`8.
`
`g
`
`s
`
`-
`
`8:38:
`38.33
`
`FAir
`COE.8s
`
`
`
`i
`
`:
`
`
`
`
`
`---------------------------
`
`---------------------------
`
`i- 8::
`-:
`keyboard
`
`---------------------------' :
`
`if
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 8 of 9
`
`US 2012/O194679 A1
`
`''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
`
`?*
`
`********************************************
`
`**************************************************
`
`§§§§§§§§
`
`ºoo
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`:
`
`:-
`
`§§§§§
`
`*********************************************************************************************************************************************************************************************
`
`

`

`Patent Application Publication
`
`Aug. 2, 2012 Sheet 9 of 9
`
`US 2012/O194679 A1
`
`
`
`
`
`
`
`
`
`
`
`connect anciscoviruri covice to anonscrocopus Device
`
`::::::::::::::::
`
`:
`
`::::::::::::::::::::::::883 :::::::::::::::::::::::::88-88
`{::::::::::::::::::::::::::::::::::::::::
`i:
`i::::::::::::::
`X:::::::::::::::::::::::::::::::: 8888 X::::::::::::
`
`88::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
`C:*::::::::: {xk} {}{888 (8: 8: 8-Ois C8883 ::: 8:8
`88-88:::::8
`
`10.4
`
`3:08
`
`::::::::::::::::::
`
`if it
`
`

`

`US 2012/0 194679 A1
`
`Aug. 2, 2012
`
`MULT-MODE VEHICLE COMPUTING
`DEVICE SUPPORTING IN-CAB AND
`STAND-ALONE OPERATION
`
`RELATED APPLICATIONS
`
`0001. This application claims the benefit of Provisional
`Patent Application No. 61/438,250, filed on Jan. 31, 2011, to
`which priority is claimed pursuant to 35 U.S.C. S 119(e) and
`which is incorporated herein by reference in its entirety.
`
`SUMMARY
`
`0002 Embodiments described in this disclosure are gen
`erally directed to a portable computing device removably
`connectable to a vehicle onboard computer. Connections may
`be made directly or by way of a docking cradle. Transporta
`tion-related tasks can thus be conducted on a single device
`which serves as both the user interface to the onboard com
`puting device, as well as a detachable/portable computing
`device to execute other business related functions.
`0003. According to embodiments described herein, tech
`niques methods of the disclosure involve connecting an in
`cab computing device to an onboard computing device
`mounted in a vehicle. Vehicle-related information may be
`communicated between the in-cab computing device and
`onboard computing device while the in-cab computing device
`is connected to the onboard computing device. Techniques
`involve facilitating disconnection of the in-cab computing
`device from the onboard computing device and operating the
`in-cab computing device in a stand-alone mode, and facilitat
`ing reconnection of the in-cab computing device to the
`onboard computing device to resume operations between the
`in-cab computing device and onboard computing device.
`0004. According to another representative embodiment, a
`system includes an onboard computing device and an in-cab
`computing device. The onboard computing device includes a
`first processor configured to collect vehicle-related data, and
`includes a transceiver configured to communicate at least
`some of the vehicle-related data over one or more networks to
`one or more destination entities. The in-cab computing device
`includes at least one disconnectable connection to the
`onboard computing device to communicate information
`between the in-cab computing device and the onboard com
`puting device, and a second processor configured to execute
`one or more applications independently of the onboard com
`puting device when disconnected from the onboard comput
`ing device.
`0005. This summary introduces representative concepts
`that are further described in the ensuing description. The
`Summary is not intended to identify essential features of
`current or future claimed subject matter, nor is it intended to
`be used to limit the scope of the claimed subject matter.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0006 FIG. 1 is a block diagram illustrating a representa
`tive environment in which the principles described herein
`may be practiced;
`0007 FIG. 2 is a block diagram illustrating a representa
`tive vehicle system utilizing an in-cab computing device;
`0008 FIG. 3 is a block diagram illustrating a representa
`tive manner for connecting the in-cab computing device to
`other components in the representative system;
`
`0009 FIG. 4 illustrates a representative example of pow
`ering the onboard computing device and/or in-cab computing
`device;
`0010 FIG.5 depicts a more particular example of connec
`tors and signals that may be used in connection with the
`in-cab computing device;
`0011
`FIG. 6 is a flow diagram illustrating an exemplary
`method for managing OBC data when the in-cab computing
`device has been disconnected from the OBC;
`0012 FIG. 7A is a block diagram illustrating various rep
`resentative features of an in-cab computing device according
`to embodiments of the invention;
`0013 FIG. 7B illustrates an example of a form factor and
`representative layout of an in-cab computing device;
`0014 FIG. 8 illustrates an example display that presents at
`least selectable icons, a button bar 804, and menu navigation
`initiation;
`0015 FIG. 9 is a diagram illustrating a representative sys
`tem in which the in-cab computing device may be utilized;
`and
`0016 FIG. 10 is a flow diagram illustrating a representa
`tive method in which the in-cab computing device serves as a
`multi-mode vehicle computing device Supporting both in-cab
`and stand-alone operation.
`
`DETAILED DESCRIPTION
`0017. In the following description, reference is made to
`the accompanying drawings that depict representative imple
`mentation examples. It is to be understood that other embodi
`ments and implementations may be utilized, as structural
`and/or operational changes may be made without departing
`from the scope of the disclosure. Throughout the disclosure,
`like reference numbers are used to identify like components,
`blocks and other items where appropriate.
`0018. The disclosure is generally directed to transporta
`tion-related activities in transportation industries, such as in
`the trucking industry. While the disclosure is directed prima
`rily to trucks and fleets of trucks, the principles described
`herein are equally applicable to other vehicle types.
`0019. Implementations may be used in connection with
`vehicles ranging from a single vehicle to large fleets of
`vehicles having different characteristics. Traveling vehicles
`equipped with communication devices are configured to at
`least communicate data to a data center or other central office
`system. While the vehicles and/or drivers need not have any
`association with one another, the vehicles may be part of one
`or more fleets of vehicles, such as in the trucking industry. The
`central office may serve as a fleet management system in
`which the trucks or other vehicles communicate, regardless of
`which fleet, if any, they may be associated with. The fleet
`management system delivers an array of services and solu
`tions utilizing a fleet of mobile communication devices and
`in-cab computing devices in the vehicles.
`0020. As noted above, the principles and representative
`implementations described herein may be implemented in
`any vehicle, whetheran individual vehicle or associated with
`one or more fleets of vehicles. For purposes of illustration and
`not of limitation, FIG. 1 generally illustrates a representative
`use of in-cab computing devices and their cooperative opera
`tion with on-board computers (OBC) in a fleet of trucks to
`facilitate communication with a central office and/or other
`facility. The block diagram of FIG. 1 therefore illustrates a
`representative environment in which the principles described
`herein may be practiced. The example of FIG. 1 assumes that
`
`

`

`US 2012/0 194679 A1
`
`Aug. 2, 2012
`
`one or more entities, labeled company-A100A through com
`pany-N100N manages a fleet of one or more vehicles. Rep
`resentative trucks 102 and/or other vehicles are associated
`with company-A 100A in the illustrated embodiment. The
`company-A 100A may track locations of the vehicles 102
`using location services, such as cellular triangulation, global
`positioning system (GPS) 104 or other satellite 106 tracking
`mechanisms, and/or other manners of tracking the movement
`and location of the fleet. Other information may be gathered
`by company-A 100A (e.g. a dispatch company) that may be
`provided by the vehicles 102 to the company-A100A by any
`desired means, such as data transmission via the cellular
`infrastructure represented by the cellular base station 108.
`The information may be provided in other manners, such as
`via satellite 106 and/or other data delivery mechanisms.
`Company-A 100A may utilize the information in its fleet
`dispatch operations. Information concerning the vehicles 102
`may instead or additionally be collected by one or more third
`parties 110. Such as fuel card providers, mobile communica
`tion companies, etc.
`0021 Services and applications may be made available,
`for example, for the companies 100A-100N and/or the
`vehicle 102 operators. Companies 100A-100N may provide
`dispatch services to their fleet, and may provide a software
`interface that drivers of the vehicles 102 may access. Infor
`mation may alternatively or additionally be provided by way
`of a mobile communication vendor(s), represented in FIG. 1
`as a third party 110. Companies having a fleet of vehicles, or
`independently owned vehicles may utilize services of a
`mobile communication vendor 110 such as PeopleNetTM
`Communications Corporation. With onboard computing (not
`shown) on such vehicles 102 to obtain information such as
`GPS or other location data, electronic engine data, onboard
`event recording information and the like, a mobile commu
`nication vendor 110 can collect information that may then be
`provided directly, and/or by way of services/applications, for
`use by the companies 110A-110N and/or vehicles 102.
`0022. In accordance with the disclosure, an in-cab com
`puting solution facilitates the use of Such services, applica
`tions and other functionality. Embodiments of an in-cab com
`puting device include cooperative communication with the
`onboard computer to provide travel-related functionality as
`well as other computing functionality to assist vehicle drivers.
`FIG. 2 is a block diagram illustrating a representative vehicle
`system 200 utilizing an in-cab computing device 202. In one
`embodiment, the onboard computer (OBC) 204 serves as the
`communications hub for both wireless communication, and
`data from the truck or OBC to the in-cab computing device
`202. Thus, the OBC 204 may provide mobile communica
`tions, onboard computing, fleet management, etc. The OBC
`204 can facilitate multi-network communications. Such as
`dual-mode wireless-satellite communications. In one
`embodiment, Global Positioning System (GPS) technology is
`employed at the OBC 204, which in one embodiment is
`provided by wide area augmentation system (WAAS) tech
`nology. In one embodiment the OBC exhibits an open devel
`opment platform for rapid and custom development of new
`applications. OBC 204 connections may include, for
`example, universal serial bus (USB) connectors and vehicle
`diagnostics connections (e.g. J1708, J1909, CAN, OBDII,
`etc.).
`0023. More particularly, as shown in FIG. 2, one embodi
`ment of the system 200 includes the OBC 204 that represents
`an embedded system having its own processor and associated
`
`processing capabilities. The OBC 204 may connect to an
`engine data bus 206 that provides engine data 208. For
`example, vehicles Such as commercial trucks typically
`include an engine control module (ECM) or other electronic
`control unit that is associated with the engine of the respective
`vehicle. In addition to assisting with operational functions
`Such as controlling fuel mixture, timing, idle speed, etc.,
`ECMs are capable of providing the data to which they are
`privy to. For example, an ECM includes a data bus to provide
`engine data Such as RPM, speed, calculated miles per gallon
`(MPG) of fuel consumed, miles traveled, engine idle time,
`engine hours, door lock status, windshield wiper status, and
`the like. The OBC 204 may obtain such engine data 208 for
`processing and/or communication to other entities.
`(0024. The OBC 204 may also be connected to a Global
`Positioning System (GPS) receiver 210 and/or other location
`technology receiver. GPS and other analogous technologies
`can identify the location of the GPS receiver, which is co
`located with the truck or other vehicle in the present disclo
`Sure. Thus, latitude/longitude coordinates, landmarks or
`other location identifiers can be obtained by the OBC 204 by
`way of the GPS receiver 210. This enables the location, and
`continuous route if desired, to be tracked by the driver of the
`truck as well as an external entity Such as the dispatch com
`pany responsible for managing fleet transportation.
`0025. In one embodiment, a cellular modem 212 is pro
`vided to communicate at least data, and in Some embodiments
`Voice as well, with other entities Such as the driver's company,
`a dispatch company, a mobile communications company, etc.
`The cellular modem 212 may be configured to communicate
`via CDMA technology, GSM/GPRS technology or any other
`similar technology. Other communication devices may also
`or alternatively be provided, such as a satellite modem 214 or
`other 216 communication receiver or transceiver.
`(0026. The depicted OBC 204 is representative of what
`may reside in each vehicle monitored in accordance with
`embodiments of the disclosure. In one embodiment the OBC
`204 is powered by the power system of the vehicle and
`includes a processor(s). Such as a microprocessor 220. Pro
`cessor 220 is coupled to communication module 222 which is
`configured to cooperatively communicate with a messaging
`module of a central communication center or other entity by
`way of the cellular modem 212, satellite modem 214 and/or
`other modem 216. For example, the OBC 204 may attempt to
`communicate by cellular modem 212 first, and loss of suffi
`cient cellular signal strength may automatically or manually
`activate data communications via the satellite modem 214 or
`other 216 communication mechanism. The OBC 204 may
`also include various sensors 224 to provide information not
`otherwise provided by the engine data. GPS circuitry 226
`may also be provided to manage GPS information received
`from the GPS receiver 210.
`0027. In one embodiment, information relating to the
`engine data 208, location data obtained from the GPS receiver
`210 and other information is provided to a data center of a
`company, dispatch center, mobile communication company
`and/or other entity by way of data call records. Such data call
`records can contain an enormous amount of information col
`lected by the OBC 204 regarding cell signal strength, GPS
`location, Service Identifier (SID) or analogous cellular net
`work identifier, channel, baud, data payload, and duration, for
`example. Call records may include vehicle data for each fleet
`vehicle that communicates with the central office. Vehicle
`data may include at least identification data that uniquely
`
`

`

`US 2012/0 194679 A1
`
`Aug. 2, 2012
`
`identifies each OBC 204 and location data indicative of a
`geographic location of each vehicle at the time of data trans
`mission initiation. The vehicle data associated with each data
`transmission is stored locally at each vehicle as a call record
`or other data packet, and transmitted to the central office on a
`repeated and/or prompted basis.
`0028. In accordance with the present disclosure, the OBC
`204 is also coupled to the in-cab computing device 202. The
`in-cab computing device 202 provides a user interface for the
`vehicle operator, as well as processing capabilities for con
`ducting communications, executing applications, and the
`like. Representative examples of in-cab computing devices
`202 are described more fully below.
`0029 FIG. 3 is a block diagram illustrating a representa
`tive manner for connecting the in-cab computing device 202
`to other components in the representative system. The in-cab
`computing device 202 may be directly coupled to various
`devices, including the onboard computer 204, by way of
`connectors 300 associated with the in-cab computing device
`202. For example, connectors 300 may enable connection to
`the onboard computer 204, peripheral devices 302, sensors
`and/or other items via RS-422 connections 304, RS-232 con
`nections 306, USB connections 308, and other 310 types of
`connections. In one embodiment, the in-cab computing
`device 202 is mounted in the vehicle cab in a fixed manner,
`whereby the appropriate connections 304-310 may be
`directly coupled to the connectors 300 on the in-cab comput
`ing device 202. In another embodiment, the in-cab computing
`device 202 may be removable, and the connections 304-310
`are connected and disconnected directly from the in-cab com
`puting device 202. This embodiment provides a portable solu
`tion that enables the in-cab computing device 202 to be
`removed from the cab, or at least from its mounted location,
`for other uses.
`0030. In another embodiment, portability of the in-cab
`computing device 202 is enhanced through the use of a dock
`ing station320. Both the in-cab computing device 202 and the
`docking station320 may respectively include connectors 322,
`324 to facilitate connecting the in-cab computing device 202
`to the docking station 320. A RAM-ball type of mount is
`utilized in one embodiment. The docking station 320 may
`include a key lock for a fixed mount, and peripheral devices
`are Supported when plugged into the docking station ports
`326. In this manner, the onboard computer 204, peripheral
`devices 302 and other items may be coupled to the in-cab
`computing device 202 by way of the docking station 320.
`0031 When used in-cab, the in-cab computing device 202
`may receive power directly, or by way of the docking station
`320, from the vehicle battery. A representative example of a
`power implementation is depicted in FIG. 4. The vehicle
`power 400 may be, for example, a 12-volt automotive battery
`in the truck or other vehicle. The power may be wired, such as
`via blunt cut wires 402,404 to connectors 406, 408. A fuse(s)
`410 may be used, such as along the +12-volt lead. The con
`nectors 406, 408 enable connection of the vehicle power
`wires 402, 404 to be connected to a DC-DC converter 412,
`which in the illustrated embodiment is a 12V-to-19V DC-DC
`converter. The converted DC power is provided via connector
`414 to the OBC 204, and to the in-cab computing device 202
`either directly or by way of the docking station 320. For
`example, a connector 414 may be used to provide power to the
`OBC 204. As another example, the connector 416 may be
`used to directly provide power to a connector 418 on the
`in-cab computing device 202, or to the in-cab computing
`
`device 202 by way of connector 420 associated with docking
`station320. The RS-422 (or other interface) enables commu
`nication between the in-cab computing device 202 and the
`onboard computer 204.
`0032. As the in-cab computing device 202 may be used
`independently from the vehicle operations, it includes a bat
`tery 422. When disconnected from the vehicle power 400, the
`battery 422 can provide power to the in-cab computing device
`202 for portable use.
`0033 FIG.5 depicts a more particular example of connec
`tors and signals that may be used in connection with the
`in-cab computing device 202. In the example of FIG. 5, it is
`assumed that a docking station 320 is used, although the
`interfaces could be directly coupled to the in-cab computing
`device 202. In this example, the docking station includes a
`connector 500 that is used to at least provide an RS-422
`interface 502 to communicate with the OBC 204. As noted in
`FIG.4, power may also be provided via the connector 500.
`0034. The docking station 320 also includes one or more
`connectors 504 that provide other inputs and outputs. For
`example, connector 504 provides an audio out interface 506,
`Such as Stereo left, stereo right, and stereo ground. Thus,
`external speakers may be coupled to the docking station 320
`and ultimately the in-cab computing device 202. Similarly, a
`mute output 508 may be provided, as well as dash panel lamps
`input 510 and possibly spare inputs and ground 512. Another
`connector(s) 514 may provide one or more USB ports, such as
`USB ports 516,518, 520. In one embodiment, the connector
`514 is connected to the USB ports 516, 518, 520 via a USB
`pigtail harness.
`0035 Any number or type of connectors may be utilized
`on the docking station 320 and/or in-cab computing device
`202. The connectors, interfaces and signals described in con
`nection with FIG. 5 are provided for purposes of illustration
`only.
`0036. The portability of the in-cab computing device pro
`vides for great flexibility of use when the in-cab computing
`device is removed from the docking station or otherwise
`disconnected from the OBC and other components. While
`traveling and connected to the onboard computer, the in-cab
`computing device operates as a user interface for the OBC
`functionality, as well as providing other computing functions.
`When the in-cab computing device is disconnected from the
`OBC, it can still execute applications. Thus, a single device
`can be used to perform both travel-related functions, and
`industry-related applications that are not dependent upon
`connection to an OBC or other vehicle components. The
`in-cab computing device thus serves as both a cab-based
`device and a hand-held device to aggregately serve the needs
`of drivers and fleet management.
`0037. In one embodiment, the system is capable of pre
`serving travel-related data when the in-cab computing device
`is disconnected from the OBC. For example, a driver may
`have an in-cab computing device 202 connected to a docking
`station 320 as he is driving. The in-cab computing device 202
`may have business rules Software that uses data from the
`onboard computer 204 relating to, for example, location
`information, odometer readings, etc. The business rules Soft
`ware may dictate how certain information will be captured,
`Such as for driver's logs. For example, information Such as the
`identity of the driver, GPS position, and the like may be
`utilized. In many cases, state Department of Transportation
`(DOT) rules may vary from state to state, and vary from
`federal DOT rules. When positioning systems indicate that
`
`

`

`US 2012/0 194679 A1
`
`Aug. 2, 2012
`
`boundaries have been crossed, the business rules may need to
`be changed to comply with that state or other area's rules.
`0038. Therefore, connection to the OBC in such situations
`may be important to continue to receive information from the
`OBC. However, the driver may remove the in-cab computing
`device 202 from the docking station 320 to perform other
`tasks, whether the vehicle is still in route or stopped. The OBC
`204 is, however, still collecting data at such times, but the
`in-cab computing device 202 is not in a position to receive
`that data when disconnected. In one embodiment, the OBC
`204 recognizes that the in-cab computing device 202 has been
`disconnected, in which case accumulated data will be stored
`until the in-cab computing device 202 has been reconnected.
`When the in-cab computing device 202 is reconnected, a
`“playback mode” is effected that causes the data to be pre
`sented to the reconnected in-cab computing device 202 in the
`order it originally occurred, whereby the in-cab computing
`device 202 processes the buffered information just as if the
`events were happening as they actually occurred. In this man
`ner, driver's logs and other applications can be "caught up'
`Such that the logs are complete and accurate when the in-cab
`computing device has been reconnected.
`0039 FIG. 6 is a flow diagram illustrating an exemplary
`method for managing OBC data when the in-cab computing
`device has been disconnected from the OBC. In this repre
`sentative example, it is assumed that the in-cab computing
`device is connected to the OBC as shown at block 600. As
`shown at block 602, the data collected by the OBC is provided
`from the OBC to the in-cab computing device. Meanwhile,
`the OBC monitors for a disconnection of the in-cab comput
`ing device from the OBC. If such a disconnection is not
`detected as determined at decision block 604, the data con
`tinues to flow from the OBC to the in-cab computing device as
`shown at block 602. Otherwise, if it is detected 604 that the
`in-cab computing device has been disconnected, the OBC
`queues or otherwise buffers the data as shown at block 606.
`The data may be buffered in memory, cache, permanent Stor
`age or any other storage mechanism. In one embodiment, the
`data is buffered or queued in the order that the data occurred,
`so that the data can eventually be provided to the reconnected
`in-cab computing device in the order that it occurred.
`0040. When the in-cab computing device has been discon
`nected 604 and OBC data is being buffered 606, the OBC
`monitors for a reconnection of the in-cab computing device.
`If no such reconnection is detected 608, the OBC data con
`tinues to be queued. Otherwise, if a reconnection is detected
`608, one embodiment involves communicating all of the buff
`ered data to the reconnected in-cab computing device as
`shown at block 610. With the buffered data now provided to
`the in-cab computing device, the in-cab computing device can
`update 612 any information (e.g. driver's logs, etc.) with the
`buffered data.
`0041. It should be recognized that the in-cab computing
`device may alternatively or additionally notify the OBC when
`it is to be detected. For example, a user interface may enable
`a driver to indicate that the in-cab computing device is to be
`disconnected, which can trigger the data buffering by the
`OBC. It should also be recognized that detection of the con
`nection and/or reconnection of the in-cab computing device
`can be performed in any known fashion. For example, a
`grounded signal when connected can float to a different logic
`level when disconnected, and Such signal can be monitored by
`the processor on the OBC (or alternatively the in-cab com
`puting device) to detect when the in-cab computing device
`
`has been disconnected. Such a signal(s) can be continuously
`or periodically monitored, may trigger an interrupt, etc.
`0042. Thus, as noted by the example of FIG. 6, the in-cab
`computing device may be operated in different modes. One
`mode involves operation while the in-cab computing device
`202 is connected to the OBC, such as when mounted to the
`docking cradle in a truck. Another mode involves operation
`while the in-cab computing device is disconnected from the
`OBC and any docking cradle. In one embodiment, the system
`is designed such that the in-cab computing device is normally
`connected 600 to the OBC. While the vehicle is moving, data
`flows 602 from the OBC to the in-cab computing device, such
`as ECM data and the like. For example, data obtained by the
`OBC and/or provided by the OBC to the in-cab computing
`device may include GPS readings, odometer readings, RPM,
`speed, calculated miles per gallon (MPG) of fuel consumed,
`engine idle time, engine hours, door lock status, windshield
`wiper status, etc. The in-cab computing device uses this data
`in one or more applications, such as business rules Software to
`determine electronic log reporting for DOT reporting/com
`pliance, routing data, and numerous other reports that may be
`important to the dispatching office or other entity.
`0043. When the in-cab computing device is disconnected
`from the OBC, it is essentially operating in a portable mode.
`In this case, the data from the OBC containing positioning
`information and other vehicle data cannot be communicated
`to the in-cab computing device. This information may affect
`the accuracy of electronic log (e.g. eLog) reporting, accuracy
`of the dispatching information communicated back to the
`dispatch office, etc. Thus, as noted above, one embodiment
`involves detecting 604 when the in-cab computing device is
`disconnected from the OBC, and then directs the OBC to
`queue 606 (or otherwise temporarily hold/store) the vehicle
`data in its memory until, as determined at block 608, the
`in-cab computing device is reconnected to the OBC. At that
`point, the queued data is communicated 610 to the in-cab
`computing device from the OBC so that the in-cab computing
`device can update its rules Software and/or any other Software
`to reflect the current condition (e.g. Vehicle position, odom
`eter readings, etc.).
`0044 FIG. 7A is a block diagram illustrating various rep