US20210108938A1 - Methods and systems for determining a usage preference of a vehicle operator - Google Patents
Methods and systems for determining a usage preference of a vehicle operator Download PDFInfo
- Publication number
- US20210108938A1 US20210108938A1 US16/599,557 US201916599557A US2021108938A1 US 20210108938 A1 US20210108938 A1 US 20210108938A1 US 201916599557 A US201916599557 A US 201916599557A US 2021108938 A1 US2021108938 A1 US 2021108938A1
- Authority
- US
- United States
- Prior art keywords
- application
- vehicle
- usage
- mobile device
- personal mobile
- 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
- 238000000034 method Methods 0.000 title claims description 37
- 238000004891 communication Methods 0.000 claims description 49
- 238000013500 data storage Methods 0.000 claims description 20
- 238000010079 rubber tapping Methods 0.000 claims description 4
- 238000013507 mapping Methods 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 description 17
- 238000004590 computer program Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3453—Special cost functions, i.e. other than distance or default speed limit of road segments
- G01C21/3484—Personalized, e.g. from learned user behaviour or user-defined profiles
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/36—Input/output arrangements for on-board computers
- G01C21/3605—Destination input or retrieval
- G01C21/3617—Destination input or retrieval using user history, behaviour, conditions or preferences, e.g. predicted or inferred from previous use or current movement
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/0011—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots associated with a remote control arrangement
- G05D1/0022—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots associated with a remote control arrangement characterised by the communication link
-
- 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
- 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 generally relates to vehicle systems, computing devices, and methods carried out by the systems and devices, and more specifically, to methods, systems, and devices for determining a usage preference for an application on a personal mobile device over a vehicle feature of a vehicle.
- Vehicles may be equipped with hardware and software that provide drivers or other vehicle occupants with a rich user experience.
- a vehicle may include a touchscreen display and software applications that can be operated via the touchscreen display. These software applications may assist with vehicle navigation, provide weather conditions or other information to the driver, or allow for playback of podcasts or other media, as examples.
- An embodiment of the present disclosure takes the form of a method that includes obtaining application-usage data from a personal mobile device of a vehicle operator of a vehicle.
- the application-usage data reflects a usage, during operation of the vehicle, of an application on the personal mobile device.
- the method further includes identifying a vehicle feature, of the vehicle, that provides a vehicle functionality similar to an application functionality provided by the application on the personal mobile device, and performing a comparison of the obtained application-usage data with feature-usage data.
- the feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle feature.
- the method also includes determining, based on the comparison, a usage preference for the application during operation of the vehicle over the identified vehicle feature.
- Another embodiment takes the form of a computing device that includes a processor and a non-transitory computer-readable storage medium that includes instructions.
- the instructions when executed by the processor, cause the computing device to obtain application-usage data from a personal mobile device of a vehicle operator of a vehicle.
- the application-usage data reflects a usage, during operation of the vehicle, of an application on the personal mobile device.
- the instructions further cause the computing device to identify a vehicle feature, of the vehicle, that provides a vehicle functionality similar to an application functionality provided by the application on the personal mobile device, and perform a comparison of the obtained application-usage data with feature-usage data.
- the feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle feature.
- the instructions also cause the computing device to determine, based on the comparison, a usage preference for the application during operation of the vehicle over the identified vehicle feature.
- a further embodiment takes the form of a method that includes obtaining application-usage data from a personal mobile device of a vehicle operator of a vehicle.
- the application-usage data reflects a usage, during operation of the vehicle, of a mobile-device application executed by the personal mobile device.
- the method further includes identifying a vehicle application, executed by the vehicle, that provides a vehicle functionality similar to an application functionality provided by the mobile-device application executed by personal mobile device, and performing a comparison of the obtained application-usage data with feature-usage data.
- the feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle application.
- the method also includes determining, based on the comparison, a usage preference for the mobile-device application during operation of the vehicle over the identified vehicle application.
- FIG. 1 depicts a vehicle system, according to one or more embodiments described and illustrated herein;
- FIG. 2 a depicts a user interface device of a personal mobile device, according to one or more embodiments described and illustrated herein;
- FIG. 2 b depicts a user interface device of a vehicle, according to one or more embodiments described and illustrated herein;
- FIG. 3 depicts a block diagram of a computing device, according to one or more embodiments described and illustrated herein;
- FIG. 4 depicts a flowchart of a method, according to one or more embodiments described and illustrated herein;
- FIG. 5 a depicts a database of applications of personal mobile devices, according to one or more embodiments described and illustrated herein;
- FIG. 5 b depicts a manifest of vehicle features of a vehicle, according to one or more embodiments described and illustrated herein.
- a system obtains application-usage data from a personal mobile device of a vehicle operator of a vehicle.
- the application-usage data reflects a usage, during operation of the vehicle, of an application on the personal mobile device.
- the system identifies a vehicle feature, of the vehicle, that provides a vehicle functionality similar to an application functionality provided by the application on the personal mobile device, and performs a comparison of the obtained application-usage data with feature-usage data.
- the feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle feature.
- the system determines, based on the comparison, a usage preference for the application during operation of the vehicle over the identified vehicle feature.
- a usage preference for the application By determining such usage preferences of vehicle operators, it may be possible to identify vehicle features providing functionality that vehicle operators instead prefer to obtain from applications on personal mobile devices. These identified vehicle features may be removed from vehicles, and subsequently-produced vehicles may be delivered without the identified vehicle features, which may potentially reduce the amount of resources required to produce or operate the vehicles and possibly reduce the costs of the vehicles.
- FIG. 1 depicts a vehicle system, according to one or more embodiments described and illustrated herein.
- a system 100 includes a vehicle 102 , a personal mobile device 104 , and a server computer 106 , each of which are communicatively connected via a network 108 and respective communication links 110 to the network. Additionally, vehicle 102 is communicatively connected to personal mobile device 104 via a local communication link 112 . Any of vehicle 102 , personal mobile device 104 , or server computer 106 , or any combination of these, may be configured to carry out the vehicle-system functions described herein.
- Vehicle 102 could take the form of an autonomous vehicle, a semi-autonomous vehicle, or a manually-operated vehicle, among other possibilities.
- the vehicle may include a user interface device, and could include a computing device configured to carry out the vehicle functions and/or vehicle-system functions described herein. Additional aspects of vehicle 102 are described throughout the specification.
- Personal mobile device 104 could include a smartphone, a mobile phone, a tablet computer, a wearable computer, a smartwatch, a head-mounted display, a mobile computing device, or any other personal mobile device configured to carry out the personal-mobile-device functions and/or vehicle-system functions described herein.
- Personal mobile device 104 may be used by a vehicle operator of vehicle 102 , though it should be understood that the vehicle operator of vehicle 102 is not limited to a driver of the vehicle. For instance, the vehicle operator could include a passenger of the vehicle, a driver of the vehicle, or a combination of these, as examples.
- Server computer 106 could take the form of a mainframe, a workstation, a terminal, a personal computer, a virtual machine, or any combination of these or other server computers.
- the server computer could include a computing device configured to carry out the server-computer functions and/or the vehicle-system functions described herein. Though system 100 is shown as including a single server computer, those of skill in the art will appreciate that the system could include multiple server computers.
- Network 108 may include one or more computing systems and network infrastructure configured to facilitate communication between any one or more of vehicle 102 , personal mobile device 104 , and server computer 106 .
- the network may take the form of (or include) one or more Wide-Area Networks (WANs), Local-Area Networks (LANs), the Internet, cellular networks, wired networks, wireless networks, or any combination of these or other networks.
- Network 108 may operate according to one or more communication protocols such as Ethernet, Wi-Fi, IP, TCP, or LTE, as examples. Though network 108 is shown as a single network, it should be understood that the network may include multiple, distinct networks that are communicatively linked. Network 108 could take other forms as well.
- Communication links 110 may communicatively connect vehicle 102 , personal mobile device 104 , and/or server computer 106 to network 108 to facilitate communication between these or other entities communicatively connected to the network. Any of communication links 110 could include wired and/or wireless communication links, and could include a combination of hardware and/or software, perhaps operating on one or more communication-link layers such as one or more physical, network, transport, and/or application layers. Communication links 110 may include one or more intermediate paths or systems, for example.
- Local communication link 112 may facilitate communication between vehicle 102 and personal mobile device 104 , and could include a wired and/or wireless link.
- local communication link 112 facilitates direct communication between the vehicle and the personal mobile device, and the local communication link does not include any intermediate systems, networks, or paths except for those that may be part of the vehicle or the personal mobile device.
- the local communication link may facilitate communication via a short-range communication protocol, which may include wireless protocols such as Bluetooth, Wi-Fi, near-field communication (NFC), ZigBee, or Z-Wave (as examples), wired protocols such as Universal Serial Bus (USB) or IEEE 1394 (FireWire) (among other possibilities), or a combination of these.
- USB Universal Serial Bus
- IEEE 1394 WireWire
- system 100 may include different and/or additional entities, and will appreciate that the functions of system 100 (including the functions of vehicle 102 , personal mobile device 104 , and/or server computer 106 ) may be carried out by any combination of entities of system 100 .
- system 100 could include additional personal mobile devices, and may not include server computer 106 .
- one or more of communication links 110 may be absent, such as the communication link between personal mobile device 104 and network 108 .
- local communication link 112 may be absent. Other variations are possible as well.
- FIG. 2 a depicts a user interface device of personal mobile device 104 , according to one or more embodiments described and illustrated herein.
- a user interface device 200 of the personal mobile device includes a display device 202 , a microphone 204 , and a speaker 206 .
- Personal mobile device 104 may receive input (e.g., from a vehicle operator of vehicle 102 ), and/or provide output (e.g., to the vehicle operator), via user interface device 200 using one or more of the display device, the microphone, and the speaker. For instance, input may be received by personal mobile device 104 via display device 202 , microphone 204 , and/or another input component of user interface device 200 .
- output may be provided by the personal mobile device via display device 202 , speaker 206 , another output component of user interface device 200 , or a combination of these.
- Some components of user interface device 200 may facilitate both input and output—for instance, display device 202 could take the form of a touchscreen display device, and personal mobile device 104 may provide output and receive input via the touchscreen display device. It should be understood that user interface device 200 may take the form of multiple user interface devices, and may include different and/or additional components.
- FIG. 2 b depicts a user interface device of vehicle 102 , according to one or more embodiments described and illustrated herein.
- a user interface device 230 of vehicle 102 includes display device 232 (e.g., a touchscreen display device), push buttons 234 a , 234 b , 234 c , and 234 d , and control knob 236 .
- Vehicle 102 may receive input from a vehicle operator of the vehicle, and/or provide output to the vehicle operator, via user interface device 230 using one or more of the display device, the push buttons, and the control knob.
- input may be received by vehicle 102 via display device 232 , push buttons 234 a - 234 d , control knob 236 , a microphone of user interface device 230 , and/or another input component of the user interface device.
- output may be provided by the vehicle via display device 232 and/or another component of user interface device 230 , such as a speaker of the user interface device.
- user interface device 230 need not take the form of a single, discrete device, but could instead take the form of multiple user interface devices.
- the user interface device could include a first user interface device in the form of an automotive head unit that includes display device 232 , push buttons 234 a - 234 d , and control knob 236 , and a second user interface device that includes a microphone and a speaker installed in an interior of vehicle 102 .
- user interface device 230 may include different and/or additional components.
- FIG. 3 depicts a block diagram of a computing device, according to one or more embodiments described and illustrated herein.
- a computing device 300 includes a processor 302 , a data storage 304 including instructions 305 , a communication interface 306 , and a user interface module 308 , each of which are communicatively connected via a system bus 310 .
- Vehicle 102 , personal mobile device 104 , server computer 106 , any other entity of system 100 , or any combination of these could take the form of (or include) computing device 300 .
- Processor 302 may take the form of one or more general-purpose processors and/or one or more special-purpose processors, and may be integrated in whole or in part with data storage 304 , communication interface 306 , user interface module 308 , and/or any other component of computing device 300 , as examples. Accordingly, processor 302 may take the form of or include a controller, an integrated circuit, a microchip, a central processing unit (CPU), a microprocessor, a system on a chip (SoC), a field-programmable gate array (FPGA), and/or an application-specific integrated circuit (ASIC), among other possibilities.
- CPU central processing unit
- SoC system on a chip
- FPGA field-programmable gate array
- ASIC application-specific integrated circuit
- Data storage 304 may take the form of a non-transitory computer-readable storage medium such as a hard drive, a solid-state drive, an erasable programmable read-only memory (EPROM), a universal serial bus (USB) storage device, a compact disc read-only memory (CD-ROM) disk, a digital versatile disc (DVD), a relational database management system (RDBMS), any other non-volatile storage, or any combination of these, to name just a few examples.
- a non-transitory computer-readable storage medium such as a hard drive, a solid-state drive, an erasable programmable read-only memory (EPROM), a universal serial bus (USB) storage device, a compact disc read-only memory (CD-ROM) disk, a digital versatile disc (DVD), a relational database management system (RDBMS), any other non-volatile storage, or any combination of these, to name just a few examples.
- EPROM erasable programmable read-only memory
- Instructions 305 may be stored in data storage 304 , and may include machine-language instructions executable by processor 302 to cause computing device 300 to perform the computing-device functions and/or vehicle-system functions described herein. Additionally or alternatively, instructions 305 may include script instructions executable by a script interpreter configured to cause processor 302 and computing device 300 to execute the instructions specified in the script instructions. It should be understood that instructions 305 may take other forms as well.
- Additional data may be stored in data storage 304 , such as a database of applications of personal mobile devices and/or a manifest of vehicle features of one or more vehicles, as will be described in further detail below.
- the additional data could be stored as a table, a flat file, data in a file system of the data storage, a heap file, a B+ tree, a hash table, a hash bucket, or any combination of these, as examples.
- Communication interface 306 may be any component capable of performing the communication-interface functions described herein, including facilitating wired and/or wireless communication between computing device 300 and another entity (such as an entity of system 100 ). As such, communication interface 306 could take the form of a Bluetooth, Wi-Fi, USB, and/or LTE interface, among many other examples. Communication interface 306 may receive data over network 108 via one or more of communication links 110 and local communication link 112 , for instance.
- User interface module 308 may be any component capable of carrying out the user-interface-module functions described herein.
- the user interface module may include user interface device 200 of personal mobile device 104 , user interface device 230 of vehicle 102 , or another user interface device, and could further include other hardware and/or software for realizing input and/or output via the user interface device.
- System bus 310 may be any component capable of performing the system-bus functions described herein.
- system bus 310 is any component configured to transfer data between processor 302 , data storage 304 , communication interface 306 , user interface module 308 , and/or any other component of computing device 300 .
- system bus 310 includes a traditional bus as is known in the art.
- system bus 310 includes a serial RS-232 communication link, a USB communication link, and/or an Ethernet communication link, alone or in combination with a traditional computer bus, among numerous other possibilities.
- system bus 310 may be formed from any medium that is capable of transmitting a signal, such as conductive wires, conductive traces, or optical waveguides, among other possibilities.
- system bus 310 may be formed from a combination of mediums capable of transmitting signals.
- the system bus could take the form of (or include) a vehicle bus, such as a local interconnect network (LIN) bus, a controller area network (CAN) bus, a vehicle area network (VAN) bus, or any combination of these or mediums.
- LIN local interconnect network
- CAN controller area network
- VAN vehicle area network
- System bus 310 may take various other forms as well.
- computing device 300 may include different and/or additional components, and some or all of the functions of a given component could instead be carried out by one or more different components. Additionally, computing device 300 could take the form of (or include) multiple computing devices, and some or all of the functions of a given component could be carried out by any combination of one or more of the computing devices.
- FIG. 4 depicts a flowchart of a method carried out by a vehicle system, according to one or more embodiments described and illustrated herein.
- a method 400 begins at step 402 with system 100 obtaining application-usage data from personal mobile device 104 of a vehicle operator of vehicle 102 .
- the application could be a computer program or software application executed by personal mobile device 104 .
- the application may provide application functionality such as mapping and navigation, media playback (including playback of audio, video, music, and/or podcasts), text messaging (e.g., SMS), telephony, and/or data tethering, among other possibilities.
- the application includes application instructions stored on a data storage of personal mobile device 104 (such as data storage 304 of the personal mobile device). The application instructions, when executed by a processor of the personal mobile device, cause the personal mobile device to provide the functionality of the application.
- the application-usage data reflects a usage of an application on personal mobile device 104 during operation of vehicle 102 .
- the application-usage data may reflect usage of the application by the vehicle operator of the vehicle—such as a driver of the vehicle and/or a passenger of the vehicle, among other examples.
- the application-usage data may reflect usage of the application via user interface device 200 of personal mobile device 104 —for instance, via display device 202 , microphone 204 , and speaker 206 .
- Display device 202 could include a touchscreen display, and usage of the application via display device 202 could include a tapping, pressing, or swiping of the vehicle operator's fingers on the touchscreen display.
- usage of the application could include words or utterances spoken to (e.g., received by) microphone 204 by the vehicle operator.
- usage of the application could include a display presented by display device 202 to the vehicle operator, and/or audio generated for the vehicle operator by speaker 206 . For instance, if the vehicle operator is navigating to a given destination and the application provides navigation functionality, then the display could include display of a map or a list of turn-by-turn directions on display device 202 .
- personal mobile device 104 includes an operating system (e.g., an operating system executed by the personal mobile device).
- the operating system could include operating-system instructions that are stored on a data storage of the personal mobile device and that, when executed by a processor of the personal mobile device, cause the personal mobile device to execute the operating system.
- usage of the application could include usage detected by the operating system while the application is in a foreground of a shell of the operating system.
- the application-usage data could include application-usage data (e.g., logs files, a screenshot of display device 202 of personal mobile device 104 ) that is generated by the operating system and that reflects the usage detected by the operating system while the application is in the foreground of the shell.
- usage of the application could include usage detected by the application based on data received by the application from the operating system.
- usage of the application could include usage while the application is in a foreground of a shell of an operating system of the personal mobile device, and/or while the application is in a background of the operating system (e.g., while the application is executed as a background process by the operating system).
- the application-usage data could include application-usage data (e.g., log files, a screenshot of display device 202 , and/or a screenshot of the application as captured by the app) that is generated by the application and that reflects usage of the application (as detected by the app).
- the application-usage data reflecting usage of the application may include data reflecting an amount of time that the application was displayed by personal mobile device 104 via display device 202 of the personal mobile device, and/or a number of times that the application was displayed by the personal mobile device via display device 202 .
- the application-usage data reflecting usage of the application may include an amount of time that the vehicle operator interacted with the application, and/or a number of times that the vehicle operator interacted with the application.
- the application-usage data reflecting usage of the application may include a number of times that the application was launched on personal mobile device 104 by the vehicle operator (e.g., via an operating system of the mobile device), and/or a number of times that the application was brought to a foreground of a shell of an operating system of the personal mobile device. It should be understood that the application-usage data may include data reflecting any combination of these or other usage of the application.
- the application-usage data may reflect usage of the application on personal mobile device 104 via user interface device 230 of vehicle 102 .
- vehicle 102 may establish a remote-interface connection with personal mobile device 104 via local communication link 112 .
- the personal mobile device may provide output to the vehicle operator by causing the vehicle to provide the output via user interface device 230 (e.g., via display device 232 ) of vehicle 102 .
- usage of the application could include a display, presented by display device 232 of vehicle 102 , of a map or a list of turn-by-turn directions.
- the personal mobile device may receive input from a vehicle operator of the vehicle by causing the vehicle to receive the input via user interface device 230 (e.g., via display device 232 , push buttons 234 a - 234 d , and/or control knob 236 ) of vehicle 102 , which may then be received by the personal mobile device.
- user interface device 230 e.g., via display device 232 , push buttons 234 a - 234 d , and/or control knob 236
- Other examples are possible as well.
- Operation of vehicle 102 may include an ignition-on cycle of the vehicle, and usage of the application during operation of the vehicle could include usage of the application during the ignition-on cycle.
- An ignition-on cycle could begin at an ignition-on of vehicle 102 , for instance, and could end at an ignition-off of the vehicle, among other examples.
- operation of vehicle 102 may include an accessory power-on cycle of the vehicle, and usage of the application during operation of the vehicle could include usage of the application during the accessory power-on cycle.
- An accessory power-on cycle could begin at an accessory power-on of vehicle 102 , for example, and could end at an accessory power-off of the vehicle.
- Other examples of operation of vehicle 102 as possible as well, as are examples of usage of the application during operation of the vehicle.
- Obtaining the application-usage data from personal mobile device 104 may include vehicle 102 obtaining the application-usage data from the personal mobile device via (wired and/or wireless) local communication link 112 .
- Obtaining the application-usage data from the personal mobile device via local communication link 112 could include establishing a remote-interface connection with personal mobile device 104 via local communication link 112 (as discussed above), and obtaining the application-usage data from the personal mobile device over the remote-interface connection via local communication link 112 .
- obtaining the application-usage data from personal mobile device 104 could include server computer 106 obtaining the application-usage data from the personal mobile device over network 108 via respective communication links 110 (e.g., LTE communication links) between the server computer and the network and between the network and the personal mobile device.
- obtaining the application-usage data could include vehicle 102 obtaining the application-usage data from personal mobile device 104 over network 108 via respective communication links 110 (e.g., LTE communication links) between the vehicle and the network and between the network and the personal mobile device. It should be understood that obtaining the application-usage data from personal mobile device 104 may take other forms as well.
- system 100 identifies a vehicle feature, of vehicle 102 , that provides a vehicle functionality similar to an application functionality provided by the application on personal mobile device 104 .
- system 100 may identify a vehicle application, executed by vehicle 102 , that provides a vehicle functionality similar to an application functionality provided by the mobile-device application executed by personal mobile device 104 .
- the vehicle feature could be a computer program or software application executed by vehicle 102 .
- the vehicle feature may provide vehicle functionality such as mapping, navigation, media playback (including playback of audio, video, music, and/or podcasts), text messaging (e.g., SMS), telephony, and/or data tethering, among other possibilities.
- the vehicle features takes the form of (or includes) vehicle-feature instructions stored on a data storage of vehicle 102 (such as data storage 304 of the vehicle).
- the vehicle-feature instructions when executed by a processor of the vehicle, cause the vehicle to provide the functionality of the vehicle feature.
- the vehicle feature could take the form of an electronic control unit (ECU). Other examples are possible as well.
- identifying the vehicle feature of vehicle 102 that provides the vehicle functionality similar to the application functionality includes determining the application functionality and identifying, from a manifest of respective vehicle functionalities provided by one or more vehicle features, a vehicle functionality similar to the determined application.
- identifying the vehicle feature of vehicle 102 that provides the vehicle functionality similar to the application functionality includes determining the application functionality and identifying, from among respective vehicle functionalities provided by one or more vehicle features, a vehicle functionality similar to the determined application functionality.
- identifying the vehicle features includes obtaining a feature identification of the vehicle feature that provides the identified vehicle functionality.
- FIG. 5 a depicts a database of applications of personal mobile devices
- FIG. 5 b depicts a manifest of vehicle features of a vehicle, according to one or more embodiments described and illustrated herein.
- a database 500 of applications of personal mobile devices includes applications 502 , 504 , 506 , 508 , and 510 .
- the database includes a respective application ID 512 and a respective application functionality indication 514 .
- a manifest 550 of vehicle features of vehicle 102 includes vehicle features 552 , 554 , and 556 .
- the manifest includes a respective vehicle feature ID 562 and a respective vehicle functionality indication 564 .
- determining the application functionality may include obtaining an application ID 512 of the application on personal mobile device 104 .
- the application could have been downloaded from an application repository (such as an application marketplace), which may have assigned the application with an application ID unique to the application.
- the personal mobile device may have installed the application and concurrently saved the unique application ID for the application to a data storage of the personal mobile device.
- obtaining the application ID may involve obtaining the application ID from the data storage.
- Determining the application functionality may then include identifying an application, from among database 500 of applications, having the same application ID as that obtained from the data storage.
- the application ID of the application on personal mobile device 104 could be “Audio App 2”, and identifying an application, from among database 500 of applications having the same application ID as the application ID obtained from the data storage may include identifying application 508 , which also has an application ID of “Audio App 2”.
- Determining the application functionality may include determining the application functionality based on an obtained application ID of the application on personal mobile device 104 . For instance, with reference to FIG. 5 a , determining the application functionality based on the obtained application ID of “Audio App 2” for the application on personal mobile device 104 (which is also the application ID of application 508 in database 500 ) may include retrieving the respective application functionality indication 514 of application 508 having the same application ID 512 as the obtained application ID. As shown in FIG. 5 a , the respective application functionality indication 514 of application 508 is “Music”.
- Identifying the vehicle functionality similar to the determined application functionality may include identifying, from among manifest 550 of vehicle features, a vehicle functionality indication 564 that is the same as (and/or similar to) application functionality indication 514 of the application in database 500 (retrieved as described above) that has the same application ID 512 as the obtained application ID for the application on personal mobile device 104 .
- identifying a vehicle functionality indication 564 that is the same as or similar to application functionality indication 514 may include identifying vehicle feature 554 , which has a respective vehicle functionality indication 564 of “Music” that is the same as application functionality indication 514 of application 508 (as retrieved in the manner described above).
- Obtaining the feature identification of the vehicle feature that provides the identified vehicle functionality may include retrieving respective vehicle feature ID 562 of the vehicle feature having respective vehicle functionality indication 564 (as identified in the manner discussed above) that is the same as (and/or similar to) application functionality indication 514 (as retrieved in the manner described above).
- retrieving respective vehicle feature ID 562 may include retrieving the respective vehicle feature ID of vehicle feature 554 , which has respective vehicle functionality indication 564 that is the same as respective application functionality indication 514 of application 508 in database 500 .
- system 100 performs a comparison of the application-usage data obtained at step 402 with feature-usage data.
- the feature-usage data reflects a usage, during operation of vehicle 102 , of the vehicle feature identified at step 404 .
- system 100 may perform a comparison of the obtained application-usage data with feature-usage data that reflects a usage, during operation of vehicle 102 , of the identified vehicle application.
- the feature-usage data may reflect that the vehicle feature was not used during operation of the vehicle.
- the usage of the identified vehicle feature may take a form similar to usage of the application on personal mobile device 104 as described above with reference to step 402
- the feature-usage data may take a form similar to the application-usage data obtained at step 402
- the feature-usage data may reflect usage of the vehicle feature by the vehicle operator of the vehicle, such as a driver of the vehicle and/or a passenger of the vehicle, among other examples.
- the feature-usage data may reflect usage of the vehicle feature via user interface device 230 of vehicle 102 —for instance, via display device 232 , push buttons 234 a - 234 d , and/or control knob 236 .
- Display device 232 could include a touchscreen display, and usage of the vehicle feature via display device 232 could include a tapping, pressing, or swiping of the vehicle operator's fingers on the touchscreen display and/or a display presented by display device 232 to the vehicle operator.
- usage of the vehicle feature could include words or utterances spoken to (e.g., received by) a microphone of user interface device 230 by the vehicle operator, and/or audio generated for the vehicle operator by a speaker of user interface device 230 of vehicle 102 .
- the vehicle feature could include a podcast application executed by vehicle 102 , and usage of the vehicle feature could include audio generated for playback of a podcast by the podcast application, or could include tapping of the vehicle operator's fingers on display device 232 (which could be a touchscreen display, for instance).
- vehicle 102 includes an operating system (e.g., an operating system executed by the vehicle).
- the operating system could include operating-system instructions that are stored on a data storage of the vehicle and that, when executed by a processor of the vehicle, cause the vehicle to execute the operating system.
- usage of the vehicle feature could include usage detected by the operating system while the vehicle feature is in a foreground of a shell of the operating system.
- the feature-usage data could include feature-usage data (e.g., logs files, a screenshot of display device 232 of vehicle 102 ) that is generated by the operating system and that reflects the usage detected by the operating system while the vehicle feature is in the foreground of the shell.
- usage of the vehicle feature could include usage detected by the vehicle feature itself based on data received by the vehicle feature from the operating system.
- usage of the vehicle feature could include usage while the vehicle feature is in a foreground of a shell of an operating system of the vehicle, and/or while the vehicle feature is in a background of the operating system (e.g., while the vehicle feature is executed as a background process by the operating system).
- the feature-usage data could include feature-usage data (e.g., log files, a screenshot of display device 232 , and/or a screenshot of the vehicle feature as captured by the vehicle feature) that is generated by the vehicle feature and that reflects usage of the vehicle feature (as detected by the vehicle feature).
- the feature-usage data reflecting usage of the vehicle feature may include data reflecting an amount of time that the vehicle feature was displayed by vehicle 102 via display device 232 of the vehicle, and/or a number of times that the vehicle feature was displayed by the vehicle via display device 232 .
- performing the comparison of the application-usage data with feature-usage data could include comparing this amount of time and/or number of times, with an amount of time that the application on personal mobile device 104 was displayed by personal mobile device 104 via display device 202 of the personal mobile device and/or a number of times that the application was displayed by the personal mobile device via display device 202 .
- the feature-usage data reflecting usage of the vehicle feature may include an amount of time that the vehicle operator interacted with the vehicle feature, and/or a number of times that the vehicle operator interacted with the vehicle feature.
- performing the comparison of the application-usage data with feature-usage data could include comparing this amount of time and/or number of times, with an amount of time that the vehicle operator interacted with the application, and/or a number of times that the vehicle operator interacted with the application.
- the feature-usage data reflecting usage of the vehicle feature may include a number of times that the vehicle feature was launched on vehicle 102 by the vehicle operator (e.g., via an operating system of the mobile device), and/or a number of times that the vehicle feature was brought to a foreground of a shell of an operating system of the vehicle.
- performing the comparison of the application-usage data with feature-usage data could include comparing either or both of these numbers of times with a number of times that the application was launched on personal mobile device 104 by the vehicle operator (e.g., via an operating system of the mobile device), and/or comparing either or both of these numbers with a number of times that the application was brought to a foreground of a shell of an operating system of the personal mobile device.
- the feature-usage data may include data reflecting any combination of these or other usage of the vehicle features.
- system 100 determines, based on the comparison performed at step 406 , a usage preference for the application during operation of vehicle 102 over the vehicle feature identified at step 404 .
- system 100 may determine, based on the comparison, a usage preference for the application during operation of the vehicle over a vehicle application (e.g., a software application executed by the vehicle) identified at step 404 .
- the usage preference may reflect a preference of the vehicle operator to use the application over the vehicle feature, and may reflect a preference to utilize application functionality provided by the application over similar functionality provided by the vehicle feature.
- Determining the usage preference could include generating a report based on the determined usage preference.
- the report could indicate the usage preference, and could include some or all of the application-usage data and/or the feature-usage data.
- method 400 may be performed for each of a plurality of vehicle operators, and the generated report could indicate respective usage preferences for each of the vehicle operators (and/or an aggregate usage preference).
- system 100 e.g., server computer 106
- server computer 106 could obtain application-usage data from respective personal mobile devices of each of the vehicle operators, and identify a vehicle functionality that provides functionality similar to respective application functionality provided by respective applications on the personal mobile devices.
- the system could perform a comparison of the obtained application-usage data with feature-usage data that reflects usage of the identified vehicle feature, and based on the comparison, could determine respective usage preferences (and/or an aggregate usage preference) for the applications over the identified vehicle feature.
- the generated report (whether generated for a given vehicle operator or for multiple vehicle operators) could then be presented via a user interface—e.g., to a user via a user interface. For instance, the generated report could be presented via user interface device 230 of vehicle 102 , and/or could be presented via a user interface of server computer 106 .
- the report could be generated by server computer 106 and presented by the server computer via a user interface of a different entity of system 100 —the different entity receives the report from server computer 106 and presents the received report via a user interface of the entity.
- the different entity receives the report from server computer 106 and presents the received report via a user interface of the entity.
- Other examples are possible as well.
- Determining the usage preference could include removing, from vehicle 102 , the vehicle feature (identified at step 404 ) in response to determining the usage preference.
- the vehicle feature could include a vehicle application (e.g., a software application) executed by the vehicle.
- Vehicle 102 could determine the usage preference and responsively uninstall the vehicle application from the vehicle.
- personal mobile device 104 and/or server computer 106 may determine the usage preference, and in response to determining the usage preference, may send an instruction to vehicle 102 to uninstall the application.
- the vehicle could then uninstall the application.
- the instruction could be sent to vehicle 102 over network 108 and communication links 110 , and/or could be sent to the vehicle via local communication link 112 . It should be understood that determining the usage preference could take numerous other forms as well.
- a system obtains application-usage data from a personal mobile device of a vehicle operator of a vehicle.
- the application-usage data reflects a usage, during operation of the vehicle, of an application on the personal mobile device.
- the system identifies a vehicle feature, of the vehicle, that provides a vehicle functionality similar to an application functionality provided by the application on the personal mobile device, and performs a comparison of the obtained application-usage data with feature-usage data.
- the feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle feature.
- the system determines, based on the comparison, a usage preference for the application during operation of the vehicle over the identified vehicle feature.
Landscapes
- Engineering & Computer Science (AREA)
- Remote Sensing (AREA)
- Radar, Positioning & Navigation (AREA)
- Automation & Control Theory (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Social Psychology (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Aviation & Aerospace Engineering (AREA)
- Navigation (AREA)
Abstract
Description
- The present disclosure generally relates to vehicle systems, computing devices, and methods carried out by the systems and devices, and more specifically, to methods, systems, and devices for determining a usage preference for an application on a personal mobile device over a vehicle feature of a vehicle.
- Vehicles may be equipped with hardware and software that provide drivers or other vehicle occupants with a rich user experience. For instance, a vehicle may include a touchscreen display and software applications that can be operated via the touchscreen display. These software applications may assist with vehicle navigation, provide weather conditions or other information to the driver, or allow for playback of podcasts or other media, as examples.
- An embodiment of the present disclosure takes the form of a method that includes obtaining application-usage data from a personal mobile device of a vehicle operator of a vehicle. The application-usage data reflects a usage, during operation of the vehicle, of an application on the personal mobile device. The method further includes identifying a vehicle feature, of the vehicle, that provides a vehicle functionality similar to an application functionality provided by the application on the personal mobile device, and performing a comparison of the obtained application-usage data with feature-usage data. The feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle feature. The method also includes determining, based on the comparison, a usage preference for the application during operation of the vehicle over the identified vehicle feature.
- Another embodiment takes the form of a computing device that includes a processor and a non-transitory computer-readable storage medium that includes instructions. The instructions, when executed by the processor, cause the computing device to obtain application-usage data from a personal mobile device of a vehicle operator of a vehicle. The application-usage data reflects a usage, during operation of the vehicle, of an application on the personal mobile device. The instructions further cause the computing device to identify a vehicle feature, of the vehicle, that provides a vehicle functionality similar to an application functionality provided by the application on the personal mobile device, and perform a comparison of the obtained application-usage data with feature-usage data. The feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle feature. The instructions also cause the computing device to determine, based on the comparison, a usage preference for the application during operation of the vehicle over the identified vehicle feature.
- A further embodiment takes the form of a method that includes obtaining application-usage data from a personal mobile device of a vehicle operator of a vehicle. The application-usage data reflects a usage, during operation of the vehicle, of a mobile-device application executed by the personal mobile device. The method further includes identifying a vehicle application, executed by the vehicle, that provides a vehicle functionality similar to an application functionality provided by the mobile-device application executed by personal mobile device, and performing a comparison of the obtained application-usage data with feature-usage data. The feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle application. The method also includes determining, based on the comparison, a usage preference for the mobile-device application during operation of the vehicle over the identified vehicle application.
- These and additional features provided by the embodiments of the present disclosure will be more fully understood in view of the following detailed description, in conjunction with the drawings.
- The embodiments set forth in the drawings are illustrative and exemplary in nature and not intended to limit the disclosure. The following detailed description of the illustrative embodiments can be understood when read in conjunction with the following drawings, where like structure is indicated with like reference numerals and in which:
-
FIG. 1 depicts a vehicle system, according to one or more embodiments described and illustrated herein; -
FIG. 2a depicts a user interface device of a personal mobile device, according to one or more embodiments described and illustrated herein; -
FIG. 2b depicts a user interface device of a vehicle, according to one or more embodiments described and illustrated herein; -
FIG. 3 depicts a block diagram of a computing device, according to one or more embodiments described and illustrated herein; -
FIG. 4 depicts a flowchart of a method, according to one or more embodiments described and illustrated herein; -
FIG. 5a depicts a database of applications of personal mobile devices, according to one or more embodiments described and illustrated herein; and -
FIG. 5b depicts a manifest of vehicle features of a vehicle, according to one or more embodiments described and illustrated herein. - Vehicle systems, computing devices, and methods for determining a usage preference for an application on a personal mobile device over a vehicle feature of a vehicle are disclosed herein. In some embodiments, a system obtains application-usage data from a personal mobile device of a vehicle operator of a vehicle. The application-usage data reflects a usage, during operation of the vehicle, of an application on the personal mobile device. The system identifies a vehicle feature, of the vehicle, that provides a vehicle functionality similar to an application functionality provided by the application on the personal mobile device, and performs a comparison of the obtained application-usage data with feature-usage data. The feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle feature. The system determines, based on the comparison, a usage preference for the application during operation of the vehicle over the identified vehicle feature. By determining such usage preferences of vehicle operators, it may be possible to identify vehicle features providing functionality that vehicle operators instead prefer to obtain from applications on personal mobile devices. These identified vehicle features may be removed from vehicles, and subsequently-produced vehicles may be delivered without the identified vehicle features, which may potentially reduce the amount of resources required to produce or operate the vehicles and possibly reduce the costs of the vehicles. Various embodiments of vehicle systems, computing devices, and methods for determining a usage preference for an application over a vehicle feature will now be described in detail with reference to the drawings.
-
FIG. 1 depicts a vehicle system, according to one or more embodiments described and illustrated herein. As shown, asystem 100 includes avehicle 102, a personalmobile device 104, and aserver computer 106, each of which are communicatively connected via anetwork 108 andrespective communication links 110 to the network. Additionally,vehicle 102 is communicatively connected to personalmobile device 104 via alocal communication link 112. Any ofvehicle 102, personalmobile device 104, orserver computer 106, or any combination of these, may be configured to carry out the vehicle-system functions described herein. -
Vehicle 102 could take the form of an autonomous vehicle, a semi-autonomous vehicle, or a manually-operated vehicle, among other possibilities. The vehicle may include a user interface device, and could include a computing device configured to carry out the vehicle functions and/or vehicle-system functions described herein. Additional aspects ofvehicle 102 are described throughout the specification. - Personal
mobile device 104 could include a smartphone, a mobile phone, a tablet computer, a wearable computer, a smartwatch, a head-mounted display, a mobile computing device, or any other personal mobile device configured to carry out the personal-mobile-device functions and/or vehicle-system functions described herein. Personalmobile device 104 may be used by a vehicle operator ofvehicle 102, though it should be understood that the vehicle operator ofvehicle 102 is not limited to a driver of the vehicle. For instance, the vehicle operator could include a passenger of the vehicle, a driver of the vehicle, or a combination of these, as examples. -
Server computer 106 could take the form of a mainframe, a workstation, a terminal, a personal computer, a virtual machine, or any combination of these or other server computers. The server computer could include a computing device configured to carry out the server-computer functions and/or the vehicle-system functions described herein. Thoughsystem 100 is shown as including a single server computer, those of skill in the art will appreciate that the system could include multiple server computers. - Network 108 may include one or more computing systems and network infrastructure configured to facilitate communication between any one or more of
vehicle 102, personalmobile device 104, andserver computer 106. The network may take the form of (or include) one or more Wide-Area Networks (WANs), Local-Area Networks (LANs), the Internet, cellular networks, wired networks, wireless networks, or any combination of these or other networks.Network 108 may operate according to one or more communication protocols such as Ethernet, Wi-Fi, IP, TCP, or LTE, as examples. Thoughnetwork 108 is shown as a single network, it should be understood that the network may include multiple, distinct networks that are communicatively linked.Network 108 could take other forms as well. -
Communication links 110 may communicatively connectvehicle 102, personalmobile device 104, and/orserver computer 106 to network 108 to facilitate communication between these or other entities communicatively connected to the network. Any ofcommunication links 110 could include wired and/or wireless communication links, and could include a combination of hardware and/or software, perhaps operating on one or more communication-link layers such as one or more physical, network, transport, and/or application layers.Communication links 110 may include one or more intermediate paths or systems, for example. - Local communication link 112 may facilitate communication between
vehicle 102 and personalmobile device 104, and could include a wired and/or wireless link. In an embodiment,local communication link 112 facilitates direct communication between the vehicle and the personal mobile device, and the local communication link does not include any intermediate systems, networks, or paths except for those that may be part of the vehicle or the personal mobile device. The local communication link may facilitate communication via a short-range communication protocol, which may include wireless protocols such as Bluetooth, Wi-Fi, near-field communication (NFC), ZigBee, or Z-Wave (as examples), wired protocols such as Universal Serial Bus (USB) or IEEE 1394 (FireWire) (among other possibilities), or a combination of these. It should be understood thatlocal communication link 112 could take other forms as well, including a form similar to any of communication links 110. - Those of skill in the art will appreciate that
system 100 may include different and/or additional entities, and will appreciate that the functions of system 100 (including the functions ofvehicle 102, personalmobile device 104, and/or server computer 106) may be carried out by any combination of entities ofsystem 100. As an example,system 100 could include additional personal mobile devices, and may not includeserver computer 106. Further, one or more ofcommunication links 110 may be absent, such as the communication link between personalmobile device 104 andnetwork 108. As another example,local communication link 112 may be absent. Other variations are possible as well. -
FIG. 2a depicts a user interface device of personalmobile device 104, according to one or more embodiments described and illustrated herein. As shown, auser interface device 200 of the personal mobile device includes adisplay device 202, amicrophone 204, and aspeaker 206. Personalmobile device 104 may receive input (e.g., from a vehicle operator of vehicle 102), and/or provide output (e.g., to the vehicle operator), viauser interface device 200 using one or more of the display device, the microphone, and the speaker. For instance, input may be received by personalmobile device 104 viadisplay device 202,microphone 204, and/or another input component ofuser interface device 200. Additionally, output may be provided by the personal mobile device viadisplay device 202,speaker 206, another output component ofuser interface device 200, or a combination of these. Some components ofuser interface device 200 may facilitate both input and output—for instance,display device 202 could take the form of a touchscreen display device, and personalmobile device 104 may provide output and receive input via the touchscreen display device. It should be understood thatuser interface device 200 may take the form of multiple user interface devices, and may include different and/or additional components. -
FIG. 2b depicts a user interface device ofvehicle 102, according to one or more embodiments described and illustrated herein. As shown, auser interface device 230 ofvehicle 102 includes display device 232 (e.g., a touchscreen display device), pushbuttons control knob 236.Vehicle 102 may receive input from a vehicle operator of the vehicle, and/or provide output to the vehicle operator, viauser interface device 230 using one or more of the display device, the push buttons, and the control knob. For instance, input may be received byvehicle 102 viadisplay device 232, push buttons 234 a-234 d,control knob 236, a microphone ofuser interface device 230, and/or another input component of the user interface device. Additionally, output may be provided by the vehicle viadisplay device 232 and/or another component ofuser interface device 230, such as a speaker of the user interface device. It should be understood thatuser interface device 230 need not take the form of a single, discrete device, but could instead take the form of multiple user interface devices. For instance, the user interface device could include a first user interface device in the form of an automotive head unit that includesdisplay device 232, push buttons 234 a-234 d, andcontrol knob 236, and a second user interface device that includes a microphone and a speaker installed in an interior ofvehicle 102. Additionally,user interface device 230 may include different and/or additional components. -
FIG. 3 depicts a block diagram of a computing device, according to one or more embodiments described and illustrated herein. As shown, acomputing device 300 includes aprocessor 302, adata storage 304 includinginstructions 305, acommunication interface 306, and auser interface module 308, each of which are communicatively connected via asystem bus 310.Vehicle 102, personalmobile device 104,server computer 106, any other entity ofsystem 100, or any combination of these could take the form of (or include)computing device 300. -
Processor 302 may take the form of one or more general-purpose processors and/or one or more special-purpose processors, and may be integrated in whole or in part withdata storage 304,communication interface 306,user interface module 308, and/or any other component ofcomputing device 300, as examples. Accordingly,processor 302 may take the form of or include a controller, an integrated circuit, a microchip, a central processing unit (CPU), a microprocessor, a system on a chip (SoC), a field-programmable gate array (FPGA), and/or an application-specific integrated circuit (ASIC), among other possibilities. -
Data storage 304 may take the form of a non-transitory computer-readable storage medium such as a hard drive, a solid-state drive, an erasable programmable read-only memory (EPROM), a universal serial bus (USB) storage device, a compact disc read-only memory (CD-ROM) disk, a digital versatile disc (DVD), a relational database management system (RDBMS), any other non-volatile storage, or any combination of these, to name just a few examples. -
Instructions 305 may be stored indata storage 304, and may include machine-language instructions executable byprocessor 302 to causecomputing device 300 to perform the computing-device functions and/or vehicle-system functions described herein. Additionally or alternatively,instructions 305 may include script instructions executable by a script interpreter configured to causeprocessor 302 andcomputing device 300 to execute the instructions specified in the script instructions. It should be understood thatinstructions 305 may take other forms as well. - Additional data may be stored in
data storage 304, such as a database of applications of personal mobile devices and/or a manifest of vehicle features of one or more vehicles, as will be described in further detail below. The additional data could be stored as a table, a flat file, data in a file system of the data storage, a heap file, a B+ tree, a hash table, a hash bucket, or any combination of these, as examples. -
Communication interface 306 may be any component capable of performing the communication-interface functions described herein, including facilitating wired and/or wireless communication betweencomputing device 300 and another entity (such as an entity of system 100). As such,communication interface 306 could take the form of a Bluetooth, Wi-Fi, USB, and/or LTE interface, among many other examples.Communication interface 306 may receive data overnetwork 108 via one or more ofcommunication links 110 andlocal communication link 112, for instance. -
User interface module 308 may be any component capable of carrying out the user-interface-module functions described herein. For example, the user interface module may includeuser interface device 200 of personalmobile device 104,user interface device 230 ofvehicle 102, or another user interface device, and could further include other hardware and/or software for realizing input and/or output via the user interface device. -
System bus 310 may be any component capable of performing the system-bus functions described herein. In an embodiment,system bus 310 is any component configured to transfer data betweenprocessor 302,data storage 304,communication interface 306,user interface module 308, and/or any other component ofcomputing device 300. In an embodiment,system bus 310 includes a traditional bus as is known in the art. In other embodiments,system bus 310 includes a serial RS-232 communication link, a USB communication link, and/or an Ethernet communication link, alone or in combination with a traditional computer bus, among numerous other possibilities. In some examples,system bus 310 may be formed from any medium that is capable of transmitting a signal, such as conductive wires, conductive traces, or optical waveguides, among other possibilities. Moreover,system bus 310 may be formed from a combination of mediums capable of transmitting signals. The system bus could take the form of (or include) a vehicle bus, such as a local interconnect network (LIN) bus, a controller area network (CAN) bus, a vehicle area network (VAN) bus, or any combination of these or mediums.System bus 310 may take various other forms as well. - It should be understood that
computing device 300 may include different and/or additional components, and some or all of the functions of a given component could instead be carried out by one or more different components. Additionally,computing device 300 could take the form of (or include) multiple computing devices, and some or all of the functions of a given component could be carried out by any combination of one or more of the computing devices. -
FIG. 4 depicts a flowchart of a method carried out by a vehicle system, according to one or more embodiments described and illustrated herein. As shown, amethod 400 begins at step 402 withsystem 100 obtaining application-usage data from personalmobile device 104 of a vehicle operator ofvehicle 102. - The application could be a computer program or software application executed by personal
mobile device 104. The application may provide application functionality such as mapping and navigation, media playback (including playback of audio, video, music, and/or podcasts), text messaging (e.g., SMS), telephony, and/or data tethering, among other possibilities. In an example, the application includes application instructions stored on a data storage of personal mobile device 104 (such asdata storage 304 of the personal mobile device). The application instructions, when executed by a processor of the personal mobile device, cause the personal mobile device to provide the functionality of the application. - The application-usage data reflects a usage of an application on personal
mobile device 104 during operation ofvehicle 102. For instance, the application-usage data may reflect usage of the application by the vehicle operator of the vehicle—such as a driver of the vehicle and/or a passenger of the vehicle, among other examples. The application-usage data may reflect usage of the application viauser interface device 200 of personalmobile device 104—for instance, viadisplay device 202,microphone 204, andspeaker 206.Display device 202 could include a touchscreen display, and usage of the application viadisplay device 202 could include a tapping, pressing, or swiping of the vehicle operator's fingers on the touchscreen display. As a further possibility, usage of the application could include words or utterances spoken to (e.g., received by)microphone 204 by the vehicle operator. Additionally, usage of the application could include a display presented bydisplay device 202 to the vehicle operator, and/or audio generated for the vehicle operator byspeaker 206. For instance, if the vehicle operator is navigating to a given destination and the application provides navigation functionality, then the display could include display of a map or a list of turn-by-turn directions ondisplay device 202. - In an embodiment, personal
mobile device 104 includes an operating system (e.g., an operating system executed by the personal mobile device). The operating system could include operating-system instructions that are stored on a data storage of the personal mobile device and that, when executed by a processor of the personal mobile device, cause the personal mobile device to execute the operating system. For instance, usage of the application could include usage detected by the operating system while the application is in a foreground of a shell of the operating system. In such a case, the application-usage data could include application-usage data (e.g., logs files, a screenshot ofdisplay device 202 of personal mobile device 104) that is generated by the operating system and that reflects the usage detected by the operating system while the application is in the foreground of the shell. As another example, usage of the application could include usage detected by the application based on data received by the application from the operating system. For example, usage of the application could include usage while the application is in a foreground of a shell of an operating system of the personal mobile device, and/or while the application is in a background of the operating system (e.g., while the application is executed as a background process by the operating system). In such a case, the application-usage data could include application-usage data (e.g., log files, a screenshot ofdisplay device 202, and/or a screenshot of the application as captured by the app) that is generated by the application and that reflects usage of the application (as detected by the app). - The application-usage data reflecting usage of the application may include data reflecting an amount of time that the application was displayed by personal
mobile device 104 viadisplay device 202 of the personal mobile device, and/or a number of times that the application was displayed by the personal mobile device viadisplay device 202. As another possibility, the application-usage data reflecting usage of the application may include an amount of time that the vehicle operator interacted with the application, and/or a number of times that the vehicle operator interacted with the application. As a further possibility, the application-usage data reflecting usage of the application may include a number of times that the application was launched on personalmobile device 104 by the vehicle operator (e.g., via an operating system of the mobile device), and/or a number of times that the application was brought to a foreground of a shell of an operating system of the personal mobile device. It should be understood that the application-usage data may include data reflecting any combination of these or other usage of the application. - In some cases, the application-usage data may reflect usage of the application on personal
mobile device 104 viauser interface device 230 ofvehicle 102. For instance,vehicle 102 may establish a remote-interface connection with personalmobile device 104 vialocal communication link 112. Subsequent to establishing the connection, the personal mobile device may provide output to the vehicle operator by causing the vehicle to provide the output via user interface device 230 (e.g., via display device 232) ofvehicle 102. As an example, if the vehicle operator is navigating to a given destination and the application provides navigation functionality, then usage of the application could include a display, presented bydisplay device 232 ofvehicle 102, of a map or a list of turn-by-turn directions. Additionally, the personal mobile device may receive input from a vehicle operator of the vehicle by causing the vehicle to receive the input via user interface device 230 (e.g., viadisplay device 232, push buttons 234 a-234 d, and/or control knob 236) ofvehicle 102, which may then be received by the personal mobile device. Other examples are possible as well. - Operation of
vehicle 102 may include an ignition-on cycle of the vehicle, and usage of the application during operation of the vehicle could include usage of the application during the ignition-on cycle. An ignition-on cycle could begin at an ignition-on ofvehicle 102, for instance, and could end at an ignition-off of the vehicle, among other examples. As another possibility, operation ofvehicle 102 may include an accessory power-on cycle of the vehicle, and usage of the application during operation of the vehicle could include usage of the application during the accessory power-on cycle. An accessory power-on cycle could begin at an accessory power-on ofvehicle 102, for example, and could end at an accessory power-off of the vehicle. Other examples of operation ofvehicle 102 as possible as well, as are examples of usage of the application during operation of the vehicle. - Obtaining the application-usage data from personal
mobile device 104 may includevehicle 102 obtaining the application-usage data from the personal mobile device via (wired and/or wireless)local communication link 112. Obtaining the application-usage data from the personal mobile device vialocal communication link 112 could include establishing a remote-interface connection with personalmobile device 104 via local communication link 112 (as discussed above), and obtaining the application-usage data from the personal mobile device over the remote-interface connection vialocal communication link 112. - As another possibility, obtaining the application-usage data from personal
mobile device 104 could includeserver computer 106 obtaining the application-usage data from the personal mobile device overnetwork 108 via respective communication links 110 (e.g., LTE communication links) between the server computer and the network and between the network and the personal mobile device. As a further possibility, obtaining the application-usage data could includevehicle 102 obtaining the application-usage data from personalmobile device 104 overnetwork 108 via respective communication links 110 (e.g., LTE communication links) between the vehicle and the network and between the network and the personal mobile device. It should be understood that obtaining the application-usage data from personalmobile device 104 may take other forms as well. - At
step 404,system 100 identifies a vehicle feature, ofvehicle 102, that provides a vehicle functionality similar to an application functionality provided by the application on personalmobile device 104. For instance,system 100 may identify a vehicle application, executed byvehicle 102, that provides a vehicle functionality similar to an application functionality provided by the mobile-device application executed by personalmobile device 104. - The vehicle feature could be a computer program or software application executed by
vehicle 102. The vehicle feature may provide vehicle functionality such as mapping, navigation, media playback (including playback of audio, video, music, and/or podcasts), text messaging (e.g., SMS), telephony, and/or data tethering, among other possibilities. In an example, the vehicle features takes the form of (or includes) vehicle-feature instructions stored on a data storage of vehicle 102 (such asdata storage 304 of the vehicle). The vehicle-feature instructions, when executed by a processor of the vehicle, cause the vehicle to provide the functionality of the vehicle feature. As another possibility, the vehicle feature could take the form of an electronic control unit (ECU). Other examples are possible as well. - In an embodiment, identifying the vehicle feature of
vehicle 102 that provides the vehicle functionality similar to the application functionality includes determining the application functionality and identifying, from a manifest of respective vehicle functionalities provided by one or more vehicle features, a vehicle functionality similar to the determined application. - In an embodiment identifying the vehicle feature of
vehicle 102 that provides the vehicle functionality similar to the application functionality includes determining the application functionality and identifying, from among respective vehicle functionalities provided by one or more vehicle features, a vehicle functionality similar to the determined application functionality. In such an embodiment, identifying the vehicle features includes obtaining a feature identification of the vehicle feature that provides the identified vehicle functionality. Several examples of identifying the vehicle feature are provided below with reference toFIGS. 5a and 5 b. -
FIG. 5a depicts a database of applications of personal mobile devices, andFIG. 5b depicts a manifest of vehicle features of a vehicle, according to one or more embodiments described and illustrated herein. As shown inFIG. 5a , adatabase 500 of applications of personal mobile devices includesapplications respective application ID 512 and a respectiveapplication functionality indication 514. As shown inFIG. 5b , amanifest 550 of vehicle features ofvehicle 102 includes vehicle features 552, 554, and 556. For each vehicle feature, the manifest includes a respectivevehicle feature ID 562 and a respectivevehicle functionality indication 564. - With reference to
FIG. 5a , determining the application functionality may include obtaining anapplication ID 512 of the application on personalmobile device 104. For instance, the application could have been downloaded from an application repository (such as an application marketplace), which may have assigned the application with an application ID unique to the application. Subsequent to downloading the application, the personal mobile device may have installed the application and concurrently saved the unique application ID for the application to a data storage of the personal mobile device. In such a case, obtaining the application ID may involve obtaining the application ID from the data storage. Determining the application functionality may then include identifying an application, from amongdatabase 500 of applications, having the same application ID as that obtained from the data storage. For instance, the application ID of the application on personalmobile device 104 could be “Audio App 2”, and identifying an application, from amongdatabase 500 of applications having the same application ID as the application ID obtained from the data storage may include identifyingapplication 508, which also has an application ID of “Audio App 2”. - Determining the application functionality may include determining the application functionality based on an obtained application ID of the application on personal
mobile device 104. For instance, with reference toFIG. 5a , determining the application functionality based on the obtained application ID of “Audio App 2” for the application on personal mobile device 104 (which is also the application ID ofapplication 508 in database 500) may include retrieving the respectiveapplication functionality indication 514 ofapplication 508 having thesame application ID 512 as the obtained application ID. As shown inFIG. 5a , the respectiveapplication functionality indication 514 ofapplication 508 is “Music”. - Identifying the vehicle functionality similar to the determined application functionality may include identifying, from among
manifest 550 of vehicle features, avehicle functionality indication 564 that is the same as (and/or similar to)application functionality indication 514 of the application in database 500 (retrieved as described above) that has thesame application ID 512 as the obtained application ID for the application on personalmobile device 104. For instance, with reference toFIG. 5b , identifying avehicle functionality indication 564 that is the same as or similar toapplication functionality indication 514 may include identifyingvehicle feature 554, which has a respectivevehicle functionality indication 564 of “Music” that is the same asapplication functionality indication 514 of application 508 (as retrieved in the manner described above). - Obtaining the feature identification of the vehicle feature that provides the identified vehicle functionality may include retrieving respective
vehicle feature ID 562 of the vehicle feature having respective vehicle functionality indication 564 (as identified in the manner discussed above) that is the same as (and/or similar to) application functionality indication 514 (as retrieved in the manner described above). For instance, with reference toFIG. 5b , retrieving respectivevehicle feature ID 562 may include retrieving the respective vehicle feature ID ofvehicle feature 554, which has respectivevehicle functionality indication 564 that is the same as respectiveapplication functionality indication 514 ofapplication 508 indatabase 500. - Referring back to
FIG. 4 , atstep 406,system 100 performs a comparison of the application-usage data obtained at step 402 with feature-usage data. The feature-usage data reflects a usage, during operation ofvehicle 102, of the vehicle feature identified atstep 404. For example,system 100 may perform a comparison of the obtained application-usage data with feature-usage data that reflects a usage, during operation ofvehicle 102, of the identified vehicle application. In some cases, the feature-usage data may reflect that the vehicle feature was not used during operation of the vehicle. - The usage of the identified vehicle feature may take a form similar to usage of the application on personal
mobile device 104 as described above with reference to step 402, and the feature-usage data may take a form similar to the application-usage data obtained at step 402. For instance, the feature-usage data may reflect usage of the vehicle feature by the vehicle operator of the vehicle, such as a driver of the vehicle and/or a passenger of the vehicle, among other examples. The feature-usage data may reflect usage of the vehicle feature viauser interface device 230 ofvehicle 102—for instance, viadisplay device 232, push buttons 234 a-234 d, and/orcontrol knob 236.Display device 232 could include a touchscreen display, and usage of the vehicle feature viadisplay device 232 could include a tapping, pressing, or swiping of the vehicle operator's fingers on the touchscreen display and/or a display presented bydisplay device 232 to the vehicle operator. As a further possibility, usage of the vehicle feature could include words or utterances spoken to (e.g., received by) a microphone ofuser interface device 230 by the vehicle operator, and/or audio generated for the vehicle operator by a speaker ofuser interface device 230 ofvehicle 102. For instance, the vehicle feature could include a podcast application executed byvehicle 102, and usage of the vehicle feature could include audio generated for playback of a podcast by the podcast application, or could include tapping of the vehicle operator's fingers on display device 232 (which could be a touchscreen display, for instance). - In an embodiment,
vehicle 102 includes an operating system (e.g., an operating system executed by the vehicle). The operating system could include operating-system instructions that are stored on a data storage of the vehicle and that, when executed by a processor of the vehicle, cause the vehicle to execute the operating system. For instance, usage of the vehicle feature could include usage detected by the operating system while the vehicle feature is in a foreground of a shell of the operating system. In such a case, the feature-usage data could include feature-usage data (e.g., logs files, a screenshot ofdisplay device 232 of vehicle 102) that is generated by the operating system and that reflects the usage detected by the operating system while the vehicle feature is in the foreground of the shell. As another example, usage of the vehicle feature could include usage detected by the vehicle feature itself based on data received by the vehicle feature from the operating system. For example, usage of the vehicle feature could include usage while the vehicle feature is in a foreground of a shell of an operating system of the vehicle, and/or while the vehicle feature is in a background of the operating system (e.g., while the vehicle feature is executed as a background process by the operating system). In such a case, the feature-usage data could include feature-usage data (e.g., log files, a screenshot ofdisplay device 232, and/or a screenshot of the vehicle feature as captured by the vehicle feature) that is generated by the vehicle feature and that reflects usage of the vehicle feature (as detected by the vehicle feature). - The feature-usage data reflecting usage of the vehicle feature may include data reflecting an amount of time that the vehicle feature was displayed by
vehicle 102 viadisplay device 232 of the vehicle, and/or a number of times that the vehicle feature was displayed by the vehicle viadisplay device 232. In such an example, performing the comparison of the application-usage data with feature-usage data could include comparing this amount of time and/or number of times, with an amount of time that the application on personalmobile device 104 was displayed by personalmobile device 104 viadisplay device 202 of the personal mobile device and/or a number of times that the application was displayed by the personal mobile device viadisplay device 202. As another possibility, the feature-usage data reflecting usage of the vehicle feature may include an amount of time that the vehicle operator interacted with the vehicle feature, and/or a number of times that the vehicle operator interacted with the vehicle feature. In such an example, performing the comparison of the application-usage data with feature-usage data could include comparing this amount of time and/or number of times, with an amount of time that the vehicle operator interacted with the application, and/or a number of times that the vehicle operator interacted with the application. - As a further possibility, the feature-usage data reflecting usage of the vehicle feature may include a number of times that the vehicle feature was launched on
vehicle 102 by the vehicle operator (e.g., via an operating system of the mobile device), and/or a number of times that the vehicle feature was brought to a foreground of a shell of an operating system of the vehicle. In such a case, performing the comparison of the application-usage data with feature-usage data could include comparing either or both of these numbers of times with a number of times that the application was launched on personalmobile device 104 by the vehicle operator (e.g., via an operating system of the mobile device), and/or comparing either or both of these numbers with a number of times that the application was brought to a foreground of a shell of an operating system of the personal mobile device. It should be understood that the feature-usage data may include data reflecting any combination of these or other usage of the vehicle features. - At
step 408,system 100 determines, based on the comparison performed atstep 406, a usage preference for the application during operation ofvehicle 102 over the vehicle feature identified atstep 404. For example,system 100 may determine, based on the comparison, a usage preference for the application during operation of the vehicle over a vehicle application (e.g., a software application executed by the vehicle) identified atstep 404. The usage preference may reflect a preference of the vehicle operator to use the application over the vehicle feature, and may reflect a preference to utilize application functionality provided by the application over similar functionality provided by the vehicle feature. - Determining the usage preference could include generating a report based on the determined usage preference. The report could indicate the usage preference, and could include some or all of the application-usage data and/or the feature-usage data. In some cases,
method 400 may be performed for each of a plurality of vehicle operators, and the generated report could indicate respective usage preferences for each of the vehicle operators (and/or an aggregate usage preference). For instance, system 100 (e.g., server computer 106) could obtain application-usage data from respective personal mobile devices of each of the vehicle operators, and identify a vehicle functionality that provides functionality similar to respective application functionality provided by respective applications on the personal mobile devices. The system could perform a comparison of the obtained application-usage data with feature-usage data that reflects usage of the identified vehicle feature, and based on the comparison, could determine respective usage preferences (and/or an aggregate usage preference) for the applications over the identified vehicle feature. The generated report (whether generated for a given vehicle operator or for multiple vehicle operators) could then be presented via a user interface—e.g., to a user via a user interface. For instance, the generated report could be presented viauser interface device 230 ofvehicle 102, and/or could be presented via a user interface ofserver computer 106. As another possibility, the report could be generated byserver computer 106 and presented by the server computer via a user interface of a different entity ofsystem 100—the different entity receives the report fromserver computer 106 and presents the received report via a user interface of the entity. Other examples are possible as well. - Determining the usage preference could include removing, from
vehicle 102, the vehicle feature (identified at step 404) in response to determining the usage preference. For instance, the vehicle feature could include a vehicle application (e.g., a software application) executed by the vehicle.Vehicle 102 could determine the usage preference and responsively uninstall the vehicle application from the vehicle. Additionally or alternatively, personalmobile device 104 and/orserver computer 106 may determine the usage preference, and in response to determining the usage preference, may send an instruction tovehicle 102 to uninstall the application. Upon receiving the instructions, the vehicle could then uninstall the application. The instruction could be sent tovehicle 102 overnetwork 108 andcommunication links 110, and/or could be sent to the vehicle vialocal communication link 112. It should be understood that determining the usage preference could take numerous other forms as well. - It should now be understood that embodiments described herein are directed to vehicle systems, computing devices, and methods for determining a usage preference for an application on a personal mobile device over a vehicle feature of a vehicle. In some embodiments, a system obtains application-usage data from a personal mobile device of a vehicle operator of a vehicle. The application-usage data reflects a usage, during operation of the vehicle, of an application on the personal mobile device. The system identifies a vehicle feature, of the vehicle, that provides a vehicle functionality similar to an application functionality provided by the application on the personal mobile device, and performs a comparison of the obtained application-usage data with feature-usage data. The feature-usage data reflects a usage, during operation of the vehicle, of the identified vehicle feature. The system determines, based on the comparison, a usage preference for the application during operation of the vehicle over the identified vehicle feature.
- It is noted that the terms “substantially” and “about” may be utilized herein to represent the inherent degree of uncertainty that may be attributed to any quantitative comparison, value, measurement, or other representation. These terms are also utilized herein to represent the degree by which a quantitative representation may vary from a stated reference without resulting in a change in the basic function of the subject matter at issue.
- While particular embodiments have been illustrated and described herein, it should be understood that various other changes and modifications may be made without departing from the spirit and scope of the claimed subject matter. Moreover, although various aspects of the claimed subject matter have been described herein, such aspects need not be utilized in combination. It is therefore intended that the appended claims cover all such changes and modifications that are within the scope of the claimed subject matter.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/599,557 US11536581B2 (en) | 2019-10-11 | 2019-10-11 | Methods and systems for determining a usage preference of a vehicle operator |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/599,557 US11536581B2 (en) | 2019-10-11 | 2019-10-11 | Methods and systems for determining a usage preference of a vehicle operator |
Publications (2)
Publication Number | Publication Date |
---|---|
US20210108938A1 true US20210108938A1 (en) | 2021-04-15 |
US11536581B2 US11536581B2 (en) | 2022-12-27 |
Family
ID=75382194
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/599,557 Active 2041-01-06 US11536581B2 (en) | 2019-10-11 | 2019-10-11 | Methods and systems for determining a usage preference of a vehicle operator |
Country Status (1)
Country | Link |
---|---|
US (1) | US11536581B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220398055A1 (en) * | 2021-06-11 | 2022-12-15 | The Procter & Gamble Company | Artificial intelligence based multi-application systems and methods for predicting user-specific events and/or characteristics and generating user-specific recommendations based on app usage |
WO2023008992A1 (en) * | 2021-07-30 | 2023-02-02 | Maxis Broadband Sdn. Bhd. | Methods, systems, and devices for managing user vehicular operation, activity, and safety |
US11875468B2 (en) | 2021-06-29 | 2024-01-16 | The Procter & Gamble Company | Three-dimensional (3D) image modeling systems and methods for determining respective mid-section dimensions of individuals |
US11967031B2 (en) | 2021-06-11 | 2024-04-23 | The Procter & Gamble Company | Digital imaging analysis of biological features detected in physical mediums |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160144714A1 (en) * | 2014-11-20 | 2016-05-26 | Toyota Motor Engineering & Manufacturing North America, Inc. | System for synchronization of applications between vehicle head unit and companion device |
US10104564B1 (en) * | 2017-04-13 | 2018-10-16 | The Nielsen Company (Us), Llc | Methods and apparatus to determine mobile device application usage in vehicles including media applications |
US20190073412A1 (en) * | 2017-09-05 | 2019-03-07 | Samsung Electronics Co., Ltd. | Personalized automatic tagging |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5653354B2 (en) * | 2008-08-11 | 2015-01-14 | ティーティーアイ インベンションズ ディー エルエルシー | System and method for using networked mobile devices in a vehicle |
US10824330B2 (en) * | 2011-04-22 | 2020-11-03 | Emerging Automotive, Llc | Methods and systems for vehicle display data integration with mobile device data |
US9285944B1 (en) * | 2011-04-22 | 2016-03-15 | Angel A. Penilla | Methods and systems for defining custom vehicle user interface configurations and cloud services for managing applications for the user interface and learned setting functions |
US9665991B2 (en) * | 2011-06-30 | 2017-05-30 | Accenture Global Services Limited | Tolling using mobile device |
DE102012005054A1 (en) * | 2012-03-15 | 2013-09-19 | Volkswagen Aktiengesellschaft | Method, mobile device and infotainment system for projecting a user interface on a screen |
KR101914097B1 (en) * | 2012-09-07 | 2018-11-01 | 삼성전자주식회사 | Apparatus and method for driving application for vehicle interworking mobile device |
US9436428B2 (en) * | 2012-11-08 | 2016-09-06 | Ebay Inc. | Methods, apparatus, and system for mobile piggybacking |
CN104919833B (en) * | 2012-12-20 | 2019-11-08 | 爱尔比奎特公司 | Efficient head unit communication is integrated |
US10655979B2 (en) * | 2013-06-08 | 2020-05-19 | Apple Inc. | User interface for displaying predicted destinations |
US9883353B2 (en) * | 2013-03-15 | 2018-01-30 | Volkswagen Ag | Method to transmit real-time in-vehicle information to an internet service |
US10251034B2 (en) * | 2013-03-15 | 2019-04-02 | Blackberry Limited | Propagation of application context between a mobile device and a vehicle information system |
US10477454B2 (en) * | 2013-05-08 | 2019-11-12 | Cellcontrol, Inc. | Managing iOS-based mobile communication devices by creative use of CallKit API protocols |
US9508199B2 (en) | 2013-08-09 | 2016-11-29 | Honda Motor Co., Ltd. | Mobile device communicating with motor vehicle system |
US20150195669A1 (en) * | 2014-01-06 | 2015-07-09 | Ford Global Technologies, Llc | Method and system for a head unit to receive an application |
US20150262198A1 (en) * | 2014-03-13 | 2015-09-17 | GM Global Technology Operations LLC | Method and apparatus of tracking and predicting usage trend of in-vehicle apps |
US10089053B2 (en) * | 2014-08-01 | 2018-10-02 | Volkswagen Ag | Mirroring deeplinks |
US10180832B2 (en) | 2014-11-14 | 2019-01-15 | George Stantchev | Application matching method for mobile device and accessory method |
US10093197B2 (en) * | 2015-12-22 | 2018-10-09 | Ford Global Technologies, Llc | Key off energy management system |
US9979813B2 (en) | 2016-10-04 | 2018-05-22 | Allstate Solutions Private Limited | Mobile device communication access and hands-free device activation |
US9988016B1 (en) | 2016-12-07 | 2018-06-05 | Ford Global Technologies, Llc | Authentication of mobile devices for vehicle communication |
-
2019
- 2019-10-11 US US16/599,557 patent/US11536581B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160144714A1 (en) * | 2014-11-20 | 2016-05-26 | Toyota Motor Engineering & Manufacturing North America, Inc. | System for synchronization of applications between vehicle head unit and companion device |
US10104564B1 (en) * | 2017-04-13 | 2018-10-16 | The Nielsen Company (Us), Llc | Methods and apparatus to determine mobile device application usage in vehicles including media applications |
US20190073412A1 (en) * | 2017-09-05 | 2019-03-07 | Samsung Electronics Co., Ltd. | Personalized automatic tagging |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220398055A1 (en) * | 2021-06-11 | 2022-12-15 | The Procter & Gamble Company | Artificial intelligence based multi-application systems and methods for predicting user-specific events and/or characteristics and generating user-specific recommendations based on app usage |
US11967031B2 (en) | 2021-06-11 | 2024-04-23 | The Procter & Gamble Company | Digital imaging analysis of biological features detected in physical mediums |
US11875468B2 (en) | 2021-06-29 | 2024-01-16 | The Procter & Gamble Company | Three-dimensional (3D) image modeling systems and methods for determining respective mid-section dimensions of individuals |
WO2023008992A1 (en) * | 2021-07-30 | 2023-02-02 | Maxis Broadband Sdn. Bhd. | Methods, systems, and devices for managing user vehicular operation, activity, and safety |
Also Published As
Publication number | Publication date |
---|---|
US11536581B2 (en) | 2022-12-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11536581B2 (en) | Methods and systems for determining a usage preference of a vehicle operator | |
US11205421B2 (en) | Selection system and method | |
US8855575B2 (en) | Device-vehicle interoperability verification method | |
US9578668B2 (en) | Bluetooth pairing system and method | |
US9674331B2 (en) | Transmitting data from an automated assistant to an accessory | |
US10742575B2 (en) | Coordination of data received from one or more sources over one or more channels into a single context | |
US9071568B2 (en) | Customer-identifying email addresses to enable a medium of communication that supports many service providers | |
US20150193090A1 (en) | Method and system for application category user interface templates | |
US8762059B1 (en) | Navigation system application for mobile device | |
CN109656923B (en) | Data processing method and device, electronic equipment and storage medium | |
US9974100B2 (en) | In-vehicle unit, communication system, communication method, and program | |
US20120296494A1 (en) | Remote operator assistance for one or more user commands in a vehicle | |
US20150195669A1 (en) | Method and system for a head unit to receive an application | |
US20210097787A1 (en) | Information presentation method and apparatus | |
WO2017181909A1 (en) | Transport vehicle control method, control device, and control system | |
US10149137B2 (en) | Enhanced communication system | |
CN111324470A (en) | Method and device for generating information | |
JP2015148831A (en) | On-vehicle information system, information terminal, and application execution method | |
KR20160037535A (en) | Mirroring device in vehicle and pairng method thereof | |
KR101647111B1 (en) | Audio Video Navigation control System There of Method | |
CN113849416A (en) | Test method, test device, storage medium and electronic equipment | |
CN112116733A (en) | Backup and acquisition method and system of vehicle Bluetooth key and electronic equipment | |
JP6183271B2 (en) | In-vehicle device and program | |
US20150317973A1 (en) | Systems and methods for coordinating speech recognition | |
CN111031499A (en) | Address book-based position sharing method and system, storage medium and terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: TOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WILLIAMS, CLINTON;REEL/FRAME:050719/0843 Effective date: 20191008 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction |