A method, device, equipment, medium and system for mutual charging of automobiles

Abstract

The application discloses a kind of automobile mutual assistance charging method, device, equipment, medium and system, by responding to the charging request sent by power receiving vehicle, from the all vehicles in the pre-set candidate power supply vehicle account book, determine the power supply vehicle that meets the charging demand of the charging request;Feedback power supply vehicle information to the power receiving vehicle, and synchronously power receiving vehicle information to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle meet, complete mutual assistance charging. Realize the mutual assistance charging between electric vehicles, improve the convenience of electric vehicle charging, and timely charge for the vehicle with insufficient power.

Description

Technical Field

[0001] This invention relates to the field of vehicle-side control technology, specifically to a method, apparatus, equipment, medium, and system for mutual charging of automobiles. Background Technology

[0002] With the promotion and popularization of electric vehicles, the number of electric vehicles on the road is increasing, and the demand for charging is also growing. Currently, electric vehicles drive to charging stations to charge. However, the coverage of charging stations is relatively low, and electric vehicles often run out of power to reach the nearest charging station. Therefore, the existing electric vehicle charging service is not convenient enough and fails to provide a better user experience for car owners. Summary of the Invention

[0003] To address the aforementioned issues, this invention proposes a method, apparatus, equipment, medium, and system for mutual charging of electric vehicles, enabling vehicle-to-vehicle mutual charging, improving the convenience of electric vehicle charging, and providing timely charging for vehicles with insufficient power.

[0004] To achieve the above objectives, embodiments of the present invention provide a method for mutual charging of automobiles, the method comprising:

[0005] In response to a charging request sent by a powered vehicle, a power supply vehicle that meets the charging requirements of the charging request is determined from all vehicles in a preset candidate power supply vehicle register.

[0006] The power supply vehicle information is fed back to the power receiving vehicle, and the power receiving vehicle information is synchronized to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging.

[0007] As an improvement to the above scheme, the candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0008] The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

[0009] Preferably, the process of completing the vehicle registration for power supply specifically includes:

[0010] The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply. The vehicle number includes the OEM information to which the vehicle belongs.

[0011] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0012] As a preferred embodiment, the real-time update process of the vehicle information specifically includes:

[0013] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0014] Preferably, the method further includes:

[0015] When a power supply cancellation request is received from a registered vehicle, the registration request information and vehicle information of the registered vehicle mentioned in the power supply vehicle ledger of this cloud platform are deleted.

[0016] As a preferred embodiment, the charging request includes the required power supply of the receiving vehicle and the location of the receiving vehicle;

[0017] The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes:

[0018] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0019] Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles;

[0020] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0021] As an improvement to the above scheme, before determining one of the candidate power supply vehicles as the power supply vehicle based on the obtained list of candidate power supply vehicles, the method further includes:

[0022] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0023] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0024] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes:

[0025] Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM;

[0026] The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power.

[0027] The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0028] As a preferred embodiment, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes:

[0029] Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list;

[0030] The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0031] Preferably, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles specifically includes:

[0032] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0033] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0034] Preferably, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles specifically includes:

[0035] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0036] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0037] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0038] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0039] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0040] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0041] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0042] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0043] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0044] The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

[0045] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0046] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0047] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0048] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0049] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0050] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0051] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0052] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0053] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0054] As a preferred embodiment, the step of feeding back the power supply vehicle information to the power receiving vehicle and synchronizing the power receiving vehicle information to the power supply vehicle specifically includes:

[0055] When the power supply vehicle is not a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the vehicle number of the power supply vehicle is uploaded to the candidate power supply vehicle ledger, so that the cloud platform of the power supply vehicle can obtain the vehicle number of the power supply vehicle from the candidate power supply vehicle ledger, and send the power receiving vehicle information to the power supply vehicle according to the key of the power supply vehicle.

[0056] When the power supply vehicle is a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the power receiving vehicle information is sent to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet up and complete mutual charging.

[0057] As a preferred embodiment, the power supply vehicle information includes the real-time location information, real-time remaining power information, and contact information of the power supply vehicle;

[0058] The information about the receiving vehicle includes its power receiving location, real-time remaining power information, and contact information.

[0059] This invention also provides a car mutual charging device, the device comprising:

[0060] The charging request response module is used to respond to a charging request sent by a powered vehicle and determine a power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register.

[0061] The signal feedback module is used to feed back the power supply vehicle information to the power receiving vehicle and synchronize the power receiving vehicle information to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging.

[0062] As an improvement to the above scheme, the candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0063] The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

[0064] Preferably, the process of completing the vehicle registration for power supply specifically includes:

[0065] The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply. The vehicle number includes the OEM information to which the vehicle belongs.

[0066] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0067] Furthermore, the real-time update process of the vehicle information specifically includes:

[0068] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0069] As a preferred embodiment, the device further includes:

[0070] The cancellation module is used to delete the registration application information and vehicle information of the registered vehicle in the power supply vehicle sub-ledger of this cloud platform when a power supply cancellation request is received from a registered vehicle.

[0071] As a preferred embodiment, the charging request includes the required power supply of the receiving vehicle and the location of the receiving vehicle;

[0072] The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes:

[0073] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0074] Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles;

[0075] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0076] As an improvement to the above scheme, before determining one of the candidate power supply vehicles as the power supply vehicle based on the obtained list of candidate power supply vehicles, the method further includes:

[0077] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0078] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0079] Furthermore, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes:

[0080] Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM;

[0081] The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power.

[0082] The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0083] As a parallel implementation, the charging request response module is further used for:

[0084] Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list;

[0085] The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0086] Preferably, the charging request response module is further configured to:

[0087] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0088] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0089] Preferably, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles specifically includes:

[0090] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0091] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0092] The charging request response module is also specifically used for:

[0093] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0094] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0095] As a parallel implementation, the charging request response module is further used for:

[0096] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0097] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0098] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0099] The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

[0100] As a parallel implementation, the charging request response module is further used for:

[0101] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0102] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0103] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0104] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0105] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0106] As a parallel implementation, the charging request response module is further used for:

[0107] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0108] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0109] As a preferred embodiment, the signal feedback module is specifically used for:

[0110] When the power supply vehicle is not a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the vehicle number of the power supply vehicle is uploaded to the candidate power supply vehicle ledger, so that the cloud platform of the power supply vehicle can obtain the vehicle number of the power supply vehicle from the candidate power supply vehicle ledger, and send the power receiving vehicle information to the power supply vehicle according to the key of the power supply vehicle.

[0111] When the power supply vehicle is a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the power receiving vehicle information is sent to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet up and complete mutual charging.

[0112] Preferably, the power supply vehicle information includes the real-time location information, real-time remaining power information, and contact information of the power supply vehicle;

[0113] The information about the receiving vehicle includes its power receiving location, real-time remaining power information, and contact information.

[0114] Another embodiment of the present invention provides a method for mutual charging of automobiles, the method comprising:

[0115] The cloud platform receiving the power supply vehicle determines the power supply vehicle information from all vehicles in the preset candidate power supply vehicle ledger.

[0116] The power receiving vehicle information is sent to the power supply vehicle so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging.

[0117] Preferably, the candidate power supply vehicle ledger includes power supply vehicle sub-ledgers established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0118] The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

[0119] As a preferred method, the process of the vehicle completing the power supply vehicle registration specifically includes:

[0120] The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply. The vehicle number includes the OEM information to which the vehicle belongs.

[0121] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0122] Furthermore, the real-time update process of the vehicle information specifically includes:

[0123] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0124] Preferably, the method further includes:

[0125] When a power supply cancellation request is received from a registered vehicle, the registration request information and vehicle information of the registered vehicle mentioned in the power supply vehicle ledger of this cloud platform are deleted.

[0126] Preferably, the process by which the cloud platform of the power receiving vehicle determines the power supply vehicle specifically includes the cloud platform of the power receiving vehicle executing:

[0127] Receive the charging request sent by the receiving vehicle;

[0128] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0129] From all the acquired vehicles, a list of candidate power supply vehicles that meet the charging requirements of the charging request is selected. The charging requirements include the required power and the location of the receiving vehicle.

[0130] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0131] As a preferred approach, before determining one of the candidate power supply vehicles from the obtained list as the power supply vehicle, the cloud platform of the power receiving vehicle performs the following:

[0132] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0133] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0134] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0135] Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM;

[0136] The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power.

[0137] The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0138] As a preferred embodiment, the process involves filtering out a list of candidate power supply vehicles that meet the charging requirements from all acquired vehicles, and the cloud platform of the receiving vehicle performs the following:

[0139] Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list;

[0140] The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0141] Preferably, determining one of the candidate power supply vehicles from the obtained list specifically includes the following steps: the cloud platform of the power receiving vehicle executes the following:

[0142] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0143] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0144] Preferably, determining one of the candidate power supply vehicles from the obtained list specifically includes the following steps: the cloud platform of the power receiving vehicle executes the following:

[0145] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0146] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0147] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list specifically includes the following steps: the cloud platform of the power receiving vehicle executes the following:

[0148] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0149] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0150] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list specifically includes the following steps: the cloud platform of the power receiving vehicle executes the following:

[0151] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0152] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0153] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0154] The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

[0155] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list specifically includes the following steps: the cloud platform of the power receiving vehicle executes the following:

[0156] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0157] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0158] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0159] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0160] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0161] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list specifically includes the following steps: the cloud platform of the power receiving vehicle executes the following:

[0162] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0163] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0164] Preferably, the power receiving vehicle information includes the power receiving vehicle's location, real-time remaining power information, and contact information.

[0165] In another embodiment of the present invention, a vehicle mutual charging device is provided, the device comprising:

[0166] The receiving module is used to receive vehicle information of the power supply vehicle determined by the cloud platform of the power receiving vehicle from all vehicles in the preset candidate power supply vehicle ledger.

[0167] The transmitting module is used to send information about the receiving vehicle to the power supply vehicle, so that the power supply vehicle and the receiving vehicle can meet and complete mutual charging.

[0168] Preferably, the candidate power supply vehicle ledger includes power supply vehicle sub-ledgers established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0169] The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

[0170] As a preferred method, the process of the vehicle completing the power supply vehicle registration specifically includes:

[0171] The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply. The vehicle number includes the OEM information to which the vehicle belongs.

[0172] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0173] Furthermore, the real-time update process of the vehicle information specifically includes:

[0174] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0175] Preferably, the device further includes:

[0176] The unregistration module is used to delete the registration application information and vehicle information of the registered vehicle in the power supply vehicle sub-ledger of this cloud platform when a power supply cancellation request is received from a registered vehicle.

[0177] Furthermore, the process by which the cloud platform of the power receiving vehicle determines the power supply vehicle specifically includes the following steps: the cloud platform of the power receiving vehicle executes:

[0178] Receive the charging request sent by the receiving vehicle;

[0179] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0180] From all the acquired vehicles, a list of candidate power supply vehicles that meet the charging requirements of the charging request is selected. The charging requirements include the required power and the location of the receiving vehicle.

