EP1870302A1 - Personnalisation à distance d'une unité embarquée - Google Patents

Personnalisation à distance d'une unité embarquée Download PDF

Info

Publication number
EP1870302A1
EP1870302A1 EP06012769A EP06012769A EP1870302A1 EP 1870302 A1 EP1870302 A1 EP 1870302A1 EP 06012769 A EP06012769 A EP 06012769A EP 06012769 A EP06012769 A EP 06012769A EP 1870302 A1 EP1870302 A1 EP 1870302A1
Authority
EP
European Patent Office
Prior art keywords
personalization
board unit
obu
data
relevant data
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.)
Withdrawn
Application number
EP06012769A
Other languages
German (de)
English (en)
Inventor
Peter Selmayr
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.)
Ages International & Co KG GmbH
Original Assignee
Ages International & Co KG GmbH
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 Ages International & Co KG GmbH filed Critical Ages International & Co KG GmbH
Priority to EP06012769A priority Critical patent/EP1870302A1/fr
Publication of EP1870302A1 publication Critical patent/EP1870302A1/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
    • G07B15/06—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems

Definitions

  • the present invention is in the field of telematics or traffic control using on-board units. More particularly, the invention relates to a method of personalizing such an on-board unit, an on-board unit formed with a corresponding personalization entity, and a personalization system.
  • An on-board unit is a small electronic device with corresponding interfaces for the transmission of data that can be used in mobile devices such. As vehicles, ships, motor vehicles, trucks or other transport devices can be installed or integrated.
  • On-board units generally communicate via appropriate interfaces with a central back-office in which data can be further processed and / or provided. On-board units can be used, for example, in toll collection or for other telematics services.
  • the data transfer from the on-board unit to the back-office (this may be, for example, position-related data of the respective vehicle) or a data transfer from the back-office to the on-board -Unit (this may be, for example, information data to be provided to the user of the vehicle when driving on the intended route).
  • a unidirectional or bidirectional data transmission can be provided.
  • the on-board units are designed differently or with different modules. Basically, they have at least one interface for data transmission with the back-office. In general, they also include a receiver for the reception of position-related data (these are usually satellite-based), depending on the purpose However, any other modules or instances can also be integrated into the on-board unit.
  • GPS on-board units there are so-called Dedicated Short Range Communications (DSRC) on-board units designed for use in DSRC systems.
  • DSRC on-board unit interacts with the stationary beacon and can also have an additional interface (eg USB, GSM, WLAN, RS232, smartcard, etc.) for interacting with the back-office.
  • on-board units must always be personalized prior to their operation in a vehicle.
  • the relevant on-board unit must be initialized with relevant data before it can be put into operation. This applies in particular if the on-board unit is to be used for toll collection.
  • the relevant data includes contract data, vehicle data such. As the license plate of each vehicle, axle class, vehicle dimensions, etc.
  • the relevant data must be stored in the on-board unit and / or at least provided. By storing this data, an on-board unit is personalized. Only after personalization can it be used.
  • an on-board unit for toll collection is personalized either directly at the outlets for the on-board unit.
  • the previous personalization is thus localized.
  • the respective on-board unit is personalized directly via the DSRC interface of the on-board unit. Personalization is then carried out via this interface, that is to say the reading of the user and / or vehicle data, which as a rule takes place via proprietary protocol of the respective manufacturer.
  • a beacon module or a so-called “toaster” is used for personalization.
  • the personalization takes place in the Usually via a personalization computer, which is connected to the on-board unit via a special cable.
  • the present invention has therefore set itself the task of demonstrating a way in which the personalization process for an on-board unit can be improved.
  • the personalization process should be made simpler, more decentralized, more flexible and cheaper.
  • a significant advantage of the present invention is the fact that the personalization process of the on-board unit for toll collection is transferred to the user himself.
  • the previous disadvantages of the known methods can be overcome, which can be seen in particular in a temporal and local delay. So far, the time delay has arisen because the personalization process could only take place at designated locations.
  • changes to the data (re-personalization) or the deletion of data (de-personalization) could only take place at the designated locations or the OBU had to be replaced if necessary.
  • the previous method which is not only complicated from a logistical point of view, can be omitted according to the invention.
  • An advantage of the solution according to the invention is thus to be seen in the fact that the user does not have to send in the OBU for the actual personalization or must drive to a service / issuing office. This is a time and cost factor especially in the commercial sector.
  • another advantage lies in the decentralized personalization option. According to the invention, each user can personally personalize "his" unit and do so at a time that suits him. The personalization process according to the invention is thus independent of time and / or location.
  • the on-board unit is formed with a personalization interface.
  • the personalization interface is an additional interface; however, it is alternatively and preferably also possible to use the previous (usual) interface of the on-board unit or to expand it so that it also includes a decentralized personalization functionality.
  • the personalization interface is any interface of known type, e.g. B. to a serial interface (USB, RS232, RS-422, RS-485, etc.) or to a Bluetooth interface, etc., or to a data transfer by means of a mobile data carrier (smart card or the like).
  • the interface depends on the technical possibilities the on-board unit.
  • the personalization interface is basically used to transfer data relevant for personalization to the on-board unit and from the same to the back-office.
  • An essential feature of the invention is the fact that personalization can take place in a decentralized manner and so to speak "remotely", ie from a remote location. The user or an authorized person can personalize himself directly at the on-board unit.
  • a user of the vehicle usually registers with an instance with a corresponding interface for inputting user and / or vehicle data.
  • This can be a back-office or another instance.
  • this can be done, for example, in writing or electronically (eg via the Internet or by e-mail).
  • he can buy an on-board unit (order, buy, lease, etc.).
  • the process of registering takes place only after the purchase of the on-board unit.
  • the purchased on-board unit is basically in a non-personalized state and can not yet be put into operation in this unpersonalized state. For this, it is necessary that only the relevant for the registration user and / or vehicle data for the operation of the on-board unit are recorded.
  • the collection of the relevant data can take place in different ways: it is possible that the data is collected directly in the back office; It is likewise possible for the user or a service person to enter the data at any computer-aided instance or to enter it manually on forms. Subsequently, the data are recorded electronically, whereby the data thus acquired are stored by means of electronic data transmission in the back-office. Also, the data can be taken on behalf of the user by another service provider. It is conceivable, for example, that the vehicle data comes from a partner A, while payment-related data or contract data come from another partner B. The In addition, data can also be provided by another contractual partner and read in for the method according to the invention.
  • the data relevant for personalization are always managed centrally, preferably in the back office. These records can then be distributed according to the invention to decentralized units for the purpose of personalization.
  • the relevant data recorded at a registration office are then transferred via an interface to the on-board unit or read in there.
  • the provision of the acquired data at the on-board unit will thus preferably be a reading in of the data or a transfer of the data to the on-board unit.
  • the relevant data is always distributed centrally, ie from the back office, to the mobile units. Alternatively, however, registrars may also send the data directly to the mobile units and inform the back office.
  • the relevant data may also include other data relevant for personalization, since the on-board unit can not be used exclusively for toll collection, but can also support other services.
  • the step of capturing the data is followed by a verification step.
  • the collected data is checked according to configurable criteria. Usually they are verified with regard to admissibility and / or validity. In other embodiments of the invention, further verification criteria are conceivable here. If a check of the data is to take place, a personalization of the on-board unit can only be completed successfully if the verification step has also been successfully completed. However, it is also possible that the feature of the check is deactivated or omitted. Verification may also be a manual step in which the collected data is compared to vehicle paper data.
  • the relevant data ie the data that is relevant for the respective personalization process
  • the relevant data will differ from case to case. Which data is selected here is basically dependent on the desired and commissioned services and services available to the user to be asked. Only when all relevant data has been entered, the personalization process can be completed. Otherwise, the user is asked to enter the necessary data.
  • the data is collated and provided in an encrypted file format.
  • registering the user and providing the personalization software may occur at a different time (e.g. in an upstream phase or after the collection and / or verification of the relevant data).
  • the on-board unit is formed with a known to the expert interface to the back-office; According to the invention, the on-board unit may further comprise a further personalization interface for transmitting the relevant data.
  • the relevant data, in particular the user and / or vehicle data are provided by a separate, external entity (in particular by the back office).
  • the relevant data, in particular the user and / or vehicle data are present in a so-called personalization file.
  • the personalization file is preferably encrypted and / or signed. This file can be accessed via any electronic or other medium, such as As diskette, CD, USB stick, flash card, smart card, etc., or other type of electronic data transmission, such.
  • B. E-mail or via Internet download any other type of transmission for the purpose of providing the data on the on-board unit is also within the scope of the invention (e.g., sending the file by mail and reading the data).
  • the user therefore needs three components: namely the on-board unit, a personalization software and the personalization file. Once all three components are present, the personalization process can be triggered.
  • the user includes the on-board unit on a commercially available computer or on electronic handset such.
  • a PDA or a handheld PC, etc. has been installed on the personalization software and on which the personalization file is read or is still being read.
  • the personalization interface is used, which is a USB interface in the preferred embodiment.
  • Online personalization essentially uses a similar mechanism.
  • An essential difference to offline personalization is the fact that it is no longer necessary to send the user a personalization file. This logistically complicated transmission process can be omitted.
  • the on-board unit is also connected to a computer and an additional connection is established from the computer to the back-office, so that a communication tunnel between the on-board unit and the back-office can be established.
  • the connection is preferably encrypted.
  • the data is then compiled directly in an online procedure in the back-office and transmitted to the on-board unit.
  • the on-board unit can then load the provided personalization file directly into its own memory. This completes the personalization process of online personalization.
  • an intermediate computer provided between the on-board unit and the back-office is no longer necessary.
  • the on-board unit interacts or communicates directly with the back-office via an interface.
  • the on-board unit may be connected to a multi-instance local area network, with personalization software provided on one of the instances. On a command of the personalization software then the personalization process can be triggered, so that in particular the on-board unit is caused to get the relevant Download data from the back-office. Alternatively, it may be provided that the on-board unit itself, ie actively, fetches the relevant data from the back-office.
  • the personalization software retrieves the data online from the back-office and this - as it were offline - copied directly into the on-board unit or in a memory of the on-board unit.
  • the personalization software can also be designed on a further external entity that communicates with the on-board unit.
  • the relevant data are made available.
  • the recorded, relevant data it is possible for the recorded, relevant data to be installed or stored on the on-board unit, without the on-board unit having to initiate this with a specific command.
  • this is done by the personalization software and is used particularly in offline personalization.
  • the collected relevant data may be provided by being actively retrieved from the on-board unit.
  • a specific command is usually issued by the on-board unit to a separate instance (usually the back-office).
  • This method is commonly used in online personalization.
  • other combinations are also conceivable here, so that the initiation of the personalization can be configured by another entity, in particular also in the case of online personalization.
  • the provision of the relevant data usually takes place by reading the respective personalization file via an interface, in particular via the personalization interface, on the on-board unit itself.
  • the personalization file is not directly connected to the on-board unit. Unit, but at a data-technically connectable further instance, which in turn transmits the data to the on-board unit.
  • further variability can be achieved.
  • the provided relevant data for the on-board unit is used directly for the personalization process.
  • the provided relevant data is only a test step subjected.
  • the provided data are checked according to configurable criteria.
  • a signature check, an authorization check, checking an authentication, a decryption check, a check for correct affiliation of the personalization file to the connected on-board unit, as well as the data transmission connection to the on-board unit can be checked by the personalization software during the personalization process.
  • the criteria by means of which the test is to take place can be configured so that the method can be adjusted to the respective application.
  • the data transfer in relation to the on-board unit ie from and to the on-board unit for all or selected data to be transmitted is preferably encrypted and / or signed.
  • this feature is optional.
  • a check of the relevant data entered by the user can take place (eg on consistency, permissibility, completeness, etc. of the entered data).
  • the personalization is triggered directly by a specific user action on the on-board unit.
  • a further degree of freedom can be achieved in terms of time.
  • the personalization process can be triggered at any time, provided that all necessary conditions are met (the on-board unit is present, the personalization software is present - in the online personalization according to the invention, the personalization software already in the on -Board unit is integrated or is provided for this or loaded and thus in this case automatically provided with the on-borad-unit itself - and the user and / or vehicle data are provided).
  • the personalization software already in the on -Board unit is integrated or is provided for this or loaded and thus in this case automatically provided with the on-borad-unit itself - and the user and / or vehicle data are provided.
  • the term "personalization” is to be understood within the scope of the present invention and encompasses all processes in the context of an OBU personalization, in particular also a re-personalization of an on-board unit (eg when a new one is acquired) personalization data (re-personalization) and also the deletion of personalization data (de-personalization).
  • Re-personalization may be necessary, for example be if user and / or vehicle data changes or if other services are to be made available to the user and / or if other services are to be commissioned. In any change of relevant data, the inventive method can be applied easily, quickly and without the use of further instances.
  • a de-personalization should be included; In this case, relevant data or at least parts of it should be able to be deleted on the on-board unit. This is the case when the user terminates services or services provided.
  • the personalization according to the invention may further relate to vehicle-related data (vehicle data, such as license plate, vehicle class, etc.) and / or also to personal data (eg contract data of the user or other data concerning the user).
  • vehicle data vehicle data, such as license plate, vehicle class, etc.
  • personal data eg contract data of the user or other data concerning the user.
  • the personal data can extend over several vehicles (eg contract account PAN from which a fee is deducted). If the OBU is not used for toll, only one or the other of the above-mentioned types of data can be considered.
  • the relevant data is basically data that is relevant for the personalization process. Typically, these are user and / or vehicle data provided in a personalization file. Likewise, however, other data, in particular other toll-related data, may also be included here.
  • a personalization file is related to a specific on-board unit.
  • the inventive method can also be used if an on-board unit used by different users and / or if an on-board unit is used for several different vehicles.
  • an on-board unit is intended for use in a mobile device.
  • the mobile device may be, for example, a vehicle, a ship, a truck or their parts.
  • the personalization entity is integrated into the on-board unit. It is thus possible for the personalization instance to be a separate module that only provides the personalization software to the on-board unit.
  • An alternative task solution provides a storage medium which is intended to store the above-described computer-implemented method and is readable by a computer.
  • the method for personalizing an on-board unit OBU is determined.
  • the on-board unit OBU is installed in a mobile device, in particular in a vehicle.
  • the on-board unit OBU is provided with an interface for data transmission with a back-office BO.
  • This can be a direct or an indirect data transfer between the on-board unit OBU and the back-office BO.
  • the user usually operates the on-board unit OBU and / or the vehicle.
  • the user registers in the system. Alternatively, it is possible that already registered registration data of the user is accessed, possibly after a successful verification of the same. This is preferably done centrally in the back office BO. In an alternative embodiment, however, this can be done also decentralized to contract offices and in writing.
  • the user is provided with personalization software depending on the provided personalization method (online vs. offline).
  • Personalization software PSW is an executable file that resides on a mobile data carrier, such as a mobile device.
  • a mobile data carrier such as a mobile device.
  • a CD, a floppy disk, a Smardcard or the like may be stored and the user is provided.
  • the personalization software PSW is not provided on the on-board unit OBU but on an external instance, e.g. on the back office BO.
  • relevant data ND that is necessary for the personalization of the on-board unit OBU is acquired.
  • the relevant data are preferably user and / or vehicle data ND, which are essential for the operation of the on-board unit.
  • other data such as contract data, vehicle data (eg license plate, axle class, vehicle dimension), user data (contract data, account data, etc.) and / or other data (which can be found, for example, on the On Board unit OBU itself, such as provided interfaces, serial number, etc.).
  • the on-board unit OBU according to the invention does not necessarily have to be oriented towards toll collection but can also provide any other services and benefits.
  • the inventive method for personalizing the on-board unit OBU is highly variable configurable and designed so that the respective relevant data ND are recorded, which are necessary for each application of the on-board unit OBU. Usually, then, a check of the detected relevant data ND takes place. However, this feature is optional and may be omitted if desired. After the relevant data ND have been recorded and possibly checked, these are provided for the on-board unit OBU.
  • two tests can be carried out independently of each other: On the one hand, a test that takes place when entering relevant data by the user (eg a check for consistency, permissibility and completeness of the entered data) and on the other hand, a test that is carried out by means of the personalization software PSW during the personalization process and can relate, inter alia, to whether the selected relevant data also relate to the connected on-board unit OBU or fit for it.
  • relevant data eg a check for consistency, permissibility and completeness of the entered data
  • PSW personalization software
  • the scope of the respective test is basically configurable.
  • criteria can be specified via a specific interface on which the check should be based.
  • an authentication check, a signature check, a completeness check, an assignment check (whether the respective relevant data records ND also relate to the on-board unit OBU to be personalized may be conceivable here, for example by reading and comparing parameters which stored both in the user and / or vehicle data ND and in the on-board unit OBU itself, for example, this may be an OBU identification number, a serial number, a manufacturer number or other parameters), a check on Decryptability of the user and / or vehicle data ND etc.
  • several checks can be carried out sequentially. It is also possible that a beaukombinatorik is created from several parameters.
  • the user and / or vehicle data ND are transmitted to the on-board unit OBU by means of the personalization software PSW.
  • the transmission is encrypted and authentication methods are used.
  • the personalization method according to the invention is thus a decentralized personalization method, which takes place so to speak "remotely", namely via remote entities that are separate with respect to the back-office BO, e.g. via the on-board units OBU itself.
  • Fig. 1 the method steps in the sequence are indicated, which are selected according to the preferred embodiment.
  • other embodiments relate to a different time sequence of the above-mentioned method steps.
  • the registration of the user and the provision of the personalization software PSW can take place in a time-advanced phase.
  • the capturing of user and / or vehicle data ND can take place.
  • the personalization of the on-board unit OBU can be performed.
  • the three phases mentioned above are basically decoupled in time from one another and do not have to take place in a necessary temporal context.
  • registering, provisioning and capturing can also be done in a different order.
  • an on-board unit OBU For the method step of personalizing it is only necessary that an on-board unit OBU is provided, that a corresponding personalization software PSW is provided (either on the on-board unit OBU itself or in the back-office BO or on another instance) and that the relevant data ND recorded and via any (eg electronic) medium, such as a smart card, have been provided. It may be provided according to the invention to store personalization data from a central location (e.g., a back office) on a smart card, and then to send it to the user. Inserting the smart card into a SmartCard reader provided in the on-board unit transfers the data to the on-board unit. The SmartCard can then be removed again. Likewise, the uses of other media (e.g., sending a mobile data carrier by mail) known to those skilled in the art are within the scope of this invention.
  • a corresponding personalization software PSW is provided (either on the on-board unit OBU itself or in the back-office BO or on another instance) and that
  • a data communications link is formed between the on-board unit OBU and the back-office BO.
  • This is either a direct connection or it may be formed indirectly and an intermediate element, in particular a further computer (in Figures 2 and 3 referred to as PC) include.
  • the on-board unit OBU is connected to another computer-aided instance, which in turn is in connection with the back-office BO.
  • FIG. 2 illustrates in that, in the case of the direct connection between the on-board unit OBU and the back-office BO, the connection between the participating instances is drawn, while in the other case the data-related connection is via the further computer takes place, which should be shown in Fig. 2 by the lower part of the drawing, which is shown only dotted.
  • the continuous data-technical connection and the dotted-illustrated data connection are alternatives.
  • the type of data connection is not fixed and therefore it can be a dial-up connection or an Internet connection.
  • the personalization software PSW or the corresponding personalization module is integrated into the on-board unit OBU. This is usually part of the OBU software.
  • personalization software can be provided on a PC if there is no direct connection.
  • the personalization software for the PC serves as a kind of link / router between on-board unit OBU and back-office BO.
  • a significant advantage of this embodiment is the fact that the personalization software PSW does not have to be a proprietary solution.
  • standard applications such. As an Internet browser can be used. Accordingly, the user is offered the personalization service by means of an Internet portal service.
  • the personalization software PSW can already be installed in the OBU on-board unit or it can be a component of the OBU software. It either acts as a router or triggers the on-board unit over the network to start the personalization.
  • the personalization software PSW can also be forwarded to the on-board unit OBU in other ways, for B. by a mobile disk that is read or by downloading via an Internet connection. It is also possible in an alternative embodiment that the personalization software PSW is not provided (directly) on the on-board unit OBU but on another instance, e.g. on a PC if the dashed line in Figure 2 is used. Otherwise (especially with an offline personalization, which will be described in more detail below) is the provision of the personalization software PSW on the on-board unit OBU is not mandatory.
  • the personalization process can be started by the user.
  • a data connection between the on-board unit OBU and - indirectly or directly - with the back-office BO is constructed, which is preferably encrypted, z. Over IPsec.
  • the relevant data ND are assembled online and transmitted to the on-board unit OBU.
  • the relevant data ND are stored directly in a memory of the on-board unit OBU.
  • the personalization process may be performed manually by the user, e.g. through a user interaction.
  • the trigger event may e.g. This is because it is detected automatically if the on-board unit OBU has not yet been personalized when first switched on, or that it is informed by means of a standard communication that new personalization data is available in the back-office BO. This has a very significant advantage and reduces errors due to failure of personalization operations, as the on-board unit OBU, so to speak, (automatically) personalizes itself after having been provided a connection with the back-office BO in the user's environment is.
  • the on-board unit OBU uses the on-board unit OBU the other computer as a kind of router to the back-office BO.
  • the routing functionality provides either the operating system on the computer or the personalization software PSW or the Internet browser (eg with the aid of a Java applet, script, existing or future Internet protocols) via the aforementioned Internet portal. Solution.
  • the personalization software or the browser PSW may also initially download and buffer the user and / or vehicle data ND online (preferably on the computer). Subsequently, the on-board unit OBU can directly load the user and / or vehicle data ND from the computer or the personalization software or the browser PSW can "push" the data into the memory of the OBU.
  • the on-board unit OBU can be connected via a radio interface (eg. GSM, WLAN or WAN) or via a direct interface to the local user network (eg Ethernet) establish a connection to the back office BO.
  • a radio interface eg. GSM, WLAN or WAN
  • a direct interface to the local user network eg Ethernet
  • the personalization process is typically triggered by a user action on the on-board unit OBU or is automatically triggered by other events. This personalization process can thus z. B. be started by pressing a button.
  • the data is actively retrieved by the on-board unit OBU.
  • the personalization file ND is sent directly to the on-board unit OBU in this embodiment.
  • the way in which this is done depends on the technical possibilities of the respective on-board unit OBU and the respective user.
  • the user can use the necessary personalization software PSW received. It is thus possible for the personalization software PSW to be provided in a different type of on-board unit OBU than the personalization file ND, for example by using a standard browser (eg Java applet, script, existing or future Internet protocols ).
  • a standard browser eg Java applet, script, existing or future Internet protocols
  • the personalization process can be started.
  • the user connects the on-board unit OBU to a commercially available computer or to a portable electronic device with corresponding interfaces on which the personalization software PSW and the user and / or vehicle data ND are already present or can be read.
  • a special personalization interface is used as the interface to the on-board unit OBU.
  • the personalization interface is preferably a USB interface. However, other interfaces known to those skilled in the art are also within the scope of this invention.
  • the relevant user and / or vehicle data ND are selected from the set of user and / or vehicle data, namely those which are necessary for the respective on-board unit OBU.
  • the step of checking can now be carried out, namely checking whether the selected relevant data for the connected on-board unit OBU "fit" (or relate to another OBU, for example).
  • the relevant user and / or vehicle data ND are copied to the on-board unit OBU by means of the personalization software PSW.
  • the transmission of the data from or to the on-board unit OBU is encrypted.
  • FIG. 3 also refers to the "direct connection between OBU and BO" (which is shown as a solid line and exists only in the case of online personalization) and in which " indirect connection between OBU via computer to BO "(which is shown as a dotted line) around alternatives.
  • the user and / or vehicle data ND and the personalization software PSW are present on the further computer and via the interface or via an additional personalization interface in the on-board unit OBU can be read.
  • the user and / or vehicle data ND are each routed to the on-board unit OBU on other channels ( these embodiments are not shown in Fig. 3).
  • the user and / or vehicle data ND are preferably installed on the on-board unit OBU by means of the personalization software PSW, which is preferably provided here in the back-office BO. In this case, therefore, the data ND is not actively retrieved by the on-board unit OBU (in contrast to online personalization).
  • a significant advantage of personalization according to the invention is the fact that it can be operated both online and offline. In addition, no separate personalization output points are necessary, as was the case in the prior art. Moreover, the method according to the invention can be applied simply and quickly even when changing personalization data, without the user having to send back or replace the on-board unit OBU. He can z. B. initiate a change and / or change of services or features themselves. According to the invention, in this case the user is provided only with a new, adapted user and / or vehicle data file ND and the user can carry out the personalization or "re-personalization" himself. This means a significant simplification and acceleration of the logistical process.
  • de-personalization is within the scope of the invention, which results in the deletion of relevant data relating to a user. Even such de-personalization can be performed by the user himself, after which the user can send back the on-board unit OBU.
  • the de-personalization ensures that eg for a DSRC-OBU no unwanted transactions are caused by mail.
  • the logistics process can thus be reduced to the dispatch of the on-board unit OBU, since the user can carry out the personalization himself.
  • a pure distribution of on-board units OBU in the normal retail is possible in the future, without personalization equipment must be provided there.
  • the on-board unit can remain much longer in use by the inventive solution than was possible in the prior art. This leads to a significant time and cost advantage, since a change of personalization-relevant data (eg, other service requests) can immediately be followed by a new personalization.
  • a new or changed user and / or vehicle data file ND can be made available within seconds without the on-board unit OBU having to be removed and returned.

