EP0927410A1 - Verfahren und einrichtung zur erfassung von verkehrsdaten von fahrzeugen - Google Patents
Verfahren und einrichtung zur erfassung von verkehrsdaten von fahrzeugenInfo
- Publication number
- EP0927410A1 EP0927410A1 EP97943779A EP97943779A EP0927410A1 EP 0927410 A1 EP0927410 A1 EP 0927410A1 EP 97943779 A EP97943779 A EP 97943779A EP 97943779 A EP97943779 A EP 97943779A EP 0927410 A1 EP0927410 A1 EP 0927410A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- unit
- decentralized
- data
- vehicles
- function
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
Definitions
- the invention relates to a method for recording traffic data from vehicles and devices for carrying it out.
- the object of the invention is to reduce the vehicle-related expenditure and to implement a flexible detection and reporting method and corresponding facilities which are optimized from the traffic point of view
- An advantage of the invention is the possibility of detecting traffic disturbances at the location where they occur, without having to use stationary detection structures
- Mobile traffic data acquisition is used to obtain dynamic traffic data from the driving data.
- the method for mobile acquisition of traffic data is also called FCD (Floating Car Data) method
- FCD Floating Car Data
- Mobile traffic data acquisition distinguishes between event-related acquisition and route or network-related basic data acquisition.
- a jam occurs autonomously through the terminal-side application process (EA) and is reported directly to the central-side application process (ZA).
- the basic data acquisition is controlled by the ZA, which converts the acquisition orders from the traffic department into concrete control information for the EA and transmits this to the EA - if possible via broadcast medium.
- the basic data acquisition takes place statically at and between virtual acquisition points (ES), which are set up in a view of the digital map and stored in the non-volatile memory of the EA.
- ES virtual acquisition points
- the ZA divides the entire federal territory into
- Detection point areas ESG and generates a detection point description (ESB) for each ESG, which contains the macro commands for detection and reporting behavior as well as a list of the ES.
- ESG Detection point areas
- EB detection point description
- the mobile traffic data acquisition application is based on the IntraGSM platform and uses its communication and localization subsystems in particular.
- FIG. 1 shows the functions of the FCD method on three abstraction levels. At level 1, the central function of obtaining traffic data is broken down by data type. Level 2 below describes the
- FCD-independent basic functions of the terminal and the control center such as communication, location, statistics and general basic functions, are made available to Level 2.
- FCD procedure is presented based on this division into functional groups.
- the following sections contain a description of the traffic data acquisition processes and some examples of measurement algorithms for traffic data acquisition.
- Event-related traffic data acquisition serves to detect traffic-relevant events. Events are recognized autonomously in the EA using parameterizable algorithms. Examples of events are: entry into a traffic jam, exit from a traffic jam, entry into slow-moving traffic, exit from slow-moving traffic, route type and network type change and weather change (planned).
- the route-related collection of traffic data is part of the basic data collection, which is controlled by the ZA, and is carried out with the help of the collection point concept.
- the traffic data is measured on and between the ES and after the ES-
- the following data are at least recorded: average speed, variance in speed, travel time, possibly status values such as Windscreen wiper, fog lamp, ABS, ASR, outside temperature sensor etc.
- the network-related collection of traffic data is part of the basic data collection, which is controlled by the ZA, and is carried out with the help of the collection point concept.
- the traffic data is measured on and between the ES and classified according to the ES attribute network type. Source-target relationships can also be evaluated using OD matrices.
- ES-ID Attributes of the ES in the map view: ES-ID, global coordinates (e.g. WGS84), geometry class (circle / rectangle, extension), direction class (including opening angle), connector type, network type
- ES-ID Attributes of the ES in the ESB: ES-ID, relative coordinates (in relation to the ESG umbrella), geometry class (circle / rectangle, extension), direction class (including opening angle), plug ⁇ type, network type
- ESG Registration point areas
- BAB-ESG Creation of an ESG for the BAB network
- AB-ESG Creation of regional ESG for the "home region".
- Each ESG has an ESG umbrella (rectangle, center with global coordinates, extension) and possibly The edge of each end device contains the BAB-ESG and at least one regional ESG
- the size of the regional ESG depends on a fixed storage space specification, the size of the ESG is independent of the device versions and capacities, devices with a higher storage capacity may contain several regional ESGs by reloading ESB when leaving a regional ESG (indicated by the use of edge umbrellas or . ⁇ .) must be decided with regard to the expandability of the procedure
- the ESB contains the application data of an ESG incl. the ES for the interpreter EA.
- the ESB contains ESG type (BAB, regional), ESG umbrella
- EA is able to combine and work through several ESBs.
- the BAB-ESG and the regional / s ESG are always active
- detection umbrellas can be defined for special, regional and temporary recording tasks. A reference to certain routes or network types is possible.
- Each registration umbrella has a validity period, one
- the special macro type within a data entry umbrella overwrites the macro type for the basic data entry.
- Several acquisition umbrellas can be specified at the same time.
- the ZA converts registration orders from traffic editors into specific control information for the EA.
- the acquisition and reporting behavior is controlled via parameter sets specified by the ZA.
- the parameter sets for event-related as well as route and network-related recording can be changed by the ZA, route- or network-related recording: For each ESG (BAB-ESG and regional ESG) there is a specified parameter set (including macro commands) that includes the basic recording and the Reporting behavior. The different regional ESG can have specific parameter sets. The parameter sets are classified according to route and network types.
- Control information is implemented using macro commands.
- a macro instruction consists of any number of logical ones
- Macros can be nested as required; a macro can link other macro commands.
- EA recognizes route and network type based on the attributes of the recognized ES.
- EA creates a history of the passed ES. History is given to the ZA with FCD.
- Encryption Appropriate procedures are used to encrypt the recorded traffic data in order to prevent unauthorized access to the data
- FCD protocol A uniform FCD protocol is used
- control information simple areas circles, rectangles
- FCD application uses the basic functions of the IntraGSM communication subsystem, which is described in the specification "Definition of the range of functions and interfaces of a multifunctional traffic telematics terminal", version 1.2, February 1996.
- the FCD application uses the basic functions of the IntraGSM subsystem localization, which is specified in the specification "Definition of the range of functions and the
- a basic set of mathematical functions (such as for calculating the mean and variance) is provided.
- the process enables free programmability for measured value acquisition, reporting behavior, communication, control.
- the traffic data is recorded on the one hand via the event-oriented macro commands. These macro commands are initialized at the start (e.g. monitoring the speed of the vehicle). When an event occurs (such as falling below a certain
- Speed threshold as an indication of a traffic jam
- the commands linked to it are executed (e.g. message to the ZA).
- the EA determines the distances to all ES of all existing ESG and arranges the ES in a registration point list (ESL) according to the smallest distance.
- ESL registration point list
- a certain number of nearest ES (achbar detection points) are loaded into the localization subsystem as waypoints.
- the ESL is updated again and again after a certain time step.
- "Removing" ES are deliberately deleted from the FIFO of the basic function "Waypoint" before newly added neighboring detection points are loaded into the FIFO. If the basic function "Waypoint" reports that a detection point has been reached, the commands specified by the ZA are processed by the control module of the EA. For this purpose, the corresponding macros are started and the associated measurement or communication commands are executed.
- the EA anonymously transmits individual event and ES-related data to the ZA.
- the control information specified by the ZA determines which data are transmitted to the ZA. I. a. not all recorded data is also transmitted.
- the version of the ESB and the number of the ESG are included.
- Examples of route or network-related data ES-ID, average speed since the last ES and variance, braking and acceleration profiles etc.
- Examples of event-related data current position or current ES-ID, type of event e.g. "Traffic jam start", "accident”.
- the ZA assigns the individual ES-related driving data to the map view. From the individual driving data, statistical data such as averaging are used to obtain traffic data which are made available to the traffic department.
- the VD messages of the EA often relate to several route sections. For this reason, a participant's VD messages must first be used to determine which sections of the route he has traveled. For this purpose, the ZA compares the route length traveled between the two ES with the route lengths of the possible routes from the map view and uses this to determine the route actually traveled (ie the route section sequence). The subscriber's ES-related traffic data are then converted into traffic data for the subscriber
- the route-related traffic data can be obtained from the traffic data of many participants who have traveled through different route section sequences by setting up and solving systems of equations.
- Statistical processing can also be activated and parameterized for event-related data in the ZA. If a traffic disruption occurs, the traffic department can instruct the ZA to activate the red ES of special road sections for a certain period of time. The ZA can also proactively activate the red ES. The ZA informs all affected EA that now activate all affected red ES. After the specified period has expired or when the ZA withdraws it, the EA deactivates all affected red ES again. The red ES should be loaded via SMS-CB.
- the EA may pick up one or more neighboring ESBs from the ZA's mailbox. However, the current ESB is not overwritten, but is retained in the EA.
- macros are started by commands that are referenced to a macro. Set up a macro with a command sequence (macro identifier is returned). Possible commands in the macro:
- Waypoints in the basic function "Waypoint" 3. Macro calls 4. ...
- the function value can be a success message Machining result or include a pointer to the result.
- the function values, ie commands, can be used directly as parameters of commands (nesting).
- Average value memories are required to determine variables such as average speed, average travel time on a section of the route, etc.
- the localization subsystem delivers the speed and direction of the vehicle every second.
- Speed-oriented commands are used to observe the speed values and to evaluate whether certain threshold values are exceeded or not reached.
- the EA determines the acceleration from the speeds that are provided every second by the localization subsystem. Acceleration-oriented commands are used to observe the acceleration values and to evaluate whether certain threshold values are exceeded or not reached.
- acceleration trigger Setting up an acceleration trigger with threshold, response direction (acceleration overshoot or undershoot) and reference to a macro (acceleration trigger identifier is returned) Removing an acceleration trigger Removing all acceleration triggers
- Strongly application-oriented commands can be developed for complex evaluations.
- An example of this is the creation and evaluation of braking or
- Acceleration profiles after an acceleration trigger has responded It can then be evaluated, for example, for "unexpected hazard / obstacle”, “full braking”, “accident”
- vehicle-related event data such as indicators (hazard lights in the event of a traffic jam), windshield wipers (rain), rear fog lamp (fog) or
- each ESB contains the ESG numbers of the neighboring registration point areas. Adjacent TSG are staggered so that only three ESG can touch each other at the corners.
- one or more neighboring ESBs should, if necessary, be picked up by the ZA if they have not yet been saved in the EA.
- so-called ESG edge umbrellas are set in the edge regions of the ESG umbrella (see Fig. 2: Current detection point area (ESG 1), which is surrounded by offset neighboring ESG. The edge of the ESG is covered by 8 edge umbrellas). If the vehicle reaches such an edge umbrella, the EA automatically picks up one or more associated neighboring ESG.
- the AM-VD can e.g. are parameterized so that only 2 ESB are stored in the EA: a "long-distance ESB" for the user's home country and a "regional ESB”. in the
- Long-distance ESB are only the most important long-distance ES, the other long-distance ES and other regional ES are stored in the regional ESB. Both ESB remain semi-permanent in the EA. The ESB change occurs only if the user has left his region for a long time, so that a threshold value of "page faults" has been exceeded. (Without SMS-CB
- All ESB are provided by the AM-VD ZA in an ESB mailbox, where they can be picked up by the EA under the ESG number as a mailbox subaddress.
- the ZG of the AM-VD continuously maintains the ESG and its ESB. If the ESG and its ESB are updated (e.g. deletion and re-establishment of registration points, modification of macro commands, creation of new measuring orders, shifting the limits of an ESG), the new ESG version is given a new ESG number.
- the ZA of the AM-VD decides at what point in time (by broadcast) it informs the EA concerned about a new ESG version by specifying the new ESG number and asks them to pick up the new ESB from the ESB mailbox.
- the number of the corresponding ESB is included in the transmission of traffic data. If the ESB is out of date, so if necessary, the ZA requests its EA to collect a new ESB from the ESB mailbox.
- a newly charged ESB is only activated when it has been fully received.
Landscapes
- Chemical & Material Sciences (AREA)
- Analytical Chemistry (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Traffic Control Systems (AREA)
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE19638069 | 1996-09-18 | ||
DE19638069.3A DE19638069B4 (de) | 1996-09-18 | 1996-09-18 | Verfahren und Einrichtung zur Erfassung von Verkehrsdaten von Fahrzeugen |
PCT/DE1997/002086 WO1998012682A1 (de) | 1996-09-18 | 1997-09-17 | Verfahren und einrichtung zur erfassung von verkehrsdaten von fahrzeugen |
Publications (2)
Publication Number | Publication Date |
---|---|
EP0927410A1 true EP0927410A1 (de) | 1999-07-07 |
EP0927410B1 EP0927410B1 (de) | 2001-07-04 |
Family
ID=7806023
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP97943779A Expired - Lifetime EP0927410B1 (de) | 1996-09-18 | 1997-09-17 | Verfahren und einrichtung zur erfassung von verkehrsdaten von fahrzeugen |
Country Status (6)
Country | Link |
---|---|
EP (1) | EP0927410B1 (de) |
AT (1) | ATE202870T1 (de) |
AU (1) | AU4549497A (de) |
DE (2) | DE19638069B4 (de) |
ES (1) | ES2160973T3 (de) |
WO (1) | WO1998012682A1 (de) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101162551B (zh) * | 2006-10-12 | 2011-07-27 | 爱信艾达株式会社 | 导航*** |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19836089A1 (de) * | 1998-07-31 | 2000-02-03 | Inst Halbleiterphysik Gmbh | Verfahren zur Ermittlung von dynamischen Verkehrsinformationen |
DE19917154B4 (de) * | 1999-04-16 | 2013-09-05 | Deutsche Telekom Ag | Verfahren zum Erkennen von Stausituationen auf Straßen und Fahrzeuggeräte mit einer Einheit zur Durchführung des Verfahrens |
DE10004524A1 (de) * | 2000-02-02 | 2001-08-09 | Volkswagen Ag | Verfahren und Vorrichtung zum Erfassen und Beurteilen von Verkehrslagedaten |
DE10014365B4 (de) * | 2000-03-16 | 2011-08-11 | DDG Gesellschaft für Verkehrsdaten mbH, 40547 | Funktionale Telematikendgeräte-Steuerung |
DE10018562C1 (de) * | 2000-04-14 | 2002-02-07 | Daimler Chrysler Ag | Verfahren zur Gewinnung von Verkehrsdaten für ein Verkehrsnetz mit verkehrsgeregelten Netzknoten durch Meldefahrzeuge |
DE10029816A1 (de) * | 2000-06-16 | 2002-01-03 | Daimler Chrysler Ag | Fahrerunterstützendes Assistenzsystem |
CZ301906B6 (cs) * | 2000-07-19 | 2010-07-28 | Deutsche Telekom Ag | Zpusob zjištování informací o dopravní situaci a zarízení k provádení zpusobu |
DE10043797A1 (de) * | 2000-09-06 | 2002-03-28 | Daimler Chrysler Ag | Integriertes Verkehrsüberwachungssystem |
DE10045944B4 (de) * | 2000-09-16 | 2013-11-07 | Volkswagen Ag | Verfahren zur Regelung des Abstandes und/oder der Geschwindigkeit eines Fahrzeuges bei einem Überholvorgang |
JP3849435B2 (ja) * | 2001-02-23 | 2006-11-22 | 株式会社日立製作所 | プローブ情報を利用した交通状況推定方法及び交通状況推定・提供システム |
DE10219531A1 (de) * | 2002-05-02 | 2003-11-20 | Volkswagen Ag | Verfahren und Datenprotokoll zum Austausch von Informationen zwischen einer Verkehrszentrale und einem Stichprobenfahrzeug |
WO2005024753A1 (en) * | 2003-09-10 | 2005-03-17 | Evgueni Essaoulov | Automatic vehicle traffic control system |
JP2016119547A (ja) * | 2014-12-19 | 2016-06-30 | トヨタ自動車株式会社 | 車両データのリモート収集システム |
DE102018203178A1 (de) | 2018-03-02 | 2019-09-05 | Audi Ag | Verfahren und Steuervorrichtung zum Ermitteln von zumindest einem Ereignisdatensatz eines Auslöseereignisses in einem Kraftfahrzeug sowie Kraftfahrzeug |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AT54760B (de) | 1910-04-19 | 1912-08-10 | Berthold Rosenman | Steuerung für Kraftmaschinen mit zwei in einem Ringzylinder abwechselnd kreisenden und stillstehenden Kolben. |
US3646580A (en) * | 1969-07-18 | 1972-02-29 | Raytheon Co | Surface vehicle fleet command and control system |
DE2136321B2 (de) * | 1971-07-21 | 1980-01-03 | Robert Bosch Gmbh, 7000 Stuttgart | Verfahren zum Überwachen von Fahrzeugen |
GB8311303D0 (en) * | 1983-04-26 | 1983-06-02 | British Telecomm | Vehicle route finding system |
US5025261A (en) * | 1989-01-18 | 1991-06-18 | Sharp Kabushiki Kaisha | Mobile object navigation system |
FR2642875B1 (fr) * | 1989-02-03 | 1994-02-18 | Urba 2000 | Systeme de collecte et de diffusion d'informations pour automobilistes |
US5182555A (en) * | 1990-07-26 | 1993-01-26 | Farradyne Systems, Inc. | Cell messaging process for an in-vehicle traffic congestion information system |
DE4105584C1 (en) * | 1991-02-22 | 1992-02-20 | Audi Ag, 8070 Ingolstadt, De | Traffic information system using mobile telephones - provides two=way communication between subscribers and central via organisation channel(s) |
JPH04319991A (ja) * | 1991-04-19 | 1992-11-10 | Pioneer Electron Corp | 移動体の遠方監視制御装置 |
GB2261977B (en) * | 1991-11-29 | 1994-09-28 | John Bernard Leonard | Method and apparatus for controlling movements of vehicles and/or persons |
FR2693820B1 (fr) * | 1992-07-15 | 1994-09-09 | Sagem | Procédé d'acquisition de données sur la circulation urbaine, central et véhicule pour la mise en Óoeuvre du procédé. |
DE4411125C2 (de) * | 1993-04-01 | 1996-05-09 | Man Nutzfahrzeuge Ag | Informationssystem |
DE4321437A1 (de) * | 1993-06-28 | 1994-02-17 | Kraiss Karl Friedrich Prof Dr | Verfahren zur Verkehrsregelung und zur Ermittlung zielführender Verkehrsinformation an Bord von Kraftfahrzeugen auf Fernstraßen |
DE4410896A1 (de) * | 1994-03-29 | 1995-10-05 | Bosch Gmbh Robert | Fahrzeuggerät für Transponderbetrieb |
DE4439708A1 (de) * | 1994-11-05 | 1996-05-09 | Bosch Gmbh Robert | Verfahren zur Positionsbestimmung eines Fahrzeugs auf einer Straße |
DE19513640C2 (de) * | 1994-11-28 | 1997-08-07 | Mannesmann Ag | Verfahren zur Reduzierung einer aus den Fahrzeugen einer Fahrzeugflotte zu übertragenden Datenmenge |
DE19521914C2 (de) * | 1994-11-28 | 2000-05-04 | Mannesmann Ag | Verfahren und Vorrichtung zur Gewinnung von Informationen über die Umgebung eines Fahrzeugs einer Stichprobenfahrzeugflotte |
DE19604084A1 (de) * | 1995-03-23 | 1996-10-02 | Deutsche Telekom Mobil | Verfahren und Einrichtung zur Ermittlung von Dynamischen Verkehrsinformationen |
JP2000504859A (ja) * | 1996-02-08 | 2000-04-18 | マンネスマン・アクチエンゲゼルシャフト | 交通状況データの収集方法 |
-
1996
- 1996-09-18 DE DE19638069.3A patent/DE19638069B4/de not_active Expired - Lifetime
-
1997
- 1997-09-17 AT AT97943779T patent/ATE202870T1/de active
- 1997-09-17 ES ES97943779T patent/ES2160973T3/es not_active Expired - Lifetime
- 1997-09-17 EP EP97943779A patent/EP0927410B1/de not_active Expired - Lifetime
- 1997-09-17 WO PCT/DE1997/002086 patent/WO1998012682A1/de active IP Right Grant
- 1997-09-17 AU AU45494/97A patent/AU4549497A/en not_active Abandoned
- 1997-09-17 DE DE59703970T patent/DE59703970D1/de not_active Expired - Lifetime
Non-Patent Citations (1)
Title |
---|
See references of WO9812682A1 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101162551B (zh) * | 2006-10-12 | 2011-07-27 | 爱信艾达株式会社 | 导航*** |
Also Published As
Publication number | Publication date |
---|---|
DE59703970D1 (de) | 2001-08-09 |
AU4549497A (en) | 1998-04-14 |
DE19638069B4 (de) | 2014-05-08 |
ATE202870T1 (de) | 2001-07-15 |
DE19638069A1 (de) | 1998-03-19 |
WO1998012682A1 (de) | 1998-03-26 |
EP0927410B1 (de) | 2001-07-04 |
ES2160973T3 (es) | 2001-11-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE102018100112B4 (de) | Verfahren und Systeme zum Verarbeiten von lokalen und Cloud-Daten in einem Fahrzeug | |
EP3482160B1 (de) | Verfahren und system zur erzeugung von karteninformationen für notfallflächen | |
EP0927410B1 (de) | Verfahren und einrichtung zur erfassung von verkehrsdaten von fahrzeugen | |
EP2149132B1 (de) | Verfahren und vorrichtung zur erkennung von verkehrsrelevanten informationen | |
EP1026649B1 (de) | Verfahren und Vorrichtung zur Bereitstellung von Verkehrsinformation | |
EP1610971B1 (de) | Verfahren zur risikogeregelten geschwindigkeit eines kraftfahrzeuges und einrichtung zur durchführung des verfahrens | |
EP4025470A1 (de) | Querführung eines fahrzeugs mittels von anderen fahrzeugen erfassten umgebungsdaten | |
WO2015188905A1 (de) | Verfahren zur ermittlung von positionsdaten zur nutzung beim betrieb eines fahrzeugsystems eines kraftfahrzeugs und positionsdatenermittlungs- und -verteilungssystem | |
DE102016211751B4 (de) | Verfahren, Vorrichtungen und Computerprogramme zum Bestimmen eines Zustands zumindest eines Fahrbahnrandobjekts | |
DE19521919C2 (de) | Verfahren und Vorrichtung zur Reduzierung einer aus Fahrzeugen einer Stichprobenfahrzeugflotte zu übertragenden Datenmenge | |
DE102017201665A1 (de) | Verfahren zur Einbindung eines dynamischen Objektes in eine digitale Karte eines hochautomatisierten Fahrzeugs (HAF) | |
WO2019072550A1 (de) | Evaluation von komponenten automatischer fahrfunktionen und fahrbahnerkennung auf unterschiedlichen verabeitungsstufen | |
EP1017965B1 (de) | Verfahren zur aktualisierung einer digitalen strassenkarte | |
EP2662848A2 (de) | Verfahren zur Erstellung eines Fahrprofils | |
DE102019002790A1 (de) | Verfahren zur Prädiktion einer Verkehrssituation für ein Fahrzeug | |
DE112021003339T5 (de) | Parkhaltepunktverwaltungsvorrichtung, parkhaltepunktverwaltungsverfahren und fahrzeugvorrichtung | |
DE112019001919T5 (de) | Einrichtung und verfahren zum identifizieren eines geschwindigkeitsüberschreitungszustands eines fahrzeugs | |
DE112021003340T5 (de) | Hindernisinformationsverwaltungsvorrichtung,hindernisinformationsverwaltungsverfahren und vorrichtung für ein fahrzeug | |
DE102016224576B4 (de) | Verhaltensmodell von Verkehrsteilnehmern für ein Fahrerassistenzsystem umfassend Statistiken zu Abweichungen vom Normverhalten | |
EP2690601B1 (de) | Mautkontrollverfahren und Mautkontrolleinrichtungen sowie Mautsystem mit derartigen Mautkontrolleinrichtungen | |
DE102017208168A1 (de) | Verfahren zum Erzeugen einer Überholwahrscheinlichkeitssammlung, Verfahren zum Betreiben einer Steuereinrichtung eines Kraftfahrzeugs, Überholwahrscheinlichkeitssammeleinrichtung und Steuereinrichtung | |
EP0715288A1 (de) | Verfahren und Vorrichtung zur Reduzierung einer aus Fahrzeugen einer Stichprobenfahrzeugflotte zu übertragenden Datenmenge | |
WO2022106087A1 (de) | Verfahren zur übertragung von daten zwischen einem fahrzeug und einer fahrzeugexternen rechnereinheit | |
DE10063588A1 (de) | Verfahren zum Übermitteln von Daten zur Verkehrslagebeurteilung und ein Endgerät in einem mobilen Detektor | |
EP0715291B1 (de) | Verfahren und Vorrichtung zur Positionsbestimmung eines Fahrzeugs |
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: 19990327 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH DE DK ES FI FR GB IT LI LU NL SE |
|
17Q | First examination report despatched |
Effective date: 19990906 |
|
GRAG | Despatch of communication of intention to grant |
Free format text: ORIGINAL CODE: EPIDOS AGRA |
|
GRAG | Despatch of communication of intention to grant |
Free format text: ORIGINAL CODE: EPIDOS AGRA |
|
GRAH | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOS IGRA |
|
GRAH | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOS IGRA |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE CH DE DK ES FI FR GB IT LI LU NL SE |
|
REF | Corresponds to: |
Ref document number: 202870 Country of ref document: AT Date of ref document: 20010715 Kind code of ref document: T |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REF | Corresponds to: |
Ref document number: 59703970 Country of ref document: DE Date of ref document: 20010809 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20010917 |
|
ITF | It: translation for a ep patent filed |
Owner name: STUDIO GLP S.R.L. |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20011004 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: NV Representative=s name: LUCHS & PARTNER PATENTANWAELTE |
|
GBT | Gb: translation of ep patent filed (gb section 77(6)(a)/1977) |
Effective date: 20011018 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2160973 Country of ref document: ES Kind code of ref document: T3 |
|
ET | Fr: translation filed | ||
REG | Reference to a national code |
Ref country code: GB Ref legal event code: IF02 |
|
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 |
|
26N | No opposition filed | ||
NLT1 | Nl: modifications of names registered in virtue of documents presented to the patent office pursuant to art. 16 a, paragraph 1 |
Owner name: T-MOBILE DEUTSCHLAND GMBH |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PFA Free format text: DETEMOBIL DEUTSCHE TELEKOM MOBILNET GMBH TRANSFER- T-MOBILE DEUTSCHLAND GMBH |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 20 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FI Payment date: 20160921 Year of fee payment: 20 Ref country code: DE Payment date: 20160922 Year of fee payment: 20 Ref country code: NL Payment date: 20160922 Year of fee payment: 20 Ref country code: GB Payment date: 20160921 Year of fee payment: 20 Ref country code: CH Payment date: 20160926 Year of fee payment: 20 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20160922 Year of fee payment: 20 Ref country code: SE Payment date: 20160926 Year of fee payment: 20 Ref country code: AT Payment date: 20160921 Year of fee payment: 20 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: BE Payment date: 20160922 Year of fee payment: 20 Ref country code: ES Payment date: 20160923 Year of fee payment: 20 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20160922 Year of fee payment: 20 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R071 Ref document number: 59703970 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MK Effective date: 20170916 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: PE20 Expiry date: 20170916 |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: EUG |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK07 Ref document number: 202870 Country of ref document: AT Kind code of ref document: T Effective date: 20170917 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION Effective date: 20170916 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MK Effective date: 20170917 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FD2A Effective date: 20180508 |
|
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 EXPIRATION OF PROTECTION Effective date: 20170918 |