Patent Description:
Today, transportation by vehicle requires measurement of parameters and information relating to the driver activities. This is not exclusively done to satisfy regulations regarding road transportation, but also for fleet management to measure and increase performance and efficiency, as well as for the purpose of electronic road tolling, monitoring vehicle or engine performance parameters, monitoring data relevant for special transports e.g. dangerous goods, livestock or refrigerated food etc. Therefore, most vehicles, such as lorry trucks, carry a Vehicle Unit (VU) to measure, store and possible also report the collected data. In this document, the term "Vehicle Unit" shall mean a digital unit capable of gathering information relating to the vehicle. Examples of such information may be a geographical location, driving hours, distance traveled, start time, finish time, rest time, driver name, starting location and finishing location, exhaust measurements, fuel consumption, temperature data from vehicle or cargo sensors, opening and closing of cargo doors or operation of other vehicle systems, e.g. cranes and lifts etc. One example of a VU is a digital tachograph, capable of recording and digitally compiling and storing the vehicle data.

The VU is normally located in the cabin of the vehicle, where the VU is arranged in the instrument board, so that the vehicle operator may operate the VU in adjacency to start or stop of a journey. In order to calculate and estimate the speed and the travel distance, or other parameters for instance as listed above, of the vehicle, the VU is in connectivity to one or more sensors, where the sensors are capable of measuring for instance the motion of the wheels or other parameters.

Legislation stipulates that the vehicle operator, i.e. the driver, owns a driver card which is inserted into the VU in order to record his/her activities during operation of the vehicle. Further, legislation requires that the driver cards are downloaded by the fleet company/fleet management on a regular basis. In order to ensure compliance with EC561/<NUM>, the fleet company needs to have control of the downloads of the driver cards.

In prior art solutions it is known to download driver cards on a regular basis, such as e.g. every <NUM> days, by connection between the VU and an external server via e.g. a telematics unit having a built-in GSM/GPRS mode which keeps track of when it is time to read out or download the driver card. In other solutions the data stored within the driver card is uploaded or offloaded via a remote downloading device, such as e.g. a "dongle" and further to a remote server by connecting the remote downloading device to the VU or to a separate card reader. Such uploading of data may first be preceded by a check of server data if the driver data is to be downloaded.

However, there is an increasing number of drivers working temporary and/or irregular shifts or periods in multiple vehicles. For example, one driver may be employed by different companies in different countries with varying regularity. It is possible that the driver does not return to the same fleet company for an extended period of time. As a result, the fixed interval of downloading driver cards is not sufficient for ensuring that the fleet company/fleet management is in possession of updated records of all driver activities at any given time.

Document <CIT> discloses an assembly comprising a tachograph, while document <CIT> discloses a personnel activity recording terminal.

A drawback with the known art is that the latest activities of the driver during operation of the vehicle will not be downloaded. This has the effect that fleet companies will not be in control of driver data that is up to date. As a result, a further effect may be that the company in question is not able to provide an accurate accounting of the data, which may lead to the required payment of costly penalty charges.

It is an object of the invention to address at least some of the limitations, problems and issues outlined above. It is also an object to provide a solution for enabling download of a user data device to a Vehicle Unit, VU, wherein the latest activities of the driver will be downloaded. It may be possible to achieve these objects and others by using a Vehicle Unit, a method, a computer program and a computer program product according to the invention as defined in the attached independent claims.

In the following, a detailed description of the invention will be given:.

<FIG> illustrates a perspective view of a Vehicle Unit, VU, <NUM>, such as e.g. a tachograph <NUM>, for measuring, processing, storing or reporting collected vehicle data. The outer design and form factor of the Vehicle Unit <NUM> complies with standards in the field of tachographs such as e.g. ISO <NUM>. The front end <NUM> of the Vehicle Unit <NUM> comprises an access panel <NUM> being in a closed position, i.e. wherein the access panel is closed, thereby covering a space <NUM> for housing a printer, preferably a removable printer module <NUM>. The Vehicle Unit <NUM> further comprises a display <NUM>, a first user data device port <NUM> and a second user data device port <NUM>', and a first side end <NUM>' to disclose the depth of the Vehicle Unit <NUM> in a direction perpendicular to the front side <NUM>. According to one embodiment, the user data device ports <NUM>, <NUM>' are card slots adapted to receive user data devices <NUM>, <NUM>' adapted to comprise stored user data. A first user data device <NUM> and a second user data device <NUM>' are further disclosed in <FIG>. According to one embodiment, the user data devices <NUM>, <NUM>' are so called driver cards. Eject or release buttons <NUM>, <NUM>' for ejecting/releasing of the respective user data device <NUM>, <NUM>' upon pressing or touching said eject buttons <NUM>, <NUM>' are further shown in <FIG>. The Vehicle Unit <NUM> comprises a vehicle unit downloading system <NUM> or node for enabling downloading of user data of an external user data device <NUM>, <NUM>'.

