Method, system and device for simultaneously realizing TBOX and IVI functions in SOC and vehicle

Abstract

The invention discloses a method for simultaneously realizing TBOX and IVI functions in an SOC (system on chip), which comprises the following steps: at least running a TBOX partition and an IVI partition on the SOC, and binding different kernel resources to the TBOX partition and the IVI partition; in the TBOX partition, TBOX software communicates with the wireless module through an interface, and meanwhile, a UART interface is adopted to perform connection and data interaction with the microprocessor; in the IVI partition, each piece of IVI software is in connection and data interaction with the microprocessor through an SPI (Serial Peripheral Interface); and the microprocessor carries out isolation processing on services of the TBOX partition and the IVI partition. The invention further discloses a corresponding system, device and vehicle. By implementing the method, the TBOX and IVI functions can be realized in the SOC, and the TBOX and the IVI are isolated from each other and do not influence each other during operation, so that the cost can be saved and the safety can be improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle computer technology, and in particular to a method, system, device and vehicle for simultaneously realizing TBOX and IVI functions in a SOC. Background Art

[0002] In the prior art, the intelligent vehicle terminal (Telematics BOX, TBOX) is mostly installed in the vehicle in the form of an independent box, and the operating system running on the TBOX is also basically the Linux system, which is more stable than the Android system. However, the cost of an independent TBOX is relatively high, and the in-vehicle infotainment system (IVI, i.e., the vehicle computer) also has functional modules such as the system on chip (SOC), microprocessor (MCU), and global positioning (GPS). Therefore, in order to save costs, some existing solutions also integrate the vehicle computer with the TBOX, so that the vehicle computer and the TBOX can share the same SOC, MCU and operating system, etc., which can greatly save costs.

[0003] Generally, in this kind of integration solution, since the application requirements of the vehicle ecological system require the use of the Android system, the integration solution also needs to use a single Android system. However, since the vehicle Android system itself has many applications and a large load, it is prone to unstable freezing, crashing, etc., which easily leads to TBOX instability in the integration solution. However, as a safety component, TBOX involves safety functions such as vehicle control and collision emergency calls. If the TBOX function cannot be guaranteed, there will be functional failure and safety risks. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a method, system, device and vehicle for realizing TBOX and IVI functions in SOC at the same time. TBOX and IVI functions can be realized in SOC, and TBOX and IVI are isolated from each other and do not affect each other during operation, which can save costs and improve safety.

[0005] In order to solve the above technical problems, as one aspect of the present invention, a method for simultaneously realizing TBOX and IVI functions in a SOC is provided, which is realized by a system including an interconnected system on chip SOC and a microprocessor MCU, and the method at least comprises:

[0006] At least a TBOX partition and an IVI partition are run on the SOC, wherein the TBOX partition and the IVI partition are bound to different kernel resources;

[0007] In the TBOX partition, the TBOX software communicates with the wireless module through an interface, and uses a UART interface to connect and exchange data with the microprocessor;

[0008] In the IVI partition, each IVI software is connected and exchanges data with the microprocessor via an SPI interface;

[0009] The microprocessor isolates the services of the TBOX partition and the IVI partition.

[0010] Among them, further include:

[0011] Allocating at least one kernel resource on the SOC, installing an Android system, and running each IVI software of the IVI partition on the Android system;

[0012] At least one other kernel resource is allocated on the SOC, and an embedded operating system is installed. The TBOX software in the TBOX partition runs on the embedded operating system, and the embedded operating system is FreeRTOS, QNX, VxWorks or embedded Linux operating system.

[0013] Among them, further include:

[0014] After the SOC is powered on, the microprocessor performs handshake operations with the Tbox software and the IVI software in turn. If no reply handshake message is received within the first predetermined time, the corresponding Tbox software or IVI software is restarted;

[0015] After the microprocessor and the TBOX software complete the handshake and establish the communication link, the heartbeat message periodically sent by the TBOX software is monitored, and if no heartbeat message is received within the second time, the TBOX software is controlled to be restarted.

