WO2021051852A1 - 一种设备认证方法及装置 - Google Patents

一种设备认证方法及装置 Download PDF

Info

Publication number
WO2021051852A1
WO2021051852A1 PCT/CN2020/092176 CN2020092176W WO2021051852A1 WO 2021051852 A1 WO2021051852 A1 WO 2021051852A1 CN 2020092176 W CN2020092176 W CN 2020092176W WO 2021051852 A1 WO2021051852 A1 WO 2021051852A1
Authority
WO
WIPO (PCT)
Prior art keywords
certificate
information
signature
authentication
identifier
Prior art date
Application number
PCT/CN2020/092176
Other languages
English (en)
French (fr)
Inventor
彭建芬
郭志鹏
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to MX2021009397A priority Critical patent/MX2021009397A/es
Priority to KR1020217021420A priority patent/KR102476107B1/ko
Priority to EP20866025.8A priority patent/EP3923613A4/en
Priority to JP2021542509A priority patent/JP2022531815A/ja
Publication of WO2021051852A1 publication Critical patent/WO2021051852A1/zh
Priority to US17/368,382 priority patent/US11392685B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/069—Authentication using certificates or pre-shared keys
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • G06F21/445—Program or device authentication by mutual authentication, e.g. between devices or programs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0869—Network architectures or network communication protocols for network security for authentication of entities for achieving mutual authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/009—Security arrangements; Authentication; Protecting privacy or anonymity specially adapted for networks, e.g. wireless sensor networks, ad-hoc networks, RFID networks or cloud networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/48—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for in-vehicle communication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2129—Authenticate client device independently of the user

Definitions

  • This application relates to the field of communication technology, and in particular to a device authentication method and device.
  • vehicle-mounted equipment can be certified.
  • in-vehicle equipment is divided into multiple levels, and a hierarchical authentication mechanism is implemented.
  • the first-level in-vehicle equipment can authenticate the second-level in-vehicle equipment. If the second-level in-vehicle equipment is certified, the second-level in-vehicle equipment The third-level in-vehicle equipment can be certified.
  • Such authentication measures will rely more on intermediate nodes.
  • the second-level in-vehicle equipment can be regarded as an intermediate node.
  • the second-level in-vehicle equipment fails to be authenticated, the second-level in-vehicle equipment will not be able to communicate with the third-level in-vehicle equipment. Certification has resulted in a large number of in-vehicle devices not being certified.
  • the embodiments of the present application provide a device authentication method and device, which are used to increase the probability that vehicle-mounted equipment can be authenticated and reduce potential safety hazards.
  • a first device authentication method includes: a first device sends first information and a first certificate to a second device, where the first information is used to instruct the second device, and the first device A certificate is the device certificate of the first device; the first device receives the first random number from the second device; the first device uses the first private key, according to the first random number and the first An identifier to obtain a first signature, where the first identifier is the identifier of the first device; the first device sends the first signature to the second device, and the first signature is used to One device is certified.
  • the method of the first aspect may be executed by a first communication device, and the first communication device may be a communication device or a device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an in-vehicle device. In the following description, it is taken as an example that the first communication device is the first device.
  • the first information is used to indicate the second device.
  • the first information may be the identifier of the first service, or the address of the second device, etc., as long as the first device sends the first information to the second device.
  • the second device can authenticate the first device without relying on the hierarchical relationship between the devices. For example, even if the first device is a first-tier device, the second device is a third-tier device, and the first device Authentication can also be carried out with the second device, thus realizing the distributed authentication process.
  • the authentication method in the embodiment of the present application does not require an intermediate node to authenticate multiple nodes, which reduces the burden on the device.
  • end-to-end authentication between devices is realized, the dependence on intermediate nodes is reduced, more vehicle-mounted devices can be authenticated, and the safety of vehicle-mounted devices is improved.
  • the authentication scheme provided by the embodiment of the application has a certain degree of resilience.
  • the end-to-end authentication scheme provided by the embodiment of the present application has nothing to do with the architecture of the entire vehicle, has good compatibility, and can be applied to the current automobile architecture as well as the future automobile architecture.
  • the first information includes an identifier of the first service.
  • the first information may include the identification of the first service, and the identification of the first service may indicate the target device for authentication.
  • the certified target device such as the second device. Therefore, the first information can indicate the second device.
  • the authentication process can be related to the first service. Therefore, when the business is different, the corresponding second device can be different, so that the authentication process can be combined with the business and serve the business, so that the security of the business is higher.
  • the second device first needs to authenticate the first device.
  • the first information may include the service identifier.
  • the first device and the second device can be authenticated before the automatic driving function is performed.
  • the first information sent by the first device to the second device may include the identification of the service of the autopilot function, so that the second device can make it clear that the current authentication corresponds to the autopilot service.
  • the first information may be the identifier of the first service, or, in addition to the identifier of the first service, the first information may also include other information.
  • the first information may also include other content.
  • the first information may include information about the second device, and the information about the second device may include, for example, the identification of the second device (for example, the ID of the second device), or may include the first information.
  • the IP address of the second device may include the IP address of the second device and the identification of the second device, or the information of the second device may also include other information of the second device. Therefore, the first information can indicate the second device. For example, when the first device and the second device perform authentication, both the first device and the second device have made it clear that the authentication corresponds to a certain service. Then, in this case, the first device sends the data to the second device.
  • the first information may not include the identification of the first service.
  • the first information sent by the first device may include the information of the second device, for example, the ID of the second device, or the second device.
  • the IP address of the device, etc. so that the second device can clarify that the information from the first device corresponds to the second device, so that the authentication process can proceed.
  • the first information may also include other information, and there is no restriction on the information specifically included in the first information.
  • the method further includes: the first device generates a second random number; and the first device sends the second random number to the Mentioned second device.
  • the first device in addition to the second device that can authenticate the first device, can also authenticate the second device to further improve the security of the communication process.
  • the first device can generate a second random number.
  • the second device can obtain a signature based on the second random number, so that the first device can authenticate the second device based on the second random number and the signature. .
  • Using random numbers for authentication improves the recognition success rate in the case where the legal device is replaced by an illegal device, and improves the reliability of the vehicle system.
  • the method further includes: the first device receives a second signature and a second identifier from the second device, the second identifier Is the identity of the second device; the first device authenticates the second device according to the second signature, the second random number, and the second identity.
  • the second device can obtain the signature according to the second random number, so that the first device can authenticate the second device according to the second random number and the signature.
  • Using random numbers for authentication improves the recognition success rate in the case where the legal device is replaced by an illegal device, and improves the reliability of the vehicle system.
  • the authentication between the first device and the second device may adopt an asymmetric authentication method. Compared with the symmetric authentication method, the asymmetric authentication method can further improve the reliability of authentication.
  • the first device authenticates the second device according to the second signature, the second random number, and the second identifier ,include:
  • the first device uses the second public key to verify the second signature, the second random number, and the second identifier, and obtain a returned result, when the returned result indicates that the verification passed , It is determined that the authentication of the second device is successful, otherwise, when the returned result indicates that the signature verification is not passed, it is determined that the authentication of the second device has failed.
  • the first device may use the second public key to authenticate the second device according to the second random number, the second signature, and the second identification.
  • the second public key and the second private key used to obtain the second signature are the same Pair asymmetric keys.
  • the first device can use the second public key to verify the second signature, the second random number, and the second identification, and start the verification based on the returned result. If the verification is passed, it indicates that the second device The authentication is successful; otherwise, it indicates that the authentication of the second device has failed.
  • the way of verification is, for example, that the first device uses a hash algorithm to obtain a hash value based on the second random number and the second identifier, for example, the third hash value.
  • the first device uses the second public key and the third hash value.
  • the value and the second signature are input into the signature verification function (for example, called the second function) to verify the signature, and determine whether the verification is passed according to the returned result.
  • the first certificate does not include subject attribute information.
  • the first certificate may not include subject attribute information, and the subject attribute information may be the subject attribute information of the first certificate, or the subject attribute information may also be referred to as application scenario information.
  • the device certificate can only be used for authentication between devices and not used for authentication in other scenarios. This reflects the specific nature of the device certificate and helps ensure the security of the system. Moreover, the size of the device certificate can also be reduced through the solution provided by the embodiment of this application.
  • the first certificate may not include the subject attribute information of the first certificate, and is related to the authentication of the first certificate. For example, when the first device and the second device are authenticated for the first service, the The first certificate may not include the subject attribute information of the first certificate.
  • the first certificate does not include the subject attribute information of the first certificate, and it may have nothing to do with whether the authentication process is business-related. For example, authentication is performed between the first device and the second device, but the authentication has nothing to do with the business, and the first certificate used may not include the subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information: version information of the first certificate, Signer information of a certificate, subject information of the first certificate, validity information of the first certificate, or signature information of the first certificate.
  • the first certificate includes the version information of the first certificate; or, the first certificate includes the signer information of the first certificate and the subject information of the first certificate; or, the first certificate includes the subject information of the first certificate, and the first certificate
  • the first certificate includes the version information of the first certificate, the signer information of the first certificate, the subject information of the first certificate, the validity information of the first certificate, and The signature information of the first certificate, and so on.
  • the method further includes: the first device receives instruction information from the second device, where the instruction information is used to instruct the The authentication of the first device fails, or it is used to instruct the first device to stop working or to stop using part of the functions of the first device; the first device to stop working or to stop using part of the functions of the first device.
  • the second device may determine the first execution strategy.
  • the first execution strategy includes, for example, the device stops working or the device stops using part of the functions of the device.
  • the first execution strategy is, for example, determined by the second device according to the first service, so that the execution strategy of the device is more in line with service requirements.
  • the first execution strategy may be executed by the second device or executed by the first device. If the first execution strategy should be executed by the first device, the second device may send instruction information to the first device, and the first device receives the instruction information from the second device, and the instruction information is used to indicate the first execution strategy.
  • the first execution strategy may be executed by the first device, and the second device may send instruction information to the first device; or If the device is a device other than a gateway and a router, or is an entity other than an entity with routing and forwarding functions, the first execution strategy may be executed by the second device, and the second device may not send the message to the first device. Send the instruction information, but execute the first execution strategy by yourself.
  • a second device authentication method includes: a second device receives first information and a first certificate from a first device, where the first information is used to instruct the second device, the first A certificate is the device certificate of the first device; the second device verifies whether the first certificate is correct according to the root certificate or the secondary certificate of the first device; when the first certificate is correct, all The second device generates a first random number; the second device sends the first random number to the first device; the second device receives the first signature from the first device; the first device The second device authenticates the first device according to the first signature, the first random number, and the first identifier, where the first identifier is the identifier of the first device.
  • the method of the second aspect may be executed by a second communication device, and the second communication device may be a communication device or a device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an in-vehicle device. In the following description, it is taken as an example that the second communication device is the second device.
  • the first information is used to indicate the second device.
  • the first information may be the identifier of the first service, or the address of the second device, etc., as long as the first device sends the first information to the second device.
  • the second device can authenticate the first device without relying on the hierarchical relationship between the devices. For example, even if the first device is a first-tier device, the second device is a third-tier device, and the first device Authentication can also be carried out with the second device, thus realizing the distributed authentication process.
  • the authentication method in the embodiment of the present application does not require an intermediate node to authenticate multiple nodes, which reduces the burden on the device.
  • end-to-end authentication between devices is realized, the dependence on intermediate nodes is reduced, more vehicle-mounted devices can be authenticated, and the safety of vehicle-mounted devices is improved.
  • the authentication scheme provided by the embodiment of the application has a certain degree of resilience.
  • the end-to-end authentication scheme provided by the embodiment of the present application has nothing to do with the architecture of the entire vehicle, has good compatibility, and can be applied to the current automobile architecture as well as the future automobile architecture.
  • the first information includes an identifier of the first service.
  • the first information may include the identification of the first service, that is, the authentication process may be related to the first service. Therefore, when the business is different, the corresponding second device can be different, so that the authentication process can be combined with the business and serve the business, so that the security of the business is higher.
  • the first information may also include other content.
  • the first information may include information about the second device, and the information about the second device may include, for example, the identification of the second device (for example, the ID of the second device), or include the second device. The IP address of the device, etc.
  • the first information may also include other information.
  • the second device authenticates the first device according to the first signature, the first random number, and the first identifier, include:
  • the second device uses the first public key to verify the first signature, the first random number, and the first identifier, and obtain a returned result, when the returned result indicates that the verification passed , It is determined that the authentication of the first device is successful, otherwise, when the returned result indicates that the signature verification is not passed, it is determined that the authentication of the first device has failed.
  • the second device may use the first public key to authenticate the first device according to the first random number, the first signature, and the first identification.
  • the first public key and the first private key used to obtain the first signature are the same. Pair asymmetric keys.
  • the second device can use the first public key to verify the first signature, the first random number, and the first identification, and start the verification based on the returned result. If the verification is passed, it indicates that the first device The authentication is successful; otherwise, it indicates that the authentication of the first device has failed.
  • the verification method is, for example, that the second device uses a hash algorithm to obtain a hash value based on the first random number and the first identifier, for example, the fourth hash value.
  • the second device combines the first public key and the fourth hash value.
  • the value and the first signature are input into the signature verification function (for example, called the first function) for verification, and the verification is determined according to the returned result.
  • the method further includes: the second device receives a second random number from the first device; when authenticating the first device When passing, the second device uses the second private key to generate a second signature based on the second random number and the second identification; the second device sends the second signature and the second identification to all In the first device, the second signature is used to authenticate the second device, and the second identifier is the identifier of the second device.
  • the second device can obtain the signature according to the second random number, so that the first device can authenticate the second device according to the second random number and the signature.
  • Using random numbers for authentication improves the recognition success rate in the case where the legal device is replaced by an illegal device, and improves the reliability of the vehicle system.
  • the authentication between the first device and the second device may adopt an asymmetric authentication method. Compared with the symmetric authentication method, the asymmetric authentication method can further improve the reliability of authentication.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate may not include the subject attribute information of the first certificate, or the subject attribute information may also be referred to as application scenario information.
  • the device certificate can only be used for authentication between devices and not used for authentication in other scenarios. This reflects the specific nature of the device certificate and helps ensure the security of the system. Moreover, the size of the device certificate can also be reduced through the solution provided by the embodiment of this application.
  • the first certificate includes one of the following information or any combination of the following multiple types of information: version information of the first certificate, Signer information of a certificate, subject information of the first certificate, validity information of the first certificate, or signature information of the first certificate.
  • the first certificate includes the version information of the first certificate; or, the first certificate includes the signer information of the first certificate and the subject information of the first certificate; or, the first certificate includes the subject information of the first certificate, and the first certificate
  • the first certificate includes the version information of the first certificate, the signer information of the first certificate, the subject information of the first certificate, the validity information of the first certificate, and The signature information of the first certificate, and so on.
  • the method further includes:
  • the second device sends instruction information to the first device, where the instruction information is used to indicate that the authentication of the first device fails, or is used to indicate the first device A device stops working or stops using part of the functions of the first device; or,
  • the second device stops working or the second device stops using part of the functions of the second device.
  • the second device may determine the first execution strategy.
  • the first execution strategy includes, for example, the device stops working or the device stops using part of the functions of the device.
  • the first execution strategy is, for example, determined by the second device according to the first service, so that the execution strategy of the device is more in line with service requirements.
  • the first execution strategy may be executed by the second device or executed by the first device. If the first execution strategy should be executed by the first device, the second device may send instruction information to the first device, and the first device receives the instruction information from the second device, and the instruction information is used to indicate the first execution strategy.
  • the first execution strategy may be executed by the first device, and the second device may send instruction information to the first device; or If the device is a device other than a gateway and a router, or is an entity other than an entity with routing and forwarding functions, the first execution strategy may be executed by the second device, and the second device may not send the message to the first device. Send the instruction information, but execute the first execution strategy by yourself.
  • a third device authentication method includes: a third device receives first information and a first certificate from a first device, the first information is used to indicate the second device, and the first certificate Is the device certificate of the first device; finds the corresponding second device according to the first information; sends the first information and the first certificate to the second device, the first The certificate is used by the second device to authenticate the first device.
  • the method of the third aspect may be executed by a third communication device, and the third communication device may be a communication device or a device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an in-vehicle device.
  • the vehicle-mounted device is a device such as a gateway or a router, or may also be another device with a routing and forwarding function.
  • the third communication device is the third device.
  • the third device may only perform a forwarding function, that is, the third device does not perform any processing on the information (for example, the first information and the first certificate, etc.) from the first device, but directly forwards it to the second device.
  • the third device may perform a query based on the first information to find the corresponding second device.
  • the first information is the ID of the first service
  • the first device only sends the ID of the first service and the first certificate to the third device.
  • the third device stores the correspondence between the ID of the service and the device.
  • the correspondence may be the correspondence between the ID of the service and the address of the device, and the address of the device is, for example, the IP address of the device.
  • the corresponding relationship is used to indicate which devices the corresponding service should be executed by, or used to indicate which devices need to be authenticated to perform the corresponding service, or in other words, indicate the devices associated with the service.
  • the third device queries the correspondence relationship and determines the device corresponding to the ID of the first service, for example, including the second device, then the third device can forward the first certificate and the first information to the second device.
  • the ID of one service may correspond to one or more devices.
  • the ID of the first service may only correspond to the second device, or it may correspond to multiple devices. Including the second device.
  • the third device may only forward the first information and the first certificate to the part of the device corresponding to the ID of the first service, for example, only the second device, or the third device may also forward the first information and the first service ID.
  • a certificate etc. are forwarded to all the devices corresponding to the ID of the first service.
  • the third device is responsible for forwarding, and the first device does not need to know too much information of the target device, which reduces the burden of the first device, and the third device realizes unified forwarding, which can make the forwarding of information more consistent with unified rules.
  • the corresponding relationship can also be stored in the first device.
  • the first device can query and determine the corresponding device according to the ID of the service.
  • the third device can only be used as a forwarding device and does not need to be based on the first device.
  • the information determines the second device, or in this case, the third device can also play a filtering role as described below.
  • the third device may play a role of filtering. For example, according to the first information, the third device determines whether the second device corresponding to the first information complies with preset rules. If the second device complies with the preset rules, the third device may combine the first information with the first information. The certificate is forwarded to the second device. Otherwise, the third device does not forward the first information and the first certificate to the second device. For example, the third device may discard the first information and the first certificate, and the process ends. In this way, the possibility of mis-sending information by the first device is reduced, and the security of communication is improved.
  • the third device can have multiple functions.
  • the third aspect above is just taking the query function of the third device as an example.
  • the first information includes an identifier of the first service.
  • the first information may include the identification of the first service, that is, the authentication process may be related to the first service. Therefore, when the business is different, the corresponding second device can be different, so that the authentication process can be combined with the business and serve the business, so that the security of the business is higher.
  • the first information may also include other content.
  • the first information may include information about the second device, and the information about the second device may include, for example, the identification of the second device (for example, the ID of the second device), or include the second device. The IP address of the device, etc.
  • the first information may also include other information.
  • the first information is an identifier of a first service
  • searching for the corresponding second device according to the first information includes: The identifier of the first service is used to search for the second device related to the first service.
  • the identifier of the first service is the ID of the first service
  • the first device only sends the ID of the first service and the first certificate to the third device.
  • the third device stores the correspondence between the ID of the service and the device.
  • the correspondence may be the correspondence between the ID of the service and the address of the device, and the address of the device is, for example, the IP address of the device.
  • the corresponding relationship is used to indicate which devices the corresponding service should be executed by, or used to indicate which devices need to be authenticated to perform the corresponding service, or in other words, indicate the devices associated with the service.
  • the third device queries the correspondence relationship and determines the device corresponding to the ID of the first service, for example, including the second device, then the third device can forward the first certificate and the first information to the second device.
  • the ID of one service may correspond to one or more devices.
  • the ID of the first service may only correspond to the second device, or it may correspond to multiple devices. Including the second device.
  • the third device may only forward the first information and the first certificate to the part of the device corresponding to the ID of the first service, for example, only the second device, or the third device may also forward the first information and the first service ID.
  • a certificate etc. are forwarded to all the devices corresponding to the ID of the first service.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate may not include the subject attribute information of the first certificate, or the subject attribute information may also be referred to as application scenario information.
  • the device certificate can only be used for authentication between devices and not used for authentication in other scenarios. This reflects the specific nature of the device certificate and helps ensure the security of the system. Moreover, the size of the device certificate can also be reduced through the solution provided by the embodiment of this application.
  • the first certificate includes one of the following information or any combination of the following multiple types of information: version information of the first certificate, Signer information of a certificate, subject information of the first certificate, validity information of the first certificate, or signature information of the first certificate.
  • the first certificate includes the version information of the first certificate; or, the first certificate includes the signer information of the first certificate and the subject information of the first certificate; or, the first certificate includes the subject information of the first certificate, and the first certificate
  • the first certificate includes the version information of the first certificate, the signer information of the first certificate, the subject information of the first certificate, the validity information of the first certificate, and The signature information of the first certificate, and so on.
  • a fourth device authentication method includes: a second device fails to authenticate a first device; the second device determines a first execution strategy according to the first service, and the authentication corresponds to the first device. A service; the second device sends the first execution strategy to the first device, or the second device executes the first execution strategy.
  • the method of the fourth aspect may be executed by a fourth communication device, and the fourth communication device may be a communication device or a device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an in-vehicle device.
  • the third communication device is the third device.
  • the second device if the second device fails to authenticate the first device, because the authentication is an authentication process related to the first service, when the second device determines the execution strategy, the determined execution strategy may be the same as that of the first device.
  • a business-related execution strategy in other words, an execution strategy can be determined according to the first business, so that the determined execution strategy is more in line with the needs of the business.
  • the first execution strategy includes that the device stops working, or the device stops using part of the functions of the device.
  • the first execution strategy includes, for example, the device stops working, or the device stops using part of the functions of the device.
  • the first execution strategy may include that the second device stops working, or the second device stops using part of the functions of the second device.
  • Some of the functions here may be functions related to the first business.
  • the second device is an MDC and the first service is an automatic driving function, so the MDC stops using part of the MDC functions, for example, stops using the functions related to the automatic driving function.
  • the method further includes:
  • the second device verifies whether the first certificate is correct according to the third certificate of the first device
  • the second device When the first certificate is correct, the second device generates a first random number
  • the second device receives the first signature from the first device
  • the second device authenticates the first device according to the first signature, the first random number, and a first identifier, where the first identifier is the identifier of the first device.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate may not include the subject attribute information of the first certificate, or the subject attribute information may also be referred to as application scenario information.
  • the device certificate can only be used for authentication between devices and not used for authentication in other scenarios. This reflects the specific nature of the device certificate and helps ensure the security of the system. Moreover, the size of the device certificate can also be reduced through the solution provided by the embodiment of this application.
  • the first certificate includes one of the following information or any combination of the following multiple types of information: version information of the first certificate, Signer information of a certificate, subject information of the first certificate, validity information of the first certificate, or signature information of the first certificate.
  • the first certificate includes the version information of the first certificate; or, the first certificate includes the signer information of the first certificate and the subject information of the first certificate; or, the first certificate includes the subject information of the first certificate, and the first certificate
  • the first certificate includes the version information of the first certificate, the signer information of the first certificate, the subject information of the first certificate, the validity information of the first certificate, and The signature information of the first certificate, and so on.
  • a communication device is provided, for example, the communication device is the first communication device as described above.
  • the first communication device is configured to execute the foregoing first aspect or the method in any possible implementation manner of the first aspect.
  • the first communication device may include a module for executing the method in the first aspect or any possible implementation of the first aspect, for example, including a processing module and a transceiver module.
  • the transceiver module may refer to a functional module, which can complete the function of receiving information as well as the function of sending information.
  • the transceiver module may be a collective term for the sending module and the receiving module.
  • the sending module is used to complete the function of sending information
  • the receiving module is used to complete the function of receiving information.
  • the first communication device is a vehicle-mounted device. among them,
  • the transceiver module is configured to send first information and a first certificate to a second device, the first information is used to indicate the second device, and the first certificate is the device certificate of the first communication device ;
  • the transceiver module is further configured to receive the first random number from the second device;
  • the processing module is configured to use a first private key to obtain a first signature according to the first random number and a first identifier, where the first identifier is the identifier of the first communication device;
  • the transceiver module is further configured to send the first signature to a second device, and the first signature is used to authenticate the first communication device.
  • the first information includes an identifier of the first service.
  • the processing module is also used to generate a second random number
  • the transceiver module is further configured to send the second random number to the second device.
  • the transceiver module is further configured to receive a second signature and a second identifier from the second device, where the second identifier is the identifier of the second device;
  • the processing module is further configured to authenticate the second device according to the second signature, the second random number, and the second identifier.
  • the processing module is configured to compare the second signature, the second random number, and the second identifier in the following manner.
  • the second public key to verify the second signature, the second random number, and the second identifier, and obtain the returned result.
  • the returned result indicates that the verification is passed, it is determined to The authentication of the second device is successful; otherwise, when the returned result indicates that the signature verification fails, it is determined that the authentication of the second device has failed.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • the transceiver module is also used to receive instruction information from the second device, where the instruction information is used to indicate that the authentication of the first communication device fails, or is used to instruct the first communication device to stop working or Stop using part of the functions of the first communication device;
  • the processing module is also used to stop the first communication device from working, or stop using part of the functions of the first communication device.
  • a communication device is provided, for example, the communication device is the second communication device as described above.
  • the second communication device is configured to execute the foregoing second aspect or the method in any possible implementation manner of the second aspect.
  • the second communication device may include a module for executing the method in the second aspect or any possible implementation of the second aspect, for example, including a processing module and a transceiver module.
  • the transceiver module may refer to a functional module, which can complete the function of receiving information as well as the function of sending information.
  • the transceiver module may be a collective term for the sending module and the receiving module.
  • the sending module is used to complete the function of sending information
  • the receiving module is used to complete the function of receiving information.
  • the second communication device is a vehicle-mounted device. among them,
  • the transceiver module is configured to receive first information and a first certificate from a first device, the first information is used to indicate the second communication device, and the first certificate is the device certificate of the first device ;
  • the processing module is configured to verify whether the first certificate is correct according to the root certificate or the secondary certificate of the first device;
  • the processing module is further configured to generate a first random number when the first certificate is correct;
  • the transceiver module is further configured to send the first random number to the first device
  • the transceiver module is further configured to receive the first signature from the first device;
  • the processing module is further configured to authenticate the first device according to the first signature, the first random number, and a first identifier, where the first identifier is an identifier of the first device.
  • the first information includes an identifier of the first service.
  • the processing module is configured to perform processing on the first signature according to the first signature, the first random number, and the first identifier in the following manner.
  • Equipment for certification :
  • the first public key to verify the first signature, the first random number, and the first identifier, and obtain the returned result.
  • the returned result indicates that the verification is passed, it is determined that the The authentication of the first device is successful; otherwise, when the returned result indicates that the signature verification fails, it is determined that the authentication of the first device has failed.
  • the transceiver module is further configured to receive a second random number from the first device
  • the processing module is further configured to use a second private key to generate a second signature according to the second random number and the second identifier when the first device is authenticated;
  • the transceiver module is further configured to send the second signature and a second identifier to the first device, the second signature is used to authenticate the second communication device, and the second identifier is The identification of the second communication device.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • the transceiver module is further configured to send instruction information to the first device when the processing module fails to authenticate the first device, where the instruction information is used to indicate that the authentication to the first device fails, or , Used to instruct the first device to stop working or to stop using part of the functions of the first device; or,
  • the processing module is further configured to stop the operation of the second communication device or stop using part of the functions of the second communication device when the authentication of the first device fails.
  • a communication device is provided, for example, the communication device is the aforementioned third communication device.
  • the third communication device is configured to execute the foregoing third aspect or the method in any possible implementation manner of the third aspect.
  • the third communication device may include a module for executing the third aspect or the method in any possible implementation manner of the third aspect, for example, including a processing module and a transceiver module.
  • the transceiver module may refer to a functional module, which can complete the function of receiving information as well as the function of sending information.
  • the transceiver module may be a collective term for the sending module and the receiving module.
  • the sending module is used to complete the function of sending information
  • the receiving module is used to complete the function of receiving information.
  • the third communication device is a vehicle-mounted device. among them,
  • the transceiver module is configured to receive first information and a first certificate from a first device, the first information is used to indicate a second device, and the first certificate is a device certificate of the first device;
  • the processing module is configured to search for the corresponding second device according to the first information
  • the transceiver module is further configured to send the first information and the first certificate to the second device, and the first certificate is used by the second device to authenticate the first device.
  • the first information includes an identifier of the first service.
  • the first information is an identifier of the first service
  • the processing module is configured to search for the corresponding all information based on the first information in the following manner.
  • search for the second device related to the first service According to the identifier of the first service, search for the second device related to the first service.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • a communication device is provided, for example, the communication device is the fourth communication device as described above.
  • the fourth communication device is configured to execute the foregoing fourth aspect or the method in any possible implementation manner of the fourth aspect.
  • the fourth communication device may include a module for executing the fourth aspect or the method in any possible implementation manner of the fourth aspect, for example, including a processing module and a transceiver module.
  • the transceiver module may refer to a functional module, which can complete the function of receiving information as well as the function of sending information.
  • the transceiver module may be a collective term for the sending module and the receiving module.
  • the sending module is used to complete the function of sending information
  • the receiving module is used to complete the function of receiving information.
  • the fourth communication device is a vehicle-mounted device. among them,
  • the processing module is configured to fail authentication of the first device
  • the processing module is further configured to determine a first execution strategy according to the first service, and the authentication corresponds to the first service;
  • the transceiver module is configured to send the first execution strategy to the first device, or the processing module is further configured to execute the first execution strategy.
  • the first execution strategy includes that the device stops working, or the device stops using part of the functions of the device.
  • the transceiver module is further configured to receive first information and a first certificate from the first device, the first information is used to indicate the second device, and the first certificate is the first device's Equipment certificate
  • the processing module is further configured to verify whether the first certificate is correct according to the third certificate of the first device;
  • the processing module is further configured to generate a first random number when the first certificate is correct;
  • the transceiver module is further configured to send the first random number to the first device
  • the transceiver module is further configured to receive the first signature from the first device;
  • the processing module is further configured to authenticate the first device according to the first signature, the first random number, and a first identifier, where the first identifier is an identifier of the first device.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • a communication device is provided.
  • the communication device is, for example, the first communication device as described above.
  • the first communication device includes a processor and a transceiver, and the processor and the transceiver are used to implement the foregoing first aspect or the methods described in various possible designs of the first aspect.
  • the first communication device is a chip provided in a communication device.
  • the transceiver is realized by, for example, an antenna, a feeder, a codec in the communication device, or, if the first communication device is a chip set in the communication device, the transceiver is, for example, a communication interface in the chip.
  • the communication interface is connected with the radio frequency transceiving component in the communication device, so as to realize the sending and receiving of information through the radio frequency transceiving component.
  • the transceiver may refer to a functional module, which can complete the function of receiving information as well as the function of sending information.
  • the transceiver may be a collective term for a transmitter and a receiver. The transmitter is used to complete the function of sending information, and the receiver is used to complete the function of receiving information.
  • the communication device is a vehicle-mounted device. among them,
  • the transceiver is configured to send first information and a first certificate to a second device, the first information is used to indicate the second device, and the first certificate is the device certificate of the first communication device ;
  • the transceiver is further configured to receive the first random number from the second device;
  • the processor is configured to use a first private key to obtain a first signature according to the first random number and a first identifier, where the first identifier is the identifier of the first communication device;
  • the transceiver is further configured to send the first signature to a second device, and the first signature is used to authenticate the first communication device.
  • the first information includes an identifier of the first service.
  • the processor is further configured to generate a second random number
  • the transceiver is also configured to send the second random number to the second device.
  • the transceiver is further configured to receive a second signature and a second identifier from the second device, where the second identifier is the identifier of the second device;
  • the processor is further configured to authenticate the second device according to the second signature, the second random number, and the second identifier.
  • the processor is configured to compare the second signature, the second random number, and the second identifier to the second signature in the following manner.
  • Equipment for certification :
  • the second public key to verify the second signature, the second random number, and the second identifier, and obtain the returned result.
  • the returned result indicates that the verification is passed, it is determined to The authentication of the second device is successful; otherwise, when the returned result indicates that the signature verification fails, it is determined that the authentication of the second device has failed.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • the transceiver is also used to receive instruction information from the second device, where the instruction information is used to indicate that the authentication of the first communication device fails, or is used to instruct the first communication device to stop working or Stop using part of the functions of the first communication device;
  • the processor is further configured to stop the first communication device from working or stop using part of the functions of the first communication device.
  • a communication device is provided.
  • the communication device is, for example, the second communication device as described above.
  • the second communication device includes a processor and a transceiver, and the processor and the transceiver are used to implement the foregoing second aspect or the methods described in various possible designs of the second aspect.
  • the second communication device is a chip provided in a communication device.
  • the transceiver is realized by, for example, an antenna, a feeder, a codec in the communication device, etc., or if the second communication device is a chip set in the communication device, the transceiver is, for example, a communication interface in the chip.
  • the communication interface is connected with the radio frequency transceiving component in the communication device, so as to realize the sending and receiving of information through the radio frequency transceiving component.
  • the transceiver may refer to a functional module, which can complete the function of receiving information as well as the function of sending information.
  • the transceiver may be a collective term for a transmitter and a receiver. The transmitter is used to complete the function of sending information, and the receiver is used to complete the function of receiving information.
  • the communication device is a vehicle-mounted device. among them,
  • the transceiver is configured to receive first information and a first certificate from a first device, the first information is used to indicate the second communication device, and the first certificate is the device certificate of the first device ;
  • the processor is configured to verify whether the first certificate is correct according to the root certificate or the secondary certificate of the first device;
  • the processor is further configured to generate a first random number when the first certificate is correct;
  • the transceiver is further configured to send the first random number to the first device
  • the transceiver is further configured to receive the first signature from the first device
  • the processor is further configured to authenticate the first device according to the first signature, the first random number, and a first identifier, where the first identifier is an identifier of the first device.
  • the first information includes an identifier of the first service.
  • the processor is configured to: To authenticate:
  • the first public key to verify the first signature, the first random number, and the first identifier, and obtain the returned result.
  • the returned result indicates that the verification is passed, it is determined that the The authentication of the first device is successful; otherwise, when the returned result indicates that the signature verification fails, it is determined that the authentication of the first device has failed.
  • the transceiver is further configured to receive a second random number from the first device
  • the processor is further configured to use a second private key to generate a second signature according to the second random number and the second identifier when the first device is authenticated;
  • the transceiver is further configured to send the second signature and a second identifier to the first device, the second signature is used to authenticate the second communication device, and the second identifier is The identification of the second communication device.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • the transceiver is further configured to send instruction information to the first device when the processor fails to authenticate the first device, where the instruction information is used to indicate that the authentication to the first device fails, or , Used to instruct the first device to stop working or to stop using part of the functions of the first device; or,
  • the processor is further configured to stop the second communication device or stop using part of the functions of the second communication device when the authentication of the first device fails.
  • a communication device is provided.
  • the communication device is, for example, the third communication device as described above.
  • the third communication device includes a processor and a transceiver, and the processor and the transceiver are used to implement the methods described in the foregoing third aspect or various possible designs of the third aspect.
  • the third communication device is a chip provided in a communication device.
  • the transceiver is realized by, for example, an antenna, a feeder, a codec in the communication device, etc., or, if the third communication device is a chip set in the communication device, the transceiver is, for example, a communication interface in the chip.
  • the communication interface is connected with the radio frequency transceiving component in the communication device, so as to realize the sending and receiving of information through the radio frequency transceiving component.
  • the transceiver may refer to a functional module, which can complete the function of receiving information as well as the function of sending information.
  • the transceiver may be a collective term for a transmitter and a receiver. The transmitter is used to complete the function of sending information, and the receiver is used to complete the function of receiving information.
  • the communication device is a vehicle-mounted device. among them,
  • the transceiver is configured to receive first information and a first certificate from a first device, the first information is used to indicate a second device, and the first certificate is a device certificate of the first device;
  • the processor is configured to search for the corresponding second device according to the first information
  • the transceiver is further configured to send the first information and the first certificate to the second device, and the first certificate is used by the second device to authenticate the first device.
  • the first information includes an identifier of the first service.
  • the first information is an identifier of a first service
  • the processor is configured to find the corresponding The second device:
  • search for the second device related to the first service According to the identifier of the first service, search for the second device related to the first service.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • a communication device is provided.
  • the communication device is, for example, the fourth communication device as described above.
  • the fourth communication device includes a processor and a transceiver, and the processor and the transceiver are used to implement the methods described in the foregoing fourth aspect or various possible designs of the fourth aspect.
  • the fourth communication device is a chip provided in a communication device.
  • the transceiver is realized by, for example, an antenna, a feeder, a codec in the communication device, etc., or, if the fourth communication device is a chip set in the communication device, the transceiver is, for example, a communication interface in the chip.
  • the communication interface is connected with the radio frequency transceiving component in the communication device, so as to realize the sending and receiving of information through the radio frequency transceiving component.
  • the transceiver may refer to a functional module, which can complete the function of receiving information as well as the function of sending information.
  • the transceiver may be a collective term for a transmitter and a receiver. The transmitter is used to complete the function of sending information, and the receiver is used to complete the function of receiving information.
  • the communication device is a vehicle-mounted device. among them,
  • the processor is configured to fail authentication of the first device
  • the processor is further configured to determine a first execution strategy according to the first service, and the authentication corresponds to the first service;
  • the transceiver is configured to send the first execution strategy to the first device, or the processor is further configured to execute the first execution strategy.
  • the first execution strategy includes that the device stops working, or the device stops using part of the functions of the device.
  • the transceiver is further configured to receive first information and a first certificate from the first device, the first information is used to indicate the second device, and the first certificate is the first device's Equipment certificate
  • the processor is further configured to verify whether the first certificate is correct according to the third certificate of the first device;
  • the processor is further configured to generate a first random number when the first certificate is correct;
  • the transceiver is further configured to send the first random number to the first device
  • the transceiver is further configured to receive the first signature from the first device
  • the processor is further configured to authenticate the first device according to the first signature, the first random number, and a first identifier, where the first identifier is an identifier of the first device.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • a communication device may be the first communication device in the above method design.
  • the first communication device is a chip provided in a communication device.
  • the communication device is a vehicle-mounted device.
  • the first communication device may include: a communication interface for communicating with other devices or equipment; and a processor, where the processor is coupled with the communication interface.
  • the communication interface may be the transceiver in the communication device, for example, implemented by the antenna, feeder, and codec in the communication device, or if the communication device is a chip set in the communication device, the communication interface may be It is the input/output interface of the chip, such as input/output pins.
  • the first communication device may further include a memory for storing computer executable program code.
  • the program code stored in the memory includes instructions.
  • the processor executes the instruction, the first communication device is caused to execute the foregoing first aspect or the method in any one of the possible implementation manners of the first aspect.
  • the first communication device may not include a memory.
  • the processor may execute instructions stored in an external memory, so that the first communication device executes the first aspect or any one of the possible implementation manners of the first aspect. method.
  • a communication device may be the second communication device in the above method design.
  • the second communication device is a chip provided in a communication device.
  • the communication device is an in-vehicle device.
  • the second communication device may include: a communication interface for communicating with other devices or equipment; and a processor, where the processor is coupled with the communication interface.
  • the communication interface may be the transceiver in the communication device, for example, implemented by the antenna, feeder, and codec in the communication device, or if the communication device is a chip set in the communication device, the communication interface may be It is the input/output interface of the chip, such as input/output pins.
  • the second communication device may further include a memory for storing computer executable program code.
  • the program code stored in the memory includes instructions.
  • the processor executes the instruction, the second communication device is caused to execute the foregoing second aspect or the method in any one of the possible implementation manners of the second aspect.
  • the second communication device may not include a memory.
  • the processor may execute instructions stored in an external memory to make the second communication device execute the second aspect or any one of the possible implementation manners of the second aspect. method.
  • a communication device may be the third communication device in the above method design.
  • the third communication device is a chip provided in a communication device.
  • the communication device is an in-vehicle device.
  • the third communication device may include: a communication interface for communicating with other devices or equipment; and a processor, where the processor is coupled with the communication interface.
  • the communication interface may be the transceiver in the communication device, for example, implemented by the antenna, feeder, and codec in the communication device, or if the communication device is a chip set in the communication device, the communication interface may be It is the input/output interface of the chip, such as input/output pins.
  • the third communication device may further include a memory for storing computer executable program code.
  • the program code stored in the memory includes instructions.
  • the processor executes the instruction, the third communication device is caused to execute the foregoing third aspect or the method in any one of the possible implementation manners of the third aspect.
  • the third communication device may not include a memory.
  • the processor may execute instructions stored in an external memory to make the third communication device execute the third aspect or any one of the possible implementation manners of the third aspect. method.
  • a communication device may be the fourth communication device in the above method design.
  • the fourth communication device is a chip provided in a communication device.
  • the communication device is an in-vehicle device.
  • the fourth communication device may include: a communication interface for communicating with other devices or equipment; and a processor, where the processor is coupled with the communication interface.
  • the communication interface may be the transceiver in the communication device, for example, implemented by the antenna, feeder, and codec in the communication device, or if the communication device is a chip set in the communication device, the communication interface may be It is the input/output interface of the chip, such as input/output pins.
  • the fourth communication device may further include a memory for storing computer executable program code.
  • the program code stored in the memory includes instructions.
  • the processor executes the instruction, the fourth communication device is caused to execute the foregoing fourth aspect or the method in any one of the possible implementation manners of the fourth aspect.
  • the fourth communication device may not include a memory.
  • the processor may execute instructions stored in an external memory to make the fourth communication device execute the fourth aspect or any one of the possible implementation manners of the fourth aspect. method.
  • a communication system in a seventeenth aspect, includes the communication device described in the fifth aspect, the communication device described in the ninth aspect, or the communication device described in the thirteenth aspect, and the communication system includes the communication device described in the sixth aspect.
  • the communication system may further include the communication device described in the seventh aspect, the communication device described in the eleventh aspect, or the fifteenth aspect The communication device.
  • An eighteenth aspect provides a communication system, which includes the communication device according to the eighth aspect, the communication device according to the twelfth aspect, or the communication device according to the sixteenth aspect.
  • the communication system may further include the communication device described in the fifth aspect, the communication device described in the ninth aspect, or the communication device described in the thirteenth aspect. Mentioned communication device.
  • the communication device in a possible implementation manner of the eighteenth aspect, the communication device according to the sixth aspect, the communication device according to the tenth aspect, or the communication device according to the fourteenth aspect.
  • a computer storage medium is provided, the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, the computer executes the first aspect or the first aspect described above.
  • a computer storage medium is provided, the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, the computer executes the above-mentioned second aspect or the first aspect.
  • a computer storage medium is provided, the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, the computer executes the third aspect or the third aspect.
  • a computer storage medium is provided, the computer-readable storage medium is used to store a computer program, and when the computer program runs on a computer, the computer executes the fourth aspect or the fourth aspect.
  • a computer program product containing instructions is provided, the computer program product is used to store a computer program, and when the computer program runs on a computer, the computer executes the first aspect or the first aspect.
  • a computer program product containing instructions is provided, the computer program product is used to store a computer program, and when the computer program runs on a computer, the computer executes the second aspect or the first The method described in any one of the possible implementations of the aspect.
  • a computer program product containing instructions is provided.
  • the computer program product is used to store a computer program.
  • the computer program runs on a computer, the computer executes the third aspect or the third aspect.
  • a computer program product containing instructions is provided, the computer program product is used to store a computer program, and when the computer program runs on a computer, the computer executes the fourth aspect or the fourth aspect.
  • the authentication between devices does not depend on the hierarchical relationship between the devices. For example, even if the first device is a first-tier device, the second device is a third-tier device, and the first device and the second device Authentication can also be carried out between, thus realizing the distributed authentication process.
  • the authentication method of the embodiment of the present application does not require an intermediate node to authenticate multiple nodes, which reduces the burden on the device, reduces the dependence on the intermediate node, and improves the reliability of the system.
  • FIG. 1 is a schematic diagram of a network architecture applied in an embodiment of this application
  • Figure 2 is a flowchart of a device authentication method provided by an embodiment of the application
  • FIG. 3 is a flowchart of a device authentication method provided by an embodiment of the application.
  • FIG. 4 is a flowchart of a device authentication method provided by an embodiment of the application.
  • FIG. 5 is a flowchart of a device authentication method provided by an embodiment of the application.
  • FIG. 6 is a flowchart of a method for mutual authentication between MDC and T-Box according to an embodiment of the application
  • FIG. 7 is a flowchart of a method for a VCU to authenticate an MDC according to an embodiment of the application
  • FIG. 8 is a flowchart of a method for two-way authentication between HMI and MDC provided by an embodiment of the application
  • FIG. 9 is a flowchart of a method for MDC to authenticate a sensor according to an embodiment of the application.
  • FIG. 10 is a flowchart of a method for BCM to authenticate PEPS according to an embodiment of the application
  • FIG. 11 is a flowchart of a method for VCU to authenticate BCM according to an embodiment of the application
  • FIG. 12 is a flowchart of a method for VCU to authenticate OBC according to an embodiment of the application
  • FIG. 13 is a flowchart of a device authentication method provided by an embodiment of this application.
  • FIG. 14 is a schematic block diagram of a first device according to an embodiment of this application.
  • FIG. 15 is another schematic block diagram of a first device according to an embodiment of this application.
  • FIG. 16 is a schematic block diagram of a first type of second device according to an embodiment of this application.
  • FIG. 17 is another schematic block diagram of the first type of second device according to an embodiment of this application.
  • FIG. 18 is a schematic block diagram of a third device according to an embodiment of this application.
  • FIG. 19 is another schematic block diagram of a third device according to an embodiment of this application.
  • FIG. 20 is a schematic block diagram of a second type of second device according to an embodiment of this application.
  • FIG. 21 is another schematic block diagram of a second type of second device according to an embodiment of this application.
  • FIG. 22 is a schematic block diagram of a communication device provided by an embodiment of this application.
  • FIG. 23 is another schematic block diagram of a communication device provided by an embodiment of this application.
  • FIG. 24 is still another schematic block diagram of the communication device provided by an embodiment of the application.
  • Vehicle-mounted equipment equipment placed or installed on the vehicle can be regarded as vehicle-mounted equipment.
  • vehicle-mounted equipment For example, for vehicles that can perform autonomous driving functions, they generally rely on ADAS systems to provide information to make driving decisions.
  • ADAS includes many sensors, such as cameras, millimeter wave radar, ultrasonic radar, or LiDAR, etc., which can be considered as vehicle-mounted devices.
  • the in-vehicle network of a car may include multiple electronic control units (ECUs), and these ECUs can all be considered as on-board equipment.
  • an on-board equipment is an onboard unit (OBU), which is generally installed on a vehicle.
  • OBU onboard unit
  • ETC electronic toll collection
  • RSU roadside unit
  • OBU can communicate with RSU, for example, it can communicate through microwave.
  • the OBU and RSU can use microwave to communicate.
  • the OBU uses dedicated short-range communications (DSRC) technology to establish a microwave communication link with the RSU.
  • DSRC dedicated short-range communications
  • various terminal devices described below if they are located on a vehicle (for example, placed in a vehicle or installed in a vehicle), they can all be regarded as vehicle-mounted terminal devices, or called vehicle-mounted devices.
  • Terminal devices include devices that provide users with voice and/or data connectivity. For example, they may include handheld devices with a wireless connection function or processing devices connected to a wireless modem.
  • the terminal device can communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN.
  • RAN radio access network
  • the terminal equipment may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, device-to-device communication (device-to-device, D2D) terminal equipment, V2X terminal equipment, machine-to-machine/machine-type communication ( machine-to-machine/machine-type communications, M2M/MTC) terminal equipment, Internet of things (IoT) terminal equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station) , Remote station (remote station), access point (access point, AP), remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), or user equipment (user device) and so on.
  • IoT Internet of things
  • it may include mobile phones (or “cellular” phones), computers with mobile terminal equipment, portable, pocket-sized, hand-held, mobile devices with built-in computers, and so on.
  • PCS personal communication service
  • PCS cordless phones
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistants
  • restricted devices such as devices with low power consumption, or devices with limited storage capabilities, or devices with limited computing capabilities. Examples include barcodes, radio frequency identification (RFID), sensors, global positioning system (GPS), laser scanners and other information sensing equipment.
  • RFID radio frequency identification
  • GPS global positioning system
  • laser scanners and other information sensing equipment.
  • the in-vehicle device placed or installed on the vehicle may also include a wearable device.
  • Wearable devices can also be called wearable smart devices or smart wearable devices, etc. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes Wait.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones Use, such as all kinds of smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring.
  • At least one means one or more, and “plurality” means two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • "The following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one item (a) of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • first and second are used to distinguish multiple objects, and are not used to limit the order, timing, priority, or order of multiple objects. Importance.
  • first message and the second message are only for distinguishing different messages, but do not indicate the difference in priority, sending order, or importance of the two messages.
  • in-vehicle equipment can be certified.
  • in-vehicle equipment is divided into multiple levels and a level authentication mechanism is implemented.
  • all on-board equipment or part of the on-board equipment included in a vehicle except the gateway (gateway) can be divided into several domains, each domain includes one or more on-board equipment, and each domain has A domain manager (domain manager, DM), the domain manager can act as a domain controller.
  • Devices in the domain can communicate with the gateway through the domain controller.
  • the gateway is a first-tier device
  • the domain controller is a second-tier device
  • the domain device is a third-tier device.
  • the first-level in-vehicle devices can authenticate the second-level in-vehicle devices.
  • the second-level in-vehicle devices can authenticate the third-level in-vehicle devices.
  • the gateway may authenticate the domain controller. If the domain controller passes the authentication, the domain controller may authenticate the devices in the domain where the domain controller is located.
  • a domain controller can be regarded as an intermediate node. If the gateway fails to authenticate the domain controller, the domain controller as an insecure device cannot authenticate the devices in the domain, resulting in a large number of devices in the domain that cannot be authenticated.
  • the first information is used to indicate the second device.
  • the first information may be the identifier of the first service, or the address of the second device, etc., as long as the first device sends the first information to the second device.
  • the second device can authenticate the first device without relying on the hierarchical relationship between the devices. For example, even if the first device is a first-tier device, the second device is a third-tier device, and the first device and Authentication can also be performed between the second devices, thus realizing a distributed authentication process.
  • the authentication method in the embodiment of the present application does not require an intermediate node to authenticate multiple nodes, which reduces the burden on the device.
  • end-to-end authentication between devices is realized, the dependence on intermediate nodes is reduced, more vehicle-mounted devices can be authenticated, and the safety of vehicle-mounted devices is improved.
  • the authentication scheme provided by the embodiment of the application has a certain degree of resilience.
  • the end-to-end authentication scheme provided by the embodiment of the present application has nothing to do with the architecture of the entire vehicle, has good compatibility, and can be applied to the current automobile architecture as well as the future automobile architecture.
  • FIG. 1 is a network architecture applied in the embodiment of this application.
  • FIG. 1 shows all the on-board equipment or part of the on-board equipment included in a vehicle.
  • vehicle-mounted devices can be divided into several domains, each domain includes one or more vehicle-mounted devices, and each domain has a domain administrator, which can also be called a domain controller.
  • a mobile data center mobile data center (mobile data center, MDC), one or more sensors (sensors) and a global positioning system (global positioning system, GPS), etc. belong to a domain
  • the MDC is the domain controller of this domain.
  • a vehicle control unit (VCU), one or more electronic control units (ECU) and wireless power transmission (WPT) belong to a domain, and the VCU is the domain controller of this domain.
  • VCU vehicle control unit
  • ECU electronice control units
  • WPT wireless power transmission
  • HMI Human machine interface
  • ECUs Human machine interface
  • BCM body control module
  • PEPS passive entry passive start
  • the domain controller is connected to the gateway, and the gateway is connected to equipment such as on-board diagnostics (OBD) and telematics box (T-Box).
  • OBD on-board diagnostics
  • T-Box telematics box
  • the domain controller can communicate with T-Box and other devices through the gateway, and the devices in the domain can communicate with the gateway and other devices through the domain controller.
  • Figure 1 takes the gateway as the main authentication node as an example.
  • the main authentication node is not limited to the gateway, and can also be other vehicle-mounted devices.
  • the in-vehicle device When dividing the in-vehicle device into multiple domains, there may be various dividing factors. For example, it can be divided according to the functions completed by the on-board equipment. For example, there are several vehicle-mounted devices used to coordinate to complete a certain function (for example, power function), and these vehicle-mounted devices can be divided into one domain. Or you can divide different domains according to other factors. Regarding the domain controller, for example, a vehicle-mounted device in the domain is randomly selected as the domain controller, or a vehicle-mounted device with an overall management function in the domain can also be selected as the domain controller.
  • the embodiment of the present application provides a device authentication method. Please refer to FIG. 2, which is a flowchart of the method.
  • the application of this method to the network architecture shown in FIG. 1 is taken as an example.
  • the method can be executed by three communication devices (or, three communication devices), which are, for example, the first communication device, the second communication device, and the third communication device.
  • the first communication device, the second communication device, or the third communication device may be a vehicle-mounted device or a communication device (such as a chip system) capable of supporting the vehicle-mounted device to implement the functions required by the method, and of course, may also be other communication devices.
  • the first communication device, the second communication device, and the third communication device there are no restrictions on the implementation of the first communication device, the second communication device, and the third communication device.
  • the three communication devices can be implemented in the same form, for example, all can be implemented in the form of equipment, or the three communication devices can be implemented in the same form.
  • the device can also be implemented in different forms.
  • the first communication device is implemented in the form of equipment
  • the second communication device is implemented in the form of a chip system
  • the third communication device is implemented in the form of equipment.
  • These three communication devices can also be three types of communication devices. kind of different chips, and so on.
  • the method is executed by the first device, the second device, and the third device as an example, that is, it is assumed that the first communication device is the first device, the second communication device is the second device, and the second device is the second device.
  • the third communication device is the third device as an example.
  • the first device may be a device to be authenticated
  • the second device may be a device other than a gateway and a router, or an entity other than an entity having a routing and forwarding function.
  • the gateway may also refer to a physical device with the function of routing and forwarding equipment. Because this embodiment is applied to the network architecture shown in FIG. 1 as an example, the first device described below is, for example, the domain controller in the network architecture shown in FIG.
  • the device is, for example, the T-Box or OBD in the network architecture shown in FIG. 1, and the third device described below is, for example, the gateway in the network architecture shown in FIG. 1; or, the first device described below is, for example, It is the T-Box or OBD in the network architecture shown in FIG. 1, the second device described below is, for example, the domain controller in the network architecture shown in FIG. 1, and the third device described below is, for example, FIG.
  • the first device sends the first information and the first certificate to the second device, and the second device receives the first information and the first certificate from the first device.
  • the first information is used to indicate the second device, and the first certificate is the device certificate of the first device.
  • the first information may be used for authentication.
  • the first information may include information about the second device, the information about the second device may include, for example, the IP address of the second device, or the information about the second device may include, for example, the ID of the second device, or the information about the second device may include, for example, the first device.
  • the IP address of the second device and the ID of the second device, or the information of the second device may also include other information of the second device. Therefore, the first information can indicate the second device.
  • the first information may indicate the second device, or the first information may be associated with the second device, where the association may be an association between services, or an association contained in the first information carrier in S201 relationship.
  • the first information may also include an identifier of the service, and the identifier may indicate a target device for authentication.
  • the target device for authentication can be determined by looking up a table (or looking up the corresponding relationship); or according to the identifier, the target device for authentication indicated by the identifier can be determined without additional operations such as table looking up.
  • the certified target device such as the second device.
  • the identification of the service is the identification number (ID) of the service, and the service is called the first service, for example.
  • the first service may be the service that the first device and the second device are about to perform. For example, before the first device and the second device are about to perform the first service, the second device first needs to authenticate the first device. Therefore, it can be considered that The target device for this authentication indicated by the service identifier is the second device.
  • the first information may also include information responsive to the input information, for example, including information responsive to the user input, or in other words, the first information includes information related to the user's input.
  • the first information is information in response to input information
  • the input information is, for example, information input by the user.
  • the user wants to perform the first service, the user presses a certain button or key, which is equivalent to inputting information, or the user performs an operation on the human-computer interaction interface or other interactive interface, which is equivalent to input ⁇ The information.
  • the first message may also be in response to certain judgment conditions or triggers. After the first device receives the information input from the user, it can start the authentication process to execute the first service.
  • the first information may also indicate the second device in an implicit manner, or the first information may include other information similar to the foregoing description.
  • the first information may also include identifications of other trigger conditions provided by other devices or the first device itself.
  • the first information includes information in response to measurement results, triggers, or information reports periodically reported by other devices, or may include the startup or restart, software and hardware updates, or plug-and-play of the first device or other devices or the entire vehicle. Information about the introduction of the device.
  • the first information may also include information in response to other events, such as an event in which the first device is powered on, or an event in which the first device receives information from other devices, and so on.
  • the user wants to perform the first service, the user presses a certain button or some buttons, which is equivalent to inputting information, and the information input by the user is received by other devices.
  • the other device can notify the first device to start the authentication process, and the first device can execute S201.
  • the first information may also include message ID information.
  • the first certificate may be the device certificate of the first device.
  • the identity information of the device can be written to the device after the production of the device is completed.
  • the manufacturer can test the device. After the test is qualified, the device manufacturer or original equipment manufacturer (original equipment manufacturer, OEM) can write the identity information of the device to the device.
  • the identity information of the device includes, for example, one or more of the following: the root certificate or secondary certificate of the device, the device certificate of the device, the model of the device, the private key used by the device, or the identity of the device.
  • the identity information of the device includes the root certificate and device certificate of the device; or, the identity information of the device includes the identity of the device; or, the identity information of the device includes the secondary certificate of the device, the private key of the device, and the device certificate.
  • the identity information of the device includes the root certificate or secondary certificate of the device, the device certificate of the device, the private key of the device, the model of the device, and the identity of the device, etc.
  • the first device may also send the first identification to the second device, and the second device may receive the first identification from the first device.
  • the first identifier is the identifier of the first device, for example, the ID of the first device.
  • the first device and the second device need to forward information through the third device. Therefore, the first device actually sends the first certificate and the first information to the third device, and the third device transfers the first certificate to the third device. And the first information is forwarded to the third device, and the second device receives the first certificate and the first information from the third device.
  • the first certificate and the first information are sent by the first device to the third device, it can also be considered that the second device receives the first certificate and the first information from the first device. If the first device still needs to send the first identification to the second device, the first identification also needs to be forwarded to the second device through the third device.
  • the third device may only perform a forwarding function, that is, the third device does not perform any processing on the information (for example, the first information and the first certificate, etc.) from the first device, but directly forwards it to the second device.
  • the third device may perform a query based on the first information to find the corresponding second device.
  • the first information is the ID of the first service
  • the first device only sends the ID of the first service and the first certificate to the third device.
  • the third device stores the correspondence between the ID of the service and the device.
  • the correspondence may be the correspondence between the ID of the service and the address of the device, and the address of the device is, for example, the IP address of the device.
  • the corresponding relationship is used to indicate which devices the corresponding service should be executed by, or used to indicate which devices need to be authenticated to perform the corresponding service, or in other words, indicate the devices associated with the service.
  • the third device queries the correspondence relationship and determines the device corresponding to the ID of the first service, for example, including the second device, then the third device can forward the first certificate and the first information to the second device.
  • the ID of one service may correspond to one or more devices.
  • the ID of the first service may only correspond to the second device, or it may correspond to multiple devices. Including the second device.
  • the third device may only forward the first information and the first certificate to the part of the device corresponding to the ID of the first service, for example, only the second device, or the third device may also forward the first information and the first service ID.
  • a certificate etc. are forwarded to all the devices corresponding to the ID of the first service.
  • the corresponding relationship can also be stored in the first device.
  • the first device can query and determine the corresponding device according to the ID of the service.
  • the third device can only be used as a forwarding device and does not need to be based on the first device.
  • the information determines the second device, or in this case, the third device can also play a filtering role as described below.
  • the third device may play a role of filtering. For example, according to the first information, the third device determines whether the second device corresponding to the first information complies with preset rules. If the second device complies with the preset rules, the third device may combine the first information with the first information. The certificate is forwarded to the second device. Otherwise, the third device does not forward the first information and the first certificate to the second device. For example, the third device may discard the first information and the first certificate, and the process ends.
  • the first information includes the ID of the first service and the identification of the second device, such as an IP address, and the first device sends the ID of the first service, the IP address of the second device, and the first certificate to the third device.
  • the third device stores the corresponding relationship, and the corresponding relationship can be considered as a preset rule.
  • the third device queries the correspondence to determine the device corresponding to the ID of the first service.
  • the third device can determine whether there is a second device corresponding to the IP address of the second device among the devices corresponding to the ID of the first service. If there is a second device, the second device complies with the preset rules.
  • the third device can forward the ID of the first service, the IP address of the second device, and the first certificate to the second device.
  • the second device does not meet the preset rules, and the third device may not forward the ID of the first service, the IP address of the second device, and the first certificate to the second device , So as to ensure information security.
  • the first information includes an identification of the second device, such as an IP address, and the first device sends the IP address of the second device and the first certificate to the third device.
  • the third device stores the association relationship between the devices. For example, for the first device, it may interact with some devices when performing corresponding services. Then the third device can store the relationship between the first device and these devices. The corresponding relationship can be considered as a preset rule. For example, the third device queries the association relationship to determine the device corresponding to the first device. The third device can determine whether there is a second device corresponding to the IP address of the second device among the devices corresponding to the first device.
  • the second device complies with the preset rules
  • the third device can forward the IP address and the first certificate of the second device to the second device, and if there is no second device in the device corresponding to the first device, then The second device does not conform to the preset rule, and the third device may not forward the IP address and the first certificate of the second device to the second device, thereby ensuring information security.
  • the first certificate it may include one of the following information or any combination of the following information: version information of the first certificate, signer information of the first certificate, subject information of the first certificate, validity information of the first certificate , Or, the signature information of the first certificate.
  • the first certificate includes the version information of the first certificate; or, the first certificate includes the signer information of the first certificate and the subject information of the first certificate; or, the first certificate includes the subject information of the first certificate, and the first certificate
  • the first certificate includes the version information of the first certificate, the signer information of the first certificate, the subject information of the first certificate, the validity information of the first certificate, and The signature information of the first certificate, and so on.
  • the first certificate may not include the subject attribute information of the first certificate, or the subject attribute information may also be referred to as application scenario information.
  • the device certificate can only be used for authentication between devices, not for authentication in other scenarios, such as secure boot or over the air (OTA) authentication, which reflects the specific nature of the device certificate and is not affected by the third aspect of other application scenarios.
  • OTA over the air
  • the leakage of the private key of the certificate affects the validity of the device certificate signature, which helps to ensure the security of the communication between different devices and the system.
  • the size of the device certificate can also be reduced through the solution provided by the embodiment of this application.
  • the first certificate including the version information of the first certificate, the signer information of the first certificate, the subject information of the first certificate, the validity information of the first certificate, and the signature information of the first certificate as an example.
  • the first device may also not send to the first device.
  • the second device sends the first information, that is, in S201, the first device can send the first certificate to the second device without sending the first information to the second device.
  • the second device sends a first random number to the first device, and the first device receives the first random number from the second device.
  • the second device may verify the first certificate to determine whether the first certificate is reliable. For example, the second device may verify the first certificate according to the third certificate of the first device. If the verification passes, it is determined that the first certificate is reliable, and if the verification fails, it is determined that the first certificate is unreliable.
  • the third certificate of a device can be an OEM root certificate, or a second-level certificate issued by an OEM/certificate authority (CA), or a third-level certificate issued by an OEM/CA, or a fourth-level certificate. It may be more levels of certificates, etc. There is no restriction on the level of certificates.
  • the third certificate of the first device may be a root certificate, or a second-level certificate, or a third-level certificate, or a fourth-level certificate, or more levels of certificates, and so on.
  • the second device may generate a random number, for example, called a first random number, and the second device may send the first random number to the first device.
  • the first random number can be used to verify the first device.
  • the second device determines that the first certificate is reliable as an example.
  • the second device may not need to generate the first random number.
  • the second device may also send a notification message to the first device, where the notification message is used to indicate that the first certificate is unreliable, or that the authentication process fails.
  • the second device may forward the first random number to the first device through the third device.
  • the content related to the first certificate may be combined in the embodiment shown in FIG. 2 or may also be used as an embodiment alone.
  • the operation of the first device to send the first certificate to the second device, and the content of the first certificate, etc. can be taken as a separate embodiment.
  • the operation of verifying the first certificate by the second device, and the content of the first certificate, etc. may be taken as a separate embodiment.
  • the first device uses the first private key to obtain the first signature according to the first random number.
  • the first private key is the private key used by the first device.
  • the first private key belongs to the identity information of the first device. It can be written into the first device after production is completed, or it can be randomly generated by the device in advance. The random number is stored in the device. Therefore, the first private key does not need to be temporarily written into the first device, and the first device can be used directly, which improves the efficiency of device authentication.
  • the first device may obtain the first signature according to the first random number and the first identifier.
  • the first device may use a hash algorithm to obtain a hash value based on the first random number and the first identifier, for example, called the first hash value, and the first device may perform the first hash value based on the first private key.
  • Sign get the first signature.
  • the first device sends the first signature to the second device, and the second device receives the first signature from the first device.
  • the first signature can be used to authenticate the first device.
  • the first device may send the first signature to the third device, and the third device forwards the first signature to the second device.
  • the second device authenticates the first device according to the first signature and the first random number.
  • the second device may authenticate the first device according to the first signature and the first random number.
  • the second device may authenticate the first device according to the first signature, the first random number, and the first identifier.
  • the second device may use the first public key to authenticate the first device according to the first random number, the first signature, and the first identification.
  • the first public key and the first private key used to obtain the first signature are the same. Pair asymmetric keys.
  • the second device can use the first public key to verify the first signature, the first random number, and the first identification, and start the verification based on the returned result. If the verification is passed, it indicates that the first device The authentication is successful; otherwise, it indicates that the authentication of the first device has failed.
  • the verification method is, for example, that the second device uses a hash algorithm to obtain a hash value based on the first random number and the first identifier, for example, the fourth hash value.
  • the second device combines the first public key and the fourth hash value.
  • the value and the first signature are input into the signature verification function (for example, called the first function) for verification, and the verification is determined according to the returned result.
  • the second device may forward the authentication result to the first device through the third device, so that the first device can learn the authentication result.
  • the authentication process described in S202 to S206 can also be replaced by other authentication processes, or, in the steps S202 to S206, there may be any one or more steps that do not need to be executed, for example, S202 does not need to be executed.
  • the second device may not need to send the first random number to the first device, and the first device may generate the first signature according to the first identifier without the first random number. As long as the authentication of the second device to the first device can be completed.
  • the second device determines a first execution strategy according to the first service. Among them, the authentication process described above corresponds to the first business.
  • S206 is also an optional step and need not be performed.
  • S206 is based on the premise that the second device fails to authenticate the first device, that is, if the second device fails to authenticate the first device in S205, the second device can perform S206, and if the second device fails to authenticate the first device in S205, If one device fails the authentication, the second device may not perform S206. For example, if the second device successfully authenticates the first device, then the subsequent step 207 may be continued, or the subsequent step 207 may not be performed, but other processes may be performed, for example, the first service may be started.
  • the first execution strategy includes, for example, the device stops working, or the device stops using part of the functions of the device.
  • the first execution strategy may include that the second device stops working, or the second device stops using part of the functions of the second device.
  • Some of the functions here may be functions related to the first business.
  • the second device is an MDC and the first service is an automatic driving function, so the MDC stops using part of the MDC functions, for example, stops using the functions related to the automatic driving function.
  • the first execution strategy may be executed by the second device or executed by the first device.
  • the second device may send instruction information to the first device, and the first device receives the instruction information from the second device, and the instruction information is used to indicate the first execution strategy.
  • the second device is a device such as a gateway or a router, or an entity with routing and forwarding functions
  • the first execution strategy may be executed by the first device, and the second device may send instruction information to the first device; or If the device is a device other than a gateway and a router, or is an entity other than an entity with routing and forwarding functions, the first execution strategy may be executed by the second device, and the second device may not send the message to the first device. Send the instruction information, but execute the first execution strategy by yourself.
  • the first information is used to indicate the second device.
  • the first information may be the identifier of the first service, or the address of the second device, etc., as long as the first device sends the first information to the second device.
  • the second device can authenticate the first device without relying on the hierarchical relationship of the devices. For example, even if the first device is a first-tier device and the second device is a third-tier device, authentication can be performed between the first device and the second device, thus realizing a distributed authentication process.
  • the authentication method in the embodiment of the present application does not require an intermediate node to authenticate multiple nodes, which reduces the burden on the device.
  • the third device can only play a forwarding role, or the third device can query and determine the second device without the first device to determine the second device by itself, which reduces the workload of the first device, or the third device It can also play a filtering role, which can further improve the security of communication.
  • the authentication scheme provided by the embodiment of the application has a certain degree of resilience.
  • the end-to-end authentication scheme provided by the embodiment of the present application has nothing to do with the architecture of the entire vehicle, has good compatibility, and can be applied to the current automobile architecture as well as the future automobile architecture.
  • the first device and the second device need to forward information through the third device.
  • the following introduces another device authentication method.
  • the first device and the second device can communicate directly without forwarding information through other devices.
  • Figure 3 is a flowchart of this method.
  • the application of this method to the network architecture shown in FIG. 1 is taken as an example.
  • the method can be executed by two communication devices (or two communication devices), for example, the first communication device and the second communication device.
  • the first communication device or the second communication device may be a vehicle-mounted device or a communication device (such as a chip system) capable of supporting the vehicle-mounted device to implement the functions required by the method, and of course, may also be other communication devices.
  • the two communication devices can be implemented in the same form, for example, both can be implemented in the form of equipment, or the two communication devices can also be implemented as Different forms, for example, the first communication device is implemented in the form of a device, the second communication device is implemented in the form of a chip system, and so on.
  • the method is executed by the first device and the second device as an example, that is, the first communication device is the first device and the second communication device is the second device as an example.
  • the first device may be the device to be authenticated
  • the second device may be other devices except gateways and routers, or other entities other than entities with routing and forwarding functions, or the second device may also be gateways Or a device such as a router, or the second device may also be an entity with a routing and forwarding function.
  • the gateway may also refer to a physical device with the function of routing and forwarding equipment.
  • the embodiment shown in FIG. 3 can be considered to be a scenario where the gateway performs centralized authentication.
  • each domain controller can The authentication is performed by the gateway.
  • the embodiment shown in FIG. 3 can also be considered as a distributed authentication scenario.
  • each domain controller can be authenticated by the gateway, or mutually authenticate each other.
  • the second device is a device other than a gateway and a router, it can be considered that the embodiment shown in FIG. 3 is a distributed authentication scenario that does not require a gateway to perform centralized authentication. Because this embodiment is applied to the network architecture shown in FIG. 1 as an example, the first device described below is, for example, the domain controller in the network architecture shown in FIG. 1, and the second device described below is The device is, for example, the T-Box, OBD, or gateway in the network architecture shown in FIG. 1.
  • the first device sends the first information and the first certificate to the second device, and the second device receives the first information and the first certificate from the first device.
  • the first information is used to indicate the second device, and the first certificate is the device certificate of the first device.
  • the first information may be used for authentication.
  • the first information may include information about the second device, the information about the second device may include, for example, the IP address of the second device, or the information about the second device may include, for example, the ID of the second device, or the information about the second device may include, for example, the first device.
  • the IP address of the second device and the ID of the second device, or the information of the second device may also include other information of the second device. Therefore, the first information can indicate the second device. Or it can be considered that the first information is associated with the second device.
  • the first information may also include an identifier of the service, and the identifier may indicate a target device for authentication.
  • the target device for authentication can be determined by looking up the table; or based on the identifier, the target device for authentication indicated by the identifier can be determined without additional operations such as looking up the table.
  • the certified target device such as the second device.
  • the identification of the service is the identification number (ID) of the service, and the service is called the first service, for example.
  • the first service may be the service that the first device and the second device are about to perform. For example, before the first device and the second device are about to perform the first service, the second device first needs to authenticate the first device. Therefore, it can be considered that The target device for this authentication indicated by the service identifier is the second device.
  • the first information may also include information responsive to the input information, for example, including information responsive to the user input, or in other words, the first information includes information related to the user's input.
  • the first information is information in response to input information
  • the input information is, for example, information input by the user.
  • the user wants to perform the first service, the user presses a certain button or key, which is equivalent to inputting information, or the user performs an operation on the human-computer interaction interface or other interactive interface, which is equivalent to input ⁇ The information.
  • the first device After the first device receives the information input from the user, it can start the authentication process to execute the first service.
  • the first information may also indicate the second device in an implicit manner, or the first information may include other information similar to the foregoing description.
  • the first information may also include identifications of other trigger conditions provided by other devices or the first device itself.
  • the first information includes information in response to measurement results, triggers, or information reports periodically reported by other devices, or may include the startup or restart, software and hardware updates, or plug-and-play of the first device or other devices or the entire vehicle. Information about the introduction of the device.
  • the first information may also include information in response to other events, such as an event in which the first device is powered on, or an event in which the first device receives information from other devices, and so on.
  • the user wants to perform the first service, the user presses a certain button or some buttons, which is equivalent to inputting information, and the information input by the user is received by other devices.
  • the other device can notify the first device to start the authentication process, and the first device can execute S201.
  • the first information may also include message ID information.
  • the first certificate may be the device certificate of the first device.
  • the identity information of the device can be written to the device after the production of the device is completed.
  • the manufacturer can test the device, and after the test is qualified, the manufacturer or OEM of the device can write the identity information of the device to the device.
  • the identity information of the device includes, for example, one or more of the following: the third certificate of the device, the device certificate of the device, the model of the device, the private key used by the device, or the identity of the device.
  • the identity information of the device includes the third certificate and the device certificate of the device; or, the identity information of the device includes the identity of the device; or, the identity information of the device includes the third certificate of the device, the private key of the device, and the device certificate.
  • the identity of the device; or, the identity information of the device includes the third certificate of the device, the device certificate of the device, the private key of the device, the model of the device, the identity of the device, and so on.
  • the third certificate of a device can be an OEM root certificate, or a second-level certificate issued by OEM/CA, or a third-level certificate issued by OEM/CA, or a fourth-level certificate, or a certificate of more levels. And so on, there is no restriction on the level of the certificate.
  • the third certificate of the first device may be a root certificate, or a second-level certificate, or a third-level certificate, or a fourth-level certificate, or more levels of certificates, and so on.
  • the first device may also send the first identification to the second device, and the second device may receive the first identification from the first device.
  • the first identifier is the identifier of the first device, for example, the ID of the first device.
  • the first device can directly send the first certificate and the first information to the second device, and the second device can also directly send the first certificate and the first information to the second device. Receive the first certificate and first information from the first device.
  • the first certificate it may include one of the following information or any combination of the following information: version information of the first certificate, signer information of the first certificate, subject information of the first certificate, validity information of the first certificate , Or, the signature information of the first certificate.
  • the first certificate includes the version information of the first certificate; or, the first certificate includes the signer information of the first certificate and the subject information of the first certificate; or, the first certificate includes the subject information of the first certificate, and the first certificate
  • the first certificate includes the version information of the first certificate, the signer information of the first certificate, the subject information of the first certificate, the validity information of the first certificate, and The signature information of the first certificate, and so on.
  • the first certificate may not include the subject attribute information of the first certificate, or the subject attribute information may also be referred to as application scenario information.
  • the first certificate including the version information of the first certificate, the signer information of the first certificate, the subject information of the first certificate, the validity information of the first certificate, and the signature information of the first certificate as an example.
  • the included content refer to Table 1 in the embodiment shown in FIG. 2.
  • the first device may also not send to the first device.
  • the second device sends the first information, that is, in S301, the first device can send the first certificate to the second device without sending the first information to the second device.
  • the second device sends a first random number to the first device, and the first device receives the first random number from the second device.
  • the second device may verify the first certificate to determine whether the first certificate is reliable. For example, the second device may verify the first certificate according to the third certificate of the first device. If the verification passes, it is determined that the first certificate is reliable, and if the verification fails, it is determined that the first certificate is unreliable.
  • the second device may generate a random number, for example, called a first random number, and the second device may send the first random number to the first device.
  • the first random number can be used to verify the first device.
  • the second device determines that the first certificate is reliable as an example.
  • the second device may not need to generate the first random number.
  • the second device may also send a notification message to the first device, where the notification message is used to indicate that the first certificate is unreliable, or that the authentication process fails.
  • the content related to the first certificate may be combined in the embodiment shown in FIG. 3, or may also be used as an embodiment alone.
  • the operation of the first device to send the first certificate to the second device, and the content of the first certificate, etc. can be taken as a separate embodiment.
  • the operation of verifying the first certificate by the second device, and the content of the first certificate, etc. may be taken as a separate embodiment.
  • the first device uses the first private key to obtain the first signature according to the first random number.
  • S303 reference may be made to S203 in the embodiment shown in FIG. 2.
  • the first device sends the first signature to the second device, and the second device receives the first signature from the first device.
  • the first signature can be used to authenticate the first device.
  • the second device authenticates the first device according to the first signature and the first random number.
  • the second device may send the authentication result to the first device, so that the first device can learn the authentication result.
  • S305 refer to S205 in the embodiment shown in FIG. 2.
  • the authentication process described in S302 to S306 can also be replaced by other authentication processes, or, in the steps S302 to S306, there may be any one or more steps that do not need to be executed, for example, S302 does not need to be executed.
  • the first device may not need to send the second random number to the second device, and the second device may generate the second signature according to the second identifier without the second random number. As long as the authentication of the first device to the second device can be completed.
  • the second device determines a first execution strategy according to the first service. Among them, the authentication process described above corresponds to the first business.
  • S306 is also an optional step and need not be performed.
  • S306 is based on the premise that the second device fails to authenticate the first device, that is, if the second device fails to authenticate the first device in S305, the second device can perform S306, and if the second device fails to authenticate the first device in S305, If one device fails the authentication, the second device may not perform S306. For example, if the second device authenticates the first device successfully, then the subsequent step 307 may be continued, or the subsequent step 307 may not be performed, but other processes may be performed, for example, the first service may be started.
  • the first execution strategy includes, for example, the device stops working, or the device stops using part of the functions of the device.
  • the first execution strategy may include that the second device stops working, or the second device stops using part of the functions of the second device.
  • Some of the functions here may be functions related to the first business. For example, if the second device is an MDC and the first service is an automatic driving function, the MDC stops using part of the MDC functions, for example, stops using functions related to the automatic driving function.
  • the first execution strategy may be executed by the second device or executed by the first device.
  • the second device may send instruction information to the first device, and the first device receives the instruction information from the second device, and the instruction information is used to indicate the first execution strategy.
  • the second device is a device such as a gateway or a router, or an entity with routing and forwarding functions
  • the first execution strategy may be executed by the first device, and the second device may send instruction information to the first device; or If the device is a device other than a gateway and a router, or is an entity other than an entity with routing and forwarding functions, the first execution strategy may be executed by the second device, and the second device may not send the message to the first device. Send the instruction information, but execute the first execution strategy by yourself.
  • the first information is used to indicate the second device.
  • the first information may be the identifier of the first service, or the address of the second device, etc., as long as the first device sends the first information to the second device.
  • the second device can authenticate the first device without relying on the hierarchical relationship of the devices. For example, even if the first device is a first-tier device and the second device is a third-tier device, authentication can be performed between the first device and the second device, thus realizing a distributed authentication process.
  • the authentication method in the embodiment of the present application does not require an intermediate node to authenticate multiple nodes, which reduces the burden on the device.
  • end-to-end authentication between devices is realized, the dependence on intermediate nodes is reduced, more vehicle-mounted devices can be authenticated, and the safety of vehicle-mounted devices is improved.
  • the first device and the second device do not need to forward information through other devices, but can communicate directly, reducing communication delay, improving authentication efficiency, and more effectively achieving end-to-end authentication between devices .
  • the authentication scheme provided by the embodiment of the application has a certain degree of resilience.
  • the end-to-end authentication scheme provided by the embodiment of the present application has nothing to do with the architecture of the entire vehicle, has good compatibility, and can be applied to the current automobile architecture as well as the future automobile architecture.
  • the process introduced in the embodiment shown in FIG. 2 and the embodiment shown in FIG. 3 can be regarded as a one-way authentication process, in which the second device authenticates the first device.
  • two-way authentication may be implemented, that is, in addition to the second device to authenticate the first device, the first device may also authenticate the second device.
  • FIG. 4 is a flowchart of the method.
  • the application of this method to the network architecture shown in FIG. 1 is taken as an example.
  • the method can be executed by three communication devices (or, three communication devices), which are, for example, the first communication device, the second communication device, and the third communication device.
  • the first communication device, the second communication device, or the third communication device may be a vehicle-mounted device or a communication device (such as a chip system) capable of supporting the vehicle-mounted device to implement the functions required by the method, and of course, may also be other communication devices.
  • the three communication devices can be implemented in the same form, for example, all can be implemented in the form of equipment, or the three communication devices can be implemented in the same form.
  • the device may also be implemented in different forms, for example, the first communication device is implemented in the form of a device, the second communication device is implemented in the form of a chip system, and the third communication device is implemented in the form of a device, and so on.
  • the method is executed by the first device, the second device, and the third device as an example, that is, it is assumed that the first communication device is the first device, the second communication device is the second device, and the second device is the second device.
  • the third communication device is the third device as an example.
  • the first device may be a device to be authenticated
  • the second device may be a device other than a gateway and a router, or an entity other than an entity having a routing and forwarding function.
  • the gateway may also refer to a physical device with the function of routing and forwarding equipment. Because this embodiment is applied to the network architecture shown in FIG. 1 as an example, the first device described below is, for example, the domain controller in the network architecture shown in FIG.
  • the device is, for example, the T-Box or OBD in the network architecture shown in FIG. 1, and the third device described below is, for example, the gateway in the network architecture shown in FIG. 1; or, the first device described below is, for example, It is the T-Box or OBD in the network architecture shown in FIG. 1, the second device described below is, for example, the domain controller in the network architecture shown in FIG. 1, and the third device described below is, for example, FIG.
  • the first device sends the first information and the first certificate to the second device, and the second device receives the first information and the first certificate from the first device.
  • the first information is used to indicate the second device, and the first certificate is the device certificate of the first device.
  • the first device may also not send to the first device.
  • the second device sends the first information, that is, in S401, the first device can send the first certificate to the second device without sending the first information to the second device.
  • the second device sends a second certificate to the first device, and the first device receives the second certificate from the second device.
  • the second certificate is the device certificate of the second device.
  • the second device may verify the first certificate to determine whether the first certificate is reliable. For example, the second device may verify the first certificate according to the third certificate of the first device. If the verification passes, it is determined that the first certificate is reliable, and if the verification fails, it is determined that the first certificate is unreliable.
  • the third certificate of a device can be an OEM root certificate, or a second-level certificate issued by OEM/CA, or a third-level certificate issued by OEM/CA, or a fourth-level certificate, or a certificate of more levels. And so on, there is no restriction on the level of the certificate.
  • the third certificate of the first device may be a root certificate, or a second-level certificate, or a third-level certificate, or a fourth-level certificate, or more levels of certificates, and so on.
  • the second device may send the second certificate to the first device.
  • the second device may send the second certificate to the third device, and the third device forwards it to the first device.
  • the second device may also send a second identification to the first device, where the second identification is the identification of the second device, for example, the ID of the second device.
  • the second device can send the second identifier to the third device, and the third device forwards it to the first device.
  • the second device may not need to send the second certificate to the first device.
  • the second device may also send a notification message to the first device, where the notification message is used to indicate that the first certificate is unreliable, or that the authentication process fails.
  • the content included in the second certificate may be similar to the content included in the first certificate.
  • the second certificate may include the following information or any combination of the following information: version information of the second certificate, signer information of the second certificate, subject information of the second certificate, validity information of the second certificate , Or, the signature information of the second certificate.
  • the second certificate includes the version information of the second certificate; or, the second certificate includes the signer information of the second certificate and the subject information of the second certificate; or, the second certificate includes the subject information of the second certificate, and the second certificate
  • the second certificate includes the version information of the second certificate, the signer information of the second certificate, the subject information of the second certificate, the validity information of the second certificate, and The signature information of the second certificate, and so on.
  • the second certificate please refer to the introduction to the first certificate in the embodiment shown in FIG. 2.
  • the content related to the first certificate may be combined in the embodiment shown in FIG. 4, or may also be used as an embodiment alone.
  • the operation of the first device to send the first certificate to the second device, and the content of the first certificate, etc. can be taken as a separate embodiment.
  • the operation of verifying the first certificate by the second device, and the content of the first certificate, etc. may be taken as a separate embodiment.
  • the content related to the second certificate can be combined in the embodiment shown in FIG. 4, or can also be used as an embodiment alone.
  • the operation of the second device to send the second certificate to the first device, and the content of the second certificate, etc. can be taken as a separate embodiment.
  • the operation of verifying the second certificate by the first device, and the content of the second certificate, etc. may be taken as an embodiment separately.
  • the first device sends a second random number to the second device, and the second device receives the second random number from the first device.
  • the first device may generate a second random number, and may send the second random number to the second device.
  • the second random number is used to authenticate the second device.
  • the first device may send the second random number to the third device, and the third device forwards it to the second device.
  • the second device uses the second private key to obtain the second signature according to the second random number.
  • the second device may obtain the second signature only according to the second random number, or, as an optional manner, the second device may also obtain the second signature according to the second random number and the second identifier.
  • the second identification is the identification of the second device, for example, the ID of the second device.
  • the second private key is a private key used by the second device.
  • the second private key belongs to the identity information of the second device, and may be written by the second device to the second device after production is completed. Therefore, the second private key does not need to be temporarily written into the second device, and the second device can be used directly, which improves the efficiency of device authentication.
  • the second device may use a hash algorithm to obtain a hash value based on the second random number and the second identifier, for example, called the second hash value.
  • the second device may perform the second hash value based on the second private key. Sign, get the second signature.
  • the second device sends the second signature and the second identity to the first device, and the first device receives the second signature and the second identity from the second device.
  • the second signature is used to authenticate the second device.
  • the second device may send the second signature and the second identification to the third device, and the third device forwards the second signature and the second identification to the first device.
  • the second device may also send the second identifier to the third device, and the third device forwards it to the first device.
  • the second device may also generate the first random number, send the first random number to the third device, and the third device forwards it to the first device.
  • S406 The first device authenticates the second device according to the second signature and the second random number. If the authentication is passed, execute S408, or if the authentication fails, execute S407.
  • the first device may authenticate the second device according to the second signature and the second random number. Or, if the second device obtains the second signature based on the second random number and the second identification, the first device may authenticate the second device based on the second signature, the second random number, and the second identification.
  • the first device may use the second public key to authenticate the second device according to the second random number, the second signature, and the second identification.
  • the second public key and the second private key used to obtain the second signature are the same Pair asymmetric keys.
  • the first device can use the second public key to verify the second signature, the second random number, and the second identification, and start the verification based on the returned result. If the verification is passed, it indicates that the second device The authentication is successful; otherwise, it indicates that the authentication of the second device has failed.
  • the way of verification is, for example, that the first device uses a hash algorithm to obtain a hash value based on the second random number and the second identifier, for example, the third hash value.
  • the first device uses the second public key and the third hash value.
  • the value and the second signature are input into the signature verification function (for example, called the second function) to verify the signature, and determine whether the verification is passed according to the returned result.
  • the first function and the second function used for signature verification may be the same function or different functions.
  • the first device may forward the authentication result to the second device through the third device, so that the second device can learn the authentication result.
  • the first device determines a second execution strategy according to the first service. Among them, the authentication process described above corresponds to the first business.
  • S407 is also an optional step and need not be performed.
  • S407 is based on the premise that the second device fails to authenticate the first device, that is, if the first device fails to authenticate the second device in S406, the first device can perform S407, and if the first device fails to authenticate the second device in S406, If the authentication of the second device fails, the first device may not execute S407, but execute S408.
  • the second execution strategy includes, for example, the device stops working, or the device stops using part of the function of the device.
  • the first execution strategy may include that the first device stops working, or the first device stops using part of the functions of the first device.
  • Some of the functions here may be functions related to the first business. For example, if the first device is MDC, and the first service is an automatic driving function, then MDC stops using part of the MDC function, for example, stops using functions related to the automatic driving function. For example, the MDC may not activate the automatic driving function, or the MDC may be disabled Autopilot function.
  • the second execution strategy may be executed by the first device or executed by the second device. If the second execution strategy should be executed by the second device, the first device may send instruction information to the second device, and the second device receives the instruction information from the first device, and the instruction information is used to indicate the second execution strategy.
  • the second execution strategy can be executed by the first device, and the first device may not need to send instructions to the second device, but instead It is sufficient to execute the first execution strategy; or, if the second device is a device other than gateways and routers, or is an entity other than an entity with routing and forwarding functions, then the second execution strategy can be used by the second device If executed, the first device can send the instruction information to the second device.
  • the first device uses the first private key to obtain the first signature according to the first random number.
  • the first device can obtain the first signature, and the first signature is used to authenticate the first device.
  • the first private key is a private key used by the first device.
  • the first private key belongs to the identity information of the first device, and may be written by the first device to the first device after production is completed. Therefore, the first private key does not need to be temporarily written into the first device, and the first device can be used directly, which improves the efficiency of device authentication.
  • the first device may obtain the first signature according to the first random number and the first identifier.
  • the first device may use a hash algorithm to obtain a hash value based on the first random number and the first identifier, for example, called the first hash value, and the first device may perform the first hash value based on the first private key.
  • Sign get the first signature.
  • the first device sends the first signature to the second device, and the second device receives the first signature from the first device.
  • the first device may send the first signature to the third device, and the third device forwards the first signature to the second device.
  • the second device authenticates the first device according to the first signature and the first random number.
  • the second device may authenticate the first device according to the first signature and the first random number.
  • the second device may authenticate the first device according to the first signature, the first random number, and the first identifier.
  • For the authentication process refer to S205 in the embodiment shown in FIG. 2.
  • the second device may forward the authentication result to the first device through the third device, so that the first device can learn the authentication result.
  • the authentication process described in S402 ⁇ S410 can also be replaced by other authentication processes, or, in the steps S402 ⁇ S410, there can also be any one or more steps that do not need to be executed, for example, S403 does not need to be executed.
  • the first device may not need to send the second random number to the second device, and the second device may generate the second signature according to the second identification, without the second random number, as long as the authentication of the first device to the second device can be completed.
  • the second device determines a first execution strategy according to the first service. Among them, the authentication process described above corresponds to the first business.
  • S411 is also an optional step and need not be performed.
  • S411 is based on the premise that the second device fails to authenticate the first device, that is, if the second device fails to authenticate the first device in S410, the second device can perform S411, and if the second device fails to authenticate the first device in S410, If one device fails the authentication, the second device may not perform S411. For example, if the second device successfully authenticates the first device, other processes can be continued, for example, the first service can be started.
  • the first execution strategy includes, for example, the device stops working, or the device stops using part of the functions of the device.
  • the first execution strategy may include that the second device stops working, or the second device stops using part of the functions of the second device.
  • Some of the functions here may be functions related to the first business.
  • the second device is an MDC and the first service is an automatic driving function, so the MDC stops using part of the MDC functions, for example, stops using the functions related to the automatic driving function.
  • the first execution strategy may be executed by the second device or executed by the first device. If the first execution strategy should be executed by the first device, the second device may send instruction information to the first device, and the first device receives the instruction information from the second device, and the instruction information is used to indicate the first execution strategy. For example, if the second device is a device such as a gateway or a router, or an entity with routing and forwarding functions, the first execution strategy may be executed by the first device, and the second device may send instruction information to the first device; or If the device is a device other than a gateway and a router, or is an entity other than an entity with routing and forwarding functions, the first execution strategy may be executed by the second device, and the second device may not send the message to the first device. Send the instruction information, but execute the first execution strategy by yourself.
  • the first information is used to indicate the second device.
  • the first information may be the identifier of the first service, or the address of the second device, etc., as long as the first device sends the first information to the second device.
  • the second device can authenticate the first device without relying on the hierarchical relationship of the devices. For example, even if the first device is a first-tier device and the second device is a third-tier device, authentication can be performed between the first device and the second device, thus realizing a distributed authentication process.
  • the authentication method in the embodiment of the present application does not require an intermediate node to authenticate multiple nodes, which reduces the burden on the device.
  • the third device can only play a forwarding role, or the third device can query and determine the second device without the first device to determine the second device by itself, which reduces the workload of the first device, or the third device It can also play a filtering role, which can further improve the security of communication.
  • the authentication scheme provided by the embodiment of the application has a certain degree of resilience.
  • the end-to-end authentication scheme provided by the embodiment of the present application has nothing to do with the architecture of the entire vehicle, has good compatibility, and can be applied to the current automobile architecture as well as the future automobile architecture.
  • two-way authentication can be implemented between the two devices, which can further improve the reliability of the communication process.
  • the first device and the second device need to forward information through the third device.
  • the following introduces another device authentication method.
  • the first device and the second device still perform two-way authentication, but the first device and the second device can communicate directly without forwarding information through other devices.
  • Figure 5 is a flowchart of this method.
  • the application of this method to the network architecture shown in FIG. 1 is taken as an example.
  • the method can be executed by two communication devices (or two communication devices), for example, the first communication device and the second communication device.
  • the first communication device or the second communication device may be a vehicle-mounted device or a communication device (such as a chip system) capable of supporting the vehicle-mounted device to implement the functions required by the method, and of course, may also be other communication devices. And there are no restrictions on the implementation of the first communication device and the second communication device.
  • the two communication devices can be implemented in the same form, for example, both can be implemented in the form of equipment, or the two communication devices can also be implemented as Different forms, for example, the first communication device is implemented in the form of a device, the second communication device is implemented in the form of a chip system, and so on.
  • the method is executed by the first device and the second device as an example, that is, the first communication device is the first device and the second communication device is the second device as an example.
  • the first device may be the device to be authenticated
  • the second device may be other devices except gateways and routers, or other entities other than entities with routing and forwarding functions, or the second device may also be gateways Or a device such as a router, or the second device may also be an entity with a routing and forwarding function.
  • the gateway may also refer to a physical device with the function of routing and forwarding equipment. Among them, if the second device is a device such as a gateway or a router, or an entity with routing and forwarding functions, the embodiment shown in FIG.
  • each domain controller can The authentication is performed by the gateway.
  • the embodiment shown in FIG. 5 can also be considered as a distributed authentication scenario.
  • each domain controller can be authenticated by the gateway, or mutually authenticate each other.
  • the second device is a device other than a gateway and a router, it can be considered that the embodiment shown in FIG. 5 is a distributed authentication scenario that does not require a gateway to perform centralized authentication. Because this embodiment is applied to the network architecture shown in FIG. 1 as an example, the first device described below is, for example, the domain controller in the network architecture shown in FIG. 1, and the second device described below is The device is, for example, the T-Box, OBD, or gateway in the network architecture shown in FIG. 1.
  • the first device sends the first information and the first certificate to the second device, and the second device receives the first information and the first certificate from the first device.
  • the first information is used to indicate the second device, and the first certificate is the device certificate of the first device.
  • the first device may also not send to the first device.
  • the second device sends the first information, that is, in S501, the first device can send the first certificate to the second device without sending the first information to the second device.
  • the second device sends a second certificate to the first device, and the first device receives the second certificate from the second device.
  • the second certificate is the device certificate of the second device.
  • the second device may verify the first certificate to determine whether the first certificate is reliable. For example, the second device may verify the first certificate according to the third certificate of the first device. If the verification passes, it is determined that the first certificate is reliable, and if the verification fails, it is determined that the first certificate is unreliable.
  • the third certificate of a device can be an OEM root certificate, or a second-level certificate issued by OEM/CA, or a third-level certificate issued by OEM/CA, or a fourth-level certificate, or a certificate of more levels. And so on, there is no restriction on the level of the certificate.
  • the third certificate of the first device may be a root certificate, or a second-level certificate, or a third-level certificate, or a fourth-level certificate, or more levels of certificates, and so on.
  • the second device may send the second certificate to the first device.
  • the second device may also send a second identification to the first device, where the second identification is the identification of the second device, for example, the ID of the second device.
  • the second device may not need to send the second certificate to the first device.
  • the second device may also send a notification message to the first device, where the notification message is used to indicate that the first certificate is unreliable, or that the authentication process fails.
  • the content related to the first certificate may be combined in the embodiment shown in FIG. 5, or may also be used as an embodiment alone.
  • the operation of the first device to send the first certificate to the second device, and the content of the first certificate, etc. can be taken as a separate embodiment.
  • the operation of verifying the first certificate by the second device, and the content of the first certificate, etc. may be taken as a separate embodiment.
  • the content related to the second certificate can be combined in the embodiment shown in FIG. 5, or can also be used as an embodiment alone.
  • the operation of the second device to send the second certificate to the first device, and the content of the second certificate, etc. can be taken as a separate embodiment.
  • the operation of verifying the second certificate by the first device, and the content of the second certificate, etc. may be taken as an embodiment separately.
  • S503 The first device sends a second random number to the second device, and the second device receives the second random number from the first device.
  • the first device may generate a second random number, and may send the second random number to the second device.
  • the second random number is used to authenticate the second device.
  • the second device uses the second private key to obtain the second signature according to the second random number.
  • the second device may obtain the second signature only according to the second random number, or, as an optional manner, the second device may also obtain the second signature according to the second random number and the second identifier.
  • the second identification is the identification of the second device, for example, the ID of the second device.
  • the second private key is a private key used by the second device.
  • the second private key belongs to the identity information of the second device, and may be written by the second device to the second device after production is completed. Therefore, the second private key does not need to be temporarily written into the second device, and the second device can be used directly, which improves the efficiency of device authentication.
  • the second device may use a hash algorithm to obtain a hash value based on the second random number and the second identifier, for example, called the second hash value.
  • the second device may perform the second hash value based on the second private key. Sign, get the second signature.
  • S505 The second device sends the second signature and the second identification to the first device, and the first device receives the second signature and the second identification from the second device.
  • the second signature is used to authenticate the second device.
  • the second device may also send the second identifier to the first device.
  • the second device may also generate a first random number, and send the first random number to the first device.
  • S506 The first device authenticates the second device according to the second signature and the second random number. If the authentication is passed, execute S508, or if the authentication fails, execute S507.
  • the first device may authenticate the second device according to the second signature and the second random number. Or, if the second device obtains the second signature based on the second random number and the second identification, the first device may authenticate the second device based on the second signature, the second random number and the second identification.
  • the first device may send the authentication result to the second device, so that the second device can learn the authentication result.
  • the first device determines a second execution strategy according to the first service. Among them, the authentication process described above corresponds to the first business.
  • S507 is also an optional step and does not have to be performed.
  • S507 is based on the premise that the second device fails to authenticate the first device, that is, if the first device fails to authenticate the second device in S506, the first device can execute S507, and if the first device fails to authenticate the second device in S506, If the authentication of the second device fails, the first device may not execute S507, but execute S508.
  • the second execution strategy includes, for example, the device stops working, or the device stops using part of the function of the device.
  • the first execution strategy may include that the first device stops working, or the first device stops using part of the functions of the first device.
  • Some of the functions here may be functions related to the first business. For example, if the first device is MDC, and the first service is an automatic driving function, then MDC stops using part of the MDC function, for example, stops using functions related to the automatic driving function. For example, the MDC may not activate the automatic driving function, or the MDC may be disabled Autopilot function.
  • the second execution strategy may be executed by the second device or executed by the first device. If the second execution strategy should be executed by the second device, the first device may send instruction information to the second device, and the second device receives the instruction information from the first device, and the instruction information is used to indicate the second execution strategy.
  • the second execution strategy can be executed by the first device, and the first device may not need to send instructions to the second device, but instead It is sufficient to execute the second execution strategy; or, if the second device is a device other than gateways and routers, or is an entity other than an entity with routing and forwarding functions, then the second execution strategy can be used by the second device If executed, the first device can send the instruction information to the second device.
  • the first device uses the first private key to obtain the first signature according to the first random number.
  • the first device can obtain the first signature, and the first signature is used to authenticate the first device.
  • the first private key is a private key used by the first device.
  • the first private key belongs to the identity information of the first device, and may be written by the first device to the first device after production is completed. Therefore, the first private key does not need to be temporarily written into the first device, and the first device can be used directly, which improves the efficiency of device authentication.
  • the first device may obtain the first signature according to the first random number and the first identifier.
  • the first device may use a hash algorithm to obtain a hash value based on the first random number and the first identifier, for example, called the first hash value, and the first device may perform the first hash value based on the first private key.
  • Sign get the first signature.
  • the first device sends the first signature to the second device, and the second device receives the first signature from the first device.
  • the second device authenticates the first device according to the first signature and the first random number.
  • the second device may perform signature verification and verification on the first device according to the public key, the first signature, and the first random number of the first device.
  • the second device may perform signature verification and verification on the first device based on the first signature, the first random number, and the first identifier.
  • For the authentication process refer to S205 in the embodiment shown in FIG. 2.
  • the second device may forward the authentication result to the first device through the third device, so that the first device can learn the authentication result.
  • the authentication process described in S502-S510 can also be replaced by other authentication processes, or, in the steps S502-S510, there may be any one or more steps that do not need to be executed, for example, S503 may not need to be executed.
  • the first device may not need to send the second random number to the second device, and the second device may generate the second signature according to the second identification, without the second random number, as long as the authentication of the first device to the second device can be completed.
  • the second device determines a first execution strategy according to the first service. Among them, the authentication process described above corresponds to the first business.
  • S511 is also an optional step and does not have to be performed.
  • S511 is based on the premise that the second device fails to authenticate the first device, that is, if the second device fails to authenticate the first device in S510, the second device can perform S511, and if the second device fails to authenticate the first device in S510, If one device fails the authentication, the second device may not perform S511. For example, if the second device successfully authenticates the first device, other processes can be continued, for example, the first service can be started.
  • the first execution strategy includes, for example, the device stops working, or the device stops using part of the functions of the device.
  • the first execution strategy may include that the second device stops working, or the second device stops using part of the functions of the second device.
  • Some of the functions here may be functions related to the first business.
  • the second device is a T-Box
  • the first service is an automatic driving function, so the T-Box stops using part of the T-Box functions, for example, it stops using the functions related to the automatic driving function.
  • the first execution strategy may be executed by the second device or executed by the first device. If the first execution strategy should be executed by the first device, the second device may send instruction information to the first device, and the first device receives the instruction information from the second device, and the instruction information is used to indicate the first execution strategy. For example, if the second device is a device such as a gateway or a router, or an entity with routing and forwarding functions, the first execution strategy may be executed by the first device, and the second device may send instruction information to the first device; or If the device is a device other than a gateway and a router, or is an entity other than an entity with routing and forwarding functions, the first execution strategy may be executed by the second device, and the second device may not send the message to the first device. Send the instruction information, but execute the first execution strategy by yourself.
  • the first information is used to indicate the second device.
  • the first information may be the identifier of the first service, or the address of the second device, etc., as long as the first device sends the first information to the second device.
  • the second device can authenticate the first device without relying on the hierarchical relationship of the devices. For example, even if the first device is a first-tier device and the second device is a third-tier device, authentication can be performed between the first device and the second device, thus realizing a distributed authentication process.
  • the authentication method in the embodiment of the present application does not require an intermediate node to authenticate multiple nodes, which reduces the burden on the device.
  • end-to-end authentication between devices is realized, the dependence on intermediate nodes is reduced, more vehicle-mounted devices can be authenticated, and the safety of vehicle-mounted devices is improved.
  • the first device and the second device do not need to forward information through other devices, but can communicate directly, reducing communication delay, improving authentication efficiency, and more effectively achieving end-to-end authentication between devices .
  • the authentication scheme provided by the embodiment of the application has a certain degree of resilience.
  • the end-to-end authentication scheme provided by the embodiment of the present application has nothing to do with the architecture of the entire vehicle, has good compatibility, and can be applied to the current automobile architecture as well as the future automobile architecture.
  • two devices can implement two-way authentication, which further improves the reliability of the communication process.
  • the MDC communicates with the T-Box through the gateway.
  • the MDC and the T-BOX communicate through Ethernet or a flexible data rate controller area network (controller area network with rlexible data-rate).
  • a secure transmission channel can be established between MDC and T-Box for end-to-end secure transmission.
  • the information transmitted through the secure transmission channel can be transparently transmitted at the gateway without encryption and decryption, which improves the transmission speed.
  • end-to-end authentication is required, that is, authentication is required between MDC and T-Box.
  • FIG. 6 is a flowchart of the authentication process between MDC and T-Box.
  • the mutual authentication between the MDC and the T-Box is taken as an example.
  • T-Box can be regarded as the first device
  • MDC can be regarded as the second device.
  • Information can be forwarded between MDC and T-Box through a gateway, and the gateway can be regarded as a third device.
  • the T-Box sends the device certificate 1 and the first information to the MDC, and the MDC receives the device certificate 1 and the first information from the T-Box.
  • T-Box sends the device certificate 1 and the first information to the gateway, and the gateway forwards it to the MDC.
  • Device certificate 1 is the device certificate of T-Box.
  • the first information includes the IP address of the MDC
  • the gateway may forward the device certificate 1 and the first information to the MDC according to the IP address.
  • the gateway may determine whether forwarding is required according to the filtering rules during forwarding. If the forwarding rules are violated, the gateway discards the first information and the device certificate 1, and does not forward the information.
  • the first information includes the ID of the first service.
  • the gateway After the gateway receives the ID of the first service, it can query the correspondence between the ID of the service and the device to determine the device corresponding to the ID of the first service, for example, the ID of the first service.
  • the device corresponding to the ID includes the MDC, and the gateway forwards the device certificate 1 and the first information to the MDC.
  • T-Box can also send ID1 to MDC.
  • T-Box can forward ID1 to MDC through the gateway.
  • ID1 is the ID of the T-Box.
  • the MDC verifies whether the device certificate 1 is legal.
  • the MDC can verify the device certificate 1 based on the root certificate or the secondary certificate of the T-Box. In addition, MDC can also verify the validity of ID1.
  • the MDC sends the device certificate 2 to the T-Box, and the T-Box receives the device certificate 2 from the MDC.
  • Device certificate 2 is the device certificate of MDC.
  • the MDC sends the device certificate 2 to the gateway, and the gateway forwards it to the T-Box.
  • MDC can also send ID2 to T-Box.
  • MDC can send ID2 to the gateway, and the gateway forwards it to T-Box.
  • ID2 is the ID of the MDC.
  • the T-Box verifies whether the device certificate 2 is legal.
  • T-Box can verify the device certificate 2 based on the root certificate or the secondary certificate of the MDC. In addition, T-Box can also verify the validity of ID2.
  • the T-Box sends a random number r2 to the MDC, and the MDC receives a random number r2 from the T-Box.
  • the random number r2 may be a second random number.
  • T-Box sends the random number r2 to the gateway, and the gateway forwards it to the MDC.
  • the MDC calculates the second signature according to the random number r2.
  • the MDC can calculate the second signature based on the random number r2 and ID2, where ID2 represents the ID of the MDC.
  • hash() represents the hash algorithm.
  • MDC can use a hash algorithm to obtain a hash value based on the random numbers r2 and ID2, for example, called the second hash value.
  • the second device can sign the second hash value according to the second private key to obtain the second hash value. Sign sig2.
  • the MDC sends ID2 and sig2 to the T-Box, and the T-Box receives ID2 and sig2 from the MDC.
  • MDC can send ID2 and sig2 to the gateway, and the gateway forwards ID2 and sig2 to the T-Box.
  • the MDC can also generate a random number r1, and send the random number r1 to the gateway, and the gateway forwards the random number r1 to the T-Box.
  • r1 can be the first random number.
  • T-Box performs signature verification on MDC according to sig2.
  • T-Box can verify sig2 based on ID2, random number r2, and the public key in the MDC device certificate. If the verification is successful, T-Box considers the MDC to be credible and can execute S609. If the verification fails, S609 may not be executed.
  • the T-Box calculates the first signature according to the random number r1.
  • the T-Box can calculate the first signature based on the random number r1 and ID1, where ID1 is the ID of the T-Box.
  • ID1 is the ID of the T-Box.
  • the T-Box sends ID1 and sig1 to the MDC, and the MDC receives ID1 and sig1 from the T-Box.
  • T-Box can send ID1 and sig1 to the gateway, and the gateway forwards ID1 and sig1 to MDC.
  • the MDC performs signature verification on the T-Box according to sig1.
  • MDC can verify sig1 based on the random number r1 and ID1. If MDC verifies sig1 successfully, MDC considers the T-Box to be credible. If MDC verifies sig1 successfully and T-Box verifies sig2 successfully, then MDC and T-Box can establish a secure transmission channel. If the MDC fails to verify the sig1, or the T-Box fails to verify the sig2, or the MDC fails to verify the sig1, and the T-Box fails to verify the sig2, the MDC and the T-Box may not establish a secure transmission channel.
  • the embodiment shown in FIG. 6 describes the authentication process between MDC and T-Box. This embodiment can be considered as an example of the embodiment shown in FIG. 4. In the following, another authentication process is used to illustrate any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 5.
  • the first business is the autonomous driving function.
  • the activation of the automatic driving function generally requires the completion of the following three certification processes:
  • One-way authentication of VCU to MDC After the MDC is started, the MDC can request the VCU to authenticate the MDC. If the VCU fails to pass the MDC authentication, the VCU can send an authentication failure message to the HMI.
  • HMI Two-way authentication between HMI and MDC.
  • the device information of the HMI for example, the identification of the HMI
  • the certificate of the HMI can be sent to the MDC.
  • HMI sends HMI device information and HMI certificate to MDC, if it does not receive MDC feedback information, it can periodically send HMI device information and HMI certificate to MDC, sending cycle time and transmission protocol
  • the sending cycle can be an integer multiple of the message cycle, and if it is Ethernet transmission, the sending cycle can be more flexible and can be customized.
  • the device information of the MDC for example, the ID of the MDC
  • the certificate of the MDC can be sent to the HMI.
  • MDC sends the MDC device information and the MDC certificate to the HMI, if it does not receive the HMI feedback information, it can periodically send the MDC device information and the MDC certificate to the HMI, the sending cycle time and the transmission protocol
  • the sending cycle can be an integer multiple of the message cycle, and if it is Ethernet transmission, the sending cycle can be more flexible and can be customized.
  • the one-way authentication of the MDC to the sensor is a sensor belonging to the same domain as the MDC.
  • the MDC After the MDC receives the identification of the autonomous driving function (that is, the identification of the first business), it can perform one-way authentication for sensors such as on-board millimeter wave radar or navigation equipment.
  • the activation of the automatic driving function may also involve other certification processes.
  • the certification process may be different.
  • autonomous driving functions may also involve authentication between MDC and T-Box.
  • authentication processes only take the above three authentication processes as an example.
  • the first authentication process VCU one-way authentication of the MDC
  • the second authentication process two-way authentication between HMI and MDC
  • the second authentication process can be carried out after receiving the identification of the automatic driving function. It can be understood that the second authentication process can be carried out after the automatic driving function is triggered. For example, if the user clicks the button for starting the automatic driving function, or the user performs an operation for starting the automatic driving function on the human-computer interaction interface, it can be a way to trigger the automatic driving function.
  • the second authentication process can be executed, and if the authentication of the first authentication process fails, the second authentication process does not need to be executed, for example, if the authentication of the first authentication process If it fails, the automatic driving function cannot be activated, and the second authentication process does not need to be performed.
  • the third authentication process MDC one-way authentication of the sensor can be performed. If the authentication of the second authentication process fails, the third authentication process does not need to be executed.
  • the automatic driving function cannot be activated, and the third authentication process does not need to be executed. If the authentication of the third authentication process is successful, the automatic driving function can be used normally. And if the authentication of the third authentication process fails, the automatic driving function cannot be activated.
  • the strategy that can be adopted is not to activate the automatic driving function. The following three embodiments will respectively introduce the above three authentication processes.
  • FIG. 7 is the flow chart of the first authentication process above.
  • the MDC can be regarded as the first device
  • the VCU can be regarded as the second device.
  • the embodiment shown in FIG. 7 can be regarded as an example of the embodiment shown in FIG. 2 and can also be regarded as an example of the embodiment shown in FIG. 3.
  • the MDC sends the ID, ID2 and the equipment certificate 2 of the automatic driving function to the VCU, and the VCU receives the ID, ID2 and the equipment certificate 2 of the automatic driving function from the MDC.
  • ID2 is the ID of the MDC
  • device certificate 2 is the device certificate of the MDC.
  • the first information may include the ID of the automatic driving function, ID2 is the first identification, and the device certificate 2 is the first certificate.
  • the MDC and the VCU can communicate through the gateway, and refer to the network architecture shown in Figure 1. Then the MDC can send the ID, ID2, and device certificate 2 of the autopilot function to the gateway, and the gateway forwards it to the VCU. Alternatively, the MDC and the VCU can communicate directly without forwarding through other devices, and the MDC can directly send the ID, ID2, and device certificate 2 of the autopilot function to the VCU.
  • Figure 7 uses the gateway communication between MDC and VCU as an example.
  • the VCU verifies the legitimacy of ID2 and device certificate 2. If it is determined that ID2 and device certificate 2 are legal, S703 can be executed. And if it is determined that ID2 is illegal, or device certificate 2 is determined to be illegal, or both ID2 and device certificate 2 are determined to be unlawful, then the MDC authentication failure information can be sent to the HMI.
  • the authentication failure information can include error code 1. It can also include the ID of the autopilot function. Among them, verifying the legitimacy of the ID can also be described as verifying the validity of the ID.
  • the VCU sends the ID of the automatic driving function and the random number r to the MDC, and the MDC receives the ID and the random number r of the automatic driving function from the VCU.
  • the random number r may be the first random number.
  • the VCU can send the ID of the autopilot function and the random number r to the gateway, and the gateway will forward it to the MDC.
  • the MDC and the VCU can also communicate directly without forwarding through other devices, and the VCU can directly send the ID of the autopilot function and the random number r to the MDC.
  • the MDC calculates the first signature sig1.
  • the MDC can obtain the first signature based on the random number r and ID2.
  • MDC can use a hash algorithm to obtain a hash value based on the random number r and ID2, which is called the first hash value, for example.
  • MDC can sign the first hash value based on the first private key to obtain the first signature sig1 .
  • the MDC sends the ID, ID2 and sig1 of the automatic driving function to the VCU, and the VCU receives the ID, ID2 and sig1 of the automatic driving function from the MDC.
  • the MDC can send the ID, ID2, and sig1 of the autopilot function to the gateway, and the gateway forwards it to the VCU.
  • the MDC and the VCU can communicate directly without forwarding through other devices, and the MDC can directly send the ID, ID2, and sig1 of the autopilot function to the VCU.
  • the MDC can also send the ID of the autonomous driving function to the VCU, so that the VCU can make it clear that the authentication process corresponds to the authentication performed by the autonomous driving function business.
  • the VCU authenticates the MDC according to sig1. If the authentication is successful, execute S707, if the authentication fails, execute S708.
  • the VCU can verify sig1 according to the random number r and ID2. If the verification passes, the MDC is determined to be credible, and if the verification fails, it is determined that the MDC is not credible.
  • the VCU sends the autopilot function ID and authentication success information to the HMI, and the HMI receives the autopilot function ID and authentication success information from the VCU.
  • the successful authentication information is used to indicate that the VCU has successfully authenticated the MDC.
  • the VCU can send the autopilot function ID and the successful authentication information to the gateway, and the gateway will forward it to the HMI.
  • the MDC and the VCU can communicate directly without forwarding through other devices, and the VCU can directly send the ID of the autopilot function and the successful authentication information to the HMI.
  • the VCU can send the ID of the autonomous driving function to the HMI, so that the HMI can make it clear that the authentication process corresponds to the authentication performed by the autonomous driving function business.
  • the VCU sends the automatic driving function ID and authentication failure information to the HMI, and the HMI receives the automatic driving function ID and authentication failure information from the VCU.
  • the authentication failure information includes, for example, error code 2, which may indicate that the VCU has failed to authenticate the MDC.
  • VCU can perform error logging.
  • the VCU can send the autopilot function ID and authentication failure information to the gateway, and the gateway will forward it to the HMI.
  • the MDC and the VCU can communicate directly without forwarding through other devices, and the VCU can directly send the ID of the autopilot function and the authentication failure information to the HMI.
  • the VCU can send the ID of the autonomous driving function to the HMI, so that the HMI can make it clear that the authentication process corresponds to the authentication performed by the autonomous driving function business.
  • FIG. 8 is a flowchart of the second authentication process above.
  • the MDC can be regarded as the first device
  • the HMI can be regarded as the second device.
  • the embodiment shown in FIG. 8 can be regarded as an example of the embodiment shown in FIG. 4, and can also be regarded as an example of the embodiment shown in FIG. 5.
  • the MDC sends the ID, ID2 and the device certificate 2 of the automatic driving function to the HMI, and the HMI receives the ID, ID2 and the device certificate 2 of the automatic driving function from the MDC.
  • ID2 is the ID of the MDC
  • the device certificate 2 is the device certificate of the MDC.
  • the MDC and HMI can communicate through a gateway, and refer to the network architecture shown in Figure 1. Then the MDC can send the ID, ID2 and device certificate 2 of the autopilot function to the gateway, and the gateway will forward it to the HMI. Alternatively, the MDC and the HMI can communicate directly without forwarding through other devices, and the MDC can directly send the ID, ID2, and device certificate 2 of the autopilot function to the HMI.
  • Figure 8 takes the communication between MDC and HMI through a gateway as an example. Therefore, in the subsequent steps of the embodiment shown in Figure 8, all information that involves the transmission of information between MDC and HMI needs to be forwarded through the gateway. Go into details.
  • HMI verifies the validity of ID2 and verifies whether the device certificate 2 is legal. If ID2 is valid and device certificate 2 is valid, execute S803. Otherwise, HMI can send authentication failure information to MDC.
  • the authentication failure information is, for example, error code 1. In addition, it can also send the ID of the autopilot function to MDC.
  • the HMI sends the ID, ID3 and device certificate 3 of the automatic driving function to the MDC, and the MDC receives the ID, ID3 and device certificate 3 of the automatic driving function from the MDC.
  • ID3 is the ID of the HMI
  • device certificate 3 is the device certificate of the HMI.
  • the MDC verifies the validity of the device ID3 and verifies whether the device certificate 3 is legal. If ID3 is valid and device certificate 3 is valid, execute S805. Otherwise, MDC will not send information to HMI. After authentication is completed, MDC will not activate the autopilot function and perform error recording. If necessary, MDC can send error codes to cloud devices.
  • the MDC sends the ID of the automatic driving function and the random number r1 to the HMI, and the HMI receives the ID and the random number r1 of the automatic driving function from the MDC.
  • the random number r1 may be a second random number.
  • the HMI calculates the second signature.
  • the HMI sends the ID, ID3, sig2, and random number r2 of the automatic driving function to the MDC, and the MDC receives the ID, ID3, sig2, and random number r2 of the automatic driving function from the HMI.
  • the random number r2 may be the first random number.
  • MDC authenticate HMI according to sig2. If the authentication is passed, execute S808. If the authentication fails, the MDC does not send information to the HMI, and the MDC does not activate the automatic driving function. At this time, the authentication is over and the MDC can record the error.
  • the MDC calculates the first signature.
  • r2 represents the exclusive OR of the random numbers r1 and r2, or the sequence obtained by splicing the random number r1 sequence and the random number r2 sequence, for example, the random number r2 sequence is spliced to the end of the random number r1 sequence .
  • MDC sends the ID, ID2 and sig3 of the autopilot function to the HMI, and the HMI receives the ID, ID2 and sig3 of the autopilot function from the MDC.
  • HMI HMI authenticate MDC according to sig3. If the authentication is passed, execute S812. If the authentication fails, the HMI can send authentication failure information to the MDC.
  • the authentication failure information includes error code 2, for example, and can be displayed through the HMI, and the automatic driving function cannot be activated.
  • the HMI sends the ID of the autopilot function to the MDC, and the MDC receives the ID of the autopilot function from the HMI.
  • Figure 9 is the flow chart of the third authentication process above.
  • the sensor can be regarded as the first device, and the MDC can be regarded as the second device.
  • the embodiment shown in FIG. 9 can be regarded as an example of the embodiment shown in FIG. 3.
  • the sensor sends the ID, ID4 and device certificate 4 of the autopilot function to MDC, and the MDC receives the ID, ID4 and device certificate 4 of the autopilot function from the sensor.
  • ID4 is the ID of the sensor
  • device certificate 4 is the device certificate of the sensor.
  • the MDC verifies that the ID4 has a message, and verifies the legitimacy of the device certificate 4. If it is determined that ID4 and device certificate 4 are legal, S903 can be executed. If it is determined that ID4 is illegal, or device certificate 4 is determined to be illegal, or both ID4 and device certificate 4 are determined to be illegal, then the authentication failure information can be sent to the sensor.
  • the authentication failure information can include error code 1, or The ID of the autonomous driving function may be included.
  • error code 1 and the ID of the automatic driving function can also be sent to the HMI.
  • the MDC sends the autopilot function ID and random number r3 to the sensor, and the sensor receives the autopilot function ID and random number r3 from the MDC.
  • the sensor calculates the first signature.
  • the sensor can calculate the first signature sig4 based on the random numbers r3 and ID4.
  • the sensor sends the ID, ID4 and sig4 of the autopilot function to the MDC, and the MDC receives the ID, ID4 and sig4 of the autopilot function from the sensor.
  • MDC authenticate the sensor according to sig4. If the authentication is successful, execute S907, if the authentication fails, execute S908.
  • the MDC sends the ID of the autopilot function and the information of the successful authentication to the HMI and the sensor.
  • the HMI receives the ID of the autopilot function from the VCU and the information of the authentication success
  • the sensor receives the ID of the autopilot function from the VCU.
  • the successful authentication information is used to indicate that the VCU has successfully authenticated the MDC. Among them, the steps of MDC sending information to HMI are not shown in Figure 9.
  • the MDC sends the automatic driving function ID and authentication failure information to the HMI, and the HMI receives the automatic driving function ID and authentication failure information from the VCU.
  • the authentication failure information includes, for example, error code 2, which may indicate that the MDC has failed to authenticate the sensor.
  • MDC can record errors, and the recorded information can also be reported to the cloud device.
  • MDC's automatic driving function is not activated. Among them, the steps of MDC sending information to HMI are not shown in Figure 9.
  • both the first authentication process and the second authentication process described above can be executed without receiving the ID of the autopilot function.
  • the automatic driving function can be disabled.
  • the embodiment shown in FIG. 6 to the embodiment shown in FIG. 9 are all distributed authentication processes. However, the embodiment of the present application also supports the centralized authentication process performed by the gateway. Continue to take the first business is the autonomous driving function as an example.
  • the gateway authenticates HMI, MDC and other equipment.
  • the gateway receives the ID of the automatic driving function from the HMI, and the gateway searches for the equipment that needs to be authenticated and the order of authentication based on the ID of the automatic driving function. For example, according to the ID of the autopilot function, the gateway determines that the devices that need to be authenticated are HMI, VCU, MDC, and sensor.
  • the order of authentication is:
  • the order of 1) and 2) can be exchanged.
  • the automatic driving function cannot be activated.
  • the gateway may issue an instruction to the VCU to indicate that the VCU cannot process the instruction from the MDC.
  • the embodiment shown in FIG. 6 to the embodiment shown in FIG. 9 are introduced by taking the automatic driving function as an example.
  • the following uses the anti-theft activation function as an example.
  • the embodiment shown in FIG. 2 or the embodiment shown in FIG. 3 The examples are introduced.
  • the car owner directly puts on the gear and leaves.
  • the car owner can use the mobile phone virtual key to unlock the car, and Bluetooth will match the mobile phone with the car.
  • the mobile phone application (app) is turned on or close to the car while running in the background , The door is automatically unlocked, and then the car is powered on.
  • the certification process for on-board equipment includes the following three:
  • BDCU body domain control unit
  • VCU performs one-way authentication on BCM, and VCU confirms the legality of the equipment requested by the BCM to power on;
  • VCU performs one-way authentication for devices in the domain, and VCU performs battery management system (BMS) or on-board charger (on-board charge, OBC) and other domain devices (VCU, BMS, OBC, etc.) can belong to the same domain , VCU is a domain controller) for one-way legality verification.
  • BMS battery management system
  • OBC on-board charger
  • VCU, BMS, OBC, etc. can belong to the same domain
  • VCU is a domain controller for one-way legality verification.
  • the vehicle cannot be started; if the fourth certification process and the fifth certification process are both successful, and the sixth certification process is If the VCU fails to OBC authentication, the VCU can record and report an error, but the vehicle can be started.
  • FIG. 10 is a flowchart of the fourth authentication process above.
  • the BCM can be regarded as the second device
  • the PEPS can be regarded as the first device.
  • the embodiment shown in FIG. 10 can be regarded as an example of the embodiment shown in FIG. 3.
  • PEPS sends the ID, ID5 and device certificate 5 of the anti-theft activation function to MDC, and MDC receives the ID, ID5 and device certificate 5 of the anti-theft activation function from PEPS.
  • ID5 is the ID of PEPS
  • device certificate 5 is the device certificate of PEPS.
  • PEPS can be an intra-domain device in the domain where the BCM is located. Therefore, BCM and PEPS can communicate directly without forwarding through other devices.
  • S1002 BCM verifies the validity of ID5, and verifies the legitimacy of device certificate 5. If it is determined that ID5 and device certificate 5 are legal, S1003 can be executed. And if it is determined that ID5 is illegal, or device certificate 5 is determined to be illegal, or both ID5 and device certificate 5 are determined to be neither legal, then the PEPS authentication failure information can be sent to PEPS.
  • the authentication failure information can include error code 1.
  • the ID of the anti-theft activation function can also be included.
  • BCM sends the anti-theft activation function ID and random number r1 to PEPS, and PEPS receives the anti-theft activation function ID and random number r1 from BCM.
  • the random number r1 may be the first random number.
  • PEPS calculates the first signature.
  • PEPS can obtain the first signature based on random numbers r1 and ID5.
  • PEPS can use a hash algorithm to obtain a hash value based on the random numbers r1 and ID5, which is called the first hash value, for example.
  • PEPS can sign the first hash value based on the first private key to obtain the first signature sig1 .
  • S1005 and PEPS send the ID, ID5 and sig1 of the anti-theft activation function to the BCM, and the BCM receives the ID, ID5 and sig1 of the anti-theft activation function from the PEPS.
  • the BCM can verify sig1 based on the random numbers r1 and ID5. If the verification passes, the PEPS is determined to be credible, and if the verification fails, it is determined that the PEPS is not credible.
  • the BCM sends the anti-theft activation function ID and the authentication success information to the PEPS, and the PEPS receives the anti-theft activation function ID and the authentication success information from the BCM.
  • the authentication success information is used to indicate that the BCM has successfully authenticated the PEPS.
  • the BCM sends the anti-theft activation function ID and authentication failure information to the PEPS, and the PEPS receives the anti-theft activation function ID and authentication failure information from the BCM.
  • the authentication failure information includes, for example, error code 2, which may indicate that the BCM has failed to authenticate the PEPS, and the BCM door is in a closed state, and the door cannot be opened.
  • BCM can record errors or issue alarms, and the recorded information can also be reported to cloud devices.
  • FIG. 11 is the flow chart of the fifth authentication process above.
  • the VCU can be regarded as the second device
  • the BCM can be regarded as the first device.
  • the embodiment shown in FIG. 11 can be regarded as an example of the embodiment shown in FIG. 2 and can also be regarded as an example of the embodiment shown in FIG. 3.
  • the BCM sends the ID, ID6 and device certificate 6 of the anti-theft activation function to the VCU, and the VCU receives the ID, ID6 and device certificate 6 of the anti-theft activation function from the BCM.
  • ID6 is the ID of the BCM
  • the device certificate 6 is the device certificate of the BCM.
  • the BCM and the VCU can communicate through the gateway, and refer to the network architecture shown in Figure 1. Then the BCM can send the ID, ID6 and device certificate 6 of the anti-theft activation function to the gateway, and the gateway forwards it to the VCU. Alternatively, the BCM and the VCU can communicate directly without forwarding through other devices, and the BCM can directly send the ID, ID6 and device certificate 6 of the anti-theft activation function to the VCU.
  • Figure 11 takes the communication between the BCM and the VCU through the gateway as an example. Therefore, in the subsequent steps of the embodiment shown in Figure 11, all information that involves the transmission of information between the BCM and the VCU needs to be forwarded through the gateway. Go into details.
  • VCU verifies the validity of ID6, and verifies the legality of device certificate 6. If it is determined that ID6 and device certificate 6 are legal, S1103 can be executed. And if it is determined that ID6 is illegal, or device certificate 6 is determined to be illegal, or both ID6 and device certificate 6 are determined to be illegal, then BCM authentication failure information can be sent to BCM.
  • the authentication failure information can include error code 1.
  • the ID of the anti-theft activation function can also be included.
  • the VCU sends the anti-theft activation function ID and random number r1 to the BCM, and the BCM receives the anti-theft activation function ID and random number r2 from the VCU.
  • the random number r2 may be the first random number.
  • the BCM calculates the first signature.
  • the BCM can obtain the first signature based on the random number r2 and ID6.
  • BCM can use a hash algorithm to obtain a hash value based on the random numbers r2 and ID6, which is called the first hash value, for example.
  • BCM can sign the first hash value based on the first private key to obtain the first signature sig2 .
  • S1105 and BCM send the ID, ID6 and sig2 of the anti-theft start function to the VCU, and the VCU receives the ID, ID6 and sig2 of the anti-theft start function from the BCM.
  • S1106 and VCU authenticate BCM according to sig2. If the authentication is successful, execute S1107, if the authentication fails, execute S1108.
  • the VCU can verify sig2 according to the random numbers r2 and ID6. If the verification passes, the BCM is determined to be credible, and if the verification fails, it is determined that the BCM is not credible.
  • the VCU sends the anti-theft activation function ID and authentication success information to the BCM, and the BCM receives the anti-theft activation function ID and authentication success information from the VCU.
  • the successful authentication information is used to indicate that the VCU has successfully authenticated the BCM.
  • the VCU sends the anti-theft activation function ID and authentication failure information to the BCM, and the BCM receives the anti-theft activation function ID and authentication failure information from the VCU.
  • the authentication failure information includes, for example, error code 2, which may indicate that the VCU has failed to authenticate the BCM.
  • the VCU can record errors, and the recorded information can also be reported to the cloud device.
  • FIG. 12 is a flowchart of the sixth authentication process as above.
  • the VCU can be regarded as the second device
  • the OBC can be regarded as the first device.
  • the embodiment shown in FIG. 12 can be regarded as an example of the embodiment shown in FIG. 3.
  • OBC sends the ID, ID7 and device certificate 7 of the anti-theft startup function to the VCU, and the VCU receives the ID, ID7 and device certificate 7 of the anti-theft startup function from OBC.
  • ID7 is the ID of OBC
  • device certificate 7 is the device certificate of OBC.
  • the OBC can be a device in the domain where the VCU is located, so the VCU and the OBC can communicate directly without forwarding through other devices.
  • S1202 VCU verifies the validity of ID7, and verifies the legitimacy of device certificate 7. If it is determined that ID7 and device certificate 7 are legal, S1203 can be executed. If it is determined that ID7 is illegal, or device certificate 7 is determined to be illegal, or both ID7 and device certificate 7 are determined to be illegal, then it can send OBC authentication failure information to OBC.
  • the authentication failure information can include error code 1.
  • the ID of the anti-theft activation function can also be included.
  • the VCU sends the anti-theft activation function ID and random number r3 to OBC, and the OBC receives the anti-theft activation function ID and random number r3 from the VCU.
  • the random number r3 may be the first random number.
  • the OBC calculates the first signature.
  • OBC can obtain the first signature based on the random number r3 and ID7.
  • OBC can use a hash algorithm to obtain a hash value based on the random numbers r3 and ID7, which is called the first hash value, for example.
  • OBC can sign the first hash value based on the first private key to obtain the first signature sig3 .
  • S1205 and OBC send the ID, ID7 and sig3 of the anti-theft start function to the VCU, and the VCU receives the ID, ID7 and sig3 of the anti-theft start function from OBC.
  • VCU authenticate OBC according to sig3. If the authentication is successful, go to S1207, if the authentication fails, go to S1208.
  • the VCU can verify sig3 based on the random numbers r3 and ID7. If the verification passes, the OBC is determined to be credible, and if the verification fails, it is determined that the OBC is not credible.
  • the VCU sends the anti-theft activation function ID and authentication success information to the OBC, and the OBC receives the anti-theft activation function ID and authentication success information from the VCU.
  • the authentication success information is used to indicate that the VCU has successfully authenticated the OBC.
  • the VCU sends the anti-theft activation function ID and authentication failure information to the OBC, and the OBC receives the anti-theft activation function ID and authentication failure information from the VCU.
  • the authentication failure information includes, for example, error code 2, which may indicate that the VCU has failed to authenticate the OBC.
  • the VCU can record errors, and the recorded information can also be reported to the cloud device.
  • the first device described in the embodiment shown in FIG. 13 may be a device to be authenticated, or a device that fails to be authenticated
  • the second device may be a device other than a gateway and a router, or in addition to having An entity other than the entity with the routing and forwarding function, or the second device may also be a device such as a gateway or a router, or the second device may also be an entity with the routing and forwarding function.
  • the gateway may also refer to a physical device with the function of routing and forwarding equipment.
  • the embodiment shown in FIG. 13 can be considered to be a scenario where the gateway performs centralized authentication.
  • each domain controller can The authentication is performed by the gateway.
  • the embodiment shown in FIG. 13 can also be considered as a distributed authentication scenario.
  • each domain controller can be authenticated by the gateway, or mutually authenticate each other.
  • the second device is a device other than a gateway and a router, it can be considered that the embodiment shown in FIG. 13 is a distributed authentication scenario that does not require a gateway to perform centralized authentication. Because this embodiment is applied to the network architecture shown in FIG. 1 as an example, the first device described below is, for example, the domain controller in the network architecture shown in FIG. 1, and the second device described below is The device is, for example, the T-Box, OBD, or gateway in the network architecture shown in FIG. 1.
  • the second device fails to authenticate the first device.
  • the second device may first receive the first information and the first certificate from the first device, the first information is used to indicate the second device, and the first certificate is the device certificate of the first device.
  • the second device verifies whether the first certificate is correct according to the third certificate of the first device.
  • the second device generates a first random number, and can send the first random number to the first device.
  • the first device may generate a first signature, and send the first signature to the second device, and the second device receives the first signature from the first device.
  • the second device may authenticate the first device according to the first signature, the first random number, and the first identification, where the first identification is the identification of the first device.
  • the third certificate of a device can be an OEM root certificate, or a second-level certificate issued by OEM/CA, or a third-level certificate issued by OEM/CA, or a fourth-level certificate, or a certificate of more levels. And so on, there is no restriction on the level of the certificate.
  • the third certificate of the first device may be a root certificate, or a second-level certificate, or a third-level certificate, or a fourth-level certificate, or more levels of certificates, and so on.
  • the first certificate may not include the subject attribute information of the first certificate, and the first certificate includes one of the following information or any combination of the following multiple types of information, the version information of the first certificate, and the signer information of the first certificate , The subject information of the first certificate, the validity information of the first certificate, or the signature information of the first certificate.
  • the content related to the first certificate may be combined in the embodiment shown in FIG. 13 or may also be used as an embodiment alone.
  • the operation of the first device to send the first certificate to the second device, and the content of the first certificate, etc. can be taken as a separate embodiment.
  • the operation of verifying the first certificate by the second device, and the content of the first certificate, etc. may be taken as a separate embodiment.
  • the second device determines a first execution strategy according to the first service, and the authentication corresponds to the first service.
  • the second device may determine the first execution strategy according to the first service.
  • the second device determines the first execution strategy according to the first service, for example, determines the first execution strategy according to the identity of the first service, because when the second device fails to authenticate the first device, it can be determined that the authentication is related to the first service.
  • the specific determination method may be to determine that the authentication process is related to the identity of the first service, so the second device can determine the first execution strategy according to the identity of the first service.
  • the execution strategy determined by the second device may be different.
  • the first execution strategy includes, for example, the device stops working, or the device stops using part of the functions of the device.
  • the first execution strategy may include that the second device stops working, or the second device stops using part of the functions of the second device.
  • Some of the functions here may be functions related to the first business.
  • the second device is an MDC and the first service is an automatic driving function, so the MDC stops using part of the MDC functions, for example, stops using the functions related to the automatic driving function.
  • the first device is a BMS
  • the second device is a VCU
  • the first service is an ignition function. If the VCU fails to verify the BMS, the first execution strategy determined by the VCU may be to continue to start the ignition function, but the VCU may issue an alarm message.
  • the first device is an MDC
  • the second device is a VCU
  • the first service is an automatic driving function. If the VCU fails to verify the MDC, the first execution strategy determined by the VCU may be not to activate the automatic driving function.
  • the second device sends the first execution strategy to the first device, or the second device executes the first execution strategy.
  • the second device may execute the first execution strategy.
  • the first device is an MDC and the second device is a VCU.
  • the first service is an automatic driving function. If the VCU fails to verify the MDC, the first execution strategy determined by the VCU may be not to execute subsequent messages and instructions sent by the MDC.
  • the second device may send the first execution policy to the first device,
  • the first execution strategy is executed by the first device.
  • the first device is an MDC
  • the second device is a gateway
  • the gateway performs centralized authentication
  • the first service is an automatic driving function. If the gateway fails to verify the MDC, the first execution strategy determined by the gateway may be not to start the automatic driving function. Then the gateway may send the first execution strategy to the MDC to instruct the MDC not to start the automatic driving function. After the MDC receives the first execution strategy, the automatic driving function may not be activated.
  • the second device if the second device fails to authenticate the first device, because the authentication is an authentication process related to the first service, when the second device determines the execution strategy, the determined execution strategy may be the same as that of the first device.
  • a business-related execution strategy in other words, an execution strategy can be determined according to the first business, so that the determined execution strategy is more in line with the needs of the business.
  • FIG. 14 is a schematic block diagram of a communication device 1400 according to an embodiment of the application.
  • the communication device 1400 may be a communication device, or a device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an in-vehicle device.
  • the communication device is the first device 1400, for example.
  • the communication device 1400 includes a processing module 1410 and a transceiver module 1420.
  • the communication device 1400 may be the first device, or may be a chip applied in the first device or other combination devices, components, etc. having the functions of the first device.
  • the transceiver module 1420 may be a transceiver, which may include an antenna and a radio frequency circuit
  • the processing module 1410 may be a processor, such as a baseband processor.
  • the baseband processor may include one or more central Processing unit (central processing unit, CPU).
  • the transceiver module 1420 may be a radio frequency unit, and the processing module 1410 may be a processor, such as a baseband processor.
  • the transceiver module 1420 may be an input/output interface of a chip system (such as a baseband chip), and the processing module may be a processor of the chip system, and may include one or more central processing units.
  • the processing module 1410 may be used to perform all operations other than the transceiving operation performed by the first device in the embodiment shown in FIG. 2, such as S203, and/or other processes used to support the technology described herein.
  • the transceiving module 1420 may be used to perform all the transceiving operations performed by the first device in the embodiment shown in FIG. 2, such as S201, S202, and S204, and/or other processes used to support the technology described herein.
  • the processing module 1410 may be used to perform all operations other than the transceiving operation performed by the first device in the embodiment shown in FIG. 3, such as S303, and/or other processes used to support the technology described herein .
  • the transceiver module 1420 may be used to perform all the transceiver operations performed by the first device in the embodiment shown in FIG. 3, such as S301, S302, and S304, and/or other processes used to support the technology described herein.
  • the processing module 1410 may be used to perform all operations other than the transceiving operations performed by the first device in the embodiment shown in FIG. 4, such as S406 to S408, and/or to support the technology described herein.
  • the transceiver module 1420 may be used to perform all the transceiver operations performed by the first device in the embodiment shown in FIG. 4, such as S401, S402, S403, S405, and S409, and/or other technologies used to support the technology described herein. process.
  • the processing module 1410 may be used to perform all operations other than the transceiving operations performed by the first device in the embodiment shown in FIG. 5, such as S506 to S508, and/or to support the technology described herein.
  • the transceiving module 1420 can be used to perform all the transceiving operations performed by the first device in the embodiment shown in FIG. 5, such as S501, S502, S503, S505, and S509, and/or other technologies used to support the technology described herein. process.
  • the processing module 1410 may be used to perform all operations performed by the T-Box in the embodiment shown in FIG. 6 except for the receiving and sending operations, such as S604, S608, and S609, and/or to support the operations described herein.
  • Other processes of technology can be used to perform all the transceiver operations performed by the T-Box in the embodiment shown in FIG. 6, such as S601, S603, S605, S607, and S610, and/or other technologies used to support the technology described herein. process.
  • the processing module 1410 may be used to perform all operations other than the transceiving operation performed by the MDC in the embodiment shown in FIG. 7, such as S704, and/or other processes used to support the technology described herein.
  • the transceiver module 1420 may be used to perform all the transceiver operations performed by the MDC in the embodiment shown in FIG. 7, such as S701, S703, and S705, and/or other processes used to support the technology described herein.
  • the processing module 1410 may be used to perform all operations performed by the MDC in the embodiment shown in FIG. 8 except for the transceiving operations, such as S804, S808, and S809, and/or for supporting the technology described herein.
  • the transceiver module 1420 can be used to perform all the transceiver operations performed by the MDC in the embodiment shown in FIG. 8, such as S801, S803, S805, S807, S810, and S812, and/or other technologies used to support the technology described herein. process.
  • the processing module 1410 may be used to perform all operations other than the transceiving operation performed by the sensor in the embodiment shown in FIG. 9, such as S904, and/or other processes used to support the technology described herein.
  • the transceiver module 1420 may be used to perform all the transceiver operations performed by the sensor in the embodiment shown in FIG. 9, such as S901, S903, S905, S907, and S908, and/or other processes used to support the technology described herein.
  • the processing module 1410 may be used to perform all operations other than the transceiving operation performed by the PEPS in the embodiment shown in FIG. 10, such as S1004, and/or other processes used to support the technology described herein.
  • the transceiver module 1420 may be used to perform all the transceiver operations performed by the PEPS in the embodiment shown in FIG. 10, such as S1001, S1003, S1005, S1007, and S1008, and/or other processes for supporting the technology described herein.
  • the processing module 1410 may be used to perform all operations other than the transceiving operation performed by the BCM in the embodiment shown in FIG. 11, such as S1104, and/or other processes used to support the technology described herein.
  • the transceiver module 1420 may be used to perform all the transceiver operations performed by the BCM in the embodiment shown in FIG. 11, such as S1101, S1103, S1105, S1107, and S1108, and/or other processes for supporting the technology described herein.
  • the processing module 1410 may be used to perform all operations other than the transceiving operation performed by the OBC in the embodiment shown in FIG. 12, such as S1204, and/or other processes used to support the technology described herein.
  • the transceiver module 1420 may be used to perform all the transceiver operations performed by the OBC in the embodiment shown in FIG. 12, such as S1201, S1203, S1205, S1207, and S1208, and/or other processes for supporting the technology described herein.
  • the transceiver module 1420 may be a functional module that can complete both sending operations and receiving operations.
  • the transceiver module 1420 may be used to execute the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12 In any embodiment, all the sending and receiving operations performed by the first device. For example, when the sending operation is performed, the transceiver module 1420 can be considered as the sending module, and when the receiving operation is performed, the transceiver module 1420 can be considered as the receiving module.
  • the transceiver module 1420 can also be a collective term for two functional modules, the two functional modules are respectively a sending module and a receiving module, the sending module is used to complete the sending operation, for example, the sending module can be used to perform as shown in Figure 2
  • the receiving module is used to complete the receiving operation.
  • the receiving module may be used to perform the embodiment shown in FIG. 2 To all the receiving operations performed by the first device in any of the embodiments shown in FIG. 12.
  • the transceiver module 1420 is configured to send first information and a first certificate to the second device, the first information is used to indicate the second device, and the first certificate is the device certificate of the communication device 1400;
  • the transceiver module 1420 is further configured to receive the first random number from the second device;
  • the processing module 1410 is configured to use the first private key to obtain a first signature according to the first random number and the first identifier, where the first identifier is the identifier of the communication device 1400;
  • the transceiver module 1420 is further configured to send the first signature to the second device, and the first signature is used to authenticate the communication device 1400.
  • the first information includes an identifier of the first service.
  • the processing module 1410 is also used to generate a second random number
  • the transceiver module 1420 is further configured to send the second random number to the second device.
  • the transceiver module 1420 is further configured to receive a second signature and a second identifier from the second device, where the second identifier is the identifier of the second device;
  • the processing module 1410 is further configured to authenticate the second device according to the second signature, the second random number, and the second identifier.
  • the processing module 1410 is configured to authenticate the second device according to the second signature, the second random number, and the second identifier in the following manner:
  • the second public key to verify the second signature, the second random number, and the second identifier, and obtain the returned result.
  • the returned result indicates that the verification is passed, it is determined to The authentication of the second device is successful; otherwise, when the returned result indicates that the signature verification fails, it is determined that the authentication of the second device has failed.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • the transceiver module 1420 is also used to receive instruction information from the second device, where the instruction information is used to indicate that the authentication of the communication device 1400 fails, or is used to instruct the communication device 1400 to stop working or stop using parts of the communication device 1400 Features;
  • the processing module 1410 is also used to stop the communication device 1400 from working or to stop using part of the functions of the communication device 1400.
  • processing module 1410 in the embodiment of the present application may be implemented by a processor or a processor-related circuit component
  • transceiver module 1420 may be implemented by a transceiver or a transceiver-related circuit component.
  • an embodiment of the present application also provides a communication device 1500.
  • the communication apparatus 1500 is, for example, the first device 1500.
  • the communication apparatus 1500 may be a communication device, such as a terminal device, or may also be a chip system or the like.
  • the communication device 1500 includes a processor 1510.
  • a memory 1520 may also be included.
  • a transceiver 1530 may also be included.
  • the memory 1520 stores computer instructions or programs, and the processor 1510 can execute the computer instructions or programs stored in the memory 1520.
  • the processor 1510 When the computer instructions or programs stored in the memory 1520 are executed, the processor 1510 is used to perform the operations performed by the processing module 1410 in the foregoing embodiment, and the transceiver 1530 is used to perform the operations performed by the transceiver module 1420 in the foregoing embodiment.
  • the communication device 1500 may not include the memory 1520.
  • the memory is located outside the communication device 1500.
  • the processor 1510 When the computer instructions or programs stored in the external memory are executed, the processor 1510 is used to execute the processing performed by the processing module 1410 in the foregoing embodiment. Operation, the transceiver 1530 is used to perform the operations performed by the transceiver module 1420 in the foregoing embodiment.
  • the transceiver 1530 may be a functional unit that can complete both sending and receiving operations.
  • the transceiver 1530 may be used to perform the steps in the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12 In any embodiment, all the sending and receiving operations performed by the first device.
  • the transceiver 1530 can be considered as a transmitter, and when the receiving operation is performed, the transceiver 1530 can be considered as a receiver.
  • the transceiver 1530 can also be a collective term for two functional units, the two functional units are respectively a transmitter and a receiver, the transmitter is used to complete the transmission operation, for example, the transmitter can be used to perform the implementation shown in Figure 2
  • the receiver is used to complete the receiving operation.
  • the receiver can be used to perform the embodiments shown in FIG. 2 to FIG. All the receiving operations performed by the first device in any of the embodiments shown in 12.
  • the transceiver 1530 can also be implemented through a communication interface of the chip system, and the communication interface is connected to a radio frequency transceiving component in a communication device to implement information transmission and reception through the radio frequency transceiving component.
  • the communication interface can be a functional unit that can complete both sending and receiving operations.
  • the communication interface can be used to execute any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG.
  • the communication interface can be considered as a sending interface, and when performing a receiving operation, the communication interface can be considered as a receiving interface; or, the communication interface It can also be a collective term for two functional units.
  • the two functional units are respectively a sending interface and a receiving interface.
  • the sending interface is used to complete the sending operation.
  • the sending interface can be used to execute the embodiment shown in FIG. 2 to the one shown in FIG. 12
  • the receiving interface is used to complete the receiving operation, for example, the receiving interface can be used to perform the embodiment shown in FIG. 2 to the implementation shown in FIG. 12 All receiving operations performed by the first device in any of the embodiments in the examples.
  • the communication device 1400 or the communication device 1500 can implement the function of the first device in any one of the embodiments shown in FIG. 2 to the embodiment shown in FIG. 12, and the communication device The operation and/or function of each module in the 1400 or the communication device 1500 is to implement the corresponding process in any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12. For the sake of brevity, it is not here. Go into details again.
  • FIG. 16 is a schematic block diagram of a communication device 1600 according to an embodiment of the application.
  • the communication device 1600 may be a communication device, or a device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an in-vehicle device.
  • the communication device is the second device 1600, for example.
  • the communication device 1600 includes a processing module 1610 and a transceiver module 1620.
  • the communication apparatus 1600 may be a second device, or may be a chip applied in the second device, or other combination devices, components, etc. having the functions of the second device.
  • the transceiver module 1620 may be a transceiver, which may include an antenna and a radio frequency circuit, etc.
  • the processing module 1610 may be a processor, such as a baseband processor.
  • the baseband processor may include one or more CPUs. .
  • the transceiver module 1620 may be a radio frequency unit, and the processing module 1610 may be a processor, such as a baseband processor.
  • the transceiver module 1620 may be an input/output interface of a chip system (such as a baseband chip), and the processing module may be a processor of the chip system, and may include one or more central processing units.
  • the processing module 1610 can be used to perform all the operations performed by the second device in the embodiment shown in FIG. 2 except for the receiving and sending operations, such as S205 and S206, and/or for supporting the technology described herein. Other processes.
  • the transceiving module 1620 may be used to perform all the transceiving operations performed by the second device in the embodiment shown in FIG. 2, such as S201, S202, and S204, and/or other processes used to support the technology described herein.
  • the processing module 1610 may be used to perform all operations other than the transceiving operations performed by the second device in the embodiment shown in FIG. 3, such as S305 and S306, and/or to support the technology described herein.
  • the transceiver module 1620 may be used to perform all the transceiver operations performed by the second device in the embodiment shown in FIG. 3, such as S301, S302, and S304, and/or other processes used to support the technology described herein.
  • the processing module 1610 may be used to perform all operations other than the transceiving operations performed by the second device in the embodiment shown in FIG. 4, such as S404, S410, and S411, and/or to support the operations described herein.
  • Other processes of technology can be used to perform all the transceiver operations performed by the second device in the embodiment shown in FIG. 4, such as S401, S402, S403, S405, and S409, and/or other technologies used to support the technology described herein. process.
  • the processing module 1610 may be used to perform all operations other than the transceiving operations performed by the second device in the embodiment shown in FIG. 5, such as S504, S510, and S511, and/or to support the operations described herein.
  • Other processes of technology can be used to perform all the transceiver operations performed by the second device in the embodiment shown in FIG. 5, such as S501, S502, S503, S505, and S509, and/or other technologies used to support the technology described herein. process.
  • the processing module 1610 may be used to perform all operations performed by the MDC in the embodiment shown in FIG. 6 except for the transceiving operations, such as S602, S606, and S611, and/or for supporting the technology described herein Other processes.
  • the transceiver module 1620 may be used to perform all the transceiver operations performed by the MDC in the embodiment shown in FIG. 6, such as S601, S603, S605, S607, and S610, and/or other processes for supporting the technology described herein.
  • the processing module 1610 may be used to perform all operations other than the transceiving operations performed by the VCU in the embodiment shown in FIG. 7, such as S702 and S706, and/or other processes used to support the technology described herein .
  • the transceiver module 1620 may be used to perform all the transceiver operations performed by the VCU in the embodiment shown in FIG. 7, such as S701, S703, and S705, and/or other processes used to support the technology described herein.
  • the processing module 1610 may be used to perform all operations other than the transceiving operations performed by the HMI in the embodiment shown in FIG. 8, such as S802, S806, and S811, and/or for supporting the technology described herein.
  • the transceiver module 1620 can be used to perform all the transceiver operations performed by the HMI in the embodiment shown in FIG. 8, such as S801, S803, S805, S807, S810, and S812, and/or other technologies used to support the technology described herein. process.
  • the processing module 1610 may be used to perform all operations other than the transceiving operations performed by the MDC in the embodiment shown in FIG. 9, such as S902 and S906, and/or other processes used to support the technology described herein .
  • the transceiver module 1620 may be used to perform all the transceiver operations performed by the MDC in the embodiment shown in FIG. 9, such as S901, S903, S905, S907, and S908, and/or other processes used to support the technology described herein.
  • the processing module 1610 may be used to perform all operations performed by the BCM in the embodiment shown in FIG. 10 except for the transceiving operations, such as S1002 and S1006, and/or other processes used to support the technology described herein .
  • the transceiver module 1620 may be used to perform all the transceiver operations performed by the BCM in the embodiment shown in FIG. 10, such as S1001, S1003, S1005, S1007, and S1008, and/or other processes for supporting the technology described herein.
  • the processing module 1610 may be used to perform all operations performed by the VCU in the embodiment shown in FIG. 11 except for the transceiving operations, such as S1102 and S1106, and/or other processes used to support the technology described herein .
  • the transceiver module 1620 may be used to perform all the transceiver operations performed by the VCU in the embodiment shown in FIG. 11, such as S1101, S1103, S1105, S1107, and S1108, and/or other processes for supporting the technology described herein.
  • the processing module 1610 may be used to perform all operations performed by the VCU in the embodiment shown in FIG. 12 except for the transceiving operations, such as S1202 and S1206, and/or other processes used to support the technology described herein .
  • the transceiver module 1620 may be used to perform all the transceiver operations performed by the VCU in the embodiment shown in FIG. 12, such as S1201, S1203, S1205, S1207, and S1208, and/or other processes for supporting the technology described herein.
  • the transceiver module 1620 may be a functional module that can perform both sending operations and receiving operations.
  • the transceiver module 1620 may be used to perform steps from the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12 In any embodiment, all the sending and receiving operations performed by the second device.
  • the transceiver module 1620 when the sending operation is performed, the transceiver module 1620 can be considered as the sending module, and when the receiving operation is performed, the transceiver module 1620 can be considered as the receiving module.
  • the transceiver module 1620 can also be a collective term for two functional modules, the two functional modules are the sending module and the receiving module, the sending module is used to complete the sending operation, for example, the sending module can be used to perform the For all the sending operations performed by the second device in any one of the embodiments to the embodiment shown in FIG. 12, the receiving module is used to complete the receiving operation.
  • the receiving module may be used to perform the embodiment shown in FIG. 2 To all the receiving operations performed by the second device in any of the embodiments shown in FIG. 12.
  • the transceiver module 1620 is configured to receive first information and a first certificate from a first device, the first information is used to indicate the communication device 1600, and the first certificate is the device certificate of the first device;
  • the processing module 1610 is configured to verify whether the first certificate is correct according to the root certificate or the secondary certificate of the first device;
  • the processing module 1610 is further configured to generate a first random number when the first certificate is correct;
  • the transceiver module 1620 is further configured to send the first random number to the first device;
  • the transceiver module 1620 is further configured to receive the first signature from the first device;
  • the processing module 1610 is further configured to authenticate the first device according to the first signature, the first random number, and a first identifier, where the first identifier is an identifier of the first device.
  • the first information includes an identifier of the first service.
  • the processing module 1610 is configured to authenticate the first device according to the first signature, the first random number, and the first identifier in the following manner:
  • the first public key to verify the first signature, the first random number, and the first identifier, and obtain the returned result.
  • the returned result indicates that the verification is passed, it is determined that the The authentication of the first device is successful; otherwise, when the returned result indicates that the signature verification fails, it is determined that the authentication of the first device has failed.
  • the transceiver module 1620 is further configured to receive a second random number from the first device
  • the processing module 1610 is further configured to: when the first device is authenticated, use a second private key to generate a second signature according to the second random number and the second identifier;
  • the transceiver module 1620 is further configured to send the second signature and second identifier to the first device, the second signature is used to authenticate the communication device 1600, and the second identifier is the identifier of the communication device 1600 .
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • the transceiver module 1620 is further configured to send instruction information to the first device when the processing module 1610 fails to authenticate the first device, where the instruction information is used to indicate that the authentication of the first device fails, or To instruct the first device to stop working or to stop using part of the functions of the first device; or,
  • the processing module 1610 is further configured to stop the communication device 1600 or stop using part of the functions of the communication device 1600 when the authentication of the first device fails.
  • processing module 1610 in the embodiment of the present application may be implemented by a processor or processor-related circuit components
  • transceiver module 1620 may be implemented by a transceiver or transceiver-related circuit components.
  • an embodiment of the present application also provides a communication device 1700.
  • the communication device 1700 is the second device 1700, for example.
  • the communication apparatus 1700 may be a communication device, such as a terminal device, or may also be a chip system or the like.
  • the communication device 1700 includes a processor 1710.
  • a memory 1720 may also be included.
  • a transceiver 1730 may also be included.
  • the memory 1720 stores computer instructions or programs, and the processor 1710 can execute the computer instructions or programs stored in the memory 1720.
  • the processor 1710 When the computer instructions or programs stored in the memory 1720 are executed, the processor 1710 is used to perform the operations performed by the processing module 1610 in the foregoing embodiment, and the transceiver 1730 is used to perform the operations performed by the transceiver module 1620 in the foregoing embodiment.
  • the communication device 1700 may not include the memory 1720.
  • the memory is located outside the communication device 1700.
  • the processor 1710 When the computer instructions or programs stored in the external memory are executed, the processor 1710 is used to execute the processing performed by the processing module 1610 in the foregoing embodiment. Operation, the transceiver 1730 is used to perform the operations performed by the transceiver module 1620 in the foregoing embodiment.
  • the transceiver 1730 may be a functional unit that can complete both sending and receiving operations.
  • the transceiver 1730 may be used to perform the steps in the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12 In any embodiment, all the sending operations and receiving operations performed by the second device.
  • the transceiver 1730 when performing a sending operation, can be considered as a transmitter, and when performing a receiving operation, the transceiver 1730 can be considered as a receiver.
  • the transceiver 1730 can also be a collective term for two functional units, the two functional units are the transmitter and the receiver, the transmitter is used to complete the transmission operation, for example, the transmitter can be used to perform the implementation shown in Figure 2
  • the receiver is used to complete the receiving operation.
  • the receiver can be used to perform the embodiments shown in FIG. 2 to FIG. All receiving operations performed by the second device in any of the embodiments shown in 12.
  • the transceiver 1730 can also be implemented through a communication interface of the chip system, and the communication interface is connected to a radio frequency transceiving component in a communication device to implement information transmission and reception through the radio frequency transceiving component.
  • the communication interface can be a functional unit that can complete both sending and receiving operations.
  • the communication interface can be used to execute any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12 All the sending operations and receiving operations performed by the second device in the second device.
  • the communication interface when performing a sending operation, can be considered as a sending interface, and when performing a receiving operation, the communication interface can be considered as a receiving interface; or, the communication interface It can also be a collective term for two functional units.
  • the two functional units are respectively a sending interface and a receiving interface.
  • the sending interface is used to complete the sending operation.
  • the sending interface can be used to execute the embodiment shown in FIG. 2 to the one shown in FIG. 12
  • the receiving interface is used to complete all the sending operations performed by the second device.
  • the receiving interface can be used to perform the embodiment shown in FIG. 2 to the implementation shown in FIG. 12 All receiving operations performed by the second device in any of the embodiments in the examples.
  • the communication device 1600 or the communication device 1700 can implement the function of the second device in any one of the embodiments shown in FIG. 2 to the embodiment shown in FIG. 12, and the communication device The operations and/or functions of each module in the 1600 or the communication device 1700 are to implement the corresponding process in any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12. For the sake of brevity, it is not here. Go into details again.
  • FIG. 18 is a schematic block diagram of a communication device 1800 according to an embodiment of the application.
  • the communication device 1800 may be a communication device, or a device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an in-vehicle device.
  • the communication device is the third device 1800, for example.
  • the communication device 1800 includes a processing module 1810 and a transceiver module 1820.
  • the communication apparatus 1800 may be a third device, or may be a chip applied in the third device, or other combination devices, components, etc. having the functions of the third device.
  • the transceiver module 1820 may be a transceiver, which may include an antenna and a radio frequency circuit, etc.
  • the processing module 1810 may be a processor, such as a baseband processor, which may include one or more CPUs. .
  • the transceiver module 1820 may be a radio frequency unit, and the processing module 1810 may be a processor, such as a baseband processor.
  • the transceiver module 1820 may be an input/output interface of a chip system (such as a baseband chip), and the processing module may be a processor of the chip system, and may include one or more central processing units.
  • the processing module 1810 can be used to perform all operations performed by the third device in the embodiment shown in FIG. 2 except for receiving and sending operations, such as querying the operation of the second device based on the first information, or based on the first information Perform filtering operations, and/or other processes used to support the techniques described herein.
  • the transceiving module 1820 may be used to perform all the transceiving operations performed by the third device in the embodiment shown in FIG. 2, such as S201, S202, and S204, and/or other processes used to support the technology described herein.
  • the processing module 1810 may be used to perform all operations performed by the third device in the embodiment shown in FIG. 4 except for the transceiving operation, such as querying the operation of the second device based on the first information, or based on the first information Perform filtering operations, and/or other processes used to support the techniques described herein.
  • the transceiver module 1820 can be used to perform all the transceiver operations performed by the third device in the embodiment shown in FIG. 4, such as S401, S402, S403, S405, and S409, and/or other technologies used to support the technology described herein. process.
  • the processing module 1810 may be used to perform all operations performed by the gateway in the embodiment shown in FIG. 6 except for the sending and receiving operations, such as querying the second device based on the first information, or filtering based on the first information And/or other processes used to support the techniques described herein.
  • the transceiver module 1820 may be used to perform all the transceiver operations performed by the gateway in the embodiment shown in FIG. 6, such as S601, S603, S605, S607, and S610, and/or other processes used to support the technology described herein.
  • the processing module 1810 may be used to perform all operations performed by the gateway in the embodiment shown in FIG. 7 except for the sending and receiving operations, such as querying the second device based on the first information, or filtering based on the first information And/or other processes used to support the techniques described herein.
  • the transceiver module 1820 may be used to perform all the transceiver operations performed by the gateway in the embodiment shown in FIG. 7, such as S701, S703, and S705, and/or other processes used to support the technology described herein.
  • the processing module 1810 may be used to perform all operations performed by the gateway in the embodiment shown in FIG. 8 except for the sending and receiving operations, such as querying the second device based on the first information, or filtering based on the first information And/or other processes used to support the techniques described herein.
  • the transceiver module 1820 can be used to perform all the transceiver operations performed by the gateway in the embodiment shown in FIG. 8, such as S801, S803, S805, S807, S810, and S812, and/or other technologies used to support the technology described herein. process.
  • the processing module 1810 may be used to perform all operations performed by the gateway in the embodiment shown in FIG. 11 except for the sending and receiving operations, such as querying the second device based on the first information, or filtering based on the first information And/or other processes used to support the techniques described herein.
  • the transceiver module 1820 may be used to perform all the transceiver operations performed by the gateway in the embodiment shown in FIG. 11, such as S1101, S1103, S1105, S1107, and S1108, and/or other processes for supporting the technology described herein.
  • the transceiver module 1820 may be a functional module that can perform both sending operations and receiving operations.
  • the transceiver module 1820 may be used to perform steps from the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12 In any embodiment, all the sending and receiving operations performed by the third device.
  • the transceiver module 1820 when the sending operation is performed, the transceiver module 1820 can be considered as the sending module, and when the receiving operation is performed, the transceiver module 1820 can be considered as the receiving module.
  • the transceiver module 1820 can also be a collective term for two functional modules, the two functional modules are respectively a sending module and a receiving module, the sending module is used to complete the sending operation, for example, the sending module can be used to perform as shown in Figure 2
  • the receiving module is used to complete the receiving operation.
  • the receiving module may be used to perform the embodiment shown in FIG. 2 To all the receiving operations performed by the third device in any of the embodiments shown in FIG. 12.
  • the transceiver module 1820 is configured to receive first information and a first certificate from a first device, where the first information is used to indicate a second device, and the first certificate is a device certificate of the first device;
  • the processing module 1810 is configured to search for the corresponding second device according to the first information
  • the transceiver module 1820 is further configured to send the first information and the first certificate to the second device, where the first certificate is used by the second device to authenticate the first device.
  • the first information includes an identifier of the first service.
  • the first information is an identifier of the first service
  • the processing module 1810 is configured to find the corresponding second device according to the first information in the following manner:
  • search for the second device related to the first service According to the identifier of the first service, search for the second device related to the first service.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • processing module 1810 in the embodiment of the present application may be implemented by a processor or a processor-related circuit component
  • transceiver module 1820 may be implemented by a transceiver or a transceiver-related circuit component.
  • an embodiment of the present application also provides a communication device 1900.
  • the communication device 1900 is a third device 1900, for example.
  • the communication apparatus 1900 may be a communication device, such as a terminal device, or may also be a chip system or the like.
  • the communication device 1900 includes a processor 1910.
  • a memory 1920 may also be included.
  • a transceiver 1930 may also be included.
  • the memory 1920 stores computer instructions or programs, and the processor 1910 can execute the computer instructions or programs stored in the memory 1920.
  • the processor 1910 When the computer instructions or programs stored in the memory 1920 are executed, the processor 1910 is configured to execute the operations performed by the processing module 1810 in the foregoing embodiment, and the transceiver 1930 is configured to execute the operations performed by the transceiver module 1820 in the foregoing embodiment.
  • the communication device 1900 may not include the memory 1920.
  • the memory is located outside the communication device 1900.
  • the processor 1910 When the computer instructions or programs stored in the external memory are executed, the processor 1910 is used to execute the processing performed by the processing module 1810 in the foregoing embodiment. Operation, the transceiver 1930 is configured to perform the operations performed by the transceiver module 1820 in the foregoing embodiment.
  • the transceiver 1930 may be a functional unit, which can complete both sending and receiving operations.
  • the transceiver 1930 may be used to perform the steps in the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12 All the sending and receiving operations performed by the third device in any of the embodiments.
  • the transceiver 1930 when the sending operation is performed, the transceiver 1930 can be considered as a transmitter, and when the receiving operation is performed, the transceiver 1930 can be considered as a receiver.
  • the transceiver 1930 can also be a collective term for two functional units, the two functional units are the transmitter and the receiver, the transmitter is used to complete the transmission operation, for example, the transmitter can be used to perform the implementation shown in Figure 2 Example to all the sending operations performed by the third device in any of the embodiments shown in FIG. 12, the receiver is used to complete the receiving operation, for example, the receiver can be used to perform the embodiments shown in FIG. 2 to FIG. All the receiving operations performed by the third device in any of the embodiments shown in 12.
  • the transceiver 1930 can also be implemented through a communication interface of the chip system, and the communication interface is connected to a radio frequency transceiver component in the communication device to implement information transmission and reception through the radio frequency transceiver component.
  • the communication interface can be a functional unit that can complete both sending and receiving operations.
  • the communication interface can be used to execute any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12 All sending operations and receiving operations performed by the third device in the third device.
  • the communication interface when performing a sending operation, can be considered as a sending interface, and when performing a receiving operation, the communication interface can be considered as a receiving interface; or, a communication interface It can also be a collective term for two functional units.
  • the two functional units are respectively a sending interface and a receiving interface.
  • the sending interface is used to complete the sending operation.
  • the sending interface can be used to execute the embodiment shown in FIG. 2 to the one shown in FIG. 12
  • the receiving interface is used to complete all the sending operations performed by the third device.
  • the receiving interface can be used to perform the embodiment shown in FIG. 2 to the implementation shown in FIG. 12 All the receiving operations performed by the third device in any of the embodiments in the examples.
  • the communication device 1800 or the communication device 1900 can implement the function of the third device in any one of the embodiments shown in FIG. 2 to the embodiment shown in FIG. 12, and the communication device The operation and/or function of each module in the 1800 or the communication device 1900 is to implement the corresponding process in any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12, and is not here for brevity. Go into details again.
  • FIG. 20 is a schematic block diagram of a communication device 2000 according to an embodiment of the application.
  • the communication device 2000 may be a communication device, or a device capable of supporting the communication device to implement the functions required by the method, such as a chip system.
  • the communication device is an in-vehicle device.
  • the communication device is the second device 2000, for example.
  • the communication device 2000 includes a processing module 2010 and a transceiver module 2020.
  • the communication apparatus 2000 may be a second device, or may be a chip applied in the second device, or other combination devices, components, etc. that have the functions of the second device described above.
  • the transceiver module 2020 may be a transceiver, which may include an antenna and a radio frequency circuit, etc.
  • the processing module 2010 may be a processor, such as a baseband processor, which may include one or more CPUs. .
  • the transceiver module 2020 may be a radio frequency unit, and the processing module 2010 may be a processor, such as a baseband processor.
  • the transceiver module 2020 may be an input/output interface of a chip system (such as a baseband chip), and the processing module may be a processor of the chip system, and may include one or more central processing units.
  • the processing module 2010 may be used to perform all the operations performed by the second device in the embodiment shown in FIG. 13 except for receiving and sending operations, such as S1301 to S1303, and/or for supporting the technology described herein. Other processes.
  • the transceiving module 2020 may be used to perform all the transceiving operations performed by the second device in the embodiment shown in FIG. 13, such as S1303, and/or other processes used to support the technology described herein.
  • the transceiver module 2020 may be a functional module that can complete both sending operations and receiving operations.
  • the transceiver module 2020 may be used to perform all the transmissions performed by the second device in the embodiment shown in FIG. 13 Operation and receiving operations.
  • the transceiver module 2020 when performing a sending operation, can be considered as a sending module, and when performing a receiving operation, the transceiver module 2020 can be considered as a receiving module; alternatively, the transceiver module 2020 can also be two functional modules.
  • the two functional modules are respectively a sending module and a receiving module.
  • the sending module is used to complete the sending operation.
  • the sending module can be used to perform all the sending operations performed by the second device in the embodiment shown in FIG. 13
  • the receiving module is used to complete receiving operations.
  • the receiving module may be used to perform all receiving operations performed by the second device in any of the embodiments shown in FIG. 13.
  • the processing module 2010 is configured to fail the authentication of the first device
  • the processing module 2010 is further configured to determine a first execution strategy according to the first service, and the authentication corresponds to the first service;
  • the transceiver module 2020 is configured to send the first execution strategy to the first device, or the processing module is further configured to execute the first execution strategy.
  • the first execution strategy includes that the device stops working, or the device stops using part of the functions of the device.
  • the transceiver module 2020 is further configured to receive first information and a first certificate from the first device, the first information is used to indicate the second device, and the first certificate is the device of the first device certificate;
  • the processing module 2010 is further configured to verify whether the first certificate is correct according to the third certificate of the first device;
  • the processing module 2010 is further configured to generate a first random number when the first certificate is correct;
  • the transceiver module is further configured to send the first random number to the first device
  • the transceiver module 2020 is further configured to receive the first signature from the first device
  • the processing module 2010 is further configured to authenticate the first device according to the first signature, the first random number, and a first identifier, where the first identifier is an identifier of the first device.
  • the first certificate does not include subject attribute information of the first certificate.
  • the first certificate includes one of the following information or any combination of the following multiple types of information:
  • the validity information of the first certificate or,
  • processing module 2010 in the embodiments of the present application may be implemented by a processor or processor-related circuit components
  • transceiver module 2020 may be implemented by a transceiver or transceiver-related circuit components.
  • an embodiment of the present application also provides a communication device 2100.
  • the communication apparatus 2100 is the second device 2100, for example.
  • the communication apparatus 2100 may be a communication device, such as a terminal device, or may also be a chip system or the like.
  • the communication device 2100 includes a processor 2110.
  • a memory 2120 may also be included.
  • a transceiver 2130 may also be included.
  • the memory 2120 stores computer instructions or programs, and the processor 2110 can execute the computer instructions or programs stored in the memory 2120.
  • the processor 2110 When the computer instructions or programs stored in the memory 2120 are executed, the processor 2110 is configured to execute the operations performed by the processing module 2010 in the foregoing embodiment, and the transceiver 2130 is configured to execute the operations performed by the transceiver module 2020 in the foregoing embodiment.
  • the communication device 2100 may not include the memory 2120.
  • the memory is located outside the communication device 2100.
  • the processor 2110 When the computer instructions or programs stored in the external memory are executed, the processor 2110 is used to execute the processing performed by the processing module 2010 in the foregoing embodiment. Operation, the transceiver 2130 is used to perform the operations performed by the transceiver module 2020 in the foregoing embodiment.
  • the transceiver 2130 may be a functional unit that can perform both sending operations and receiving operations.
  • the transceiver 2130 may be used to perform all the transmissions performed by the second device in the embodiment shown in FIG. 13 Operation and receiving operations.
  • the transceiver 2130 when performing a sending operation, can be considered as a transmitter, and when performing a receiving operation, the transceiver 2130 can be considered as a receiver; or, the transceiver 2130 can also be two functional units.
  • the two functional units are the transmitter and the receiver respectively.
  • the transmitter is used to complete the transmission operation.
  • the transmitter can be used to perform all the transmission operations performed by the second device in the embodiment shown in FIG.
  • the receiver is used to complete the receiving operation.
  • the receiver may be used to perform all the receiving operations performed by the second device in any of the embodiments shown in FIG. 13.
  • the transceiver 2130 can also be implemented through a communication interface of the chip system, which is connected to a radio frequency transceiver component in a communication device to implement information transmission and reception through the radio frequency transceiver component.
  • the communication interface can be a functional unit that can complete both sending operations and receiving operations.
  • the communication interface can be used to perform the operations performed by the second device in any of the embodiments shown in FIG. 13 All sending operations and receiving operations.
  • the communication interface can be considered as a sending interface, and when performing a receiving operation, the communication interface can be considered as a receiving interface; or, the communication interface can also be a combination of two functional units.
  • the sending interface is used to complete the sending operation.
  • the sending interface can be used to execute any of the embodiments shown in FIG. 13 and executed by the second device.
  • the receiving interface is used to complete the receiving operation.
  • the receiving interface can be used to perform all the receiving operations performed by the second device in any of the embodiments shown in FIG. 13.
  • the communication device 2000 or the communication device 2100 can implement the function of the second device in any of the embodiments shown in FIG. 13, and each of the communication device 2000 or the communication device 2100 The operations and/or functions of the modules are used to implement the corresponding processes in any of the embodiments shown in FIG. 13, and are not repeated here for brevity.
  • the embodiment of the present application also provides a communication device, and the communication device may be a terminal device or a circuit.
  • the communication apparatus may be used to perform the actions performed by the first device, the second device, or the third device in the foregoing method embodiments.
  • FIG. 22 shows a simplified schematic diagram of the structure of the device. It is easy to understand and easy to illustrate.
  • the terminal device is taken as an example.
  • the device includes a processor, a memory, a radio frequency circuit, an antenna, and an input and output device.
  • the processor is mainly used to process the communication protocol and communication data, and to control the device, execute the software program, and process the data of the software program.
  • the memory is mainly used to store software programs and data.
  • the radio frequency circuit is mainly used for the conversion of baseband signal and radio frequency signal and the processing of radio frequency signal.
  • the antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users. It should be noted that some types of equipment may not have input and output devices.
  • the processor When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal to the outside in the form of electromagnetic waves through the antenna.
  • the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.
  • FIG. 22 only one memory and processor are shown in FIG. 22. In an actual device product, there may be one or more processors and one or more memories.
  • the memory may also be referred to as a storage medium or storage device.
  • the memory may be set independently of the processor, or may be integrated with the processor, which is not limited in the embodiment of the present application.
  • the antenna and radio frequency circuit with the transceiving function can be regarded as the transceiving unit of the device, and the processor with the processing function can be regarded as the processing unit of the device.
  • the device includes a transceiver unit 2210 and a processing unit 2220.
  • the transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, and so on.
  • the processing unit may also be called a processor, a processing board, a processing module, a processing device, and so on.
  • the device for implementing the receiving function in the transceiver unit 2210 can be regarded as the receiving unit, and the device for implementing the sending function in the transceiver unit 2210 as the sending unit, that is, the transceiver unit 2210 includes a receiving unit and a sending unit.
  • the transceiver unit may sometimes be called a transceiver, transceiver, or transceiver circuit.
  • the receiving unit may sometimes be called a receiver, a receiver, or a receiving circuit.
  • the transmitting unit may sometimes be called a transmitter, a transmitter, or a transmitting circuit.
  • the transceiving unit 2210 may also be used to perform the sending and receiving operations on the first device side in the foregoing method embodiment, and the processing unit 2220 is used to perform other than the transceiving operations on the first device in the foregoing method embodiment. Other operations.
  • the transceiving unit 2210 is used to perform all the sending and receiving operations of the first device in the embodiment shown in FIG. 2, such as S201, S202, and S204, and/or the transceiving unit 2210 is also used to Perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the first device in the embodiment shown in FIG. 2 except for the transceiving operation, such as S203, and/or the processing unit 2220 is also configured to perform support for the technology described herein Other processes.
  • the transceiver unit 2210 is configured to perform all the sending operations and receiving operations of the first device in the embodiment shown in FIG. 3, such as S301, S302, and S304, and/or the transceiver unit 2210 also uses To perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the first device in the embodiment shown in FIG. 3 except for the transceiving operation, such as S303, and/or the processing unit 2220 is also configured to perform support for the technology described herein Other processes.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the first device in the embodiment shown in FIG. 4, such as S401, S402, S403, S405, and S409, and/or the transceiver
  • the unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is configured to perform all operations performed by the first device in the embodiment shown in FIG. 4 except for the receiving and sending operations, such as S406 to S408, and/or the processing unit 2220 is also configured to perform support described herein Other processes of the technology.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the first device in the embodiment shown in FIG. 5, such as S501, S502, S503, S505, and S509, and/or The unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is configured to perform all operations performed by the first device in the embodiment shown in FIG. 5 except for the receiving and sending operations, such as S506 to S508, and/or the processing unit 2220 is also configured to perform support described herein Other processes of the technology.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the T-Box in the embodiment shown in FIG. 6, such as S601, S603, S605, S607, and S610, and/or the transceiver
  • the unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is used to perform all operations performed by the T-Box in the embodiment shown in FIG. 6 except for receiving and sending operations, such as S604, S608, and S609, and/or the processing unit 2220 is also used to perform support for this text Other processes of the described technique.
  • the transceiver unit 2210 is used to perform all the sending and receiving operations of the MDC in the embodiment shown in FIG. 7, such as S701, S703, and S705, and/or the transceiver unit 2210 is also used to perform Other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the MDC in the embodiment shown in FIG. 7 except for the transceiving operation, such as S704, and/or the processing unit 2220 is also configured to perform other operations that support the technology described herein process.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the MDC in the embodiment shown in FIG. 8, such as S801, S803, S805, S807, S810, and S812, and/or the transceiver
  • the unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is configured to perform all operations performed by the MDC in the embodiment shown in FIG. 8 except for the receiving and sending operations, such as S804, S808, and S809, and/or the processing unit 2220 is also used to perform the support described herein Other processes of the technology.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the sensor in the embodiment shown in FIG. 9, such as S901, S903, S905, S907, and S908, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the sensor in the embodiment shown in FIG. 9 except for receiving and sending operations, such as S904, and/or the processing unit 2220 is also configured to perform other operations that support the technology described herein process.
  • the transceiver unit 2210 is configured to perform all PEPS transmission operations and reception operations in the embodiment shown in FIG. 10, such as S1001, S1003, S1005, S1007, and S1008, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the PEPS in the embodiment shown in FIG. 10 except for receiving and sending operations, such as S1004, and/or the processing unit 2220 is also configured to perform other operations that support the technology described herein process.
  • the transceiver unit 2210 is configured to perform all the BCM sending and receiving operations in the embodiment shown in FIG. 11, such as S1101, S1103, S1105, S1107, and S1108, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the BCM in the embodiment shown in FIG. 11 except for the transceiving operation, such as S1104, and/or the processing unit 2220 is also configured to perform other operations that support the technology described herein process.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the OBC in the embodiment shown in FIG. 12, such as S1201, S1203, S1205, S1207, and S1208, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the OBC in the embodiment shown in FIG. 12 except for the transceiving operation, such as S1204, and/or the processing unit 2220 is also configured to perform other operations that support the technology described herein process.
  • transceiving unit 2210 may be used to perform the sending and receiving operations on the second device side in the foregoing method embodiment, and the processing unit 2220 is used to perform other operations on the second device in the foregoing method embodiment except for the transceiving operation.
  • the transceiving unit 2210 is used to perform all the sending and receiving operations of the second device in the embodiment shown in FIG. 2, such as S201, S202, and S204, and/or the transceiving unit 2210 is also used to Perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the second device in the embodiment shown in FIG. 2 except for the receiving and sending operations, such as S205 and S206, and/or the processing unit 2220 is also configured to perform the support described herein Other processes of the technology.
  • the transceiver unit 2210 is configured to perform all the sending operations and receiving operations of the second device in the embodiment shown in FIG. 3, such as S301, S302, and S304, and/or the transceiver unit 2210 also uses To perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the second device in the embodiment shown in FIG. 3 except for the receiving and sending operations, such as S305 and S306, and/or the processing unit 2220 is also configured to perform the support described herein Other processes of the technology.
  • the transceiving unit 2210 is configured to perform all the sending and receiving operations of the second device in the embodiment shown in FIG. 4, such as S401, S402, S403, S405, and S409, and/or transceiving
  • the unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is used to perform all operations performed by the second device in the embodiment shown in FIG. 4 except for the receiving and sending operations, such as S404, S410, and S411, and/or the processing unit 2220 is also used to perform support for this text Other processes of the described technique.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the second device in the embodiment shown in FIG. 5, such as S501, S502, S503, S505, and S509, and/or the transceiver
  • the unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is configured to perform all operations other than the transceiving operation performed by the second device in the embodiment shown in FIG. 5, such as S504, S510, and S511, and/or the processing unit 2220 is also configured to perform support for this text Other processes of the described technique.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the MDC in the embodiment shown in FIG. 6, such as S601, S603, S605, S607, and S610, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the MDC in the embodiment shown in FIG. 6 except for the receiving and sending operations, such as S602, S606, and S611, and/or the processing unit 2220 is also used to perform the support described herein Other processes of the technology.
  • the transceiver unit 2210 is used to perform all the sending and receiving operations of the VCU in the embodiment shown in FIG. 7, such as S701, S703, and S705, and/or the transceiver unit 2210 is also used to perform Other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the VCU in the embodiment shown in FIG. 7 except for the transceiving operation, such as S702 and S706, and/or the processing unit 2220 is also configured to perform support for the technology described herein Other processes.
  • the transceiver unit 2210 is used to perform all the sending and receiving operations of the HMI in the embodiment shown in FIG. 8, such as S801, S803, S805, S807, S810, and S812, and/or the transceiver
  • the unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is used to perform all operations performed by the HMI in the embodiment shown in FIG. 8 except for receiving and sending operations, such as S802, S806, and S811, and/or the processing unit 2220 is also used to perform support described herein Other processes of the technology.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the MDC in the embodiment shown in FIG. 9, such as S901, S903, S905, S907, and S908, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the MDC in the embodiment shown in FIG. 9 except for receiving and sending operations, such as S902 and S906, and/or the processing unit 2220 is also configured to perform support for the technology described herein Other processes.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the BCM in the embodiment shown in FIG. 10, such as S1001, S1003, S1005, S1007, and S1008, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the BCM in the embodiment shown in FIG. 10 except for the transceiving operation, such as S1002 and S1006, and/or the processing unit 2220 is also configured to perform support for the technology described herein Other processes.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the VCU in the embodiment shown in FIG. 11, such as S1101, S1103, S1105, S1107, and S1108, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the VCU in the embodiment shown in FIG. 11 except for the transceiving operation, such as S1102 and S1106, and/or the processing unit 2220 is also configured to perform support for the technology described herein Other processes.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the VCU in the embodiment shown in FIG. 12, such as S1201, S1203, S1205, S1207, and S1208, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the VCU in the embodiment shown in FIG. 12 except for the transceiving operation, such as S1202 and S1206, and/or the processing unit 2220 is also configured to perform support for the technology described herein Other processes.
  • the transceiving unit 2210 is used to perform all the sending and receiving operations of the second device in the embodiment shown in FIG. 13, such as S1303, and/or the transceiving unit 2210 is also used to perform supporting text Other processes of the described technique.
  • the processing unit 2220 is configured to perform all operations performed by the second device in the embodiment shown in FIG. 13 except for receiving and sending operations, such as S1301 to S1303, and/or the processing unit 2220 is also configured to perform support described herein Other processes of the technology.
  • the transceiving unit 2210 may also be used to perform the sending and receiving operations on the third device side in the foregoing method embodiment, and the processing unit 2220 is used to perform other than the transceiving operations on the third device in the foregoing method embodiment. Other operations.
  • the transceiving unit 2210 is used to perform all the sending and receiving operations of the third device in the embodiment shown in FIG. 2, such as S201, S202, and S204, and/or the transceiving unit 2210 is also used to Perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the third device in the embodiment shown in FIG. 2 except for the sending and receiving operations, such as querying the second device based on the first information, or filtering based on the first information
  • the operation and/or processing unit 2220 is also used to perform other processes that support the technology described herein.
  • the transceiving unit 2210 is configured to perform all the sending and receiving operations of the third device in the embodiment shown in FIG. 4, such as S401, S402, S403, S405, and S409, and/or transceiving
  • the unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is configured to perform all operations performed by the third device in the embodiment shown in FIG. 4 except for receiving and sending operations, such as querying the second device based on the first information, or filtering based on the first information
  • the operation and/or processing unit 2220 is also used to perform other processes that support the technology described herein.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the gateway in the embodiment shown in FIG. 6, such as S601, S603, S605, S607, and S610, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the gateway in the embodiment shown in FIG. 6 except for the sending and receiving operations, for example, the operation of querying the second device based on the first information, or the operation of filtering based on the first information , And/or the processing unit 2220 is also used to perform other processes that support the technology described herein.
  • the transceiver unit 2210 is used to perform all the sending and receiving operations of the gateway in the embodiment shown in FIG. 7, such as S701, S703, and S705, and/or the transceiver unit 2210 is also used to perform Other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the gateway in the embodiment shown in FIG. 7 except for the sending and receiving operations, for example, the operation of querying the second device based on the first information, or the operation of filtering based on the first information , And/or the processing unit 2220 is also used to perform other processes that support the technology described herein.
  • the transceiver unit 2210 is used to perform all the sending and receiving operations of the gateway in the embodiment shown in FIG. 8, such as S801, S803, S805, S807, S810, and S812, and/or
  • the unit 2210 is also used to perform other processes that support the technology described herein.
  • the processing unit 2220 is configured to perform all operations performed by the gateway in the embodiment shown in FIG. 8 except for the sending and receiving operations, such as the operation of querying the second device based on the first information, or the operation of filtering based on the first information , And/or the processing unit 2220 is also used to perform other processes that support the technology described herein.
  • the transceiver unit 2210 is configured to perform all the sending and receiving operations of the gateway in the embodiment shown in FIG. 11, such as S1101, S1103, S1105, S1107, and S1108, and/or the transceiver unit 2210 It is also used to perform other processes that support the technology described in this article.
  • the processing unit 2220 is configured to perform all operations performed by the gateway in the embodiment shown in FIG. 11 except for the sending and receiving operations, such as the operation of querying the second device based on the first information, or the operation of filtering based on the first information , And/or the processing unit 2220 is also used to perform other processes that support the technology described herein.
  • the device may include a transceiver unit and a processing unit.
  • the transceiving unit may be an input/output circuit and/or a communication interface;
  • the processing unit is an integrated processor or a microprocessor or an integrated circuit.
  • the device shown in FIG. 23 can be referred to.
  • the device can perform functions similar to the processor 1510 in FIG. 15.
  • the device can perform functions similar to the processor 1710 in FIG. 17.
  • the device can perform functions similar to the processor 1910 in FIG. 19.
  • the device may perform functions similar to the processor 2110 in FIG. 21.
  • the device includes a processor 2310, a data sending processor 2320, and a data receiving processor 2330.
  • the processing module 1410 in the foregoing embodiment may be the processor 2310 in FIG. 23 and complete corresponding functions; the transceiver module 1420 in the foregoing embodiment may be the sending data processor 2320 in FIG.
  • the processing module 1610 in the foregoing embodiment may be the processor 2310 in FIG. 23 and perform corresponding functions; the transceiver module 1620 in the foregoing embodiment may be the sending data processor 2320 in FIG. 23, and/or Receive data processor 2330.
  • the processing module 1810 in the foregoing embodiment may be the processor 2310 in FIG. 23 and complete corresponding functions; the transceiver module 1820 in the foregoing embodiment may be the sending data processor 2320 in FIG. 23, and/or Receive data processor 2330.
  • the processing module 2010 in the foregoing embodiment may be the processor 2310 in FIG.
  • the transceiver module 2020 in the foregoing embodiment may be the sending data processor 2320 in FIG. 23, and/or Receive data processor 2330.
  • the channel encoder and the channel decoder are shown in FIG. 23, it can be understood that these modules do not constitute a restrictive description of this embodiment, and are only illustrative.
  • Fig. 24 shows another form of this embodiment.
  • the processing device 2400 includes modules such as a modulation subsystem, a central processing subsystem, and a peripheral subsystem.
  • the communication device in this embodiment can be used as the modulation subsystem therein.
  • the modulation subsystem may include a processor 2403 and an interface 2404.
  • the processor 2403 completes the function of the aforementioned processing module 1410
  • the interface 2404 completes the function of the aforementioned transceiver module 1420.
  • the processor 2403 completes the function of the aforementioned processing module 1610
  • the interface 2404 completes the function of the aforementioned transceiver module 1620.
  • the processor 2403 completes the function of the aforementioned processing module 1810, and the interface 2404 completes the function of the aforementioned transceiver module 1820.
  • the processor 2403 completes the function of the aforementioned processing module 2010, and the interface 2404 completes the function of the aforementioned transceiver module 2020.
  • the modulation subsystem includes a memory 2406, a processor 2403, and a program stored on the memory 2406 and running on the processor.
  • the processor 2403 implements the first device in the foregoing method embodiment when the program is executed. , The second device or the third device side method.
  • the memory 2406 can be non-volatile or volatile, and its location can be located inside the modulation subsystem or in the processing device 2400, as long as the memory 2406 can be connected to the The processor 2403 is sufficient.
  • the embodiment of the present application provides a first communication system.
  • the first communication system may include at least one first device involved in any one of the above-mentioned embodiment shown in FIG. 2 to the embodiment shown in FIG. 12, and at least one of the above-mentioned implementation shown in FIG. 2 Examples to the second device involved in any of the embodiments shown in FIG. 12.
  • the first device is, for example, the communication device 1400 in FIG. 14 or the communication device 1500 in FIG. 15.
  • the first device can be used to perform all operations performed by the first device in any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12, for example: in the embodiment shown in FIG. S201-S204, and/or other processes used to support the technology described herein; or, S301-S304 in the embodiment shown in FIG.
  • the second device is, for example, the communication device 1600 in FIG. 16 or the communication device 1700 in FIG. 17.
  • the second device can be used to perform all operations performed by the second device in any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12, for example: S201 in the embodiment shown in FIG. 2 , S202, S204, S205, and S206, and/or other processes used to support the technology described herein; or, S301, S302, S304, S305, and S306 in the embodiment shown in FIG. 3, and/or used for Other processes that support the technology described herein; or, S401, S402, S403, S405, S409, S404, S410, and S411 in the embodiment shown in FIG.
  • the first communication system may further include at least one third device involved in any one of the above-mentioned embodiment shown in FIG. 2 to the embodiment shown in FIG. 12.
  • the third device is, for example, the communication device 1800 in FIG. 18 or the communication device 1900 in FIG. 19.
  • the third device can be used to perform all operations performed by the third device in any one of the embodiment shown in FIG. 2 to the embodiment shown in FIG. 12, for example: S201 in the embodiment shown in FIG. 2 , S202 and S204, query the operation of the second device based on the first information, or perform filtering based on the first information, and/or other processes used to support the technology described herein; or, the embodiment shown in FIG.
  • S401, S402, S403, S405 and S409 query the operation of the second device based on the first information, or perform filtering based on the first information, and/or other processes used to support the technology described herein; or, S601, S603, S605, S607, and S610 in the embodiment shown in FIG. 6 query the operation of the second device according to the first information, or perform the filtering operation according to the first information, and/or are used to support the operations described herein Other processes of the technology; or, S701, S703, and S705 in the embodiment shown in FIG.
  • the embodiment of the present application provides a second communication system.
  • the second communication system may include at least one second device involved in the above-mentioned embodiment shown in FIG. 13.
  • the second device is, for example, the communication device 2000 in FIG. 20 or the communication device 2100 in FIG. 21.
  • the second device can be used to perform all operations performed by the second device in the embodiment shown in FIG. 13, for example: S1301 to S1303 in the embodiment shown in FIG. 13, and/or used to support the technology described herein Other processes.
  • the second communication system may further include at least one first device involved in any one of the above-mentioned embodiment shown in FIG. 2 to the embodiment shown in FIG. 12.
  • the second communication system may further include at least one third device involved in any one of the above-mentioned embodiment shown in FIG. 2 to the embodiment shown in FIG. 12.
  • the above two communication systems may be the same communication system, or may also be different communication systems.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 2 provided by the foregoing method embodiment. The process related to the first device in the embodiment.
  • the embodiments of the present application also provide a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 3 provided by the foregoing method embodiment. The process related to the first device in the embodiment.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 4 provided by the foregoing method embodiment. The process related to the first device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 5 provided by the foregoing method embodiment.
  • the process related to the first device in the embodiment is also provided.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 6 provided by the foregoing method embodiment.
  • the process related to the first device in the embodiment is also provided.
  • the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 7 provided by the foregoing method embodiment. The process related to the first device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 8 provided by the foregoing method embodiment.
  • the process related to the first device in the embodiment is not limited to a computer-readable storage medium.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 9 provided by the foregoing method embodiment. The process related to the first device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 10 provided by the foregoing method embodiment The process related to the first device in the embodiment.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 11 provided by the foregoing method embodiment. The process related to the first device in the embodiment.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 12 provided by the foregoing method embodiment. The process related to the first device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 2 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • the embodiments of the present application also provide a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 3 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 4 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 5 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 6 provided by the foregoing method embodiment.
  • the process related to the second device in the embodiment is also provided.
  • the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 7 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 8 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 9 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • the embodiments of the present application also provide a computer-readable storage medium that stores a computer program.
  • the computer program When executed by a computer, the computer can implement the method shown in FIG. 10 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 11 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 12 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 13 provided by the foregoing method embodiment. The process related to the second device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 2 provided by the foregoing method embodiment.
  • the process related to the third device in the embodiment is also provided.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 4 provided by the foregoing method embodiment. The process related to the third device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 6 provided by the foregoing method embodiment.
  • the process related to the third device in the embodiment is also provided.
  • the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 7 provided by the foregoing method embodiment. The process related to the third device in the embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer can implement the method shown in FIG. 8 provided by the foregoing method embodiment.
  • the process related to the third device in the embodiment is also provided.
  • An embodiment of the present application also provides a computer-readable storage medium that stores a computer program.
  • the computer program When the computer program is executed by a computer, the computer can implement the method shown in FIG. 11 provided by the foregoing method embodiment. The process related to the third device in the embodiment.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 2 provided by the above method embodiment The process related to the first device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 3 provided by the above method embodiment The process related to the first device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 4 provided by the above method embodiment The process related to the first device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 5 provided by the above method embodiment The process related to the first device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 6 provided by the above method embodiment The process related to the first device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 7 provided by the above method embodiment The process related to the first device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 8 provided by the above method embodiment The process related to the first device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 9 provided by the above method embodiment The process related to the first device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 10 provided by the above method embodiment The process related to the first device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 11 provided by the above method embodiment The process related to the first device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 12 provided by the above method embodiment The process related to the first device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 2 provided by the above method embodiment The process related to the second device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 3 provided by the above method embodiment The process related to the second device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 4 provided by the above method embodiment The process related to the second device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 5 provided by the above method embodiment The process related to the second device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 6 provided by the above method embodiment The process related to the second device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 7 provided by the above method embodiment The process related to the second device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 8 provided by the above method embodiment The process related to the second device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 9 provided by the above method embodiment The process related to the second device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 10 provided by the above method embodiment The process related to the second device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 11 provided by the above method embodiment The process related to the second device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 12 provided by the above method embodiment The process related to the second device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 13 provided by the above method embodiment The process related to the second device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 2 provided by the above method embodiment The process related to the third device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 4 provided by the above method embodiment The process related to the third device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 6 provided by the above method embodiment The process related to the third device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 7 provided by the above method embodiment The process related to the third device.
  • the embodiments of the present application also provide a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 8 provided by the above method embodiment The process related to the third device.
  • the embodiment of the present application also provides a computer program product, the computer program product is used to store a computer program, when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 11 provided by the above method embodiment The process related to the third device.
  • processors mentioned in the embodiments of this application may be a CPU, or other general-purpose processors, digital signal processors (digital signal processors, DSP), application specific integrated circuits (ASICs), ready-made Field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请涉及一种设备认证方法及装置，可应用于车联网，例如V2X、LTE-V、V2V等，或可用于智能驾驶，智能网联车等领域。第一设备将第一信息和第一证书发送给第二设备，第一信息用于指示第二设备，第一证书为第一设备的设备证书。第一设备接收来自第二设备的第一随机数。所述第一设备采用第一私钥，根据第一随机数和第一标识，得到第一签名，第一标识为第一设备的标识。第一设备将第一签名发送给第二设备，第一签名用于对第一设备进行认证。本申请实施例实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式因为无需一个中间节点对多个节点进行认证，减轻了设备的负担。

Description

一种设备认证方法及装置
相关申请的交叉引用
本申请要求在2019年09月19日提交中国国家知识产权局、申请号为201910886787.9、申请名称为“一种设备认证方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种设备认证方法及装置。
背景技术
随着汽车向智能化、网联化的发展，汽车的功能不断增加，车辆的联网不仅让车厂可以了解、跟踪车辆的情况，同时也给用户的日常生活带来了更多的便利。然而，非法用户通过网络深入联网汽车系统，对车辆进行操作、控制，会给车辆安全带来极大的威胁。为此，需要采取一定的措施，以保证车辆安装的终端设备是合法的设备，防止安装非授权的设备对车载数据的监听以及发送恶意、虚假的指令、数据对车辆功能的干扰、破坏。
目前采取的一种措施是，可以对车载设备进行认证。目前将车载设备划分为多个层级，实行层级认证机制，例如第一层级的车载设备可以对第二层级的车载设备进行认证，如果第二层级的车载设备认证通过，则第二层级的车载设备可以对第三层级的车载设备进行认证。这种认证措施会较为依赖中间节点，例如第二层级的车载设备就可以视为中间节点，如果第二层级的车载设备被认证失败，那么第二层级的车载设备无法对第三层级的车载设备进行认证，导致大量的车载设备得不到认证。
可见，在这种认证机制下，可能导致一些车载设备得不到认证，安全隐患较大。
发明内容
本申请实施例提供一种设备认证方法及装置，用于提高车载设备能够得到认证的几率，减小安全隐患。
第一方面，提供第一种设备认证方法，该方法包括：第一设备将第一信息和第一证书发送给第二设备，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；所述第一设备接收来自所述第二设备的第一随机数；所述第一设备采用第一私钥，根据所述第一随机数和第一标识，得到第一签名，所述第一标识为所述第一设备的标识；所述第一设备将所述第一签名发送给第二设备，所述第一签名用于对所述第一设备进行认证。
该第一方面的方法可由第一通信装置执行，第一通信装置可以是通信设备或能够支持通信设备实现该方法所需的功能的装置，例如芯片系统。示例性地，通信设备为车载装置。在下文的描述中，以第一通信装置是第一设备为例。
在本申请实施例中，第一信息用于指示第二设备，例如，第一信息可能是第一业务的标识，或者是第二设备的地址等，只要第一设备将第一信息发送给第二设备，第二设备就 可以对第一设备进行认证，不依赖设备之间的层级关系，例如，即使第一设备是第一层级的设备，第二设备是第三层级的设备，第一设备和第二设备之间也能进行认证，这样就实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式因为无需一个中间节点对多个节点进行认证，减轻了设备的负担。通过本申请实施例的技术方案，实现了设备之间端到端的认证，减少了对于中间节点的依赖，使得更多的车载设备能够得到认证，提高了车载设备的安全性。本申请实施例提供的认证方案具有一定的韧性。此外，本申请实施例提供的端到端的认证方案与整车的架构无关，兼容性比较好，可以适用于现在的汽车架构，也可以适用于未来的汽车架构。
结合第一方面，在第一方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
例如，第一信息可以包括第一业务的标识，第一业务的标识可以指示认证的目标设备。认证的目标设备，例如第二设备。因此第一信息可以指示第二设备。也就是说，所述的认证过程可以与第一业务相关。从而，在业务不同时，对应的第二设备可以有所不同，使得认证过程能够与业务相结合，服务于业务，从而使得业务的安全性更高。例如，在第一设备和第二设备即将进行第一业务之前，第二设备先要对第一设备进行认证，在这种场景下，第一信息就可以包括业务的标识。例如要进行自动驾驶功能，自动驾驶功能涉及到第一设备和第二设备，那么第一设备和第二设备就可以在进行自动驾驶功能之前进行认证。在这种情况下，第一设备发送给第二设备的第一信息，就可以包括自动驾驶功能这一业务的标识，以让第二设备可以明确，当前的认证是对应于自动驾驶业务的。作为一种可选的实施方式，第一信息可以就是第一业务的标识，或者，第一信息除了包括第一业务的标识之外，还可以包括其他的信息。
或者，第一信息还可以包括其他的内容，例如，第一信息可以包括第二设备的信息，第二设备的信息例如包括第二设备的标识(例如第二设备的ID)，或者，包括第二设备的IP地址，或者，包括第二设备的IP地址和第二设备的标识，或者，第二设备的信息还可以包括第二设备的其他信息。因此，第一信息可以指示第二设备。例如，在第一设备和第二设备执行认证时，第一设备和第二设备已经都明确该认证是对应于某个业务的，那么在这种情况下，第一设备发送给第二设备的第一信息可以不包括第一业务的标识。为了使得第二设备明确第一设备所发送的信息是对应于第二设备的，第一设备所发送的第一信息可以包括第二设备的信息，例如包括第二设备的ID，或者包括第二设备的IP地址等，从而第二设备可以明确来自第一设备的信息是对应于第二设备的，使得认证过程得以进行。
或者，第一信息还可以包括其他的信息，对于第一信息所具体包括的信息不做限制。
结合第一方面，在第一方面的一种可能的实施方式中，所述方法还包括：所述第一设备生成第二随机数；所述第一设备将所述第二随机数发送给所述第二设备。
在本申请实施例中，除了第二设备可以对第一设备进行认证之外，第一设备也可以对第二设备进行认证，以进一步提高通信过程的安全性。为了对第二设备进行认证，第一设备可以生成第二随机数，例如第二设备可以根据第二随机数得到签名，从而第一设备可以根据第二随机数和该签名对第二设备进行认证。通过随机数来进行认证，提高了对于合法设备被非法设备替换的情况下的识别成功率，提高了车辆系统的可靠性。
结合第一方面，在第一方面的一种可能的实施方式中，所述方法还包括：所述第一设备接收来自所述第二设备的第二签名和第二标识，所述第二标识为所述第二设备的标识； 所述第一设备根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证。
例如，第二设备可以根据第二随机数得到签名，从而第一设备可以根据第二随机数和该签名对第二设备进行认证。通过随机数来进行认证，提高了对于合法设备被非法设备替换的情况下的识别成功率，提高了车辆系统的可靠性。而且第一设备和第二设备之间的认证可以采取非对称的认证方式，相对于对称的认证方式来说，非对称的认证方式可以进一步提高认证的可靠性。
结合第一方面，在第一方面的一种可能的实施方式中，所述第一设备根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证，包括：
所述第一设备采用第二公钥，对所述第二签名、所述第二随机数和所述第二标识进行验签，得到返回的结果，当所述返回的结果指示验签通过时，确定对所述第二设备认证成功，否则，当所述返回的结果指示验签未通过时，确定对所述第二设备认证失败。
例如，第一设备可以采用第二公钥，根据第二随机数、第二签名和第二标识对第二设备进行认证，第二公钥和用于得到第二签名的第二私钥是一对非对称密钥。例如，第一设备可以采用第二公钥，对第二签名、第二随机数和第二标识进行验签，并根据返回的结果启动验签是否通过，如果验签通过，表明对第二设备认证成功，否则，表明对第二设备认证失败。验签的方式例如为，第一设备采用哈希算法，根据第二随机数和第二标识得到哈希值，例如称为第三哈希值，第一设备将第二公钥、第三哈希值和第二签名输入签名验证函数(例如称为第二函数)进行验签，根据返回的结果确定验签是否通过。
结合第一方面，在第一方面的一种可能的实施方式中，所述第一证书不包括主题属性信息。
第一证书可以不包括主题属性信息，该主题属性信息可以是第一证书的主题属性信息，或者，也可以将主题属性信息称为应用场景信息。设备证书可以只用于设备间的认证，不用作其它场景的认证，体现了设备证书的专属性，有利于保障系统的安全。而且通过本申请实施例提供的方案，也能减少设备证书的大小。其中，第一证书可以不包括第一证书的主题属性信息，与第一证书是用于与业务的认证相关，例如，在第一设备和第二设备为第一业务进行认证时，所使用的第一证书可以不包括第一证书的主题属性信息。或者，第一证书不包括第一证书的主题属性信息，也可以与认证过程是否与业务相关没有关系。例如，第一设备和第二设备之间进行认证，但该认证与业务无关，所使用的第一证书也可以不包括第一证书的主题属性信息。
结合第一方面，在第一方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：所述第一证书的版本信息，所述第一证书的签名者信息，所述第一证书的主题信息，所述第一证书的有效性信息，或，所述第一证书的签名信息。
例如，第一证书包括第一证书的版本信息；或者，第一证书包括第一证书的签名者信息和第一证书的主题信息；或者，第一证书包括第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息；或者，第一证书包括第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息，等等。
结合第一方面，在第一方面的一种可能的实施方式中，所述方法还包括：所述第一设备接收来自所述第二设备的指示信息，所述指示信息用于指示对所述第一设备认证失败，或，用于指示所述第一设备停止工作或停止使用所述第一设备的部分功能；所述第一设备 停止工作，或停止使用所述第一设备的部分功能。
如果第二设备对第一设备认证失败，则第二设备可以确定第一执行策略，第一执行策略例如包括，设备停止工作，或者设备停止使用该设备的部分功能。第一执行策略例如是第二设备根据第一业务确定的，从而使得设备的执行策略更为符合业务的需求。第一执行策略可以是第二设备执行，也可以是第一设备执行。如果第一执行策略应该由第一设备执行，则第二设备可以向第一设备发送指示信息，第一设备接收来自第二设备的指示信息，指示信息用于指示第一执行策略。例如，第二设备为网关或路由器等设备，或者为具有路由转发功能的实体，则第一执行策略可以由第一设备执行，则第二设备可以向第一设备发送指示信息；或者，第二设备为除了网关和路由器之外的其他设备，或者为除了具有路由转发功能的实体之外的其他的实体，则第一执行策略可以由第二设备执行，则第二设备可以不向第一设备发送指示信息，而是自行执行第一执行策略即可。
第二方面，提供第二种设备认证方法，该方法包括：第二设备接收来自第一设备的第一信息和第一证书，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；所述第二设备根据所述第一设备的根证书或二级证书，验证所述第一证书是否正确；当所述第一证书正确时，所述第二设备生成第一随机数；所述第二设备将所述第一随机数发送给所述第一设备；所述第二设备接收来自所述第一设备的第一签名；所述第二设备根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
该第二方面的方法可由第二通信装置执行，第二通信装置可以是通信设备或能够支持通信设备实现该方法所需的功能的装置，例如芯片系统。示例性地，通信设备为车载装置。在下文的描述中，以第二通信装置是第二设备为例。
在本申请实施例中，第一信息用于指示第二设备，例如，第一信息可能是第一业务的标识，或者是第二设备的地址等，只要第一设备将第一信息发送给第二设备，第二设备就可以对第一设备进行认证，不依赖设备之间的层级关系，例如，即使第一设备是第一层级的设备，第二设备是第三层级的设备，第一设备和第二设备之间也能进行认证，这样就实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式因为无需一个中间节点对多个节点进行认证，减轻了设备的负担。通过本申请实施例的技术方案，实现了设备之间端到端的认证，减少了对于中间节点的依赖，使得更多的车载设备能够得到认证，提高了车载设备的安全性。本申请实施例提供的认证方案具有一定的韧性。此外，本申请实施例提供的端到端的认证方案与整车的架构无关，兼容性比较好，可以适用于现在的汽车架构，也可以适用于未来的汽车架构。
结合第二方面，在第二方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
例如，第一信息可以包括第一业务的标识，也就是说，所述的认证过程可以与第一业务相关。从而，在业务不同时，对应的第二设备可以有所不同，使得认证过程能够与业务相结合，服务于业务，从而使得业务的安全性更高。或者，第一信息还可以包括其他的内容，例如，第一信息可以包括第二设备的信息，第二设备的信息例如包括第二设备的标识(例如第二设备的ID)，或者包括第二设备的IP地址等。或者，第一信息还可以包括其他的信息。
结合第二方面，在第二方面的一种可能的实施方式中，所述第二设备根据所述第一签 名、所述第一随机数和第一标识，对所述第一设备进行认证，包括：
所述第二设备采用第一公钥，对所述第一签名、所述第一随机数和所述第一标识进行验签，得到返回的结果，当所述返回的结果指示验签通过时，确定对所述第一设备认证成功，否则，当所述返回的结果指示验签未通过时，确定对所述第一设备认证失败。
例如，第二设备可以采用第一公钥，根据第一随机数、第一签名和第一标识对第一设备进行认证，第一公钥和用于得到第一签名的第一私钥是一对非对称密钥。例如，第二设备可以采用第一公钥，对第一签名、第一随机数和第一标识进行验签，并根据返回的结果启动验签是否通过，如果验签通过，表明对第一设备认证成功，否则，表明对第一设备认证失败。验签的方式例如为，第二设备采用哈希算法，根据第一随机数和第一标识得到哈希值，例如称为第四哈希值，第二设备将第一公钥、第四哈希值和第一签名输入签名验证函数(例如称为第一函数)进行验签，根据返回的结果确定验签是否通过。
结合第二方面，在第二方面的一种可能的实施方式中，所述方法还包括：所述第二设备接收来自所述第一设备的第二随机数；当对所述第一设备认证通过时，所述第二设备采用第二私钥，根据所述第二随机数和所述第二标识生成第二签名；所述第二设备将所述第二签名和第二标识发送给所述第一设备，所述第二签名用于对所述第二设备进行认证，所述第二标识为所述第二设备的标识。
例如，第二设备可以根据第二随机数得到签名，从而第一设备可以根据第二随机数和该签名对第二设备进行认证。通过随机数来进行认证，提高了对于合法设备被非法设备替换的情况下的识别成功率，提高了车辆系统的可靠性。而且第一设备和第二设备之间的认证可以采取非对称的认证方式，相对于对称的认证方式来说，非对称的认证方式可以进一步提高认证的可靠性。
结合第二方面，在第二方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
第一证书可以不包括第一证书的主题属性信息，或者，也可以将主题属性信息称为应用场景信息。设备证书可以只用于设备间的认证，不用作其它场景的认证，体现了设备证书的专属性，有利于保障系统的安全。而且通过本申请实施例提供的方案，也能减少设备证书的大小。
结合第二方面，在第二方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：所述第一证书的版本信息，所述第一证书的签名者信息，所述第一证书的主题信息，所述第一证书的有效性信息，或，所述第一证书的签名信息。
例如，第一证书包括第一证书的版本信息；或者，第一证书包括第一证书的签名者信息和第一证书的主题信息；或者，第一证书包括第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息；或者，第一证书包括第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息，等等。
结合第二方面，在第二方面的一种可能的实施方式中，所述方法还包括：
当对所述第一设备认证失败时，所述第二设备向所述第一设备发送指示信息，所述指示信息用于指示对所述第一设备认证失败，或，用于指示所述第一设备停止工作或停止使用所述第一设备的部分功能；或，
当对所述第一设备认证失败时，所述第二设备停止工作或所述第二设备停止使用所述第二设备的部分功能。
如果第二设备对第一设备认证失败，则第二设备可以确定第一执行策略，第一执行策略例如包括，设备停止工作，或者设备停止使用该设备的部分功能。第一执行策略例如是第二设备根据第一业务确定的，从而使得设备的执行策略更为符合业务的需求。第一执行策略可以是第二设备执行，也可以是第一设备执行。如果第一执行策略应该由第一设备执行，则第二设备可以向第一设备发送指示信息，第一设备接收来自第二设备的指示信息，指示信息用于指示第一执行策略。例如，第二设备为网关或路由器等设备，或者为具有路由转发功能的实体，则第一执行策略可以由第一设备执行，则第二设备可以向第一设备发送指示信息；或者，第二设备为除了网关和路由器之外的其他设备，或者为除了具有路由转发功能的实体之外的其他的实体，则第一执行策略可以由第二设备执行，则第二设备可以不向第一设备发送指示信息，而是自行执行第一执行策略即可。
第三方面，提供第三种设备认证方法，该方法包括：第三设备接收来自第一设备的第一信息和第一证书，所述第一信息用于指示第二设备，所述第一证书为所述第一设备的设备证书；根据所述第一信息，查找对应的所述第二设备；将所述第一信息和所述第一证书发送给所述第二设备，所述第一证书用于所述第二设备对所述第一设备进行认证。
该第三方面的方法可由第三通信装置执行，第三通信装置可以是通信设备或能够支持通信设备实现该方法所需的功能的装置，例如芯片系统。示例性地，通信设备为车载装置。例如该车载装置为网关或路由器等装置，或者也可以是其他的具有路由转发功能的装置。在下文的描述中，以第三通信装置是第三设备为例。
第三设备可以仅仅起到转发功能，即，第三设备不对来自第一设备的信息(例如第一信息和第一证书等)做任何处理，而是直接转发给第二设备。
或者，第三设备可以根据第一信息进行查询，以查找对应的第二设备。例如，第一信息为第一业务的ID，第一设备只是将第一业务的ID和第一证书发送给第三设备。第三设备例如存储了业务的ID和设备之间的对应关系，例如该对应关系可以是业务的ID和设备的地址之间的对应关系，设备的地址例如为设备的IP地址。该对应关系是用于指示相应的业务应该由哪些设备执行，或者用于指示要执行相应的业务，需与哪些设备进行认证，或者说，是指示与业务关联的设备。例如第三设备查询该对应关系，确定第一业务的ID所对应的设备，例如包括第二设备，那么第三设备就可以将第一证书和第一信息转发给第二设备。在这种情况下，在该对应关系中，可能一个业务的ID会对应一个或多个设备，例如第一业务的ID可能只对应第二设备，或者也可能对应多个设备，这多个设备中包括第二设备。那么，第三设备可以只将第一信息和第一证书等转发给第一业务的ID所对应的部分设备，例如只转发给第二设备，或者，第三设备也可以将第一信息和第一证书等转发给第一业务的ID所对应的全部的设备。由第三设备来负责转发，第一设备无需获知目标设备的过多的信息，减少了第一设备的负担，且第三设备实现统一转发，可以使得信息的转发更为符合统一的规则。当然，所述的对应关系也可以存储在第一设备中，第一设备可以根据业务的ID自行查询确定对应的设备，在这种情况下，第三设备可以仅作为转发设备，无需根据第一信息确定第二设备，或者在这种情况下，第三设备也可以起到如下介绍的过滤作用。
或者，第三设备可以起到过滤的作用。例如，第三设备根据第一信息，确定所述第一信息对应的第二设备是否符合预设的规则，如果第二设备符合预设的规则，则第三设备可以将第一信息和第一证书转发给第二设备，否则，第三设备不将第一信息和第一证书转发 给第二设备，例如第三设备可以丢弃第一信息和第一证书，且流程结束。通过这种方式，减少了第一设备误发信息的可能性，提高了通信的安全性。
第三设备的功能可以有多种，如上的第三方面只是以第三设备的查询功能为例。
结合第三方面，在第三方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
例如，第一信息可以包括第一业务的标识，也就是说，所述的认证过程可以与第一业务相关。从而，在业务不同时，对应的第二设备可以有所不同，使得认证过程能够与业务相结合，服务于业务，从而使得业务的安全性更高。或者，第一信息还可以包括其他的内容，例如，第一信息可以包括第二设备的信息，第二设备的信息例如包括第二设备的标识(例如第二设备的ID)，或者包括第二设备的IP地址等。或者，第一信息还可以包括其他的信息。
结合第三方面，在第三方面的一种可能的实施方式中，所述第一信息为第一业务的标识，根据所述第一信息，查找对应的所述第二设备，包括：根据所述第一业务的标识，查找与所述第一业务相关的所述第二设备。
例如，第一业务的标识为第一业务的ID，第一设备只是将第一业务的ID和第一证书发送给第三设备。第三设备例如存储了业务的ID和设备之间的对应关系，例如该对应关系可以是业务的ID和设备的地址之间的对应关系，设备的地址例如为设备的IP地址。该对应关系是用于指示相应的业务应该由哪些设备执行，或者用于指示要执行相应的业务，需与哪些设备进行认证，或者说，是指示与业务关联的设备。例如第三设备查询该对应关系，确定第一业务的ID所对应的设备，例如包括第二设备，那么第三设备就可以将第一证书和第一信息转发给第二设备。在这种情况下，在该对应关系中，可能一个业务的ID会对应一个或多个设备，例如第一业务的ID可能只对应第二设备，或者也可能对应多个设备，这多个设备中包括第二设备。那么，第三设备可以只将第一信息和第一证书等转发给第一业务的ID所对应的部分设备，例如只转发给第二设备，或者，第三设备也可以将第一信息和第一证书等转发给第一业务的ID所对应的全部的设备。
结合第三方面，在第三方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
第一证书可以不包括第一证书的主题属性信息，或者，也可以将主题属性信息称为应用场景信息。设备证书可以只用于设备间的认证，不用作其它场景的认证，体现了设备证书的专属性，有利于保障系统的安全。而且通过本申请实施例提供的方案，也能减少设备证书的大小。
结合第三方面，在第三方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：所述第一证书的版本信息，所述第一证书的签名者信息，所述第一证书的主题信息，所述第一证书的有效性信息，或，所述第一证书的签名信息。
例如，第一证书包括第一证书的版本信息；或者，第一证书包括第一证书的签名者信息和第一证书的主题信息；或者，第一证书包括第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息；或者，第一证书包括第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息，等等。
第四方面，提供第四种设备认证方法，该方法包括：第二设备对第一设备认证失败；所述第二设备根据第一业务，确定第一执行策略，所述认证对应于所述第一业务；所述第 二设备将所述第一执行策略发送给所述第一设备，或，所述第二设备执行所述第一执行策略。
该第四方面的方法可由第四通信装置执行，第四通信装置可以是通信设备或能够支持通信设备实现该方法所需的功能的装置，例如芯片系统。示例性地，通信设备为车载装置。在下文的描述中，以第三通信装置是第三设备为例。
在本申请实施例中，如果第二设备对第一设备认证失败，因为该认证是与第一业务相关的认证过程，因此第二设备在确定执行策略时，所确定的执行策略可以是与第一业务相关的执行策略，或者说，可以根据第一业务确定执行策略，从而使得所确定的执行策略更为符合业务的需求。
结合第四方面，在第四方面的一种可能的实施方式中，所述第一执行策略包括，设备停止工作，或，设备停止使用所述设备的部分功能。
第一执行策略例如包括，设备停止工作，或设备停止使用该设备的部分功能。以第二设备来说，第一执行策略可以包括，第二设备停止工作，或第二设备停止使用第二设备的部分功能。这里的部分功能，可以是与第一业务相关的功能。例如第二设备为MDC，第一业务是自动驾驶功能，那么MDC停止使用MDC的部分功能，例如是停止使用与自动驾驶功能相关的功能。
结合第四方面，在第四方面的一种可能的实施方式中，所述方法还包括：
所述第二设备接收来自所述第一设备的第一信息和第一证书，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；
所述第二设备根据所述第一设备的第三证书，验证所述第一证书是否正确；
当所述第一证书正确时，所述第二设备生成第一随机数；
所述第二设备将所述第一随机数发送给所述第一设备；
所述第二设备接收来自所述第一设备的第一签名；
所述第二设备根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
这里介绍的是第二设备对第一设备进行认证的一种方式。关于第二设备如何认证第一设备，可参考如前的第一方面或第一方面的各种可能的实施方式、第二方面或第二方面的各种可能的实施方式、第三方面或第三方面的各种可能的实施方式、或第四方面或第四方面的各种可能的实施方式的相关介绍。
结合第四方面，在第四方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
第一证书可以不包括第一证书的主题属性信息，或者，也可以将主题属性信息称为应用场景信息。设备证书可以只用于设备间的认证，不用作其它场景的认证，体现了设备证书的专属性，有利于保障系统的安全。而且通过本申请实施例提供的方案，也能减少设备证书的大小。
结合第四方面，在第四方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：所述第一证书的版本信息，所述第一证书的签名者信息，所述第一证书的主题信息，所述第一证书的有效性信息，或，所述第一证书的签名信息。
例如，第一证书包括第一证书的版本信息；或者，第一证书包括第一证书的签名者信息和第一证书的主题信息；或者，第一证书包括第一证书的主题信息，第一证书的有效性 信息，和第一证书的签名信息；或者，第一证书包括第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息，等等。
第五方面，提供一种通信装置，例如该通信装置为如前所述的第一通信装置。所述第一通信装置用于执行上述第一方面或第一方面的任一可能的实现方式中的方法。具体地，所述第一通信装置可以包括用于执行第一方面或第一方面的任一可能的实现方式中的方法的模块，例如包括处理模块和收发模块。其中，收发模块可以是指一个功能模块，该功能模块既能完成接收信息的功能也能完成发送信息的功能。或者，收发模块可以是发送模块和接收模块的统称，发送模块用于完成发送信息的功能，接收模块用于完成接收信息的功能。示例性地，所述第一通信装置为车载装置。其中，
所述收发模块，用于将第一信息和第一证书发送给第二设备，所述第一信息用于指示所述第二设备，所述第一证书为所述第一通信装置的设备证书；
所述收发模块，还用于接收来自所述第二设备的第一随机数；
所述处理模块，用于采用第一私钥，根据所述第一随机数和第一标识，得到第一签名，所述第一标识为所述第一通信装置的标识；
所述收发模块，还用于将所述第一签名发送给第二设备，所述第一签名用于对所述第一通信装置进行认证。
结合第五方面，在第五方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
结合第五方面，在第五方面的一种可能的实施方式中，
所述处理模块，还用于生成第二随机数；
所述收发模块，还用于将所述第二随机数发送给所述第二设备。
结合第五方面，在第五方面的一种可能的实施方式中，
所述收发模块，还用于接收来自所述第二设备的第二签名和第二标识，所述第二标识为所述第二设备的标识；
所述处理模块，还用于根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证。
结合第五方面，在第五方面的一种可能的实施方式中，所述处理模块用于通过如下方式根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证：
采用第二公钥，对所述第二签名、所述第二随机数和所述第二标识进行验签，得到返回的结果，当所述返回的结果指示验签通过时，确定对所述第二设备认证成功，否则，当所述返回的结果指示验签未通过时，确定对所述第二设备认证失败。
结合第五方面，在第五方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
结合第五方面，在第五方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
结合第五方面，在第五方面的一种可能的实施方式中，
所述收发模块，还用于接收来自所述第二设备的指示信息，所述指示信息用于指示对所述第一通信装置认证失败，或，用于指示所述第一通信装置停止工作或停止使用所述第一通信装置的部分功能；
所述处理模块，还用于令所述第一通信装置停止工作，或停止使用所述第一通信装置的部分功能。
关于第五方面或第五方面的各种可能的实施方式所带来的技术效果，可参考对于第一方面或第一方面的各种可能的实施方式的技术效果的介绍。
第六方面，提供一种通信装置，例如该通信装置为如前所述的第二通信装置。所述第二通信装置用于执行上述第二方面或第二方面的任一可能的实现方式中的方法。具体地，所述第二通信装置可以包括用于执行第二方面或第二方面的任一可能的实现方式中的方法的模块，例如包括处理模块和收发模块。其中，收发模块可以是指一个功能模块，该功能模块既能完成接收信息的功能也能完成发送信息的功能。或者，收发模块可以是发送模块和接收模块的统称，发送模块用于完成发送信息的功能，接收模块用于完成接收信息的功能。示例性地，所述第二通信装置为车载装置。其中，
所述收发模块，用于接收来自第一设备的第一信息和第一证书，所述第一信息用于指示所述第二通信装置，所述第一证书为所述第一设备的设备证书；
所述处理模块，用于根据所述第一设备的根证书或二级证书，验证所述第一证书是否正确；
所述处理模块，还用于当所述第一证书正确时，生成第一随机数；
所述收发模块，还用于将所述第一随机数发送给所述第一设备；
所述收发模块，还用于接收来自所述第一设备的第一签名；
所述处理模块，还用于根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
结合第六方面，在第六方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
结合第六方面，在第六方面的一种可能的实施方式中，所述处理模块用于通过如下方式根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证：
采用第一公钥，对所述第一签名、所述第一随机数和所述第一标识进行验签，得到返回的结果，当所述返回的结果指示验签通过时，确定对所述第一设备认证成功，否则，当所述返回的结果指示验签未通过时，确定对所述第一设备认证失败。
结合第六方面，在第六方面的一种可能的实施方式中，
所述收发模块，还用于接收来自所述第一设备的第二随机数；
所述处理模块，还用于当对所述第一设备认证通过时，采用第二私钥，根据所述第二随机数和所述第二标识生成第二签名；
所述收发模块，还用于将所述第二签名和第二标识发送给所述第一设备，所述第二签名用于对所述第二通信装置进行认证，所述第二标识为所述第二通信装置的标识。
结合第六方面，在第六方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
结合第六方面，在第六方面的一种可能的实施方式中，所述第一证书包括如下的一种 信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
结合第六方面，在第六方面的一种可能的实施方式中，
所述收发模块，还用于当所述处理模块对所述第一设备认证失败时，向所述第一设备发送指示信息，所述指示信息用于指示对所述第一设备认证失败，或，用于指示所述第一设备停止工作或停止使用所述第一设备的部分功能；或，
所述处理模块，还用于当对所述第一设备认证失败时，令所述第二通信装置停止工作或停止使用所述第二通信装置的部分功能。
关于第六方面或第六方面的各种可能的实施方式所带来的技术效果，可参考对于第二方面或第二方面的各种可能的实施方式的技术效果的介绍。
第七方面，提供一种通信装置，例如该通信装置为如前所述的第三通信装置。所述第三通信装置用于执行上述第三方面或第三方面的任一可能的实现方式中的方法。具体地，所述第三通信装置可以包括用于执行第三方面或第三方面的任一可能的实现方式中的方法的模块，例如包括处理模块和收发模块。其中，收发模块可以是指一个功能模块，该功能模块既能完成接收信息的功能也能完成发送信息的功能。或者，收发模块可以是发送模块和接收模块的统称，发送模块用于完成发送信息的功能，接收模块用于完成接收信息的功能。示例性地，所述第三通信装置为车载装置。其中，
所述收发模块，用于接收来自第一设备的第一信息和第一证书，所述第一信息用于指示第二设备，所述第一证书为所述第一设备的设备证书；
所述处理模块，用于根据所述第一信息，查找对应的所述第二设备；
所述收发模块，还用于将所述第一信息和所述第一证书发送给所述第二设备，所述第一证书用于所述第二设备对所述第一设备进行认证。
结合第七方面，在第七方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
结合第七方面，在第七方面的一种可能的实施方式中，所述第一信息为第一业务的标识，所述处理模块用于通过如下方式根据所述第一信息，查找对应的所述第二设备：
根据所述第一业务的标识，查找与所述第一业务相关的所述第二设备。
结合第七方面，在第七方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
结合第七方面，在第七方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
关于第七方面或第七方面的各种可能的实施方式所带来的技术效果，可参考对于第三方面或第三方面的各种可能的实施方式的技术效果的介绍。
第八方面，提供一种通信装置，例如该通信装置为如前所述的第四通信装置。所述第四通信装置用于执行上述第四方面或第四方面的任一可能的实现方式中的方法。具体地，所述第四通信装置可以包括用于执行第四方面或第四方面的任一可能的实现方式中的方法的模块，例如包括处理模块和收发模块。其中，收发模块可以是指一个功能模块，该功能模块既能完成接收信息的功能也能完成发送信息的功能。或者，收发模块可以是发送模块和接收模块的统称，发送模块用于完成发送信息的功能，接收模块用于完成接收信息的功能。示例性地，所述第四通信装置为车载装置。其中，
所述处理模块，用于对第一设备认证失败；
所述处理模块，还用于根据第一业务，确定第一执行策略，所述认证对应于所述第一业务；
所述收发模块，用于将所述第一执行策略发送给所述第一设备，或，所述处理模块，还用于执行所述第一执行策略。
结合第八方面，在第八方面的一种可能的实施方式中，所述第一执行策略包括，设备停止工作，或，设备停止使用所述设备的部分功能。
结合第八方面，在第八方面的一种可能的实施方式中，
所述收发模块，还用于接收来自所述第一设备的第一信息和第一证书，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；
所述处理模块，还用于根据所述第一设备的第三证书，验证所述第一证书是否正确；
所述处理模块，还用于当所述第一证书正确时，生成第一随机数；
所述收发模块，还用于将所述第一随机数发送给所述第一设备；
所述收发模块，还用于接收来自所述第一设备的第一签名；
所述处理模块，还用于根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
结合第八方面，在第八方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
结合第八方面，在第八方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
关于第八方面或第八方面的各种可能的实施方式所带来的技术效果，可参考对于第四方面或第四方面的各种可能的实施方式的技术效果的介绍。
第九方面，提供一种通信装置，该通信装置例如为如前所述的第一通信装置。该第一通信装置包括处理器和收发器，处理器和收发器用于实现上述第一方面或第一方面的各种可能的设计所描述的方法。示例性地，所述第一通信装置为设置在通信设备中的芯片。其中，收发器例如通过通信设备中的天线、馈线和编解码器等实现，或者，如果所述第一通 信装置为设置在通信设备中的芯片，那么收发器例如为芯片中的通信接口，该通信接口与通信设备中的射频收发组件连接，以通过射频收发组件实现信息的收发。其中，收发器可以是指一个功能模块，该功能模块既能完成接收信息的功能也能完成发送信息的功能。或者，收发器可以是发送器和接收器的统称，发送器用于完成发送信息的功能，接收器用于完成接收信息的功能。示例性的，所述通信设备为车载装置。其中，
所述收发器，用于将第一信息和第一证书发送给第二设备，所述第一信息用于指示所述第二设备，所述第一证书为所述第一通信装置的设备证书；
所述收发器，还用于接收来自所述第二设备的第一随机数；
所述处理器，用于采用第一私钥，根据所述第一随机数和第一标识，得到第一签名，所述第一标识为所述第一通信装置的标识；
所述收发器，还用于将所述第一签名发送给第二设备，所述第一签名用于对所述第一通信装置进行认证。
结合第九方面，在第九方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
结合第九方面，在第九方面的一种可能的实施方式中，
所述处理器，还用于生成第二随机数；
所述收发器，还用于将所述第二随机数发送给所述第二设备。
结合第九方面，在第九方面的一种可能的实施方式中，
所述收发器，还用于接收来自所述第二设备的第二签名和第二标识，所述第二标识为所述第二设备的标识；
所述处理器，还用于根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证。
结合第九方面，在第九方面的一种可能的实施方式中，所述处理器用于通过如下方式根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证：
采用第二公钥，对所述第二签名、所述第二随机数和所述第二标识进行验签，得到返回的结果，当所述返回的结果指示验签通过时，确定对所述第二设备认证成功，否则，当所述返回的结果指示验签未通过时，确定对所述第二设备认证失败。
结合第九方面，在第九方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
结合第九方面，在第九方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
结合第九方面，在第九方面的一种可能的实施方式中，
所述收发器，还用于接收来自所述第二设备的指示信息，所述指示信息用于指示对所述第一通信装置认证失败，或，用于指示所述第一通信装置停止工作或停止使用所述第一通信装置的部分功能；
所述处理器，还用于令所述第一通信装置停止工作，或停止使用所述第一通信装置的部分功能。
关于第九方面或第九方面的各种可能的实施方式所带来的技术效果，可参考对于第一方面或第一方面的各种可能的实施方式的技术效果的介绍。
第十方面，提供一种通信装置，该通信装置例如为如前所述的第二通信装置。该第二通信装置包括处理器和收发器，处理器和收发器用于实现上述第二方面或第二方面的各种可能的设计所描述的方法。示例性地，所述第二通信装置为设置在通信设备中的芯片。其中，收发器例如通过通信设备中的天线、馈线和编解码器等实现，或者，如果所述第二通信装置为设置在通信设备中的芯片，那么收发器例如为芯片中的通信接口，该通信接口与通信设备中的射频收发组件连接，以通过射频收发组件实现信息的收发。其中，收发器可以是指一个功能模块，该功能模块既能完成接收信息的功能也能完成发送信息的功能。或者，收发器可以是发送器和接收器的统称，发送器用于完成发送信息的功能，接收器用于完成接收信息的功能。示例性的，所述通信设备为车载装置。其中，
所述收发器，用于接收来自第一设备的第一信息和第一证书，所述第一信息用于指示所述第二通信装置，所述第一证书为所述第一设备的设备证书；
所述处理器，用于根据所述第一设备的根证书或二级证书，验证所述第一证书是否正确；
所述处理器，还用于当所述第一证书正确时，生成第一随机数；
所述收发器，还用于将所述第一随机数发送给所述第一设备；
所述收发器，还用于接收来自所述第一设备的第一签名；
所述处理器，还用于根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
结合第十方面，在第十方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
结合第十方面，在第十方面的一种可能的实施方式中，所述处理器用于通过如下方式根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证：
采用第一公钥，对所述第一签名、所述第一随机数和所述第一标识进行验签，得到返回的结果，当所述返回的结果指示验签通过时，确定对所述第一设备认证成功，否则，当所述返回的结果指示验签未通过时，确定对所述第一设备认证失败。
结合第十方面，在第十方面的一种可能的实施方式中，
所述收发器，还用于接收来自所述第一设备的第二随机数；
所述处理器，还用于当对所述第一设备认证通过时，采用第二私钥，根据所述第二随机数和所述第二标识生成第二签名；
所述收发器，还用于将所述第二签名和第二标识发送给所述第一设备，所述第二签名用于对所述第二通信装置进行认证，所述第二标识为所述第二通信装置的标识。
结合第十方面，在第十方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
结合第十方面，在第十方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
结合第十方面，在第十方面的一种可能的实施方式中，
所述收发器，还用于当所述处理器对所述第一设备认证失败时，向所述第一设备发送指示信息，所述指示信息用于指示对所述第一设备认证失败，或，用于指示所述第一设备停止工作或停止使用所述第一设备的部分功能；或，
所述处理器，还用于当对所述第一设备认证失败时，令所述第二通信装置停止工作或停止使用所述第二通信装置的部分功能。
关于第十方面或第十方面的各种可能的实施方式所带来的技术效果，可参考对于第二方面或第二方面的各种可能的实施方式的技术效果的介绍。
第十一方面，提供一种通信装置，该通信装置例如为如前所述的第三通信装置。该第三通信装置包括处理器和收发器，处理器和收发器用于实现上述第三方面或第三方面的各种可能的设计所描述的方法。示例性地，所述第三通信装置为设置在通信设备中的芯片。其中，收发器例如通过通信设备中的天线、馈线和编解码器等实现，或者，如果所述第三通信装置为设置在通信设备中的芯片，那么收发器例如为芯片中的通信接口，该通信接口与通信设备中的射频收发组件连接，以通过射频收发组件实现信息的收发。其中，收发器可以是指一个功能模块，该功能模块既能完成接收信息的功能也能完成发送信息的功能。或者，收发器可以是发送器和接收器的统称，发送器用于完成发送信息的功能，接收器用于完成接收信息的功能。示例性的，所述通信设备为车载装置。其中，
所述收发器，用于接收来自第一设备的第一信息和第一证书，所述第一信息用于指示第二设备，所述第一证书为所述第一设备的设备证书；
所述处理器，用于根据所述第一信息，查找对应的所述第二设备；
所述收发器，还用于将所述第一信息和所述第一证书发送给所述第二设备，所述第一证书用于所述第二设备对所述第一设备进行认证。
结合第十一方面，在第十一方面的一种可能的实施方式中，所述第一信息包括第一业务的标识。
结合第十一方面，在第十一方面的一种可能的实施方式中，所述第一信息为第一业务的标识，所述处理器用于通过如下方式根据所述第一信息，查找对应的所述第二设备：
根据所述第一业务的标识，查找与所述第一业务相关的所述第二设备。
结合第十一方面，在第十一方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
结合第十一方面，在第十一方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
关于第十一方面或第十一方面的各种可能的实施方式所带来的技术效果，可参考对于第三方面或第三方面的各种可能的实施方式的技术效果的介绍。
第十二方面，提供一种通信装置，该通信装置例如为如前所述的第四通信装置。该第四通信装置包括处理器和收发器，处理器和收发器用于实现上述第四方面或第四方面的各种可能的设计所描述的方法。示例性地，所述第四通信装置为设置在通信设备中的芯片。其中，收发器例如通过通信设备中的天线、馈线和编解码器等实现，或者，如果所述第四通信装置为设置在通信设备中的芯片，那么收发器例如为芯片中的通信接口，该通信接口与通信设备中的射频收发组件连接，以通过射频收发组件实现信息的收发。其中，收发器可以是指一个功能模块，该功能模块既能完成接收信息的功能也能完成发送信息的功能。或者，收发器可以是发送器和接收器的统称，发送器用于完成发送信息的功能，接收器用于完成接收信息的功能。示例性的，所述通信设备为车载装置。其中，
所述处理器，用于对第一设备认证失败；
所述处理器，还用于根据第一业务，确定第一执行策略，所述认证对应于所述第一业务；
所述收发器，用于将所述第一执行策略发送给所述第一设备，或，所述处理器，还用于执行所述第一执行策略。
结合第十二方面，在第十二方面的一种可能的实施方式中，所述第一执行策略包括，设备停止工作，或，设备停止使用所述设备的部分功能。
结合第十二方面，在第十二方面的一种可能的实施方式中，
所述收发器，还用于接收来自所述第一设备的第一信息和第一证书，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；
所述处理器，还用于根据所述第一设备的第三证书，验证所述第一证书是否正确；
所述处理器，还用于当所述第一证书正确时，生成第一随机数；
所述收发器，还用于将所述第一随机数发送给所述第一设备；
所述收发器，还用于接收来自所述第一设备的第一签名；
所述处理器，还用于根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
结合第十二方面，在第十二方面的一种可能的实施方式中，所述第一证书不包括所述第一证书的主题属性信息。
结合第十二方面，在第十二方面的一种可能的实施方式中，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
关于第十二方面或第十二方面的各种可能的实施方式所带来的技术效果，可参考对于第四方面或第四方面的各种可能的实施方式的技术效果的介绍。
第十三方面，提供一种通信装置。该通信装置可以为上述方法设计中的第一通信装置。示例性地，所述第一通信装置为设置在通信设备中的芯片。示例性地，通信设备为车载装 置。该第一通信装置可以包括：通信接口，用于与其他装置或设备通信；以及处理器，处理器与通信接口耦合。该通信接口可以是该通信装置中的收发器，例如通过所述通信装置中的天线、馈线和编解码器等实现，或者，如果该通信装置为设置在通信设备中的芯片，则通信接口可以是该芯片的输入/输出接口，例如输入/输出管脚等。
可选的，第一通信装置还可以包括存储器，用于存储计算机可执行程序代码。存储器所存储的程序代码包括指令。当处理器执行所述指令时，使第一通信装置执行上述第一方面或第一方面的任意一种可能的实施方式中的方法。或者，第一通信装置也可以不包括存储器，例如，处理器可以执行外部的存储器所存储的指令，使第一通信装置执行上述第一方面或第一方面的任意一种可能的实施方式中的方法。
第十四方面，提供一种通信装置。该通信装置可以为上述方法设计中的第二通信装置。示例性地，所述第二通信装置为设置在通信设备中的芯片。示例性地，通信设备为车载装置。该第二通信装置可以包括：通信接口，用于与其他装置或设备通信；以及处理器，处理器与通信接口耦合。该通信接口可以是该通信装置中的收发器，例如通过所述通信装置中的天线、馈线和编解码器等实现，或者，如果该通信装置为设置在通信设备中的芯片，则通信接口可以是该芯片的输入/输出接口，例如输入/输出管脚等。
可选的，第二通信装置还可以包括存储器，用于存储计算机可执行程序代码。存储器所存储的程序代码包括指令。当处理器执行所述指令时，使第二通信装置执行上述第二方面或第二方面的任意一种可能的实施方式中的方法。或者，第二通信装置也可以不包括存储器，例如，处理器可以执行外部的存储器所存储的指令，使第二通信装置执行上述第二方面或第二方面的任意一种可能的实施方式中的方法。
第十五方面，提供一种通信装置。该通信装置可以为上述方法设计中的第三通信装置。示例性地，所述第三通信装置为设置在通信设备中的芯片。示例性地，通信设备为车载装置。该第三通信装置可以包括：通信接口，用于与其他装置或设备通信；以及处理器，处理器与通信接口耦合。该通信接口可以是该通信装置中的收发器，例如通过所述通信装置中的天线、馈线和编解码器等实现，或者，如果该通信装置为设置在通信设备中的芯片，则通信接口可以是该芯片的输入/输出接口，例如输入/输出管脚等。
可选的，第三通信装置还可以包括存储器，用于存储计算机可执行程序代码。存储器所存储的程序代码包括指令。当处理器执行所述指令时，使第三通信装置执行上述第三方面或第三方面的任意一种可能的实施方式中的方法。或者，第三通信装置也可以不包括存储器，例如，处理器可以执行外部的存储器所存储的指令，使第三通信装置执行上述第三方面或第三方面的任意一种可能的实施方式中的方法。
第十六方面，提供一种通信装置。该通信装置可以为上述方法设计中的第四通信装置。示例性地，所述第四通信装置为设置在通信设备中的芯片。示例性地，通信设备为车载装置。该第四通信装置可以包括：通信接口，用于与其他装置或设备通信；以及处理器，处理器与通信接口耦合。该通信接口可以是该通信装置中的收发器，例如通过所述通信装置中的天线、馈线和编解码器等实现，或者，如果该通信装置为设置在通信设备中的芯片，则通信接口可以是该芯片的输入/输出接口，例如输入/输出管脚等。
可选的，第四通信装置还可以包括存储器，用于存储计算机可执行程序代码。存储器所存储的程序代码包括指令。当处理器执行所述指令时，使第四通信装置执行上述第四方面或第四方面的任意一种可能的实施方式中的方法。或者，第四通信装置也可以不包括存 储器，例如，处理器可以执行外部的存储器所存储的指令，使第四通信装置执行上述第四方面或第四方面的任意一种可能的实施方式中的方法。
第十七方面，提供一种通信系统，该通信系统包括第五方面所述的通信装置、第九方面所述的通信装置、或第十三方面所述的通信装置，以及包括第六方面所述的通信装置、第十方面所述的通信装置、或第十四方面所述的通信装置。
结合第十七方面，在第十七方面的一种可能的实施方式中，该通信系统还可以包括第七方面所述的通信装置、第十一方面所述的通信装置、或第十五方面所述的通信装置。
第十八方面，提供一种通信系统，该通信系统包括第八方面所述的通信装置、第十二方面所述的通信装置、或第十六方面所述的通信装置。
结合第十八方面，在第十八方面的一种可能的实施方式中，该通信系统还可以包括第五方面所述的通信装置、第九方面所述的通信装置、或第十三方面所述的通信装置。
结合第十八方面，在第十八方面的一种可能的实施方式中，第六方面所述的通信装置、第十方面所述的通信装置、或第十四方面所述的通信装置。
第十九方面，提供一种计算机存储介质，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述第一方面或第一方面的任意一种可能的实施方式中所述的方法。
第二十方面，提供一种计算机存储介质，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述第二方面或第一方面的任意一种可能的实施方式中所述的方法。
第二十一方面，提供一种计算机存储介质，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述第三方面或第三方面的任意一种可能的实施方式中所述的方法。
第二十二方面，提供一种计算机存储介质，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述第四方面或第四方面的任意一种可能的实施方式中所述的方法。
第二十三方面，提供一种包含指令的计算机程序产品，所述计算机程序产品用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述第一方面或第一方面的任意一种可能的实施方式中所述的方法。
第二十四方面，提供一种包含指令的计算机程序产品，所述计算机程序产品用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述第二方面或第而方面的任意一种可能的实施方式中所述的方法。
第二十五方面，提供一种包含指令的计算机程序产品，所述计算机程序产品用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述第三方面或第三方面的任意一种可能的实施方式中所述的方法。
第二十六方面，提供一种包含指令的计算机程序产品，所述计算机程序产品用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述第四方面或第四方面的任意一种可能的实施方式中所述的方法。
在本申请实施例中，设备间的认证不依赖设备之间的层级关系，例如，即使第一设备是第一层级的设备，第二设备是第三层级的设备，第一设备和第二设备之间也能进行认证，这样就实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式 因为无需一个中间节点对多个节点进行认证，减轻了设备的负担，减少了对中间节点的依赖，提高了系统的可靠性。
附图说明
图1为本申请实施例所应用的一种网络架构的示意图；
图2为本申请实施例提供的一种设备认证方法的流程图；
图3为本申请实施例提供的一种设备认证方法的流程图；
图4为本申请实施例提供的一种设备认证方法的流程图；
图5为本申请实施例提供的一种设备认证方法的流程图；
图6为本申请实施例提供的MDC与T-Box进行双向认证的方法的流程图；
图7为本申请实施例提供的VCU对MDC进行认证的方法的流程图；
图8为本申请实施例提供的HMI与MDC进行双向认证的方法的流程图；
图9为本申请实施例提供的MDC对sensor进行认证的方法的流程图；
图10为本申请实施例提供的BCM对PEPS进行认证的方法的流程图；
图11为本申请实施例提供的VCU对BCM进行认证的方法的流程图；
图12为本申请实施例提供的VCU对OBC进行认证的方法的流程图；
图13为本申请实施例提供的一种设备认证方法的流程图；
图14为本申请实施例提供的一种第一设备的示意性框图；
图15为本申请实施例提供的一种第一设备的另一示意性框图；
图16为本申请实施例提供的第一种第二设备的示意性框图；
图17为本申请实施例提供的第一种第二设备的另一示意性框图；
图18为本申请实施例提供的一种第三设备的示意性框图；
图19为本申请实施例提供的一种第三设备的另一示意性框图；
图20为本申请实施例提供的第二种第二设备的示意性框图；
图21为本申请实施例提供的第二种第二设备的另一示意性框图；
图22为本申请实施例提供的通信装置的示意性框图；
图23为本申请实施例提供的通信装置的另一示意性框图；
图24为本申请实施例提供的通信装置的再一示意性框图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施例作进一步地详细描述。
1)车载设备，放置或安装在车辆上的设备都可以认为是车载设备。例如对于能够执行自动驾驶功能的车辆来说，一般依赖ADAS系统提供信息进行驾驶决策，而ADAS包括很多传感器，例如照相机、毫米波雷达、超声波雷达或LiDAR等，这些传感器都可以认为是车载设备。例如，一辆车的车内网络可以包括多个电子控制单元(electronic control unit，ECU)，这些ECU都可以认为是车载设备。
例如，一种车载设备为车载单元(on board unit，OBU)，一般安装在车辆上，在电子不停车收费系统(electronic toll collection，ETC)系统中，路边架设路侧单元(road side unit， RSU)，OBU可以与RSU进行通信，例如可以通过微波来通信。在车辆通过RSU时，OBU和RSU之间可以使用微波进行通信。在ETC系统中，OBU采用专用短距离通信(dedicated short range communications，DSRC)技术，与RSU建立微波通信链路，在车辆行进的途中，在不停车的情况下，可以实现车辆的身份识别或电子扣费等过程。
或者，如下介绍的各种终端设备，如果位于车辆上(例如放置在车辆内或安装在车辆内)，都可以认为是车载终端设备，或者称为车载设备。
终端设备，包括向用户提供语音和/或数据连通性的设备，例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网(radio access network，RAN)与核心网进行通信，与RAN交换语音和/或数据。该终端设备可以包括用户设备(user equipment，UE)、无线终端设备、移动终端设备、设备到设备通信(device-to-device，D2D)终端设备、V2X终端设备、机器到机器/机器类通信(machine-to-machine/machine-type communications，M2M/MTC)终端设备、物联网(internet of things，IoT)终端设备、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、远程站(remote station)、接入点(access point，AP)、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、或用户装备(user device)等。例如，可以包括移动电话(或称为“蜂窝”电话)，具有移动终端设备的计算机，便携式、袖珍式、手持式、计算机内置的移动装置等。例如，个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、等设备。还包括受限设备，例如功耗较低的设备，或存储能力有限的设备，或计算能力有限的设备等。例如包括条码、射频识别(radio frequency identification，RFID)、传感器、全球定位系统(global positioning system，GPS)、激光扫描器等信息传感设备。
作为示例而非限定，在本申请实施例中，放置或安装在车辆上的车载设备还可以包括可穿戴设备。可穿戴设备也可以称为穿戴式智能设备或智能穿戴式设备等，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能头盔、智能首饰等。
2)本申请实施例中的术语“系统”和“网络”可被互换使用。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
以及，除非有相反的说明，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。例如，第一消 息和第二消息，只是为了区分不同的消息，而并不是表示这两种消息的优先级、发送顺序或者重要程度等的不同。
如上介绍了本申请实施例涉及的一些概念，下面介绍本申请实施例的技术特征。
随着汽车向智能化、网联化的发展，汽车的功能不断增加，车辆的联网不仅让车厂可以了解、跟踪车辆的情况，同时也给用户的日常生活带来了更多的便利。然而，非法用户通过网络深入联网汽车系统，对车辆进行操作、控制，会给车辆安全带来极大的威胁。为此，需要采取一定的措施，以保证车辆安装的终端设备是合法的设备，防止安装非授权的设备对车载数据的监听以及发送恶意、虚假的指令、数据对车辆功能的干扰、破坏。
目前采取的一种措施是，可以对车载设备进行认证。目前将车载设备划分为多个层级，实行层级认证机制。例如，可以将一个车辆所包括的除了网关(gateway)之外的全部的车载设备或部分的车载设备划分成若干个域(domain)，每个域包括一个或多个车载设备，每个域有一个域管理员(domain manager，DM)，该域管理员可以作为域控制器。域内设备可以通过域控制器与网关通信。例如，网关为第一层级的设备，域控制器为第二层级的设备，域内设备为第三层级的设备。第一层级的车载设备可以对第二层级的车载设备进行认证，如果第二层级的车载设备认证通过，则第二层级的车载设备可以对第三层级的车载设备进行认证。例如，网关可以对域控制器进行认证，如果域控制器认证通过，则该域控制器可以对该域控制器所在的域内的域内设备进行认证。
这种认证措施会较为依赖中间节点，例如域控制器就可以视为中间节点。如果网关对域控制器认证失败，那么作为不安全设备的域控制器无法对域内设备进行认证，导致大量的域内设备得不到认证。
可见，在这种认证机制下，可能导致一些车载设备得不到认证，安全隐患较大。
鉴于此，提供本申请实施例的技术方案。在本申请实施例中，第一信息用于指示第二设备，例如，第一信息可能是第一业务的标识，或者是第二设备的地址等，只要第一设备将第一信息发送给第二设备，第二设备就可以对第一设备进行认证，不依赖设备间的层级关系，例如，即使第一设备是第一层级的设备，第二设备是第三层级的设备，第一设备和第二设备之间也能进行认证，这样就实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式因为无需一个中间节点对多个节点进行认证，减轻了设备的负担。通过本申请实施例的技术方案，实现了设备之间端到端的认证，减少了对于中间节点的依赖，使得更多的车载设备能够得到认证，提高了车载设备的安全性。本申请实施例提供的认证方案具有一定的韧性。此外，本申请实施例提供的端到端的认证方案与整车的架构无关，兼容性比较好，可以适用于现在的汽车架构，也可以适用于未来的汽车架构。
下面介绍本申请实施例所应用的网络架构。请参考图1，为本申请实施例所应用的一种网络架构。
图1所示的，是一个车辆所包括的全部的车载设备或部分的车载设备。这些车载设备可以被分成若干个域，每个域包括一个或多个车载设备，每个域有一个域管理员，域管理员也可以称为域控制器。例如，移动数据中心(mobile data center，MDC)和一个或多个传感器(sensor)以及全球定位系统(global positioning system，GPS)等属于一个域，MDC是这个域的域控制器。车辆控制单元(vehicle control unit，VCU)和一个或多个电子控制单元(electronic control unit，ECU)以及无线电能传输(wireless power transmission，WPT)等属于一个域，VCU是这个域的域控制器。人机接口(human machine interface，HMI)和 一个或多个ECU等属于一个域，HMI是这个域的域控制器。车身控制模块(body control module，BCM)和一个或多个ECU、以及被动进入被动启动(passive entry passive start，PEPS)等属于一个域，BCM是这个域的域控制器。域控制器与网关连接，网关又连接了车载自动诊断系统(on-board diagnostics，OBD)和车载信息盒(telematics box，T-Box)等设备。例如，域控制器可以通过网关与T-Box等设备通信，域内设备可以通过域控制器与网关等设备通信。
图1是以网关作为主认证节点为例，实际上主认证节点不限于网关，还可以是其他车载设备。
在将车载设备划分为多个域时，划分因素可能有多种。例如可以根据车载设备所完成的功能来进行划分。例如有几个车载设备用于协同完成某种功能(例如，动力功能)，就可以将这几个车载设备划分为一个域。或者也可以按照其他因素来划分不同的域。而关于域控制器，例如随机选择域内的一个车载设备作为域控制器，或者也可以选择域内的有统筹管理功能的一个车载设备作为域控制器。
接下来结合附图介绍本申请实施例提供的技术方案。
本申请实施例提供一种设备认证方法，请参见图2，为该方法的流程图。在下文的介绍过程中，以该方法应用于图1所示的网络架构为例。另外，该方法可由三个通信装置(或者说，三种通信装置)执行，这三个通信装置例如为第一通信装置、第二通信装置和第三通信装置。其中，第一通信装置、第二通信装置或第三通信装置，可以是车载装置或能够支持车载装置实现该方法所需的功能的通信装置(例如芯片系统)，当然还可以是其他通信装置。且对于第一通信装置、第二通信装置和第三通信装置的实现方式均不做限制，例如这三个通信装置可以实现为相同的形式，例如均通过设备的形式实现，或者这三个通信装置也可以实现为不同的形式，例如第一通信装置通过设备的形式实现，第二通信装置通过芯片系统的方式实现，第三通信装置通过设备的形式实现，这三种通信装置也可以是三种不同的芯片，等等。
为了便于介绍，在下文中，以该方法由第一设备、第二设备和第三设备执行为例，也就是说，以第一通信装置是第一设备、第二通信装置是第二设备、第三通信装置是第三设备为例。例如，第一设备可以是待认证的设备，第二设备可以是除了网关和路由器之外的其他设备，或者是除了具有路由转发功能的实体之外的其他实体。另外，网关也可是指具有路由转发设备功能的实体装置。因为本实施例是以应用在图1所示的网络架构为例，因此，下文中所述的第一设备例如为图1所示的网络架构中的域控制器，下文中所述的第二设备例如为图1所示的网络架构中的T-Box或OBD，下文中所述的第三设备例如为图1所示的网络架构中的网关；或者，下文中所述的第一设备例如为图1所示的网络架构中的T-Box或OBD，下文中所述的第二设备例如为图1所示的网络架构中的域控制器，下文中所述的第三设备例如为图1所示的网络架构中的网关。
S201、第一设备将第一信息和第一证书发送给第二设备，第二设备接收来自第一设备的第一信息和第一证书。其中，第一信息用于指示第二设备，第一证书为第一设备的设备证书。
第一信息可以是用于认证的。第一信息可以包括第二设备的信息，第二设备的信息例如包括第二设备的IP地址，或者，第二设备的信息例如包括第二设备的ID，或者，第二设备的信息例如包括第二设备的IP地址和第二设备的ID，或者，第二设备的信息还可以 包括第二设备的其他信息。因此，第一信息可以指示第二设备。第一信息可以指示第二设备，或者，可以是第一信息和第二设备相关联，这里的相关联可以是业务之间的关联，也可以是由S201中的第一信息载体所包含的关联关系。
或者，第一信息也可以包括业务的标识，该标识可以指示认证的目标设备。例如根据该标识，通过查表(或查找对应的关系)可以确定认证的目标设备；或者根据该标识，无需通过查表等额外的操作，就可以确定该标识所指示的认证的目标设备。认证的目标设备，例如第二设备。例如，业务的标识为业务的身份号(ID)，该业务例如称为第一业务。第一业务可以是第一设备和第二设备即将进行的业务，例如，在第一设备和第二设备即将进行第一业务之前，第二设备先要对第一设备进行认证，因此可以认为，该业务标识指示的本次认证的目标设备是第二设备。
或者，第一信息也可以包括响应于所输入的信息的信息，例如包括响应于用户输入的信息的信息，或者说，第一信息包括与用户的输入相关的信息。例如，第一信息是响应于输入信息的信息，该输入信息例如是用户输入的信息。例如，用户想要进行第一业务，则用户按下了某个或某些按钮或按键，这就相当于输入了信息，或者用户在人机交互界面或其他交互界面进行了操作，相当于输入了信息。第一消息也可以是响应于某些判断条件或触发。第一设备接收了来自用户输入的信息后，就可以启动认证过程，以便执行第一业务。
或者，第一信息也可以通过隐式方式指示第二设备，或者第一信息包括类似于上述描述的其它信息。
或者，第一信息也可以包括其他设备或者第一设备自身提供的其它触发条件的标识。例如，第一信息包括响应于其他设备周期上报的测量结果、触发标识、或信息报告的信息，或者可以包括第一设备或其他设备或整车的启动或重启、软硬件更新或即插即用的设备的引入的信息。
或者，第一信息也可以包括响应于其他事件的信息，其他事件例如为第一设备上电的事件，或者第一设备接收了来自其他设备的信息的事件，等等。例如，用户想要进行第一业务，则用户按下了某个或某些按钮，这就相当于输入了信息，而接收用户输入的信息的是其他设备。其他设备接收了用户输入的信息后，可以通知第一设备启动认证过程，则第一设备就可以执行S201。
或者，第一信息也可以包括报文ID信息。
第一证书可以是第一设备的设备证书。例如，为了保证安全性，可以在设备生产完成后，向设备写入该设备的身份信息。例如，在设备生产完成后，厂商可以对设备进行测试，在测试合格后，该设备的生产商或者原始设备制造商(original equipment manufacturer，OEM)可以向该设备写入该设备的身份信息。设备的身份信息例如包括如下的一项或多项：该设备的根证书或二级证书，该设备的设备证书，该设备的型号，该设备使用的私钥，或，该设备的标识。例如，设备的身份信息包括该设备的根证书和设备证书；或者，设备的身份信息包括该设备的标识；或者，设备的身份信息包括该设备的二级证书、该设备的私钥和该设备的标识；或者，设备的身份信息包括该设备的根证书或二级证书，该设备的设备证书，该设备的私钥，该设备的型号，和该设备的标识，等等。
第一设备除了可以将第一信息和第一证书发送给第二设备之外，还可以将第一标识发送给第二设备，则第二设备可以接收来自第一设备的第一标识。第一标识为第一设备的标识，例如为第一设备的ID。
其中，第一设备和第二设备之间要通过第三设备进行信息转发，因此，第一设备实际上是将第一证书和第一信息发送给第三设备，由第三设备将第一证书和第一信息转发给第三设备，第二设备接收的是来自第三设备的第一证书和第一信息。但因为第一证书和第一信息是第一设备发送给第三设备的，因此也可以认为第二设备接收的是来自第一设备的第一证书和第一信息。如果第一设备还要将第一标识发送给第二设备，则第一标识也是要通过第三设备转发给第二设备。
第三设备可以仅仅起到转发功能，即，第三设备不对来自第一设备的信息(例如第一信息和第一证书等)做任何处理，而是直接转发给第二设备。
或者，第三设备可以根据第一信息进行查询，以查找对应的第二设备。例如，第一信息为第一业务的ID，第一设备只是将第一业务的ID和第一证书发送给第三设备。第三设备例如存储了业务的ID和设备之间的对应关系，例如该对应关系可以是业务的ID和设备的地址之间的对应关系，设备的地址例如为设备的IP地址。该对应关系是用于指示相应的业务应该由哪些设备执行，或者用于指示要执行相应的业务，需与哪些设备进行认证，或者说，是指示与业务关联的设备。例如第三设备查询该对应关系，确定第一业务的ID所对应的设备，例如包括第二设备，那么第三设备就可以将第一证书和第一信息转发给第二设备。在这种情况下，在该对应关系中，可能一个业务的ID会对应一个或多个设备，例如第一业务的ID可能只对应第二设备，或者也可能对应多个设备，这多个设备中包括第二设备。那么，第三设备可以只将第一信息和第一证书等转发给第一业务的ID所对应的部分设备，例如只转发给第二设备，或者，第三设备也可以将第一信息和第一证书等转发给第一业务的ID所对应的全部的设备。当然，所述的对应关系也可以存储在第一设备中，第一设备可以根据业务的ID自行查询确定对应的设备，在这种情况下，第三设备可以仅作为转发设备，无需根据第一信息确定第二设备，或者在这种情况下，第三设备也可以起到如下介绍的过滤作用。
或者，第三设备可以起到过滤的作用。例如，第三设备根据第一信息，确定所述第一信息对应的第二设备是否符合预设的规则，如果第二设备符合预设的规则，则第三设备可以将第一信息和第一证书转发给第二设备，否则，第三设备不将第一信息和第一证书转发给第二设备，例如第三设备可以丢弃第一信息和第一证书，且流程结束。
例如，第一信息包括第一业务的ID和第二设备的标识，例如IP地址，第一设备将第一业务的ID、第二设备的IP地址和第一证书发送给第三设备。第三设备例如存储了所述的对应关系，该对应关系就可以认为是预设的规则。例如第三设备查询该对应关系，确定第一业务的ID所对应的设备，第三设备可以确定第一业务的ID所对应的设备中是否有第二设备的IP地址所对应的第二设备，如果有第二设备，则第二设备符合预设的规则，第三设备可以将第一业务的ID、第二设备的IP地址和第一证书等转发给第二设备，而如果第一业务的ID所对应的设备中没有第二设备，则第二设备不符合预设的规则，第三设备可以不将第一业务的ID、第二设备的IP地址和第一证书等转发给第二设备，从而保证信息安全。
或者，例如，第一信息包括第二设备的标识，例如IP地址，第一设备将第二设备的IP地址和第一证书发送给第三设备。第三设备例如存储了设备之间的关联关系，例如对于第一设备来说，可能在执行相应的业务时会与一些设备有所交互，那么第三设备可以存储第一设备和这些设备之间的关联关系，该对应关系就可以认为是预设的规则。例如第三设备 查询该关联关系，确定第一设备所对应的设备，第三设备可以确定第一设备所对应的设备中是否有第二设备的IP地址所对应的第二设备，如果有第二设备，则第二设备符合预设的规则，第三设备可以将第二设备的IP地址和第一证书等转发给第二设备，而如果第一设备所对应的设备中没有第二设备，则第二设备不符合预设的规则，第三设备可以不将第二设备的IP地址和第一证书等转发给第二设备，从而保证信息安全。
关于第一证书，可以包括如下的一种信息或如下多种信息的任意组合：第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，或，第一证书的签名信息。例如，第一证书包括第一证书的版本信息；或者，第一证书包括第一证书的签名者信息和第一证书的主题信息；或者，第一证书包括第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息；或者，第一证书包括第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息，等等。
另外，第一证书可以不包括第一证书的主题属性信息，或者，也可以将主题属性信息称为应用场景信息。设备证书可以只用于设备间的认证，不用作其它场景的认证，如安全启动或空中升级(over the air，OTA)认证等，体现了设备证书的专属性，不因其它应用场景的第三证书私钥的泄露影响设备证书签名的有效性，有利于保障不同设备间通信及系统的安全。而且通过本申请实施例提供的方案，也能减少设备证书的大小。
以第一证书包括第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息为例，对于第一证书所包括的内容的一种示例可参考表1。
表1
Figure PCTCN2020092176-appb-000001
作为一种可选的方式，如果第二设备为除网关或路由器之外的其它设备，或者第二设备为除了具有路由转发功能的实体之外的其他实体，则第一设备也可以不向第二设备发送第一信息，也就是说，S201中，第一设备可以向第二设备发送第一证书，而不必向第二设备发送第一信息。
S202、第二设备向第一设备发送第一随机数，第一设备接收来自第二设备的第一随机 数。
第二设备接收第一信息和第一证书后，可以对第一证书进行验证，以确定第一证书是否可靠。例如，第二设备可以根据第一设备的第三证书对第一证书进行验证，如果验证通过，则确定第一证书是可靠的，如果验证失败，则确定第一证书不可靠。一个设备的第三证书，可以是OEM根证书，或者是OEM/证书颁发机构(certificate authority，CA)签发的二级证书，或者是OEM/CA签发的三级证书，或者是四级证书，还可能是更多层级的证书，等等，对于证书的层级不作限制。例如，第一设备的第三证书，可以是根证书，或者是二级证书，或者是三级证书，或者是四级证书，还可能是更多层级的证书，等等。
如果第二设备确定第一证书可靠，则第二设备可以生成随机数，例如称为第一随机数，第二设备可以将第一随机数发送给第一设备。第一随机数可以用于验证第一设备。本实施例以第二设备确定第一证书可靠为例。
如果第二设备确定第一证书不可靠，则第二设备可以不必生成第一随机数。示例性地，如果第二设备确定第一证书不可靠，第二设备还可以向第一设备发送通知消息，该通知消息用于指示第一证书不可靠，或用于指示认证过程失败等。
第二设备可以通过第三设备将第一随机数转发给第一设备。
其中，与第一证书有关的内容，可以结合在图2所示的实施例中，或者也可以单独作为一个实施例。例如，第一设备向第二设备发送第一证书的操作，以及第一证书的内容等，可单独作为一个实施例。或者，第二设备对第一证书进行验证的操作，以及第一证书的内容等，可单独作为一个实施例。
S203、第一设备采用第一私钥，根据第一随机数，得到第一签名。
第一私钥是第一设备使用的私钥，例如第一私钥属于第一设备的身份信息，可以是第一设备在生产完成后写入第一设备的，也可以是设备预先随机生成的随机数并保存在设备中。因此第一私钥无需临时再写入第一设备，第一设备可以直接使用，提高了设备认证的效率。
作为一种可选的方式，第一设备可以根据第一随机数和第一标识来得到第一签名。例如，第一设备可以采用哈希算法，根据第一随机数和第一标识得到哈希值，例如称为第一哈希值，第一设备可以根据第一私钥对第一哈希值进行签名，得到第一签名。第一签名例如表示为sig1＝sig pk(r1,ID1)，其中，r1表示第一随机数，ID1表示第一标识，pk表示第一设备的私钥。
S204、第一设备将第一签名发送给第二设备，第二设备接收来自第一设备的第一签名。第一签名可以用于对第一设备进行认证。
第一设备可以将第一签名发送给第三设备，由第三设备将第一签名转发给第二设备。
S205、第二设备根据第一签名和第一随机数，对第一设备进行认证。
如果第一设备是根据第一随机数得到第一签名，则第二设备可以根据第一签名和第一随机数对第一设备进行认证。或者，如果第一设备是根据第一随机数和第一标识得到第一签名，则第二设备可以根据第一签名、第一随机数和第一标识，对第一设备进行认证。
例如，第二设备可以采用第一公钥，根据第一随机数、第一签名和第一标识对第一设备进行认证，第一公钥和用于得到第一签名的第一私钥是一对非对称密钥。例如，第二设 备可以采用第一公钥，对第一签名、第一随机数和第一标识进行验签，并根据返回的结果启动验签是否通过，如果验签通过，表明对第一设备认证成功，否则，表明对第一设备认证失败。验签的方式例如为，第二设备采用哈希算法，根据第一随机数和第一标识得到哈希值，例如称为第四哈希值，第二设备将第一公钥、第四哈希值和第一签名输入签名验证函数(例如称为第一函数)进行验签，根据返回的结果确定验签是否通过。
第二设备可以将认证结果通过第三设备转发给第一设备，使得第一设备能够获知认证结果。
其中，S202～S206所述的认证过程，也可以被其他的认证过程所替换，或者，S202～S206这几个步骤，也可以有任意的一个或多个步骤不必执行，例如S202可以不必执行，第二设备可以无需向第一设备发送第一随机数，第一设备可以根据第一标识生成第一签名，无需第一随机数。只要能够完成第二设备对第一设备的认证即可。
S206、第二设备根据第一业务，确定第一执行策略。其中，如上所介绍的认证过程是对应于第一业务的。
S206也是可选的步骤，不是必须执行的。S206是以第二设备对第一设备认证失败为前提的，也就是说，如果S205中第二设备对第一设备认证失败，则第二设备可以执行S206，而如果S205中第二设备对第一设备认证失败，则第二设备可以不执行S206。例如，如果第二设备对第一设备认证成功，那么可以继续执行后续的步骤207，或者，也可以不再执行后续的步骤207，而是可以执行其他过程，例如可以启动第一业务等。
第一执行策略例如包括，设备停止工作，或设备停止使用该设备的部分功能。以第二设备来说，第一执行策略可以包括，第二设备停止工作，或第二设备停止使用第二设备的部分功能。这里的部分功能，可以是与第一业务相关的功能。例如第二设备为MDC，第一业务是自动驾驶功能，那么MDC停止使用MDC的部分功能，例如是停止使用与自动驾驶功能相关的功能。第一执行策略可以是第二设备执行，也可以是第一设备执行。如果第一执行策略应该由第一设备执行，则第二设备可以向第一设备发送指示信息，第一设备接收来自第二设备的指示信息，指示信息用于指示第一执行策略。例如，第二设备为网关或路由器等设备，或者为具有路由转发功能的实体，则第一执行策略可以由第一设备执行，则第二设备可以向第一设备发送指示信息；或者，第二设备为除了网关和路由器之外的其他设备，或者为除了具有路由转发功能的实体之外的其他的实体，则第一执行策略可以由第二设备执行，则第二设备可以不向第一设备发送指示信息，而是自行执行第一执行策略即可。
在本申请实施例中，第一信息用于指示第二设备，例如，第一信息可能是第一业务的标识，或者是第二设备的地址等，只要第一设备将第一信息发送给第二设备，第二设备就可以对第一设备进行认证，不依赖设备的层级关系。例如，即使第一设备是第一层级的设备，第二设备是第三层级的设备，第一设备和第二设备之间也能进行认证，这样就实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式因为无需一个中间节点对多个节点进行认证，减轻了设备的负担。通过本申请实施例的技术方案，实现了设备之间端到端的认证，减少了对于中间节点的依赖，使得更多的车载设备能够得到认证，提高了车载设备的安全性，同时能根据业务需要进行认证，保证业务安全。而且，第三设备可以仅仅起到转发作用，或者，可以由第三设备来查询确定第二设备，无需第一设备自行确定第二设备，减少了第一设备的工作量，或者，第三设备还可以起到过滤作用， 可以进一步提高通信的安全性。本申请实施例提供的认证方案具有一定的韧性。此外，本申请实施例提供的端到端的认证方案与整车的架构无关，兼容性比较好，可以适用于现在的汽车架构，也可以适用于未来的汽车架构。
在图2所示的实施例中，第一设备和第二设备要通过第三设备来转发信息。下面再介绍一种设备认证方法，在该方法中，第一设备和第二设备可以直接通信，无需通过其他设备来转发信息。请参见图3，为该方法的流程图。在下文的介绍过程中，以该方法应用于图1所示的网络架构为例。另外，该方法可由两个通信装置(或者说，两种通信装置)执行，这两个通信装置例如为第一通信装置和第二通信装置。其中，第一通信装置或第二通信装置，可以是车载装置或能够支持车载装置实现该方法所需的功能的通信装置(例如芯片系统)，当然还可以是其他通信装置。且对于第一通信装置和第二通信装置的实现方式均不做限制，例如这两个通信装置可以实现为相同的形式，例如均通过设备的形式实现，或者这两个通信装置也可以实现为不同的形式，例如第一通信装置通过设备的形式实现，第二通信装置通过芯片系统的方式实现，等等。
为了便于介绍，在下文中，以该方法由第一设备和第二设备执行为例，也就是说，以第一通信装置是第一设备、第二通信装置是第二设备为例。例如，第一设备可以是待认证的设备，第二设备可以是除了网关和路由器之外的其他设备，或者是除了具有路由转发功能的实体之外的其他实体，或者第二设备也可以是网关或路由器等设备，或者第二设备也可以是具有路由转发功能的实体。另外，网关也可是指具有路由转发设备功能的实体装置。其中，如果第二设备是网关或路由器等设备，或者是具有路由转发功能的实体，则可以认为图3所示的实施例是由网关进行集中式认证的场景，例如，各个域控制器都可以由网关来进行认证，或者，也可以认为图3所示的实施例依然是分布式认证的场景，例如，各个域控制器可以由网关来认证，或者也可以彼此之间互相认证。而如果第二设备是除了网关和路由器之外的其他设备，则可以认为图3所示的实施例是无需网关进行集中式认证的分布式认证场景。因为本实施例是以应用在图1所示的网络架构为例，因此，下文中所述的第一设备例如为图1所示的网络架构中的域控制器，下文中所述的第二设备例如为图1所示的网络架构中的T-Box、OBD或网关等。
S301、第一设备将第一信息和第一证书发送给第二设备，第二设备接收来自第一设备的第一信息和第一证书。其中，第一信息用于指示第二设备，第一证书为第一设备的设备证书。
第一信息可以是用于认证的。第一信息可以包括第二设备的信息，第二设备的信息例如包括第二设备的IP地址，或者，第二设备的信息例如包括第二设备的ID，或者，第二设备的信息例如包括第二设备的IP地址和第二设备的ID，或者，第二设备的信息还可以包括第二设备的其他信息。因此，第一信息可以指示第二设备。或者可以认为，第一信息和第二设备相关联。
或者，第一信息也可以包括业务的标识，该标识可以指示认证的目标设备。例如根据该标识，通过查表可以确定认证的目标设备；或者根据该标识，无需通过查表等额外的操作，就可以确定该标识所指示的认证的目标设备。认证的目标设备，例如第二设备。例如，业务的标识为业务的身份号(ID)，该业务例如称为第一业务。第一业务可以是第一设备和第二设备即将进行的业务，例如，在第一设备和第二设备即将进行第一业务之前，第二设备先要对第一设备进行认证，因此可以认为，该业务标识指示的本次认证的目标设备是 第二设备。
或者，第一信息也可以包括响应于所输入的信息的信息，例如包括响应于用户输入的信息的信息，或者说，第一信息包括与用户的输入相关的信息。例如，第一信息是响应于输入信息的信息，该输入信息例如是用户输入的信息。例如，用户想要进行第一业务，则用户按下了某个或某些按钮或按键，这就相当于输入了信息，或者用户在人机交互界面或其他交互界面进行了操作，相当于输入了信息。第一设备接收了来自用户输入的信息后，就可以启动认证过程，以便执行第一业务。
或者，第一信息也可以通过隐式方式指示第二设备，或者第一信息包括类似于上述描述的其它信息。
或者，第一信息也可以包括其他设备或者第一设备自身提供的其它触发条件的标识。例如，第一信息包括响应于其他设备周期上报的测量结果、触发标识、或信息报告的信息，或者可以包括第一设备或其他设备或整车的启动或重启、软硬件更新或即插即用的设备的引入的信息。
或者，第一信息也可以包括响应于其他事件的信息，其他事件例如为第一设备上电的事件，或者第一设备接收了来自其他设备的信息的事件，等等。例如，用户想要进行第一业务，则用户按下了某个或某些按钮，这就相当于输入了信息，而接收用户输入的信息的是其他设备。其他设备接收了用户输入的信息后，可以通知第一设备启动认证过程，则第一设备就可以执行S201。
或者，第一信息也可以包括报文ID信息。
第一证书可以是第一设备的设备证书。例如，为了保证安全性，可以在设备生产完成后，向设备写入该设备的身份信息。例如，在设备生产完成后，厂商可以对设备进行测试，在测试合格后，该设备的生产商或者OEM可以向该设备写入该设备的身份信息。设备的身份信息例如包括如下的一项或多项：该设备的第三证书，该设备的设备证书，该设备的型号，该设备使用的私钥，或，该设备的标识。例如，设备的身份信息包括该设备的第三证书和设备证书；或者，设备的身份信息包括该设备的标识；或者，设备的身份信息包括该设备的第三证书、该设备的私钥和该设备的标识；或者，设备的身份信息包括该设备的第三证书，该设备的设备证书，该设备的私钥，该设备的型号，和该设备的标识，等等。一个设备的第三证书，可以是OEM根证书，或者是OEM/CA签发的二级证书，或者是OEM/CA签发的三级证书，或者是四级证书，还可能是更多层级的证书，等等，对于证书的层级不作限制。例如，第一设备的第三证书，可以是根证书，或者是二级证书，或者是三级证书，或者是四级证书，还可能是更多层级的证书，等等。
第一设备除了可以将第一信息和第一证书发送给第二设备之外，还可以将第一标识发送给第二设备，则第二设备可以接收来自第一设备的第一标识。第一标识为第一设备的标识，例如为第一设备的ID。
在本申请实施例中，第一设备和第二设备之间无需通过其他设备进行信息转发，第一设备可以直接将第一证书和第一信息等发送给第二设备，第二设备也可以直接接收来自第一设备的第一证书和第一信息。
关于第一证书，可以包括如下的一种信息或如下多种信息的任意组合：第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，或，第一证书的签名信息。例如，第一证书包括第一证书的版本信息；或者，第一证书包括第一 证书的签名者信息和第一证书的主题信息；或者，第一证书包括第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息；或者，第一证书包括第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息，等等。
另外，第一证书可以不包括第一证书的主题属性信息，或者，也可以将主题属性信息称为应用场景信息。
以第一证书包括第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，和第一证书的签名信息为例，对于第一证书所包括的内容的一种示例可参考图2所示的实施例中的表1。
作为一种可选的方式，如果第二设备为除网关或路由器之外的其它设备，或者第二设备为除了具有路由转发功能的实体之外的其他实体，则第一设备也可以不向第二设备发送第一信息，也就是说，S301中，第一设备可以向第二设备发送第一证书，而不必向第二设备发送第一信息。
S302、第二设备向第一设备发送第一随机数，第一设备接收来自第二设备的第一随机数。
第二设备接收第一信息和第一证书后，可以对第一证书进行验证，以确定第一证书是否可靠。例如，第二设备可以根据第一设备的第三证书对第一证书进行验证，如果验证通过，则确定第一证书是可靠的，如果验证失败，则确定第一证书不可靠。
如果第二设备确定第一证书可靠，则第二设备可以生成随机数，例如称为第一随机数，第二设备可以将第一随机数发送给第一设备。第一随机数可以用于验证第一设备。本实施例以第二设备确定第一证书可靠为例。
如果第二设备确定第一证书不可靠，则第二设备可以不必生成第一随机数。示例性地，如果第二设备确定第一证书不可靠，第二设备还可以向第一设备发送通知消息，该通知消息用于指示第一证书不可靠，或用于指示认证过程失败等。
其中，与第一证书有关的内容，可以结合在图3所示的实施例中，或者也可以单独作为一个实施例。例如，第一设备向第二设备发送第一证书的操作，以及第一证书的内容等，可单独作为一个实施例。或者，第二设备对第一证书进行验证的操作，以及第一证书的内容等，可单独作为一个实施例。
S303、第一设备采用第一私钥，根据第一随机数，得到第一签名。
关于S303，可参考图2所示的实施例中的S203。
S304、第一设备将第一签名发送给第二设备，第二设备接收来自第一设备的第一签名。第一签名可以用于对第一设备进行认证。
S305、第二设备根据第一签名和第一随机数，对第一设备进行认证。
第二设备可以将认证结果发送给第一设备，使得第一设备能够获知认证结果。关于S305的更多介绍，可参考图2所示的实施例中的S205。
其中，S302～S306所述的认证过程，也可以被其他的认证过程所替换，或者，S302～S306这几个步骤，也可以有任意的一个或多个步骤不必执行，例如S302可以不必执行，第一设备可以无需向第二设备发送第二随机数，第二设备可以根据第二标识生成第二签名，无需第二随机数。只要能够完成第一设备对第二设备的认证即可。
S306、第二设备根据第一业务，确定第一执行策略。其中，如上所介绍的认证过程是 对应于第一业务的。
S306也是可选的步骤，不是必须执行的。S306是以第二设备对第一设备认证失败为前提的，也就是说，如果S305中第二设备对第一设备认证失败，则第二设备可以执行S306，而如果S305中第二设备对第一设备认证失败，则第二设备可以不执行S306。例如，如果第二设备对第一设备认证成功，那么可以继续执行后续的步骤307，或者，也可以不再执行后续的步骤307，而是可以执行其他过程，例如可以启动第一业务等。
第一执行策略例如包括，设备停止工作，或设备停止使用该设备的部分功能。以第二设备来说，第一执行策略可以包括，第二设备停止工作，或第二设备停止使用第二设备的部分功能。这里的部分功能，可以是与第一业务相关的功能。例如第二设备为MDC，第一业务是自动驾驶功能，那么MDC停止使用MDC的部分功能，例如停止使用与自动驾驶功能相关的功能。第一执行策略可以是第二设备执行，也可以是第一设备执行。如果第一执行策略应该由第一设备执行，则第二设备可以向第一设备发送指示信息，第一设备接收来自第二设备的指示信息，指示信息用于指示第一执行策略。例如，第二设备为网关或路由器等设备，或者为具有路由转发功能的实体，则第一执行策略可以由第一设备执行，则第二设备可以向第一设备发送指示信息；或者，第二设备为除了网关和路由器之外的其他设备，或者为除了具有路由转发功能的实体之外的其他的实体，则第一执行策略可以由第二设备执行，则第二设备可以不向第一设备发送指示信息，而是自行执行第一执行策略即可。
在本申请实施例中，第一信息用于指示第二设备，例如，第一信息可能是第一业务的标识，或者是第二设备的地址等，只要第一设备将第一信息发送给第二设备，第二设备就可以对第一设备进行认证，不依赖设备的层级关系。例如，即使第一设备是第一层级的设备，第二设备是第三层级的设备，第一设备和第二设备之间也能进行认证，这样就实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式因为无需一个中间节点对多个节点进行认证，减轻了设备的负担。通过本申请实施例的技术方案，实现了设备之间端到端的认证，减少了对于中间节点的依赖，使得更多的车载设备能够得到认证，提高了车载设备的安全性。而且，第一设备和第二设备之间无需通过其他设备来转发信息，而是可以直接通信，减小了通信时延，提高了认证效率，且更有效地实现了设备之间端到端的认证。本申请实施例提供的认证方案具有一定的韧性。此外，本申请实施例提供的端到端的认证方案与整车的架构无关，兼容性比较好，可以适用于现在的汽车架构，也可以适用于未来的汽车架构。
图2所示的实施例和图3所示的实施例介绍的过程可以认为是单向认证过程，是第二设备对第一设备进行认证。而在有些场景下，为了提高安全性，可以实行双向认证，即，除了第二设备要对第一设备进行认证之外，第一设备也可以对第二设备进行认证。为此，本申请实施例提供一种设备认证方法，请参见图4，为该方法的流程图。在下文的介绍过程中，以该方法应用于图1所示的网络架构为例。另外，该方法可由三个通信装置(或者说，三种通信装置)执行，这三个通信装置例如为第一通信装置、第二通信装置和第三通信装置。其中，第一通信装置、第二通信装置或第三通信装置，可以是车载装置或能够支持车载装置实现该方法所需的功能的通信装置(例如芯片系统)，当然还可以是其他通信装置。且对于第一通信装置、第二通信装置和第三通信装置的实现方式均不做限制，例如这三个通信装置可以实现为相同的形式，例如均通过设备的形式实现，或者这三个通信装置也可以实现为不同的形式，例如第一通信装置通过设备的形式实现，第二通信装置通过 芯片系统的方式实现，第三通信装置通过设备的形式实现，等等。
为了便于介绍，在下文中，以该方法由第一设备、第二设备和第三设备执行为例，也就是说，以第一通信装置是第一设备、第二通信装置是第二设备、第三通信装置是第三设备为例。例如，第一设备可以是待认证的设备，第二设备可以是除了网关和路由器之外的其他设备，或者是除了具有路由转发功能的实体之外的其他实体。另外，网关也可是指具有路由转发设备功能的实体装置。因为本实施例是以应用在图1所示的网络架构为例，因此，下文中所述的第一设备例如为图1所示的网络架构中的域控制器，下文中所述的第二设备例如为图1所示的网络架构中的T-Box或OBD，下文中所述的第三设备例如为图1所示的网络架构中的网关；或者，下文中所述的第一设备例如为图1所示的网络架构中的T-Box或OBD，下文中所述的第二设备例如为图1所示的网络架构中的域控制器，下文中所述的第三设备例如为图1所示的网络架构中的网关。
S401、第一设备将第一信息和第一证书发送给第二设备，第二设备接收来自第一设备的第一信息和第一证书。其中，第一信息用于指示第二设备，第一证书为第一设备的设备证书。
关于S401，可参考图2所示的实施例中的S201的介绍。
作为一种可选的方式，如果第二设备为除网关或路由器之外的其它设备，或者第二设备为除了具有路由转发功能的实体之外的其他实体，则第一设备也可以不向第二设备发送第一信息，也就是说，S401中，第一设备可以向第二设备发送第一证书，而不必向第二设备发送第一信息。
S402、第二设备向第一设备发送第二证书，第一设备接收来自第二设备的第二证书。第二证书为第二设备的设备证书。
第二设备接收第一信息和第一证书后，可以对第一证书进行验证，以确定第一证书是否可靠。例如，第二设备可以根据第一设备的第三证书对第一证书进行验证，如果验证通过，则确定第一证书是可靠的，如果验证失败，则确定第一证书不可靠。一个设备的第三证书，可以是OEM根证书，或者是OEM/CA签发的二级证书，或者是OEM/CA签发的三级证书，或者是四级证书，还可能是更多层级的证书，等等，对于证书的层级不作限制。例如，第一设备的第三证书，可以是根证书，或者是二级证书，或者是三级证书，或者是四级证书，还可能是更多层级的证书，等等。
如果第二设备确定第一证书可靠，第二设备可以将第二证书发送给第一设备。第二设备可以将第二证书发送给第三设备，由第三设备转发给第一设备。
另外，第二设备还可以将第二标识发送给第一设备，第二标识为第二设备的标识，例如为第二设备的ID。同样的，第二设备可以将第二标识发送给第三设备，由第三设备转发给第一设备。
如果第二设备确定第一证书不可靠，则第二设备可以不必向第一设备发送第二证书。示例性地，如果第二设备确定第一证书不可靠，第二设备还可以向第一设备发送通知消息，该通知消息用于指示第一证书不可靠，或用于指示认证过程失败等。
其中，第二证书所包括的内容可以与第一证书所包括的内容类似。例如，第二证书可以包括如下的一种信息或如下多种信息的任意组合：第二证书的版本信息，第二证书的签名者信息，第二证书的主题信息，第二证书的有效性信息，或，第二证书的签名信息。例如，第二证书包括第二证书的版本信息；或者，第二证书包括第二证书的签名者信息和第 二证书的主题信息；或者，第二证书包括第二证书的主题信息，第二证书的有效性信息，和第二证书的签名信息；或者，第二证书包括第二证书的版本信息，第二证书的签名者信息，第二证书的主题信息，第二证书的有效性信息，和第二证书的签名信息，等等。关于第二证书的更多介绍，可参考图2所示的实施例中对于第一证书的介绍。
其中，与第一证书有关的内容，可以结合在图4所示的实施例中，或者也可以单独作为一个实施例。例如，第一设备向第二设备发送第一证书的操作，以及第一证书的内容等，可单独作为一个实施例。或者，第二设备对第一证书进行验证的操作，以及第一证书的内容等，可单独作为一个实施例。
同理，与第二证书有关的内容，可以结合在图4所示的实施例中，或者也可以单独作为一个实施例。例如，第二设备向第一设备发送第二证书的操作，以及第二证书的内容等，可单独作为一个实施例。或者，第一设备对第二证书进行验证的操作，以及第二证书的内容等，可单独作为一个实施例。
S403、第一设备向第二设备发送第二随机数，第二设备接收来自第一设备的第二随机数。
如果第一设备确定第二证书可靠，则第一设备可以生成第二随机数，并可以将第二随机数发送给第二设备。第二随机数用于对第二设备进行认证。
第一设备可以将第二随机数发送给第三设备，由第三设备转发给第二设备。
S404、第二设备采用第二私钥，根据第二随机数得到第二签名。
第二设备可以只根据第二随机数得到第二签名，或者，作为一种可选的方式，第二设备也可以根据第二随机数和第二标识来得到第二签名。第二标识是第二设备的标识，例如为第二设备的ID。第二私钥是第二设备使用的私钥，例如第二私钥属于第二设备的身份信息，可以是第二设备在生产完成后写入第二设备的。因此第二私钥无需临时再写入第二设备，第二设备可以直接使用，提高了设备认证的效率。
例如，第二设备可以采用哈希算法，根据第二随机数和第二标识得到哈希值，例如称为第二哈希值，第二设备可以根据第二私钥对第二哈希值进行签名，得到第二签名。第二签名例如表示为sig2＝sig pk(r2,ID2)，其中，r2表示第二随机数，ID2表示第二标识。
S405、第二设备将第二签名和第二标识发送给第一设备，第一设备接收来自第二设备的第二签名和第二标识。第二签名用于对第二设备进行认证。
第二设备可以将第二签名和第二标识发送给第三设备，由第三设备将第二签名和第二标识转发给第一设备。
第二设备还可以将第二标识发送给第三设备，由第三设备转发给第一设备。
另外，第二设备还可以生成第一随机数，将第一随机数发送给第三设备，由第三设备转发给第一设备。
S406、第一设备根据第二签名和第二随机数对第二设备进行认证。如果认证通过，执行S408，或者，如果认证失败，执行S407。
如果第二设备是根据第二随机数得到第二签名，则第一设备可以根据第二签名和第二随机数对第二设备进行认证。或者，如果第二设备是根据第二随机数和第二标识得到第二签名，则第一设备可以根据第二签名、第二随机数和第二标识，对第二设备进行认证。
例如，第一设备可以采用第二公钥，根据第二随机数、第二签名和第二标识对第二设 备进行认证，第二公钥和用于得到第二签名的第二私钥是一对非对称密钥。例如，第一设备可以采用第二公钥，对第二签名、第二随机数和第二标识进行验签，并根据返回的结果启动验签是否通过，如果验签通过，表明对第二设备认证成功，否则，表明对第二设备认证失败。验签的方式例如为，第一设备采用哈希算法，根据第二随机数和第二标识得到哈希值，例如称为第三哈希值，第一设备将第二公钥、第三哈希值和第二签名输入签名验证函数(例如称为第二函数)进行验签，根据返回的结果确定验签是否通过。
其中，用于进行验签的第一函数和第二函数，可以是同一函数，也可以是不同的函数。
第一设备可以将认证结果通过第三设备转发给第二设备，使得第二设备能够获知认证结果。
S407、第一设备根据第一业务，确定第二执行策略。其中，如上所介绍的认证过程是对应于第一业务的。
S407也是可选的步骤，不是必须执行的。S407是以第二设备对第一设备认证失败为前提的，也就是说，如果S406中第一设备对第二设备认证失败，则第一设备可以执行S407，而如果S406中第一设备对第二设备认证失败，则第一设备可以不执行S407，而是执行S408。
第二执行策略例如包括，设备停止工作，或设备停止使用该设备的部分功能。以第一设备来说，第一执行策略可以包括，第一设备停止工作，或第一设备停止使用第一设备的部分功能。这里的部分功能，可以是与第一业务相关的功能。例如第一设备为MDC，第一业务是自动驾驶功能，那么MDC停止使用MDC的部分功能，例如是停止使用与自动驾驶功能相关的功能，例如MDC可以不启动自动驾驶功能，或者MDC可以停用自动驾驶功能。
第二执行策略可以是第一设备执行，也可以是第二设备执行。如果第二执行策略应该由第二设备执行，则第一设备可以向第二设备发送指示信息，第二设备接收来自第一设备的指示信息，指示信息用于指示第二执行策略。例如，第二设备为网关或路由器等设备，或者为具有路由转发功能的实体，则第二执行策略可以由第一设备执行，则第一设备可以无需向第二设备发送指示信息，而是自行执行第一执行策略即可；或者，第二设备为除了网关和路由器之外的其他设备，或者为除了具有路由转发功能的实体之外的其他的实体，则第二执行策略可以由第二设备执行，则第一设备可以向第二设备发送指示信息。
S408、第一设备采用第一私钥，根据第一随机数，得到第一签名。
如果第一设备对第二设备认证通过，则第一设备可以得到第一签名，第一签名用于对第一设备进行认证。
第一私钥是第一设备使用的私钥，例如第一私钥属于第一设备的身份信息，可以是第一设备在生产完成后写入第一设备的。因此第一私钥无需临时再写入第一设备，第一设备可以直接使用，提高了设备认证的效率。
作为一种可选的方式，第一设备可以根据第一随机数和第一标识来得到第一签名。例如，第一设备可以采用哈希算法，根据第一随机数和第一标识得到哈希值，例如称为第一哈希值，第一设备可以根据第一私钥对第一哈希值进行签名，得到第一签名。第一签名例如表示为sig1＝sig pk(r1,ID1)，其中，r1表示第一随机数，ID1表示第一标识。
S409、第一设备将第一签名发送给第二设备，第二设备接收来自第一设备的第一签名。
第一设备可以将第一签名发送给第三设备，由第三设备将第一签名转发给第二设备。
S410、第二设备根据第一签名和第一随机数，对第一设备进行认证。
如果第一设备是根据第一随机数得到第一签名，则第二设备可以根据第一签名和第一随机数对第一设备进行认证。或者，如果第一设备是根据第一随机数和第一标识得到第一签名，则第二设备可以根据第一签名、第一随机数和第一标识，对第一设备进行认证。认证过程可以参考图2所示的实施例中的S205。
第二设备可以将认证结果通过第三设备转发给第一设备，使得第一设备能够获知认证结果。
其中，S402～S410所述的认证过程，也可以被其他的认证过程所替换，或者，S402～S410这几个步骤，也可以有任意的一个或多个步骤不必执行，例如S403可以不必执行，第一设备可以无需向第二设备发送第二随机数，第二设备可以根据第二标识生成第二签名，无需第二随机数，只要能够完成第一设备对第二设备的认证即可。同理，第一设备对第二设备的认证过程，也可以有部分步骤无需执行，只要能够完成第二设备对第一设备的认证即可。
S411、第二设备根据第一业务，确定第一执行策略。其中，如上所介绍的认证过程是对应于第一业务的。
S411也是可选的步骤，不是必须执行的。S411是以第二设备对第一设备认证失败为前提的，也就是说，如果S410中第二设备对第一设备认证失败，则第二设备可以执行S411，而如果S410中第二设备对第一设备认证失败，则第二设备可以不执行S411。例如，如果第二设备对第一设备认证成功，那么可以继续执行其他过程，例如可以启动第一业务等。
第一执行策略例如包括，设备停止工作，或设备停止使用该设备的部分功能。以第二设备来说，第一执行策略可以包括，第二设备停止工作，或第二设备停止使用第二设备的部分功能。这里的部分功能，可以是与第一业务相关的功能。例如第二设备为MDC，第一业务是自动驾驶功能，那么MDC停止使用MDC的部分功能，例如是停止使用与自动驾驶功能相关的功能。
第一执行策略可以是第二设备执行，也可以是第一设备执行。如果第一执行策略应该由第一设备执行，则第二设备可以向第一设备发送指示信息，第一设备接收来自第二设备的指示信息，指示信息用于指示第一执行策略。例如，第二设备为网关或路由器等设备，或者为具有路由转发功能的实体，则第一执行策略可以由第一设备执行，则第二设备可以向第一设备发送指示信息；或者，第二设备为除了网关和路由器之外的其他设备，或者为除了具有路由转发功能的实体之外的其他的实体，则第一执行策略可以由第二设备执行，则第二设备可以不向第一设备发送指示信息，而是自行执行第一执行策略即可。
关于图4所示的实施例中的步骤的介绍，可参考图2所示的实施例中的相关步骤的介绍。
在本申请实施例中，第一信息用于指示第二设备，例如，第一信息可能是第一业务的标识，或者是第二设备的地址等，只要第一设备将第一信息发送给第二设备，第二设备就可以对第一设备进行认证，不依赖设备的层级关系。例如，即使第一设备是第一层级的设备，第二设备是第三层级的设备，第一设备和第二设备之间也能进行认证，这样就实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式因为无需一个中间节点对多个节点进行认证，减轻了设备的负担。通过本申请实施例的技术方案，实现了设备之间端到端的认证，减少了对于中间节点的依赖，使得更多的车载设备能够得到认证，提高了车载设备的安全性。而且，第三设备可以仅仅起到转发作用，或者，可以由第三设备来查询确定第二设备，无需第一设备自行确定第二设备，减少了第一设备的工作量，或者，第三设备还可以起到过滤作用，可以进一步提高通信的安全性。本申请实施例提供 的认证方案具有一定的韧性。此外，本申请实施例提供的端到端的认证方案与整车的架构无关，兼容性比较好，可以适用于现在的汽车架构，也可以适用于未来的汽车架构。
而且，两个设备之间可以实行双向认证，可以进一步提高通信过程的可靠性。
在图4所示的实施例所介绍的双向认证方法中，第一设备和第二设备要通过第三设备来转发信息。下面再介绍一种设备认证方法，在该方法中，第一设备和第二设备依然是执行双向认证，但第一设备和第二设备之间可以直接通信，无需通过其他设备来转发信息。请参见图5，为该方法的流程图。在下文的介绍过程中，以该方法应用于图1所示的网络架构为例。另外，该方法可由两个通信装置(或者说，两种通信装置)执行，这两个通信装置例如为第一通信装置和第二通信装置。其中，第一通信装置或第二通信装置，可以是车载装置或能够支持车载装置实现该方法所需的功能的通信装置(例如芯片系统)，当然还可以是其他通信装置。且对于第一通信装置和第二通信装置的实现方式均不做限制，例如这两个通信装置可以实现为相同的形式，例如均通过设备的形式实现，或者这两个通信装置也可以实现为不同的形式，例如第一通信装置通过设备的形式实现，第二通信装置通过芯片系统的方式实现，等等。
为了便于介绍，在下文中，以该方法由第一设备和第二设备执行为例，也就是说，以第一通信装置是第一设备、第二通信装置是第二设备为例。例如，第一设备可以是待认证的设备，第二设备可以是除了网关和路由器之外的其他设备，或者是除了具有路由转发功能的实体之外的其他实体，或者第二设备也可以是网关或路由器等设备，或者第二设备也可以是具有路由转发功能的实体。另外，网关也可是指具有路由转发设备功能的实体装置。其中，如果第二设备是网关或路由器等设备，或者是具有路由转发功能的实体，则可以认为图5所示的实施例是由网关进行集中式认证的场景，例如，各个域控制器都可以由网关来进行认证，或者，也可以认为图5所示的实施例依然是分布式认证的场景，例如，各个域控制器可以由网关来认证，或者也可以彼此之间互相认证。而如果第二设备是除了网关和路由器之外的其他设备，则可以认为图5所示的实施例是无需网关进行集中式认证的分布式认证场景。因为本实施例是以应用在图1所示的网络架构为例，因此，下文中所述的第一设备例如为图1所示的网络架构中的域控制器，下文中所述的第二设备例如为图1所示的网络架构中的T-Box、OBD或网关等。
S501、第一设备将第一信息和第一证书发送给第二设备，第二设备接收来自第一设备的第一信息和第一证书。其中，第一信息用于指示第二设备，第一证书为第一设备的设备证书。
关于S501，可参考图4所示的实施例中的S401的介绍。
作为一种可选的方式，如果第二设备为除网关或路由器之外的其它设备，或者第二设备为除了具有路由转发功能的实体之外的其他实体，则第一设备也可以不向第二设备发送第一信息，也就是说，S501中，第一设备可以向第二设备发送第一证书，而不必向第二设备发送第一信息。
S502、第二设备向第一设备发送第二证书，第一设备接收来自第二设备的第二证书。第二证书为第二设备的设备证书。
第二设备接收第一信息和第一证书后，可以对第一证书进行验证，以确定第一证书是否可靠。例如，第二设备可以根据第一设备的第三证书对第一证书进行验证，如果验证通过，则确定第一证书是可靠的，如果验证失败，则确定第一证书不可靠。一个设备的第三 证书，可以是OEM根证书，或者是OEM/CA签发的二级证书，或者是OEM/CA签发的三级证书，或者是四级证书，还可能是更多层级的证书，等等，对于证书的层级不作限制。例如，第一设备的第三证书，可以是根证书，或者是二级证书，或者是三级证书，或者是四级证书，还可能是更多层级的证书，等等。
如果第二设备确定第一证书可靠，第二设备可以将第二证书发送给第一设备。
另外，第二设备还可以将第二标识发送给第一设备，第二标识为第二设备的标识，例如为第二设备的ID。
如果第二设备确定第一证书不可靠，则第二设备可以不必向第一设备发送第二证书。示例性地，如果第二设备确定第一证书不可靠，第二设备还可以向第一设备发送通知消息，该通知消息用于指示第一证书不可靠，或用于指示认证过程失败等。
其中，与第一证书有关的内容，可以结合在图5所示的实施例中，或者也可以单独作为一个实施例。例如，第一设备向第二设备发送第一证书的操作，以及第一证书的内容等，可单独作为一个实施例。或者，第二设备对第一证书进行验证的操作，以及第一证书的内容等，可单独作为一个实施例。
同理，与第二证书有关的内容，可以结合在图5所示的实施例中，或者也可以单独作为一个实施例。例如，第二设备向第一设备发送第二证书的操作，以及第二证书的内容等，可单独作为一个实施例。或者，第一设备对第二证书进行验证的操作，以及第二证书的内容等，可单独作为一个实施例。
S503、第一设备向第二设备发送第二随机数，第二设备接收来自第一设备的第二随机数。
如果第一设备确定第二证书可靠，则第一设备可以生成第二随机数，并可以将第二随机数发送给第二设备。第二随机数用于对第二设备进行认证。
S504、第二设备采用第二私钥，根据第二随机数得到第二签名。
第二设备可以只根据第二随机数得到第二签名，或者，作为一种可选的方式，第二设备也可以根据第二随机数和第二标识来得到第二签名。第二标识是第二设备的标识，例如为第二设备的ID。第二私钥是第二设备使用的私钥，例如第二私钥属于第二设备的身份信息，可以是第二设备在生产完成后写入第二设备的。因此第二私钥无需临时再写入第二设备，第二设备可以直接使用，提高了设备认证的效率。
例如，第二设备可以采用哈希算法，根据第二随机数和第二标识得到哈希值，例如称为第二哈希值，第二设备可以根据第二私钥对第二哈希值进行签名，得到第二签名。第二签名例如表示为sig2＝sig pk(r2,ID2)，其中，r2表示第二随机数，ID2表示第二标识。
S505、第二设备将第二签名和第二标识发送给第一设备，第一设备接收来自第二设备的第二签名和第二标识。第二签名用于对第二设备进行认证。
除此之外，第二设备还可以将第二标识发送给第一设备。
另外，第二设备还可以生成第一随机数，将第一随机数发送给第一设备。
S506、第一设备根据第二签名和第二随机数对第二设备进行认证。如果认证通过，执行S508，或者，如果认证失败，执行S507。
如果第二设备是根据第二随机数得到第二签名，则第一设备可以根据第二签名和第二随机数对第二设备进行认证。或者，如果第二设备是根据第二随机数和第二标识得到第二 签名，则第一设备可以根据第二签名、第二随机数和第二标识，对第二设备进行认证。
关于第二设备对第一设备进行认证的过程，可参考图4所示的实施例中的S406。
第一设备可以将认证结果发送给第二设备，使得第二设备能够获知认证结果。
S507、第一设备根据第一业务，确定第二执行策略。其中，如上所介绍的认证过程是对应于第一业务的。
S507也是可选的步骤，不是必须执行的。S507是以第二设备对第一设备认证失败为前提的，也就是说，如果S506中第一设备对第二设备认证失败，则第一设备可以执行S507，而如果S506中第一设备对第二设备认证失败，则第一设备可以不执行S507，而是执行S508。
第二执行策略例如包括，设备停止工作，或设备停止使用该设备的部分功能。以第一设备来说，第一执行策略可以包括，第一设备停止工作，或第一设备停止使用第一设备的部分功能。这里的部分功能，可以是与第一业务相关的功能。例如第一设备为MDC，第一业务是自动驾驶功能，那么MDC停止使用MDC的部分功能，例如是停止使用与自动驾驶功能相关的功能，例如MDC可以不启动自动驾驶功能，或者MDC可以停用自动驾驶功能。
第二执行策略可以是第二设备执行，也可以是第一设备执行。如果第二执行策略应该由第二设备执行，则第一设备可以向第二设备发送指示信息，第二设备接收来自第一设备的指示信息，指示信息用于指示第二执行策略。例如，第二设备为网关或路由器等设备，或者为具有路由转发功能的实体，则第二执行策略可以由第一设备执行，则第一设备可以无需向第二设备发送指示信息，而是自行执行第二执行策略即可；或者，第二设备为除了网关和路由器之外的其他设备，或者为除了具有路由转发功能的实体之外的其他的实体，则第二执行策略可以由第二设备执行，则第一设备可以向第二设备发送指示信息。
S508、第一设备采用第一私钥，根据第一随机数，得到第一签名。
如果第一设备对第二设备认证通过，则第一设备可以得到第一签名，第一签名用于对第一设备进行认证。
第一私钥是第一设备使用的私钥，例如第一私钥属于第一设备的身份信息，可以是第一设备在生产完成后写入第一设备的。因此第一私钥无需临时再写入第一设备，第一设备可以直接使用，提高了设备认证的效率。
作为一种可选的方式，第一设备可以根据第一随机数和第一标识来得到第一签名。例如，第一设备可以采用哈希算法，根据第一随机数和第一标识得到哈希值，例如称为第一哈希值，第一设备可以根据第一私钥对第一哈希值进行签名，得到第一签名。第一签名例如表示为sig1＝sig pk(r1,ID1)，其中，r1表示第一随机数，ID1表示第一标识。
S509、第一设备将第一签名发送给第二设备，第二设备接收来自第一设备的第一签名。
S510、第二设备根据第一签名和第一随机数，对第一设备进行认证。
如果第一设备是根据第一随机数得到第一签名，则第二设备可以根据第一设备的公钥、第一签名和第一随机数对第一设备进行签名验签认证。或者，如果第一设备是根据第一随机数和第一标识得到第一签名，则第二设备可以根据第一签名、第一随机数和第一标识，对第一设备进行签名验签认证。认证过程可以参考图2所示的实施例中的S205。
第二设备可以将认证结果通过第三设备转发给第一设备，使得第一设备能够获知认证结果。
其中，S502～S510所述的认证过程，也可以被其他的认证过程所替换，或者，S502～S510 这几个步骤，也可以有任意的一个或多个步骤不必执行，例如S503可以不必执行，第一设备可以无需向第二设备发送第二随机数，第二设备可以根据第二标识生成第二签名，无需第二随机数，只要能够完成第一设备对第二设备的认证即可。同理，第一设备对第二设备的认证过程，也可以有部分步骤无需执行，只要能够完成第二设备对第一设备的认证即可。
S511、第二设备根据第一业务，确定第一执行策略。其中，如上所介绍的认证过程是对应于第一业务的。
S511也是可选的步骤，不是必须执行的。S511是以第二设备对第一设备认证失败为前提的，也就是说，如果S510中第二设备对第一设备认证失败，则第二设备可以执行S511，而如果S510中第二设备对第一设备认证失败，则第二设备可以不执行S511。例如，如果第二设备对第一设备认证成功，那么可以继续执行其他过程，例如可以启动第一业务等。
第一执行策略例如包括，设备停止工作，或设备停止使用该设备的部分功能。以第二设备来说，第一执行策略可以包括，第二设备停止工作，或第二设备停止使用第二设备的部分功能。这里的部分功能，可以是与第一业务相关的功能。例如第二设备为T-Box，第一业务是自动驾驶功能，那么T-Box停止使用T-Box的部分功能，例如是停止使用与自动驾驶功能相关的功能。
第一执行策略可以是第二设备执行，也可以是第一设备执行。如果第一执行策略应该由第一设备执行，则第二设备可以向第一设备发送指示信息，第一设备接收来自第二设备的指示信息，指示信息用于指示第一执行策略。例如，第二设备为网关或路由器等设备，或者为具有路由转发功能的实体，则第一执行策略可以由第一设备执行，则第二设备可以向第一设备发送指示信息；或者，第二设备为除了网关和路由器之外的其他设备，或者为除了具有路由转发功能的实体之外的其他的实体，则第一执行策略可以由第二设备执行，则第二设备可以不向第一设备发送指示信息，而是自行执行第一执行策略即可。
关于图5所示的实施例中的步骤的介绍，可参考图2所示的实施例或图3所示的实施例或图4所示的实施例中的相关步骤的介绍。
在本申请实施例中，第一信息用于指示第二设备，例如，第一信息可能是第一业务的标识，或者是第二设备的地址等，只要第一设备将第一信息发送给第二设备，第二设备就可以对第一设备进行认证，不依赖设备的层级关系。例如，即使第一设备是第一层级的设备，第二设备是第三层级的设备，第一设备和第二设备之间也能进行认证，这样就实现了分布式认证过程。相对于集中式认证的机制来说，本申请实施例的认证方式因为无需一个中间节点对多个节点进行认证，减轻了设备的负担。通过本申请实施例的技术方案，实现了设备之间端到端的认证，减少了对于中间节点的依赖，使得更多的车载设备能够得到认证，提高了车载设备的安全性。而且，第一设备和第二设备之间无需通过其他设备来转发信息，而是可以直接通信，减小了通信时延，提高了认证效率，且更有效地实现了设备之间端到端的认证。本申请实施例提供的认证方案具有一定的韧性。此外，本申请实施例提供的端到端的认证方案与整车的架构无关，兼容性比较好，可以适用于现在的汽车架构，也可以适用于未来的汽车架构。
而且，两个设备可以实行双向认证，进一步提高了通信过程的可靠性。
为了更加易于理解，下面以具体的业务为例，对图2所示的实施例至图5所示的实施例中的任一个实施例进行举例介绍。
例如，MDC通过网关与T-Box进行通信，例如，MDC与T-BOX之间通过以太网或 灵活数据速率控制器局域网(controller area networkwith rlexible data-rate)进行传输。在MDC通过T-Box传输地理位置信息等保密信息到智能计算平台时，为了保证消息传输的安全以及传输的及时性，MDC与T-Box之间可以建立安全传输通道，进行端到端的安全传输，通过安全传输通道所传输的信息在网关可以进行透传，无需加解密，提高传输的速度。为了建立端到端的安全传输通道，需要进行端到端的认证，也就是说，MDC和T-Box之间需要认证。请参考图6，为MDC和T-Box之间的认证过程的流程图。在图6所示的实施例中，以MDC和T-Box之间进行双向认证为例。例如，T-Box可以视为第一设备，MDC可以视为第二设备。而MDC和T-Box之间可以通过网关来转发信息，网关可以视为第三设备。
S601、T-Box向MDC发送设备证书1及第一信息，MDC接收来自T-Box的设备证书1及第一信息。
其中，T-Box将设备证书1及第一信息发送给网关，由网关转发给MDC。设备证书1为T-Box的设备证书。
例如，第一信息包括MDC的IP地址，网关可以根据该IP地址将设备证书1和第一信息转发给MDC。其中，网关在转发时可以根据过滤规则判断是否需要转发，若违反转发规则，则网关丢弃第一信息和设备证书1，不予转发。
或者，第一信息包括第一业务的ID，网关接收第一业务的ID后，可以查询业务的ID和设备之间的对应关系，确定与第一业务的ID对应的设备，例如第一业务的ID对应的设备中包括MDC，则网关将设备证书1和第一信息转发给MDC。
另外，T-Box还可以将ID1发送给MDC，同样的，T-Box可以通过网关将ID1转发给MDC。ID1为T-Box的ID。
S602、MDC验证设备证书1是否合法。
例如，MDC可以根据T-Box的根证书或二级证书来对设备证书1进行验证。另外，MDC还可以验证ID1的有效性。
如果通过验证确定设备证书1合法，以及确定ID1有效，则可以继续执行S603，否则，流程结束。
S603、MDC向T-Box发送设备证书2，T-Box接收来自MDC的设备证书2。设备证书2为MDC的设备证书。
其中，MDC将设备证书2发送给网关，由网关转发给T-Box。另外，MDC还可以向T-Box发送ID2，同样的，MDC可以将ID2发送给网关，由网关转发给T-Box。ID2为MDC的ID。
S604、T-Box验证设备证书2是否合法。
例如，T-Box可以根据MDC的根证书或二级证书来对设备证书2进行验证。另外，T-Box还可以验证ID2的有效性。
如果通过验证确定设备证书2合法，以及确定ID2有效，则可以继续执行S605，否则，流程结束。
S605、T-Box向MDC发送随机数r2，MDC接收来自T-Box的随机数r2。随机数r2可以是第二随机数。
其中，T-Box将随机数r2发送给网关，由网关转发给MDC。
S606、MDC根据随机数r2计算第二签名。
作为一种可选的方式，MDC可以根据随机数r2和ID2计算第二签名，ID2表示MDC的ID。
例如第二签名表示为sig2＝sig(h2)，h2＝hash(ID2,r2)。hash()表示哈希算法。例如，MDC可以采用哈希算法，根据随机数r2和ID2得到哈希值，例如称为第二哈希值，第二设备可以根据第二私钥对第二哈希值进行签名，得到第二签名sig2。
S607、MDC将ID2和sig2发送给T-Box，T-Box接收来自MDC的ID2和sig2。
例如，MDC可以将ID2和sig2发送给网关，网关将ID2和sig2转发给T-Box。另外，MDC还可以生成随机数r1，并将随机数r1发送给网关，网关将随机数r1转发给T-Box。r1可以是第一随机数。
S608、T-Box根据sig2对MDC进行签名验签认证。
T-Box可以根据ID2和随机数r2以及MDC的设备证书中的公钥验证sig2。如果验证成功，则T-Box认为MDC可信，可以执行S609。如果验证失败，可以不执行S609。
S609、T-Box根据随机数r1计算第一签名。
作为一种可选的方式，T-Box可以根据随机数r1和ID1计算第一签名，ID1为T-Box的ID。例如第一签名表示为sig1，sig1＝sig(h1)，其中h1＝hash(ID1，r1)。
S610、T-Box向MDC发送ID1和sig1，MDC接收来自T-Box的ID1和sig1。
T-Box可以将ID1和sig1发送给网关，网关将ID1和sig1转发给MDC。
S611、MDC根据sig1对T-Box进行签名验签认证。
MDC可以根据随机数r1和ID1验证sig1。如果MDC对sig1验证成功，则MDC认为T-Box可信。如果MDC对sig1验证成功，T-Box对sig2也验证成功，则MDC和T-Box可以建立安全传输通道。而如果MDC对sig1验证失败，或者，T-Box对sig2验证失败，或者，MDC对sig1验证失败，以及T-Box对sig2验证失败，则MDC和T-Box可以不建立安全传输通道。
图6所示的实施例介绍的都是MDC和T-Box之间的认证过程，该实施例可以认为是对图4所示的实施例的举例。下面再通过其他的认证过程来对图2所示的实施例至图5所示的实施例中的任一个实施例进行举例。
例如，第一业务为自动驾驶功能。自动驾驶功能的启用，一般需要完成以下的三个认证过程：
1、VCU对MDC的单向认证。当MDC启动后，MDC可以请求VCU对MDC进行认证，如果VCU对MDC认证不通过，VCU可以向HMI发送认证失败的信息。
2、HMI与MDC之间的双向认证。当HMI启动后，可以向MDC发送HMI的设备信息(例如，HMI的标识)和HMI的证书。HMI在向MDC发送HMI的设备信息和HMI的证书后，如果未收到MDC的反馈信息，则可以周期性地发送向MDC发送HMI的设备信息和HMI的证书，发送的周期时间与传输的协议有关，例如若是CAN-FD协议或CAN协议，则发送的周期可以是报文周期的整数倍，而如果是以太网传输，则发送的周期可以更灵活，可以自定义。或者，当MDC启动后，可以向HMI发送MDC的设备信息(例如，MDC的标识)和MDC的证书。MDC在向HMI发送MDC的设备信息和MDC的证书后，如果未收到HMI的反馈信息，则可以周期性地发送向HMI发送MDC的设备信息和MDC的证书，发送的周期时间与传输的协议有关，例如若是CAN-FD协议或CAN协议，则发送的周期可以是报文周期的整数倍，而如果是以太网传输，则发送的周期可以更灵活，可 以自定义。
3、MDC对传感器的单向认证，这里的传感器是与MDC属于一个域的传感器。MDC收到自动驾驶功能的标识(也就是第一业务的标识)后，可以对车载毫米波雷达或导航设备等传感器进行单向认证。
当然，除了如上的三个认证过程之外，自动驾驶功能的启用可能还涉及到其他的认证过程，例如当系统的架构不同时，可能涉及的认证过程不同。例如在某些系统架构下，自动驾驶功能还可能涉及到MDC和T-Box之间的认证等。这里只以如上的三个认证过程为例。
为了减少用户等待启用自动驾驶功能按钮的时间，第1个认证过程(VCU对MDC的单向认证)可以在还未收到自动驾驶功能的标识的情况下就进行，或者理解为，可以在还未启动自动驾驶功能的情况下就进行。第2个认证过程(HMI与MDC之间的双向认证)可以在收到自动驾驶功能的标识的情况下进行，可以理解为，第2个认证过程可以在触发自动驾驶功能后进行。例如用户点击了启动自动驾驶功能的按钮，或者用户在人机交互界面进行了用于启动自动驾驶功能的操作，都可以是触发自动驾驶功能的方式。例如，如果第1个认证过程的认证成功，则可以执行第2个认证过程，而如果第1个认证过程的认证失败，则第2个认证过程不必执行，例如如果第1个认证过程的认证失败，则自动驾驶功能无法启动，则第2个认证过程也就不必执行。在第2个认证过程的认证成功后，也就是HMI对MDC认证成功，以及MDC对HMI认证成功，可以进行第3个认证过程(MDC对传感器的单向认证)。而如果第2个认证过程的认证失败，则第3个认证过程不必执行，例如如果第2个认证过程的认证失败，则自动驾驶功能无法启动，则第3个认证过程也就不必执行。如果第3个认证过程的认证成功，则可以正常使用自动驾驶功能。而如果第3个认证过程的认证失败，则自动驾驶功能无法启动。为了保证人身安全，对于如上的3个认证过程，只要有任意一个认证过程的认证失败，则可以采取的策略是，不启动自动驾驶功能。下面通过几个实施例分别介绍如上的3个认证过程。
请参考图7，为如上的第1个认证过程的流程图。在图7所示的实施例中，MDC可以看作第一设备，VCU可以看作第二设备。图7所示的实施例，可以看作是对图2所示的实施例的举例，也可以看作是对图3所示的实施例的举例。
S701、MDC向VCU发送自动驾驶功能的ID、ID2和设备证书2，VCU接收来自MDC的自动驾驶功能的ID、ID2和设备证书2。ID2是MDC的ID，设备证书2是MDC的设备证书。此时，第一信息可以包括自动驾驶功能的ID，ID2就是第一标识，设备证书2是第一证书。
其中，MDC和VCU之间可以通过网关通信，可参考图1所示的网络架构。那么MDC可以将自动驾驶功能的ID、ID2和设备证书2发送给网关，由网关转发给VCU。或者，MDC和VCU之间也可以直接通信，无需通过其他设备转发，则MDC可以将自动驾驶功能的ID、ID2和设备证书2直接发送给VCU。图7以MDC和VCU之间通过网关通信为例。
S702、VCU验证ID2和设备证书2的合法性。如果确定ID2和设备证书2合法，可以执行S703。而如果确定ID2不合法，或确定设备证书2不合法，或确定ID2和设备证书2都不合法，则可以向HMI发送对MDC认证失败的信息，例如该认证失败的信息可以包括错误码1，还可以包括自动驾驶功能的ID。其中，验证ID的合法性，也可以描述为验 证ID的有效性。
S703、VCU将自动驾驶功能的ID和随机数r发送给MDC，MDC接收来自VCU的自动驾驶功能的ID和随机数r。随机数r可以是第一随机数。
如果MDC和VCU之间通过网关通信，那么VCU可以将自动驾驶功能的ID和随机数r发送给网关，由网关转发给MDC。或者，MDC和VCU之间也可以直接通信，无需通过其他设备转发，则VCU可以将自动驾驶功能的ID和随机数r直接发送给MDC。
S704、MDC计算第一签名sig1。
例如，MDC可以根据随机数r和ID2来得到第一签名。例如，MDC可以采用哈希算法，根据随机数r和ID2得到哈希值，例如称为第一哈希值，MDC可以根据第一私钥对第一哈希值进行签名，得到第一签名sig1。
S705、MDC将自动驾驶功能的ID、ID2和sig1发送给VCU，VCU接收来自MDC的自动驾驶功能的ID、ID2和sig1。
如果VCU和MDC之间通过网关通信，那么MDC可以将自动驾驶功能的ID、ID2和sig1发送给网关，由网关转发给VCU。或者，MDC和VCU之间也可以直接通信，无需通过其他设备转发，则MDC可以将自动驾驶功能的ID、ID2和sig1直接发送给VCU。另外，MDC也可以将自动驾驶功能的ID发给VCU，使得VCU明确该认证过程是对应于自动驾驶功能业务进行的认证。
S706、VCU根据sig1对MDC进行认证。如果认证成功，执行S707，如果认证失败，执行S708。
例如，VCU可以根据随机数r和ID2对sig1进行验证，如果验证通过，则确定MDC可信，如果验证失败，确定MDC不可信。
S707、若认证成功，VCU将自动驾驶功能的ID和认证成功的信息发送给HMI，HMI接收来自VCU的自动驾驶功能的ID和认证成功的信息。认证成功的信息用于指示VCU对MDC认证成功。
如果VCU和HMI之间通过网关通信，那么VCU可以将自动驾驶功能的ID和认证成功的信息发送给网关，由网关转发给HMI。或者，MDC和VCU之间也可以直接通信，无需通过其他设备转发，则VCU可以将自动驾驶功能的ID和认证成功的信息直接发送给HMI。VCU可以将自动驾驶功能的ID发给HMI，使得HMI明确该认证过程是对应于自动驾驶功能业务进行的认证。
S708、若认证失败，VCU将自动驾驶功能的ID和认证失败的信息发送给HMI，HMI接收来自VCU的自动驾驶功能的ID和认证失败的信息。认证失败的信息例如包括错误码2，可以指示VCU对MDC的认证失败。另外，VCU可以进行错误记录。
如果VCU和HMI之间通过网关通信，那么VCU可以将自动驾驶功能的ID和认证失败的信息发送给网关，由网关转发给HMI。或者，MDC和VCU之间也可以直接通信，无需通过其他设备转发，则VCU可以将自动驾驶功能的ID和认证失败的信息直接发送给HMI。VCU可以将自动驾驶功能的ID发给HMI，使得HMI明确该认证过程是对应于自动驾驶功能业务进行的认证。
请参考图8，为如上的第2个认证过程的流程图。在图8所示的实施例中，MDC可以看作第一设备，HMI可以看作第二设备。图8所示的实施例，可以看作是对图4所示的实施例的举例，也可以看作是对图5所示的实施例的举例。
S801、MDC将自动驾驶功能的ID、ID2及设备证书2发送给HMI，HMI接收来自MDC的自动驾驶功能的ID、ID2和设备证书2。
ID2为MDC的ID，设备证书2为MDC的设备证书。
其中，MDC和HMI之间可以通过网关通信，可参考图1所示的网络架构。那么MDC可以将自动驾驶功能的ID、ID2和设备证书2发送给网关，由网关转发给HMI。或者，MDC和HMI之间也可以直接通信，无需通过其他设备转发，则MDC可以将自动驾驶功能的ID、ID2和设备证书2直接发送给HMI。图8以MDC和HMI之间通过网关通信为例，因此，图8所示的实施例后续的步骤，凡是涉及到MDC和HMI之间传输信息的，都需要通过网关转发，后文不再多赘述。
S802、HMI验证ID2的有效性，及验证设备证书2是否合法。如果ID2有效，以及设备证书2合法，执行S803，否则，HMI可以向MDC发送认证失败的信息，认证失败的信息例如为错误码1，另外，还可以向MDC发送自动驾驶功能的ID。
S803、HMI将自动驾驶功能的ID、ID3及设备证书3发送给MDC，MDC接收来自MDC的自动驾驶功能的ID、ID3和设备证书3。ID3为HMI的ID，设备证书3为HMI的设备证书。
S804、MDC验证设备ID3的有效性，及验证设备证书3是否合法。如果ID3有效，以及设备证书3合法，执行S805，否则，MDC不向HMI发送信息，认证结束，MDC不启动自动驾驶功能，并且进行错误记录，必要时，MDC可以向云端设备发送错误码。
S805、MDC将自动驾驶功能的ID和随机数r1发送给HMI，HMI接收来自MDC的自动驾驶功能的ID和随机数r1。随机数r1可以是第二随机数。
S806、HMI计算第二签名。
例如，第二签名sig2＝sig(h2)，其中h2＝hash(ID3，r1)。
S807、HMI将自动驾驶功能的ID、ID3、sig2及随机数r2发送给MDC，MDC接收来自HMI的自动驾驶功能的ID、ID3、sig2及随机数r2。随机数r2可以是第一随机数。
S808、MDC根据sig2对HMI进行认证。如果认证通过，执行S808，如果认证失败，MDC不向HMI发送信息，且MDC不启动自动驾驶功能，此时，认证结束，MDC可以进行错误记录。
S809、MDC计算第一签名。
例如，第一签名sig3＝sig(h3)，其中h3＝hash(ID2，r1||r2)。r1||r2表示随机数r1和r2的异或,或将随机数r1的序列和随机数r2的序列拼接后得到的序列，例如是将随机数r2的序列拼接到随机数r1的序列的尾部。
S810、MDC将自动驾驶功能的ID、ID2及sig3发送给HMI，HMI接收来自MDC的自动驾驶功能的ID、ID2及sig3。
S811、HMI根据sig3对MDC进行认证。如果认证通过，执行S812，如果认证失败，HMI可以向MDC发送认证失败的信息，认证失败的信息例如包括错误码2，并且可以通过HMI显示，不能启动自动驾驶功能。
S812、HMI将自动驾驶功能的ID发送给MDC，MDC接收来自HMI的自动驾驶功能的ID。
请参考图9，为如上的第3个认证过程的流程图。在图9所示的实施例中，sensor可以看作第一设备，MDC可以看作第二设备。图9所示的实施例，可以看作是对图3所示 的实施例的举例。
S901、sensor将自动驾驶功能的ID、ID4和设备证书4发送给MDC，MDC接收来自sensor的自动驾驶功能的ID、ID4和设备证书4。ID4是该sensor的ID，设备证书4是该sensor的设备证书。
S902、MDC验证ID4的有消息，及验证设备证书4的合法性。如果确定ID4和设备证书4合法，可以执行S903。而如果确定ID4不合法，或确定设备证书4不合法，或确定ID4和设备证书4都不合法，则可以向该sensor发送认证失败的信息，例如该认证失败的信息可以包括错误码1，还可以包括自动驾驶功能的ID。另外，如果确定ID4不合法，或确定设备证书4不合法，或确定ID4和设备证书4都不合法，还可以向HMI发送错误码1和自动驾驶功能的ID。
S903、MDC将自动驾驶功能的ID和随机数r3发送给sensor，sensor接收来自MDC的自动驾驶功能的ID和随机数r3。
S904、sensor计算第一签名。例如，sensor可以根据随机数r3和ID4计算第一签名sig4。
S905、sensor将自动驾驶功能的ID、ID4和sig4发送给MDC，MDC接收来自sensor的自动驾驶功能的ID、ID4和sig4。
S906、MDC根据sig4对sensor进行认证。如果认证成功，执行S907，如果认证失败，执行S908。
S907、若认证成功，MDC将自动驾驶功能的ID和认证成功的信息发送给HMI和sensor，HMI接收来自VCU的自动驾驶功能的ID和认证成功的信息，sensor接收来自VCU的自动驾驶功能的ID和认证成功的信息。认证成功的信息用于指示VCU对MDC认证成功。其中，图9中未画出MDC给HMI发送信息的步骤。
S908、若认证失败，MDC将自动驾驶功能的ID和认证失败的信息发送给HMI，HMI接收来自VCU的自动驾驶功能的ID和认证失败的信息。认证失败的信息例如包括错误码2，可以指示MDC对sensor的认证失败。另外，MDC可以进行错误记录，记录的信息还可以上报给云端设备。在认证失败的情况下，MDC的自动驾驶功能不启用。其中，图9中未画出MDC给HMI发送信息的步骤。
关于错误码1和错误码2的解释，可参考表2。
表2
Figure PCTCN2020092176-appb-000002
另外，为了使得用户有更好的体验，如上的第1个认证过程和第2个认证过程都可以在未收到自动驾驶功能的ID时就执行。当第1个认证过程或第2个认证过程中的任意一个或两个过程是认证失败时，自动驾驶功能可以禁用。
图6所示的实施例至图9所示的实施例，均是分布式认证过程。而本申请实施例还支持由网关执行集中式认证过程。继续以第一业务是自动驾驶功能为例。
网关作为整个车载系统的中心服务器，对HMI、MDC等设备进行认证。在自动驾驶 情况下，网关接收来自HMI的自动驾驶功能的ID，网关根据自动驾驶功能的ID，查找需要认证的设备及进行认证的顺序。例如，网关根据自动驾驶功能的ID，确定需要认证的设备为HMI、VCU、MDC、sensor，则认证的顺序为：
1)网关对HMI的单向认证；
2)网关对VCU的单向认证；
3)网关对MDC的单向认证；
4)MDC对sensor的单向认证。
其中，1)和2)的顺序可以调换。以上的四个认证过程，任意一个过程认证失败，都不能启动自动驾驶功能。例如，网关对MDC认证失败，则网关可以向VCU下发指令，以指示VCU不能处理来自MDC的指令。
关于如上的四个单向认证过程，可参考其他实施例中对于单向认证过程的介绍。
图6所示的实施例至图9所示的实施例是以自动驾驶功能为例进行介绍，下面再以防盗启动功能这种业务为例，对图2所示的实施例或图3所示的实施例进行介绍。
无钥匙进入，车主直接挂档走人，在这种场景下，车主可用手机虚拟钥匙对车辆解锁，蓝牙将手机和车子进行匹配，当手机的应用(app)开启或在后台运行情况下靠近车辆，自动解锁车门，之后汽车上电。
为了保证接入设备以及车载设备的合法性，车载设备需要完成的认证流程包括以下三个：
4、BCM对PEPS的单向认证，车身域控制单元(body domain control unit，BDCU)确认蓝牙模块的启动指令设备合法性；
5、VCU对BCM进行单向认证，VCU确认BCM上电请求的设备合法性；
6、VCU对域内设备进行单向认证，VCU对电池管理系统(battery management system，BMS)或车载充电器(on-board charge，OBC)等域内设备(VCU、BMS和OBC等可以属于同一个域，VCU是域控制器)进行单向合法性验证。
上述认证过程中，如果第4个认证过程和第5个认证过程是认证失败，则车辆不能启动；如果第4个认证过程和第5个认证过程都是认证成功，而第6个认证过程中的VCU对OBC认证失败，则VCU可以记录，并可以报错，但是车辆可以启动。
请参考图10，为如上的第4个认证过程的流程图。在图10所示的实施例中，BCM可以看作第二设备，PEPS可以看作第一设备。图10所示的实施例，可以看作是对图3所示的实施例的举例。
S1001、PEPS将防盗启动功能的ID、ID5和设备证书5发送给MDC，MDC接收来自PEPS的防盗启动功能的ID、ID5和设备证书5。ID5是PEPS的ID，设备证书5是PEPS的设备证书。
其中，可参考图1所示的架构，PEPS可以是BCM所在的域的域内设备，因此BCM和PEPS之间可以直接通信，无需通过其他设备转发。
S1002、BCM验证ID5的有效性，及验证设备证书5的合法性。如果确定ID5和设备证书5合法，可以执行S1003。而如果确定ID5不合法，或确定设备证书5不合法，或确定ID5和设备证书5都不合法，则可以向PEPS发送对PEPS认证失败的信息，例如该认证失败的信息可以包括错误码1，还可以包括防盗启动功能的ID。
S1003、BCM将防盗启动功能的ID和随机数r1发送给PEPS，PEPS接收来自BCM 的防盗启动功能的ID和随机数r1。随机数r1可以是第一随机数。
S1004、PEPS计算第一签名。
例如，PEPS可以根据随机数r1和ID5来得到第一签名。例如，PEPS可以采用哈希算法，根据随机数r1和ID5得到哈希值，例如称为第一哈希值，PEPS可以根据第一私钥对第一哈希值进行签名，得到第一签名sig1。
S1005、PEPS将防盗启动功能的ID、ID5和sig1发送给BCM，BCM接收来自PEPS的防盗启动功能的ID、ID5和sig1。
S1006、BCM根据sig1对PEPS进行认证。如果认证成功，执行S1007，如果认证失败，执行S1008。
例如，BCM可以根据随机数r1和ID5对sig1进行验证，如果验证通过，则确定PEPS可信，如果验证失败，确定PEPS不可信。
S1007、若认证成功，BCM将防盗启动功能的ID和认证成功的信息发送给PEPS，PEPS接收来自BCM的防盗启动功能的ID和认证成功的信息。认证成功的信息用于指示BCM对PEPS认证成功。
S1008、若认证失败，BCM将防盗启动功能的ID和认证失败的信息发送给PEPS，PEPS接收来自BCM的防盗启动功能的ID和认证失败的信息。认证失败的信息例如包括错误码2，可以指示BCM对PEPS的认证失败，BCM车门处于关闭状态，不能打开车门。另外，BCM可以进行错误记录或发出警报，记录的信息还可以上报给云端设备。
请参考图11，为如上的第5个认证过程的流程图。在图11所示的实施例中，VCU可以看作第二设备，BCM可以看作第一设备。图11所示的实施例，可以看作是对图2所示的实施例的举例，也可以看作是对图3所示的实施例的举例。
S1101、BCM将防盗启动功能的ID、ID6和设备证书6发送给VCU，VCU接收来自BCM的防盗启动功能的ID、ID6和设备证书6。ID6是BCM的ID，设备证书6是BCM的设备证书。
其中，BCM和VCU之间可以通过网关通信，可参考图1所示的网络架构。那么BCM可以将防盗启动功能的ID、ID6和设备证书6发送给网关，由网关转发给VCU。或者，BCM和VCU之间也可以直接通信，无需通过其他设备转发，则BCM可以将防盗启动功能的ID、ID6和设备证书6直接发送给VCU。图11以BCM和VCU之间通过网关通信为例，因此，图11所示的实施例后续的步骤，凡是涉及到BCM和VCU之间传输信息的，都需要通过网关转发，后文不再多赘述。
S1102、VCU验证ID6的有效性，及验证设备证书6的合法性。如果确定ID6和设备证书6合法，可以执行S1103。而如果确定ID6不合法，或确定设备证书6不合法，或确定ID6和设备证书6都不合法，则可以向BCM发送对BCM认证失败的信息，例如该认证失败的信息可以包括错误码1，还可以包括防盗启动功能的ID。
S1103、VCU将防盗启动功能的ID和随机数r1发送给BCM，BCM接收来自VCU的防盗启动功能的ID和随机数r2。随机数r2可以是第一随机数。
S1104、BCM计算第一签名。
例如，BCM可以根据随机数r2和ID6来得到第一签名。例如，BCM可以采用哈希算法，根据随机数r2和ID6得到哈希值，例如称为第一哈希值，BCM可以根据第一私钥对第一哈希值进行签名，得到第一签名sig2。
S1105、BCM将防盗启动功能的ID、ID6和sig2发送给VCU，VCU接收来自BCM的防盗启动功能的ID、ID6和sig2。
S1106、VCU根据sig2对BCM进行认证。如果认证成功，执行S1107，如果认证失败，执行S1108。
例如，VCU可以根据随机数r2和ID6对sig2进行验证，如果验证通过，则确定BCM可信，如果验证失败，确定BCM不可信。
S1107、若认证成功，VCU将防盗启动功能的ID和认证成功的信息发送给BCM，BCM接收来自VCU的防盗启动功能的ID和认证成功的信息。认证成功的信息用于指示VCU对BCM认证成功。
S1108、若认证失败，VCU将防盗启动功能的ID和认证失败的信息发送给BCM，BCM接收来自VCU的防盗启动功能的ID和认证失败的信息。认证失败的信息例如包括错误码2，可以指示VCU对BCM的认证失败。另外，VCU可以进行错误记录，记录的信息还可以上报给云端设备。
请参考图12，为如上的第6个认证过程的流程图。在图12所示的实施例中，VCU可以看作第二设备，OBC可以看作第一设备。图12所示的实施例，可以看作是对图3所示的实施例的举例。
S1201、OBC将防盗启动功能的ID、ID7和设备证书7发送给VCU，VCU接收来自OBC的防盗启动功能的ID、ID7和设备证书7。ID7是OBC的ID，设备证书7是OBC的设备证书。
其中，OBC可以是VCU所在的域的域内设备，因此VCU和OBC之间可以直接通信，无需通过其他设备转发。
S1202、VCU验证ID7的有效性，及验证设备证书7的合法性。如果确定ID7和设备证书7合法，可以执行S1203。而如果确定ID7不合法，或确定设备证书7不合法，或确定ID7和设备证书7都不合法，则可以向OBC发送对OBC认证失败的信息，例如该认证失败的信息可以包括错误码1，还可以包括防盗启动功能的ID。
S1203、VCU将防盗启动功能的ID和随机数r3发送给OBC，OBC接收来自VCU的防盗启动功能的ID和随机数r3。随机数r3可以是第一随机数。
S1204、OBC计算第一签名。
例如，OBC可以根据随机数r3和ID7来得到第一签名。例如，OBC可以采用哈希算法，根据随机数r3和ID7得到哈希值，例如称为第一哈希值，OBC可以根据第一私钥对第一哈希值进行签名，得到第一签名sig3。
S1205、OBC将防盗启动功能的ID、ID7和sig3发送给VCU，VCU接收来自OBC的防盗启动功能的ID、ID7和sig3。
S1206、VCU根据sig3对OBC进行认证。如果认证成功，执行S1207，如果认证失败，执行S1208。
例如，VCU可以根据随机数r3和ID7对sig3进行验证，如果验证通过，则确定OBC可信，如果验证失败，确定OBC不可信。
S1207、若认证成功，VCU将防盗启动功能的ID和认证成功的信息发送给OBC，OBC接收来自VCU的防盗启动功能的ID和认证成功的信息。认证成功的信息用于指示VCU对OBC认证成功。
S1208、若认证失败，VCU将防盗启动功能的ID和认证失败的信息发送给OBC，OBC接收来自VCU的防盗启动功能的ID和认证失败的信息。认证失败的信息例如包括错误码2，可以指示VCU对OBC的认证失败。另外，VCU可以进行错误记录，记录的信息还可以上报给云端设备。
关于图10所示的实施例至图12所示的实施例中的任一个实施例所涉及的错误码1或错误码2，可参考前文的介绍。
如上的各个实施例介绍了认证过程。在本申请实施例中，如果认证失败，则可以采取相应的策略，所采取的策略也可以与业务相关，下面再通过一些实施例进行介绍。
请参见图13，为本申请实施例提供的一种设备认证方法的流程图。在下文的介绍过程中，以该方法应用于图1所示的网络架构为例。例如，图13所示的实施例所述的第一设备可以是待认证的设备，或者说是被认证失败的设备，第二设备可以是除了网关和路由器之外的其他设备，或者是除了具有路由转发功能的实体之外的其他实体，或者第二设备也可以是网关或路由器等设备，或者第二设备也可以是具有路由转发功能的实体。另外，网关也可是指具有路由转发设备功能的实体装置。其中，如果第二设备是网关或路由器等设备，或者是具有路由转发功能的实体，则可以认为图13所示的实施例是由网关进行集中式认证的场景，例如，各个域控制器都可以由网关来进行认证，或者，也可以认为图13所示的实施例依然是分布式认证的场景，例如，各个域控制器可以由网关来认证，或者也可以彼此之间互相认证。而如果第二设备是除了网关和路由器之外的其他设备，则可以认为图13所示的实施例是无需网关进行集中式认证的分布式认证场景。因为本实施例是以应用在图1所示的网络架构为例，因此，下文中所述的第一设备例如为图1所示的网络架构中的域控制器，下文中所述的第二设备例如为图1所示的网络架构中的T-Box、OBD或网关等。
S1301、第二设备对第一设备认证失败。
例如，第二设备可以先接收来自第一设备的第一信息和第一证书，第一信息用于指示第二设备，第一证书为第一设备的设备证书。第二设备根据第一设备的第三证书，验证第一证书是否正确。当第一证书正确时，第二设备生成第一随机数，并可以将第一随机数发送给第一设备。第一设备接收第一随机数后，可以生成第一签名，并将第一签名发送给第二设备，第二设备接收来自第一设备的第一签名。第二设备可以根据第一签名、第一随机数和第一标识，对第一设备进行认证，第一标识为第一设备的标识。一个设备的第三证书，可以是OEM根证书，或者是OEM/CA签发的二级证书，或者是OEM/CA签发的三级证书，或者是四级证书，还可能是更多层级的证书，等等，对于证书的层级不作限制。例如，第一设备的第三证书，可以是根证书，或者是二级证书，或者是三级证书，或者是四级证书，还可能是更多层级的证书，等等。
另外，第一证书可以不包括第一证书的主题属性信息，以及，第一证书包括如下的一种信息或如下多种信息的任意组合，第一证书的版本信息，第一证书的签名者信息，第一证书的主题信息，第一证书的有效性信息，或，第一证书的签名信息。
其中，与第一证书有关的内容，可以结合在图13所示的实施例中，或者也可以单独作为一个实施例。例如，第一设备向第二设备发送第一证书的操作，以及第一证书的内容等，可单独作为一个实施例。或者，第二设备对第一证书进行验证的操作，以及第一证书的内容等，可单独作为一个实施例。
上一段落只是概述了第二设备对第一设备进行认证的过程，关于此认证过程的较为详细的介绍，可以参考图2所示的实施例至图5所示的实施例中的任一个实施例。另外，第一设备和第二设备之间可以直接通信，或者也可以通过第三设备进行信息的转发，关于这些内容，也可以参考图2所示的实施例至图5所示的实施例中的任一个实施例的介绍。
S1302、第二设备根据第一业务，确定第一执行策略，所述认证对应于第一业务。
如果第二设备对第一设备认证失败，那么第二设备可以根据第一业务来确定第一执行策略。其中，第二设备根据第一业务确定第一执行策略，例如是根据第一业务的标识确定第一执行策略，因为第二设备对第一设备认证失败时，可以确定该认证是与第一业务有关，具体的确定方式可能是确定该认证过程与第一业务的标识有关，因此第二设备可以根据第一业务的标识确定第一执行策略。在业务不同时，第二设备所确定的执行策略可能是不同的。
第一执行策略例如包括，设备停止工作，或设备停止使用该设备的部分功能。以第二设备来说，第一执行策略可以包括，第二设备停止工作，或第二设备停止使用第二设备的部分功能。这里的部分功能，可以是与第一业务相关的功能。例如第二设备为MDC，第一业务是自动驾驶功能，那么MDC停止使用MDC的部分功能，例如是停止使用与自动驾驶功能相关的功能。
例如，第一设备为BMS，第二设备为VCU，第一业务为点火功能。如果VCU对BMS验证失败，则VCU确定的第一执行策略可以是，继续启动点火功能，但是VCU可以发出报警信息。或者，第一设备为MDC，第二设备为VCU，第一业务为自动驾驶功能。如果VCU对MDC验证失败，则VCU确定的第一执行策略可以是，不启动自动驾驶功能。
S1303、第二设备将第一执行策略发送给第一设备，或，第二设备执行第一执行策略。
例如，如果本申请实施例采用的认证场景是分布式认证场景，那么，如果第二设备对第一设备认证失败，则第二设备可以执行第一执行策略。例如，第一设备为MDC，第二设备为VCU，这是分布式认证的场景，第一业务为自动驾驶功能。如果VCU对MDC验证失败，则VCU确定的第一执行策略可以是，不执行后续MDC发送的消息、指令。
或者，如果本申请实施例采用的认证场景是由网关进行集中式认证的场景，那么，如果第二设备对第一设备认证失败，则第二设备可以将第一执行策略发送给第一设备，由第一设备来执行第一执行策略。例如，第一设备是MDC，第二设备是网关，网关进行集中式认证，第一业务是自动驾驶功能。如果网关对MDC验证失败，则网关确定的第一执行策略可以是，不启动自动驾驶功能。那么网关可以将第一执行策略发送给MDC，以指示MDC不启动自动驾驶功能。MDC接收第一执行策略后，就可以不启动自动驾驶功能。另外，在如前的图2所示的实施例至图12所示的实施例中的一些实施例(例如图8所示的实施例，图9所示的实施例，或图10所示的实施例等)中，也涉及了根据业务的不同而采取不同的执行策略的内容，可相应参考。
在本申请实施例中，如果第二设备对第一设备认证失败，因为该认证是与第一业务相关的认证过程，因此第二设备在确定执行策略时，所确定的执行策略可以是与第一业务相关的执行策略，或者说，可以根据第一业务确定执行策略，从而使得所确定的执行策略更为符合业务的需求。
下面结合附图介绍本申请实施例中用来实现上述方法的装置。因此，上文中的内容均可以用于后续实施例中，重复的内容不再赘述。
图14为本申请实施例提供的通信装置1400的示意性框图。通信装置1400可以是通信设备，或是能够支持通信设备实现该方法所需的功能的装置，例如芯片系统。示例性地，通信设备为车载装置。示例性地，通信设备例如为第一设备1400。
通信装置1400包括处理模块1410和收发模块1420。示例性地，通信装置1400可以是第一设备，也可以是应用于第一设备中的芯片或者其他具有上述第一设备功能的组合器件、部件等。当通信装置1400是第一设备时，收发模块1420可以是收发器，可以包括天线和射频电路等，处理模块1410可以是处理器，例如基带处理器，基带处理器中可以包括一个或多个中央处理单元(central processing unit，CPU)。当通信装置1400是具有上述第一设备的功能的部件时，收发模块1420可以是射频单元，处理模块1410可以是处理器，例如基带处理器。当通信装置1400是芯片系统时，收发模块1420可以是芯片系统(例如基带芯片)的输入输出接口、处理模块可以是芯片系统的处理器，可以包括一个或多个中央处理单元。
其中，处理模块1410可以用于执行图2所示的实施例中由第一设备所执行的除了收发操作之外的全部操作，例如S203，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图2所示的实施例中由第一设备所执行的全部收发操作，例如S201、S202和S204，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图3所示的实施例中由第一设备所执行的除了收发操作之外的全部操作，例如S303，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图3所示的实施例中由第一设备所执行的全部收发操作，例如S301、S302和S304，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图4所示的实施例中由第一设备所执行的除了收发操作之外的全部操作，例如S406～S408，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图4所示的实施例中由第一设备所执行的全部收发操作，例如S401、S402、S403、S405和S409，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图5所示的实施例中由第一设备所执行的除了收发操作之外的全部操作，例如S506～S508，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图5所示的实施例中由第一设备所执行的全部收发操作，例如S501、S502、S503、S505和S509，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图6所示的实施例中由T-Box所执行的除了收发操作之外的全部操作，例如S604、S608和S609，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图6所示的实施例中由T-Box所执行的全部收发操作，例如S601、S603、S605、S607和S610，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图7所示的实施例中由MDC所执行的除了收发操作之外的全部操作，例如S704，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图7所示的实施例中由MDC所执行的全部收发操作，例如S701、S703和S705，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图8所示的实施例中由MDC所执行的除了收发操作之外的全部操作，例如S804、S808和S809，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图8所示的实施例中由MDC所执行的全部收发操作，例如S801、S803、S805、S807、S810和S812，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图9所示的实施例中由sensor所执行的除了收发操作之外的全部操作，例如S904，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图9所示的实施例中由sensor所执行的全部收发操作，例如S901、S903、S905、S907和S908，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图10所示的实施例中由PEPS所执行的除了收发操作之外的全部操作，例如S1004，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图10所示的实施例中由PEPS所执行的全部收发操作，例如S1001、S1003、S1005、S1007和S1008，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图11所示的实施例中由BCM所执行的除了收发操作之外的全部操作，例如S1104，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图11所示的实施例中由BCM所执行的全部收发操作，例如S1101、S1103、S1105、S1107和S1108，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1410可以用于执行图12所示的实施例中由OBC所执行的除了收发操作之外的全部操作，例如S1204，和/或用于支持本文所描述的技术的其它过程。收发模块1420可以用于执行图12所示的实施例中由OBC所执行的全部收发操作，例如S1201、S1203、S1205、S1207和S1208，和/或用于支持本文所描述的技术的其它过程。
另外，收发模块1420可以是一个功能模块，该功能模块既能完成发送操作也能完成接收操作，例如收发模块1420可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为收发模块1420是发送模块，而在执行接收操作时，可以认为收发模块1420是接收模块；或者，收发模块1420也可以是两个功能模块的统称，这两个功能模块分别为发送模块和接收模块，发送模块用于完成发送操作，例如发送模块可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部发送操作，接收模块用于完成接收操作，例如接收模块可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部接收操作。
例如，收发模块1420，用于将第一信息和第一证书发送给第二设备，所述第一信息用于指示所述第二设备，所述第一证书为通信装置1400的设备证书；
收发模块1420，还用于接收来自所述第二设备的第一随机数；
处理模块1410，用于采用第一私钥，根据所述第一随机数和第一标识，得到第一签名，所述第一标识为通信装置1400的标识；
收发模块1420，还用于将所述第一签名发送给第二设备，所述第一签名用于对通信装置1400进行认证。
作为一种可选的实施方式，所述第一信息包括第一业务的标识。
作为一种可选的实施方式，
处理模块1410，还用于生成第二随机数；
收发模块1420，还用于将所述第二随机数发送给所述第二设备。
作为一种可选的实施方式，
收发模块1420，还用于接收来自所述第二设备的第二签名和第二标识，所述第二标识为所述第二设备的标识；
处理模块1410，还用于根据所述第二签名、所述第二随机数和所述第二标识对所述第 二设备进行认证。
作为一种可选的实施方式，处理模块1410用于通过如下方式根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证：
采用第二公钥，对所述第二签名、所述第二随机数和所述第二标识进行验签，得到返回的结果，当所述返回的结果指示验签通过时，确定对所述第二设备认证成功，否则，当所述返回的结果指示验签未通过时，确定对所述第二设备认证失败。
作为一种可选的实施方式，所述第一证书不包括所述第一证书的主题属性信息。
作为一种可选的实施方式，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
作为一种可选的实施方式，
收发模块1420，还用于接收来自所述第二设备的指示信息，所述指示信息用于指示对通信装置1400认证失败，或，用于指示通信装置1400停止工作或停止使用通信装置1400的部分功能；
处理模块1410，还用于令通信装置1400停止工作，或停止使用通信装置1400的部分功能。
应理解，本申请实施例中的处理模块1410可以由处理器或处理器相关电路组件实现，收发模块1420可以由收发器或收发器相关电路组件实现。
如图15所示，本申请实施例还提供一种通信装置1500。示例性地，通信装置1500例如为第一设备1500。示例性地，通信装置1500可以是通信设备，例如为终端设备，或者也可以是芯片系统等。通信装置1500包括处理器1510。可选的，还可以包括存储器1520。可选的，还可以包括收发器1530。其中，存储器1520中存储计算机指令或程序，处理器1510可以执行存储器1520中存储的计算机指令或程序。存储器1520中存储的计算机指令或程序被执行时，该处理器1510用于执行上述实施例中处理模块1410执行的操作，收发器1530用于执行上述实施例中收发模块1420执行的操作。或者，通信装置1500也可以不包括存储器1520，例如存储器位于通信装置1500外部，在外部存储器所存储的计算机指令或程序被执行时，该处理器1510用于执行上述实施例中处理模块1410执行的操作，收发器1530用于执行上述实施例中收发模块1420执行的操作。
其中，收发器1530可以是一个功能单元，该功能单元既能完成发送操作也能完成接收操作，例如收发器1530可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为收发器1530是发送器，而在执行接收操作时，可以认为收发器1530是接收器；或者，收发器1530也可以是两个功能单元的统称，这两个功能单元分别为发送器和接收器，发送器用于完成发送操作，例如发送器可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部发送操作，接收器用于完成接收操作，例如接收器可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由 第一设备所执行的全部接收操作。
另外，如果通信装置1500是芯片系统，则收发器1530也可以通过该芯片系统的通信接口实现，该通信接口与通信设备中的射频收发组件连接，以通过射频收发组件实现信息的收发。通信接口可以是一个功能单元，该功能单元既能完成发送操作也能完成接收操作，例如通信接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为通信接口是发送接口，而在执行接收操作时，可以认为通信接口是接收接口；或者，通信接口也可以是两个功能单元的统称，这两个功能单元分别为发送接口和接收接口，发送接口用于完成发送操作，例如发送接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部发送操作，接收接口用于完成接收操作，例如接收接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部接收操作。
应理解，根据本申请实施例的通信装置1400或通信装置1500可实现图2所示的实施例至图12所示的实施例中的任一个实施例中的第一设备的功能，并且通信装置1400或通信装置1500中的各个模块的操作和/或功能分别为了实现图2所示的实施例至图12所示的实施例中的任一个实施例中的相应流程，为了简洁，在此不再赘述。
图16为本申请实施例提供的通信装置1600的示意性框图。通信装置1600可以是通信设备，或是能够支持通信设备实现该方法所需的功能的装置，例如芯片系统。示例性地，通信设备为车载装置。示例性地，通信设备例如为第二设备1600。
通信装置1600包括处理模块1610和收发模块1620。示例性地，通信装置1600可以是第二设备，也可以是应用于第二设备中的芯片或者其他具有上述第二设备功能的组合器件、部件等。当通信装置1600是第二设备时，收发模块1620可以是收发器，可以包括天线和射频电路等，处理模块1610可以是处理器，例如基带处理器，基带处理器中可以包括一个或多个CPU。当通信装置1600是具有上述第二设备的功能的部件时，收发模块1620可以是射频单元，处理模块1610可以是处理器，例如基带处理器。当通信装置1600是芯片系统时，收发模块1620可以是芯片系统(例如基带芯片)的输入输出接口、处理模块可以是芯片系统的处理器，可以包括一个或多个中央处理单元。
其中，处理模块1610可以用于执行图2所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S205和S206，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图2所示的实施例中由第二设备所执行的全部收发操作，例如S201、S202和S204，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图3所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S305和S306，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图3所示的实施例中由第二设备所执行的全部收发操作，例如S301、S302和S304，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图4所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S404、S410和S411，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图4所示的实施例中由第二设备所执行的全部收发操作，例如S401、S402、S403、S405和S409，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图5所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S504、S510和S511，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图5所示的实施例中由第二设备所执行的全部收发操作，例如S501、S502、S503、S505和S509，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图6所示的实施例中由MDC所执行的除了收发操作之外的全部操作，例如S602、S606和S611，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图6所示的实施例中由MDC所执行的全部收发操作，例如S601、S603、S605、S607和S610，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图7所示的实施例中由VCU所执行的除了收发操作之外的全部操作，例如S702和S706，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图7所示的实施例中由VCU所执行的全部收发操作，例如S701、S703和S705，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图8所示的实施例中由HMI所执行的除了收发操作之外的全部操作，例如S802、S806和S811，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图8所示的实施例中由HMI所执行的全部收发操作，例如S801、S803、S805、S807、S810和S812，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图9所示的实施例中由MDC所执行的除了收发操作之外的全部操作，例如S902和S906，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图9所示的实施例中由MDC所执行的全部收发操作，例如S901、S903、S905、S907和S908，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图10所示的实施例中由BCM所执行的除了收发操作之外的全部操作，例如S1002和S1006，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图10所示的实施例中由BCM所执行的全部收发操作，例如S1001、S1003、S1005、S1007和S1008，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图11所示的实施例中由VCU所执行的除了收发操作之外的全部操作，例如S1102和S1106，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图11所示的实施例中由VCU所执行的全部收发操作，例如S1101、S1103、S1105、S1107和S1108，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1610可以用于执行图12所示的实施例中由VCU所执行的除了收发操作之外的全部操作，例如S1202和S1206，和/或用于支持本文所描述的技术的其它过程。收发模块1620可以用于执行图12所示的实施例中由VCU所执行的全部收发操作，例如S1201、S1203、S1205、S1207和S1208，和/或用于支持本文所描述的技术的其它过程。
另外，收发模块1620可以是一个功能模块，该功能模块既能完成发送操作也能完成接收操作，例如收发模块1620可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为收发模块1620是发送模块，而在执行接收操作时，可以认为收发模块1620是接收模块；或者，收发模块1620也可以是两个功能模块的统称，这两个功能模块分别为发送模块和接收模块，发送模块用于完成发送操作，例如发送模块可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部发送操作，接 收模块用于完成接收操作，例如接收模块可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部接收操作。
例如，收发模块1620，用于接收来自第一设备的第一信息和第一证书，所述第一信息用于指示通信装置1600，所述第一证书为所述第一设备的设备证书；
处理模块1610，用于根据所述第一设备的根证书或二级证书，验证所述第一证书是否正确；
处理模块1610，还用于当所述第一证书正确时，生成第一随机数；
收发模块1620，还用于将所述第一随机数发送给所述第一设备；
收发模块1620，还用于接收来自所述第一设备的第一签名；
处理模块1610，还用于根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
作为一种可选的实施方式，所述第一信息包括第一业务的标识。
作为一种可选的实施方式，处理模块1610用于通过如下方式根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证：
采用第一公钥，对所述第一签名、所述第一随机数和所述第一标识进行验签，得到返回的结果，当所述返回的结果指示验签通过时，确定对所述第一设备认证成功，否则，当所述返回的结果指示验签未通过时，确定对所述第一设备认证失败。
作为一种可选的实施方式，
收发模块1620，还用于接收来自所述第一设备的第二随机数；
处理模块1610，还用于当对所述第一设备认证通过时，采用第二私钥，根据所述第二随机数和所述第二标识生成第二签名；
收发模块1620，还用于将所述第二签名和第二标识发送给所述第一设备，所述第二签名用于对通信装置1600进行认证，所述第二标识为通信装置1600的标识。
作为一种可选的实施方式，所述第一证书不包括所述第一证书的主题属性信息。
作为一种可选的实施方式，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
作为一种可选的实施方式，
收发模块1620，还用于当处理模块1610对所述第一设备认证失败时，向所述第一设备发送指示信息，所述指示信息用于指示对所述第一设备认证失败，或，用于指示所述第一设备停止工作或停止使用所述第一设备的部分功能；或，
处理模块1610，还用于当对所述第一设备认证失败时，令通信装置1600停止工作或停止使用通信装置1600的部分功能。
应理解，本申请实施例中的处理模块1610可以由处理器或处理器相关电路组件实现，收发模块1620可以由收发器或收发器相关电路组件实现。
如图17所示，本申请实施例还提供一种通信装置1700。示例性地，通信装置1700例 如为第二设备1700。示例性地，通信装置1700可以是通信设备，例如为终端设备，或者也可以是芯片系统等。通信装置1700包括处理器1710。可选的，还可以包括存储器1720。可选的，还可以包括收发器1730。其中，存储器1720中存储计算机指令或程序，处理器1710可以执行存储器1720中存储的计算机指令或程序。存储器1720中存储的计算机指令或程序被执行时，该处理器1710用于执行上述实施例中处理模块1610执行的操作，收发器1730用于执行上述实施例中收发模块1620执行的操作。或者，通信装置1700也可以不包括存储器1720，例如存储器位于通信装置1700外部，在外部存储器所存储的计算机指令或程序被执行时，该处理器1710用于执行上述实施例中处理模块1610执行的操作，收发器1730用于执行上述实施例中收发模块1620执行的操作。
其中，收发器1730可以是一个功能单元，该功能单元既能完成发送操作也能完成接收操作，例如收发器1730可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为收发器1730是发送器，而在执行接收操作时，可以认为收发器1730是接收器；或者，收发器1730也可以是两个功能单元的统称，这两个功能单元分别为发送器和接收器，发送器用于完成发送操作，例如发送器可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部发送操作，接收器用于完成接收操作，例如接收器可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部接收操作。
另外，如果通信装置1700是芯片系统，则收发器1730也可以通过该芯片系统的通信接口实现，该通信接口与通信设备中的射频收发组件连接，以通过射频收发组件实现信息的收发。通信接口可以是一个功能单元，该功能单元既能完成发送操作也能完成接收操作，例如通信接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为通信接口是发送接口，而在执行接收操作时，可以认为通信接口是接收接口；或者，通信接口也可以是两个功能单元的统称，这两个功能单元分别为发送接口和接收接口，发送接口用于完成发送操作，例如发送接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部发送操作，接收接口用于完成接收操作，例如接收接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部接收操作。
应理解，根据本申请实施例的通信装置1600或通信装置1700可实现图2所示的实施例至图12所示的实施例中的任一个实施例中的第二设备的功能，并且通信装置1600或通信装置1700中的各个模块的操作和/或功能分别为了实现图2所示的实施例至图12所示的实施例中的任一个实施例中的相应流程，为了简洁，在此不再赘述。
图18为本申请实施例提供的通信装置1800的示意性框图。通信装置1800可以是通信设备，或是能够支持通信设备实现该方法所需的功能的装置，例如芯片系统。示例性地，通信设备为车载装置。示例性地，通信设备例如为第三设备1800。
通信装置1800包括处理模块1810和收发模块1820。示例性地，通信装置1800可以是第三设备，也可以是应用于第三设备中的芯片或者其他具有上述第三设备功能的组合器件、部件等。当通信装置1800是第三设备时，收发模块1820可以是收发器，可以包括天线和射频电路等，处理模块1810可以是处理器，例如基带处理器，基带处理器中可以包 括一个或多个CPU。当通信装置1800是具有上述第三设备的功能的部件时，收发模块1820可以是射频单元，处理模块1810可以是处理器，例如基带处理器。当通信装置1800是芯片系统时，收发模块1820可以是芯片系统(例如基带芯片)的输入输出接口、处理模块可以是芯片系统的处理器，可以包括一个或多个中央处理单元。
其中，处理模块1810可以用于执行图2所示的实施例中由第三设备所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程。收发模块1820可以用于执行图2所示的实施例中由第三设备所执行的全部收发操作，例如S201、S202和S204，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1810可以用于执行图4所示的实施例中由第三设备所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程。收发模块1820可以用于执行图4所示的实施例中由第三设备所执行的全部收发操作，例如S401、S402、S403、S405和S409，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1810可以用于执行图6所示的实施例中由网关所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程。收发模块1820可以用于执行图6所示的实施例中由网关所执行的全部收发操作，例如S601、S603、S605、S607和S610，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1810可以用于执行图7所示的实施例中由网关所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程。收发模块1820可以用于执行图7所示的实施例中由网关所执行的全部收发操作，例如S701、S703和S705，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1810可以用于执行图8所示的实施例中由网关所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程。收发模块1820可以用于执行图8所示的实施例中由网关所执行的全部收发操作，例如S801、S803、S805、S807、S810和S812，和/或用于支持本文所描述的技术的其它过程。
或者，处理模块1810可以用于执行图11所示的实施例中由网关所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程。收发模块1820可以用于执行图11所示的实施例中由网关所执行的全部收发操作，例如S1101、S1103、S1105、S1107和S1108，和/或用于支持本文所描述的技术的其它过程。
另外，收发模块1820可以是一个功能模块，该功能模块既能完成发送操作也能完成接收操作，例如收发模块1820可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为收发模块1820是发送模块，而在执行接收操作时，可以认为收发模块1820是接收模块；或者，收发模块1820也可以是两个功能模块的统称，这两个功能模块分别为发送模块和接收模块，发送模块用于完成发送操作，例如发送模块可以用于执行图2所示的 实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部发送操作，接收模块用于完成接收操作，例如接收模块可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部接收操作。
例如，收发模块1820，用于接收来自第一设备的第一信息和第一证书，所述第一信息用于指示第二设备，所述第一证书为所述第一设备的设备证书；
处理模块1810，用于根据所述第一信息，查找对应的所述第二设备；
收发模块1820，还用于将所述第一信息和所述第一证书发送给所述第二设备，所述第一证书用于所述第二设备对所述第一设备进行认证。
作为一种可选的实施方式，所述第一信息包括第一业务的标识。
作为一种可选的实施方式，所述第一信息为第一业务的标识，处理模块1810用于通过如下方式根据所述第一信息，查找对应的所述第二设备：
根据所述第一业务的标识，查找与所述第一业务相关的所述第二设备。
作为一种可选的实施方式，所述第一证书不包括所述第一证书的主题属性信息。
作为一种可选的实施方式，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
应理解，本申请实施例中的处理模块1810可以由处理器或处理器相关电路组件实现，收发模块1820可以由收发器或收发器相关电路组件实现。
如图19所示，本申请实施例还提供一种通信装置1900。示例性地，通信装置1900例如为第三设备1900。示例性地，通信装置1900可以是通信设备，例如为终端设备，或者也可以是芯片系统等。通信装置1900包括处理器1910。可选的，还可以包括存储器1920。可选的，还可以包括收发器1930。其中，存储器1920中存储计算机指令或程序，处理器1910可以执行存储器1920中存储的计算机指令或程序。存储器1920中存储的计算机指令或程序被执行时，该处理器1910用于执行上述实施例中处理模块1810执行的操作，收发器1930用于执行上述实施例中收发模块1820执行的操作。或者，通信装置1900也可以不包括存储器1920，例如存储器位于通信装置1900外部，在外部存储器所存储的计算机指令或程序被执行时，该处理器1910用于执行上述实施例中处理模块1810执行的操作，收发器1930用于执行上述实施例中收发模块1820执行的操作。
其中，收发器1930可以是一个功能单元，该功能单元既能完成发送操作也能完成接收操作，例如收发器1930可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为收发器1930是发送器，而在执行接收操作时，可以认为收发器1930是接收器；或者，收发器1930也可以是两个功能单元的统称，这两个功能单元分别为发送器和接收器，发送器用于完成发送操作，例如发送器可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部发送操作，接收器用于完成接收操作，例如接收器可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由 第三设备所执行的全部接收操作。
另外，如果通信装置1900是芯片系统，则收发器1930也可以通过该芯片系统的通信接口实现，该通信接口与通信设备中的射频收发组件连接，以通过射频收发组件实现信息的收发。通信接口可以是一个功能单元，该功能单元既能完成发送操作也能完成接收操作，例如通信接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为通信接口是发送接口，而在执行接收操作时，可以认为通信接口是接收接口；或者，通信接口也可以是两个功能单元的统称，这两个功能单元分别为发送接口和接收接口，发送接口用于完成发送操作，例如发送接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部发送操作，接收接口用于完成接收操作，例如接收接口可以用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部接收操作。
应理解，根据本申请实施例的通信装置1800或通信装置1900可实现图2所示的实施例至图12所示的实施例中的任一个实施例中的第三设备的功能，并且通信装置1800或通信装置1900中的各个模块的操作和/或功能分别为了实现图2所示的实施例至图12所示的实施例中的任一个实施例中的相应流程，为了简洁，在此不再赘述。
图20为本申请实施例提供的通信装置2000的示意性框图。通信装置2000可以是通信设备，或是能够支持通信设备实现该方法所需的功能的装置，例如芯片系统。示例性地，通信设备为车载装置。示例性地，通信设备例如为第二设备2000。
通信装置2000包括处理模块2010和收发模块2020。示例性地，通信装置2000可以是第二设备，也可以是应用于第二设备中的芯片或者其他具有上述第二设备功能的组合器件、部件等。当通信装置2000是第二设备时，收发模块2020可以是收发器，可以包括天线和射频电路等，处理模块2010可以是处理器，例如基带处理器，基带处理器中可以包括一个或多个CPU。当通信装置2000是具有上述第二设备的功能的部件时，收发模块2020可以是射频单元，处理模块2010可以是处理器，例如基带处理器。当通信装置2000是芯片系统时，收发模块2020可以是芯片系统(例如基带芯片)的输入输出接口、处理模块可以是芯片系统的处理器，可以包括一个或多个中央处理单元。
其中，处理模块2010可以用于执行图13所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S1301～S1303，和/或用于支持本文所描述的技术的其它过程。收发模块2020可以用于执行图13所示的实施例中由第二设备所执行的全部收发操作，例如S1303，和/或用于支持本文所描述的技术的其它过程。
另外，收发模块2020可以是一个功能模块，该功能模块既能完成发送操作也能完成接收操作，例如收发模块2020可以用于执行图13所示的实施例中由第二设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为收发模块2020是发送模块，而在执行接收操作时，可以认为收发模块2020是接收模块；或者，收发模块2020也可以是两个功能模块的统称，这两个功能模块分别为发送模块和接收模块，发送模块用于完成发送操作，例如发送模块可以用于执行图13所示的实施例中由第二设备所执行的全部发送操作，接收模块用于完成接收操作，例如接收模块可以用于执行图13所示的实施例中的任一个实施例中由第二设备所执行的全部接收操作。
例如，处理模块2010，用于对第一设备认证失败；
处理模块2010，还用于根据第一业务，确定第一执行策略，所述认证对应于所述第一业务；
收发模块2020，用于将所述第一执行策略发送给所述第一设备，或，所述处理模块，还用于执行所述第一执行策略。
作为一种可选的实施方式，所述第一执行策略包括，设备停止工作，或，设备停止使用所述设备的部分功能。
作为一种可选的实施方式，
收发模块2020，还用于接收来自所述第一设备的第一信息和第一证书，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；
处理模块2010，还用于根据所述第一设备的第三证书，验证所述第一证书是否正确；
处理模块2010，还用于当所述第一证书正确时，生成第一随机数；
收发模块，还用于将所述第一随机数发送给所述第一设备；
收发模块2020，还用于接收来自所述第一设备的第一签名；
处理模块2010，还用于根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
作为一种可选的实施方式，所述第一证书不包括所述第一证书的主题属性信息。
作为一种可选的实施方式，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
所述第一证书的版本信息；
所述第一证书的签名者信息；
所述第一证书的主题信息；
所述第一证书的有效性信息；或，
所述第一证书的签名信息。
应理解，本申请实施例中的处理模块2010可以由处理器或处理器相关电路组件实现，收发模块2020可以由收发器或收发器相关电路组件实现。
如图21所示，本申请实施例还提供一种通信装置2100。示例性地，通信装置2100例如为第二设备2100。示例性地，通信装置2100可以是通信设备，例如为终端设备，或者也可以是芯片系统等。通信装置2100包括处理器2110。可选的，还可以包括存储器2120。可选的，还可以包括收发器2130。其中，存储器2120中存储计算机指令或程序，处理器2110可以执行存储器2120中存储的计算机指令或程序。存储器2120中存储的计算机指令或程序被执行时，该处理器2110用于执行上述实施例中处理模块2010执行的操作，收发器2130用于执行上述实施例中收发模块2020执行的操作。或者，通信装置2100也可以不包括存储器2120，例如存储器位于通信装置2100外部，在外部存储器所存储的计算机指令或程序被执行时，该处理器2110用于执行上述实施例中处理模块2010执行的操作，收发器2130用于执行上述实施例中收发模块2020执行的操作。
其中，收发器2130可以是一个功能单元，该功能单元既能完成发送操作也能完成接收操作，例如收发器2130可以用于执行图13所示的实施例中由第二设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为收发器2130是发送器，而在执行接收操作时，可以认为收发器2130是接收器；或者，收发器2130也可以是两个功能单元的统称，这两个功能单元分别为发送器和接收器，发送器用于完成发送操作，例如发送 器可以用于执行图13所示的实施例中由第二设备所执行的全部发送操作，接收器用于完成接收操作，例如接收器可以用于执行图13所示的实施例中的任一个实施例中由第二设备所执行的全部接收操作。
另外，如果通信装置2100是芯片系统，则收发器2130也可以通过该芯片系统的通信接口实现，该通信接口与通信设备中的射频收发组件连接，以通过射频收发组件实现信息的收发。通信接口可以是一个功能单元，该功能单元既能完成发送操作也能完成接收操作，例如通信接口可以用于执行图13所示的实施例中的任一个实施例中由第二设备所执行的全部发送操作和接收操作，例如，在执行发送操作时，可以认为通信接口是发送接口，而在执行接收操作时，可以认为通信接口是接收接口；或者，通信接口也可以是两个功能单元的统称，这两个功能单元分别为发送接口和接收接口，发送接口用于完成发送操作，例如发送接口可以用于执行图13所示的实施例中的任一个实施例中由第二设备所执行的全部发送操作，接收接口用于完成接收操作，例如接收接口可以用于执行图13所示的实施例中的任一个实施例中由第二设备所执行的全部接收操作。
应理解，根据本申请实施例的通信装置2000或通信装置2100可实现图13所示的实施例中的任一个实施例中的第二设备的功能，并且通信装置2000或通信装置2100中的各个模块的操作和/或功能分别为了实现图13所示的实施例中的任一个实施例中的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供一种通信装置，该通信装置可以是终端设备也可以是电路。该通信装置可以用于执行上述方法实施例中由第一设备、第二设备或第三设备所执行的动作。
当该通信装置为设备时，图22示出了一种简化的设备的结构示意图。便于理解和图示方便，图22中，该设备以终端设备作为例子。如图22所示，设备包括处理器、存储器、射频电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对该设备进行控制，执行软件程序，处理软件程序的数据等。存储器主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。需要说明的是，有些种类的设备可以不具有输入输出装置。
当需要发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到该设备时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。为便于说明，图22中仅示出了一个存储器和处理器。在实际的设备产品中，可以存在一个或多个处理器和一个或多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以是独立于处理器设置，也可以是与处理器集成在一起，本申请实施例对此不做限制。
在本申请实施例中，可以将具有收发功能的天线和射频电路视为该设备的收发单元，将具有处理功能的处理器视为该设备的处理单元。如图22所示，该设备包括收发单元2210和处理单元2220。收发单元也可以称为收发器、收发机、收发装置等。处理单元也可以称为处理器，处理单板，处理模块、处理装置等。可选的，可以将收发单元2210中用于实现接收功能的器件视为接收单元，将收发单元2210中用于实现发送功能的器件视为发送单元，即收发单元2210包括接收单元和发送单元。收发单元有时也可以称为收发机、收 发器、或收发电路等。接收单元有时也可以称为接收机、接收器、或接收电路等。发送单元有时也可以称为发射机、发射器或者发射电路等。
或者，应理解，收发单元2210也可以用于执行上述方法实施例中第一设备侧的发送操作和接收操作，处理单元2220用于执行上述方法实施例中第一设备上除了收发操作之外的其他操作。
例如，在一种实现方式中，收发单元2210用于执行图2所示的实施例中第一设备的全部发送操作和接收操作，例如S201、S202和S204，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图2所示的实施例中由第一设备所执行的除了收发操作之外的全部操作，例如S203，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图3所示的实施例中第一设备的全部发送操作和接收操作，例如S301、S302和S304，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图3所示的实施例中由第一设备所执行的除了收发操作之外的全部操作，例如S303，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图4所示的实施例中第一设备的全部发送操作和接收操作，例如S401、S402、S403、S405和S409，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图4所示的实施例中由第一设备所执行的除了收发操作之外的全部操作，例如S406～S408，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图5所示的实施例中第一设备的全部发送操作和接收操作，例如S501、S502、S503、S505和S509，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图5所示的实施例中由第一设备所执行的除了收发操作之外的全部操作，例如S506～S508，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图6所示的实施例中T-Box的全部发送操作和接收操作，例如S601、S603、S605、S607和S610，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图6所示的实施例中由T-Box所执行的除了收发操作之外的全部操作，例如S604、S608和S609，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图7所示的实施例中MDC的全部发送操作和接收操作，例如S701、S703和S705，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图7所示的实施例中由MDC所执行的除了收发操作之外的全部操作，例如S704，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图8所示的实施例中MDC的全部发送操作和接收操作，例如S801、S803、S805、S807、S810和S812，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图8所示的实施例中由MDC所执行的除了收发操作之外的全部操作，例如S804、S808和S809，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图9所示的实施例中sensor的全部发送操作和接收操作，例如S901、S903、S905、S907和S908，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图9所示的实施例中由sensor所执行的除了收发操作之外的全部操作，例如S904，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图10所示的实施例中PEPS的全部发送操作和接收操作，例如S1001、S1003、S1005、S1007和S1008，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图10所示的实施例中由PEPS所执行的除了收发操作之外的全部操作，例如S1004，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图11所示的实施例中BCM的全部发送操作和接收操作，例如S1101、S1103、S1105、S1107和S1108，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图11所示的实施例中由BCM所执行的除了收发操作之外的全部操作，例如S1104，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图12所示的实施例中OBC的全部发送操作和接收操作，例如S1201、S1203、S1205、S1207和S1208，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图12所示的实施例中由OBC所执行的除了收发操作之外的全部操作，例如S1204，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
应理解，收发单元2210可以用于执行上述方法实施例中第二设备侧的发送操作和接收操作，处理单元2220用于执行上述方法实施例中第二设备上除了收发操作之外的其他操作。
例如，在一种实现方式中，收发单元2210用于执行图2所示的实施例中第二设备的全部发送操作和接收操作，例如S201、S202和S204，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图2所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S205和S206，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图3所示的实施例中第二设备的全部发送操作和接收操作，例如S301、S302和S304，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图3所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S305和S306，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图4所示的实施例中第二设备的全部发送操作和接收操作，例如S401、S402、S403、S405和S409，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图4所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S404、S410和S411，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图5所示的实施例中第二设备的全部发送操作和接收操作，例如S501、S502、S503、S505和S509，和/或收发单元2210 还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图5所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S504、S510和S511，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图6所示的实施例中MDC的全部发送操作和接收操作，例如S601、S603、S605、S607和S610，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图6所示的实施例中由MDC所执行的除了收发操作之外的全部操作，例如S602、S606和S611，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图7所示的实施例中VCU的全部发送操作和接收操作，例如S701、S703和S705，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图7所示的实施例中由VCU所执行的除了收发操作之外的全部操作，例如S702和S706，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图8所示的实施例中HMI的全部发送操作和接收操作，例如S801、S803、S805、S807、S810和S812，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图8所示的实施例中由HMI所执行的除了收发操作之外的全部操作，例如S802、S806和S811，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图9所示的实施例中MDC的全部发送操作和接收操作，例如S901、S903、S905、S907和S908，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图9所示的实施例中由MDC所执行的除了收发操作之外的全部操作，例如S902和S906，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图10所示的实施例中BCM的全部发送操作和接收操作，例如S1001、S1003、S1005、S1007和S1008，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图10所示的实施例中由BCM所执行的除了收发操作之外的全部操作，例如S1002和S1006，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图11所示的实施例中VCU的全部发送操作和接收操作，例如S1101、S1103、S1105、S1107和S1108，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图11所示的实施例中由VCU所执行的除了收发操作之外的全部操作，例如S1102和S1106，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图12所示的实施例中VCU的全部发送操作和接收操作，例如S1201、S1203、S1205、S1207和S1208，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图12所示的实施例中由VCU所执行的除了收发操作之外的全部操作，例如S1202和S1206，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图13所示的实施例中第二设备的全部发送操作和接收操作，例如S1303，和/或收发单元2210还用于执行支持本文所描 述的技术的其它过程。处理单元2220，用于执行图13所示的实施例中由第二设备所执行的除了收发操作之外的全部操作，例如S1301～S1303，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
或者，应理解，收发单元2210也可以用于执行上述方法实施例中第三设备侧的发送操作和接收操作，处理单元2220用于执行上述方法实施例中第三设备上除了收发操作之外的其他操作。
例如，在一种实现方式中，收发单元2210用于执行图2所示的实施例中第三设备的全部发送操作和接收操作，例如S201、S202和S204，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图2所示的实施例中由第三设备所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图4所示的实施例中第三设备的全部发送操作和接收操作，例如S401、S402、S403、S405和S409，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图4所示的实施例中由第三设备所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图6所示的实施例中网关的全部发送操作和接收操作，例如S601、S603、S605、S607和S610，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图6所示的实施例中由网关所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图7所示的实施例中网关的全部发送操作和接收操作，例如S701、S703和S705，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图7所示的实施例中由网关所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图8所示的实施例中网关的全部发送操作和接收操作，例如S801、S803、S805、S807、S810和S812，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图8所示的实施例中由网关所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或处理单元2220还用于执行支持本文所描述的技术的其它过程。
又例如，在一种实现方式中，收发单元2210用于执行图11所示的实施例中网关的全部发送操作和接收操作，例如S1101、S1103、S1105、S1107和S1108，和/或收发单元2210还用于执行支持本文所描述的技术的其它过程。处理单元2220，用于执行图11所示的实施例中由网关所执行的除了收发操作之外的全部操作，例如根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或处理单元2220还用于执行支持本文所描述 的技术的其它过程。
当该通信装置为芯片类的装置或者电路时，该装置可以包括收发单元和处理单元。其中，所述收发单元可以是输入输出电路和/或通信接口；处理单元为集成的处理器或者微处理器或者集成电路。
本实施例中的通信装置为终端设备时，可以参照图23所示的设备。作为一个例子，该设备可以完成类似于图15中处理器1510的功能。或者，作为一个例子，该设备可以完成类似于图17中处理器1710的功能。或者，作为一个例子，该设备可以完成类似于图19中处理器1910的功能。或者，作为一个例子，该设备可以完成类似于图21中处理器2110的功能。在图23中，该设备包括处理器2310，发送数据处理器2320，接收数据处理器2330。上述实施例中的处理模块1410可以是图23中的该处理器2310，并完成相应的功能；上述实施例中的收发模块1420可以是图23中的发送数据处理器2320，和/或接收数据处理器2330。或者，上述实施例中的处理模块1610可以是图23中的该处理器2310，并完成相应的功能；上述实施例中的收发模块1620可以是图23中的发送数据处理器2320，和/或接收数据处理器2330。或者，上述实施例中的处理模块1810可以是图23中的该处理器2310，并完成相应的功能；上述实施例中的收发模块1820可以是图23中的发送数据处理器2320，和/或接收数据处理器2330。或者，上述实施例中的处理模块2010可以是图23中的该处理器2310，并完成相应的功能；上述实施例中的收发模块2020可以是图23中的发送数据处理器2320，和/或接收数据处理器2330。虽然图23中示出了信道编码器、信道解码器，但是可以理解这些模块并不对本实施例构成限制性说明，仅是示意性的。
图24示出本实施例的另一种形式。处理装置2400中包括调制子系统、中央处理子系统、周边子系统等模块。本实施例中的通信装置可以作为其中的调制子系统。具体的，该调制子系统可以包括处理器2403，接口2404。其中，处理器2403完成上述处理模块1410的功能，接口2404完成上述收发模块1420的功能。或者，处理器2403完成上述处理模块1610的功能，接口2404完成上述收发模块1620的功能。或者，处理器2403完成上述处理模块1810的功能，接口2404完成上述收发模块1820的功能。或者，处理器2403完成上述处理模块2010的功能，接口2404完成上述收发模块2020的功能。作为另一种变形，该调制子系统包括存储器2406、处理器2403及存储在存储器2406上并可在处理器上运行的程序，该处理器2403执行该程序时实现上述方法实施例中第一设备、第二设备或第三设备侧的方法。需要注意的是，所述存储器2406可以是非易失性的，也可以是易失性的，其位置可以位于调制子系统内部，也可以位于处理装置2400中，只要该存储器2406可以连接到所述处理器2403即可。
本申请实施例提供第一通信系统。第一通信系统可以包括至少一个上述的图2所示的实施例至图12所示的实施例中的任一个实施例所涉及的第一设备，以及包括至少一个上述的图2所示的实施例至图12所示的实施例中的任一个实施例所涉及的第二设备。第一设备例如为图14中的通信装置1400或图15中的通信装置1500。例如，第一设备可用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第一设备所执行的全部操作，例如：图2所示的实施例中的S201～S204，和/或用于支持本文所描述的技术的其它过程；或者，图3所示的实施例中的S301～S304，和/或用于支持本文所描述的技术的其它过程；或者，图4所示的实施例中的S401～S403、S405～S409，和/或用于支持本文所描述的技术的其它过程；或者，图5所示的实施例中的S501～S503、S505～S509，和/或用于 支持本文所描述的技术的其它过程；或者，图6所示的实施例中的S601、S603～S606、S607～S610，和/或用于支持本文所描述的技术的其它过程；或者，图7所示的实施例中的S701、S703、S704和S705，和/或用于支持本文所描述的技术的其它过程；或者，图8所示的实施例中的S801、S803、S805、S807、S810、S812、S804、S808和S809，和/或用于支持本文所描述的技术的其它过程；或者，图9所示的实施例中的S901、S903、S904、S905、S907和S908，和/或用于支持本文所描述的技术的其它过程；或者，图10所示的实施例中的S1001、S1003、S1004、S1005、S1007和S1008，和/或用于支持本文所描述的技术的其它过程；或者，图11所示的实施例中的S1101、S1103、S1104、S1105、S1107和S1108，和/或用于支持本文所描述的技术的其它过程；或者，图12所示的实施例中的S1201、S1203、S1204、S1205、S1207和S1208，和/或用于支持本文所描述的技术的其它过程。
第二设备例如为图16中的通信装置1600或图17中的通信装置1700。第二设备可用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第二设备所执行的全部操作，例如：图2所示的实施例中的S201、S202、S204、S205和S206，和/或用于支持本文所描述的技术的其它过程；或者，图3所示的实施例中的S301、S302、S304、S305和S306，和/或用于支持本文所描述的技术的其它过程；或者，图4所示的实施例中的S401、S402、S403、S405、S409、S404、S410和S411，和/或用于支持本文所描述的技术的其它过程；或者，图5所示的实施例中的S501、S502、S503、S505、S509、S504、S510和S511，和/或用于支持本文所描述的技术的其它过程；或者，图6所示的实施例中的S601、S603、S605、S607和S610、S602、S606和S611，和/或用于支持本文所描述的技术的其它过程；或者，图7所示的实施例中的S701、S703、S705、S702和S706，和/或用于支持本文所描述的技术的其它过程；或者，图8所示的实施例中的S801、S803、S805、S807、S810、S812、S802、S806和S811，和/或用于支持本文所描述的技术的其它过程；或者，图9所示的实施例中的S901、S903、S905、S907、S908、S902和S906，和/或用于支持本文所描述的技术的其它过程；或者，图10所示的实施例中的S1001、S1003、S1005、S1007、S1008、S1002和S1006，和/或用于支持本文所描述的技术的其它过程；或者，图11所示的实施例中的S1101、S1103、S1105、S1107、S1108、S1102和S1106，和/或用于支持本文所描述的技术的其它过程；或者，图12所示的实施例中的S1201、S1203、S1205、S1207、S1208、S1202和S1206，和/或用于支持本文所描述的技术的其它过程。
可选的，第一通信系统还可以包括至少一个上述的图2所示的实施例至图12所示的实施例中的任一个实施例所涉及的第三设备。第三设备例如为图18中的通信装置1800或图19中的通信装置1900。第三设备可用于执行图2所示的实施例至图12所示的实施例中的任一个实施例中由第三设备所执行的全部操作，例如：图2所示的实施例中的S201、S202和S204，根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程；或者，图4所示的实施例中的S401、S402、S403、S405和S409，根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程；或者，图6所示的实施例中的S601、S603、S605、S607和S610，根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程；或者，图7所示的实施例中的S701、S703和S705，根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支 持本文所描述的技术的其它过程；或者，图8所示的实施例中的S801、S803、S805、S807、S810和S812，根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程；或者，图11所示的实施例中的S1101、S1103、S1105、S1107和S1108，根据第一信息查询第二设备的操作，或根据第一信息进行过滤的操作，和/或用于支持本文所描述的技术的其它过程。
本申请实施例提供第二通信系统。第二通信系统可以包括至少一个上述的图13所示的实施例所涉及的第二设备。第二设备例如为图20中的通信装置2000或图21中的通信装置2100。第二设备可用于执行图13所示的实施例中由第二设备所执行的全部操作，例如：图13所示的实施例中的S1301～S1303，和/或用于支持本文所描述的技术的其它过程。
可选的，第二通信系统还可以包括至少一个上述的图2所示的实施例至图12所示的实施例中的任一个实施例所涉及的第一设备。
可选的，第二通信系统还可以包括至少一个上述的图2所示的实施例至图12所示的实施例中的任一个实施例所涉及的第三设备。
如上的两个通信系统可以是同一通信系统，或者也可以分别是不同的通信系统。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图2所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图3所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图4所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图5所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图6所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图7所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图8所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图9所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图10 所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图11所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图12所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图2所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图3所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图4所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图5所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图6所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图7所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图8所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图9所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图10所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图11所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图12所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图13所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图2所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图4所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图6所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图7所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图8所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图11所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图2所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图3所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图4所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图5所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图6所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图7所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序， 该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图8所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图9所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图10所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图11所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图12所示的实施例中与第一设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图2所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图3所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图4所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图5所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图6所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图7所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图8所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图9所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图10所示的 实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图11所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图12所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图13所示的实施例中与第二设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图2所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图4所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图6所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图7所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图8所示的实施例中与第三设备相关的流程。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品用于存储计算机程序，该计算机程序被计算机执行时，所述计算机可以实现上述方法实施例提供的图11所示的实施例中与第三设备相关的流程。
应理解，本申请实施例中提及的处理器可以是CPU，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、 同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应所述以权利要求的保护范围为准。

Claims (52)

  1. 一种设备认证方法，其特征在于，包括：
    第一设备将第一信息和第一证书发送给第二设备，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；
    所述第一设备接收来自所述第二设备的第一随机数；
    所述第一设备采用第一私钥，根据所述第一随机数和第一标识，得到第一签名，所述第一标识为所述第一设备的标识；
    所述第一设备将所述第一签名发送给第二设备，所述第一签名用于对所述第一设备进行认证。
  2. 根据权利要求1所述的方法，其特征在于，所述第一信息包括第一业务的标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一设备生成第二随机数；
    所述第一设备将所述第二随机数发送给所述第二设备。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收来自所述第二设备的第二签名和第二标识，所述第二标识为所述第二设备的标识；
    所述第一设备根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证。
  5. 根据权利要求1～4任一项所述的方法，其特征在于，所述第一证书不包括所述第一证书的主题属性信息。
  6. 根据权利要求1～5任一项所述的方法，其特征在于，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
    所述第一证书的版本信息；
    所述第一证书的签名者信息；
    所述第一证书的主题信息；
    所述第一证书的有效性信息；或，
    所述第一证书的签名信息。
  7. 根据权利要求1～6任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收来自所述第二设备的指示信息，所述指示信息用于指示对所述第一设备认证失败，或，用于指示所述第一设备停止工作或停止使用所述第一设备的部分功能；
    所述第一设备停止工作，或停止使用所述第一设备的部分功能。
  8. 一种设备认证方法，其特征在于，包括：
    第二设备接收来自第一设备的第一信息和第一证书，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；
    所述第二设备根据所述第一设备的根证书或二级证书，验证所述第一证书是否正确；
    当所述第一证书正确时，所述第二设备生成第一随机数；
    所述第二设备将所述第一随机数发送给所述第一设备；
    所述第二设备接收来自所述第一设备的第一签名；
    所述第二设备根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行 认证，所述第一标识为所述第一设备的标识。
  9. 根据权利要求8所述的方法，其特征在于，所述第一信息包括第一业务的标识。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述第二设备接收来自所述第一设备的第二随机数；
    当对所述第一设备认证通过时，所述第二设备采用第二私钥，根据所述第二随机数和所述第二标识生成第二签名；
    所述第二设备将所述第二签名和第二标识发送给所述第一设备，所述第二签名用于对所述第二设备进行认证，所述第二标识为所述第二设备的标识。
  11. 根据权利要求8～10任一项所述的方法，其特征在于，所述第一证书不包括所述第一证书的主题属性信息。
  12. 根据权利要求8～11任一项所述的方法，其特征在于，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
    所述第一证书的版本信息；
    所述第一证书的签名者信息；
    所述第一证书的主题信息；
    所述第一证书的有效性信息；或，
    所述第一证书的签名信息。
  13. 根据权利要求8～12任一项所述的方法，其特征在于，所述方法还包括：
    当对所述第一设备认证失败时，所述第二设备向所述第一设备发送指示信息，所述指示信息用于指示对所述第一设备认证失败，或，用于指示所述第一设备停止工作或停止使用所述第一设备的部分功能；或，
    当对所述第一设备认证失败时，所述第二设备停止工作或所述第二设备停止使用所述第二设备的部分功能。
  14. 一种设备认证方法，其特征在于，包括：
    第三设备接收来自第一设备的第一信息和第一证书，所述第一信息用于指示第二设备，所述第一证书为所述第一设备的设备证书；
    根据所述第一信息，查找对应的所述第二设备；
    将所述第一信息和所述第一证书发送给所述第二设备，所述第一证书用于所述第二设备对所述第一设备进行认证。
  15. 根据权利要求14所述的方法，其特征在于，所述第一信息包括第一业务的标识。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一信息为第一业务的标识，根据所述第一信息，查找对应的所述第二设备，包括：
    根据所述第一业务的标识，查找与所述第一业务相关的所述第二设备。
  17. 根据权利要求14～16任一项所述的方法，其特征在于，所述第一证书不包括所述第一证书的主题属性信息。
  18. 根据权利要求14～17任一项所述的方法，其特征在于，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
    所述第一证书的版本信息；
    所述第一证书的签名者信息；
    所述第一证书的主题信息；
    所述第一证书的有效性信息；或，
    所述第一证书的签名信息。
  19. 一种设备认证方法，其特征在于，包括：
    第二设备对第一设备认证失败；
    所述第二设备根据第一业务，确定第一执行策略，所述认证对应于所述第一业务；
    所述第二设备将所述第一执行策略发送给所述第一设备，或，所述第二设备执行所述第一执行策略。
  20. 根据权利要求19所述的方法，其特征在于，所述第一执行策略包括，设备停止工作，或，设备停止使用所述设备的部分功能。
  21. 根据权利要求19或20所述的方法，其特征在于，所述方法还包括：
    所述第二设备接收来自所述第一设备的第一信息和第一证书，所述第一信息用于指示所述第二设备，所述第一证书为所述第一设备的设备证书；
    所述第二设备根据所述第一设备的第三证书，验证所述第一证书是否正确；
    当所述第一证书正确时，所述第二设备生成第一随机数；
    所述第二设备将所述第一随机数发送给所述第一设备；
    所述第二设备接收来自所述第一设备的第一签名；
    所述第二设备根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
  22. 根据权利要求21所述的方法，其特征在于，所述第一证书不包括所述第一证书的主题属性信息。
  23. 根据权利要求21或22所述的方法，其特征在于，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
    所述第一证书的版本信息；
    所述第一证书的签名者信息；
    所述第一证书的主题信息；
    所述第一证书的有效性信息；或，
    所述第一证书的签名信息。
  24. 一种通信装置，其特征在于，包括：
    收发模块，用于将第一信息和第一证书发送给第二设备，所述第一信息用于指示所述第二设备，所述第一证书为所述通信装置的设备证书；
    所述收发模块，还用于接收来自所述第二设备的第一随机数；
    处理模块，用于采用第一私钥，根据所述第一随机数和第一标识，得到第一签名，所述第一标识为所述通信装置的标识；
    所述收发模块，还用于将所述第一签名发送给第二设备，所述第一签名用于对所述通信装置进行认证。
  25. 根据权利要求24所述的通信装置，其特征在于，所述第一信息包括第一业务的标识。
  26. 根据权利要求24或25所述的通信装置，其特征在于，
    所述处理模块，还用于生成第二随机数；
    所述收发模块，还用于将所述第二随机数发送给所述第二设备。
  27. 根据权利要求26所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述第二设备的第二签名和第二标识，所述第二标识为所述第二设备的标识；
    所述处理模块，还用于根据所述第二签名、所述第二随机数和所述第二标识对所述第二设备进行认证。
  28. 根据权利要求24～27任一项所述的通信装置，其特征在于，所述第一证书不包括所述第一证书的主题属性信息。
  29. 根据权利要求24～28任一项所述的通信装置，其特征在于，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
    所述第一证书的版本信息；
    所述第一证书的签名者信息；
    所述第一证书的主题信息；
    所述第一证书的有效性信息；或，
    所述第一证书的签名信息。
  30. 根据权利要求24～29任一项所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述第二设备的指示信息，所述指示信息用于指示对所述通信装置认证失败，或，用于指示所述通信装置停止工作或停止使用所述通信装置的部分功能；
    所述处理模块，还用于令所述通信装置停止工作，或停止使用所述通信装置的部分功能。
  31. 一种通信装置，其特征在于，包括：
    收发模块，用于接收来自第一设备的第一信息和第一证书，所述第一信息用于指示所述通信装置，所述第一证书为所述第一设备的设备证书；
    处理模块，用于根据所述第一设备的根证书或二级证书，验证所述第一证书是否正确；
    所述处理模块，还用于当所述第一证书正确时，生成第一随机数；
    所述收发模块，还用于将所述第一随机数发送给所述第一设备；
    所述收发模块，还用于接收来自所述第一设备的第一签名；
    所述处理模块，还用于根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
  32. 根据权利要求31所述的通信装置，其特征在于，所述第一信息包括第一业务的标识。
  33. 根据权利要求31或32所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述第一设备的第二随机数；
    所述处理模块，还用于当对所述第一设备认证通过时，采用第二私钥，根据所述第二随机数和所述第二标识生成第二签名；
    所述收发模块，还用于将所述第二签名和第二标识发送给所述第一设备，所述第二签名用于对所述通信装置进行认证，所述第二标识为所述通信装置的标识。
  34. 根据权利要求31～33任一项所述的通信装置，其特征在于，所述第一证书不包括所述第一证书的主题属性信息。
  35. 根据权利要求31～34任一项所述的通信装置，其特征在于，所述第一证书包括如 下的一种信息或如下多种信息的任意组合：
    所述第一证书的版本信息；
    所述第一证书的签名者信息；
    所述第一证书的主题信息；
    所述第一证书的有效性信息；或，
    所述第一证书的签名信息。
  36. 根据权利要求31～35任一项所述的通信装置，其特征在于，
    所述收发模块，还用于当所述处理模块对所述第一设备认证失败时，向所述第一设备发送指示信息，所述指示信息用于指示对所述第一设备认证失败，或，用于指示所述第一设备停止工作或停止使用所述第一设备的部分功能；或，
    所述处理模块，还用于当对所述第一设备认证失败时，令所述通信装置停止工作或停止使用所述通信装置的部分功能。
  37. 一种通信装置，其特征在于，包括：
    收发模块，用于接收来自第一设备的第一信息和第一证书，所述第一信息用于指示第二设备，所述第一证书为所述第一设备的设备证书；
    处理模块，用于根据所述第一信息，查找对应的所述第二设备；
    所述收发模块，还用于将所述第一信息和所述第一证书发送给所述第二设备，所述第一证书用于所述第二设备对所述第一设备进行认证。
  38. 根据权利要求37所述的通信装置，其特征在于，所述第一信息包括第一业务的标识。
  39. 根据权利要求37或38所述的通信装置，其特征在于，所述第一信息为第一业务的标识，所述处理模块用于通过如下方式根据所述第一信息，查找对应的所述第二设备：
    根据所述第一业务的标识，查找与所述第一业务相关的所述第二设备。
  40. 根据权利要求37～39任一项所述的通信装置，其特征在于，所述第一证书不包括所述第一证书的主题属性信息。
  41. 根据权利要求37～40任一项所述的通信装置，其特征在于，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
    所述第一证书的版本信息；
    所述第一证书的签名者信息；
    所述第一证书的主题信息；
    所述第一证书的有效性信息；或，
    所述第一证书的签名信息。
  42. 一种通信装置，其特征在于，包括：
    处理模块，用于对第一设备认证失败；
    所述处理模块，还用于根据第一业务，确定第一执行策略，所述认证对应于所述第一业务；
    收发模块，用于将所述第一执行策略发送给所述第一设备，或，所述第二设备执行所述第一执行策略。
  43. 根据权利要求42所述的通信装置，其特征在于，所述第一执行策略包括，设备停止工作，或，设备停止使用所述设备的部分功能。
  44. 根据权利要求42或43所述的通信装置，其特征在于，
    所述收发模块，还用于接收来自所述第一设备的第一信息和第一证书，所述第一信息用于指示所述通信装置，所述第一证书为所述第一设备的设备证书；
    所述处理模块，还用于根据所述第一设备的第三证书，验证所述第一证书是否正确；
    所述处理模块，还用于当所述第一证书正确时，生成第一随机数；
    所述收发模块，还用于将所述第一随机数发送给所述第一设备；
    所述收发模块，还用于接收来自所述第一设备的第一签名；
    所述处理模块，还用于根据所述第一签名、所述第一随机数和第一标识，对所述第一设备进行认证，所述第一标识为所述第一设备的标识。
  45. 根据权利要求44所述的通信装置，其特征在于，所述第一证书不包括所述第一证书的主题属性信息。
  46. 根据权利要求44或45所述的通信装置，其特征在于，所述第一证书包括如下的一种信息或如下多种信息的任意组合：
    所述第一证书的版本信息；
    所述第一证书的签名者信息；
    所述第一证书的主题信息；
    所述第一证书的有效性信息；或，
    所述第一证书的签名信息。
  47. 一种通信系统，其特征在于，包括如权利要求24～30中任意一项所述的通信装置，以及如权利要求31～36中任意一项所述的通信装置。
  48. 根据权利要求47所述的通信系统，其特征在于，所述通信系统还包括如权利要求37～41中任意一项所述的通信装置。
  49. 一种通信系统，其特征在于，包括如权利要求42～46中任意一项所述的通信装置。
  50. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1～7中任意一项所述的方法，或使得所述计算机执行如权利要求8～13中任意一项所述的方法，或使得所述计算机执行如权利要求14～18中任意一项所述的方法，或使得所述计算机执行如权利要求19～23中任意一项所述的方法。
  51. 一种芯片系统，其特征在于，所述芯片系统包括：
    通信接口，用于与其他装置进行通信；
    处理器，用于使得安装有所述芯片系统的通信装置执行如权利要求1～7中任意一项所述的方法，或使得所述通信装置执行如权利要求8～13中任意一项所述的方法，或使得所述通信装置执行如权利要求14～18中任意一项所述的方法，或使得所述通信装置执行如权利要求19～23中任意一项所述的方法。
  52. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行如权利要求1～7中任意一项所述的方法，或使得所述计算机执行如权利要求8～13中任意一项所述的方法，或使得所述计算机执行如权利要求14～18中任意一项所述的方法，或使得所述计算机执行如权利要求19～23中任意一项所述的方法。
PCT/CN2020/092176 2019-09-19 2020-05-25 一种设备认证方法及装置 WO2021051852A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
MX2021009397A MX2021009397A (es) 2019-09-19 2020-05-25 Metodo y aparato de autenticacion de dispositivo.
KR1020217021420A KR102476107B1 (ko) 2019-09-19 2020-05-25 디바이스 인증 방법 및 장치
EP20866025.8A EP3923613A4 (en) 2019-09-19 2020-05-25 METHOD AND APPARATUS FOR DEVICE AUTHENTICATION
JP2021542509A JP2022531815A (ja) 2019-09-19 2020-05-25 デバイス認証方法および装置
US17/368,382 US11392685B2 (en) 2019-09-19 2021-07-06 Device authentication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910886787.9 2019-09-19
CN201910886787.9A CN112533195B (zh) 2019-09-19 2019-09-19 一种设备认证方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/368,382 Continuation US11392685B2 (en) 2019-09-19 2021-07-06 Device authentication method and apparatus

Publications (1)

Publication Number Publication Date
WO2021051852A1 true WO2021051852A1 (zh) 2021-03-25

Family

ID=74883913

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/092176 WO2021051852A1 (zh) 2019-09-19 2020-05-25 一种设备认证方法及装置

Country Status (7)

Country Link
US (1) US11392685B2 (zh)
EP (1) EP3923613A4 (zh)
JP (1) JP2022531815A (zh)
KR (1) KR102476107B1 (zh)
CN (1) CN112533195B (zh)
MX (1) MX2021009397A (zh)
WO (1) WO2021051852A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114785521A (zh) * 2022-04-15 2022-07-22 深圳汇辰软件有限公司 认证方法、装置、电子设备及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11386791B2 (en) * 2019-03-29 2022-07-12 GM Cruise Holdings, LLC Autonomous vehicle fleet management system
CN113568986B (zh) * 2021-07-06 2024-05-10 东风汽车集团股份有限公司 远程联网终端生产数据匹配方法及系统
CN114662082B (zh) * 2022-02-25 2023-06-06 荣耀终端有限公司 电子设备的访问控制方法、可读介质和电子设备
CN114666154B (zh) * 2022-04-08 2023-11-24 深圳市欧瑞博科技股份有限公司 设备通信方法、装置、网关、设备、系统、介质和产品
CN114785531B (zh) * 2022-06-22 2022-10-18 广州万协通信息技术有限公司 一种基于服务节点切换的双向认证方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017201753A1 (zh) * 2016-05-27 2017-11-30 华为技术有限公司 一种移动网络的认证方法和装置
CN107919955A (zh) * 2017-12-28 2018-04-17 北京奇虎科技有限公司 一种车辆网络安全认证方法、系统、车辆、装置及介质
US20180205560A1 (en) * 2014-06-23 2018-07-19 Google Llc Per-device authentication
CN108377184A (zh) * 2018-01-09 2018-08-07 清华大学 一种智能汽车内部网络分布式认证加密方法
CN109495441A (zh) * 2018-09-10 2019-03-19 北京车和家信息技术有限公司 接入认证方法、装置、相关设备及计算机可读存储介质
CN109808697A (zh) * 2019-01-16 2019-05-28 北京百度网讯科技有限公司 车辆控制方法、装置及设备

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2728033B2 (ja) * 1995-05-23 1998-03-18 日本電気株式会社 コンピュータネットワークにおけるセキュリティ方式
JP2001350534A (ja) * 2000-06-08 2001-12-21 Nec Eng Ltd 有償ソフトウェアのダウンロード方法及びシステム
CN101051898B (zh) * 2006-04-05 2010-04-21 华为技术有限公司 无线网络端到端通信认证方法及其装置
JP2008001133A (ja) * 2006-06-20 2008-01-10 Tokai Rika Co Ltd 車両用セキュリティ制御装置
JP4838916B2 (ja) * 2006-08-01 2011-12-14 株式会社日立ソリューションズ クライアントサーバシステム
US9148422B2 (en) * 2006-11-30 2015-09-29 Mcafee, Inc. Method and system for enhanced wireless network security
CN101136915B (zh) * 2007-10-16 2011-08-10 中兴通讯股份有限公司 一种实现多业务统一安全认证的方法和系统
JP5085430B2 (ja) * 2008-05-22 2012-11-28 デルタ エレクトロニックス，インコーポレイテッド 車両構成部品のための電子盗難防止システム
KR20130064217A (ko) * 2011-12-08 2013-06-18 (주)바소콤 장치 대 장치서비스를 제공하기 위한 제어모듈시스템 및 방법
US9264419B1 (en) * 2014-06-26 2016-02-16 Amazon Technologies, Inc. Two factor authentication with authentication objects
FR3032293B1 (fr) * 2015-02-03 2018-03-23 Stmicroelectronics (Rousset) Sas Procede d'authentification d'un objet par un dispositif capables de communiquer mutuellement sans contact, systeme et objet correspondants
CN105083218B (zh) * 2015-07-16 2018-10-19 浙江吉利汽车研究院有限公司 车辆启动方法
CN105292020B (zh) 2015-10-29 2018-02-13 东莞酷派软件技术有限公司 车辆控制方法、车辆控制装置和终端
CN105282179B (zh) * 2015-11-27 2018-12-25 中国电子科技集团公司第五十四研究所 一种基于cpk的家庭物联网安全控制的方法
CN107182052A (zh) 2016-03-11 2017-09-19 阿里巴巴集团控股有限公司 网络接入方法、装置及系统
WO2018012078A1 (ja) * 2016-07-14 2018-01-18 ソニー株式会社 認証装置及び認証方法
JP6873066B2 (ja) * 2018-01-15 2021-05-19 三菱電機株式会社 認証装置、認証方法および認証システム
CN109617698B (zh) * 2019-01-09 2021-08-03 腾讯科技（深圳）有限公司 发放数字证书的方法、数字证书颁发中心和介质
CN110177001A (zh) * 2019-05-21 2019-08-27 广东联合电子服务股份有限公司 一种基于软证书的nfc圈存方法、系统及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180205560A1 (en) * 2014-06-23 2018-07-19 Google Llc Per-device authentication
WO2017201753A1 (zh) * 2016-05-27 2017-11-30 华为技术有限公司 一种移动网络的认证方法和装置
CN107919955A (zh) * 2017-12-28 2018-04-17 北京奇虎科技有限公司 一种车辆网络安全认证方法、系统、车辆、装置及介质
CN108377184A (zh) * 2018-01-09 2018-08-07 清华大学 一种智能汽车内部网络分布式认证加密方法
CN109495441A (zh) * 2018-09-10 2019-03-19 北京车和家信息技术有限公司 接入认证方法、装置、相关设备及计算机可读存储介质
CN109808697A (zh) * 2019-01-16 2019-05-28 北京百度网讯科技有限公司 车辆控制方法、装置及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3923613A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114785521A (zh) * 2022-04-15 2022-07-22 深圳汇辰软件有限公司 认证方法、装置、电子设备及存储介质
CN114785521B (zh) * 2022-04-15 2024-05-14 深圳成谷科技有限公司 认证方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
US11392685B2 (en) 2022-07-19
US20210334353A1 (en) 2021-10-28
EP3923613A1 (en) 2021-12-15
KR102476107B1 (ko) 2022-12-08
MX2021009397A (es) 2021-09-10
JP2022531815A (ja) 2022-07-12
KR20210097797A (ko) 2021-08-09
CN112533195A (zh) 2021-03-19
EP3923613A4 (en) 2022-06-22
CN112533195B (zh) 2023-03-10

Similar Documents

Publication Publication Date Title
WO2021051852A1 (zh) 一种设备认证方法及装置
US11951944B2 (en) Localization and passive entry/passive start systems and methods for vehicles
US11597350B2 (en) Passive entry/passive start systems and methods for vehicles
JP7430817B2 (ja) 通信方法、装置、およびシステム
CN111049651A (zh) 一种车载智能计算装置、云端服务器以及唤醒方法
JP7367032B2 (ja) 識別確認方法および装置
Pese Bringing Practical Security to Vehicles
Sanchez Carmona Pedestrian to Vehicle Communication: A Safe and Private Solution Proposal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20866025

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20217021420

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021542509

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020866025

Country of ref document: EP

Effective date: 20210908

NENP Non-entry into the national phase

Ref country code: DE