Acquisition of vehicle information and display of acquired vehicle information by code

Abstract

To provide a method for acquiring vehicle information.SOLUTION: In a method for acquiring vehicle information, a menu is presented on a user interface of an infotainment system of a vehicle for acquiring the vehicle information. The vehicle information is selected via the menu for acquiring the vehicle information from a storage device related to at least one electronic control unit of the vehicle. The vehicle information acquired on the basis of the selection of the vehicle information can be received. A code having the embedded vehicle information is generated. The code having the embedded vehicle information is displayed.SELECTED DRAWING: Figure 1

Description

[Background technology]

[0001] The present specification relates to obtaining vehicle information, displaying the obtained vehicle information in code, and methods using the same.

[0002] Sophisticated and expensive equipment is used to obtain vehicle information that describes the vehicle's status. An electronic control unit (ECU), also known as an electronic control module (ECM), is an embedded system of automotive electronics that controls one or more of the electrical systems or subsystems of an automobile or other motor vehicle. Modern vehicles have many ECUs, which may include some or all of the following: engine control module (ECM), powertrain control module (PCM), transmission control module (TCM), brake control module (BCM or EBCM), central control module (CCM), central timing module (CTM), general electronic module (GEM), body control module (BCM), and suspension control module (SCM). As the transition from more mechanical types of vehicles to more electronically based vehicles continues, vehicles are having more and more ECUs.

[0003] On-board diagnostics (OBD) refers to a vehicle's self-diagnostic and reporting capabilities. In the United States, OBD is used to comply with federal emissions standards and detect faults that could increase emissions from the vehicle's tailpipe. The primary benefit of this is that the OBD system gives the vehicle owner or repair technician access to the status of various vehicle subsystems. OBD allows technicians to connect to the vehicle to obtain useful information stored in memory. However, with newer model vehicles, different vehicle architectures vary. Current solutions using OBD do not allow for data generation as the architecture evolves. Current methods are difficult to use to obtain vehicle information. Summary of the Invention

[0004] In at least one embodiment, a method for obtaining vehicle information includes presenting a menu on a user interface of an infotainment system of a vehicle to obtain vehicle information, selecting, via the menu, vehicle information for retrieval from storage associated with at least one electronic control unit of the vehicle, receiving the retrieved vehicle information based on the selection of the vehicle information, generating a code having the vehicle information embedded therein, and displaying the code having the vehicle information embedded therein.

[0005] In at least one embodiment, a system for obtaining vehicle information includes a storage device that stores computer-readable instructions and a processor coupled to the storage device, the processor configured to execute the computer-readable instructions to perform operations: presenting a menu of an infotainment system of the vehicle for obtaining the vehicle information; receiving, via the menu, a selection of vehicle information to obtain from a storage device associated with at least one electronic control unit; receiving the obtained vehicle information based on the selection of the vehicle information; generating a code having the vehicle information embedded therein; and displaying the code having the embedded vehicle information.

[0006] In at least one embodiment, the computer program causes a processor to perform operations including presenting a menu on a user interface of an infotainment system of the vehicle for obtaining vehicle information; selecting, via the menu, vehicle information for retrieval from a storage device associated with the at least one electronic control unit; receiving the retrieved vehicle information based on the selection of the vehicle information; generating a code having the vehicle information embedded therein; and displaying the code having the embedded vehicle information.

[0007] 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, in accordance with the practice in the art, various features have not been drawn to scale. In fact, the dimensions of various features may be increased or decreased for clarity of discussion. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates a vehicle cockpit according to at least one embodiment. [Figure 2] FIG. 2 illustrates a user interface with options for different menu selections according to at least one embodiment. [Figure 3] FIG. 3 illustrates a user interface for initiating the generation of vehicle information, according to at least one embodiment. [Figure 4] FIG. 4 illustrates a menu for selecting options for generating vehicle information, according to at least one embodiment. [Figure 5] FIG. 5 illustrates a transition to a preset menu according to at least one embodiment. [Figure 6] FIG. 6 illustrates a transition to a custom menu according to at least one embodiment. [Figure 7] FIG. 7 illustrates a status display according to at least one embodiment. [Figure 8] FIG. 8 illustrates a software stack for obtaining vehicle information using generated code, according to at least one embodiment. [Figure 9] FIG. 9 is a flowchart of a method for obtaining vehicle information according to at least one embodiment. [Figure 10] FIG. 10 is a high-level functional block diagram of a processor-based system according to at least one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] The embodiments described herein illustrate examples for implementing different features of the provided subject matter. Below, examples of components, values, operations, materials, arrangements, and the like are described to simplify the disclosure. These are, of course, examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, and the like are contemplated. For example, the formation of a first feature on or over 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 cannot be in direct contact. Additionally, the present disclosure repeats reference numerals and / or letters in various examples. This repetition is for simplicity and clarity and does not dictate a relationship between the various aspects and / or configurations discussed.