[0016] The microprocessor performs isolation processing on the services of the TBOX partition and the IVI partition, further comprising:

[0017] Independent TBOX microservices and IVI microservices are set in the microprocessor to communicate with the TBOX software and IVI software respectively;

[0018] Among them, the PKI parameters of TBOX and IVI are controlled and set by calling different public key infrastructure PKI server addresses, and the digital certificates required for communication with TBOX and IVI are configured through corresponding PKI parameters; and separate application programming interfaces APIs for encryption, decryption and secure storage are configured for TBOX and IVI respectively.

[0019] Accordingly, as one aspect of the present invention, a system for simultaneously implementing TBOX and IVI functions in a SOC is provided, which comprises at least a SOC and a microprocessor MCU connected to the SOC, wherein:

[0020] At least a TBOX partition and an IVI partition are run on the SOC, wherein the TBOX partition and the IVI partition are bound to different kernel resources; in the TBOX partition, the TBOX software communicates with the wireless module through an interface, and uses a UART interface to connect and exchange data with the microprocessor; in the IVI partition, each IVI software is connected and exchanges data with the microprocessor through an SPI interface;

[0021] The microprocessor is used to isolate the services of the TBOX partition and the IVI partition.

[0022] Among them, further include:

[0023] A kernel resource allocation unit, used for allocating at least one kernel resource on the SOC, having an Android system installed thereon, and each IVI software of the IVI partition runs on the Android system;

[0024] And for allocating at least another kernel resource on the SOC, an embedded operating system is installed, the TBOX software in the TBOX partition runs on the embedded operating system, and the embedded operating system is FreeRTOS, QNX, VxWorks or embedded Linux operating system.

[0025] Among them, further include:

[0026] The exception handling unit is used to, after the SOC is powered on, cause the microprocessor to perform handshake operations with the Tbox software and the IVI software in turn, and if no reply handshake message is received within a predetermined first time, restart the corresponding Tbox software or IVI software; and after the microprocessor completes the handshake with the TBOX software and establishes a communication link, monitor the heartbeat message periodically sent by the TBOX software, and if no heartbeat message is received within a second time, control the restart operation of the TBOX software.

[0027] Among them, further include:

[0028] The network isolation processing unit is used to set up independent TBOX microservices and IVI microservices on the microprocessor to communicate with the TBOX software and the IVI software respectively;

[0029] Among them, the PKI parameters of TBOX and IVI are controlled and set by calling different public key infrastructure PKI server addresses, and the digital certificates required for communication with TBOX and IVI are configured through corresponding PKI parameters; and separate application programming interfaces APIs for encryption, decryption and secure storage are configured for TBOX and IVI respectively.

[0030] Accordingly, in another aspect of the present invention, there is also provided a SOC chip, which at least comprises:

[0031] A partition processing unit, for running at least a TBOX partition and an IVI partition on the SOC, wherein the TBOX partition and the IVI partition are bound to different kernel resources; in the TBOX partition, its TBOX software communicates with the wireless module through an interface, and uses a UART interface to connect and exchange data with the microprocessor; in the IVI partition, its various IVI software connect and exchange data with the microprocessor through an SPI interface;

[0032] A kernel resource allocation unit is used to allocate at least one kernel resource on the SOC, which is installed with an Android system, and each IVI software in the IVI partition runs on the Android system; and is used to allocate at least another kernel resource on the SOC, which is installed with an embedded operating system, and the TBOX software in the TBOX partition runs on the embedded operating system, and the embedded operating system is FreeRTOS, QNX, VxWorks or embedded Linux operating system.

[0033] Accordingly, another aspect of the present invention further provides a microprocessor, which at least comprises:

[0034] The exception handling unit is used for, after the SOC is powered on, the microprocessor performs handshake operations with the Tbox software and the IVI software in sequence, and if no reply handshake message is received within a predetermined first time, the corresponding Tbox software or IVI software is restarted; and after the microprocessor completes the handshake with the TBOX software and establishes a communication link, the heartbeat message sent periodically by the TBOX software is monitored, and if no heartbeat message is received within a second time, the TBOX software is restarted;

