Vehicle wireless communication method, controller and vehicle

Abstract

The invention provides a vehicle wireless communication method, a controller and a vehicle, and relates to the technical field of wireless communication, the method is applied to the vehicle controller, the vehicle controller comprises a bottom layer, a middle layer and an application layer which are in communication connection in sequence, and the method comprises the following steps: responding to a received wireless communication connection request of a mobile device; and establishing a wireless communication connection with the mobile equipment through the bottom layer. And determining connection attribute information of the mobile equipment through the middle layer. And distributing a dynamic adaptation strategy to the mobile equipment according to the connection attribute information. In response to the received communication information sent to the intermediate layer through the application layer, converting the communication information through the intermediate layer according to the connection attribute information, and sending the converted communication information to a bottom layer according to a dynamic adaptation strategy; or in response to the received communication information sent to the intermediate layer through the bottom layer, converting the communication information through the intermediate layer according to the connection attribute information, and sending the converted communication information to the application layer according to the dynamic adaptation strategy.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a vehicle wireless communication method, controller, and vehicle. Background Technology

[0002] With the increasing popularity of intelligent connected vehicles, in-vehicle infotainment systems connect to mobile devices via Bluetooth, and functions such as audio playback and voice calls have become basic vehicle features. Currently, vehicles generally use dual Bluetooth channels for control: one channel provides call services according to HFP (Hands-free Profile) / HSP (Headset Profile), and the other channel provides media audio playback services according to A2DP (Advanced Audio Distribution Profile). However, there are compatibility issues between in-vehicle infotainment systems and mobile devices, affecting the quality of Bluetooth communication connections. Summary of the Invention

[0003] In view of this, the purpose of this application is to propose a vehicle wireless communication method, controller and vehicle to solve the problem of poor compatibility between vehicle-mounted systems and mobile devices.

[0004] To achieve the above objectives, a first aspect of this application provides a vehicle wireless communication method applied to a vehicle controller, the vehicle controller comprising a bottom layer, a middle layer, and an application layer that are communicatively connected in sequence, the method comprising: In response to receiving a wireless communication connection request from a mobile device, a wireless communication connection is established with the mobile device through the underlying layer; The connection attribute information of the mobile device is determined through the intermediate layer, and a dynamic adaptation strategy is assigned to the mobile device based on the connection attribute information. In response to receiving communication information sent from the application layer to the middle layer, the middle layer converts the communication information according to the connection attribute information and sends the converted communication information to the lower layer according to the dynamic adaptation strategy; or, in response to receiving communication information sent from the lower layer to the middle layer, the middle layer converts the communication information according to the connection attribute information and sends the converted communication information to the application layer according to the dynamic adaptation strategy.

[0005] Optionally, determining the connection attribute information of the mobile device through the intermediate layer includes: The intermediate layer queries a preset device database to see if there is historical information corresponding to the mobile device. In response to the existence of the historical information, the historical information is used as the connection attribute information; In response to the absence of the historical information, an attribute test is performed on the mobile device to determine the connection attribute information of the mobile device. Optionally, the step of performing attribute testing on the mobile device to determine the connection attribute information of the mobile device includes: The mobile device supports information about the types of services it can access by querying the service discovery protocol. The control command set supported by the mobile device is tested by sending a test command set; The service type information and the control instruction set are used as the connection attribute information.

[0006] Optionally, the step of assigning a dynamic adaptation strategy to the mobile device based on the connection attribute information includes: Based on the connection attribute information, determine the audio track switching strategy, connection activity strategy, and resource allocation strategy of the mobile device respectively; The audio track switching strategy, the connection activity strategy, and the resource allocation strategy are used as the dynamic adaptation strategy.

[0007] Optionally, the step of converting the communication information according to the connection attribute information through the intermediate layer includes: Determine the type of the communication information, and convert the communication information according to the type of the communication information.

[0008] Optionally, the step of converting the communication information according to its type includes: In response to the fact that the type of the communication information is audio data, the current data format and the target data format of the audio data are determined; A decoder matching the current data format is determined from a pre-built codec library, and the audio data is decoded by the decoder to obtain standard audio data; The standard audio data is adjusted according to the target data format; An encoder matching the target data format is determined in the codec library, and the standard audio data with adjusted parameters is encoded using the encoder to obtain the target audio data.

[0009] Optionally, the step of converting the communication information according to its type includes: In response to the fact that the type of the communication information is a control instruction, the control instruction is converted into a target instruction according to a pre-built instruction mapping relationship.

[0010] Optionally, the method further includes: Receive device update information from the cloud; The device database is updated using the device update information.

[0011] Based on the same inventive concept, a second aspect of this application also provides a vehicle controller, comprising: The bottom layer is configured to establish a wireless communication connection with the mobile device in response to receiving a wireless communication connection request from the mobile device; and to forward the communication information to the middle layer in response to receiving communication information. The middle layer includes a device detection module, a dynamic adaptation engine, an information conversion engine, and an interface module; The device detection module, connected to the underlying layer, is configured to determine the connection attribute information of the mobile device; A dynamic adaptation engine, connected to the device detection module, is configured to assign a dynamic adaptation strategy to the mobile device based on the connection attribute information. An information conversion engine, connected to the device detection module, is configured to convert communication information according to the connection attribute information; The interface module is connected to the dynamic adaptation engine and the information conversion engine respectively, and is configured to provide a standardized interface for the application layer. The application layer, connected to the interface module, is configured to forward the communication information to the middle layer in response to receiving the communication information.

