Cross-system peripheral enabling method and system, in-vehicle infotainment system and storage medium

Abstract

The invention relates to the technical field of intelligent automobiles, in particular to a cross-system peripheral enabling method and system, a vehicle machine and a storage medium. The method comprises the following steps: when a slave operating system detects power-on, acquiring an identifier of a target peripheral and a corresponding working parameter from a pre-stored configuration file; the target peripheral is an in-vehicle peripheral for enabling the slave operating system. When the identifiers of the plurality of vehicle peripheral devices capable of being enabled by the master operation system comprise the identifier of the target peripheral device, it is indicated that the master operation system can help the slave operation system to configure the working parameters of the target peripheral device, and the working parameters of the target peripheral device can be configured based on the virtual configuration module associated with the target peripheral device. And transmitting a working parameter corresponding to the identifier of the target peripheral from the slave operating system to the master operating system, so that the master operating system controls a physical working parameter configuration module to enable the target peripheral based on the working parameter corresponding to the identifier of the target peripheral. In this way, the target peripheral which is only independently controlled by the slave operating system can be enabled, and the application range is wide.

Description

Technical Field

[0001] The present application relates to the field of intelligent vehicle technology, and in particular to a cross-system peripheral enabling method, system, vehicle computer and storage medium. Background Art

[0002] With the development of science and technology, the functions of vehicles are showing a trend of diversification. With the diversification of vehicle functions, it is necessary to install a large number of applications on the vehicle computer. Usually, due to the large number of applications installed in the vehicle computer, more computing resources are required. In order to avoid the vehicle computer from crashing during operation, the main operating system (i.e. HostVM) and the slave operating system (i.e. GuestVM) can be run on the virtual machine of the vehicle computer. The main operating system is used to install applications related to driving functions (such as navigation applications, instrument applications, and intelligent control applications), and the slave operating system is used to install applications related to entertainment functions (such as music applications, browser applications, etc.).

[0003] Generally, different operating systems of the vehicle computer can be used to control different vehicle computer peripherals. For example, the main operating system of the vehicle computer can be used to control the vehicle's driver's seat, sound card, and sunroof, etc., and the vehicle's slave operating system can also be used to control the vehicle's seat, sound card, and sunroof. It should be noted that the above-mentioned driver's seat, sound card, sunroof and other peripherals need to be enabled in advance using the working parameters configured by the physical working parameter configuration module associated with the main operating system. However, the main operating system can only enable vehicle computer peripherals (such as the driver's seat, sound card) that are only controlled by the main operating system alone or jointly controlled with the slave operating system, but cannot enable vehicle computer peripherals (such as USB interface) that are only controlled by the slave operating system alone, which has certain limitations. As a result, the slave operating system cannot control vehicle computer peripherals such as USB interface alone. Summary of the invention

[0004] The present application provides a cross-system peripheral enabling method, system, vehicle computer and storage medium, which are used to solve the problem that the prior art cannot enable vehicle computer peripherals (such as USB interfaces) that need to be controlled independently from the operating system, which has certain limitations.

[0005] In a first aspect, the present application provides a cross-system peripheral enabling method, which is applied to a cross-system peripheral enabling system of a vehicle computer, wherein the cross-system peripheral enabling system includes a master operating system and a slave operating system, wherein the vehicle computer is connected to a target peripheral for enabling the slave operating system, and the method provided by the present application includes:

[0006] After detecting that the power is on, the main operating system transmits the identifiers of multiple vehicle peripherals that can be enabled to the slave operating system;

[0007] The operating system creates corresponding virtual configuration modules for configuring working parameters of the plurality of vehicle computer peripherals according to the identifications of the plurality of vehicle computer peripherals;

[0008] Obtaining the identification of the target peripheral device and the corresponding operating parameters from a pre-stored configuration file of the operating system;

[0009] When the slave operating system determines that the identifiers of the plurality of vehicle peripherals include the identifier of the target peripheral, the virtual configuration module of the slave operating system associated with the target peripheral transmits the operating parameters corresponding to the identifier of the target peripheral from the slave operating system to the master operating system;

[0010] The main operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameters corresponding to the identifier of the target peripheral device.

[0011] In some implementations, a virtual configuration module of the slave operating system associated with the target peripheral device transmits an operating parameter corresponding to an identifier of the target peripheral device from the slave operating system to the master operating system, including:

