EP2486549B1 - Transfer of tachograph related information - Google Patents

Transfer of tachograph related information Download PDF

Info

Publication number
EP2486549B1
EP2486549B1 EP10822314.0A EP10822314A EP2486549B1 EP 2486549 B1 EP2486549 B1 EP 2486549B1 EP 10822314 A EP10822314 A EP 10822314A EP 2486549 B1 EP2486549 B1 EP 2486549B1
Authority
EP
European Patent Office
Prior art keywords
vehicle
user account
tachograph
identity information
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP10822314.0A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2486549A4 (en
EP2486549A1 (en
Inventor
Christer Thorén
Patrik Nilsson
Mathias Björkman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Scania CV AB
Original Assignee
Scania CV AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Scania CV AB filed Critical Scania CV AB
Publication of EP2486549A1 publication Critical patent/EP2486549A1/en
Publication of EP2486549A4 publication Critical patent/EP2486549A4/en
Application granted granted Critical
Publication of EP2486549B1 publication Critical patent/EP2486549B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • G07C5/085—Registering performance data using electronic data carriers
    • G—PHYSICS
    • G08—SIGNALLING
    • G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
    • G08C17/00—Arrangements for transmitting signals characterised by the use of a wireless electrical link
    • G08C17/02—Arrangements for transmitting signals characterised by the use of a wireless electrical link using a radio link
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • G07C5/085—Registering performance data using electronic data carriers
    • G07C5/0858—Registering performance data using electronic data carriers wherein the data carrier is removable

Definitions

  • the present invention relates to a method for establishing a connection between a vehicle and a data base, as defined in the preamble of claim 1.
  • the present invention also relates to a system for establishing a connection between a vehicle and a data base, as defined in the preamble of claim 10.
  • the present invention also relates to a computer program and a computer program product implementing the method of the present invention.
  • a tachograph is a device combining the functions of a speedometer and a clock, generally recording the speed of the vehicle over time.
  • Analogue mechanical tachographs record the speed of the vehicle in every moment on a round piece of paper, which turns one full rotation in 24 hours. The speed is recorded by marking a distance from a rotation axis of the paper, where the distance is related to the speed of the vehicle.
  • Analogue tachographs have a problem in that they easily can be tampered with.
  • Digital tachographs have also been introduced, which are much more difficult to tamper with. Since year 2006, digital tachographs are mandatory in commercial vehicles in most European countries. See also WO 2006/008527 Also, it is mandatory to store the data being recorded by the digital tachographs in a safe place. The truck owner must also be able to retrieve and provide this stored data within a reasonable time duration to the authorities if they require access to this data.
  • FIG. 1 schematically shows a prior art system 100 for transfer of data being recorded by a digital tachograph (DTCO) 110, also called Vehicle Unit (VU), in a vehicle 101 to a database 150 external from the vehicle 101.
  • the DTCO 110 has a card reader 111, in which e.g. the driver card can be inserted, and records data when a driver card is inserted into a card reader 111 of the DTCO.
  • the driver card has normally been inserted when driving is performed, and data being recorded by the DTCO is then stored both in the DTCO and on the driver card.
  • the data stored in the VU 110 is to be transferred to a read-out unit 120 being connectable to the DTCO 110.
  • a company card should be inserted into the card reader 111 of the VU and the read-out unit 120 is connected to the VU. The data is then transferred to the read-out unit 120 and is stored there.
  • the read-out unit 120 is disconnected from the DTCO 110 and is physically brought to a location 102 being external from the vehicle 101.
  • the physical movement of the read-out unit 120 is here illustrated by the arrow 160, and is normally performed manually, such that a person disconnects the read-out unit 120 from the DTCO 110, and transports it to the external location 102.
  • the read-out unit 120 is connected to a stationary computer 130, which is connected to a DTCO service entity 140.
  • the DTCO service entity 140 is connected to the database 150.
  • the data can hereby be stored in the database 150 and can later be retrieved from the database 150 if requested by the authorities.
  • the data being stored on the driver card is normally transferred by physically bringing the driver card to the external location 102, inserting the driver card in a card reader 131, and storing the data in the data base 150.
  • the data on the driver card is normally not transferred when the driver card is still in the card reader 111 of the DTCO.
  • the data on the driver card can be transferred to the data base in other ways as well.
  • the prior art system 100 has a number of drawbacks, e.g. the need for manually performed connection of the read-out unit 120 to the DTCO 110, the manually performed physical movement of the read-out unit 120, and the manually performed connection of the read-out unit 120 to the stationary computer 130. All of these manually performed actions are time consuming, and are therefore also expensive. Also, the company card has to be put into the card reader 111 of the VU 110 when data stored in the VU is to be read out.
  • the present invention aims to provide a more flexible establishment of the connection and a more flexible transfer of tachograph related information than the transfer known in the background art.
  • the object is achieved by the above mentioned method for establishing a connection between a vehicle and a data base according to the characterizing portion of claim 1.
  • the object is also achieved by the above mentioned system for establishing a connection between a vehicle and a data base according to the characterizing portion of claim 10.
  • the establishment of a connection between a vehicle and a data base is characterized in that a vehicle identity information is used for determining a user account in a tachograph service entity, which is to be used for the transfer of connection establishment information.
  • the determined user account should be accessible by a remote user entity. Since at least the connection establishment information is then made available on said user account, the connection can be established and the transfer of tachograph related information to the data base from the vehicle can be achieved.
  • connection establishment information between a vehicle and a remote user entity can be performed regardless of where the remote user entity is located and regardless of where the vehicle is located, as long as the vehicle is within coverage of a wireless communication system providing a wireless connection, and the remote user entity has access to the Internet.
  • the solution according to the present invention is very easy to expand, since there is essentially no limitation of how many vehicles or company cards that can be handled by the system according to the solution.
  • a company owner can, if requested, essentially without delay, provide up to date tachograph related information for a vehicle to the authorities, even if the vehicle is very far away from the remote user entity, which is of course very time saving and appreciated by the authorities.
  • the tachograph service entity receives a vehicle identity information being associated with the vehicle together with at least one first message including connection establishment information. The tachograph service entity then provides the at least one first message and the vehicle identity information to the determined user account.
  • the remote user entity periodically accesses that user account, and if at least one first message and the vehicle identity information are present in that user account, the remote user entity retrieves them.
  • the at least one first message and the vehicle identity information are published on the user account, i.e. they are not sent to the remote user entity by the tachograph service entity.
  • the system therefore does not have to know the location of or the address to the remote user entity in order to transfer the tachograph related information to it, which reduces the complexity of the system dramatically.
  • FIG. 2 shows a system 200 according to the present invention for transfer of tachograph related information from a vehicle 201 to a data base 250.
  • a DTCO 210 records tachograph data when a driver card is inserted into its card reader 211.
  • the tachograph data is provided to a communicator entity 220, via a communication line 212.
  • the communication line 212 can have a standardized interface, and can include essentially any cable connection, wireless connection or bus connection, such a CAN-buss (Controller Area Network bus), a MOST-buss (Media Orientated Systems Transport bus), or the like.
  • the communicator entity 220 is, via antennas 221 and 241, in wireless connection 222 with a tachograph service entity 240.
  • the tachograph service entity 240 is connected to a database 250 arranged for storing tachograph related information.
  • the wireless connection 222 can utilize essentially any wireless communication technique being able to transfer the tachograph data, such as GPRS (General Packet Radio Service), 3GPP (3 rd Generation Partnership Project), LTE (Long Term Evolution), or the like.
  • GPRS General Packet Radio Service
  • 3GPP 3 rd Generation Partnership Project
  • LTE Long Term Evolution
  • the system 200 also includes a remote user entity 260, which comprises a processing unit 261, such as a Personal Computer (PC), and a card reader 262.
  • the card reader 262 can be included in the processing unit 261, or can be external from the processing unit 261, and is arranged to receive a company card 263.
  • the remote user entity 260 is connected to the tachograph service entity 240 via an Internet connection 264, which can be a wire line connection or a wireless Internet connection.
  • the present invention establishes a connection between the DTCO 210 in the vehicle 201 and the data base 250, such that tachograph related information can be transferred between them in a secure and safe way.
  • tachograph related information can be transferred between them in a secure and safe way.
  • only the DTCO owner, or at least a person having a company card should be able to unlock the DTCO 210 and retrieve tachograph related information from the DTCO 210.
  • the tachograph related information in the DTCO should be accessible and be possible to store in the data base 250.
  • connection establishment information has to be exchanged between the DTCO and the company card 263 in the remote user entity 260.
  • the connection establishment information can include essentially any type of information being useful for unlocking the DTCO, such as one or more identification parameters, one or more handshake parameters, one or more signaling keys, or the like.
  • the remote user entity 260 of the system of the present invention should be able to have a flexible location.
  • the exchange of the connection establishment information between the DTCO in the vehicle 201 and the remote user entity 260 can be very complicated, especially if the vehicle 201 is not aware of the exact location of the remote user entity 260, and thus of the exact location of the company card 263.
  • a vehicle identity information is used for determining a user account in the tachograph service entity 240.
  • This user account is accessible by the remote user entity 260.
  • a user account in the tachograph service entity 240 is chosen.
  • the connection establishment information is made available on this chosen account, which is accessible by the remote user entity 260.
  • connection establishment information including information needed for unlocking the DTCO 210 becomes accessible for the remote user entity 260, and exchange of connection establishment information between the DTCO 210 in the vehicle 201 and the company card 263 in the remote user entity 260 is possible.
  • the connection between the DTCO 210 and the data base 250 can then be set up by this exchange of connection establishment information.
  • the solution according to the present invention has an advantage in that it offers total flexibility for the location of the remote user entity 260.
  • the DTCO 210, and also the tachograph service entity 240 do not have to know where the remote user entity 260 is physically located in order to exchange connection establishment information between the DTCO 210 in the vehicle 201 and the remote user identity 260 in order to establish a connection between the vehicle 201 and the data base 250.
  • a company owner, or a person having a company card can, essentially anywhere in the world, retrieve connection establishment information, which makes it possible to establish the connection between the DTCO 210 in a vehicle being located essentially anywhere in the world and the data base 250.
  • the tachograph related information being stored in the database 250 will thus be up to date and can also be accessible anywhere if requested e.g. by the authorities.
  • the vehicle identity information includes a vehicle identification number (VIN).
  • VIN vehicle identification number
  • This VIN can be based on information being provided via the wireless connection 222, or can be based on parameters being related to the wireless connection 222 itself, such as a telephone number or the like being used by the communicator entity 220 when establishing the wireless connection 222.
  • the tachograph service entity 240 determines the user account to be used for the connection establishment information exchange by determining a company being associated with the vehicle identity information, and then subsequently determining a user account being associated with the determined company.
  • the tachograph service entity 240 here includes two tables. One of these tables includes relationships between at least one vehicle identity information (1-10) and at least one company (A-C). A schematic example of such a table illustrated by Table 1 below. Table 1 VIN Company 1 A 2 A 3 A 4 B 5 B 6 B 7 B 8 B 9 C 10 C ⁇ ⁇
  • the other one of these two tables includes relationships between at least one company (A-C) and at least one user account (UA 1 - UA 3).
  • a schematic example of such a table is illustrated by Table 2 below.
  • the tachograph service entity 240 determines the user account to be used by directly determining a user account being associated with said vehicle identity information.
  • the tachograph service entity 240 here includes one table, which lowers the implementation complexity.
  • the table includes relationships between at least one vehicle identity information (1-10) and at least one user account (UA 1 - UA 10).
  • a schematic example of such a table is illustrated by Table 3 below.
  • Table 3 VIN User Account 1 UA 1 2 UA 2 3 UA 2 4 UA 4 5 UA 5 6 UA 6 7 UA 7 8 UA 8 9 UA 9 10 UA 10 ⁇ ⁇
  • these tables can be designed in a large number of ways, and the above disclosed tables are only examples of such designs.
  • the determination of the user account to be used can be performed in a number of ways, utilizing a number of different tables of information.
  • a table can also be used, which includes relationships between at lease one vehicle identification number (VIN) and at least one telephone number being used by the communicator entity 220 when establishing the wireless connection 222.
  • VIN vehicle identification number
  • the VIN can be retrieved, which can be used for determining a company and/or a user account by the use of one or more of the above disclosed tables.
  • the tachograph service entity 240 receives, from the vehicle 201, a vehicle identity information being associated with the vehicle 201 together with at least one first message including connection establishment information. The tachograph service entity 240 then provides the at least one first message and the vehicle identity information to the user account being determined by utilizing the vehicle identity information.
  • connection establishment information and the vehicle identity information originating from the vehicle 201 are made available on the chosen user account of the tachograph service entity, irrespectively of the location of the vehicle.
  • the remote user entity 260 periodically accesses the user account, which is determined to be used for the transfer of the connection establishment information. Periodically here means that the user account is accessed at suitable intervals, where the intervals can have equal, different, or varying time durations. If at least one first message and the vehicle identity information are present in that user account, the remote user entity 260 retrieves the at least one first message and the vehicle identity information from that user account.
  • the at least one first message and the vehicle identity information are here not pushed to the remote user entity 260. Instead, they are only made available, i.e. are only published, on the user account. It is then up to the remote user entity 260 to access the user account and retrieve the at least on first message and the vehicle identity information.
  • This has an advantage in that the system does not have to know where the remote user entity 260 is physically located or imaginary located, e.g. at which IP address, since it does not have to transmit the at least one first message and the vehicle identity information to that location or IP address.
  • the only setting up that has to be made is that the remote user entity 260 should be set to find the right user account to access, i.e.
  • the remote user entity 260 must be able to find the user account being chosen to be used for transfer of the connection establishment information. To set this up in the remote user entity is very easily and cost effectively achieved, and after that the remote user entity 260 can be connected to the Internet essentially anywhere and is able to retrieve the tachograph related information.
  • the system and the method for establishing the connection for transfer of tachograph related information between the vehicle 201 and the database 250 is very robust, since the at least one first message and the vehicle identity information are stored, i.e. buffered, on that user account until the remote user entity 260 retrieves them.
  • the at least one first message and the vehicle identity information will be stored on the user account for the PC 261 to retrieve once the PC 261 is turned on again or once the Internet connection 264 works again.
  • the remote user entity 260 when the least one first message and the vehicle identity information have been retrieved by the remote user entity 260, the remote user entity 260 returns at least one second message and the vehicle identification information to the user account in the tachograph service entity 240 being used for exchange of the connection establishment information.
  • This at least one second message includes information being used for unlocking the DTCO, such as one or more identification parameters, one or more handshake parameters, one or more signaling keys, or the like.
  • the at least one first message and the at least second message include one or more signalling keys or the like, that are exchanged between the DTCO 210 and the remote user entity 260.
  • This exchange results in that the DTCO 210 is unlocked and in than the connection between the DTCO 210 in the vehicle 201 and the data base 250 is established.
  • the tachograph related information is transferred from the DTCO 210 to the data base 250, and is stored in the data base 250.
  • the connection establishment information has been exchanged between the DTCO 210 and the remote user entity 260, i.e. once the DTCO has been unlocked
  • the tachograph related information is stored in the data base 250 by a transfer of the tachograph related information via the wireless connection 222 and the tachograph service entity 240 to the data base 250.
  • the tachograph service entity 240 Since the vehicle identity information is returned from the remote user entity 260 and provided to the user account, the tachograph service entity 240 is made aware of that an exchange of connection establishment information between that specific vehicle and that specific remote user entity 260 is performed. The tachograph service entity then knows that it should keep on providing connection establishment information intended for that remote user entity on the user account until the connection between the DTCO 210 and the data base 250 has been established.
  • more than one company cards 263 can be connected to the PC 261. These company cards may be associated with different companies and/or with different vehicles. Also, more that one remote user entity 260 may be used in the system. Thus, since the connection establishment information is only made available on the user account, i.e. is not transmitted, and since the vehicle identity information is also utilized and included in information transfer both to and from the remote user entity, full flexibility is achieved by this embodiment of the invention.
  • the tachograph service entity 240 provides the at least one second message and the vehicle identification information from the user account to the DTCO 210 in the vehicle 201, whereby the exchange of the connection establishment information is achieved.
  • FIG. 3 shows a flow chart diagram for the method of the present invention.
  • a vehicle identity information is utilized for determining the user account in a tachograph service entity 240 to be used for transfer of connection establishment information.
  • this user account should be accessible by a the remote user entity 260.
  • at least the connection establishment information is made available on the user account having been determined to be used for performing the establishment of the connection between the DTCO 210 in the vehicle 201 to the data base 250.
  • the present invention can be implemented by the use of one or more processing units, where each one of these one or more processing units can be of essentially any type of processor, such as a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • Such a processing unit is connected to a memory entity, storing program code, results from the calculations of the processing units, and the like.
  • one or more of the DTCO 210, the communicator entity 220, the tachograph service entity 240, and the remote user entity 260 can include such a processing unit for implementing the method of the invention.
  • the method of the present invention can implemented by the use of a computer program, having code means, which when run in a computer causes the computer to execute the steps of the method.
  • the computer program is included in a computer readable medium of a computer program product.
  • the computer readable medium may consist of essentially any memory, such as a ROM (Read-Only Memory), a PROM (Programmable Read-Only Memory), an EPROM (Erasable PROM), a Flash memory, an EEPROM (Electrically Erasable PROM), or a hard disk drive.
  • a system 200 includes a tachograph service entity 240, which includes a number of user accounts.
  • the tachograph service entity 240 is arranged to utilize a vehicle identity information for determining a user account to be used for transfer of connection establishment information.
  • the system 200 is arranged for making at least the connection establishment information available on that user account.
  • the user account is accessible by the remote user entity 260.
  • the tachograph service entity of the system 200 includes at least one of Table 1, Table 2, and Table 3 above.
  • the system 200 of the present invention can be arranged to perform all the steps of the above described methods of the invention. Also, as is obvious for a skilled person, a number of other implementations, modifications, variations and/or additions can be made to the above described exemplary embodiments. It is to be understood that the invention includes all such other implementations, modifications, variations and/or additions which fall within the scope of the claims.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Traffic Control Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
EP10822314.0A 2009-10-06 2010-09-22 Transfer of tachograph related information Active EP2486549B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SE0950733A SE534787C2 (sv) 2009-10-06 2009-10-06 Överföring av färdskrivarrelaterad information
PCT/SE2010/051017 WO2011043715A1 (en) 2009-10-06 2010-09-22 Transfer of tachograph related information

Publications (3)

Publication Number Publication Date
EP2486549A1 EP2486549A1 (en) 2012-08-15
EP2486549A4 EP2486549A4 (en) 2013-08-07
EP2486549B1 true EP2486549B1 (en) 2015-07-29

Family

ID=43856997

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10822314.0A Active EP2486549B1 (en) 2009-10-06 2010-09-22 Transfer of tachograph related information

Country Status (7)

Country Link
EP (1) EP2486549B1 (pt)
CN (1) CN102576474A (pt)
BR (1) BR112012004449A2 (pt)
IN (1) IN2012DN01595A (pt)
RU (1) RU2495495C1 (pt)
SE (1) SE534787C2 (pt)
WO (1) WO2011043715A1 (pt)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9922001B2 (en) 2012-05-10 2018-03-20 Omnitracs, Llc Off-board hours-of-service (“HOS”) processing
SE536934C2 (sv) * 2013-02-15 2014-11-04 Scania Cv Ab Metod och arrangemang i samband med utläsning av förarkort
EP3827419A4 (en) * 2018-07-26 2022-04-27 Takosan Otomobil Gostergeleri Sanayi ve Ticaret A.S. MONITORING, CONTROL AND REPORTING OF DRIVER ACTIONS BY AUTOMATIC TRAFFIC RULES FOLLOW-UP
EP4283423A1 (en) * 2022-05-24 2023-11-29 Volvo Truck Corporation A computer-implemented method and a system for providing recommendation data associated to a vehicle

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6317668B1 (en) * 1999-06-10 2001-11-13 Qualcomm Incorporated Paperless log system and method
FR2803677B1 (fr) * 2000-01-07 2002-06-21 Gen Trailers France Dispositif de controle d'un vehicule routier et systeme electronique embarque comprenant un tel dispositif
US20020111725A1 (en) * 2000-07-17 2002-08-15 Burge John R. Method and apparatus for risk-related use of vehicle communication system data
US20050060070A1 (en) * 2000-08-18 2005-03-17 Nnt, Inc. Wireless communication framework
ES2382994T3 (es) * 2001-06-20 2012-06-15 Siemens Aktiengesellschaft Procedimiento para registrar datos de un tacógrafo de un vehículo mediante un sistema de comunicaciones por radio
US20040064247A1 (en) * 2002-09-26 2004-04-01 Davis Christopher E. Method and system for remotely managing vehicle mileage
US8041779B2 (en) * 2003-12-15 2011-10-18 Honda Motor Co., Ltd. Method and system for facilitating the exchange of information between a vehicle and a remote location
GB2416421B (en) 2004-07-20 2008-09-10 Francis John Steele The universal satellite key (USK)
GB0422921D0 (en) * 2004-10-15 2004-11-17 Clark David Apparatus and method for monitoring the usage status of an asset
RU2298494C1 (ru) * 2006-07-10 2007-05-10 Общество с ограниченной ответственностью "АЛЬТОНИКА" (ООО "АЛЬТОНИКА") Система контроля состояния транспортного средства и оповещения
US20080238690A1 (en) * 2007-03-30 2008-10-02 International Business Machines Corporation Driver and registration identification for vehicle enablement
US9129460B2 (en) * 2007-06-25 2015-09-08 Inthinc Technology Solutions, Inc. System and method for monitoring and improving driver behavior
RU69661U1 (ru) * 2007-08-14 2007-12-27 Юрий Николаевич Кручинкин Система удаленного доступа по принятию решений по анализу и оценке дорожно-транспортного происшествия
DE102008025065A1 (de) * 2007-12-21 2009-07-02 Continental Automotive Gmbh Verfahren und System zur Übertragung von Daten
DE102007062960A1 (de) * 2007-12-21 2009-06-25 Continental Automotive Gmbh Kommunikationssteuergerät und Verfahren zur Durchführung einer Übertragung von Daten

Also Published As

Publication number Publication date
WO2011043715A1 (en) 2011-04-14
EP2486549A4 (en) 2013-08-07
BR112012004449A2 (pt) 2016-03-22
CN102576474A (zh) 2012-07-11
EP2486549A1 (en) 2012-08-15
RU2495495C1 (ru) 2013-10-10
SE0950733A1 (sv) 2011-04-07
IN2012DN01595A (pt) 2015-06-05
SE534787C2 (sv) 2011-12-20

Similar Documents

Publication Publication Date Title
US20180165247A1 (en) Off-board hours-of-service ("hos") processing
US9710975B2 (en) Rental/car-share vehicle access and management system and method
CN1260687C (zh) 用于碰撞信息的自动传输的方法与装置
US10586292B2 (en) Vehicle information collection system and module therefor
EP2486549B1 (en) Transfer of tachograph related information
CN104925005A (zh) 一种车辆监控方法及装置
CN1971656A (zh) 一种能对机动车和驾驶员进行可靠管理的电子检测系统
WO2004029774A2 (en) Vehicle monitoring and reporting system
CN111295862A (zh) 用于密码地保证车辆身份的系统和方法
CN101681554A (zh) 车辆违章执法系统和方法
CN105139504A (zh) 车辆智能管理装置及方法
CN102054357A (zh) 一种基于无线射频识别的车辆监控系统及方法
CN103198667A (zh) 高速公路车速监测系统
JP2008258740A (ja) 車載用監視記録システム、映像蓄積装置、鍵保管装置、および車載用監視レコーダ
ES2356326T3 (es) Procedimiento para la transferencia de datos desde un tacógrafo.
CN104331948B (zh) 行驶记录仪升级信息发送方法、接收方法、装置及系统
EP3109835B1 (de) Verfahren und system zur fahr- und fahrerdatenerfassung
US20100305808A1 (en) Method and System for Transmitting Data
JP2017054423A (ja) 車両用運行情報記録装置
KR101479725B1 (ko) 운행기록 분석콘텐츠 제공 방법
CN205541468U (zh) 智能公交系统
CN111246434A (zh) 一种用于确定车载单元的安全状态的方法及系统
JP4362000B2 (ja) 通信システム、通信装置及び通信方法並びに通信用ソフトウェアを記録した記録媒体
CN110689237A (zh) 一种车辆管理人员的管理方法及其相关产品
CN111976651A (zh) 用车管理方法、用车管理服务器及用车管理终端

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20120507

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20130708

RIC1 Information provided on ipc code assigned before grant

Ipc: G07C 5/00 20060101AFI20130702BHEP

Ipc: G08C 17/02 20060101ALI20130702BHEP

Ipc: G08G 1/00 20060101ALI20130702BHEP

Ipc: B60R 25/102 20130101ALI20130702BHEP

17Q First examination report despatched

Effective date: 20140704

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602010026336

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G07C0005000000

Ipc: G07C0005080000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: G08G 1/00 20060101ALI20150304BHEP

Ipc: G07C 5/08 20060101AFI20150304BHEP

Ipc: G07C 5/00 20060101ALI20150304BHEP

INTG Intention to grant announced

Effective date: 20150327

RIN1 Information on inventor provided before grant (corrected)

Inventor name: THOREN, CHRISTER

Inventor name: BJOERKMAN, MATHIAS

Inventor name: NILSSON, PATRIK

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 739829

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150815

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010026336

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 739829

Country of ref document: AT

Kind code of ref document: T

Effective date: 20150729

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20150729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151030

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151029

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151130

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20151129

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: LU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150922

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010026336

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

26N No opposition filed

Effective date: 20160502

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150922

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150930

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150930

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20100922

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150729

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230518

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230803

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230808

Year of fee payment: 14

Ref country code: DE

Payment date: 20230802

Year of fee payment: 14