[0010] Additionally, spatially relative terms, such as "below," "below," "above," "up," etc., are used herein for ease of description and to describe the relationship of one element or feature to another, as shown in the figures. Spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation shown in the figures. The device may be otherwise oriented (rotated 90 degrees or at other orientations), and the spatially relative descriptors used herein interpreted accordingly.

[0011] In at least one embodiment, a method for obtaining vehicle information includes presenting a menu on a user interface of an infotainment system of the vehicle to obtain the vehicle information, selecting, via the menu, vehicle information for retrieval from a storage device associated with at least one electronic control unit of the vehicle, receiving the retrieved vehicle information based on the selection of the vehicle information, generating a code having the vehicle information embedded therein, and displaying the code having the vehicle information embedded therein.

[0012] The embodiments described herein provide a method that provides one or more advantages. For example, an infotainment system provides a menu for a user to select vehicle information to acquire. A preset menu allows the user to acquire a collection of preset information. A custom menu allows the user to select from a list of parameters for vehicle information to acquire. Once the information is acquired, a code is generated and presented on a display, the code including the acquired vehicle information. Furthermore, an operation can be initiated at each of multiple vehicles, such as a fleet of vehicles, and the user does not have to wait until information about the first vehicle is available before triggering the acquisition of vehicle information about subsequent vehicles. Information can then be collected from each vehicle at once in rapid succession.

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

[0014] 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 also referred to as a heating, ventilation, and air conditioning (HVAC) system. The infotainment system 130 includes any type of infotainment system in a vehicle that has an interactive display. The steering wheel is part of the steering system that the driver operates to control the steering system and the direction of the vehicle. By operating the steering wheel 110, the driver directs the vehicle's direction to the front wheels via a linkage 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 referred to as a throttle or gas pedal. The brake pedal 114 is pressed to apply the brakes, thereby slowing and / or stopping the vehicle.

[0015] The instrument panel 120 is a portion of the dashboard located behind the steering wheel 110. The instrument panel 120 includes various gauges and lights that update the driver on the status of the vehicle. For example, the instrument panel 120 often includes a traction control indicator, engine temperature, a tachometer, a fuel gauge, a speedometer, an odometer, turn indicators, a gear display, and various warning lights. The tachometer displays the rotations of the engine's crankshaft in revolutions per minute (RPM). The speedometer displays the vehicle's speed. The odometer displays the total miles traveled since the car began driving. The fuel gauge indicates how much fuel is remaining in the vehicle. The temperature gauge indicates the current engine temperature. Alternatively, designated lights may include warnings of engine temperature issues, such as an overheating engine. Turn signals represent flashing lights on both sides of the vehicle that inform other drivers of the direction the driver intends to turn. The gear display or gear position indicator indicates the currently engaged gear, such as park, neutral, or drive. Warning lights communicate different status items of the vehicle. Vehicles have various features like pre-installed ESC and ABS, not to mention more standard components or elements. Warning lights come on briefly at start-up as the vehicle checks and ensures the systems are safe and drivable. Occasionally, one warning light will come on and could indicate a problem with the engine, headlights, temperature, etc.

[0016] 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 includes any type of infotainment system in a vehicle that has an interactive display. According to at least one embodiment, the infotainment system 130 presents a user interface for menus that allow a user to generate information related to the vehicle. 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 generate vehicle information that guide the user through different vehicle information generation operations. For example, the menu options 134, 136 include a selector for selecting a preset menu and a selector for selecting a custom menu.

[0017] Climate control system 140 includes controls for setting the temperature inside the vehicle and controls for setting the operation of climate control system 140, such as air conditioning, heating, defrost, floor vents, defrost vents, passenger vents, and combinations thereof. For example, there are air vents located in different locations within the vehicle, such as vent 142 to provide center airflow, vent 144 to provide airflow toward the driver, vent 146 to provide airflow toward the passengers, and above-dash vent 148 to defrost windshield 150. Additional vents can be located in different areas of the vehicle, such as in the rear seat area, under the dash, etc.

[0018] FIG. 2 illustrates a user interface 200 with options for different menu selections in accordance with at least one embodiment.

