Vehicle and equipment interconnection method and device, equipment, medium and vehicle

Abstract

The invention relates to a vehicle and equipment interconnection method and device, equipment, a medium and a vehicle, and particularly relates to the technical field of vehicles. Comprising the steps that a vehicle terminal authenticates target equipment according to equipment information broadcasted by the target equipment; selecting a target communication protocol from the communication protocol set under the condition that the authentication of the target equipment is passed; establishing a communication link between the vehicle terminal and the target equipment based on the target communication protocol; and sending the service data to the target device through the communication link, and / or receiving the service data sent by the target device through the communication link. The embodiment of the invention is used for solving the problems of complex business development process and slow landing progress of the existing vehicle terminal and other equipment.

Description

Technical Field

[0001] This disclosure relates to the field of vehicle technology, and more particularly to a method, apparatus, device, medium, and vehicle for interconnecting vehicles and devices. Background Technology

[0002] Intelligent vehicles have become crucial players in the Internet of Things, making the interconnection between vehicles, people, and things increasingly important. Currently, in solutions for connecting in-vehicle terminals to other devices, various protocols and interfaces have been customized to achieve different business functions, such as screen projection protocols, data transfer protocols, and vehicle control protocols. When developing new services, it is also necessary to pay attention to the underlying connection technologies of the new services and re-customize protocols and interfaces. This leads to complex development processes, slow implementation progress, and poor scalability and compatibility of this targeted customization method. Therefore, there is an urgent need in this field for a simple and efficient method to achieve vehicle-to-device interconnection. Summary of the Invention

[0003] To solve the above-mentioned technical problems, or at least partially solve them, this disclosure provides a method, apparatus, device, medium, and vehicle for interconnecting vehicles and equipment, which can simply and efficiently realize the interconnection of vehicles with other equipment.

[0004] To achieve the above objectives, the technical solutions provided by the embodiments of this disclosure are as follows:

[0005] In a first aspect, this disclosure provides a method for interconnecting a vehicle and a device, comprising:

[0006] The vehicle terminal authenticates the target device based on the device information broadcast by the target device; the device information includes the device type and the callable services, which are obtained by abstracting the hardware capabilities of the target device;

[0007] If the target device passes authentication, the target communication protocol is selected from the set of communication protocols;

[0008] Establish a communication link between the vehicle terminal and the target device based on the target communication protocol;

[0009] Sending service data to the target device via the communication link, and / or receiving service data sent by the target device via the communication link.

[0010] As an optional implementation of this disclosure, before authenticating the target device based on the device information broadcast by the target device, the method further includes: scanning the soft bus to obtain device information to be processed; the device information to be processed includes the account information of the device to be processed; verifying whether the account information matches the account information corresponding to the vehicle terminal; if so, storing the device information to be processed in the device list.

[0011] As an optional implementation of this disclosure, if the target device is successfully authenticated, selecting a target communication protocol from the communication protocol set includes: obtaining a service type if the target device is successfully authenticated; and selecting a target communication protocol from the communication protocol set according to the service type.

[0012] As an optional implementation of this disclosure, selecting a target communication protocol from a set of communication protocols according to the service type includes: determining a communication protocol strongly associated with the service type as the target communication protocol from the set of communication protocols.

[0013] As an optional implementation of this disclosure, the service type includes at least one of screen projection or collaboration service, file transfer service, and vehicle control notification service; different service types correspond to different service data interaction methods, wherein the service data interaction method corresponding to screen projection or collaboration service is video streaming, the service data interaction method corresponding to file transfer service is file streaming, and the service data interaction method corresponding to vehicle control notification service is message transfer; determining a communication protocol strongly associated with the service type as the target communication protocol from the communication protocol set includes: if the service type is screen projection or collaboration service, then selecting a communication protocol strongly associated with video streaming from the communication protocol set as the target communication protocol; if the service type is file transfer service, then selecting a communication protocol strongly associated with file streaming from the communication protocol set as the target communication protocol; if the service type is vehicle control notification service, then selecting a communication protocol strongly associated with message transfer from the communication protocol set as the target communication protocol.

[0014] As an optional implementation of this disclosure, establishing a communication link between the vehicle terminal and the target device based on the target communication protocol includes: monitoring the connection status of the target device; and adjusting the connection parameters based on network conditions and communication load to re-establish the communication link between the vehicle terminal and the target device when the connection status indicates an abnormal connection.

[0015] Secondly, this disclosure provides a device for interconnecting a vehicle and a device, the device comprising:

[0016] The authentication module is used to authenticate the target device based on the device information broadcast by the target device. The device information includes the device type and callable services. The callable services are obtained by abstracting the hardware capabilities of the target device.

[0017] The selection module is used to select a target communication protocol from the set of communication protocols if the target device is successfully authenticated.

[0018] The communication module is used to establish a communication link between the vehicle terminal and the target device based on the target communication protocol; to send service data to the target device through the communication link, and / or to receive service data sent by the target device through the communication link.