[0035] The network-connected isolation processing unit is used to set up independent TBOX microservices and IVI microservices in the microprocessor to communicate with the TBOX software and the IVI software respectively; wherein, the PKI parameters of TBOX and IVI are controlled and set by calling different public key infrastructure PKI server addresses, and the digital certificates required for communication with TBOX and IVI are configured through corresponding PKI parameters; and separate application programming interfaces APIs for encryption, decryption and secure storage are configured for TBOX and IVI respectively.

[0036] Correspondingly, another aspect of the present invention further provides a vehicle, on which at least a vehicle machine device is provided, and the above-mentioned system is deployed in the vehicle machine device.

[0037] The implementation of the embodiments of the present invention has the following beneficial effects:

[0038] The present invention provides a method, system, device and vehicle for realizing TBOX and IVI functions simultaneously in SOC. By setting TBOX partitions and IVI partitions in SOC, a solution of integrating TBOX in a vehicle computer is realized. At the same time, by binding TBOX to independent kernel resources and adopting communication isolation, abnormal safety handling mechanism, secure storage and network isolation, TBOX and IVI can be isolated from each other and do not affect each other during operation. The implementation of the present invention not only saves costs, but also reduces the cost of TBOX and improves safety;

[0039] The implementation of the embodiments of the present invention can not only save hardware and costs, but also achieve decoupling and isolation, thereby ensuring the safety of the TBOX and the vehicle computer, minimizing the impact of abnormalities, and improving the safety of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, without paying creative labor, other drawings obtained based on these drawings still belong to the scope of the present invention.

[0041] Figure 1 A schematic diagram of the main process of an embodiment of a method for simultaneously realizing TBOX and IVI functions in a SOC provided by the present invention;

[0042] Figure 2 for Figure 1 Schematic diagram of the application environment;

[0043] Figure 3 for Figure 1 Schematic diagram of the principle of anomaly monitoring involved;

[0044] Figure 4 A schematic diagram of the structure of an embodiment of a system for realizing TBOX and IVI functions simultaneously in a SOC provided by the present invention. DETAILED DESCRIPTION

[0045] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention will be further described in detail below with reference to the accompanying drawings.

[0046] like Figure 1 FIG. 1 is a schematic diagram showing a main flow chart of an embodiment of a method for realizing TBOX and IVI functions in a SOC simultaneously provided by the present invention. Figure 2 and Figure 3 As shown, in this embodiment, the method is implemented by a system including an interconnected system on chip SOC and a microprocessor MCU, and the method includes at least the following steps:

[0047] Step S1, at least a TBOX partition and an IVI partition are running on the SOC, wherein the TBOX partition and the IVI partition are bound to different kernel resources;

[0048] Refer to Figure 2 As shown, in this embodiment, the TBOX partition may include components such as TBOX software, TBOX API and TBOX service, specifically, wherein:

[0049] TBOX software is a software application running in the TBOX module, which is responsible for handling data communication with the vehicle, network connection and remote operation, etc. TBOX software can be an application in the vehicle system to provide functions such as vehicle status monitoring and remote control.

[0050] TBOX API is a set of software interfaces provided to third-party developers or other applications to interact with TBOX. By using TBOX API, developers can write their own applications to achieve data communication and control with the vehicle.

[0051] TBOX service is a background service running in the TBOX module. It is responsible for managing the functions and communications of TBOX, as well as tasks such as data transmission and OTA upgrade with external servers. TBOX service is always in the background to ensure the normal operation of the TBOX module and provide necessary functional support.

[0052] In this solution, if TBOX has independent OTA (Over-the-Air) capability, that is, it can be remotely upgraded and configured, then TBOX software, TBOX API and TBOX service can work independently of the kernel. They can work independently of the kernel and interact with the MCU through appropriate communication interfaces (such as UART).

[0053] The IVI partition may include components such as IVI software, framework, and hardware abstraction layer (HAL).