[0181] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0182] Preferably, before determining one of the candidate power supply vehicles from the obtained list as the power supply vehicle, the cloud platform of the power receiving vehicle performs the following:

[0183] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0184] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0185] Preferably, one of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles. Specifically, this includes the charging request response module of the cloud platform of the power receiving vehicle executing the following:

[0186] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0187] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0188] Preferably, one of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles. Specifically, this includes the charging request response module of the cloud platform of the power receiving vehicle executing the following:

[0189] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0190] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0191] Preferably, one of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles. Specifically, this includes the charging request response module of the cloud platform of the power receiving vehicle executing the following:

[0192] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0193] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0194] Preferably, one of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles. Specifically, this includes the charging request response module of the cloud platform of the power receiving vehicle executing the following:

[0195] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0196] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0197] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0198] The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

[0199] Preferably, one of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles. Specifically, this includes the charging request response module of the cloud platform of the power receiving vehicle executing the following:

[0200] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0201] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0202] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0203] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0204] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0205] Preferably, one of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles. Specifically, this includes the charging request response module of the cloud platform of the power receiving vehicle executing the following:

[0206] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0207] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0208] Preferably, the power receiving vehicle information includes the power receiving vehicle's location, real-time remaining power information, and contact information.

[0209] This invention provides a method for mutual charging of automobiles, the method comprising:

[0210] In response to a user-inputted charging command, a charging request is sent to the cloud platform of the OEM, so that the cloud platform can determine a power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register.

[0211] Based on the power supply vehicle information fed back by the cloud platform, the system meets with the power supply vehicle and completes mutual charging.

[0212] As an improvement to the above scheme, the candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0213] The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

[0214] Preferably, the process of completing the registration of the power supply vehicle specifically includes:

[0215] The registration application information is sent to the cloud platform of the vehicle's OEM manufacturer. The registration application information includes the vehicle number, the user-set threshold power supply, and the user-set threshold distance for power supply. The vehicle number includes the OEM manufacturer information to which the vehicle belongs.

[0216] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0217] As a preferred embodiment, the real-time update process of the vehicle information specifically includes:

[0218] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0219] Preferably, the method further includes:

[0220] Send a power supply cancellation request to the cloud platform of this OEM, so that the cloud platform, upon receiving the power supply cancellation request, deletes the vehicle's registration application information and vehicle information from the power supply vehicle sub-ledger of this cloud platform.

[0221] As a preferred embodiment, the charging request includes the required power supply of the receiving vehicle and the location of the receiving vehicle;

[0222] The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0223] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0224] Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles;

[0225] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0226] As an improvement to the above scheme, before determining one of the candidate power supply vehicles from the obtained list as the power supply vehicle, the cloud platform of the power receiving vehicle performs the following:

[0227] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0228] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0229] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0230] Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM;

[0231] The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power.

[0232] The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0233] As a preferred embodiment, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0234] Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list;

[0235] The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0236] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0237] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0238] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0239] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0240] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0241] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0242] As a parallel solution, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following: the cloud platform of the receiving vehicle performs the following:

[0243] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0244] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0245] As a parallel solution, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following: the cloud platform of the receiving vehicle performs the following:

[0246] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0247] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0248] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0249] The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

[0250] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0251] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0252] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0253] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0254] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0255] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0256] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0257] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0258] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0259] As a preferred embodiment, the power supply vehicle information includes the real-time location information, real-time remaining power information, and contact information of the power supply vehicle.

[0260] Another embodiment of the present invention provides a car mutual charging device, the device comprising:

[0261] The charging request module is used to respond to the charging command input by the user and send a charging request to the cloud platform of the OEM so that the cloud platform can determine the charging vehicle that meets the charging requirements of the charging request from all vehicles in the preset candidate power supply vehicle ledger.

[0262] The mutual charging module is used to connect with the power supply vehicle based on the power supply vehicle information fed back by the cloud platform and complete the mutual charging.

[0263] Preferably, the candidate power supply vehicle ledger includes power supply vehicle sub-ledgers established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0264] The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

[0265] Preferably, the process of completing the registration of the power supply vehicle specifically includes:

[0266] The registration application information is sent to the cloud platform of the vehicle's OEM manufacturer. The registration application information includes the vehicle number, the user-set threshold power supply, and the user-set threshold distance for power supply. The vehicle number includes the OEM manufacturer information to which the vehicle belongs.

[0267] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0268] As a preferred embodiment, the real-time update process of the vehicle information specifically includes:

[0269] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0270] Preferably, the device further includes:

[0271] The deregistration module is used to send a power supply cancellation request to the cloud platform of this OEM, so that the cloud platform deletes the vehicle's registration application information and vehicle information from the power supply vehicle sub-ledger of this cloud platform upon receiving the power supply cancellation request.

[0272] As a preferred embodiment, the charging request includes the required power supply of the receiving vehicle and the location of the receiving vehicle;

[0273] The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0274] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0275] Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles;

[0276] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0277] As an improvement to the above scheme, before determining one of the candidate power supply vehicles from the obtained list as the power supply vehicle, the cloud platform of the power receiving vehicle performs the following:

[0278] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0279] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0280] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle performs the following:

[0281] Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM;

[0282] The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power.

[0283] The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0284] As a preferred embodiment, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle executes the following:

[0285] Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list;

[0286] The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0287] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle performs the following:

[0288] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0289] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0290] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle performs the following:

[0291] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0292] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0293] As a parallel solution, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle executes the following:

[0294] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0295] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0296] As a parallel solution, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle executes the following:

[0297] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0298] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0299] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0300] The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

[0301] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list specifically includes the following: the charging request response module of the cloud platform of the power receiving vehicle executes the following:

[0302] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0303] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0304] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0305] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0306] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0307] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list specifically includes the following: the charging request response module of the cloud platform of the power receiving vehicle executes the following:

[0308] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0309] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0310] As a preferred embodiment, the power supply vehicle information includes the real-time location information, real-time remaining power information, and contact information of the power supply vehicle.

[0311] Another embodiment of the present invention provides a method for mutual charging of automobiles, the method comprising:

[0312] The cloud platform receives power-receiving vehicle information through communication established by the vehicle number of the vehicle. The vehicle number is the vehicle number of the power supply vehicle determined by the cloud platform from all vehicles in the preset candidate power supply vehicle ledger.

[0313] After meeting with the receiving vehicle based on the information of the receiving vehicle, mutual charging is completed.

[0314] As an improvement to the above scheme, the candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0315] The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

[0316] Preferably, the process of completing the registration of the power supply vehicle specifically includes:

[0317] The registration application information is sent to the cloud platform of the vehicle's OEM manufacturer. The registration application information includes the vehicle number, the user-set threshold power supply, and the user-set threshold distance for power supply. The vehicle number includes the OEM manufacturer information to which the vehicle belongs.

[0318] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0319] As a preferred embodiment, the real-time update process of the vehicle information specifically includes:

[0320] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0321] Preferably, the method further includes:

[0322] Send a power supply cancellation request to the cloud platform of this OEM, so that the cloud platform, upon receiving the power supply cancellation request, deletes the vehicle's registration application information and vehicle information from the power supply vehicle sub-ledger of this cloud platform.

[0323] As a preferred embodiment, the charging request includes the required power supply of the receiving vehicle and the location of the receiving vehicle;

[0324] The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0325] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0326] Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles;

[0327] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0328] As an improvement to the above scheme, before determining one of the candidate power supply vehicles from the obtained list as the power supply vehicle, the cloud platform of the power receiving vehicle performs the following:

[0329] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0330] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0331] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0332] Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM;

[0333] The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power.

[0334] The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0335] As a preferred embodiment, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0336] Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list;

[0337] The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0338] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0339] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0340] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0341] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0342] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0343] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0344] As a parallel solution, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following: the cloud platform of the receiving vehicle performs the following:

[0345] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0346] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0347] As a parallel solution, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following: the cloud platform of the receiving vehicle performs the following:

[0348] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0349] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0350] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0351] The congestion score is equal to the sum of the product of the distance of the route with a congestion level of congestion and the first preset value, the distance of the route with a very congestion level of congestion and the second preset value, the distance of the route with a severe congestion level of congestion and the third preset value, and the distance of the route with a deadlock level of congestion and the fourth preset value.

[0352] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0353] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0354] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0355] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0356] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0357] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0358] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0359] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0360] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0361] As a preferred embodiment, the power receiving vehicle information includes the power receiving vehicle's location, real-time remaining power information, and contact information.

[0362] Another embodiment of the present invention provides a car mutual charging device, the device comprising:

[0363] The powered vehicle information receiving module is used to receive powered vehicle information sent by the cloud platform through the vehicle number of the vehicle. The vehicle number is the vehicle number of the power supply vehicle determined by the cloud platform of the powered vehicle from all vehicles in the preset candidate power supply vehicle ledger.

[0364] The mutual charging module is used to complete mutual charging after meeting with the receiving vehicle based on the receiving vehicle information.

[0365] Preferably, the candidate power supply vehicle ledger includes power supply vehicle sub-ledgers established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0366] The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

[0367] Preferably, the process of completing the registration of the power supply vehicle specifically includes:

[0368] The registration application information is sent to the cloud platform of the vehicle's OEM manufacturer. The registration application information includes the vehicle number, the user-set threshold power supply, and the user-set threshold distance for power supply. The vehicle number includes the OEM manufacturer information to which the vehicle belongs.

[0369] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0370] As a preferred embodiment, the real-time update process of the vehicle information specifically includes:

[0371] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0372] Preferably, the device further includes:

[0373] The deregistration module is used to send a power supply cancellation request to the cloud platform of this OEM, so that the cloud platform deletes the vehicle's registration application information and vehicle information from the power supply vehicle sub-ledger of this cloud platform upon receiving the power supply cancellation request.

[0374] As a preferred embodiment, the charging request includes the required power supply of the receiving vehicle and the location of the receiving vehicle;

[0375] The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes the following steps: the cloud platform of the receiving vehicle executes the following:

[0376] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0377] Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles;

[0378] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0379] As an improvement to the above scheme, before determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle, the cloud platform of the power receiving vehicle performs the following:

[0380] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0381] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0382] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle performs the following:

[0383] Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM;

[0384] The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power.

[0385] The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0386] As a preferred embodiment, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle executes the following:

[0387] Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list;

[0388] The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0389] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle performs the following:

[0390] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0391] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0392] Preferably, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle performs the following:

[0393] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0394] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0395] As a parallel solution, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle executes the following:

[0396] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0397] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0398] As a parallel solution, the step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes the following: the charging request response module of the cloud platform of the receiving vehicle executes the following:

[0399] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0400] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0401] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0402] The congestion score is equal to the sum of the product of the distance of the route with a congestion level of congestion and the first preset value, the distance of the route with a very congestion level of congestion and the second preset value, the distance of the route with a severe congestion level of congestion and the third preset value, and the distance of the route with a deadlock level of congestion and the fourth preset value.

[0403] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list specifically includes the following: the charging request response module of the cloud platform of the power receiving vehicle executes the following:

[0404] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0405] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0406] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0407] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0408] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0409] As a parallel solution, determining one of the candidate power supply vehicles from the obtained list specifically includes the following: the charging request response module of the cloud platform of the power receiving vehicle executes the following:

[0410] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0411] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0412] As a preferred embodiment, the power receiving vehicle information includes the power receiving vehicle's location, real-time remaining power information, and contact information.

[0413] Another embodiment of the present invention provides a car mutual charging system, the system comprising: at least one OEM cloud platform, and all OEM cloud platforms being connected to a blockchain;

[0414] The first cloud platform in the system is used to execute a vehicle mutual charging method as described in any of the above embodiments.

[0415] Preferably, each OEM cloud platform of the system is used to obtain vehicle registration information, and the vehicle includes at least one of any vehicle of that OEM, a power supply vehicle, and a power receiving vehicle.

[0416] Another embodiment of the present invention provides a vehicle mutual charging system, the system comprising: a power supply vehicle cloud platform and a power receiving vehicle cloud platform, the power supply vehicle cloud platform and the power receiving vehicle cloud platform being connected via blockchain;

[0417] The receiving vehicle cloud platform or the supplying vehicle cloud platform is used to execute a vehicle mutual charging method as described in any of the above embodiments.

[0418] Another embodiment of the present invention provides a terminal device including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the vehicle mutual charging method as described in any of the above embodiments.

[0419] Another embodiment of the present invention provides a computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the vehicle mutual charging method as described in any of the above embodiments.

[0420] Another embodiment of the present invention provides a vehicle mutual charging system, including a cloud platform, a power supply vehicle, and a power receiving vehicle, wherein the cloud platform is used to execute the vehicle mutual charging method as described in any of the above embodiments.

[0421] Compared with existing technologies, the present invention provides a method, apparatus, device, medium, and system for mutual charging of electric vehicles. In response to a charging request sent by a receiving vehicle, it determines a vehicle whose charging needs match the request from all vehicles in a pre-set candidate power supply vehicle register; it feeds back the power supply vehicle information to the receiving vehicle and synchronizes the receiving vehicle information to the power supply vehicle, enabling the power supply vehicle and the receiving vehicle to meet and complete mutual charging. This achieves vehicle-to-vehicle mutual charging between electric vehicles, improving the convenience of electric vehicle charging and enabling timely charging of vehicles with insufficient power. Attached Figure Description

[0422] Figure 1 This is a schematic flowchart of a vehicle mutual charging method provided in an embodiment of the present invention;

[0423] Figure 2 This is a schematic diagram showing the distribution of a candidate power supply vehicle ledger provided in an embodiment of the present invention;

[0424] Figure 3 This is a schematic diagram of the communication process of a vehicle mutual charging method provided in an embodiment of the present invention;

[0425] Figure 4 This is a schematic diagram of the structure of a car mutual charging device provided in an embodiment of the present invention;

[0426] Figure 5 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present invention. Detailed Implementation

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

[0428] See Figure 1 This is a flowchart illustrating a vehicle mutual charging method provided in an embodiment of the present invention, the method comprising steps S1 to S2:

[0429] S1, in response to a charging request sent by a powered vehicle, determine a power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register.

[0430] S2, feed back the power supply vehicle information to the power receiving vehicle, and synchronize the power receiving vehicle information to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging.

[0431] In the specific implementation of this embodiment, this method is executed by the cloud platform of the receiving vehicle. When the remaining power of the receiving vehicle is lower than the set charging threshold, a charging request is automatically sent to the cloud platform of the OEM of the receiving vehicle. When charging is needed, the vehicle owner can independently control the sending of a charging request to the cloud platform.

[0432] The cloud platform receives the charging request sent by the receiving vehicle, obtains a candidate power supply vehicle ledger containing all power supply vehicles, and determines the power supply vehicle that meets the charging needs of the receiving vehicle from all vehicles in the candidate power supply vehicle ledger.

[0433] Feedback of power supply vehicle information to the power receiving vehicle, notification to the power receiving vehicle that the power supply vehicles for mutual charging have been allocated, and feedback of information on the allocated power supply vehicles.

[0434] Synchronize the information of the receiving vehicles to the supplying vehicles, notify the supplying vehicles that the mutual charging distribution is complete, and provide feedback on the information of the receiving vehicles that need assistance.

[0435] This embodiment uses an anonymous data sharing ledger established by different nodes of the blockchain to store vehicle information from various OEMs. Data sharing is achieved through the blockchain, while the anonymity protects the data security of various cloud platforms. The blockchain also decentralizes the data of various platforms in the process of mutual charging of vehicles. Data from different OEMs' cloud platforms is shared through the blockchain, enabling mutual charging of vehicles from different OEMs' clouds.

[0436] By receiving charging requests from powered vehicles, responding to the charging requests, confirming powered vehicles from a pre-set list of candidate powered vehicles, completing the allocation of powered vehicles for mutual charging, synchronizing the information of powered vehicles to powered vehicles, and sending the information of powered vehicles to powered vehicles, the powered vehicles and powered vehicles meet and complete mutual charging.

[0437] In another embodiment provided by the present invention, the candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platforms of at least one OEM participating in mutual charging.

[0438] The vehicle ledger for power supply on any cloud platform includes registration application information for vehicles registered on that cloud platform and real-time updated vehicle information.

[0439] In the specific implementation of this embodiment, the cloud platforms of at least one OEM participating in mutual charging establish power supply vehicle ledgers in different nodes of the blockchain. The candidate power supply vehicle ledgers include the power supply vehicle ledgers established by each cloud platform. Each OEM has an independent cloud platform, and the vehicles produced by each OEM only communicate with the cloud platform of its own OEM.

[0440] The power supply vehicle ledger on any cloud platform contains registration application information for vehicles manufactured by the OEM that have completed power supply vehicle registration, as well as real-time updated vehicle information for registered vehicles.

[0441] The candidate power supply vehicle ledger is a collection of registration application information and real-time vehicle information for all vehicles distributed across different nodes of the blockchain.

[0442] See Figure 2 This is a schematic diagram of the distribution of a candidate power supply vehicle ledger provided in an embodiment of the present invention; wherein: the cloud platform A of the OEM A receives the registration application information of vehicles A1 to Ai, and sends the registration application information to the pre-built power supply vehicle sub-ledger A in the blockchain node A, and generates a key for each registered vehicle through the wallet A in the blockchain, and stores the key in the cloud platform A;

[0443] The cloud platform B of the OEM B receives the registration application information of vehicles B1 to Bj, and sends the registration application information to the pre-built power supply vehicle ledger B in the blockchain node B. It also generates a key for each registered vehicle through the wallet B in the blockchain and stores the key in the cloud platform B.

[0444] Similarly, the cloud platform X of the OEM X receives the registration application information of vehicles X1 to Xk, and sends the registration application information to the pre-built power supply vehicle ledger X in the blockchain node X. It also generates a key for each registered vehicle through the wallet X in the blockchain and stores the key in the cloud platform X.

[0445] The power supply vehicle ledgers A to X generated by cloud platform A, cloud platform B and cloud platform X are distributed on different blockchain nodes, constituting all the data of the candidate power supply vehicle ledger;

[0446] Vehicles A1 to Ai on cloud platform A can serve as power supply vehicles, and vehicle A produced by OEM A on cloud platform A can serve as power receiving vehicles.

[0447] Vehicles B1 to Bj on cloud platform B can be used as power supply vehicles, and vehicles B produced by the OEM B of cloud platform B can be used as power receiving vehicles.

[0448] Vehicles X1 to Xk on cloud platform X can serve as power supply vehicles, and vehicles X produced by OEM X on cloud platform X can serve as power receiving vehicles.

[0449] It should be noted that this embodiment uses cloud platform A, cloud platform B, ... cloud platform X as examples to illustrate the preset method of candidate power supply vehicle ledger in the blockchain. In other embodiments, the number of cloud platforms of the OEMs participating in mutual charging can be 1.

[0450] By collecting vehicle registration application information and real-time vehicle information from different OEMs' cloud platforms, and managing the power supply vehicle ledgers on each cloud platform, and achieving data sharing through blockchain, each cloud platform can access the power supply vehicle ledgers uploaded by other cloud platforms, realizing mutual charging between different manufacturers. However, by communicating with the vehicles of the OEMs themselves through each cloud platform and managing the candidate power supply vehicle ledgers on their respective platforms, the system complies with security protocols and ensures the confidentiality of vehicle information between different OEMs during the mutual charging process.

[0451] In another embodiment provided by the present invention, the process of the vehicle completing the power supply vehicle registration specifically includes:

[0452] The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply.

[0453] The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

[0454] In a specific implementation of this embodiment, the process of any vehicle completing the power supply vehicle registration specifically includes:

[0455] The vehicle sends registration application information to the cloud platform of the OEM that owns the vehicle. The registration application information includes the vehicle number, the threshold power level and the threshold distance for power supply set by the vehicle. The vehicle is allowed to become a power supply vehicle only if the real-time power level of the vehicle is not lower than the threshold power level and the real-time distance between the vehicle and the power receiving vehicle is not greater than the threshold distance. The threshold power level and threshold distance are conditions set by the vehicle itself when registering to ensure the power supply of the power supply vehicle. When the above conditions are not met, the vehicle cannot be used as a power supply vehicle, thus realizing a more user-friendly allocation of power supply vehicles.

[0456] The vehicle number can be given by the cloud platform according to the registration order of the power supply vehicles in the candidate power supply vehicle ledger of the blockchain. The vehicle number is unique among all cloud platforms participating in mutual charging. It serves as the vehicle's identity code in the mutual charging process. Communication between cloud platforms is used to identify the vehicle. The vehicle number contains the OEM information to which the vehicle belongs.

[0457] The vehicle's cloud platform receives the registration information, and after approval, uses a blockchain wallet to generate a key for the vehicle. The key and the vehicle's vehicle number are then stored together and the registration application information is uploaded to the pre-established power supply vehicle ledger on the vehicle's cloud platform to complete the registration.

[0458] The key serves as an identification code for communicating with the vehicle and is associated with the vehicle's serial number as a public key. The key and key pair are stored in the vehicle's cloud platform. Only the cloud platform can communicate with the vehicle through the key, ensuring the privacy of the vehicle's identity and the confidentiality of the communication.

[0459] In another embodiment provided by the present invention, the real-time update process of the vehicle information specifically includes:

[0460] Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

[0461] In this specific implementation, the vehicle information in the power supply vehicle sub-ledger of each cloud platform is updated in real time. The update process is as follows:

[0462] Each cloud platform receives real-time vehicle information uploaded by the registered vehicles of the OEM and updates the vehicle information of the vehicle to the power supply vehicle sub-ledger of this cloud platform, overwriting the outdated vehicle information of this vehicle.

[0463] Each cloud platform synchronizes and updates the real-time information of the vehicles on that cloud platform, thereby enabling real-time updates of vehicle information in all vehicles in the candidate power supply vehicle ledger.