Landscapes

  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
EP06012769A 2006-06-21 2006-06-21 Personnalisation à distance d'une unité embarquée Withdrawn EP1870302A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP06012769A EP1870302A1 (fr) 2006-06-21 2006-06-21 Personnalisation à distance d'une unité embarquée

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP06012769A EP1870302A1 (fr) 2006-06-21 2006-06-21 Personnalisation à distance d'une unité embarquée

Publications (1)

Publication Number Publication Date
EP1870302A1 true EP1870302A1 (fr) 2007-12-26

Family

ID=37110381

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06012769A Withdrawn EP1870302A1 (fr) 2006-06-21 2006-06-21 Personnalisation à distance d'une unité embarquée

Country Status (1)

Country Link
EP (1) EP1870302A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2128825A2 (fr) * 2008-05-29 2009-12-02 Robert Bosch GmbH Appareil de détection de péage et procédé d'agencement d'un appareil de détection de péage
EP2249313A1 (fr) * 2009-05-05 2010-11-10 Kapsch TrafficCom AG Procédé d'initialisation spécifique à l'utilisation d'appareils de véhicules
EP2312535A1 (fr) * 2009-10-15 2011-04-20 Kapsch TrafficCom AG Dispositif de personnalisation et d'enregistrement d'appareils de véhicules
EP2530654A1 (fr) 2011-05-30 2012-12-05 Toll Collect GmbH Procédé d'installation d'un appareil de véhicule mobile et dispositif de véhicule doté d'un tel appareil de véhicule mobile
EP3001386A1 (fr) 2014-09-29 2016-03-30 Toll Collect GmbH Initialisation d'un appareil embarqué
EP3174015A1 (fr) * 2015-11-27 2017-05-31 Toll Collect GmbH Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage
CN107767475A (zh) * 2017-11-16 2018-03-06 江苏省泰州引江河管理处 可实现船民不上岸办理过闸缴费的船闸电子收费信息系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999006987A2 (fr) * 1997-08-01 1999-02-11 Calcar Advertising, Inc. Systeme centralise de commande et de gestion pour automobiles
DE10104499A1 (de) * 2001-01-31 2002-08-14 Daimler Chrysler Ag Strassengebührenerfassungssystem

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999006987A2 (fr) * 1997-08-01 1999-02-11 Calcar Advertising, Inc. Systeme centralise de commande et de gestion pour automobiles
DE10104499A1 (de) * 2001-01-31 2002-08-14 Daimler Chrysler Ag Strassengebührenerfassungssystem

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2128825A2 (fr) * 2008-05-29 2009-12-02 Robert Bosch GmbH Appareil de détection de péage et procédé d'agencement d'un appareil de détection de péage
EP2128825A3 (fr) * 2008-05-29 2012-05-30 Robert Bosch GmbH Appareil de détection de péage et procédé d'agencement d'un appareil de détection de péage
EP2249313A1 (fr) * 2009-05-05 2010-11-10 Kapsch TrafficCom AG Procédé d'initialisation spécifique à l'utilisation d'appareils de véhicules
EP2312535A1 (fr) * 2009-10-15 2011-04-20 Kapsch TrafficCom AG Dispositif de personnalisation et d'enregistrement d'appareils de véhicules
US8346598B2 (en) 2009-10-15 2013-01-01 Kapsch Trafficcom Ag Apparatus for the personalization and registration of vehicle devices
EP2530654A1 (fr) 2011-05-30 2012-12-05 Toll Collect GmbH Procédé d'installation d'un appareil de véhicule mobile et dispositif de véhicule doté d'un tel appareil de véhicule mobile
EP2530655A1 (fr) 2011-05-30 2012-12-05 Toll Collect GmbH Procédé d'installation d'un appareil de véhicule mobile et dispositif de véhicule doté d'un tel appareil de véhicule mobile
EP2530656A1 (fr) 2011-05-30 2012-12-05 Toll Collect GmbH Procédé d'installation d'un appareil de véhicule mobile et dispositif de véhicule doté d'un tel appareil de véhicule mobile
EP3001386A1 (fr) 2014-09-29 2016-03-30 Toll Collect GmbH Initialisation d'un appareil embarqué
EP3174015A1 (fr) * 2015-11-27 2017-05-31 Toll Collect GmbH Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage
CN107767475A (zh) * 2017-11-16 2018-03-06 江苏省泰州引江河管理处 可实现船民不上岸办理过闸缴费的船闸电子收费信息系统