[0012] Writing, from a virtual transmission front end in the operating system, operating parameters corresponding to the identifier of the target peripheral device from a virtual configuration module associated with the target peripheral device into a preset shared memory;

[0013] Sending a target notification message from the virtual transmission front end in the operating system to the main operating system through the virtual machine monitor, the target notification message is used to indicate that the working parameters corresponding to the identifier of the target peripheral device have been written into the shared memory;

[0014] The virtual transmission backend in the main operating system responds to the target notification message and reads the working parameters corresponding to the identifier of the target peripheral device from the shared memory.

[0015] In some implementations, the main operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameter corresponding to the identifier of the target peripheral device, including:

[0016] The main operating system responds to the validation request from the slave operating system to validate the working parameters corresponding to the identifier of the target peripheral device;

[0017] The master operating system sends a first notification message to the slave operating system, where the first notification message is used to indicate that a working parameter corresponding to the identifier of the target peripheral device is effective;

[0018] In response to the enable request from the slave operating system, the master operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameter corresponding to the identifier of the valid target peripheral device.

[0019] In some implementations, the operating parameters include a clock frequency and an operating voltage, the physical operating parameter configuration module includes a clock module and a voltage configuration module, and the main operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameters corresponding to the identifier of the target peripheral device, including:

[0020] The main operating system controls the clock module to configure the clock frequency to the target peripheral and the operating voltage to the target peripheral, so as to enable the target peripheral according to the clock frequency and the operating voltage.

[0021] In some implementations, after detecting power-on, the master operating system transmits the identifiers of multiple vehicle peripherals that can be enabled to the slave operating system, including:

[0022] Sending a peripheral quantity inquiry request from the operating system to the main operating system;

[0023] The slave operating system receives the number of identifiers of multiple vehicle computer peripherals that can be enabled, which is sent by the main operating system in response to the peripheral quantity inquiry request;

[0024] The slave operating system obtains the identifiers of the multiple vehicle computer peripheral devices that can be enabled one by one from the master operating system based on the number of the identifiers of the multiple vehicle computer peripheral devices received.

[0025] In some implementations, before the slave operating system sends a peripheral quantity inquiry request to the master operating system, the method further includes:

[0026] Sending a version inquiry request from the operating system to the main operating system;

[0027] receiving, from the operating system, version information of a protocol for configuring working parameters of a vehicle computer peripheral device, sent by the main operating system in response to a version query request;

[0028] The slave operating system sends a peripheral quantity inquiry request to the master operating system, including:

[0029] When the version information of the protocol for configuring the working parameters of the vehicle computer peripherals is verified, a peripheral quantity inquiry request is sent from the operating system to the main operating system.

[0030] In some implementations, the target peripheral is a USB interface, and after the main operating system controls the physical operating parameter configuration module to enable the target peripheral based on the operating parameters corresponding to the identifier of the target peripheral, the method further includes:

[0031] The main operating system uses the configured working parameters to access the plug-in electronic device plugged into the USB interface.

[0032] In a second aspect, the present application further provides a cross-system peripheral enabling system, including a main operating system and a slave operating system loaded on a vehicle computer, the vehicle computer being connected to a target peripheral for enabling the slave operating system, wherein:

[0033] The main operating system is used to transmit the identifications of multiple vehicle peripherals that can be enabled to the slave operating system after detecting power-on;

[0034] The slave operating system is used to create virtual configuration modules respectively corresponding to the working parameters of the plurality of vehicle computer peripherals according to the identifications of the plurality of vehicle computer peripherals; obtain the identification of the target peripheral and the corresponding working parameters from the pre-stored configuration file; when the slave operating system determines that the identifications of the plurality of vehicle computer peripherals include the identification of the target peripheral, the virtual configuration module of the slave operating system associated with the target peripheral transmits the working parameters corresponding to the identification of the target peripheral from the slave operating system to the master operating system;

[0035] The main operating system is also used to control the physical working parameter configuration module to enable the target peripheral device based on the working parameters corresponding to the identifier of the target peripheral device.

[0036] In a third aspect, the present application further provides a vehicle computer, including:

[0037] processor;

[0038] a memory for storing processor-executable instructions;

