Cockpit domain controller, vehicle and memory operation method

Abstract

The present invention relates to a cockpit domain controller, a car and a memory operation method, and relates to the field of storage. The present invention includes: after power-on startup, monitoring the I / O operation of the application on the built-in memory; if it is monitored that an application performs an I / O operation on the built-in memory, determining the data type of the application data corresponding to the I / O operation; if the data type of the application data is a preset data type, modifying the read and write parameters corresponding to the preset data type in the memory to reduce the number of I / O operations. Because the embodiment of the present invention can modify the corresponding read and write parameters in the memory when the application data type is the preset data type when the I / O operation on the built-in memory is performed, so as to reduce the number of I / O operations, thereby improving the life of the built-in memory.

Description

Technical Field

[0001] The present invention relates to the field of storage technology, and in particular to a cockpit domain controller, a car and a memory operation method. Background Art

[0002] When the user starts an application, the application's running data will be read from the built-in storage to the memory, so that the application can run. And during the application running process, the data generated by the application's business will be stored in the memory and written from the memory to the built-in storage. When there are many applications in the cockpit domain controller, when the application's business generates a large amount of data, a large amount of data will be read and written to the built-in storage. However, such a large amount of data reading and writing will accelerate the aging of the built-in storage, resulting in a short life of the built-in storage. Summary of the invention

[0003] The present invention provides a cockpit domain controller, a car and a memory operation method, which can modify the read and write parameters in the memory when the data type of application data is a preset data type, reduce the number of I / O operations, and thus increase the life of the built-in memory.

[0004] In a first aspect, an embodiment of the present invention provides a cockpit domain controller, comprising: a memory, a built-in storage, and a processor;

[0005] The processor is used to monitor the I / O operations of the application on the built-in memory after power-on startup; if it is monitored that an application performs an I / O operation on the built-in memory, determine the data type of the application data corresponding to the I / O operation; if the data type of the application data is a preset data type, modify the read and write parameters corresponding to the preset data type in the memory to reduce the number of I / O operations.

[0006] The cockpit domain controller can modify the read and write parameters corresponding to the preset data type in the memory when the data type of the application data of the application performing the I / O operation is the preset data type, thereby reducing the number of I / O operations and improving the life of the built-in memory.

[0007] In a possible implementation manner, the processor is specifically configured to:

[0008] If the preset data type is a preset local type, modifying a parameter in the memory for controlling the amount of data read from the built-in memory to the memory each time;

[0009] If the preset data type is the first preset service type, a parameter in the memory for controlling a compression ratio of data written from the memory to the built-in memory is modified.

[0010] The above-mentioned cockpit domain controller can, when the data type of application data of the application performing I / O operations is a preset local type, modify the parameters in the memory for controlling the amount of data read from the built-in memory to the memory each time, thereby increasing the amount of data read from the built-in memory to the memory each time, thereby reducing the number of I / O operations; it can also, when the data type of application data of the application performing I / O operations is a first preset service type, modify the parameters in the memory for controlling the compression ratio of data written from the memory to the built-in memory, thereby reducing the amount of data stored in the built-in memory, thereby reducing the number of I / O operations.

[0011] In a possible implementation manner, the processor is further used in at least one of the following manners:

[0012] If the preset data type is not the second preset service type, modifying a parameter in the memory for controlling a time interval for writing dirty data in the memory into the built-in memory;

[0013] If the read / write performance of the built-in memory exceeds the preset read / write performance, modifying the parameters in the memory for controlling the timing of writing dirty data of the memory into the built-in memory;

[0014] If the total capacity of the memory exceeds the preset capacity, the parameters in the memory for controlling the time interval for data in the memory to become dirty data are modified, and the parameters in the memory for controlling the length of the request queue for writing into the built-in memory are modified.

[0015] The above-mentioned cockpit domain controller, when the preset data type is not the second preset business type, modifies the parameters in the memory for controlling the time interval for writing dirty data in the memory into the built-in memory, thereby reducing the unnecessary dirty data being written into the built-in memory, thereby reducing the number of I / O operations; when the read and write performance of the built-in memory exceeds the preset read and write performance, modifies the parameters in the memory for controlling the timing of writing data into the built-in memory, thereby increasing the application data that can be stored in the memory, thereby reducing the number of I / O operations; when the total capacity of the memory exceeds the preset capacity, modifies the parameters in the memory for controlling the time interval for data in the memory to become dirty data, thereby reducing the unnecessary data from becoming dirty data and writing it into the built-in memory, and modifies the parameters in the memory for controlling the length of the request write queue of the built-in memory, and after modifying the parameters, multiple write operations can be merged, thereby reducing the number of I / O operations.

[0016] In a possible implementation manner, the processor is further configured to:

[0017] If it is detected that an application performs an I / O operation on the built-in memory, determine the amount of data written from the memory to the built-in memory by the application performing the I / O operation within a preset time, and if the amount of data written from the memory to the built-in memory by the application performing the I / O operation within the preset time is greater than the preset data amount, prompt the user that the application performing the I / O operation is a malicious application; or

[0018] If it is monitored that an application performs an I / O operation on the built-in memory, it is determined how many times the application performing the I / O operation receives synchronization commands to synchronize the data in the internal memory to the built-in memory within a preset time. If the number is greater than the preset number, the user is prompted that the application performing the I / O operation is a malicious application.

[0019] The above-mentioned cockpit domain controller can, when it is monitored that the amount of data written from the internal memory to the built-in memory by the application performing I / O operations within a preset time is greater than the preset amount of data, or the number of synchronization commands received by the application performing I / O operations within a preset time to synchronize the data in the internal memory to the built-in memory is greater than the preset number of times, prompt the user that the application performing I / O operations is a malicious application, and issue an early warning to the user, warning that malicious applications are occupying the built-in memory.

[0020] In a possible implementation manner, the processor is further configured to:

[0021] If the memory stores data generated by a preset service of a preset application, and an external memory is inserted into the cockpit domain controller, the data generated by the preset service of the preset application is written from the memory to the external memory; and / or

[0022] If the installation data of the third-party application is stored in the memory and the external memory is inserted into the cockpit domain controller, the installation data of the third-party application is written from the memory to the external memory.

[0023] The cockpit domain controller can store data generated by preset services of preset applications or installation data of third-party applications in the memory, and use an external memory to store the data, thereby reducing the number of I / O operations.