<FIG> illustrates a side view of a vehicle <NUM> comprising a Vehicle Unit <NUM> and/or a vehicle unit downloading node <NUM>. According to one embodiment, the vehicle unit downloading system <NUM> comprises one of e.g. the following: a digital tachograph, a TEM (Telematics Module), a CEM (Central Electronics Module) or an ECU (Electronic Control Module). According to one embodiment, the vehicle unit <NUM> further comprises a user data device eject system <NUM> or node which enables the ejecting of the user data device <NUM>, <NUM>'. <FIG> further shows a computer environment <NUM> comprising a remote node <NUM>.

According to one embodiment, the Vehicle Unit <NUM> is or comprises a downloading tool, or so called IDE (intelligent dedicated equipment) i.e. adapted to connect remotely to external remote nodes <NUM>, e.g. remote servers. According to one embodiment, a remote node <NUM> comprises a so called company card or company smart card of a fleet company.

According to one non-claimed embodiment, downloading comprises the process of receiving data from a remote node or system so that data may be further processed, used or stored locally, for instance in a Vehicle Unit <NUM>. According to the invention, downloading comprises the process of downloading data from a user data device, to a Vehicle Unit <NUM>. According to one embodiment, uploading comprises the process of sending or transmitting data to e.g. a remote node <NUM> or system such as a remote server or any other client, so that the data can be further processed, used, or stored in the remote node or system. According to one embodiment, the data may be uploaded to a remode node <NUM> or system, such as a remote server or any other client, simultaneously as being downloaded from a user data device without requiring an intermediate storing of the data, e.g. storing in the Vehicle Unit <NUM>.

According to one embodiment, user data comprises user activities carried out during operation of the vehicle, such as e.g. driving or resting time, availability and other work. According to one embodiment, user data comprises user identification data for identifying the driver.

A procedure or method in a vehicle unit downloading system <NUM> for enabling downloading of the latest user data of a user data device <NUM>, <NUM>', as seen in <FIG>, will now be described with reference to <FIG>. In a first step S100, an eject request signal is received. According to one embodiment, the eject request signal is generated by an ejecting request by an operator of the vehicle <NUM> to eject the user data device <NUM>, <NUM>' from the user data device port <NUM>, <NUM>' wherein the user data device <NUM>, <NUM>' is received during operation of the vehicle <NUM>. According to one embodiment, the pressing of an eject button <NUM>, <NUM>' or eject area or release button generates such eject request signal. According to one embodiment, the eject request signal is received from the user data device eject system <NUM>. In a further step S110 the vehicle unit downloading system <NUM> requests downloading of user data from the user data device <NUM>, <NUM>'. According to one embodiment, the vehicle unit downloading system checks whether the card has been entered in to the user data device port <NUM>, <NUM>' at least a plurality of times within a certain time frame, and wherein the vehicle unit downloading system <NUM> does not request downloading of user data from the user data device <NUM>, <NUM>' if this is the case. According to one embodiment, the plurality of times is four times during a period of a week or work week or seven days. According to this embodiment, the Vehicle Unit <NUM> recognizes a user which is an employee and thus a recurring driver and user of the vehicle. In such cases, and upon the setting of the Vehicle Unit <NUM>, the inactivation of the release of the user data device <NUM>, <NUM>' may be removed since the user data will be collected anyway. According to one embodiment the downloaded user data is stored in a memory <NUM> of the vehicle unit downloading system <NUM>. According to one embodiment, the downloaded user data is stored in a memory <NUM> of the remote node <NUM>. According to one embodiment, the downloaded user data is stored in the memory <NUM> of the remote node <NUM> without being stored in, or stored in an intermediate manner, in the memory <NUM> of the vehicle unit downloading system <NUM>. According to one embodiment, the downloaded user data is stored in the memory <NUM> of the remote node <NUM> without being stored in, or stored in an intermediate manner, in the memory <NUM> of the vehicle unit downloading system <NUM>, but where user data is stored in an intermediate manner in a separate remote download tool connected to the Vehicle Unit <NUM>. According to one embodiment, in a next possible step S120, the vehicle unit download system receives a download finalized signal when the downloading of the user data of the user date device has been completed. According to one embodiment, the downloading of the user data is completed when the last activity prior to the eject signal is received has been downloaded. In a further step S130, a user data device releasing signal is transmitted to enable an ejecting of the user data device <NUM>, <NUM>'. According to one embodiment, the vehicle unit downloading system <NUM>, or user data device eject system <NUM> is arranged to prevent release of user data device <NUM>, <NUM>', e.g. by an activated means for preventing release or withdrawal and thus further ejecting the user data device <NUM>, <NUM>', until the user data has been downloaded and a releasing signal enables a release of the user data device <NUM>, <NUM>'. According to one embodiment, the user data device eject system <NUM> comprises an electrical control means for activating and inactivating the release of use data device <NUM>, <NUM>'. According to one embodiment, a mechanical locking of the user data device <NUM>, <NUM>' is activated or inactivated for preventing and allowing the release of, and further ejecting, the user data device <NUM>, <NUM>' respectively. According to one embodiment, the user data device release signal is transmitted after downloading of the user data. According to one embodiment, the download finalized signal is received before transmitting the user data device releasing signal. According to one embodiment, the user data device release signal is transmitted to a user data device eject system <NUM> or node which enables the ejecting of the user data device <NUM>, <NUM>'. In a further step S140, as seen in <FIG>, the vehicle unit download system requests uploading of user data to a remote node <NUM>. According to one embodiment, the remote node <NUM> is a remote server or remote back end server. According to one embodiment, the back end server comprises a fleet management system. According to one embodiment, such uploading is carried out when the card is ejected from the user data device port <NUM>, <NUM>'. In a further step, S150, user data is transmitted to the remote node <NUM>. According to one embodiment, the user data is transmitted to the remote node <NUM> upon establishing a valid connection to the remote node <NUM>. According to one embodiment, a valid connection to a remote node <NUM>, is an existing connection enabling a communication, such as e.g. an uploading of user data, between the vehicle unit downloading system and the remote node <NUM>. According to one embodiment, a valid connection is an existing connection enabling the authentication of a remote node <NUM> such as company card.

