Provisioning vehicle application to in-vehicle infotainment system to support user device detected in vehicle

Abstract

To provide a method, a vehicle information system, and non-transitory computer-readable media.SOLUTION: A device is detected in a vehicle. In response to detecting the device in the vehicle, an application is provided to an In-Vehicle Infotainment (IVI) system to collect information and provide a service to a user based on the collected information. The information collected from the detected device by the application provisioned to the IVI system is received. In response to receiving the information, an action is automatically triggered by the IVI system for the service based on the information collected by the application.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present specification relates to provisioning vehicle applications to an in-vehicle infotainment (IVI) system to support user devices detected in a vehicle, and methods of using the vehicle applications. [Background technology]

[0002] New vehicles now have sensors and various devices that collect data about the vehicle and driver. Fleet management systems allow fleet operators to monitor and manage their fleets of vehicles, including tracking fuel diagnostics, optimizing routes, and scheduling maintenance to improve efficiency and reduce costs. Additionally, cloud-connected Internet of Things (IoT) boxes link to telematics devices to provide real-time data on driver health and vehicle status. The systems share statistics about driver performance and health, detect drowsiness, and send idle alarms.

[0003] Wearable devices are also on the rise, with one of the most popular forms of wearable devices being fitness bands, watches, smart rings, and trackers that record and report a user's activity, location, and biometric data. Integrating wearable devices into connected cars can provide numerous benefits to drivers and passengers in areas related to safety, infotainment experience, and more.

[0004] Vehicles currently cannot obtain or collect any information from such sensors and devices. For example, an in-vehicle infotainment (IVI) system (also simply referred to as an infotainment system) can detect and pair wearable devices using wireless communication, e.g., Bluetooth®. However, because the vehicle does not have sensors or appropriate, accurate algorithms to identify and connect to the user device, the vehicle is technically unable to gather accurate or detailed information from the user's wearable device. Although the wearable device can obtain information related to the state of the user and the environment, it is not configured to communicate with the infotainment system to provide the relevant information. Therefore, the vehicle cannot collect information from the user's wearable device and use the information to provide a natural experience or real-world applications inside the vehicle. Summary of the Invention

[0005] In at least some embodiments, a processor-executed method for provisioning an application to an in-vehicle infotainment (IVI) system in a vehicle includes detecting a device in the vehicle; in response to detecting the device in the vehicle, provisioning an application to the IVI system to collect information from the detected device and provide a service to a user based on the collected information; receiving the information collected from the detected device by the application provisioned to the IVI system; and in response to receiving the information, automatically triggering an operation for the service by the IVI system based on the information collected by the application from the detected device.

[0006] In at least one embodiment, a vehicle information system includes a memory storing computer-readable instructions and a processor coupled to the memory, the processor configured to execute the computer-readable instructions to perform operations to detect a device in the vehicle, in response to detecting the device in the vehicle, provision an application to collect information from the detected device, provide a service to a user based on the collected information, receive information collected from the detected device by the application provisioned to collect information from the detected device, and in response to receiving the information, automatically trigger an operation for the service based on the information collected by the application from the detected device.

[0007] In at least one embodiment, a computer program having computer-readable instructions stored thereon that, when executed by a processor, cause the processor to perform operations including: detecting a device in a vehicle; in response to detecting the device in the vehicle, provisioning an application in an in-vehicle infotainment (IVI) system to collect information from the detected device and provide a service to a user based on the collected information; receiving the information collected from the detected device by the application provisioned to the IVI system; and in response to receiving the information, automatically triggering an operation for the service by the IVI system based on the information collected by the application from the detected device. [Brief explanation of the drawings]

[0008] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. It should be noted that, according to industry practice, various features have not been drawn to scale. In fact, the dimensions of various features may be increased or decreased for clarity of illustration.

[0009] [Figure 1] FIG. 1 illustrates a vehicle cockpit according to at least one embodiment. [Figure 2] FIG. 2 is a block diagram of a system for providing an application for detecting user devices in a vehicle and collecting information from the detected user devices, according to at least one embodiment. [Figure 3] FIG. 3 illustrates a process for pairing devices, according to at least one embodiment. [Figure 4] FIG. 4 illustrates a flowchart of a method for monitoring the status of a customer device, according to at least one embodiment. [Figure 5] FIG. 5 illustrates an in-vehicle infotainment (IVI) GUI for obtaining customer service, according to at least one embodiment. [Figure 6] FIG. 6 illustrates the application store GUI when the application store is accessed, according to at least one embodiment. [Figure 7] FIG. 7 illustrates an in-cabin application GUI according to at least one embodiment. [Figure 8] FIG. 8 is a ring wearable device GUI according to at least one embodiment. [Figure 9] FIG. 9 is a ring wearable device 1234568 GUI according to at least one embodiment. [Figure 10] FIG. 10 is an application description GUI according to at least one embodiment. [Figure 11] FIG. 11 is a flowchart of a method for provisioning an application in an in-vehicle infotainment (IVI) system to collect information from devices detected in a vehicle, according to at least one embodiment. [Figure 12] FIG. 12 is a high-level functional block diagram of a processor-based system according to at least one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] The embodiments described herein set forth examples of implementing various features of the provided subject matter. To simplify the disclosure, examples of components, values, operations, materials, arrangements, or the like are described below. Of course, these are examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, or the like are contemplated. For example, the formation of a first feature above or on a second feature in the following description includes embodiments in which the first and second features are formed in direct contact, as well as embodiments in which an additional feature is formed between the first and second features such that the first and second features are not in direct contact. Additionally, the present disclosure repeats reference numerals and / or letters in various examples. This repetition is for the purposes of brevity and clarity and does not dictate a relationship between the various embodiments and / or configurations described.

