Vehicle-mounted application authentication method and device, electronic equipment and storage medium

Abstract

The invention discloses an authentication method and device of a vehicle-mounted application program, electronic equipment and a storage medium. The method comprises the steps that in response to starting of a vehicle-mounted operating system, authentication demand information is acquired from an authentication search information set, and the authentication search information set is pre-filled into a kernel of the operating system; generating an authentication request signal based on the authentication demand information, and sending the authentication request signal to the target application program; in response to received authentication response information, authentication check information in the authentication search information set is utilized to perform authentication check on the authentication response information to obtain an authentication check result, the authentication response information is pre-stored in a read-only data segment of the target application program, and the authentication check result is stored in the read-only data segment of the target application program. The authentication verification result is used for representing whether the target application program is successfully authenticated and verified. According to the method and the device, the technical problem of relatively high cost caused by frequent authentication code development and maintenance in order to authenticate the vehicle-mounted application program in the prior art is solved.

Description

Technical Field

[0001] This invention relates to the field of vehicle technology, and more specifically, to an authentication method, apparatus, electronic device, and storage medium for in-vehicle applications. Background Technology

[0002] In modern in-vehicle electronic systems, with the widespread adoption of intelligent driving assistance systems, connected entertainment, and remote vehicle management, the number and complexity of in-vehicle applications have increased rapidly. The legitimacy and security of these applications have become a key focus for the automotive industry. However, current in-vehicle application authentication mechanisms face multiple challenges. Traditional application authentication methods often rely on software developers manually modifying the application and operating system kernel code to embed specific authentication logic. This process is time-consuming and laborious, and prone to introducing errors, reducing code stability and security. Manual coding adjustments for different operating system platforms also limit code reusability, increase development costs and maintenance difficulty, meaning that related technologies require frequent development and maintenance of authentication code to implement in-vehicle application authentication, resulting in high costs.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This invention provides an authentication method, apparatus, electronic device, and storage medium for in-vehicle applications, at least to solve the technical problem in the related art that the frequent development and maintenance of authentication code is required to authenticate in-vehicle applications, resulting in high costs.

[0005] According to one aspect of the present invention, an authentication method for an in-vehicle application is provided, comprising: in response to the startup of the in-vehicle operating system, obtaining authentication request information from an authentication lookup information set, wherein the authentication lookup information set is pre-filled into the kernel of the operating system, the authentication lookup information set includes authentication request information, the authentication request information including at least an application name, the application name being used to indicate a target application requiring authentication; generating an authentication request signal based on the authentication request information, and sending the authentication request signal to the target application; in response to receiving authentication response information, performing authentication verification on the authentication response information using authentication verification information in the authentication lookup information set, and obtaining an authentication verification result, wherein the authentication response information is generated by the target application in responding to a request, the authentication response information is pre-stored in a read-only data segment of the target application, and the authentication verification result is used to characterize whether the target application has successfully performed authentication verification.

[0006] In this embodiment of the invention, obtaining authentication request information from the authentication lookup information set includes: using the inspection module in the operating system to query the authentication lookup information set according to a preset frequency corresponding to the target application to obtain authentication request information, wherein the preset frequency is stored in the authentication lookup information set and the preset frequency is used to represent the predefined frequency of authentication requests to the target application.

[0007] In this embodiment of the invention, generating an authentication request signal based on authentication requirement information and sending the authentication request signal to the target application includes: using an inspection module to send the queried authentication requirement information to a task scheduling module in the operating system; using the task scheduling module to obtain the first process identifier of the target application at the current moment based on the authentication requirement information; generating an authentication request signal based on the first process identifier and the authentication requirement information, and sending the authentication request signal to the target application.

[0008] In this embodiment of the invention, the method further includes: in response to the authentication verification result being that the authentication verification of the target application is successful, updating the authentication timestamp corresponding to the target application in the authentication lookup information set based on the current time; in response to the authentication verification result being that the authentication verification of the target application is unsuccessful, controlling the target application to stop running.

[0009] In this embodiment of the invention, the method further includes: using an inspection module to determine the time difference between the current time and the authentication timestamp; and controlling the target application to stop running when the time difference is greater than a preset timeout, wherein the preset timeout is stored in the authentication lookup information set.

[0010] In this embodiment of the invention, controlling the target application to stop running includes: using an inspection module to send the second process identifier of the target application at the current moment and the exception handling action information corresponding to the target application to a task scheduling module, wherein the exception handling action information is stored in an authentication lookup information set and is used to describe the corresponding processing action that needs to be executed to control the target application to stop running; and using the task scheduling module to control the target application to stop running based on the second process identifier and the exception handling action information.

[0011] According to another aspect of the present invention, an authentication method for an in-vehicle application is also provided, comprising: responding to receiving an authentication request signal by requesting and responding to the authentication request signal using data pre-stored in a read-only data segment to obtain authentication response information, wherein the authentication request signal is obtained by the above-described method; and sending the authentication response information to an operating system, wherein the authentication response information is used to perform the above-described method to authenticate and verify the target application.

[0012] In this embodiment of the invention, the authentication request signal is responded to using data pre-stored in a read-only data segment to obtain authentication response information. This includes: using a signal processing function pre-defined in the target application to call the data stored in the read-only data segment to respond to the authentication request signal and obtain authentication response information.

[0013] In this embodiment of the invention, sending authentication response information to the operating system includes: using a signal processing function to call a user-mode interface in the target application to pass the authentication response information to a system call function; and using the system call function to send the authentication response information to the operating system.

[0014] According to another aspect of the present invention, an authentication device for an in-vehicle application is also provided, comprising: an acquisition module, configured to acquire authentication request information from an authentication lookup information set in response to the startup of the in-vehicle operating system, wherein the authentication lookup information set is pre-filled into the kernel of the operating system, the authentication lookup information set includes authentication request information, the authentication request information including at least an application name, the application name being used to indicate a target application requiring authentication; a generation module, configured to generate an authentication request signal based on the authentication request information and send the authentication request signal to the target application; and a verification module, configured to perform authentication verification on the authentication response information using authentication verification information in the authentication lookup information set in response to receiving authentication response information, and obtain an authentication verification result, wherein the authentication response information is generated by the target application in responding to a request, the authentication response information is pre-stored in a read-only data segment of the target application, and the authentication verification result is used to characterize whether the target application has successfully completed authentication verification.