[0019] As an optional implementation of this disclosure, the authentication module, before authenticating the target device based on the device information broadcast by the target device, is further configured to: scan the soft bus to obtain device information to be processed; the device information to be processed includes the account information of the device to be processed; verify whether the account information matches the account information corresponding to the vehicle terminal; if so, store the device information to be processed in the device list.

[0020] As an optional implementation of this disclosure, the selection module is specifically used for: obtaining the service type when the target device is authenticated; and selecting a target communication protocol from the communication protocol set according to the service type.

[0021] As an optional implementation of this disclosure, the selection module is specifically used to: determine, from the set of communication protocols, a communication protocol strongly associated with the service type as the target communication protocol.

[0022] As an optional implementation of this disclosure, the service type includes at least one of screen projection or collaboration service, file transfer service and vehicle control notification service; different service types correspond to different service data interaction methods, wherein the service data interaction method corresponding to screen projection or collaboration service is video streaming, the service data interaction method corresponding to file transfer service is file streaming, and the service data interaction method corresponding to vehicle control notification service is message transfer.

[0023] The selection module is specifically used for: if the business type is screen projection or collaborative business, then selecting a communication protocol strongly associated with video streaming from the communication protocol set as the target communication protocol; if the business type is file transfer business, then selecting a communication protocol strongly associated with file streaming from the communication protocol set as the target communication protocol; if the business type is vehicle control notification business, then selecting a communication protocol strongly associated with message transfer from the communication protocol set as the target communication protocol.

[0024] Thirdly, this disclosure provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the vehicle-to-device interconnection method as described in the first aspect or any alternative embodiment thereof.

[0025] Fourthly, this disclosure provides a computer-readable storage medium, comprising: storing a computer program on the computer-readable storage medium, wherein the computer program, when executed by a processor, implements the vehicle-to-device interconnection method as described in the first aspect or any alternative embodiment thereof.

[0026] Fifthly, this disclosure provides a vehicle, including: a vehicle-to-device interconnection device as described in the second aspect or any alternative embodiment thereof, or an electronic device as described in the third aspect.

[0027] In a sixth aspect, this disclosure provides a computer program product comprising: a computer program that, when run on a computer, causes the computer to implement the vehicle-to-device interconnection method as described in the first aspect or any alternative embodiment thereof.

[0028] The technical solution provided in this disclosure has the following advantages compared with the prior art:

[0029] This disclosure provides a method, apparatus, device, medium, and vehicle for vehicle-to-device interconnection. The method first involves an in-vehicle terminal authenticating a target device based on device information broadcast by the target device. If the target device is successfully authenticated, a target communication protocol is selected from a set of communication protocols. Then, a communication link is established between the in-vehicle terminal and the target device based on the target communication protocol, thereby exchanging service data with the target device through this communication link. Thus, this disclosure integrates a unified communication protocol between the in-vehicle terminal and other devices, eliminating the need to customize protocols based on underlying connection technologies during service development. This allows for efficient connection, transmission channel establishment, and service data transmission between different devices, making it suitable for various vehicle-to-device interconnection scenarios and improving the scalability and compatibility of vehicle-to-device interconnection. Attached Figure Description

[0030] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0031] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without creative effort.

[0032] Figure 1A A schematic diagram of the system framework provided for an embodiment of this disclosure;

[0033] Figure 1B System framework illustration provided for embodiments of this disclosure Figure 2 ;

[0034] Figure 2 This is a schematic flowchart illustrating a method for interconnecting a vehicle and a device according to an embodiment of the present disclosure.

[0035] Figure 3 An apparatus for vehicle-to-device interconnection provided in an embodiment of this disclosure;

[0036] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure. Detailed Implementation

[0037] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the technical terms used in the description of the embodiments or the prior art will be briefly introduced below:

[0038] A software bus is a software architecture that provides services for multiple and various types of components written in multiple computer languages. This set of virtual data transmission lines serves as an interface for a set of common standard components and is also a set of standard software modules. The software bus is a virtual common channel and interface for data transmission and communication between the computer operating system and various components, or between components themselves. It is a virtualization and mapping of the hardware bus, designed to ensure the standardization of the construction process and the reliability, applicability, and scalability of the system in application.

[0039] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0040] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0041] To address some or all of the technical problems existing in related technologies, embodiments of this disclosure provide a method, apparatus, device, medium, and vehicle for vehicle-to-device interconnection. The method first involves an in-vehicle terminal authenticating a target device based on device information broadcast by the target device. If the target device is successfully authenticated, a target communication protocol is selected from a set of communication protocols. Then, a communication link is established between the in-vehicle terminal and the target device based on the target communication protocol, thereby exchanging service data with the target device through this communication link. Thus, embodiments of this disclosure integrate a unified communication protocol between vehicles and devices, eliminating the need to customize protocols based on underlying connection technologies during service development. This allows vehicles to efficiently connect with different devices, establish transmission channels, and transmit service data, making it suitable for various vehicle-to-device interconnection scenarios and improving the scalability and compatibility of vehicle-to-device interconnection.