[0464] The vehicle information includes the vehicle number, the vehicle's real-time remaining battery power, and the vehicle's real-time location information.

[0465] By obtaining real-time vehicle information such as remaining battery power and location, and by identifying the vehicle corresponding to the vehicle information through a unique vehicle number, vehicle information can be easily managed and differentiated between different vehicles.

[0466] In another embodiment provided by the present invention, the charging requirement of the charging request includes the required power of the receiving vehicle and the receiving location.

[0467] The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes:

[0468] Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes.

[0469] Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles;

[0470] One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

[0471] In the specific implementation of this embodiment, please refer to Figure 3 This is a schematic diagram of the communication process of a vehicle mutual charging method provided in an embodiment of the present invention; the diagram uses cloud platform A of OEM A and cloud platform B of OEM B as examples to illustrate the communication process.

[0472] Cloud platform A establishes a power supply vehicle ledger for OEM A in the blockchain.

[0473] When the power receiving vehicle A0 has insufficient power, it sends a charging request to the cloud platform A through base station 1. The charging request includes the power demand of the power receiving vehicle and the current power receiving location of the power receiving vehicle.

[0474] Based on the received charging request, cloud platform A retrieves information on all vehicles in the candidate power supply vehicle ledger from the blockchain through blockchain protocol verification such as KYC authentication and / or communication protocols.

[0475] Cloud platform A filters out a list of candidate power supply vehicles that meet the charging requirements from all the vehicles it has acquired, based on the charging request sent by the power receiving vehicle A0.

[0476] Based on the obtained list of candidate power supply vehicles, one vehicle is selected as the power supply vehicle.

[0477] Candidate vehicles are obtained by screening vehicles that meet charging needs as candidate power supply vehicles. Power supply vehicles are then confirmed from the candidate vehicles to complete the allocation of power supply vehicles. During the allocation process, each vehicle communicates only with the cloud platform of its respective OEM to ensure vehicle security. To avoid information leakage, the cloud platform and blockchain transmit information through a communication protocol, making the communication process more secure and stable.

[0478] In another embodiment of the present invention, before determining one of the candidate power supply vehicles as the power supply vehicle based on the obtained list of candidate power supply vehicles, the method further includes:

[0479] The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number.

[0480] Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0481] In the specific implementation of this embodiment, the candidate power supply vehicle list includes vehicle A from OEM A and vehicles B1 and B2 from OEM B. Therefore, vehicle A, vehicle B1, and vehicle B2 are all candidate vehicles.

[0482] Cloud platform A sends the vehicle numbers of vehicle B1 and vehicle B2 from the candidate power supply vehicle list to cloud platform B;

[0483] Cloud platform A obtains the key of vehicle A1, establishes communication with vehicle A1 through the key, and sends a request for help to vehicle A1;

[0484] Cloud platform B obtains the keys of vehicle B1 and vehicle B2 based on the vehicle number of vehicle B1 and vehicle B2, establishes communication with vehicle B1 and vehicle B2 through the keys, and sends a group request for help to vehicle B1 and vehicle B2.

[0485] The requested assistance information sent includes vehicle information of the receiving vehicle A0, including its location and required power supply.

[0486] After receiving a request for assistance, vehicles A, B1, and B2 can choose whether to confirm assistance. If they confirm assistance, they will send a confirmation message to the corresponding cloud platform. If they decide not to provide assistance, they will either not send a confirmation message or send a no-assistance message to the corresponding cloud platform.

[0487] Suppose that vehicle A and vehicle B1 send confirmation of rescue information to their respective cloud platforms, and cloud platform B sends confirmation of rescue information for vehicle B1 to cloud platform A.

[0488] Vehicle B2 did not provide confirmation of assistance, so vehicle B2 is removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

[0489] Candidate vehicles are obtained by screening the candidate power supply vehicle register, and communication with the candidate vehicles through the candidate vehicle's cloud platform confirms whether the candidate vehicle has confirmed the assistance of the receiving vehicle. Among the candidate vehicles that have confirmed assistance, the candidate vehicle closest to the receiving vehicle is selected as the power supply vehicle, thus completing the allocation of power supply vehicles. The willingness of the candidate vehicles to provide assistance is confirmed by their feedback on whether they have confirmed assistance, thereby improving the satisfaction of the candidate vehicle allocation process.

[0490] In another embodiment of the present invention, the step of filtering out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles specifically includes:

[0491] Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM;

[0492] The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power.

[0493] The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0494] In the specific implementation of this embodiment, all vehicles from the same OEM A as the power receiving vehicle A0 are preferentially selected as vehicles from the same OEM. In this embodiment, vehicles from the same OEM include vehicle A.

[0495] The cloud platform filters the vehicles from the same manufacturer and only those that meet two conditions are considered as candidate vehicles.

[0496] Condition 1: The real-time remaining battery power in the vehicle information is greater than the threshold battery power set in the vehicle registration application information, and also greater than the required battery power.

[0497] Condition 2: The distance between the real-time location information in the vehicle information and the power receiving location is not greater than the threshold distance set in the vehicle registration application information;

[0498] Select all vehicles from the same factory that simultaneously meet both Condition 1 and Condition 2 as a candidate power supply vehicle list.

[0499] Priority is given to screening vehicles in the candidate power supply vehicle register, using vehicles from the same OEM as the power supply vehicles. This avoids the need for additional power adapters when charging vehicles from different manufacturers, improving power charging efficiency and safety. The power demand and power receiving location of the receiving vehicle are also assessed. Only vehicles whose power receiving needs meet the conditions set by the vehicle itself will be selected as candidate power supply vehicles. If the above conditions are not met, the vehicle cannot be selected as a candidate vehicle, thus achieving a more user-friendly allocation of power supply vehicles.

[0500] In another embodiment of the present invention, the step of filtering out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles specifically includes:

[0501] Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list;

[0502] The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

[0503] In a specific implementation of this embodiment, as another way to screen the list of power supply vehicles, when the number of candidate vehicles in the candidate power supply vehicle list obtained by screening vehicles from the same OEM as the power receiving vehicle A0 is too small, it is impossible to determine the power supply vehicle.

[0504] Using an alternative approach, the cloud platform filters all the acquired vehicles, and only those that meet two conditions will be considered as candidate vehicles.

[0505] Condition 1: The real-time remaining battery power in the vehicle information is greater than the threshold battery power set in the vehicle registration application information, and also greater than the required battery power.

[0506] Condition 2: The distance between the real-time location information in the vehicle information and the power receiving location is not greater than the threshold distance set in the vehicle registration application information;

[0507] Select all vehicles in the candidate power supply vehicle register that simultaneously meet both condition one and condition two as a candidate power supply vehicle list.

[0508] By screening vehicles in the candidate power supply vehicle register, judging the power demand and power receiving location of the receiving vehicles, a vehicle will be selected as a candidate power supply vehicle only if its power receiving demand meets the conditions set by the vehicle itself. If the above conditions are not met, the vehicle cannot be selected as a candidate vehicle, thus achieving a more humanized allocation of power supply vehicles.

[0509] In another embodiment of the present invention, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0510] The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location.

[0511] The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

[0512] In the specific implementation of this embodiment, the list of candidate power supply vehicles obtained includes: vehicle A, vehicle B1, and vehicle B2;

[0513] It should be noted that, in this embodiment, the specific method of determining the power supply vehicle is illustrated by using a candidate power supply vehicle list obtained by filtering from all vehicles in the blockchain as an example.

[0514] Calculate the real-time location information of vehicles A, B1, and B2 and the power supply distance to the power receiving location of the powered vehicle A0, respectively.

[0515] Based on the power supply distances of vehicles A, B1, and B2, the vehicle with the shortest distance is selected as the power supply vehicle, and its vehicle number is obtained.

[0516] Candidate vehicles are obtained by screening the candidate power supply vehicle register. Among the candidate vehicles, the one closest to the power receiving vehicle is selected as the power supply vehicle, thus completing the allocation of power supply vehicles. During the allocation process, each vehicle only communicates with the cloud platform of its respective OEM to ensure the safety of the vehicle.

[0517] In another embodiment of the present invention, determining one of the candidate power supply vehicles from the obtained candidate power supply vehicle list specifically includes:

[0518] The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated.

[0519] The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

[0520] In this specific implementation, cloud platform A calculates the real-time location information of vehicle A and the destination distance A of vehicle A; calculates the real-time location information of vehicle B1 and the destination distance B1 of vehicle A; and calculates the real-time location information of vehicle B2 and the destination distance B2 of vehicle A.

[0521] Based on the destination distances A, B1, and B2 of vehicles A, B1, and B2, select the vehicle with the shortest destination distance as the power supply vehicle and obtain its vehicle number.

[0522] Selecting the vehicle closest to the destination from the candidate vehicles as the power supply vehicle can avoid situations where the destination is too far away and the vehicle does not have enough power to reach the destination after power is supplied.

[0523] In another embodiment of the present invention, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0524] The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list.

[0525] The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

[0526] In the specific implementation of this embodiment, the list of candidate power supply vehicles obtained includes: vehicle A, vehicle B1, and vehicle B2;

[0527] It should be noted that, in this embodiment, the specific method for determining power supply vehicles is illustrated by using a candidate power supply vehicle list obtained by filtering from all vehicles in the blockchain.

[0528] The real-time remaining power of vehicles A, B1, and B2 can be obtained from the vehicle information in the candidate power supply vehicle ledger.

[0529] Based on the real-time remaining battery power of vehicles A, B1, and B2, the vehicle with the highest real-time remaining battery power is selected as the power supply vehicle, and its vehicle number is obtained.

[0530] Candidate vehicles are obtained by screening the candidate power supply vehicle register. Among the candidate vehicles, the one with the highest real-time remaining power is selected as the power supply vehicle, thus completing the allocation of power supply vehicles.

[0531] In another embodiment of the present invention, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0532] The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location.

[0533] The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle.

[0534] The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle;

[0535] The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

[0536] In the specific implementation of this embodiment, the list of candidate power supply vehicles obtained includes: vehicle A, vehicle B1, and vehicle B2;

[0537] It should be noted that, in this embodiment, the specific method of determining the power supply vehicle is illustrated by using a candidate power supply vehicle list obtained by filtering from all vehicles in the blockchain as an example.

[0538] Obtain the real-time location information and destination location from the vehicle information of vehicle A, vehicle B1, and vehicle B2;

[0539] Navigation routes from the real-time location information of vehicles A, B1, and B2 to their respective destinations are automatically generated using navigation software or city maps.

[0540] Obtain the route distances for different levels of congestion in the navigation routes of each candidate vehicle, and calculate the congestion score for each candidate vehicle based on the route distances for each level of congestion in the navigation routes of each candidate vehicle.

[0541] When the distance of the route with a congestion level of vehicle A is 1.2km, the distance of the route with a very congestion level of vehicle A is 0.8km, the distance of the route with a severe congestion level of vehicle A is 0.5km, and the distance of the route with a deadlock level of vehicle A is 0km;

