A vehicle-mounted external device access method and device, a storage medium, and a vehicle

Abstract

The application discloses a vehicle-mounted external device access method and device, a storage medium and a vehicle, and relates to the technical field of external device identity authentication and data security, and comprises the following steps: detecting an external device based on a vehicle-mounted USB interface, creating a virtual sandbox environment, and temporarily mounting the external device based on the virtual sandbox environment; performing access testing on the external device, determining an access testing result; and in response to the access testing result meeting an access condition, determining that the external device accesses a vehicle-mounted system. Through the application, it can be ensured that a crash in a testing stage does not affect a main system, so that more than 99% of vehicle-machine black screen restarts caused by external devices are eliminated, the ability of the system to intelligently identify problem external devices can improve user recognition of vehicle technology, and negative publicity of "vehicle-machine easy to crash" is avoided.

Description

Technical Field

[0001] This application relates to the field of external device authentication and data security technology, and in particular to in-vehicle external device access methods, in-vehicle external device access devices, storage media, and vehicles. Background Technology

[0002] Current in-vehicle infotainment systems generally support connecting external devices (such as USB flash drives) via USB interfaces to achieve functions such as driving record data storage, music playback, image browsing, and video playback. The typical processing flow of existing technology is as follows: when a USB flash drive is inserted into the vehicle's USB interface, the system directly attempts to mount the device and expose it to upper-level media applications for user access.

[0003] Regarding compatibility, existing in-vehicle infotainment systems primarily address USB flash drive differences in two ways: first, by continuously expanding the list of compatible devices through firmware updates; and second, by informing users of recommended USB flash drive specifications (such as FAT32 format, 32GB capacity, etc.) in the user manual. Some high-end models may optimize for specific brand USB flash drives, but overall, they still remain in a passive "plug and play" response mode.

[0004] Because the quality of USB flash drives on the market varies greatly, inferior USB flash drives may cause the car's infotainment system to crash, affecting the user's experience with the system and directly impacting the user's perception of its quality. This results in the after-sales department facing a large number of unnecessary testing requests, wasting manpower, and failing to reproduce the problem. Summary of the Invention

[0005] The purpose of this invention is to provide a method, device, electronic device, storage medium, and vehicle for accessing in-vehicle external devices, at least to solve the problem of vehicle system crashes caused by inferior USB flash drives, and to address the technical issues of reducing unnecessary testing requests from after-sales departments and reducing waste of human resources.

[0006] This invention provides the following solution:

[0007] According to one aspect of the present invention, a method for granting access to an in-vehicle external device is provided, comprising:

[0008] Based on the detection of an external device through the vehicle's USB interface, a virtual sandbox environment is created, and the external device is temporarily mounted based on the virtual sandbox environment;

[0009] Perform an access test on the external device and determine the access test results;

[0010] In response to the access test results meeting the access conditions, the external device is granted access to the vehicle system.

[0011] Preferably, the step of detecting an external device based on the vehicle's USB interface, creating a virtual sandbox environment, and temporarily mounting the external device based on the virtual sandbox environment includes:

[0012] The system detects an external device based on the vehicle's USB interface and establishes a connection with the external device based on the physical access layer of the in-vehicle infotainment system.

[0013] In response to a successful connection with the external device, the device descriptor of the external device is obtained through basic enumeration of the external device via the USB controller.

[0014] Create a virtual sandbox environment using the sandbox manager;

[0015] Based on the device descriptor, the external device is mounted in the virtual sandbox environment.

[0016] Preferably, the step of performing an access test on the external device and determining the access test result includes:

[0017] Obtain the preset admission test dimensions and the judgment criteria corresponding to the admission test dimensions;

[0018] Based on the test engine, in the virtual sandbox environment, the external device is subjected to admission test according to the admission test dimensions, and the dimension test results corresponding to each dimension are determined.

[0019] The admission test results are determined based on the aforementioned criteria for the corresponding dimension test results.

[0020] Preferably, the access test dimensions include: protocol handshake test, read / write speed benchmark test, file system integrity verification, format compatibility check, and voltage / current anomaly detection.

[0021] Preferably, the method further includes:

