Clock synchronization method and apparatus, storage medium

Abstract

The present disclosure provides a clock synchronization method and device, and a storage medium. The method comprises: in response to being unable to synchronize the clock with the background server of the vehicle, sending a system time synchronization request message to a terminal device; wherein the system time synchronization request message is used to request to synchronize the clock with the terminal device; receiving a system time synchronization response message returned by the terminal device; and synchronizing the clock of a telematics controller on the vehicle based on a first clock included in the system time synchronization response message. In the present disclosure, the vehicle can synchronize the clock with the terminal device in the case of being unable to synchronize the clock with the background server of the vehicle, and timely complete the clock synchronization of the vehicle. Subsequently, the validity period of the digital vehicle key can be verified based on the clock synchronized from the terminal device, thereby improving the security of the use of the digital vehicle key.

Description

Technical Field

[0001] This disclosure relates to the field of communications, and more particularly to a clock synchronization method, apparatus, and storage medium. Background Technology

[0002] Currently, when a user uses a digital car key, the vehicle can check whether the digital car key is valid.

[0003] However, if a vehicle loses its current clock for some reason, such as reverting to an earlier initial clock, and if there are network problems preventing the vehicle from synchronizing its clock with the backend server, the vehicle's clock will increment based on the initial clock. This means that a digital car key that should have expired can still be used, which poses a risk and compromises security. Summary of the Invention

[0004] In view of this, this application discloses a clock synchronization method, apparatus, and storage medium.

[0005] According to a first aspect of the present disclosure, a clock synchronization method is provided, the method being applied to a vehicle, the method comprising:

[0006] In response to the inability to synchronize the clock with the vehicle's backend server, a system time synchronization request message is sent to the terminal device; wherein, the system time synchronization request message is used to request clock synchronization with the terminal device;

[0007] Receive the system time synchronization response message returned by the terminal device;

[0008] The clock of the telematics processor on the vehicle is synchronized based on the first clock included in the system time synchronization response message.

[0009] Optionally, the method further includes:

[0010] In response to the remote information processor performing a reset operation and the vehicle being unable to establish a connection with the backend server, it is determined that clock synchronization with the vehicle's backend server is not possible.

[0011] Optionally, the system time synchronization request message includes at least one of the following fields:

[0012] The first name field is used to indicate the message name;

[0013] The first identifier field is used to indicate the message identifier;

[0014] The first parameter field is used to indicate the parameters requested by the system time synchronization request message.

[0015] Optionally, the first parameter field includes at least a clock type field.

[0016] Optionally, the system time synchronization response message includes at least one of the following fields:

[0017] A second name field used to indicate the message name;

[0018] A second identifier field used to indicate the message identifier;

[0019] The second parameter field is used to indicate the parameters included in the system time synchronization response message.

[0020] Optionally, the second parameter field includes at least one of the following:

[0021] Clock type field;

[0022] A clock information field used to indicate the first clock;

[0023] A status field used to indicate whether the clock type requested by the system time synchronization request message has been successfully returned;

[0024] A signature field used to sign the clock type field, the clock information field, and the status field.

[0025] Optionally, the clock type field indicates any of the following in ascending order of type priority:

[0026] Accepts any clock from the terminal device;

[0027] Receive the network clock from the terminal device;

[0028] The terminal device returns a local clock and signs the local clock;

[0029] The terminal device returns the network clock and signs the network clock.

[0030] Optionally, the method further includes:

[0031] The information in the signature field included in the system time synchronization response message is verified based on the public key of the digital car key to obtain the verification result;

[0032] In response to the verification result indicating that the information in the signature field is valid, the step of synchronizing the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message is performed.

[0033] Optionally, the system time synchronization request message is used to request a clock of a first type priority.

[0034] The method further includes:

[0035] In response to determining that the system time synchronization response information indicates that the terminal device cannot provide a clock of the first type priority, a new system time synchronization request message is sent to the terminal device; wherein, the new system time synchronization request message is used to request a clock of the second type priority, and the second type priority is lower than the first type priority;

[0036] Receive the new system time synchronization response message returned by the terminal device;

[0037] The clock of the telematics processor on the vehicle is synchronized based on the second type priority clock included in the new system time synchronization response message.

[0038] Optionally, the system time synchronization request message is used to request a clock of a first type priority.

[0039] The method further includes:

[0040] In response to the determination that the number of times the system time synchronization request message has been sent has reached a specified number, and the system time synchronization response messages returned by the terminal device all indicate that the terminal device cannot provide a clock of the first type priority, a new system time synchronization request message is sent to the terminal device; wherein, the new system time synchronization request message is used to request a clock of the second type priority, and the second type priority is lower than the first type priority;

[0041] Receive the new system time synchronization response message returned by the terminal device;

[0042] The clock of the telematics processor on the vehicle is synchronized based on the second type priority clock included in the new system time synchronization response message.

[0043] Optionally, after synchronizing the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message, the method further includes:

[0044] Obtain the second clock from the backend server;

[0045] The clock of the telematics processor on the vehicle is synchronized based on the second clock.

[0046] Optionally, before sending a system time synchronization request message to the terminal device, the method further includes:

[0047] Establish a connection with the terminal device.

[0048] According to a second aspect of the present disclosure, a clock synchronization method is provided, the method being applied to a terminal device, the method comprising:

[0049] Receive a system time synchronization request message sent by the vehicle when it is unable to synchronize its clock with the vehicle's backend server; wherein the system time synchronization request message is used to request clock synchronization with the terminal device;

[0050] A system time synchronization response message is sent to the vehicle, and the vehicle synchronizes the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message.

[0051] Optionally, the system time synchronization request message includes at least one of the following fields:

[0052] The first name field is used to indicate the message name;

[0053] The first identifier field is used to indicate the message identifier;

[0054] The first parameter field is used to indicate the parameters requested by the system time synchronization request message.

[0055] Optionally, the first parameter field includes at least a clock type field.

[0056] Optionally, the system time synchronization response message includes at least one of the following fields:

[0057] A second name field used to indicate the message name;

[0058] A second identifier field used to indicate the message identifier;

[0059] The second parameter field is used to indicate the parameters included in the system time synchronization response message.

[0060] Optionally, the second parameter field includes at least one of the following:

[0061] Clock type field;

[0062] A clock information field used to indicate the first clock;

[0063] A status field used to indicate whether the clock type requested by the system time synchronization request message has been successfully returned;

[0064] A signature field used to sign the clock type field, the clock information field, and the status field.

[0065] Optionally, the clock type field indicates any of the following in ascending order of type priority:

[0066] Accepts any clock from the terminal device;

[0067] Receive the network clock from the terminal device;

[0068] The terminal device returns a local clock and signs the local clock;

[0069] The terminal device returns the network clock and signs the network clock.

[0070] Optionally, after receiving the system time synchronization request message, the method further includes:

[0071] Obtain the first clock requested by the system time synchronization request message.

[0072] Optionally, when the system time synchronization request message is used to request the terminal device to return the network clock, obtaining the first clock requested by the system time synchronization request message includes any one of the following:

[0073] Obtain the first clock from the backend server;

[0074] If the local clock of the terminal device is obtained from the network side, the local clock of the terminal device is obtained.

[0075] Optionally, before sending a system time synchronization response message to the vehicle, the method further includes:

[0076] Using the private key of the digital car key, the information of the clock type field, the clock information field, and the clock status field included in the system time synchronization response message is signed to determine the information of the signature field.

[0077] Optionally, when the system time synchronization request message is used to request a clock of a first type priority, sending the system time synchronization response message to the vehicle includes:

[0078] In response to the inability to obtain a clock of the first type priority, a system time synchronization response message is sent to the vehicle indicating that the terminal device is unable to provide a clock of the first type priority.

[0079] Optionally, the method further includes:

[0080] Receive a new system time synchronization request message sent by the vehicle; wherein the new system time synchronization request message is used to request a clock of a second type priority, and the second type priority is lower than the first type priority;

[0081] After obtaining the clock of the second type priority, a new system time synchronization response message including the clock of the second type priority is sent to the vehicle.

[0082] Optionally, before receiving the system time synchronization request message, the method further includes:

[0083] Establish a connection with the vehicle.

[0084] According to a third aspect of the present disclosure, a clock synchronization device is provided, the device being applied to a vehicle, the device comprising:

[0085] The first sending module is used to send a system time synchronization request message to the terminal device in response to the inability to synchronize the clock with the vehicle's backend server; wherein the system time synchronization request message is used to request clock synchronization with the terminal device;

[0086] The first receiving module is used to receive the system time synchronization response message returned by the terminal device;

[0087] The first synchronization module is used to synchronize the clock of the remote information processor on the vehicle based on the first clock included in the system time synchronization response message.

[0088] According to a fourth aspect of the present disclosure, a clock synchronization device is provided, the device being applied to a terminal device, the device comprising:

[0089] The second receiving module is used to receive a system time synchronization request message sent by the vehicle when it is unable to synchronize its clock with the vehicle's backend server; wherein the system time synchronization request message is used to request clock synchronization with the terminal device;

[0090] The second sending module is used to send a system time synchronization response message to the vehicle, so that the vehicle synchronizes the clock of the remote information processor on the vehicle based on the first clock included in the system time synchronization response message.

[0091] According to a fifth aspect of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the clock synchronization method described in any of the above-described vehicle-side embodiments.

[0092] According to a sixth aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the clock synchronization method described in any of the above-described terminal device side.

[0093] According to a seventh aspect of the present disclosure, a clock synchronization device is provided, comprising:

[0094] processor;

[0095] Memory used to store processor-executable instructions;

[0096] The processor is configured to execute the executable instructions to implement the steps of the clock synchronization method described in any of the above-described vehicle-side methods.

[0097] According to an eighth aspect of the present disclosure, a clock synchronization device is provided, comprising:

[0098] processor;

[0099] Memory used to store processor-executable instructions;

[0100] The processor is configured to execute the executable instructions to implement the steps of the clock synchronization method described in any one of the above-described terminal device side.

[0101] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0102] In this disclosure, the vehicle can synchronize its clock with the terminal device even when it is unable to synchronize its clock with the vehicle's backend server, thus completing the vehicle's clock synchronization in a timely manner. Subsequently, the validity period of the digital car key can be verified based on the clock synchronized from the terminal device, thereby improving the security of the use of the digital car key.

[0103] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0104] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0105] Figure 1 This is a flowchart illustrating a clock synchronization method according to an exemplary embodiment of the present disclosure;

[0106] Figure 2 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0107] Figure 3 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0108] Figure 4 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0109] Figure 5 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0110] Figure 6 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0111] Figure 7 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0112] Figure 8 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0113] Figure 9 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0114] Figure 10 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0115] Figure 11 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0116] Figure 12 This is a flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0117] Figure 13 A flowchart illustrating another clock synchronization method according to an exemplary embodiment of the present disclosure;

[0118] Figure 14 A block diagram of a clock synchronization device according to an exemplary embodiment of the present disclosure;

[0119] Figure 15 A block diagram of another clock synchronization device illustrated in an exemplary embodiment of the present disclosure;

[0120] Figure 16 A schematic diagram of a clock synchronization device according to an exemplary embodiment is disclosed.

[0121] Figure 17 A schematic diagram of another clock synchronization device according to an exemplary embodiment is disclosed. Detailed Implementation

[0122] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0123] Considering the possibility of an unexpected power outage, the vehicle will lose its current clock. For example, if the vehicle loses power, or the T-BOX (Telematics Box) performs a reset, or in other circumstances, the vehicle's clock may revert to an initial value, such as January 1, 1970. In this case, the vehicle will attempt to synchronize the T-BOX clock with its backend server. However, if there are network issues, such as the vehicle being located in an underground parking garage or mountainous area with poor signal coverage, the T-BOX clock may fail to synchronize with the server. In this case, the T-BOX clock will increment according to the initial value.

[0124] Suppose a vehicle owner shares a digital car key with a Friend device via the Owner device, and the digital car key is valid for 4 hours. However, since the T-BOX clock increments based on the initial value, the usable validity period of the digital car key is far longer than the validity period expected by the vehicle owner. In this case, the use of the digital car key faces risks and has poor security.

[0125] To address this technical problem, this disclosure provides the following clock synchronization method. The clock synchronization method provided in this disclosure will first be introduced from the vehicle side.

[0126] Reference Figure 1 As shown, Figure 1 This is a flowchart illustrating a clock synchronization method according to an exemplary embodiment of the present disclosure. This embodiment is described from the vehicle side, as follows: Figure 1 As shown, the clock synchronization method may include the following steps:

[0127] In step 101, in response to the inability to synchronize the clock with the vehicle's backend server, a system time synchronization request message is sent to the terminal device.

[0128] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, used to request clock synchronization with the terminal device. The terminal device can be a terminal device that has previously established a connection with the vehicle, including but not limited to mobile phones, laptops, desktop computers, iPads, etc.

[0129] In one possible implementation, if the vehicle determines that the T-BOX has been reset and the vehicle is unable to establish a connection with the backend server, it determines that it cannot synchronize its clock with the backend server.

[0130] In another possible implementation, if a vehicle loses power and loses its current clock, it is determined that it cannot synchronize its clock with the backend server if it is unable to establish a connection with the backend server.

[0131] The above is merely an illustrative example. In actual applications, the reasons why a vehicle cannot synchronize its clock with the vehicle's backend server, i.e., obtain the correct clock, should all fall within the scope of protection of this disclosure.

[0132] In step 102, a system time synchronization response message returned by the terminal device is received.

[0133] In this embodiment of the disclosure, the system time synchronization response message can be represented as SystemTimeSync_res. This system time synchronization response message can be used to provide feedback on the first clock requested for synchronization by the vehicle, and for the terminal device to sign the clock-related information provided in the feedback.

[0134] In step 103, the clock of the telematics processor on the vehicle is synchronized based on the first clock included in the system time synchronization response message.

[0135] In the above embodiments, the vehicle can synchronize its clock with the terminal device even when it is unable to synchronize its clock with the vehicle's backend server, thus completing the vehicle's clock synchronization in a timely manner. Subsequently, the validity period of the digital car key can be verified based on the clock synchronized from the terminal device, thereby improving the security of the use of the digital car key.

[0136] In some optional embodiments, this disclosure provides an exemplary description of a system time synchronization request message. The message format of the system time synchronization request message, as well as the fields included and their meanings, can be agreed upon in the protocol. When a vehicle is unable to synchronize its clock with its backend server, it can send a system time synchronization request message in a specified format to the terminal device according to the protocol, in order to synchronize its clock with the terminal device.

[0137] In this embodiment of the disclosure, the system time synchronization request message may include, but is not limited to, at least one of the following fields: a first name field for indicating the message name; a first identifier field for indicating the message identifier; and a first parameter field for indicating the parameters requested by the system time synchronization request message.

[0138] The first name field can be represented as the Message field, and the first name field can indicate that the message name is SystemTimeSync_req.

[0139] The first identifier field can be represented as the Message ID field, and the value of the first identifier field can be 0x20.

[0140] The first parameter field can be represented as a Parameters field, and it can include at least a clock type field. The clock type field can be represented as a ClockTimeType field.

[0141] The message format for the system time synchronization request message can be found in Table 1.

[0142] Table 1

[0143]

[0144] It should be noted that each field in Table 1 can be deployed independently or in combination with other fields; this disclosure does not impose any limitations on this. In one possible implementation, the clock type field in the system time synchronization request message can be used to indicate the type of clock requested by the system time synchronization request message.

[0145] In another possible implementation, the length or number of bits occupied by the clock type field in the system time synchronization request message is 1.

[0146] In another possible implementation, the clock type field in the system time synchronization request message can range from 0 to 0xFE.

[0147] In another possible implementation, the clock type field in the system time synchronization request message can use different values ​​to represent different clock types. Specifically, a clock type field value of 00 indicates that the clock type is any clock of the receiving terminal device. A clock type field value of 01 indicates that the clock type is the network clock of the receiving terminal device. A clock type field value of 02 indicates that the clock type is the local clock returned by the terminal device, and the local clock is signed. A clock type field value of 03 indicates that the clock type is the network clock returned by the terminal device, and the network clock is signed.

[0148] In another possible implementation, in addition to the values ​​mentioned above, the clock type field can also be configured with reserved values ​​for different future use cases.

[0149] In another possible implementation, different values ​​in the clock type field correspond to different type priorities.

[0150] Specifically, the clock type field indicates, in order of priority from low to high, any clock of the receiving terminal device, the network clock of the receiving terminal device, the local clock returned by the terminal device and signed by the local clock, and the network clock returned by the terminal device and signed by the network clock.

[0151] Among them, the clock type field indicates that the type priority corresponding to any clock of the receiving terminal device can be the lowest, and the clock type field indicates that the terminal device returns the network clock, and the type priority corresponding to signing the network clock can be the highest.

[0152] In this embodiment of the disclosure, the vehicle can prioritize requesting the clock with the highest type priority. For example, if the clock type field indicates the highest type priority and is set to 03, then when the vehicle is unable to synchronize its clock with the backend server, the clock type field in the system time synchronization request message sent to the terminal device is preferably set to 03.

[0153] If the system time synchronization response message returned by the terminal device indicates that it cannot provide a clock of the highest priority type, the vehicle can send a new system time synchronization request message to the terminal device, sequentially reducing the type priority indicated by the clock type field. For example, the clock type field value in the new system time synchronization request message can be adjusted to 02. If the system time synchronization response message returned by the terminal device still indicates that it cannot provide a clock of the 02 priority type, the vehicle can again sequentially reduce the type priority indicated by the clock type field. For example, the clock type field value in the new system time synchronization request message can be 01. This process continues until a clock of the type priority requested by the terminal device is obtained, or until the terminal device returns a clock that cannot provide the lowest priority type.