[0019] User interface 200 includes a title bar 210 that provides an indicator of the current menu. In FIG. 2 , title bar 210 shows the Vehicle XYZ menu. User interface 200 includes a display area 220 for displaying additional menu options. User interface 200 may be provided, for example, as part of an infotainment system, including any type of infotainment system for a vehicle with an interactive display. Displayed within display area 220 is a vehicle information generation menu 230 for selecting to generate vehicle information. The vehicle information is provided by a code, such as a two-dimensional barcode (also known as a "QR code") 232. Display area 220 may also display menu option 240 and other menu options 250.

[0020] FIG. 3 illustrates a user interface 300 for initiating the generation of vehicle information, according to at least one embodiment.

[0021] In FIG. 3 , user interface 300 includes title bar 310, which provides an indicator of the current menu. Title bar 310 shows the Vehicle XYZ menu. User interface 300 again shows display area 320 for the display of additional menu options. Within display area 320, vehicle information generation menu 330 is shown selected (as represented by a highlighted border) to initiate the generation of vehicle information. Vehicle information is provided by a code, such as a two-dimensional barcode 332. Display area 320 may also display menu option 340 and other menu options 350.

[0022] FIG. 4 illustrates a menu 400 for selecting options for generating vehicle information, according to at least one embodiment.

[0023] In FIG. 4, menu 400 is displayed after selecting vehicle information generation menu 330, as described above with reference to FIG. 3. Menu 400 includes title bar 410, which provides an indicator of the current menu. Title bar 410 indicates the Vehicle XYZ menu. Within display area 420, preset generation menu 430 is displayed for selection by a user to generate vehicle information in a code, such as a two-dimensional barcode, based on preset parameters. Custom generation menu 440 is displayed for selection by a user to generate vehicle information in a code, such as a two-dimensional barcode, based on a selection of custom parameters. Again, display area 420 can display other menu options 450.

[0024] FIG. 5 illustrates a transition to a preset menu 500 according to at least one embodiment.

[0025] 5, the preset creation menu 530 is shown selected as indicated by the border of the preset creation menu 530 being highlighted. Title bar 510 shows the menu for vehicle XYZ. Within display area 520, the preset creation menu 530 appears selected to display a preset options menu 560. Display area 520 also shows a deselected custom creation menu selector 540, as well as other menu options 550.

[0026] Selecting the preset generation menu displays a preset options menu 560. The preset options menu 560 includes a title bar 562 that identifies navigation to a menu for selecting a preset. The preset options menu 560 includes a display area 520 for the preset options menu 560 and presents a pre-established collection of information that a manufacturer believes a user, such as a mechanic or vehicle technician, would be interested in obtaining for analyzing and troubleshooting a vehicle. For example, in at least one embodiment, the preset options menu 560 displays an option for selecting tire information 570, an option for selecting electric vehicle (EV) battery health information 580, and other menu options 590. The preset options menu 560 uses preset settings to generate vehicle information without the user having to select individual information.

[0027] FIG. 6 illustrates a transition to a custom menu 600 according to at least one embodiment.

[0028] 6, the custom create menu 640 is shown selected as indicated by the border of the custom create menu 640 being highlighted. The title bar 610 shows the vehicle XYZ menu. Within the display area 620, the preset create menu 630 is shown as unselected to display the preset options menu 560. The display area 620 also shows other menu options 650.

[0029] Selecting the custom creation menu 640 displays a custom options menu 660. The custom options menu 660 includes a title bar 662 that represents navigation to a menu for selecting custom information. The custom options menu 660 includes a custom options menu 660 display area 620 that shows the individual pieces of information that can be selected for generating customized vehicle information.

[0030] The custom options menu 660 allows the user to select individual pieces of information as desired, such as a menu for selecting battery statistics 670, tire pressure statistics 680, on-board system software information 690, etc. Each of the options, e.g., battery statistics 670, tire pressure statistics 680, and on-board system software information 690, includes a respective toggle button 672, 682, 692 for selection of each option. In FIG. 6 , toggle button 672 indicates that battery statistics 670 is not selected, and toggle button 682 indicates that tire pressure statistics 680 is not selected. Toggle button 692 indicates that on-board system software information 690 is selected. When a generate button 698 is selected, vehicle information associated with on-board system software information 690 is generated.

[0031] FIG. 7 illustrates a status display 700 according to at least one embodiment.

[0032] Status display 700 is displayed after selecting to generate preset information as shown in preset options menu 560 of FIG. 5 or after selecting generate button 698 in custom options menu 660. In FIG. 7, title bar 710 indicates that vehicle information is being acquired for vehicle XYZ. Display area 720 indicates that vehicle information generation is in progress. Indicator light and arrow 730 indicate that vehicle information generation is in progress. A partial code 732, such as a partial two-dimensional barcode, is displayed. Status display 700 indicates that vehicle information generation is enabled and that vehicle information is being downloaded.