[0015] According to another aspect of the present invention, an authentication device for an in-vehicle application is also provided, comprising: a response module, configured to respond to an authentication request signal received by using data pre-stored in a read-only data segment to request and respond to the authentication request signal, thereby obtaining authentication response information, wherein the authentication request signal is obtained by the method described above; and a sending module, configured to send the authentication response information to an operating system, wherein the authentication response information is used to perform the method described above to authenticate and verify the target application.

[0016] According to another aspect of the present invention, an electronic device is also provided, comprising: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods of various embodiments of the present invention during runtime.

[0017] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is executed, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of the present invention.

[0018] According to another aspect of the present invention, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of the present invention.

[0019] According to another aspect of the present invention, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods of various embodiments of the present invention.

[0020] According to another aspect of the present invention, a computer program is also provided, which, when executed by a processor, implements the methods of the various embodiments of the present invention.

[0021] In this embodiment of the invention, firstly, in response to the startup of the vehicle's operating system, authentication request information can be obtained from the authentication lookup information set. The authentication lookup information set is pre-filled into the kernel of the operating system and contains authentication request information, which includes at least the application name. The application name is used to indicate the target application that needs to be authenticated. Next, based on the authentication request information, an authentication request signal can be generated and sent to the target application. Finally, in response to receiving authentication response information, the authentication verification information in the authentication lookup information set can be used to perform authentication verification on the authentication response information to obtain an authentication verification result. The authentication response information is generated by the target application in responding to the request and is pre-stored in the read-only data segment of the target application. The authentication verification result is used to characterize whether the target application has successfully performed authentication verification. The authentication lookup information set in this application is pre-filled into the operating system kernel. This set can contain relevant information about each application requiring authentication, enabling automated execution of the authentication process and fulfilling authentication requests for the target application. By modifying the operating system kernel code only once, it avoids the frequent development and modification of operating system authentication information required in traditional authentication processes. Furthermore, by pre-storing authentication response information in the target application's read-only data segment and responding to authentication request signals, it avoids additional authentication response calculations during target application runtime, reducing the impact of the authentication process on target application performance. It also avoids the need for additional authentication response information development for the application, thus solving the technical problem in related technologies where frequent authentication code development and maintenance are required to authenticate in-vehicle applications, leading to high costs. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0023] Figure 1 This is a flowchart of an authentication method for an in-vehicle application according to an embodiment of the present invention;

[0024] Figure 2 This is a flowchart of another authentication method for an in-vehicle application according to an embodiment of the present invention;

[0025] Figure 3 This is a schematic diagram of an optional operating system-side configuration according to an embodiment of the present invention;

[0026] Figure 4 This is a schematic diagram of an optional target application-side setting according to an embodiment of the present invention;

[0027] Figure 5 This is a schematic diagram of an optional authentication process for a target application according to an embodiment of the present invention;

[0028] Figure 6 This is a schematic diagram of an authentication device for an in-vehicle application according to an embodiment of the present invention;

[0029] Figure 7 This is a schematic diagram of an authentication device for another in-vehicle application according to an embodiment of the present invention. Detailed Implementation

[0030] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of the present invention.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] According to one aspect of the present invention, an authentication method for an in-vehicle application is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0033] Figure 1 This is a flowchart of an authentication method for an in-vehicle application according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0034] Step S102: In response to the startup of the vehicle's operating system, obtain authentication request information from the authentication lookup information set.

[0035] The authentication lookup information set is pre-filled into the operating system kernel. The authentication lookup information set contains authentication requirement information, which includes at least the application name. The application name is used to indicate the target application that needs to be authenticated.

[0036] The aforementioned operating system can refer to the software system running in the vehicle controller, responsible for managing hardware resources and providing a runtime environment for user-mode applications. The operating system may include components such as drivers, a system kernel, and service programs. It can be a real-time operating system or a general-purpose operating system. In this application, the operating system is also responsible for scheduling applications and executing authentication mechanisms.

[0037] The aforementioned authentication lookup information set can refer to a data structure maintained by the operating system kernel, used to store information about each application to be authenticated. For example, the authentication lookup information set can be an authentication lookup table (LUT), which can be loaded at operating system startup or dynamically updated during runtime. The authentication lookup information set can contain the authentication requirements of applications, which can be predefined in a configuration file and populated into the operating system kernel by the linker.

[0038] The aforementioned authentication requirement information refers to a set of parameters defined for each application within the authentication lookup information set. These parameters can be used to indicate and specify the details of the authentication behavior. The authentication requirement information may include, but is not limited to, the application name, preset frequency, preset timeout, and exception handling information. The authentication requirement information provides the operating system with criteria for verifying the legitimacy of applications.

[0039] The application name mentioned above can refer to the identifier of the target application stored in the authentication lookup information set. It can be used to identify and locate a specific application, ensuring that the authentication mechanism executes on the correct program. The application name can be specified by the user when building the application.

[0040] The target application mentioned above can refer to an application that requires authentication. The target application has recorded authentication request information in the authentication lookup information set and needs to respond to authentication requests from the operating system at runtime.

[0041] In one optional embodiment, after the in-vehicle operating system boots up, it can load a set of authentication lookup information pre-stored in the operating system kernel. This set can be populated into the kernel during the program compilation and linking stage using a customized linker, and it can contain information about each application requiring authentication. The authentication lookup information set can be designed using efficient data structures, such as hash tables or arrays, for fast lookup and access. The operating system can call a specially designed module to read each entry in the authentication lookup information set. Each entry can contain fields such as the application name, and other parameters such as preset frequency and preset timeout. During the process of reading authentication request information, the operating system can also check whether the authentication lookup information set is intact, complete, and has been recently updated. If there are no abnormalities, the operating system can continue to execute the subsequent authentication process; if there are abnormalities, the operating system can take predefined error handling measures, such as restarting, logging, or prompting the user.