[0154] In another possible implementation, different values ​​in the clock type field correspond to different type priorities and different clock types.

[0155] Specifically, a value of 00 for the clock type field indicates that the clock type is any clock from the receiving terminal device, with the lowest type priority. A value of 01 for the clock type field indicates that the clock type is the network clock from the receiving terminal device, with a type priority higher than the lowest type priority. A value of 02 for the clock type field indicates that the clock type is a local clock returned by the terminal device and signed, and also indicates a type priority higher than the type priority when the value is 01. A value of 03 for the clock type field indicates that the clock type is a network clock returned by the terminal device and signed, and also indicates the highest type priority.

[0156] In addition, the first parameter field in the system time synchronization request message is further defined in this embodiment, as shown in Table 2.

[0157] Table 2

[0158]

[0159] It should be noted that in practical applications, each row or column in Table 2 can be deployed individually or in combination with other rows or columns. Table 2 is only an illustrative example and may be described in other ways. This disclosure does not limit this.

[0160] The above is an illustrative description. In practical applications, at least one field included in the actual synchronization request message provided by the system based on the solution of this disclosure, as well as the specific explanation of each field, should fall within the protection scope of this disclosure.

[0161] The above embodiments provide a message format for a vehicle to send a system time synchronization request message to a terminal device. The vehicle can request clock synchronization with the terminal device through the system time synchronization request message, which is simple to implement and highly available.

[0162] In some optional embodiments, this disclosure provides an exemplary description of system time synchronization response messages. The message format of the system time synchronization response message, as well as the fields included and their meanings, can be agreed upon in the protocol. The vehicle can receive system time synchronization response messages in a specified format sent by the terminal device according to the protocol, so as to perform clock synchronization on the vehicle side.

[0163] In this embodiment of the disclosure, the system time synchronization response message may include, but is not limited to, at least one of the following fields: a second name field for indicating the message name; a second identifier field for indicating the message identifier; and a second parameter field for indicating the parameters included in the system time synchronization response message.

[0164] The second name field can be represented as the Message field, and the second name field can indicate that the message name is SystemTimeSync_res.

[0165] The second identifier field can be represented as the Message ID field, and the value of the second identifier field can be 0x21.

[0166] The second parameter field can be represented as a Parameters field, and may include, but is not limited to, at least one of the following fields: a clock type field; a clock information field indicating the first clock; a clock status field indicating whether the clock type requested by the system time synchronization request message was successfully returned; and a signature field for signing the clock type field, the clock information field, and the status field. Wherein, the clock type field can be represented as a ClockTimeType field, the clock information field can be represented as a ClockTime field, the status field can be represented as a Status field, and the signature field can be represented as a Sig field.

[0167] The message format and field explanations for the system time synchronization response message are shown in Table 3.

[0168] Table 3

[0169]

[0170] It should be noted that each field in Table 3 can be deployed individually or in combination with other fields, and this disclosure does not impose any restrictions on this.

[0171] In one possible implementation, the clock type field in the system time synchronization response message can be used to indicate the type of clock fed back by the system time synchronization response message, or it can indicate the type of clock requested by the system time synchronization request message, and this disclosure does not limit it in this way.

[0172] The description of the clock type field in the system time synchronization response message is similar to that in the system time synchronization request message, and will not be repeated here.

[0173] In this embodiment of the disclosure, the clock information field can be used to provide feedback to the vehicle on the specific value of the first clock that the vehicle requests to synchronize.

[0174] In one possible implementation, the clock information field has a length or occupies 8 bits.

[0175] In another possible implementation, the clock information field can take values ​​from 0 to 0xFFFFFFFFFFFFFFFF.

[0176] In another possible implementation, the clock information field indicates a specific value for the first clock in megaseconds of UTC (Universal Time Coordinated) time.

[0177] In this embodiment of the disclosure, the status field is further defined.

[0178] In one possible implementation, the length of the status field, or the number of bits it occupies, is 2.

[0179] In another possible implementation, a status field value of 0000 can be used to indicate that a clock of the type requested by the system time synchronization request message was successfully returned. A status field value of 0001 can be used to indicate that a clock of the type requested by the system time synchronization request message could not be successfully returned. For example, the terminal device cannot obtain the network clock requested by the vehicle from the network-side device. The network-side device can be a base station or the vehicle's backend server, etc., and this disclosure does not limit this to any particular device.

[0180] In another possible implementation, the status field may include reserved values ​​for other clock sources. Here, "other clock sources" refers to clock sources other than the local clock and network clock of this disclosure.

[0181] In this embodiment of the disclosure, the signature field is further defined.

[0182] In one possible implementation, the signature field has a length or number of bits occupied of 64.

[0183] In another possible implementation, the signature field is used to sign at least one other field in the second parameter field besides the signature field. These other fields include, but are not limited to, the clock type field, the clock information field, and the status field of this disclosure.

[0184] In this embodiment of the disclosure, the second parameter field in the system time synchronization request message is further defined, as shown in Table 4.

[0185] Table 4

[0186]

[0187]

[0188] It should be noted that in practical applications, each row or column in Table 4 can be deployed individually or in combination with other rows or columns. Table 4 is only an illustrative example and may be described in other ways. This disclosure does not limit this.

[0189] The above is merely an illustrative example. In actual applications, at least one field included in the system's actual synchronous response message based on the scheme of this disclosure, as well as the specific explanation of each field, should fall within the protection scope of this disclosure.

[0190] The above embodiments provide a message format for the terminal device to send a system time synchronization response message to the vehicle, so that the vehicle can perform clock synchronization, which is simple to implement and highly available.

[0191] In some alternative embodiments, refer to Figure 2 As shown, Figure 2 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to vehicles, such as... Figure 2 As shown, the clock synchronization method may include the following steps:

[0192] In step 201, in response to the inability to synchronize the clock with the vehicle's backend server, a system time synchronization request message is sent to the terminal device.

[0193] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, used to request clock synchronization with the terminal device. The terminal device can be a terminal device that has previously established a connection with the vehicle, including but not limited to mobile phones, laptops, desktop computers, iPads, etc.

[0194] In one possible implementation, if the vehicle determines that the T-BOX has been reset and the vehicle is unable to establish a connection with the backend server, it determines that it cannot synchronize its clock with the backend server.

[0195] In another possible implementation, if a vehicle loses power and loses its current clock, it is determined that it cannot synchronize its clock with the backend server if it is unable to establish a connection with the backend server.

[0196] The above is merely an illustrative example. In actual applications, the reasons why a vehicle cannot synchronize its clock with the vehicle's backend server, i.e., obtain the correct clock, should all fall within the scope of protection of this disclosure.

[0197] In step 202, a system time synchronization response message returned by the terminal device is received.

[0198] In this embodiment of the disclosure, the system time synchronization response message can be represented as SystemTimeSync_res. This system time synchronization response message can be used to provide feedback on the first clock requested for synchronization by the vehicle, and for the terminal device to sign the clock-related information provided in the feedback.

[0199] In step 203, the information in the signature field included in the system time synchronization response message is verified based on the public key of the digital car key to obtain the verification result.

[0200] In this embodiment of the disclosure, the vehicle can use the public key of the digital car key to verify the information in the signature field included in the system time synchronization response message.

[0201] In step 204, in response to the verification result indicating that the information in the signature field is valid, the clock of the telematics on the vehicle is synchronized based on the first clock included in the system time synchronization response message.

[0202] In this embodiment of the disclosure, the vehicle can verify the information in the signature field based on the public key. If the signature has not been tampered with, i.e. the information in the signature field is valid, the vehicle can use the first clock included in the system time synchronization response message fed back by the terminal device as a trusted clock source and synchronize the clock of the T-BOX on the vehicle based on the first clock.

[0203] In the above embodiments, the clock source can be verified based on the signature field in the system time synchronization response message returned by the terminal device, and the vehicle clock synchronization can be performed based on the trusted clock source returned by the terminal device, thereby improving the reliability and accuracy of vehicle clock synchronization.

[0204] In some alternative embodiments, refer to Figure 3 As shown, Figure 3 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to vehicles, such as... Figure 3 As shown, the clock synchronization method may include the following steps:

[0205] In step 301, in response to the inability to synchronize the clock with the vehicle's backend server, a system time synchronization request message is sent to the terminal device.

[0206] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, used to request clock synchronization with the terminal device. The terminal device can be a terminal device that has previously established a connection with the vehicle, including but not limited to mobile phones, laptops, desktop computers, iPads, etc.

[0207] In one possible implementation, if the vehicle determines that the T-BOX has been reset and the vehicle is unable to establish a connection with the backend server, it determines that it cannot synchronize its clock with the backend server.

