A monitoring method for security protection of a car machine APP

Abstract

The application discloses a kind of monitoring methods for car machine APP security protection, by obtaining the package information and running behavior of car machine APP, when the package information of the car machine APP is in the cache or whitelist of car machine, the running behavior of the car machine APP is managed according to cache or whitelist;When the package information of the car machine APP is not in the cache and whitelist of car machine, and the interception mode of car machine system to car machine APP is monitoring mode at current time, car machine system obtains the characteristics of the car machine APP, and determines whether to allow the running behavior of the car machine APP according to the characteristics;The application can improve the fine management of car machine APP running behavior, and can improve the accuracy of car machine APP running behavior management.

Description

Technical Field

[0001] This invention belongs to the field of vehicle-mounted mobile app monitoring technology, and in particular relates to a monitoring method for the security protection of vehicle-mounted mobile apps. Background Technology

[0002] With the continuous development of intelligent connected vehicle technology, the types and functions of in-vehicle infotainment apps are increasing rapidly. However, the ever-expanding functionality of these apps presents certain challenges to vehicle system security and increases entry points for hackers to attack vehicles. Current technologies rely on simple monitoring strategies to track and manage the installation and operation of in-vehicle apps, making it difficult to achieve sophisticated monitoring of the diverse and multifunctional nature of these apps.

[0003] Based on the above issues, this paper proposes a method for security protection and monitoring of in-vehicle infotainment apps. Summary of the Invention

[0004] Based on the above problems, this invention proposes a method for security protection and monitoring of in-vehicle infotainment apps, the method specifically including the following steps: S1. Obtain the running behavior of the vehicle infotainment app and obtain the package information of the vehicle infotainment app; The package information of the vehicle-mounted APP includes at least: package name, version number, and signature information; S2. Determine whether the package information of the vehicle-mounted APP exists in the vehicle-mounted APP cache. If it exists, query the cache decision result corresponding to the package information of the vehicle-mounted APP from the cache, and determine whether to allow the vehicle-mounted APP to run based on the cache decision result; if it does not exist, proceed to step S3. S3. Determine if the package information of the vehicle infotainment app exists in the whitelist. If it exists, determine whether to allow the vehicle infotainment app to run based on the current vehicle operating status. If it does not exist, proceed to step S4. S4. Obtain the vehicle system's blocking mode for the vehicle system APP. When the blocking mode is the blocking mode, block the operation of the vehicle system APP. When the blocking mode is the monitoring mode, execute step S5. S5. The vehicle system acquires the characteristics of the vehicle system APP and determines whether to allow the vehicle system APP to run based on the characteristics.

[0005] Furthermore, the operational behavior includes at least: installation, update, launching the interface, obtaining location, launching background services, controlling vehicle functions, accessing vehicle data, and broadcasting requests; The startup interface includes at least: the main startup interface, a pop-up window, a startup dialog box, and a startup settings page; Location acquisition includes at least: acquiring precise location and acquiring approximate location; Starting a background service includes at least: recording audio using a microphone, accessing Bluetooth devices, and using a camera; Controlling vehicle functions includes at least: unlocking doors, turning on air conditioning, setting seat positions, and controlling windows; Accessing vehicle data includes at least: reading vehicle speed, reading engine speed, reading mileage information, reading battery status, reading gear information, reading door status, reading window status, and reading tire pressure data; A broadcast request must include at least: broadcast registration and broadcast reception.

[0006] Further, step S2 specifically includes: The vehicle infotainment system cache stores multiple rows of decision data; the data format of each row of decision data is: vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and cached decision result; The caching decision results include: allow or deny.

[0007] Furthermore, step S3 specifically includes: S31. Determine whether the package information of the vehicle-mounted APP exists in the whitelist. If it exists, obtain the current vehicle operating status and execute step S32; otherwise, execute step S4. The current vehicle operating status includes at least: vehicle speed, engine speed, gear status, handbrake status, turn signal status, battery charge, powertrain status, tire pressure data, driving mode, vehicle position, airbag status, seat belt status, external light intensity, windshield wiper status, door status, window status, hood status, and tailgate status. S32. Obtain the package information of the vehicle infotainment APP and the dynamic decision results corresponding to the vehicle status from the dynamic inspection strategy table of the vehicle infotainment system; The dynamic inspection strategy table stores multiple rows of data, with each row containing the following data format: vehicle infotainment app package name, vehicle infotainment app version number, running behavior, vehicle status, and dynamic decision result. The dynamic decision-making results include: allow, prohibit; S33. When the dynamic decision result is allowed, the operation of the vehicle-mounted APP is allowed; otherwise, the operation of the vehicle-mounted APP is blocked.

