CN114124401B - Data authentication method, device, equipment and storage medium - Google Patents

Data authentication method, device, equipment and storage medium Download PDF

Info

Publication number
CN114124401B
CN114124401B CN202111290898.7A CN202111290898A CN114124401B CN 114124401 B CN114124401 B CN 114124401B CN 202111290898 A CN202111290898 A CN 202111290898A CN 114124401 B CN114124401 B CN 114124401B
Authority
CN
China
Prior art keywords
verification
authentication data
check code
authentication
mcu
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202111290898.7A
Other languages
Chinese (zh)
Other versions
CN114124401A (en
Inventor
张博
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Faurecia Clarion Electronics Fengcheng Co Ltd
Original Assignee
Faurecia Clarion Electronics Fengcheng Co Ltd
Faurecia Clarion Electronics Foshan Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Faurecia Clarion Electronics Fengcheng Co Ltd, Faurecia Clarion Electronics Foshan Co Ltd filed Critical Faurecia Clarion Electronics Fengcheng Co Ltd
Priority to CN202111290898.7A priority Critical patent/CN114124401B/en
Publication of CN114124401A publication Critical patent/CN114124401A/en
Application granted granted Critical
Publication of CN114124401B publication Critical patent/CN114124401B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/068—Authentication using credential vaults, e.g. password manager applications or one time password [OTP] applications

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Storage Device Security (AREA)

Abstract

The application provides a data authentication method, a device, equipment and a storage medium, relates to the technical field of vehicles, and can improve the authentication success probability of vehicle-mounted important data. The method comprises the following steps: determining that the first authentication data stored in the MCU fails to pass the verification of the first check code; the first check code is stored in the MCU in advance; acquiring second authentication data and a second check code; the second authentication data and the second check code are both pre-stored in the SOC; in case the second authentication data passes the verification of the second check code, an authentication operation is performed based on the second authentication data.

Description

Data authentication method, device, equipment and storage medium
Technical Field
The present application relates to the field of vehicle technologies, and in particular, to a data authentication method, device, apparatus, and storage medium.
Background
Currently, the important data for authentication in-vehicle infotainment systems (in-vehicle infotainment, IVI) are typically stored in the solid state memory FLASH of the micro control unit (microcontroller unit, MCU).
However, the power supply of the IVI system is usually derived from a battery and an engine of a vehicle body, but the electronic environment in the vehicle is more disturbed, such as power supply noise interference during ignition, and excessive instantaneous current fluctuation caused by power-on and power-off of the battery, can cause logic disorder of an internal circuit of the MCU, and important data cannot be read from the FLASH by a steady-state reading signal, so that problems of abnormal functions, authentication failure and the like of the IVI system are caused.
Disclosure of Invention
The application provides a data authentication method, a device, equipment and a storage medium, which can improve the authentication success probability of vehicle-mounted important data.
In order to achieve the above purpose, the application adopts the following technical scheme:
in a first aspect, the present application provides a data authentication method, applied to a system on a chip SOC, the method may include: determining that the first authentication data stored in the MCU fails to pass the verification of the first check code; the first check code is stored in the MCU in advance; acquiring second authentication data and a second check code; the second authentication data and the second check code are both pre-stored in the SOC; in case the second authentication data passes the verification of the second check code, an authentication operation is performed based on the second authentication data.
Optionally, determining that the first authentication data stored in the MCU fails verification of the first check code includes: receiving a verification failure message sent by the MCU; the verification failure message is used for indicating that the first authentication data fails verification of the first verification code; the verification failure message is generated by the MCU in case the first authentication data fails verification of the first verification code.
Optionally, determining that the first authentication data stored in the MCU fails verification of the first check code includes: acquiring first authentication data and a first check code; determining a target check code of the first authentication data; and under the condition that the target check code is inconsistent with the first check code, determining that the first authentication data stored in the MCU does not pass the verification of the first check code.
Optionally, in the case that the target check code is identical to the first check code, updating the second authentication data in the SOC based on the received first authentication data, and updating the second check code in the SOC based on the received first check code.
Optionally, acquiring the first authentication data and the first check code includes: receiving a verification success message sent by the MCU, and acquiring first authentication data and a first verification code from the verification success message; the verification success message is generated by the MCU after determining that the first authentication data passes the verification of the first verification code.
In a second aspect, the present application provides a data authentication device applied to a system on chip SOC, the data authentication device comprising: the determining unit is used for determining that the first authentication data stored in the MCU fails to pass the verification of the first check code; the first check code is stored in the MCU in advance; the acquisition unit is used for acquiring second authentication data and a second check code; the second authentication data and the second check code are both pre-stored in the SOC; and an authentication unit for performing an authentication operation based on the second authentication data in case the second authentication data passes a check of the second check code.
Optionally, the determining unit is specifically configured to: receiving a verification failure message sent by the MCU; the verification failure message is used for indicating that the first authentication data fails verification of the first verification code; the verification failure message is generated by the MCU in case the first authentication data fails verification of the first verification code.
Optionally, the determining unit is specifically configured to: acquiring first authentication data and a first check code; determining a target check code of the first authentication data; and under the condition that the target check code is inconsistent with the first check code, determining that the first authentication data stored in the MCU does not pass the verification of the first check code.
Optionally, the data authentication device further comprises an updating unit; the updating unit is used for updating the second authentication data in the SOC based on the received first authentication data and updating the second check code in the SOC based on the received first check code under the condition that the target check code is consistent with the first check code.
Optionally, the acquiring unit is specifically configured to: receiving a verification success message sent by the MCU, and acquiring first authentication data and a first verification code from the verification success message; the verification success message is generated by the MCU after determining that the first authentication data passes the verification of the first verification code.
In a third aspect, the present application provides a terminal comprising: a processor, a communication interface, and a memory. Wherein the memory is used to store one or more programs. The one or more programs include computer-executable instructions that, when executed by the terminal, cause the terminal to perform the data authentication method of the first aspect and any of its various alternative implementations.
In a fourth aspect, the present application provides a computer readable storage medium having instructions stored therein which, when executed by a computer, perform the data authentication method of the first aspect and any of its various alternative implementations.
In a fifth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the data authentication method of the first aspect and any of its various alternative implementations.
The data authentication method and the data authentication device provided by the application are characterized in that the second authentication data and the second CRC code are stored in the EMMC of the SOC. After the SOC receives the verification failure message sent by the MCU, the SOC determines that the first authentication data in the MCU fails to verify. Further, the SOC obtains second authentication data and a second CRC code from the EMMC thereof to check the second authentication data, and determines to provide an authentication basis for an application of the IVI system based on the second authentication data if the second authentication data passes the second CRC code check. Therefore, even if the MCU is in error in reading data due to factors such as circuit logic disorder or current fluctuation in the process of reading the first authentication data, the SOC can ensure that each function of the IVI system is normal according to the second authentication data stored by the SOC.
Drawings
Fig. 1 is a schematic structural diagram of a terminal according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of another terminal according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a data authentication method according to an embodiment of the present application;
fig. 4 is a flow chart of another data authentication method according to an embodiment of the present application;
fig. 5 is a flow chart of another data authentication method according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a data authentication device according to an embodiment of the present application.
Detailed Description
The following describes in detail a data authentication method, device, equipment and storage medium provided in the embodiments of the present application with reference to the accompanying drawings.
The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.
The terms "first" and "second" and the like in the description and in the drawings are used for distinguishing between different objects or between different processes of the same object and not for describing a particular order of objects.
Furthermore, references to the terms "comprising" and "having" and any variations thereof in the description of the present application are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed but may optionally include other steps or elements not listed or inherent to such process, method, article, or apparatus.
It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
In the description of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more.
The data authentication method provided by the embodiment of the application can be applied to the terminal shown in figure 1,
as shown in fig. 1, the terminal 10 includes a system-on-a-chip (SOC) and an MCU, and the terminal 12 may be an in-vehicle communication terminal.
The SOC and the MCU can be connected through line communication.
It should be noted that fig. 1 is only an exemplary architecture diagram, and the terminal may further include other functional units besides the functional units shown in fig. 1, which is not limited by the embodiment of the present application.
Fig. 2 shows a schematic diagram of one possible architecture of a terminal, as shown in fig. 2, the terminal 20 comprising a processor 201, a communication interface 202, a communication line 203 and a memory 204.
The processor 201 may be a CPU, general purpose processor network processor (network processor, NP), digital signal processor (digital signal processing, DSP), microprocessor, microcontroller, programmable logic device (programmable logic device, PLD), or any combination thereof, among others. The processor 201 may also be other devices with processing functions, such as, without limitation, circuits, devices, or software modules. In one example, processor 201 may include one or more CPUs, such as CPU0 and CPU1 in fig. 2.
Communication interface 202 is used to communicate with other devices or other communication networks. The other communication network may be an ethernet, a radio access network (radio access network, RAN), a wireless local area network (wireless local area networks, WLAN), etc. The communication interface may be a module, a circuit, a communication interface, or any device capable of enabling communication.
Communication line 203 for communicating information between the components included in the data authentication system.
Memory 204 for storing instructions. Wherein the instructions may be computer programs.
The memory 204 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device capable of storing static information and/or instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device capable of storing information and/or instructions, an EEPROM, a CD-ROM (compact disc read-only memory) or other optical disk storage, an optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, etc.
It should be noted that the memory 204 may exist separately from the processor 201 or may be integrated with the processor 201. Memory 204 may be used to store instructions or program code or some data, etc. The memory 302 may be located within the terminal 20 or outside the terminal 20, without limitation. The processor 201 is configured to execute instructions stored in the memory 204 to implement a data authentication method according to the following embodiments of the present application.
As an alternative implementation, the terminal 20 comprises a plurality of processors, e.g. in addition to the processor 201 in fig. 2, a processor 207 may be included.
As an alternative implementation, the terminal 20 further comprises an output device 205 and an input device 206. Illustratively, the input device 205 is a keyboard, mouse, microphone, or joystick device, and the output device 205 is a display screen, speaker (spaker), or the like.
In the embodiment of the application, the chip system can be composed of chips, and can also comprise chips and other discrete devices.
Further, actions, terms, and the like, which are referred to between embodiments of the present application, are not limited thereto. The message names of interactions between the devices or parameter names in the messages in the embodiments of the present application are just an example, and other names may be used in specific implementations without limitation.
Further, actions, terms, and the like, which are referred to between embodiments of the present application, are not limited thereto. The message names of interactions between the devices or parameter names in the messages in the embodiments of the present application are just an example, and other names may be used in specific implementations without limitation.
The embodiment of the application provides a data authentication method, which can be applied to the terminal, a data authentication device included in the terminal and other similar equipment including the authentication device. Hereinafter, the application of the data authentication method to the SOC will be described as an example. As shown in fig. 3, the method may include S301-S304:
s301, determining that first authentication data stored in the MCU does not pass through verification of a first check code.
The first check code is stored in the MCU in advance. As a possible implementation manner, the SOC may receive the verification failure message sent by the MCU, where the first authentication data fails verification of the first verification code.
It should be noted that the authentication data is data for performing an authentication operation, and the first check code is used for verifying the authentication data. The first check code is pre-stored in a solid state memory FLASH in the MCU, and the check code can be a cyclic redundancy check CRC code.
Additionally, the authentication data may include an identification code TUID, a vehicle frame number (vehicle identification number, VIN), and a vehicle model configuration code.
For a specific implementation of this step, reference may be made to the following descriptions of S3011-S3015, which are not described here in detail.
S302, the SOC acquires second authentication data and a second check code.
The second authentication data and the second check code are both stored in the SOC in advance.
As a possible implementation, the SOC may obtain the second authentication data and the second check code from the embedded multimedia card EMMC of the SOC.
It should be noted that, the SOC may establish a communication connection with the MCU through a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART), a controller area network (controller area network, CAN) to receive authentication data and a check code sent by the MCU, and store the received authentication data and check code in the EMMC, thereby forming second authentication data and second check code.
S303, the SOC judges whether the second authentication data passes the verification of the second check code;
s304, the SOC performs authentication operation based on the second authentication data under the condition that the second authentication data passes the verification of the second verification code.
As one possible implementation, the SOC may identify, authenticate, and apply configuration via the second authentication data.
It can be understood that when the first authentication data stored in the MCU by the SOC fails to pass the verification of the first check code, whether the second authentication data in the SOC can pass the verification of the second check code is judged, so that the problems of IVI vehicle type configuration errors, identity verification failures and the like caused by no remedial measures after the MCU authenticates the data and verifies errors in the prior art are avoided.
In one design, in order to determine that the first authentication data stored in the MCU does not pass the verification of the first check code, as shown in fig. 4, S301 provided in the embodiment of the present application specifically includes the following S3011:
s3011, the SOC receives a verification failure message sent by the MCU.
The verification failure message is used for indicating that the first authentication data fails verification of the first verification code. The verification failure message is generated by the MCU in case the first authentication data fails verification of the first verification code.
As a possible implementation manner, the SOC may receive the verification failure message sent by the MCU through a UART, SPI, or other communication interface.
In some embodiments, when the IVI system is started, the MCU may calculate whether the first authentication data may pass through the first check code by reading the first authentication data and the first check code in the FLASH.
It can be understood that after authentication data in the MCU fails to be verified, a verification failure message is actively sent to the SOC, so that no remedial measure is required after authentication data in the MCU fails to be verified, and the authentication success rate is improved.
In one design, in order to determine that the first authentication data stored in the MCU does not pass the verification of the first check code, as shown in fig. 4, S301 provided in the embodiment of the present application specifically further includes the following S3012-S3015:
s3012, the SOC acquires the first authentication data and the first check code.
As a possible implementation, the SOC may obtain the first authentication data and the first check code from the MCU.
S3013, the SOC determines a target check code of the first authentication data.
The target check code is a check code calculated by the SOC according to the first authentication data.
As a possible implementation manner, the SOC calculates a target check code according to the first authentication data.
The target verification code may be a CRC code.
S3014, the SOC judges whether the target check code is consistent with the first check code.
S3015, under the condition that the target check code is inconsistent with the first check code, the SOC determines that the first authentication data stored in the MCU does not pass the verification of the first check code.
It can be understood that the SOC can calculate the corresponding target check code according to the first authentication data in the MCU, and then compare the corresponding target check code with the first check code in the MCU, so as to determine whether the target check code is consistent with the first check code, thereby improving the accuracy of the authentication data.
In one design, in the case where the target check code is consistent with the first check code, as shown in fig. 4, after S3014 provided in the embodiment of the present application, the provided method further includes the following S401-S402:
s401, the SOC updates second authentication data in the SOC based on the received first authentication data.
As a possible implementation manner, the SOC may delete the second authentication data currently stored in the EMMC and store the received first authentication data to update the second authentication data in the SOC.
It should be noted that the SOC may store the first authentication data in the EMMC.
S402, the SOC updates a second check code in the SOC based on the received first check code.
As a possible implementation manner, the SOC may delete the second check code currently stored in the EMMC and store the received first check code to update the second check code in the SOC.
The SOC may store the first check code in the EMMC.
It can be appreciated that the SOC can improve the success rate of the SOC to acquire authentication data from the EMMC by updating the second check code and the second verification data in the SOC.
In one design, in order to obtain the first authentication data and the first check code, as shown in fig. 5, S3012 provided in the embodiment of the present application specifically includes the following S501-502:
s501, the SOC receives a verification success message sent by the MCU.
The verification success message is generated by the MCU after determining that the first authentication data passes the verification of the first verification code.
It should be noted that the verification success message includes the first authentication data and the first verification code.
In some embodiments, the MCU reads the first authentication data and the first check code in the FLASH, and when the first authentication data passes the first check code, the MCU generates a check success message.
S502, the SOC acquires first authentication data and a first check code from the check success message.
In one possible implementation, the SOC parses a verification success message to obtain first authentication data and a first check code
It can be appreciated that the second authentication data and the second CRC code are stored in the EMMC of the SOC in the present application. After the SOC receives the verification failure message sent by the MCU, the SOC determines that the first authentication data in the MCU fails to verify. Further, the SOC obtains second authentication data and a second CRC code from the EMMC thereof to check the second authentication data, and determines to provide an authentication basis for an application of the IVI system based on the second authentication data if the second authentication data passes the second CRC code check. Therefore, even if the MCU is in error in reading data due to factors such as circuit logic disorder or current fluctuation in the process of reading the first authentication data, the SOC can ensure that each function of the IVI system is normal according to the second authentication data stored by the SOC.
The embodiment of the application can divide the functional modules or functional units of the terminal according to the method example, for example, each functional module or functional unit can be divided corresponding to each function, and two or more functions can be integrated in one module. The integrated modules may be implemented in hardware, or in software functional modules or functional units. The division of the modules or units in the embodiment of the present application is schematic, which is merely a logic function division, and other division manners may be implemented in practice.
Fig. 6 is a schematic diagram of a possible configuration of the data authentication device according to the above embodiment. As shown in fig. 6, the data authentication device 60 includes a determining unit 601, an acquiring unit 602, and an authentication unit 603.
A determining unit 601, configured to determine that the first authentication data stored in the MCU fails to pass verification of the first check code; the first check code is pre-stored in the MCU. For example, as shown in fig. 3, the determination unit 601 may be used to perform S301.
An obtaining unit 602, configured to obtain second authentication data and a second check code; the second authentication data and the second check code are both pre-stored in the SOC; for example, as shown in fig. 3, the acquisition unit 602 is configured to execute S302.
An authentication unit 603 for performing an authentication operation based on the second authentication data in case the second authentication data passes a check of the second check code. For example, as shown in fig. 3, the authentication unit 603 is used to perform S303.
The specific implementation of the data authentication device 60 may refer to the behavior function of the data authentication device in the data authentication method shown in fig. 3.
In a possible design, as shown in fig. 6, the determining unit 601 provided in the embodiment of the present application is specifically configured to: receiving a verification failure message sent by the MCU; the verification failure message is used for indicating that the first authentication data fails verification of the first verification code; the verification failure message is generated by the MCU in case the first authentication data fails verification of the first verification code. For example, as shown in fig. 4, the determination unit 601 may also be used to perform S3012-S3015.
In a possible design, as shown in fig. 6, the determining unit 601 provided in the embodiment of the present application is specifically configured to: acquiring first authentication data and a first check code; determining a target check code of the first authentication data; and under the condition that the target check code is inconsistent with the first check code, determining that the first authentication data stored in the MCU does not pass the verification of the first check code. For example, as shown in fig. 5, the determination unit 601 may also be used to perform S3031-S3033.
In one possible design, as shown in fig. 6, the data authentication device provided in the embodiment of the present application further includes an updating unit 604; the updating unit 604 is configured to update the second authentication data in the SOC based on the received first authentication data and update the second check code in the SOC based on the received first check code, if the target check code is identical to the first check code. For example, as shown in FIG. 4, the update unit 604 may also be used to perform S401-S402.
In one possible design, as shown in fig. 6, the obtaining unit 602 is specifically configured to: receiving a verification success message sent by the MCU, and acquiring first authentication data and a first verification code from the verification success message; the verification success message is generated by the MCU after determining that the first authentication data passes the verification of the first verification code. For example, as shown in FIG. 5, the acquisition unit 602 may also be used to perform S501-S502.
It can be appreciated that the data authentication device provided by the present application stores the second authentication data and the second CRC code in the EMMC of the SOC. After the SOC receives the verification failure message sent by the MCU, the SOC determines that the first authentication data in the MCU fails to verify. Further, the SOC obtains second authentication data and a second CRC code from the EMMC thereof to check the second authentication data, and determines to provide an authentication basis for an application of the IVI system based on the second authentication data if the second authentication data passes the second CRC code check. Therefore, even if the MCU is in error in reading data due to factors such as circuit logic disorder or current fluctuation in the process of reading the first authentication data, the SOC can ensure that each function of the IVI system is normal according to the second authentication data stored by the SOC.
From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.
Embodiments of the present application provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the data authentication method of the method embodiments described above.
The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores instructions, and when the data authentication device executes the instructions, the data authentication device executes each step executed by the data authentication device in the method flow shown in the method embodiment.
The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access Memory (Random Access Memory, RAM), a Read-Only Memory (ROM), an erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), a register, a hard disk, an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing, or any other form of computer readable storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuit, ASIC). In embodiments of the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The foregoing is merely illustrative of specific embodiments of the present application, and the scope of the present application is not limited thereto, but any changes or substitutions within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (8)

