Method for connecting in-vehicle infotainment device, electronic equipment and storage medium

Abstract

The invention provides a method for connecting an in-vehicle infotainment device, electronic equipment and a storage medium, relates to the technical field of terminals, and mainly aims at the situation that normal communication can be ensured only by switching a USB connection mode of the electronic equipment based on a USB connection mode of the in-vehicle infotainment device when the electronic equipment communicates with the in-vehicle infotainment device. According to the technical scheme, the Bluetooth information and the USB connection mode of the vehicle machine can be pre-stored in the electronic equipment, so that when the electronic equipment subsequently detects that the Bluetooth and the USB of the electronic equipment are in a connection state and the Bluetooth information of a Bluetooth connection object is matched with the pre-stored Bluetooth information, the connection mode of the USB of the electronic equipment can be directly switched based on the pre-stored USB connection mode, and the Bluetooth information of the Bluetooth connection object can be directly switched to the USB connection mode of the electronic equipment. And establishing connection with the vehicle machine based on the switched USB connection mode, so that a user does not need to trigger the electronic equipment to switch the USB connection mode through operations such as clicking, the learning cost of the user can be reduced, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a method for connecting a vehicle infotainment system, an electronic device, and a storage medium. Background Technology

[0002] The interconnectivity technology between mobile phones and other electronic devices and in-vehicle systems allows services from electronic devices to be transferred to the in-vehicle system. This enables users to directly access and operate applications on their electronic devices, such as navigation, music playback, phone calls, and message notifications, through the in-vehicle screen. This technology allows users to conveniently access and control various services and functions on their electronic devices while focusing on the road, significantly improving driving safety and convenience.

[0003] Current vehicle connectivity applications in electronic devices typically support multiple connection methods, such as wired connection, wireless WLAN connection, wireless hotspot connection, enhanced connection, and compatible connection. However, some vehicle systems can only connect via enhanced connection or compatible connection. Moreover, these two connection methods involve cumbersome operation steps. Once the connection is lost, the entire connection process must be repeated when reconnecting. This repeated operation seriously affects the user experience, causing many users to give up using vehicle connectivity functions after multiple attempts. Summary of the Invention

[0004] This application provides a method, electronic device, and storage medium for connecting a vehicle infotainment system. For vehicle infotainment systems that require a compatibility or enhanced mode to establish a connection, the application proposes that the Bluetooth information and Universal Serial Bus (USB) connection mode of the vehicle infotainment system can be pre-stored in the electronic device. This allows the electronic device to automatically establish a connection with the vehicle infotainment system when the Bluetooth and USB of the electronic device are subsequently established with the Bluetooth and USB of the vehicle infotainment system, respectively, thereby improving the user experience.

[0005] In a first aspect, embodiments of this application provide a method for connecting to a vehicle infotainment system, applied to an electronic device including Bluetooth and USB. The electronic device pre-stores Bluetooth information and USB connection mode of a first vehicle infotainment system. When communicating with the first vehicle infotainment system, the electronic device needs to switch its own USB connection mode based on the USB connection mode of the first vehicle infotainment system. The method includes: when the Bluetooth and USB of the electronic device are detected to be connected, determining whether the Bluetooth information of the Bluetooth connection object of the electronic device matches the Bluetooth information of the first vehicle infotainment system; when the Bluetooth information of the Bluetooth connection object of the electronic device matches the Bluetooth information of the first vehicle infotainment system, switching its own USB connection mode based on the USB connection mode of the first vehicle infotainment system; and establishing a connection with the first vehicle infotainment system based on the switched USB connection mode.

[0006] It should be noted that the aforementioned "establishing a connection with the first vehicle infotainment system" can be understood as establishing a connection between the vehicle connectivity applications in the electronic device and the vehicle connectivity applications in the first vehicle infotainment system. It should be understood that after the electronic device establishes a connection with the first vehicle infotainment system, some services on the electronic device can be transferred to the vehicle infotainment system. For example, the vehicle infotainment system can display icons of some applications from the electronic device, such as navigation, music, and phone applications, allowing users to directly access and operate these applications on the electronic device through the in-vehicle screen.

[0007] Optionally, the Bluetooth information may be a Bluetooth name or a media access control (MAC) address, etc. It should be understood that the Bluetooth name can usually be configured or changed by the user, while the MAC address is unique and cannot be changed. Therefore, to improve the accuracy of matching, this application will mainly use the Bluetooth information of the first vehicle system as the MAC address as an example, but it should be understood that it is not limited to this in practice.

[0008] Optionally, the electronic device may also simultaneously store Bluetooth information and USB connection modes of one or more other vehicle-mounted systems, with each system having a mapping relationship between its own Bluetooth information and USB connection mode; this application does not limit this. Based on this, when the Bluetooth information of the electronic device's current Bluetooth connection object matches a pre-stored Bluetooth information, it can switch its own USB connection mode based on the USB connection mode corresponding to that Bluetooth information.

[0009] It should be understood that different car head units may have USB connections that correspond to different modes. Taking a particular car head unit as an example, its USB connection modes may include any one of the following: charging mode, image transfer mode, file transfer mode, and Musical Instrument Digital Interface (MIDI) mode. Furthermore, the USB connection modes of this car head unit may also include Android Debug Bridge (ADB) mode or Android Open Accessory (AOA) mode. ADB mode can be either standard ADB or enhanced ADB mode, and AOA mode can be either standard AOA or enhanced AOA mode. It should also be understood that charging mode, image transfer mode, file transfer mode, or MIDI mode can also be understood as a USB connection protocol or connection method.

[0010] Currently, connected car applications in different electronic devices typically support different connection methods. For example, a connected car application in a certain electronic device may support multiple connection methods, such as wired connection, wireless WLAN connection, wireless hotspot connection, enhanced connection, and compatible connection. Some in-vehicle systems can connect via wired connection, for example, when the in-vehicle system's USB connection modes include charging mode and normal AOA / ADB mode. However, some in-vehicle systems can only connect via enhanced connection or compatible connection. For example, if the in-vehicle system's USB connection modes include enhanced ADB mode, then an enhanced connection is required; if the in-vehicle system's USB connection modes include enhanced AOA mode, then a compatible connection is required; and if the in-vehicle system's USB connection modes include not only enhanced ADB / AOA mode but also non-default connection modes such as image transfer mode, file transfer mode, or MIDI mode, then when using an enhanced or compatible connection, the user needs to select the appropriate mode on the electronic device's connection guide page after plugging in the USB cable.

[0011] Taking the enhanced mode and compatibility mode mentioned above as examples, when users need to establish a connection between electronic devices and the vehicle system, they need to first connect via Bluetooth and USB, and then trigger the electronic device to switch the USB connection mode by clicking or other operations based on the interface prompts. This operation is quite cumbersome, and once the connection is lost, the entire connection process must be repeated when reconnecting. This repeated operation seriously affects the user experience, causing many users to give up using the vehicle connectivity function after multiple attempts.

[0012] Based on this, in response to the situation where electronic devices need to switch their own USB connection mode based on the vehicle's USB connection mode when communicating with the vehicle's infotainment system, this application proposes to pre-store the vehicle's Bluetooth information and USB connection mode in the electronic device. This allows the electronic device to automatically establish a connection with the vehicle's infotainment system when it detects that its Bluetooth and USB are connected and the Bluetooth information of the Bluetooth connection target matches the pre-stored Bluetooth information. Specifically, the electronic device can first automatically switch its own USB connection mode based on the pre-stored USB connection mode of the vehicle's infotainment system, and then establish a connection with the vehicle's infotainment system based on the switched USB connection mode. This eliminates the need for users to trigger the switching of their own USB connection mode through clicks or other operations on the electronic device's interface, thereby reducing the user's learning cost and improving the user experience.

[0013] In conjunction with the first aspect above, in some implementations of the first aspect, the switching of its own USB connection mode based on the USB connection mode of the first vehicle unit includes: detecting whether the electronic device has established a connection with the first vehicle unit; and when it is detected that the electronic device has not established a connection with the first vehicle unit, switching its own USB connection mode based on the USB connection mode of the first vehicle unit.

[0014] Based on this implementation, electronic devices can switch their own USB connection mode according to the vehicle's USB connection mode when they detect that a connection has not yet been established with the vehicle's infotainment system; conversely, when a connection has been established with the vehicle's infotainment system, they will not switch their own USB connection mode, thereby avoiding repeated switching of USB connection modes and reducing resource consumption.

[0015] In conjunction with the first aspect above, in some implementations of the first aspect, before detecting that the Bluetooth and USB of the electronic device are in a connected state, the method further includes: upon detecting a first operation, in response to the first operation, establishing a Bluetooth connection between the electronic device and the Bluetooth of the first vehicle unit; upon detecting a second operation, in response to the second operation, establishing a USB connection between the electronic device and the USB of the first vehicle unit; upon detecting a third operation, in response to the third operation, switching the connection mode of its own USB based on the connection mode of the USB of the first vehicle unit; establishing an initial connection with the first vehicle unit based on the switched USB connection mode; and storing the Bluetooth information of the first vehicle unit and the USB connection mode of the first vehicle unit.

[0016] When a user wants to establish a connection between an electronic device and the vehicle's infotainment system for the first time, and the electronic device needs to switch its own USB connection mode based on the vehicle's USB connection mode, the first operation can be performed to establish a Bluetooth connection between the two, the second operation can be performed to establish a USB connection between the two, and finally the third operation can be performed to trigger the electronic device to switch its USB connection mode. Based on this, a connection will be established between the electronic device and the vehicle's infotainment system.