[0008] Furthermore, before the vehicle system acquires the characteristics of the vehicle APP in step S5, the following steps are also included: S501. The vehicle system obtains the software type corresponding to the vehicle system APP, and obtains the first list corresponding to the software type from the first list set; The first list set is stored in the vehicle system; the first list set includes one or more first lists; each first list contains multiple rows of data, and the data format of each row of data is: vehicle APP package name, vehicle APP version number, running behavior, vehicle status, and first decision result; The first decision result includes: allow or prohibit; S502. Obtain the vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and vehicle status, and determine whether there is a row of data in the first list corresponding to the software type that is equal to the vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and vehicle status. If it exists, retrieve the first decision result from that row of data; if the first decision result is allowed, allow the operation of the vehicle infotainment app; if the first decision result is prohibited, block the operation of the vehicle infotainment app. If it does not exist, proceed to step S5.

[0009] Furthermore, the method for obtaining the first list set in step S501 includes the following steps: S5011. The cloud treats each vehicle infotainment app package name and vehicle infotainment app version number as a node, and this node is associated with and stores multiple first-type features and multiple second-type features; Each first-class feature includes at least: operational behavior, vehicle status, and second decision result; The multiple second-category features include at least: software vendor and software type; S5012. The cloud will treat multiple nodes with the same software type as a set of nodes corresponding to that software type; S5013. For multiple first-class features corresponding to multiple nodes in each node set, for each first-class feature, when the second decision result of the first-class feature is the same in all nodes with the first-class feature, add the vehicle APP package name, vehicle APP version number, running behavior, vehicle status and second decision result corresponding to the node as a row of data in the first list corresponding to the software type to the first list corresponding to the software type. S5014. For each set of nodes, repeat step S5013 to obtain the first list corresponding to each software type, forming the first list set; S5015. The cloud will synchronize the first list set to each vehicle system in real time, and the cloud will also synchronize the first type of features stored by each node and the nodes to all vehicle systems.

[0010] Furthermore, step S5 specifically includes the following steps: S51. The vehicle system obtains multiple first-type features corresponding to the vehicle APP and the vehicle APP version number, and determines whether the first-type features corresponding to the running behavior and vehicle status exist among the multiple first-type features; if they exist, the running behavior of the vehicle APP is allowed or blocked according to the second decision result in the first-type feature; if they do not exist, step S52 is executed. S52. Send the vehicle infotainment app package name, vehicle infotainment app version number, running behavior, and vehicle status to the cloud.

[0011] Furthermore, step S5 also includes the following steps: S53. Check the cloud to see if there is a node corresponding to the received vehicle infotainment APP package name and vehicle infotainment APP version number; if it exists, proceed to step S54; otherwise, proceed to step S56. S54. Obtain the set of similar nodes corresponding to the node; The set of similar nodes includes There are 10 nodes; among them... ; S55. In Each node retrieves the corresponding data regarding the described operational behavior and vehicle status. A first-class feature, when the When the second decision results in the first type of features are the same, the cloud feeds back the second decision result to the vehicle system, associates the running behavior, vehicle status, and second decision result as the first type of features with the node in step S53, and synchronizes the newly added first type of feature of the node to all vehicle systems; otherwise, it re-acquires the set of similar nodes corresponding to the node and returns to step S54. in, ; S56. Create a new node in the cloud corresponding to the received vehicle infotainment APP package name and vehicle infotainment APP version number, and obtain the set of similar nodes corresponding to that node.

[0012] Furthermore, in step S55, after receiving the second decision result, the vehicle system allows or blocks the operation of the vehicle APP based on the second decision result.

[0013] Furthermore, step S55 involves re-acquiring the set of similar nodes corresponding to the node, specifically including the following steps: S551. When the above When the second decision results in the first type of features are different, the cloud will prohibit the feedback of the instruction to the vehicle system and feed back the received vehicle APP package name, vehicle APP version number, running behavior, and vehicle status to the administrator user. The administrator user will then set the second decision result and store the running behavior, vehicle status, and the second decision result set by the administrator user as the first type of feature associated with the node in step S53. The newly added first type of feature of the node will be synchronized to all vehicle systems. The cloud will then use the first method to re-obtain the set of similar nodes corresponding to the node. S552. When At this time, the cloud will prohibit the feedback of the command to the vehicle system, and will also provide the administrator user with the received vehicle APP package name, vehicle APP version number, running behavior, and vehicle status. The administrator user will set the second decision result, and store the running behavior, vehicle status, and the second decision result set by the administrator user as the first type of feature associated with the node in step S53. The newly added first type of feature of the node will be synchronized to all vehicle systems. The cloud will then use the second method to re-obtain the set of similar nodes corresponding to the node.