[0022] In response to the failure of any of the admission test dimensions, it is determined that the admission test result does not meet the admission conditions, and the anomaly type of the external device is determined.

[0023] Uninstall the external device in the virtual sandbox environment, record the exception log, and trigger human-machine interface interaction.

[0024] Preferably, the recording of the exception log and triggering of human-computer interface interaction includes:

[0025] Based on the device descriptor of the external device, the exception type, and the test data of the admission test, the exception log is determined;

[0026] The aforementioned abnormal logs will be recorded locally on the vehicle's infotainment system.

[0027] The non-modal prompt box on the human-machine interface displays the reason for the abnormality of the external device.

[0028] Preferably, determining the access permission of the external device to the vehicle system includes:

[0029] The external device is hot-migrated to user space, mounted, and its icon is displayed on a human-machine interface, allowing media applications to access the external device.

[0030] According to a second aspect of the present invention, an in-vehicle external device access control device is provided, comprising:

[0031] A module is created to detect an external device via the vehicle's USB interface, create a virtual sandbox environment, and temporarily mount the external device based on the virtual sandbox environment.

[0032] The testing module is used to perform access testing on the external device and determine the access testing results;

[0033] An access module is used to determine the access of the external device to the vehicle system in response to the access test result meeting the access conditions.

[0034] According to three aspects of the present invention, an electronic device is provided, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0035] The memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of the on-board external device access method.

[0036] According to four aspects of the present invention, a computer-readable storage medium is provided, comprising: storing a computer program executable by an electronic device, wherein when the computer program is run on the electronic device, the electronic device performs the steps of a vehicle external device access method.

[0037] According to five aspects of the present invention, a vehicle is provided, comprising:

[0038] Electronic devices, steps for implementing a method for access control of vehicle-mounted external devices;

[0039] The processor runs a program that, when running, executes the steps of the vehicle external device access method based on data output from the electronic device.

[0040] Storage medium for storing a program that, when running, executes the steps of the vehicle external device access method on data output from an electronic device.

[0041] The above solution achieves the following beneficial technical effects:

[0042] This application detects external devices based on the vehicle's USB interface, creates a virtual sandbox environment, and temporarily mounts external devices based on the virtual sandbox environment, which can ensure that crashes during the testing phase do not affect the main system.

[0043] This application performs access tests on the external devices to determine the access test results, which can detect abnormal voltage and current and prevent inferior USB flash drives from burning out the vehicle's USB module.

[0044] This application, by responding to the access test results and meeting the access conditions, determines that external devices are allowed to enter the vehicle system. This can eliminate more than 99% of vehicle system black screen restarts caused by external devices. The system's ability to intelligently identify problematic external devices can also enhance users' perception of the vehicle's technological sophistication and avoid the spread of negative word-of-mouth about "vehicle systems being prone to crashing". Attached Figure Description

[0045] Figure 1 This is a flowchart of a vehicle-mounted external device access method provided by one or more embodiments of the present invention.

[0046] Figure 2 This is a schematic diagram of the USB flash drive access and mounting process provided in a specific embodiment of the present invention.

[0047] Figure 3 This is a structural diagram of a vehicle-mounted external device access device provided in one or more embodiments of the present invention.

[0048] Figure 4 This is a block diagram of an electronic device structure for an in-vehicle external device access method provided in one or more embodiments of the present invention. Detailed Implementation

[0049] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0050] Currently, due to the varying quality of external devices on the market, inferior external devices may cause the car's infotainment system to crash due to the following issues:

[0051] For example, insufficient read / write speeds can cause I / O timeouts and exhaust system resources when low-speed external devices attempt high-speed reads from the vehicle's infotainment system. File system anomalies, such as logical bad sectors or non-standard partitions, can lead to kernel reads entering an infinite loop. Poor protocol compatibility, with some external devices experiencing excessive handshake latency or abnormal electrical characteristics, can cause driver layer errors. Abnormal voltage and current, particularly from inferior external devices, can pose a short-circuit or overcurrent risk, potentially burning out the vehicle's USB control chip.