[0024] In a second aspect, an embodiment of the present invention provides an automobile, comprising a cockpit domain controller located inside the automobile body, and one or more of the following hardware: a driving recorder located on the rearview mirror of the automobile; a main display located on the center console; a rear pillow display located on the back seat; sensors located around the automobile body; a TBOX located inside the automobile body; and a projector located on the automobile body in front of the driver;

[0025] The cockpit domain controller includes a memory, a built-in memory and a processor; the processor is used to monitor the I / O operation of the application on the built-in memory after power-on startup; if it is monitored that an application performs an I / O operation on the built-in memory, determine the data type of the application data corresponding to the I / O operation; if the data type of the application data is a preset data type, modify the read and write parameters corresponding to the preset data type in the memory to reduce the number of the I / O operations;

[0026] The driving recorder is connected to the cockpit domain controller, and the processor is also used to control the start-up of the driving recorder, and the driving recorder is used to collect images in front of the vehicle after starting;

[0027] The sensor is connected to the cockpit domain controller, and the processor is further used to control the start-up of the sensor, and the sensor is used to collect images around the vehicle body after start-up and send them to the cockpit domain controller;

[0028] The main display is connected to the cockpit domain controller, the processor is further used to obtain a user interface according to the application data, and the main display is used to display the user interface and the image around the vehicle body;

[0029] The rear pillow display is connected to the cockpit domain controller, and the rear pillow display is used to display the user interface;

[0030] The TBOX is connected to the cockpit domain controller, and is used for the cockpit domain controller to perform network communication with other electronic devices;

[0031] The projector is connected to the cockpit domain controller, the processor is also used to obtain the driving information of the car, and the projector is used to project the driving information of the car onto the front windshield of the car.

[0032] In a third aspect, an embodiment of the present invention provides a memory operation method, which is applied to a cockpit domain controller, including:

[0033] After power-on, monitor the application's I / O operations on the built-in memory;

[0034] If it is detected that an application performs an I / O operation on the built-in memory, determining the data type of the application data corresponding to the I / O operation;

[0035] If the data type of the application data is a preset data type, the read and write parameters corresponding to the preset data type in the memory are modified to reduce the number of I / O operations.

[0036] In a possible implementation, the modifying the read / write parameters corresponding to the preset data type in the memory includes:

[0037] If the preset data type is a preset local type, modifying a parameter in the memory for controlling the amount of data read from the built-in memory to the memory each time;

[0038] If the preset data type is the first preset service type, a parameter in the memory for controlling a compression ratio of data written from the memory to the built-in memory is modified.

[0039] In a possible implementation manner, the method further includes at least one of the following manners:

[0040] If the preset data type is not the second preset service type, modifying a parameter in the memory for controlling a time interval for writing dirty data in the memory into the built-in memory;

[0041] If the read / write performance of the built-in memory exceeds the preset read / write performance, modifying the parameters in the memory for controlling the timing of writing dirty data of the memory into the built-in memory;

[0042] If the total capacity of the memory exceeds the preset capacity, the parameters in the memory for controlling the time interval for data in the memory to become dirty data are modified, and the parameters in the memory for controlling the length of the request queue for writing into the built-in memory are modified.

[0043] In a possible implementation, after the monitoring application detects the I / O operation of the built-in memory, the method further includes:

[0044] If it is detected that an application performs an I / O operation on the built-in memory, determine the amount of data written from the memory to the built-in memory by the application performing the I / O operation within a preset time, and if the amount of data written from the memory to the built-in memory by the application performing the I / O operation within the preset time is greater than the preset data amount, prompt the user that the application performing the I / O operation is a malicious application; or

[0045] If it is monitored that an application performs an I / O operation on the built-in memory, it is determined how many times the application performing the I / O operation receives synchronization commands to synchronize the data in the internal memory to the built-in memory within a preset time. If the number is greater than the preset number, the user is prompted that the application performing the I / O operation is a malicious application.

[0046] In a possible implementation, after power-on startup, the method further includes:

[0047] If the memory stores data generated by a preset service of a preset application, and an external memory is inserted into the cockpit domain controller, the data generated by the preset service of the preset application is written from the memory to the external memory; and / or

[0048] If the installation data of the third-party application is stored in the memory and the external memory is inserted into the cockpit domain controller, the installation data of the third-party application is written from the memory to the external memory.

[0049] In a fourth aspect, the present application further provides a computer storage medium on which a computer program is stored, and when the program is executed by a processing unit, the steps of the memory operation method described in the second aspect are implemented.

[0050] In addition, the technical effects brought about by any implementation method in the second to fourth aspects can refer to the technical effects brought about by different implementation methods in the first aspect, and will not be repeated here.

[0051] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present invention, and together with the description are used to explain the principles of the present invention, and do not constitute improper limitations of the present invention.

[0053] Figure 1 is a structural block diagram of an automobile interior provided by an embodiment of the present invention;

[0054] Figure 2 is a schematic diagram of the functions of a vehicle-mounted cockpit domain controller provided by an embodiment of the present invention;

[0055] Figure 3 is a flow chart of a memory operation method provided by an embodiment of the present invention;

[0056] Figure 4 is a schematic diagram of a complete method for memory operation provided by an embodiment of the present invention;

[0057] Figure 5 is a flow chart of a method for determining whether a running application is a malicious application provided by an embodiment of the present invention;

[0058] Figure 6 is a flow chart of another method for determining whether a running application is a malicious application provided by an embodiment of the present invention;

[0059] Figure 7 is a flow chart of a method for storing in an external memory provided by an embodiment of the present invention;

[0060] Figure 8 It is a flowchart of another method for storing in an external memory provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0061] In order to enable ordinary persons in the art to better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings.

[0062] It should be noted that the terms "first", "second", etc. in the description of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0063] The application scenarios described in the embodiments of the present invention are intended to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation on the technical solutions provided by the embodiments of the present invention. It is known to those skilled in the art that with the emergence of new application scenarios, the technical solutions provided by the embodiments of the present invention are also applicable to similar technical problems. In the description of the present invention, unless otherwise specified, the meaning of "multiple" is

[0064] At present, with the increase of applications and functions in cockpit domain controllers, a large amount of data will be read and written to the built-in memory. Such a large amount of data reading and writing will accelerate the aging of the built-in memory, resulting in a short life of the built-in memory. In particular, the automotive grade standard requires that the life of the whole vehicle is at least ten years, and the corresponding on-board built-in memory of the vehicle must also meet this standard. In this invention, through a variety of tuning strategies, based on the existing storage technology, the number of I / O operations during the operation of the vehicle is reduced, and the service life of the built-in memory is increased. The specific contents are as follows:

[0065] An embodiment of the present invention provides a cockpit domain controller, which includes a memory, a built-in memory, a processor, and an external interface. The external memory can be connected to the external interface.

[0066] The memory is used to store temporary data, and the built-in memory is used to store permanently saved data. Only data stored in the memory can be used directly by the processor. Therefore, when the application is running, it is necessary to read the application's running data from the built-in memory to the memory. When the application executes various services, the data generated by the service can be stored in the memory first, and then written from the memory to the built-in memory. Among them, reading data from the built-in memory is an O (output) operation, and writing data to the built-in memory is an I (input) operation.

[0067] The external memory is a pluggable memory, such as an SD card, and the built-in memory is an embedded memory, such as an eMMC (Embedded Multi Media Card).

[0068] Exemplarily, an embodiment of the present invention further provides a car, including a cockpit domain controller located inside the car body, and one or more of the following hardware: a driving recorder located on the rearview mirror of the car; a main display located on the center console; a rear pillow display located on the back seat; sensors located around the car body; a TBOX located inside the car body; a projector located on the car body in front of the driver;

[0069] The cockpit domain controller includes a memory, a built-in memory and a processor; the processor is used to monitor the I / O operation of the application on the built-in memory after power-on startup; if it is monitored that an application performs an I / O operation on the built-in memory, determine the data type of the application data corresponding to the I / O operation; if the data type of the application data is a preset data type, modify the read and write parameters corresponding to the preset data type in the memory to reduce the number of the I / O operations;

[0070] Exemplarily, an embodiment of the present invention provides an internal structure of a car, such as Figure 1 As shown, the cockpit domain controller 100 in the car is respectively connected to the driving recorder 101, the main display 102, the rear pillow display 103, the sensor 104, the TBOX 105, and the projector 106;

[0071] The following is combined with Figure 1 The various hardware connected to the cockpit domain controller 100 are introduced in detail:

[0072] The driving recorder 101 is arranged on the rearview mirror of the car, and is shaped like Figure 2 As shown, the processor of the cockpit domain controller 100 can be used to control the start of the driving recorder, and the driving recorder 100 is used to collect the image in front of the vehicle after starting. It can also be displayed, and the collected image in front of the vehicle is stored in the built-in memory in the cockpit domain controller 100.

[0073] The sensor 104 is connected to the cockpit domain controller 100. The processor in the cockpit domain controller 100 is also used to control the start of the sensor 104. The sensor 104 is used to collect images around the vehicle body after start-up and send them to the cockpit domain controller 104.

[0074] The processor in the cockpit domain controller 100 is also used to obtain a user interface based on application data, and the main display is used to display the user interface and the images around the vehicle body; the main display can also be used to display the air conditioning control interface, the audio control interface, etc.

[0075] Exemplarily, the sensors 104 are arranged around the outside of the vehicle body, and the number of sensors can be one or more. When the vehicle includes multiple sensors 104, the multiple sensors 104 can obtain images around the entire vehicle. The obtained images are sent to the cockpit domain controller 100, and the cockpit domain controller 100 combines the obtained images with the three-dimensional image of the vehicle to obtain a 360-degree panoramic image, such as Figure 2 As shown, the 360-degree panoramic image is sent to the main display 102 for display. The 360-degree panoramic image can be stored in the built-in memory of the cockpit domain controller 100.

[0076] The rear pillow display 103 is shaped like Figure 2 As shown, it is used to display the user interface, and can also display the control interface of the rear air conditioner, the control interface of the rear audio system, etc. Among them, the running data of the application displayed by the main display 102 and the auxiliary display 103 can be stored in the built-in memory of the cockpit domain controller 100.

[0077] TBOX (Telematics BOX) 105 is a box with communication function and Android operating system. It is used for network communication between cockpit domain controller 100 and other electronic devices, so as to realize the connection of automobile to 4G / 5G network. Figure 2 As shown, it is possible to realize other electronic devices controlling the cockpit domain controller.

[0078] The processor in the cockpit domain controller 100 is also used to obtain the driving information of the car, and the projector 106 is used to project the driving information of the car onto the front windshield of the car, as shown in FIG. Figure 2 Specifically, the cockpit domain controller 100 can obtain driving information such as vehicle speed and navigation, and then send it to the projector 106 so that the projector 106 can project and display the driving information. The driving information can be stored in the built-in memory of the cockpit domain controller 100.

[0079] The cockpit domain controller of the car can be connected to the digital instrument panel, which is used to display driving information such as vehicle speed and rotation speed during driving. The appearance of the digital instrument panel can be as follows: Figure 2 The cockpit domain controller can store the car's driving information in the digital instrument panel in the built-in memory.

[0080] In addition to the above functions, the car can also have an on-board comprehensive information processing system, such as: ADAS (Advanced Driving Assistance System) and an on-board entertainment system, and the data generated by the advanced assistance system and the on-board entertainment system can also be stored in the built-in memory of the cockpit domain controller 100.

[0081] Among them, the ADAS of the cockpit domain controller can also be called the autonomous driving function:

[0082] Autonomous driving is divided into six levels: L0, L1, L2, L3, L4, and L5. The specific classification is as follows:

[0083] Level L0: represents traditional human driving without any autonomous driving. The car only gives partial warnings, such as speed, distance to the vehicle in front, blind spots, etc.

[0084] Level 1: The steering wheel and acceleration and deceleration provide an automatic operation, such as adaptive cruise control or lane keeping.

[0085] L2 level: The steering wheel and acceleration and deceleration provide two automatic operations, such as adaptive cruise control + lane keeping.

[0086] All three levels above require the driver to monitor the environment and make decisions quickly. The car itself only has actions similar to "conditioned reflexes" without any "thinking".

[0087] L3 level: All driving operations are performed automatically, and the system can observe road conditions (such as traffic lights, pedestrians, roadside conditions, etc.) and make correct decisions, but the system's requests require responses from the driver. L3 level means that the system has a preliminary "thinking ability" and can be fully autonomous most of the time, but it needs humans to "escort" it, just like students in a driving school who can already drive on the road, but need a coach sitting next to them.

[0088] L4 level: The system automatically makes all driving operations and autonomous decisions, and the driver does not need to provide a response, but it is generally limited to its driving area, such as public transportation, logistics, taxis, etc. L4 level means that the two vehicles can be completely autonomous on the road without human accompaniment, so devices such as steering wheels, accelerators, and brakes can also be cancelled.

