Provisioning of vehicle applications for in-vehicle infotainment systems to support user devices detected in the 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 of a vehicle application to an in-vehicle infotainment (IVI) system for supporting user devices detected in a vehicle, and to a method of using the vehicle application. [Background Art]

[0002] Currently, new vehicles exist that are equipped with sensors and various devices that collect data related to the vehicle and the driver. Fleet management systems enable fleet operators to monitor and manage a fleet of vehicles, including tracking fuel diagnostics, optimizing routes, and scheduling maintenance to improve efficiency and reduce costs. Furthermore, cloud-connected Internet of Things (IoT) boxes link to telematics devices to provide real-time data on driver health and vehicle conditions. Such systems share statistics related to driver capability and health, detect drowsiness, and send idle alarms.

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

[0004] Vehicles are currently unable to acquire or collect any information from such sensors and devices. For example, in-vehicle infotainment (IVI) systems (also simply referred to as infotainment systems) can detect and pair wearable devices using wireless communication, such as Bluetooth®. However, vehicles are not technically able to collect accurate or detailed information from a user's wearable device because they lack sensors or appropriate and accurate algorithms to identify and connect to user devices. Wearable devices are capable of acquiring information related to the user and the environment, but they are not configured to communicate with the infotainment system to provide relevant information. Therefore, vehicles cannot collect information from a user's wearable device and cannot use that information to provide a natural experience or practical applications within the vehicle. [Overview of the project]

[0005] In at least one embodiment, a method performed by a processor that provisions an application to an in-vehicle infotainment (IVI) system in a vehicle includes: detecting a device in the vehicle; provisioning an application to the IVI system in response to the detection of a device in the vehicle to collect information from the detected device and provide services to a user based on the collected information; receiving information collected from the detected device by the application provisioned to the IVI system; and, in response to the receipt of 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, the vehicle information system includes a memory for storing computer-readable instructions and a processor connected to the memory, the processor being configured to execute computer-readable instructions to perform operations to detect devices in a vehicle, provision an application in response to the detection of devices in the vehicle to collect information from the detected devices, provide services to a user based on the collected information, receive information collected from the detected devices by an application provisioned to collect information from the detected devices, and, in response to the receipt of the information, automatically trigger an operation for a service based on the information collected by the application from the detected devices.

[0007] In at least one embodiment, a computer program, when executed by a processor, stores computer-readable instructions causing the processor to perform an action, the action comprising: detecting a device in a vehicle; provisioning an application to an in-vehicle infotainment (IVI) system in response to the detection of a device in the vehicle to collect information from the detected device and provide a service to a user based on the collected information; receiving information collected from the detected device by the application provisioned to the IVI system; and, in response to the receipt of the information, automatically triggering an action for the service by the IVI system based on the information collected by the application from the detected device. [Brief explanation of the drawing]

[0008] The aspects of this disclosure are best understood by reading the following detailed description with reference to the attached figures. Note that, in accordance with industry practice, various features are not depicted to scale. In fact, for clarity in the description, the dimensions of various features may be increased or decreased.

[0009] [Figure 1] Figure 1 shows a vehicle cockpit according to at least one embodiment. [Figure 2] Figure 2 is a block diagram of a system that provides 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] Figure 3 shows the process of pairing devices according to at least one embodiment. [Figure 4] Figure 4 shows a flowchart of a method for monitoring the status of a customer device according to at least one embodiment. [Figure 5] Figure 5 shows an in-vehicle infotainment (IVI) GUI for obtaining customer service according to at least one embodiment. [Figure 6] Figure 6 shows the application store GUI when accessing the application store according to at least one embodiment. [Figure 7] Figure 7 shows an in-cabin application GUI according to at least one embodiment. [Figure 8] Figure 8 shows a ring wearable device GUI according to at least one embodiment. [Figure 9] Figure 9 shows a ring wearable device 1234568GUI according to at least one embodiment. [Figure 10] Figure 10 is an application description GUI according to at least one embodiment. [Figure 11] Figure 11 is a flowchart of a method for provisioning an application to an in-vehicle infotainment (IVI) system to collect information from devices detected in a vehicle, according to at least one embodiment. [Figure 12] Figure 12 is a high-level functional block diagram of a processor-based system according to at least one embodiment. [Modes for carrying out the invention]