[0542] When the distance of the route with a congestion level of vehicle B1 is 1.5km, the distance of the route with a very congestion level of vehicle B1 is 1km, the distance of the route with a severe congestion level of vehicle B1 is 0km, and the distance of the route with a deadlock level of vehicle B1 is 0km.

[0543] When the distance of the route in the navigation route of vehicle B2 is 0.5km for the congested route, 0.1km for the very congested route, 0km for the severely congested route, and 0.5km for the deadlock route;

[0544] When calculating the congestion score, it is necessary to preset the score weights for different levels of congestion. The first preset value is 1 / km, the second preset value is 3 / km, the third preset value is 5 / km, and the fourth preset value is 10 / km.

[0545] The congestion score for vehicle A is calculated as follows: 1.2km*1 / km + 0.8km*3 / km + 0.5km*5 / km = 6.1;

[0546] The congestion score for vehicle B1 is calculated as follows: 1.5km * 1 / km + 1km * 3 / km = 4.5;

[0547] The congestion score for vehicle B2 is calculated as follows: 0.5km*1 / km + 0.1km*3 / km + 0.5km*10 / km = 5.8;

[0548] When the vehicle with the lowest congestion score is selected as the power supply vehicle, vehicle B1 is determined to be the power supply vehicle, and the vehicle number of vehicle B1 is obtained.

[0549] When the vehicle with the highest congestion score is selected as the power supply vehicle, vehicle A can be identified as the power supply vehicle, and its vehicle number can be obtained.

[0550] It should be noted that, in this embodiment, the congestion score can also be obtained from the estimated travel time of the navigation route;

[0551] Candidate vehicles are obtained by screening the candidate power supply vehicle register. Among the candidate vehicles, the one with the highest or lowest congestion score is selected as the power supply vehicle. This means that the vehicle with the highest road congestion can be selected to supply power to the receiving vehicle, or the vehicle with the lowest road congestion can be selected to supply power to the receiving vehicle, thus completing the allocation of power supply vehicles. During the allocation process, each vehicle only communicates with the cloud platform of its respective OEM to ensure the safety of the vehicle.

[0552] In another embodiment of the present invention, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0553] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0554] Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2;

[0555] The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle.

[0556] Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle.

[0557] The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

[0558] In the specific implementation of this embodiment, the list of candidate power supply vehicles obtained includes: vehicle A, vehicle B1, and vehicle B2;

[0559] It should be noted that, in this embodiment, the specific method of determining the power supply vehicle is illustrated by using a candidate power supply vehicle list obtained by filtering from all vehicles in the blockchain as an example.

[0560] Based on the vehicle information of each candidate vehicle, the vehicle number, real-time remaining battery power, real-time location information, and destination location of vehicle A, vehicle B1, and vehicle B2 are obtained respectively.

[0561] Based on the real-time location information and destination location of vehicle A, the first destination distance of vehicle A is calculated to be 3km. Based on the real-time location information of vehicle A and the power receiving location of the power receiving vehicle, the first power supply distance of vehicle A is calculated to be 3km. The first remaining power of vehicle A is obtained as 10kWh. Based on the real-time location information and destination location of vehicle A, the navigation route of vehicle A is obtained. The first congestion score of vehicle A is calculated as 6.5. The first OEM score of vehicle A is calculated. Since vehicle A and the power receiving vehicle A0 belong to the same OEM, the fifth score of vehicle A is 1.

[0562] Based on the real-time location information and destination location of vehicle B1, the second destination distance of vehicle B1 is calculated to be 5km. Based on the real-time location information of vehicle B1 and the power receiving location of the power receiving vehicle, the second power supply distance of vehicle B1 is calculated to be 6km. The second remaining power of vehicle B1 is obtained as 8kWh. Based on the real-time location information and destination location of vehicle B1, the navigation route of vehicle B1 is obtained. The second congestion score of vehicle B1 is calculated as 3.5. The second OEM score of vehicle B1 is 0. Since vehicle B1 and power receiving vehicle A0 do not belong to the same OEM, the fifth score of vehicle B1 is 0.

[0563] Based on the real-time location information and destination location of vehicle B2, the third destination distance of vehicle B2 is calculated to be 3.5km. Based on the real-time location information of vehicle B2 and the power receiving location of the power receiving vehicle, the third power supply distance of vehicle B2 is calculated to be 4km. The third remaining power of vehicle B2 is obtained as 7kWh. Based on the real-time location information and destination location of vehicle B2, the navigation route of vehicle B2 is obtained, and the third congestion score of vehicle B2 is calculated as 8. The third OEM score of vehicle B2 is given. Since vehicle B2 and power receiving vehicle A0 do not belong to the same OEM, the fifth score of vehicle B2 is 0.

[0564] It should be noted that in this embodiment, the fifth score value of candidate vehicles belonging to the same OEM is 1, and the fifth score value of candidate vehicles not belonging to the same OEM is 0.

[0565] The destination distances of all vehicles are normalized. The first destination distance of vehicle A is 3km, the second destination distance of vehicle B1 is 5km, and the third destination distance of vehicle B2 is 3.5km. After normalization, the first score of vehicle A is 3km / 5km = 0.6, the first score of vehicle B1 is 5km / 5km = 1, and the first score of vehicle B2 is 3.5km / 5km = 0.7.

[0566] The power supply distances of all vehicles are normalized. The first power supply distance of vehicle A is 3km, the second power supply distance of vehicle B1 is 6km, and the third power supply distance of vehicle B2 is 4km. After normalization, the second score of vehicle A is 3km / 6km = 0.5, the second score of vehicle B1 is 6km / 6km = 1, and the second score of vehicle B2 is 4km / 6km = 0.67.

[0567] The remaining battery power of all vehicles is normalized. The first remaining battery power of vehicle A is 10 kWh, the second remaining battery power of vehicle B1 is 8 kWh, and the third remaining battery power of vehicle B2 is 7 kWh. After normalization, the third score of vehicle A is 10 kWh / 10 kWh = 1, the third score of vehicle B1 is 8 kWh / 10 kWh = 0.8, and the third score of vehicle B2 is 7 kWh / 10 kWh = 0.7.

[0568] After normalizing the congestion scores of all vehicles, the first congestion score of vehicle A is 6.5, the second congestion score of vehicle B1 is 3.5, and the third congestion score of vehicle B2 is 8. After normalization, the fourth congestion score of vehicle A is 3.5 / 8 = 0.44, the fourth congestion score of vehicle B1 is 6.5 / 8 = 0.81, and the fourth congestion score of vehicle B2 is 8 / 8 = 1.

[0569] Based on the weight of each rating value, the first rating value has a negative weight, set to -1; the second rating value has a negative weight, set to -1; the third rating value has a positive weight, set to 1; the fourth rating value has a negative weight, set to -1; and the fifth rating value has a positive weight, set to 1.

[0570] For each candidate vehicle, select several identical score values ​​from different OEMs and sum them using a weighted average.

[0571] For example, selecting the first and fifth score values ​​for each candidate vehicle;

[0572] After calculation: the ranking value of vehicle A is 0.6*(-1)+1*1=0.4, the ranking value of vehicle B1 is 1*(-1)+1*0=-1, and the ranking value of vehicle A is 0.67*(-1)+1*0=-0.67.

[0573] Therefore, it can be seen that vehicle A has the largest ranking value, and A is determined to be the power supply vehicle;

[0574] It should be noted that in this embodiment, the calculation process of the ranking value is illustrated using the first ranking value and the fifth ranking value as examples. In other embodiments, the ranking value can be calculated using other rating values, and the number of rating values ​​that can be used is not limited to 2.

[0575] By calculating different scores for vehicles, evaluating different states of candidate vehicles, and selecting the vehicle with the best state through weighted selection, the accuracy of power supply vehicle allocation is improved.

[0576] In another embodiment of the present invention, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle specifically includes:

[0577] A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle.

[0578] The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

[0579] In this specific implementation, a scoring database for each candidate vehicle is calculated based on the vehicle information of each candidate vehicle and the charging requirements.

[0580] Each candidate vehicle's score from its scoring database is sent to the receiving vehicle via the receiving vehicle's key. The user on the receiving vehicle then selects the power supply vehicle, receives the vehicle number from the receiving vehicle, and confirms the power supply vehicle.

[0581] By providing the receiving vehicle with the ratings from the rating database of each candidate vehicle, the user of the receiving vehicle decides which vehicle to supply power. This user-friendly design of mutual charging improves the user experience of mutual charging.

[0582] In another embodiment of the present invention, the step of feeding back the power supply vehicle information to the power receiving vehicle and synchronizing the power receiving vehicle information to the power supply vehicle specifically includes:

[0583] When the power supply vehicle is not a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the vehicle number of the power supply vehicle is uploaded to the candidate power supply vehicle ledger, so that the cloud platform of the power supply vehicle can obtain the vehicle number of the power supply vehicle from the candidate power supply vehicle ledger, and send the power receiving vehicle information to the power supply vehicle according to the key of the power supply vehicle.

[0584] When the power supply vehicle is a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the power receiving vehicle information is sent to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet up and complete mutual charging.

[0585] In the specific implementation of this embodiment, Figure 2 For example:

[0586] If the nearest power supply vehicle confirmed by the power receiving vehicle A0 is vehicle A, which is also from OEM A, the cloud platform A will use the key of the power receiving vehicle A0 to send the power supply vehicle information of vehicle A to the power receiving vehicle A0, and use the key of vehicle A to send the power receiving vehicle information of the power receiving vehicle A0 to vehicle A.

[0587] If the nearest power supply vehicle confirmed by the receiving vehicle A0 is vehicle B2 of OEM B, cloud platform A sends the power supply vehicle information of vehicle A to the receiving vehicle A0 using the key of the receiving vehicle A0; and sends the vehicle number of vehicle B2 to the candidate power supply vehicle ledger so that the candidate power supply vehicle ledger is updated synchronously. Cloud platform B obtains the vehicle number of vehicle B2 from the updated candidate power supply vehicle ledger, and matches the obtained number with the key of vehicle B2. Cloud platform B then sends the receiving vehicle information of the receiving vehicle A0 to vehicle B2 using the key of vehicle B2.

[0588] By identifying whether the receiving and supplying vehicles belong to the same OEM, when the supplying vehicle does not belong to the same OEM, a message is sent through the supplying vehicle's cloud platform to complete the allocation of supplying vehicles during the mutual charging process.

[0589] In another embodiment provided by the present invention, the power supply vehicle information includes the real-time location information, real-time remaining power information, and contact information of the power supply vehicle;

[0590] The information about the receiving vehicle includes its power receiving location, real-time remaining power information, and contact information.

[0591] In this specific implementation, the power supply vehicle's real-time location information, real-time remaining power information, and contact information are sent to the power receiving vehicle, and the power receiving vehicle's power receiving location, real-time remaining power information, and contact information are sent to the power supply vehicle, so that the power receiving vehicle and the power supply vehicle can approach each other until they meet. Then, the power supply vehicle supplies power to the power receiving vehicle, completing the mutual charging process.