[0039] The processor is configured to execute instructions to implement the cross-system peripheral enabling method provided in the first aspect of the present application.

[0040] In a fourth aspect, the present application further provides a storage medium. When the instructions in the storage medium are executed by the processor of the vehicle computer, the vehicle computer can execute the cross-system peripheral enabling method provided in the first aspect of the present application.

[0041] The present application provides a cross-system peripheral enabling method, system, vehicle computer and storage medium. When the vehicle computer is powered on, the identification and corresponding working parameters of the target peripheral are obtained from the pre-stored configuration file of the operating system. Among them, the target peripheral is a vehicle computer peripheral enabled by the slave operating system. When the identifications of multiple vehicle computer peripherals that can be enabled by the main operating system include the identification of the target peripheral, it means that the main operating system can help the slave operating system configure the working parameters of the target peripheral. Furthermore, the working parameters corresponding to the identification of the target peripheral can be transmitted from the slave operating system to the main operating system from the virtual configuration module that associates the operating system with the target peripheral. Next, the main operating system can control the physical working parameter configuration module to enable the target peripheral based on the working parameters corresponding to the identification of the target peripheral. In this way, target peripherals that are only controlled by the slave operating system alone can be enabled, and the application range is wide. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0043] Figure 1 A software architecture block diagram of the central control chip of the vehicle computer provided in an embodiment of the present application;

[0044] Figure 2 One of the flowcharts of the cross-system peripheral enabling method provided in an embodiment of the present application;

[0045] Figure 3 A second flowchart of a method for enabling a cross-system peripheral provided in an embodiment of the present application;

[0046] Figure 4 A functional module block diagram of a cross-system peripheral enabling device provided in an embodiment of the present application;

[0047] Figure 5 A circuit connection block diagram of the vehicle computer provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0049] Various structural schematic diagrams according to embodiments of the present disclosure are shown in the accompanying drawings. These figures are not drawn to scale, and some details are magnified and some details may be omitted for the purpose of clear expression. The shapes of various regions and layers shown in the figures and the relative sizes and positional relationships therebetween are only exemplary, and may deviate in practice due to manufacturing tolerances or technical limitations, and those skilled in the art may further design regions / layers with different shapes, sizes, and relative positions according to actual needs.

[0050] In the context of the present disclosure, when a layer / element is referred to as being "on" another layer / element, the layer / element may be directly on the other layer / element or an intervening layer / element may exist therebetween. In addition, if a layer / element is "on" another layer / element in one orientation, the layer / element may be "below" the other layer / element when the orientation is reversed.

[0051] The following is a detailed description of the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0052] An embodiment of the present application provides a cross-system peripheral enabling method, which is applied to the central control chip of the vehicle computer. The central control chip of the vehicle computer, the physical working parameter configuration module and multiple vehicle computer peripherals are communicatively connected in sequence. Among them, the central control chip 301 of the vehicle computer can be a SOC chip. The central control chip of the vehicle computer is loaded with a main operating system and a slave operating system. Among them, the main operating system can be but not limited to the Linux operating system, and the slave operating system can be but not limited to the Android operating system. Among them, the main operating system and the slave operating system are divided into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the main operating system and the slave operating system can be divided into four layers, namely, the application layer (applications), the framework layer (application framework), the hardware abstract layer (hardware abstract layer, HAL) and the kernel layer (kernel). As Figure 1 As shown, the kernel layer of the slave operating system includes a clock driver, an operating voltage driver, a reset driver, a first transmission layer, and a virtual transmission front end, and the kernel layer of the master operating system includes a virtual transmission back end and a second transmission layer. The physical operating parameter configuration module may include but is not limited to a clock frequency configuration hardware module, an operating voltage configuration hardware module, and a reset parameter configuration module that interact with the master operating system. In addition, the plurality of vehicle peripherals include a target peripheral enabled by the slave operating system. Among them, the target peripheral may be, but is not limited to, a USB interface. As Figure 2 As shown, the method provided in the embodiment of the present application includes:

[0053] S201: After detecting that power is on, the main operating system transmits the identifiers of multiple vehicle peripherals that can be enabled to the slave operating system.