[0010] The embodiments described herein describe examples of implementing various features of the subject matter provided. For the sake of brevity of this disclosure, examples of components, values, operations, materials, arrangements, or similars are described below. Of course, these are examples and not intended to be limiting. Other components, values, operations, materials, arrangements, or similars are conceivable. 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, and embodiments in which an additional feature is formed between the first and second features so that the first and second features cannot make direct contact. In addition, this disclosure repeats reference numbers and / or reference letters in various examples. This repetition is for the sake of brevity and clarity and does not define the relationships between the various embodiments and / or configurations described.

[0011] Furthermore, spatially relative terms such as “downward,” “below,” “below,” “upward,” “above,” and similar terms are used herein to facilitate explanation, describing 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 during use or operation, in addition to the orientation depicted in the figures. The device may have different orientations (90-degree rotation or other orientations), and the spatially relative descriptions used herein are interpreted accordingly.

[0012] Terms such as “user equipment,” “mobile station,” “mobile,” “mobile device,” “subscriber station,” “subscriber equipment,” “access terminal,” “terminal,” and “headset,” and similar terms, refer to wireless devices used by subscribers or users of wireless communication services to receive or transmit data, control, voice, video, audio, games, data streaming, or signaling streaming. These terms are interchangeable in the subject matter 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; provisioning an application to the IVI system in response to the detection of a device in the vehicle to collect information from the detected device and provide services to a user based on the collected information; receiving information collected from the detected device by the application provisioned to the IVI system; and, in response to the receipt of the information, automatically triggering an operation for a service by the IVI system based on the information collected by the application from the detected device.

[0014] The embodiments described herein offer one or more advantages. For example, by detecting a user device in a vehicle and provisioning an application to the 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 a notification to the user when the user has decided to fall asleep, adjusting the temperature in the vehicle to a more comfortable level, making automatic payments, and the like.

[0015] Figure 1 shows a vehicle cockpit 100 according to at least one embodiment.

[0016] In Figure 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 the 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 direction of the vehicle to the front wheels through a linkage mechanism system. The accelerator pedal 112 is used to control the supply of fuel and air to the engine by applying pressure. The accelerator pedal 112 is also known as the throttle or gas pedal. The brake pedal 114 is pressed to apply the brakes, thereby slowing down and / or stopping the vehicle.

[0017] The instrument panel 120 is the part 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 on the vehicle's status. For example, the instrument panel 120 often includes a traction control indicator, engine temperature, tachometer, fuel gauge, speedometer, odometer, turn signals, gear display, various warning lights, and similar. The tachometer displays the rotation of the engine's crankshaft in revolutions per minute (RPM). The speedometer indicates the vehicle's speed. The odometer shows the driver the total number of miles traveled since they started driving the car. The fuel gauge shows the driver how much fuel is left in the vehicle. The temperature gauge indicates the current engine temperature. Alternatively, it may include a designated light to warn about engine temperature issues such as engine overheating. Turn signals are flashing lights on either side of the vehicle to communicate to other drivers the direction in which the driver intends to turn. The gear display or gear position indicator shows the currently engaged gear, such as Park, Neutral, Drive, and similar. 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 illuminate temporarily at startup when the vehicle checks to ensure the system is safe and ready to operate. In some cases, certain warning lights may remain on to indicate a problem with, for example, the engine, headlights, temperature, and similar.