[0014] The beneficial effects of this invention are as follows: (1) The present invention establishes nodes for the vehicle-mounted APP package name and vehicle-mounted APP version number, and realizes the monitoring of vehicle-mounted APP operation behavior and management of operation strategy based on the first type and second type of node features, thereby improving the precision and accuracy of vehicle-mounted APP operation behavior management.

[0015] (2) The present invention uses similarity calculation to obtain a set of similar nodes, and monitors and manages the running behavior and vehicle status of in-vehicle APPs that are not in the cache and whitelist, thereby improving the accuracy of managing the running behavior of in-vehicle APPs.

[0016] (3) This invention addresses the specific circumstances of the second decision result in the first type of features of each node in the similar node set, thereby enabling the management of the operation behavior of the vehicle-mounted APP and the dynamic adjustment of the similar node set, further improving the accuracy of the management of the operation behavior of the vehicle-mounted APP.

[0017] (4) This invention first uses a caching method to verify the operation behavior of in-vehicle APPs, and then uses a whitelist method to verify the operation behavior, which greatly improves the efficiency of managing the operation behavior of in-vehicle APPs. At the same time, it performs refined management of in-vehicle APPs that are not in the cache and not in the whitelist, which improves the accuracy of monitoring the operation behavior of high-risk in-vehicle APPs.

[0018] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above description and other objects, features and advantages of the present invention more obvious and understandable, preferred embodiments are provided and described in detail below. Attached Figure Description

[0019] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This is a flowchart of a monitoring method for security protection of in-vehicle infotainment apps. Detailed Implementation

[0020] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0021] In the description of this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," "fixing," etc., should be interpreted broadly. For example, they can refer to a connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0022] Example 1 like Figure 1 As shown, this invention proposes a monitoring method for the security protection of in-vehicle infotainment apps, which includes the following steps: S1. Obtain the running behavior of the vehicle infotainment app and obtain the package information of the vehicle infotainment app; The package information of the vehicle-mounted APP includes at least: package name, version number, and signature information; S2. Determine whether the package information of the vehicle-mounted APP exists in the vehicle-mounted system cache. If it exists, query the cache decision result corresponding to the package information of the vehicle-mounted APP from the vehicle-mounted system cache, and determine whether to allow the vehicle-mounted APP to run based on the cache decision result. If it does not exist, proceed to step S3. S3. Determine if the package information of the vehicle infotainment app exists in the whitelist. If it exists, determine whether to allow the vehicle infotainment app to run based on the current vehicle operating status. If it does not exist, proceed to step S4. S4. Obtain the vehicle system's blocking mode for the vehicle system APP. When the blocking mode is the blocking mode, block the operation of the vehicle system APP. When the blocking mode is the monitoring mode, execute step S5. S5. The vehicle system acquires the characteristics of the vehicle system APP and determines whether to allow the vehicle system APP to run based on the characteristics.

[0023] Furthermore, the operational behavior includes at least: installation, update, launching the interface, obtaining location, launching background services, controlling vehicle functions, accessing vehicle data, and broadcasting requests; The startup interface includes at least: the main startup interface, a pop-up window, a startup dialog box, and a startup settings page; Location acquisition includes at least: acquiring precise location and acquiring approximate location; Starting a background service includes at least: recording audio using a microphone, accessing Bluetooth devices, and using a camera; Controlling vehicle functions includes at least: unlocking doors, turning on air conditioning, setting seat positions, and controlling windows; Accessing vehicle data includes at least: reading vehicle speed, reading engine speed, reading mileage information, reading battery status, reading gear information, reading door status, reading window status, and reading tire pressure data; A broadcast request must include at least: broadcast registration and broadcast reception.

[0024] Further, step S2 specifically includes: The vehicle infotainment system cache stores multiple rows of decision data; the data format of each row of decision data is: vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and cached decision result; The caching decision results include: allow or deny.