[0033] After the selected vehicle information has been downloaded, a status display 760 is displayed. The status display 760 includes a title bar 762 that identifies the vehicle information obtained for vehicle XYZ. The display area 720 makes it clear that the vehicle data is available for scanning 770 using a code 772. The code 772 is either a two-dimensional barcode or any other code that is displayable with the vehicle information embedded in it. The two-dimensional barcode is presented to the user in the display area 720, and the user can either take a screenshot of the two-dimensional barcode or scan the two-dimensional barcode.

[0034] Other features may also be implemented, such as allowing a user to select predetermined vehicle information on an input / output device or input vehicle information the user wishes to obtain, and the user is authenticated and the user-requested input is accepted by the authenticated user.

[0035] In response to a user managing many vehicles, the user can trigger the collection of information and generation of two-dimensional barcodes on different vehicles using preset options menu 560 or custom options menu 660 without waiting for the two-dimensional barcodes to be generated. The user can then scan the two-dimensional barcodes individually after they are generated without the user having to physically connect to each vehicle to download the vehicle information.

[0036] Thus, the infotainment system presents a user interface that allows the user to generate vehicle information. In the preset options menu 560, the user does not have to select individual information, but instead receives preset information. The custom options menu 660 allows the user to select individual types of information that are of interest to the user. The generated vehicle information is a snapshot of the vehicle information and does not represent live data. In response to a user managing many vehicles, the user can trigger this process on different vehicles and then collect the information one by one after the vehicle information is generated for each vehicle.

[0037] FIG. 8 illustrates a software stack 800 for obtaining vehicle information using code generated in accordance with at least one embodiment.

[0038] In FIG. 8, infotainment system 810 includes a user interface 820, such as user interfaces 200 and 300. Infotainment system 810 includes any type of infotainment system for a vehicle with an interactive display. Different vehicle architectures vary with newer vehicle models. Current solutions using OBD do not allow for data generation as the architecture evolves. A copy software developer kit (SDK) is provided to allow for evolution to accommodate architectural changes.

[0039] A user interacts with a user interface 820 of the infotainment system 810, which interacts with the software, which then interacts with the appropriate vehicle information source 890.

[0040] The software handles the communication mechanisms with the ECUs and also provides the user interface 820. Various software tools and mechanisms are provided together in a software developer kit (SDK). The user interface 820 runs in the background and interacts with a background service 830 that collects data from the different ECUs. The user interface 820 interacts with an API 840 that contains a list of API calls 842. The developer updates the user interface 820 to be relevant for each vehicle, identifies the API calls 842, and groups the information in the generated code 880, e.g., a two-dimensional barcode. The developer references the collection of API calls 842 in the SDK.

[0041] The software is a stack of different applications controlled via a user interface 820. Different background services 830 collect vehicle information from vehicle information sources 890. The user interface 820 actually communicates with the background services 830, which run in the background. The background services 830 make different API calls 842 to the different vehicle information sources 890, e.g., at least one electronic control unit (ECU). While the background services 830 are generating the vehicle information, the user interface 820 displays it in a status display 870. Once the different data has been collected, the background services 830 respond to the user interface 820 in a status display 870 to communicate that the vehicle information has been collected and is available.

[0042] The user interface 820 retrieves the data and generates a two-dimensional barcode 880 that is displayed in the status display 870. The background service 830 communicates with the appropriate ECU or other component to retrieve relevant vehicle information. For example, the background service 830 can communicate with the appropriate ECU via API calls 842.

[0043] Each of the vehicle information sources 890, e.g., ECUs, provides different information, and the generated two-dimensional barcode 880 has the actual information embedded within it. The vehicle information in the generated two-dimensional barcode 880 can be encrypted or unencrypted. For example, the vehicle information may be encrypted and arranged in a predetermined format. The system knows the information available for searching. An interface with background services 830 provides API calls 842 to vehicle information sources 890. The API calls 842 contain details about the information available. Developers can update the user interface 820 and API calls 842 to relate to the actual information available for each vehicle.

[0044] A developer creates a user interface 820 with different types of vehicle information and groups the types of vehicle information as selected presets in a preset options menu 850 or a custom options menu 860 by referencing a collection of API calls 842 found in the SDK.

[0045] The vehicle information generated depends on the capacity of the generated code 880, e.g., a two-dimensional barcode. For example, in at least one embodiment, the capacity of the two-dimensional barcode is 8 kilobytes. However, the embodiments described herein are not meant to be limited to such capacity. Also, other codes with different capacity capabilities can be used. Different two-dimensional barcodes can be cached, or sequences of two-dimensional barcodes can be presented. Alternatively, the generated vehicle data can be compressed to increase capacity. Also, real-time information can be collected in real time, e.g., using a smartphone, according to at least one embodiment. The generated two-dimensional barcode 880 can be periodically updated or refreshed to represent current information.