[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, for example, obtains information about various aspects of the vehicle from one or more electronic control units (ECUs), and provides an information system that performs interface connection with vehicle systems, such as pairing of Bluetooth (registered trademark) devices, setup of devices (e.g., user devices and vehicle devices), and the like. According to at least one embodiment, the infotainment system 130 presents a user interface of a menu that enables the vehicle to detect a user device, set up the user device, and provide services using the user device. For example, the vehicle can accurately monitor, for example, the user's health, sleep status, and the like in real time, and obtain information from the detected user device. This information relates to the experience inside the vehicle.

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

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

[0021] In FIG. 2, the system 200 is implemented in an in-vehicle infotainment (IVI) system, also referred to herein as an information system. The system 200 includes a local wireless communication service 210 that communicates with customer devices 250, such as a customer device A 252, a customer device B 254, and a 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, after a user enters the vehicle, the system 200 detects the presence of the user device and installs an appropriate application 258 for the customer device 250 in a memory 259 of the system 200. The customer device A 252 is then able to provide information to the system 200 for various services. For example, a user who has entered the vehicle with the customer device A 252 can provide useful information, such as the sleep status or body temperature of a driver or a passenger. For example, after the system 200 is set up by providing an appropriate application 258, the device can be connected to the system 200. If an appropriate application 258 is not provisioned to the system 200, 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 the local wireless device service 214. The local wireless device service 214 communicates with a local device registry, for example, the local wireless device registry 216. The local wireless device service 214 also communicates with a service, for example, customer service service 218. The local wireless device service 214 and customer service service 218 communicate with the system 200. The in-vehicle infotainment (IVI) graphical user interface (GUI) 220 facilitates communication with the user.

[0024] Customer service 218 communicates with service 222. Service 222 includes various vehicle services such as heating, ventilation, and air conditioning (HVAC) service 224, seat service 226, lighting service 228, voice service 230, and similar services. HVAC service 224 and seat service 226 communicate with HVAC electronic control unit (ECU) 260 and seat ECU 262, respectively, through internal wired communication service 1 232. However, a person skilled in the art will recognize that other types of communication services are available. 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] Customer service 218 communicates with external wireless communication service 240. External wireless communication service 240 accesses a network, such as the Internet 270. Customer service 218 accesses application store server 272 via external wireless communication service 240 and the Internet 270. Application store server 272 communicates with application store registry 274.

[0026] Therefore, the system 200 can install application 258 in memory 259 so that the system 200 can run application 258 to interface with a customer device 250, for example, customer device A252. For example, the system 200 can use application 258 to monitor the user's sleep state by accessing information received from customer device A252. Application 258 can receive information from customer device A252, and then the system 200 can trigger an alarm, vibration, or other notification based on the received information. Therefore, in response to the determination that the driver is asleep, customer device A252 can provide information to application 258 installed in the system 200. In response to the temperature of the customer or the internal environment of the vehicle cockpit becoming too high, an automatic trigger can be sent to the 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 A252, customer device B254, and customer device N256, using a wireless communication mechanism such as Bluetooth® and similar technologies. Customer device A252 is registered with the vehicle at least once. The next time customer device A252 is detected, it is automatically recognized and paired via Bluetooth®. However, those skilled in the art will understand that other communication protocols are available.

[0028] System 200 detects at least one of customer devices A252, B254, and N256, and the local radio device service 210 begins processing customer devices A252, B254, and N256 using the local radio device service 214. The local radio device service 214 detects whether the detected customer device A252 is already paired with System 200 by accessing the local radio device registry 216.

[0029] Depending on whether customer device A252 has not yet been paired with system 200, the IVI GUI 220 is notified by the local radio device service 214 that the new device is ready to be paired. The user then pairs customer device A252 with system 200 using the IVI GUI 220. Customer device A252 identifies itself to system 200 using specific information. Ideally, the communication protocol followed by the device is used to allow customer device A252 to announce the connection in a predetermined format so that the vehicle immediately recognizes what the information represents and how to use that information when running an existing application. 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] Once customer device A252 is paired with system 200, information is collected by application 258. Based on the received information, system 200 can trigger some type of automated control for user convenience and safety. Through its interface with system 200, application 258 collects information from customer device 250. For example, a device application tailored to a specific customer device 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] Figure 3 shows a device pairing process 300 according to at least one embodiment.