[0017] Based on this implementation, when an electronic device establishes a connection with the vehicle's infotainment system for the first time and the electronic device needs to switch its own USB connection mode based on the vehicle's USB connection mode, the electronic device can store the vehicle's Bluetooth information and USB connection mode after establishing a connection with the vehicle's infotainment system, so that it can automatically establish a connection the next time it is needed.

[0018] Alternatively, if the vehicle's Bluetooth information and USB connection mode are known in advance, this information can be stored directly in the electronic device without needing to establish an initial connection between the two.

[0019] In conjunction with the first aspect described above, in certain implementations of the first aspect, establishing an initial connection with the first vehicle-mounted infotainment system based on the switched USB connection mode includes: interacting with the first vehicle-mounted infotainment system using commands based on the switched USB connection mode; identifying the vehicle-mounted system signal based on the command interaction; obtaining the first Bluetooth information and the USB connection mode of the first vehicle-mounted system based on the vehicle-mounted system signal; and initiating the initial connection with the first vehicle-mounted system. Based on this, the initial connection between the electronic device and the vehicle-mounted system can be achieved, and the electronic device can obtain the Bluetooth information and USB connection mode of the vehicle-mounted system.

[0020] In conjunction with the first aspect above, in some implementations of the first aspect, after the Bluetooth of the electronic device establishes a connection with the Bluetooth of the first vehicle system, the method further includes: if the electronic device is currently connected to at least one Bluetooth connection object, displaying the Bluetooth name of one of the Bluetooth connection objects that is connected to the at least one Bluetooth connection object on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device.

[0021] In conjunction with the first aspect described above, in certain implementations of the first aspect, displaying the Bluetooth name of a connected Bluetooth object among the at least one connected Bluetooth objects on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device includes: obtaining the device type and input / output capabilities of each of the at least one Bluetooth connected objects; determining, based on the device type and input / output capabilities of each Bluetooth connected object, whether any of the at least one Bluetooth connected objects is a vehicle-mounted system; and, when it is determined that the first Bluetooth connected object among the at least one Bluetooth connected objects is a vehicle-mounted system, displaying the Bluetooth name of the first Bluetooth connected object on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device. Based on this, the Bluetooth connected object displayed on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device can preferentially be a vehicle-mounted system, and the accuracy of this determination is relatively high.

[0022] The device type and input / output capabilities of each Bluetooth connection object can be obtained from the Bluetooth information of each Bluetooth connection object.

[0023] In conjunction with the first aspect described above, in some implementations of the first aspect, when it is determined that the vehicle-mounted system is not among the at least one Bluetooth connection object, the method further includes: detecting whether the Bluetooth name of any of the at least one Bluetooth connection objects is related to the vehicle-mounted system; and when it is detected that the Bluetooth name of a second Bluetooth connection object among the at least one Bluetooth connection objects is related to the vehicle-mounted system, displaying the Bluetooth name of the second Bluetooth connection object on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device. Based on this, the Bluetooth connection object displayed on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device can be the vehicle-mounted system.

[0024] It should be understood that the Bluetooth name can be changed and configured by the user, who can change the Bluetooth name according to their own needs.

[0025] In conjunction with the first aspect above, in some implementations of the first aspect, when it is detected that the Bluetooth name of each of the at least one Bluetooth connection objects is unrelated to the vehicle system, the method further includes: detecting whether there is a Bluetooth connection object among the at least one Bluetooth connection objects whose device type is a preset type; when it is detected that the device type of a third Bluetooth connection object among the at least one Bluetooth connection objects is a preset type, displaying the Bluetooth name of the third Bluetooth connection object on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device.

[0026] It should be understood that since some in-vehicle infotainment systems may be configured with Bluetooth device type as headphones or other device types, if no Bluetooth connection object is detected as an in-vehicle infotainment system through the above two methods, it is possible to check whether there is a Bluetooth connection object with a preset device type. If the device type of a Bluetooth connection object is a preset device type, it can be considered that the Bluetooth connection object is an in-vehicle infotainment system. Furthermore, the Bluetooth name of the Bluetooth connection object can be displayed on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device.

[0027] In conjunction with the first aspect above, in some implementations of the first aspect, after establishing an initial connection with the first vehicle-mounted unit and before storing the Bluetooth information and USB connection mode of the first vehicle-mounted unit, the method further includes: obtaining second Bluetooth information of the first vehicle-mounted unit from the first vehicle-mounted unit; and updating the first Bluetooth information based on the second Bluetooth information.

[0028] Since the Bluetooth information obtained after the electronic device establishes a connection with the vehicle system is more accurate, this application proposes to update the Bluetooth information (i.e., the first Bluetooth information mentioned above) obtained during the connection process after the electronic device establishes an initial connection with the vehicle system, thereby improving the accuracy of the final stored Bluetooth information.

[0029] In conjunction with the first aspect above, in some implementations of the first aspect, the USB connection mode of the first vehicle unit includes a first connection mode and a second connection mode, wherein the first connection mode is a charging mode, and the second connection mode is an enhanced Android Debug Bridge (ADB) mode or an enhanced Android Open Accessory (AOA) mode; or, the first connection mode is an image transmission mode, a file transmission mode, or a MIDI mode, and the second connection mode is an AOA mode, which is a normal AOA mode or an enhanced AOA mode.

[0030] The USB connection mode of the first vehicle-mounted system mentioned above is just an example. In actual applications, other connection modes may also be included. As long as it is based on this connection mode, when the electronic device communicates with the vehicle-mounted system, the electronic device needs to switch its own USB connection mode according to the vehicle-mounted system's USB connection mode in order to ensure normal communication with the vehicle-mounted system.

[0031] In conjunction with the first aspect above, in some implementations of the first aspect, the Bluetooth information includes the Bluetooth MAC address.

[0032] In a second aspect, embodiments of this application provide an electronic device, including: one or more processors; one or more memories; the memories storing one or more programs, which, when executed by the processors, cause the electronic device to perform any of the possible methods described in the first aspect.

[0033] Thirdly, embodiments of this application provide an apparatus included in an electronic device, which has the function of implementing the behaviors of the electronic device in the above aspects and possible implementations thereof. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. For example, a display module or unit, a detection module or unit, a processing module or unit, etc.

[0034] Fourthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform any of the possible methods described in the first aspect.

[0035] Fifthly, embodiments of this application provide a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the possible methods described in the first aspect above.

[0036] The technical effects achieved by the second, third, fourth, and fifth aspects mentioned above are similar to those achieved by the corresponding technical means in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0037] Figure 1 This is a schematic diagram illustrating an application scenario provided in an embodiment of this application;

[0038] Figure 2 This is a schematic diagram of the interface of a vehicle screen after a mobile phone and a vehicle system are interconnected, provided in an embodiment of this application;

[0039] Figure 3 This is a schematic diagram of the operation entry point of a vehicle-to-everything (V2X) application in a mobile phone, provided in an embodiment of this application.

[0040] Figure 4This is a schematic diagram of a user operation process for connecting to a vehicle-mounted infotainment system, provided in an embodiment of this application.

[0041] Figure 5 This is a schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application;

[0042] Figure 6 This is a software structure block diagram of an electronic device 100 provided in an embodiment of this application;

[0043] Figure 7 This is a schematic diagram of the system architecture of an electronic device provided in an embodiment of this application;

[0044] Figure 8 This is a flowchart illustrating a method for connecting a vehicle-mounted system according to an embodiment of this application;

[0045] Figure 9 This is a schematic flowchart illustrating another method for connecting a vehicle-mounted system provided in an embodiment of this application;

[0046] Figure 10 This is a schematic flowchart illustrating the initial connection to the vehicle's infotainment system, provided in an embodiment of this application.

[0047] Figure 11 This is a schematic flowchart illustrating a non-first-time connection to the vehicle system provided in an embodiment of this application;

[0048] Figure 12 This is a schematic diagram of a device for connecting a vehicle infotainment system provided in an embodiment of this application;

[0049] Figure 13 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0050] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and purpose. For example, "first chip" and "second chip" are used only to distinguish different chips and do not limit their order. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" do not necessarily imply that they are different.

[0051] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0052] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0053] The following is a detailed description of the proposed solution with reference to the accompanying drawings.

[0054] Figure 1 This is a schematic diagram illustrating an application scenario provided in an embodiment of this application. For example... Figure 1 As shown, this application scenario includes an electronic device 10 and an in-vehicle infotainment system 20. The electronic device 10 may include an application capable of connecting to the in-vehicle infotainment system (hereinafter referred to as the first vehicle-connected application), and the in-vehicle infotainment system 20 may include an application supporting connection to the vehicle-connected application in the electronic device (hereinafter referred to as the second vehicle-connected application). It should be understood that the first and second vehicle-connected applications are human-machine interface (HMI) applications, serving as a medium for interaction and information exchange between the user and the system.

[0055] The electronic device 10 and the vehicle infotainment system 20 may each include a software development kit (SDK) related to vehicle connectivity applications. The first and second vehicle connectivity applications can establish a connection based on the SDK. As an example, the SDK may be named CarLife SDK, but this application does not limit it. For ease of description, the CarLife SDK in the electronic device 10 will be uniformly referred to as the first CarLife SDK, and the CarLife SDK in the vehicle infotainment system 20 will be uniformly referred to as the second CarLife SDK.