[0054] IVI software is an in-vehicle infotainment application running on the Android system, such as navigation software, music player, communication applications, etc. IVI software provides the actual functions and user interface, enabling drivers and passengers to use the vehicle's entertainment and information services.

[0055] The Framework is a software layer that provides an environment for application development and operation. It contains many libraries, APIs, and services to simplify application development and interaction with system functions. The Framework provides a general development framework that can support the development of various IVI applications.

[0056] HAL is a part of the Android system that provides an abstract layer interface with the underlying hardware devices. HAL encapsulates the specific details of the underlying hardware and provides a unified hardware access interface for the upper-level Framework and applications. Through HAL, the upper-level components of the Android system can communicate with different hardware devices without paying attention to the specific implementation details of the hardware.

[0057] These components (IVI software, Framework, and HAL) interact with the kernel to achieve complete vehicle system functions. For example, IVI software calls related API interfaces through the Framework to access media, navigation, and communication functions. The Framework communicates with the underlying hardware devices through the hardware abstraction layer interface provided by the HAL to control and manage hardware resources.

[0058] More specifically, in a specific example, the SOC is described as a multi-core (such as 8-core) system, and the step S1 further includes:

[0059] At least one kernel resource is allocated on the SOC, an Android system is installed, and each IVI software of the IVI partition runs on the Android system; the SOC usually contains multiple cores (i.e., CPU cores). These cores can undertake different tasks and run different software to improve the processing power and efficiency of the system. In the SOC, the kernel of the Android system is the core component of the Android system, responsible for managing system resources, device drivers, and various low-level functions. The kernel of the Android system (i.e., kernel) usually works with the processing core in the SOC as the core part of the operating system. Other components of the Android system (such as applications, frameworks, user interfaces, etc.) run on top of the kernel and interact with the kernel and other cores in the SOC to provide complete Android system functions.

[0060] At least one other kernel resource is allocated on the SOC, and an embedded operating system is installed. The TBOX software in the TBOX partition runs on the embedded operating system, and the embedded operating system is FreeRTOS, QNX, VxWorks or an embedded Linux operating system. In short, in this embodiment, TBOX can run independently of the kernel (Kenel) of the Android system. In this embodiment, the TBOX service is bound to an independent core, and through the independent core allocation, the real-time and non-interference performance of the TBOX service is guaranteed under the heavy load condition of the overall system.

[0061] TBOX directly accesses the wireless module (Modem) through an interface, and does not rely on the Android system. Even if the Android system crashes, it will not affect the TBOX partition. Through this solution, Android upgrades require a system restart, and Android can be upgraded independently; TBOX can be OTA independently, so that the integrated solution does not affect each other's software and matching.

[0062] Step S2, in the TBOX partition, the TBOX software communicates with the wireless module (Modem) through an interface, and uses a UART interface to connect and exchange data with the microprocessor; the interaction between the two mainly includes vehicle data, power status, etc.;

[0063] Step S3, in the IVI partition, each IVI software is connected and exchanges data with the microprocessor through the SPI interface; the SPI interface is a serial data transmission interface between the IVI and the MCU, which has the advantage of higher transmission speed and can adapt to the characteristics of the IVI needing to transmit large amounts of data.

[0064] Step S4: the microprocessor isolates the services of the TBOX partition and the IVI partition.

[0065] In this embodiment, step S4 is implemented by the following three measures:

[0066] (1) Independent TBOX microservices and IVI microservices are set up in the microprocessor to communicate with the TBOX software and IVI software respectively; at the same time, it can ensure that the functions and data of TBOX and IVI are isolated from each other when processing, avoiding mutual interference.

[0067] In a more specific example, the TBOX microservice is a microservice that specifically communicates with TBOX. TBOX is usually an on-board communication device that is responsible for handling functions such as remote monitoring of the vehicle, vehicle data collection and transmission, etc. The TBOX microservice can realize functions such as data interaction, remote control, data collection and processing with TBOX, and provide services related to TBOX.