[0592] It should be noted that the process of the receiving vehicle and the supplying vehicle meeting up is as follows: the supplying vehicle goes to the receiving vehicle's receiving location, or the receiving vehicle and the supplying vehicle contact each other, agree on the meeting point, and complete the mutual charging after meeting up.

[0593] In another embodiment provided by the present invention, the method further includes:

[0594] When a power supply cancellation request is received from a registered vehicle, the registration request information and vehicle information of the registered vehicle mentioned in the power supply vehicle ledger of this cloud platform are deleted.

[0595] In the specific implementation of this embodiment, vehicles that have completed the registration of the power supply vehicle can send a power supply cancellation application to the cloud platform;

[0596] Upon receiving the power supply cancellation request, the cloud platform deletes the registration application information and vehicle information of the vehicle that sent the power supply cancellation request from the power supply vehicle sub-ledger, thus completing the cancellation of the power supply vehicle registration.

[0597] join Figure 4 This is a schematic diagram of a car mutual charging device provided in an embodiment of the present invention. The device includes:

[0598] The charging request response module is used to respond to a charging request sent by a powered vehicle and determine a power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register.

[0599] The signal feedback module is used to feed back the power supply vehicle information to the power receiving vehicle and synchronize the power receiving vehicle information to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging.

[0600] It should be noted that the vehicle mutual charging device provided in this embodiment of the invention is used to execute all the process steps of the vehicle mutual charging method in the above embodiment. The working principle and beneficial effects of the two are one-to-one, so they will not be described again.

[0601] Another embodiment of the present invention provides a method for mutual charging of automobiles, the method comprising:

[0602] The cloud platform receiving the power supply vehicle determines the power supply vehicle information from all vehicles in the preset candidate power supply vehicle ledger.

[0603] The power receiving vehicle information is sent to the power supply vehicle so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging.

[0604] In this specific implementation, it is executed by the cloud platform of the power supply vehicle.

[0605] When the remaining battery power of the receiving vehicle is lower than the set charging threshold, a charging request is automatically sent to the cloud platform of the vehicle's OEM. When charging is needed, the vehicle owner can independently control the sending of a charging request to the cloud platform.

[0606] The cloud platform of the receiving vehicle receives the charging request sent by the receiving vehicle, obtains the power supply vehicle ledger containing all power supply vehicles, and determines the power supply vehicle that meets the charging needs of the receiving vehicle from all vehicles in the power supply vehicle ledger.

[0607] The cloud platform for power supply vehicles obtains vehicle information of power supply vehicles determined from all vehicles in the preset candidate power supply vehicle ledger through the candidate vehicle ledger on the blockchain.

[0608] The cloud platform of the power supply vehicle sends the power receiving vehicle information to the power supply vehicle, notifying the power supply vehicle that the mutual charging allocation is complete, and providing feedback on the power receiving vehicle that needs assistance, so that the power supply vehicle and the power receiving vehicle can meet and complete the mutual charging.

[0609] This embodiment uses an anonymous data sharing ledger established by different nodes of the blockchain to store vehicle information from various OEMs. Data sharing is achieved through the blockchain, while the anonymity protects the data security of various cloud platforms. The blockchain also decentralizes the data of various platforms in the process of mutual charging of vehicles. Data from different OEMs' cloud platforms is shared through the blockchain, enabling mutual charging of vehicles from different OEMs' clouds.

[0610] By receiving charging requests from the receiving vehicles, responding to the charging requests, confirming the power supply vehicles from the preset power supply vehicle register, completing the allocation of power supply vehicles for mutual charging, synchronizing the information of the receiving vehicles to the power supply vehicles, and sending the information of the power supply vehicles to the receiving vehicles, the power supply vehicles and the receiving vehicles meet and complete the mutual charging.

[0611] It should be noted that the mutual charging function performed by the vehicle mutual charging method provided in this embodiment of the invention is similar to all the process steps of the vehicle mutual charging method in the above embodiment. The working principle and beneficial effects of the two correspond one-to-one, so they will not be described again.

[0612] Another embodiment of the present invention provides a car mutual charging device, the device comprising:

[0613] The receiving module is used to receive vehicle information of the power supply vehicle determined by the cloud platform of the power receiving vehicle from all vehicles in the preset candidate power supply vehicle ledger.

[0614] The transmitting module is used to send information about the receiving vehicle to the power supply vehicle, so that the power supply vehicle and the receiving vehicle can meet and complete mutual charging.

[0615] It should be noted that the mutual charging function performed by the car mutual charging device provided in this embodiment of the invention is similar to all the process steps of the car mutual charging method in the above embodiment. The working principle and beneficial effects of the two correspond one-to-one, so they will not be described again.

[0616] Another embodiment of the present invention provides a method for mutual charging of automobiles, the method comprising:

[0617] In response to a user-inputted charging command, a charging request is sent to the cloud platform of the OEM, so that the cloud platform can determine a power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register.

[0618] Based on the power supply vehicle information fed back by the cloud platform, the system meets with the power supply vehicle and completes mutual charging.

[0619] In this specific implementation, the method is performed by the energized vehicle.

[0620] When the remaining battery power of the receiving vehicle is lower than the set charging threshold, the vehicle owner can choose to send a charging request to the cloud platform of the receiving vehicle independently. This process can also be automatically controlled by the vehicle.

[0621] The cloud platform receives the charging request sent by the receiving vehicle, obtains a power supply vehicle ledger containing all power supply vehicles, and determines the power supply vehicle that meets the charging needs of the receiving vehicle from all vehicles in the power supply vehicle ledger.

[0622] Feedback of power supply vehicle information to the power receiving vehicle, notification to the power receiving vehicle that the power supply vehicles for mutual charging have been allocated, and feedback of information on the allocated power supply vehicles.

[0623] Synchronize the information of the receiving vehicles to the supplying vehicles, notify the supplying vehicles that the mutual charging distribution is complete, and provide feedback on the information of the receiving vehicles that need assistance.

[0624] This embodiment uses an anonymous data sharing ledger established by different nodes of the blockchain to store vehicle information from various OEMs. Data sharing is achieved through the blockchain, while the anonymity protects the data security of various cloud platforms. The blockchain also decentralizes the data of various platforms in the process of mutual charging of vehicles. Data from different OEMs' cloud platforms is shared through the blockchain, enabling mutual charging of vehicles from different OEMs' clouds.

[0625] By sending a charging request to the cloud platform, the cloud platform responds to the charging request, confirms the power supply vehicle from the preset power supply vehicle ledger, completes the allocation of power supply vehicles for mutual charging, synchronizes the power receiving vehicle information to the power supply vehicle, and sends the power supply vehicle information to the power receiving vehicle, so that the power supply vehicle and the power receiving vehicle meet and complete the mutual charging.

[0626] It should be noted that the mutual charging function performed by the vehicle mutual charging method provided in this embodiment of the invention is similar to all the process steps of the vehicle mutual charging method in the above embodiment. The working principle and beneficial effects of the two correspond one-to-one, so they will not be described again.

[0627] This invention provides a vehicle mutual charging device, the device comprising:

[0628] The charging request module is used to respond to the charging command input by the user and send a charging request to the cloud platform of the OEM so that the cloud platform can determine the charging vehicle that meets the charging requirements of the charging request from all vehicles in the preset candidate power supply vehicle ledger.

[0629] The mutual charging module is used to connect with the power supply vehicle based on the power supply vehicle information fed back by the cloud platform and complete the mutual charging.

[0630] It should be noted that the mutual charging function performed by the car mutual charging device provided in this embodiment of the invention is similar to all the process steps of the car mutual charging method in the above embodiment. The working principle and beneficial effects of the two correspond one-to-one, so they will not be described again.

[0631] Another embodiment of the present invention provides a method for mutual charging of automobiles, the method comprising:

[0632] The cloud platform receives power-receiving vehicle information through communication established by the vehicle number of the vehicle. The vehicle number is the vehicle number of the power supply vehicle determined by the cloud platform from all vehicles in the preset candidate power supply vehicle ledger.

[0633] After meeting with the receiving vehicle based on the information of the receiving vehicle, mutual charging is completed.

[0634] In this specific implementation, the method is performed by the power supply vehicle;

[0635] When the remaining battery power of the receiving vehicle is lower than the set charging threshold, a charging request is automatically sent to the cloud platform of the vehicle's OEM. When charging is needed, the vehicle owner can independently control the sending of a charging request to the cloud platform.

[0636] The cloud platform of the receiving vehicle receives the charging request sent by the receiving vehicle, obtains the power supply vehicle ledger containing all power supply vehicles, and determines the power supply vehicle that meets the charging needs of the receiving vehicle from all vehicles in the power supply vehicle ledger.

[0637] The receiving vehicle will provide feedback on the power supply vehicle information to the receiving vehicle, notify the receiving vehicle that the power supply vehicles for mutual charging have been allocated, and provide feedback on the allocated power supply vehicles.

[0638] The power supply vehicle synchronizes the power receiving vehicle information to the power supply vehicle through the cloud platform, notifies the power supply vehicle that the mutual charging allocation is complete, and provides feedback on the power receiving vehicle that needs assistance.

[0639] The power supply vehicle receives information from the power receiving vehicle, responds to the charging request, and meets up with the power receiving vehicle to complete mutual charging.

[0640] It should be noted that the mutual charging function performed by the vehicle mutual charging method provided in this embodiment of the invention is similar to all the process steps of the vehicle mutual charging method in the above embodiment. The working principle and beneficial effects of the two correspond one-to-one, so they will not be described again.

[0641] Another embodiment of the present invention provides a car mutual charging device, the device comprising:

[0642] The powered vehicle information receiving module is used to receive powered vehicle information sent by the cloud platform through the vehicle number of the vehicle. The vehicle number is the vehicle number of the power supply vehicle determined by the cloud platform of the powered vehicle from all vehicles in the preset candidate power supply vehicle ledger.

[0643] The mutual charging module is used to complete mutual charging after meeting with the receiving vehicle based on the receiving vehicle information.

[0644] It should be noted that the mutual charging function performed by the car mutual charging device provided in this embodiment of the invention is similar to all the process steps of the car mutual charging method in the above embodiment. The working principle and beneficial effects of the two correspond one-to-one, so they will not be described again.

[0645] Another embodiment of the present invention provides a car mutual charging system, the system comprising: at least one OEM cloud platform, and all OEM cloud platforms being connected to a blockchain;

[0646] The first cloud platform in the system is used to execute a vehicle mutual charging method as described in any of the above embodiments.

[0647] In this specific implementation, the system includes at least one OEM cloud platform, and all OEM cloud platforms are connected to the blockchain; information is transmitted through the OEM.

[0648] A car mutual charging system is formed by connecting at least one airport cloud platform. When a car needs to charge, it can achieve mutual charging through the OEM cloud platform and the connected blockchain.

[0649] Any cloud platform in the system serves as the first cloud platform, which is used to execute a vehicle mutual charging method executed by the cloud platform of the receiving vehicle in the above embodiments or a vehicle mutual charging method executed by the cloud platform of the supplying vehicle in the above embodiments.