[0208] In another possible implementation, if a vehicle loses power and loses its current clock, it is determined that it cannot synchronize its clock with the backend server if it is unable to establish a connection with the backend server.

[0209] The above is merely an illustrative example. In actual applications, the reasons why a vehicle cannot synchronize its clock with the vehicle's backend server, i.e., obtain the correct clock, should all fall within the scope of protection of this disclosure.

[0210] In this embodiment of the disclosure, the system time synchronization request message is used to request a clock of the first priority type. Assuming that the clock type field included in the system time synchronization request message has a value of 03, according to Table 2, it can be determined that the vehicle requests the terminal device to return a network clock and signs the network clock.

[0211] In step 302, a system time synchronization response message returned by the terminal device is received.

[0212] In step 303, in response to determining that the system time synchronization response information indicates that the terminal device cannot provide a clock of the first type priority, a new system time synchronization request message is sent to the terminal device.

[0213] In this embodiment of the disclosure, the new system time synchronization request message is used to request a clock of a second type priority, and the second type priority is lower than the first type priority.

[0214] Suppose a vehicle requests a network clock from a terminal device and signs the network clock. If the terminal device is located in an area with poor signal coverage, such as an underground parking garage or mountainous region, and cannot obtain a network clock from the network side, then the status field in the system time synchronization response message sent back to the vehicle by the terminal device can have a value of 0001. The vehicle, according to Table 4, determines that the terminal device cannot provide a clock of the first priority type. In this case, the vehicle can send a new system time synchronization request message to the terminal device, and the clock type field in the new system time synchronization request message has a value of 00, 01, or 02. That is, the new system time synchronization request message requests a clock type of the second priority type, which is lower than the first priority type. Optionally, the second priority type can be lower than the first priority type. For example, if the clock type field value is 03 for the first priority type, then the second priority type is preferably set to 02.

[0215] In step 304, a new system time synchronization response message is received from the terminal device.

[0216] In step 305, the clock of the telematics processor on the vehicle is synchronized based on the second type priority clock included in the new system time synchronization response message.

[0217] In the above embodiments, if the vehicle determines that the terminal device cannot provide a clock of the first priority type, it can reduce the type priority of the requested clock type to ensure that clock synchronization with the terminal device can be completed in a timely manner, resulting in high availability.

[0218] In some alternative embodiments, refer to Figure 4 As shown, Figure 4 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to vehicles, such as... Figure 4 As shown, the clock synchronization method may include the following steps:

[0219] In step 401, in response to the inability to synchronize the clock with the vehicle's backend server, a system time synchronization request message is sent to the terminal device.

[0220] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, used to request clock synchronization with the terminal device. The terminal device can be a terminal device that has previously established a connection with the vehicle, including but not limited to mobile phones, laptops, desktop computers, iPads, etc.

[0221] In one possible implementation, if the vehicle determines that the T-BOX has been reset and the vehicle is unable to establish a connection with the backend server, it determines that it cannot synchronize its clock with the backend server.

[0222] The above is merely an illustrative example. In actual applications, the reasons why a vehicle cannot synchronize its clock with the vehicle's backend server, i.e., obtain the correct clock, should all fall within the scope of protection of this disclosure.

[0223] In this embodiment of the disclosure, the system time synchronization request message is used to request a clock of the first priority type. Assuming that the clock type field included in the system time synchronization request message has a value of 03, according to Table 2, it can be determined that the vehicle requests the terminal device to return a network clock and signs the network clock.

[0224] In step 402, a system time synchronization response message returned by the terminal device is received.

[0225] In step 403, in response to the determination that the number of times the system time synchronization request message has been sent has reached a specified number, and that the system time synchronization response messages returned by the terminal device all indicate that the terminal device cannot provide a clock of the first type priority, a new system time synchronization request message is sent to the terminal device.

[0226] In this embodiment of the disclosure, the specified number of times can be determined by agreement or negotiation between the vehicle and the terminal device, and this disclosure does not limit this. The specified number of times can be once or multiple times.

[0227] Suppose the vehicle sends a specified number of system time synchronization request messages to the terminal device, and each received system time synchronization response message indicates that the terminal device cannot provide a clock of the first priority type. In this case, a new system time synchronization request message can be sent to the terminal device. This new system time synchronization request message requests a clock of the second priority type, where the second priority type is lower than the first priority type.

[0228] For example, the clock type field in the previously sent system time synchronization request messages, a specified number of times, has a value of 03. The clock type field in the new system time synchronization request message has a value of 00, 01, or 02. Optionally, the second type priority can be lower than the first type priority; for example, if the clock type field value is 03 in the first type priority setting, then the second type priority setting is preferably 02.

[0229] In step 404, a new system time synchronization response message is received from the terminal device.

[0230] In step 405, the clock of the telematics processor on the vehicle is synchronized based on the second type priority clock included in the new system time synchronization response message.

[0231] In the above embodiments, if the vehicle determines that the terminal device cannot provide a clock of the first priority type a specified number of times, it can reduce the type priority of the requested clock type to ensure that clock synchronization with the terminal device can be completed in a timely manner, resulting in high availability.

[0232] In some alternative embodiments, refer to Figure 5 As shown, Figure 5 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to vehicles, such as... Figure 5 As shown, the clock synchronization method may include the following steps:

[0233] In step 501, in response to the inability to synchronize the clock with the vehicle's backend server, a system time synchronization request message is sent to the terminal device.

[0234] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, used to request clock synchronization with the terminal device. The terminal device can be a terminal device that has previously established a connection with the vehicle, including but not limited to mobile phones, laptops, desktop computers, iPads, etc.

[0235] In one possible implementation, if the vehicle determines that the T-BOX has been reset and the vehicle is unable to establish a connection with the backend server, it determines that it cannot synchronize its clock with the backend server.

[0236] In another possible implementation, if a vehicle loses power and loses its current clock, it is determined that it cannot synchronize its clock with the backend server if it is unable to establish a connection with the backend server.

[0237] The above is merely an illustrative example. In actual applications, the reasons why a vehicle cannot synchronize its clock with the vehicle's backend server, i.e., obtain the correct clock, should all fall within the scope of protection of this disclosure.

[0238] In step 502, a system time synchronization response message returned by the terminal device is received.

[0239] In step 503, the clock of the telematics processor on the vehicle is synchronized based on the first clock included in the system time synchronization response message.

[0240] In step 504, a second clock is obtained from the backend server.

[0241] In this embodiment of the disclosure, the vehicle re-establishes a connection with the backend server, and can then obtain a second clock from the backend server.

[0242] In step 505, the clock of the telematics processor on the vehicle is synchronized based on the second clock.

[0243] In this embodiment of the disclosure, the vehicle can use a second clock as a new trusted clock source for clock synchronization.

[0244] In the above embodiments, after the vehicle synchronizes its clock with the terminal device, if it re-establishes a connection with the backend server, it can synchronize its clock with the backend server again, ensuring the accuracy of the vehicle's clock synchronization. Subsequently, the validity period of the digital car key can be verified based on the clock synchronized from the terminal device, thereby improving the security of using the digital car key.

[0245] In some alternative embodiments, refer to Figure 6 As shown, Figure 6This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to vehicles, such as... Figure 5 As shown, the clock synchronization method may include the following steps:

[0246] In step 601, a connection is established with the terminal device.

[0247] In this embodiment of the disclosure, the vehicle can establish a connection with the terminal device through any of the following communication methods: Bluetooth, WiFi (Wireless Fidelity), UWB (Ultra Wide Band), NFC (Near Field Communication), etc.

[0248] In step 602, in response to the inability to synchronize the clock with the vehicle's backend server, a system time synchronization request message is sent to the terminal device.

[0249] In this embodiment of the disclosure, the vehicle can send a system time synchronization request message to the terminal device through a connection established with the terminal device.

[0250] In step 603, a system time synchronization response message returned by the terminal device is received.

[0251] In this embodiment of the disclosure, the vehicle can receive a system time synchronization response message returned by the terminal device through a connection established with the terminal device.

[0252] In step 604, the clock of the telematics processor on the vehicle is synchronized based on the first clock included in the system time synchronization response message.

[0253] In the above embodiments, the vehicle can establish a connection with the terminal device in advance. If the vehicle's backend server cannot synchronize its clock, it can synchronize its clock with the terminal device to complete the vehicle's clock synchronization in a timely manner. Subsequently, the validity period of the digital car key can be verified based on the clock synchronized from the terminal device, thereby improving the security of the digital car key.

[0254] The clock synchronization method provided in this disclosure will now be introduced from the perspective of the terminal device.

[0255] Reference Figure 7 As shown, Figure 7 This is a flowchart illustrating a clock synchronization method according to an exemplary embodiment of this disclosure. This embodiment is described from the perspective of a terminal device, wherein the terminal device includes, but is not limited to, mobile phones, laptops, desktop computers, iPads, etc. Figure 7 As shown, the clock synchronization method may include the following steps:

[0256] In step 701, a system time synchronization request message is received from the vehicle when it is unable to synchronize its clock with the vehicle's backend server.

[0257] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, and the system time synchronization request message is used to request clock synchronization with the terminal device.

[0258] In step 702, a system time synchronization response message is sent to the vehicle, and the vehicle synchronizes the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message.

[0259] In this embodiment of the disclosure, the system time synchronization response message can be represented as SystemTimeSync_res. This system time synchronization response message can be used to provide feedback on the first clock requested for synchronization by the vehicle, and for the terminal device to sign the clock-related information provided in the feedback.

[0260] In the above embodiments, the terminal device can return a system time synchronization response message to the vehicle based on a vehicle request. The vehicle then synchronizes the clock of its remote information processor with the first clock included in the system time synchronization response message. This achieves the goal of synchronizing the vehicle's clock with the terminal device even when the vehicle's backend server cannot synchronize its clock. Subsequently, the validity period of the digital car key can be verified based on the clock synchronized from the terminal device, thereby improving the security of the digital car key.

[0261] In some alternative embodiments, this disclosure provides an exemplary description of the system time synchronization request message, which is similar to the exemplary description of the system time synchronization request message on the vehicle side, and will not be repeated here.

[0262] In some alternative embodiments, this disclosure provides exemplary descriptions of system time synchronization response messages, which are similar to exemplary descriptions of system time synchronization response messages on the vehicle side, and will not be repeated here.

[0263] In some alternative embodiments, refer to Figure 8 As shown, Figure 8 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to terminal devices, such as... Figure 8 As shown, the clock synchronization method may include the following steps:

[0264] In step 801, a system time synchronization request message is received from the vehicle when it is unable to synchronize its clock with the vehicle's backend server.

[0265] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, and the system time synchronization request message is used to request clock synchronization with the terminal device.

[0266] In step 802, the first clock requested by the system time synchronization request message is obtained.

[0267] In this embodiment of the disclosure, if the clock type requested by the system time synchronization request message is a local clock, the terminal device obtains its own local clock and uses the local clock as the first clock requested by the vehicle.

[0268] If the system time synchronization request message requests to obtain the network clock, the first clock can be obtained in any of the following ways:

[0269] The first method involves obtaining the first clock from the backend server.

[0270] In this embodiment of the disclosure, the terminal device can obtain the clock from the vehicle's backend server and use that clock as the first clock.

[0271] The second method involves obtaining the local clock of the terminal device when the local clock of the terminal device is obtained from the network side.

[0272] In this embodiment of the disclosure, if the terminal device uses a network clock, then the terminal device can directly use its local clock as the network clock, i.e., the first clock. Obtaining the local clock from the network side here refers to obtaining the local clock from the backend server of the network-side device, including but not limited to the base station or the vehicle.

[0273] In step 803, a system time synchronization response message is sent to the vehicle, and the vehicle synchronizes the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message.

[0274] In this embodiment of the disclosure, the system time synchronization response message can be represented as SystemTimeSync_res. This system time synchronization response message can be used to provide feedback on the first clock requested for synchronization by the vehicle, and for the terminal device to sign the clock-related information provided in the feedback.

[0275] In the above embodiments, the terminal device can return a system time synchronization response message to the vehicle based on a vehicle request. The vehicle then synchronizes the clock of its remote information processor with the first clock included in the system time synchronization response message. This achieves the goal of synchronizing the vehicle's clock with the terminal device even when the vehicle's backend server cannot synchronize its clock. Subsequently, the validity period of the digital car key can be verified based on the clock synchronized from the terminal device, thereby improving the security of the digital car key.

[0276] In some alternative embodiments, refer to Figure 9 As shown, Figure 9 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to terminal devices, such as... Figure 9 As shown, the clock synchronization method may include the following steps:

[0277] In step 901, a system time synchronization request message is received from the vehicle when it is unable to synchronize its clock with the vehicle's backend server.

[0278] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, and the system time synchronization request message is used to request clock synchronization with the terminal device.

[0279] In step 902, the information of the clock type field, clock information field and clock status field included in the system time synchronization response message is signed using the private key of the digital car key, and the information of the signature field is determined.

[0280] In this embodiment of the disclosure, the DK Framework (Digital Key framework) of the terminal device can sign the information of the above-mentioned fields included in the system time synchronization response message using the private key of the digital car key, thereby determining the information of the signature fields included in the system time synchronization response message.

[0281] In step 903, a system time synchronization response message is sent to the vehicle, and the vehicle synchronizes the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message.

[0282] In this embodiment of the disclosure, after receiving the system time synchronization response message, the vehicle can use the public key of the digital vehicle key to verify the information in the signature field included in the system time synchronization response message. If it is determined that the signature has not been tampered with, i.e., the information in the signature field is valid, the first clock included in the system time synchronization response message fed back by the terminal device is used as a trusted clock source, and the clock of the T-BOX on the vehicle is synchronized based on the first clock.

[0283] In the above embodiments, the terminal device can sign the fields in the system time synchronization response message to ensure that the clock source returned to the vehicle is a reliable clock source, thereby improving the reliability and accuracy of vehicle clock synchronization.

[0284] In some alternative embodiments, refer to Figure 10 As shown, Figure 10 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to terminal devices, such as... Figure 10 As shown, the clock synchronization method may include the following steps:

[0285] In step 1001, a system time synchronization request message is received when the vehicle is unable to synchronize its clock with the vehicle's backend server.

[0286] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, and is used to request clock synchronization with the terminal device. Specifically, the system time synchronization request message can be used to request a clock of a first priority type.

[0287] In step 1002, in response to the inability to obtain a clock of the first type priority, a system time synchronization response message indicating that the terminal device cannot provide a clock of the first type priority is sent to the vehicle.

[0288] In this embodiment of the disclosure, the terminal device can set the value of the status field in the second parameter field included in the system time synchronization response message to 0001, which can be used to indicate that the clock of the clock type requested by the system time synchronization request message cannot be successfully returned.

[0289] After receiving the system's time synchronization response message, the vehicle can try to synchronize its clock with the backend server again, or try to synchronize its clock with other terminal devices.

[0290] In the above embodiments, if the terminal device cannot obtain the clock of the first type of priority, it can notify the vehicle through the system time synchronization response message, which facilitates the vehicle to synchronize its clock with other terminal devices or with the backend server again, making it simple and highly available.

[0291] In some alternative embodiments, refer to Figure 11 As shown, Figure 11 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to terminal devices, such as... Figure 11 As shown, the clock synchronization method may include the following steps:

[0292] In step 1101, a system time synchronization request message is received from the vehicle when it is unable to synchronize its clock with the vehicle's backend server.

[0293] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, and is used to request clock synchronization with the terminal device. Specifically, the system time synchronization request message can be used to request a clock of a first priority type.

[0294] In step 1102, in response to the inability to obtain a clock of the first type priority, a system time synchronization response message indicating that the terminal device cannot provide a clock of the first type priority is sent to the vehicle.

[0295] In this embodiment of the disclosure, the terminal device can set the value of the status field in the second parameter field included in the system time synchronization response message to 0001, which can be used to indicate that the clock of the clock type requested by the system time synchronization request message cannot be successfully returned.

[0296] In step 1103, a new system time synchronization request message sent by the vehicle is received.

[0297] In this embodiment of the disclosure, after receiving the system time synchronization response message, the vehicle can re-attempt clock synchronization with the backend server or attempt clock synchronization with other terminal devices. If the vehicle still decides to synchronize its clock with the terminal device, it can send a new system time synchronization request message to the terminal device.

[0298] The new system time synchronization request message is used to request a clock of the second priority type, and the second priority type is lower than the first priority type.

[0299] For example, the clock type field in the previously sent system time synchronization request message had a value of 03. The clock type field in the new system time synchronization request message has a value of 00, 01, or 02.

[0300] Optionally, the priority of the second type can be lower than that of the first type. For example, if the clock type field is 03 when the first type is prioritized, then the priority of the second type is set to 02.

[0301] In step 1104, after obtaining the clock of the second type priority, a new system time synchronization response message including the clock of the second type priority is sent to the vehicle.

[0302] In the above embodiments, if the vehicle determines that the terminal device cannot provide a clock of the first type priority, it can reduce the type priority of the requested clock type to ensure that clock synchronization with the terminal device can be completed in a timely manner, resulting in high availability.

[0303] In some alternative embodiments, refer to Figure 12 As shown, Figure 12 This is a flowchart illustrating an exemplary embodiment of a clock synchronization method disclosed herein. This embodiment can be applied to terminal devices, such as... Figure 12 As shown, the clock synchronization method may include the following steps:

[0304] In step 1201, a connection is established with the vehicle.

[0305] In this embodiment of the disclosure, the terminal device can establish a connection with the vehicle through any of the following communication methods: Bluetooth, WiFi, UWB, NFC, etc.

[0306] In step 1202, a system time synchronization request message is received from the vehicle when it is unable to synchronize its clock with the vehicle's backend server.