[0042] like Figure 1A As shown, Figure 1AThe system framework diagram provided in this embodiment of the disclosure is shown in Figure 1. The illustrated system includes: a service layer, a soft bus, a bus layer, and a device layer. The soft bus includes an interface layer and a management layer. The service layer can initiate services such as near-field device interconnection and inter-domain device interconnection. Near-field device interconnection services include vehicle-to-everything (V2X) interconnection with a mobile phone, while inter-domain device interconnection services include interconnection between the intelligent cockpit control domain (HU) and the central domain controller (XCU). The interface layer is the soft bus software development kit (SDK), specifically including device interconnection interfaces, etc.

[0043] The management layer comprises: a device registration module, a device discovery module, a device authentication module, and a connection management module. The device registration module is responsible for securely and efficiently adding new device information to the soft bus, ensuring the vehicle terminal can be recognized by other devices; quickly entering device information through a simple registration process; automatically verifying the accuracy and completeness of device information; and updating device status in real time. The device discovery module is responsible for real-time detection and identification of devices on the bus, displaying connection possibilities between devices to facilitate rapid interconnection; quickly scanning device information on the soft bus to intelligently match connectable devices based on device type, function, and services; and updating the device list on the soft bus to display the latest device status and services. The device authentication module is responsible for verifying the identity and permissions of devices, ensuring the security and reliability of communication between devices; verifying device identity information to ensure the accuracy of device identity; reviewing device access permissions; and encrypting communication data between devices. The connection management module is responsible for establishing, managing, and optimizing communication connections between devices, ensuring efficient and stable data transmission between devices; monitoring connection status in real time to ensure the stability and reliability of data transmission; and adjusting connection parameters according to network conditions and communication load to optimize transmission efficiency.

[0044] The bus layer includes communication buses such as Bluetooth (BT), Wireless Local Area Network (WIFI), 5th Generation Mobile Communication Technology (5G), Near Field Communication (NFC), Ultra Wideband (UWB), Serial Peripheral Interface (SPI), Controller Area Network (CAN), and Universal Asynchronous Receiver / Transmitter (UART), etc.

[0045] The device layer includes mobile phones, watches, in-vehicle systems, smart peripherals, computing boxes, cloud servers, and other devices.

[0046] refer to Figure 1A The system framework shown describes a method for vehicle-to-device (V2D) interconnection. First, the management layer discovers target devices and authenticates them based on the device information broadcast by the target device. Then, if the target device is successfully authenticated, a target communication protocol is selected from a set of communication protocols to establish a communication link between the vehicle terminal and the target device. This communication link is a type of communication bus in the bus layer. Further, the communication link enables the sending and receiving of service data between the vehicle terminal and the target device. Thus, the device discovery module in the management layer efficiently detects target devices, and the device authentication module verifies the device's identity and permissions to ensure the security and reliability of the interconnection between the vehicle terminal and other devices. The connection management module establishes communication links between devices to ensure efficient and stable transmission of service data between the vehicle terminal and the devices. This enables simple and efficient interconnection and communication between cross-devices on a soft bus.

[0047] like Figure 1B As shown, Figure 1B System framework illustration provided for embodiments of this disclosure Figure 2 The illustrated system comprises: a business layer, a soft bus, a system layer, and a link layer. The soft bus includes an interface layer, a management layer, a protocol layer, and part of the system layer. The business layer can initiate intra-domain interconnection, inter-domain interconnection, inter-core interconnection, and inter-device interconnection services. Intra-domain interconnection services include interconnection between the HU and a Microcontroller Unit (MCU); inter-domain interconnection includes interconnection between the HU, XCU, and the Full Self-Drive (FSD) domain; inter-core interconnection includes interconnection between the A-core and M-core; and inter-device interconnection includes interconnection between the HU and peripherals such as mobile phones. The interface layer is the soft bus SDK, including device interconnection interfaces, service call interfaces, and data transmission interfaces. The soft bus SDK provides interfaces for application software (APP) access. APPs can easily develop interconnection functions by calling the interfaces of this module. Furthermore, the interface definitions follow the Service-Oriented Architecture (SOA) principle, are standardized and service-oriented, provide multi-language support, and facilitate APP access on different systems.

[0048] The management layer includes: a near-field sensing module, a device management module, a service management module, a connection management module, and a transmission management module. The near-field sensing module comprises a sensing submodule, a discovery submodule, a networking submodule, and a broadcast submodule. The near-field sensing module enables mutual awareness among near-field devices, allowing devices to identify each other by calling broadcast and discovery interfaces. For example, device A can broadcast its local device type, supported services, and hardware capabilities. Device B's near-field sensing module receives this information, identifies and analyzes it, and distributes the information to the device management or service management module.