[0012] Based on the same inventive concept, a third aspect of this application also provides a vehicle, including a vehicle controller as described in the second aspect.

[0013] As can be seen from the above, the vehicle wireless communication method provided in this application is applied to a vehicle controller. The software layer architecture of the vehicle controller includes a bottom layer, a middle layer, and an application layer that are connected in sequence. The method includes: in response to receiving a wireless communication connection request from a mobile device, establishing a wireless communication connection with the mobile device through the bottom layer to enable communication between the mobile device and the vehicle controller; determining the connection attribute information of the mobile device through the middle layer, which includes the protocol services and control commands supported by the mobile device itself; allocating a dynamic adaptation strategy to the mobile device according to the connection attribute information, which specifies the personalized communication method between the mobile device and the vehicle controller, which is beneficial to maintaining stable wireless communication between the mobile device and the vehicle controller; in response to receiving communication information sent from the application layer to the middle layer, converting the communication information according to the connection attribute information through the middle layer, and sending the converted communication information to the bottom layer according to the dynamic adaptation strategy; or, in response to receiving communication information sent from the bottom layer to the middle layer, converting the communication information according to the connection attribute information through the middle layer, and sending the converted communication information to the application layer according to the dynamic adaptation strategy. Because there may be incompatibility issues between the vehicle-mounted controller and the mobile device, an intermediate layer added to the controller can convert the communication information so that the converted communication information is in a form compatible with the protocol services supported by the vehicle-mounted controller or the mobile device. This solves the incompatibility problem between the vehicle-mounted controller and the mobile device, and improves the stability of the communication connection and the comprehensiveness of the functionality between the vehicle-mounted controller and the mobile device. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in this application or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 This is a flowchart illustrating the vehicle wireless communication method according to an embodiment of this application; Figure 2 This is a schematic diagram of the vehicle controller according to an embodiment of this application; Figure 3 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0017] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "first," "second," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are only used to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0018] Currently, the software architecture of in-vehicle infotainment systems includes a lower-level communication layer and an application layer, while the hardware layer includes a Bluetooth radio frequency module, audio codec hardware, and chips. Mobile devices emit wireless communication signals via their own Bluetooth radio frequency modules. Upon receiving these signals, the Bluetooth radio frequency module in the in-vehicle infotainment system demodulates them to establish a basic, physical-level wireless data channel with the mobile device. The in-vehicle hardware layer then transmits the wireless communication signals to the lower-level layer. The Bluetooth protocol stack in the lower layer engages in a series of standard interactions with the mobile device based on these signals, establishing a logically reliable and encrypted communication link to complete the Bluetooth connection.

[0019] Incompatibility issues between in-vehicle infotainment systems and mobile devices result in poor Bluetooth communication connection quality between them. The main reasons include the following: 1. Due to different technical approaches used by different mobile device manufacturers, different mobile devices support different codecs. When a vehicle leaves the factory, the audio hardware chip has the supported codecs pre-installed. If the codec supported by the mobile device is different from the codec supported by the vehicle's infotainment system, the mobile device and the vehicle's infotainment system will be unable to communicate via Bluetooth or the communication quality will be very poor.

[0020] 2. AT (Attention) commands are control commands used to control Bluetooth devices. For example, a car infotainment system can use AT commands to control a Bluetooth device to answer or hang up a call. However, to enrich the functionality of their devices, mobile device manufacturers have added many non-standard AT commands, and these non-standard AT commands vary between different mobile device manufacturers. It's impossible for a car infotainment system to pre-store all non-standard AT commands from all mobile device manufacturers. This means that after a Bluetooth connection is established between the car infotainment system and the mobile device, the non-standard AT commands cannot be executed, and the corresponding Bluetooth functions cannot be implemented.

[0021] 3. Both in-vehicle systems and mobile devices typically support multiple codecs. However, since Bluetooth connections generally use a static negotiation mechanism, if a codec with poor communication quality is selected at the start of the negotiation, it will not switch to a codec with better communication quality later. In other words, dynamic selection of codecs cannot be achieved.

[0022] 4. Different mobile devices have different control logics, including inconsistent control commands, timing, and behavior. For example, some mobile devices have specific control commands for pausing audio playback, while others do not. Also, some mobile devices pause audio playback before a call is connected, while others pause playback after the call is connected. These differences in control logic can lead to problems after a Bluetooth connection is established between the vehicle and mobile devices, such as the inability to automatically pause audio playback when a call comes in, the inability to automatically resume audio playback after a call ends, and multiple mobile devices simultaneously connecting to the vehicle's infotainment system via Bluetooth competing for audio tracks.

[0023] In view of the above problems, this application proposes a vehicle wireless communication method. An intermediate layer is constructed within the software hierarchy of the vehicle controller. This intermediate layer provides communication information conversion services for vehicle controllers and mobile devices with poor compatibility, and configures personalized dynamic adaptation strategies for mobile devices. This improves the stability and quality of the wireless communication connection between the vehicle controller and mobile devices. Simultaneously, the converted communication information enables the vehicle system or mobile device to correctly execute functional services, improving the comprehensiveness of functional service execution and thus enhancing user satisfaction.

