EP3968600B1 - Steuerung einer kommunikation zwischen einem fahrzeug und einer backend-vorrichtung - Google Patents

Steuerung einer kommunikation zwischen einem fahrzeug und einer backend-vorrichtung Download PDF

Info

Publication number
EP3968600B1
EP3968600B1 EP20195710.7A EP20195710A EP3968600B1 EP 3968600 B1 EP3968600 B1 EP 3968600B1 EP 20195710 A EP20195710 A EP 20195710A EP 3968600 B1 EP3968600 B1 EP 3968600B1
Authority
EP
European Patent Office
Prior art keywords
vehicle
control unit
electronic control
message
timer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP20195710.7A
Other languages
English (en)
French (fr)
Other versions
EP3968600A1 (de
Inventor
Frederik Bas
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.)
Volkswagen AG
Original Assignee
Volkswagen AG
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 Volkswagen AG filed Critical Volkswagen AG
Priority to EP20195710.7A priority Critical patent/EP3968600B1/de
Priority to US17/469,459 priority patent/US20220086943A1/en
Publication of EP3968600A1 publication Critical patent/EP3968600A1/de
Application granted granted Critical
Publication of EP3968600B1 publication Critical patent/EP3968600B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
    • H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • the invention is related to a method for controlling a communication between a vehicle and at least one backend device in a vehicle-to-cloud-system, especially from the vehicle side of the system, according to the independent method claim. Further, the invention is related to an electronic control unit according to the independent device claim. Furthermore, the invention is related to a vehicle comprising a corresponding electronic control unit according to the second independent device claim. Moreover, the invention is related to a computer program product for a corresponding method according to the independent product claim.
  • Vehicle communication systems using a publish-subscribe messaging protocol are basically known, for example from DE 10 2018 130 216 A1 and CN 106 856 502 A .
  • a vehicle By establishing a connection between a vehicle and a backend device, for example cloud server, the vehicle sends a connect message to the backend device with a defined keep alive timer. If the open connection is not used for a time set with the keep alive timer, the vehicle will generate a ping request message and expect to receive a ping response message from the backend device to keep the connection open. Ping messages have no useful content and cause non-useful traffic for the network.
  • CN 106 161 586 B discloses a server-vehicle communication architecture wherein the server sets a keep alive timeout longer than a timeout set by the vehicle in order to enable the maintenance of an open connection between vehicle and server for the issuing of commands from server to vehicle. However, the release of the connection is not prevented if connection is command-idle for a longer period than the timeout set by the server.
  • the aim of the present invention is to provide a method, as claimed in claim 1, for controlling a communication between a vehicle and at least one backend device in a vehicle-to-cloud-system, especially from the vehicle side of the system, with improved connectivity.
  • the aim of the present invention is especially to provide a method for controlling a communication between a vehicle and at least one backend device in a vehicle-to-cloud-system, which enables to keep the connection between the vehicle and the backend device open in an easy, but useful way, preferably without non-useful traffic for the network.
  • the aim of the invention is to provide a corresponding electronic control unit for the vehicle, as claimed in claim 8, a corresponding vehicle according to claim 12 and a related computer program product as claimed in claim 14 for the inventive method. Preferred embodiments are covered by the appended dependent claims.
  • Fig. 1 a schematic design of an electronic control unit within the meaning of the invention.
  • Figure 1 serves to show different aspects of the invention, such as a method for controlling a communication between a vehicle 10 and at least one backend device 20 (for example a cloud server) in a vehicle-to-cloud-system, a corresponding electronic control unit ECU, a corresponding vehicle 10 (not shown in detail for reasons of simplicity only) as well as a corresponding computer program product. Furthermore, a corresponding vehicle-to-cloud-system may be also provided.
  • Embodiments of the method for controlling a communication between the vehicle 10 and the at least one backend device 20 comprise the following.
  • at least one (network) connection D is established between the vehicle 10 and the at least one backend device 20 with a keep alive timer Tkat, especially by an online connectivity unit OCU of an electronic control unit ECU of the vehicle 10 sending a connect and/or subscribe message m to the backend device 20.
  • a timer T (may also be called keep open timer) is set smaller (or less) than or equal to the keep alive timer Tkat.
  • a message m is sent from the vehicle 10 to the at least one backend device 20.
  • the message contains a payload pl.
  • the message m may be a connect, subscribe or a publish message-
  • the message m is sent, if no communication has occurred between the vehicle 10 and the at least one backend device 20 within the timer T, that is when no messages m between the vehicle 10 and the at least one backend device 20 were sent within the timer T, in order to keep the connection D open.
  • the idea is to provide a useful message m containing a payload pl to keep the connection D open, without waste to the network with non-useful messages. That is, the connection D is kept op with messages with payload without using messages sent for the sole purpose to keep the connection upon instead or additionally.
  • the useful message m is sent just inside the keep alive timer Tkat as maximum.
  • a timer T is set.
  • the timer T may be set as the keep alive timer Tkat minus 1 second.
  • the timer T may be set as a time in a range of 0,5 to 0,99, especially 0,7 to 0,95, preferably 0,9 times the time of the keep alive timer Tkat.
  • an easy mechanism to set a timer T may be provided.
  • a user may set the timer T manually, for example by operating an input device, for example in the form of a display device at a vehicle dashboard 12.
  • the timer T may be set automatically by an electronic control unit ECU of the vehicle 10.
  • automatic setting of the timer T may be provided.
  • a confirmation and/or adjustment possibility of the automatically set timer T may be provided for a user of the vehicle 10, for example by operating an input device, for example in the form of a display device at a vehicle dashboard.
  • a verification may be carried out, if sending is possible, wherein especially a communication test to the backend device 20 may be carried out.
  • the message m may be published by a vehicle state provider VSP.
  • the vehicle state provider VSP may be connected to a power manager PM of the vehicle 10.
  • the added information to the message m cannot be too large. No answer to such message m is needed.
  • the backend device 20 may optimize many online services for the vehicle 10.
  • the payload pl in the message m may contain application-specific data from at least one vehicle device MOD.
  • the message m may be published by at least one of the following vehicle devices MOD:
  • the part of the electronic control unit ECU shown in figure 1 may also be called online connectivity unit OCU.
  • the electronic control unit ECU has a memory M, in which a program code is stored, and a computing unit CU, wherein when carrying out the program code by the computing unit CU, a method may be performed as described above.
  • the electronic control unit ECU comprises a vehicle state provider VSP configured to provide the payload pl in the message m. Additionally, the electronic control unit ECU comprises a power manager PM connected to the vehicle state provider VSP. Nevertheless, the invention may provide that the electronic control unit ECU comprises a wakeup manager WUM, whereas the wakeup manager WUM may be deactivated or inactive, when the method according to one of the proceeding claims is performed. Thus, the wakeup manager WUM may provide a fail back option to reactivate the connection D by sending a PING request message to the at least one corresponding backend device 20.
  • the electronic control unit ECU may provide connectivity subunits C, so called Message Queuing Telemetry Transport (MQTT) clients, for the vehicle devices MOD.
  • MQTT Message Queuing Telemetry Transport
  • the backend device 20 may then be called MQTT server.
  • Figure 1 shows only schematically the example of one vehicle device MOD and one backend device 20, wherein a plurality of vehicle devices MOD and a variety of backend devices 20 may be provided within the meaning of the invention.
  • the vehicle devices MOD may subscribe to a publish-subscribe messaging environment pub/sub using different topics t provided by the at least one backend device 20 or even various backend devices 20.
  • the publish-subscribe messaging environment pub/sub may use for example, the MQTT protocol.
  • the at least one backend device 20 or even various backend devices 20 may provide mobile online services (or in other words cloud-computing applications) for the vehicle devices MOD.
  • the electronic control unit ECU may comprise a managing connecting gateway GP for routing the messages m between a plurality of vehicle devices MOD and a variety of backend devices 20, whereas the message m is transmitted by the managing connecting gateway GP to the variety of backend devices 20.
  • the managing connecting gateway GP may provide bridges to the various backend devices 20 for different vehicle devices MOD according to the topics t to which the vehicle devices MOD are subscribed.
  • the electronic control unit ECU may comprise a project connecting gateway PGP (for example in form of local MQTT broker of Mosquitto type) connected to the plurality of the connectivity subunits C over corresponding communication lines L.
  • the project connecting gateway PGP is connected to the a managing connecting gateway GP over a communication line TLS by means of a TLS-Server TLS-S.
  • the project connecting gateway PGP may provide a MQTT bridge MB to the managing connecting gateway GP.
  • the managing connecting gateway GP may use a manifest manager MM and an MQTT manifest manager interface MMI to identify the connectivity subunits C connected to the project connecting gateway PGP. Further, the managing connecting gateway GP may use a service router SR to translate the topics t to which the connectivity subunits C are subscribed.
  • the managing connecting gateway GP may comprise a subscription mapping repository Map for the different topics t provided by various backend devices X, Y, Z and for the connectivity subunits C subscribed to the different topics t.
  • the managing connecting gateway GP may address messages m using a topic routing to distribute the messages m to the right backend device 20. If a message m published by one vehicle device MOD has a topic t that is supported by multiple backend devices 20, then this message m may be correspondingly forwarded to matching backend devices 20. Also, if a message m published by a backend device 20 has a topic t to which multiple vehicle devices MOD are subscribed, this message m may be correspondingly forwarded to matching vehicle devices MOD.
  • the managing connecting gateway GP may comprise a proxy server SGP to translate the messages m and/or to provide authentication and/or authorization between the plurality of the vehicle device MOD and the various backend devices 20.
  • the invention may foresee that the managing connecting gateway GP decrypts the messages m for purposes of routing to the various backend devices 20. After assigning messages m to the corresponding backend devices 20, the messages m may be encrypted again.
  • the message m containing the payload pl will be transmitted by the managing connecting gateway GP to all backend devices 20 to keep all bridges or all connections D to all backend devices 20 open.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Medical Informatics (AREA)
  • Cardiology (AREA)
  • Small-Scale Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Traffic Control Systems (AREA)