[0046] For example, in response to displaying information on the smartphone, the smartphone will interact with the infotainment system 810, and ongoing communication with the background service 830 will occur periodically to retrieve current information.

[0047] According to at least one embodiment, the vehicle can provide data to a local server and the user can connect directly to the vehicle via a computer, for example, via a web browser, but this raises security concerns due to the nature of Wi-Fi and the wired connection to the computer.

[0048] Advantages are provided in response to a user wishing to collect data for a fleet of vehicles. Information retrieval can be triggered for one vehicle at a time, while collection and generation of two-dimensional barcodes 880 can be obtained depending on the availability of the two-dimensional barcodes. In contrast, with OBD, a user plugs a cable into each vehicle and waits for the data to be transferred. Thus, according to at least one embodiment, an operation can be initiated for each vehicle, and the user does not have to wait until the information is ready to initiate an operation for the next vehicle. Information can then be collected one at a time in rapid succession.

[0049] FIG. 9 is a flowchart 900 of a method for obtaining vehicle information according to at least one embodiment.

[0050] In Figure 9, the method begins at S902, where a menu is presented on the user interface for obtaining vehicle information (S910). Referring to Figure 2, a vehicle information generation menu 230 is displayed in display area 220 for selecting to generate vehicle information. Referring to Figure 3, a vehicle information generation menu 330 is shown selected (as indicated by a highlighted border) in display area 320 to initiate generation of vehicle information.

[0051] Vehicle information is selected via a menu within the user interface for retrieval from storage associated with the electronic control unit (S914). Referring to Figure 4, within display area 420, a preset generation menu 430 is displayed for selection by the user to generate vehicle information in a code, such as a two-dimensional barcode, based on preset parameters. A custom generation menu 440 is displayed for selection by the user to generate vehicle information in a code, such as a two-dimensional barcode, based on a selection of custom parameters.

[0052] 5, display area 520 displays preset generation menu 530 selected to display preset options menu 560. Selecting preset generation menu 530 displays preset options menu 560. Preset options menu 560 includes display area 520 and displays pre-established collections of information that a manufacturer assumes a user, such as a mechanic or vehicle technician, would be interested in obtaining for vehicle analysis and troubleshooting. For example, in at least one embodiment, preset options menu 560 displays an option for selecting tire information 570, an option for selecting electric vehicle (EV) battery health information, and an option for selecting other menu options 590. Preset options menu 560 uses preset settings to generate vehicle information without the user having to select individual information.

[0053] Referring to FIG. 6 , within display area 620, a create preset menu 630 is displayed as unselected to display preset options menu 560. Selecting create custom menu 640 displays custom options menu 660. Custom options menu 660 includes a display area 620 for custom options menu 660, which shows individual pieces of information selectable for generating customized vehicle information. Custom options menu 660 allows a user to select individual pieces of information as desired, such as menus for selecting battery statistics 670, tire pressure statistics 680, onboard system software information 690, etc. Each of the options, e.g., battery statistics 670, tire pressure statistics 680, and onboard system software information 690, includes a respective toggle button 672, 682, and 692 for selection of each option. In FIG. 6 , toggle button 672 indicates that battery statistics 670 is unselected, and toggle button 682 indicates that tire pressure statistics 680 is unselected. Toggle button 692 indicates that onboard system software information 690 is selected. When the generate button 698 is selected, the vehicle information associated with the on-board system software information 690 is generated.

[0054] A call to the electronic control unit is made to obtain vehicle information (S918). Referring to FIG. 8, a user interface 820 interacts with a background service 830 that runs in the background and collects data from different ECUs. The user interface 820 interacts with an API 840 that contains a list of API calls 842. The user interface 820 communicates with the background service 830 that runs in the background. The background service 830 makes different API calls 842 to different vehicle information sources 890. The interface with the background service 830 provides the API calls 842 to the vehicle information sources 890. The API calls 842 contain details about the information available. A developer can update the user interface 820 and the API calls 842 to relate to the actual information available for each vehicle. A developer creates a user interface 820 with different types of vehicle information and groups the types of vehicle information as selected presets in a preset options menu 850 or a custom options menu 860 by referencing a collection of API calls 842 found in the SDK.

[0055] A status indicator associated with the status of the vehicle information being acquired is presented (S922). Referring to FIG. 7, status display 700 is displayed after selecting to generate preset information as shown in preset options menu 560 of FIG. 5 or after selecting generate button 698 in custom options menu 660. Display area 720 indicates that generation of vehicle information is in progress. Indicator light and arrow 730 indicate that generation of vehicle information is being acquired. A partial code 732, such as a partial two-dimensional barcode, is displayed. Status display 700 indicates that generation of vehicle information is enabled and that the vehicle information is being downloaded. After the selected vehicle information is downloaded, status display 760 is displayed.