[0025] Further, determining whether the vehicle infotainment system (VMS) app's package information exists in the vehicle infotainment system cache includes: if there is a row of decision data in the VMS cache, and the VMS app's package name and version number in that row of decision data are the same as the VMS app's package name and version number in step S1, then the VMS app's package information exists in the VMS cache; otherwise, the VMS app's package information does not exist in the VMS cache.

[0026] When the vehicle's cache contains the package information of the vehicle's infotainment app, and the cache decision result is "allow," the vehicle's app is allowed to run. When the vehicle's cache contains the package information of the vehicle's infotainment app, and the cache decision result is "prohibit," the vehicle's app is not allowed to run, i.e., the vehicle's app's running behavior is blocked.

[0027] Furthermore, step S3 specifically includes: S31. Determine whether the package information of the vehicle-mounted APP exists in the whitelist. If it exists, obtain the current vehicle operating status and execute step S32; otherwise, execute step S4. The current vehicle operating status includes at least: vehicle speed, engine speed, gear status, handbrake status, turn signal status, battery charge, powertrain status, tire pressure data, driving mode, vehicle position, airbag status, seat belt status, external light intensity, windshield wiper status, door status, window status, hood status, and tailgate status. S32. Obtain the package information of the vehicle infotainment APP and the dynamic decision results corresponding to the vehicle status from the dynamic inspection strategy table of the vehicle infotainment system; The dynamic inspection strategy table stores multiple rows of data, with each row containing the following data format: vehicle infotainment app package name, vehicle infotainment app version number, running behavior, vehicle status, and dynamic decision result. The dynamic decision-making results include: allow, prohibit; S33. When the dynamic decision result is allowed, the operation of the vehicle-mounted APP is allowed; otherwise, the operation of the vehicle-mounted APP is blocked.

[0028] The whitelist includes multiple lines of data, each line containing the following format: vehicle infotainment app package name and vehicle infotainment app version number.

[0029] Furthermore, determining whether the package information of the vehicle infotainment app exists in the whitelist specifically includes: if the package name and version number of the vehicle infotainment app in the whitelist are the same as the package name and version number of the vehicle infotainment app in step S1, then the package information of the vehicle infotainment app exists in the whitelist; otherwise, the package information of the vehicle infotainment app does not exist in the whitelist.

[0030] Furthermore, the dynamic decision results corresponding to the vehicle status and the package information of the vehicle-mounted APP are obtained from the dynamic inspection strategy table of the vehicle-mounted system. Specifically, this includes: obtaining a row of data corresponding to the package name, version number, and vehicle status of the vehicle-mounted APP from the dynamic inspection strategy table, and using the dynamic decision results in that row of data as the package information and dynamic decision results corresponding to the vehicle status of the vehicle-mounted APP.

[0031] Furthermore, when the vehicle infotainment app package name exists in the whitelist, before obtaining the current vehicle operating status, the system also includes: verifying the signature information of the vehicle infotainment app; if the verification passes, obtaining the current vehicle operating status and executing step S32; if the verification fails, blocking the operation of the vehicle infotainment app.

[0032] Furthermore, in step S4, obtaining the vehicle system's interception mode for the vehicle-mounted APP specifically involves obtaining the current interception mode of the vehicle system for the untrusted vehicle-mounted APP as the interception mode of the vehicle system for the vehicle-mounted APP.

[0033] The untrusted in-vehicle apps mentioned above are those not stored in the in-vehicle cache or whitelist.

[0034] The ways to set up the blocking mode for untrusted in-vehicle apps in the vehicle system include, but are not limited to: setting it through the vehicle owner's mobile terminal, setting it through the vehicle's display screen, etc.

[0035] The interception modes include: blocking mode and monitoring mode.

[0036] When the vehicle system's interception mode for a vehicle-mounted app is blocking mode, the app's operation is blocked. When the vehicle system's interception mode for a vehicle-mounted app is monitoring mode, step S5 is executed.

[0037] Furthermore, before the vehicle system acquires the characteristics of the vehicle APP in step S5, the following steps are also included: S501. The vehicle system obtains the software type corresponding to the vehicle system APP, and obtains the first list corresponding to the software type from the first list set; The first list set is stored in the vehicle system; the first list set includes one or more first lists; each first list contains multiple rows of data, and the data format of each row of data is: vehicle APP package name, vehicle APP version number, running behavior, vehicle status, and first decision result; The first decision result includes: allow or prohibit; S502. Obtain the vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and vehicle status, and determine whether there is a row of data in the first list corresponding to the software type that is equal to the vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and vehicle status. If it exists, retrieve the first decision result from that row of data; if the first decision result is allowed, allow the operation of the vehicle infotainment app; if the first decision result is prohibited, block the operation of the vehicle infotainment app. If it does not exist, proceed to step S5.