Claims (14)

  1. Verfahren zum Steuern einer Kommunikation zwischen einem Fahrzeug (10) und mindestens einer Backend-Vorrichtung (20) in einem Fahrzeug-zu-Cloud-System, das Verfahren umfassend:
    - Herstellen einer Verbindung (D) zwischen dem Fahrzeug (10) und der mindestens einen Backend-Vorrichtung (20) mit einem Keep-Alive-Zeitgeber (Tkat);
    - Einstellen eines Zeitgebers (T) geringer oder gleich dem Keep-Alive-Zeitgeber (Tkat); und
    - Senden einer Nachricht (m), die eine Nutzlast (pl) von dem Fahrzeug (10) enthält, an die mindestens eine Backend-Vorrichtung (20), falls innerhalb des Zeitgebers (T) keine Kommunikation zwischen dem Fahrzeug (10) und der mindestens einen Backend-Vorrichtung (20) stattgefunden hat, um die Verbindung (D) offen zu halten,
    - wobei
    - der Zeitgeber (T) manuell durch einen Benutzer des Fahrzeugs (10) und/oder automatisch durch eine elektronische Steuereinheit (ECU) des Fahrzeugs (10) eingestellt wird.
  2. Verfahren nach Anspruch 1,
    dadurch gekennzeichnet, dass
    die Nutzlast (pl) in der Nachricht (m) einen Fahrzeugzustand (Start, Stopp) enthält und/oder die Nachricht (m) durch einen Fahrzeugzustandsanbieter (VSP) veröffentlicht wird.
  3. Verfahren nach Anspruch 1 oder 2,
    dadurch gekennzeichnet, dass
    die Nutzlast (pl) in der Nachricht (m) anwendungsspezifische Daten von mindestens einer Fahrzeugvorrichtung (MOD) enthält und/oder die Nachricht (m) durch mindestens eine der folgenden Fahrzeugvorrichtungen (MOD) veröffentlicht wird:
    - Sensorvorrichtung,
    - Sicherheitsvorrichtung,
    - Umgebungsvorrichtung,
    - Informationsvorrichtung,
    - Unterhaltungsvorrichtung und/oder
    - Komfortvorrichtung.
  4. Verfahren nach einem der vorstehenden Ansprüche,
    dadurch gekennzeichnet, dass
    der Zeitgeber (T) als der Keep-Alive-Zeitgeber (Tkat) minus 1 Sekunde eingestellt wird oder der Zeitgeber (T) auf eine Zeit in einem Bereich von 0,5 bis 0,99, insbesondere 0,7 bis 0,95, vorzugsweise 0,9 mal der Zeit des Keep-Alive-Zeitgebers (Tkat) eingestellt wird.
  5. Verfahren nach einem der vorstehenden Ansprüche,
    dadurch gekennzeichnet, dass
    der Zeitgeber (T) manuell durch einen Benutzer des Fahrzeugs (10) durch ein Bedienen einer Eingabevorrichtung, vorzugsweise einer Anzeigevorrichtung an einem Fahrzeug-Armaturenbrett des Fahrzeugs (10), eingestellt wird.
  6. Verfahren nach dem vorstehenden Anspruch,
    dadurch gekennzeichnet, dass
    einem Benutzer des Fahrzeugs (10) eine Bestätigungs- und/oder Anpassmöglichkeit des Zeitgebers (T) bereitgestellt wird, insbesondere durch das Bedienen einer Eingabevorrichtung, beispielsweise einer Anzeigevorrichtung an einem Fahrzeug-Armaturenbrett, des Fahrzeugs (10).
  7. Verfahren nach einem der vorstehenden Ansprüche,
    dadurch gekennzeichnet, dass
    das Verfahren ferner, vor dem Senden der Nachricht, ein Ausführen einer Überprüfung umfasst, ob das Senden möglich ist, wobei insbesondere ein Kommunikationstest mit der Backend-Vorrichtung (20) ausgeführt wird.
  8. Elektronische Steuereinheit (ECU), umfassend:
    einen Speicher (M), in dem ein Programmcode gespeichert ist, und
    eine Recheneinheit (CU), wobei bei dem Ausführen des Programmcodes durch die Recheneinheit (CU) ein Verfahren nach einem der vorstehenden Ansprüche durchgeführt wird.
  9. Elektronische Steuereinheit (ECU) nach dem vorstehenden Anspruch,
    dadurch gekennzeichnet, dass
    die elektronische Steuereinheit (ECU) einen Fahrzeugzustandsanbieter (VSP) umfasst, der konfiguriert ist, um die Nutzlast (pl) in der Nachricht (m) bereitzustellen,
    wobei insbesondere die elektronische Steuereinheit (ECU) einen Leistungsverwalter (PM) umfasst, der mit dem Fahrzeugzustandsanbieter (VSP) verbunden ist.
  10. Elektronische Steuereinheit (ECU) nach einem der vorstehenden Ansprüche 8 oder 9,
    dadurch gekennzeichnet, dass
    die elektronische Steuereinheit (ECU) einen Wakeup-Verwalter (WUM) umfasst,
    wobei der Wakeup-Verwalter (WUM) konfiguriert ist, um deaktiviert oder inaktiv zu sein, falls das Verfahren nach einem der Ansprüche 1 bis 7 durchgeführt wird,
    und wobei der Wakeup-Verwalter (WUM) konfiguriert ist, um die Verbindung (D) durch das Senden einer PING-Anforderungsnachricht an die mindestens eine entsprechende Backend-Vorrichtung (20) zu reaktivieren.
  11. Elektronische Steuereinheit (ECU) nach einem der vorstehenden Ansprüche 8 bis 10,
    dadurch gekennzeichnet, dass
    die elektronische Steuereinheit (ECU) ein verwaltendes Verbindungs-Gateway (GP) zum Weiterleiten von Nachrichten zwischen einer Vielzahl von Fahrzeugvorrichtungen (MOD) und einer Vielzahl von Backend-Vorrichtungen (20) umfasst,
    wobei das verwaltende Verbindungs-Gateway (GP) konfiguriert ist, um die Nachricht an die Vielzahl von Backend-Vorrichtungen (20) zu übertragen.
  12. Fahrzeug (10), umfassend eine elektronische Steuereinheit (ECU) nach einem der vorstehenden Ansprüche 8 bis 11.
  13. Fahrzeug (10) nach dem vorstehenden Anspruch,
    dadurch gekennzeichnet, dass
    das Fahrzeug ferner eine Vielzahl von Fahrzeugvorrichtungen (MOD) umfasst, wobei die Vielzahl von Fahrzeugvorrichtungen (MOD) für die Verbindung mit der mindestens einen entsprechenden Backend-Vorrichtung (20) mit der elektronischen Steuereinheit (ECU) kommunikativ gekoppelt ist, wobei die Vielzahl von Fahrzeugvorrichtungen mindestens eine der folgenden Vorrichtungen umfasst:
    - Sensorvorrichtung,
    - Sicherheitsvorrichtung,
    - Umgebungsvorrichtung,
    - Informationsvorrichtung,
    - Unterhaltungsvorrichtung und/oder
    - Komfortvorrichtung.
  14. Computerprogrammprodukt, umfassend Anweisungen, die, wenn das Programm durch einen Computer ausgeführt wird, bewirken, dass der Computer ein Verfahren nach einem der Ansprüche 1 bis 7 ausführt.