[0307] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, and is used to request clock synchronization with the terminal device. Specifically, the system time synchronization request message can be used to request a clock of a first priority type. The terminal can receive this system time synchronization request message through a previously established connection with the vehicle.

[0308] In step 1203, a system time synchronization response message is sent to the vehicle, and the vehicle synchronizes the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message.

[0309] In this embodiment of the disclosure, the system time synchronization response message can be represented as SystemTimeSync_res. This system time synchronization response message can be used to provide feedback on the first clock requested for synchronization by the vehicle, and the terminal device can sign the feedback clock-related information. The terminal device can send the system time synchronization response message to the vehicle through a previously established connection with the vehicle.

[0310] In the above embodiments, the terminal device can return a system time synchronization response message to the vehicle based on a vehicle request. The vehicle then synchronizes the clock of its remote information processor with the first clock included in the system time synchronization response message. This achieves the goal of synchronizing the vehicle's clock with the terminal device even when the vehicle's backend server cannot synchronize its clock. Subsequently, the validity period of the digital car key can be verified based on the clock synchronized from the terminal device, thereby improving the security of the digital car key.

[0311] In some alternative embodiments, refer to Figure 13 As shown, Figure 13 This is a flowchart illustrating a clock synchronization method according to an exemplary embodiment of the present disclosure. The method may include the following steps:

[0312] In step 1301, the vehicle establishes a connection with the terminal device.

[0313] In this embodiment of the disclosure, the vehicle can establish a connection with the terminal device through any of the following communication methods: Bluetooth, WiFi, UWB, NFC, etc.

[0314] In one possible implementation, the vehicle can send an adv_ind message to the terminal device. Once the terminal determines that it has been Bluetooth paired with the vehicle, it sends a Connect_ind message back to the vehicle, thereby establishing a Bluetooth connection with the vehicle.

[0315] In step 1302, in response to the inability to synchronize the clock with the vehicle's backend server, the vehicle sends a system time synchronization request message to the terminal device.

[0316] In this embodiment of the disclosure, the system time synchronization request message can be represented as SystemTimeSync_req, used to request clock synchronization with the terminal device. The terminal device can be a terminal device that has previously established a connection with the vehicle, including but not limited to mobile phones, laptops, desktop computers, iPads, etc.

[0317] The format of the system time synchronization request message can be found in Tables 1 and 2, and will not be repeated here.

[0318] In one possible implementation, if the vehicle determines that the T-BOX has been reset and the vehicle is unable to establish a connection with the backend server, it determines that it cannot synchronize its clock with the backend server.

[0319] In another possible implementation, if a vehicle loses power and loses its current clock, it is determined that it cannot synchronize its clock with the backend server if it is unable to establish a connection with the backend server.

[0320] The above is merely an illustrative example. In actual applications, the reasons why a vehicle cannot synchronize its clock with the vehicle's backend server, i.e., obtain the correct clock, should all fall within the scope of protection of this disclosure.

[0321] In step 1303, the terminal device acquires the first clock.

[0322] In step 1304, the terminal device uses the private key of the digital car key to sign the information of the clock type field, the clock information field, and the clock status field included in the system time synchronization response message, and determines the information of the signature field.

[0323] In this embodiment of the disclosure, the digital key framework of the terminal device can sign the information of the above-mentioned fields included in the system time synchronization response message using the private key of the digital car key, thereby determining the information of the signature fields included in the system time synchronization response message.

[0324] In step 1305, the terminal device sends a system time synchronization response message to the vehicle.

[0325] In this embodiment of the disclosure, the system time synchronization response message can be represented as SystemTimeSync_res. This system time synchronization response message can be used to provide feedback on the first clock requested for synchronization by the vehicle, and for the terminal device to sign the clock-related information provided in the feedback.

[0326] The format of the system time synchronization response message can be found in Tables 3 and 4, and will not be repeated here.

[0327] In step 1306, the vehicle verifies the information in the signature field included in the system time synchronization response message based on the public key of the digital car key, and obtains the verification result.

[0328] In this embodiment of the disclosure, the vehicle can use the public key of the digital car key to verify the information in the signature field included in the system time synchronization response message.

[0329] In step 1307, in response to the verification result indicating that the information in the signature field is valid, the vehicle synchronizes the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message.

[0330] In this embodiment of the disclosure, the vehicle can verify the information in the signature field based on the public key. If the signature has not been tampered with, i.e. the information in the signature field is valid, the vehicle can use the first clock included in the system time synchronization response message fed back by the terminal device as a trusted clock source and synchronize the clock of the T-BOX on the vehicle based on the first clock.

[0331] In step 1308, the vehicle obtains a second clock from the backend server.

[0332] In this embodiment of the disclosure, after the vehicle re-establishes its connection with the backend server, it can obtain a second clock from the backend server.

[0333] In step 1309, the vehicle synchronizes the clock of the telematics processor on the vehicle based on the second clock.

[0334] In this embodiment of the disclosure, the vehicle can use a second clock as a new trusted clock source for clock synchronization.

[0335] The above embodiments ensure the accuracy of vehicle clock synchronization. Subsequently, the validity period of the digital car key can be verified based on the clock synchronized from the terminal device, thereby improving the security of digital car key use.

[0336] Corresponding to the aforementioned embodiments of the application function implementation method, this disclosure also provides embodiments of the application function implementation apparatus.

[0337] Reference Figure 14 , Figure 14 This is a block diagram illustrating a clock synchronization device according to an exemplary embodiment, the device being applied to a vehicle, the device comprising:

[0338] The first sending module 1401 is used to send a system time synchronization request message to the terminal device in response to the inability to synchronize the clock with the back-end server of the vehicle; wherein the system time synchronization request message is used to request clock synchronization with the terminal device;

[0339] The first receiving module 1402 is used to receive the system time synchronization response message returned by the terminal device;

[0340] The first synchronization module 1403 is used to synchronize the clock of the remote information processor on the vehicle based on the first clock included in the system time synchronization response message.

[0341] Optionally, the device further includes:

[0342] The first determining module is configured to determine that clock synchronization with the vehicle's backend server is impossible in response to a reset operation performed by the remote information processor and the vehicle being unable to establish a connection with the backend server.

[0343] For specific implementation details, please refer to the above. Figure 1 The implementation of the illustrated embodiment will not be described in detail here.

[0344] In some optional cases, the system time synchronization request message includes at least one of the following fields:

[0345] The first name field is used to indicate the message name;

[0346] The first identifier field is used to indicate the message identifier;

[0347] The first parameter field is used to indicate the parameters requested by the system time synchronization request message.

[0348] Optionally, the first parameter field includes at least a clock type field.

[0349] Optionally, the system time synchronization response message includes at least one of the following fields:

[0350] A second name field used to indicate the message name;

[0351] A second identifier field used to indicate the message identifier;

[0352] The second parameter field is used to indicate the parameters included in the system time synchronization response message.

[0353] Optionally, the second parameter field includes at least one of the following:

[0354] Clock type field;

[0355] A clock information field used to indicate the first clock;

[0356] A status field used to indicate whether the clock type requested by the system time synchronization request message has been successfully returned;

[0357] A signature field used to sign the clock type field, the clock information field, and the status field.

[0358] Optionally, the clock type field indicates any of the following in ascending order of type priority:

[0359] Accepts any clock from the terminal device;

[0360] Receive the network clock from the terminal device;

[0361] The terminal device returns a local clock and signs the local clock;

[0362] The terminal device returns the network clock and signs the network clock.

[0363] The specific implementation methods are described in Tables 1, 2, 3 and 4, and will not be repeated here.

[0364] In some alternative embodiments, the apparatus further includes:

[0365] The verification module is used to verify the information in the signature field included in the system time synchronization response message based on the public key of the digital car key, and obtain the verification result;

[0366] The control module is configured to, in response to the verification result indicating that the information in the signature field is valid, control the first synchronization module to synchronize the clock of the remote information processor on the vehicle based on the first clock included in the system time synchronization response message.

[0367] For specific implementation details, please refer to the above. Figure 2 The implementation of the illustrated embodiment will not be described in detail here.

[0368] In some alternative embodiments, the system time synchronization request message is used to request a clock of a first type priority.

[0369] The device further includes:

[0370] The third sending module is configured to send a new system time synchronization request message to the terminal device in response to determining that the system time synchronization response information indicates that the terminal device cannot provide a clock of the first type priority; wherein the new system time synchronization request message is used to request a clock of the second type priority, and the second type priority is lower than the first type priority;

[0371] The third receiving module is used to receive a new system time synchronization response message returned by the terminal device;

[0372] The second synchronization module is used to synchronize the clock of the telematics processor on the vehicle based on the clock of the second type priority included in the new system time synchronization response message.

[0373] For specific implementation details, please refer to the above. Figure 3 The implementation of the illustrated embodiment will not be described in detail here.

