Data storage and certification method, device, electronic device and computer-readable storage medium

Abstract

A data deposit and verification method, device, electronic device, and computer-readable storage medium. The method includes: detecting a mode switching behavior implemented by a vehicle operator, where the mode switching behavior is used to trigger switching the driving mode of the vehicle between a manual driving mode and an autonomous driving mode; obtaining first data corresponding to the mode switching behavior, where the first data includes a vehicle identifier of the vehicle, as well as switching trigger information and time information corresponding to the mode switching behavior; and depositing the first data into a blockchain network. According to the present disclosure, reliable deposit and verification of the first data can be achieved, and data malicious tampering can be avoided. Moreover, through the switching trigger information and time information deposited into the blockchain network, the true driving mode of the vehicle at a historical moment can be determined, and then the responsible party corresponding to the vehicle can be determined, which helps to achieve reliable driving responsibility division and effectively avoid disputes among relevant parties.

Description

Technical Field

[0001] The present disclosure relates to the field of autonomous driving technology, and more particularly, to a method, apparatus, electronic device, and computer-readable storage medium for data deposit and certification. Background Art

[0002] With the increasing maturity of the vehicle's autonomous driving function, more and more vehicles with autonomous driving functions are on the road. Usually, such vehicles can also be controlled by a driver or other operators to achieve manual driving.

[0003] The relevant data generated by the above-mentioned vehicle during driving can be used to judge the change of the vehicle's driving mode. For example, a traffic accident may occur during the driving of the above-mentioned vehicle. After the accident occurs, the above-mentioned relevant data stored locally in the vehicle or in the cloud storage space provided by the vehicle manufacturer can be obtained to determine whether the vehicle was in the autonomous driving mode or the manual driving mode at the moment of the accident based on this data, so as to facilitate the division of liability for the traffic accident.

[0004] However, there is a risk that the above-mentioned status data may be maliciously tampered with by the vehicle owner or the vehicle manufacturer. Therefore, the status data obtained by the above-mentioned method is often difficult to convince relevant parties such as users, autonomous driving providers, and vehicle providers, and even leads to disputes among relevant parties. Summary of the Invention

[0005] In view of this, embodiments of the present disclosure propose a method, apparatus, electronic device, and computer-readable storage medium for data deposit and certification to solve the deficiencies in the related art.

[0006] According to a first aspect of an embodiment of the present disclosure, a method for data deposit and certification is proposed. The method includes:

[0007] Detecting a mode switching behavior performed by an operator of the vehicle, where the mode switching behavior is used to trigger switching the driving mode of the vehicle between a manual driving mode and an autonomous driving mode;

[0008] Obtaining first data corresponding to the mode switching behavior, where the first data includes a vehicle identifier of the vehicle, as well as switching trigger information and time information corresponding to the mode switching behavior;

[0009] Depositing and certifying the first data to a blockchain network.

[0010] Optionally, before obtaining the first data corresponding to the mode switching behavior, it further includes:

[0011] Generating a mode switching request including the identity information of the operator;

[0012] Send the mode switching request to the decision-making server corresponding to the autonomous driving mode, and receive a mode switching response returned by the decision-making server, where the mode switching response is used to indicate whether the operator has the permission to use the autonomous driving mode.

[0013] Optionally, it further includes:

[0014] In the case where the mode switching response indicates that the operator has the permission to use the autonomous driving mode, switch the driving mode of the vehicle between the manual driving mode and the autonomous driving mode; and,

[0015] In the case where the mode switching response indicates that the operator does not have the permission to use the autonomous driving mode, refuse to switch the driving mode of the vehicle between the manual driving mode and the autonomous driving mode.

[0016] Optionally, the switching trigger information includes: the mode switching request and the mode switching response

[0017] Optionally, the mode switching behavior is a mode switching action, and the method further includes:

[0018] In response to the mode switching action, switch the driving mode of the vehicle between the manual driving mode and the autonomous driving mode, where the switching trigger information includes video information recording the mode switching behavior.

[0019] Optionally, it further includes:

[0020] Obtain second data corresponding to the mode switching behavior, where the second data includes at least one of the following: the vehicle identification, vehicle position, vehicle state parameters, vehicle environment parameters, and behavior parameters of the mode switching behavior;

[0021] Send the second data to the decision-making server corresponding to the autonomous driving mode.

[0022] Optionally, the decision-making server includes:

[0023] A cloud server or an edge server deployed in the vehicle.

[0024] Optionally, the first data further includes the identity information of the operator,

[0025] It further includes: encrypting the identity information;

[0026] The step of depositing the first data into the blockchain network includes: depositing the encrypted identity information into the blockchain network.

[0027] Optionally, storing the first data on the blockchain network includes:

[0028] Determining the data to be uploaded to the chain corresponding to the first data, and initiating a blockchain network transaction for the data to be uploaded to the chain in the blockchain network;

[0029] When the blockchain network transaction passes consensus, storing the data to be uploaded to the chain in the blockchain network.

[0030] Optionally, determining the data to be uploaded to the chain corresponding to the first data includes:

[0031] Determining the first data as the data to be uploaded to the chain; or,

[0032] Determining the data digest of the first data as the data to be uploaded to the chain, where the first data is stored in a preset off-chain storage space.

[0033] Optionally, the vehicle is connected to the blockchain network server corresponding to the provider of the vehicle through a locally running blockchain network client to access the blockchain network.

[0034] Optionally, the blockchain network is a consortium chain, and the consortium chain members include the vehicle, and also include a first server corresponding to the provider of the vehicle, a second server corresponding to the provider of the autonomous driving function, and / or a regulator server corresponding to a predefined regulator.

[0035] Optionally, the autonomous driving mode includes:

[0036] An assisted driving mode that requires the operator to participate; and,

[0037] A fully autonomous driving mode that does not require the operator to participate.

[0038] According to a second aspect of the embodiments of the present disclosure, a data storage and certification device is provided, including:

[0039] Determining target data stored on the blockchain network according to the target vehicle identifier and target time information of the target vehicle, where the target data corresponds to the historical mode switching behavior of the operator for the target vehicle, and the historical mode switching behavior is used to trigger the switching of the driving mode of the target vehicle between the manual driving mode and the autonomous driving mode;

[0040] Obtaining the target switching trigger information in the target data, and determining the historical driving mode corresponding to the target time information according to the target switching trigger information.

[0041] Optionally, determining the target data stored in the blockchain network according to the target vehicle identifier and target time information of the target vehicle includes:

[0042] Determine vehicle data containing the target vehicle identifier from the data stored in the blockchain network, and use the vehicle data with the included time information matching the target time information as the target data.

[0043] Optionally, the target time information is a target historical moment, and the time information recorded in the target data indicates that the historical mode switching behavior occurred before the target historical moment; determining the historical driving mode corresponding to the target time information according to the target switching trigger information includes:

[0044] Determine the mode switching method corresponding to the historical mode switching behavior according to the target switching trigger information, where the mode switching method is switching from the manual driving mode to the autonomous driving mode or switching from the autonomous driving mode to the manual driving mode;

[0045] Use the switched mode corresponding to the mode switching method as the historical driving mode corresponding to the target time information.

[0046] According to the third aspect of the embodiments of the present disclosure, a data storage and certification device is proposed. The device includes one or more processors, and the processors are configured to:

[0047] Detect a mode switching behavior performed by a vehicle operator, where the mode switching behavior is used to trigger switching the driving mode of the vehicle between the manual driving mode and the autonomous driving mode;

[0048] Obtain first data corresponding to the mode switching behavior, where the first data includes the vehicle identifier of the vehicle and the switching trigger information and time information corresponding to the mode switching behavior;

[0049] Store the first data in the blockchain network.

[0050] According to the fourth aspect of the embodiments of the present disclosure, a device for determining a driving mode is proposed. The device includes one or more processors, and the processors are configured to:

[0051] Determine target data stored in the blockchain network according to the target vehicle identifier and target time information of the target vehicle, where the target data corresponds to a historical mode switching behavior performed by an operator on the target vehicle, and the historical mode switching behavior is used to trigger switching the driving mode of the target vehicle between the manual driving mode and the autonomous driving mode;

[0052] Obtain the target switching trigger information in the target data, and determine the historical driving mode corresponding to the target time information according to the target switching trigger information.

[0053] According to a fifth aspect of the embodiments of the present disclosure, an electronic device is provided, including: a processor; a memory for storing instructions executable by the processor; wherein, the processor is configured to implement the above data deposit method.

[0054] According to a sixth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the steps in the above data deposit method are implemented.

[0055] According to the embodiments of the present disclosure, the operator of the vehicle can perform a mode switching behavior to trigger the switching of the driving mode of the vehicle between the manual driving mode and the automatic driving mode; correspondingly, when the vehicle detects the above behavior, it can obtain the first data corresponding to the behavior, including the vehicle identifier, the switching trigger information and the time information corresponding to the behavior, and deposit the first data into the blockchain network.

[0056] On the one hand, since the blockchain network is composed of multiple blockchain network nodes, and each blockchain network node independently records the data to be deposited, the data deposited into the blockchain network is basically impossible to be tampered with by individual blockchain network nodes, so as to effectively ensure the authenticity of the deposited data. By depositing the above first data into the blockchain network, the above characteristics of the blockchain network can be utilized to realize the reliable deposit of the first data and ensure the authenticity of the data. On the other hand, since the first data includes the vehicle identifier and the switching trigger information and time information corresponding to the mode switching behavior performed by the operator, based on the above real data deposited into the blockchain network, it is possible to accurately judge the real driving mode of the vehicle at any historical moment, and then accurately determine the corresponding responsible party, which helps to realize a reliable driving responsibility division and effectively avoid disputes among relevant parties.

[0057] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the following drawings are only some embodiments of the present disclosure. For those of ordinary skill in the art, other drawings can be obtained without creative efforts based on these drawings.

[0059] Figure 1It is a schematic structural diagram of a blockchain network shown according to an embodiment of the present disclosure.

[0060] Figure 2 It is a flowchart of a data deposit method shown according to an embodiment of the present disclosure.

[0061] Figure 3 It is a schematic structural diagram of a vehicle shown according to an embodiment of the present disclosure.

[0062] Figure 4 It is an interaction flowchart of a data deposit method shown according to an embodiment of the present disclosure.

[0063] Figure 5 It is an interaction flowchart of another data deposit method shown according to an embodiment of the present disclosure.

[0064] Figure 6 It is a flowchart of a method for determining a driving mode shown according to an embodiment of the present disclosure.

[0065] Figure 7 It is a schematic block diagram of a device for data deposit or driving mode determination shown according to an embodiment of the present disclosure. Detailed implementation manners

[0066] Next, the technical solutions in the embodiments of the present disclosure will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure.