[0024] The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0025] Embodiments of this application provide a vehicle wireless communication method applied to a vehicle controller, the vehicle controller comprising a bottom layer, a middle layer, and an application layer that are communicatively connected in sequence, as shown in the reference. Figure 1 The method includes the following steps: Step 102: In response to receiving a wireless communication connection request from a mobile device, establish a wireless communication connection with the mobile device through the underlying layer.

[0026] Specifically, the controller in this embodiment can be a vehicle infotainment system, cockpit domain controller, body domain controller, or vehicle gateway, etc. The controller's software architecture includes a bottom-up layer, middle layer, and application layer. Mobile devices include mobile phones, tablets, wearable devices, etc. Wireless communication connection requests include Bluetooth connection requests, Wi-Fi connection requests, etc. After receiving a wireless communication connection request, the controller can establish a wireless communication connection with the mobile device through the bottom layer. The following uses Bluetooth communication connection as an example to illustrate the process of establishing a wireless communication connection. The mobile device sends a wireless communication signal as a Bluetooth connection request through its own Bluetooth radio frequency module. After receiving the wireless communication signal, the Bluetooth radio frequency module of the controller hardware layer demodulates the wireless communication signal to establish the most basic, physical-level wireless data channel with the mobile device. The controller hardware layer sends the wireless communication signal to the bottom layer. The Bluetooth protocol stack in the bottom layer performs a series of standard dialogues with the mobile device based on the wireless communication signal to establish a logically trusted and encrypted communication link, completing the establishment of the Bluetooth connection.

[0027] Step 104: Determine the connection attribute information of the mobile device through the intermediate layer, and assign a dynamic adaptation strategy to the mobile device based on the connection attribute information.

[0028] Specifically, after a wireless communication connection is established between the mobile device and the vehicle controller, the middleware layer can determine the mobile device's connection attribute information through its session with the mobile device. This connection attribute information describes the mobile device's wireless connectivity characteristics, serving as a profile of its capabilities. The session between the middleware layer and the mobile device includes negotiating the wireless communication protocol version, exchanging supported functional services, and control commands. The connection attribute information can specifically include the protocol types supported by the mobile device, the protocol versions, a list of supported audio codecs under the protocol, and the control command set. Here, the protocol type refers to the type of communication protocol followed by the vehicle controller and the mobile device; the protocol version refers to the version of the communication protocol; and the audio codec list lists all encoder and decoder types supported by the mobile device under the followed communication protocol. The control command set refers to the set of command languages ​​used when the mobile device and the vehicle controller communicate.

[0029] Based on connection attribute information, dynamic adaptation strategies can be assigned to mobile devices. These strategies define the communication rules between the mobile device and the vehicle controller. Different mobile devices require different dynamic adaptation strategies, enabling personalized settings for mobile device communication rules. Dynamic adaptation strategies ensure stable wireless communication connections between the mobile device and the vehicle controller, guaranteeing the smooth execution of the functional services supported by the mobile device.

[0030] Step 106: In response to receiving communication information sent from the application layer to the intermediate layer, the intermediate layer converts the communication information according to the connection attribute information and sends the converted communication information to the bottom layer according to the dynamic adaptation strategy; or, in response to receiving communication information sent from the bottom layer to the intermediate layer, the intermediate layer converts the communication information according to the connection attribute information and sends the converted communication information to the application layer according to the dynamic adaptation strategy.

[0031] Specifically, the application layer provides a human-machine interface (HMI) for users. Users send communication information through virtual function buttons on the HMI to control various functional modules, such as call modules or media playback modules. For example, a call module can be used to send a message to connect or disconnect a call, or a media playback module can be used to send a message to pause audio playback. The application layer sends the communication information to the middle layer. Due to differences in the control command formats or codec types supported by the vehicle controller and mobile devices, mobile devices may be unable to correctly execute the functional services corresponding to the communication information. To avoid this problem, the middle layer converts the communication information according to connection attribute information, transforming it into command formats supported by the mobile device or audio data that the mobile device can decode correctly, enabling the mobile device to correctly execute the functional services corresponding to the communication information. Conversely, users can also control the vehicle controller to execute corresponding functional services through their mobile devices. After a user sends communication information through their mobile device, the communication information is forwarded to the lower layer of the vehicle controller, which then forwards it to the middle layer. The middle layer converts the communication information and finally sends it to the application layer to control the various functional modules within the application layer.

[0032] For example, communication information includes audio data or control commands. The middle layer can convert audio data into an audio format that the vehicle-mounted controller or mobile device can decode, and it can also convert control commands into a command format that the vehicle-mounted controller or mobile device can execute. In this way, adding a middle layer to the controller solves the hardware incompatibility problem between the vehicle-mounted controller and the mobile device, improving the stability of the communication connection and the comprehensiveness of functionality between the vehicle-mounted controller and the mobile device.