[0054] It can be understood that the multiple vehicle peripherals that the main operating system can enable may include a sound card, an on-board physical screen, a driver's seat, a sunroof, a USB interface, etc. In this way, the sound card identifier, the on-board physical screen identifier, the driver's seat identifier, the sunroof identifier, and the USB interface identifier, etc. can be transmitted to the slave operating system.

[0055] S202: Creating corresponding virtual configuration modules for configuring working parameters of the plurality of vehicle computer peripherals respectively according to the identifiers of the plurality of vehicle computer peripherals from the operating system.

[0056] Exemplarily, when the identifiers of multiple vehicle peripherals include the identifier of a sound card, the identifier of an on-board physical screen, the identifier of a driver's seat, the identifier of a sunroof, and the identifier of a USB interface, a virtual configuration module for the working parameters corresponding to the sound card, a virtual configuration module for the working parameters corresponding to the on-board physical screen, a virtual configuration module for the working parameters of the driver's seat, a virtual configuration module for the working parameters of the sunroof, and a virtual configuration module for the working parameters of the USB interface are created.

[0057] S203: Obtaining the identification of the target peripheral device and the corresponding working parameters from a pre-stored configuration file of the operating system.

[0058] For example, when the target peripheral is a USB interface, the identification of the USB interface and the corresponding operating parameters are obtained. For example, the operating parameters may include a clock frequency of X Hz, an operating voltage of B volts, and a reset parameter of C.

[0059] S204: When the slave operating system determines that the identifiers of the plurality of vehicle peripherals include the identifier of the target peripheral, the virtual configuration module of the slave operating system associated with the target peripheral transmits the operating parameters corresponding to the identifier of the target peripheral from the slave operating system to the master operating system.

[0060] It can be understood that when the identifiers of multiple vehicle peripherals include the identifier of the USB interface (i.e., the identifier of the target peripheral), the slave operating system confirms that the master operating system can help the slave operating system configure the clock frequency, operating voltage, and reset parameters of the USB interface. Therefore, the clock frequency, operating voltage, and reset parameters of the USB interface can be transmitted to the master operating system.

[0061] Specifically, Figure 3 As shown, S204 can be specifically implemented as follows:

[0062] S301: From a virtual transmission front end in an operating system, writing working parameters corresponding to an identifier of a target peripheral device from a virtual configuration module associated with the target peripheral device into a preset shared memory.

[0063] S302: Sending a target notification message from the virtual transmission front end in the operating system to the main operating system through the virtual machine monitor, where the target notification message is used to indicate that the working parameters corresponding to the identifier of the target peripheral device have been written into the shared memory.

[0064] S303: The virtual transmission backend in the main operating system reads the operating parameters corresponding to the identifier of the target peripheral device from the shared memory in response to the target notification message.

[0065] Further, based on the above S301-S303, when the virtual transmission front-end driver of the slave operating system writes the working parameters corresponding to the identifier of the target peripheral into the shared memory, an exception will be generated and fall into the virtual machine monitor; the virtual machine monitor captures the exception and determines whether it is a read or write request for the shared memory; if so, a virtual interrupt notification (i.e., a target notification message) is sent to the main operating system; the Hyp module on the main operating system receives the corresponding request and forwards it to the corresponding virtual transmission backend; the virtual transmission backend parses the virtual interrupt notification and reads the working parameters corresponding to the identifier of the target peripheral from the shared memory.

[0066] S205: The main operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameters corresponding to the identifier of the target peripheral device.

[0067] Specifically, the specific implementation of S205 can be: the main operating system responds to the validation request from the slave operating system, so that the working parameters corresponding to the identifier of the target peripheral device are effective. The main operating system sends a first notification message to the slave operating system, and the first notification message is used to indicate that the working parameters corresponding to the identifier of the target peripheral device are effective. The main operating system responds to the enable request from the slave operating system, and controls the physical working parameter configuration module to enable the target peripheral device based on the working parameters corresponding to the identifier of the effective target peripheral device. In this way, the target peripheral device can be enabled efficiently and more reliably.

[0068] In some embodiments, the operating parameters include clock frequency and operating voltage, and the physical operating parameter configuration module may include but is not limited to a clock frequency configuration hardware module, an operating voltage configuration hardware module, and a reset parameter configuration module that interact with the main operating system. In this way, the main operating system can control the clock module to configure the clock frequency to the target peripheral and the operating voltage to the target peripheral, so as to enable the target peripheral according to the clock frequency and the operating voltage.