[0056] When a connection is established between vehicle-to-everything (V2X) applications on an electronic device and those on the vehicle's infotainment system, service flows from the electronic device can be routed to the vehicle's infotainment system, allowing users to directly access and operate some applications on the electronic device through the vehicle's screen. Taking a mobile phone as an example... Figure 2 This is a schematic diagram of the interface of an in-vehicle screen after a mobile phone and a vehicle infotainment system are interconnected, provided in an embodiment of this application. Figure 2As shown, after the mobile phone 30 and the vehicle's infotainment system 40 establish a connection, some applications on the mobile phone 30, such as navigation, music, phone calls, videos, contacts, and messages, can be displayed on the vehicle's screen. Based on this, users can conveniently access and control various services and functions on their mobile phones while focusing on the road, greatly improving driving safety and convenience. It should be understood that... Figure 2 The application shown is for illustrative purposes only; other applications may be displayed in practice, and this application does not limit this.

[0057] It should be understood that the corresponding USB connection modes may differ for different car head units. Taking a particular car head unit as an example, its USB connection modes typically include Connection Mode 1 and Connection Mode 2. Connection Mode 1 can be any of the following: charging mode, image transfer mode, file transfer mode, and MIDI mode. Connection Mode 2 can be ADB mode or AOA mode. ADB mode can be either standard ADB mode or enhanced ADB mode, and AOA mode can be either standard AOA mode or enhanced AOA mode. It should also be understood that the aforementioned charging mode, image transfer mode, file transfer mode, or MIDI mode can also be understood as a USB connection protocol or connection method.

[0058] For electronic devices, their default USB connection mode is usually charging mode. Therefore, when an electronic device connects to a vehicle-mounted infotainment system via USB in either charging or standard ADB / AOA mode, it can communicate normally without adjusting its USB connection mode (meaning the system can correctly recognize the information sent by the electronic device). However, when the system's USB connection mode includes non-default modes such as image transfer, file transfer, or MIDI, and / or enhanced ADB / AOA mode, the system cannot correctly recognize the information sent by the electronic device. Therefore, the electronic device needs to switch its USB connection mode to a mode that the system can recognize. This "recognizable" connection mode ensures that the information sent by the electronic device can be correctly recognized by the system during USB communication. It should be noted that in one possible implementation, after the USB cable is plugged in, the electronic device's interface will display charging mode, image transfer mode, file transfer mode, and MIDI mode via a pop-up window for the user to select. The user can choose according to their actual needs, and the default mode will be charging mode if the user does not select one.

[0059] It should be understood that the naming of the various connection modes above is only an example, and there may be other naming methods in practice. For example, enhanced ADB / AOA mode may also be described as special ADB / AOA mode, etc., or enhanced AOA mode may also be described as compatible AOA mode, etc. This application does not limit this.

[0060] To achieve connectivity with different in-vehicle infotainment systems, connected car applications in electronic devices typically support various connection methods. As an example, and not a limitation, a connected car application in a particular electronic device may support wired connections, wireless WLAN connections, wireless hotspot connections, enhanced connections, and compatible connections. For some in-vehicle infotainment systems, a wired connection is sufficient. For instance, when the in-vehicle infotainment system's USB connection modes include charging mode and standard AOA / ADB mode, a wired connection is possible. However, some in-vehicle infotainment systems can only connect via enhanced or compatible connections. For example, when the in-vehicle infotainment system's USB connection modes include charging mode and enhanced ADB mode, an enhanced connection is required. After plugging in the USB cable, the user needs to select the charging mode in the pop-up window on the electronic device's connection guide page (it should be understood that after plugging in the USB cable, the connection guide page can automatically display options such as charging mode, image transfer mode, file transfer mode, and MIDI mode). When the in-vehicle infotainment system's USB connection modes include non-default connection modes such as image transfer mode, file transfer mode, or MIDI mode, or enhanced ADB mode, an enhanced connection is required. For in-vehicle infotainment systems, the USB connection mode includes charging mode and enhanced AOA mode. When the USB connection mode is compatible with charging mode, the user must select the charging mode or the default charging mode in the pop-up window of the connection guide page after plugging in the USB cable. Similarly, for in-vehicle infotainment systems with non-default connection modes such as image transfer mode, file transfer mode, or MIDI mode, or enhanced AOA mode, the user must select the charging mode in the pop-up window of the connection guide page after plugging in the USB cable.

[0061] Taking mobile phones as an example, Figure 3 This is a schematic diagram illustrating the operation entry point of a vehicle-to-everything (V2X) application in a mobile phone, as provided in an embodiment of this application. Figure 3 As shown in (a) to (d), mobile phone users typically need to go through steps such as Settings - More Connections - Car Connectivity to access the car connectivity application. The following section combines... Figure 4 An example of the user operation process for connecting to the vehicle's infotainment system based on this vehicle connectivity application is provided.

[0062] For example, Figure 4This is a schematic diagram of a user operation process for connecting to a vehicle-mounted infotainment system, provided in an embodiment of this application. Figure 4 As shown in (a), when a user enters the vehicle connectivity application interface of an electronic device, they can first click the "Wired Connection" control; in response to the user's click, the phone displays as shown in (a). Figure 4 The interface shown in (b) may include a connection guide: "After opening the vehicle connectivity application on the vehicle's infotainment system, connect your phone and the vehicle's infotainment system using a USB cable." Based on this guide, the user opens the vehicle connectivity application on the vehicle's infotainment system and connects their phone and the system using a USB cable. Additionally, the interface may include a connection guide: "If the connection fails, try clicking the 'Enhanced Connection' control." It should be noted that, for situations where the current vehicle's infotainment system can only connect to the phone via enhanced connection (taking the current vehicle's USB connection modes as an example, including charging mode and enhanced ADB mode) or compatible connection (taking the current vehicle's USB connection modes as an example, including charging mode and enhanced AOA mode), a connection failure may occur after the user opens the vehicle connectivity application and connects the phone and the system using a USB cable. In this case, the user can click the "Enhanced Connection" control according to the connection guide on the interface. In response to the user's click, the phone displays the following... Figure 4 The interface shown in (c) may include connection guides "Step 1: Connect to Car Bluetooth" and "Select Bluetooth in Settings, then select Connect to Car Bluetooth in Bluetooth settings." This interface may also include a "Go directly to Bluetooth" control and a "Next" control. Based on the connection guides, users can establish a Bluetooth connection between their phone and the car's infotainment system. Furthermore, after a successful Bluetooth connection, the interface can display the connected car's Bluetooth name, for example, "Connected: 'VW BT 6029'." After confirming a successful Bluetooth connection, the user can click the "Next" control. In response to the user's click on the "Next" control, the phone displays the following... Figure 4 The interface shown in (d) includes connection guides "Step 2: USB Data Cable Connection" and "Connecting the Phone and Car System with a USB Data Cable," as well as a "Next" control. Based on these connection guides, users can establish a USB connection between their phone and the car system. It should be noted that after the user inserts the USB data cable, the phone connection guide page can automatically display options such as charging mode, image transfer mode, file transfer mode, and MIDI mode. Users can choose either the default charging mode or directly select the charging mode. Furthermore, after a successful USB connection, the interface can display "Connected." After confirming a successful USB connection, the user can click the "Next" control. In response to the user's click on the corresponding "Next" control, the phone displays the following... Figure 4The interface shown in (e) may include connection guides "Step 3: Open the vehicle connectivity application" and "Open the vehicle connectivity application on the vehicle's infotainment system, and click the 'Start Connection' control below on your mobile phone to initiate enhanced connection," as well as a "Start Connection" control. Based on the above connection guides, the user can click the "Start Connection" control after confirming that the vehicle connectivity application on the vehicle's infotainment system is open. In response to the user's click on the corresponding "Start Connection" control, the mobile phone switches its USB connection mode to enhanced ADB mode so that the vehicle's infotainment system, including both charging mode and enhanced ADB mode, can recognize the messages it sends. However, if the current USB connection mode of the vehicle's infotainment system actually includes both charging mode and enhanced ADB mode, a connection error will occur, and the following will be displayed: Figure 4 The interface shown in (f) prompts the user "Connection error, you can click the 'Switch Compatible Connection' control below to try to reconnect" and displays the "Cancel" and "Switch Compatible Connection" controls. Based on this, if the user no longer wants to use the vehicle connectivity function, they can click the "Cancel" control; if they want to continue using it, they can click the "Switch Compatible Connection" control. In response to the user's click on the "Switch Compatible Connection" control, the phone switches its own USB connection mode to enhanced AOA mode so that the vehicle system, including charging mode and enhanced AOA mode, can recognize the messages it sends.

[0063] Based on the above operation process, it can be seen that the current in-vehicle system can only connect to the mobile phone through enhanced connection or compatible connection methods. The operation is quite cumbersome, and users usually need at least 5 steps to complete the connection. Moreover, once the connection is lost, the entire connection process must be repeated when reconnecting. This repeated operation seriously affects the user experience, causing many users to give up using the vehicle connectivity function after multiple attempts.

[0064] Based on this, in response to the situation where electronic devices need to switch their own USB connection modes based on the vehicle's USB connection mode when communicating with the vehicle's infotainment system, this application proposes that the Bluetooth information and USB connection mode of the vehicle's infotainment system be pre-stored in the electronic device. This allows the electronic device to directly switch its own USB connection mode based on the pre-stored Bluetooth connection mode when it detects that its Bluetooth and USB are connected and the Bluetooth information of the Bluetooth connection target matches the pre-stored Bluetooth information. Then, it can establish a connection with the vehicle's infotainment system based on the switched USB connection mode. This eliminates the need for users to trigger the electronic device to switch USB connection modes through clicks or other operations, thereby reducing the user's learning cost and improving the user experience.

[0065] Optionally, the aforementioned electronic device may also be referred to as user equipment (UE), terminal equipment, or user terminal, etc.; the electronic device may be, but is not limited to, mobile phones, tablets, desktops, laptops, handheld computers, notebook computers, in-vehicle systems, ultra-mobile personal computers (UMPCs), netbooks, cellular phones, personal digital assistants (PDAs), augmented reality (AR) / virtual reality (VR) devices, etc., and the embodiments of this application do not limit this.

[0066] For example, Figure 5 This is a schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a USB interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, etc.

[0067] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0068] Processor 110 may include one or more processing units, such as application processors, satellite communication processors, modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0069] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0070] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0071] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0072] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, display screen 194, camera 193, and wireless communication module 160, etc. In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0073] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0074] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.