[0038] Furthermore, the method for obtaining the first list set in step S501 includes the following steps: S5011. The cloud treats each vehicle infotainment app package name and vehicle infotainment app version number as a node, and this node is associated with and stores multiple first-type features and multiple second-type features; Each first-class feature includes at least: operational behavior, vehicle status, and second decision result; The multiple second-category features include at least: software vendor and software type; S5012. The cloud will treat multiple nodes with the same software type as a set of nodes corresponding to that software type; S5013. For multiple first-class features corresponding to multiple nodes in each node set, for each first-class feature, when the second decision result of the first-class feature is the same in all nodes with the first-class feature, add the vehicle APP package name, vehicle APP version number, running behavior, vehicle status and second decision result corresponding to the node as a row of data in the first list corresponding to the software type to the first list corresponding to the software type. S5014. For each set of nodes, repeat step S5013 to obtain the first list corresponding to each software type, forming the first list set; S5015. The cloud will synchronize the first list set to each vehicle system in real time, and the cloud will also synchronize the first type of features stored by each node and the nodes to all vehicle systems.

[0039] Furthermore, step S5 specifically includes the following steps: S51. The vehicle system obtains multiple first-type features corresponding to the vehicle APP and the vehicle APP version number, and determines whether the first-type features corresponding to the running behavior and vehicle status exist among the multiple first-type features; if they exist, the running behavior of the vehicle APP is allowed or blocked according to the second decision result in the first-type feature; if they do not exist, step S52 is executed. S52. Send the vehicle infotainment app package name, vehicle infotainment app version number, running behavior, and vehicle status to the cloud.

[0040] Furthermore, step S5 also includes the following steps: S53. Check the cloud to see if there is a node corresponding to the received vehicle infotainment APP package name and vehicle infotainment APP version number; if it exists, proceed to step S54; otherwise, proceed to step S56. S54. Obtain the set of similar nodes corresponding to the node; The set of similar nodes includes There are 10 nodes; among them... 4 or 5; S55. In Each node retrieves the corresponding data regarding the described operational behavior and vehicle status. A first-class feature, when the When the second decision results in the first type of features are the same, the cloud feeds back the second decision result to the vehicle system, associates the running behavior, vehicle status, and second decision result as the first type of features with the node in step S53, and synchronizes the newly added first type of feature of the node to all vehicle systems; otherwise, it re-acquires the set of similar nodes corresponding to the node and returns to step S54. For example, There are nodes Each node, Each node possesses a first-type feature. If the operational behavior and vehicle status of this first-type feature are identical to the operational behavior and vehicle status corresponding to the vehicle-mounted APP in step S51, then the process is complete. Each node retrieves the corresponding data regarding the described operational behavior and vehicle status. The first type of feature.

[0041] in, ; S56. Create a new node in the cloud corresponding to the received vehicle infotainment APP package name and vehicle infotainment APP version number, and obtain the set of similar nodes corresponding to that node.

[0042] Furthermore, in step S55, after receiving the second decision result, the vehicle system allows or blocks the operation of the vehicle APP based on the second decision result.

[0043] Furthermore, step S55 involves re-acquiring the set of similar nodes corresponding to the node, specifically including the following steps: S551. When the above When the second decision results in the first type of features are different, the cloud will prohibit the feedback of the instruction to the vehicle system and feed back the received vehicle APP package name, vehicle APP version number, running behavior, and vehicle status to the administrator user. The administrator user will then set the second decision result and store the running behavior, vehicle status, and the second decision result set by the administrator user as the first type of feature associated with the node in step S53. The newly added first type of feature of the node will be synchronized to all vehicle systems. The cloud will then use the first method to re-obtain the set of similar nodes corresponding to the node. S552. When At this time, the cloud will prohibit the feedback of the command to the vehicle system, and will also provide the administrator user with the received vehicle APP package name, vehicle APP version number, running behavior, and vehicle status. The administrator user will set the second decision result, and store the running behavior, vehicle status, and the second decision result set by the administrator user as the first type of feature associated with the node in step S53. The newly added first type of feature of the node will be synchronized to all vehicle systems. The cloud will then use the second method to re-obtain the set of similar nodes corresponding to the node.