1. A data authentication method applied to a system on chip SOC, comprising:
under the condition that a verification failure message sent by the MCU is received, second authentication data and a second verification code are obtained; the second authentication data and the second check code are both pre-stored in the SOC; the verification failure message is used for indicating that the first authentication data stored in the MCU fails verification of a first verification code; the first check code is stored in the solid-state memory FLASH of the MCU in advance; the verification failure message is generated by the MCU under the condition that the first authentication data fails to pass the verification of the first verification code; the MCU is used for determining whether the first authentication data can pass through the first check code when the vehicle-mounted information entertainment system is started; the authentication data comprises one or more of an identification code/frame number and a vehicle type configuration code;
performing an authentication operation based on the second authentication data in case the second authentication data passes a check of the second check code;
in the event that it is determined that the first authentication data passes verification of the first check code, updating the second authentication data in the SOC based on the received first authentication data, and updating the second check code in the SOC based on the received first check code.
2. The method for authenticating data according to claim 1, wherein determining that the first authentication data stored in the MCU does not pass verification of the first check code comprises:
acquiring the first authentication data and the first check code;
determining a target check code of the first authentication data;
and under the condition that the target check code is inconsistent with the first check code, determining that the first authentication data stored in the MCU does not pass the verification of the first check code.
3. The method for data authentication according to claim 2, wherein the obtaining the first authentication data and the first check code includes:
receiving a verification success message sent by the MCU, and acquiring the first authentication data and the first verification code from the verification success message; the verification success message is generated by the MCU after determining that the first authentication data passes the verification of the first verification code.
4. The data authentication device is applied to a System On Chip (SOC), and is characterized by comprising an acquisition unit, an authentication unit and an updating unit;
the acquisition unit is used for acquiring second authentication data and a second check code under the condition of receiving a check failure message sent by the MCU; the second authentication data and the second check code are both pre-stored in the SOC; the verification failure message is used for indicating that the first authentication data stored in the MCU fails verification of a first verification code; the first check code is stored in the solid-state memory FLASH of the MCU in advance; the verification failure message is generated by the MCU under the condition that the first authentication data fails to pass the verification of the first verification code; the MCU is used for determining whether the first authentication data can pass through the first check code when the vehicle-mounted information entertainment system is started; the authentication data comprises one or more of an identification code/frame number and a vehicle type configuration code;
the authentication unit is used for performing authentication operation based on the second authentication data in the case that the second authentication data passes the verification of the second verification code;
the updating unit is configured to update the second authentication data in the SOC based on the received first authentication data and update the second check code in the SOC based on the received first check code, in a case where it is determined that the first authentication data passes verification of the first check code.
5. The data authentication device according to claim 4, further comprising a determining unit, in particular for:
acquiring the first authentication data and the first check code;
determining a target check code of the first authentication data;
and under the condition that the target check code is inconsistent with the first check code, determining that the first authentication data stored in the MCU does not pass the verification of the first check code.
6. The data authentication device according to claim 4, wherein the obtaining unit is specifically configured to:
receiving a verification success message sent by the MCU, and acquiring the first authentication data and the first verification code from the verification success message; the verification success message is generated by the MCU after determining that the first authentication data passes the verification of the first verification code.
7. A terminal, the terminal comprising: a processor, a communication interface, and a memory; wherein the memory is configured to store one or more programs, the one or more programs comprising computer-executable instructions that, when executed by the terminal, cause the terminal to perform the data authentication method of any of claims 1 to 3.
8. A computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by a computer, cause the computer to perform the data authentication method of any of claims 1-3.
CN202111290898.7A 2021-11-02 2021-11-02 Data authentication method, device, equipment and storage medium Active CN114124401B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111290898.7A CN114124401B (en) 2021-11-02 2021-11-02 Data authentication method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111290898.7A CN114124401B (en) 2021-11-02 2021-11-02 Data authentication method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114124401A CN114124401A (en) 2022-03-01
CN114124401B true CN114124401B (en) 2023-11-17