[0067] Figure 1 It is a schematic structural diagram of a blockchain network provided by an exemplary embodiment. As Figure 1 shown, the network may include a vehicle provider 11 (such as a vehicle manufacturer, etc.), an autonomous driving provider 12, a supervisor 13, and a number of vehicles, such as vehicle 14, vehicle 15, and vehicle 16, etc. Among them, the vehicle provider 11 can be understood as the first server corresponding to the vehicle provider, the autonomous driving provider 12 can be understood as the second server corresponding to the autonomous driving function provider, and the supervisor 13 can be understood as the supervisor server corresponding to the supervisor. In addition, the vehicle provider 11 and the autonomous driving provider 12 can be the same party, such as a vehicle manufacturer that provides both vehicles and autonomous driving technologies to users.

[0068] Any vehicle can be connected to the above blockchain network as an independent blockchain node, as shown by vehicle 14. In this scenario, any vehicle is regarded as a blockchain node in the said blockchain network. Multiple vehicles can also be connected to the same node device and access the blockchain network through this node device. For example, vehicle 15 and vehicle 16 access the blockchain network through node device 17. In this scenario, the same node device to which multiple vehicles are connected is regarded as a blockchain node in the said blockchain network. The above node device can be provided by any one of vehicle provider 11, autonomous driving provider 12 or supervisor 13. The embodiments of the present disclosure do not limit this.

[0069] Of course, for the above blockchain network, the number of vehicle providers, autonomous driving providers, supervisors, vehicles and / or node devices included therein can all be one or more. The embodiments of the present disclosure do not limit the brand, model, parameters, etc. of any vehicle, as long as it has autonomous driving function and manual driving function.

[0070] Any vehicle (such as vehicle 14, vehicle 15 or vehicle 16 above) described in the embodiments of the present disclosure has both autonomous driving function and manual driving function at the same time: when the vehicle is in the autonomous driving mode, the vehicle is controlled by the autonomous driving logic corresponding to the autonomous driving function; when the vehicle is in the manual driving mode, the vehicle is controlled by the above-mentioned operator. Moreover, the autonomous driving function described in the embodiments of the present disclosure includes assisted driving function and fully autonomous driving function. Among them, in the assisted driving mode corresponding to the assisted driving function, the vehicle requires the participation of the operator, that is, the vehicle needs the operator to cooperate with the assisted driving logic to achieve normal driving in this mode. For example, in the assisted driving mode, the vehicle can provide the user with assisted driving functions such as cruise control, lane reminder, and automatic emergency braking. In the fully autonomous driving mode corresponding to the fully autonomous driving function, the vehicle can achieve complete driving functions without the participation of the operator, that is, achieve its own full autonomous driving.

[0071] In fact, the related art defines multiple levels for the automation degree of vehicles with autonomous driving functions. For example, the automation degree of L0-L5 levels gradually increases. The concepts such as the manual driving mode, assisted driving mode, and fully autonomous driving mode described in the embodiments of the present disclosure can satisfy a certain corresponding relationship with the L0-L5 autonomous driving levels defined in the related art. For example, the above-mentioned manual driving mode can correspond to the L0 level, the above-mentioned assisted driving mode can correspond to the L1-L4 levels, and the fully autonomous driving mode can correspond to the L5 level. The embodiments of the present disclosure do not limit the specific corresponding relationship between the above-mentioned modes and the autonomous driving levels in the related art.

[0072] In addition, the operator of the vehicle described in the present disclosure may be the driver of the vehicle, such as the person inside the vehicle who drives the vehicle through the steering wheel and function buttons. Alternatively, when the degree of automation of the vehicle is relatively high, the vehicle may not be provided with a steering wheel, and the person inside the vehicle (such as a passenger) can drive the vehicle by means of voice, actions, etc. In this case, such a person inside the vehicle can be regarded as the operator of the vehicle. Or, for a vehicle with a remote control (such as remote control) function, a person outside the vehicle who controls the vehicle to travel by remote control can also be regarded as the operator of the vehicle. The specific form of the operator is not limited in the embodiments of the present disclosure.

[0073] For the above-mentioned vehicle, the operator can trigger the vehicle to switch its driving mode between the autonomous driving mode and the manual driving mode by performing a mode switching action. Specifically, the manual driving mode can be switched to the autonomous driving mode (i.e., starting the autonomous driving function), or the autonomous driving mode can be switched to the manual driving mode (i.e., turning off the autonomous driving function). The data storage and proof scheme described in the present disclosure is used to store the first data corresponding to the mode switching action in the blockchain. The data storage and proof scheme of this specification will be described in detail below with reference to the accompanying drawings.

[0074] Figure 2 is a flowchart of a data storage and proof method shown in an exemplary embodiment of the present disclosure. As Figure 2 shown, the method may include the following steps:

[0075] In step S201, a mode switching action performed by the operator of the vehicle is detected, and the mode switching action is used to trigger the switching of the driving mode of the vehicle between the manual driving mode and the autonomous driving mode.

[0076] In the embodiments described in the present disclosure, the mode switching action performed by the operator is used to trigger the switching of the driving mode of the vehicle between the manual driving mode and the autonomous driving mode. The above-mentioned mode switching action may include an autonomous driving start action and an autonomous driving stop action. Among them, the autonomous driving start action is used to trigger the switching of the driving mode of the vehicle from the manual driving mode to the autonomous driving mode, and the autonomous driving stop action is used to trigger the switching of the driving mode of the vehicle from the autonomous driving mode to the manual driving mode.

[0077] The vehicle described in the embodiments of the present disclosure can be understood as the entire "vehicle" in the conventional sense, or can be understood as the control system or in-vehicle controller of the vehicle. The specific meaning can be determined according to the context of the embodiments of the present disclosure and will not be elaborated herein one by one.

[0078] When the operator is a person inside the vehicle, the vehicle can detect the mode switching behavior implemented by the operator through the sensors equipped on itself. For example, the operator can move the cruise control lever to a preset position, and the position sensor corresponding to the control lever can send the detected position information after the movement to the vehicle, and the latter can determine that the user has implemented the above mode switching behavior based on this signal. Further, it can also determine whether this behavior is an autonomous driving activation behavior or an autonomous driving deactivation behavior according to the specific value of this signal. For another example, when the vehicle is in the autonomous driving mode, the operator can implement autonomous driving deactivation behaviors such as turning the steering wheel, stepping on the accelerator pedal (or throttle), and stepping on the brake pedal (or brake), and the corresponding sensors can send the detected position change information of the steering wheel, accelerator pedal, and brake pedal to the vehicle, and the latter can determine that the operator has implemented the autonomous driving deactivation behavior based on this information.

[0079] Alternatively, when the operator is a person outside the vehicle, the vehicle can receive the mode switching instruction sent by the operator (through the control device used by himself), and determine the autonomous driving activation behavior or autonomous driving deactivation behavior implemented by the operator according to this instruction.

[0080] The vehicle can be pre-registered in the blockchain. In one embodiment, the blockchain can be a consortium blockchain. Correspondingly, in addition to the vehicle, the consortium blockchain members can also include the first server corresponding to the provider of the vehicle (such as a vehicle enterprise server, etc.), the second server corresponding to the provider of the autonomous driving function of the vehicle, and / or the regulatory server corresponding to the predefined regulatory party (such as a traffic management department server, etc.). An optional structure of this consortium blockchain can be seen in Figure 1 the said embodiment, which will not be elaborated here.

[0081] Among them, a blockchain client can run locally on the vehicle. Thus, the vehicle can directly access the blockchain network through the blockchain client running locally, or connect to the blockchain network server corresponding to the provider of the vehicle through this client to access the blockchain. As Figure 3 shown, a blockchain client runs in the vehicle, and this client is connected to the blockchain network server outside the vehicle. Among them, the blockchain network server can be used as a blockchain node in the blockchain, and thus the vehicle is connected to this blockchain node through the blockchain network server running locally to access this blockchain.

[0082] As Figure 3As shown, a data processing unit for obtaining first data also operates in the vehicle. This unit can send the first data it obtains to the blockchain client, so that the latter can deposit the first data into the blockchain. Additionally, a decision-making client may also operate in the vehicle, and this client is connected to the decision-making server corresponding to the vehicle. Among them, the decision-making server can be an edge server installed in the vehicle (hardware environment) to bring the decision-making process forward, facilitating subsequent processing of mode switching requests locally in the vehicle, reducing communication time consumption, and improving the response efficiency of requests. Or, the decision-making server can also be a cloud server deployed outside the vehicle (such as the server room of the vehicle provider), which is convenient for implementing more complex decision-making logics and richer functions, and also helps to reduce the hardware cost of the vehicle.

[0083] In step S202, obtain the first data corresponding to the mode switching behavior, where the first data includes the vehicle identification of the vehicle and the switching trigger information and time information corresponding to the mode switching behavior;

[0084] After detecting the above-mentioned mode switching behavior, the vehicle can obtain the switching trigger information and time information corresponding to the behavior, and determine the above information and the vehicle identification of the vehicle as the first data to be deposited.

[0085] In an embodiment, when detecting the above-mentioned mode switching behavior, the vehicle can obtain the identity information of the operator. For example, biometric information such as the voice information, fingerprint information, and iris information of the operator can be collected. Taking voice information as an example, when the mode switching behavior implemented by the operator is to issue a switching voice, the vehicle can extract the voice information from the voice issued by the operator. Or, when the mode switching behavior implemented by the operator is to toggle the cruise control lever, the vehicle can instruct the operator to issue a verification voice (such as playing a prompt voice of "Please say the wake-up word" to the operator, displaying the text prompt of "Please say the wake-up word" on the display screen, or emitting a vibration signal with a preset frequency, etc.), and collect the verification voice issued by the operator in response to the instruction, and then extract the corresponding voice information from the voice. The voice information extracted in the above process can be characteristic parameters such as pitch, frequency, and period, and the embodiments of the present disclosure do not limit this. The above fingerprint information can be the characteristic points of the fingerprint pattern of the operator, and the above iris information can be the characteristic points or characteristic angles of the iris pattern, etc., which will not be elaborated. Again, for example, the vehicle can also collect information such as the account password and preset switching wake-up word of the operator as the identity information of the operator.

[0086] Furthermore, the vehicle can generate a mode switching request containing the identity information of the operator, then send the request to the decision-making server corresponding to the autonomous driving mode, and receive a mode switching response returned by the decision-making server, where the mode switching response is used to indicate whether the operator has the permission to use the autonomous driving mode. The above decision-making server is used to determine whether the operator has the permission to use the autonomous driving mode according to the above identity information.