[0044] Furthermore, in step S551, the cloud re-obtains the set of similar nodes corresponding to the node using the first method, specifically including the following steps: S5511. Obtain the software type from the second type of features of this node in the cloud, and obtain other nodes with the same software type; S5512. Obtain the weight values ​​of each first-class feature in this node from the cloud; S5513. For each of the other nodes, obtain one or more first-class features that are the same as the node in the other node, and sum the weight values ​​of the one or more first-class features to obtain the similarity coefficient between the node and the other nodes; S5514. For each of the other nodes, repeat step S5513 until the similarity coefficient between the node and each of the other nodes is obtained; S5515. Sort the similarity coefficients from largest to smallest, and obtain the top... The other nodes corresponding to each similarity coefficient are considered as the set of similar nodes for that node.

[0045] Furthermore, in step S552, the cloud uses the second method to re-obtain the set of similar nodes corresponding to the node, specifically including the following steps: S5521. Obtain the weight values ​​of each first-class feature in this node from the cloud; S5522. For each of all nodes stored in the cloud other than the node in step S5521, obtain one or more first-class features that are the same as the node in the other node, and add up the weight values ​​of the one or more first-class features to obtain the similarity coefficient between the node and the other node. S5523. For each of the other nodes, repeat step S5522 until the similarity coefficient between the node and each of the other nodes is obtained; S5524. Sort the similarity coefficients from largest to smallest, and obtain the top... The other nodes corresponding to each similarity coefficient are considered as the set of similar nodes for that node.

[0046] Furthermore, step S56 specifically includes the following steps: S561. Create a new node in the cloud corresponding to the received vehicle infotainment APP package name and vehicle infotainment APP version number, and synchronize the newly created node and the first type of feature of the newly created node to all vehicle infotainment systems; The first characteristic of the newly created node is empty; The cloud query retrieves the software information corresponding to the newly created node, and obtains the software supplier and software type of the vehicle's infotainment app as the second type of feature corresponding to the node; The software information includes: software vendor, software type, and feature list; The function list contains multiple function items; S562. For each node in the cloud computing and cloud storage system, count the number of identical functional items among the multiple functional items of the newly created node, sort the counts in descending order, and obtain the top... The number of nodes corresponding to each quantity; among them. ; S563. Determine the result obtained in step S562. The number of nodes in the node group that have the same software type as the newly created node. When that number Greater than If so, proceed to step S564; otherwise, proceed to the next step. Each node and Among the nodes, the first A set of similar nodes corresponding to the newly created node is defined as a set of nodes whose software type is different from that of the newly created node. S564. Judgment The number of nodes in the node that share the same software vendor as the newly created node. When that number Greater than At that time, from that Get the previous node from each node One node is used as the set of similar nodes corresponding to the newly created node; otherwise, the set of similar nodes is used. Each node and Among the nodes, the first A set of similar nodes corresponding to the newly created node is defined as a set of nodes whose software vendors are different from those of the newly created node.

[0047] The beneficial effects of this invention are as follows: (1) The present invention establishes nodes for the vehicle-mounted APP package name and vehicle-mounted APP version number, and realizes the monitoring of vehicle-mounted APP operation behavior and management of operation strategy based on the first type and second type of node features, thereby improving the precision and accuracy of vehicle-mounted APP operation behavior management.

[0048] (2) The present invention uses similarity calculation to obtain a set of similar nodes, and monitors and manages the running behavior and vehicle status of in-vehicle APPs that are not in the cache and whitelist, thereby improving the accuracy of managing the running behavior of in-vehicle APPs.

[0049] (3) This invention addresses the specific circumstances of the second decision result in the first type of features of each node in the similar node set, thereby enabling the management of the operation behavior of the vehicle-mounted APP and the dynamic adjustment of the similar node set, further improving the accuracy of the management of the operation behavior of the vehicle-mounted APP.

[0050] (4) This invention first uses a caching method to verify the operation behavior of in-vehicle APPs, and then uses a whitelist method to verify the operation behavior, which greatly improves the efficiency of managing the operation behavior of in-vehicle APPs. At the same time, it performs refined management of in-vehicle APPs that are not in the cache and not in the whitelist, which improves the accuracy of monitoring the operation behavior of high-risk in-vehicle APPs.