[0068] IVI microservices are microservices that specifically communicate with IVI. IVI is usually an in-vehicle entertainment and information system that provides functions such as navigation, entertainment, and communication. IVI microservices can implement functions such as data interaction, information transmission, and entertainment control with IVI, and provide services related to IVI.

[0069] Through independent microservice architecture, better modularization and isolation can be achieved, and the scalability and flexibility of the system can be improved. Each microservice is responsible for communicating with the corresponding device and providing corresponding services and functions. In this way, the separation and independent processing of TBOX and IVI are achieved.

[0070] (2) In this embodiment, the PKI parameters of TBOX and IVI are controlled and set by calling different public key infrastructure PKI server addresses, and the digital certificates required for communication with TBOX and IVI are configured through the corresponding PKI parameters;

[0071] It is understandable that under normal circumstances, a single host of the integrated solution has a single SN code and VIN code, and the port number and domain name are fixed, and generally only one PKI certificate needs to be downloaded. However, if one PKI is used in this embodiment, IVI will reuse the PKI certificate of TBOX, and the networking will be affected by each other.

[0072] In this embodiment, cefp can achieve isolation between TBOX and IVI by using different PKI parameters and different PKI server addresses to ensure that they have independent security identification and authentication. For example, the TBOX microservice can call a PKI server address named TBOX_PKI, and the IVI microservice can call a PKI server address named IVI_PKI to distinguish and set different PKI parameters.

[0073] Assume that the communication between MCU and TBOX and IVI requires the use of digital certificates for authentication and encrypted communication. In MCU, the PKI parameters are used to configure the digital certificate-related information required for communication with TBOX and IVI, such as the certificate path, certificate password, and certificate authority. These parameters can be set according to the specific system requirements and the PKI implementation used.

[0074] When communicating with TBOX, MCU can use the pre-configured PKI parameters of TBOX to ensure the security and identity authentication of communication. MCU loads TBOX's digital certificate, verifies the validity and authenticity of the certificate, and uses the public key in the certificate for encrypted communication. This ensures the confidentiality and integrity of communication while verifying the identity of TBOX.

[0075] Similarly, when communicating with an IVI, the MCU can use the pre-configured PKI parameters of the IVI to ensure the security and identity authentication of the communication. The MCU loads the IVI's digital certificate, verifies the validity and authenticity of the certificate, and uses the public key in the certificate for encrypted communication. This ensures the confidentiality and integrity of the communication while verifying the identity of the IVI.

[0076] It can be understood that by using different PKI parameters in MCU to configure the digital certificates required for communication with TBOX and IVI, the identity authentication and communication security of each communication entity can be ensured. Such security settings can prevent unauthorized access and data tampering, ensuring the reliability and security of the system. The specific PKI parameter settings and digital certificate management can be customized according to system requirements and the PKI implementation used.

[0077] (3) In this embodiment, separate application programming interface APIs for encryption and decryption and secure storage can be configured for TBOX and IVI respectively. Separate encryption and decryption and secure storage APIs are implemented for TBOX and IVI respectively to ensure independent encryption and storage operations on their data. For example, the TBOX microservice can call the encryption and decryption and secure storage APIs named TBOX_Encryption_API and TBOX_Storage_API, while the IVI microservice can call the APIs named IVI_Encryption_API and IVI_Storage_API. Therefore, by using different encryption and decryption and secure storage APIs, single files can be encrypted and stored for TBOX and IVI respectively, which can further ensure security.

[0078] In a more specific example, the following program can be used to implement the above functions:

[0079] / / TBOX Microservices

[0080] void TBOX_Service(){

[0081] / / Call TBOX_PKI server address to set TBOX PKI parameters

[0082] setPKIParameters("TBOX_PKI");

[0083] / / Call TBOX_Encryption_API to perform encryption operation

[0084] encryptData("TBOX_Encryption_API");

[0085] / / Call TBOX_Storage_API for secure storage

[0086] storeData("TBOX_Storage_API");

[0087] / / Other TBOX functions and operations

[0088] }

[0089] / / IVI Microservices