EP20195710.7A 2020-09-11 2020-09-11 Steuerung einer kommunikation zwischen einem fahrzeug und einer backend-vorrichtung Active EP3968600B1 (de)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20195710.7A EP3968600B1 (de) 2020-09-11 2020-09-11 Steuerung einer kommunikation zwischen einem fahrzeug und einer backend-vorrichtung
US17/469,459 US20220086943A1 (en) 2020-09-11 2021-09-08 Method for controlling a communication between a vehicle and a backend device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP20195710.7A EP3968600B1 (de) 2020-09-11 2020-09-11 Steuerung einer kommunikation zwischen einem fahrzeug und einer backend-vorrichtung

Publications (2)

Publication Number Publication Date
EP3968600A1 EP3968600A1 (de) 2022-03-16
EP3968600B1 true EP3968600B1 (de) 2024-11-06

Family

ID=72473457

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20195710.7A Active EP3968600B1 (de) 2020-09-11 2020-09-11 Steuerung einer kommunikation zwischen einem fahrzeug und einer backend-vorrichtung

Country Status (2)

Country Link
US (1) US20220086943A1 (de)
EP (1) EP3968600B1 (de)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150281374A1 (en) * 2014-03-31 2015-10-01 Ford Global Technologies, Llc Remote vehicle connection status
CN106161586A (zh) * 2016-06-07 2016-11-23 四川长虹电器股份有限公司 实现智能终端对车机的长轮询控制系统及方法
CN106856502A (zh) * 2016-12-02 2017-06-16 北京京东尚科信息技术有限公司 无人车控制方法、无人车、服务器和无人车系统

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6311186B1 (en) * 1998-02-20 2001-10-30 Priority Call Management, Inc. Telecommunications switching system utilizing a channelized database access mechanism
US6760775B1 (en) * 1999-03-05 2004-07-06 At&T Corp. System, method and apparatus for network service load and reliability management
US7706299B2 (en) * 2004-10-13 2010-04-27 Cisco Technology, Inc. Upstream bandwidth estimation
US7899921B2 (en) * 2004-12-08 2011-03-01 Microsoft Corporation Verifying and maintaining connection liveliness in a reliable messaging for web services environment
US20070274233A1 (en) * 2006-05-25 2007-11-29 Amnon Ptashek Method, apparatus and system for multi peer to peer services
US7885616B2 (en) * 2006-08-16 2011-02-08 Research In Motion Limited Method and system for coordinating necessary radio transmission events with unrelated opportunistic events to optimize battery life and network resources
US8023432B2 (en) * 2007-03-12 2011-09-20 Microsoft Corporation Cost reduction of NAT connection state keep-alive
US20100110899A1 (en) * 2008-10-31 2010-05-06 Vanzante Craig A Stressing a network device
US9313800B2 (en) * 2009-06-23 2016-04-12 Nokia Technologies Oy Method and apparatus for optimizing energy consumption for wireless connectivity
US8335853B2 (en) * 2009-12-17 2012-12-18 Sonus Networks, Inc. Transparent recovery of transport connections using packet translation techniques
US8736438B1 (en) * 2012-08-15 2014-05-27 Google Inc. Computing device as a vehicle key
US9350550B2 (en) * 2013-09-10 2016-05-24 M2M And Iot Technologies, Llc Power management and security for wireless modules in “machine-to-machine” communications
GB2512501A (en) * 2014-02-25 2014-10-01 Cambridge Silicon Radio Ltd Packet identification
EP3148431A4 (de) * 2014-05-16 2018-04-04 Masdar Institute of Science and Technology Selbstangetriebene mikrosensoren für räumliche und zeitliche in-situ-messungen und verfahren zur verwendung davon bei der hydraulischen frakturierung
US10104454B2 (en) * 2015-10-05 2018-10-16 Parkifi, Inc. Parking data aggregation and distribution
US10672242B2 (en) * 2015-10-16 2020-06-02 Vivint, Inc. Proximity based security monitoring
KR102715376B1 (ko) * 2016-12-30 2024-10-11 인텔 코포레이션 라디오 통신을 위한 방법 및 디바이스
CN107819642B (zh) * 2017-09-15 2020-02-28 中国科学院计算技术研究所 基于分布式的自适应心跳方法和系统
US20190173951A1 (en) * 2017-12-01 2019-06-06 GM Global Technology Operations LLC Vehicle communication using publish-subscribe messaging protocol
US11294949B2 (en) * 2018-09-04 2022-04-05 Toyota Connected North America, Inc. Systems and methods for querying a distributed inventory of visual data
US11188099B2 (en) * 2019-04-25 2021-11-30 GM Global Technology Operations LLC Method, system and apparatus for an autonomous routing algorithm with a failsafe provision at a final drop-off location
US11827237B2 (en) * 2019-12-27 2023-11-28 Toyota Connected North America, Inc. Systems and methods for real-time crash detection using telematics data
US11115482B1 (en) * 2020-03-31 2021-09-07 Xevo Inc. System and method for correlating keep-alive connection communications with unary connection communications
US11622414B2 (en) * 2020-07-17 2023-04-04 Qualcomm Incorporated Enhanced connection release techniques for wireless communications systems

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150281374A1 (en) * 2014-03-31 2015-10-01 Ford Global Technologies, Llc Remote vehicle connection status
CN106161586A (zh) * 2016-06-07 2016-11-23 四川长虹电器股份有限公司 实现智能终端对车机的长轮询控制系统及方法
CN106856502A (zh) * 2016-12-02 2017-06-16 北京京东尚科信息技术有限公司 无人车控制方法、无人车、服务器和无人车系统