[0011] Additionally, spatially relative terms such as "lower," "below," "belower than," "upper," "above," and the like are used herein for ease of description to describe the relationship of one element or feature to another element or feature as shown in the figures. Spatially relative terms are intended to encompass various orientations of the device in use or operation in addition to the orientation depicted in the figures. The device may be oriented differently (rotated 90 degrees or at other orientations), and the spatially relative descriptions used herein interpreted accordingly.

[0012] Terms such as "user equipment," "mobile station," "mobile," "mobile device," "subscriber station," "subscriber equipment," "access terminal," "terminal," "headset," and similar terms refer to wireless devices utilized by subscribers or users of wireless communication services to receive or transmit data, control, voice, video, audio, gaming, data streaming, or signaling streaming. These terms are used interchangeably in the subject specification and related drawings.

[0013] In at least one embodiment, a method for provisioning an application to an in-vehicle infotainment (IVI) system in a vehicle includes detecting a device in the vehicle; in response to detecting the device in the vehicle, provisioning an application to the IVI system to collect information from the detected device and provide a service to a user based on the collected information; receiving the information collected from the detected device by the application provisioned to the IVI system; and in response to receiving the information, automatically triggering an operation for the service by the IVI system based on the information collected by the application from the detected device.

[0014] The embodiments described herein provide one or more advantages. For example, by detecting a user device in a vehicle and provisioning an application to an IVI system, the user device can be configured to communicate with the IVI system via the application to collect information and enable the IVI system to provide a natural experience inside the vehicle, such as sending notifications to the user in response to determining that the user is falling asleep, adjusting the temperature in the vehicle to a more comfortable level, making automatic payments, and the like.

[0015] FIG. 1 illustrates a vehicle cockpit 100 according to at least one embodiment.

[0016] In FIG. 1 , the vehicle cockpit includes a steering wheel 110, an accelerator pedal 112, a brake pedal 114, an instrument panel 120, an infotainment system 130, and a climate control system 140. The climate control system 140 is sometimes referred to as a heating, ventilation, and air conditioning (HVAC) system. The steering wheel is part of the steering system operated by the driver to control the steering system and direction of the vehicle. By operating the steering wheel 110, the driver directs the front wheels of the vehicle through a linkage system. The accelerator pedal 112 is used to control the supply of fuel and air to the engine through the application of pressure. The accelerator pedal 112 is also known as a throttle or gas pedal. The brake pedal 114 is pressed to apply the brakes, thereby slowing and / or stopping the vehicle.

[0017] The instrument panel 120 is the portion of the dashboard located behind the steering wheel 110. The instrument panel 120 includes various gauges and lights that provide the driver with up-to-date information about the vehicle's status. For example, the instrument panel 120 often includes a traction control indicator, engine temperature, a tachometer, a fuel gauge, a speedometer, an odometer, turn signals, a gear display, various warning lights, and the like. The tachometer displays the rotations of the engine's crankshaft in revolutions per minute (RPM). The speedometer indicates the vehicle's speed. The odometer tells a person the total miles traveled since the person began driving the car. The fuel gauge tells a person how much fuel is left in the vehicle. The temperature gauge shows the current engine temperature. Alternatively, designated lights can be included to warn about engine temperature issues, such as an overheating engine. Turn signals display flashing lights on either side of the vehicle to communicate the direction the driver intends to turn. A gear display or gear position indicator shows the gear currently engaged, e.g., park, neutral, drive, and the like. Warning lights communicate various status items of the vehicle. Vehicles have various features such as pre-installed ESC and ABS, which are, of course, more standard components or elements. Warning lights are illuminated briefly at start-up as the vehicle checks to ensure the systems are safe and ready for operation. In some cases, certain warning lights may remain on indicating a problem, for example, with the engine, headlights, temperature, and the like.

[0018] The infotainment system 130 is a combination of information and entertainment. The infotainment system 130 is a collection of hardware and software in a vehicle that provides audio and video entertainment / information. The infotainment system 130 provides an information system that obtains information about various aspects of the vehicle, for example, from one or more electronic control units (ECUs), interfaces with the vehicle's systems, for example, pairing Bluetooth® devices, setting up devices (e.g., user devices and vehicle devices), and the like. According to at least one embodiment, the infotainment system 130 presents a menu user interface that allows the vehicle to detect user devices, set up the user devices, and provide services using the user devices. For example, the vehicle can obtain information from detected user devices, for example, to accurately and in real time monitor the user's health, sleep status, and the like. This information is relevant to the experience inside the vehicle.