[0042] In the above process, the authentication lookup information set is filled into the operating system kernel during the program compilation and linking stage. The authentication lookup information set can contain relevant information of each application that needs to be authenticated, so that the authentication process can be executed automatically, which can enhance the stability and reliability of the authentication process.

[0043] Step S104: Based on the authentication requirement information, generate an authentication request signal and send the authentication request signal to the target application.

[0044] The aforementioned authentication request signal can be a request signal sent by the operating system to the target application, requiring the application to provide proof of legitimacy. For example, it could be a SIGUSR signal. The authentication request signal can trigger the target application to execute the signal processing function for legitimacy verification.

[0045] In one optional embodiment, after the operating system completes startup and loads the authentication lookup information set, it can check the authentication request information in the authentication lookup information set. Based on actual needs, it can generate an authentication request signal for the target application and transmit the authentication request signal to the target application. Specifically, it can read the authentication request information of each target application recorded in the authentication lookup information set, which may include parameters such as application name and prediction frequency. Then, based on the authentication request information, it can generate an authentication request signal. The authentication request signal may contain the information required for the authentication request to ensure that the authentication request can be correctly identified and processed.

[0046] In the above process, the task scheduling mechanism and signal processing mechanism in the operating system are used to realize the authentication request for the target application. The authentication request signal can be generated and sent efficiently without modifying the application itself, thereby reducing the burden on software developers.

[0047] Step S106: In response to receiving the authentication response information, the authentication response information is authenticated using the authentication verification information in the authentication lookup information set to obtain the authentication verification result.

[0048] The authentication response information is generated by the target application in responding to the request. The authentication response information is stored in the read-only data segment of the target application in advance. The authentication verification result is used to indicate whether the target application has successfully performed authentication verification.

[0049] The authentication response information mentioned above can refer to the response information returned to the operating system after the target application receives the authentication request signal, reads pre-stored authentication-related data from the read-only data segment, and returns it. The authentication response information may include a message digest value of the application name or other forms of identification, which the operating system uses for subsequent legitimacy verification.

[0050] The aforementioned authentication verification information refers to the verification information stored in the authentication lookup information set, used to compare and verify the authentication response information. Authentication verification information may include the application's expected message digest value or other preset identifiers, as well as parameters such as authentication frequency and timeout, ensuring that the operating system can correctly determine the legitimacy of the application.

[0051] The aforementioned authentication verification result can refer to the result of whether the target application is legitimate, which is obtained by comparing the authentication response information received and processed by the operating system with the authentication verification information in the authentication lookup information set.

[0052] In one optional embodiment, after the authentication request signal is sent, the operating system can receive and verify the authentication response information. When the target application responds to the authentication request signal, it can read the pre-stored authentication response information from the read-only data segment. The authentication response information may include the application's message digest value and other authentication data such as timestamps. The application can call a specific system call function through the user-mode interface to send the authentication response information back to the operating system. After receiving the authentication response information, the operating system can perform verification using the authentication verification information stored in the authentication lookup information set. The authentication verification information may include the application's expected message digest value and other authentication-related parameters. The operating system can compare the message digest value in the authentication response information with the expected message digest value stored in the authentication lookup information set. If the comparison results match, it can be determined that the target application has passed the authentication verification, and the authentication verification result can be "authentication verification successful"; if the comparison results do not match, the authentication verification result can be "authentication verification failed". To ensure the accuracy and security of the authentication process, the operating system can also check whether the target application's response time is within a preset timeout threshold when comparing message digest values. If the target application's response time is too long, the authentication verification result can also be "authentication verification failed" to prevent potential delayed security attacks.

[0053] In the above process, by pre-storing authentication response information in the read-only data segment of the target application, dynamic calculations during runtime of the target application can be avoided, reducing the impact of the authentication process on the performance of the target application. It also improves the integrity and immutability of the authentication information, enhancing the reliability of the authentication mechanism. Verification using authentication check information from the authentication lookup information set enables the operating system to accurately match each application, ensuring accurate authentication for each application in complex scenarios with multiple concurrent applications.

[0054] In this embodiment of the invention, firstly, in response to the startup of the vehicle's operating system, authentication request information can be obtained from the authentication lookup information set. The authentication lookup information set is pre-filled into the kernel of the operating system and contains authentication request information, which includes at least the application name. The application name is used to indicate the target application that needs to be authenticated. Next, based on the authentication request information, an authentication request signal can be generated and sent to the target application. Finally, in response to receiving authentication response information, the authentication verification information in the authentication lookup information set can be used to perform authentication verification on the authentication response information to obtain an authentication verification result. The authentication response information is generated by the target application in responding to the request and is pre-stored in the read-only data segment of the target application. The authentication verification result is used to characterize whether the target application has successfully performed authentication verification. The authentication lookup information set in this application is pre-filled into the operating system kernel. This set can contain relevant information about each application requiring authentication, enabling automated execution of the authentication process and fulfilling authentication requests for the target application. By modifying the operating system kernel code only once, it avoids the frequent development and modification of operating system authentication information required in traditional authentication processes. Furthermore, by pre-storing authentication response information in the target application's read-only data segment and responding to authentication request signals, it avoids additional authentication response calculations during target application runtime, reducing the impact of the authentication process on target application performance. It also avoids the need for additional authentication response information development for the application, thus solving the technical problem in related technologies where frequent authentication code development and maintenance are required to authenticate in-vehicle applications, leading to high costs.

[0055] In this embodiment of the invention, obtaining authentication request information from the authentication lookup information set includes: using the inspection module in the operating system to query the authentication lookup information set according to a preset frequency corresponding to the target application to obtain authentication request information, wherein the preset frequency is stored in the authentication lookup information set and the preset frequency is used to represent the predefined frequency of authentication requests to the target application.

[0056] The aforementioned inspection module can refer to a software component set in the operating system used to determine the target application that needs to be authenticated. By reading the information in the authentication lookup information set, the inspection module can determine the authentication requirements of each application, including preset frequency and preset timeout.