[0032] In Figure 3, a first prompt 310 is presented, which has a banner 312 identifying the vehicle type, for example, a 2024 manufacturer model. Prompt 310 presents a question 314 asking the user whether they want to pair a user device such as the Ring Wearable A "1234568", and presents a yes option 316 and a no option 318. If the yes option 316 is selected, a pairing status indicator 330 is displayed. A confirmation 340 is displayed depending on the success of pairing the Ring Wearable A "1234568". A pairing failure 350 is displayed depending on the success of pairing the Ring Wearable A "1234568".

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

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

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

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

[0037] Referring to Figure 2, system 200 interfaces with vehicle services 222, such as HVAC services 224, seating services 226, lighting services 228, voice services 230, and similar services. System 200 can communicate with electronic control units (ECUs) that monitor and control such services. System 200 allows the user to pair a specific customer device 250 with system 200 and presents the status of the pairing process to the user via the 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 Figure 2, the IVI GUI 220 is used by the user in the vehicle to obtain customer service. Depending on whether application installation is selected, the application is downloaded and installed. The customer service service 218 accesses the application store server 272 via the internet 270 using the external wireless communication service 240. The application store server 272 uses the application store registry 274 to present the appropriate application 258 in the application store server 272 and transfers 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 protocol for communication. However, the system is configured to recognize the functions 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 only tested and verified device applications are presented to the user. This prevents random device applications from being downloaded to memory 259. The download of random device applications is problematic for security and other reasons. Therefore, the developers of the device applications are recognized and adhere to rules regarding how the device applications should be developed.

[0040] For applications provided by the application store server 272, the actual API or SDK is provided to developers to support services for such applications on the application store server 272. Since the SDK is not open or accessible to everyone, the information is provided to recognized developers. For customer devices 250, the information is provided in the SDK to determine which developers are included in the developer list.

[0041] Upon accessing the application store server 272, system 200 identifies the vehicle along with the device of interest. System 200 requests information compatible with the current environment. System 200 takes into account the customer device 250 paired with system 200 so that the application store server 272 provides system 200 with an application 258 that is suitable for the current configuration.

[0042] Figure 5 shows an in-vehicle infotainment (IVI) GUI 500 for acquiring customer service according to at least one embodiment.

[0043] Figure 5 shows the IVI GUI 500, which has a banner 510 that identifies how to obtain the application used by the IVI system to provide information when supporting at least one service. An option to access the application store 520 is presented in the IVI GUI 500. If the system chooses to access the application store 520, the system downloads the application into the system's memory for execution and connects to the application store server to collect information from the customer device. The customer device is registered along with the associated service.

[0044] Figure 6 shows the application store GUI 600 when accessing the application store, according to at least one embodiment.

[0045] In Figure 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 customer devices.

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

[0047] In Figure 7, a banner 710 is presented identifying GUI 700 as a list of in-cabin applications for customer devices. The in-cabin applications GUI 700 provides an interface 720 for listing third-party developers, allowing customers to select applications associated with customer services for download to their user devices. In Figure 7, health wearable devices 722, artificial intelligence (AI) pins 724, sports wearable device A726, multipurpose wearable device 728, sports wearable device B730, ring wearable device 732, and similar devices are listed. Those skilled in the art will understand that it is possible to list more than one type of device, for example, sports wearable device A726 and sports wearable device B730, or to omit certain types of devices from the list.

[0048] Figure 8 shows a ring wearable device GUI800 according to at least one embodiment.

[0049] In Figure 8, the Ring Wearable Device GUI 800 is displayed after the Ring Wearable Device A732 in Figure 7 is selected by the user. The Ring Wearable Device A GUI 800 includes a banner 810 that identifies the 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 A732 in Figure 7 as the device of interest, the Ring Wearable Device A GUI 800 provides a list of customer devices such as Ring Wearable Device A1 820, Ring Wearable Device A1234568 822, and Ring Wearable Device AUltra++824. Developers can add or remove customer devices when circumstances change, for example, when customer devices are phased out or new customer devices are developed.

[0050] Figure 9 shows a ring wearable device 1234568GUI900 according to at least one embodiment.