[0052] If any of the above issues occur, it can lead to a black screen on the vehicle's infotainment system. When a faulty external device is plugged in, causing the system to restart after a black screen, the user's immediate perception is that "the infotainment system is broken," rather than realizing that the problem lies with the external device. This disconnect in user experience leads to complaints that directly point to the overall quality of the vehicle. The after-sales department faces a large number of unnecessary inspection requests, and 4S stores spend considerable manpower troubleshooting but are unable to reproduce the problem.

[0053] To address these issues, related technologies provide user manuals recommending specifications, but users rarely read them, and inferior external devices are still widely used. While firmware updates for in-vehicle systems expand the compatibility list, this is a reactive approach that cannot cover all USB drive models. After-sales replacement of USB drives is costly and does not fundamentally resolve the problem. Forced reboots are merely stopgap measures, leading to recurring issues.

[0054] Therefore, addressing the stability issues of in-vehicle infotainment systems caused by substandard USB flash drives, this embodiment proposes a method, device, storage medium, and vehicle for accessing external devices in vehicles. It presents a proactive and preventative external device management mechanism. Through isolation sandbox testing and multi-dimensional access standards, problematic devices are identified and blocked before the USB flash drive is officially used, preventing system crashes caused by USB flash drives at their source. Before the USB flash drive is officially mounted and exposed to upper-layer applications, it undergoes multi-dimensional performance and security testing in an isolated environment. Only external devices that pass all tests are allowed to be used. This transforms passive crash detection into proactive defense, identifying and blocking problematic devices before their official use. Clear prompts guide users to replace external devices, preventing users from misjudging the problem as an in-vehicle infotainment system malfunction and eliminating cognitive biases. By detecting abnormal voltage and current, it prevents substandard USB flash drives from burning out the in-vehicle infotainment system's USB module, reducing unnecessary after-sales service requests due to USB flash drive issues.

[0055] The specific implementation method is as follows.

[0056] Figure 1 This is a flowchart of a vehicle-mounted external device access method provided by one or more embodiments of the present invention.

[0057] like Figure 1 The access methods for vehicle-mounted external devices shown include:

[0058] Step S1: Based on the detection of external devices through the vehicle's USB interface, a virtual sandbox environment is created, and the external devices are temporarily mounted based on the virtual sandbox environment.

[0059] The in-vehicle system, based on the in-vehicle USB driver interface, establishes a connection with the external device at the physical access layer of the in-vehicle infotainment system after detecting that an external device has been plugged into the USB port. Once the connection is confirmed, the USB controller performs basic enumeration of the external device to obtain its device descriptor.

[0060] It should be noted that the sandbox manager has a central processing unit (CPU) and memory usage limit (e.g., CPU cannot exceed 10%, memory cannot exceed 50MB), is isolated from the main system file system, cannot access the vehicle's core data, has an independent driver space, and driver crashes within the sandbox will not affect the main system.

[0061] Based on this, a virtual sandbox environment is created using a sandbox manager, allowing external devices to be mounted within this environment based on device descriptors. This virtual sandbox environment is isolated from the main system file system, cannot access the vehicle's core data, and exists as an independent driver space, ensuring that driver failures within the sandbox do not affect the main system.

[0062] Step S2: Perform an access test on the external device and determine the access test results.

[0063] In this embodiment, the sandbox environment can ensure that crashes during the testing phase do not affect the main system. Therefore, access tests can be performed on external devices in the virtual sandbox environment to determine the access test results.

[0064] The test results include multiple dimensions, such as protocol handshake test results, read / write speed benchmark test results, file system integrity verification results, format compatibility check results, and voltage / current anomaly detection results. Each dimension of the test corresponds to a pre-set judgment criterion, which is used to determine the final test result by judging each test result according to the set judgment criterion.

[0065] By conducting access tests on external devices through multiple access test dimensions in this embodiment, problematic USB drives can be identified from all aspects, including protocol, speed, file system, and electrical characteristics, thus eliminating various anomalies.

[0066] Step S3: In response to the access test results meeting the access conditions, determine that the external device is allowed to enter the vehicle system.