[0019] The user interface may present a title bar 132 that provides an indicator of the current menu. Menu options 134, 136 are presented for selection to set up the user device and provide services using the user device. A climate control system 140 includes controls for setting the temperature inside the vehicle and configuring the operation of the climate control system 140, such as air conditioning, heating, defrost, floor vents, defrost vents, passenger vents, and combinations thereof. For example, vents located in various locations in the vehicle, such as a center vent 142 that provides airflow, a vent 144 that provides airflow toward the driver, a vent 146 that provides airflow toward the passenger, and a vent 148 above the dashboard for defrosting the windshield 150. Additional vents may be located in various areas of the vehicle, such as the rear seat area, below the dashboard, and the like.

[0020] FIG. 2 is a block diagram of a system 200 for providing an application for detecting user devices in a vehicle and collecting information from the detected devices, according to at least one embodiment.

[0021] 2, system 200 is implemented in an in-vehicle infotainment (IVI) system, also referred to herein as an information system. System 200 includes a local wireless communication service 210 that communicates with customer devices 250, such as customer device A 252, customer device B 254, and customer device N 256. Such devices include health wearable devices, artificial intelligence (AI) pins, sports wearable devices, multi-purpose wearable devices, ring wearable devices, and the like.

[0022] For example, the system 200 detects the presence of a user device after the user enters the vehicle and installs an appropriate application 258 for the customer device 250 in the memory 259 of the system 200. The customer device A 252 can then provide information to the system 200 for various services. For example, a user entering the vehicle with the customer device A 252 can provide useful information, such as the driver's or passenger's sleep status or temperature. After the system 200 is set up, for example, by providing the appropriate application 258, the device can connect to the system 200. Without provisioning the system 200 with the appropriate application 258, the system 200 cannot obtain information from the customer device A 252 and control the service 222 accordingly.

[0023] The local wireless communication service 210 communicates with a local wireless device service 214. The local wireless device service 214 communicates with a local device registry, such as a local wireless device registry 216. The local wireless device service 214 also communicates with services, such as a customer service service 218. The local wireless device service 214 and the customer service service 218 communicate with the system 200. An in-vehicle infotainment (IVI) graphical user interface (GUI) 220 facilitates communication with a user.

[0024] Customer service services 218 communicate with services 222. Services 222 include various vehicle services such as heating, ventilation, and air conditioning (HVAC) services 224, seat services 226, lighting services 228, voice services 230, and the like. HVAC services 224 and seat services 226 communicate with HVAC electronic control units (ECUs) 260 and seat ECUs 262, respectively, through internal wired communication service 1 232. However, one skilled in the art will recognize that other types of communication services may be used. Lighting service 228 communicates with lighting ECU 264 through internal wired communication service 2 234. Voice service 230 communicates with voice ECU 266 through internal wired communication service 3 236.

[0025] The customer service service 218 communicates with an external wireless communication service 240. The external wireless communication service 240 has access to a network, for example, the Internet 270. The customer service service 218 accesses an application store server 272 via the external wireless communication service 240 and the Internet 270. The application store server 272 communicates with an application store registry 274.

[0026] Thus, system 200 may install application 258 in memory 259 such that system 200 can execute application 258 to interface with customer device 250, e.g., customer device A 252. For example, system 200 may use application 258 to monitor a user's sleep state by accessing information received from customer device A 252, for example. Application 258 may receive information from customer device A 252, and system 200 may then trigger an alarm, vibration, or other notification based on the received information. Thus, in response to determining that the driver is asleep, customer device A 252 may provide information to application 258 installed in system 200. In response to a temperature associated with the customer or the interior environment of the vehicle's cockpit becoming too high, an automatic trigger may be sent to HVAC ECU 260 to adjust the temperature.

[0027] After the user enters the vehicle, the local wireless communication service 210 pairs with customer devices 250, such as customer device A 252, customer device B 254, and customer device N 256, using wireless communication mechanisms such as Bluetooth® and the like. Customer device A 252 is registered with the vehicle at least once. The next time customer device A 252 is detected, it is automatically recognized and paired via Bluetooth®. However, those skilled in the art will appreciate that other communication protocols may be used.

[0028] The system 200 detects at least one of customer device A 252, customer device B 254, and customer device N 256, and the local wireless device service 210 begins processing customer device A 252, customer device B 254, and customer device N 256 using the local wireless device service 214. The local wireless device service 214 detects whether the detected customer device A 252 is already paired with the system 200 by accessing the local wireless device registry 216.

[0029] In response to the fact that customer device A252 is not yet paired with system 200, IVI GUI 220 is notified by local wireless device service 214 that a new device is ready to be paired. The user then uses IVI GUI 220 to pair customer device A252 with system 200. Customer device A252 identifies itself to system 200 using specific information. Ideally, the communication protocol followed by the device is used so that when customer device A252 connects, customer device A252 can announce the connection in a predetermined format so that the vehicle immediately knows what the information represents and how to utilize the information when running existing applications. This provides system 200 with the ability to collect various information from multiple devices. However, according to at least one embodiment, the communication of information is a function of the application and is not limited to a single device.