Also Published As

Publication number Publication date
US20220086943A1 (en) 2022-03-17
EP3968600A1 (de) 2022-03-16

Similar Documents

Publication Publication Date Title
EP3726806B1 (de) Verfahren zur fernsteuerung eines fahrzeugs auf der basis einer intelligenten vorrichtung
CN100588175C (zh) 在不对称路由网络中处理通信流
US20190173951A1 (en) Vehicle communication using publish-subscribe messaging protocol
US20150310378A1 (en) System Interfacing a Fleet Management System and a Ride Sharing System
US10206015B2 (en) System and method for vehicle data communication
WO2019021995A1 (ja) 通信装置、通信方法及び通信システム
CN110109458B (zh) 车载自动驾驶调度系统、方法、设备及存储介质
US20140321366A1 (en) Method for transmitting messages from a data network to a vehicle and server device for a data network
Ojanperä et al. Use cases and communications architecture for 5G-enabled road safety services
US20170148321A1 (en) Method for Operating a Vehicle, and Motor Vehicle
EP3293893B1 (de) Bodenausrichtung von flugzeugdatenverbindungen
EP3968602B1 (de) Online-konnektivitätseinheit in einer elektronischen steuereinheit eines fahrzeugs, zugehöriges verfahren und zugehöriges computerprogrammprodukt
Hayes et al. End to end vanet/iot communications a 5g smart cities case study approach
EP3968600B1 (de) Steuerung einer kommunikation zwischen einem fahrzeug und einer backend-vorrichtung
CN1582542B (zh) 向移动平台提供网络地址的系统和方法
US20240185645A1 (en) A real time monitoring module for a vehicle
US9299250B1 (en) Processing requests to establish communication sessions in a mobile vehicle communication system
Yacchirema et al. Onem2m based-interworking architecture for heterogeneous devices interoperability in iot
US11997567B2 (en) V2X network communication
US10756954B2 (en) Information processing system, relay device, auxiliary relay device, management device, method, and storage medium
KR20190117268A (ko) 메시지 서버 및 이를 포함하는 메시지 처리 장치
JP2008547292A (ja) 車両ベースのコンテンツ表示システム
CA2398267A1 (en) Optical communication systems including network management systems, apparatuses, and methods
JP5911405B2 (ja) 列車通信システムおよび列車通信方法
KR101846791B1 (ko) 이동통신망을 이용한 모노레일 원격 운행관리 방법 및 시스템

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

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

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

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

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220916