[0067] In this embodiment, the admission condition is that the test results for each dimension meet the preset judgment criteria. That is, if the test results for each dimension pass the test, the external device is determined to be admitted to the vehicle system. Furthermore, the external device can be normally mounted, and its icon can be displayed on the display device's interface. At the same time, the media applications of the vehicle system are allowed to access the external device.

[0068] This embodiment creates a virtual sandbox environment before normally mounting detected external devices, temporarily mounting the external devices to ensure that crashes during the testing phase do not affect the main system. Testing detected external devices in a virtual sandbox environment can eliminate over 99% of in-vehicle infotainment system black screen restarts caused by peripherals, and also prevents USB control chip burnout. In terms of commercial value, it can also reduce sales store testing requests and return / exchange disputes caused by USB flash drive issues, avoiding the spread of negative word-of-mouth regarding "in-vehicle infotainment systems being prone to crashing."

[0069] Figure 2 This is a schematic diagram of the USB flash drive access and mounting process provided in a specific embodiment of the present invention. Figure 2 As shown, after the user inserts the USB flash drive, a connection is established based on the physical access layer of the in-vehicle infotainment system. The USB interface driver detects the device connection and performs basic enumeration to obtain the device descriptor. A virtual sandbox environment is created in the sandbox manager of the in-vehicle infotainment system's access control layer. The detected external device is temporarily mounted in the created virtual sandbox environment, and preset access test dimensions are obtained, along with the test content and corresponding judgment criteria for each dimension. For example, the protocol handshake test includes detecting the USB enumeration process and device descriptor response time, with the judgment criterion being: response time < 500ms. The read / write speed benchmark test includes writing a 4MB test file and reading it, calculating the actual speed: read > 10MB / s, write > 2MB / s. The file system integrity verification test includes scanning the file system structure and detecting bad sectors / illegal indexes, with the judgment criterion being: no serious errors. The format compatibility check test includes identifying the file system type (FAT32 / exFAT / NTFS, etc.), with the judgment criterion being: within the whitelist. Voltage and current anomaly detection: The test content is to monitor the operating current / voltage fluctuation of the USB flash drive. The corresponding judgment criteria are: current <500mA, without sudden rise or fall.

[0070] Furthermore, based on the access control layer's test engine, in the created virtual sandbox environment, access tests are performed on the inserted external device according to preset access test dimensions and their corresponding test content, determining the test results for each dimension. Based on the judgment criteria corresponding to each access test dimension, the policy arbitrator of the access control layer judges the test results for each dimension, thereby determining the access test result for the external device based on the judgment results for each access test dimension. If the access test results for each access test dimension meet their corresponding judgment criteria, the access test for the external device is considered passed. The USB drive is then "hot-migrated" from the sandbox environment to the user space, normally mounted, and its icon is displayed on the interface based on the Human Machine Interface (HMI) interaction layer, allowing the media player in the application service layer to access the external device normally. After the test passes, the USB drive is seamlessly migrated from the sandbox to the user space without requiring the user to unplug and plug it in again.

[0071] If the admission test results of one or more admission test dimensions do not meet their corresponding judgment criteria, the external device is determined to have failed the test. The type of abnormality of the external device is determined, the USB flash drive is immediately unloaded in the sandbox and the power is cut off, the abnormality log is recorded, and the HMI interaction is triggered. The corresponding non-modal prompt box pops up on the display interface based on the HMI interaction layer, displaying the reason for the abnormality of the external device.

[0072] Among the features, a non-modal prompt box can pop up in a prominent position on the vehicle's infotainment display (without obscuring critical information such as navigation and speed). An example message might read: "The connected USB drive has been detected to have insufficient read / write speed, which may cause system instability and has been disabled by the system. Please replace it with a USB drive that meets the vehicle's standards (FAT32 format recommended, read speed of 10MB / s or higher)." This non-modal prompt interaction provides clear guidance to users, directing them to replace the USB drive instead of leading them to misdiagnose a vehicle system malfunction. Users receive a clear indication that the USB drive is not up to standard, rather than being left bewildered by a black screen, thus improving user satisfaction with the vehicle's infotainment system. Furthermore, the non-modal prompt does not obstruct important information such as navigation, ensuring driving safety.