[0089] L5: Full-domain autonomous driving. L5 autonomous driving cars are like experienced human drivers. They can drive autonomously in all regions and all weather conditions, and can expertly respond to changes in geography, climate and other environments.

[0090] Exemplarily, the built-in memory of the cockpit domain controller is eMMC and the external memory is an SD card.

[0091] In order to reduce the number of I / O operations and improve the life of the built-in memory of the cockpit domain controller, the vehicle-mounted central control can monitor the I / O operations of the application on the built-in storage device after power-on and, if it is detected that an application performs an I / O operation on the built-in memory, determine the data type of the application data corresponding to the I / O operation;

[0092] If the data type of the application data corresponding to the I / O operation is a preset local type, the parameters in the memory used to control the amount of data read from the eMMC to the memory each time are modified, so that the amount of data read from the eMMC to the memory at one time becomes larger, thereby reducing the number of I / O operations from the eMMC to the memory.

[0093] If the data type of the application data corresponding to the I / O operation is the first preset business type, the parameters in the memory used to control the compression ratio of the data written from the memory to the eMMC are modified, so that the data can be merged with other data and written into the eMMC, thereby reducing the number of I operations from the memory to the eMMC.

[0094] If it is detected that an application performs an I / O operation on the built-in memory, the amount of data written from the memory to the eMMC by the application performing the I / O operation within the preset time is determined. If the amount of data written from the memory to the eMMC by the application performing the I / O operation within the preset time is greater than the preset amount of data, the user is prompted that the application performing the I / O operation is a malicious application; or the number of synchronization commands received by the application performing the I / O operation within the preset time to synchronize the data in the memory to the eMMC is determined. If the number is greater than the preset number, the user is prompted that the application performing the I / O operation is a malicious application. In this way, the user can delete the malicious application to avoid continuing to write the data of the malicious application to the eMMC, thereby reducing the number of I operations from the memory to the eMMC.

[0095] If the preset data type is not the second preset service type, a parameter in the memory for controlling the time interval for writing dirty data in the memory to the eMMC is modified; thereby, some deleted dirty data will not be written to the eMMC, thereby alleviating unnecessary data from being written to the eMMC, thereby reducing the number of I operations from the memory to the eMMC;

[0096] If the read and write performance of the eMMC exceeds the preset read and write performance, the parameters in the memory used to control the timing of writing dirty data into the eMMC are modified. When the amount of data stored in the memory accounts for a large percentage of the total amount, the memory can store more data, thereby reducing the number of I operations from the memory to the eMMC.

[0097] If the total capacity of the memory exceeds the preset capacity, the parameters in the memory for controlling the time interval for the data in the memory to become dirty data are modified, so that some deleted data will not become dirty data and thus be written to the eMMC, effectively avoiding writing unnecessary data to the eMMC, thereby reducing the number of I operations from the memory to the eMMC;

[0098] At the same time, when the total capacity of the memory exceeds the preset capacity, it is also necessary to modify the parameters in the memory used to control the request queue length for writing to the eMMC, so that the write operations can be merged and the number of I operations from the memory to the eMMC can be reduced.

[0099] If the memory stores data generated by the preset service of the preset application and an SD card is inserted in the cockpit domain controller, the data generated by the preset service of the preset application is written from the memory to the SD card. The data originally written to the eMMC is written to the SD card, thereby reducing the number of I operations from the memory to the eMMC.

[0100] Similarly, if the memory stores the installation data of a third-party application and an SD card is inserted into the cockpit domain controller, the installation data of the third-party application is written from the memory to the SD card. The data originally written to the eMMC is written to the SD card, thereby reducing the number of I operations from the memory to the eMMC.

[0101] Based on the above disclosed contents, the present invention is described in detail below.

[0102] Combination Figure 3 As shown, an embodiment of the present invention provides a memory operation method, which is applied to the cockpit domain controller provided above, and specifically includes:

[0103] S300: After power-on, monitor the I / O operation of the application on the built-in memory;

[0104] S301: If it is detected that an application performs an I / O operation on the built-in memory, determine the data type of the application data corresponding to the I / O operation;

[0105] If it is detected that no application performs I / O operations on the built-in memory, the monitoring continues until the power is turned off.

[0106] S302: If the data type of the application data is a preset data type, modify the read and write parameters corresponding to the preset data type in the memory to reduce the number of I / O operations.

[0107] If the data type of the application data is not the preset data type, the read and write parameters in the current memory remain unchanged.

[0108] Among them, the data type of application data can be a local type or a business type; the local type is data stored in the built-in memory, such as data that the application can run, music or videos stored locally, and the business type is data generated by the application when performing certain businesses, such as OTA (Over-the-Air Technology) system upgrade packages, updated maps in navigation applications, videos viewed online in video applications, music listened to online in music applications, and driving conditions recorded in a driving recorder during vehicle driving.

[0109] If the preset data type is a preset local type, it means that local data needs to be started, that is, the preset local type application data needs to be read from the built-in memory into the memory. If you want to reduce the number of O operations, you can increase the amount of preset local type application data that can be read from the built-in memory into the memory at one time after modifying the parameters, thereby achieving the purpose of reducing the number of O operations. When the local type is preset, not all local types are preset data types, but some preset local types, for example, the running program of the music application itself, the running program of the video application itself, the running program of the navigation application itself, the local application in the music application, the local video in the video application, the local map in the navigation application, and so on. The preset can be determined according to the specific application installed in the cockpit domain controller, and the present invention does not make specific restrictions on this.

[0110] Specifically, if the preset data type is a preset local type, a parameter in the memory for controlling the amount of data read from the built-in storage to the memory each time is modified;

[0111] The parameter used to control the amount of data read from the built-in memory to the main memory each time is / sys / block / mmcblk0 / queue / read_ahead_kb.

[0112] The preset local type can include music, videos, navigation maps, etc. stored locally. For example, when reading a navigation map in a navigation application, the value of the parameter / sys / block / mmcblk0 / queue / read_ahead_kb can be modified, and when playing music or videos in a multimedia application, the value of the parameter / sys / block / mmcblk0 / queue / read_ahead_kb can be modified.

[0113] For modification, a specific parameter value can be modified. For example, the default value of the parameter / sys / block / mmcblk0 / queue / read_ahead_kb is 128kb, and the modified value of the parameter / sys / block / mmcblk0 / queue / read_ahead_kb is 2048kb. Specifically, if the preset data type is a preset local type, the value of the parameter in the memory for controlling the amount of data read from the built-in memory to the memory each time is modified.