[0069] For example, the clock frequency configuration hardware module configures the clock frequency X Hz corresponding to the USB interface identifier, the working voltage configuration hardware module configures the working voltage B volts corresponding to the USB interface identifier, and the reset parameter configuration hardware module configures the reset parameters corresponding to the USB interface identifier to enable the USB interface.

[0070] It is understandable that when the USB interface is enabled, USB devices such as USB flash drives and USB cameras can be driven to work normally. In this way, the electronic devices (such as USB flash drives and USB cameras) plugged into the USB interface can be accessed based on the configured working parameters of the main operating system.

[0071] In summary, an embodiment of the present application provides a cross-system peripheral enabling method, in which the slave operating system obtains the identification of the target peripheral and the corresponding working parameters from a pre-stored configuration file when detecting power-on. Among them, the target peripheral is a vehicle computer peripheral enabled by the slave operating system. When the identifications of multiple vehicle computer peripherals that can be enabled by the main operating system include the identification of the target peripheral, it means that the main operating system can help the slave operating system configure the working parameters of the target peripheral. Furthermore, based on the virtual configuration module associated with the target peripheral, the working parameters corresponding to the identification of the target peripheral can be transmitted from the slave operating system to the main operating system. Next, based on the main operating system, the physical working parameter configuration module can be controlled to enable the target peripheral based on the working parameters corresponding to the identification of the target peripheral. In this way, target peripherals that are only controlled by the slave operating system alone can be enabled, and the application range is wide.

[0072] In some embodiments, Figure 2 Based on the corresponding embodiment, the above S201 may specifically include:

[0073] Step 1: Send a peripheral quantity inquiry request from the slave operating system to the master operating system.

[0074] Furthermore, before step 1, the method provided in the embodiment of the present application may further include:

[0075] The slave operating system sends a version query request to the main operating system; the slave operating system receives the version information of the protocol for configuring the working parameters of the vehicle peripherals sent by the main operating system in response to the version query request; when the version information of the protocol for configuring the working parameters of the vehicle peripherals is verified, the slave operating system sends a peripheral quantity query request to the main operating system. In this way, the reliability of sending the peripheral quantity query request can be guaranteed.

[0076] Step 2: receiving the number of identifiers of multiple vehicle peripherals that can be enabled, which is sent by the main operating system in response to a peripheral quantity inquiry request, from the operating system.

[0077] Step 3: Based on the number of received identifiers of the multiple vehicle computer peripherals, the slave operating system obtains the identifiers of the multiple vehicle computer peripherals that can be enabled from the main operating system one by one.

[0078] In this way, the identifiers of multiple vehicle peripherals that can be enabled by the main operating system can be accurately and efficiently transmitted to the slave operating system.

[0079] In addition, the embodiment of the present application also provides a cross-system peripheral enabling system, including a main operating system and a slave operating system loaded on the vehicle computer. It should be noted that the basic principle and technical effects of the cross-system peripheral enabling system provided by the embodiment of the present application are the same as those of the above embodiment. For the sake of brief description, for the parts not mentioned in the embodiment of the present application, please refer to the corresponding contents in the above embodiment. Among them, the vehicle computer is connected to a target peripheral for enabling the slave operating system, wherein,

[0080] The main operating system is used to transmit the identifications of multiple vehicle peripherals that can be enabled to the slave operating system after detecting power-on;

[0081] The slave operating system is used to create virtual configuration modules respectively corresponding to the working parameters of the plurality of vehicle computer peripherals according to the identifications of the plurality of vehicle computer peripherals; obtain the identification of the target peripheral and the corresponding working parameters from the pre-stored configuration file; when the slave operating system determines that the identifications of the plurality of vehicle computer peripherals include the identification of the target peripheral, the virtual configuration module of the slave operating system associated with the target peripheral transmits the working parameters corresponding to the identification of the target peripheral from the slave operating system to the master operating system;

[0082] The main operating system is also used to control the physical working parameter configuration module to enable the target peripheral device based on the working parameters corresponding to the identifier of the target peripheral device.