[0073] Finally, based on the device descriptor, anomaly type, and access test data of the external device, the corresponding anomaly log for this anomaly event is determined. This anomaly log (including the USB flash drive's VID / PID, anomaly type, and test data) is recorded in the vehicle's local log. Alternatively, the anomaly log can be uploaded to the cloud-based after-sales system for subsequent compatibility analysis and firmware optimization. Recording the anomaly log provides accurate diagnostic data for after-sales service, feeds back into the USB flash drive compatibility database, accumulates data to optimize compatibility strategies, and guides subsequent firmware optimization.

[0074] The ability of the in-vehicle system in this embodiment to intelligently identify abnormal external devices can also enhance users' perception of the vehicle's technological sophistication.

[0075] For example, in one embodiment, in a low-speed USB flash drive testing scenario, a user inserts an old USB 2.0 flash drive with an actual read speed of only 3MB / s, lower than the minimum 8MB / s requirement for the vehicle's infotainment system to play 1080P video. The infotainment system detects the flash drive insertion, and the sandbox manager creates an isolated environment (i.e., a virtual sandbox environment). The test engine performs read / write speed tests, and the results are: writing a 4MB test file takes 2.1 seconds (approximately 1.9MB / s), and reading takes 1.3 seconds (approximately 3.1MB / s). The policy arbiter determines that the read speed of 3.1MB / s < the threshold of 8MB / s, the test fails, the system unmounts the flash drive in the sandbox, and cuts off the USB power supply. The HMI pops up a message: "The flash drive read speed is too slow, which may cause video playback stuttering. It has been automatically disabled. Please replace it with a high-speed flash drive (recommended read speed of 10MB / s or higher)." The exception log records: VID is 0930, PID is 6545, the exception type is determined to be speed failure, and the read speed is 3.1MB / s.

[0076] In another embodiment, a file system corruption scenario occurs when a user inserts a USB drive that was previously improperly removed from a computer, resulting in logical bad sectors in the file system. The vehicle's infotainment system detects the USB drive insertion, the sandbox manager creates an isolated environment, and the test engine performs a file system integrity check. It finds inconsistent entries in the FAT (File Allocation Table) and attempts to repair it time out. The FAT table is the core of the FAT32 file system, used to record the usage of each cluster. The policy arbitrator determines that the file system has a serious error, and the test fails. The system unmounts the USB drive in the sandbox, cuts off power to the USB, and the HMI displays a message: "A file system error was detected on the USB drive, which may cause the vehicle's infotainment system to crash. It has been automatically disabled. Please connect the USB drive to a computer, format it, and try again." The exception log records: VID 0781, PID 5583, exception type: file system corruption.

[0077] In another embodiment, a user inserts a substandard USB flash drive, posing a short-circuit risk in its internal circuitry. The current surges to 800mA the instant of insertion. The vehicle's infotainment system detects the USB flash drive insertion, and the physical layer detects an abnormal current (>500mA threshold). The access control layer immediately cuts off the USB power, preventing entry into the sandbox testing phase. The HMI displays a message: "Abnormal current detected in the USB flash drive; power has been automatically cut off to protect the infotainment system. Please check if the USB flash drive is damaged." The anomaly log records: the anomaly type is determined to be overcurrent protection, with a current value of 820mA.

[0078] In another embodiment, the user inserts a branded USB flash drive (SanDisk 32GB FAT32 format) that meets the vehicle's infotainment system requirements. The system detects the USB flash drive insertion, the sandbox manager creates an isolated environment, and the test engine executes all access test dimensions. The test results include: protocol response time 120ms, read speed 25MB / s, write speed 15MB / s, no file system anomalies, and stable voltage and current. The policy arbiter determines that all tests have passed, and the system hot-migrates the USB flash drive from the sandbox to user space, mounts it normally, displays the USB flash drive icon on the HMI, media applications can access files normally, and the user can play music / videos normally using the USB flash drive without any abnormal prompts.

[0079] Figure 3 This is a structural diagram of a vehicle-mounted external device access device provided in one or more embodiments of the present invention.

[0080] like Figure 3 The on-board external device access control system shown includes: a creation module, a testing module, and an access control module.

[0081] Create a module to detect external devices based on the vehicle's USB interface, create a virtual sandbox environment, and temporarily mount the external devices based on the virtual sandbox environment;

[0082] The testing module is used to perform access tests on external devices and determine the access test results.

[0083] The access module is used to determine the access permission of external devices to the vehicle system in response to the access test results meeting the access conditions.

[0084] The module is created to detect external devices based on the vehicle's USB interface and establish a connection with the external devices based on the physical access layer of the in-vehicle infotainment system. In response to a successful connection with the external device, the module performs basic enumeration of the external device through the USB controller to obtain the device descriptor of the external device. A virtual sandbox environment is created through the sandbox manager. Based on the device descriptor, the external device is mounted in the virtual sandbox environment.

[0085] The testing module is used to obtain preset access test dimensions and corresponding judgment criteria; based on the testing engine, it performs access tests on external devices in a virtual sandbox environment according to the access test dimensions, and determines the dimension test results corresponding to each dimension; based on the judgment criteria, it judges the corresponding dimension test results to determine the access test results.

[0086] The access testing dimensions include: protocol handshake test, read / write speed benchmark test, file system integrity verification, format compatibility check, and voltage / current anomaly detection.

[0087] The testing module is also used to respond to the failure of any admission test dimension, determine that the admission test result does not meet the admission conditions, and determine the type of abnormality of the external device; uninstall the external device in the virtual sandbox environment, record the abnormality log, and trigger human-machine interface interaction.

[0088] The testing module is used to determine the exception log based on the device descriptor of the external device, the exception type, and the test data of the access test; record the exception log to the vehicle's local system; and display the exception reason for the exception of the external device based on the non-modal prompt box of the human-machine interface.

[0089] The access control module is used to hot-migrate external devices to user space, mount and display icons of external devices on the human-machine interface, and allow media applications to access external devices.

[0090] Figure 4 This is a block diagram of an electronic device structure for an in-vehicle external device access method provided in one or more embodiments of the present invention.

[0091] like Figure 4 As shown, this application provides an electronic device, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0092] The memory stores a computer program that, when executed by a processor, causes the processor to perform steps of a method for admitting access to an onboard external device.