[0114] For example, if the data type of the application data is the preset local type, the value of / sys / block / mmcblk0 / queue / read_ahead_kb is modified from 128kb to 2048kb; if the data type of the application data is not the preset local type, the value of / sys / block / mmcblk0 / queue / read_ahead_kb is kept at 128kb. Optionally, after the modification, if it is detected that the data type of the application data is not the preset local type, the value of / sys / block / mmcblk0 / queue / read_ahead_kb is modified from 2048kb to 128kb.

[0115] If the preset data type is the first preset service type, a parameter in the memory for controlling the compression ratio of the data stored in the memory is modified.

[0116] The parameter used to control the compression ratio of data stored in memory is the encoding format.

[0117] If the preset data type is the first preset business type, it means that the application is generating data and needs to be written from the memory to the built-in memory. After modifying the parameters, for the same data in the memory, the modified encoding format can be used to compress the file to a smaller size, so that the amount of data written to the built-in memory is reduced, so that the data can be written to the built-in memory together with other data, reducing the number of I operations.

[0118] The first preset service type is the driving service type in the driving recorder.

[0119] For modification, for example, if the preset data type is a driving service type, the encoding format is modified to the H265 encoding format.

[0120] According to the above process, the present invention provides a complete method for memory operation. Figure 4 As shown, including:

[0121] S400: After power-on, monitor the I / O operations of the application on the built-in memory;

[0122] S401: If it is detected that an application performs an I / O operation on the built-in memory, determine the data type of the application data corresponding to the I / O operation;

[0123] S402: If the preset data type is a preset local type, modifying a parameter in the memory for controlling the amount of data read from the built-in memory to the memory each time;

[0124] S403: If the preset data type is a preset business type, modify the parameters in the memory for controlling the compression ratio of the data stored in the memory.

[0125] S404: If the data type of the application data is not the preset data type, the read and write parameters in the current memory are kept unchanged.

[0126] In order to reduce I / O operations, the embodiment of the present invention further includes:

[0127] If the read / write performance of the built-in memory exceeds the preset read / write performance, a parameter in the memory for controlling the timing of writing dirty data of the memory into the built-in memory is modified.

[0128] The preset read / write performance is, for example, 50 MB / s. The parameters for controlling the timing of writing dirty data of the memory into the built-in memory are / proc / sys / vm / dirty_ratio and / proc / sys / vm / dirty_background_ratio.

[0129] / proc / sys / vm / dirty_ratio specifies when the dirty data in the file system cache reaches a certain percentage of the system memory (e.g. 10%), the system has to start processing the dirty data in the cache (because there is already a lot of dirty data at this time, in order to avoid data loss, some dirty data needs to be flushed to the built-in memory);

[0130] The parameter / proc / sys / vm / dirty_background_ratio specifies that when the dirty data cached by the file system reaches a certain percentage of the system's memory (such as 5%), the background write-back processes such as pdflush / flush / kdmflush will be triggered to run, and a certain amount of cached dirty data will be asynchronously flushed to the built-in memory.

[0131] For example, when the read / write performance of the built-in memory exceeds 50 MB / s, the value of / proc / sys / vm / dirty_ratio is modified to 60%, and the value of / proc / sys / vm / dirty_background_ratio is modified to 40%. When the read / write performance of the built-in memory does not exceed 50 MB / s, the value of / proc / sys / vm / dirty_ratio is modified to 40%, and the value of / proc / sys / vm / dirty_background_ratio is modified to 20%.

[0132] Among them, the timing for modifying / proc / sys / vm / dirty_ratio and / proc / sys / vm / dirty_background_ratio can be to detect the read and write performance of the built-in memory and the values ​​of the above two parameters once after each power-on. If they exceed 50MB / s, and the two values ​​are 40% and 20% respectively for / proc / sys / vm / dirty_ratio, modify the value of / proc / sys / vm / dirty_ratio to 60% and modify the value of / proc / sys / vm / dirty_background_ratio to 40%. If it does not exceed 50 MB / s, and the two values ​​are / proc / sys / vm / dirty_ratio is 60% and / proc / sys / vm / dirty_background_ratio is 40%, then change the value of / proc / sys / vm / dirty_ratio to 40% and the value of / proc / sys / vm / dirty_background_ratio to 20%.

[0133] Of course, the modification of / proc / sys / vm / dirty_ratio and / proc / sys / vm / dirty_background_ratio can be set in the upgrade package. When upgrading, the values ​​of / proc / sys / vm / dirty_ratio and / proc / sys / vm / dirty_background_ratio are modified to match the read and write performance of the built-in memory.

[0134] If the total capacity of the memory exceeds the preset capacity, the parameters in the memory for controlling the time interval for data in the memory to become dirty data are modified, and the parameters in the memory for controlling the length of the request queue for writing into the built-in memory are modified.

[0135] The preset capacity is 2 GB. The parameter used to control the time interval for data in the memory to become dirty data is / proc / sys / vm / dirty_expire_centisecs, and the parameter used to control the length of the request queue for writing to the built-in memory is / sys / block / sda / queue / nr_requests.

[0136] The parameter / proc / sys / vm / dirty_expire_centisecs refers to the time when data becomes dirty data. Specifically, after declaring that the data in the Linux kernel write buffer is too "old", the data will be turned into dirty data. Only after it becomes dirty data, the pdflus process will start to consider writing it to the built-in memory. The unit is 1 / 100 second. This parameter mainly depends on the total capacity of the memory. If the total capacity of the memory is relatively large and can store more data, then the value of / proc / sys / vm / dirty_expire_centisecs becomes larger, so that users can have some reaction time to delete unwanted data, such as data withdrawn during chat. When the time interval is relatively large, the unwanted data can be directly deleted from the memory and will not be written to the built-in memory, thereby reducing the number of I operations. Therefore, when the total capacity of the memory is greater than 2GB, the value of / proc / sys / vm / dirty_expire_centisecs is 500, and when the total capacity of the memory is not greater than 2GB, the value of / proc / sys / vm / dirty_expire_centisecs is 200.

[0137] The parameter / sys / block / sda / queue / nr_requests limits the length of the request queue for writing to the built-in storage. The larger the queue length for writing to the built-in storage, the more write operations can be merged. Therefore, when the total memory capacity is greater than 2GB, the value of / sys / block / sda / queue / nr_requests is 512. When the total memory capacity is not greater than 2GB, the value of / sys / block / sda / queue / nr_requests is 128.