[0650] It should be noted that the first cloud platform in the vehicle mutual charging system provided in the embodiments of the present invention is used to execute all the process steps of the vehicle mutual charging method in the above embodiments. The working principles and beneficial effects of the two are one-to-one, so they will not be described again.

[0651] In another embodiment of the present invention, each OEM cloud platform of the system is used to obtain vehicle registration information, wherein the vehicle includes at least one of any vehicle of the OEM, a power supply vehicle, and a power receiving vehicle.

[0652] In the specific implementation of this embodiment, each OEM's cloud platform obtains the vehicle registration information, including any vehicle of that OEM, and may also include power supply vehicles and / or charging vehicles.

[0653] Any OEM's cloud platform can serve as a cloud platform for power supply vehicles, a cloud platform for power receiving vehicles, or simply collect information on vehicles registered by that OEM.

[0654] In another embodiment of the present invention, a vehicle mutual charging system is provided, the system comprising: a power supply vehicle cloud platform and a power receiving vehicle cloud platform, the power supply vehicle cloud platform and the power receiving vehicle cloud platform being connected via blockchain.

[0655] In this specific implementation, the system includes a power supply vehicle cloud platform, a power receiving vehicle cloud platform, and other cloud platforms that collect registration information. The various cloud platforms communicate with each other through blockchain.

[0656] The power-receiving vehicle cloud platform is configured as follows:

[0657] In response to a charging request sent by a powered vehicle, a power supply vehicle that meets the charging requirements of the charging request is determined from all vehicles in a preset candidate power supply vehicle register.

[0658] The power supply vehicle information is fed back to the power receiving vehicle, and the power receiving vehicle information is synchronized to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging.

[0659] When the cloud platform for receiving vehicles allocates power supply vehicles, it executes the following:

[0660] In response to a charging request sent by a powered vehicle, a power supply vehicle that meets the charging requirements of the charging request is determined from all vehicles in a preset candidate power supply vehicle register.

[0661] The power supply vehicle information is fed back to the power receiving vehicle, and the power receiving vehicle information is synchronized to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging.

[0662] It should be noted that the cloud platform for receiving vehicles in the vehicle mutual charging system provided in this embodiment of the invention is used to execute all the process steps of the vehicle mutual charging method in the above embodiment. The working principles and beneficial effects of the two are one-to-one, so they will not be described again.

[0663] See Figure 5This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present invention. The terminal device provided in this embodiment includes a processor 51, a memory 52, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, it implements the vehicle mutual charging method described in any of the above embodiments.

[0664] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0665] Another embodiment of the present invention provides a vehicle mutual charging system, including a cloud platform, a power supply vehicle, and a power receiving vehicle. The cloud platform is used to execute the vehicle mutual charging method as described in any of the above embodiments.

[0666] It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this invention, and these improvements and modifications are also considered to be within the scope of protection of this invention.

Claims

1. A method for mutual charging of automobiles, characterized in that, The method includes: In response to a charging request sent by a powered vehicle, a power supply vehicle that meets the charging requirements of the charging request is determined from all vehicles in a preset candidate power supply vehicle register. Feedback of power supply vehicle information to the power receiving vehicle, and synchronization of power receiving vehicle information to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging; The charging request includes the required power supply and the location of the receiving vehicle. The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes: Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles; One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles; Specifically, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles includes: The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location. The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle. The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle; The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

2. The vehicle mutual charging method as described in claim 1, characterized in that, The candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platform of at least one OEM participating in mutual charging. The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

3. The vehicle mutual charging method as described in claim 2, characterized in that, The process of completing the vehicle's registration as a power supply vehicle specifically includes: The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply. The vehicle number includes the OEM information to which the vehicle belongs. The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

4. The vehicle mutual charging method as described in claim 3, characterized in that, The method further includes: When a power supply cancellation request is received from a registered vehicle, the registration request information and vehicle information of the registered vehicle mentioned in the power supply vehicle ledger of this cloud platform are deleted.

5. The vehicle mutual charging method as described in claim 2, characterized in that, The real-time update process of the vehicle information specifically includes: Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

6. The vehicle mutual charging method as described in claim 1, characterized in that, Before determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles as the power supply vehicle, the method further includes: The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number. Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

7. The vehicle mutual charging method as described in claim 1, characterized in that, The step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes: Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM; The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power. The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

8. The vehicle mutual charging method as described in claim 1, characterized in that, The step of filtering out a candidate power supply vehicle list that meets the charging requirements from all the acquired vehicles specifically includes: Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list; The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

9. The vehicle mutual charging method as described in claim 1, characterized in that, The step of determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles specifically includes: The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location. The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

10. The vehicle mutual charging method as described in claim 1, characterized in that, The step of determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles specifically includes: The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated. The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

11. The vehicle mutual charging method as described in claim 1, characterized in that, The step of determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles specifically includes: The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list. The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

12. The vehicle mutual charging method as described in claim 1, characterized in that, The step of determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles specifically includes: A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle. Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2; The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle. Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle. The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

13. The vehicle mutual charging method as described in claim 1, characterized in that, The step of determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles specifically includes: A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle. The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

14. The vehicle mutual charging method as described in claim 1, characterized in that, The process of feeding back the power supply vehicle information to the power receiving vehicle and synchronizing the power receiving vehicle information to the power supply vehicle specifically includes: When the power supply vehicle is not a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the vehicle number of the power supply vehicle is uploaded to the candidate power supply vehicle ledger, so that the cloud platform of the power supply vehicle can obtain the vehicle number of the power supply vehicle from the candidate power supply vehicle ledger, and send the power receiving vehicle information to the power supply vehicle according to the key of the power supply vehicle. When the power supply vehicle is a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the power receiving vehicle information is sent to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet up and complete mutual charging.

15. The vehicle mutual charging method as described in claim 1, characterized in that, The power supply vehicle information includes the real-time location information, real-time remaining power information, and contact information of the power supply vehicle; The information about the receiving vehicle includes its power receiving location, real-time remaining power information, and contact information.

16. A car mutual charging device, characterized in that, The device includes: The charging request response module is used to respond to a charging request sent by a powered vehicle and determine a power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register. The signal feedback module is used to feed back the power supply vehicle information to the power receiving vehicle and synchronize the power receiving vehicle information to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging. The charging request includes the required power supply and the location of the receiving vehicle. The charging request response module is specifically used for: Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles; One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles; The charging request response module is also specifically used for: The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location. The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle. The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle; The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

17. The vehicle mutual charging device as described in claim 16, characterized in that, The candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platform of at least one OEM participating in mutual charging. The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

18. The vehicle mutual charging device as described in claim 17, characterized in that, The process of completing the vehicle's registration as a power supply vehicle specifically includes: The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply. The vehicle number includes the OEM information to which the vehicle belongs. The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

19. The vehicle mutual charging device as described in claim 18, characterized in that, The device further includes: The unregistration module is used to delete the registration application information and vehicle information of the registered vehicle in the power supply vehicle sub-ledger of this cloud platform when a power supply cancellation request is received from a registered vehicle.

20. The vehicle mutual charging device as described in claim 17, characterized in that, The real-time update process of the vehicle information specifically includes: Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

21. The vehicle mutual charging device as described in claim 16, characterized in that, The device further includes: The rescue confirmation module is used for: The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number. Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

22. The vehicle mutual charging device as described in claim 16, characterized in that, The charging request response module is also specifically used for: Prioritize selecting all vehicles from all acquired vehicles that are manufactured by the same OEM as the receiving vehicle as vehicles from the same OEM; The second candidate list is selected from the vehicle information of vehicles from the same factory that have a real-time remaining battery power greater than the threshold battery power set in the vehicle's registration application information and greater than the required battery power. The second candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

23. The vehicle mutual charging device as described in claim 16, characterized in that, The charging request response module is also specifically used for: Filter out all vehicles whose real-time remaining battery power is greater than the threshold battery power set in the vehicle's registration application information and also greater than the required battery power, and select them as the first candidate list; The first candidate list is used to select all vehicles whose real-time location information in the vehicle information is no greater than the threshold distance set in the vehicle's registration application information, and these are selected as the candidate power supply vehicle list.

24. The vehicle mutual charging device as described in claim 16, characterized in that, The charging request response module is also specifically used for: The real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list is calculated and compared with the power supply distance of the power receiving location. The candidate vehicle with the shortest power supply distance is determined as the power supply vehicle.

25. The vehicle mutual charging device as described in claim 16, characterized in that, The charging request response module is also specifically used for: The target distance between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding target location is calculated. The candidate vehicle with the shortest destination distance is determined as the power supply vehicle.

26. The vehicle mutual charging device as described in claim 16, characterized in that, The charging request response module is also specifically used for: The real-time remaining power of each candidate vehicle in the candidate power supply vehicle list. The candidate vehicle with the highest real-time remaining power is determined as the power supply vehicle.

27. The vehicle mutual charging device as described in claim 16, characterized in that, The charging request response module is also specifically used for: A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle. Select n rating values ​​from the rating database for each candidate vehicle, and select the same n rating values ​​for each candidate vehicle, where n≥2; The n scores of each candidate vehicle are weighted and summed according to the preset weight of each score to obtain the ranking value of each candidate vehicle. Based on the ranking value of each candidate vehicle's charging, the vehicle with the highest ranking value in the obtained list of candidate power supply vehicles is determined as the power supply vehicle. The scoring database for each candidate vehicle includes: a normalized first score value for the power supply distance of the candidate vehicle, a normalized second score value for the destination distance of the candidate vehicle, a normalized third score value for the remaining power of the candidate vehicle, a normalized fourth score value for the congestion level of the candidate vehicle, and a fifth score value for the OEM of the candidate vehicle; the fifth score value of candidate vehicles belonging to the same OEM as the receiving vehicle is a first preset value, and the fifth score value of candidate vehicles not belonging to the same OEM as the receiving vehicle is a second preset value; the weight of the first score value is negative, the weight of the second score value is negative, the weight of the third score value is positive, the weight of the fourth score value is negative, and the weight of the fifth score value is positive.

28. The vehicle mutual charging device as described in claim 16, characterized in that, The charging request response module is also specifically used for: A score database for each candidate vehicle is calculated based on the vehicle information and charging requirements of each candidate vehicle. The power supply vehicle is determined by sending the scoring database of each candidate vehicle to the power receiving vehicle according to the key of the power receiving vehicle and receiving the vehicle number selected by the user in the power receiving vehicle according to the scoring database of each candidate vehicle.

29. The vehicle mutual charging device as described in claim 16, characterized in that, The signal feedback module is specifically used for: When the power supply vehicle is not a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the vehicle number of the power supply vehicle is uploaded to the candidate power supply vehicle ledger, so that the cloud platform of the power supply vehicle can obtain the vehicle number of the power supply vehicle from the candidate power supply vehicle ledger, and send the power receiving vehicle information to the power supply vehicle according to the key of the power supply vehicle. When the power supply vehicle is a vehicle from the same manufacturer as the power receiving vehicle, the power supply vehicle information is fed back to the power receiving vehicle, and the power receiving vehicle information is sent to the power supply vehicle, so that the power supply vehicle and the power receiving vehicle can meet up and complete mutual charging.