[0075] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the same device as at least some modules of the processor 110.

[0076] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0077] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with networks and other devices through wireless communication technology.

[0078] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0079] The display screen 194 is used to display images, display videos, and receive swipe operations, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0080] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0081] The ISP is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0082] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0083] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0084] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0085] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0086] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0087] Internal memory 121 can be used to store executable program code, including instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of electronic device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory located within the processor.

[0088] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0089] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0090] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, touch operations applied to different applications (such as taking photos, playing audio, etc.) can correspond to different vibration feedback effects. Touch operations applied to different areas of the display screen 194 can also correspond to different vibration feedback effects from motor 191. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0091] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0092] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0093] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture, etc. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of electronic device 100.

[0094] Figure 6This is a software structure block diagram of an electronic device 100 provided in an embodiment of this application. The layered architecture divides the software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system can be divided into, from top to bottom, the application layer, the business middleware, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0095] The application layer can include a series of application packages. For example... Figure 6 As shown, the application package may include applications such as camera, gallery, calling, map, navigation, WLAN, Bluetooth, music, video, messaging, and vehicle connectivity.

[0096] The business middle platform is used to execute different operations based on different instructions issued by the application layer, and it serves as a bridge between the application layer and the underlying system. In this application, the business middle platform may include an interconnection middle platform, which is used to execute different operations based on different instructions issued by the vehicle connectivity application, and serves as a bridge between the vehicle connectivity application and the Bluetooth manager and USB manager.

[0097] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0098] like Figure 6 As shown, the application framework layer may include a Bluetooth manager, USB manager, window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0099] The Bluetooth manager is used to manage the Bluetooth connection status.

[0100] The USB manager is used to manage the status of USB devices and switch between USB modes.

[0101] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0102] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0103] A view system includes visual controls, such as controls for displaying characters and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon could include a view for displaying characters and a view for displaying images.

[0104] A phone manager is used to provide communication functions for electronic devices. For example, it manages call status (including connection and disconnection).

[0105] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0106] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0107] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0108] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0109] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0110] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0111] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0112] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0113] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0114] A 2D graphics engine is a graphics engine for 2D drawing.

[0115] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, audio drivers, sensor drivers, Bluetooth drivers, USB drivers, etc.

[0116] It should be noted that although the embodiments of this application are described using the Android system, the solutions of this application are also applicable to electronic devices with operating systems such as iOS or Windows.

[0117] In conjunction with the scheme of this application, Figure 7 This is a schematic diagram of the system architecture of an electronic device provided in an embodiment of this application. For example... Figure 7 As shown, the system architecture mainly involves the application layer, business middle platform, application framework layer and kernel layer.

[0118] The application layer primarily includes vehicle connectivity applications, which are HMI applications and serve as the direct interface for user interaction with the system. They are mainly responsible for managing device connections, interface display, and the connection status management of vehicle connectivity applications. Device connection management includes handling the establishment, maintenance, and disconnection of connections such as Bluetooth and USB. Interface display includes showing the connection status of Bluetooth and USB devices, connection guides, etc. Vehicle connectivity application connection status management includes sending the connection status to the connectivity platform after a successful connection between the electronic device and the vehicle's connectivity application. Additionally, it can send the vehicle's Bluetooth information and USB connection mode to the connectivity platform.

[0119] The business middle platform mainly includes an interconnection middle platform. This interconnection middle platform is used to execute different operations based on different instructions issued by the vehicle connectivity application. It acts as a bridge between the vehicle connectivity application and the Bluetooth and USB frameworks to ensure communication and coordination between different modules. In this application, this interconnection middle platform can be used to send the discovered vehicle system signals to the vehicle connectivity application when a USB and Bluetooth connection is established. It can also be used to store the vehicle system's Bluetooth information and USB connection mode when it receives the connection status, vehicle system Bluetooth information, and USB connection mode from the vehicle connectivity application.

[0120] The application framework layer mainly includes the USB framework and the Bluetooth framework. The USB framework includes a USB manager for managing USB connection status and USB mode switching, while the Bluetooth framework includes a Bluetooth manager for managing Bluetooth connection status. The kernel layer mainly includes the USB driver and the Bluetooth driver, primarily responsible for data interaction with the peer vehicle's infotainment system.

[0121] In this application's solution, after detecting a physical connection to a USB device, the USB driver can generate a connection state change event and report the event to the USB framework. Upon receiving the event, the USB framework updates the USB connection state and then notifies the interconnection platform of the USB connection state change. Subsequently, the interconnection platform can generate a message to inform the application layer that the vehicle-mounted device has been discovered. Similarly, after detecting a Bluetooth connection, the Bluetooth driver can generate a connection state change event and report the event to the Bluetooth framework. Upon receiving the event, the Bluetooth framework updates the Bluetooth connection state and then notifies the interconnection platform of the Bluetooth connection state change. Subsequently, the interconnection platform can generate a message to inform the application layer that the vehicle-mounted device has been discovered. In addition, after a user clicks the "Start Connection" control (i.e., requests to switch USB connection modes) in the vehicle connectivity application, the user can send the USB connection mode switching request to the USB framework through the connectivity platform. After receiving the request, the USB framework verifies the current status and sends a mode switching command to the USB driver. After receiving the command, the USB driver interacts with the hardware to execute the specific mode switching operation. Furthermore, after the USB driver completes the switch, it can also feed back the execution result and current status to the USB framework. Subsequently, the USB framework updates the system status and notifies the vehicle connectivity application through the connectivity platform.