[0030] When customer device A 252 is paired with system 200, information is collected by application 258. Based on the received information, system 200 can trigger some type of automatic control for the convenience and safety of the user. Through an interface with system 200, application 258 collects information from customer device 250. For example, a device application compatible with a particular one of customer devices 250 can be installed in system 200 to communicate and interact with the corresponding customer device 250, collect data, and provide services to the user.

[0031] FIG. 3 illustrates a process 300 for pairing devices according to at least one embodiment.

[0032] 3 , a first prompt 310 is presented with a banner 312 identifying the type of vehicle, e.g., 2024 manufacturer model. The prompt 310 presents a question 314 asking the user if they would like to pair a user device, such as Ring wearable A "1234568," and presents a yes option 316 and a no option 318. If yes option 316 is selected, a pairing status indicator 330 is displayed. In response to successful pairing of Ring wearable A "1234568," a confirmation 340 is displayed. In response to successful pairing of Ring wearable A "1234568," a pairing failure 350 is displayed.

[0033] 2 , customer service service 218 is triggered following detection (newly paired or otherwise) of at least one of customer devices 250. Once a device is detected or paired, system 200 can be triggered to present options for service 222 based on information collected by application 258 from customer device 250. The brand of customer device 250 and device application are presented to the user. Because the vehicle collects information about the registered device, e.g., that the device is a sports wearable model X, system 200 can present different device applications based on customer device 250. For example, the system can access a database that associates different devices and different vehicle models with compatible device applications.

[0034] FIG. 4 illustrates a flowchart 400 of a method for monitoring the status of a customer device, according to at least one embodiment.

[0035] In Figure 4, a customer service service monitors the status of customer devices to start or stop the customer service. The method starts (S402), and a determination is made whether at least one customer device is connected (S410). In response to determining that at least one customer device is connected (S412), a determination is made whether the service is running (S420). In response to determining that the service is not running (S422), the process returns to start S402. In response to determining that the service is running (S424), the customer service is stopped (S430), and the process returns to start S402.

[0036] In response to determining that at least one customer device is connected (S414), a determination is made as to whether the service is running (S440). In response to determining that the service is running (S442), the process returns to start S402. In response to determining that the service is not running (S444), a determination is made as to whether the service is enabled (S450). In response to determining that the service is not enabled (S452), the process returns to start S402. In response to determining that the service is enabled (S454), the customer service is started (S460). The process then returns to start S402.

[0037] 2, system 200 interfaces with vehicle services 222, such as HVAC service 224, seat service 226, lighting service 228, voice service 230, and the like. System 200 can communicate with an electronic control unit (ECU) that monitors and controls such services. System 200 allows a user to pair a particular customer device 250 with system 200 and presents the status of the pairing process to the user via IVI GUI 220. System 200 can stop services that are running but not connected and start services that are enabled but not running.

[0038] In FIG. 2 , the IVI GUI 220 is used by a user in the vehicle to obtain customer service. In response to selecting installation of an application, the application is downloaded and installed. The customer service service 218 uses the external wireless communication service 240 to access the application store server 272 over the Internet 270. The application store server 272 uses the application store registry 274 to present appropriate applications 258 in the application store server 272 and transfer data according to the requested application 258. The application 258 is downloaded to memory 259, and the customer service service 218 registers the application 258 with the customer service registry 212. The customer service registry 212 communicates the registered application to the local wireless communication service 210.

[0039] In some situations, the customer device 250 and the system do not share the same language and protocols for communication. However, the system is configured to recognize the capabilities being communicated by the customer device 250. In such situations, some human intervention is used to compile a list of applications per device to ensure that tested and proven device applications are presented to the user. This prevents random device applications from being downloaded to memory 259. Downloading random device applications is problematic for security and other reasons. Therefore, device application developers are aware and follow rules regarding how device applications should be developed.

[0040] For applications provided by the application store server 272, the actual APIs or SDKs are provided to developers to support the services for such applications in the application store server 272. Because the SDK is not open or accessible to everyone, information is provided to identified developers. For the customer device 250, information is provided in the SDK to determine which developers are included in the developer list.

[0041] In response to accessing the application store server 272, the system 200 identifies the vehicle along with the device of interest. The system 200 requests information compatible with the current environment. The system 200 takes into account the customer devices 250 paired with the system 200 so that the application store server 272 provides the system 200 with applications 258 that are compatible with the current configuration.

[0042] FIG. 5 illustrates an in-vehicle infotainment (IVI) GUI 500 for obtaining customer service, according to at least one embodiment.

[0043] 5, an IVI GUI 500 is displayed with a banner 510 identifying how to obtain applications used by the IVI system to provide information in support of at least one service. A choice to access an application store 520 is presented in the IVI GUI 500. Upon selecting to access the application store 520, the system connects to an application store server to download applications into the system's memory for execution by the system and to collect information from the customer device. The customer device is registered with the associated services.

[0044] FIG. 6 illustrates an application store GUI 600 when the application store is accessed, according to at least one embodiment.

[0045] 6, the application store GUI 600 includes a banner 610 that identifies the interface associated with the application store. The application store GUI 600 also provides access to in-cabin applications 620 for the customer device.

[0046] FIG. 7 illustrates an in-cabin application GUI 700 according to at least one embodiment.

