EP2816781A1 - Comportement sur la base d'identification de dispositifs appariés - Google Patents

Comportement sur la base d'identification de dispositifs appariés Download PDF

Info

Publication number
EP2816781A1
EP2816781A1 EP13173115.0A EP13173115A EP2816781A1 EP 2816781 A1 EP2816781 A1 EP 2816781A1 EP 13173115 A EP13173115 A EP 13173115A EP 2816781 A1 EP2816781 A1 EP 2816781A1
Authority
EP
European Patent Office
Prior art keywords
mobile device
ivis
paired
behaviour
identity information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP13173115.0A
Other languages
German (de)
English (en)
Other versions
EP2816781B1 (fr
Inventor
Sanjai Nathwani
Charles Angus Duffy
Devendra JUGDEO
Allan Jeffrey Stirrett
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.)
BlackBerry Ltd
Original Assignee
QNX Software Systems Ltd
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 QNX Software Systems Ltd filed Critical QNX Software Systems Ltd
Priority to EP21152419.4A priority Critical patent/EP3829140B1/fr
Priority to ES21152419T priority patent/ES2951283T3/es
Priority to EP13173115.0A priority patent/EP2816781B1/fr
Publication of EP2816781A1 publication Critical patent/EP2816781A1/fr
Application granted granted Critical
Publication of EP2816781B1 publication Critical patent/EP2816781B1/fr
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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • 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/08—Protocols specially adapted for terminal emulation, e.g. Telnet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/60—Substation equipment, e.g. for use by subscribers including speech amplifiers
    • H04M1/6033—Substation equipment, e.g. for use by subscribers including speech amplifiers for providing handsfree use or a loudspeaker mode in telephone sets
    • H04M1/6041—Portable telephones adapted for handsfree use
    • H04M1/6075—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle
    • H04M1/6083—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle by interfacing with the vehicle audio system
    • H04M1/6091—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle by interfacing with the vehicle audio system including a wireless interface
    • 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/48—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for in-vehicle communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Definitions

  • the present disclosure relates to pairing of electronic devices and in particular to behaviour of a mobile device when connected to another paired electronic device.
  • the pairing of mobile devices, such as smartphones or tablet devices, with other electronic devices, such as in-vehicle infotainment systems, can provide hands-free access, data access, and communication functions from the mobile device through the vehicle control interfaces.
  • the communications protocols between the mobile device and in-vehicle infotainment system can enable a range of resources to be shared and accessed.
  • the user of the vehicle may still utilize the mobile device while in the vehicle and not necessarily be aware of the device pairing with the in-vehicle infotainment system.
  • the user may not be aware of the services of the mobile device that are available via the in-vehicle infotainment system.
  • a mobile device comprising a processor; and a memory containing instructions which when executed by a processor performing the steps of method claims 1 to 13.
  • a non-transitory computer-readable memory having computer readable code embodied, the code when executed by a processor performing the step of method claims 1 to 13.
  • Figure 1 shows a representation of a paired in-vehicle information and entertainment (infotainment) system 150 or head unit and a mobile device 100.
  • the in-vehicle infotainment system 150 can provide rear-seat entertainment (such as movies, games, TV, social networking, etc.), navigation, audio playback (AM/FM, CD, DVD, HDD, satellite radio, internet radio), location-based services and external communications services and is accessed via control interfaces integrated in the vehicle or a touch-screen interface.
  • the mobile device 100 such as a smartphone or tablet computing device, can pair with an in-vehicle infotainment system (IVIS) 150 to provide data connectivity between devices and enable services or functions of the IVIS 150.
  • the mobile device 100 may be built on a mobile operating system providing advanced computing capability and connectivity for communications, accessing content and playback of media content via a wireless network.
  • the pairing of the mobile device 100 to the IVIS 150 provides a secure communication connection to enable services or functionality of the mobile device 100 to be accessed via the IVIS 150.
  • Services such as SMS, MMS, voice, video, e-mail and access content stored on the mobile device 100 or accessible by the mobile device via a network interface, in various formats can be provided.
  • the content formats may be such as, but not limited to, AAC, AMR, FLAC, MP3, M4A, OGG, WMA, WAV, Video, 3GP, AVI, ASF, MP4, MOV and WMV.
  • the pairing may be performed by a wireless technology such as Bluetooth® (Bluetooth is a trademark of the Bluetooth SIG of Kirkland, WA) or Wi-Fi® (Wi-Fi is a registered trademark of Wi-Fi Alliance of Austin, TX) or by wired technology such as Universal Serial Bus (USB), FirewireTM, IEEE 1394, or ThunderboltTM connections implementing a pairing protocol.
  • Bluetooth® Bluetooth is a trademark of the Bluetooth SIG of Kirkland, WA
  • Wi-Fi® Wi-Fi is a registered trademark of Wi-Fi Alliance of Austin, TX
  • wired technology such as Universal Serial Bus (USB), FirewireTM, IEEE 1394, or ThunderboltTM connections implementing a pairing protocol.
  • USB Universal Serial Bus
  • FirewireTM FirewireTM
  • IEEE 1394 IEEE 1394
  • ThunderboltTM connections implementing a pairing protocol.
  • ThunderboltTM connections implementing a pairing protocol.
  • the mobile device 100 obtains identification information from the in-vehicle information system 150 which may be related to the type of vehicle
  • the device information in the device identifier is not sufficiently unambiguous to identify the vehicle during pairing the mobile device 100, but can be identified as being associated with a vehicle, selection options can be provided for the user to further identify the vehicle (e.g. by providing a pick list) to disambiguate the identity.
  • the paired-device identity information Once the paired-device identity information is known it can be stored on the mobile device 100 and used to determine behaviour of the mobile device 100 on future pairing with the in-vehicle communication system 150.
  • an information display screen can be presented on the mobile device 100 to identify that a connection has been established and identify services that are provided between the IVIS 150 and the mobile device 100.
  • the information display screen may be in the form of a dismissible splash screen or a lock screen to discourage interaction with the mobile device 100 while connected to the IVIS 150 thereby potentially mitigating driver distraction.
  • the information display can also include a list of services available for interacting with the mobile device 100 or supported by the vehicle.
  • information from applications that can be executed on the device or data received from the vehicle such as telematics received from the vehicle can be displayed.
  • the pairing of the mobile device 100 with the IVIS 150 and the paired-device identity information can also be associated with profile defining pairing behaviour.
  • the profile may for example be associated with a label such as "My Car" on the mobile device 100.
  • the mobile device 100 comprises a processor 102 coupled to a memory 104.
  • the memory 104 contains instructions for providing an operating system, databases, and communication functions such as pairing to the IVIS 150 by establishing a connection by one or more interfaces such as a wireless transceiver 106 or wired interface 108.
  • the memory may also provide instructions for storing or retrieving or data, applications and media content.
  • the wireless transceiver 106 may support one or more personal area network (PAN) technologies such as Bluetooth®, near field communications (NFC), or local area networks (LAN) based technologies such as IEEE 802 family of technologies such as Wi-Fi®.
  • PAN personal area network
  • NFC near field communications
  • LAN local area networks
  • the mobile device 100 also provides a display 110, which can provide a touch-sensitive input to the operating system.
  • a wide area network (WAN) wireless transceiver 116 is provided to access mobile networks GSM, EDGE, UMTS/UTRA, 3G (3GPP), and 4G (LTE) and beyond. Audio input and output functions 112 such as speaker and microphone are incorporated into the mobile device 100.
  • a Global Position System (GPS) or Global Navigation Satellite System (GNSS) receiver 114 may be provided for location services and navigation.
  • GPS Global Position System
  • GNSS Global Navigation Satellite System
  • the IVIS 150 comprises a processor 152 coupled to a memory 154.
  • the memory 154 contains instructions for providing an operating system and communication functions such as pairing to the mobile device 100 by establishing a connection by one or more interfaces such as a wireless transceiver 156 or wired interface 158.
  • the wireless transceiver 156 may support one or more personal area networks (PAN) technologies such as Bluetooth®, NFC, or local area networks (LAN) based technologies such as IEEE 802 based Wi-Fi®.
  • PAN personal area networks
  • LAN local area networks
  • the IVIS 150 also provides a display 160, which can provide a touch-sensitive input or may also have physical interfaces as a button or dials.
  • a Global Position System (GPS) or Global Navigation Satellite System (GNSS) receiver 164 may be provided for location services and navigation.
  • GPS Global Position System
  • GNSS Global Navigation Satellite System
  • Audio input and output functions 162 such as speaker and microphone are also incorporated.
  • the IVIS 150 can provide communications functions from the mobile device 100 once paired, for example hands-free call access, media playback, short message service (SMS) functions can be interfaced through the IVIS 150.
  • SMS short message service
  • Figure 2 shows a representation of display screen on a mobile device 100 when connected to the IVIS 150.
  • the display screen 200 is generated when a device identifier provided from the IVIS 150 matches to a defined behaviour or behaviour profile on the mobile device 100.
  • the screen 200 that is displayed on the mobile device 100 while connected to the IVIS 150 presents information relevant to user in regards to the device pairing.
  • One or more items may be displayed such as but not limited to an automobile manufacturer 202 identifier such as a logo, a list of services 204 that are provided by the pairing, or identification of the services that are connected or are supported but not currently connected.
  • Applications or services 206 that may be provided by the mobile device 100 may also be identified, for example telemetry, logging functions, or mapping functions that are integrated with the IVIS 150 functions.
  • the services that may be identified may include, for example, SMS, MMS, voice control, hands-free, message download, media library accesses, DNLA support, MirrorlinkTM, etc.
  • the screen of the mobile device 100 may be locked, which can be identified by an icon 210 to limit user access to functions of the mobile device 100 when in the vehicle.
  • the screen 200 may be dismissed by a touch or gesture input.
  • the locking of the display 110 may alternatively only occur when the vehicle is moving therefore selectively enabling access to functions directly on the mobile device 100 when the vehicle is in park or stopped.
  • the IVIS 150 may provide information regarding the operation of the vehicle to the mobile device 100 which may result in different aspects to be displayed on the mobile device 100 based upon the associated behaviour profile.
  • the display screen 200 formatting and content can also be determined by user configuration, provided by the mobile device operating system or the auto manufacturer as a default behaviour.
  • Figure 3 shows a representation of a system for retrieving information for display on the mobile device 100 in relation to the connected IVIS 150.
  • device identifiers 302 are exchanged to uniquely identify each device in establishing the communications link.
  • the device identifiers 302 are subsequently used to establish connections between the devices and are stored on each device.
  • the device identifier 302 may include additional information to identify the type of device, a manufacturer or product identifier, software features, and version information to enable each device to configure appropriately or may only be discernible to the fact that a vehicle is associated with the device identifier 302.
  • the mobile device 100 may provide the device identifier 302 provided by the IVIS 150 to a server 310 via a wireless network 300 to request associated or corresponding configuration or behaviour profile, or the mobile device 100 may maintain a database which can be periodically updated.
  • the behaviour profiles can be associated with individual or groups of identifier and may also be associated with information such as for example, icons, logos or graphics, display formatting options, locking behaviours and services that can be provided by the IVIS 150 and the mobile device 100.
  • the mobile device 100 may also be configured to provide default behaviour based upon identification that a particular device identifier 302 is associated with a vehicle when connected.
  • Figure 4 shows a representation of a display screen on a mobile device 100 for receiving further vehicle identification during the initial pairing process.
  • the IVIS 150 may be able to identify that the received device identifier 302 is associated with a vehicle.
  • the paired device 402 may be identified based upon the type of connection provided; for example, 402 identifies that the device is paired to 'Car1'.
  • the device identifier 302 may provide additional levels of detail, for example identify the make, year of manufacture, brand, model and option packages is so implemented in the identifier.
  • additional pairing screens or pop-ups such as in Figure 4B and 4C may be displayed to allow the user to provide additional selection input.
  • additional selections may be presented. For example if the IVIS 150 is used by multiple vehicle manufacturers, selections as shown in screen 410 may be provided to narrow the vehicle manufacturer. If the vehicle manufacturer is known further details such as year, model, and package as shown in screen 412 may be presented. The screens 410 and 412 may be presented during the initial pairing process or on subsequent connections as further behaviour profiles are generated that may require the information or as additional information is provided.
  • the in-vehicle infotainment device 150 can then be associated with one or more behaviours on the mobile device 100.
  • the device identifier 302 and associated vehicle may then be labelled, in this example as 'My Car', providing identification that the mobile device 100 has a behaviour associated with the vehicle when connected. If two device identifiers 302 are similar, additional device identification information such the device identifier address (e.g. media access control (MAC) address) may be utilized to distinguish between the two paired devices and enable behaviour to be tailored to individual vehicles.
  • MAC media access control
  • Figure 5 shows a method of mobile device 100 behaviour based on paired device identification.
  • the method 500 is provided on the mobile device 100 when connecting with an IVIS 150.
  • the device identifiers 302 can associated with identity information that was provided during pairing such as but not limited to device name, device class, list of services, technical information (for example: device features, manufacturer, specification used, clock offset) such as defined in the Bluetooth® specification to enable the communication channel to be configured appropriately. This information may be maintained by each device to enable subsequent network connections as required to remember configuration parameters and enable automatic connection.
  • the mobile device 100 can utilize the device identifier 302 to determine how it will behave when connected to the paired IVIS 150.
  • the mobile device 100 can provide information identifying which services are available through the IVIS 150, enable or disable functions of the mobile device 100 and also lock the mobile device 100 to discourage user access while connected.
  • the mobile device 100 connects to the IVIS 150 during connection establishment and receives an IVIS device identifier (502). Paired-device identity information is retrieved that is associated with an IVIS device identifier 302 (504).
  • a device behaviour can then be determined from the paired-device identity information (506) and the mobile device 100 can be configured based upon the determined behaviour (508).
  • the behaviour may be a single action or may be defined by a behaviour profile such as displaying information pertaining to the vehicle on the display of the mobile device 100.
  • the behaviour may be identified when the device identifier 302 has been labelled by the user, for example 'My Car'.
  • Figure 6 shows a method of mobile device 100 behaviour based on paired-device identity information.
  • Connection of the IVIS 150 with the mobile device 100 is initiated through user interaction with the IVIS 150 and mobile device 100 (602).
  • a device identifier 302 is received from the IVIS 150 by the mobile device 100.
  • the device identifier 302 may include a device address or a communications profile.
  • Device identity information may be provided during the pairing establishment which may have been previously performed or provided as part of the connection initiation. If the device identifier 302 matches paired device identity information of an existing defined behaviour or behaviour profile, (Yes at 604) the mobile device 100 is configured based upon one or more actions defined by the behaviour or behaviour profile (620).
  • the device identifier 302 does not match an existing profile (No at 604), it is determined if the device identifier 302 is associated with a known vehicle or IVIS device identifier identity information (606) either by labels received in the pairing process such as in a communication profile, or based on a device identifier address that is known to be associated with a particular vehicle manufacturer and therefore likely an IVIS. If the device identifier 302 can be identified associated with a vehicle (Yes at 606) it is then determined if it is to be associated with a particular behaviour or behaviour profile, which may for example be associated with a label on the mobile device 100 such as 'My Car'.
  • the behaviour or behaviour profile is applied, if not (No at 622) regular device pairing can occur. If a device identifier 302 does not provide sufficient information to identify the vehicle, and therefore it is unknown if it should be associated with a behaviour (Unknown at 622) further choices or parameter selections can then be presented (614) for the user to select parameters from to refine the paired device identity information. Once user selections have been made, the user may then associate the device identifier 302 with a behaviour or behaviour profile. If a selection is made (Yes at 618) the mobile device 100 can then be configured based upon the pairing (620). If the device identifier 302 is not associated with a profile (No at 618), regular device pairing can occur.
  • the pairing will continue as per regular connection establishment or initial pairing. If the device identifier 302 is not associated with a known automaker (No at 606) the pairing will continue as per regular connection establishment or initial pairing. If the device identifier 302 is not associated with a known vehicle device identifier 302 (Unknown at 606) the device identifier 302 is further analyzed to determine if it indicates that it is associated with a vehicle. If the device identifier 302 does not indicate that it is associated with a vehicle (No at 608) as determined by characteristics such as the protocols supported or interfaces provided by the device, the connection will continue as per regular connection establishment or initial pairing.
  • a database lookup (610) may be performed to determine if further information can be used to refine the device identity information to be associated with the device identifier.
  • the database may be resident on the mobile device 100 or accessed remotely to a server 310. If a match is found to the device identifier 302 (Yes at 612), selection choices may be displayed to the user (614) to confirm the pairing. If a match is not found (No at 612) it is assumed that regular connection or pairing should occur and the device is not associated with an IVIS 150. Once user selections have been made, the user may then associate the device identifier 302 with a behaviour or behaviour profile, for example by applying a label to the behaviour. If a selection is made (Yes at 618) the mobile device 100 can then be configured based upon the pairing (620). If device identifier 302 is not associated with a profile (No at 618), the process continues as per regular connection establishment or initial pairing.
  • Figure 7 shows an alternative method mobile device behaviour based on paired-device identity information.
  • the method 700 assumes that the mobile device 100 has already been paired with an IVIS 150.
  • An IVIS 150 device identifier 302 is received by the mobile device 100 (702) during the connection initiation. If an existing pairing behaviour profile is not associated with the received device identifier 302 (NO at 704) regular pairing of the device will occur (706). If a profile is associated with the device identifier 302 (YES at 704) the behaviour profile is retrieved, or the parameters associated with the profile are determined (708).
  • the connection between the devices is completed (710) to establish a communication link between the mobile device 100 and the IVIS 150.
  • content may be retrieved from memory of the mobile device 100 or remotely, for display on the mobile device 100 (712).
  • the content may be items such as graphics, icons, applications or notification that are required to implement the profile.
  • services that are associated with the connection are to identified on the mobile device 100 they may be determined (714) either based upon the services identified in the behaviour profile or by polling or publishing mechanism.
  • the display of the mobile device 100 is then configured to identify information pertaining to the in-vehicle infotainment connection (716).
  • the behaviour profile may also configure resources of the mobile device 100 for example by disabling applications or functions not required while connected to the paired IVIS such as GPS, data, network access setting, running applications, or implementing power saving features.