[0138] Among them, the timing for modifying / proc / sys / vm / dirty_expire_centisecs and / sys / block / sda / queue / nr_requests can be to detect the total memory capacity and the values ​​of the above two parameters once after each power-on. If they exceed 2GB, and the two values ​​are / proc / sys / vm / dirty_expire_centisecs is 200 and / sys / block / sda / queue / nr_requests is 128, then modify the value of / proc / sys / vm / dirty_expire_centisecs to 500 and the value of / sys / block / sda / queue / nr_requests to 512. If the size does not exceed 2 GB, and the value of / proc / sys / vm / dirty_expire_centisecs is 500 and the value of / sys / block / sda / queue / nr_requests is 512, change the value of / proc / sys / vm / dirty_expire_centisecs to 200 and the value of / sys / block / sda / queue / nr_requests to 128.

[0139] Of course, the changes to / proc / sys / vm / dirty_expire_centisecs and / sys / block / sda / queue / nr_requests can be set in the upgrade package. When upgrading, modify the values ​​of / proc / sys / vm / dirty_expire_centisecs and / sys / block / sda / queue / nr_requests to match the total capacity of the memory.

[0140] Exemplarily, an embodiment of the present invention further provides that, if the preset data type is not the second preset service type, the value of a parameter in the memory for controlling the time interval for writing dirty data in the memory into the built-in memory is modified;

[0141] The parameter / proc / sys / vm / dirty_writeback_centisecs is used to control the time interval for writing dirty data in the memory to the built-in storage.

[0142] If the preset data type is the second preset business type, it means that the application is generating data at this time, and the application data of the preset business type needs to be written back from the memory to the built-in memory. At this time, using a relatively small parameter value can reduce the time interval for each write back from the memory to the built-in memory, and can write useful data to the built-in memory faster.

[0143] If the preset data type is not the second preset business type, the value of the parameter in the memory used to control the time interval for writing dirty data in the memory into the built-in memory is modified. The modified value is relatively large, thereby increasing the time interval for writing back to the built-in memory from the memory each time, which can avoid writing deleted data to the built-in memory and reduce the operation of I.

[0144] The second preset service type can be an upgrade service of the OTA system, an update map service in a navigation application, a video playback service, a music playback service, or a driving service in a driving recorder. For example, if the data type of the application data is not an upgrade service of the OTA system, the value of / proc / sys / vm / dirty_writeback_centisecs is modified to increase the time interval for writing the upgrade package data of the OTA system from the memory to the built-in memory; if the data type of the application data is not a video playback service, the value of / proc / sys / vm / dirty_writeback_centisecs is modified to increase the time interval for writing the video data from the memory to the built-in memory.

[0145] For modification, a specific parameter value can be modified. For example, if the data type of the application data is the second preset service type, the value of the parameter / proc / sys / vm / dirty_writeback_centisecs is 500, with a unit of 1 / 100 seconds. If the data type of the application data is not the second preset service type, the value of the modified parameter / proc / sys / vm / dirty_writeback_centisecs is 1000, with a unit of 1 / 100 seconds.

[0146] For example, after power-on, if / proc / sys / vm / dirty_writeback_centisecs is not 1000, the value of / proc / sys / vm / dirty_writeback_centisecs can be first modified to 1000, and then if an I / O operation is detected, it is determined that the data type of the application data corresponding to the I / O operation is the second preset business type, and the value of / proc / sys / vm / dirty_writeback_centisecs is changed to 500. If it is continued to be detected that it is not the second preset business type, the value of / proc / sys / vm / dirty_writeback_centisecs is changed to 1000.

[0147] It should be noted that the second preset service type mentioned here and the first preset service type when modifying the compression ratio parameter can be the same service type or different service types. The present invention does not impose any specific limitation.

[0148] Of course, the modification of / proc / sys / vm / dirty_writeback_centisecs can be set in the upgrade package. When upgrading, the value of / proc / sys / vm / dirty_writeback_centisecs is modified to 1000, that is, the preset data type is not the value corresponding to the second preset business type.

[0149] In order to prevent malicious applications from increasing the number of I / O operations, the embodiment of the present invention also provides a function of monitoring malicious applications, specifically:

[0150] If it is detected that an application performs an I / O operation on the built-in memory, determine the amount of data written from the memory to the built-in memory by the application performing the I / O operation within a preset time, and if the amount of data written from the memory to the built-in memory by the application performing the I / O operation within the preset time is greater than the preset amount of data, prompt the user that the application performing the I / O operation is a malicious application; or

[0151] If it is monitored that an application performs an I / O operation on the built-in memory, it is determined how many times the application performing the I / O operation receives synchronization commands to synchronize the data in the internal memory to the built-in memory within a preset time. If the number is greater than the preset number, the user is prompted that the application performing the I / O operation is a malicious application.

[0152] Exemplarily, when monitoring malicious applications, the command: storaged –u can be used, and the command output format: name / uid fg_rchar, fg_wchar, fg_rbytes, fg_wbytes, bg_rchar, bg_wchar bg_rbytes bg_wbytes, fg_fsync, bg_fsync.

[0153] Exemplarily, the embodiment of the present invention provides an execution process, combining Figure 5 As shown, including:

[0154] S500: Get multiple application arrays through the stored-u command. The application can be understood as a process, and the elements included in the array are p_name, w_data, w_p_data, s_sum, and s_p_sum, wherein p_name records the current application name or process number; w_data records the amount of data written to the built-in memory by an application from the start of operation to the current moment; w_p_data records the amount of data written by an application from the start of operation to the previous preset time interval; s_sum records the number of times an application receives a synchronization command to synchronize the data in the memory to the built-in memory from the start of operation to the current moment; s_p_sum records the number of times an application receives a synchronization command to synchronize the data in the memory to the built-in memory from the start of operation to the previous preset time interval; the initial values ​​are all 0; and a repeating timer with a time interval of 5 minutes is set.

[0155] For example, two cycles are recorded, namely 10 minutes, w_data records the amount of data written to the built-in memory by an application from 0 to 10 minutes, and w_p_data records the amount of data written to the built-in memory by an application from 0 to 5 minutes; s_sum records the number of times an application receives a synchronization command to synchronize the data in the memory to the built-in memory from 0 to 10 minutes; s_p_sum records the number of times an application receives a synchronization command to synchronize the data in the memory to the built-in memory from 0 to 5 minutes.

[0156] It should be noted that in the implementation Figure 4 You can only get p_name, w_data, and w_p_data.