[0047] In Figure 7, a banner 710 is presented that identifies the GUI 700 as a list of in-cabin applications for the customer device. The in-cabin application GUI 700 provides an interface 720 that lists third-party developers, allowing the customer to select applications associated with customer service for download to the user device. In Figure 7, health wearable device 722, artificial intelligence (AI) pin 724, sports wearable device A 726, multipurpose wearable device 728, sports wearable device B 730, ring wearable device 732, and the like are listed. Those skilled in the art will understand that more than one type of device may be listed, for example, sports wearable device A 726 and sports wearable device B 730, or that certain types of devices may not be included in the list.

[0048] FIG. 8 is a ring wearable device GUI 800 according to at least one embodiment.

[0049] In Figure 8, Ring wearable device GUI 800 is displayed after Ring wearable device A 732 in Figure 7 is selected by a user. Ring wearable device A GUI 800 includes a banner 810 that identifies Ring wearable device A GUI 800 and provides a list of customer devices to enable the user to select the correct one. For example, after selecting Ring wearable device A 732 in Figure 7 as the device of interest, Ring wearable device A GUI 800 provides a list of customer devices such as Ring wearable device A 1 820, Ring wearable device A 1234568 822, and Ring wearable device A Ultra++ 824. Developers can add or remove customer devices as circumstances change, for example, as customer devices are phased out or new customer devices are developed.

[0050] FIG. 9 is a ring wearable device 1234568 GUI 900 according to at least one embodiment.

[0051] In FIG. 9 , the Ring wearable device 1234568 GUI 900 is displayed after the Ring wearable device 1234568 822 in FIG. 8 is selected by a user. The Ring wearable device 1234568 GUI 900 includes a banner 910 that identifies the Ring wearable device 1234568 GUI 900. The Ring wearable device 1234568 GUI 900 displays applications associated with the Ring wearable device 1234568, such as drowsy driving alert 920, cabin temperature control 922, relaxing music for stress 924, and the like. From the Ring wearable device 1234568 GUI 900, a user selects applications created by third-party developers for a particular product and device applications created by third-party developers for the selected device. The applications are executed by the IVI system to collect data provided by the corresponding customer device, e.g., the Ring wearable device 1234568.

[0052] FIG. 10 is an application description GUI 1000 according to at least one embodiment.

[0053] In FIG. 10, an application description GUI 1000 is displayed after the Drowsy Driver Alert application 920 in FIG. 9 is selected by the user.

[0054] Drowsy driving alert The application description GUI 1000 includes a banner 1010 identifying the drowsy driving alert application. The application description GUI 1000 includes a compatibility status 1020. The compatibility status 1020 indicates that the application is compatible with 2024 manufacturer models. The application description GUI 1000 includes a description 1022. The description 1022 indicates, "If your Ring wearable 1234568 detects that you are asleep while driving, the car will play an audio pattern to wake you. Always be vigilant on the road. Always take breaks and avoid long driving sessions if possible." The application description GUI 1000 further includes an install button 1030 that a user can select to download and install the application onto the IVI system. In response to selecting the install button 1030, the device application is downloaded and installed onto the IVI system to collect data from the user's Ring wearable device A1234568.

[0055] Referring to FIG. 2 , the system 200 recognizes customer devices 250 and device applications corresponding to specific customer devices. Based on the copy SDK, APIs, and the like, third-party developers can develop device applications to target any type of background service inside the vehicle and trigger the automated controls the developer wants to provide to customers. Sleep monitoring and alerts, temperature determination and adjustment, and the like, as well as other services, can be implemented. For example, automatic payment can be supported, where a user wearing a smartwatch enters a taxi, and the taxi automatically detects the smartwatch. The taxi has the device application installed, and payment is automatically made at the end of the route.

[0056] Because device manufacturers have ideas about appropriate device applications to implement, developers have the ability to create automated controls. However, customers or users of customer devices 250 know more about the types of interactions they desire. Thus, according to at least one embodiment, users can access application store server 272 to obtain device applications and install them in memory 259, or they can use other methods to manually create device applications. For example, a predefined protocol can be developed that allows a device to indicate the types of information it can provide. The customer can then create the interactions they actually desire, and application 258 provides the customer with the opportunity to create its own automated controls.

[0057] The customer service service 218 executes the application 258 to communicate with the target service. The customer service service 218 executes the application 258 to communicate appropriately with the target service. The customer service service 218 checks whether the application 258 is compatible with at least one of the customer devices 250 and the type of vehicle associated with at least one of the customer devices 250. For example, the application 258 is compatible with the device and is also compatible with the vehicle in terms of APIs and the like. For example, the application 258 communicates with the local wireless communication service 210. The local wireless communication service 210 communicates with the local wireless device service 214. The wireless device service 214 communicates with the customer service service 218, which checks the customer service registry 212 to determine whether the application 258 is registered. Upon verifying that application 258 is registered in customer service registry 212, customer service service 218 sends an automatic trigger to HVAC service 224, which communicates with HVAC ECU 260 over internal wired communication service 1 232 to adjust the temperature.

[0058] FIG. 11 is a flowchart 1100 of a method for provisioning an application in an in-vehicle infotainment (IVI) system to collect information from devices detected in a vehicle, according to at least one embodiment.