[0122] The following is a detailed description of the proposed solution with reference to the accompanying drawings. Figure 8 This is a flowchart illustrating a method for connecting to a vehicle infotainment system provided in this application. It should be noted that this application primarily addresses situations where an electronic device needs to switch its own USB connection mode based on the vehicle infotainment system's USB connection mode in order to communicate normally with the system. Furthermore, before executing method 800, at least one vehicle infotainment system's Bluetooth information and USB connection mode satisfying the above conditions need to be pre-stored in the electronic device. Each vehicle infotainment system has a mapping relationship between its Bluetooth information and USB connection mode (based on this, when the Bluetooth information of the electronic device's current Bluetooth connection object matches a pre-stored Bluetooth information, it can switch its own USB connection mode based on the USB connection mode corresponding to that Bluetooth information). The following example uses an electronic device pre-stored with the Bluetooth information and USB connection mode of a first vehicle infotainment system. Figure 8 As shown, the method 800 includes steps S810 to S830, which will be described in detail below.

[0123] S810: When the electronic device detects that its Bluetooth and USB are connected, it determines whether the Bluetooth information of the Bluetooth connection object of the electronic device matches the Bluetooth information of the first vehicle system.

[0124] Specifically, electronic devices can detect whether their Bluetooth and USB connections are active by listening to Bluetooth connection broadcasts and USB connection broadcasts in real time.

[0125] The Bluetooth connection between the electronic device and the vehicle's infotainment system can be established automatically when the electronic device approaches the vehicle's infotainment system, or it can be established manually by the user; this application does not limit this. Similarly, the USB connection between the electronic device and the vehicle's infotainment system can be established manually by the user. It should be understood that this application does not limit the order in which the Bluetooth and USB connections are made.

[0126] For example, the Bluetooth information mentioned above can be a Bluetooth name or a media access control (MAC) address. It should be understood that the Bluetooth name can usually be configured or changed by the user, while the MAC address is unique and cannot be changed. Therefore, to improve the accuracy of matching, the following embodiments will mainly use the MAC address as the Bluetooth information as an example, but it should be understood that the actual implementation is not limited to this.

[0127] S820: When the Bluetooth information of the Bluetooth connection object of the electronic device matches the Bluetooth information of the first vehicle unit, the electronic device switches its own USB connection mode based on the USB connection mode of the first vehicle unit.

[0128] Specifically, the USB connection mode of the first vehicle-mounted unit can include a first connection mode and a second connection mode.

[0129] As an example, the first connection mode is charging mode, and the second connection mode is enhanced ADB mode or enhanced AOA mode.

[0130] As another example, the first connection mode is any one of image transfer mode, file transfer mode, or MIDI mode, and the second connection mode is AOA mode, which is either normal AOA mode or enhanced AOA mode.

[0131] It should be understood that the USB connection mode of the first vehicle-mounted system mentioned above is only an example. Other connection modes may also be included in actual applications. As long as it is based on this connection mode, when the electronic device communicates with the vehicle-mounted system, the electronic device needs to switch its own USB connection mode according to the vehicle-mounted system's USB connection mode in order to ensure normal communication with the vehicle-mounted system.

[0132] It should be understood that, based on the USB connection mode switched by the electronic device, the electronic device and the first vehicle-mounted system can communicate normally, meaning the first vehicle-mounted system can recognize the information sent by the electronic device. Therefore, the electronic device and the first vehicle-mounted system can establish a connection through information exchange.

[0133] Optionally, before switching its own USB connection mode based on the USB connection mode of the first vehicle unit, the electronic device can first detect whether a connection has been established between itself and the first vehicle unit; if it detects that a connection has not been established between itself and the first vehicle unit, it then switches its own USB connection mode based on the USB connection mode of the first vehicle unit; and if it detects that a connection has been established between itself and the first vehicle unit, it no longer switches its own USB connection mode, thereby avoiding repeated switching of USB connection modes and reducing resource consumption.

[0134] The S830 electronic device establishes a connection with the first vehicle-mounted system based on the switched USB connection mode.

[0135] It should be noted that the aforementioned "establishing a connection with the first vehicle infotainment system" can be understood as establishing a connection between the vehicle connectivity applications in the electronic device and the vehicle connectivity applications in the first vehicle infotainment system. It should be understood that after the electronic device establishes a connection with the first vehicle infotainment system, some services on the electronic device can be transferred to the vehicle infotainment system. For example, the vehicle infotainment system can display icons of some applications from the electronic device, such as navigation, music, and phone applications, allowing users to directly access and operate these applications on the electronic device through the in-vehicle screen.

[0136] Based on the switched USB connection mode, the process of establishing a connection between the electronic device and the first vehicle-mounted system can be as follows: Based on the switched USB connection mode, the electronic device and the first vehicle-mounted system interact with commands; based on this command interaction, the electronic device can detect the vehicle-mounted system signal of the first vehicle-mounted system; subsequently, the electronic device can initiate a connection with the first vehicle-mounted system based on the vehicle-mounted system signal.

[0137] In summary, addressing the issue that electronic devices need to switch their USB connection modes based on the vehicle's USB connection mode when communicating with the vehicle's infotainment system, this application proposes pre-storing the vehicle's Bluetooth information and USB connection mode in the electronic device. This allows the electronic device to automatically establish a connection with the vehicle's infotainment system when it detects that its Bluetooth and USB are connected and the Bluetooth information of the Bluetooth connection target matches the pre-stored Bluetooth information. Specifically, the electronic device can first automatically switch its own USB connection mode based on the pre-stored vehicle's USB connection mode, and then establish a connection with the vehicle's infotainment system based on the switched USB connection mode. This eliminates the need for users to manually switch their USB connection modes through clicks or other operations on the electronic device's interface, thereby reducing the learning curve and improving the user experience.

[0138] Alternatively, in one possible implementation, the electronic device can pre-store the Bluetooth information and USB connection mode of the first vehicle unit in the following manner:

[0139] When a user wants to establish a connection between an electronic device and a vehicle-mounted infotainment system for the first time, and the electronic device needs to switch its own USB connection mode based on the vehicle-mounted system's USB connection mode to ensure normal communication, the user can first perform a first operation. Upon detecting the first operation, the electronic device, in response, establishes a Bluetooth connection with the vehicle-mounted system's Bluetooth. Then, the user performs a second operation. Upon detecting the second operation, the electronic device, in response, establishes a USB connection with the vehicle-mounted system's USB. Finally, the user performs a third operation. Upon detecting the third operation, the electronic device, in response, switches its own USB connection mode based on the vehicle-mounted system's USB connection mode. Based on the switched USB connection mode, the electronic device establishes an initial connection with the vehicle-mounted system. Subsequently, the vehicle-mounted system's Bluetooth information and USB connection mode can be stored. It should be understood that this application does not limit the order in which the user performs the first and second operations.

[0140] by Figure 4 Taking the operation flow shown as an example, the first operation can be a user's click operation when connecting via Bluetooth; the second operation can be a user's operation of connecting electronic devices and the car's system via a USB data cable, as well as the operation of selecting charging mode, image transmission mode, file transmission mode, and MIDI mode; the third operation can be a user's operation of clicking the "Start Connection" control; or an operation of clicking the "Switch Compatible Connection" control after clicking the "Start Connection" control.

[0141] Based on this implementation, when an electronic device establishes a connection with the vehicle's infotainment system for the first time and the electronic device needs to switch its own USB connection mode based on the vehicle's USB connection mode, the electronic device can store the vehicle's Bluetooth information and USB connection mode after establishing a connection with the vehicle's infotainment system, so that it can automatically establish a connection the next time it is needed.

[0142] Specifically, the process of establishing the initial connection between the electronic device and the first vehicle-mounted system can be as follows: Based on the switched USB connection mode, the electronic device and the first vehicle-mounted system interact with commands; based on this command interaction, the electronic device recognizes the vehicle-mounted system's signal; according to this signal, the electronic device obtains the first Bluetooth information and the first vehicle-mounted system's USB connection mode; subsequently, the electronic device initiates the initial connection with the first vehicle-mounted system. Based on this, the initial connection between the electronic device and the vehicle-mounted system can be achieved, and the electronic device can obtain the vehicle-mounted system's Bluetooth information and USB connection mode.

[0143] Since the Bluetooth information obtained after the electronic device establishes a connection with the vehicle system is more accurate, this application also proposes that after the electronic device establishes an initial connection with the first vehicle system, the second Bluetooth information of the first vehicle system can be obtained again, and the first Bluetooth information obtained during the connection process can be updated based on the second Bluetooth information, thereby improving the accuracy of the final stored Bluetooth information.

[0144] Optionally, after the electronic device establishes a connection with the first vehicle-mounted system, if the electronic device detects an instruction to disconnect from the first vehicle-mounted system, the electronic device can detect whether the instruction was triggered by the user. If the instruction was triggered by the user, the electronic device can output a prompt message to ask the user whether the connection needs to be re-established, and determine whether the connection needs to be re-established based on the user's instruction. Alternatively, if the electronic device detects that the instruction was not triggered by the user, the electronic device can directly re-initiate the connection with the first vehicle-mounted system, thereby improving the user experience.

[0145] It should be understood that when it is detected that the instruction was triggered by the user's actions on the interface, it can be considered that the instruction was triggered by the user.

[0146] Optionally, after the electronic device's Bluetooth establishes a connection with the first vehicle's Bluetooth, the Bluetooth name of the connected Bluetooth object can be displayed on the Bluetooth connection guide page of the electronic device's vehicle connectivity application. However, when the electronic device is connected to at least one Bluetooth object simultaneously, ensuring that the Bluetooth name of the connected Bluetooth object displayed on the Bluetooth connection guide page is the Bluetooth name of the first vehicle's Bluetooth is a problem that urgently needs to be solved.

[0147] To address the aforementioned problems, this application proposes the following strategy:

[0148] The electronic device acquires the device type and input / output capabilities of each of the at least one Bluetooth connection objects; based on the device type and input / output capabilities of each Bluetooth connection object, it determines whether any of the at least one Bluetooth connection objects is a vehicle-mounted system; when it is determined that the first Bluetooth connection object among the at least one Bluetooth connection objects is a vehicle-mounted system, the Bluetooth name of the first Bluetooth connection object is displayed on the Bluetooth connection guide page of the electronic device's vehicle connectivity application. Therefore, the Bluetooth connection objects displayed on the Bluetooth connection guide page of the electronic device's vehicle connectivity application can preferentially be vehicle-mounted systems, and this method of determination has high accuracy.

[0149] The device type and input / output capabilities of each Bluetooth connection object can be obtained from its Bluetooth information. It should be understood that after an electronic device establishes a Bluetooth connection, it can obtain the Bluetooth information of the Bluetooth connection object. This information may include the Bluetooth name, MAC address, device attributes, etc., of the connection object. These device attributes can indicate the device type of the connection object; for example, when the Bluetooth connection object is a vehicle infotainment system, the device attributes can indicate that the device type is a vehicle infotainment system.

[0150] When an electronic device determines that the vehicle's infotainment system is not among the at least one Bluetooth connection objects, it can continue to detect whether the Bluetooth name of any of the at least one Bluetooth connection objects is associated with the vehicle's infotainment system. If a second Bluetooth connection object among the at least one Bluetooth connection objects is detected to be associated with the vehicle's infotainment system, the Bluetooth name of the second Bluetooth connection object is displayed on the Bluetooth connection guide page of the electronic device's vehicle connectivity application. Based on this, the Bluetooth connection object displayed on the Bluetooth connection guide page of the electronic device's vehicle connectivity application can be the vehicle's infotainment system.

[0151] It should be understood that the Bluetooth name can be changed and configured by the user, who can change the Bluetooth name according to their own needs.

[0152] When the electronic device detects that the Bluetooth name of each of the at least one Bluetooth connection objects is not related to the vehicle system, it can continue to detect whether there is a Bluetooth connection object whose device type is a preset type. When the device type of the third Bluetooth connection object among the at least one Bluetooth connection objects is detected to be a preset type, the Bluetooth name of the third Bluetooth connection object is displayed on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device.

[0153] It should be understood that since some in-vehicle infotainment systems may be configured with Bluetooth device type as headphones or other device types, if no Bluetooth connection object is detected as an in-vehicle infotainment system through the above two methods, it is possible to check whether there is a Bluetooth connection object with a preset device type. If the device type of a Bluetooth connection object is a preset device type, it can be considered that the Bluetooth connection object is an in-vehicle infotainment system. Furthermore, the Bluetooth name of the Bluetooth connection object can be displayed on the Bluetooth connection guide page of the vehicle connectivity application of the electronic device.

[0154] In another possible implementation, if the R&D personnel know the Bluetooth information and USB connection mode of the first vehicle's infotainment system in advance, they can directly store this information in the electronic device without having to establish an initial connection between the two.

[0155] Figure 9This is a schematic flowchart illustrating another method for connecting a vehicle-mounted system provided in this application embodiment. It should be understood that method 900 can be considered as an example of method 800 described above. Method 900 mainly includes a process for establishing a connection between the electronic device and the vehicle-mounted system for the first time, and a process for establishing a connection between the electronic device and the vehicle-mounted system for the second time. The various steps in method 900 are described below.

[0156] The execution flow during the initial connection is as follows:

[0157] S901, Bluetooth for connecting users' mobile phones and the car's infotainment system;

[0158] For example, users can base their decisions on, such as Figure 4 The Bluetooth connectivity guide in vehicle connectivity application shown in (c) connects the phone and the vehicle's Bluetooth system.

[0159] S902: The mobile phone Bluetooth and the car's Bluetooth establish a connection;

[0160] S903: The mobile phone's Bluetooth returns Bluetooth device information to the mobile car connectivity application.

[0161] S904: Users plug a USB data cable into their mobile phone and the car's infotainment system.

[0162] For example, users can base their decisions on, such as Figure 4 The USB connection guide shown in (d) in the diagram shows how to plug the USB cable into the phone and the car's infotainment system.

[0163] S905: The mobile phone's USB port and the car's USB port establish a connection;

[0164] S906: The phone's USB port returns a "USB connected" message to the phone's vehicle connectivity application.

[0165] S907, user-triggered USB mode switching;

[0166] For example, users can base their decisions on, such as Figure 4 The connection guide shown in (e) prompts you to click the "Start Connection" control to trigger the phone to switch to USB connection mode (hereinafter referred to as USB mode).

[0167] S908, the mobile car connectivity application sends a command to the mobile connectivity platform to switch USB mode;

[0168] S909, the mobile interconnection platform sends a command to the mobile phone's USB to switch USB modes;

[0169] S910 allows the phone's USB port to interact with the car's USB port, switching between phone USB modes;

[0170] S911, in-vehicle infotainment system with USB recognition for mobile phone USB devices;

[0171] S912, the car infotainment USB pulls up the car infotainment CarLife SDK;

[0172] S913: The vehicle's USB port and the mobile phone's USB port can exchange commands, and the mobile phone's USB port can detect the vehicle's signal.

[0173] S914: The mobile phone's USB port sends the vehicle's system signal to the mobile phone interconnection platform;

[0174] S915, the mobile phone interconnection platform enables mobile phone vehicle connectivity applications;

[0175] S916, the mobile car connectivity application notifies the mobile interconnection platform to initiate a connection with the vehicle system;

[0176] S917, the mobile interconnection platform notifies the mobile carlife SDK to initiate a connection with the vehicle system;

[0177] S918: The mobile phone's CarLife SDK establishes a connection channel with the vehicle's CarLife SDK.

[0178] S919, the carlife SDK of the vehicle system notifies that the vehicle system and vehicle connectivity application have been successfully connected;

[0179] It should be understood that vehicle-to-vehicle connectivity applications can display a message to the user indicating that the connection has been successfully established.

[0180] After step S918, execute synchronously:

[0181] S920, the mobile carlife SDK notifies the mobile car connectivity application that the connection is successful;

[0182] It should be understood that mobile car connectivity applications can display a message to users indicating that the connection has been successfully established.

[0183] S921, the mobile car connectivity application notifies the mobile connectivity platform that the connection has been successful and sends the vehicle device information (Bluetooth MAC address and vehicle USB connection mode) to the mobile connectivity platform;

[0184] S922, the mobile phone interconnection platform stores information about the vehicle's infotainment devices.

[0185] Based on the information stored during the initial connection, when connecting to the vehicle system again (it should be understood that a non-first-time connection could be a reconnection after an abnormal situation caused by a successful initial connection, such as a disconnection due to a loose USB port while the vehicle is in motion, followed by the user reconnecting the cable; or a non-first-time connection could be a connection established the user will make the next time they use the system after a successful initial connection, such as a connection established by the user when they want to use the vehicle connectivity service again by plugging in a USB cable and connecting via Bluetooth), the execution process is as follows:

[0186] S923, mobile interconnection platform monitoring Bluetooth connection broadcast;

[0187] S924, mobile interconnection platform monitors USB connection broadcasts;

[0188] S925, establishes a connection between the mobile phone's Bluetooth and the car's Bluetooth;

[0189] S926, the mobile interconnection platform receives the Bluetooth connection information sent by the mobile phone via Bluetooth;

[0190] S927, establish a connection between the mobile phone's USB and the vehicle's USB;

[0191] S928, the mobile interconnection platform receives the USB connection information sent by the mobile phone's USB;

[0192] S929, the mobile interconnection platform detects whether the connected object is a device that has been connected before;

[0193] Specifically, if the Bluetooth MAC address of the currently connected object is pre-stored, it can be assumed that the currently connected object is a device that has been connected before, and step S930 can continue to be executed.

[0194] S930, the mobile phone interconnection platform detects whether the current mobile phone is connected to the vehicle's infotainment system;

[0195] If not connected to the vehicle's infotainment system, continue with step S931.

[0196] S931, the mobile interconnection platform obtains the USB mode corresponding to the Bluetooth MAC address;

[0197] S932, the mobile interconnection platform sends a command to the mobile phone's USB to switch USB modes;

[0198] After the mobile phone receives the instruction to switch USB mode sent by the mobile phone interconnection platform, the connection between the mobile phone and the vehicle system can be established by referring to S910 to S921 above, which will not be repeated here.

[0199] Based on this implementation, when the phone's Bluetooth and USB are both connected to the vehicle's Bluetooth and USB, the phone and vehicle can automatically reconnect during non-first-time connections. This eliminates the need for users to perform any additional operations in the phone's vehicle connectivity application, thereby improving user experience, reducing user learning costs, and increasing connection success rate.

[0200] For example, Figure 10This is a schematic diagram illustrating the process of a mobile phone connecting to a vehicle's infotainment system for the first time, as provided in an embodiment of this application. It should be understood that this example primarily describes the interaction between various modules within the mobile phone-vehicle connectivity application after the user triggers the switch to USB mode during the initial connection process. Operations prior to the user triggering the switch to USB mode can be found in steps S901 to S906 above and will not be repeated here. Figure 10 As shown, the specific operation process is as follows:

[0201] S1001, users can trigger the switch to USB mode through the connection guide interface displayed in the mobile vehicle connectivity application;

[0202] For example, users can base their decisions on, such as Figure 4 The interface prompt in the connection guide of the mobile vehicle connectivity application shown in (e) indicates that clicking the "Start Connection" control triggers the phone to switch to USB connection mode.

[0203] S1002, The connection guide interface in the mobile vehicle connectivity application displays a notification that the user interface (UI) in the mobile vehicle connectivity application is switching to USB mode.

[0204] S1003, the UI display management module in the mobile vehicle connectivity application sends a command to the interconnection platform in the mobile phone to switch the USB mode;

[0205] S1004, the interconnection platform in the mobile phone notifies the USB to switch modes;

[0206] For details, please refer to steps S909 to S910 above.

[0207] S1005, After the USB mode switch is completed, the connection management service in the mobile vehicle connectivity application discovers the vehicle signal;

[0208] For details, please refer to steps S911 to S915 above.

[0209] S1006, The connection management service in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application that the vehicle signal has been detected;

[0210] S1007, The device manager in the mobile car connectivity application notifies the Car Connect View Factory module in the mobile car connectivity application that the vehicle signal has been detected;

[0211] S1008, the Car Connect View Factory in the mobile car connectivity application notifies the UI display management module in the mobile car connectivity application that the vehicle signal has been detected and requests the initialization of the UI interface;

[0212] S1009, The UI display management module in the mobile vehicle connectivity application sends a connection preparation instruction to the device manager in the mobile vehicle connectivity application;

[0213] S1010, The device manager in the mobile vehicle connectivity application sends a connection preparation instruction to the connection management module in the mobile vehicle connectivity application;

[0214] S1011, The connection management module in the mobile vehicle connectivity application sends the current connection policy to the connection policy processing module in the mobile vehicle connectivity application;

[0215] The current connection strategy may include connection method, connection protocol, or connection mode.

[0216] S1012, The connection strategy processing module in the mobile vehicle connectivity application processes the current connection strategy;

[0217] S1013, The connection strategy processing module in the mobile vehicle connectivity application returns the processing result to the connection management module in the mobile vehicle connectivity application;

[0218] S1014, The connection management module in the mobile vehicle connectivity application notifies the USB enhanced connection module in the mobile vehicle connectivity application to prepare for connection.

[0219] S1015, the USB enhanced connection module in the mobile car connectivity application stores the device information of the corresponding vehicle system, including the Bluetooth MAC address and USB mode of the corresponding vehicle system;

[0220] S1016, The USB enhanced connection module in the mobile vehicle connectivity application notifies the converged interconnection and interaction adaptation module in the mobile vehicle connectivity application to initiate a connection.

[0221] S1017, The USB enhanced connection module in the mobile vehicle connectivity application notifies the connection management module in the mobile vehicle connectivity application to update the connection status to "connecting".

[0222] S1018, The connection management module in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application to update the connection status to "connecting".

[0223] S1019, The device manager in the mobile vehicle connectivity application notifies the UI display management module in the mobile vehicle connectivity application to refresh the UI display;

[0224] Following step S1016, the following is also executed synchronously:

[0225] S1020, the interconnection and interaction adaptation module in the mobile vehicle connectivity application notifies the interconnection platform in the mobile phone to start the connection.

[0226] S1021, the interconnection platform in the mobile phone launches the carlife SDK in the mobile phone;

[0227] S1022, The carlife SDK in the mobile phone notifies the carlife SDK interaction adaptation module binding service in the mobile car connectivity application;

[0228] S1023, the carlife SDK in the mobile phone connects to the vehicle's infotainment system;

[0229] S1024. After a successful connection, the carlife SDK in the phone notifies the carlife SDK interaction adaptation module in the phone's vehicle connectivity application to create a virtual screen.

[0230] S1025, the carlife SDK interaction adaptation module in the mobile car connectivity application creates a virtual screen;

[0231] S1026 After the virtual screen is successfully created, the carlife SDK interaction adaptation module in the mobile car connectivity application starts the in-vehicle interface display service in the mobile car connectivity application.

[0232] S1027 After the vehicle interface is successfully loaded, the vehicle interface display service notification in the mobile vehicle connectivity application shows that the USB enhanced connection module interface in the mobile vehicle connectivity application has been successfully loaded.

[0233] S1028, The USB enhanced connection module in the mobile vehicle connectivity application notifies the connection management module in the mobile vehicle connectivity application that the connection is successful.

[0234] S1029, The connection management module in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application that the connection is successful.

[0235] S1030, the device manager in the mobile vehicle connectivity application notifies the UI display management module in the mobile vehicle connectivity application that the connection is successful and refreshes the UI display;

[0236] Following step S1025, the following is also executed synchronously:

[0237] S1031, The CarLife SDK Interaction Adaptation Module in the mobile car connectivity application notifies the CarLife SDK virtual screen on the mobile phone that it has been successfully created and screen projection has started.

[0238] S1032, the carlife SDK in the mobile phone obtains the vehicle's Bluetooth MAC address from the vehicle's infotainment system and notifies the carlife SDK interaction adaptation module in the mobile phone's vehicle connectivity application to update the previously stored Bluetooth MAC address.

[0239] S1033, the carlife SDK interaction adaptation module in the mobile car connectivity application notifies the USB enhanced connection module in the mobile car connectivity application to update the previously stored Bluetooth MAC address.

[0240] S1034, the USB enhanced connection module in the mobile car connectivity application verifies and updates the Bluetooth MAC address and obtains the vehicle's USB connection mode.

[0241] S1035, the USB enhanced connection module in the mobile vehicle connectivity application notifies the interconnection and interaction adaptation module in the mobile vehicle connectivity application of the successful connection, and sends the corresponding vehicle device information, including the Bluetooth MAC address and USB mode of the corresponding vehicle device.

[0242] S1036, the interconnection and interaction adaptation module in the mobile vehicle connectivity application notifies the interconnection platform in the mobile phone of the successful connection, and sends the corresponding vehicle device information, including the Bluetooth MAC address and USB mode of the corresponding vehicle device;

[0243] S1037, Information on the interconnected middleware storage device in the mobile phone.

[0244] Other relevant information can be found in the above introduction and will not be repeated here.

[0245] Based on this, on the one hand, the device information of the vehicle system is stored during the initial connection process, so that when the mobile phone detects that the connection object is the vehicle system the next time, it can automatically establish a connection with the vehicle system without requiring the user to perform any additional operations in the mobile phone vehicle connectivity application, which can improve the user experience and reduce the user's learning cost; on the other hand, before storage, the Bluetooth MAC address is also updated, which can improve the accuracy of the final stored Bluetooth MAC address, thereby improving the matching success rate in subsequent applications.

[0246] Based on the above introduction, for example, Figure 11 This is a schematic diagram illustrating a process for a mobile phone to connect to a vehicle's infotainment system on a non-first-time connection, as provided in an embodiment of this application. It should be understood that this example primarily describes the interaction between various modules within the mobile phone's vehicle connectivity application after the mobile phone's Bluetooth and USB connections are established with the vehicle's Bluetooth and USB connections during the non-first-time connection process. Operations prior to the establishment of the Bluetooth and USB connections can be found in steps S923 to S925 and S927 above, and will not be repeated here. Figure 11 As shown, the specific operation process is as follows:

[0247] S1101, After the mobile phone Bluetooth and the vehicle's Bluetooth establish a connection, the mobile phone interconnection platform receives the Bluetooth connection information sent by the mobile phone Bluetooth.

[0248] S1102, After the mobile phone USB and the vehicle's USB are connected, the mobile phone interconnection platform receives the USB connection information sent by the mobile phone USB.

[0249] S1103, the mobile interconnection platform detects whether the connected object is a device that has been connected before;

[0250] Specifically, it can detect whether the Bluetooth MAC address of the currently connected object has been pre-stored.

[0251] S1104, when the Bluetooth MAC address of the currently connected vehicle system is pre-stored, the mobile phone interconnection platform sends a command to the mobile phone USB to switch the USB mode.

[0252] Subsequently, referring to steps S910 to S913 above, the mobile phone USB detects the vehicle's signal;

[0253] S1105, the mobile phone's USB port sends the vehicle's system signal to the mobile phone interconnection platform;

[0254] S1106, Mobile Interconnection Platform Notifies Mobile Vehicle Connectivity Application of Connection Management Service to Discover Vehicle Signal;

[0255] S1107, The connection management service in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application that the vehicle signal has been detected;

[0256] S1108, The device manager in the mobile vehicle connectivity application notifies the UI display management module in the mobile vehicle connectivity application that the vehicle signal has been detected;

[0257] S1109, The UI display management module in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application to prepare for connection;

[0258] S1110, The device manager in the mobile vehicle connectivity application notifies the connection management module in the mobile vehicle connectivity application to prepare for connection;

[0259] S1111, The connection management module in the mobile vehicle connectivity application notifies the USB enhanced connection module in the mobile vehicle connectivity application to prepare for connection.

[0260] S1112, the USB enhanced connection module in the mobile car connectivity application sets the Bluetooth MAC address and USB mode;

[0261] S1113, The USB enhanced connection module in the mobile vehicle connectivity application notifies the connection management module in the mobile vehicle connectivity application that the connection status has changed to request connection.

[0262] S1114, The connection management module in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application that the connection status has changed to request connection.

[0263] S1115, The device manager in the mobile vehicle connectivity application notifies the UI display management module in the mobile vehicle connectivity application that the connection status has changed to request connection.

[0264] S1116, The UI display management module in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application to confirm the connection;

[0265] S1117, The device manager in the mobile vehicle connectivity application notifies the connection management module in the mobile vehicle connectivity application to confirm the connection.

[0266] S1118, The connection management module in the mobile vehicle connectivity application notifies the USB enhanced connection module in the mobile vehicle connectivity application to start connecting;

[0267] S1119, The USB enhanced connection module in the mobile vehicle connectivity application notifies the interconnection and interaction adaptation module in the mobile vehicle connectivity application to start connecting.

[0268] S1120, The USB enhanced connection module in the mobile vehicle connectivity application notifies the connection management module in the mobile vehicle connectivity application that the connection status has changed to connecting.

[0269] S1121, The connection management module in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application that the connection status has changed to connecting.

[0270] S1122, The device manager in the mobile vehicle connectivity application notifies the UI display management module in the mobile vehicle connectivity application that the connection status has changed to "connecting".

[0271] Following step S1119, the following is also executed synchronously:

[0272] S1123, The interconnection and interaction adaptation module in the mobile vehicle connectivity application notifies the mobile interconnection platform to start connecting;

[0273] S1124, the mobile interconnection platform activates the carlife SDK in the mobile phone;

[0274] S1125, after the CarLife SDK in the mobile phone successfully connects with the CarLife SDK in the vehicle system, it notifies the CarLife SDK interaction adaptation module in the mobile phone vehicle connectivity application that the connection is successful.

[0275] S1126, The carlife SDK interaction adaptation module in the mobile car connectivity application notifies the interconnection interaction adaptation module in the mobile car connectivity application that the connection is successful.

[0276] S1127, The interconnection and interaction adaptation module in the mobile vehicle connectivity application notifies the USB enhanced connection module in the mobile vehicle connectivity application that the connection is successful.

[0277] S1128, The USB enhanced connection module in the mobile vehicle connectivity application notifies the connection management module in the mobile vehicle connectivity application that the connection status has changed to successful connection.

[0278] S1129, The connection management module in the mobile vehicle connectivity application notifies the device manager in the mobile vehicle connectivity application that the connection status has changed to successful connection.

[0279] S1130, The device manager in the mobile vehicle connectivity application notifies the UI display management module in the mobile vehicle connectivity application that the connection status has changed to successful connection.

[0280] Following step S1126, the following is also executed synchronously:

[0281] S1131, The interconnection and interaction adaptation module in the mobile vehicle connectivity application notifies the mobile interconnection platform that the connection is successful.

[0282] S1132, the mobile phone interconnection platform stores the current status and device information of the connected vehicle system.

[0283] Other relevant information can be found in the above introduction and will not be repeated here.

[0284] Based on this, when the phone is detected to be connected to a vehicle system that has been previously connected, it can automatically establish a connection with that vehicle system without requiring the user to perform any additional operations in the phone's vehicle connectivity application. This can improve the user experience and reduce the user's learning cost.

[0285] The following, combined with Figure 12 This application describes a device 1200 for connecting to a vehicle infotainment system. It should be understood that this device 1200 is applied to an electronic device including Bluetooth and USB. The electronic device pre-stores Bluetooth information and the USB connection mode of the first vehicle infotainment system. When communicating with the first vehicle infotainment system, the electronic device needs to switch its own USB connection mode based on the USB connection mode of the first vehicle infotainment system. Figure 12 As shown, the device includes a judgment module 1210 and a processing module 1220.

[0286] The judgment module 1210 and the processing module 1220 are used by the device 1200 to execute the corresponding processing steps in the above method embodiments. For example, the judgment module 1210 is used to determine whether the Bluetooth information of the Bluetooth connection object of the electronic device matches the Bluetooth information of the first vehicle unit when the Bluetooth and USB of the electronic device are detected to be connected; the processing module 1220 is used to switch its own USB connection mode based on the USB connection mode of the first vehicle unit when the Bluetooth information of the Bluetooth connection object of the electronic device matches the Bluetooth information of the first vehicle unit; and establish a connection with the first vehicle unit based on the switched USB connection mode.

[0287] It should be understood that other related steps performed by the judgment module 1210 and the processing module 1220 can be found in the description in the above method embodiments, and will not be repeated here.

[0288] In one possible implementation, the device 1200 may further include a storage module. This storage module is connected to the judgment module 1210 and the processing module 1220 via a line. The storage module may include one or more memories, which can be devices in one or more devices or circuits used to store programs or data. The storage module can exist independently and be connected to the judgment module 1210 and the processing module 1220 via a communication bus. Alternatively, the storage module may be integrated with the judgment module 1210 and the processing module 1220.

[0289] The storage module may store computer-executable instructions for the methods in device 1200, causing device 1200 to execute the methods described in the above embodiments. The storage module may be a register, cache memory, or random access memory (RAM), etc. The storage module may also be a read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions.

[0290] Figure 13 This is a schematic diagram of the structure of a chip 1300 provided in an embodiment of this application. For example... Figure 13 As shown, chip 1300 includes one or more (including two) processors 1301, communication lines 1302 and communication interfaces 1303. Optionally, chip 1300 also includes a memory 1304.

[0291] In some implementations, memory 1304 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof.

[0292] The methods described in the embodiments of this application can be applied to processor 1301, or implemented by processor 1301. Processor 1301 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above methods can be completed by integrated logic circuits in the hardware of processor 1301 or by instructions in software form. The processor 1301 may be a general-purpose processor (e.g., a microprocessor or conventional processor), a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates, transistor logic devices, or discrete hardware components.

[0293] The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can be located in mature storage media in the art, such as random access memory, read-only memory, programmable read-only memory, or electrically erasable programmable read-only memory (EEPROM). This storage medium is located in memory 1304, and processor 1301 reads information from memory 1304 and, in conjunction with its hardware, completes the steps of the above method.

[0294] The processor 1301, memory 1304 and communication interface 1303 can communicate with each other via communication line 1302.

[0295] In the above embodiments, the instructions stored in the memory for execution by the processor can be implemented in the form of a computer program product. This computer program product can be pre-written into the memory, or it can be downloaded and installed into the memory as software.

[0296] This application also provides a computer program product comprising one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. For example, available media may include magnetic media (e.g., floppy disk, hard disk, or magnetic tape), optical media (e.g., digital versatile disc (DVD)), or semiconductor media (e.g., solid-state disk (SSD)).

[0297] This application also provides a device for connecting to a vehicle infotainment system, including: one or more processors; one or more memories; the memories store one or more programs, and when one or more programs are executed by the processor, the device performs the technical solutions described above.

[0298] This application provides a chip. The chip includes a processor, which is used to call a computer program in memory to execute the technical solutions in the above embodiments. Its implementation principle and technical effects are similar to those in the related embodiments described above, and will not be repeated here.

[0299] This application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are executed by a processor, they implement the methods described above. The methods described in the above embodiments can be implemented wholly or partially by software, hardware, firmware, or any combination thereof. If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted over the computer-readable medium. The computer-readable medium can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium accessible by a computer.

[0300] As one possible design, computer-readable media may include compact disc read-only memory (CD-ROM), RAM, ROM, EEPROM, or other optical disc storage; computer-readable media may include disk storage or other disk storage devices. Furthermore, any connecting cable may also be appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. As used herein, disks and optical discs include optical discs (CD), laser discs, optical discs, DVDs, floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0301] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1A device that provides the functions specified in one or more boxes.