[0374] In some alternative embodiments, the system time synchronization request message is used to request a clock of a first type priority.

[0375] The device further includes:

[0376] The fourth sending module is configured to send a new system time synchronization request message to the terminal device in response to the determination that the number of times the system time synchronization request message has been sent has reached a specified number, and that the system time synchronization response messages returned by the terminal device all indicate that the terminal device cannot provide a clock of the first type priority; wherein, the new system time synchronization request message is used to request a clock of the second type priority, and the second type priority is lower than the first type priority;

[0377] The fourth receiving module is used to receive a new system time synchronization response message returned by the terminal device;

[0378] The third synchronization module is used to synchronize the clock of the telematics processor on the vehicle based on the clock of the second type priority included in the new system time synchronization response message.

[0379] For specific implementation details, please refer to the above. Figure 4 The implementation of the illustrated embodiment will not be described in detail here.

[0380] In some alternative embodiments, the apparatus further includes:

[0381] The first acquisition module is used to acquire the second clock from the backend server;

[0382] The fourth synchronization module is used to synchronize the clock of the telematics processor on the vehicle based on the second clock.

[0383] For specific implementation details, please refer to the above. Figure 5 The implementation of the illustrated embodiment will not be described in detail here.

[0384] In some alternative embodiments, the apparatus further includes:

[0385] The first connection module is used to establish a connection with the terminal device.

[0386] For specific implementation details, please refer to the above. Figure 6 The implementation of the illustrated embodiment will not be described in detail here.

[0387] Reference Figure 15 , Figure 15 This is a block diagram illustrating a clock synchronization device according to an exemplary embodiment. The device is applied to a terminal device and includes:

[0388] The second receiving module 1501 is used to receive a system time synchronization request message sent by the vehicle when it is unable to synchronize its clock with the vehicle's backend server; wherein the system time synchronization request message is used to request clock synchronization with the terminal device.

[0389] The second sending module 1502 is used to send a system time synchronization response message to the vehicle, so that the vehicle synchronizes the clock of the remote information processor on the vehicle based on the first clock included in the system time synchronization response message.

[0390] For specific implementation details, please refer to the above. Figure 7 The implementation of the illustrated embodiment will not be described in detail here.

[0391] Optionally, the system time synchronization request message includes at least one of the following fields:

[0392] The first name field is used to indicate the message name;

[0393] The first identifier field is used to indicate the message identifier;

[0394] The first parameter field is used to indicate the parameters requested by the system time synchronization request message.

[0395] Optionally, the first parameter field includes at least a clock type field.

[0396] Optionally, the system time synchronization response message includes at least one of the following fields:

[0397] A second name field used to indicate the message name;

[0398] A second identifier field used to indicate the message identifier;

[0399] The second parameter field is used to indicate the parameters included in the system time synchronization response message.

[0400] Optionally, the second parameter field includes at least one of the following:

[0401] Clock type field;

[0402] A clock information field used to indicate the first clock;

[0403] A status field used to indicate whether the clock type requested by the system time synchronization request message has been successfully returned;

[0404] A signature field used to sign the clock type field, the clock information field, and the status field.

[0405] Optionally, the clock type field indicates any of the following in ascending order of type priority:

[0406] Accepts any clock from the terminal device;

[0407] Receive the network clock from the terminal device;

[0408] The terminal device returns a local clock and signs the local clock;

[0409] The terminal device returns the network clock and signs the network clock.

[0410] The specific implementation methods are described in Tables 1, 2, 3 and 4, and will not be repeated here.

[0411] In some alternative embodiments, the apparatus further includes:

[0412] The second acquisition module is used to acquire the first clock requested by the system time synchronization request message.

[0413] Optionally, when the system time synchronization request message is used to request the terminal device to return the network clock, the second acquisition module includes any one of the following:

[0414] The first acquisition submodule is used to acquire the first clock from the background server;

[0415] The second acquisition submodule is used to acquire the local clock of the terminal device when the local clock of the terminal device is acquired from the network side.

[0416] For specific implementation details, please refer to the above. Figure 8 The implementation of the illustrated embodiment will not be described in detail here.

[0417] In some alternative embodiments, the apparatus further includes:

[0418] The signature module is used to sign the information of the clock type field, the clock information field, and the clock status field included in the system time synchronization response message using the private key of the digital car key, and to determine the information of the signature field.

[0419] For specific implementation details, please refer to the above. Figure 9 The implementation of the illustrated embodiment will not be described in detail here.

[0420] In some alternative embodiments, when the system time synchronization request message is used to request a clock of a first type priority, the second sending module includes:

[0421] The sending submodule is configured to, in response to the inability to obtain a clock of the first type priority, send a system time synchronization response message to the vehicle indicating that the terminal device is unable to provide a clock of the first type priority.

[0422] For specific implementation details, please refer to the above. Figure 10 The implementation of the illustrated embodiment will not be described in detail here.

[0423] In some alternative embodiments, the apparatus further includes:

[0424] The fifth receiving module is used to receive a new system time synchronization request message sent by the vehicle; wherein the new system time synchronization request message is used to request a clock of a second type priority, and the second type priority is lower than the first type priority;

[0425] The fifth sending module is used to obtain the clock of the second type priority and then send a new system time synchronization response message including the clock of the second type priority to the vehicle.

[0426] For specific implementation details, please refer to the above. Figure 11 The implementation of the illustrated embodiment will not be described in detail here.

[0427] In some alternative embodiments, the apparatus further includes:

[0428] The second connection module is used to establish a connection with the vehicle.

[0429] For specific implementation details, please refer to the above. Figure 12 The implementation of the illustrated embodiment will not be described in detail here.

[0430] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this disclosure according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0431] Accordingly, this disclosure also provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, is used to implement the steps of the clock synchronization method described in any of the above-described vehicle-side methods.

[0432] Accordingly, this disclosure also provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, is used to implement the steps of the clock synchronization method described above on the terminal device side.

[0433] Accordingly, this disclosure also provides a clock synchronization device, comprising:

[0434] processor;

[0435] Memory used to store processor-executable instructions;

[0436] The processor is configured to execute the executable instructions to implement the steps of the clock synchronization method described in any of the above-described vehicle-side methods.

[0437] like Figure 16 As shown, Figure 16 This is a schematic diagram illustrating the structure of a clock synchronization device 1600 according to an exemplary embodiment. The device 1600 can be provided as a vehicle. (Refer to...) Figure 16 The device 1600 includes a processing component 1622, a wireless transmitting / receiving component 1624, an antenna component 1626, and a signal processing section specific to the wireless interface. The processing component 1622 may further include one or more processors.

[0438] One of the processors in the processing component 1622 can be configured to perform the clock synchronization method described above on the vehicle side.

[0439] Accordingly, this disclosure also provides a clock synchronization device, comprising:

[0440] processor;

[0441] Memory used to store processor-executable instructions;

[0442] The processor is configured to execute the executable instructions to implement the steps of the clock synchronization method described in any one of the above-described terminal device side.

[0443] Figure 17 This is a block diagram illustrating a clock synchronization device according to an exemplary embodiment. For example, device 1700 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, or other terminal device.

[0444] Reference Figure 17The device 1700 may include one or more of the following components: a processing component 1702, a memory 1704, a power supply component 1706, a multimedia component 1708, an audio component 1710, an input / output (I / O) interface 1712, a sensor component 1716, and a communication component 1718.

[0445] Processing component 1702 typically controls the overall operation of device 1700, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 1702 may include one or more processors 1720 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 1702 may include one or more modules to facilitate interaction between processing component 1702 and other components. For example, processing component 1702 may include a multimedia module to facilitate interaction between multimedia component 1708 and processing component 1702.

[0446] One of the processors 1720 in the processing component 1702 can be configured to perform the clock synchronization method described above for any of the vehicle terminal devices.

[0447] Memory 1704 is configured to store various types of data to support the operation of device 1700. Examples of this data include instructions for any application or method operating on device 1700, contact data, phonebook data, messages, pictures, videos, etc. Memory 1704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0448] Power supply assembly 1706 provides power to various components of device 1700. Power supply assembly 1706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 1700.

[0449] Multimedia component 1708 includes a screen that provides an output interface between device 1700 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 1708 includes a front-facing camera and / or a rear-facing camera. When device 1700 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0450] Audio component 1710 is configured to output and / or input audio signals. For example, audio component 1710 includes a microphone (MIC) configured to receive external audio signals when device 1700 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1704 or transmitted via communication component 1718. In some embodiments, audio component 1710 also includes a speaker for outputting audio signals.