[0033] Based on steps 102 to 106 above, the vehicle wireless communication method provided in this embodiment is applied to a vehicle controller. The software layer architecture of the vehicle controller includes a bottom layer, a middle layer, and an application layer that are connected in sequence. The method includes: in response to receiving a wireless communication connection request from a mobile device, establishing a wireless communication connection with the mobile device through the bottom layer to enable communication between the mobile device and the vehicle controller. The middle layer determines the connection attribute information of the mobile device, which includes protocol services and control commands supported by the mobile device itself. A dynamic adaptation strategy is assigned to the mobile device according to the connection attribute information. The dynamic adaptation strategy specifies a personalized communication method between the mobile device and the vehicle controller, which is beneficial for maintaining stable wireless communication between the mobile device and the vehicle controller. In response to receiving communication information sent from the application layer to the middle layer, the middle layer converts the communication information according to the connection attribute information and sends the converted communication information to the bottom layer according to the dynamic adaptation strategy; or, in response to receiving communication information sent from the bottom layer to the middle layer, the middle layer converts the communication information according to the connection attribute information and sends the converted communication information to the application layer according to the dynamic adaptation strategy. Because there may be incompatibility issues between the vehicle-mounted controller and the mobile device, an intermediate layer added to the controller can convert the communication information so that the converted communication information is in a form compatible with the protocol services supported by the vehicle-mounted controller or the mobile device. This solves the incompatibility problem between the vehicle-mounted controller and the mobile device, and improves the stability of the communication connection and the comprehensiveness of the functionality between the vehicle-mounted controller and the mobile device.

[0034] In some embodiments, determining the connectivity attribute information of the mobile device through the intermediate layer includes: The intermediate layer queries a preset device database to see if there is historical information corresponding to the mobile device. In response to the existence of the historical information, the historical information is used as the connection attribute information; In response to the absence of the historical information, an attribute test is performed on the mobile device to determine the connection attribute information of the mobile device. Specifically, a device database is pre-configured in the middle layer, storing historical information about mobile devices that have established wireless communication connections with the vehicle controller. This historical information can specifically include historical connection attribute information. If the current mobile device is not connecting to the vehicle controller for the first time, its historical information can be retrieved from the device database and directly used as connection attribute information. This eliminates the need for attribute testing to determine the current mobile device's connection attributes, thus improving the efficiency of mobile device adaptation.

[0035] If the device database does not contain historical information about the current mobile device, attribute testing is required. Attribute testing verifies the codecs and control command sets supported by the mobile device. Attribute testing accurately determines the mobile device's connectivity attributes, which is beneficial for subsequently assigning appropriate communication strategies to the mobile device, thereby improving the quality and stability of wireless communication between the vehicle controller and the mobile device.

[0036] In some embodiments, performing attribute testing on the mobile device to determine the connection attribute information of the mobile device includes: The mobile device supports information about the types of services it can access by querying the service discovery protocol. The control command set supported by the mobile device is tested by sending a test command set; The service type information and the control instruction set are used as the connection attribute information.

[0037] Specifically, existing service discovery protocols only query which protocols a mobile device supports, but do not explore the specific capabilities of the services supported by those protocols. For example, if the vehicle controller queries which protocols a mobile device supports, and the mobile device reports support for the A2DP protocol, the vehicle controller will not further query the list of audio codecs supported by the mobile device under the A2DP protocol.

[0038] However, in this application, the middleware layer sends a query to the mobile device according to the Service Discovery Protocol (SDP) to determine the service type information supported by the mobile device. The service type information includes not only the protocols supported by the mobile device (such as A2DP, HFP, etc.), but also the specific functional services under the protocol, which can be a list of codecs. For example, the vehicle controller sends query 1 to the mobile device to inquire about the protocol types supported by the mobile device. The mobile device replies to the vehicle controller that it supports the A2DP protocol. Then, the vehicle controller sends query 2 to the mobile device to inquire about the list of encoders supported by the A2DP protocol. The mobile device replies to the vehicle controller with the list of supported codecs. The codec list is usually arranged in descending order of audio quality. During communication between the mobile device and the vehicle controller, encoding or decoding according to the codecs with the earlier sequence numbers yields higher audio quality.

[0039] The test instruction set includes control instructions developed by most manufacturers when producing mobile devices. The vehicle-side controller sends test instructions from the test instruction set to each mobile device to inquire whether the mobile device supports the test instruction. If the device supports the test instruction, then the test instruction belongs to the control instructions supported by the mobile device. After all test instructions have been sent, the control instruction set supported by the mobile device is determined. Finally, the service type information and the control instruction set are used as connection attribute information. The connection attribute information determined in this embodiment can accurately describe the capability profile of the mobile device, providing the necessary and high-precision data foundation for subsequent dynamic adaptation strategy allocation, thus achieving accurate allocation of dynamic adaptation strategies.

[0040] In some embodiments, assigning a dynamic adaptation strategy to the mobile device based on the connection attribute information includes: Based on the connection attribute information, determine the audio track switching strategy, connection activity strategy, and resource allocation strategy of the mobile device respectively; The audio track switching strategy, the connection activity strategy, and the resource allocation strategy are used as the dynamic adaptation strategy.