[0051] In Figure 9, the Ring Wearable Device 1234568GUI900 is displayed after the Ring Wearable Device 1234568 822 in Figure 8 is selected by the user. The Ring Wearable Device 1234568GUI900 includes a banner 910 that identifies the Ring Wearable Device 1234568GUI900. The Ring Wearable Device 1234568GUI900 displays applications associated with the Ring Wearable Device 1234568, such as drowsy driving alerts 920, cabin temperature control 922, relaxing music for stress relief 924, and similar applications. From the Ring Wearable Device 1234568GUI900, the user selects applications created by third-party developers for specific products and device applications created by third-party developers for this selected device. The applications are executed by the IVI system to collect data provided by the corresponding customer device, for example, the Ring Wearable Device 1234568.

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

[0053] In Figure 10, the application description GUI 1000 is displayed after the user has selected the drowsy driving alert application 920 in Figure 9.

[0054] Drowsy driving alert The Application Description GUI 1000 includes a banner 1010 that identifies the application related to drowsy driving alerts. 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 states, "If your ring wearable 1234568 detects that you are sleeping while you are driving, the car will play an audio pattern to wake you up. Always be careful on the road. Be sure to take breaks and avoid long driving sessions whenever possible." The Application Description GUI 1000 further includes an install button 1030 that the user selects to download and install the application to the IVI system. Depending on whether the install button 1030 is selected, the device application is downloaded and installed to the IVI system to collect data from the user's ring wearable device A1234568.

[0055] Referring to Figure 2, System 200 recognizes customer devices 250 and device applications corresponding to specific customer devices. Based on the copy SDK, API, and similar, third-party developers can develop device applications to trigger automated controls that the developer wishes to provide to the customer, targeting some type of background service inside the vehicle. In addition to sleep monitoring and alerting, temperature determination and adjustment, and similar, other services can be implemented. For example, it is possible to support automatic payment, where a user wearing a smartwatch enters a taxi, and the taxi automatically detects the smartwatch. The taxi installs the device application, and payment is made automatically at the end of the route.

[0056] Device manufacturers have ideas about the appropriate device applications to implement, and developers have the ability to create automated controls. However, the customer or user of the customer device 250 knows more about the type of interaction the user desires. Therefore, according to at least one embodiment, the user can access the application store server 272 to obtain a device application and install the device application in memory 259, or use other methods to manually create a device application. For example, a given protocol can be developed so that the device can indicate the type of information it can provide. The customer can then create the interaction the customer actually desires, and application 258 provides the customer with the opportunity to create its own automated controls.

[0057] Customer service 218 executes application 258 to communicate with the target service. Customer service 218 executes application 258 to communicate appropriately with the target service. Customer service 218 checks whether application 258 is compatible with at least one of the customer devices 250 and the vehicle type associated with at least one of the customer devices 250. For example, application 258 is compatible with the device and also compatible with the vehicle in terms of APIs and similar items. For example, application 258 communicates with local radio communication service 210. Local radio communication service 210 communicates with local radio device service 214. Radio device service 214 communicates with customer service service 218, and customer service service 218 checks the customer service registry 212 to determine whether application 258 has been registered. Once it confirms that application 258 is registered in the customer service registry 212, customer service 218 sends an automatic trigger to HVAC service 224, which then communicates with HVAC ECU 260 via internal wired communication service 1 232 to adjust the temperature.

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

[0059] In Figure 11, the process begins (S1102), and at least one user device is detected in the vehicle (S1110). Referring to Figure 2, the system 200 detects the presence of the user device, for example, after the user enters the vehicle, and installs an appropriate application 258 for customer device A252 in the system 200's memory 259. The customer device A252 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, the 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 about service 222 based on the information collected by application 258 from customer device 250.

[0061] The application is installed on the IVI system (S1118). Referring to Figure 2, application 258 collects information from customer devices 250. For example, a device application tailored to a specific customer device 250 can be installed on system 200 to communicate and interact with the corresponding customer device 250, collect data, and provide services to the user.