EP13173115.0A 2013-06-20 2013-06-20 Comportement sur la base d'identification de dispositifs appariés Active EP2816781B1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21152419.4A EP3829140B1 (fr) 2013-06-20 2013-06-20 Comportement sur la base d'identification de dispositifs appariés
ES21152419T ES2951283T3 (es) 2013-06-20 2013-06-20 Comportamiento basado en identificación de dispositivo emparejado
EP13173115.0A EP2816781B1 (fr) 2013-06-20 2013-06-20 Comportement sur la base d'identification de dispositifs appariés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP13173115.0A EP2816781B1 (fr) 2013-06-20 2013-06-20 Comportement sur la base d'identification de dispositifs appariés

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP21152419.4A Division EP3829140B1 (fr) 2013-06-20 2013-06-20 Comportement sur la base d'identification de dispositifs appariés

Publications (2)

Publication Number Publication Date
EP2816781A1 true EP2816781A1 (fr) 2014-12-24
EP2816781B1 EP2816781B1 (fr) 2021-01-20

Family

ID=48672445

Family Applications (2)

Application Number Title Priority Date Filing Date
EP13173115.0A Active EP2816781B1 (fr) 2013-06-20 2013-06-20 Comportement sur la base d'identification de dispositifs appariés
EP21152419.4A Active EP3829140B1 (fr) 2013-06-20 2013-06-20 Comportement sur la base d'identification de dispositifs appariés

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP21152419.4A Active EP3829140B1 (fr) 2013-06-20 2013-06-20 Comportement sur la base d'identification de dispositifs appariés