[0051] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A monitoring method for security protection of in-vehicle infotainment apps, characterized in that, The method includes the following steps: S1. Obtain the running behavior of the vehicle infotainment app and obtain the package information of the vehicle infotainment app; The package information of the vehicle-mounted APP includes at least: package name, version number, and signature information; The operational behavior includes at least: installation, update, launching the interface, obtaining location, launching background services, controlling vehicle functions, accessing vehicle data, and broadcasting requests; S2. Determine whether the package information of the vehicle APP exists in the vehicle system cache. If it exists, query the cache decision result corresponding to the package information of the vehicle APP from the cache, and determine whether to allow the operation of the vehicle APP based on the cache decision result; if it does not exist, execute step S3. The vehicle infotainment system cache stores multiple rows of decision data; the data format of each row of decision data is: vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and cached decision result; The caching decision results include: allow or deny; S3. Determine if the package information of the vehicle infotainment app exists in the whitelist. If it exists, determine whether to allow the vehicle infotainment app to run based on the current vehicle operating status. If it does not exist, proceed to step S4. S4. Obtain the vehicle system's blocking mode for the vehicle system APP. When the blocking mode is the blocking mode, block the operation of the vehicle system APP. When the blocking mode is the monitoring mode, execute step S5. S5. The vehicle system obtains the characteristics of the vehicle system APP and determines whether to allow the vehicle system APP to run based on the characteristics; Step S5 specifically includes the following steps: S51. The vehicle system obtains multiple first-type features corresponding to the vehicle APP and the vehicle APP version number, and determines whether the first-type features corresponding to the running behavior and vehicle status exist among the multiple first-type features; if they exist, the running behavior of the vehicle APP is allowed or blocked according to the second decision result in the first-type feature; if they do not exist, step S52 is executed. The first type of feature includes at least: operational behavior, vehicle status, and second decision result; S52. Send the vehicle infotainment app package name, vehicle infotainment app version number, running behavior, and vehicle status to the cloud; S53. Check the cloud to see if there is a node corresponding to the received vehicle infotainment APP package name and vehicle infotainment APP version number; if it exists, proceed to step S54; otherwise, proceed to step S56. In this process, the cloud uses each vehicle infotainment app package name and vehicle infotainment app version number as a node, and this node is associated with and stores multiple first-type features and multiple second-type features. The multiple second-category features include at least: software vendor and software type; S54. Obtain the set of similar nodes corresponding to the node; The set of similar nodes includes There are 10 nodes; among them... ; S55. In Each node retrieves the corresponding data regarding the described operational behavior and vehicle status. A first-class feature, when the When the second decision results in the first type of features are the same, the cloud feeds back the second decision result to the vehicle system, associates the running behavior, vehicle status, and second decision result as the first type of features with the node in step S53, and synchronizes the newly added first type of feature of the node to all vehicle systems; otherwise, it re-acquires the set of similar nodes corresponding to the node and returns to step S54. Among them, when There are nodes Each node, Each of the nodes possesses a first-type feature. If the operational behavior and vehicle status of this first-type feature are identical to the operational behavior and vehicle status corresponding to the vehicle-mounted APP in step S51, then the process is complete. Each node retrieves the corresponding data regarding the described operational behavior and vehicle status. One first-class feature; ; S56. Create a new node in the cloud corresponding to the received vehicle infotainment APP package name and vehicle infotainment APP version number, and obtain the set of similar nodes corresponding to that node.

2. The monitoring method for security protection of in-vehicle infotainment apps according to claim 1, characterized in that: The startup screen should include at least: the main startup screen, a pop-up window, a startup dialog box, and a startup settings page; Location acquisition includes at least: acquiring precise location and acquiring approximate location; Starting a background service includes at least: recording audio using a microphone, accessing Bluetooth devices, and using a camera; Controlling vehicle functions includes at least: unlocking doors, turning on air conditioning, setting seat positions, and controlling windows; Accessing vehicle data includes at least: reading vehicle speed, reading engine speed, reading mileage information, reading battery status, reading gear information, reading door status, reading window status, and reading tire pressure data; A broadcast request must include at least: broadcast registration and broadcast reception.