[0062] Applications and services associated with the detected devices are registered with the IVI system (S1122). Referring to Figure 2, after the user enters the vehicle, the local wireless communication service 210 pairs with customer devices 250, such as customer device A252, customer device B254, and customer device N256, using a wireless communication mechanism such as Bluetooth® and similar technologies. Customer device A252 is registered with the vehicle at least once.

[0063] The detected device is paired with the IVI system (S1126). Referring to Figure 2, the user then pairs customer device A252 with system 200 using the IVI GUI 220. Customer device A252 identifies itself to system 200 using specific information. Ideally, the communication protocol followed by the device is used to allow customer device A252 to announce the connection in a predetermined format so that the vehicle immediately recognizes what the information represents and how to utilize that information when running an existing application. 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. Depending on whether customer device A252 has not yet been paired with system 200, the IVI GUI 220 is notified by the local radio device service 214 that the new device is ready to be paired. Next, the user uses the IVI GUI220 to pair customer device A252 with system 200. Customer device A252 identifies itself to system 200 using specific information.

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

[0065] Upon receiving information, the IVI system automatically triggers an operation regarding the service 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 Figure 2, customer service 218 runs an application to communicate with the target service. Customer service 218 runs application 258 to communicate appropriately with the target service. Customer service 218 checks whether application 258 is compatible with at least one of the customer devices 250 and the vehicle type associated with at least one of the customer devices 250. For example, application 258 is compatible with the device and also compatible with the vehicle in terms of APIs and similar items. For example, application 258 communicates with local radio communication service 210. Local radio communication service 210 communicates with local radio device service 214. Radio device service 214 communicates with customer service service 218, and customer service service 218 checks the customer service registry 212 to determine whether the application has been registered. Once the application is confirmed to be registered in the customer service registry 212, customer service 218 sends an automatic trigger to HVAC service 224, which then communicates with HVAC ECU 260 via internal wired communication service 1 232 to adjust the temperature.

[0067] Next, the process terminates (S1150).

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

[0069] Figure 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, the processing circuit 1200 detects a user device, provisions an application to the in-vehicle infotainment (IVI) system, and provides services to the user based on information collected by the application from the detected device. The processing circuit 1200 implements the method of detecting a user device, provisioning an application to the IVI system, and providing services to the user based on information collected by the application from the detected device using the processor 1202. The processing circuit 1200 also includes a non-temporary computer-readable storage medium 1204 used to implement the method of detecting a user device, provisioning an application to the IVI system, and providing services to the user based on information collected by the application from the detected device. In particular, the non-temporary computer-readable storage medium 1204 stores, i.e., an instruction 1206 executed by the processor 1202, i.e., an instruction encoded in computer program code, i.e., an instruction executed by the processor 1202, i.e., an instruction that causes the processor 1202 to perform the operation of detecting a user device, provisioning an application to the IVI system, and providing services to the user based on information collected by the application from the detected device. The execution of instruction 1206 by processor 1202 represents (at least in part) an application that implements at least a portion of the methods described herein (hereinafter, the described processes and / or methods) according to one or more embodiments.

[0071] The processor 1202 is electrically connected to a non-temporary computer-readable storage medium 1204 via a bus 1208. The processor 1202 is electrically connected to an input / output (I / O) interface 1210 via the bus 1208. The 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, and as a result, the processor 1202 and the non-temporary computer-readable storage medium 1204 are connected to external elements via the network 1214. The processor 1202 is configured to execute instructions 1206 encoded in the non-temporary computer-readable storage medium 1204 in order to make the processing circuit 1200 available to perform at least a part of a process and / or method. 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 a preferred processing unit.

[0072] The processing circuit 1200 includes an I / O interface 1210. The I / O interface 1210 is connected to an external circuit. In one or more embodiments, the I / O interface 1210 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor directional keys for communicating information and commands to the processor 1202.

[0073] The processing circuit 1200 also includes a network interface 1212 connected to the processor 1202. The network interface 1212 allows the processing circuit 1200 to communicate with a network 1214 to which one or more other computer systems are connected. The network interface 1212 includes a wireless network interface, such as Bluetooth®, Wi-Fi, Worldwide Interoperability Microwave Access (WiMAX), General-Purpose Packet Radio Service (GPRS), or Broadband Code Division Multiple Access (WCDMA®), or a wired network interface, such as Ethernet, Universal Serial Bus (USB), or IEEE 864.

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