[0041] Specifically, the dynamic adaptation strategy includes audio track switching strategy, connection activity strategy, and resource allocation strategy. The audio track switching strategy refers to the switching logic between different audio tracks, such as the switching logic between the call audio track and the audio playback track, or the switching logic between the audio playback track and the navigation prompt audio track. The connection attribute information includes the control command set supported by the mobile device. Based on the control commands supported by the mobile device, a customized audio track switching strategy can be created for the mobile device. For example, the switching logic from the audio playback track to the call audio track can be: the vehicle controller sends a "pause" audio playback control command to the mobile device → the vehicle controller waits 50ms → controls the speaker to play the audio track switched from the audio playback track to the call audio track → the ringing begins.

[0042] Connection activity strategies are used to combat wireless connection interruptions or stuttering caused by mobile device protocol versions, sleep mechanisms, and communication quality. Connection activity strategies include heartbeat strategies, sleep countermeasure strategies, and radio frequency adaptation strategies. Based on the protocol version in the connection attribute information, the risk of disconnection for the mobile device can be determined. If the protocol version is higher, the risk of disconnection is lower, and a low-power heartbeat strategy, such as sending a heartbeat signal every 7-10 seconds, can be assigned to the mobile device to maintain the wireless connection. If the protocol version is lower, the risk of disconnection is higher, and a higher-power heartbeat strategy, such as sending a heartbeat signal every 2-3 seconds, can be assigned to the mobile device to maintain the wireless connection.

[0043] The sleep mechanism of a mobile device can be determined based on the communication protocol in the connection attribute information; different mobile devices have different sleep mechanisms. If, after the mobile device goes into sleep mode, the sleep mechanism allows background tasks to run according to a preset mode without directly closing them, then the corresponding sleep countermeasure strategy could be to send status query commands to the mobile device at a low frequency to maintain the background tasks running stably according to the preset mode. If, after the mobile device goes into sleep mode, the sleep mechanism allows background tasks to close after running for a period of time, then the corresponding sleep countermeasure strategy could be to send status query commands to the mobile device at a high frequency to maintain the background tasks running stably according to the preset mode.

[0044] The RF adaptive strategy dynamically adjusts the transmit power of the signal transceiver modules based on the communication quality between the mobile device and the vehicle controller. If the communication quality is poor, the transmit power of the signal transceiver modules in both the vehicle controller and the mobile device is increased accordingly; if the communication quality is good, the transmit power of the signal transceiver modules in both the vehicle controller and the mobile device can be appropriately reduced to save power consumption.

[0045] Resource allocation strategies are used to allocate appropriate computing and memory resources to mobile devices. The vehicle controller dynamically allocates computing and memory resources to mobile devices based on the current communication information between the mobile device and the vehicle, as well as the controller's load. This avoids resource waste caused by allocating fixed computing and memory resources to mobile devices. If the current communication requires more computing and memory resources, more resources are allocated to the mobile device; conversely, if the current communication requires less resources, less resources are allocated, ultimately achieving the goal of rational resource allocation.

[0046] This embodiment achieves the goal of customizing personalized communication strategies for mobile devices by assigning dynamic adaptation strategies based on connection attribute information to the mobile device. The connection activity strategy ensures a stable wireless connection between the mobile device and the vehicle controller, while the resource allocation strategy rationally allocates vehicle-side resources to the mobile device, improving resource utilization. The audio track switching strategy enables effective switching between different audio tracks, avoiding functional conflicts under wireless communication and ensuring the effective execution of various functional services.

[0047] In some embodiments, the conversion of the communication information through the intermediate layer according to the connection attribute information includes: Determine the type of the communication information, and convert the communication information according to the type of the communication information.

[0048] Specifically, the intermediate layer uses different conversion methods for different types of communication information. Therefore, it is necessary to determine the type of communication information before conversion. Converting communication information according to its type ensures accurate conversion, enabling accurate communication between the vehicle controller and mobile devices even under hardware incompatibility.

[0049] In some embodiments, converting the communication information according to its type includes: In response to the fact that the type of the communication information is audio data, the current data format and the target data format of the audio data are determined; A decoder matching the current data format is determined from a pre-built codec library, and the audio data is decoded by the decoder to obtain standard audio data; The standard audio data is adjusted according to the target data format; An encoder matching the target data format is determined in the codec library, and the standard audio data with adjusted parameters is encoded using the encoder to obtain the target audio data.

[0050] Specifically, the codec library pre-stores multiple encoders and decoders to adapt to different mobile devices. For example, the codec library could be FFmpeg, an open-source, powerful collection of codecs that supports almost all audio and video formats. If the communication information is audio data, the current data format and target data format of the audio data are determined. The target data format is the format of the converted audio data. For example, if the audio data is sent by a mobile device, the target data format is the data format supported by the vehicle-side controller. The target data format can be the same as or different from the current data format. When the target data format is the same as the current data format, the intermediate layer can directly forward the audio data. When the target data format is different from the current data format, the intermediate layer needs to convert the audio data from the current data format to the target data format. For example, if the current data format of the audio data is LDAC (Low-latency Digital Audio Codec) and the target data format is SBC (Simple Bandwidth Coding), then the current data format is determined to be different from the target data format.