[0302] The above specific embodiments further illustrate the purpose, technical solution and beneficial effects of this application. It should be understood that the above are only specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A method of connecting a vehicle to a machine, characterized by, The method is applied to an electronic device including Bluetooth and a universal serial bus (USB), the electronic device pre-stores Bluetooth information of a first vehicle machine and a connection mode of a USB of the first vehicle machine, the electronic device needs to switch a connection mode of a USB of the electronic device based on the connection mode of the USB of the first vehicle machine when the electronic device communicates with the first vehicle machine, and the method comprises the following steps. When it is detected that the Bluetooth and the USB of the electronic device are in a connection state, it is judged whether Bluetooth information of a Bluetooth connection object of the electronic device matches the Bluetooth information of the first vehicle machine. When the Bluetooth information of the Bluetooth connection object of the electronic device matches the Bluetooth information of the first vehicle machine, the connection mode of the USB of the electronic device is switched based on the connection mode of the USB of the first vehicle machine. Based on the switched connection mode of the USB, a connection with the first vehicle machine is established.

2. The method of claim 1, wherein, The step of switching the connection mode of the USB of the electronic device based on the connection mode of the USB of the first vehicle machine comprises the following steps. It is detected whether the electronic device has established a connection with the first vehicle machine. When it is detected that the electronic device has not established a connection with the first vehicle machine, the connection mode of the USB of the electronic device is switched based on the connection mode of the USB of the first vehicle machine.