30. The vehicle mutual charging device as described in claim 16, characterized in that, The power supply vehicle information includes the real-time location information, real-time remaining power information, and contact information of the power supply vehicle; The information about the receiving vehicle includes its power receiving location, real-time remaining power information, and contact information.

31. A method for mutual charging of automobiles, characterized in that, The method includes: The cloud platform receiving the power supply vehicle determines the vehicle information of the power supply vehicle that meets the charging requirements from all vehicles in the preset candidate power supply vehicle ledger. Send the power receiving vehicle information to the power supply vehicle so that the power supply vehicle and the power receiving vehicle can meet and complete mutual charging; The charging request includes the required power supply and the location of the receiving vehicle. The step of determining the charging vehicles that meet the charging requirements from all vehicles in a preset candidate power supply vehicle register specifically includes: Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles; One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles; Specifically, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles includes: The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location. The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle. The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle; The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

32. The vehicle mutual charging method as described in claim 31, characterized in that, The candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platform of at least one OEM participating in mutual charging. The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

33. The vehicle mutual charging method as described in claim 32, characterized in that, The process of completing the vehicle's registration as a power supply vehicle specifically includes: The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply. The vehicle number includes the OEM information to which the vehicle belongs. The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

34. The vehicle mutual charging method as described in claim 32, characterized in that, The real-time update process of the vehicle information specifically includes: Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

35. The vehicle mutual charging method as described in claim 32, characterized in that, The method further includes: When a power supply cancellation request is received from a registered vehicle, the registration request information and vehicle information of the registered vehicle mentioned in the power supply vehicle ledger of this cloud platform are deleted.

36. The vehicle mutual charging method as described in claim 31, characterized in that, The process by which the cloud platform of the power receiving vehicle determines the power supply vehicle specifically includes the following steps: the cloud platform of the power receiving vehicle executes the following... Receive the charging request sent by the receiving vehicle; Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. From all the acquired vehicles, a list of candidate power supply vehicles that meet the charging requirements of the charging request is selected. The charging requirements include the required power and the location of the receiving vehicle. One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

37. The vehicle mutual charging method as described in claim 36, characterized in that, Before determining one of the candidate power supply vehicles from the obtained list, the cloud platform of the power receiving vehicle performs the following: The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number. Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

38. The vehicle mutual charging method as described in claim 31, characterized in that, The information about the receiving vehicle includes its power receiving location, real-time remaining power information, and contact information.

39. A car mutual charging device, characterized in that, The device includes: The receiving module is used to receive vehicle information of the power supply vehicle that meets the charging requirements of the charging request, which is determined by the cloud platform of the power receiving vehicle from all vehicles in the preset candidate power supply vehicle ledger. The transmitting module is used to transmit information about the receiving vehicle to the supplying vehicle, so that the supplying vehicle and the receiving vehicle can meet and complete mutual charging. The charging request includes the required power supply and the location of the receiving vehicle. The step of determining the charging vehicles that meet the charging requirements from all vehicles in a preset candidate power supply vehicle register specifically includes: Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles; One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles; Specifically, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles includes: The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location. The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle. The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle; The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

40. The vehicle mutual charging device as described in claim 39, characterized in that, The candidate power supply vehicle ledger includes a power supply vehicle sub-ledger established on different blockchain nodes by the cloud platform of at least one OEM participating in mutual charging. The power supply vehicle ledger on any cloud platform includes registration application information for vehicles that have completed power supply vehicle registration on that cloud platform, as well as real-time updated vehicle information.

41. The vehicle mutual charging device as described in claim 40, characterized in that, The process of completing the vehicle's registration as a power supply vehicle specifically includes: The vehicle sends registration application information to the cloud platform of the vehicle's OEM. The registration application information includes the vehicle number, the threshold power that the vehicle can supply, and the threshold distance that the vehicle can supply. The vehicle number includes the OEM information to which the vehicle belongs. The vehicle's cloud platform receives the registration application information, generates a key for the vehicle, saves the vehicle number and the key as a pair, and uploads the vehicle's registration application information to the power supply vehicle sub-ledger pre-established on the vehicle's cloud platform to complete the registration.

42. The vehicle mutual charging device as described in claim 40, characterized in that, The real-time update process of the vehicle information specifically includes: Any cloud platform receives real-time vehicle information uploaded by vehicles registered on this cloud platform and synchronously updates the received vehicle information to the power supply vehicle ledger on this cloud platform; wherein, the vehicle information includes vehicle number, real-time remaining power, real-time location information and vehicle destination location.

43. The vehicle mutual charging device as described in claim 41, characterized in that, The device further includes: The unregistration module is used to delete the registration application information and vehicle information of the registered vehicle in the power supply vehicle sub-ledger of this cloud platform when a power supply cancellation request is received from a registered vehicle.

44. The vehicle mutual charging device as described in claim 39, characterized in that, The process by which the cloud platform of the power receiving vehicle determines the power supply vehicle specifically includes the following steps: the cloud platform of the power receiving vehicle executes the following... Receive the charging request sent by the receiving vehicle; Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. From all the acquired vehicles, a list of candidate power supply vehicles that meet the charging requirements of the charging request is selected. The charging requirements include the required power and the location of the receiving vehicle. One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles.

45. The vehicle mutual charging device as described in claim 43, characterized in that, Before determining one of the candidate power supply vehicles from the obtained list, the cloud platform of the power receiving vehicle performs the following: The vehicle number of each candidate vehicle in the obtained candidate power supply vehicle list is synchronized to the corresponding cloud platform, so that the cloud platform of each candidate vehicle can send a request for assistance to each candidate vehicle according to the key corresponding to the vehicle number. Based on the confirmation of assistance information received by each candidate vehicle from the cloud platform, candidate vehicles that have not provided confirmation of assistance information are removed from the list of candidate power supply vehicles, and the list of candidate power supply vehicles is updated.

46. ​​The vehicle mutual charging device as described in claim 39, characterized in that, The information about the receiving vehicle includes its power receiving location, real-time remaining power information, and contact information.

47. A method for mutual charging of automobiles, characterized in that, The method includes: In response to a user-inputted charging command, a charging request is sent to the cloud platform of the OEM, so that the cloud platform can determine a power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register. Based on the power supply vehicle information fed back by the cloud platform, the system meets with the power supply vehicle and completes mutual charging. The charging request includes the required power supply of the receiving vehicle and the location of the receiving vehicle. The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes: Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles; One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles; Specifically, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles includes: The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location. The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle. The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle; The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

48. A car mutual charging device, characterized in that, The device includes: The charging request module is used to respond to the charging command input by the user and send a charging request to the cloud platform of the OEM so that the cloud platform can determine the charging vehicle that meets the charging requirements of the charging request from all vehicles in the preset candidate power supply vehicle ledger. The mutual charging module is used to meet with the power supply vehicle and complete the mutual charging based on the power supply vehicle information fed back by the cloud platform. The charging request includes the required power supply of the receiving vehicle and the location of the receiving vehicle. The step of determining the power supply vehicle that meets the charging requirements of the charging request from all vehicles in a preset candidate power supply vehicle register specifically includes: Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles; One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles; Specifically, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles includes: The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location. The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle. The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle; The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

49. A method for mutual charging of automobiles, characterized in that, The method includes: The cloud platform receives the power receiving vehicle information sent through communication established by the vehicle number of the vehicle. The vehicle number is the vehicle number of the power receiving vehicle that the cloud platform determines from all vehicles in the preset candidate power supply vehicle ledger that meet the charging requirements of the charging request. After meeting with the receiving vehicle based on the information of the receiving vehicle, mutual charging is completed. The charging request includes the required power supply and the location of the receiving vehicle. The step of determining the charging vehicles that meet the charging requirements from all vehicles in a preset candidate power supply vehicle register specifically includes: Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles; One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles; Specifically, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles includes: The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location. The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle. The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle; The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

50. A car mutual charging device, characterized in that, The device includes: The power receiving vehicle information receiving module is used to receive power receiving vehicle information sent by the cloud platform through the vehicle number of the vehicle. The vehicle number is the vehicle number of the power supply vehicle that the cloud platform determines from all vehicles in the preset candidate power supply vehicle ledger that meets the charging requirements of the charging request. The mutual charging module is used to complete mutual charging after meeting with the receiving vehicle based on the receiving vehicle information; The charging request includes the required power supply and the location of the receiving vehicle. The step of determining the charging vehicles that meet the charging requirements from all vehicles in a preset candidate power supply vehicle register specifically includes: Through blockchain protocol verification, we obtain the registration application information and real-time vehicle information of all vehicles in the power supply vehicle ledgers distributed across different cloud platforms on different blockchain nodes. Filter out a list of candidate power supply vehicles that meet the charging requirements from all the acquired vehicles; One of the candidate power supply vehicles is selected as the power supply vehicle based on the obtained list of candidate power supply vehicles; Specifically, determining one of the candidate power supply vehicles from the obtained list of candidate power supply vehicles includes: The navigation route between the real-time location information of each candidate vehicle in the obtained candidate power supply vehicle list and the corresponding destination location. The congestion score for each candidate vehicle is calculated based on the distance of the route at each level of congestion in the navigation route for each candidate vehicle. The candidate vehicle with the highest or lowest congestion score is identified as the power supply vehicle; The congestion score is equal to the sum of the product of the route distance with a congestion level of congestion and the first preset value, the route distance with a very congestion level of congestion and the second preset value, the route distance with a severe congestion level of congestion and the third preset value, and the route distance with a deadlock level of congestion and the fourth preset value.

51. A vehicle mutual charging system, characterized in that, The system includes: at least one OEM cloud platform, and all OEM cloud platforms are connected to the blockchain; The first cloud platform in the system is used to execute a vehicle mutual charging method as described in any one of claims 1-15 and 31-38.

52. The vehicle mutual charging system as described in claim 51, characterized in that, Each OEM cloud platform in the system is used to obtain vehicle registration information, and the vehicle includes at least one of any vehicle of that OEM, a power supply vehicle, and a power receiving vehicle.

53. A vehicle mutual charging system, characterized in that, The system includes: a power supply vehicle cloud platform and a power receiving vehicle cloud platform, which are connected via blockchain. The cloud platform for receiving powered vehicles is used to execute a vehicle mutual charging method as described in any one of claims 1 to 15; or... The power supply vehicle cloud platform is used to execute a vehicle mutual charging method as described in any one of claims 31 to 38.

54. A terminal device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the vehicle mutual charging method as described in any one of claims 1 to 15.

55. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device containing the computer-readable storage medium to perform the vehicle mutual charging method as described in any one of claims 1-15 and 31-38.

56. A vehicle mutual charging system, characterized in that, It includes a cloud platform, a power supply vehicle, and a power receiving vehicle, wherein the cloud platform is used to execute the vehicle mutual charging method as described in any one of claims 1 to 15 and 31 to 38.

Images