Family

ID=80380238

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111290898.7A Active CN114124401B (en) 2021-11-02 2021-11-02 Data authentication method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114124401B (en)

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105376249A (en) * 2015-11-30 2016-03-02 上海汽车集团股份有限公司 Account login method for vehicular information entertainment system and vehicular equipment
CN105519028A (en) * 2015-07-01 2016-04-20 海能达通信股份有限公司 Wireless system access control method and apparatus
CN105653390A (en) * 2014-11-10 2016-06-08 无锡华润矽科微电子有限公司 SoC system verification method
CN107040501A (en) * 2016-02-04 2017-08-11 杭州华为企业通信技术有限公司 It is the authentication method and device of service based on platform
WO2017152875A1 (en) * 2016-03-11 2017-09-14 比亚迪股份有限公司 Secure communication method and apparatus for vehicle, vehicle multimedia system, and vehicle
CN109800104A (en) * 2018-12-18 2019-05-24 盛科网络（苏州）有限公司 Detection method, device, storage medium and the electronic device of data storage
CN110176990A (en) * 2019-05-15 2019-08-27 百度在线网络技术（北京）有限公司 Vehicle assembly replaces recognition methods, device, computer equipment and storage medium
CN110389778A (en) * 2019-07-19 2019-10-29 苏州浪潮智能科技有限公司 A kind of isomery accelerates the MCU firmware upgrade method and relevant apparatus of platform
CN110908682A (en) * 2019-08-08 2020-03-24 中国第一汽车股份有限公司 Firmware upgrading method and system for vehicle controller, vehicle and storage medium
CN112165533A (en) * 2020-10-21 2021-01-01 苏州智加科技有限公司 Data checking and transmitting method, device, equipment, system and storage medium
CN112558875A (en) * 2020-12-14 2021-03-26 北京百度网讯科技有限公司 Data verification method and device, electronic equipment and storage medium
CN112653668A (en) * 2020-12-04 2021-04-13 深圳市广和通无线股份有限公司 Data interaction method and device, computer equipment and storage medium
CN113448643A (en) * 2021-03-23 2021-09-28 中科创达软件股份有限公司 Configuration data management system and method
CN113536278A (en) * 2020-04-20 2021-10-22 深圳市江波龙电子股份有限公司 Authentication method of storage device, storage device and authentication terminal

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9582262B2 (en) * 2014-06-16 2017-02-28 Wipro Limited Systems and methods for installing upgraded software on electronic devices
HK1250307A2 (en) * 2018-08-14 2018-12-07 World Concept Development Ltd Method, device, storage medium and terminal device for authentication

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105653390A (en) * 2014-11-10 2016-06-08 无锡华润矽科微电子有限公司 SoC system verification method
CN105519028A (en) * 2015-07-01 2016-04-20 海能达通信股份有限公司 Wireless system access control method and apparatus
CN105376249A (en) * 2015-11-30 2016-03-02 上海汽车集团股份有限公司 Account login method for vehicular information entertainment system and vehicular equipment
CN107040501A (en) * 2016-02-04 2017-08-11 杭州华为企业通信技术有限公司 It is the authentication method and device of service based on platform
WO2017152875A1 (en) * 2016-03-11 2017-09-14 比亚迪股份有限公司 Secure communication method and apparatus for vehicle, vehicle multimedia system, and vehicle
CN109800104A (en) * 2018-12-18 2019-05-24 盛科网络（苏州）有限公司 Detection method, device, storage medium and the electronic device of data storage
CN110176990A (en) * 2019-05-15 2019-08-27 百度在线网络技术（北京）有限公司 Vehicle assembly replaces recognition methods, device, computer equipment and storage medium
CN110389778A (en) * 2019-07-19 2019-10-29 苏州浪潮智能科技有限公司 A kind of isomery accelerates the MCU firmware upgrade method and relevant apparatus of platform
CN110908682A (en) * 2019-08-08 2020-03-24 中国第一汽车股份有限公司 Firmware upgrading method and system for vehicle controller, vehicle and storage medium
CN113536278A (en) * 2020-04-20 2021-10-22 深圳市江波龙电子股份有限公司 Authentication method of storage device, storage device and authentication terminal
CN112165533A (en) * 2020-10-21 2021-01-01 苏州智加科技有限公司 Data checking and transmitting method, device, equipment, system and storage medium
CN112653668A (en) * 2020-12-04 2021-04-13 深圳市广和通无线股份有限公司 Data interaction method and device, computer equipment and storage medium
CN112558875A (en) * 2020-12-14 2021-03-26 北京百度网讯科技有限公司 Data verification method and device, electronic equipment and storage medium
CN113448643A (en) * 2021-03-23 2021-09-28 中科创达软件股份有限公司 Configuration data management system and method