[0056] The retrieved vehicle information is received (S926) based on selecting the vehicle information via a menu within the user interface. Referring to Figure 7, after the selected vehicle information is downloaded, a status display 760 is displayed. The status display 760 includes a title bar 762 that displays the vehicle information retrieved for vehicle XYZ. The display area 720 identifies, using code 772, that vehicle data is available for scanning 770.

[0057] A code having the returned vehicle information embedded therein is generated (S930). Referring to Figure 8, background service 830 makes different API calls 842 to different vehicle information sources 890, such as one or more electronic control units (ECUs). While background service 830 is generating the vehicle information, user interface 820 displays it in status display 870. As different data is collected, background service 830 replies to user interface 820 in status display 870 to communicate that the vehicle information has been collected and is available. User interface 820 retrieves the data and generates a two-dimensional barcode 880 that is displayed in status display 870.

[0058] A code with the returned vehicle information is displayed (S934). Referring to Figure 7, display area 720 reveals that vehicle data is available for scanning 770 using code 772. Code 772 is either a two-dimensional barcode or any other code displayable with vehicle information embedded therein. The two-dimensional barcode is presented to the user in display area 720, and the user can either take a screenshot of the two-dimensional barcode or scan the two-dimensional barcode.

[0059] Then, the process ends (S940).

[0060] At least one embodiment of a method for obtaining vehicle information includes presenting a menu on a user interface of an infotainment system of the vehicle to obtain vehicle information, selecting, via the menu, vehicle information to obtain from a storage device associated with at least one electronic control unit of the vehicle, receiving the obtained vehicle information based on the selection of the vehicle information, generating a code having the vehicle information embedded therein, and displaying the code having the vehicle information embedded therein.

[0061] FIG. 10 is a high-level functional block diagram of a processor-based system 1000 according to at least one embodiment.

[0062] In at least one embodiment, processing circuit 1000 acquires vehicle information and displays the acquired vehicle information in a code, such as a two-dimensional barcode.

[0063] The processing circuit 1000, using the processor 1002, implements a method for obtaining vehicle information and displaying the obtained vehicle information in code. The processing circuit 1000 also includes a non-transitory computer-readable storage medium 1004 used to perform the obtaining of vehicle information and the displaying of the obtained vehicle information in code. The non-transitory computer-readable storage medium 1004 is coded with, among other things, instructions 1006, i.e., computer program code, that are executed by the processor 1002 to cause the processor 1002 to perform operations for obtaining vehicle information and displaying the obtained vehicle information in code. Execution of the instructions 1006 by the processor 1002 represents (at least in part) an application that implements at least a portion of the methods described herein, according to one or more embodiments (processes and / or methods described below).

[0064] The processor 1002 is electrically coupled to a non-transitory computer-readable storage medium 1004 via a bus 1008. The processor 1002 is electrically coupled to an input / output (I / O) interface 1010 by the bus 1008. A network interface 1012 is also electrically connected to the processor 1002 via the bus 1008. The network interface 1012 is connected to a network 1014, thereby connecting the processor 1002 and the non-transitory computer-readable storage medium 1004 to external elements via the network 1014. The processor 1002 is configured to execute instructions 1006 encoded on the non-transitory computer-readable storage medium 1004 to enable the processing circuit 1000 to perform at least a portion of a process and / or method. In one or more embodiments, the processor 1002 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application-specific integrated circuit (ASIC), and / or other suitable processing device.

[0065] Processing circuit 1000 includes an I / O interface 1010. I / O interface 1010 is coupled to external circuitry. In one or more embodiments, I / O interface 1010 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor direction keys for communicating information and commands to processor 1002.

[0066] The processing circuit 1000 also includes a network interface 1012 coupled to the processor 1002. The network interface 1012 enables the processing circuit 1000 to communicate with a network 1014 to which one or more other computer systems are connected. The network interface 1012 may include a wireless network interface such as Bluetooth®, Wi-Fi®, Worldwide Interoperability for Microwave Access (WiMAX®), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA®), or an Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers (IEICE) network interface.

[0067] The processing circuit 1000 is configured to receive information via an I / O interface 1010. The information received via the I / O interface 1010 may include instructions, data, design rules, libraries of cells, and / or other parameters for processing by the processor 1002. The network interface is transferred to the processor 1002 via the bus 1008. The processing circuit 1000 is configured to receive information related to a user interface (UI) 1022 via the I / O interface 1010. The information is stored as the UI 1022 in the non-transitory computer-readable storage medium 1004.