[0093] This application also provides a computer-readable storage medium storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of a vehicle-mounted external device access method.

[0094] This application also provides a vehicle, including:

[0095] Electronic equipment for implementing the steps of the access control method based on vehicle-mounted external devices;

[0096] The processor runs a program that, when running, executes the steps of the vehicle external device access method based on data output from the electronic device.

[0097] Storage medium for storing a program that, when running, executes the steps of the vehicle external device access method on data output from an electronic device.

[0098] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0099] The electronic device comprises a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory. The operating system can be any one or more computer operating systems that control the electronic device through processes, such as Linux, Unix, Android, iOS, or Windows. Furthermore, in this embodiment of the invention, the electronic device can be a smartphone, tablet computer, or other handheld device, or a desktop computer, portable computer, or other electronic device; there is no particular limitation in this embodiment.

[0100] In this embodiment of the invention, the executing entity for electronic device control can be an electronic device itself, or a functional module within an electronic device capable of calling and executing a program. The electronic device can obtain the firmware corresponding to the storage medium. This firmware is provided by the supplier, and different storage media may have the same or different firmware; no limitation is made here. After obtaining the firmware corresponding to the storage medium, the electronic device can write this firmware into the storage medium; specifically, it burns the firmware corresponding to the storage medium into the storage medium. The process of burning the firmware into the storage medium can be implemented using existing technology, and will not be elaborated upon in this embodiment of the invention.

[0101] Electronic devices can also obtain reset commands corresponding to the storage media. The reset commands corresponding to the storage media are provided by the supplier. The reset commands corresponding to different storage media can be the same or different, and no restrictions are imposed here.

[0102] At this time, the storage medium of the electronic device is a storage medium on which the corresponding firmware has been written. The electronic device can respond to the reset command corresponding to the storage medium on which the corresponding firmware has been written, thereby resetting the storage medium on which the corresponding firmware has been written according to the reset command. The process of resetting the storage medium according to the reset command can be implemented by existing technology and will not be described in detail in this embodiment of the invention.

