EP2394255A1 - Sprachverbindung nach einem ereignis zu einer infrastruktureinrichtung - Google Patents
Sprachverbindung nach einem ereignis zu einer infrastruktureinrichtungInfo
- Publication number
- EP2394255A1 EP2394255A1 EP10703259A EP10703259A EP2394255A1 EP 2394255 A1 EP2394255 A1 EP 2394255A1 EP 10703259 A EP10703259 A EP 10703259A EP 10703259 A EP10703259 A EP 10703259A EP 2394255 A1 EP2394255 A1 EP 2394255A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- vehicle
- communication
- infrastructure
- voice connection
- communication system
- 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
- 238000004891 communication Methods 0.000 claims abstract description 148
- 238000000034 method Methods 0.000 claims description 20
- 230000005540 biological transmission Effects 0.000 claims description 10
- 230000001960 triggered effect Effects 0.000 claims description 10
- 238000005516 engineering process Methods 0.000 description 3
- 101001093748 Homo sapiens Phosphatidylinositol N-acetylglucosaminyltransferase subunit P Proteins 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 108010007100 Pulmonary Surfactant-Associated Protein A Proteins 0.000 description 1
- 102100027773 Pulmonary surfactant-associated protein A2 Human genes 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
Classifications
-
- 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
- G08G1/205—Indicating the location of the monitored vehicles as destination, e.g. accidents, stolen, rental
Definitions
- the invention relates to communication between a vehicle and an infrastructure facility.
- the invention relates to a communication system for a vehicle for communication with an infrastructure device, a communication system for an infrastructure device, a vehicle having a communication system, a method for communicating a vehicle with an infrastructure device, a program element and a computer-readable medium.
- the field of application of the invention relates to a so-called vehicle-to-infrastructure communication, which is also referred to as "Car-to-Infrastructure-Communication", and manages entirely without stationary communication nodes.
- a communication system for a vehicle for communication with an infrastructure device which has a control unit for controlling the communication and a communication unit for transmitting data to the infrastructure device and for receiving data from the infrastructure device.
- the control unit is further configured to reject a structure of a communication voice connection between the vehicle and the infrastructure device if a message sent by the infrastructure device does not satisfy a required criterion.
- control unit and the communication unit are designed to transmit a request to the infrastructure device as to whether a communication voice connection is to be established between the vehicle and the infrastructure device.
- the communication system may inquire whether a communication voice connection should be established.
- the communication unit of the infrastructure receives this request and can then the
- Offer communication unit of the original vehicle to establish a voice connection. This offer may be rejected by the communication system of the original vehicle if the data sent with the offer does not meet a required criterion.
- the vehicles may be, for example, motor vehicles or motorcycles.
- the criterion is met when the infrastructure device is registered in a corresponding list of the communication system of the original vehicle.
- This list can, according to a further embodiment of the invention, be maintained by the driver of the vehicle.
- the communication system is equipped with an input and output unit, which is designed to process the list by the driver of the vehicle. The driver can thus put together a certain group of vehicles and / or infrastructures in a list, which can then communicate with each other via a communication voice connection. All other vehicles and / or infrastructures will be rejected.
- the communication system further comprises a vehicle sensor system. The request to the infrastructure device and / or the neighboring vehicles is transmitted only if the vehicle sensor system has detected a specific triggering event.
- this triggering event is the
- the request is sent to the infrastructure facility and / or the other vehicles. These may then, if the drivers of the other vehicles or the infrastructure manager so desire, or fully automatically, depending on the setting, send back an offer to establish a communication voice connection. This offer can then be accepted or rejected, for example, depending on whether the adjacent vehicle is registered in a corresponding list or not.
- control unit for automatically accepting or automatically rejecting the structure of the
- Communication language connection is executed, depending on whether the criterion is met or not. An intervention of the driver is not required. If the criterion is fulfilled, the communication voice connection to the infrastructure device or the neighboring vehicle is established automatically.
- the request comprises an identification of the transmitting vehicle.
- vehicle-specific data is sent along with the request so that the infrastructure facility or the neighboring vehicles can identify the sending vehicle.
- the communication systems in the infrastructure facility or the neighboring vehicles can decide whether to offer the establishment of a communication voice connection or not.
- the request contains information about the triggering event.
- the communication systems of the infrastructure facility or the neighboring vehicles may decide (automatically or by user intervention) whether to offer the establishment of a communication voice connection or not.
- the communication system is designed to receive a request from a corresponding communication system of the neighboring vehicle. Furthermore, it is executed for the user-side selection of a type of triggering event for which the request is to be displayed.
- the communication system for automatically offering a
- the offer for setting up a voice connection is sent directly by the first vehicle and the infrastructure device or the second vehicle can accept it directly and thereby directly establish the voice connection.
- the voice connection There are also other forms of construction of the voice connection conceivable, but always follow the basic scheme that the first vehicle sends the desire to communicate and the second vehicle decides whether it meets this desire or not.
- a vehicle is specified with a communication system described above and below.
- a communication system for an infrastructure device for communication with a vehicle comprising: a control unit for
- Controlling communication and a communication unit for communicating data from the infrastructure device to the vehicle and for receiving data from the vehicle.
- the Control unit is configured to make a request to set up a communication voice connection with the vehicle, wherein the creation of the request is triggered by a transmission of data from the vehicle to the infrastructure device.
- a method for communication of a vehicle with an infrastructure device in which a transmission of data from the vehicle to the infrastructure device takes place. This is followed by a request for the establishment of a communication voice connection by the infrastructure device, whereupon the structure of the communication voice connection is rejected by the vehicle if the request sent by the infrastructure device does not satisfy a required criterion.
- the request for setting up the communication voice connection is triggered by the transmission of the data.
- the request for setting up the communication voice connection is triggered by the transmission of the data.
- a program element which, when executed on a processor of a communication system as described above, instructs the communication system to perform the method steps described above.
- a computer-readable medium is indicated on which a program element stored, which, when executed on a processor of a communication system described above, instructs the processor to perform the method steps described above.
- the program element may be part of a software that is stored on a processor of the vehicle management.
- the processor can also be the subject of the invention.
- this embodiment of the invention comprises a program element which already uses the invention from the beginning, as well as a program element which causes by an update an existing program for use of the invention.
- identification information for forming a communication network is exchanged via radio link, which is input in the communication system of each participating vehicle in a second step Final acknowledgment by at least one other already belonging to the communication network vehicle in the same enter.
- the prerequisite for this is that the vehicles can contact the respective other vehicles of the group by radio after the occurrence of a triggering event, in order subsequently to be able to accept or reject an offer from another vehicle to set up a communication voice connection.
- This process may involve an exchange of identifiers (so-called handshake). After this handshake, each communication system recognizes whether information is coming from a group vehicle or from a foreign vehicle.
- Fig. 1 shows a communication system according to an embodiment of the invention.
- Fig. 2 shows two vehicles according to an embodiment of the invention.
- FIG. 3 shows a flowchart of a method according to an embodiment of the invention. Detailed description of embodiments
- Fig. 1 shows a communication system 100 according to an embodiment of the invention.
- the communication system 100 has a central control unit (CPU) 101, which is connected to a communication unit 102, a vehicle sensor system 103 and an input and output unit 104.
- CPU central control unit
- the vehicle sensor system 103 has, for example, a camera 105, an ESP sensor 106 and a satellite navigation unit (GPS unit) 107.
- GPS unit satellite navigation unit
- GPS is representative of all Global Navigation Satellite Systems (GNSS), such as e.g. GPS,
- sensors may be provided to detect the events to be triggered.
- FIG. 1 shows a communication system 206 for an infrastructure, which is connected to the
- Vehicle communication system 100 can communicate.
- the system 206 has a control unit 109, a communication unit 208 and possibly a
- Communication interface 110 for connection to a central office.
- an infrastructure facility is given the option to establish a voice connection to trigger the event. Will now build a voice connection through the
- the trigger gets this request displayed including an identification of the infrastructure that wants to record the voice connection and can accept or reject.
- Events for the voice connection can be:
- a vehicle remains lying and is no longer roadworthy; a vehicle has an accident; - a vehicle has dropped off an ecall; a vehicle drives against the direction of travel
- Vehicle occupants (event triggered by the vehicle occupant).
- FIG. 2 shows a first vehicle 201 and a second vehicle 202, each having a communication system 100. There is a radio connection 203 between the two communication systems 100.
- the vehicle 201 triggers the event and the vehicle 202 or the infrastructure 204, 205 with corresponding communication systems 206 is given the option for voice connection.
- Each driver can specify whether, on the occurrence of a specific, definable event, other vehicles or infrastructures should be given the opportunity to request a voice connection. Even if such a voice connection is offered by another vehicle 202 or the infrastructure device 204 or 205, the driver (or communication system 100) of the triggering vehicle 201 still has to accept the voice connection.
- the activation of the voice connection option can generally take place for all events or only for selected events. For example, a driver of a first vehicle may specify that only if other vehicles are offered the option to establish a voice connection when the first vehicle is left lying.
- the option to establish the communication voice connection is therefore sent as a message with the event, eg. B. as a "language establishment flag".
- the second vehicle 202 and / or the infrastructure 204, 205 gets the option for voice connection.
- the driver of the second vehicle 202 or the infrastructure device then offers the establishment of the voice connection, whereupon the first vehicle 201 can reject this setup.
- the first vehicle 201 has set to "automatically accept” for an event type. ""
- the second vehicle 202 or the infrastructure provides for such Event a voice connection, this is then accepted directly.
- the second vehicle 202 and / or the infrastructure device is included in a list of "desired helpers" (eg friends, colleagues, rescue control center, etc.) This list can be influenced (ie edited) by the driver of the first vehicle 201.
- the second vehicle 202 or the infrastructure device offers a voice connection after the event in the first vehicle 201 and the voice connection is then automatically established.
- the infrastructure also has the reason for this indicated (for example, "broken-down vehicle") and the location where the vehicle has been left to locate the GPS unit 107.
- the first vehicle 201 indicates who wants to offer the voice connection.
- the second vehicle 202 and / or the infrastructure device can unlock that, in addition to the position, further information about the second vehicle is released, which can then be displayed in the first vehicle.
- This may be, for example, vehicle type, vehicle color, driver's name, license plate, etc.
- the adjacent vehicles 202 may adjust for which
- Restrictions can be: Event type;
- the option to establish a voice connection is only displayed if it is a "desired" call partner.
- Communication voice connection also automatically (for this event type and / or this vehicle 202 or this infrastructure), so a voice connection is automatically established at an event.
- the voice connection As technologies for the voice connection are direct communication connections, such. B. WLAN (802. lla / b / g / n, but also Automotive WLAN 802.11p), UWB, Bluetooth, WiMax, etc. provided. Also GSM, UMTS, LTE, etc. can be used.
- the voice connection then takes place, for example, in the form of Voice over IP (VoIP).
- VoIP Voice over IP
- step 301 an event is detected by the vehicle sensor system of the first vehicle. Upon detection of this event, in step 302, the transmission of a request to an adjacent vehicle and / or an infrastructure facility. In other words, the neighboring vehicle or infrastructure receives the option to establish a communication voice connection. In step 303 then offers the second vehicle or the
- step 304 the first vehicle is given the opportunity to decline the establishment of the communication voice connection.
- the final establishment of the communication voice connection may be through the initiation procedure described above, which in this case would replace step 304 or join or precede that step.
- the communication system according to the invention can be used to set up a voice connection to infrastructure units. This will be described below with reference to FIG. 2:
- a vehicle 201 (F1) remains due to eg damage, it is responsible for those responsible for the road Infrastructure 205 (traffic management center) to know what has happened, if necessary, to take appropriate action or to estimate the duration of the disability can. Therefore, it makes sense to have a voice connection between Fl and the road Infrastructure 205 (traffic management center)
- RSU roadside units
- auxiliary vehicle Left-over vehicle and roadside assistance by an auxiliary vehicle.
- a switching of the voice connection from the control center to the auxiliary vehicle can be applied.
- RSU this may be e.g. on highways serve the (in Germany oranges) rescue telephones on the roadside.
- PSAP - Rescue Coordination Centers
- the traffic center can specifically record voice connections to vehicles of a traffic jam to find out the exact cause. For this purpose, the driver of the vehicle must have this option enabled. If a vehicle released in this way receives a traffic jam message and recognizes that it is in the traffic jam, it sends out an identifier that allows the traffic control center to contact the driver (idea of the traffic jam detector).
- a vehicle will remain on the highway due to a defect. Therefore, it sends via vehicle-to-vehicle
- Vehicle communication a warning off. This alert is received and displayed by an RSU of the traffic control center. Thereupon, the traffic center establishes a voice connection to the vehicle, which is also accepted by the vehicle, and the traffic center can inform itself more precisely about the situation and give assistance to the driver of the vehicle.
- C2X Vehicle communication
- a traffic jam is detected by an RSU, as the vehicles only drive at very low speeds or come to a complete standstill. Then a traffic jam message will be sent.
- a vehicle registered as a traffic jam receives this traffic jam message and detects that it is in the jam. It then sends its ID and the traffic center can record a voice connection to the vehicle. Via this voice connection, e.g. be told what is the reason for the congestion.
- the communication system according to the invention can be used to establish a voice connection with emergency vehicles by C2X communication. This is described below:
- a vehicle drives with a deployment signal (blue light), it also sends this information via C2X communication.
- the ID of a voice channel is also sent, via which the occupants of the emergency vehicle can talk to other vehicles via broadcast.
- a vehicle receives the warning in front of the emergency vehicle, it also establishes a voice connection to it via the specified channel.
- the technique does not have to use the C2X technique, but it can be avoided to another more suitable technology (eg because of the higher Available bandwidth).
- the voice communication is handled via Voice over IP.
- the vehicles themselves build the voice connection and not the emergency vehicle it is up to each vehicle to decide whether or not to use it.
- it may be controlled by the occupants of the vehicle to establish a voice connection by giving them the option (e.g., by an icon on a touchscreen).
- an emergency vehicle may still force the vehicles to output their voice messages to the occupants of the vehicles within a defined perimeter or range. As a result, e.g. Warnings are more easily disseminated.
- the voice messages from the emergency vehicle need not be spoken by the occupants of the emergency vehicle.
- Band announcements ("Please keep to the left") can also be used or the emergency vehicle can be used as a relay station for the voice radio of a control center.
- An ambulance 202 approaches an accident site. On the multi-lane road there is high traffic. The ambulance activates its blue light and transmits simultaneously the warning by DSRC. This warning also contains the identification of the voice channel, which is handled via normal WLAN via Voice over IP. Other vehicles receive the warning, display it to the driver and at the same time open the voice channel. This can be the passenger of the
- Ambulance now direct all vehicles on the left side of the street, so that the ambulance can drive right by.
- the 205 rescue center wants to contact vehicles in a region to warn of a fire with heavy smoke. There are no infrastructure units 204 in the region. Therefore, emergency vehicles will be sent to the region. These force via DSRC via C2X that other vehicles output the voice channel of the emergency vehicle to the driver. This voice channel is mapped via WiMax. Via this channel, the emergency vehicles now send the language directly from the operations center, with the connection between the operations center and the emergency vehicle being implemented by the authorities.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Traffic Control Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102009007177A DE102009007177A1 (de) | 2008-02-26 | 2009-02-03 | Sprachverbindung nach einem Ereignis zum Auslöser des Ereignisses |
DE102009026680 | 2009-06-03 | ||
PCT/EP2010/051256 WO2010089299A1 (de) | 2009-02-03 | 2010-02-02 | Sprachverbindung nach einem ereignis zu einer infrastruktureinrichtung |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2394255A1 true EP2394255A1 (de) | 2011-12-14 |
EP2394255B1 EP2394255B1 (de) | 2013-07-24 |
Family
ID=42317632
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP10703259.1A Active EP2394255B1 (de) | 2009-02-03 | 2010-02-02 | Sprachverbindung nach einem ereignis zu einer infrastruktureinrichtung |
Country Status (5)
Country | Link |
---|---|
US (1) | US9014677B2 (de) |
EP (1) | EP2394255B1 (de) |
CN (1) | CN102369562B (de) |
DE (1) | DE102010001514A1 (de) |
WO (1) | WO2010089299A1 (de) |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010112327A1 (de) * | 2009-04-03 | 2010-10-07 | Continental Teves Ag & Co. Ohg | Datensicherheit für die kommunikation mit gleichgestellten teilnehmern |
JP5974498B2 (ja) * | 2012-01-24 | 2016-08-23 | 株式会社デンソー | 車車間通信装置 |
DE102012205891A1 (de) * | 2012-04-11 | 2013-10-17 | Continental Automotive Gmbh | Kommunikationseinrichtung für ein Fahrzeug |
DE102012216642A1 (de) * | 2012-09-18 | 2014-03-20 | Continental Automotive Gmbh | C2X Kommunikationsvorrichtung und entsprechendes Verfahren |
KR20180087467A (ko) * | 2013-10-14 | 2018-08-01 | 콩코드 아시아 피티이.엘티디. | 모바일 제어 유닛, 설비 관리 시스템, 모바일 유닛 제어 시스템, 설비 관리 방법, 및 모바일 유닛 제어 방법 |
CN105208077A (zh) * | 2015-08-13 | 2015-12-30 | 深圳市中兴物联科技有限公司 | 车辆信息传输装置和方法 |
US9969329B2 (en) * | 2015-09-16 | 2018-05-15 | Sony Corporation | System and method for generation of a preventive alert |
US10585440B1 (en) | 2017-01-23 | 2020-03-10 | Clearpath Robotics Inc. | Systems and methods for using human-operated material-transport vehicles with fleet-management systems |
JP6806242B2 (ja) * | 2017-04-20 | 2021-01-06 | 富士通株式会社 | 衝突リスク算出プログラム、衝突リスク算出方法および衝突リスク算出装置 |
US11256270B2 (en) * | 2018-02-07 | 2022-02-22 | Clearpath Robotics Inc. | Communication systems for self-driving vehicles, and methods of providing thereof |
CN110418294A (zh) * | 2018-04-27 | 2019-11-05 | 国基电子(上海)有限公司 | 通信方法、车载装置及计算机可读存储介质 |
JP2019091467A (ja) * | 2018-12-21 | 2019-06-13 | コンコルド アジア ピーティーイー リミテッドConcorde Asia Pte.Ltd. | モバイル制御ユニットおよびファシリティ管理方法 |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6262655B1 (en) * | 1999-03-29 | 2001-07-17 | Matsushita Electric Industrial Co., Ltd. | Emergency reporting system and terminal apparatus therein |
US7382274B1 (en) * | 2000-01-21 | 2008-06-03 | Agere Systems Inc. | Vehicle interaction communication system |
EP1233387A2 (de) * | 2001-02-19 | 2002-08-21 | Hitachi Kokusai Electric Inc. | Notmeldesystem und -Verfahren für Fahrzeug |
KR100498965B1 (ko) * | 2003-04-22 | 2005-07-01 | 삼성전자주식회사 | 차량간 임시 무선 네트워크를 이용한 차량 운행정보 교환방법 및 시스템 |
CN100373820C (zh) * | 2003-10-08 | 2008-03-05 | 松下电器产业株式会社 | 道路-车辆通信系统以及用于其中的路边设备和移动设备 |
DE102004061399A1 (de) * | 2004-12-21 | 2006-07-06 | Robert Bosch Gmbh | Verfahren zur Versendung eines Notrufs sowie Einrichtung |
JP4983005B2 (ja) * | 2005-04-12 | 2012-07-25 | 富士通株式会社 | 電子機器、優先接続装置、優先接続方法及び優先接続プログラム |
DE102006023759A1 (de) | 2006-05-20 | 2007-11-22 | Deutsche Telekom Ag | Verfahren und Detektorvorrichtung zur Abwehr von über ein Internet-Protokoll-basierendes Netz übertragenen unerwünschten Telefonanrufen |
DE102007051079A1 (de) | 2006-10-25 | 2008-04-30 | Continental Teves Ag & Co. Ohg | Verfahren und Vorrichtung zum Aufbau von Daten- und Kommunikationsverbindungen zwischen Fahrzeugen |
US20080143497A1 (en) * | 2006-12-15 | 2008-06-19 | General Motors Corporation | Vehicle Emergency Communication Mode Method and Apparatus |
DE102009007177A1 (de) * | 2008-02-26 | 2009-08-27 | Continental Teves Ag & Co. Ohg | Sprachverbindung nach einem Ereignis zum Auslöser des Ereignisses |
-
2010
- 2010-02-02 WO PCT/EP2010/051256 patent/WO2010089299A1/de active Application Filing
- 2010-02-02 DE DE102010001514A patent/DE102010001514A1/de not_active Withdrawn
- 2010-02-02 CN CN201080015542.6A patent/CN102369562B/zh active Active
- 2010-02-02 US US13/146,786 patent/US9014677B2/en active Active
- 2010-02-02 EP EP10703259.1A patent/EP2394255B1/de active Active
Non-Patent Citations (1)
Title |
---|
See references of WO2010089299A1 * |
Also Published As
Publication number | Publication date |
---|---|
CN102369562A (zh) | 2012-03-07 |
US20120034905A1 (en) | 2012-02-09 |
EP2394255B1 (de) | 2013-07-24 |
DE102010001514A1 (de) | 2010-08-12 |
US9014677B2 (en) | 2015-04-21 |
WO2010089299A1 (de) | 2010-08-12 |
CN102369562B (zh) | 2014-04-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2394255B1 (de) | Sprachverbindung nach einem ereignis zu einer infrastruktureinrichtung | |
DE102009007177A1 (de) | Sprachverbindung nach einem Ereignis zum Auslöser des Ereignisses | |
DE112011105832B4 (de) | Fahrzeugseitiges System | |
EP2223504B1 (de) | Übertragung von fahrzeuginformationen | |
EP3264390B1 (de) | Verfahren zur spektral-effizienten ermittlung von kollektiver umfeld-information für das kooperative und/oder autonome fahren, sowie berichtendes fahrzeug und weiteres fahrzeug zur verwendung bei dem verfahren | |
EP3324385A1 (de) | Verfahren zur kommunikation zwischen einer bedienstelle, welche ein automatisch fahrendes fahrzeug extern steuert, und einem weiteren verkehrsteilnehmer sowie automatisch fahrendes fahrzeug | |
DE102015219467A1 (de) | Verfahren zum Betreiben eines zentralen Servers und Verfahren zum Handhaben einer Regelkarte | |
EP3446300B1 (de) | Assistenzsystem und verfahren zur übertragung von daten bezüglich eines unfalls oder einer panne eines fahrzeugs | |
EP2188798A1 (de) | Verkehrsleitsystem | |
DE102011107881A1 (de) | Optimierung von Rettungswegen für Einsatzfahrzeuge | |
DE102015219470A1 (de) | Verfahren zum Handhaben einer Regelkarte | |
DE102010028880A1 (de) | Steuergerät in der bidirektionalen Adhoc-Netzwerk-Funkkommunikation | |
EP3411866A1 (de) | Verfahren, vorrichtungen und computerprogramme zum bereitstellen von information über eine gefahrensituation über eine fahrzeug-zu-fahrzeug-schnittstelle | |
DE102017201048A1 (de) | Verfahren zur Regelung des Verkehrsflusses in einem Kreisverkehr | |
DE112017004909T5 (de) | Fahrzeugbetriebsverwaltungssystem | |
DE102018118233B4 (de) | Computerimplementiertes verfahren, softwareprogramm und vorrichtung zur aufforderung einer bildung einer einsatzgasse | |
DE102009042437A1 (de) | Informationsbereitstellungsvorrichtung und Informationsbereitstellungsverfahren | |
DE202021105162U1 (de) | System zur Übermittlung positionsbezogener Notrufe von bzw. aus Fahrzeugen zu einer Leitstelle und zur Kommunikation zwischen Fahrzeuginsassen und einer Leitstelle | |
DE102015110334A1 (de) | Notrufsystem | |
EP2430797B1 (de) | Steuergerät für fahrzeuge in der bidirektionalen adhoc-netzwerk-funkkommunikation | |
DE102022002107A1 (de) | Vorrichtung, umfassend ein Fahrzeug und eine Drohne | |
DE102019215762A1 (de) | Anordnung und Verfahren zum vernetzten Fahren | |
WO2019101274A1 (de) | Verfahren zum betreiben eines fahrzeug-zu-x-kommunikationssystems eines fahrzeugs und fahrzeug-zu-x-kommunikationssystem | |
DE102015226729A1 (de) | Vorrichtung zur Generierung und Übertragung eines automatischen Notrufs und Verfahren für eine automatische Notfall-Meldung | |
DE102023004985A1 (de) | Verfahren und System zum Betrieb einer Fahrzeugkolonne |
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: 20110905 |
|
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 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) | ||
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20130326 |
|
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): 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 Free format text: NOT ENGLISH |
|
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: 623824 Country of ref document: AT Kind code of ref document: T Effective date: 20130815 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 502010004121 Country of ref document: DE Effective date: 20130919 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20130724 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20130724 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: 20130724 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: 20131024 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: 20131125 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: 20131124 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: 20130731 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: 20130724 |
|
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: 20130724 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: 20130724 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: 20130724 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: 20131025 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: 20130724 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: 20130724 |
|
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: 20130724 |
|
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: 20130724 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: 20130724 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: 20130724 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: 20130724 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: 20130724 |
|
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: 20130724 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: 20130724 |
|
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 |
Effective date: 20140425 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 502010004121 Country of ref document: DE Effective date: 20140425 |
|
BERE | Be: lapsed |
Owner name: CONTINENTAL TEVES A.G. & CO. OHG Effective date: 20140228 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20130724 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: 20140202 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20140202 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140228 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140228 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
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: 20140202 Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140228 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140202 |
|
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: 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: 20130724 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MM01 Ref document number: 623824 Country of ref document: AT Kind code of ref document: T Effective date: 20150202 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20130724 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150202 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20130724 |
|
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: 20130724 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: 20100202 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 8 |
|
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: 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: 20130724 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 502010004121 Country of ref document: DE Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH, DE Free format text: FORMER OWNER: CONTINENTAL TEVES AG & CO. OHG, 60488 FRANKFURT, DE |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20230221 Year of fee payment: 14 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 502010004121 Country of ref document: DE Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH, DE Free format text: FORMER OWNER: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH, 30165 HANNOVER, DE |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240229 Year of fee payment: 15 |