Also Published As

Publication number Publication date
CN114124401A (en) 2022-03-01

Similar Documents

Publication Publication Date Title
US10713350B2 (en) Unlock and recovery for encrypted devices
US9792440B1 (en) Secure boot for vehicular systems
US11722315B2 (en) Factory data storage and recovery
CN107257346B (en) Single sign-on service access processing method, system end and storage medium
US10360396B2 (en) Token-based control of software installation and operation
KR20150027329A (en) Terminal including fingerprint reader and operating method of the terminal
CN110875819B (en) Password operation processing method, device and system
US20150288528A1 (en) Method for application installation, electronic device, and certificate system
CN109947449A (en) Method for upgrading system, device, storage medium and electronic equipment
CN103544013A (en) Plug-in system and plug-in management method
CN112468497B (en) Block chain terminal equipment authorization authentication method, device, equipment and storage medium
CN112513850A (en) Electronic control unit and data access method and device thereof
CN111177703B (en) Method and device for determining data integrity of operating system
CN110189434B (en) Vehicle safety checking method and related equipment thereof
CN114124401B (en) Data authentication method, device, equipment and storage medium
CN115130114B (en) Gateway secure starting method and device, electronic equipment and storage medium
CN107995214B (en) Website login method and related equipment
CN109740306A (en) The method and device that application software is authorized based on hybrid plan
US11843947B2 (en) Electronic device and authentication method in electronic device
CN111107089B (en) Method and device for protecting data transmission safety of Android system
CN113806131A (en) Access control method and device for fault code library, electronic equipment and storage medium
CN109472148B (en) Method, device and storage medium for loading hot patch
CN110912704B (en) Certificate loading method and related product
CN114090115B (en) Startup verification method, device, equipment and storage medium
CN108874696A (en) Automatic test approach, device and the electronic equipment of more legal power safety storage equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20240621

Address after: 331100 No.12, Gaoxin Avenue, Fengcheng hi tech Industrial Park, Yichun City, Jiangxi Province

Patentee after: Faurecia music electronics (Fengcheng) Co.,Ltd.

Country or region after: China

Address before: 331100 No.12, Gaoxin Avenue, Fengcheng hi tech Industrial Park, Yichun City, Jiangxi Province

Patentee before: Faurecia music electronics (Fengcheng) Co.,Ltd.

Country or region before: China

Patentee before: Faurecia electronic (Foshan) Co.,Ltd.