[0057] The aforementioned preset frequency can refer to the defined cycle or frequency of authentication requests to various target applications, stored in the authentication lookup information set. The preset frequency can be set according to the importance, security risks, and operational characteristics of the application. For example, a higher authentication frequency can be set for some critical security applications, while a lower frequency can be set for some non-critical applications. The preset frequency can be determined according to actual needs.

[0058] In one optional embodiment, after the operating system starts and loads the authentication lookup information set, the inspection module can begin running. The inspection module can access each target application according to its respective preset frequency, based on the preset frequencies recorded in the authentication lookup information set. This process can be performed in the operating system's kernel mode to reduce interaction overhead with user-mode applications and improve efficiency. The inspection module can utilize the timer function provided by the operating system kernel to set a timer so that when the timer expires, it can query the authentication lookup information set to obtain the application's authentication request information. Based on preset frequencies, the inspection module automates and periodically processes authentication requests, ensuring that the operating system can individually authenticate each application within appropriate time intervals, maintaining the operating system's security.

[0059] In the above process, the inspection module queries the authentication information set at a preset frequency, enabling the vehicle operating system to achieve an automated and frequency-controlled authentication process. The preset frequency setting allows the operating system to perform adaptive and personalized authentication checks for different applications, avoiding inappropriate authentication access to various applications, reducing unnecessary performance losses, and improving the security of the operating system.

[0060] In this embodiment of the invention, generating an authentication request signal based on authentication requirement information and sending the authentication request signal to the target application includes: using an inspection module to send the queried authentication requirement information to a task scheduling module in the operating system; using the task scheduling module to obtain the first process identifier of the target application at the current moment based on the authentication requirement information; generating an authentication request signal based on the first process identifier and the authentication requirement information, and sending the authentication request signal to the target application.

[0061] The aforementioned task scheduling module refers to a software component set up in the operating system that manages the processes of applications running on the operating system. The task scheduling module can determine which processes can run, when they can run, and for how long, based on the operating system's resource allocation strategy and the application's priority. The task scheduling module can also receive authentication request information provided by the inspection module, determine the current state and location of the target application based on the authentication request information, and then further initiate authentication requests.

[0062] The aforementioned first process identifier can refer to the process number assigned by the operating system kernel to the target application's process. Based on this first process identifier, the operating system can accurately identify and control the process corresponding to the target application. When the task scheduling module receives the authentication request information from the target application, it can look up or obtain the application's current first process identifier, which is then used to accurately send authentication request signals to the target application subsequently.

[0063] In one optional embodiment, after the inspection module queries the authentication lookup information set at a preset frequency and obtains the authentication request information of the target application, it can pass the authentication request information to the task scheduling module. The task scheduling module can, based on the authentication request information, find the current running status and location of the target application in the operating system. Specifically, it can obtain the first process identifier of the target application by querying the process table of the operating kernel. After obtaining the first process identifier, the task scheduling module can generate an authentication request signal based on the first process identifier and the authentication request information. The authentication request signal can contain the authentication request of the target application and can be sent to the target application through the signal mechanism of the operating system kernel, ensuring that the authentication request signal can directly and accurately reach the process corresponding to the target application. To ensure the correct generation and transmission of the signal, the task scheduling module can also cooperate with other modules in the operating system kernel, such as the signal processing module, to ensure that the authentication request signal is correctly formatted before transmission and can be correctly recognized and processed by the target application.

[0064] In the above process, the task scheduling module and the first process identifier are used to generate and send authentication request signals. Through the task scheduling module and the first process identifier, the operating system can accurately initiate authentication requests for the target application, which can reduce the interference of the authentication process on other processes of the operating system and improve the accuracy and efficiency of the authentication process.

[0065] In this embodiment of the invention, the method further includes: in response to the authentication verification result being that the authentication verification of the target application is successful, updating the authentication timestamp corresponding to the target application in the authentication lookup information set based on the current time; in response to the authentication verification result being that the authentication verification of the target application is unsuccessful, controlling the target application to stop running.

[0066] The authentication timestamp mentioned above refers to the time when the target application last successfully passed authentication verification, recorded in the authentication lookup information set. The authentication timestamp can be updated after each successful authentication to reflect the new authentication status, helping the operating system quickly determine the current legitimacy of the application.

[0067] In one optional embodiment, after the operating system completes the authentication verification of the target application and obtains the authentication verification result, it can perform corresponding operations based on the different authentication verification results. If the authentication verification result indicates that the target application has passed the verification, that is, the target application has successfully verified, then the operating system can update the authentication timestamp in the authentication lookup information set, obtain the current system time from the system clock, obtain the current time, and store the current time in the authentication timestamp field corresponding to the target application in the authentication lookup information set, thereby recording the time when the target application last successfully authenticated. If the authentication verification result indicates that the target application has failed the verification, that is, the target application has failed the verification, the operating system can take security measures in a timely manner to control the target application to stop running. Based on the exception handling action information recorded in the authentication lookup information set, it can generate and send a termination signal to the process corresponding to the target application, forcing the target application to stop running, thereby preventing potential security threats from continuing to affect the operating system.

[0068] In the above process, updating the authentication timestamp ensures that the operating system can track the legitimacy status of each application in real time, which helps to dynamically adjust the operating system's security policies. When authentication verification fails, the application can be stopped in time, potential security vulnerabilities can be quickly eliminated, and malicious applications can be prevented from further damaging the operating system.

[0069] In this embodiment of the invention, the method further includes: using an inspection module to determine the time difference between the current time and the authentication timestamp; and controlling the target application to stop running when the time difference is greater than a preset timeout, wherein the preset timeout is stored in the authentication lookup information set.

[0070] The aforementioned preset timeout period can refer to the timeout period for successful authentication of each application stored in the authentication lookup information set. The preset timeout period can be determined according to actual needs.

[0071] In one optional embodiment, during the authentication process of the in-vehicle application, when the operating system receives the authentication response information from the target application, or fails to receive the authentication response information within a certain time, it can assess the time difference between the current time and the authentication timestamp stored in the authentication lookup information set. The time difference can be determined by calling the system clock function to obtain the current system time (i.e., the current moment), and then calculating the difference between this time difference and the authentication timestamp of the target application in the authentication lookup information set. If the calculated time difference exceeds a preset timeout, the operating system can determine that the target application is abnormal. Then, the task scheduling module can generate and send a termination signal to the target application based on the abnormal handling action information recorded in the authentication lookup information set, thereby controlling the target application to stop running.