[0068] In one or more embodiments, one or more non-transitory computer-readable storage media 1004 having stored thereon instructions 1006 (in compressed or uncompressed form) that may be used to program a computer, processor, or other electronic device to perform the processes or methods described herein. The one or more non-transitory computer-readable storage media 1004 include one or more of an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, etc.

[0069] For example, the non-transitory computer-readable storage medium 1004 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 an optical disk, the one or more non-transitory computer-readable storage media 1004 includes a compact disk-read-only memory (CD-ROM), a compact disk-read / write (CD-R / W), and / or a digital video disc (DVD).

[0070] In one or more embodiments, the non-transitory computer-readable storage medium 1004 stores instructions 1006 configured to cause the processor 1002 to execute at least a portion of a process and / or method for obtaining vehicle information and displaying the obtained vehicle information in a code. In one or more embodiments, the non-transitory computer-readable storage medium 1004 also stores information, such as algorithms, that facilitate executing at least a portion of the process and / or method for obtaining vehicle information and displaying the obtained vehicle information in a code.

[0071] Thus, in at least one embodiment, the processor 1002 executes instructions 1006 stored on one or more non-transitory computer-readable storage media 1004 to obtain vehicle information and display the obtained vehicle information in code. The processor 1002 implements a user interface 1020 for an infotainment system 1030. The infotainment system 1030 includes any type of infotainment system for a vehicle having an interactive display. The processor 1002 is configured to provide a vehicle information generation menu 1022 within the user interface 1020. The processor 1002 is further configured to provide a preset generation menu 1024 and a custom generation menu 1026 in the vehicle information generation menu 1022. The processor 1002 receives the vehicle information and displays a code representation (display) 1028 (e.g., a two-dimensional barcode) on the user interface 1020. The processor 1002 implements a vehicle information generation menu 1032 for selecting to acquire vehicle information, and once the vehicle information is received, presents a code, such as a two-dimensional barcode, on the code display 1028. The processor 1002 implements a preset generation menu 1034 for presenting a preset option menu 1050 for selection by a user to generate vehicle information in a code, such as a two-dimensional barcode, based on preset parameters. The processor 1002 implements a custom generation menu 1036 for presenting a custom option menu 1060 for generating vehicle information in a code, such as a two-dimensional barcode, based on a user's selection of custom parameters. The processor 1002 implements the preset option menu 1050 to present a pre-established collection of information that the user is interested in acquiring for vehicle analysis and troubleshooting. The preset option menu 1050 includes tire information 1052, electric vehicle (EV) battery health information 1054, and other menu options 1056. The processor 1002 implements a custom options menu 1060 to present individual pieces of information that can be selected for generating customized vehicle information.The custom options menu 1060 includes battery statistics 1062, tire pressure statistics 1064, and on-board system software information 1066, as well as toggle buttons 1068 for selecting each option 1062, 1064, and 1066. The processor 1002 implements a status display 1038 to indicate ongoing generation of vehicle information. The processor 1002 implements a background service 1072 that interacts with vehicle information sources to collect vehicle information from different vehicle information sources. The processor 1002 implements an API 1040 for API calls 1042 made by the background service 1072 to different sources of vehicle information to retrieve vehicle information according to selections in the preset generation menu 1034 or custom selections in the custom generation menu 1036. Once vehicle information is obtained, the processor 1002 presents a code on a code display 1070 (e.g., a two-dimensional barcode), the code including the obtained vehicle information. The processor 1002 uses the display 1080 to present a user interface 1082. The user interface 1082 presents a vehicle information generation menu 1084 to allow a user to select vehicle information to acquire from a vehicle data source. The vehicle information generation menu 1084 further includes a preset generation menu 1086 and a custom generation menu 1088. The preset generation menu 1086 presents preset parameters for generating vehicle information in a code, such as a two-dimensional barcode, based on the preset parameters. The custom generation menu 1088 presents a custom option menu for selection of custom parameters by the user, and generates vehicle information in a code, such as a two-dimensional barcode, based on the selection of the custom parameters. Once the vehicle information is acquired, a code display 1090 presents a code, such as a two-dimensional barcode, that includes the acquired vehicle information.

[0072] The embodiments described herein provide a method that provides one or more advantages. For example, an infotainment system provides a menu for a user to select vehicle information to acquire. A preset menu allows the user to acquire a collection of preset information. A custom menu allows the user to select from a list of parameters for vehicle information to acquire. Once the information is acquired, a code is generated and presented on a display, the code including the acquired vehicle information. Furthermore, an operation can be initiated at each of multiple vehicles, such as a fleet of vehicles, and the user does not have to wait until information about the first vehicle is available before triggering the acquisition of vehicle information about subsequent vehicles. Information can then be collected from each vehicle at once in rapid succession.