Country Status (2)

Country Link
EP (2) EP2816781B1 (fr)
ES (1) ES2951283T3 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1729090A1 (fr) * 2004-03-19 2006-12-06 Pioneer Corporation DISPOSITIF DE TRAITEMENT D’INFORMATIONS PORTABLE
US20070182532A1 (en) * 2004-03-11 2007-08-09 Bayerische Motoren Werke Aktiengesellschaft Method and apparatus for the output of music information to an operator
EP2466262A2 (fr) * 2010-12-15 2012-06-20 Alpine Electronics, Inc. Appareil électronique
US20130046510A1 (en) * 2011-06-29 2013-02-21 State Farm Insurance Systems and Methods for Controlling the Collection of Vehicle Use Data Using a Mobile Device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8332144B2 (en) * 2005-12-31 2012-12-11 Alpine Electronics, Inc Image correction method and apparatus for navigation system with portable navigation unit
JP2012526497A (ja) * 2009-05-08 2012-10-25 オービーディーエッジ， エルエルシー 車両操作者によるモバイル装置の使用をポリシーに基づき制御および監視するシステム、方法、および装置
US8787949B2 (en) * 2011-01-04 2014-07-22 General Motors Llc Method for controlling a mobile communications device while located in a mobile vehicle

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070182532A1 (en) * 2004-03-11 2007-08-09 Bayerische Motoren Werke Aktiengesellschaft Method and apparatus for the output of music information to an operator
EP1729090A1 (fr) * 2004-03-19 2006-12-06 Pioneer Corporation DISPOSITIF DE TRAITEMENT D’INFORMATIONS PORTABLE
EP2466262A2 (fr) * 2010-12-15 2012-06-20 Alpine Electronics, Inc. Appareil électronique
US20130046510A1 (en) * 2011-06-29 2013-02-21 State Farm Insurance Systems and Methods for Controlling the Collection of Vehicle Use Data Using a Mobile Device