[0049] The device management module includes a registration submodule, a storage submodule, and a device connection submodule. It records near-field devices discovered by the near-field perception module and supports static device registration. For example, different domain controllers in the vehicle's infotainment system can be registered and loaded through configuration files. Ultimately, this module stores inter-domain devices, near-field devices, cloud devices, etc., for the app to perform device search, device connection, and so on.

[0050] The service management module includes: an add submodule, a search submodule, a service connection submodule, and a broadcast submodule. This module records the service capabilities of near-field devices discovered by the near-field perception module. It supports adding and searching for services. Local apps can register local services with this module; specifically, they register callable services as local services. The service management module then broadcasts these callable services through the broadcast submodule. These callable services are derived from the system layer's abstraction of local hardware functions. Local hardware capabilities are abstractable and concrete hardware capabilities obtained after identifying the inherent capabilities of local hardware. Upper-layer apps can call the service management module's interface to develop the service capabilities of peripheral devices. For example, if an app discovers a camera service on a nearby device, it can find both local and remote camera services (e.g., a car infotainment system discovering a phone's camera). After discovering a service, further service connections and capability calls can be implemented.

[0051] The connection management module includes: a connection establishment / disconnection submodule, a link multiplexing submodule, a logical connection submodule, and a physical connection submodule. The connection management module is used to establish and destroy connection channels between devices. A pair of APP connections corresponds to one logical connection, and a connection between two devices corresponds to one physical connection. It supports the multiplexing of physical connections between two devices.

[0052] The transmission management module includes a load balancing submodule, a Quality of Service (QoS) submodule, and a data encapsulation and parsing submodule. This module is responsible for establishing and maintaining transmission channels between devices, as well as sending and receiving data. It needs to provide different transmission capabilities, such as message transmission, streaming transmission, and file transmission, to support various communication needs. Simultaneously, this module supports QoS and load balancing capabilities, enabling reliable data transmission, priority scheduling, and multiplexing.

[0053] The protocol layer includes: a loading and arbitration submodule, a protocol aggregation and abstraction submodule, and a communication protocol set. The loading and arbitration submodule is used for selecting and arbitrating the transmission protocol between devices. For example, two devices may support multiple communication protocols; in this case, this module performs protocol optimization and feeds the result back to the transmission management module, which then uses the corresponding protocol to establish a transmission channel. The communication protocol set includes, but is not limited to: Generic Attribute Profile (GATT), Ultra Wideband (UWB) Protocol, Remote Procedure Call (RPC), Data Distribution Service (DDS), Message Queuing Telemetry Transport (MQTT), and Quick UDP Internet Connection (QUIC).

[0054] The system layer includes: a hardware capability abstraction module, a driver layer, and interfaces for Android, Linux, FreeEtos, QNX, and Windows. The hardware capability abstraction module abstracts various hardware capabilities, defining a unified API. It identifies the inherent hardware capabilities required by the system, determining which abstractable and concrete hardware capabilities the system possesses. Examples include video display capabilities, file reception capabilities, Wi-Fi, screens, and cameras. By simulating these capabilities, developers can access and debug the relevant hardware. The hardware capability abstraction module interfaces upwards with the transmission management module and downwards with different driver layers, allowing the driver layers to implement specific transmission capabilities. This module facilitates the interface between the framework and hardware capabilities.

[0055] The link layer includes: BLE, UART, CAN, SPI, UWB, WIFI, Local Interconnect Network (LIN), Processor Controlled Interrupt Controller (PCIE), and Ethernet (ETH).

[0056] refer to Figure 1B The system framework shown describes a method for vehicle-to-device (V2D) interconnection. First, the device management module authenticates the target device based on its broadcast device information. If authentication is successful, the loading and arbitration submodules at the protocol layer select a target communication protocol from a set of communication protocols. Then, based on the target communication protocol, the connection management module establishes a communication link and corresponding transmission channel between the vehicle terminal and the target device. Finally, the transmission management module sends and / or receives service data from the target device through the corresponding transmission channel. This constructs an interconnection framework from sensing to connection to data transmission, with unified and integrated communication protocols. During interconnection, the target communication protocol is selected based on specific business needs, allowing upper-layer services to focus on business development without needing to concern themselves with the underlying connection logic.

[0057] Based on the aforementioned system framework, this disclosure enables mutual sensing, connection establishment, and data transmission between devices, making it suitable for a wide range of interconnected scenarios. In particular, it enables efficient authentication, connection, and data transmission between the vehicle terminal and different devices, and upper-layer services do not need to concern themselves with the underlying connection technology, allowing them to focus on business development, thereby enabling interconnection between the vehicle terminal and peripheral devices or cloud servers.

[0058] This disclosure provides a method for vehicle-to-device interconnection, which can be implemented through a vehicle-to-device interconnection device or electronic device. The electronic device includes, but is not limited to, in-vehicle terminals, servers, personal computers, laptops, tablets, smartphones, and watches. The operating system of the electronic device may include Android, Apple's iOS, Microsoft's Windows operating system, etc., and this disclosure does not limit this. The electronic device can operate independently to implement this disclosure, or it can connect to a network and implement this disclosure through interaction with other computer devices on the network. The network where the electronic device is located includes, but is not limited to, the Internet, wide area networks (WANs), metropolitan area networks (MANs), local area networks (LANs), and virtual private networks (VPNs).

[0059] It should be noted that the scope of protection of the method for interconnecting vehicles and devices described in this disclosure is not limited to the order of steps listed in this embodiment. Any solution implemented by adding, subtracting, or replacing steps in the prior art based on the principles of this disclosure is included within the scope of protection of this disclosure.

[0060] like Figure 2 As shown, Figure 2 This is a flowchart illustrating a method for vehicle-to-device interconnection according to an embodiment of the present disclosure. This method can be executed by a vehicle-to-device interconnection device, which can be implemented in software and / or hardware, and is generally integrated into an electronic device. Figure 2 As shown, the method mainly includes the following steps S201 to S204:

[0061] S201. The vehicle terminal authenticates the target device based on the device information broadcast by the target device.

[0062] The target device can be a near-field device of the vehicle's infotainment system, and it will broadcast its own device information. The broadcast device information may include at least one of the following: device type and callable services. The callable services are abstractions of the target device's hardware capabilities. The target device can abstract its own hardware capabilities into callable services and broadcast them on the soft bus, allowing other devices to scan the soft bus and capture the target device's callable services. The broadcast device information may also include hardware information.

[0063] In some embodiments, the soft bus is scanned in real time to obtain device information broadcast by the target device on the soft bus, thereby reducing the latency of target device discovery.

[0064] Specifically, the vehicle-mounted terminal can use the FindDevice interface to discover near-field devices via Bluetooth or online advertisements, or it can use near-field sensing technology to detect networked near-field devices. After discovering a near-field device, the terminal can match the device it can connect to as a target device based on the device type, functions, and services provided by the near-field device, and further obtain the target device's device information. This intelligent matching of target devices is beneficial for business implementation.

[0065] In some embodiments, before executing step S201, the soft bus is scanned to obtain information about the device to be processed, including the account information of the device to be processed; the account information is verified to match the account information corresponding to the vehicle terminal; if so, the information about the device to be processed is stored in the device list. The information about the device to be processed refers to the device information of the near-field devices of the vehicle terminal, and there can be multiple such devices.

[0066] Specifically, the system scans the soft bus to detect near-field devices around the vehicle terminal in real time, acquiring the device information broadcast by these near-field devices on the soft bus, including the account information of the near-field devices, which is the account information logged in on the near-field devices. Then, it performs a simple registration of the device information to be processed, records the basic information of these near-field devices, and verifies the device information to be processed, verifying whether the account information of the near-field devices matches the account information logged in on the vehicle terminal to verify the accuracy and completeness of the device information to be processed. If the verification is successful, it means that the device information of the near-field devices is accurate and complete, and the device information to be processed is stored in the device list to achieve rapid authentication in subsequent device interconnection processes and reduce the waiting time for device access.

[0067] In other embodiments, after scanning and obtaining the device information to be processed on the soft bus, the device pairing database stored on the vehicle terminal is retrieved. This database stores device information between the vehicle terminal and paired devices. The database is traversed to check if it contains the information of the device to be processed. If yes, it means the device to be processed and the vehicle terminal have already been paired, and the verification is successful; if no, it means the device to be processed and the vehicle terminal have not been paired before, and the vehicle terminal can attempt to pair with the device to be processed. If pairing is successful, the verification is successful. After successful verification, the device information to be processed is stored in the device list. The accuracy and completeness of the device information to be processed are verified by using the paired device information stored on the vehicle terminal, so as to achieve rapid authentication in subsequent device interconnection processes.

[0068] In some embodiments, based on the above embodiments, the target device is authenticated according to the device information broadcast by the target device, including: checking whether the device information is included in the device list; if the device information is included in the device list, determining that the target device has passed authentication.

[0069] Specifically, the system checks a pre-created device list to see if the target device's broadcast device information is included, to determine if the target device's device information has been recorded and verified. If the device information is included in the device list, the target device's authentication is confirmed. Conversely, if the target device's broadcast device information is not included in the device list, it indicates the target device is a new device. In this case, the target device's device information is recorded and verified. If verification is successful, the broadcast device information is stored in the device list to remember the target device, enabling subsequent quick connections without registration.

[0070] S202. If the target device is successfully authenticated, select the target communication protocol from the set of communication protocols.

[0071] The communication protocol set includes multiple communication protocols, and optionally, the communication protocol set includes at least one of the following: intra-core communication protocol, inter-core communication protocol, intra-domain communication protocol, inter-domain communication protocol, inter-device communication protocol, and cloud communication protocol.

[0072] The kernel communication protocols include: inter-process communication protocol (binder), message stack communication protocol (Dbus), and Unix socket communication protocol (Unix Socket);

[0073] Inter-core communication includes: shared memory, Remote Processor Messaging (RPMSG) protocol for communication design in multiprocessor systems, and PCIe high-speed communication;

[0074] Intra-domain communication protocols include: wired network communication protocol, UART communication protocol, SPI communication protocol, and USB communication protocol;

[0075] Inter-domain communication protocols include: wired network communication protocol, CAN communication protocol, LIN, and USB communication protocol;

[0076] Inter-device communication protocols include: wireless network communication protocols, wired network communication protocols, Bluetooth communication protocols, WIFI communication, UWB communication, and USB communication; and may also include: BT, 5G, NFC, SPI, CAN, and UART.

[0077] Cloud communication protocols include: traditional network communication and vehicle-to-everything communication (V2X).

[0078] In some embodiments, if the target device is successfully authenticated, the service type is first obtained, and the target communication protocol is selected from the set of communication protocols based on the service type.

[0079] It should be noted that device interconnection services include, but are not limited to, the following: seamless interconnection, screen mirroring, QR code screen mirroring, cross-device interconnection (DLNA) screen mirroring, Bluetooth audio, smart keys, human body detection, peripheral device vehicle control, file sharing, video projection, vehicle-home interconnection, end-to-cloud interconnection, hardware collaboration, computing power sharing, etc. Correspondingly, service types include, but are not limited to: screen mirroring or collaboration services, file transfer services, and vehicle control notification services. Service data includes, but is not limited to: files, commands, and multimedia resources such as images, audio, and video.

[0080] Specifically, if the target device is successfully authenticated, it means that the target device is capable of interconnecting with the vehicle terminal. The vehicle terminal can then interconnect with the target device, thereby determining the service type based on the service initiated by the vehicle terminal, and selecting the target communication protocol from the communication protocol set according to the service type.

[0081] For example, assuming the service type is file transfer and the corresponding service data is images, then the Bluetooth communication protocol is selected as the target communication protocol from the set of communication protocols, or the WIFI communication protocol is selected as the target communication protocol.

[0082] In some embodiments, during the process of selecting a target communication protocol from a set of communication protocols based on the service type, communication protocols strongly associated with the service type are determined from the set of communication protocols as the target communication protocol. The degree of association between the service type and various communication protocols varies.

[0083] In some embodiments, different service types correspond to different service data interaction methods. For example, the service data interaction method for screen projection or collaboration is video streaming, the service data interaction method for file transfer is file streaming, and the service data interaction method for vehicle control notification is message transfer. From the set of communication protocols, a communication protocol strongly associated with the service type is determined as the target communication protocol. This includes: if the service type is screen projection or collaboration, selecting a communication protocol strongly associated with video streaming from the set of communication protocols as the target communication protocol; if the service type is file transfer, selecting a communication protocol strongly associated with file streaming from the set of communication protocols as the target communication protocol; and if the service type is vehicle control notification, selecting a communication protocol strongly associated with message transfer from the set of communication protocols as the target communication protocol.

[0084] For example, following the previous example, if the business type is file transfer, images can be transferred via Bluetooth or Wi-Fi. Since the Bluetooth communication protocol is most closely related to images, the Bluetooth communication protocol will be used as the target communication protocol.

[0085] For example, if the service type is screen mirroring or collaborative service, and the corresponding service data may be video, the video can be transmitted via Bluetooth or Wi-Fi. Since Wi-Fi communication protocol has the highest correlation with video, it will be selected as the target communication protocol. This allows for the selection of a suitable communication protocol.

[0086] S203. Establish a communication link between the vehicle terminal and the target device based on the target communication protocol.

[0087] The communication links include, but are not limited to, physical connections such as: WIFI Aware, P2P, STA, AP, BT Profile, BLE AOA, UWB, NFCIP, TCP / IP, hardware virtualization links, and computing networks. Each communication link corresponds to a transmission channel.

[0088] Optionally, if the communication link is a Bluetooth link, the corresponding transmission channel is a Generic Attribute Profile (GATT) channel; if the communication link is a Wireless Local Area Network (WLAN), the corresponding transmission channel is a Transmission Control Protocol / Internet Protocol (TCP / IP) channel or an Ultra Wideband (UWB) channel.

[0089] In some embodiments, the vehicle-mounted terminal initiates a connection request with the target device by calling the ConnectDevice interface. After receiving a response from the target device agreeing to the connection, a communication link is established between the vehicle-mounted terminal and the target device, such as a Bluetooth connection, UWB connection, Ethernet connection, WiFi connection, or inter-CPU shared memory connection. Optionally, a transmission channel is established between the vehicle-mounted terminal and the target device based on the communication link.

[0090] In some embodiments, during the execution of step S203, the connection status of the target device is first detected. If the connection status indicates an abnormal connection, the connection parameters are adjusted based on network conditions and communication load to re-establish the communication link between the vehicle terminal and the target device.

[0091] Understandably, during the process of establishing a communication link between the vehicle terminal and the target device based on the target communication protocol, the connection status of the target device is monitored in real time to continuously monitor the connection between devices. If the connection status indicates an abnormal connection, it means that the connection between devices may be disconnected. Then, the connection parameters are adjusted according to the network conditions and communication load to re-establish the communication connection and corresponding transmission channel with the target device, so that the connection status of the target device returns to normal, thereby ensuring the normal transmission and reception of subsequent business data and ensuring the stability and reliability of business data transmission.

[0092] S204. Send service data to the target device via the communication link, and / or receive service data sent by the target device via the communication link.

[0093] Business data includes, but is not limited to: files, instructions, and multimedia resources such as images, audio, and video.

[0094] In some embodiments, to ensure the security of business data transmission and reception, the vehicle terminal sends encrypted business data to the target device through the communication link and / or receives encrypted business data sent by the target device through the transmission channel, and / or decrypts the encrypted business data sent by the target device through the communication link.

[0095] For example, the vehicle-mounted terminal and the target device can transmit business data such as audio and video data, images, and files, enabling seamless business flow between the vehicle and other devices. For instance, a mobile phone can send audio and video to the vehicle-mounted terminal, video can be streamed between multiple screens in the smart cockpit, and vehicles can interconnect and share data.

[0096] In summary, this disclosure provides a method for vehicle-to-device interconnection. The method first involves an in-vehicle terminal authenticating a target device based on device information broadcast by the target device. If the target device is successfully authenticated, a target communication protocol is selected from a set of communication protocols. Then, a communication link is established between the in-vehicle terminal and the target device based on the target communication protocol, thereby exchanging service data with the target device through this communication link. Thus, this disclosure integrates a unified communication protocol between the in-vehicle terminal and other devices, eliminating the need to customize protocols based on underlying connection technologies during service development. This allows for efficient connection, transmission channel establishment, and service data transmission between the in-vehicle terminal and different devices, making it suitable for scenarios involving the interconnection of in-vehicle terminals with various devices and improving the scalability and compatibility of vehicle-to-device interconnection.

[0097] like Figure 3 As shown, Figure 3 An apparatus for vehicle-to-device interconnection provided in this disclosure includes:

[0098] The authentication module 301 is used to authenticate the target device based on the device information broadcast by the target device; the device information includes the device type and callable services, and the callable services are obtained by abstracting the hardware capabilities of the target device;

[0099] Selection module 302 is used to select a target communication protocol from the communication protocol set if the target device is successfully authenticated.

[0100] The communication module 303 is used to establish a communication link between the vehicle terminal and the target device based on the target communication protocol; to send service data to the target device through the communication link, and / or to receive service data sent by the target device through the communication link.

[0101] As an optional implementation of this disclosure, the authentication module 301, before authenticating the target device based on the device information broadcast by the target device, is further configured to: scan the soft bus to obtain the device information to be processed; the device information to be processed includes the account information of the device to be processed; verify whether the account information matches the account information corresponding to the vehicle terminal; if so, store the device information to be processed in the device list.

[0102] As an optional implementation of this disclosure, the selection module 302 is specifically used to: obtain the service type when the target device is authenticated; and select the target communication protocol from the communication protocol set according to the service type.

[0103] As an optional implementation of this disclosure, the selection module 302 is specifically used to: determine, from the set of communication protocols, a communication protocol strongly associated with the service type as the target communication protocol.

[0104] As an optional implementation of this disclosure, the service type includes at least one of screen projection or collaboration service, file transfer service, and vehicle control notification service; different service types correspond to different service data interaction methods, wherein the service data interaction method corresponding to screen projection or collaboration service is video streaming, the service data interaction method corresponding to file transfer service is file streaming, and the service data interaction method corresponding to vehicle control notification service is message transfer; the selection module 302 is specifically used for: if the service type is screen projection or collaboration service, selecting a communication protocol strongly associated with video streaming from the communication protocol set as the target communication protocol; if the service type is file transfer service, selecting a communication protocol strongly associated with file streaming from the communication protocol set as the target communication protocol; if the service type is vehicle control notification service, selecting a communication protocol strongly associated with message transfer from the communication protocol set as the target communication protocol.

[0105] like Figure 4 As shown, Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure. The electronic device includes: a processor 401, a memory 402, and a computer program stored in the memory 402 and executable on the processor 401. When the computer program is executed by the processor 401, it implements the various processes of the vehicle-device interconnection method in the above method embodiment. Since the same technical effects can be achieved, further details are omitted here to avoid repetition.

[0106] This disclosure provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the vehicle-device interconnection method described in the above method embodiments and achieves the same technical effect. To avoid repetition, further details are omitted here.

[0107] The computer-readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0108] This disclosure provides a vehicle that includes a vehicle-to-device interconnection device as described above, or an electronic device as described above. This device can implement all processes of the vehicle-to-device interconnection method in the above method embodiments and achieve the same technical effect. This enables the vehicle to achieve simple and efficient interconnection with peripheral devices, cloud servers, etc. The development of various business processes corresponding to the vehicle's interconnection with other devices does not need to focus on the underlying connection logic, thereby improving the efficiency and scalability of business development.