[0090] void IVI_Service(){

[0091] / / Call the IVI_PKI server address to set the IVI PKI parameters

[0092] setPKIParameters("IVI_PKI");

[0093] / / Call IVI_Encryption_API to perform encryption operation

[0094] encryptData("IVI_Encryption_API");

[0095] / / Call IVI_Storage_API for secure storage

[0096] storeData("IVI_Storage_API");

[0097] / / Other IVI functions and operations

[0098] }

[0099] / / Call two microservices in the main program

[0100] int main(){

[0101] / / Run TBOX microservice and IVI microservice

[0102] / / Ensure that the two microservices can run simultaneously and be isolated from each other

[0103] runMicroServices(TBOX_Service,IVI_Service);

[0104] / / Other main program logic

[0105] }.

[0106] In the above sample program, the two microservices implement different functions and operations for TBOX and IVI respectively, and realize different processing of data through independent parameter settings, encryption and decryption, and storage APIs, ensuring security and mutual isolation.

[0107] It is understandable that in the embodiment of the present invention, an abnormality monitoring step is also provided, which can be seen in Figure 3 Specifically, the abnormality monitoring step further includes:

[0108] Step S20, after the SOC is powered on, the microprocessor performs handshake operations with the Tbox software and the IVI software in turn, and if no reply handshake message is received within a predetermined first time, the corresponding Tbox software or IVI software is restarted;

[0109] More specifically, if Figure 3 As shown, after the power supply is turned on and the SOC is powered, the handshake operation with the Tbox software and the IVI software can be started in sequence.

[0110] During the handshake process with the TBOX software, if the cold start timeout is 20 minutes, the hot start timeout is 60 seconds, and the handshake reply signal (0x6666) from the TBOX software is not received, then the corresponding TBOX software can be restarted;

[0111] Similarly, during the handshake process with the IVI software, if the cold start times out for 20 minutes and the hot start times out for 150 seconds, and no handshake reply signal (0x5501) is received from the IVI software, the corresponding IVI software can be restarted.

[0112] Step S21, after the microprocessor and the TBOX software complete handshake and establish a communication link, monitor the heartbeat message sent periodically (such as 5 seconds) by the TBOX software, and if no heartbeat message is received within a second time (such as 60 seconds), control the restart operation of the TBOX software.

[0113] It is understandable that during the operation of the IVI software, if it is monitored that a restart operation is required, the IVI software can be controlled to restart independently without affecting the operation of the TBOX software.

[0114] In this embodiment, through the exception handling safety mechanism solution, restarting the TBOX alone can avoid restarting the IVI system together, and restarting the IVI host abnormally can avoid TBOX system abnormalities, which can reduce mutual impact.

[0115] like Figure 4As shown, the present invention also provides a structural schematic diagram of an implementation of a system for realizing TBOX and IVI functions in a SOC. In this embodiment, the system 1 at least includes a system-on-chip SOC chip 11 and a microprocessor MCU12 connected to the SOC, wherein:

[0116] The SOC chip 11 specifically includes:

[0117] The partition processing unit 110 is used to run at least a TBOX partition and an IVI partition on the SOC, wherein the TBOX partition and the IVI partition are bound to different kernel resources; in the TBOX partition, its TBOX software communicates with the wireless module through an interface, and uses a UART interface to connect and exchange data with the microprocessor; in the IVI partition, its various IVI software connects and exchanges data with the microprocessor through an SPI interface;

[0118] The kernel resource allocation unit 111 is used to allocate at least one kernel resource on the SOC, and has an Android system installed thereon. The IVI software in the IVI partition runs on the Android system; and is used to allocate at least another kernel resource on the SOC, and has an embedded operating system installed thereon. The TBOX software in the TBOX partition runs on the embedded operating system, and the embedded operating system is FreeRTOS, QNX, VxWorks or an embedded Linux operating system.

[0119] The microprocessor 12 at least includes:

[0120] The exception handling unit 120 is used for, after the SOC is powered on, the microprocessor performs handshake operations with the Tbox software and the IVI software in sequence, and if no reply handshake message is received within a predetermined first time, restarting the corresponding Tbox software or IVI software; and for, after the microprocessor completes handshake with the TBOX software and establishes a communication link, monitoring the heartbeat message periodically sent by the TBOX software, and if no heartbeat message is received within a second time, controlling the restart operation of the TBOX software;

[0121] The network isolation processing unit 121 is used to set up independent TBOX microservices and IVI microservices in the microprocessor to communicate with the TBOX software and the IVI software respectively; wherein, the PKI parameters of TBOX and IVI are controlled and set by calling different public key infrastructure PKI server addresses, and the digital certificates required for communication with TBOX and IVI are configured through corresponding PKI parameters; and separate application programming interfaces API for encryption, decryption and secure storage are configured for TBOX and IVI respectively.

[0122] For more details, please refer to and combine the above Figures 1 to 3 The description is not repeated here.

[0123] Accordingly, another aspect of the present invention further provides a vehicle, on which at least a vehicle machine device is provided, in which the vehicle machine device is deployed Figure 4 More details can be found in conjunction with the above Figure 4 The description is not repeated here.

[0124] The implementation of the embodiments of the present invention has the following beneficial effects:

[0125] The present invention provides a method, system, device and vehicle for realizing TBOX and IVI functions simultaneously in SOC. By setting TBOX partitions and IVI partitions in SOC, a solution of integrating TBOX in a vehicle computer is realized. At the same time, by binding TBOX to independent kernel resources and adopting communication isolation, abnormal safety handling mechanism, secure storage and network isolation, TBOX and IVI can be isolated from each other and do not affect each other during operation. The implementation of the present invention not only saves costs, but also reduces the cost of TBOX and improves safety;

[0126] The implementation of the embodiments of the present invention can not only save hardware and costs, but also achieve decoupling and isolation, thereby ensuring the safety of the TBOX and the vehicle computer, minimizing the impact of abnormalities, and improving the safety of the vehicle.

[0127] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0128] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0129] The above disclosure is only a preferred embodiment of the present invention, which certainly cannot be used to limit the scope of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.

Claims

1. A method for simultaneously realizing TBOX and IVI functions in a SOC, which is realized by a system including an interconnected system on chip SOC and a microprocessor MCU, characterized in that: The method at least comprises: At least a TBOX partition and an IVI partition are run on the SOC, wherein the TBOX partition and the IVI partition are bound to different kernel resources; In the TBOX partition, the TBOX software communicates with the wireless module through an interface, and uses a UART interface to connect and exchange data with the microprocessor; In the IVI partition, each IVI software is connected and exchanges data with the microprocessor via an SPI interface; The microprocessor isolates the services of the TBOX partition and the IVI partition.

2. The method according to claim 1, characterized in that At least a TBOX partition and an IVI partition are run on the SOC, further comprising: Allocating at least one kernel resource on the SOC, installing an Android system, and running each IVI software of the IVI partition on the Android system; At least one other kernel resource is allocated on the SOC, and an embedded operating system is installed. The TBOX software in the TBOX partition runs on the embedded operating system, and the embedded operating system is FreeRTOS, QNX, VxWorks or embedded Linux operating system.

3. The method according to claim 2, characterized in that Further including: After the SOC is powered on, the microprocessor performs handshake operations with the Tbox software and the IVI software in turn. If no reply handshake message is received within the first predetermined time, the corresponding Tbox software or IVI software is restarted; After the microprocessor and the TBOX software complete the handshake and establish the communication link, the heartbeat message periodically sent by the TBOX software is monitored, and if no heartbeat message is received within the second time, the TBOX software is controlled to be restarted.

4. The method according to claim 3, characterized in that The microprocessor isolates the services of the TBOX partition and the IVI partition, further comprising: Independent TBOX microservices and IVI microservices are set in the microprocessor to communicate with the TBOX software and IVI software respectively; Among them, the PKI parameters of TBOX and IVI are controlled and set by calling different public key infrastructure PKI server addresses, and the digital certificates required for communication with TBOX and IVI are configured through corresponding PKI parameters; and separate application programming interfaces APIs for encryption, decryption and secure storage are configured for TBOX and IVI respectively.