[0075] In one or more embodiments, one or more non-temporary computer-readable storage media 1204 store (in compressed or uncompressed form) instructions 1206 that can be used to program a computer, processor, or other electronic device to perform a process or method described herein. One or more non-temporary computer-readable storage media 1204 include one or more electronic storage media, magnetic storage media, optical storage media, quantum storage media, or the same.

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

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

[0078] Therefore, in at least one embodiment, the processor 1202 executes instructions 1206 stored in one or more non-temporary 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 in the vehicle. The processor 1202 controls customer device pairing 1234 with the IVI system 1220. The processor 1202 maintains a local radio communication service 1250 to communicate with connected customer services 1240. The processor 1202 implements a local radio device service 1252 to handle the registration of connected customer devices 1240 in the local radio device registry 1254. The processor 1202 implements a customer service service 1258 for user registration customer services in the customer service registry 1256. The processor 1202 maintains a list of connected customer devices 1240. The processor 1202 monitors the status of customer devices using customer service service 1258 to identify running services 1244 and active services 1246. The processor 1202 can start or stop running services 1244 and active 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 communicates with the external wireless communication service 1260 using customer service service 1258 and accesses the network 1214, for example, 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, seating services, lighting services, voice services, and similar services.The processor 1202 communicates with the electronic control unit (ECU) using the internal wired communication service 1264. The processor 1202 implements the IVI system 1220. The processor 1202 pairs the customer device using the IVI GUI 1282 of the IVI system 1220. The processor 1202 presents the application store GUI 1222, allowing the user to download applications to the IVI system. Through the application store GUI 1222, the processor 1202 provides access to the in-cabin application GUI 1224 for the customer device. The in-cabin application GUI 1224 for the customer device provides a list of developer apps 1226. The user can select an app from the list of developer apps 1226, and the processor presents the developer's customer device 1228. When a developer selects a customer device 1228, the user is presented with an application GUI 1230 specific to that customer device (e.g., drowsy driving alert, cabin temperature control, relaxing music for stress relief, and similar). The processor 1202 then presents the application description, compatibility, and installation GUI 1232. The processor 1202 can also present the IVI GUI 1282 on the display 1280 for the use of the IVI system 1220.

[0079] Separate instances of these programs may run on any number of separate computer systems or be distributed among them. Therefore, while certain steps are described as being performed by a specific device, software program, process, or entity, this is not necessarily required. Various alternative implementations will be understood by those skilled in the art.

[0080] Furthermore, those skilled in the art will readily understand that the above-described technology can be used in a variety of devices, environments, and situations. While the embodiments are described in terms specific to structural features or actions of methods, the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described. Rather, specific features and actions are disclosed as exemplary forms that implement the claims.

Claims

1. A method performed by a processor for provisioning an application to an in-vehicle infotainment (IVI) system in a vehicle, The vehicle detects the device, 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 services to the user based on the collected information, The application provisioned to the IVI system receives the information collected from the detected device, Upon receiving the aforementioned information, the IVI system automatically triggers an operation regarding the service based on the information collected by the application from the detected device, Includes, The provisioning of the application to the IVI system is Installing the application on the IVI system, Pairing the detected device with the IVI system, Methods that include...

2. The method according to claim 1, wherein the pairing of the detected device with the IVI system includes presenting the status of the pairing of the detected device with the IVI system.

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

4. A method performed by a processor for provisioning an application to an in-vehicle infotainment (IVI) system in a vehicle, The vehicle detects the device, 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 services to the user based on the collected information, The application provisioned to the IVI system receives the information collected from the detected device, Upon receiving the aforementioned information, the IVI system automatically triggers an operation regarding the service based on the information collected by the application from the detected device, Includes, The provisioning of the application to the IVI system is To provide a description of the service associated with the detected device, Checking the compatibility of the application with the detected device and the IVI system, Methods that include...