Also Published As

Publication number Publication date
EP2816781B1 (fr) 2021-01-20
EP3829140A1 (fr) 2021-06-02
ES2951283T3 (es) 2023-10-19
EP3829140B1 (fr) 2023-05-10

Similar Documents

Publication Publication Date Title
US20140378063A1 (en) Behavior Based on Paired Device Identification
US9584979B2 (en) Server behavior based on paired device identification
US9031710B2 (en) Cloud-based vehicle information and control system
US20150339114A1 (en) Module interface for vehicle updates
CN105635245B (zh) 车辆计算系统与装置通信的方法和系统
US9955331B2 (en) Methods for prioritizing and routing audio signals between consumer electronic devices
US9480095B2 (en) Simplified pairing of a second device in a vehicle via short range wireless communication
US10531502B2 (en) Devices, methods and computer program for producing a communication link between an information system of a transportation vehicle and a mobile device
US10919496B2 (en) Method and apparatus for wireless valet key configuration and relay
US8713299B2 (en) System and method for configuring software applications in a motor vehicle
US10200887B2 (en) Optimizing user experience in vehicles with multiple hotspots
CN107925866B (zh) 使用dsrc联系远程车辆的乘员的系统和方法
US20160167516A1 (en) Method and Apparatus for Infotainment System Control Through a Wireless Device Operating-System-Independent Protocol
EP2899643A1 (fr) Boîte de commutation multimédia
US9560470B2 (en) Updating a vehicle head unit with content from a wireless device
US20160088052A1 (en) Indexing mobile device content using vehicle electronics
US10813142B2 (en) Apparatus of paging mobile devices
US11625492B2 (en) Method and system for securely providing vehicle services data to a vehicle
US20180152880A1 (en) Controlling use of vehicular wi-fi hotspots by a handheld wireless device
EP3829140B1 (fr) Comportement sur la base d'identification de dispositifs appariés
EP3985953B1 (fr) Comportement de serveur sur la base de l'identification de dispositifs appariés
KR101478470B1 (ko) 스마트 기기를 이용한 차량의 시간정보 설정 방법 및 그 장치
US20200019415A1 (en) User terminal, user interface, computer program product, signal sequence, means of transport, and method for setting up a user interface of a means of transport
US20170265022A1 (en) Method and apparatus for providing portable telematics services
KR20160106995A (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

17P Request for examination filed

Effective date: 20130620

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

AX Request for extension of the european patent

Extension state: BA ME

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: BLACKBERRY LIMITED

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

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: H04M 1/60 20060101ALI20200729BHEP

Ipc: H04W 4/48 20180101ALI20200729BHEP

Ipc: H04L 29/08 20060101AFI20200729BHEP

INTG Intention to grant announced

Effective date: 20200812

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

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1357340

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210120

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1357340

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210120

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602013075357

Country of ref document: DE

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

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

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

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602013075357

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029080000

Ipc: H04L0065000000

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

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

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

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

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

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

26N No opposition filed

Effective date: 20211021

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

Ref country code: AL

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

Effective date: 20210120

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210630

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

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

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

Ref country code: IE

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

Effective date: 20210620

Ref country code: CH

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

Effective date: 20210630

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

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

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

Ref country code: BE

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

Effective date: 20210630

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

Ref country code: HU

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

Effective date: 20130620

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

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

Ref country code: FR

Payment date: 20230626

Year of fee payment: 11

Ref country code: DE

Payment date: 20230626

Year of fee payment: 11

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

Ref country code: GB

Payment date: 20230627

Year of fee payment: 11