[0157] S501: for each application, determine the amount of data written from the memory to the built-in memory within the current preset time, and calculate it using w_data-w_p_data, wherein both w_data and w_p_data are obtained through the command output format fg_wchar+fg_wbytes+bg_wchar+bg_wbytes.

[0158] S502: Determine whether w_data-w_p_data is greater than 1200MB. If so, the application is a malicious application and execute S503. Otherwise, the application is a normal application and return to S500.

[0159] S503: Prompt the user that the application performing the I / O operation is a malicious application.

[0160] Exemplarily, the embodiment of the present invention provides another execution process, combining Figure 6 As shown, including:

[0161] S600: Get multiple application arrays through the stored-u command; of course, execute Figure 6 When you use , you can get only p_name, s_sum, and s_p_sum.

[0162] S601: for each application, determine the number of synchronization commands received within a current preset time to synchronize the data in the memory to the built-in memory; the number is calculated using s_sum–s_p_sum; wherein s_sum and s_p_sum are both data obtained through the command output format fg_fsync+bg_fsync.

[0163] S602: Determine whether s_sum-s_p_sum is greater than 20 times. If so, determine that the application is a malicious application, and execute S603. Otherwise, determine that the application is a normal application, and return to S600.

[0164] S603: Prompt the user that the application performing the I / O operation is a malicious application.

[0165] In addition to the above, when modifying parameters and monitoring whether it is a malicious application, part of the functions of the built-in memory can also be transferred to the external memory.

[0166] Exemplarily, if the memory stores data generated by a preset service of a preset application, and an external memory is inserted into the cockpit domain controller, the data generated by the preset service of the preset application is written from the memory to the external memory.

[0167] Combination Figure 7 As shown, the specific monitoring includes:

[0168] S700: When it is detected that an external memory is inserted into the cockpit domain controller, the data in the memory is started to be monitored;

[0169] S701: If the data in the memory includes data generated by a preset service of a preset application, the data is stored in an external memory.

[0170] The preset service of the preset application may be an update service. For example, the update service of the navigation application, the update service of the music application, the update service of the video application, and the driving service of the driving record application. The preset service of the preset application may also be a temporary service of the preset application. The temporary service is a temporary file. For example, the temporary service of the navigation application, the temporary service of the music application, the temporary service of the video application, and the temporary service of the driving record application.

[0171] It should be noted that the preset service here and the first preset service type and the second preset service type can be the same service, for example, they can all be an update service, a video play service, a music play service, etc.

[0172] If the installation data of the third-party application is stored in the memory and an external memory is inserted into the cockpit domain controller, the installation data of the third-party application is written from the memory to the external memory.

[0173] In practical application, combined with Figure 8 As shown, the execution process includes:

[0174] S800: When it is detected that the installation data of the third-party application is stored in the memory, it is determined whether an external memory is inserted into the cockpit domain controller; if so, S801 is executed, otherwise, S802 is executed;

[0175] S801: Writing the installation data of the third-party application from the internal memory to the external memory;

[0176] S802: Prompt the user that no external storage device is currently inserted and a third-party application cannot be installed.

[0177] Based on the above introduction, an embodiment of the present invention also provides a cockpit domain controller, including: a memory, a built-in storage and a processor;

[0178] The processor is used to monitor the I / O operations of the application on the built-in memory after power-on startup; if it is monitored that an application performs an I / O operation on the built-in memory, determine the data type of the application data corresponding to the I / O operation; if the data type of the application data is a preset data type, modify the read and write parameters corresponding to the preset data type in the memory to reduce the number of I / O operations.

[0179] Optionally, the processor is specifically configured to:

[0180] If the preset data type is a preset local type, modifying a parameter in the memory for controlling the amount of data read from the built-in memory to the memory each time;

[0181] If the preset data type is the first preset service type, a parameter in the memory for controlling a compression ratio of data written from the memory to the built-in memory is modified.

[0182] Optionally, the processor is further used in at least one of the following methods:

[0183] If the preset data type is not the second preset service type, modifying a parameter in the memory for controlling a time interval for writing dirty data in the memory into the built-in memory;

[0184] If the read / write performance of the built-in memory exceeds the preset read / write performance, modifying the parameters in the memory for controlling the timing of writing dirty data of the memory into the built-in memory;

[0185] If the total capacity of the memory exceeds the preset capacity, the parameters in the memory for controlling the time interval for data in the memory to become dirty data are modified, and the parameters in the memory for controlling the length of the request queue for writing into the built-in memory are modified.

[0186] Optionally, the processor is further configured to:

[0187] If it is detected that an application performs an I / O operation on the built-in memory, determine the amount of data written from the memory to the built-in memory by the application performing the I / O operation within a preset time, and if the amount of data written from the memory to the built-in memory by the application performing the I / O operation within the preset time is greater than the preset data amount, prompt the user that the application performing the I / O operation is a malicious application; or

[0188] If it is monitored that an application performs an I / O operation on the built-in memory, it is determined how many times the application performing the I / O operation receives synchronization commands to synchronize the data in the internal memory to the built-in memory within a preset time. If the number is greater than the preset number, the user is prompted that the application performing the I / O operation is a malicious application.

[0189] Optionally, the processor is further configured to:

[0190] If the memory stores data generated by a preset service of a preset application, and an external memory is inserted into the cockpit domain controller, the data generated by the preset service of the preset application is written from the memory to the external memory; and / or

[0191] If the installation data of the third-party application is stored in the memory and the external memory is inserted into the cockpit domain controller, the installation data of the third-party application is written from the memory to the external memory.

[0192] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory including instructions, and the above instructions can be executed by a processor of a cockpit domain controller to complete the above memory operation method. Optionally, the storage medium can be a non-temporary computer-readable storage medium, for example, the non-temporary computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a tape, a floppy disk, an optical data storage device, etc.

[0193] An embodiment of the present invention further provides a computer program product. When the computer program product is run on a cockpit domain controller, the cockpit domain controller executes any one of the above-mentioned memory operation methods of the embodiments of the present invention.