Similar Documents

Publication Publication Date Title
EP3216659A1 (fr) Système de contrôle des fonctions d'un engin de travail
DE60313810T2 (de) Verfahren zur bereitstellung eines softwaremoduls für eine kraftfahrzeug-steuereinheit und computerprogramm zur ausführung des verfahrens
DE10237715B4 (de) Vorrichtung zum Zugriff auf ein Fahrzeugssteuersystem über eine drahtlose Verbindung
EP1870302A1 (fr) Personnalisation à distance d'une unité embarquée
DE102008021030B4 (de) Verfahren zum Betreiben eines Fahrzeugs sowie entsprechende Vorrichtung und entsprechendes Fahrzeug
DE10131395B4 (de) Verfahren zum Übertragen von Software- Modulen
EP2225733B1 (fr) Système de transmission de données via une liaison de transmission entre un tachygraph et un module de traitement de données et procédé de transmission de données
DE112019003727T5 (de) Elektronisches steuerungssystem für fahrzeug, programmaktualisierungsgenehmigungs-bestimmungsverfahren und programmaktualisierungsgenehmigungs-bestimmungsprogramm
EP2833329B1 (fr) Procédé et système destinés à améliorer un processus de stationnement payant de véhicule dans une installation de parking, programme informatique et produit-programme informatique
EP2013060A1 (fr) Systeme de diagnostic avec module de transmission wlan et test court de diagnostic mis en uvre
WO2019206502A1 (fr) Système d'exploitation pour véhicule
DE102014204762A1 (de) Telematiksystem, Telematikeinheit und Verfahren zur Fernsteuerung oder Beeinflussung von Fahrzeugfunktionen und zur Erfassung von Fahrzeugdaten
DE10258302B4 (de) Verfahren zur Autorisierung eines Telematikdienstes in einem Kraftfahrzeug
DE112013005761T5 (de) System und Verfahren zum Verwenden eines Autoradios zum Steuern der Lieferung von Premiuminhalt an ein Smartphone
EP2913989A2 (fr) Liaison d'un terminal à une poste mobile pour l'attribution de frais
EP2326959B1 (fr) Procédé de déconnexion de fonctions d'un tachygraphe
EP1859568B1 (fr) Procédé d'autorisation d'appareils externes
WO2019105609A1 (fr) Procédé d'actionnement d'un équipement de fermeture d'un véhicule automobile, équipement d'autorisation, équipement de contrôle d'accès, équipement de commande, et terminal mobile
EP2225734A1 (fr) Procédé et système de transmission de données
EP3384411B1 (fr) Dispositif de transmission d'une instruction fonctionnelle entre un véhicule automobile et un dispositif extérieur au véhicule, et dispositif d'interface et système
EP3823877A1 (fr) Utilisation d'une interface utilisateur d'un système d'information de passager et/ou d'un système de divertissement
EP3001386B1 (fr) Système et procédé d'initialisation d'un appareil embarqué
DE102017203191A1 (de) Verfahren zum Freigeben zumindest einer Kraftfahrzeugfunktion wenigstens eines Kraftfahrzeugs sowie zentrale Servereinheit und Freigabeeinrichtung
EP3916649A1 (fr) Procédé de mise en uvre d'une analyse, d'une identification et/ou d'un dépannage et système de communication de mise en uvre du procédé
DE102015204829A1 (de) Verfahren und Anordnung zum Freischalten von Funktionen in einem Tachografen

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: 20070221

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

17Q First examination report despatched

Effective date: 20080404

AKX Designation fees paid

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

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

18D Application deemed to be withdrawn

Effective date: 20110103

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

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

R18D Application deemed to be withdrawn (corrected)

Effective date: 20110104