[0072] In the above process, by setting a preset timeout and monitoring the time difference between the current time and the authentication timestamp, applications that fail to pass authentication within the specified time can be identified and processed in a timely manner. This helps the operating system to quickly eliminate potentially illegal or tampered applications and ensure the secure operation of the operating system.

[0073] In this embodiment of the invention, controlling the target application to stop running includes: using an inspection module to send the second process identifier of the target application at the current moment and the exception handling action information corresponding to the target application to a task scheduling module, wherein the exception handling action information is stored in an authentication lookup information set and is used to describe the corresponding processing action that needs to be executed to control the target application to stop running; and using the task scheduling module to control the target application to stop running based on the second process identifier and the exception handling action information.

[0074] The aforementioned second process identifier can refer to the process identifier used by the operating system when controlling the target application to stop running, and can be used to ensure that the termination signal can be accurately sent to the target application.

[0075] The aforementioned exception handling action information refers to predefined actions that should be taken against the target application when authentication fails or the operating system detects an anomaly, stored in the authentication lookup information set. This exception handling action information may include, but is not limited to, terminating the process or restarting the application. This information ensures that the operating system can take appropriate measures based on the specific application and the anomaly, thereby limiting potential security risks.

[0076] In one optional embodiment, during the authentication verification process, when the inspection module detects that the authentication verification of the target application has failed, or after the time difference exceeds a preset timeout period, it can invoke the exception handling action information stored in the authentication lookup information set. Specifically, the inspection module can obtain the second process identifier of the target application, as well as the exception handling action information corresponding to the target application in the authentication lookup information set. The inspection module can pass the second process identifier and the exception handling action information to the task scheduling module, which can generate a corresponding termination signal and send it to the target application to ensure that the authentication mechanism can respond to the abnormal state of the application in real time and take measures to prevent the spread of potential security threats. To further enhance the security of the operating system, the operating system can also include a logging mechanism to record the execution details of each exception handling action, which may include the name of the abnormal application, process identifier, specific reasons for authentication failure, etc. Setting up a logging mechanism helps with subsequent security auditing and problem investigation, and can help users quickly locate problems and repair the operating system.

[0077] In the above process, the authentication lookup information set pre-stores exception handling action information corresponding to each application. This allows the operating system to take timely exception handling measures, such as terminating the abnormal application, in the event of authentication failure or timeout, preventing the abnormal application from continuing to run and potentially causing security problems. By using a second process identifier to send a termination signal to the operating system, the operating system can ensure that the termination signal is accurately delivered to the target application, avoiding the risk of accidental operation or accidental termination of other applications.

[0078] According to another aspect of the present invention, an authentication method for in-vehicle applications is also provided. Figure 2 This is a flowchart of an authentication method for an in-vehicle application according to an embodiment of the present invention, such as... Figure 2 As shown, the method includes the following steps:

[0079] Step S202: In response to receiving the authentication request signal, the system uses data pre-stored in the read-only data segment to request and respond to the authentication request signal, thereby obtaining authentication response information.

[0080] The authentication request signal was obtained using the method described above.

[0081] Step S204: Send the authentication response information to the operating system.

[0082] The authentication response information is used to perform the above method to authenticate and verify the target application.

[0083] In this embodiment of the invention, the authentication request signal is responded to using data pre-stored in a read-only data segment to obtain authentication response information. This includes: using a signal processing function pre-defined in the target application to call the data stored in the read-only data segment to respond to the authentication request signal and obtain authentication response information.

[0084] The aforementioned signal handling function can refer to a function predefined in the target application to handle authentication request signals. When the application receives an authentication request signal, the signal handling function can be automatically called to execute the corresponding authentication response logic. The design and implementation of the signal handling function can follow the operating system specifications to ensure that it can correctly interpret the authentication request signal, access the read-only data segment inside the application, and generate authentication response information.

[0085] In one optional embodiment, when the target application receives an authentication request signal sent by the operating system, a predefined signal handling function within the target application can be activated. The signal handling function can access authentication data stored in a read-only data segment of the target application. This authentication data may include the application name, a preset message digest value, and information required for the authentication response. The use of the read-only data segment ensures the integrity and security of the authentication data, preventing damage from internal application logic errors or external attacks. Next, the signal handling function can generate authentication response information based on this authentication data. This may include specific formatting of the authentication data, such as using a message digest algorithm combined with the application name and a random string to generate a verification identifier code to prove the application's legitimacy. After the authentication response information is generated, the signal handling function can call a system call function provided by the system through a user-mode interface to send the authentication response information back to the operating system, completing the authentication response.

[0086] In the above process, the real-time response characteristics of the signal processing function enable fast authentication response and reduce latency in the authentication process. The implementation of the signal processing function can be standardized, and the application can support the authentication mechanism without complex coding, which reduces the development difficulty of the application in the vehicle operating system and speeds up the deployment of the application.

[0087] In this embodiment of the invention, sending authentication response information to the operating system includes: using a signal processing function to call a user-mode interface in the target application to pass the authentication response information to a system call function; and using the system call function to send the authentication response information to the operating system.

[0088] The aforementioned user-mode interface can refer to the interface used by an application to exchange authentication information with the operating system. It may include functions or libraries that encapsulate system calls, enabling the application to send authentication response information to the operating system in a relatively simple way.

[0089] The aforementioned system call functions can refer to a series of kernel function interfaces provided by the operating system. By calling these system call functions, applications can achieve direct communication with the underlying operating system. In this application, the system call functions can be used to receive authentication response information from the application and forward it to the corresponding module of the operating system kernel to complete the closed loop of the authentication process.