5. A system for realizing TBOX and IVI functions simultaneously in SOC, characterized in that: At least includes a SOC and a microprocessor MCU connected to the SOC, wherein: At least a TBOX partition and an IVI partition are run on the SOC, wherein the TBOX partition and the IVI partition are bound to different kernel resources; in the TBOX partition, the TBOX software communicates with the wireless module through an interface, and uses a UART interface to connect and exchange data with the microprocessor; in the IVI partition, each IVI software is connected and exchanges data with the microprocessor through an SPI interface; The microprocessor is used to isolate the services of the TBOX partition and the IVI partition.

6. The system according to claim 5, characterized in that Further including: A kernel resource allocation unit, used for allocating at least one kernel resource on the SOC, having an Android system installed thereon, and each IVI software of the IVI partition runs on the Android system; And for allocating at least another kernel resource on the SOC, an embedded operating system is installed, the TBOX software in the TBOX partition runs on the embedded operating system, and the embedded operating system is FreeRTOS, QNX, VxWorks or embedded Linux operating system.

7. The system according to claim 6, characterized in that Further including: The exception handling unit is used for the microprocessor to perform handshake operations with the Tbox software and the IVI software in sequence after the SOC is powered on. If a reply handshake message is not received within the predetermined first time, the corresponding Tbox software or IVI software is restarted; After the microprocessor and the TBOX software complete the handshake and establish the communication link, the heartbeat message periodically sent by the TBOX software is monitored, and if no heartbeat message is received within the second time, the TBOX software is controlled to be restarted.

8. The system according to claim 7, characterized in that Further including: The network isolation processing unit is used to set up independent TBOX microservices and IVI microservices on the microprocessor to communicate with the TBOX software and the IVI software respectively; Among them, the PKI parameters of TBOX and IVI are controlled and set by calling different public key infrastructure PKI server addresses, and the digital certificates required for communication with TBOX and IVI are configured through the corresponding PKI parameters; And configure separate application programming interface APIs for encryption, decryption and secure storage for TBOX and IVI respectively.

9. A SOC chip, characterized in that: At least: A partition processing unit, for running at least a TBOX partition and an IVI partition on the SOC, wherein the TBOX partition and the IVI partition are bound to different kernel resources; in the TBOX partition, its TBOX software communicates with the wireless module through an interface, and uses a UART interface to connect and exchange data with the microprocessor; in the IVI partition, its various IVI software connect and exchange data with the microprocessor through an SPI interface; A kernel resource allocation unit is used to allocate at least one kernel resource on the SOC, which is installed with an Android system, and each IVI software in the IVI partition runs on the Android system; and is used to allocate at least another kernel resource on the SOC, which is installed with an embedded operating system, and the TBOX software in the TBOX partition runs on the embedded operating system, and the embedded operating system is FreeRTOS, QNX, VxWorks or embedded Linux operating system.

10. A microprocessor, characterized in that: At least: The exception handling unit is used for the microprocessor to perform handshake operations with the Tbox software and the IVI software in sequence after the SOC is powered on. If a reply handshake message is not received within the predetermined first time, the corresponding Tbox software or IVI software is restarted; and for monitoring the heartbeat message periodically sent by the TBOX software after the microprocessor and the TBOX software complete the handshake and establish the communication link, and if the heartbeat message is not received within the second time, controlling the restart operation of the TBOX software; The network connection isolation processing unit is used to set up independent TBOX microservices and IVI microservices in the microprocessor to communicate with the TBOX software and the IVI software respectively; wherein, the PKI parameters of the TBOX and IVI are controlled and set by calling different public key infrastructure PKI server addresses, and the digital certificates required for communication with the TBOX and IVI are configured through the corresponding PKI parameters; And configure separate application programming interface APIs for encryption, decryption and secure storage for TBOX and IVI respectively.

11. A vehicle, at least provided with a vehicle machine device, wherein the system according to any one of claims 5 to 8 is configured in the vehicle machine device.

Images