3. The method according to claim 1 or 2, characterized in that, Before it is detected that the Bluetooth and the USB of the electronic device are in a connection state, the method further comprises the following steps. When a first operation is detected, the Bluetooth of the electronic device establishes a connection with the Bluetooth of the first vehicle machine in response to the first operation. When a second operation is detected, the USB of the electronic device establishes a connection with the USB of the first vehicle machine in response to the second operation. When a third operation is detected, the connection mode of the USB of the electronic device is switched based on the connection mode of the USB of the first vehicle machine in response to the third operation. Based on the switched connection mode of the USB, a first connection with the first vehicle machine is established. The Bluetooth information of the first vehicle machine and the connection mode of the USB of the first vehicle machine are stored.

4. The method of claim 3, wherein, The step of establishing the first connection with the first vehicle machine based on the switched connection mode of the USB comprises the following steps. Based on the switched connection mode of the USB, an instruction interaction with the first vehicle machine is performed. Based on the instruction interaction, a vehicle machine signal of the first vehicle machine is identified. According to the vehicle machine signal, the first Bluetooth information of the first vehicle machine and the connection mode of the USB of the first vehicle machine are obtained. The first connection with the first vehicle machine is initiated.

5. The method of claim 3, wherein, After the Bluetooth of the electronic device establishes a connection with the Bluetooth of the first vehicle machine, the method further comprises the following steps. In a case where the electronic device has currently connected at least one Bluetooth connection object, a Bluetooth connection guide page of a vehicle connection application of the electronic device displays a Bluetooth name of a certain Bluetooth connection object in the at least one Bluetooth connection object that has been connected.