[0090] In one optional embodiment, in the target application, after the signal processing function generates authentication response information, it can call a function defined in the user-mode interface to package the authentication response information and pass it to the system call function. The user-mode interface can convert the data format generated by the application into a form acceptable to the system call function, ensuring data integrity and compatibility. When the authentication response information is passed to the system call function through the user-mode interface, the system call function can be responsible for communicating with the operating system and can send the authentication response information to the operating system via a system call. The system call function can convert the authentication response information into a data structure that the operating system can understand, and then, through the system call mechanism, cross the boundary between user mode and kernel mode to send the data to the corresponding module in the operating system kernel space, such as the inspection module or the task scheduling module, to complete the task of authentication verification or updating the authentication status.

[0091] In the above process, authentication and response information is transmitted through user-mode interfaces and system call functions. The encapsulation of user-mode interfaces reduces the complexity of direct interaction between applications and the kernel, allowing software developers to implement authentication and response logic without needing a deep understanding of the operating system kernel details. Using system call functions to transmit authentication and response information provides the operating system with a unified interface to receive and process authentication and response information from different applications, enhancing the operating system's scalability and maintainability.

[0092] The technical solution proposed in this application is described below with reference to an optional embodiment. This application proposes an automatic generation method for cross-platform application authentication, and proposes a cross-platform reusable automation mechanism to at least solve the problems of cross-platform compatibility and manual coding. This application automatically compiles the application's legality verification code into the executable program through mechanisms such as modification of the toolchain and operating system kernel, automatic code insertion, and configuration file parsing; and modifies the operating system code once, cooperating with the application to perform legality verification during operating system runtime. In this way, software developers can write configuration files for the embedded operating system code during the operating system construction process, and can write the information of the program to be verified into the operating system kernel once. During the application linking stage, the corresponding verification code is inserted into the signal handling logic, and the verification information is returned to the operating system kernel through operating system callbacks, and then further processing is performed based on the legality. This application requires only one modification to the linker, eliminating the need for repetitive work; it eliminates the need to rewrite the operating system application source code, requiring only recompilation; the operating system kernel only requires a single modification; design changes can occur during the configuration file replacement step; users do not need systematic knowledge of the specific verification process; the configuration file syntax is simple, resulting in low modification costs; this application is cross-platform compatible, therefore the mechanisms, principles, and methods are applicable to various operating systems.

[0093] This application allows defining the following authentication lookup information set structure on the operating system side: Application Name (Name), which can be encoded in UTF-8 (undependent on a specific character set), with the first byte (Byte) representing the length. Identifier (UID), calculated using the application name and a random string provided by the application according to a message digest algorithm. Preset Frequency (Freq), defining the frequency at which the Ranger module queries and processes the target application's operations. Preset Timeout, defining the application response timeout in 0.1 seconds. Exception Handling Action Information (ACT), the action requested by the Ranger module to stop the target application after an exception is detected. Process Identifier (PID), generated based on the application's identifier (UID) and process ID, used for executing exception handling action information. Authentication Timestamp (LAST), the timestamp of the application's response via operating system calls. It can also add new system call code, which can directly send user data to the task scheduling module for processing.

[0094] The Ranger module's code logic can include the following: it can periodically poll the data within the authentication lookup information set in stages to identify timeout programs that do not conform to the configuration policy and send the information to the task scheduling module for processing. It can also cyclically send requests to the processes configured in the authentication lookup information set at a preset frequency, and send authentication request signals to the processes through the task scheduling module.

[0095] The task scheduling module (WorkQ) code logic may include the following: receiving application responses and updating the authentication timestamp in the authentication lookup information set; receiving timeout warnings from the inspection module and performing corresponding exception handling actions based on the process identifier of the warning, such as terminating the process; and receiving query requests from the inspection module and sending authentication request signals to the application.

[0096] Additionally, on the operating system side, the linker can use configuration files to populate the authentication lookup information set. The user-mode interface, which can be a non-kernel program, can provide libraries for users, allowing applications to indirectly use system calls.

[0097] Figure 3 This is a schematic diagram of an optional operating system-side configuration according to an embodiment of the present invention, such as... Figure 3 As shown, the operating system kernel source code can contain task scheduling logic, new system calls, inspection tasks, and authentication lookup information set structure definitions; the operating system kernel can contain the authentication lookup information set, inspection module, task scheduling module, and system call functions. The linker can populate the authentication lookup information set based on the operating system kernel source code and configuration files. The inspection module can obtain information from the authentication lookup information set and can pass information to the task scheduling module; the task scheduling module can interact with the authentication lookup information set and can receive information passed by system call functions.

[0098] In the application side of this application, during linking, the linker can manually pass the target program name and a random string. The linker can place the application name data into the read-only data segment of the binary program, calculate the message digest value based on the random string, and store it in the read-only data segment. The linker can link the object file of the signal handling function into the target program and retrieve the data using the agreed application name and process identifier address. During program initialization, the process identifier can be obtained using the system-provided program programming interface and stored in a one-time non-read-only area for use by the signal handling function. When the signal handling function receives a signal from the operating system, it recognizes that the operating system kernel requires the program to provide feedback on the validity verification result. The signal handling function can read the process identifier, application name, and identifier, and indirectly pass the data to the system call function by calling the user-mode interface. The system call function can send the response information to the operating system kernel and wait for the operating system kernel to process it. Thus, the application completes the process from receiving the signal to returning the validity information. For the application developer, the above process can be seamless, that is, by extending the functionality of the linker to create this mechanism, it does not increase the programming burden.

[0099] Figure 4 This is a schematic diagram of an optional target application-side setting according to an embodiment of the present invention, such as... Figure 4 As shown, the linker can populate link parameters into the read-only data segment, link the application source code to the target application, and insert code into the signal handling function template in the linker to obtain signal handling functions. The signal handling functions in the target application can respond to authentication request signals, retrieve information from the read-only data segment, and pass the retrieved information to the user-space interface.

[0100] In the technical solution proposed in this application, the inspection module can poll the authentication lookup information set to determine which application needs to be verified. The inspection module can send a verification request, and the task scheduling module can obtain the first process identifier based on the verification request. An authentication request signal is sent using the first process identifier. This triggers the execution of a signal handling function, which can obtain relevant application data and call user-mode library code. A system call is then made, pushing the information to the task scheduling module for execution. Based on the information, verification information is retrieved from the authentication lookup information set to confirm legality, and the authentication timestamp is updated, thus completing the authentication process. The inspection module can also find programs that have timed out and send the program's process identifier and exception handling action information to the task scheduling module. The task scheduling module can then send a termination signal to the application based on the exception handling action information, forcing the application to exit.