[0109] This disclosure provides a computer program product that stores a computer program. When the computer program is executed by a processor, it implements the various processes of the vehicle-device interconnection method described in the above method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0110] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media containing computer-usable program code.

[0111] It should be understood, in the several embodiments provided in this disclosure, that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative; for example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0112] In this disclosure, the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0113] In this disclosure, memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0114] In this disclosure, computer-readable media includes both permanent and non-permanent, removable and non-removable storage media. Storage media can store information using any method or technology; the 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, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient media, such as modulated data signals and carrier waves.

[0115] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0116] The above are merely specific embodiments of this disclosure, enabling those skilled in the art to understand or implement this disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to these embodiments, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for interconnecting a vehicle and equipment, characterized in that, The method comprises the following steps: The in-vehicle infotainment terminal authenticates the target device according to the device information broadcast by the target device; The device information comprises a device type and a callable service, and the callable service is obtained by abstracting hardware capabilities of the target device; In the case where the target device authentication is passed, a target communication protocol is selected from a communication protocol set; A communication link between the in-vehicle infotainment terminal and the target device is established based on the target communication protocol; Business data is sent to the target device through the communication link, and / or the target device sends business data through the communication link.

2. The method of claim 1, wherein, Before the authentication of the target device according to the device information broadcast by the target device, the method further comprises the following steps: Scan the soft bus to obtain to-be-processed device information; the to-be-processed device information comprises account information of a to-be-processed device; Verify whether the account information matches the account information corresponding to the in-vehicle infotainment terminal; If yes, the to-be-processed device information is stored in a device list.