[0087] Correspondingly, when the autonomous driving activation response indicates that the operator has the permission to use the autonomous driving mode, the vehicle can switch the driving mode of the vehicle between the manual driving mode and the autonomous driving mode in response to the above mode switching behavior. For example, when the above mode switching behavior is an autonomous driving activation behavior, the current manual driving mode of the vehicle can be switched to the autonomous driving mode; while when the mode switching behavior is an autonomous driving deactivation behavior, the current autonomous driving mode of the vehicle can be switched to the manual driving mode. On the contrary, when the autonomous driving activation response indicates that the operator does not have the permission to use the autonomous driving mode, the vehicle can refuse to switch the above driving mode, that is, the vehicle will maintain the current driving mode unchanged. In this way, the vehicle decides whether to switch the driving mode according to the possession of the permission to use the autonomous driving mode by the decision-making server: only when the operator has the permission to use the autonomous driving mode, the vehicle will switch its own driving mode, thus avoiding the unauthorized users from randomly changing the driving mode of the vehicle, helping to ensure the legality of the driving mode switching process, and reducing the difficulty of dividing the driving responsibility.

[0088] In addition to the vehicle identifier of the vehicle, the above-mentioned first data may further include corresponding switching trigger information and time information of the mode switching behavior. Among them, according to different mode switching behaviors, the above-mentioned switching trigger information is also correspondingly different. As an exemplary embodiment, in the case where the mode switching behavior is used to trigger the driving mode to switch from the manual driving mode to the autonomous driving mode (i.e., this behavior is the aforementioned autonomous driving activation behavior), the corresponding switching trigger information may include the above-mentioned mode switching request sent to the decision server, or the above-mentioned mode switching response returned by the decision server. Of course, the first data may also include both the above-mentioned mode switching request and mode switching response. In this case, the time information in the first data may be the sending moment of the above-mentioned mode switching request and / or the receiving moment of the mode switching response. Or, as another exemplary embodiment, in the case where the mode switching behavior is used to trigger the driving mode to switch from the autonomous driving mode to the manual driving mode (i.e., this behavior is the aforementioned autonomous driving deactivation behavior), the corresponding switching trigger information may include the above-mentioned mode switching request sent to the decision server, or the above-mentioned mode switching response returned by the decision server, or further include video information recording the above-mentioned mode switching behavior. Of course, the first data may also include at least two of the above three. In this case, the time information in the first data may be the sending moment of the above-mentioned mode switching request, the receiving moment of the mode switching response, and / or the acquisition moment of the video information (such as the shooting moment of an image or video).

[0089] In addition, according to different ways in which the vehicle decides whether to respond to the mode switching behavior to perform mode switching, the above-mentioned switching trigger information is also correspondingly different. For example, continuing with the foregoing embodiment, the vehicle may send the above-mentioned mode switching request to the decision server and receive the mode switching response returned by the latter. Furthermore, the vehicle may decide whether to switch its current driving mode based on the mode switching response. In this case, the vehicle may use the above-mentioned mode switching request and its corresponding above-mentioned mode switching response as the switching trigger information. In this manner, the above-mentioned mode switching request and mode switching response are the decision-making basis for the vehicle, so the vehicle may save the above-mentioned decision-making basis for subsequent liability determination.

[0090] For another example, the above-mentioned mode switching behavior can be mode switching actions such as turning the steering wheel, stepping on the accelerator pedal, stepping on the brake pedal, etc. Further, the vehicle can respond to the mode switching action and switch the driving mode of the vehicle between the manual driving mode and the autonomous driving mode. When the above-mentioned behavior is detected, the vehicle can use a pre-assembled video recording device such as a camera to capture a video including the above-mentioned mode switching behavior. For example, when the driver steps on the brake pedal with the foot, the foot of the driver (such as facing the brake pedal) can be photographed; when the driver toggles the cruise control lever with the hand, the hand of the driver (such as facing the cruise control lever) can be photographed, etc., which will not be elaborated here. In this case, the vehicle does not need to interact with the decision-making server during the process of switching the driving mode, but can directly switch when the above-mentioned mode switching behavior is detected, thus greatly simplifying the response logic of the vehicle to the mode switching behavior. Further, the vehicle can use the video information recording the mode switching behavior as the switching trigger information. For example, the video information can include the video itself, the video shooting time, the video shooting object, etc. In this way, the above-mentioned video information is the decision-making basis of the vehicle, so the vehicle can save the above-mentioned decision-making basis for subsequent liability determination.

[0091] By using the above-mentioned mode switching request, mode switching response, video information of the mode switching behavior, etc. as the switching trigger information, and using the above-mentioned vehicle identification, time information and the above-mentioned switching trigger information as the first data for deposit and proof, it is possible to effectively trace the mode switching behavior based on the above-mentioned first data, which is convenient for accurately determining the historical driving mode of the vehicle.

[0092] In step S203, the first data is deposited and proved to the blockchain.

[0093] After obtaining the above first data, the vehicle can store the data in the blockchain. As mentioned above, the first data may include a mode switching request, which includes the identity information of the operator. Of course, in the case where the above first data does not include a mode switching request, to ensure that the operator who performs the mode switching behavior (i.e., the subject of the behavior, usually the responsible subject) can be further determined based on the historical true driving mode of the vehicle, the above identity information may also be directly included in the first data. For the above two cases, that is, when the first data includes the identity information of the operator, this identity information obviously belongs to the user privacy of the operator. To avoid the security risks that may be brought by privacy leakage, the vehicle can encrypt the above identity information, and then store the encrypted identity information in the blockchain. Specifically, the above identity information can be encrypted and then stored in the blockchain. Among them, the key used for encrypting the above identity information can be maintained by the vehicle. For example, it can be preset for the vehicle by the operator or the vehicle owner and stored in the TEE (Trusted Execution Environment) of the vehicle local, so as to reduce the risk of key leakage. Or the derivative key can also be calculated based on the security root key deployed by the vehicle itself through the key derivation algorithm, and the derivative key is stored in the vehicle local to further reduce the difficulty of the key being cracked.

[0094] In one embodiment, the vehicle can store the first data by initiating a blockchain transaction. For example, the vehicle can first determine the data to be uploaded to the blockchain corresponding to the first data, and initiate a blockchain transaction for this data in the blockchain. Then, when the blockchain transaction passes the consensus, the data to be uploaded to the blockchain is stored in the blockchain. By this method, after the blockchain transaction corresponding to the first data passes the consensus of multiple block connection points in the blockchain network, the first data will be stored in the blockchain, ensuring that the stored first data has been jointly recognized by multiple blockchain nodes.

[0095] Among them, the vehicle can store the first data in the blockchain in various ways. Correspondingly, the data to be stored in the blockchain can have multiple possibilities. As an exemplary embodiment, the vehicle can determine the first data as the data to be stored in the blockchain, so that all the first data corresponding to the mode switching behavior is stored in the blockchain, ensuring the integrity of the stored data. As another exemplary embodiment, the vehicle can determine the data digest of the first data as the data to be stored on the blockchain, and the data digest can be the hash of all the first data. Correspondingly, when storing the digest of the first data in the blockchain, the complete first data can be saved in a preset off-chain storage space, such as saved locally in the vehicle, saved in the database of the vehicle provider, saved in the above decision server, etc. The embodiments of the present disclosure do not limit this. In this way, only the data digest of the first data needs to be stored in the blockchain. Compared with storing the complete first data, the amount of data stored on the blockchain is greatly reduced, which helps to save the on-chain storage space of the blockchain and reduces the data processing burden of each blockchain node.

[0096] The foregoing embodiments are all directed to the process of storing the first data. In fact, the vehicle can also obtain the second data corresponding to the mode switching behavior and send the data to the decision server corresponding to the autonomous driving mode. Among them, the second data can include at least one of the following: the vehicle identifier of the vehicle, the vehicle position, the vehicle state parameters, the vehicle environment parameters, and the behavior parameters of the mode switching behavior. Among them, the vehicle position can be position information such as the longitude and latitude of the vehicle (at the moment when the above mode switching behavior is detected) determined by the on-vehicle positioning module; the above on-vehicle positioning module can implement the positioning of the vehicle through GPS (Global Positioning System) positioning technology, Beidou navigation positioning technology, etc. The vehicle state parameters can include the current driving speed, the indicator light state, the multimedia device state, etc. The vehicle environment parameters can include the road surface water accumulation situation, the position and / or speed of surrounding obstacles, the current weather condition, etc. The behavior parameters of the mode switching behavior can include the behavior type (action or voice), the operation moment, and the above switching trigger information, etc. The embodiments of the present disclosure do not limit the specific content of the above second data.

[0097] Based on the above-mentioned second data, when the decision-making server obtains the authorization of the operator, it can use it to optimize and upgrade its own decision-making logic to further improve the corresponding decision-making quality. Of course, if the decision-making server is an edge server deployed in a vehicle, the edge server can upload the second data to a preset logic training party (such as the provider of the above-mentioned autonomous driving function) when it obtains the authorization of the operator, so that the latter can use the second data uploaded by multiple vehicles as training samples to train its own decision-making logic, and then send and deploy the trained new logic to each edge server to realize the upgrade and iteration of the vehicle's autonomous driving function. Moreover, the decision-making logic of the upgraded autonomous driving function will be more in line with the current driving habits of the vehicle or the driving habits of vehicle users.

[0098] According to an embodiment of the present disclosure, the operator of the vehicle can perform a mode switching behavior to trigger the switching of the driving mode of the vehicle between the manual driving mode and the autonomous driving mode; correspondingly, when the vehicle detects the above behavior, it can obtain the first data corresponding to the behavior, including the vehicle identifier, the switching trigger information and the time information corresponding to the behavior, and store the first data in the blockchain network.

[0099] On the one hand, since the blockchain network is composed of multiple blockchain network nodes, and each blockchain network node independently records the data to be stored, the data stored in the blockchain network can basically not be tampered with by individual blockchain network nodes, thus effectively ensuring the authenticity of the stored data. By storing the above-mentioned first data in the blockchain network, the above-mentioned characteristics of the blockchain network can be utilized to realize the reliable storage of the first data and ensure the authenticity of the data. On the other hand, since the first data includes the vehicle identifier, the switching trigger information and the time information corresponding to the mode switching behavior implemented by the operator, based on the above-mentioned real data stored in the blockchain network, it is possible to accurately judge the real driving mode of the vehicle at any historical moment, and then accurately determine the corresponding responsible party, which helps to realize a reliable driving responsibility division and effectively avoid disputes among relevant parties.

[0100] Figure 4 is an interaction flowchart of a data storage method shown according to an embodiment of the present disclosure. The following will be combined with Figure 4 , taking the complete process that when the vehicle is in the manual driving mode, the operator performs an autonomous driving start behavior to switch the driving mode to the autonomous driving mode, and then performs an autonomous driving stop behavior to switch the driving mode to the autonomous driving mode after a period of time as an example, to illustrate the corresponding data storage process in detail. As Figure 4 shown, this process may include steps 401a-426.

[0101] Step 401a, the vehicle detects the behavior of activating autonomous driving.

[0102] Depending on the relative position of the operator and the vehicle, the vehicle can detect the autonomous driving activation behavior implemented by the operator in different ways:

[0103] When the operator is a person inside the vehicle, the vehicle can detect the autonomous driving activation behavior implemented by the operator through the sensors installed on itself. Taking the operator as the driver as an example, the autonomous driving activation behavior implemented by the driver can be an action, specifically, the action of toggling the cruise control lever to the "ON" position. After making this action, the position sensor corresponding to the cruise control lever can detect the position change of the lever, and thus can send a corresponding position change notification message to the vehicle. Correspondingly, the vehicle can determine that the driver has made the action of toggling the cruise control lever based on this message. In addition, the above message can include the position information after toggling (i.e., the position information corresponding to the above "ON" position), so that the vehicle can determine that the action made by the driver is the autonomous driving activation behavior based on this position information. Or, the autonomous driving activation behavior implemented by the driver can also be speaking, specifically, speaking the trigger voice for activating the autonomous driving function, such as saying "XXX, please activate autonomous driving". After emitting the above voice, the voice recording sensor installed in the vehicle will collect the voice and be awakened by the wake-up word "XXX" in it. Furthermore, by recognizing keywords such as "activate" and "autonomous driving", it can be further determined that the operator has spoken the statement for triggering the activation of the autonomous driving function, that is, has implemented the autonomous driving activation behavior.

[0104] When the operator is a person outside the vehicle, the vehicle can receive the mode switching instruction sent by the operator through the operation device used by himself / herself (such as a computer, a mobile phone, a smart wearable device, etc.). Correspondingly, the vehicle can determine that the operator has implemented the autonomous driving activation behavior based on this instruction. For example, the operator can trigger the activation of the autonomous driving button on the vehicle control page of the mobile phone. Correspondingly, after the mobile phone detects this trigger operation, it can send an autonomous driving activation instruction to the vehicle, so that the vehicle can determine that the operator has implemented the autonomous driving activation behavior based on this instruction.

[0105] Step 402a, the vehicle collects the identity information of the operator.

[0106] In one embodiment, the identity information of the operator may be the biometric information of the operator. For example, the biometric information may be voice information. Specifically, it may be characteristic parameters such as the pitch, frequency, and period of the voice. The vehicle may first acquire the voice of the operator, and then extract the corresponding characteristic parameters based on the voice. For example, when the aforesaid autonomous driving activation behavior is speaking, the vehicle may directly extract the corresponding characteristic parameters for the triggered voice uttered; or, when the aforesaid autonomous driving activation behavior is an action, after detecting the aforesaid action, the vehicle may prompt the operator to speak through voice, text, vibration, or other means, collect the voice spoken by the operator, and then extract the corresponding characteristic parameters for the collected voice. The specific process of extracting characteristic parameters from the voice may refer to the voice processing technology in the related art, which will not be elaborated herein. Again, for example, the biometric information may also be fingerprint information. Specifically, it may be the feature points in the fingerprint pattern. Correspondingly, a fingerprint acquisition module may be installed on the aforesaid cruise control lever of the vehicle to acquire the fingerprint of the driver while the driver toggles the lever. Alternatively, a fingerprint acquisition module may also be provided at positions such as the steering wheel and the center console, and the operator may be instructed to acquire a fingerprint on the module, and then the fingerprint information therein may be extracted. Also, for example, the biometric information may also be iris information. Specifically, it may be the feature points in the iris pattern. Correspondingly, an iris acquisition module may be installed on the center console of the vehicle or other positions corresponding to the driver's eyes to acquire the iris of the user through the module, and then the iris information therein may be extracted.

[0107] In another embodiment, the identity information of the operator may also be the user information preset by the operator, such as account passwords, preset switching wake-up words, etc. Such user information may be used to verify the identity of the operator, which will not be elaborated herein.

[0108] When the identity information of the operator is acquired, on the one hand, the vehicle may start the process of switching the driving mode (corresponding to steps 403a - 407a), and on the other hand, it may start the process of depositing the first data (corresponding to steps 408a - 411a). The following will be described separately:

[0109] Step 403a, the vehicle sends a request to activate autonomous driving to the decision server.

[0110] After acquiring the identity information of the operator, the vehicle may generate a request to activate autonomous driving containing the identity information and send the request to the decision server.

[0111] As described above, the decision-making server can be a cloud server, in which case the server can serve multiple vehicles, that is, it can receive requests for enabling or disabling autonomous driving sent by multiple vehicles respectively. Alternatively, the decision-making server can also be an edge server deployed locally on the vehicle, in which case the server only serves the vehicle it is located in, that is, it only receives requests for enabling or disabling autonomous driving sent by the vehicle it is located in. Among them, the vehicle identification of the vehicle where the edge server is located is usually saved in the edge server. Based on this, when the decision-making server is a cloud server, the request sent by the vehicle can also include the vehicle identification to accurately inform the cloud server about the originator of the request. When the decision-making server is an edge server, the request sent by the vehicle may not include its own vehicle identification.

[0112] In addition, the above request for enabling autonomous driving can also include necessary information such as the request time and the behavior type of the autonomous driving enabling behavior, so as to make a decision and judgment with the decision-making server.

[0113] Step 404a, the decision-making server verifies the identity information of the operator.

[0114] When receiving a request for enabling autonomous driving sent by a vehicle, the decision-making server can verify the identity information of the operator included in the request. For example, when the decision-making server is a cloud server, the decision-making server can locally associate and record the vehicle identifications of its corresponding vehicles and the identity information of the legal operators (such as historical operators) of the vehicles. Correspondingly, the decision-making server can query locally according to the vehicle identification to check whether the identity information of the operator included in the above request exists: if it exists, the verification passes; otherwise, the verification fails. Alternatively, when the decision-making server is an edge server, the decision-making server can locally record the identity information of the legal operator (such as historical operator) of the vehicle it is located in. Correspondingly, the decision-making server can query locally to check whether the identity information of the operator included in the above request exists: if it exists, the verification passes; otherwise, the verification fails.

[0115] If the verification passes, it can proceed to step 405a; otherwise, it can proceed to step 406a.

[0116] Step 405a, the decision-making server determines the usage rights of the operator.

[0117] When the identity information is successfully verified, the decision-making server can further determine the identity permissions of the operator. For example, the decision-making server can locally pre-record a permission binding relationship table, which records the corresponding relationship between the vehicle identifier and the identity information of the bound user who has the permission to use the automatic driving mode for the vehicle. Thus, in response to the above automatic driving activation request, the decision-making server can query in the permission binding relationship table whether the operator has the permission to use the automatic driving mode for the vehicle.

[0118] When the operator does not have the above-mentioned permission, the bound users in the table can be further notified so that the operator can obtain the authorization of the bound users. For example, notification messages for the above automatic driving activation request can be sent to each bound user respectively to inform the bound users that the operator is requesting to activate the automatic driving mode. Furthermore, if the bound user approves the operator's use of the vehicle's automatic driving mode, a confirmation message can be returned to the decision-making server. Correspondingly, the decision-making server can count the number of confirmation messages received within a preset duration and determine the authorization result for the operator's use permission of the automatic driving mode by comparing it with the number of bound users. The specific process can be seen in Table 1 below:

[0119] Table 1

[0120]

[0121] In Table 1 above, when no confirmation message from the bound user is received within the preset duration, whether the authorization is passed or not can be pre-set by the bound user, and the embodiments of the present disclosure do not limit this.

[0122] Through the above method, if it is determined that the user has the use permission (the query result shows that the user has the permission, or the user is authorized by the bound user), step 406a can be entered; otherwise, the vehicle's own driving mode can be refused to be switched, that is, the vehicle's current driving mode (i.e., the manual driving mode) remains unchanged.

[0123] Step 406a, the decision-making server returns an automatic driving activation response to the vehicle.

[0124] Regardless of the verification result of step 404a and the determination result of step 405a, the results can be included in the automatic driving activation response and returned to the vehicle for the vehicle to perform corresponding processing. In other words, the automatic driving activation response returned by the decision-making server can be used to instruct the vehicle to switch the current manual driving mode to the automatic driving mode; or it can also be used to instruct the vehicle to reject the above switch.

[0125] Step 407a, the vehicle activates the automatic driving mode.

[0126] After receiving the response to activate the autonomous driving, if the message indicates that the operator has the permission to use the autonomous driving mode of the vehicle, the vehicle can switch its driving mode from the current manual driving mode to the autonomous driving mode, that is, activate the autonomous driving function. The specific process of switching the driving mode can refer to the records in the related art, and the embodiments of the present disclosure do not limit this. Otherwise, if the message indicates that the operator does not have the permission to use the autonomous driving mode of the vehicle, the vehicle can refuse to switch its driving mode, that is, keep the current driving mode of the vehicle (i.e., the manual driving mode) unchanged.

[0127] In addition, regardless of whether the driving mode of the vehicle is switched or not, the vehicle can inform the operator by playing voice, text display, flashing signal lights, etc., so that the operator can know the switching result corresponding to the mode switching behavior and try to avoid misoperation.

[0128] So far, the process of switching the driving mode of the vehicle after detecting the activation behavior of autonomous driving has been described. Next, the process of depositing the first data will be described in combination with steps 408a - 411a:

[0129] Step 408a, the vehicle obtains the first data corresponding to the mode switching behavior.

[0130] In the case of detecting the above-mentioned activation behavior of autonomous driving, the vehicle can obtain the first data to be deposited. For example, obtain the vehicle identifier, the switching trigger information and time information corresponding to the above-mentioned activation behavior of autonomous driving, etc. as the first data.

[0131] Among them, the above-mentioned switching trigger information can have various forms. For example, after sending the above-mentioned activation request for autonomous driving containing the identity information of the operator to the decision server, the vehicle can use this request as the switching trigger information. For another example, in the case of receiving the response to activate the autonomous driving returned by the above-mentioned decision server, the vehicle can use this response as the switching trigger information.

[0132] It can be understood that in the case of using the above-mentioned activation request for autonomous driving as the switching trigger information, the vehicle needs to determine the first data after sending the activation request for autonomous driving, that is, step 408a needs to be executed after step 401a; and in the case of using the above-mentioned response to activate the autonomous driving as the switching trigger information, the vehicle needs to determine the first data after receiving the response to activate the autonomous driving, that is, step 408a needs to be executed after step 406a. Correspondingly, the time information in the first data can be the moment of sending the above-mentioned activation request for autonomous driving, the moment of receiving the response to activate the autonomous driving, and / or the implementation moment of the above-mentioned activation behavior of autonomous driving, etc., and the embodiments of the present disclosure do not limit this.

[0133] For the above multiple first data, the vehicle can package them to generate a first data packet to facilitate the subsequent data transmission and evidence storage. In addition, since the above identity information belongs to the user privacy of the operator, in order to avoid the security risks caused by privacy leakage, the vehicle can encrypt the above identity information and use the encrypted identity information ciphertext as part of the first data.