[0051] The codec library matches a decoder corresponding to the current data format. The decoder then uses a decompression algorithm to decompress the compressed audio data, outputting standard audio data. For example, standard audio data can be uncompressed PCM (Pulse-Code Modulation) data. Since the audio properties of the current data format and the target data format may differ, directly encoding the standard audio data may lead to errors or sound quality degradation. Therefore, before encoding the standard audio data, its parameters need to be adjusted. Adjusted parameters may include sampling rate, channels, and bit depth. For example, adjusting the 96kHz sampling rate of the standard audio data to 48kHz corresponding to the target data format, or downmixing the 5.1 channel standard audio data to stereo, or adjusting 24-bit standard audio data to 16-bit.

[0052] The encoder matching the target data format is determined in the codec library. The standard audio data, after parameter adjustments, is then encoded to obtain the target audio data. The encoder uses a compression algorithm to compress the standard audio data, resulting in the target audio data corresponding to the target data format. For example, after receiving the target audio data, the vehicle-side controller can decode it using its built-in hardware decoder and play it through the speaker.

[0053] It should be noted that the codec can be optimized using NEON. NEON is the SIMD (Single Instruction, Multiple Data) instruction set for ARM processors in vehicle-mounted controller chips. NEON allows a single instruction to perform the same operation on 128 bits of data simultaneously, achieving parallel computation of single instruction multiple data streams. Encoding and decoding algorithms deeply optimized with NEON can significantly improve encoding and decoding speed, enabling the process to be completed within 20ms, with no perceptible latency to the user.

[0054] This embodiment achieves the conversion of audio data, enabling normal audio playback control between the vehicle-mounted controller and mobile devices even when the codecs are incompatible. After audio data conversion, high-quality audio playback is achieved, providing users with a delay-free experience and significantly improving user satisfaction.

[0055] In some embodiments, converting the communication information according to its type includes: In response to the fact that the type of the communication information is a control instruction, the control instruction is converted into a target instruction according to a pre-built instruction mapping relationship.

[0056] Specifically, the instruction mapping relationship stores the mapping relationship between control instructions and target instructions in various formats. A unique target instruction can be found in the instruction mapping relationship through a control instruction. Control instructions may be non-standard AT instructions or manufacturer-defined AT instructions. Different mobile devices may use different AT instructions for the same control function. For example, a non-standard AT instruction requiring a mobile device to provide battery level feedback might be AT+XAPL or AT+CVENDOR. To enable the vehicle-side controller to understand control instructions sent by different mobile devices, or for different mobile devices to understand control instructions issued by the vehicle-side controller, the control instructions need to be converted in the middleware layer. The target instruction is the converted control instruction. The middleware layer encapsulates the target instruction according to a standard event format, forming a unified data structure, and then outputs the encapsulated target instruction. This can be done by sending the target instruction to the application layer through a unified data interface between the middleware layer and the application layer, or by sending the target instruction to the lower layer through the middleware layer, and then forwarding the target instruction to the mobile device through the lower layer.

[0057] The communication information conversion method in this embodiment enables the vehicle-mounted controller and mobile devices to correctly read communication information even when control commands are incompatible. This ensures that different mobile devices can perform their functional services normally when establishing a wireless communication connection with the vehicle-mounted controller. The application layer of the vehicle-mounted controller does not need to modify its code to adapt to different mobile devices, greatly improving front-end development efficiency.

[0058] In some embodiments, the method further includes: receiving device update information sent from the cloud; and updating the device database using the device update information.

[0059] Specifically, to ensure the vehicle-side controller can quickly adapt to more mobile devices, its device database needs to be updated in real time. This update is achieved through over-the-air (OTA) upgrades. The cloud collects multiple connection attribute information uploaded by different vehicles, summarizes, organizes, refines, and corrects this information, configuring the latest and universal connection attribute information for each mobile device. If the connection attribute information maintained by the cloud is updated, the cloud sends the updated device information to the vehicle-side controller via OTA, enabling the controller to update its own device database to match different mobile devices.

[0060] Meanwhile, the vehicle controller can also transmit the dynamic adaptation strategy determined based on connection attribute information to the cloud for associated storage. The cloud can then select the optimal dynamic adaptation strategy for each mobile device from different dynamic adaptation strategies and recommend it to the vehicle controller. In this way, when assigning dynamic adaptation strategies to mobile devices, the vehicle controller can directly select from the recommended dynamic adaptation strategies issued by the cloud, without the need for real-time matching calculations, thereby reducing the resource consumption of the vehicle.

[0061] The continuous updating of the device database in this embodiment facilitates the establishment of a stable and smooth wireless communication connection between mobile devices and the vehicle controller. By continuously updating the device database, the vehicle controller can adapt to different mobile devices, reducing its development cycle and cost. Users can also continuously utilize the stable wireless communication connection between their mobile devices and the vehicle controller while using the vehicle, resulting in a better user experience.

[0062] It should be noted that the method in this embodiment can be executed by a single device, such as a computer or server. The method can also be applied in a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method in this embodiment, and the multiple devices will interact with each other to complete the method described.

[0063] It should be noted that some embodiments of this application have been described above. In some cases, the actions or steps described in the above embodiments can be performed in a different order than that shown in the above embodiments and the desired result can still be achieved. In addition, the processes depicted in the accompanying drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0064] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a vehicle controller.