3. The method of claim 1, wherein, In the case where the target device authentication is passed, the target communication protocol is selected from the communication protocol set, which comprises the following steps: In the case where the target device authentication is passed, a business type is obtained; According to the business type, the target communication protocol is selected from the communication protocol set.

4. The method of claim 3, wherein, According to the business type, the target communication protocol is selected from the communication protocol set, which comprises the following steps: From the communication protocol set, a communication protocol strongly associated with the business type is determined as the target communication protocol.

5. The method of claim 4, wherein, The business type comprises at least one of screen projection or collaboration business, file intercommunication business and vehicle control notification business; different business types correspond to different business data interaction modes, wherein the business data interaction mode corresponding to the screen projection or collaboration business is video stream transfer, the business data interaction mode corresponding to the file intercommunication business is file stream transfer, and the business data interaction mode corresponding to the vehicle control notification business is message intercommunication; According to the business type, the target communication protocol is selected from the communication protocol set, which comprises the following steps: If the business type is the screen projection or collaboration business, a communication protocol strongly associated with video stream transfer is selected from the communication protocol set as the target communication protocol; If the business type is the file intercommunication business, a communication protocol strongly associated with file stream transfer is selected from the communication protocol set as the target communication protocol; If the business type is the vehicle control notification business, a communication protocol strongly associated with message intercommunication is selected from the communication protocol set as the target communication protocol.