According to one embodiment, in a further intermediate step S101, as seen in <FIG>, the vehicle unit downloading system <NUM> transmits user identification data. According to one embodiment, the user identification data defines the user/operator of the vehicle but also the user data device <NUM>, <NUM>'. According to one embodiment, user data comprises user identification data. According to one embodiment, the user identification data is transmitted to a remote node <NUM> or server, e.g. a back end server at a fleet company, wherein data concerning the download status of a particular user is stored. In a next step S102, a download instruction is received. According to one embodiment, the download instruction is generated by the remote node <NUM>. The remote node <NUM> determines whether download of the user data device is required or not, by comparing user identification data received from the vehicle unit download system with stored data concerning the latest downloading date for the particular user and application of predefined rules. According to one embodiment, such stored data is downloading history data. Hence, the download instruction may be an instruction to download the user data of the user data device <NUM>, <NUM>', but may also be to not download the user data of the user data device <NUM>, <NUM>'. According to one embodiment, such predefined rules may be legal rules relating to downloading of user data, e.g. downloading every <NUM> days. According to one embodiment, predefined rules may define that download should be carried out at more frequent intervals than <NUM> days, or that downloads should be carried out for all new drivers operating a fleet company's vehicle <NUM> for the first time. According to one embodiment, steps S101 and S102 are carried out after step S100 and before step S110.

In a further intermediate step, S105, as seen in <FIG>, the vehicle unit downloading system <NUM> requests remote node connectivity status data. According to one embodiment, the request is sent to a vehicle unit internal remote downloading tool (IDE). According to one embodiment, the request is sent to a separate and external remote downloading tool connected to the Vehicle Unit <NUM>. In a next step S106 a remote node connectivity status data is received. In a further step S107, the vehicle unit downloading system <NUM> determines whether the remote node connectivity status data indicates a connection to a remote node. According to one embodiment, the vehicle unit downloading system <NUM> determines whether the remote node connectivity status data indicates a valid connection to a remote node. In a further step S110 the vehicle unit downloading system <NUM> requests downloading of user data from the user data device <NUM>, <NUM>' based on the received remote node connectivity status data. Hence, according to one embodiment, the steps S105-S107 are carried out after step S100. According to the invention, the vehicle unit downloading system <NUM> requests downloading of user data from the user data device <NUM>, <NUM>' if the remote node connectivity status indicates a non-existing connection to a remote node <NUM>.