6. The method of claim 5, wherein, The step of displaying the Bluetooth name of the certain Bluetooth connection object in the at least one Bluetooth connection object that has been connected on the Bluetooth connection guide page of the vehicle connection application of the electronic device comprises the following steps. Device types and input and output capabilities of each Bluetooth connection object in the at least one Bluetooth connection object are obtained. determine whether a Bluetooth connection object in the at least one Bluetooth connection object is a car machine according to a device type and an input and output capability of each Bluetooth connection object; when it is determined that a first Bluetooth connection object in the at least one Bluetooth connection object is a car machine, display a Bluetooth name of the first Bluetooth connection object on a Bluetooth connection guide page of a car application of the electronic device.

7. The method of claim 6, wherein, when it is determined that there is no car machine in the at least one Bluetooth connection object, the method further includes: detect whether a Bluetooth name of a Bluetooth connection object in the at least one Bluetooth connection object is related to a car machine; when it is detected that a Bluetooth name of a second Bluetooth connection object in the at least one Bluetooth connection object is related to a car machine, display the Bluetooth name of the second Bluetooth connection object on the Bluetooth connection guide page of the car application of the electronic device.

8. The method of claim 7, wherein, when it is detected that a Bluetooth name of each Bluetooth connection object in the at least one Bluetooth connection object is not related to a car machine, the method further includes: detect whether a device type of a Bluetooth connection object in the at least one Bluetooth connection object is a preset type; when it is detected that a device type of a third Bluetooth connection object in the at least one Bluetooth connection object is the preset type, display a Bluetooth name of the third Bluetooth connection object on the Bluetooth connection guide page of the car application of the electronic device.

9. The method of claim 4, wherein, after establishing a first connection with the first car machine, and before storing Bluetooth information and a connection mode of a USB of the first car machine, the method further includes: obtain second Bluetooth information of the first car machine from the first car machine; update the first Bluetooth information based on the second Bluetooth information.

10. The method according to any one of claims 1 to 9, characterized in that, the connection mode of the USB of the first car machine includes a first connection mode and a second connection mode, wherein the first connection mode is a charging mode, and the second connection mode is an enhanced Android Debug Bridge (ADB) mode or an enhanced Android Open Accessory (AOA) mode; or, the first connection mode is a picture transmission mode, a file transmission mode or a Musical Instrument Digital Interface (MIDI) mode, and the second connection mode is an AOA mode, and the AOA mode is a normal AOA mode or an enhanced AOA mode.

11. The method according to any one of claims 1 to 10, characterized in that, the Bluetooth information includes a Bluetooth Media Access Control (MAC) address.

12. An electronic device, comprising: including: one or more processors; one or more memories; the memory stores one or more programs, when the one or more programs are executed by the processor, the electronic device performs the method in any one of claims 1 to 11.

13. A computer-readable storage medium, characterized in that, the computer readable storage medium stores instructions, when it is run on a computer, the computer executes the method in any one of claims 1 to 11.

Images