[0194] Those skilled in the art will readily appreciate other embodiments of the invention after considering the specification and practicing the invention invented herein. The invention is intended to cover any variations, uses or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not invented by the present invention. The description and examples are to be regarded as exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0195] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A cockpit domain controller, characterized in that: include: Memory, internal storage and processors; The processor is used to monitor the I / O operation of the application on the built-in memory after power-on startup; If it is detected that an application performs an I / O operation on the built-in memory, determining the data type of the application data corresponding to the I / O operation; If the data type of the application data is a preset data type, modifying the read and write parameters corresponding to the preset data type in the memory to reduce the number of I / O operations; The processor is specifically used for: If the preset data type is a preset local type, modifying a parameter in the memory for controlling the amount of data read from the built-in memory to the memory each time; If the preset data type is the first preset service type, modifying a parameter in the memory for controlling a compression ratio of data written from the memory to the built-in memory; The processor is further configured to: If the preset data type is not the second preset service type, modifying a parameter in the memory for controlling a time interval for writing dirty data in the memory into the built-in memory; If the read / write performance of the built-in memory exceeds the preset read / write performance, modifying the parameters in the memory for controlling the timing of writing dirty data of the memory into the built-in memory; If the total capacity of the memory exceeds the preset capacity, the parameters in the memory for controlling the time interval for data in the memory to become dirty data are modified, and the parameters in the memory for controlling the length of the request queue for writing into the built-in memory are modified.

2. The cockpit domain controller according to claim 1, characterized in that: The processor is further configured to: If it is detected that an application performs an I / O operation on the built-in memory, determine the amount of data written from the memory to the built-in memory by the application performing the I / O operation within a preset time, and if the amount of data written from the memory to the built-in memory by the application performing the I / O operation within the preset time is greater than the preset amount of data, prompt the user that the application performing the I / O operation is a malicious application; or If it is monitored that an application performs an I / O operation on the built-in memory, it is determined how many times the application performing the I / O operation receives synchronization commands to synchronize the data in the internal memory to the built-in memory within a preset time. If the number is greater than the preset number, the user is prompted that the application performing the I / O operation is a malicious application.

3. The cockpit domain controller according to claim 1, characterized in that: The processor is further configured to: If the memory stores data generated by a preset service of a preset application, and an external memory is inserted into the cockpit domain controller, the data generated by the preset service of the preset application is written from the memory to the external memory; and / or If the installation data of the third-party application is stored in the memory and the external memory is inserted into the cockpit domain controller, the installation data of the third-party application is written from the memory to the external memory.

4. A car, characterized in that: It includes a cockpit domain controller located inside the vehicle body, and one or more of the following hardware: a driving recorder located on the rearview mirror of the vehicle; a main display located on the center console; a rear pillow display located on the back seat; Sensors located around the vehicle body; TBOX located inside the vehicle body; A projector located on the body of the vehicle in front of the driver; The cockpit domain controller includes a memory, a built-in memory and a processor; the processor is used to monitor the I / O operation of the application on the built-in memory after power-on startup; if it is monitored that an application performs an I / O operation on the built-in memory, determine the data type of the application data corresponding to the I / O operation; If the data type of the application data is a preset data type, modifying the read and write parameters corresponding to the preset data type in the memory to reduce the number of I / O operations; The driving recorder is connected to the cockpit domain controller, and the processor is also used to control the start-up of the driving recorder, and the driving recorder is used to collect images in front of the vehicle after starting; The sensor is connected to the cockpit domain controller, and the processor is further used to control the start-up of the sensor, and the sensor is used to collect images around the vehicle body after start-up and send them to the cockpit domain controller; The main display is connected to the cockpit domain controller, the processor is further used to obtain a user interface according to the application data, and the main display is used to display the user interface and the image around the vehicle body; The rear pillow display is connected to the cockpit domain controller, and the rear pillow display is used to display the user interface; The TBOX is connected to the cockpit domain controller, and is used for the cockpit domain controller to perform network communication with other electronic devices; The projector is connected to the cockpit domain controller, the processor is also used to obtain driving information of the car, and the projector is used to project the driving information of the car onto the front windshield of the car; The processor is specifically used for: If the preset data type is a preset local type, modifying a parameter in the memory for controlling the amount of data read from the built-in memory to the memory each time; If the preset data type is the first preset service type, modifying a parameter in the memory for controlling a compression ratio of data written from the memory to the built-in memory; The processor is further configured to: If the preset data type is not the second preset service type, modifying a parameter in the memory for controlling a time interval for writing dirty data in the memory into the built-in memory; If the read / write performance of the built-in memory exceeds the preset read / write performance, modifying the parameters in the memory for controlling the timing of writing dirty data of the memory into the built-in memory; If the total capacity of the memory exceeds the preset capacity, the parameters in the memory for controlling the time interval for data in the memory to become dirty data are modified, and the parameters in the memory for controlling the length of the request queue for writing into the built-in memory are modified.

5. A memory operation method, characterized in that: Applied to cockpit domain controller, including: After power-on, monitor the application's I / O operations on the built-in memory; If it is detected that an application performs an I / O operation on the built-in memory, determining the data type of the application data corresponding to the I / O operation; If the data type of the application data is a preset data type, modifying the read and write parameters corresponding to the preset data type in the memory to reduce the number of I / O operations; The modifying the read / write parameters corresponding to the preset data type in the memory includes: If the preset data type is a preset local type, modifying a parameter in the memory for controlling the amount of data read from the built-in memory to the memory each time; If the preset data type is the first preset service type, modifying a parameter in the memory for controlling a compression ratio of data written from the memory to the built-in memory; The method further comprises: If the preset data type is not the second preset service type, modifying a parameter in the memory for controlling a time interval for writing dirty data in the memory into the built-in memory; If the read / write performance of the built-in memory exceeds the preset read / write performance, modifying the parameters in the memory for controlling the timing of writing dirty data of the memory into the built-in memory; If the total capacity of the memory exceeds the preset capacity, the parameters in the memory for controlling the time interval for data in the memory to become dirty data are modified, and the parameters in the memory for controlling the length of the request queue for writing into the built-in memory are modified.

6. The memory operation method according to claim 5, characterized in that: After the monitoring application detects the I / O operation of the built-in memory, the method further includes: If it is detected that an application performs an I / O operation on the built-in memory, determine the amount of data written from the memory to the built-in memory by the application performing the I / O operation within a preset time, and if the amount of data written from the memory to the built-in memory by the application performing the I / O operation within the preset time is greater than the preset data amount, prompt the user that the application performing the I / O operation is a malicious application; or If it is monitored that an application performs an I / O operation on the built-in memory, it is determined how many times the application performing the I / O operation receives synchronization commands to synchronize the data in the internal memory to the built-in memory within a preset time. If the number is greater than the preset number, the user is prompted that the application performing the I / O operation is a malicious application.

Images