[0083] See also Figure 4 The embodiment of the present application also provides a cross-system peripheral enabling device 400, which is configured in the central control chip of the vehicle computer. The central control chip of the vehicle computer, the physical working parameter configuration module and multiple vehicle computer peripherals are sequentially communicated and connected. The central control chip of the vehicle computer is loaded with a master operating system and a slave operating system, wherein the multiple vehicle computer peripherals include target peripherals for enabling the slave operating system and target peripherals for enabling the slave operating system. The device 400 provided in the embodiment of the present application includes a data transmission unit 401, a module creation unit 402, a data acquisition unit 403 and a peripheral enabling unit 404, wherein,

[0084] The data transmission unit 401 is used to transmit the identifiers of multiple vehicle peripherals that can be enabled by the main operating system to the slave operating system when power is turned on.

[0085] The module creation unit 402 is used to create corresponding virtual configuration modules for configuring working parameters of the plurality of vehicle computer peripherals in the operating system according to the identifiers of the plurality of vehicle computer peripherals.

[0086] The data acquisition unit 403 is used to acquire the identification of the target peripheral device and the corresponding working parameters based on the pre-stored configuration file from the operating system.

[0087] The data transmission unit 401 is also used to transmit the working parameters corresponding to the target peripheral identifier from the slave operating system to the master operating system based on the virtual configuration module associated with the target peripheral when the target peripheral identifier is included in the identifiers of multiple vehicle peripherals.

[0088] The peripheral device enabling unit 404 is used to control the physical working parameter configuration module to enable the target peripheral device based on the working parameters corresponding to the identifier of the target peripheral device based on the main operating system.

[0089] In one possible implementation, the data transmission unit 401 is used to write the working parameters corresponding to the identifier of the target peripheral from the virtual configuration module associated with the target peripheral into a preset shared memory based on a virtual transmission front end in the slave operating system; send a target notification message to the main operating system through a virtual machine monitor based on the virtual transmission front end in the slave operating system, the target notification message being used to indicate that the working parameters corresponding to the identifier of the target peripheral have been written into the shared memory; and read the working parameters corresponding to the identifier of the target peripheral from the shared memory into the main operating system through the virtual transmission back end in the main operating system in response to the target notification message.

[0090] In a possible implementation, the peripheral enabling unit 404 is specifically used to enable the working parameters corresponding to the identifier of the target peripheral device to take effect based on the main operating system responding to the validation request from the slave operating system; sending a first notification message to the slave operating system based on the main operating system, the first notification message is used to indicate that the working parameters corresponding to the identifier of the target peripheral device is effective; based on the main operating system responding to the enable request from the slave operating system, controlling the physical working parameter configuration module to enable the target peripheral device based on the working parameters corresponding to the identifier of the effective target peripheral device.

[0091] In a possible implementation, the operating parameters include a clock frequency and an operating voltage, and the physical operating parameter configuration module includes a clock module and a voltage configuration module. The peripheral enabling unit 404 is specifically configured to control the clock module to configure the clock frequency to the target peripheral and the operating voltage to the target peripheral based on the main operating system, so as to enable the target peripheral according to the clock frequency and the operating voltage.

[0092] In a possible implementation, the data transmission unit 401 is further specifically used to send a peripheral quantity inquiry request from the slave operating system to the main operating system; receive the number of identifiers of multiple enabled vehicle computer peripherals sent by the main operating system in response to the peripheral quantity inquiry request from the slave operating system; and obtain the identifiers of multiple enabled vehicle computer peripherals one by one from the main operating system based on the number of identifiers of multiple vehicle computer peripherals received by the slave operating system.

[0093] In a possible implementation, the data transmission unit 401 is further specifically used to send a version inquiry request from the slave operating system to the main operating system; receive version information of the protocol for configuring the working parameters of the vehicle computer peripherals sent by the main operating system in response to the version inquiry request from the slave operating system; and send a peripheral quantity inquiry request from the slave operating system to the main operating system when the version information of the protocol for configuring the working parameters of the vehicle computer peripherals is verified.

[0094] In a possible implementation, the target peripheral is a USB interface, and the device 400 provided in the embodiment of the present application may also include: a data enabling unit for accessing an electronic device plugged into the USB interface based on the configured working parameters of the main operating system.

[0095] Figure 5 1 is a block diagram of a vehicle computer according to an exemplary embodiment. The vehicle computer may include one or more of the following components: a central control chip 502 of the vehicle computer, a memory 504, a power component 506, a multimedia component 508, an audio component 510, an input / output (I / O) interface 512, a sensor component 514, and a communication component 516.