[0101] Figure 5This is a schematic diagram of an optional authentication process for a target application according to an embodiment of the present invention, such as... Figure 5 As shown, the operating system kernel can contain an authentication lookup information set, a patrol module, a task scheduling module, and system call functions; the target application can contain signal handling functions and read-only data segments. The patrol module can retrieve information from the authentication lookup information set and pass it to the task scheduling module. The task scheduling module can combine the information from the authentication lookup information set to generate authentication request information and send it to the target application. The target application can respond to the authentication request signal, retrieve information from the read-only data segment, and pass the retrieved information to the task scheduling module via user-mode interface and system call functions to authenticate the target application. The task scheduling module can then control the target application to stop running as needed.

[0102] This application proposes a cross-platform solution that eliminates the need for additional coding in application development, requiring only parameter passing; it is based on a toolchain and configuration files; it utilizes signal processing functions and new system calls for expansion; and the inspection and task scheduling modules are written based on an authentication-based information lookup approach.

[0103] According to another aspect of the present invention, an authentication device for in-vehicle applications is also provided. This device can execute the authentication method for in-vehicle applications described in the above embodiments. The specific implementation method and preferred application scenarios are the same as those described in the above embodiments, and will not be repeated here.

[0104] Figure 6 This is a schematic diagram of an authentication device for an in-vehicle application according to an embodiment of this application, such as... Figure 6 As shown, the device includes the following: an acquisition module 602, a generation module 604, and a verification module 606.

[0105] The acquisition module 602 is used to acquire authentication request information from the authentication lookup information set in response to the startup of the vehicle's operating system. The authentication lookup information set is pre-filled into the kernel of the operating system and contains authentication request information, which includes at least the application name, indicating the target application that needs to be authenticated. The generation module 604 is used to generate an authentication request signal based on the authentication request information and send the authentication request signal to the target application. The verification module 606 is used to verify the authentication response information using the authentication verification information in the authentication lookup information set in response to receiving authentication response information, and obtain the authentication verification result. The authentication response information is generated by the target application in responding to the request and is pre-stored in the read-only data segment of the target application. The authentication verification result is used to indicate whether the target application has successfully completed the authentication verification.

[0106] The acquisition module is also used to use the inspection module in the operating system to query the authentication lookup information set according to the preset frequency corresponding to the target application to obtain authentication request information. The preset frequency is stored in the authentication lookup information set and is used to represent the predefined frequency of authentication requests to the target application.

[0107] The generation module is also used to send the authentication request information obtained by the inspection module to the task scheduling module in the operating system; use the task scheduling module to obtain the first process identifier of the target application at the current time based on the authentication request information; generate an authentication request signal based on the first process identifier and the authentication request information, and send the authentication request signal to the target application.

[0108] The verification module is also used to update the authentication timestamp of the target application in the authentication lookup information set based on the current time when the authentication verification result is successful; and to control the target application to stop running when the authentication verification result is unsuccessful.

[0109] The acquisition module is also used to determine the time difference between the current time and the authentication timestamp using the inspection module; if the time difference is greater than the preset timeout, the target application is controlled to stop running, wherein the preset timeout is stored in the authentication lookup information set.

[0110] The acquisition module is also used to send the second process identifier of the target application at the current moment and the exception handling action information corresponding to the target application to the task scheduling module using the inspection module. The exception handling action information is stored in the authentication lookup information set and is used to describe the corresponding processing action that needs to be executed to control the target application to stop running. The task scheduling module controls the target application to stop running based on the second process identifier and the exception handling action information.

[0111] According to another aspect of the present invention, an authentication device for in-vehicle applications is also provided. This device can execute the authentication method for in-vehicle applications described in the above embodiments. The specific implementation method and preferred application scenarios are the same as those described in the above embodiments, and will not be repeated here.

[0112] Figure 7 This is a schematic diagram of an authentication device for an in-vehicle application according to an embodiment of this application, such as... Figure 7 As shown, the device includes the following: a response module 702 and a transmission module 704.

[0113] The response module 702 is used to respond to the received authentication request signal by using data pre-stored in the read-only data segment to request and respond to the authentication request signal, thereby obtaining authentication response information. The authentication request signal is obtained using the method described above. The sending module 704 is used to send the authentication response information to the operating system. The authentication response information is used to execute the method described above to perform authentication verification on the target application.

[0114] The response module is also used to call data stored in the read-only data segment using a predefined signal processing function in the target application to respond to the authentication request signal and obtain authentication response information.

[0115] The sending module is also used to call the user-mode interface in the target application using a signal processing function to pass the authentication response information to the system call function; and to send the authentication response information to the operating system using the system call function.

[0116] Embodiments of this application also provide an electronic device, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of the present invention during runtime.

[0117] The aforementioned memory can refer to devices inside a computer used to store data and programs, including RAM, hard disks, etc. RAM can be used to temporarily store running programs and data, while hard disks can be used to store programs and data long-term. Memory enables the computer to read and write data and execute programs. The aforementioned processor is responsible for executing instructions in computer programs and performing data processing. It can also be responsible for controlling and executing various operations, including arithmetic operations, logical operations, and data transmission.

[0118] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of the present invention.

[0119] The aforementioned computer storage media can refer to the media used in computer memory to store certain discontinuous physical quantities. Computer storage media mainly include semiconductors, magnetic cores, magnetic drums, magnetic tapes, laser discs, etc. Computer-readable storage media include stored programs, which can be a set of instructions that a computer can recognize and execute, running on an electronic computer to meet certain information needs.

[0120] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the methods of various embodiments of the present invention.

[0121] The aforementioned computer program products can refer to software programs that have been written, tested, and released, and can run on computers or other devices. Computer program products can include application programs, operating systems, utility software, etc., used to achieve specific functions or solve specific problems.

[0122] Embodiments of this application also provide a computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the methods in various embodiments of the present invention.