[0451] I / O interface 1712 provides an interface between processing component 1702 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0452] Sensor assembly 1716 includes one or more sensors for providing state assessment of various aspects of device 1700. For example, sensor assembly 1716 may detect the on / off state of device 1700, the relative positioning of components such as the display and keypad of device 1700, changes in the position of device 1700 or a component of device 1700, the presence or absence of user contact with device 1700, the orientation or acceleration / deceleration of device 1700, and temperature changes of device 1700. Sensor assembly 1716 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1716 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1716 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0453] Communication component 1718 is configured to facilitate wired or wireless communication between device 1700 and other devices. Device 1700 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 5G, 6G, or combinations thereof. In one exemplary embodiment, communication component 1718 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 1718 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0454] In an exemplary embodiment, the apparatus 1700 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0455] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1704 including instructions, which can be executed by a processor 1720 of the device 1700 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0456] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0457] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0458] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A clock synchronization method, characterized in that, The method is applied to a vehicle, and the method includes: In response to the inability to synchronize the clock with the vehicle's backend server, a system time synchronization request message is sent to the terminal device; wherein the system time synchronization request message is used to request clock synchronization with the terminal device; wherein, if the system time synchronization request message includes a first parameter field indicating the parameters requested by the system time synchronization request message, the first parameter field includes at least a clock type field; wherein, the clock type field indicates any of the following in order of type priority from low to high: accepting any clock of the terminal device; accepting the network clock of the terminal device; the terminal device returning a local clock and signing the local clock; the terminal device returning a network clock and signing the network clock; Receive the system time synchronization response message returned by the terminal device; The clock of the telematics processor on the vehicle is synchronized based on the first clock included in the system time synchronization response message.

2. The method according to claim 1, characterized in that, The method further includes: In response to the remote information processor performing a reset operation and the vehicle being unable to establish a connection with the backend server, it is determined that clock synchronization with the vehicle's backend server is not possible.

3. The method according to claim 1, characterized in that, The system time synchronization request message includes at least one of the following fields: The first name field is used to indicate the message name; The first identifier field is used to indicate the message identifier; The first parameter field.

4. The method according to claim 1, characterized in that, The system time synchronization response message includes at least one of the following fields: A second name field used to indicate the message name; A second identifier field used to indicate the message identifier; The second parameter field is used to indicate the parameters included in the system time synchronization response message.

5. The method according to claim 4, characterized in that, The second parameter field includes at least one of the following: Clock type field; A clock information field used to indicate the first clock; A status field used to indicate whether the clock type requested by the system time synchronization request message has been successfully returned; A signature field used to sign the clock type field, the clock information field, and the status field.

6. The method according to claim 1, characterized in that, The method further includes: The information in the signature field included in the system time synchronization response message is verified based on the public key of the digital car key to obtain the verification result; In response to the verification result indicating that the information in the signature field is valid, the step of synchronizing the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message is performed.

7. The method according to claim 1, characterized in that, The system time synchronization request message is used to request a clock of the first priority type; The method further includes: In response to determining that the system time synchronization response information indicates that the terminal device cannot provide a clock of the first type priority, a new system time synchronization request message is sent to the terminal device; wherein, the new system time synchronization request message is used to request a clock of the second type priority, and the second type priority is lower than the first type priority; Receive the new system time synchronization response message returned by the terminal device; The clock of the telematics processor on the vehicle is synchronized based on the second type priority clock included in the new system time synchronization response message.

8. The method according to claim 1, characterized in that, The system time synchronization request message is used to request a clock of the first priority type; The method further includes: In response to the determination that the number of times the system time synchronization request message has been sent has reached a specified number, and the system time synchronization response messages returned by the terminal device all indicate that the terminal device cannot provide a clock of the first type priority, a new system time synchronization request message is sent to the terminal device; wherein, the new system time synchronization request message is used to request a clock of the second type priority, and the second type priority is lower than the first type priority; Receive the new system time synchronization response message returned by the terminal device; The clock of the telematics processor on the vehicle is synchronized based on the second type priority clock included in the new system time synchronization response message.

9. The method according to claim 1, characterized in that, After synchronizing the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message, the method further includes: Obtain the second clock from the backend server; The clock of the telematics processor on the vehicle is synchronized based on the second clock.

10. The method according to claim 1, characterized in that, Before sending a system time synchronization request message to the terminal device, the method further includes: Establish a connection with the terminal device.

11. A clock synchronization method, characterized in that, The method is applied to a terminal device, and the method includes: The system receives a system time synchronization request message sent by a vehicle when it is unable to synchronize its clock with the vehicle's backend server. The system time synchronization request message requests clock synchronization with the terminal device. When the system time synchronization request message includes a first parameter field indicating the parameters requested, the first parameter field includes at least a clock type field. The clock type field indicates any of the following in ascending order of priority: accepting any clock from the terminal device; accepting the network clock from the terminal device; the terminal device returning a local clock and signing the local clock; or the terminal device returning a network clock and signing the network clock. A system time synchronization response message is sent to the vehicle, and the vehicle synchronizes the clock of the telematics processor on the vehicle based on the first clock included in the system time synchronization response message.

12. The method according to claim 11, characterized in that, The system time synchronization request message includes at least one of the following fields: The first name field is used to indicate the message name; The first identifier field is used to indicate the message identifier; The first parameter field.

13. The method according to claim 11, characterized in that, The system time synchronization response message includes at least one of the following fields: A second name field used to indicate the message name; A second identifier field used to indicate the message identifier; The second parameter field is used to indicate the parameters included in the system time synchronization response message.

14. The method according to claim 13, characterized in that, The second parameter field includes at least one of the following: Clock type field; A clock information field used to indicate the first clock; A status field used to indicate whether the clock type requested by the system time synchronization request message has been successfully returned; A signature field used to sign the clock type field, the clock information field, and the status field.

15. The method according to claim 11, characterized in that, After receiving the system time synchronization request message, the method further includes: Obtain the first clock requested by the system time synchronization request message.

16. The method according to claim 15, characterized in that, When the system time synchronization request message is used to request the terminal device to return the network clock, obtaining the first clock requested by the system time synchronization request message includes any one of the following: Obtain the first clock from the backend server; If the local clock of the terminal device is obtained from the network side, the local clock of the terminal device is obtained.

17. The method according to claim 14, characterized in that, Before sending a system time synchronization response message to the vehicle, the method further includes: Using the private key of the digital car key, the information of the clock type field, the clock information field, and the status field included in the system time synchronization response message is signed to determine the information of the signature field.

18. The method according to claim 11, characterized in that, In the case where the system time synchronization request message is used to request a clock of a first priority type, sending a system time synchronization response message to the vehicle includes: In response to the inability to obtain a clock of the first type priority, a system time synchronization response message is sent to the vehicle indicating that the terminal device is unable to provide a clock of the first type priority.

19. The method according to claim 18, characterized in that, The method further includes: Receive a new system time synchronization request message sent by the vehicle; wherein the new system time synchronization request message is used to request a clock of a second type priority, and the second type priority is lower than the first type priority; After obtaining the clock of the second type priority, a new system time synchronization response message including the clock of the second type priority is sent to the vehicle.

20. The method according to claim 11, characterized in that, Before receiving the system time synchronization request message, the method further includes: Establish a connection with the vehicle.

21. A clock synchronization device, characterized in that, The device is applied to a vehicle, and the device includes: A first sending module is configured to send a system time synchronization request message to a terminal device in response to the inability to synchronize the clock with the vehicle's backend server; wherein the system time synchronization request message requests clock synchronization with the terminal device; wherein, when the system time synchronization request message includes a first parameter field indicating the parameters requested by the system time synchronization request message, the first parameter field includes at least a clock type field; wherein the clock type field indicates any of the following in order of type priority from low to high: accepting any clock of the terminal device; accepting the network clock of the terminal device; the terminal device returning a local clock and signing the local clock; the terminal device returning a network clock and signing the network clock; The first receiving module is used to receive the system time synchronization response message returned by the terminal device; The first synchronization module is used to synchronize the clock of the remote information processor on the vehicle based on the first clock included in the system time synchronization response message.

22. A clock synchronization device, characterized in that, The device is used in a terminal device, and the device includes: The second receiving module is configured to receive a system time synchronization request message sent by the vehicle when it is unable to synchronize its clock with the vehicle's backend server; wherein the system time synchronization request message requests clock synchronization with the terminal device; wherein, when the system time synchronization request message includes a first parameter field indicating the parameters requested by the system time synchronization request message, the first parameter field includes at least a clock type field; wherein the clock type field indicates any of the following in order of type priority from low to high: accepting any clock of the terminal device; accepting the network clock of the terminal device; the terminal device returning a local clock and signing the local clock; the terminal device returning a network clock and signing the network clock; The second sending module is used to send a system time synchronization response message to the vehicle, so that the vehicle synchronizes the clock of the remote information processor on the vehicle based on the first clock included in the system time synchronization response message.

23. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the clock synchronization method according to any one of claims 1-10.

24. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the clock synchronization method according to any one of claims 11-20.

25. A clock synchronization device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the steps of the clock synchronization method according to any one of claims 1-10.

26. A clock synchronization device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the executable instructions to implement the steps of the clock synchronization method according to any one of claims 11-20.

Images