[0103] For ease of description, the above devices are described separately by function as various units and modules. Of course, in implementing this application, the functions of each unit and module can be implemented in one or more software and / or hardware.

[0104] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the meaning consistent with their meaning in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined.

[0105] For the sake of simplicity, the method embodiments are described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0106] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0107] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for granting access to vehicle-mounted external devices, characterized in that, The access method for vehicle-mounted external devices includes: Based on the detection of an external device through the vehicle's USB interface, a virtual sandbox environment is created, and the external device is temporarily mounted based on the virtual sandbox environment; Perform an access test on the external device and determine the access test results; In response to the access test results meeting the access conditions, the external device is granted access to the vehicle system.

2. The method for access control of vehicle-mounted external devices according to claim 1, characterized in that, The process of detecting an external device via the vehicle's USB interface, creating a virtual sandbox environment, and temporarily mounting the external device within the virtual sandbox environment includes: The system detects an external device based on the vehicle's USB interface and establishes a connection with the external device based on the physical access layer of the in-vehicle infotainment system. In response to a successful connection with the external device, the device descriptor of the external device is obtained through basic enumeration of the external device via the USB controller. Create a virtual sandbox environment using the sandbox manager; Based on the device descriptor, the external device is mounted in the virtual sandbox environment.

3. The method for access control of vehicle-mounted external devices according to claim 1, characterized in that, The process of performing an access test on the external device and determining the access test results includes: Obtain the preset admission test dimensions and the judgment criteria corresponding to the admission test dimensions; Based on the test engine, in the virtual sandbox environment, the external device is subjected to admission test according to the admission test dimensions, and the dimension test results corresponding to each dimension are determined. The admission test results are determined based on the aforementioned criteria for the corresponding dimension test results.

4. The method for access control of vehicle-mounted external devices according to claim 3, characterized in that, The access testing dimensions include: protocol handshake test, read / write speed benchmark test, file system integrity verification, format compatibility check, and voltage / current anomaly detection.

5. The method for access control of vehicle-mounted external devices according to claim 4, characterized in that, The method further includes: In response to the failure of any of the admission test dimensions, it is determined that the admission test result does not meet the admission conditions, and the anomaly type of the external device is determined. Uninstall the external device in the virtual sandbox environment, record the exception log, and trigger human-machine interface interaction.

6. The method for access control of vehicle-mounted external devices according to claim 5, characterized in that, The recording of the exception log, triggering human-computer interface interaction, includes: Based on the device descriptor of the external device, the exception type, and the test data of the admission test, the exception log is determined; The aforementioned abnormal logs will be recorded locally on the vehicle's infotainment system. The non-modal prompt box on the human-machine interface displays the reason for the abnormality of the external device.

7. The method for access control of vehicle-mounted external devices according to claim 1, characterized in that, The process of determining the access permission of the external device to the vehicle system includes: The external device is hot-migrated to user space, mounted, and its icon is displayed on a human-machine interface, allowing media applications to access the external device.

8. A vehicle-mounted external device access control device, characterized in that, The vehicle-mounted external device access control includes: A module is created to detect an external device via the vehicle's USB interface, create a virtual sandbox environment, and temporarily mount the external device based on the virtual sandbox environment. The testing module is used to perform access testing on the external device and determine the access testing results; An access module is used to determine the access of the external device to the vehicle system in response to the access test result meeting the access conditions.

9. A computer-readable storage medium, characterized in that, The device stores a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the vehicle external device access method as described in any one of claims 1 to 7.

10. A vehicle, characterized in that, include: An electronic device for implementing the steps of the vehicle-mounted external device access method as described in any one of claims 1 to 7; A processor that runs a program that, when the program is running, performs the steps of the vehicle external device access method as described in any one of claims 1 to 7 from data output by the electronic device. A storage medium for storing a program that, when running, performs the steps of the vehicle external device access method as described in any one of claims 1 to 7 on data output from an electronic device.

Images