[0065] refer to Figure 2 The vehicle controller includes: The bottom layer is configured to establish a wireless communication connection with the mobile device in response to receiving a wireless communication connection request from the mobile device; and to forward the communication information to the middle layer in response to receiving communication information. The middle layer includes a device detection module, a dynamic adaptation engine, an information conversion engine, and an interface module; The device detection module, connected to the underlying layer, is configured to determine the connection attribute information of the mobile device; A dynamic adaptation engine, connected to the device detection module, is configured to assign a dynamic adaptation strategy to the mobile device based on the connection attribute information. An information conversion engine, connected to the device detection module, is configured to convert communication information according to the connection attribute information; The interface module is connected to the dynamic adaptation engine and the information conversion engine respectively, and is configured to provide a standardized interface for the application layer. The application layer, connected to the interface module, is configured to forward the communication information to the middle layer in response to receiving the communication information.

[0066] Specifically, the vehicle controller comprises a hardware layer and a software layer. The controller hardware layer includes a wireless communication module, audio codec hardware, and a CPU / DSP chip. The controller software layer, from bottom to top, includes a bottom layer, a middle layer, and an application layer. The bottom layer includes a wireless communication protocol stack and a cloud service module. Mobile devices establish a basic wireless data channel with the vehicle controller through the wireless communication module in the controller hardware layer. The controller hardware layer sends wireless communication signals to the bottom layer, where the wireless communication protocol stack engages in a series of standard dialogues with the mobile device based on the wireless communication signals, establishing a logically reliable and encrypted communication link to complete the wireless communication connection. The audio codec hardware in the vehicle hardware layer can decode or encode audio, and the CPU / DSP chip provides computing power support for various modules in the vehicle controller software. The cloud service module in the bottom layer can establish a communication connection with the cloud to update the device database and dynamic adaptation strategies stored on the vehicle.

[0067] The middle layer includes a device detection module, a dynamic adaptation engine, an information conversion engine, and an interface module. The device detection module communicates with the underlying layer. It obtains wireless communication connection requests forwarded by the underlying layer, thereby determining the connection attribute information of mobile devices. The device detection module includes a device database, a query unit, and a command testing unit. The device database stores connection attribute information for different mobile devices, enabling the vehicle controller to quickly query this information. The query unit sends query statements to the mobile device to determine its service type information, and the command testing unit sends test commands to the mobile device to test the control command set it supports. The device detection module communicates with both the dynamic adaptation engine and the information conversion engine. The dynamic adaptation engine determines the dynamic adaptation strategy based on the connection attribute information, including audio track switching, connection activity, and resource allocation strategies. The information conversion engine converts communication information, including a codec library, an audio transcoding bridge, and a command mapper. The audio transcoding bridge converts audio data, and the command mapper converts control commands. The interface module communicates with both the dynamic adaptation engine and the information conversion engine, providing a unified, standardized interface for the application layer. These standardized interfaces include a device status query interface, an audio control interface, and an event notification interface. Through the device status query interface, the vehicle controller can query the status of mobile devices. The audio control interface enables audio control with mobile devices, and the event notification interface allows for event subscription with mobile devices. The application layer includes a UI interface, a call module, and a media playback module. The UI interface provides a human-computer interaction channel and includes call and media playback modules. Users can use these modules to output communication information and control mobile devices.

[0068] The aforementioned vehicle controller establishes a wireless connection channel between the vehicle controller and the mobile device, enabling bidirectional control. Due to incompatibility issues between the vehicle controller and the mobile device, an intermediate layer added to the controller converts the communication information, ensuring the converted information is compatible with the services supported by either the vehicle controller or the mobile device. This avoids the incompatibility problem and improves the stability and comprehensiveness of the communication connection between the vehicle controller and the mobile device.

[0069] In some embodiments, the device detection module is configured to query a preset device database through the intermediate layer to see if there is historical information corresponding to the mobile device; in response to the existence of the historical information, to use the historical information as the connection attribute information; and in response to the absence of the historical information, to perform attribute testing on the mobile device to determine the connection attribute information of the mobile device. In some embodiments, the device detection module is configured to query service type information supported by the mobile device through a service discovery protocol; test the control command set supported by the mobile device by sending a test command set; and use the service type information and the control command set as the connection attribute information.

[0070] In some embodiments, the dynamic adaptation engine is configured to determine the audio track switching strategy, connection activity strategy, and resource allocation strategy of the mobile device based on the connection attribute information; and to use the audio track switching strategy, the connection activity strategy, and the resource allocation strategy as the dynamic adaptation strategy.

[0071] In some embodiments, the information conversion engine is configured to determine the type of the communication information and convert the communication information according to the type of the communication information.

[0072] In some embodiments, the information conversion engine is configured to determine the current data format and target data format of the audio data in response to the type of the communication information being audio data; A decoder matching the current data format is determined from a pre-built codec library, and the audio data is decoded by the decoder to obtain standard audio data; The standard audio data is adjusted according to the target data format; An encoder matching the target data format is determined in the codec library, and the standard audio data with adjusted parameters is encoded using the encoder to obtain the target audio data.