[0123] The aforementioned non-volatile computer-readable storage medium can refer to a medium for storing data. Non-volatile computer-readable storage media can retain data without loss when power is off and can be used to store long-term data, such as operating systems, applications, and user files. Non-volatile storage media can include hard disk drives, solid-state drives, optical disks, and flash memory storage devices, etc.

[0124] Embodiments of this application also provide a computer program that, when executed by a processor, implements the methods described in the various embodiments of the present invention.

[0125] The aforementioned computer program can refer to a set of instructions used to tell the computer to perform specific tasks or operations. Computer programs can be written by programmers using specific programming languages ​​and can include algorithms, data structures, logic, and control flow. Computer programs can be used for a variety of purposes, including application software, operating systems, etc.

[0126] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0127] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection can be through some interfaces; the indirect coupling or communication connection between units or modules can be electrical or other forms.

[0128] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0129] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0130] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0131] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. An authentication method for an in-vehicle application, characterized in that, include: In response to the startup of the vehicle's operating system, authentication requirement information is obtained from the authentication lookup information set, wherein the authentication lookup information set is pre-filled into the kernel of the operating system, the authentication lookup information set contains the authentication requirement information, and the authentication requirement information includes at least the application name, the application name being used to indicate the target application that needs to be authenticated. Based on the authentication requirement information, an authentication request signal is generated and sent to the target application. In response to receiving authentication response information, the authentication response information is used to perform authentication verification on the authentication response information in the authentication lookup information set to obtain an authentication verification result. The authentication response information is generated by the target application in responding to a request. The authentication response information is pre-stored in the read-only data segment of the target application. The authentication verification result is used to characterize whether the target application has successfully performed authentication verification.

2. The authentication method for in-vehicle applications according to claim 1, characterized in that, Obtain authentication requirement information from the authentication lookup information set, including: Using the inspection module in the operating system, the authentication lookup information set is queried according to the preset frequency corresponding to the target application to obtain the authentication request information. The preset frequency is stored in the authentication lookup information set and is used to represent the predefined frequency of authentication requests to the target application.

3. The authentication method for in-vehicle applications according to claim 1, characterized in that, Based on the authentication requirement information, an authentication request signal is generated and sent to the target application, including: Using the inspection module, the authentication requirement information obtained from the query is sent to the task scheduling module in the operating system; Using the task scheduling module, the first process identifier of the target application at the current moment is obtained based on the authentication requirement information; Based on the first process identifier and the authentication requirement information, the authentication request signal is generated and sent to the target application.

4. The authentication method for in-vehicle applications according to claim 1, characterized in that, The method further includes: In response to the authentication verification result indicating that the authentication verification of the target application is successful, the authentication timestamp corresponding to the target application in the authentication lookup information set is updated based on the current time. In response to the authentication verification result indicating that the authentication verification of the target application failed, the target application is controlled to stop running.

5. The authentication method for in-vehicle applications according to claim 4, characterized in that, The method further includes: The inspection module is used to determine the time difference between the current time and the authentication timestamp; If the time difference is greater than a preset timeout, the target application is controlled to stop running, wherein the preset timeout is stored in the authentication lookup information set.

6. The authentication method for an in-vehicle application according to claim 4 or 5, characterized in that, Controlling the target application to stop running includes: Using the inspection module, the second process identifier of the target application at the current moment and the exception handling action information corresponding to the target application are sent to the task scheduling module. The exception handling action information is stored in the authentication lookup information set and is used to describe the corresponding processing action that needs to be executed to control the target application to stop running. Using the task scheduling module, based on the second process identifier and the exception handling action information, the target application is controlled to stop running.

7. An authentication method for an in-vehicle application, characterized in that, include: In response to receiving an authentication request signal, the system uses data pre-stored in a read-only data segment to request and respond to the authentication request signal, thereby obtaining authentication response information. The authentication request signal is obtained using the method described in claim 1. The authentication response information is sent to the operating system, wherein the authentication response information is used to execute the method described in claim 1 to authenticate and verify the target application.

8. The authentication method for an in-vehicle application according to claim 7, characterized in that, The authentication request signal is responded to using data pre-stored in a read-only data segment to obtain authentication response information, including: Using a predefined signal processing function in the target application, the data stored in the read-only data segment is invoked to respond to the authentication request signal, thereby obtaining the authentication response information.

9. The authentication method for an in-vehicle application according to claim 7, characterized in that, Sending the authentication response information to the operating system includes: Using a signal processing function, the user-mode interface in the target application is called to pass the authentication response information to the system call function; The authentication response information is sent to the operating system using a system call function.

10. An authentication device for an in-vehicle application, characterized in that, include: The acquisition module is used to obtain authentication requirement information from the authentication lookup information set in response to the startup of the vehicle's operating system. The authentication lookup information set is pre-filled into the kernel of the operating system. The authentication lookup information set contains the authentication requirement information. The authentication requirement information includes at least the application name, which is used to indicate the target application that needs to be authenticated. The generation module is used to generate an authentication request signal based on the authentication requirement information and send the authentication request signal to the target application. The verification module is used to, in response to receiving authentication response information, perform authentication verification on the authentication response information using the authentication verification information in the authentication lookup information set, and obtain an authentication verification result. The authentication response information is generated by the target application in responding to a request, and the authentication response information is pre-stored in the read-only data segment of the target application. The authentication verification result is used to characterize whether the target application has successfully performed authentication verification.

11. An authentication device for an in-vehicle application, characterized in that, include: A response module is configured to respond to a received authentication request signal by using data pre-stored in a read-only data segment to request and respond to the authentication request signal, thereby obtaining authentication response information, wherein the authentication request signal is obtained using the method described in claim 1; A sending module is used to send the authentication response information to the operating system, wherein the authentication response information is used to execute the method described in claim 1 to authenticate and verify the target application.

12. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, executes the authentication method of the in-vehicle application according to any one of claims 1 to 9.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the storage medium is located to execute the authentication method of the in-vehicle application according to any one of claims 1 to 9.

14. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the authentication method for an in-vehicle application according to any one of claims 1 to 9.

Images