6. The method of claim 1, wherein, The communication link between the in-vehicle infotainment terminal and the target device is established based on the target communication protocol, which comprises the following steps: The connection state of the target device is monitored; In the case where the connection state indicates connection abnormity, connection parameters are adjusted based on network conditions and communication load to re-establish the communication link between the in-vehicle infotainment terminal and the target device.

7. An apparatus for vehicle-to-everything interconnection, the apparatus comprising: The in-vehicle infotainment terminal comprises an authentication module configured to authenticate the target device according to the device information broadcast by the target device; ​ The device information includes a device type and callable services, the callable services being abstracted from hardware capabilities of the target device; selecting a target communication protocol from a set of communication protocols if the target device passes the authentication; establishing a communication link between the vehicle terminal and the target device based on the target communication protocol, sending service data to the target device via the communication link, and / or receiving service data sent by the target device via the communication link.

8. An electronic device, comprising: comprising: a processor, a memory, and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the method for vehicle and device interconnection according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, comprising: a computer program stored on the computer readable storage medium, the computer program, when executed by the processor, implementing the method for vehicle and device interconnection according to any one of claims 1 to 6.

10. A vehicle characterized by comprising: comprising: and the device for vehicle and device interconnection according to claim 7, or the electronic device according to claim 8.

Images