[0059] 11, the method begins (S1102) and at least one user device is detected in a vehicle (S1110). Referring to FIG. 2, the system 200 detects the presence of a user device, for example, after the user enters the vehicle, and installs an appropriate application 258 for customer device A 252 in memory 259 of the system 200. The customer device A 252 can then provide information to the system 200 about various services.

[0060] Based on the detection of at least one user device in the vehicle, an application is provided to the in-vehicle infotainment (IVI) system to collect information from the detected device (S1114). Referring to Figure 2, once a device is detected or paired, the system 200 can be triggered to present options for services 222 based on information collected by the application 258 from the customer device 250.

[0061] The applications are installed on the IVI system (S1118). Referring to Figure 2, the applications 258 collect information from the customer devices 250. For example, device applications tailored to particular ones of the customer devices 250 can be installed on the system 200 to communicate and interact with the corresponding customer devices 250, collect data, and provide services to users.

[0062] Applications and services associated with the detected devices are registered with the IVI system (S1122). Referring to Figure 2, after a user enters the vehicle, the local wireless communication service 210 pairs with customer devices 250, such as customer device A 252, customer device B 254, and customer device N 256, using wireless communication mechanisms such as Bluetooth and the like. Customer device A 252 is registered with the vehicle at least once.

[0063] The detected device is paired with the IVI system (S1126). Referring to FIG. 2, the user then uses the IVI GUI 220 to pair customer device A252 with the system 200. Customer device A252 identifies itself to the system 200 using specific information. Ideally, the communication protocol followed by the device is used so that when customer device A252 connects, it can announce the connection in a predetermined format so that the vehicle immediately knows what the information represents and how to use the information when running existing applications. This provides system 200 with the ability to collect various information from multiple devices. However, according to at least one embodiment, the communication of information is a function of the application and is not limited to a single device. In response to customer device A252 not yet paired with the system 200, the IVI GUI 220 is notified by the local wireless device service 214 that a new device is ready to be paired. The user then uses the IVI GUI 220 to pair customer device A 252 with the system 200. Customer device A 252 identifies itself to the system 200 using certain information.

[0064] The application receives information collected from the detected devices (S1130). Referring to Figure 2, when customer device A 252 is paired with system 200, information is collected by application 258.

[0065] In response to receiving the information, an operation for the service is automatically triggered by the IVI system based on the collected information (S1134). Referring to Figure 2, based on the received information, the system 200 can trigger some type of automatic control for the convenience and safety of the user.

[0066] The service is performed based on the collected information (S1138). Referring to FIG. 2 , customer service service 218 executes an application to communicate with the target service. Customer service service 218 executes application 258 to appropriately communicate with the target service. Customer service service 218 checks whether application 258 is compatible with at least one of customer devices 250 and the type of vehicle associated with at least one of customer devices 250. For example, application 258 is compatible with the device and also compatible with the vehicle in terms of API and the like. For example, application 258 communicates with local wireless communication service 210. Local wireless communication service 210 communicates with local wireless device service 214. Wireless device service 214 communicates with customer service service 218, and customer service service 218 checks customer service registry 212 to determine whether the application is registered. Upon verifying that the application is registered in the customer service registry 212, the customer service service 218 sends an automatic trigger to the HVAC service 224, which communicates with the HVAC ECU 260 over the internal wired communication service 1 232 to adjust the temperature.

[0067] The process then ends (S1150).

[0068] At least one embodiment of a method for provisioning an application in an in-vehicle infotainment (IVI) system includes detecting a device in a vehicle; in response to detecting the device in the vehicle, provisioning an application in the IVI system to collect information from the detected device and provide a service to a user based on the collected information; receiving the information collected from the detected device by the application provisioned to the IVI system; and in response to receiving the information, automatically triggering an operation for the service by the IVI system based on the information collected by the application from the detected device.

[0069] FIG. 12 is a high-level functional block diagram of a processor-based system 1200 according to at least one embodiment.

[0070] In at least one embodiment, processing circuit 1200 detects a user device and provisions an application on an in-vehicle infotainment (IVI) system to provide a service to a user based on information collected by the application from the detected device. Processing circuit 1200 implements, using processor 1202, a method for detecting a user device and provisioning an application on an IVI system to provide a service to a user based on information collected by the application from the detected device. Processing circuit 1200 also includes a non-transitory computer-readable storage medium 1204 used to implement the method for detecting a user device and provisioning an application on an IVI system to provide a service to a user based on information collected by the application from the detected device. In particular, non-transitory computer-readable storage medium 1204 is encoded with, i.e., stores, instructions 1206, i.e., computer program code, executed by processor 1202 that cause processor 1202 to perform operations for detecting a user device and provisioning an application on an IVI system to provide a service to a user based on information collected by the application from the detected device. Execution of instructions 1206 by processor 1202 (at least in part) represents an application that implements at least a portion of the methods described herein (hereinafter, described processes and / or methods) in accordance with one or more embodiments.