[0134] Step 409a: The vehicle initiates a blockchain transaction for the first data to the blockchain network.

[0135] After obtaining the first data, the vehicle can initiate a blockchain transaction for the first data to the blockchain network. Accordingly, each blockchain node in the blockchain network can initiate a consensus on the blockchain transaction. Furthermore, each node can store the first data in the blockchain if the consensus is passed. The generation, initiation, consensus and execution process of the blockchain transaction can all be referred to the records in the relevant technology, and the embodiments of the present disclosure are not limited to this.

[0136] In step 410a, the blockchain network stores the first data in the blockchain after the transaction passes consensus.

[0137] In one embodiment, the vehicle may store the complete first data in the blockchain. For example, the blockchain transaction generated by the vehicle may include the complete first data, so that each blockchain node in the blockchain network may store the first data in the blockchain.

[0138] In another embodiment, in order to prevent the first data from occupying more on-chain storage space of the blockchain, the vehicle may only store the data summary of the vehicle in the blockchain, and save the complete first data to the preset off-chain storage space. For example, the vehicle can calculate the hash of the above-mentioned first data packet, and include the hash in the initiated blockchain transaction and submit it to the blockchain, so that after the transaction consensus is passed, the hash will be stored on the blockchain. In addition, the vehicle can save the first data packet locally in the vehicle, in the database corresponding to the provider of the vehicle, in the above-mentioned decision server, etc. Normally, the amount of data in the data summary is much smaller than the first data, so this method can greatly reduce the occupation of the on-chain storage space by the first data being stored.

[0139] For each of the above embodiments, the blockchain network may package the first data (or a summary of the first data) into a block, or save it in the world state of the blockchain in the form of a transaction receipt (Receipt), and the specific process will not be repeated here.

[0140] Step 411a, the blockchain network returns a notification message to the vehicle.

[0141] After the above data deposit and verification are completed, the blockchain network can return a notification message to the vehicle through the blockchain node corresponding to the vehicle to inform the deposit and verification result of the first data. Of course, in the case where the above blockchain transaction consensus is not passed, the above first data may not be deposited to the blockchain. At this time, the blockchain network can also return a notification message to the vehicle to inform information such as the reason for the failure of the deposit and verification, so that the vehicle can initiate a blockchain transaction for the first data again or abandon the deposit and verification.

[0142] So far, the description of the deposit and verification process of the first data in response to the automatic driving start behavior is completed. As mentioned above, steps 403a - 407a are the driving mode switching process, and steps 408a - 411a are the deposit and verification process of the first data. The above two processes can be independently completed by the vehicle respectively, and the specific execution order between each step can be adjusted according to the actual situation.

[0143] The above steps 401a - 411a are the description of the processing process after the operator implements the automatic driving start behavior when the vehicle is in the manual driving mode. After step 407a is executed, the vehicle is in the automatic driving mode. Thereafter, the operator can implement the automatic driving stop behavior at any time to switch the driving mode of the vehicle back to the manual driving mode. The following describes this process in combination with steps 412b - 422b similar to the foregoing steps:

[0144] Step 412b, the vehicle detects the automatic driving stop behavior.

[0145] According to the different relative positions of the operator and the vehicle, the vehicle can detect the automatic driving stop behavior implemented by the operator in different ways:

[0146] When the operator is a person inside the vehicle, the vehicle can detect the automatic driving shutdown behavior performed by the operator through the sensors installed on itself. Taking the operator as the driver as an example, the automatic driving shutdown behavior performed by the driver can be an action. Specifically, this action can be the action of toggling the cruise control lever to the "OFF" position. After this action is taken, the position sensor corresponding to the cruise control lever can detect the position change of the lever, and thus can send a corresponding position change notification message to the vehicle. Correspondingly, the vehicle can determine that the driver has taken the action of toggling the cruise control lever based on this message. In addition, the above message can include the position information after toggling (i.e., the position information corresponding to the above "OFF" position), so that the vehicle can determine that the action taken by the driver is the automatic driving shutdown behavior based on this position information. Or, the automatic driving shutdown behavior performed by the driver can also be at least one of the behaviors such as turning the steering wheel, stepping on the accelerator pedal, stepping on the brake pedal, etc. Taking the brake pedal as an example, the position sensor corresponding to the pedal can send the detected position change information to the vehicle, and the latter can determine that the operator has performed the automatic driving shutdown behavior based on this information. Or, the automatic driving shutdown behavior performed by the driver can also be speaking, specifically, it can be speaking the trigger voice for turning off the automatic driving function, such as saying "XXX, please turn off the automatic driving". After the above voice is emitted, the voice input sensor installed in the vehicle will collect this voice and be awakened by the wake-up word "XXX" in it. Furthermore, by identifying keywords such as "turn off" and "automatic driving", it can be further determined that the operator has spoken the statement for triggering the turning off of the automatic driving function, that is, has performed the automatic driving shutdown behavior.

[0147] When the operator is a person outside the vehicle, the vehicle can receive the mode switching instruction sent by the operator through the operating device used by himself / herself (such as a computer, a mobile phone, a smart wearable device, etc.). Correspondingly, the vehicle can determine that the operator has performed the automatic driving shutdown behavior based on this instruction. For example, the operator can trigger the automatic driving shutdown button on the vehicle control page of the mobile phone. Correspondingly, after the mobile phone detects this trigger operation, it can send an automatic driving shutdown instruction to the vehicle, so that the vehicle can determine that the operator has performed the automatic driving shutdown behavior based on this instruction.

[0148] Step 413b, the vehicle collects the identity information of the operator.

[0149] The specific method of collecting the identity information of the operator is not essentially different from the aforementioned step 402a, and reference can be made to the foregoing description, which will not be elaborated here. When the identity information of the operator is collected, on the one hand, the vehicle can start the process of switching the driving mode (corresponding to steps 414b - 418b), and on the other hand, it can start the process of depositing the first data (corresponding to steps 419b - 422b), which will be described separately below:

[0150] Step 414b, the vehicle sends a request to the decision-making server to turn off the automatic driving.

[0151] Step 415b, the decision-making server verifies the identity information of the operator.

[0152] If the verification is passed, step 415b can be entered; otherwise, it can refuse to switch its driving mode, that is, keep the current driving mode of the vehicle (i.e., the automatic driving mode) unchanged.

[0153] Step 416b, the decision-making server determines the usage permission of the operator for the automatic driving mode.

[0154] For the specific processes of the vehicle verifying the identity information of the operator and determining the usage permission of the operator, reference can be made to the descriptions of the aforementioned steps 404a and 405a respectively, which will not be elaborated here.

[0155] When the verification of the identity information is passed, the decision-making server can further determine the identity permission of the operator. For example, the decision-making server can pre-record a permission binding relationship table locally, and the permission binding relationship table records the corresponding relationship between the vehicle identifier and the identity information of the bound user who has the usage permission for the automatic driving mode of the vehicle. Thus, corresponding to the above-mentioned request to turn off the automatic driving, the decision-making server can query in the permission binding relationship table whether the operator has the usage permission for the automatic driving mode of the vehicle.

[0156] When the operator does not have the above-mentioned usage permission, the bound users in the table can be further notified so that the operator can obtain the authorization of the bound users. For example, a notification message for the above-mentioned request to turn off the automatic driving can be sent to each bound user respectively to inform the bound user that the operator is requesting to turn off the automatic driving mode. Furthermore, if the bound user approves the operator's use of the automatic driving mode of the vehicle, a confirmation message can be returned to the decision-making server. Correspondingly, the decision-making server can count the number of confirmation messages received within a preset time period and determine the authorization result for the operator's usage permission for the automatic driving mode by comparing it with the number of bound users. The specific process can be seen in Table 1 above, which will not be elaborated here.

[0157] Step 417b, the decision-making server returns an automatic driving shutdown response to the vehicle.

[0158] In the above manner, if it is determined that the operator has the usage permission (the query result shows that the operator has this permission, or the bound user authorizes this permission), an automatic driving shutdown response can be returned to the vehicle.

[0159] Of course, even if it is determined that the operator does not have the usage permission, a corresponding automatic driving shutdown response can also be returned to facilitate the vehicle to perform corresponding processing. For example, the vehicle can refuse to switch its driving mode, that is, keep the current driving mode (i.e., the automatic driving mode) of the vehicle unchanged.

[0160] Step 418b, the vehicle turns off the automatic driving mode.

[0161] After receiving the automatic driving shutdown response, if the message indicates that the operator has the usage permission for the automatic driving mode of the vehicle, the vehicle can switch its driving mode from the current automatic driving mode to the manual driving mode, that is, turn off the automatic driving function. The specific process of switching the driving mode can refer to the records in the related art, and the embodiments of the present disclosure do not limit this. Otherwise, if the message indicates that the operator does not have the usage permission for the automatic driving mode of the vehicle, the vehicle can refuse to switch its driving mode, that is, keep the current driving mode (i.e., the automatic driving mode) of the vehicle unchanged.

[0162] In addition, regardless of whether the driving mode of the vehicle is switched or not, the operator can be informed by means of voice prompts, text displays, flashing signal lights, etc., so that the operator can know the switching result corresponding to the mode switching behavior and avoid misoperations as much as possible.

[0163] So far, the process of switching the driving mode of the vehicle after detecting the automatic driving shutdown behavior has been described. The process of depositing the first data will be described below with reference to steps 419b - 422b:

[0164] Step 419b, the vehicle obtains the first data corresponding to the mode switching behavior.

[0165] In the case of detecting the above automatic driving shutdown behavior, the vehicle can generate the first data to be deposited. The determined first data can include the vehicle identifier, as well as the switching trigger information and the corresponding time information corresponding to the above automatic driving shutdown behavior.

[0166] The switching trigger information may be in various forms. For example, after sending the automatic driving shutdown request including the identity information of the operator to the decision server, the vehicle may use the request as the switching trigger information. For another example, when receiving the automatic driving shutdown response returned by the decision server, the vehicle may use the response as the switching trigger information.

[0167] It can be understood that, when the above-mentioned automatic driving shutdown request is used as the switching trigger information, the vehicle needs to determine the first data after sending the automatic driving shutdown request, that is, step 419b needs to be performed after step 414b. When the above-mentioned automatic driving shutdown response is used as the switching trigger information, the vehicle needs to determine the first data after receiving the automatic driving shutdown response, that is, step 419b needs to be performed after step 417b.

[0168] Step 420b: The vehicle initiates a blockchain transaction for the first data to the blockchain network.

[0169] Step 421b, the blockchain network stores the first data in the blockchain after the transaction passes consensus.

[0170] Step 422b, the blockchain network returns a notification message to the vehicle.

[0171] The specific process of storing the first data on the chain can be found in the records of the aforementioned steps 409a-411a, which will not be repeated here.