RBV Designated contracting states (corrected)

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

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20231107

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Free format text: PREVIOUS MAIN CLASS: H04L0029080000

Ipc: H04L0067125000

Ref document number: 602020040714

Country of ref document: DE

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 67/55 20220101ALN20240404BHEP

Ipc: H04L 67/141 20220101ALI20240404BHEP

Ipc: H04L 67/145 20220101ALI20240404BHEP

Ipc: H04L 67/125 20220101AFI20240404BHEP

INTG Intention to grant announced

Effective date: 20240422

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602020040714

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20241106

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

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

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

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

Ref country code: NL

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

Effective date: 20241106

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1740646

Country of ref document: AT

Kind code of ref document: T

Effective date: 20241106

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

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

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

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

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

Ref country code: LV

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

Effective date: 20241106

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

Ref country code: AT

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

Effective date: 20241106

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

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

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

Ref country code: RS

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

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

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

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

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

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

Ref country code: RO

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

Effective date: 20241106

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602020040714

Country of ref document: DE

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

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

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

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

Ref country code: DE

Payment date: 20250930

Year of fee payment: 6

26N No opposition filed

Effective date: 20250807

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

Ref country code: FR

Payment date: 20250925

Year of fee payment: 6

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

Free format text: CASE NUMBER: UPC_APP_0014665_3968600/2025

Effective date: 20251125