[0073] Separate instances of these programs may run on any number of separate computer systems or be distributed across multiple computer systems. Thus, while particular steps are described as being performed by particular devices, software programs, processes, or entities, this need not be the case. Various alternative implementations will be appreciated by those skilled in the art.

[0074] Additionally, those skilled in the art will readily recognize that the above-described techniques can be utilized in a variety of devices, environments, and situations. Although the embodiments have been described in language specific to structural features or methodological 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 exemplary forms of implementing the claims.

Claims

1. presenting a menu on a user interface of an infotainment system of the vehicle to obtain vehicle information; selecting, via the menu, the vehicle information for retrieval from a storage device associated with at least one electronic control unit of the vehicle; receiving the vehicle information obtained based on selecting the vehicle information; generating a code having the vehicle information embedded therein; displaying the code having the vehicle information embedded therein; The processor executes a method for obtaining vehicle information.

2. The method of claim 1 , wherein presenting the menu includes the processor presenting a preset menu having pre-prepared batches of information for selection to download.

3. 2. The method of claim 1, wherein presenting the menu includes the processor presenting a custom menu having at least one selectable vehicle information type for selection to download the vehicle information associated with the at least one selectable vehicle information type.

4. 4. The method of claim 3, wherein presenting the custom menu includes the processor presenting toggle buttons associated with each of the at least one selectable vehicle information type for selecting one or more of the at least one selectable vehicle information type.

5. The method of claim 1 , wherein presenting the menu includes the processor presenting a status indicator associated with the progress of the vehicle information being obtained.

6. The method of claim 1 , wherein the code comprises a two-dimensional bar code.

7. 7. The method of claim 1, wherein selecting the vehicle information for retrieval from the storage device associated with the at least one electronic control unit via the menu in the user interface includes presenting a status indicator associated with the status of the vehicle information being retrieved.

8. A system for obtaining vehicle information, comprising: a storage device storing computer readable instructions; a processor connected to the storage device; Equipped with The processor: presenting a menu of the vehicle's infotainment system for obtaining vehicle information; receiving, via the menu, a selection of the vehicle information for retrieval from the storage associated with at least one electronic control unit; receiving the vehicle information obtained based on the selection of the vehicle information; generating a code having the vehicle information embedded therein; displaying the code having the vehicle information embedded therein; 20. A system configured to execute computer-readable instructions for performing operations for:

9. 10. The system of claim 8, wherein the menu is a pre-set menu presenting pre-prepared batches of information for selection to download.

10. 10. The system of claim 8, wherein the menu is a custom menu presenting at least one selectable vehicle information type for selection to download the vehicle information associated with the at least one selectable vehicle information type.

11. 11. The system of claim 10, wherein the custom menu includes a toggle button associated with each of the at least one selectable vehicle information type for selecting one or more of the at least one selectable vehicle information type.

12. The system of claim 8 , wherein the menu presents a status indicator associated with the status of the vehicle information being obtained.

13. The system of claim 8 , wherein the code comprises a two-dimensional bar code.

14. A system according to any one of claims 8 to 13, wherein the processor is configured to present a status indicator associated with the status of the vehicle information being obtained.

15. presenting a menu on a user interface of an infotainment system of the vehicle for obtaining vehicle information; selecting, via the menu, the vehicle information for retrieval from a storage device associated with at least one electronic control unit; receiving the vehicle information obtained based on selecting the vehicle information; generating a code having the vehicle information embedded therein; displaying the code having the vehicle information embedded therein; A computer program that causes a processor to perform operations including:

16. 16. The computer program product of claim 15, wherein presenting the menu includes presenting a preset menu having pre-prepared batches of information for selection to download.

17. 16. The computer program product of claim 15, wherein presenting the menu includes presenting a custom menu having at least one selectable vehicle information type for selection to download the vehicle information associated with the at least one selectable vehicle information type, and presenting toggle buttons associated with each of the at least one selectable vehicle information type for selecting one or more of the at least one selectable vehicle information type.

18. The computer program product of claim 15 , wherein presenting the menu includes presenting a status indicator associated with a progress of the vehicle information being obtained.

19. The computer program product of claim 15 , wherein the code comprises a two-dimensional barcode.

20. 20. The computer program product of claim 15, wherein selecting the vehicle information for retrieval from the storage associated with the at least one electronic control unit via the menu within the user interface includes presenting a status indicator associated with a status of the vehicle information being retrieved.

Images