[0172] At this point, the description of the first data storage process in response to the automatic driving shutdown behavior is complete. As mentioned above, steps 414b-418b are the driving mode switching process, and steps 419b-422b are the first data storage process. The above two processes can be completed independently by the vehicle, and the specific execution order between the steps can be adjusted according to the actual situation.

[0173] The above steps are all processing procedures corresponding to the mode switching behavior implemented by the operator. In fact, after the processing of the automatic driving on behavior or the automatic driving off behavior is completed, the vehicle can also obtain the second data corresponding to the behavior and save it to the decision server. The following is an explanation in conjunction with steps 423-426.

[0174] Step 423: The vehicle determines second data corresponding to the mode switching behavior.

[0175] After detecting any of the above mode switching behaviors, the vehicle can obtain second data for the mode switching behavior. Specifically, the above second data may include vehicle identification, time information of the vehicle driving mode switching process, vehicle location, vehicle internal and external environment and other information.

[0176] Of course, the process of obtaining the above-mentioned second data can be carried out by the vehicle after obtaining the authorization of the operator or the vehicle owner to ensure the right to know of the above-mentioned personnel about the acquisition of the second data.

[0177] Step 424, the vehicle sends the second data to the decision-making server.

[0178] Step 425, the decision-making server saves the received second data.

[0179] Step 426, the decision-making server returns a second response message to the vehicle for the second data.

[0180] Then, the vehicle can send the obtained second data to the decision-making server for storage. The specific process of on-chain certification can be referred to the description of the foregoing steps 409a-411a and will not be elaborated here. Accordingly, after receiving the second data, the decision-making server can save the data in the local storage space, or save it to a preset database or other storage spaces, or upload it to a preset logical training party (such as the provider of the above-mentioned autonomous driving function). Furthermore, the above-mentioned logical training party can use the second data uploaded by multiple vehicles as training samples to train its own decision-making logic, and send the trained new logic to each edge server for deployment to achieve the upgrade and iteration of the vehicle's autonomous driving function.

[0181] Figure 4 The vehicle in the embodiment has an interaction process with the decision-making server and decides whether to switch the current driving mode according to the mode switching response returned by the decision-making server. In fact, in the case where the above-mentioned mode switching behavior is a mode switching action, the vehicle can also directly switch the current driving mode without the above-mentioned interaction process after detecting the mode switching action. The following combination Figure 5 is used to illustrate this method.

[0182] Figure 5 is an interaction flowchart of another data certification method shown according to an embodiment of the present disclosure. As Figure 5 shown, this method includes the following steps 501a-518.

[0183] Step 501a, the vehicle detects an autonomous driving start action.

[0184] According to the different relative positions of the operator and the vehicle, the vehicle can detect the autonomous driving start action implemented by the operator in different ways.

[0185] When the operator is a person inside the vehicle, the vehicle can detect the autonomous driving activation action performed by the operator through sensors installed on itself. Taking the operator as the driver as an example, the autonomous driving activation action performed by the driver can be an action, specifically, an action of toggling the cruise control lever to the "ON" position. After performing this action, the position sensor corresponding to the cruise control lever can detect the position change of the lever, and thus can send a corresponding position change notification message to the vehicle. Correspondingly, the vehicle can determine that the driver has performed the action of toggling the cruise control lever based on this message. In addition, the above message can include the position information after toggling (i.e., the position information corresponding to the above "ON" position), so that the vehicle can determine that the action performed by the driver is an autonomous driving activation action based on this position information.

[0186] Step 502a, the vehicle activates the autonomous driving mode.

[0187] When detecting the autonomous driving activation action, the vehicle can directly activate the autonomous driving mode. This method does not require the decision server to make a judgment based on the identity information of the operator, which helps to simplify the decision-making logic during the driving mode switching process of the vehicle.

[0188] Step 503a, the vehicle collects the activation video information corresponding to the autonomous driving activation action.

[0189] The vehicle can use pre-installed video recording devices such as cameras to continuously record videos at predefined positions, and in the case of detecting the above mode switching action, use the video segment corresponding to this action as the corresponding video information. Taking the action of the user toggling the cruise control lever as an example, the camera can continuously record the position where the lever is located and save the corresponding video. In the case of detecting that the above cruise control lever has been toggled, the vehicle can intercept the video segment corresponding to the time interval (such as 3s before and after that moment) when the toggling occurs from the saved video, and use this video segment as the activation video information corresponding to the autonomous driving activation action. Of course, the above activation video information can also include video time information such as the above toggling moment and time interval.

[0190] Step 504a, the vehicle obtains the first data corresponding to the autonomous driving activation action.

[0191] In the case of detecting the above autonomous driving activation action, the vehicle can obtain the first data to be archived. Such as obtaining the vehicle identifier, the switching trigger information corresponding to the above autonomous driving activation action, and time information, etc. as the first data. Among them, the above switching trigger information can be the aforementioned activation video information. Of course, in the case where the activation video information includes the video time information corresponding to the above toggling action, this video time information can be used as the time information of the detected toggling action to avoid duplicate recording of time information.

[0192] Step 505a, the vehicle initiates a blockchain transaction for the first data to the blockchain network.

[0193] Step 506a, after the transaction passes the consensus, the blockchain network archives the first data to the blockchain.

[0194] Step 507a, the blockchain network returns a notification message to the vehicle.

[0195] For the specific process of archiving the above first data, reference can be made to Figure 4 the detailed description of the corresponding steps 409a - 411a, which will not be elaborated here.

[0196] So far, the description of the process of archiving the first data in response to the autonomous driving activation action is completed. After step 503a is executed, the vehicle is in the autonomous driving mode. Thereafter, the operator can perform an autonomous driving deactivation action at any time to switch the driving mode of the vehicle back to the manual driving mode. The following describes this process in combination with steps 508b - 515b similar to the foregoing steps:

[0197] Step 508b, the vehicle detects an autonomous driving deactivation action.

[0198] Step 509a, the vehicle turns off the autonomous driving mode.

[0199] In the case of detecting an autonomous driving deactivation action, the vehicle can directly turn off the autonomous driving mode, that is, turn off the autonomous driving function of the vehicle. This method does not require the decision server to make a judgment based on the identity information of the operator, which helps to simplify the decision-making logic of the vehicle during the driving mode switching process.

[0200] Step 510b, the vehicle collects the closing video information corresponding to the autonomous driving deactivation action.

[0201] The vehicle can detect the autonomous driving deactivation action performed by the operator through the sensors installed on itself. Taking the operator as the driver as an example, the autonomous driving deactivation action performed by the driver can be an action. Specifically, this action can be the action of toggling the cruise control lever to the "OFF" position. For this action, the specific process of the vehicle continuously recording video through the camera and intercepting the video segment related to this action as the closing video information can refer to the description of the foregoing step 502a, which will not be elaborated here.

[0202] Alternatively, when the driving mode switching actions performed by the operator are actions such as turning the steering wheel, stepping on the brake pedal, stepping on the accelerator pedal, etc., the vehicle can collect video information corresponding to the above actions through the cameras installed on itself, such as taking photos or recording videos. Of course, it is also possible to continuously record the corresponding video, and when the above actions are detected, extract the video frame images corresponding to the actions or intercept the video segments corresponding to the actions from the recorded video as the closing video information. Specifically, when the driver steps on the brake pedal with the foot, the foot of the driver (such as facing the brake pedal) can be photographed to obtain the closing video information; when the driver toggles the cruise control lever with the hand, the hand of the driver (such as facing the cruise control lever) can be photographed to obtain the closing video information, etc., which will not be elaborated here.

[0203] Step 511b, the vehicle obtains the first data corresponding to the automatic driving shutdown action.

[0204] When the above automatic driving shutdown action is detected, the vehicle can obtain the first data to be certified. Such as obtaining the vehicle identification, the switching trigger information corresponding to the above automatic driving shutdown action, and the time information, etc. as the first data. Among them, the switching trigger information can be the above-mentioned closing video information. Of course, when the closing video information includes the video time information corresponding to the automatic driving shutdown action, this video time information can be used as the time information of the detected action to avoid duplicate recording of time information.

[0205] Step 512b, the vehicle initiates a blockchain transaction for the first data to the blockchain network.

[0206] Step 513b, after the transaction passes the consensus, the blockchain network certifies the first data to the blockchain.

[0207] Step 514b, the blockchain network returns a notification message to the vehicle.

[0208] For the specific certification process of the above first data, reference can be made to Figure 4 the detailed description of the corresponding steps 409a - 411a, which will not be elaborated here.

[0209] So far, the description of the driving mode switching process after the vehicle detects the automatic driving shutdown action is completed. Similar to Figure 4 After steps 501a - 504a, or after steps 508b - 511b, the vehicle can upload the corresponding second data to the decision server respectively:

[0210] Step 515, the vehicle determines the second data corresponding to the mode switching action.

[0211] Step 516, the vehicle sends the second data to the decision server.

[0212] Step 517, the decision-making server saves the received second data.

[0213] Step 518, the decision-making server returns a response message for the second data to the vehicle.

[0214] For the specific process of depositing the above first data, reference can be made to Figure 4 the detailed description corresponding to steps 423 - 426, which will not be elaborated here.

[0215] The first data deposited into the blockchain network through the foregoing process can be used to determine the historical driving mode of the vehicle. For this purpose, the present disclosure also exemplarily proposes a method for determining a driving mode. Figure 6 is a flowchart of a method for determining a driving mode shown in an exemplary embodiment of the present disclosure. As Figure 6 shown, this method is applied to any device, such as a node device of a blockchain node in the blockchain storing the first data, a server connected to the node device, or any terminal, etc., hereinafter referred to as a mode determination device. This method may include the following steps:

[0216] Step S601, according to the target vehicle identifier and target time information of the target vehicle, determine the target data deposited into the blockchain network, where the target data corresponds to the historical mode switching behavior of the operator for the target vehicle, and the historical mode switching behavior is used to trigger the switching of the driving mode of the target vehicle between a manual driving mode and an autonomous driving mode.

[0217] Step S602, obtain the target switching trigger information in the target data, and determine the historical driving mode corresponding to the target time information according to the target switching trigger information.

[0218] In the manner described in the foregoing embodiment, the first data corresponding to the mode switching behavior of the operator is deposited into the blockchain network. The target data described in this embodiment is the first data corresponding to any of the above mode switching behaviors. As described above, the first data includes a vehicle identifier, a switching trigger information corresponding to the mode switching behavior, and corresponding time information, so the corresponding target data can be determined through the vehicle identifier and time information.

[0219] In one embodiment, the mode determination device may receive a mode determination request initiated by a requester. For example, in the case of a traffic accident of the target vehicle, it is necessary to determine the driving mode of the vehicle at the moment of the accident in order to determine the responsible party for the accident among the vehicle manufacturer, the autonomous driving provider, and the driver. For this purpose, the server corresponding to any of the above parties or the regulatory party (such as the traffic management department, etc.) may initiate a mode determination request to the mode determination device.