[0096] The central control chip 502 of the vehicle generally controls the overall operation of the device 500, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The central control chip 502 of the vehicle may include one or more processors 920 to execute instructions to complete all or part of the steps of the above method. For example, the central control chip of the vehicle may include a central processing unit CPU, a graphics processing unit GPU, and a display processor DPU. In addition, the central control chip 502 of the vehicle may include one or more modules (such as a physical transmission channel) to facilitate the interaction between the central control chip 502 of the vehicle and other components. For example, the central control chip 502 of the vehicle may include a multimedia module to facilitate the interaction between the multimedia component 508 and the central control chip 502 of the vehicle.

[0097] The memory 504 is configured to store various types of data to support operations on the device 500. Examples of such data include instructions for any application or method operating on the device 500, data to be displayed, messages, pictures, videos, etc. The memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0098] The power supply component 506 provides power to the various components of the device 500. The power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 500.

[0099] The multimedia component 508 includes a screen that provides an output interface between the device 500 and the user. In an embodiment of the present application, the screen includes multiple in-vehicle physical screens. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor can not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0100] The audio component 510 is configured to output and / or input audio signals. For example, the audio component 510 includes a microphone (MIC), and when the device 500 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 504 or sent via the communication component 516. In some embodiments, the audio component 510 also includes a speaker for outputting audio signals.

[0101] The I / O interface 512 provides an interface between the central control chip 502 of the vehicle computer and the peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button and lock button.

[0102] Sensor assembly 514 includes one or more sensors for providing various aspects of status assessment for device 500. For example, sensor assembly 514 can detect the open / closed state of device 500, the relative positioning of components, such as the display and keypad of device 500, sensor assembly 514 can also detect changes in the position of device 500 or a component of device 500, the presence or absence of user contact with device 500, the orientation or acceleration / deceleration of device 500, and temperature changes of device 500.

[0103] The communication component 516 is configured to facilitate wired or wireless communication between the apparatus 500 and other devices. The apparatus 500 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 516 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.

[0104] In an exemplary embodiment, the apparatus 500 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above methods.

[0105] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 504 including instructions, and the instructions can be executed by a central control chip 502 of a vehicle computer of the apparatus 500 to complete the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device. When the instructions in the non-transitory computer-readable storage medium are executed by a processor of the vehicle computer, the vehicle computer can execute Figure 2 The cross-system peripheral enabling method is shown.

[0106] The present application also provides a computer program product, including a computer program, which, when executed by a processor, Figure 2 The cross-system peripheral enabling method is shown.

[0107] In the above description, the technical details such as the patterning of each layer are not described in detail. However, those skilled in the art should understand that various technical means can be used to form layers, regions, etc. of desired shapes. In addition, in order to form the same structure, those skilled in the art can also design methods that are not completely the same as the methods described above. In addition, although the various embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage.

[0108] Although the preferred embodiments of the present application have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

[0109] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A cross-system peripheral enabling method, characterized in that: A cross-system peripheral enabling system applied to a vehicle computer, the cross-system peripheral enabling system comprising a master operating system and a slave operating system, wherein the vehicle computer is connected to a target peripheral enabled by the slave operating system, and the method comprises: After detecting that power is on, the main operating system transmits the identifiers of multiple vehicle peripherals that can be enabled to the slave operating system; The slave operating system creates corresponding virtual configuration modules for configuring working parameters of the plurality of vehicle computer peripherals according to the identifications of the plurality of vehicle computer peripherals; The slave operating system obtains the identification of the target peripheral device and the corresponding operating parameters from a pre-stored configuration file; When the slave operating system determines that the identifiers of the plurality of vehicle peripherals include the identifier of the target peripheral, the virtual configuration module of the slave operating system associated with the target peripheral transmits the operating parameters corresponding to the identifier of the target peripheral from the slave operating system to the master operating system; The main operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameters corresponding to the identifier of the target peripheral device.