<FIG> discloses a vehicle unit downloading system <NUM> for enabling downloading of user data of an external user data device <NUM>, <NUM>'. The system <NUM> is arranged to receive an eject request signal by a communication unit <NUM>. The system <NUM> is further arranged to request downloading of user data from a user data device <NUM>, <NUM>' based on the received eject request signal by a controller <NUM>. According to one embodiment, the downloaded user data is stored in a memory device <NUM> of the vehicle unit downloading system <NUM>. According to one embodiment, the user data is stored in the memory device <NUM> as a ddd file format. According to other embodiments, the user data file is in a esm, tgd, add format. The communication unit <NUM> is arranged to receive a download finalized signal. The communication unit <NUM> is further arranged to transmit a user data device releasing signal upon receiving the download finalized signal. According to one embodiment, the controller <NUM> is thereafter arranged to request uploading of user data to a remote node <NUM>. An externa remote node communication unit <NUM>, such as e.g. a communication interface, is arranged to transmit user data to a remote node <NUM>. According to one embodiment, the external remote node communication unit <NUM> is arranged to transmit user identification data. The external remote node communication unit <NUM> is thereafter arranged to receive a download instruction. The controller <NUM> is further arranged to request a remote node connectivity status data. The external remote node communication unit <NUM> is arranged to receive remote node connectivity status data. According to one embodiment, a determination unit <NUM> is arranged to determine whether the remote node connectivity status data indicates an existing connection to a remote node <NUM>.

<FIG> shows an illustration of embodiments of a vehicle unit downloading system <NUM>. The vehicle unit downloading system <NUM> may be implemented, by means of program modules of a respective computer program comprising code means which, when run by a processing unit <NUM> causes the vehicle unit downloading system <NUM> to perform the above-described actions. The processing unit <NUM> may comprise a single Central Processing Unit (CPU), or could comprise two or more processing units. For example, the processing unit <NUM> may include general purpose microprocessors, instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuits (ASICs). The processing unit <NUM> may also comprise a storage for caching purposes.

Each computer program may be carried by a computer program product <NUM> in the vehicle unit downloading system <NUM>, shown in <FIG>, <FIG>, <FIG>, <FIG>, et al, in the form of a memory having a computer readable medium and being connected to the processing unit <NUM>. The computer program product <NUM> or memory thus comprises a computer readable medium on which the computer program is stored e.g. in the form of computer program modules "m". For example, the memory <NUM> may be a flash memory, a Random-Access Memory (RAM), a Read-Only Memory (ROM) or an Electrically Erasable Programmable ROM (EEPROM), and the program modules m could in alternative embodiments be distributed on different computer program products in the form of memories within the vehicle unit downloading system <NUM>.

The vehicle unit downloading system <NUM> may further comprise a communication interface <NUM>. The communication interface <NUM> may be arranged to communicate with for example sensor unit <NUM> e.g. sensing the presence of a user data device being received in the user data port <NUM>, <NUM>', or the pressing of the eject button <NUM>, <NUM>'. In an embodiment the communication interface <NUM> may comprise chip set adopted for communication via CAN bus (Controller Area Network) or communication adopted to ISO <NUM>. Other examples of standards which may be supported by the communication interface 265are: ZigBee, Bluetooth, RFID (Radio frequency identification), USB (Universal serial bus), or IEEE <NUM>(Institute of Electrical and Electronics Engineers), including but not limited to <NUM>. 11a/b/n or other similar forthcoming standards. The communication interface <NUM> may comprise an antenna. The communication interface <NUM> may be connectable to an external antenna. The vehicle unit downloading system <NUM> may further comprise one or more storage units <NUM> and further functionality <NUM> useful for the vehicle unit downloading system <NUM> to serve its purpose as vehicle unit downloading system, such as power supply, internal communications bus, internal cooling, database engine, operating system, not limiting to other functional ities.

Claim 1:
A Vehicle Unit (<NUM>), comprising a user data device port (<NUM>, <NUM>') for receiving a user data device (<NUM>, <NUM>') comprising user data,
wherein the Vehicle Unit (<NUM>) is arranged to determine a remote node connectivity status, wherein the Vehicle Unit (<NUM>) is arranged to download user data from the user data device (<NUM>, <NUM>') based on an ejecting request to eject the user data device (<NUM>, <NUM>') from the user data device port (<NUM>, <NUM>') and wherein the Vehicle Unit (<NUM>) is further arranged to download user data of the user data device if the remote node connectivity status indicates a non-existing connection to a remote node (<NUM>), wherein the Vehicle Unit (<NUM>) is further arranged to enable releasing of the user data device (<NUM>, <NUM>') after downloading of user data from the user data device (<NUM>, <NUM>'), whereby the user data device (<NUM>, <NUM>') may be ejected.