[0073] In some embodiments, the information conversion engine is configured to convert the control instruction into a target instruction according to a pre-built instruction mapping relationship in response to the type of the communication information being a control instruction.

[0074] In some embodiments, the underlying layer is configured to receive device update information sent from the cloud; the device detection module is configured to update the device database using the device update information.

[0075] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing this application, the functions of each module can be implemented in one or more software and / or hardware.

[0076] The apparatus of the above embodiments is used to implement the corresponding vehicle wireless communication method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0077] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle wireless communication method described in any of the above embodiments.

[0078] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a vehicle, including the vehicle controller described in any embodiment.

[0079] Figure 3 This embodiment illustrates a more specific hardware structure of an electronic device. The device may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.

[0080] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0081] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

[0082] The input / output interface 1030 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0083] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0084] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.

[0085] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0086] The electronic devices described above are used to implement the corresponding vehicle wireless communication methods in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0087] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the vehicle wireless communication method as described in any of the above embodiments.

[0088] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0089] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the vehicle wireless communication method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0090] Based on the same concept, corresponding to any of the above embodiments, this application also provides a computer program product, including computer program instructions, which, when run on a computer, cause the computer to perform the method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0091] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this application is limited to these examples; under the concept of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this application as described above, which are not provided in detail for the sake of brevity.

[0092] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this application, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this application, and this also takes into account the fact that the details of the implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this application will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuits) have been set forth to describe exemplary embodiments of this application, it will be apparent to those skilled in the art that the embodiments of this application can be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0093] Although this application has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0094] The embodiments of this application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of this application. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this application should be included within the protection scope of this application.

Claims

1. A vehicle wireless communication method characterized by, The method is applied to a vehicle controller, and a software hierarchical architecture of the vehicle controller comprises a bottom layer, a middle layer and an application layer, and the method comprises the following steps: In response to receiving a wireless communication connection request of a mobile device, establishing a wireless communication connection with the mobile device through the bottom layer; Determining connection attribute information of the mobile device through the middle layer, and assigning a dynamic adaptation strategy to the mobile device according to the connection attribute information; In response to receiving communication information sent by the application layer to the middle layer, converting the communication information according to the connection attribute information through the middle layer, and sending the converted communication information to the bottom layer according to the dynamic adaptation strategy; or, in response to receiving communication information sent by the bottom layer to the middle layer, converting the communication information according to the connection attribute information through the middle layer, and sending the converted communication information to the application layer according to the dynamic adaptation strategy.

2. The method of claim 1, wherein, The method comprises the following steps: Querying whether there is historical information corresponding to the mobile device in a preset device database through the middle layer; In response to the historical information, taking the historical information as the connection attribute information; In response to the absence of the historical information, performing attribute testing on the mobile device to determine the connection attribute information of the mobile device.

3. The method of claim 2, wherein, The method comprises the following steps: Querying service type information supported by the mobile device through a service discovery protocol; Testing a control instruction set supported by the mobile device through a test instruction set; Taking the service type information and the control instruction set as the connection attribute information.

4. The method of claim 1, wherein, The method comprises the following steps: According to the connection attribute information, determining an audio track switching strategy, a connection active strategy and a resource allocation strategy of the mobile device respectively; Taking the audio track switching strategy, the connection active strategy and the resource allocation strategy as the dynamic adaptation strategy.

5. The method of claim 1, wherein, The method comprises the following steps: Determining the type of the communication information, and converting the communication information according to the type of the communication information.

6. The method of claim 5, wherein, The method comprises the following steps: In response to the type of the communication information being audio data, determining a current data format and a target data format of the audio data; Determining a decoder matched with the current data format in a pre-constructed codec library, decoding the audio data through the decoder to obtain standard audio data; According to the target data format, adjusting parameters of the standard audio data; Determining an encoder matched with the target data format in the codec library, and encoding the standard audio data with adjusted parameters through the encoder to obtain target audio data.

7. The method of claim 5, wherein, The method comprises the following steps: In response to the type of the communication information being a control instruction, the control instruction is converted into a target instruction according to a pre-constructed instruction mapping relationship.

8. The method of claim 2, wherein, The method further includes: receiving device update information issued by a cloud; updating the device database according to the device update information.

9. A vehicle controller characterized by comprising: comprise: a bottom layer configured to establish a wireless communication connection with a mobile device in response to receiving a wireless communication connection request of the mobile device; in response to receiving communication information, forwarding the communication information to an intermediate layer; the intermediate layer comprises a device detection module, a dynamic adaptation engine, an information conversion engine and an interface module; the device detection module is connected with the bottom layer and is configured to determine connection attribute information of the mobile device; the dynamic adaptation engine is connected with the device detection module and is configured to assign a dynamic adaptation strategy to the mobile device according to the connection attribute information; the information conversion engine is connected with the device detection module and is configured to convert communication information according to the connection attribute information; the interface module is connected with the dynamic adaptation engine and the information conversion engine respectively and is configured to provide a standardized interface for the application layer; the application layer is connected with the interface module and is configured to forward the communication information to the intermediate layer in response to receiving the communication information.

10. A vehicle characterized by comprising: The vehicle comprises the vehicle controller according to claim 9.

Images