3. The monitoring method for security protection of in-vehicle infotainment apps according to claim 2, characterized in that, Step S3 specifically includes: S31. Determine whether the package information of the vehicle-mounted APP exists in the whitelist. If it exists, obtain the current vehicle operating status and execute step S32; otherwise, execute step S4. The current vehicle operating status includes at least: vehicle speed, engine speed, gear status, handbrake status, turn signal status, battery charge, powertrain status, tire pressure data, driving mode, vehicle position, airbag status, seat belt status, external light intensity, windshield wiper status, door status, window status, hood status, and tailgate status. S32. Obtain the package information of the vehicle infotainment APP and the dynamic decision results corresponding to the vehicle status from the dynamic inspection strategy table of the vehicle infotainment system; The dynamic inspection strategy table stores multiple rows of data, with each row containing the following data format: vehicle infotainment app package name, vehicle infotainment app version number, running behavior, vehicle status, and dynamic decision result. The dynamic decision-making results include: allow, prohibit; S33. When the dynamic decision result is allowed, the operation of the vehicle-mounted APP is allowed; otherwise, the operation of the vehicle-mounted APP is blocked.

4. The monitoring method for security protection of in-vehicle infotainment apps according to claim 3, characterized in that, Before the vehicle system obtains the characteristics of the vehicle APP in step S5, the following steps are also included: S501. The vehicle system obtains the software type corresponding to the vehicle system APP, and obtains the first list corresponding to the software type from the first list set; The first list set is stored in the vehicle system; the first list set includes one or more first lists; each first list contains multiple rows of data, and the data format of each row of data is: vehicle APP package name, vehicle APP version number, running behavior, vehicle status, and first decision result; The first decision result includes: allow or prohibit; S502. Obtain the vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and vehicle status, and determine whether there is a row of data in the first list corresponding to the software type that is equal to the vehicle infotainment APP package name, vehicle infotainment APP version number, running behavior, and vehicle status. If it exists, retrieve the first decision result from that row of data; if the first decision result is allowed, allow the operation of the vehicle infotainment app; if the first decision result is prohibited, block the operation of the vehicle infotainment app. If it does not exist, proceed to step S5.

5. A monitoring method for security protection of in-vehicle infotainment apps according to claim 4, characterized in that: The method for obtaining the first list set in step S501 includes the following steps: S5011. The cloud treats each vehicle infotainment app package name and vehicle infotainment app version number as a node, and this node is associated with and stores multiple first-type features and multiple second-type features; Each first-class feature includes at least: operational behavior, vehicle status, and second decision result; The multiple second-category features include at least: software vendor and software type; S5012. The cloud will treat multiple nodes with the same software type as a set of nodes corresponding to that software type; S5013. For multiple first-class features corresponding to multiple nodes in each node set, for each first-class feature, when the second decision result of the first-class feature is the same in all nodes with the first-class feature, add the vehicle APP package name, vehicle APP version number, running behavior, vehicle status and second decision result corresponding to the node as a row of data in the first list corresponding to the software type to the first list corresponding to the software type. S5014. For each set of nodes, repeat step S5013 to obtain the first list corresponding to each software type, forming the first list set; S5015. The cloud will synchronize the first list set to each vehicle system in real time, and the cloud will also synchronize the first type of features stored by each node and the nodes to all vehicle systems.

6. A monitoring method for security protection of in-vehicle infotainment apps according to claim 5, characterized in that, In step S55, after receiving the second decision result, the vehicle system allows or blocks the operation of the vehicle APP based on the second decision result.

7. A monitoring method for security protection of in-vehicle infotainment apps according to claim 6, characterized in that, Step S55 involves retrieving the set of similar nodes corresponding to the node, specifically including the following steps: S551. When the above When the second decision results in the first type of features are different, the cloud will prohibit the feedback of the instruction to the vehicle system and feed back the received vehicle APP package name, vehicle APP version number, running behavior, and vehicle status to the administrator user. The administrator user will then set the second decision result and store the running behavior, vehicle status, and the second decision result set by the administrator user as the first type of feature associated with the node in step S53. The newly added first type of feature of the node will be synchronized to all vehicle systems. The cloud will then use the first method to re-obtain the set of similar nodes corresponding to the node. S552. When At that time, the cloud will send the prohibition command to the vehicle system and send the received vehicle APP package name, vehicle APP version number, running behavior and vehicle status to the administrator user. The administrator user sets the second decision result and stores the running behavior, vehicle status and the second decision result set by the administrator user as the first type of feature associated with the node in step S53. The newly added first type of feature of the node is synchronized to all vehicle systems. The cloud uses a second method to re-obtain the set of similar nodes corresponding to that node.

Images