[0220] The above-mentioned mode determines that the request may include the target vehicle identifier and target time information of the target vehicle. Thus, the mode determination device can determine the target data from the data stored on the chain (i.e., the aforementioned first data) based on the identifier and information. Specifically, the mode determination device can determine the vehicle data including the target vehicle identifier from the data stored in the blockchain network, and use the vehicle data whose included time information matches the target time information as the target data. Furthermore, the switching trigger information included in the target data can be determined as the target switching trigger information. For example, when the above-mentioned target vehicle identifier is the factory number of the vehicle and the target time information is the accident occurrence time, the mode determination device can query all the vehicle data corresponding to the target vehicle from the first data stored in the blockchain according to the above vehicle number. Furthermore, among the vehicle data of the queried target vehicle, query the vehicle data uploaded last time before the accident occurrence time, and use this vehicle data as the corresponding target data. Furthermore, the switching trigger information included in this data is determined as the target switching trigger information.

[0221] It can be understood that the above-mentioned traffic accident must have occurred before the mode query. That is, relative to the current moment, the accident occurrence time is the target historical moment, and the time information recorded in the queried target data should indicate that the corresponding historical mode switching behavior occurred before this target historical moment. Accordingly, the mode determination device can determine the mode switching method corresponding to the historical mode switching behavior according to the above-mentioned target switching trigger information, such as determining whether it is switching from the manual driving mode to the automatic driving mode or from the automatic driving mode to the manual driving mode. Furthermore, the device can use the switched mode corresponding to the above mode switching method as the historical driving mode corresponding to the target time information, that is, determine whether the historical driving mode is the automatic driving mode or the manual driving mode.

[0222] For example, the driver of the target vehicle triggers the switching of the vehicle's driving mode to the autonomous driving mode by implementing an autonomous driving activation behavior at 12:00 on September 15, 2021; subsequently, at 12:15, by implementing an autonomous driving deactivation behavior, the driver triggers the switching of the vehicle's driving mode to the manual driving mode, that is, the autonomous driving function is activated for 15 minutes between 12:00 and 12:15 on September 15, 2021. If the target vehicle has a minor traffic accident of rubbing against another vehicle at 12:10 on September 15, 2021, the mode determination device can take 12:10 as the accident occurrence time, and then determine the first data that was most recently stored before this time (that is, the first data corresponding to the autonomous driving activation behavior implemented by the driver and stored at 12:00 on September 15, 2021) as the target data. Thus, according to the target switching trigger information in this data, it can be determined that the switched driving mode is the autonomous driving mode, and further, it can be determined that the driving mode at 12:10 on September 15, 2021 is also the autonomous driving mode, so that the provider (or vehicle enterprise) of the autonomous driving of the vehicle responsible for the accident can be determined, rather than the driver.

[0223] Through this embodiment, for the target vehicle, the mode determination device can determine the historical driving mode of the vehicle at any historical moment. Because of the characteristic that the data on the blockchain cannot be tampered with, the target data stored on the blockchain can be considered true and reliable. Furthermore, the above-mentioned historical driving mode determined based on this data can be considered the true driving state of the target vehicle at the corresponding historical moment, which helps to accurately determine the responsible entity of the vehicle according to this state, effectively ensuring the authenticity of the determination.

[0224] Corresponding to the foregoing embodiments of the data storage method, the present disclosure also provides an embodiment of a data storage device.

[0225] An embodiment of the present disclosure provides a data storage device, and the device may be a device such as an in-vehicle terminal. In one embodiment, the device includes one or more processors, and the processors are configured to:

[0226] Detect a mode switching behavior implemented by a vehicle operator, where the mode switching behavior is used to trigger the switching of the vehicle's driving mode between the manual driving mode and the autonomous driving mode;

[0227] Obtain first data corresponding to the mode switching behavior, where the first data includes the vehicle identifier of the vehicle and the switching trigger information and time information corresponding to the mode switching behavior;

[0228] Store the first data in a blockchain network.

[0229] In one embodiment, the processor is further configured to:

[0230] Before obtaining the first data corresponding to the mode switching behavior, generate a mode switching request including the identity information of the operator;

[0231] Send the mode switching request to the decision-making server corresponding to the automatic driving mode, and receive a mode switching response returned by the decision-making server, where the mode switching response is used to indicate whether the operator has the permission to use the automatic driving mode.

[0232] In one embodiment, the processor is further configured to:

[0233] When the mode switching response indicates that the operator has the permission to use the automatic driving mode, switch the driving mode of the vehicle between the manual driving mode and the automatic driving mode; and,

[0234] When the mode switching response indicates that the operator does not have the permission to use the automatic driving mode, refuse to switch the driving mode of the vehicle between the manual driving mode and the automatic driving mode.

[0235] In one embodiment, the switching trigger information includes: the mode switching request and the mode switching response.

[0236] In one embodiment, the mode switching behavior is a mode switching action, and the processor is further configured to:

[0237] In response to the mode switching action, switch the driving mode of the vehicle between the manual driving mode and the automatic driving mode, where the switching trigger information includes video information recording the mode switching behavior.

[0238] In one embodiment, the processor is further configured to:

[0239] Obtain second data corresponding to the mode switching behavior, where the second data includes at least one of the following: the vehicle identification of the vehicle, the vehicle position, the vehicle state parameters, the vehicle environment parameters, the behavior parameters of the mode switching behavior;

[0240] Send the second data to the decision-making server corresponding to the automatic driving mode.

[0241] In one embodiment, the decision-making server includes:

[0242] A cloud server or an edge server deployed in the vehicle.

[0243] In one embodiment, the first data further includes the identity information of the operator,

[0244] The processor is further configured to: perform an encryption process on the identity information;

[0245] The processor is configured to: store the encrypted identity information on the blockchain network as evidence.

[0246] In one embodiment, the processor is configured to:

[0247] Determine the data to be uploaded to the chain corresponding to the first data, and initiate a blockchain network transaction for the data to be uploaded to the chain in the blockchain network;

[0248] In the case where the blockchain network transaction passes the consensus, save the data to be uploaded to the chain in the blockchain network.

[0249] In one embodiment, the processor is configured to:

[0250] Determine the first data as the data to be uploaded to the chain; or,

[0251] Determine the data digest of the first data as the data to be uploaded to the chain, wherein the first data is saved to a preset off-chain storage space.

[0252] In one embodiment, the vehicle is connected to the blockchain network server corresponding to the provider of the vehicle through a blockchain network client running locally to access the blockchain network.

[0253] In one embodiment, the blockchain network is a consortium chain, and the consortium chain members include the vehicle, and also include a first server corresponding to the provider of the vehicle, a second server corresponding to the provider of the autonomous driving function, and / or a regulator server corresponding to a predefined regulator.

[0254] In one embodiment, the autonomous driving mode includes:

[0255] An assisted driving mode that requires the operator to participate; and,

[0256] A fully autonomous driving mode that does not require the operator to participate.

[0257] Corresponding to the embodiment of the foregoing data storage method as evidence, the present disclosure also provides an embodiment of a device for determining a driving mode.

[0258] An embodiment of the present disclosure provides a device for determining a driving mode. In one embodiment, the device includes one or more processors, and the processor is configured to:

[0259] Determine target data stored in a blockchain network based on a target vehicle identifier and target time information of a target vehicle, where the target data corresponds to a historical mode switching behavior performed by an operator on the target vehicle, and the historical mode switching behavior is used to trigger switching the driving mode of the target vehicle between a manual driving mode and an autonomous driving mode;

[0260] Obtain target switching trigger information in the target data, and determine the historical driving mode corresponding to the target time information based on the target switching trigger information.

[0261] In one embodiment, the processor is configured to:

[0262] Determine vehicle data containing the target vehicle identifier from the data stored in the blockchain network, and use the vehicle data whose contained time information matches the target time information as the target data.

[0263] In one embodiment, the target time information is a target historical moment, and the time information recorded in the target data indicates that the historical mode switching behavior occurred before the target historical moment; the processor is further configured to:

[0264] Determine the mode switching method corresponding to the historical mode switching behavior based on the target switching trigger information, where the mode switching method is switching from the manual driving mode to the autonomous driving mode or switching from the autonomous driving mode to the manual driving mode;

[0265] Use the switched-to mode corresponding to the mode switching method as the historical driving mode corresponding to the target time information.

[0266] An embodiment of the present disclosure also provides an electronic device, including: a processor; a memory for storing instructions executable by the processor; wherein, the processor is configured to implement the relevance determination method described in any of the above embodiments.

[0267] An embodiment of the present disclosure also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements the steps in the relevance determination method described in any of the above embodiments.

[0268] Regarding the device in the above embodiments, the specific manners in which each module performs operations have been described in detail in the embodiments of the related method, and will not be elaborated here.

[0269] Figure 7FIG. 0 is a schematic block diagram of an apparatus 700 for data deposit or driving mode determination according to an embodiment of the present disclosure. For example, the apparatus 700 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0270] Referring Figure 7 , the apparatus 700 may include one or more of the following components: a processing component 702, a memory 704, a power component 706, a multimedia component 708, an audio component 710, an input / output (I / O) interface 712, a sensor component 714, and a communication component 716.

[0271] The processing component 702 generally controls the overall operation of the apparatus 700, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the above-described methods. In addition, the processing component 702 may include one or more modules to facilitate the interaction between the processing component 702 and other components. For example, the processing component 702 may include a multimedia module to facilitate the interaction between the multimedia component 708 and the processing component 702.

[0272] The memory 704 is configured to store various types of data to support the operation of the apparatus 700. Examples of such data include instructions for any application or method operating on the apparatus 700, contact data, phone book data, messages, pictures, videos, etc. The memory 704 may 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 memory, flash memory, a magnetic disk, or an optical disk.

[0273] The power component 706 provides power to the various components of the apparatus 700. The power component 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the apparatus 700.

[0274] The multimedia component 708 includes a screen that provides an output interface between the device 700 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 can be implemented as a touch screen 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 can sense not only the boundaries of touch or swipe actions but also detect the duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 708 includes a front camera and / or a rear camera. When the device 700 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

[0275] The audio component 710 is configured to output and / or input audio signals. For example, the audio component 710 includes a microphone (MIC) that is configured to receive external audio signals when the device 700 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals can be further stored in the memory 704 or transmitted via the communication component 716. In some embodiments, the audio component 710 further includes a speaker for outputting audio signals.

[0276] The I / O interface 712 provides an interface between the processing component 702 and a peripheral interface module, and the peripheral interface module can be a keyboard, a click wheel, buttons, etc. These buttons can include but are not limited to: a home button, a volume button, a power button, and a lock button.