[0071] The processor 1202 is electrically connected to a non-transitory computer-readable storage medium 1204 via a bus 1208. The processor 1202 is electrically connected to an input / output (I / O) interface 1210 by the bus 1208. A network interface 1212 is also electrically connected to the processor 1202 via the bus 1208. The network interface 1212 is connected to a network 1214, such that the processor 1202 and the non-transitory computer-readable storage medium 1204 connect to external elements via the network 1214. The processor 1202 is configured to execute instructions 1206 encoded in the non-transitory computer-readable storage medium 1204 to enable the processing circuit 1200 to perform at least portions of processes and / or methods. In one or more embodiments, the processor 1202 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application-specific integrated circuit (ASIC), and / or suitable processing unit.

[0072] Processing circuit 1200 includes an I / O interface 1210. I / O interface 1210 is connected to external circuitry. In one or more embodiments, I / O interface 1210 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor direction keys that communicate information and commands to processor 1202.

[0073] Processing circuit 1200 also includes a network interface 1212 coupled to processor 1202. Network interface 1212 enables processing circuit 1200 to communicate with a network 1214 to which one or more other computer systems are connected. Network interface 1212 may include a wireless network interface, such as Bluetooth, Wi-Fi, Worldwide Interoperable Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA), or a wired network interface, such as Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers (IEEE) 864.

[0074] The processing circuit 1200 is configured to receive information through an I / O interface 1210. The information received through the I / O interface 1210 includes one or more of instructions, data, design rules, a library of cells, and / or other parameters for processing by the processor 1202. The information is transferred to the processor 1202 via a bus 1208. The processing circuit 1200 is configured to receive information related to a user interface (UI) through the I / O interface 1210. The information is stored in a non-transitory computer-readable storage medium 1204 as an IVI system 1220.

[0075] In one or more embodiments, one or more non-transitory computer-readable storage media 1204 have stored thereon instructions 1206 (in compressed or uncompressed form) that can be used to program a computer, processor, or other electronic device to perform a process or method described herein. The one or more non-transitory computer-readable storage media 1204 include one or more of an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, or the like.