2. The method according to claim 1, characterized in that The virtual configuration module of the slave operating system associated with the target peripheral device transmits the operating parameter corresponding to the identifier of the target peripheral device from the slave operating system to the master operating system, including: The virtual transmission front end in the slave operating system writes the working parameters corresponding to the identifier of the target peripheral device from the virtual configuration module associated with the target peripheral device into a preset shared memory; The virtual transmission front end in the slave operating system sends a target notification message to the master operating system through a virtual machine monitor, wherein the target notification message is used to indicate that the working parameters corresponding to the identifier of the target peripheral device have been written into the shared memory; The virtual transmission backend in the main operating system responds to the target notification message and reads the working parameters corresponding to the identifier of the target peripheral device from the shared memory.

3. The method according to claim 1, characterized in that The main operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameter corresponding to the identifier of the target peripheral device, including: The main operating system responds to the validation request from the slave operating system to validate the working parameters corresponding to the identifier of the target peripheral device; The master operating system sends a first notification message to the slave operating system, where the first notification message is used to indicate that a working parameter corresponding to the identifier of the target peripheral device is effective; In response to the enable request from the slave operating system, the master operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameters corresponding to the valid identifier of the target peripheral device.

4. The method according to claim 1, characterized in that: The operating parameters include a clock frequency and an operating voltage, the physical operating parameter configuration module includes a clock module and a voltage configuration module, and the main operating system controls the physical operating parameter configuration module to enable the target peripheral device based on the operating parameters corresponding to the identifier of the target peripheral device, including: The main operating system controls the clock module to configure the clock frequency to the target peripheral device, and the operating voltage to the target peripheral device, so as to enable the target peripheral device according to the clock frequency and the operating voltage.

5. The method according to claim 1, characterized in that After detecting that power is on, the main operating system transmits the identifications of multiple vehicle peripherals that can be enabled to the slave operating system, including: The slave operating system sends a peripheral quantity inquiry request to the master operating system; The slave operating system receives the number of identifiers of multiple vehicle peripherals that can be enabled and sent by the master operating system in response to the peripheral quantity inquiry request; The slave operating system obtains the identifiers of the multiple vehicle computer peripheral devices that can be enabled one by one from the master operating system based on the number of the identifiers of the multiple vehicle computer peripheral devices received.

6. The method according to claim 5, characterized in that Before the slave operating system sends a peripheral quantity inquiry request to the master operating system, the method further includes: The slave operating system sends a version query request to the master operating system; The slave operating system receives version information of a protocol for configuring working parameters of a vehicle peripheral device, which is sent by the master operating system in response to the version query request; The slave operating system sends a peripheral quantity inquiry request to the master operating system, including: When the version information of the protocol for configuring the working parameters of the vehicle computer peripherals is verified, the slave operating system sends a peripheral quantity inquiry request to the master operating system.

7. The method according to any one of claims 1 to 6, characterized in that: The target peripheral is a USB interface, and after the main operating system controls the physical operating parameter configuration module to enable the target peripheral based on the operating parameters corresponding to the identifier of the target peripheral, the method further includes: The main operating system uses the configured working parameters to access the plug-in electronic device plugged into the USB interface.

8. A cross-system peripheral enabling system, characterized in that: The invention comprises a main operating system and a slave operating system loaded on a vehicle computer, wherein the vehicle computer is connected to a target peripheral device for enabling the slave operating system, wherein: The master operating system is used to transmit the identifiers of multiple vehicle peripherals that can be enabled to the slave operating system after detecting power-on; The slave operating system is used to create virtual configuration modules respectively corresponding to the working parameters of the plurality of vehicle-machine peripherals according to the identifiers of the plurality of vehicle-machine peripherals; obtain the identifier of the target peripheral and the corresponding working parameters from a pre-stored configuration file; when the identifiers of the plurality of vehicle-machine peripherals include the identifier of the target peripheral, the virtual configuration module associated with the target peripheral transmits the working parameters corresponding to the identifier of the target peripheral from the slave operating system to the master operating system; The main operating system is further used to control the physical operating parameter configuration module to enable the target peripheral device based on the operating parameters corresponding to the identifier of the target peripheral device.

9. A vehicle computer, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the cross-system peripheral enabling method according to any one of claims 1 to 7. 10 . A storage medium, when instructions in the storage medium are executed by a processor of a vehicle computer, the vehicle computer is enabled to execute the cross-system peripheral enabling method according to any one of claims 1 to 7.

Images