5. Accessing the application store, For selection purposes, the third-party developers of the application in the application store are listed, Downloading the application from the application store to the IVI system, The method according to any one of claims 1 to 4, including the method described in any one of claims 1 to 4.

6. The method according to any one of claims 1 to 4, comprising performing the service based on the collected information, wherein the automatic trigger for the operation comprises communicating with the service associated with the application to provide information that triggers the operation.

7. A vehicle information system, Memory for storing computer-readable instructions, A processor connected to the aforementioned memory, The processor is equipped with the above, and performs operations by executing the computer-readable instructions. The vehicle detects the device, Upon detecting the device in the vehicle, the application is provisioned to collect information from the detected device and provide services to the user based on the collected information. The application provisioned to collect the information from the detected device receives the information collected from the detected device. Upon receiving the aforementioned information, the application is configured to automatically trigger an operation regarding the service based on the information collected from the detected device. The aforementioned processor, Installing the application that communicates with the detected device, Pairing the detected device with the application, A vehicle information system configured to provision device applications to the devices detected in the vehicle.

8. The vehicle information system according to claim 7, wherein the processor is configured to pair the detected device by presenting the status of the pairing of the detected device with the application.

9. The vehicle information system according to claim 7, 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.

10. A vehicle information system, Memory for storing computer-readable instructions, A processor connected to the aforementioned memory, The processor is equipped with the above, and performs operations by executing the computer-readable instructions. The vehicle detects the device, Upon detecting the device in the vehicle, the application is provisioned to collect information from the detected device and provide services to the user based on the collected information. The application provisioned to collect the information from the detected device receives the information collected from the detected device. Upon receiving the aforementioned information, the application is configured to automatically trigger an operation regarding the service based on the information collected from the detected device. The aforementioned processor, To provide a description of the service associated with the detected device, Checking the compatibility of the application with the detected device and the vehicle, A vehicle information system configured to provision the aforementioned application.

11. The aforementioned processor, Access the application store, For selection purposes, list the third-party developers of the application in the application store, The vehicle information system according to any one of claims 7 to 10, configured to download a device application from the aforementioned application store.

12. The vehicle information system according to any one of claims 7 to 10, wherein the processor is configured to perform 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 and providing information that triggers the operation.

13. A computer program that, when executed by a processor, causes the processor to perform an action, wherein the action is: Detecting devices in a vehicle, In response to detecting the device in the vehicle, provisioning an application to the in-vehicle infotainment (IVI) system to collect information from the detected device and provide services to the user based on the collected information, The application provisioned to the IVI system receives the information collected from the detected device, Upon receiving the aforementioned information, the IVI system automatically triggers an operation regarding the service based on the information collected by the application from the detected device, Includes, The provisioning of the application to the IVI system is Installing the application on the IVI system, Pairing the detected device with the IVI system, A computer program that includes [this].

14. The computer program according to claim 13, wherein the pairing of the detected device with the IVI system includes presenting the 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 services associated with the detected device in a service registry.

15. A computer program that, when executed by a processor, causes the processor to perform an operation, wherein the operation is: Detecting devices in a vehicle, In response to detecting the device in the vehicle, provisioning an application to the in-vehicle infotainment (IVI) system to collect information from the detected device and provide services to the user based on the collected information, The application provisioned to the IVI system receives the information collected from the detected device, Upon receiving the aforementioned information, the IVI system automatically triggers an operation regarding the service based on the information collected by the application from the detected device, Includes, The provisioning of a device application for the device detected in the vehicle is: To provide a description of the service associated with the device, To check the compatibility of the device application with the aforementioned device and the aforementioned vehicle, A computer program that includes [this].

16. The aforementioned operation is, Accessing the application store, For selection purposes, the third-party developers of the application in the application store are listed, Downloading a device application from the aforementioned application store to the aforementioned IVI system, A computer program according to any one of claims 13 to 15, including the following:

17. The computer program according to any one of claims 13 to 15, wherein the operation includes performing the service based on the collected information, and the automatic trigger for the operation includes communicating with the service associated with the application to provide information that triggers the operation.

Images