[0076] For example, non-transitory computer-readable storage medium 1204 may include, but is not limited to, a hard drive, a floppy diskette, an optical disk, a read-only memory (ROM), a random-access memory (RAM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a magnetic or optical card, a solid-state memory device, or any other type of physical medium suitable for storing electronic instructions. In one or more embodiments using optical disks, one or more non-transitory computer-readable storage media 1204 includes a compact disk read-only memory (CD-ROM), a compact disk read / write (CD-R / W), and / or a digital video disk (DVD).

[0077] In one or more embodiments, the non-transitory computer-readable storage medium 1204 stores instructions 1206 configured to cause the processor 1202 to perform at least a portion of a process and / or method for detecting a user device and provisioning an application in an in-vehicle infotainment (IVI) system to provide a service to the user based on information collected by the application from the detected device. In one or more embodiments, the non-transitory computer-readable storage medium 1204 also stores information, such as algorithms, that facilitate performing at least a portion of the process and / or method for detecting a user device and provisioning an application in an IVI system to provide a service to the user based on information collected by the application from the detected device.

[0078] Thus, in at least one embodiment, the processor 1202 executes instructions 1206 stored on one or more non-transitory computer-readable storage media 1204 to detect user devices, provision applications to the IVI system, and provide services to the user based on information collected by the applications from the detected devices. The processor 1202 implements customer device detection 1248 to detect customer devices entering the vehicle. The processor 1202 controls customer device pairing 1234 with the IVI system 1220. The processor 1202 maintains a local wireless communication service 1250 to communicate with connected customer services 1240. The processor 1202 implements a local wireless device service 1252 to handle registration of connected customer devices 1240 in a local wireless device registry 1254. The processor 1202 implements a customer service service 1258 for the user's registered customer services in a customer service registry 1256. The processor 1202 maintains a list of connected customer devices 1240. The processor 1202 monitors the status of the customer devices using customer service services 1258 to identify running services 1244 and enabled services 1246. The processor 1202 can start or stop running services 1244 and enabled services 1246. The processor 1202 maintains applications in the application store server 1242, and the applications are registered in the application store registry 1236. The processor 1202 uses the customer service services 1258 to communicate with an external wireless communication service 1260 to access the network 1214, e.g., the Internet. The processor 1202 accesses the application store server 1242 via the external wireless communication service 1260. The processor 1202 implements various services, such as heating, ventilation, and air conditioning (HVAC) services, seat services, lighting services, voice services, and the like.The processor 1202 communicates with an electronic control unit (ECU) using an internal wired communication service 1264. The processor 1202 implements an IVI system 1220. The processor 1202 pairs a customer device using an IVI GUI 1282 of the IVI system 1220. The processor 1202 presents an application store GUI 1222 to allow a user to download applications to the IVI system. Through the application store GUI 1222, the processor 1202 provides access to an in-cabin application GUI 1224 for the customer device. The in-cabin application GUI 1224 for the customer device provides a list 1226 of apps by developers. The user can select an app from the list 1226 of apps by developers, and the processor presents a customer device by developer 1228. Upon selection of a customer device 1228 by a developer, an application GUI 1230 for the customer device (e.g., drowsy driving alert, cabin temperature control, relaxing music for stressful situations, and the like) is presented to the user. The processor 1202 then presents an application description, compatibility, and installation GUI 1232. The processor 1202 can present an IVI GUI 1282 on the display 1280 for use by the IVI system 1220.

[0079] Separate instances of these programs may be running on or distributed among any number of separate computer systems. Thus, although particular steps are described as being performed by particular devices, software programs, processes, or entities, this is not required. Various alternative implementations will be appreciated by those skilled in the art.

[0080] Furthermore, those skilled in the art will readily appreciate that the above-described techniques may be utilized in a variety of devices, environments, and contexts. Although the embodiments have been described in terms specific to structural features or method acts, the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claims.

Claims

1. 1. A processor-implemented method for provisioning an application to an in-vehicle infotainment (IVI) system in a vehicle, comprising: Detecting a device in the vehicle; In response to detecting the device in the vehicle, provisioning an application to an IVI system to collect information from the detected device and provide a service to a user based on the collected information. receiving the information collected from the detected device by the application provisioned to the IVI system; In response to receiving the information, automatically triggering an operation for the service by the IVI system based on the information collected by the application from the detected device; A method comprising:

2. The detection of the device in the vehicle includes: Accessing the application store; listing third party developers of the application in the application store for selection; downloading the application from the application store to the IVI system; The method of claim 1 , comprising:

3. The provisioning of the application to the IVI system comprises: installing the application on the IVI system; pairing the detected device with the IVI system; 3. The method of claim 1 or 2, comprising:

4. The method of claim 3 , wherein the pairing of the detected device with the IVI system includes presenting a status of the pairing of the detected device with the IVI system.

5. The method of claim 3 , wherein the installation of the application in the IVI system includes registering the application and the service associated with the detected device in a service registry.

6. The provisioning of the application to the IVI system comprises: providing a description of the service associated with the detected device; and checking compatibility of the application with the detected device and the IVI system; 3. The method of claim 1 or 2, comprising:

7. 3. The method of claim 1, wherein receiving the information collected by the application includes executing the service based on the collected information, and wherein automatically triggering the operation includes communicating with the service associated with the application to provide information that triggers the operation.

8. A vehicle information system, comprising: a memory storing computer readable instructions; a processor connected to the memory; wherein the processor executes the computer-readable instructions to perform operations, Detecting the device in the vehicle; In response to detecting the device in the vehicle, provisioning an application to collect information from the detected device and provide a service to a user based on the collected information; receiving the information collected from the detected device by the application provisioned to collect the information from the detected device; and a vehicle information system configured, in response to receiving the information, to automatically trigger an operation for the service based on the information collected by the application from the detected device.

9. The processor: Accessing the application store; listing third party developers of the application in the application store for selection; downloading a device application from the application; 9. The vehicle information system of claim 8, configured to detect the device in the vehicle by

10. The processor: installing the application to communicate with the detected device; pairing the detected device with the application; 10. The vehicle information system of claim 8 or 9, configured to provision device applications to the devices detected in the vehicle by

11. 11. The vehicle information system of claim 10, wherein the processor is configured to pair the detected device by presenting a status of the pairing of the detected device with the application.

12. The vehicle information system of claim 10 , wherein the processor is configured to install the application by registering the application and the service associated with the detected device in a service registry.

13. The processor: providing a description of the service associated with the detected device; and checking compatibility of the application with the detected device and the vehicle; 11. The vehicle information system of claim 10, configured to provision the application by:

14. 10. The vehicle information system of claim 8 or 9, wherein the processor is configured to receive the information collected by the application by executing the service based on the collected information, and the processor is configured to automatically trigger the operation by communicating with the service associated with the application to provide information that triggers the operation.

15. A computer program which, when executed by a processor, causes the processor to perform operations, said operations comprising: Detecting a device in a vehicle; In response to detecting the device in the vehicle, provisioning an application in an in-vehicle infotainment (IVI) system to collect information from the detected device and provide a service to a user based on the collected information; receiving the information collected from the detected device by the application provisioned to the IVI system; In response to receiving the information, automatically triggering an operation for the service by the IVI system based on the information collected by the application from the detected device; a computer program comprising:

16. The detection of the device in the vehicle includes: Accessing the application store; listing third party developers of the application in the application store for selection; downloading a device application from the application store to the IVI system; 16. The computer program of claim 15, comprising:

17. The provisioning of the application to the IVI system comprises: installing the application on the IVI system; pairing the detected device with the IVI system; 17. A computer program according to claim 15 or 16, comprising:

18. 18. The computer program product of claim 17, wherein the pairing of the detected device with the IVI system includes presenting a status of the pairing of the detected device with the IVI system, and the installation of the application on the IVI system includes registering the application and the service associated with the detected device in a service registry.

19. The provisioning of device applications to the devices detected in the vehicle includes: providing a description of the services associated with the device; checking compatibility of the device application with the device and the vehicle; 17. A computer program according to claim 15 or 16, comprising:

20. 17. The computer program product of claim 15 or 16, wherein receiving the information collected by the application includes executing the service based on the collected information, and automatically triggering the operation includes communicating with the service associated with the application to provide information that triggers the operation.

Images