[0277] The sensor component 714 includes one or more sensors for providing status assessments of various aspects of the device 700. For example, the sensor component 714 can detect the on / off state of the device 700, the relative positioning of components, such as the display and the keypad of the device 700. The sensor component 714 can also detect a change in the position of the device 700 or a component of the device 700, the presence or absence of user contact with the device 700, the orientation or acceleration / deceleration of the device 700, and the temperature change of the device 700. The sensor component 714 can include a proximity sensor that is configured to detect the presence of nearby objects without any physical contact. The sensor component 714 can also include a light sensor, such as a CMOS or a CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 714 can further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0278] The communication component 716 is configured to facilitate communication, either wired or wirelessly, between the device 700 and other devices. The device 700 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G LTE, 6G NR, or a combination thereof. In an exemplary embodiment, the communication component 716 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 716 further 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.

[0279] In an exemplary embodiment, the device 700 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 for performing the above method.

[0280] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions, such as a memory 704 including instructions, is also provided. The above instructions may be executed by a processor 720 of the device 700 to complete the above 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.

[0281] Other embodiments of the present disclosure will be readily apparent to those skilled in the art after considering the specification and practicing the embodiments disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure, which follow the general principles of the present disclosure and include known common knowledge or conventional technical means in the technical field not disclosed herein. The specification and embodiments are only to be considered as exemplary, and the true scope and spirit of the present disclosure are pointed out by the following claims.

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

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

[0284] The methods and apparatuses provided by the embodiments of the present disclosure have been introduced in detail above. Specific examples are used in this document to elaborate on the principles and implementation manners of the present disclosure. The description of the above embodiments is only used to help understand the method and its core idea of the present disclosure; at the same time, for those of ordinary skill in the art, according to the idea of the present disclosure, there will be changes in the specific implementation manners and application scopes. In summary, the content of this specification should not be construed as a limitation to the present disclosure.

Claims

1. A data archiving method, comprising: Detecting a mode switching behavior implemented by a vehicle operator, where the mode switching behavior is used to trigger switching the driving mode of the vehicle between a manual driving mode and an autonomous driving mode; Generating a mode switching request including the identity information of the operator; sending the mode switching request to a decision-making server corresponding to the autonomous driving mode, and receiving a mode switching response returned by the decision-making server, where the mode switching response is used to indicate whether the operator has the permission to use the autonomous driving mode; Obtaining first data corresponding to the mode switching behavior, where the first data includes a vehicle identifier of the vehicle, as well as switching trigger information and time information corresponding to the mode switching behavior; Archiving the first data to a blockchain network; Obtaining second data corresponding to the mode switching behavior, and sending the second data to the decision-making server for optimizing the decision-making logic of the decision-making server, where the second data includes at least one of the following: the vehicle identifier of the vehicle, vehicle position, vehicle state parameters, vehicle environment parameters, and behavior parameters of the mode switching behavior.

2. The method according to claim 1, further comprising: When the mode switching response indicates that the operator has the permission to use the autonomous driving mode, switching the driving mode of the vehicle between the manual driving mode and the autonomous driving mode; And, When the mode switching response indicates that the operator does not have the permission to use the autonomous driving mode, refusing to switch the driving mode of the vehicle between the manual driving mode and the autonomous driving mode.

3. The method according to claim 1, The switching trigger information includes: The mode switching request and the mode switching response.

4. The method according to claim 1, where the mode switching behavior is a mode switching action, and the method further comprises: In response to the mode switching action, switching the driving mode of the vehicle between the manual driving mode and the autonomous driving mode, where the switching trigger information includes video information recording the mode switching behavior.

5. The method according to any one of claims 1-4, where the decision-making server includes: A cloud server or an edge server deployed in the vehicle.

6. The method according to claim 1, where the first data further includes the identity information of the operator, The method further includes: Performing an encryption process on the identity information; The archiving the first data to the blockchain network includes: archiving the encrypted identity information to the blockchain network.

7. The method according to claim 1, where the archiving the first data to the blockchain network includes: Determining the data to be uploaded to the blockchain corresponding to the first data, and initiating a blockchain network transaction for the data to be uploaded to the blockchain in the blockchain network; When the blockchain network transaction passes consensus, saving the data to be uploaded to the blockchain in the blockchain network.

8. The method according to claim 7, where the determining the data to be uploaded to the blockchain corresponding to the first data includes: Determine the first data as the data to be uploaded to the blockchain; Or, Determine the data digest of the first data as the data to be uploaded to the blockchain, where the first data is saved to a preset off-chain storage space.

9. The method according to claim 1, wherein the vehicle connects to the blockchain network server corresponding to the provider of the vehicle through the blockchain network client running locally to access the blockchain network.

10. The method according to claim 1, wherein the blockchain network is a consortium chain, and the consortium chain members include the vehicle, a first server corresponding to the provider of the vehicle, a second server corresponding to the provider of the autonomous driving function, and / or a regulator server corresponding to a predefined regulator.

11. The method according to claim 1, wherein the autonomous driving mode includes: An assisted driving mode that requires the operator's participation; And, A fully autonomous driving mode that does not require the operator's participation.

12. A method for determining a driving mode, comprising: Determine target data stored in the blockchain network according to the target vehicle identifier and target time information of the target vehicle, where the target data corresponds to a historical mode switching behavior implemented by the operator for the target vehicle, and the historical mode switching behavior is used to trigger the switching of the driving mode of the target vehicle between the manual driving mode and the autonomous driving mode; wherein, when the decision server corresponding to the autonomous driving mode of the target vehicle returns a mode switching response in response to a mode switching request including the identity information of the operator indicating that the operator has the permission to use the autonomous driving mode, the switching is performed; Obtain the target switching trigger information in the target data, and determine the historical driving mode corresponding to the target time information according to the target switching trigger information; The second data corresponding to the mode switching behavior is sent to the decision server for optimizing the decision logic of the decision server, and the second data includes at least one of the following: the vehicle identifier of the vehicle, the vehicle position, the vehicle state parameters, the vehicle environment parameters, and the behavior parameters of the mode switching behavior.

13. The method according to claim 12, wherein the determining the target data stored in the blockchain network according to the target vehicle identifier and target time information of the target vehicle includes: Determine vehicle data including the target vehicle identifier from the data stored in the blockchain network, and use the vehicle data whose included time information matches the target time information as the target data.

14. The method according to claim 12, wherein the target time information is a target historical moment, and the time information recorded in the target data indicates that the historical mode switching behavior occurred before the target historical moment; the determining the historical driving mode corresponding to the target time information according to the target switching trigger information includes: Determine the mode switching method corresponding to the historical mode switching behavior according to the target switching trigger information, and the mode switching method is switching from the manual driving mode to the autonomous driving mode or switching from the autonomous driving mode to the manual driving mode; Use the switched mode corresponding to the mode switching method as the historical driving mode corresponding to the target time information.

15. A data certification device, the device includes one or more processors, and the processors are configured to: Detect a mode switching behavior implemented by an operator of the vehicle, where the mode switching behavior is used to trigger switching of the driving mode of the vehicle between a manual driving mode and an autonomous driving mode; Generate a mode switching request including the identity information of the operator; send the mode switching request to the decision-making server corresponding to the automatic driving mode, and receive a mode switching response returned by the decision-making server, where The mode switching response is used to indicate whether the operator has the permission to use the autonomous driving mode; Obtain first data corresponding to the mode switching behavior, where the first data includes a vehicle identifier of the vehicle and switching trigger information and time information corresponding to the mode switching behavior; Certify the first data to the blockchain network; Obtain second data corresponding to the mode switching behavior and send the second data to the decision server for optimizing the decision logic of the decision server, where the second data includes at least one of the following: the vehicle identifier of the vehicle, the vehicle position, vehicle state parameters, vehicle environment parameters, and behavior parameters of the mode switching behavior.

16. The device according to claim 15, wherein the processor is further configured to: Switch the driving mode of the vehicle between a manual driving mode and an autonomous driving mode when the mode switching response indicates that the operator has the permission to use the autonomous driving mode; and, Refuse to switch the driving mode of the vehicle between a manual driving mode and an autonomous driving mode when the mode switching response indicates that the operator does not have the permission to use the autonomous driving mode.

17. The device according to claim 15, The switching trigger information includes: The mode switching request and the mode switching response.

18. The device according to claim 15, where the mode switching behavior is a mode switching action, and the processor is further configured to: In response to the mode switching action, switch the driving mode of the vehicle between a manual driving mode and an autonomous driving mode, where The switching trigger information includes video information recording the mode switching behavior.

19. The device according to claim 15, wherein the processor is configured to: Determine the data to be uploaded to the chain corresponding to the first data and initiate a blockchain network transaction for the data to be uploaded to the chain in the blockchain network; Save the data to be uploaded to the chain in the blockchain network when the blockchain network transaction passes consensus.

20. The device according to claim 19, wherein the processor is configured to: Determine the first data as the data to be uploaded to the chain; or, Determine the data digest of the first data as the data to be chained, where The first data is saved to a preset off-chain storage space.

21. A device for determining a driving mode, the device includes one or more processors, and the processors are configured to: Determine target data stored in the blockchain network according to the target vehicle identifier and target time information of the target vehicle, where the target data corresponds to a historical mode switching behavior of an operator for the target vehicle, and the historical mode switching behavior is used to trigger switching the driving mode of the target vehicle between a manual driving mode and an autonomous driving mode; wherein, Perform the switching when the mode switching response returned by the decision server corresponding to the autonomous driving mode of the target vehicle in response to a mode switching request including the identity information of the operator indicates that the operator has the permission to use the autonomous driving mode; Obtain the target switching trigger information in the target data, and determine the historical driving mode corresponding to the target time information according to the target switching trigger information; The second data corresponding to the mode switching behavior is sent to the decision server for optimizing the decision logic of the decision server. The second data includes at least one of the following: the vehicle identification of the vehicle, the vehicle location, the vehicle state parameters, the vehicle environment parameters, and the behavior parameters of the mode switching behavior.

22. The apparatus according to claim 21, wherein the processor is configured to: Determine vehicle data including the target vehicle identification from the data stored in the blockchain network, and use the vehicle data whose included time information matches the target time information as the target data.

23. The apparatus according to claim 21, wherein the target time information is a target historical moment, and the time information recorded in the target data indicates that the historical mode switching behavior occurred before the target historical moment; the processor is further configured to: Determine the mode switching method corresponding to the historical mode switching behavior according to the target switching trigger information, where the mode switching method is switching from the manual driving mode to the autonomous driving mode or switching from the autonomous driving mode to the manual driving mode; Use the switched-to mode corresponding to the mode switching method as the historical driving mode corresponding to the target time information.

24. An electronic device, characterized in that, Comprising: A processor; A memory for storing instructions executable by the processor; Wherein, the processor is configured to implement the data storage method according to any one of claims 1 to 11 or implement the method for determining the driving mode according to any one of claims 12 to 14.

25. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps in the data storage method according to any one of claims 1 to 11 or implements the steps in the method for determining the driving mode according to any one of claims 12 to 14.

Images