Charging method and device
By using a unique production equipment identification number and charging event, the vehicle identification code is verified, and the risk of electric vehicles being stolen in plug-and-play charging scenarios is solved, achieving higher charging safety.
Patent Information
- Application Number
- CN202310518603.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-12
AI Technical Summary
In the plug-and-play charging scenario, the risk of electric vehicles being stolen is high, and the prior art is difficult to effectively reduce such risks.
Reduce usage by using the unique production equipment identification number (PDID) and charging event of each device to be charged, identifying and verifying the vehicle identification number (VIN), and encrypting the charging event if necessary to ensure the safety and authenticity of charging, reducing impersonation and the possibility of stolen charges.
It effectively reduces the risk of electric vehicles being stolen in plug-and-play charging scenarios, improves charging safety, and ensures the authenticity and safety of charging events.
Smart Images

Figure CN118928134A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of terminal technology, and in particular to a charging method and device. Background Art
[0002] With the development of vehicle technology, electric vehicles, such as electric cars, are becoming more and more popular. Correspondingly, equipment for charging electric vehicles, such as charging piles, has also become a rigid demand. Currently, electric vehicles can be charged in a plug-and-charge manner. Plug-and-charge means that the user signs a plug-and-charge agreement (or plug-and-charge service, etc.) for the electric vehicle in advance. In this way, when the electric vehicle is charging, the charging gun of the charging pile is directly inserted into the charging port of the electric vehicle to charge the electric vehicle.
[0003] However, in the plug-and-charge solution, charging and deduction are performed by identifying the vehicle identification number (VIN) of the electric vehicle. The VIN of the electric vehicle that has signed the plug-and-charge agreement may be used by other electric vehicles, and the risk of stolen charging is high. Summary of the invention
[0004] The present application provides a charging method and device, which can reduce the risk of electric vehicles being stolen and charged in a plug-and-charge scenario.
[0005] In order to achieve the above objectives, this application adopts the following technical solutions:
[0006] In a first aspect, a charging method is provided, which is applied to a first device. Optionally, the first device can be a device to be charged or a terminal device. The method includes: receiving a first request message from a network device; in response to the first request message, sending a production device identification number PDID of the first device to be charged and a charging event to the network device, wherein the charging event is used to characterize the charging status of the first device to be charged, and the PDID and charging event of the first device to be charged are used to determine whether to start the power supply device to charge the device to be charged that reports the first vehicle identification code VIN, and the first VIN is the VIN of the first device to be charged.
[0007] Based on the above technical solution, since the PDID of each device to be charged is unique and cannot be tampered with, the real device to be charged is identified through the PDID, and then the charging event of the real device to be charged is used to determine whether to charge the device that reports the VIN of the real device to be charged. The charging event of the real device to be charged can be used to characterize the charging status of the real device to be charged, such as whether it is charging or whether there is a charging demand, etc., and then it can be determined whether the device that reports the VIN of the real device to be charged is the real device to be charged, so as to determine whether to charge this device. It can avoid the situation where a third party counterfeits the VIN for charging, reduce the risk of the charging device, such as electric vehicles, being stolen and charged in the plug-and-play scenario, and improve charging safety.
[0008] In one possible design, before sending the PDID of the first device to be charged and the charging event to the network device, the method further includes: encrypting the charging event using the private key corresponding to the PDID of the first device to be charged. Based on this design, after encrypting the charging event using the private key corresponding to the PDID and then sending it to the network device, the security of the charging event can be further guaranteed, ensuring that the charging event is confirmed to be from a real device to be charged, and reducing the probability of the charging event of the real device to be charged being impersonated.
[0009] In one possible design, the charging event includes the geographic location of the first device to be charged. When the distance between the geographic location of the first device to be charged and the power supply device meets the preset distance range, the PDID of the first device to be charged and the charging event are used to determine whether to start the power supply device to charge the device to be charged that reports the first VIN. Based on this design, the distance between the real device to be charged and the power supply device is identified by the geographic location. When the distance meets the preset distance range, it means that the real device to be charged and the power supply device are in the same location. Then the device to be charged that reports the VIN may indeed be a real charging device, and then it is possible to charge the device to be charged that reports the VIN. The difficulty of unauthorized charging is increased, the risk of the device to be charged, such as electric vehicles, being stolen and charged can be reduced, and charging safety is improved.
[0010] In one possible design, the charging event includes the state of the charging port of the first device to be charged. When the state of the charging port of the first device to be charged is open, the PDID of the first device to be charged and the charging event are used to determine whether to start the power supply device to charge the device to be charged that reports the first VIN. Based on this design, by identifying the state of the charging port of the real device to be charged, when it is in the open state, it means that the real device to be charged may indeed need to be charged. That is, the device to be charged that reports the VIN may be the real device to be charged. In addition, other people may not be able to open the charging port of the real device to be charged when they do not have the key, which can further illustrate that the device to be charged that reports the VIN may be the real device to be charged, and then it is possible to charge the device to be charged that reports the VIN. The difficulty of unauthorized charging is increased, the risk of the device to be charged, such as electric vehicles, being stolen and charged can be reduced, and charging safety is improved.
[0011] In one possible design, the charging event includes the state of the first device to be charged after the power supply device is started to charge the device to be charged that reports the first VIN. When the state of the first device to be charged is a non-charging state, the PDID of the first device to be charged and the charging event are used to determine whether to stop the power supply device from charging the device to be charged that reports the first VIN. In this way, after the power supply device is started to charge the device to be charged that reports the VIN, by identifying the state of the real device to be charged, if it is a non-charging state. It means that the device to be charged that reports the VIN is not the real device to be charged. Then, charging the device to be charged is stopped, which increases the difficulty of stealing charging, can reduce the risk of stolen charging of devices to be charged, such as electric vehicles, and improve charging safety.
[0012] In one possible design, the PDID of the first device to be charged and the private key corresponding to the PDID of the first device to be charged are stored in the chip of the first device to be charged. Based on this design, the PDID and the private key corresponding to the PDID are stored in the chip of the device to be charged, so that it is more difficult for others to obtain the PDID and the corresponding private key of the device to be charged. Furthermore, by identifying the identity of the device to be charged and the charging events of the device to be charged through the PDID and the private key of the PDID, it can be ensured that the reported charging events are indeed those of the real device to be charged, reducing the probability of others impersonating the charging events of the real device to be charged, thereby increasing the difficulty of unauthorized charging, reducing the risk of the devices to be charged, such as electric vehicles, being charged illegally, and improving charging safety.
[0013] In one possible design, before receiving the first request message from the network device, the method further includes: sending a second request message to the network device, the second request message including the first VIN, the second request message being used to request to sign up for a plug-and-charge service, the plug-and-charge service being used to start charging the power supply device in a plug-and-charge manner. Based on this design, the device to be charged can be charged in a plug-and-charge manner, bringing convenience to the user.
[0014] In a second aspect, a charging method is provided, which is applied to a second device, and the method includes: receiving a first message sent by a device to be charged from a power supply device, the first message carrying a first VIN, and the first message is used to instruct the power supply device to start charging the device to be charged; obtaining a charging event of a device corresponding to a target PDID, the charging event is used to characterize the charging status of the device corresponding to the target PDID, and the target PDID corresponds to the first VIN; and determining whether to start the power supply device to charge the device to be charged according to the charging event.
[0015] In one possible design, obtaining a charging event of a device corresponding to a target PDID includes: receiving a charging event encrypted using a private key corresponding to the target PDID from the device corresponding to the target PDID; and decrypting the charging event according to a public key corresponding to the target PDID.
[0016] In one possible design, the charging event includes the geographic location of the device corresponding to the target PDID; determining whether to start the power supply device to charge the device to be charged based on the charging event includes: when the distance between the geographic location of the device corresponding to the target PDID and the power supply device satisfies a preset distance range, determining to start the power supply device to charge the device to be charged.
[0017] In one possible design, the charging event includes the status of the charging port of the device corresponding to the target PDID; determining whether to start the power supply device to charge the device to be charged based on the charging event includes: when the status of the charging port of the device corresponding to the target PDID is open, determining to start the power supply device to charge the device to be charged.
[0018] In one possible design, the charging event includes the state of the device corresponding to the target PDID after the power supply device is started to charge the device to be charged; determining whether to start the power supply device to charge the device to be charged based on the charging event includes: when the state of the device corresponding to the target PDID is a non-charging state, determining to stop the power supply device from charging the device to be charged.
[0019] In one possible design, the target PDID and the private key corresponding to the target PDID are stored in the chip of the device corresponding to the target PDID; the public key corresponding to the target PDID is stored in the network device.
[0020] In one possible design, before determining to start the power supply device to charge the device to be charged, the method also includes: determining that the first VIN has signed a plug-and-charge service, and the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner.
[0021] For the technical effects brought about by any design in the second aspect, reference can be made to the technical effects of the corresponding design in the first aspect.
[0022] In a third aspect, a charging method is provided, which is applied to a first device. Optionally, the first device may be a device to be charged. The method includes: sending a second message to a network device, the second message carrying a dynamically generated second VIN, the second message being used to start the power supply device to charge the device to be charged; when the first VIN corresponding to the second VIN has signed a plug-and-charge service, receiving the amount of electricity delivered by the power supply device, the plug-and-charge service being used to start charging the power supply device in a plug-and-charge manner.
[0023] Based on the above technical solution, since the second VIN is randomly generated, the probability that a third party can impersonate the second VIN is low. Therefore, the device to be charged uses the second VIN to charge, which can reduce the risk of the device to be charged, such as an electric vehicle, being stolen and charged in a plug-and-play scenario.
[0024] In one possible design, before sending the second message to the network device, the method further includes: determining that the second VIN meets the validity condition, and the validity condition includes: the number of times of use is less than or equal to the preset number threshold, and the usage time is within the preset usage time. Based on this design, the device to be charged will use the second VIN for charging only when it is determined that the second VIN meets the validity condition, that is, the second VIN can only be used under certain conditions. This can ensure that the second VIN does not conflict with the VIN of other devices, and can also ensure that the second VIN is more random, and the probability of a third party being able to impersonate the second VIN is lower, which can further reduce the risk of the device to be charged, such as an electric vehicle, being stolen and charged in a plug-and-play scenario.
[0025] In a possible design, before sending the second message to the network device, the method further includes: sending the first VIN to the network device; receiving the second VIN from the network device, the second VIN being generated according to at least one of the first VIN, a preset random number, and a preset usage time. Based on this design, the second VIN is generated according to the first VIN, the preset random number, the preset usage time and other parameters, and the random number, the usage time and the like are all preset by the developer, so that the randomness of the second VIN generation can be guaranteed, and the probability of a third party impersonating the second VIN can be reduced, thereby reducing the risk of the charging device, such as an electric vehicle, being stolen and charged in a plug-and-play scenario.
[0026] In a possible design, the second message includes a battery management system BMS and a vehicle identification message BRM message. Based on this design, the second VIN is carried by the BRM message, so that the power supply device can identify the second VIN and complete the process of charging the device to be charged.
[0027] In a fourth aspect, a charging method is provided, which is applied to a second device, and the method includes: receiving a second message, the second message carrying a dynamically generated second VIN, and the second message is used to start the power supply device to charge the device to be charged; when a first VIN corresponding to the second VIN has signed a plug-and-charge service, instructing the power supply device to charge the device to be charged, and the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner.
[0028] In one possible design, the second VIN satisfies validity conditions, which include: the number of uses is less than or equal to a preset number threshold, and the usage time is within at least one of the preset usage time.
[0029] In one possible design, before receiving the second message, the method also includes: receiving a first VIN; generating a second VIN based on at least one of the first VIN, a preset random number, and a preset usage time; and sending the second VIN to the device to be charged.
[0030] In a possible design, the first VIN includes a first field, a second field, and a third field, the first field includes the world manufacturer identification code WMI and the vehicle description part VDS, the second field includes the model year and assembly plant, and the third field includes a secure random number; generating the second VIN according to at least one of the first VIN, the preset random number, and the preset usage time includes: generating a target random number according to the reference field, the preset random number, and the preset usage time; generating the second VIN according to the reference field and the target random number; wherein the reference field includes the first field and the second field, and the length of the target random number is the same as the length of the third field; or, the reference field includes the first field, the total length of the second field and the third field, which is the same as the length of the target random number. Based on this design, the power supply device can identify the manufacturer, VDS, and other information of the device to be charged according to the generated second VIN, and complete the process of charging the device to be charged.
[0031] In a possible design, a target random number is generated according to a reference field, a preset random number, and a preset usage time, including: encoding a hash value of the reference field, the preset random number, and the preset usage time to obtain the target random number.
[0032] In a possible design, the reference field includes the first field and the second field, and the length of the third field is 6 bytes; the target random number is the first 6 bytes after encoding RAND1, and RAND1 satisfies the following formula:
[0033] RAND1=sha256(VIN[1-11]|Salt|Day)
[0034] Among them, VIN[1-11] is the first field and the second field, Salt is a preset random number, Day is a preset usage time, and sha256 is a hash function.
[0035] In a possible design, the reference field includes the first field, and the total length of the second field and the third field is 8 bytes; the target random number is the first 8 bytes after encoding RAND2, and RAND2 satisfies the following formula:
[0036] RAND2=sha256(VIN[1-9]|Salt|Day)
[0037] Among them, VIN[1-9] is the first field, Salt is the preset random number, Day is the preset usage time, and sha256 is the hash function.
[0038] In one possible design, before sending the second VIN to the device to be charged, the method further includes: determining that the second VIN is different from the VIN of other devices within a preset usage time. Based on this design, it can be ensured that the second VINs of different devices to be charged are different within the same time, thereby reducing the probability of second VIN conflict.
[0039] In one possible design, before instructing the power supply device to charge the charging device, the method also includes: obtaining a charging event of the device corresponding to the target PDID, the charging event is used to characterize the charging status of the device corresponding to the target PDID, and the target PDID corresponds to the first VIN; determining that the charging event satisfies the corresponding first preset condition; wherein the charging event includes: the geographic location of the device corresponding to the target PDID, and the corresponding first preset condition includes: the distance between the geographic location of the device corresponding to the target PDID and the power supply device satisfies a preset distance range; and / or, the charging event includes: the state of the charging port of the device corresponding to the target PDID, and the corresponding first preset condition includes: the state of the charging port of the device corresponding to the target PDID is open.
[0040] In one possible design, after instructing the power supply device to charge the device to be charged, the method also includes: obtaining the status of the device corresponding to the target PDID; when the status of the device corresponding to the target PDID is a non-charging state, instructing the power supply device to stop charging the device to be charged.
[0041] In one possible design, obtaining a charging event of a device corresponding to a target PDID includes: receiving a charging event encrypted using a private key corresponding to the target PDID; and decrypting the charging event according to a public key corresponding to the target PDID.
[0042] In one possible design, the target PDID and the private key corresponding to the target PDID are stored in the chip of the device corresponding to the target PDID; the public key corresponding to the target PDID is stored in the network device.
[0043] In one possible design, the second message includes a battery management system BMS and a vehicle identification message BRM message.
[0044] Regarding the technical effects brought about by other designs in the fourth aspect, reference may be made to the technical effects brought about by the corresponding designs in the third aspect or the first aspect.
[0045] In a fifth aspect, a device is provided, which has the function of implementing the method described in the first aspect and any one of the designs thereof. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions. In a possible example, the device includes a communication unit (or communication module): a communication unit, which is used to: receive a first request message from a network device; in response to the first request message, send a production device identification number PDID and a charging event of a first device to be charged to the network device, the charging event is used to characterize the charging status of the first device to be charged, and the PDID and charging event of the first device to be charged are used to determine whether to start the power supply device to charge the device to be charged that reports the first vehicle identification code VIN, and the first VIN is the VIN of the first device to be charged.
[0046] In one possible design, the device also includes a processing unit (or processing module); the processing unit is used to encrypt the charging event using a private key corresponding to the PDID of the first device to be charged.
[0047] In one possible design, the charging event includes the geographic location of the first device to be charged. When the distance between the geographic location of the first device to be charged and the power supply device meets a preset distance range, the PDID of the first device to be charged and the charging event are used to determine whether to start the power supply device to charge the device to be charged that reports the first VIN.
[0048] In one possible design, the charging event includes the status of the charging port of the first device to be charged. When the charging port of the first device to be charged is in an open state, the PDID of the first device to be charged and the charging event are used to determine whether to start the power supply device to charge the device to be charged that reports the first VIN.
[0049] In one possible design, the charging event includes the state of the first device to be charged after the power supply device is started to charge the device to be charged that reports the first VIN. When the state of the first device to be charged is a non-charging state, the PDID of the first device to be charged and the charging event are used to determine to stop the power supply device from charging the device to be charged that reports the first VIN.
[0050] In a possible design, the PDID of the first device to be charged and the private key corresponding to the PDID of the first device to be charged are stored in a chip of the first device to be charged.
[0051] In one possible design, the communication unit is also used to send a second request message to the network device, the second request message includes the first VIN, the second request message is used to request to sign a plug-and-charge service, and the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner.
[0052] In a sixth aspect, a device is provided, which has the function of implementing the method described in the second aspect and any one of the designs thereof. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions. In a possible example, the device includes a communication unit (or communication module) and a processing unit (or processing module); the communication unit is used to receive a first message sent by a device to be charged from a power supply device, the first message carries a first VIN, and the first message is used to indicate that the power supply device is started to charge the device to be charged; the processing unit is used to obtain a charging event of a device corresponding to a target PDID, and the charging event is used to characterize the charging status of the device corresponding to the target PDID, and the target PDID corresponds to the first VIN; the processing unit is also used to determine whether to start the power supply device to charge the device to be charged according to the charging event.
[0053] In one possible design, the communication unit is also used to receive a charging event encrypted using a private key corresponding to the target PDID from a device corresponding to the target PDID; the processing unit is also used to decrypt the charging event based on a public key corresponding to the target PDID.
[0054] In one possible design, the charging event includes the geographic location of the device corresponding to the target PDID; the processing unit is specifically used to determine to start the power supply device to charge the device to be charged when the distance between the geographic location of the device corresponding to the target PDID and the power supply device meets a preset distance range.
[0055] In one possible design, the charging event includes the state of the charging port of the device corresponding to the target PDID; the processing unit is specifically used to determine to start the power supply device to charge the device to be charged when the state of the charging port of the device corresponding to the target PDID is open.
[0056] In one possible design, the charging event includes the state of the device corresponding to the target PDID after the power supply device is started to charge the device to be charged; the processing unit is specifically used to determine to stop the power supply device from charging the device to be charged when the state of the device corresponding to the target PDID is a non-charging state.
[0057] In one possible design, the target PDID and the private key corresponding to the target PDID are stored in the chip of the device corresponding to the target PDID; the public key corresponding to the target PDID is stored in the network device.
[0058] In one possible design, the processing unit is further used to determine that the first VIN has signed a plug-and-charge service, and the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner.
[0059] In the seventh aspect, a device is provided, which has the function of implementing the method described in the third aspect and any one of the designs thereof. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions. In a possible example, the device includes a communication unit (or communication module) and a processing unit (or processing module); the communication unit is used to send a second message to the network device, the second message carries a dynamically generated second VIN, and the second message is used to start the power supply device to charge the device to be charged; the processing unit is used to receive the power delivered by the power supply device when the first VIN corresponding to the second VIN has signed a plug-and-charge service, and the plug-and-charge service is used to start the power supply device charging in a plug-and-charge manner.
[0060] In one possible design, the processing unit is further used to determine that the second VIN meets a validity condition, and the validity condition includes at least one of: the number of uses is less than or equal to a preset number threshold, and the usage time is within a preset usage time.
[0061] In one possible design, the communication unit is also used to send a first VIN to the network device; the communication unit is also used to receive a second VIN from the network device, and the second VIN is generated based on at least one of the first VIN, a preset random number, and a preset usage time.
[0062] In one possible design, the second message includes a battery management system BMS and a vehicle identification message BRM message.
[0063] In an eighth aspect, a device is provided, which has the function of implementing the method described in the fourth aspect and any one of the designs thereof. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions. In a possible example, the device includes a communication unit (or communication module) and a processing unit (or processing module); the communication unit is used to receive a second message, the second message carries a dynamically generated second VIN, and the second message is used to start the power supply device to charge the device to be charged; the processing unit is used to instruct the power supply device to charge the device to be charged when the first VIN corresponding to the second VIN has signed a plug-and-charge service, and the plug-and-charge service is used to start the power supply device to charge in a plug-and-charge manner.
[0064] In one possible design, the second VIN satisfies validity conditions, which include: the number of uses is less than or equal to a preset number threshold, and the usage time is within at least one of the preset usage time.
[0065] In one possible design, the communication unit is also used to receive the first VIN; the processing unit is also used to generate a second VIN based on at least one of the first VIN, a preset random number, and a preset usage time; the communication unit is also used to send the second VIN to the device to be charged.
[0066] In one possible design, the first VIN includes a first field, a second field and a third field, the first field includes a world manufacturer identification code WMI and a vehicle description part VDS, the second field includes a model year and an assembly plant, and the third field includes a secure random number; a processing unit is specifically used to generate a target random number based on a reference field, a preset random number and a preset usage time; a second VIN is generated based on the reference field and the target random number; wherein the reference field includes the first field and the second field, and the length of the target random number is the same as the length of the third field; or, the reference field includes the total length of the first field, the second field and the third field, which is the same as the length of the target random number.
[0067] In one possible design, the processing unit is also used to encode the hash value of the reference field, the preset random number and the preset usage time to obtain the target random number.
[0068] In a possible design, the reference field includes the first field and the second field, and the length of the third field is 6 bytes; the target random number is the first 6 bytes after encoding RAND1, and RAND1 satisfies the following formula:
[0069] RAND1=sha256(VIN[1-11]|Salt|Day)
[0070] Among them, VIN[1-11] is the first field and the second field, Salt is a preset random number, Day is a preset usage time, and sha256 is a hash function.
[0071] In a possible design, the reference field includes the first field, and the total length of the second field and the third field is 8 bytes; the target random number is the first 8 bytes after encoding RAND2, and RAND2 satisfies the following formula:
[0072] RAND2=sha256(VIN[1-9]|Salt|Day)
[0073] Among them, VIN[1-9] is the first field, Salt is the preset random number, Day is the preset usage time, and sha256 is the hash function.
[0074] In one possible design, the processing unit is further used to determine that the second VIN is different from the VINs of other devices within a preset usage time.
[0075] In one possible design, the processing unit is further used to obtain a charging event of a device corresponding to the target PDID, the charging event is used to characterize the charging status of the device corresponding to the target PDID, and the target PDID corresponds to the first VIN; the processing unit is further used to determine that the charging event satisfies a corresponding first preset condition; wherein the charging event includes: the geographic location of the device corresponding to the target PDID, and the corresponding first preset condition includes: the distance between the geographic location of the device corresponding to the target PDID and the power supply device satisfies a preset distance range; and / or, the charging event includes: the state of the charging port of the device corresponding to the target PDID, and the corresponding first preset condition includes: the state of the charging port of the device corresponding to the target PDID is open.
[0076] In one possible design, the processing unit is also used to obtain the status of the device corresponding to the target PDID; the processing unit is also used to instruct the power supply device to stop charging the device to be charged when the status of the device corresponding to the target PDID is a non-charging state.
[0077] In one possible design, the communication unit is further used to receive a charging event encrypted using a private key corresponding to the target PDID; the processing unit is further used to decrypt the charging event based on a public key corresponding to the target PDID.
[0078] In one possible design, the target PDID and the private key corresponding to the target PDID are stored in the chip of the device corresponding to the target PDID; the public key corresponding to the target PDID is stored in the network device.
[0079] In one possible design, the second message includes a battery management system BMS and a vehicle identification message BRM message.
[0080] In the ninth aspect, a device is provided, comprising a processor and a memory, wherein the memory is coupled to the processor, the memory is used to store computer program code, the computer program code comprises computer instructions, and the processor reads the computer instructions from the memory so that the device executes the method as described in the first aspect and any one of the designs thereof, or so that the device executes the method as described in the second aspect and any one of the designs thereof, or so that the device executes the method as described in the third aspect and any one of the designs thereof, or so that the device executes the method as described in the fourth aspect and any one of the designs thereof.
[0081] In one possible design, the device further includes a communication interface, which can be used for the device to communicate with other devices. Exemplarily, the communication interface can be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc.
[0082] In the tenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium including a computer program or instructions. When the computer program or instructions are run on a device, the device executes the method described in the first aspect and any one of the designs thereof, or the device executes the method described in the second aspect and any one of the designs thereof, or the device executes the method described in the third aspect and any one of the designs thereof, or the device executes the method described in the fourth aspect and any one of the designs thereof.
[0083] In the eleventh aspect, a computer program product is provided. When the computer program product is run on a computer, the computer can execute the method as described in the first aspect and any one of the designs thereof, or the computer can execute the method as described in the second aspect and any one of the designs thereof, or the computer can execute the method as described in the third aspect and any one of the designs thereof, or the computer can execute the method as described in the fourth aspect and any one of the designs thereof.
[0084] In the twelfth aspect, a circuit system is provided, which includes a processing circuit, and the processing circuit is configured to execute the method described in any design of the first aspect above, or to execute the method described in any design of the second aspect above, or to execute the method described in any design of the third aspect above, or to execute the method described in any design of the fourth aspect above.
[0085] In the thirteenth aspect, a chip system is provided, comprising at least one processor and at least one interface circuit, wherein the at least one interface circuit is used to perform transceiver functions and send instructions to at least one processor, and when the at least one processor executes the instructions, the at least one processor executes the method as described in the first aspect and any one of the designs therein, or the method as described in the second aspect and any one of the designs therein, or the method as described in the third aspect and any one of the designs therein, or the method as described in the fourth aspect and any one of the designs therein.
[0086] In a fourteenth aspect, a communication system is provided, comprising a first device and a second device, wherein the first device is used to execute the method described in the first aspect, i.e., any one of the designs thereof, and the second device is used to execute the method described in the second aspect, i.e., any one of the designs thereof.
[0087] In a fifteenth aspect, a communication system is provided, comprising a first device and a second device, the first device being used to execute the method described in the third aspect, i.e., any one of the designs thereof, and the second device being used to execute the method described in the fourth aspect, i.e., any one of the designs thereof.
[0088] It should be noted that the technical effects brought about by any design in the above-mentioned fifth to fifteenth aspects can refer to the technical effects brought about by the corresponding design in the first or second aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0089] Figure 1 A schematic diagram of a flow chart of an existing charging method;
[0090] Figure 2 A schematic diagram of a flow chart of another existing charging method;
[0091] Figure 3 A schematic diagram of an interface provided in an embodiment of the present application;
[0092] Figure 4 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;
[0093] Figure 5 A schematic diagram of a charging scenario provided in an embodiment of the present application;
[0094] Figure 6 A schematic diagram of the structure of a charging device provided in an embodiment of the present application;
[0095] Figure 7 A schematic diagram of the structure of another charging device and / or server provided in an embodiment of the present application;
[0096] Figure 8 A schematic diagram of a charging method provided in an embodiment of the present application;
[0097] Fig. 9 A schematic diagram of a flow chart of another charging method provided in an embodiment of the present application;
[0098] Fig.10 A schematic diagram of a flow chart of another charging method provided in an embodiment of the present application;
[0099] Fig.11 A schematic diagram of a frame structure provided in an embodiment of the present application;
[0100] Fig.12 A schematic diagram of a flow chart of another charging method provided in an embodiment of the present application;
[0101] Fig.13 A schematic diagram of a flow chart of another charging method provided in an embodiment of the present application;
[0102] Fig.14 A schematic diagram of the structure of a device provided in an embodiment of the present application;
[0103] Fig.15 A schematic diagram of the structure of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0104] The technical solution provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings.
[0105] The terms "including" and "having" and any variations thereof mentioned in the description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.
[0106] It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.
[0107] In the description of this application, unless otherwise specified, the meaning of "plurality" refers to two or more. "And / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.
[0108] In some scenarios, users can charge their electric vehicles by scanning a QR code on a charging station. Figure 1 FIG. 1 shows a schematic diagram of a conventional charging method. Figure 1 As shown, the method comprises the following steps:
[0109] S101. The terminal device scans the QR code on the charging pile.
[0110] For example, the terminal device may include but is not limited to mobile phones, watches, computers, vehicle-mounted devices, and other terminal devices. For example, the user may use the software installed on the terminal device to scan the QR code on the charging pile. The software may include but is not limited to payment applications, social applications, and various charging applications, applets, etc. In response to the user's scanning operation, the terminal device may start the camera to recognize the QR code on the charging pile.
[0111] It can be understood that the charging pile can be fixed on the ground or wall and installed in various places, such as community parking lots, public building areas, charging stations, etc., to supply power to electric vehicles of different models.
[0112] S102: The terminal device obtains the details of the charging pile.
[0113] For example, the terminal device can obtain the details of the charging pile according to the scanned QR code. For example, the details of the charging pile may include the charging standards and charging rules of the charging pile. The user can determine whether to charge according to the details of the charging pile and choose the corresponding payment method.
[0114] S103: The terminal device receives a charging operation.
[0115] For example, the user can perform a charging operation through the software described in step S101, such as clicking a button to start charging. Accordingly, the terminal device can receive the charging operation. Further, the user can insert the charging gun of the charging pile into the charging port of the electric vehicle to charge the charging car.
[0116] S104. The terminal device sends a charging instruction to the vehicle cloud.
[0117] It is understood that the car cloud can refer to a cloud service deployed by a car manufacturer (ie, a vehicle provider). In some examples, the cloud service can be provided by a server.
[0118] S105. The car cloud sends a charging instruction to the third-party charging service.
[0119] Among them, the car cloud can also send information such as the identification of the charging pile to the third-party charging service. It can be understood that the third-party charging service can refer to the cloud service deployed by the charging pile provider.
[0120] S106. The third-party charging service sends a charging instruction to the charging pile.
[0121] S107. The charging pile charges the electric vehicle.
[0122] S108: The electric vehicle indicates to the charging pile that charging is complete.
[0123] When the charging of the electric vehicle is completed, step S108 may be executed.
[0124] S109. The charging pile indicates to the third-party charging service that charging is complete.
[0125] S110. The third-party charging service generates a charging bill.
[0126] S111. Reconciliation between third-party charging services and Cheyun.
[0127] S112, Cheyun settles the charging fee.
[0128] Rucheyun can settle charging fees according to the payment method selected by the user.
[0129] S113. The car cloud sends a charging bill to the terminal device.
[0130] Correspondingly, after the terminal device receives the charging bill, it can output the charging bill for the user to view.
[0131] In the above-mentioned scanning code charging solution, users need to start the charging operation through the software installed on the terminal device. This process is cumbersome and the user experience is poor. In addition, in some scenarios, others may paste a QR code on the charging pile, resulting in multiple QR codes on the charging pile, which makes it impossible for users to determine which QR code on the charging pile to scan for charging, causing inconvenience to users. In addition, there are currently many vehicle providers and charging pile providers, and QR code recognition needs to adapt to many vehicle providers and charging pile providers.
[0132] Combined with the reasons mentioned above, there are many inconveniences in charging electric vehicles by scanning the QR code on the charging pile. Therefore, in order to bring users a more convenient charging experience. In other scenarios, users can also charge electric vehicles in a plug-and-play manner. For example, Figure 2 A schematic flow chart of another existing charging method is shown.
[0133] like Figure 2 As shown, the method comprises the following steps:
[0134] S201. The terminal device receives a user operation.
[0135] Among them, the user operation can be used to sign a plug-and-charge agreement for the electric vehicle.
[0136] In some examples, users can sign a plug-and-charge agreement for electric vehicles through software installed on terminal devices. For example, take the add intelligence to Auto (AITO) application installed on a mobile phone as an example. Figure 3 A schematic diagram of an interface provided by an embodiment of the present application is shown. Figure 3 As shown, the mobile phone displays the operation interface 300 of the AITO application, wherein the operation interface 300 may include the details of the electric vehicle (such as vehicle 1) that the user has bound in the AITO application, such as: vehicle display name, model, license plate number, frame number, etc. The operation interface 300 includes a plug-and-charge activation button 301, which can be used to sign a plug-and-charge agreement for vehicle 1. Optionally, the operation interface 300 may also include one or more charging payment methods, such as: password-free payment, points payment, bill payment, etc. The user can select a suitable charging payment method according to actual needs, so as to perform payment settlement when charging the electric vehicle in the plug-and-charge mode in the future.
[0137] Exemplarily, the user operation may be, for example, a click operation on the plug and charge activation button 301 .
[0138] S202. In response to a user operation, the terminal device obtains the VIN (hereinafter referred to as VIN) of the electric vehicle.
[0139] S203. The terminal device reports the VIN to the vehicle cloud.
[0140] S204, Cheyun saves the VIN to the whitelist.
[0141] It is understood that the whitelist includes one or more VINs of electric vehicles that have signed the plug-and-charge agreement. Saving the VIN to the whitelist means that the electric vehicle to which the VIN belongs has signed the plug-and-charge agreement. Subsequently, the electric vehicle using the VIN can be charged using the plug-and-charge method.
[0142] S205 . In response to the charging operation, the electric vehicle sends a VIN to the charging pile.
[0143] For example, the charging operation may be an operation in which a user inserts a charging gun of a charging pile into a charging port of an electric vehicle, etc. Specifically, a battery management system (BMS) of the electric vehicle may send a VIN to the charging pile.
[0144] S206: The charging pile sends the VIN to the third-party charging service.
[0145] S207. The third-party charging service confirms with the car cloud whether plug-and-play charging can be adopted according to the VIN.
[0146] S208. The car cloud confirms that the VIN is in the whitelist and returns to the third-party charging service that plug-and-play charging can be used.
[0147] S209. The third-party charging service sends a charging instruction to the charging pile.
[0148] S210: The charging pile starts charging the electric vehicle.
[0149] S211. The third-party charging service sends a charging bill to Cheyun.
[0150] Among them, after the electric vehicle is charged, the third-party charging service can execute step S211.
[0151] S212. Cheyun settles the charging fee according to the charging bill.
[0152] In the above plug-and-charge solution, the BMS of the electric vehicle and the charging pile use the message format specified in the national standard charging protocol to transmit the VIN. The national standard charging protocol is a protocol standard launched to enable cars produced by different manufacturers to be charged on charging piles produced by different manufacturers.
[0153] Exemplarily, Table 1 shows the message format specified by the existing national standard charging protocol.
[0154] Table 1
[0155]
[0156] As shown in Table 1, the message code sent by the charger (i.e., charging pile) to the BMS of the electric vehicle is the charger recognition message (CRM), the parameter group number (PGN) in decimal is 256, the PGN in hexadecimal is 000100H, and the message length is 8 bytes. The message code sent by the BMS of the electric vehicle to the charger is the BMS and vehicle recognition message (BRM), the PGN in decimal is 512, the PGN in hexadecimal is 000200H, and the message length is 41 bytes.
[0157] The VIN sent by the BMS of the electric vehicle to the charging pile is contained in a BRM message with a message length of 41 bytes. For example, Table 2 shows the definition of each byte contained in the BRM message.
[0158] Table 2
[0159]
[0160]
[0161] As shown in Table 2, the suspect parameter number (SPN) corresponding to the bits starting from the 25th byte and having a length of 17 bytes in the BRM message is defined as VIN. In other words, the VIN is located from the 25th byte to the 41st byte in the BRM message.
[0162] In the above-mentioned plug-and-charge solution, charging and deductions are performed by identifying the VIN of the electric vehicle, and the BRM message is transmitted in plain text, that is, the VIN contained in the BRM message is transmitted in plain text. In addition, the VIN is located under the front windshield of the electric vehicle and can be viewed without unlocking the vehicle. Based on the aforementioned reasons, the VIN of an electric vehicle that has signed a plug-and-charge agreement may be misused by other electric vehicles, that is, other electric vehicles may use the VIN of an electric vehicle that has signed a plug-and-charge agreement to charge, which may result in the payment account of the electric vehicle that has signed a plug-and-charge agreement being deducted. The risk of stolen charging is high, which may cause property losses to users.
[0163] A solution is proposed in the related art. When an electric vehicle is charging, the vehicle cloud obtains the corresponding information of the electric vehicle, such as Figure 3 The account of the software installed in the terminal device, such as the registered mobile phone number, is used to verify the electric vehicle to determine whether the electric vehicle is an electric vehicle that has signed a plug-and-charge agreement. However, this solution requires the user to start the software installed on the terminal device before the car cloud can obtain the corresponding account.
[0164] The plug-and-play charging method is to bring users a more convenient charging experience. This solution requires users to actively start the software installed in the terminal device, which adds cumbersome operations, which is obviously contrary to the purpose of adopting the plug-and-play charging method. Therefore, this solution is not suitable for plug-and-play charging scenarios. In addition, this solution requires Cheyun to synchronize the account to the third-party charging service, which will introduce security and privacy risks. Therefore, this solution cannot solve the above technical problems.
[0165] Based on this, an embodiment of the present application provides a charging method that can reduce the risk of electric vehicles being stolen and charged in a plug-and-charge scenario.
[0166] For example, Figure 4 The schematic diagram of the architecture of a communication system for a charging method provided in an embodiment of the present application is shown. Figure 4 As shown, the communication system 400 includes a device to be charged 401 and a power supply device 402 .
[0167] Among them, the device to be charged 401 is a device that receives electricity. Exemplarily, the device to be charged 401 may include, but is not limited to, electric vehicles, augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, vehicle-mounted devices, and / or smart city devices and other devices that need to be charged. Electric vehicles may include, but are not limited to, cars, cars, trucks, motorcycles, buses, ships, airplanes, helicopters, lawn mowers, recreational vehicles, amusement park vehicles, construction equipment, trams, golf carts, trains, and carts, etc., and the embodiments of the present application are not particularly limited.
[0168] The power supply device 402 may be a device that provides power. For example, the power supply device 402 may include, but is not limited to, a charging pile, an on-board charger, an off-board charger, etc., and the present application embodiment does not specifically limit this. In some embodiments, the power supply device 402 needs to be paid for use.
[0169] In some embodiments, the above-mentioned device to be charged 401 can receive power from the power supply device 402 by communicating with the power supply device 402. The message format transmitted during the communication between the device to be charged 401 and the power supply device 402 can adopt the message format specified by the national standard charging protocol described above. For example, taking the device to be charged 401 as an electric car and the power supply device 402 as a charging pile, Figure 5 A schematic diagram of a charging scenario provided by an embodiment of the present application is shown. Figure 5 As shown, an electric car 501 is charged at a charging station, which includes one or more charging posts 502. A charging gun 503 of the charging post 502 can be inserted into a charging port of the electric car 501 to charge the electric car 501.
[0170] In some embodiments, the communication system 400 may further include a terminal device 403. The terminal device 403 may be used to implement the operation of charging the device to be charged 401 through the power supply device 402. For example, the terminal device 403 may scan the QR code on the power supply device 402 to start the power supply device 402 to charge the device to be charged 401. For another example, the terminal device 403 may be used to sign a plug-and-charge agreement for the device to be charged 401, and subsequently start the power supply device 402 to charge the device to be charged 401 through the plug-and-charge method.
[0171] Exemplarily, the terminal device 403 may include, but is not limited to, a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, a netbook, a personal digital assistant (PDA), an artificial intelligence (AI) device, a wearable device, a vehicle-mounted device, and / or a smart home device. The embodiments of the present application do not impose any special restrictions on the specific type of the terminal device 403.
[0172] Optionally, the operating system installed on the above-mentioned charging device 401, and / or the power supply device 402, and / or the terminal device 403 includes but is not limited to Or other operating systems. Of course, the device to be charged 401, and / or the power supply device 402, and / or the terminal device 403 may not have an operating system installed. In some embodiments, the device to be charged 401, and / or the power supply device 402, and / or the terminal device 403 may be a fixed device or a portable device. This application does not limit the specific type of the device to be charged 401, and / or the power supply device 402, and / or the terminal device 403, whether an operating system is installed, and the operating system installed under the installed operating system.
[0173] In some embodiments, the communication system 400 may also include one or more servers (or network devices, etc., three of which are shown in the figure, such as server 404, server 405, and server 406, etc.). The server may be a device or server with computing functions such as a cloud server or a network server. The server may be a single server, or a server cluster consisting of multiple servers, or a cloud computing service center. Optionally, the server's operating system includes but is not limited to Or other operating systems. This application does not impose any restrictions on the specific type of server and the installed operating system.
[0174] Exemplarily, the server 404 may be a server corresponding to the device 401 to be charged. For example, it may be a server deployed by a provider of the device 401 to be charged, so as to provide cloud services to the device 401 to be charged. The server 405 may be a server corresponding to the power supply device 402. For example, it may be a server deployed by a provider of the power supply device 402, so as to provide cloud services to the power supply device 402. The server 406 may be a server corresponding to the terminal device 403, and may specifically be a server corresponding to the software installed in the terminal device 403. For example, it may be a server deployed by a software provider installed in the terminal device 403, so as to provide cloud services to the software installed in the terminal device 403. Exemplarily, the software installed in the terminal device 403 may include, but is not limited to, payment applications, social applications, or other charging applications, applets, etc. Optionally, the terminal device 403 may implement functions such as charging the device 401 to be charged through the power supply device 402 as described above through the software.
[0175] In some embodiments, the server 404 and the service 406 may be separately provided. In other embodiments, the server 404 and the service 406 may be integrated together.
[0176] Optionally, the above-mentioned servers, the servers and the corresponding devices, and the different devices can establish communication connections through wired communication technology and / or wireless communication technology. Exemplarily, the wireless communication technology includes but is not limited to at least one of the following: near field communication (NFC), Bluetooth (BT) (for example, traditional Bluetooth or Bluetooth low energy (BLE)), wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Zigbee, frequency modulation (FM), infrared (IR), wide area network transferred by relay devices, etc.
[0177] Exemplarily, when the wireless communication technology is the above-mentioned wide area network, the wireless communication technology can be a third-generation mobile communication technology (3rd-generation wireless telephone technology, 3G) network, a fourth-generation mobile communication technology (the 4th generation mobile communication technology, 4G) network, a fifth-generation mobile communication technology (5th-generation mobile communication technology, 5G) network, a future evolved public land mobile network (public land mobile network, PLMN) or the Internet, etc.
[0178] Optional, Figure 4 The simplified schematic diagram is provided for ease of understanding. In actual applications, the above system may further include other devices which are not shown in the figure.
[0179] For example, Figure 6 (1) shows a schematic diagram of the structure of a charging device 401 provided in an embodiment of the present application. Figure 6 As shown in (1), the device to be charged 401 may include a processor 601, a memory 602, a communication module 603, a positioning module 604, a battery management system (BMS) module 605, a charging management module 606, a battery 607, a device management module 608, etc.
[0180] The processor 601 may include one or more processing units, for example, the processor 601 may include an application processor (AP), a modem processor, an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.
[0181] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.
[0182] A memory may also be provided in the processor 601 for storing instructions and data. In some embodiments, the memory in the processor 601 is a cache memory. The memory may store instructions or data that the processor 601 has just used or cyclically used. If the processor 601 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 601, and thus improves the efficiency of the system.
[0183] The memory 602 can be used to store computer executable program codes, which include instructions. The memory 602 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function), etc. The data storage area may store data created during the use of the device to be charged 401, etc. In addition, the memory 602 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (universal flash storage, UFS), etc. The processor 601 executes various functional applications and data processing of the device to be charged 401 by running instructions stored in the memory 602, and / or instructions stored in a memory provided in the processor 601.
[0184] In some embodiments of the present application, a device certificate of the device to be charged 401 is stored in the memory 602. It is understood that the device certificate is a file issued by a certificate authority or an official agency, which can authenticate the identity of the device to be charged 401. It is understandable that for different devices to be charged, the device certificates they have are different. Among them, the device certificate contains a product device identification (PDID). In some embodiments, the device certificate may also include a private key corresponding to the PDID. Among them, the private key can be used to encrypt data transmitted from the device to be charged 401 to other devices to ensure information security. In some embodiments, the PDID and the private key corresponding to the PDID are stored in the hardware security domain of the device to be charged 401, such as a chip, and the private key cannot be read out and cannot be tampered with.
[0185] In other embodiments of the present application, one or more dynamic VINs may also be stored in the memory 602, and the dynamic VIN may be used to charge the device 401 to be charged in a plug-and-play manner. In some examples, the dynamic VIN may be generated by the server 406 according to the VIN of the device 401 to be charged and sent to the device 401 to be charged. Optionally, the server 406 and the device 401 to be charged may communicate directly or forward the communication through other devices. In other examples, the dynamic VIN may be generated by the server 404 according to the VIN of the charging device 401 and sent to the device 401 to be charged. Please refer to the following description for the specific implementation of generating the dynamic VIN.
[0186] The communication function of the device to be charged 401 can be realized through the antenna and the communication module 603 .
[0187] The communication module 603 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the device to be charged 401. The communication module 603 can be one or more devices integrating at least one communication processing module. The communication module 603 receives electromagnetic waves via an antenna, modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 601. The communication module 603 can also receive the signal to be sent from the processor 601, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna.
[0188] In some embodiments of the present application, the communication module 603 can communicate with the server 404 and send the charging event of the device to be charged 401 to the server 404. For an introduction to the charging event, please refer to the following description.
[0189] The positioning module 604 may be used to estimate the geographical location of the device to be charged 401, and realize the function of positioning the device to be charged 401. Exemplarily, the positioning module 604 may be a global positioning system (GPS), or a Beidou system or other positioning systems.
[0190] The charging management module 606 is used to receive charging input from the power supply device. While the charging management module 606 charges the battery 607, it can also power the device to be charged 401 through the BMS module 605. In some embodiments of the present application, the charging management module 606 includes a charging port of the device to be charged 401 and its auxiliary devices.
[0191] The BMS module 605 can be connected to the battery 607, the charging management module 606, the processor 601, etc. The BMS module 605 receives input from the battery 607 and / or the charging management module 606, and supplies power to the processor 601, the memory 602, the communication module 603, etc. The BMS module 605 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the BMS module 605 can also be set in the processor 601. In some other embodiments, the BMS module 605 and the charging management module 606 can also be set in the same device.
[0192] The device management module 608 is a controller of the device to be charged 401, and can provide communication and remote control functions for the device to be charged 401. Exemplarily, the device management module 608 can be a telematics box (T-BOX) or the like.
[0193] For example, Figure 6 (2) shows a schematic diagram of the structure of a server 404 provided in an embodiment of the present application. Figure 6 As shown in (2), the server 404 may include a memory 611, a charging service module 612, a data collection module 613, and a device authentication module 614. Optionally, the server 404 may also include a dynamic VIN generation module 615 and the like.
[0194] In some embodiments, the memory 611 may store the PDID contained in the device certificate of one or more devices to be charged and the public key corresponding to the PDID. Among them, the public key corresponding to the PDID and the private key stored in the corresponding device to be charged constitute a key pair. It can be understood that for a key pair consisting of a public key and a private key, if the data is encrypted with the private key in the key pair, the public key in the key pair is required to decrypt the data. Similarly, if the data is encrypted with the public key in the key pair, the private key in the key pair is required to decrypt the data. The memory 611 also stores the mapping relationship between the PDID and the VIN of the device to be charged.
[0195] In some other embodiments, the memory 611 may also store one or more dynamic VINs, which may be generated by the server 406 according to the VIN of the device to be charged and sent to the server 404, or may be generated by the server 404. The memory 611 may also store a mapping relationship between the dynamic VIN of the device to be charged and the VIN.
[0196] For other functions of memory 611, please refer to Figure 6 Introduction of memory 602 shown in (1).
[0197] The charging service module 612 can provide various services such as signing a plug-and-charge agreement, charging, charging fee payment, and password-free payment charging for the device to be charged. It can also be used to query and determine the status of the device to be charged, such as: geographical location, whether it is in a charging state, whether the charging port is open, charging progress, etc. In some examples, the charging service module 612 can obtain corresponding data from the data acquisition module 613 and perform corresponding judgment operations.
[0198] In some embodiments, the charging service module 612 can also be implemented as two modules. One module is used to provide various services such as signing a plug-and-charge agreement, charging, charging fee payment, and password-free payment charging. The other module is used to query and determine the status of the device to be charged.
[0199] The data collection module 613 may be used to receive and store charging events reported by the device to be charged, and report the charging events to other modules, such as but not limited to the charging service module 612 .
[0200] The device authentication module 614 can be used to receive charging events reported by the device to be charged, and authenticate the identity of the device to be charged to confirm whether the identity of the device to be charged is legal. For example: when the device authentication module 614 receives the PDID reported by the device to be charged and the charging event data encrypted using the private key corresponding to the PDID, the device authentication module 614 can obtain the public key corresponding to the PDID from the memory 611, and use the public key to decrypt the encrypted data. If the decryption is successful, the device authentication module 614 can obtain the charging event and determine that the identity of the device to be charged is legal. Optionally, the device authentication module 614 can also send the decrypted charging event to the data acquisition module 613 for storage.
[0201] The dynamic VIN generation module 615 may be used to generate one or more dynamic VINs of the device to be charged, and the dynamic VIN may be used to charge the device to be charged in a plug-and-play manner.
[0202] It can be understood that this embodiment takes the example that the dynamic VIN generation module 615 is located in the server 404. The dynamic VIN generation module 615 can also be located in the server 406.
[0203] Understandably, Figure 6 The structures of the charging device 401 and the server 404 shown are only exemplary and do not constitute limitations of the present application. Figure 7 A schematic diagram of the structure of another device to be charged 401 and / or server 404 provided in an embodiment of the present application is shown. The device to be charged 401 and / or server 404 includes at least one processor 701 , a communication line 702 , a memory 703 and at least one communication interface 704 .
[0204] The processor 701 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.
[0205] The communication link 702 may include a pathway to transmit information between the above-mentioned components.
[0206] Communication interface 704, used to communicate with other devices. In the embodiment of the present application, the communication interface can be a module, a circuit, a bus, an interface, a transceiver or other device capable of implementing a communication function, used to communicate with other devices. Optionally, when the communication interface is a transceiver, the transceiver can be an independently arranged transmitter, which can be used to send information to other devices, and the transceiver can also be an independently arranged receiver, which is used to receive information from other devices. The transceiver can also be a component that integrates the functions of sending and receiving information, and the embodiment of the present application does not limit the specific implementation of the transceiver.
[0207] The memory 703 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 703 may exist independently and be connected to the processor 701 via the communication line 702. The memory 703 may also be integrated with the processor 701.
[0208] The memory 703 is used to store computer-executable instructions for implementing the solution of the present application, and the execution is controlled by the processor 701. The processor 701 is used to execute the computer-executable instructions stored in the memory 703, thereby implementing the method provided in the embodiment of the present application.
[0209] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, instructions, computer program or other names, which are not specifically limited in the embodiments of the present application.
[0210] In a specific implementation, as an embodiment, the processor 701 may include one or more CPUs, such as Figure 7 CPU0 and CPU1 in.
[0211] In a specific implementation, as an embodiment, the device to be charged 401 and / or the server 404 may include multiple processors, such as Figure 7 701 and processor 705 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).
[0212] The above-mentioned device to be charged 401 and / or server 404 can be a general device or a dedicated device. The embodiment of the present application does not limit the type of the device to be charged 401 and / or server 404. Figure 7 Devices of similar structure.
[0213] It is understandable that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the device to be charged 401 and / or the server 404. In other embodiments of the present application, the device to be charged 401 and / or the server 404 may include Figure 6 , Figure 7 More or fewer components are shown, or some components are combined, or some components are separated, or different component arrangements are arranged. The components shown can be implemented in hardware, software, or a combination of software and hardware.
[0214] Optional, for Figure 4 The structures of other devices shown, such as but not limited to the terminal device 403, the server 406, etc., can be referred to respectively. Figure 6 , Figure 7 The structure of the device to be charged 401, the server 404, etc. is shown in FIG. Optionally, the terminal device 403, the server 406, etc. may include Figure 6 , Figure 7 The device to be charged 401, the server 404, etc. shown in the figure may be more or less components, or some components may be combined, or some components may be separated, or different component arrangements may be made. The components may be implemented in hardware, software, or a combination of software and hardware.
[0215] The technical solutions involved in the following embodiments can all be Figure 6 , Figure 7 The device of the structure shown, and Figure 4 The system is implemented in the system with the architecture shown.
[0216] It can be understood that in the following embodiments, the device to be charged 401, the power supply device 402, the terminal device 403, and the server 404 are described as the device to be charged, the power supply device, the terminal device, and the server, respectively. The device to be charged, and / or the power supply device, and / or the server, etc. can perform some or all of the steps in the embodiments of the present application. These steps or operations are only examples. The embodiments of the present application can also perform other operations or variations of various operations. In addition, the various steps can be performed in different orders presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.
[0217] In some embodiments, when the server receives the VIN reported by the device to be charged, it can determine the corresponding PDID according to the VIN, and then obtain the charging event of the real device to be charged corresponding to the VIN according to the PDID, and then determine whether to charge the device to be charged that reports the VIN according to the charging event. For example: when the charging event of the real device to be charged meets the first preset condition, it is determined to charge the device to be charged that reports the VIN. When the charging event of the real device to be charged does not meet the first preset condition, it is determined not to charge the device to be charged that reports the VIN. In this way, since the PDID of each device to be charged is unique and cannot be tampered with. Therefore, by identifying the real device to be charged corresponding to the VIN through the PDID, the charging event of the real device to be charged can reflect whether the device to be charged that reports the VIN is the real device to be charged, and then determine whether to charge the device to be charged that reports the VIN. It can avoid the situation where a third party counterfeits the VIN for charging, reduce the risk of stolen charging of devices to be charged, such as electric vehicles, in plug-and-play scenarios, and improve charging safety.
[0218] In this embodiment, Figure 8 FIG. 1 is a flow chart of a charging method provided by an embodiment of the present application. Figure 8 As shown, the method comprises the following steps:
[0219] S801: The device to be charged receives a charging operation.
[0220] The charging operation may be used to start the power supply device to charge the device to be charged. For example, the charging operation may include but is not limited to the operation of inserting a charging gun of the power supply device into the charging port of the device to be charged.
[0221] In some embodiments, before the device to be charged executes step S801, the device to be charged may sign a plug-and-charge agreement to charge in a plug-and-charge manner. For example, the device to be charged may send a request message including a VIN to the server to request to sign the plug-and-charge agreement. Accordingly, after the server receives the VIN, it may save it to the whitelist. In this way, the device to be charged has signed a plug-and-charge agreement. Exemplarily, the plug-and-charge agreement may be signed for the device to be charged by software installed on the terminal device. For the implementation of signing the plug-and-charge agreement, please refer to Figure 3 The relevant introduction described above.
[0222] S802: In response to the charging operation, the device to be charged sends a VIN to the power supply device. Correspondingly, the power supply device receives the VIN from the device to be charged.
[0223] It is understood that in the embodiment of the present application, the VIN sent by the device to be charged to the power supply device can be carried in the charging request message, and the charging request message is used to start the charging device to charge the device to be charged. Please refer to the above for the introduction of VIN.
[0224] S803: The power supply device sends a VIN to the server. Correspondingly, the server receives the VIN from the power supply device.
[0225] Optionally, the power supply device and the server may communicate directly or forward the communication through other devices, such as the power supply device may communicate through Figure 4 The server 405 sends the VIN to the server 404 and so on.
[0226] S804: The server determines whether the VIN is in the whitelist.
[0227] If it is in the white list, then execute step S805 and step S806. If it is not in the white list, then execute step S808.
[0228] The whitelist includes one or more VINs of the devices to be charged that have signed the plug-and-charge agreement. If the VIN is in the whitelist, it means that the device to be charged to which the VIN belongs has signed the plug-and-charge agreement, that is, the device to be charged can be charged using the plug-and-charge method. Otherwise, it means that the device to be charged to which the VIN belongs has not signed the plug-and-charge agreement, that is, the device to be charged cannot be charged using the plug-and-charge method.
[0229] In some embodiments, the server may perform this step, for example, the white list is stored in the server. In other embodiments, the server may not perform this step, for example, when the white list is stored in the server 405, the server 405 may directly determine whether the VIN is in the white list. If it is in the white list, the VIN is sent to the server 404, otherwise, the VIN is not sent to the server 404.
[0230] S805: The server obtains the charging event of the PDID corresponding to the VIN.
[0231] In some embodiments, a mapping relationship between VIN and PDID is stored in the server, and the server can determine the PDID corresponding to the VIN based on the VIN and the mapping relationship described in step S803. Furthermore, the server can obtain the charging event of the corresponding device to be charged based on the determined PDID. The device to be charged corresponding to the PDID is also the real device to be charged to which the VIN belongs. The device to be charged corresponding to the PDID is described as the real device to be charged below. The charging event of the real device to be charged can be used to characterize the charging status of the real device to be charged, such as: whether it is being charged, etc.
[0232] Exemplarily, the charging event may include, but is not limited to, one or more of the geographical location of the actual device to be charged, the state of the charging port of the actual device to be charged, and the state of the actual device to be charged.
[0233] In some embodiments, the server may directly or indirectly receive a charging event from a real device to be charged.
[0234] For example, the server can directly send a message requesting a charging event to the real device to be charged, and accordingly, after receiving the message, the real device to be charged can directly report the charging event to the server. For example, the real device to be charged can report the charging event to the server through a telematics service provider (TSP) channel or other channels.
[0235] For another example: the server can directly send a message requesting a charging event to the real device to be charged. Correspondingly, after receiving the message, the real device to be charged can send the charging event to the terminal device, which will report it to the server. Optionally, in this example, in order to facilitate the terminal device to determine which server to report the charging event to, the real device to be charged can send the server's identifier, the server's address, etc. to the terminal device, so that the terminal device can report the charging event. Optionally, in this example, there can also be a binding relationship between the terminal device and the real device to be charged, so that the real device to be charged can determine which terminal device to send the charging event to. For example: the terminal device and the real device to be charged can be bound through an AITO application such as the one described above.
[0236] For another example: the server can send a message to the terminal device requesting a charging event. Correspondingly, the terminal device can obtain the charging event from the real device to be charged according to the message, and then the terminal device sends the obtained charging event to the server. Optionally, in this example, binding relationships can be established between the server and the terminal device, and between the terminal device and the device to be charged. For example, the server can store the identifier of the terminal device corresponding to the PDID, or the identifier of the terminal device corresponding to the VIN, etc. The identifier of the terminal device can be a mobile phone number, a Huawei account, etc. In this way, the server can determine which terminal device to send the message requesting a charging event. Similarly, the terminal device and the real device to be charged can also be bound through the AITO application described above.
[0237] For another example: the server can send a message to the terminal device requesting a charging event, and accordingly, the terminal device can instruct the real device to be charged to report the charging event to the server according to the message. Accordingly, after receiving the instruction from the terminal device, the real device to be charged can report the charging event to the server. Optionally, in this example, a binding relationship such as that described in the previous example can be established between the server and the terminal device, and between the terminal device and the device to be charged. Optionally, the terminal device can also send the server's identifier, the server's address, etc. to the real device to be charged, so that the real device to be charged can determine which server to send the charging event to.
[0238] Specifically, in the above example, when the real device to be charged or the terminal device reports the charging event to the server, the private key corresponding to the PDID can be used to encrypt the charging event. Correspondingly, when the server receives the charging event, it can decrypt the received charging event according to the public key corresponding to the PDID. If the decryption is successful, the server can successfully obtain the charging event of the PDID corresponding to the VIN, which means that the charging event is reported by the real device to be charged corresponding to the VIN, and not by the real device to be charged that impersonates the VIN.
[0239] Optionally, in the above example, the real device to be charged or the terminal device can report multiple charging events to the server simultaneously, or can report charging events to the server one by one. The real device to be charged or the terminal device can report the PDID of the real device to be charged while reporting the charging event.
[0240] Optionally, the charging event can be reported to the server in real time or periodically by the actual device to be charged or the terminal device, or it can be reported to the server by the actual device to be charged or the terminal device after step S801. The embodiment of the present application does not impose any limitation on the timing when the actual device to be charged or the terminal device reports the charging event to the service.
[0241] S806: The server determines whether the charging event meets a first preset condition.
[0242] If the conditions are met, the process goes to step S807. If the conditions are not met, the process goes to step S808.
[0243] Exemplarily, when the charging event is the geographic location of the real device to be charged, the first preset condition may include: the distance between the real device to be charged and the power supply device meets the preset distance range (such as less than or equal to the preset distance threshold, etc.). For example, taking into account the error in the geographic location reported by the real device to be charged, the distance between the real device to be charged and the power supply device when they can complete the plug-and-play operation, and other factors. Exemplarily, the preset distance threshold can be set to 200 meters. Of course, the preset distance threshold can also be set to other distances, and the preset distance threshold can be set by the developer according to actual needs.
[0244] In this way, the distance between the real device to be charged and the power supply device is identified by the geographic location. When the distance meets the preset distance range, it means that the real device to be charged and the power supply device are in the same location. Then the device to be charged with the reported VIN may indeed be a real charging device, and then it is possible to charge the device to be charged with the reported VIN. The difficulty of unauthorized charging is increased, and the risk of the device to be charged, such as electric vehicles, being charged by theft can be reduced, and charging safety can be improved.
[0245] When the charging event is the state of the charging port of the real device to be charged, the first preset condition may include: the state of the charging port of the real device to be charged is in an open state. In this way, by identifying the state of the charging port of the real device to be charged, when it is in an open state, it means that the real device to be charged may indeed need to be charged. That is, the device to be charged with the reported VIN may be the real device to be charged. In addition, other people may not be able to open the charging port of the real device to be charged without the key, which can further illustrate that the device to be charged with the reported VIN may be the real device to be charged, and then it is possible to charge the device to be charged with the reported VIN. The difficulty of stealing charging is increased, the risk of stolen charging of devices to be charged, such as electric vehicles, etc., can be reduced, and charging safety is improved.
[0246] When the charging event is the state of the real device to be charged, the first preset condition may include: after the power supply device starts charging, the real device to be charged is in the charging state. In this way, after the power supply device is started to charge the device to be charged that reports the VIN, by identifying the state of the real device to be charged, if it is in the charging state. It means that the device to be charged that reports the VIN is indeed the real device to be charged. Then continue to charge the device to be charged, which increases the difficulty of stealing charging, can reduce the risk of stolen charging of the device to be charged, such as electric vehicles, and improve charging safety.
[0247] It can be understood that, when including the above-mentioned multiple charging events, the charging event meeting the first preset condition can mean that each charging event meets the corresponding first preset condition. Conversely, if some charging events do not meet the corresponding first preset condition, it can be determined that the charging event does not meet the first preset condition.
[0248] Optionally, the above step S804 and step S806 may be executed simultaneously or sequentially. When they are executed sequentially, the present application does not limit the order.
[0249] S807: The server instructs the power supply device to charge the device to be charged. Correspondingly, after receiving the instruction, the power supply device charges the charging device.
[0250] Optionally, after the charging device is finished charging, the server may use Figure 1 , Figure 2 The charging fee is settled in the manner shown.
[0251] S808: The server instructs the power supply device not to charge the device to be charged. Correspondingly, after receiving the instruction, the power supply device does not charge the device to be charged.
[0252] In some embodiments, the power supply device not charging the device to be charged may mean that the power supply device does not charge the device to be charged. In other embodiments, the power supply device not charging the device to be charged may mean that the power supply device stops charging the device to be charged after charging the device to be charged for a short time.
[0253] In some embodiments, when the server identifies that the device to be charged is charging by using a VIN fraudulently, for example, when the server determines that the charging event does not meet the first preset condition, it can be determined that the device to be charged is charging by using a VIN fraudulently. For another example, when the server determines that the device to be charged is already in a charging state, it still receives a charging request with the same VIN as the device to be charged, and it can be determined that the device to be charged is charging by using a VIN fraudulently.
[0254] At this time, the server can start the alarm function, for example: notify the power supply equipment to collect various information such as the license plate number of the device to be charged, the owner's image, etc., and warn the owner of "your current charging behavior is detected to be illegal, please stop immediately" and so on. Another example: notify the operator to stop the illegal charging behavior on site. In order to achieve a deterrent effect and reduce the probability of subsequent illegal charging. Another example: notify the user of the real device to be charged through the terminal device that there may be someone else's illegal charging, and remind the user to close the password-free payment of charging fees in time to protect the user's property safety.
[0255] It can be understood that the above embodiment is based on the example of the server executing the above steps S803 to S808, etc. In other embodiments, one or more of the above steps S803 to S808, etc., and other operations performed by the server, such as starting the alarm function, etc., can also be performed by the terminal device. Optionally, in this embodiment, when the terminal device executes step S803, in order to facilitate the power supply device to determine which terminal device to send the received VIN, the power supply device (or the server corresponding to the power supply device, such as Figure 4 A binding relationship can be established between the server 405 shown and the terminal device. For example, the power supply device can store the identifier of the terminal device corresponding to the VIN. The identifier of the terminal device can be such as a mobile phone number, a Huawei account, etc. In this way, the power supply device can determine which terminal device to send the VIN to.
[0256] Optionally, in this embodiment, in order to facilitate the terminal device to determine which device to be charged to obtain the charging event, a binding relationship may be established between the terminal device and the real device to be charged corresponding to the VIN, such as by establishing a binding relationship through the AITO application described above.
[0257] In some examples, similar to the implementation of step S805 performed by the server, the terminal device may also store a mapping relationship between VIN and PDID, that is, the terminal device may be bound to multiple devices to be charged. The terminal device determines the PDID corresponding to the VIN based on the mapping relationship, and then obtains the charging event of the real device to be charged corresponding to the PDID.
[0258] In other examples, the terminal device may only bind a single device to be charged, which is the real device to be charged corresponding to the VIN sent by the power supply device to the terminal device. In this way, after receiving the VIN sent by the power supply device, the terminal device can obtain the charging event of the currently bound single device to be charged.
[0259] Optionally, in this embodiment, the power supply device and the terminal device may communicate directly or through other devices, such as Figure 4 The server 405 etc. shown forwards the communication.
[0260] Combination Figure 4 as well as Figure 6 The architecture shown is a specific embodiment. Fig. 9 FIG. 2 shows a flow chart of another charging method provided by an embodiment of the present application. Fig. 9 As shown, the method comprises the following steps:
[0261] S901, the communication module of the device to be charged (hereinafter referred to as the communication module) reports the geographical location and the PDID of the device to be charged to the device authentication module (hereinafter referred to as the device authentication module) of the server 404. Correspondingly, the device authentication module receives the geographical location and PDID from the communication module.
[0262] Optionally, the number of the devices to be charged may be one or more. It is understood that before the devices to be charged adopt the plug-and-play charging method, they can report their own geographical location and PDID to the device authentication module in real time or periodically through the communication module.
[0263] In some embodiments, the device to be charged can use the private key corresponding to its own PDID to encrypt the reported geographical location, and then send the encrypted data to the device authentication module through the communication module. Correspondingly, the device authentication module can use the public key corresponding to the PDID of the device to be charged to decrypt the encrypted data, and then obtain the decrypted geographical location.
[0264] In some embodiments, the device authentication module may send the decrypted geographic location and the corresponding PDID to a data collection module (hereinafter referred to as the data collection module) of the server 404 for storage.
[0265] It can be understood that this embodiment takes the example that the server 404 receives the geographical location reported by the device to be charged before the device to be charged is charged. The server 404 may also receive the geographical location reported by the device to be charged at other times.
[0266] S902 . In response to the charging operation, the power supply device and the BMS module of the first device to be charged (hereinafter referred to as the BMS module) perform a charging handshake.
[0267] For an introduction to the charging operation, please refer to the above description.
[0268] It can be understood that if the first device to be charged is a device that uses a fake VIN to charge, then the first device to be charged is not the device to be charged described in step S901. Otherwise, the first device to be charged is the device to be charged described in step S901.
[0269] S903: The BMS module executes a charging response and sends a VIN to the power supply device.
[0270] It can be understood that after executing step S902 and step S903, a communication link is established between the power supply device and the BMS module, and data can be transmitted between the power supply device and the BMS module through the communication link. For example, the BMS module reports the VIN to the power supply device through the communication link.
[0271] S904: The power supply device sends the VIN to the server 405. Correspondingly, the server 405 receives the VIN from the power supply device.
[0272] S905 , the server 405 sends the VIN to the charging service module (hereinafter referred to as the charging service module) of the server 404 . Correspondingly, the charging service module receives the VIN from the server 405 .
[0273] S906: The charging service module determines whether the VIN is in the whitelist.
[0274] If it is in the white list, that is, the VIN is a VIN that has signed the plug-and-charge agreement, then execute step S907. If it is not in the white list, that is, the VIN is not a VIN that has signed the plug-and-charge agreement, then execute step S916. Please refer to the above for the introduction of the white list.
[0275] S907: The charging service module obtains the geographic location corresponding to the target PDID from the device authentication module.
[0276] The target PDID is the PDID corresponding to the VIN reported by the first device to be charged. For the method of determining the target PDID according to the VIN reported by the first device to be charged, reference may be made to the relevant introduction of the above step S805.
[0277] It can be understood that the geographic location corresponding to the target PDID is the geographic location reported by the second device to be charged, and the second device to be charged is the device to be charged described in step S901. If the VIN reported by the first device to be charged is its own, the first device to be charged and the second device to be charged are the same. If the VIN reported by the first device to be charged is fake, the first device to be charged and the second device to be charged are not the same.
[0278] In some examples, if the device authentication module sends the PDID of the device to be charged and the corresponding geographic location to the data acquisition module for storage, the charging service can also directly obtain the geographic location corresponding to the target PDID from the data acquisition module.
[0279] S908. The charging service module determines whether the distance between the geographical location corresponding to the target PDID and the power supply device meets a preset distance range.
[0280] In some embodiments, since the device to be charged will report its geographic location in real time or periodically, there may be multiple geographic locations corresponding to the target PDID. In this embodiment, the charging service module can determine whether the distance between the geographic location corresponding to the target PDID and the reporting time closest to the current time and the power supply device meets the preset distance range.
[0281] Please refer to the above for an introduction to the preset distance range.
[0282] If the preset distance range is met, step S909 is executed. If the preset distance range is not met, step S916 is executed.
[0283] S909: The charging service module obtains the status of the charging port corresponding to the target PDID from the device authentication module.
[0284] It can be understood that the state of the charging port corresponding to the target PDID is also the state of the charging port of the second device to be charged.
[0285] In some embodiments, the device authentication module can obtain the status of the charging port of the second device to be charged through the communication module. For example, the second device to be charged can use the private key corresponding to its own PDID to encrypt the status of the charging port, and then send the encrypted data to the device authentication module through the communication module. Correspondingly, the device authentication module can use the public key corresponding to the PDID of the second device to be charged to decrypt the encrypted data, and then obtain the decrypted status of the charging port.
[0286] In some embodiments, the device authentication module can send the decrypted status of the charging port and the corresponding PDID to the data acquisition module for storage. The charging service module can also directly obtain the status of the charging port corresponding to the target PDID from the data acquisition module.
[0287] S910. The charging service module determines whether the charging port corresponding to the target PDID is in an open state.
[0288] Optionally, step S906, step S908 and step S910 may be performed simultaneously or sequentially. In the case of sequential execution, the present application does not limit the sequence.
[0289] If it is in the open state, then execute step S911 to step S915. If it is not in the open state, then execute step S916.
[0290] S911 . The charging service module sends a command to the server 405 to start charging.
[0291] It can be understood that the instruction to start charging can be used to start the power supply device to charge the first device to be charged.
[0292] S912. The server 405 sends a command to the power supply device to start charging.
[0293] S913: The power supply device starts charging the BMS module.
[0294] S914. The charging service module obtains the status corresponding to the target PDID from the device authentication module.
[0295] It can be understood that the state corresponding to the target PDID is also the state of the second device to be charged.
[0296] In some embodiments, the device authentication module can obtain the status of the second device to be charged through the communication module. For example, the second device to be charged can use the private key corresponding to its own PDID to encrypt the status, and then send the encrypted data to the device authentication module through the communication module. Correspondingly, the device authentication module can use the public key corresponding to the PDID of the second device to be charged to decrypt the encrypted data, and then obtain the decrypted status.
[0297] In some embodiments, the device authentication module can send the decrypted status and the corresponding PDID to the data acquisition module for storage. The charging service module can also directly obtain the status corresponding to the target PDID from the data acquisition module.
[0298] S915. The charging service module determines whether the state corresponding to the target PDID is a charging state.
[0299] If yes, the charging service module may not process. Alternatively, the charging service module may instruct the power supply device to continue charging the first device to be charged. If no, that is, the state corresponding to the target PDID is a non-charging state, then step S916 is executed.
[0300] S916: The charging service module instructs the power supply device not to charge the first device to be charged.
[0301] It can be understood that before the power supply device starts charging the first device to be charged, if the charging service module executes step S916, then the power supply device does not charge the first device to be charged after receiving the instruction. After the power supply device starts charging the first device to be charged, if the charging service module executes step S916, then the power supply device stops charging the first device to be charged after receiving the instruction.
[0302] In other embodiments, the device to be charged can be charged using a randomly generated dynamic VIN. Since the dynamic VIN is randomly generated, the probability that a third party can impersonate the dynamic VIN is low. Therefore, the risk of the device to be charged, such as an electric vehicle, being stolen and charged in a plug-and-play scenario can be reduced.
[0303] In this embodiment, Fig.10 FIG. 2 shows a flow chart of another charging method provided by an embodiment of the present application. Fig.10 As shown, the method comprises the following steps:
[0304] S1001: The device to be charged receives a charging operation.
[0305] For the introduction of this step, please refer to the relevant introduction of step S801.
[0306] S1002: In response to the charging operation, the device to be charged sends a dynamic VIN to the power supply device. Correspondingly, the power supply device receives the dynamic VIN from the device to be charged.
[0307] In some embodiments, the dynamic VIN is dynamically generated. The dynamic VIN is used to start the device to be charged to charge the power supply device. As a possible implementation, the dynamic VIN can be generated according to at least one of the VIN, a preset random number, and a preset usage time. It can be understood that the preset random number can be a set of random strings pre-set by the developer, which may include one or more of random uppercase and lowercase letters, numbers, characters, etc. In some embodiments, when the dynamic VINs of different devices to be charged are generated according to the preset random numbers, the preset random numbers corresponding to different devices to be charged may be the same.
[0308] It can also be understood that the dynamic VIN is valid within the corresponding preset usage time, that is, within the preset usage of the dynamic VIN, the device to be charged can use the dynamic VIN for charging. For example: if the preset usage time of the dynamic VIN is April 4, 2023, then the dynamic VIN is only valid when used on April 4, 2023, and is invalid when used at other times. Optionally, the length of the preset usage time can be one day, 2 days, one week, 1 hour, etc., and this application does not specifically limit the length of the preset usage time.
[0309] For example, Fig.11 FIG. 2 shows a frame structure of a VIN provided in an embodiment of the present application. Fig.11 As shown, the VIN consists of a total of 17 bytes. Among them, the first 3 bytes are the world manufacturer identifier (WMI), which is used to record the geographical area and country of the manufacturer of the device to be charged. The 4th to 9th bytes are the vehicle descriptor section (VDS), which contains the feature code (such as type, series, engine type, etc.) and check digit of the device to be charged. WMI and VDS are the first field. The 10th byte is the model year, and the 11th byte is the assembly plant. The model year and assembly plant are the second field. The 12th to 17th bytes are secure random numbers, which are the third field.
[0310] To ensure that after using the dynamic VIN, the manufacturer, VDS and other information of the device to be charged can still be identified through the dynamic VIN to complete the charging process of the device to be charged. In some embodiments, the first random number can be generated according to one or more of the first to 11th bytes in the VIN frame structure, a preset random number, and a preset usage time, for example: solving the hash value of one or more of the first to 11th bytes in the VIN frame structure, a preset random number, and a preset usage time, or performing other operations, and then encoding the solved value, such as encoding in base62 encoding, or encoding in other ways, and obtaining the first random number according to the encoding.
[0311] It can be understood that each byte in the base62 encoding method consists of uppercase and lowercase English letters and numbers, and each character consists of 62 numerical values. For example, 6 bytes have a total of 56800235584 encoding spaces, which can reduce the probability of dynamic VIN collision, that is, the probability of different charging devices having the same dynamic VIN at the same time is small.
[0312] In some examples, the hash value of the 1st to 11th bytes in the VIN frame structure, the preset random number, and the preset usage time can be represented by RAND1, and RAND1 can satisfy Formula 1.
[0313] RAND1=sha256(VIN[1-11]|Salt|Day) Formula 1
[0314] In Formula 1, sha256 is a hash function that can generate a hash value of 256 bits in length. VIN[1-11] represents the first to 11th bytes in the VIN frame structure. Salt refers to a preset random number. Day represents the preset usage time of the generated dynamic VIN. Formula 1 indicates that the value of RAND1 is the hash value obtained by concatenating VIN[1-11], Salt, and Day.
[0315] Optionally, in this embodiment, the length of the first random number can be the same as the length of the secure random number, such as 6 bytes. Optionally, the 6 bytes can be any 6 bytes after encoding the hash value obtained by solving Formula 1, such as the first 6 bytes, the last 6 bytes, the middle 6 bytes, etc., and the 6 bytes can be continuous or discontinuous.
[0316] To ensure that the length of the dynamic VIN is the same as that of the VIN, so that the device can successfully identify the dynamic VIN. In some embodiments, the length of the preset random number can be 32 bytes, or can also be 16 bytes, and this application does not impose specific restrictions on this.
[0317] Then, a dynamic VIN may be generated according to the first random number and the first to 11th bytes in the VIN frame structure, for example, the first random number and the first to 11th bytes in the VIN frame structure are concatenated to generate a dynamic VIN.
[0318] In other embodiments, since the bytes such as the model year and assembly plant in the VIN frame structure do not affect the charging process of the device to be charged, the second random number can also be generated based on one or more of the first to ninth bytes in the VIN frame structure, a preset random number, and a preset usage time. For example: solve the hash value of one or more of the first to ninth bytes in the VIN frame structure, a preset random number, and a preset usage time, or perform other operations, and then encode the solved value, and obtain the second random number according to the code.
[0319] In some examples, the hash value of the 1st to 9th bytes in the VIN frame structure, the preset random number, and the preset usage time can be represented by RAND2, and RAND2 can satisfy Formula 2.
[0320] RAND2=sha256(VIN[1-9]|Salt|Day) Formula 2
[0321] In Formula 2, VIN[1-9] represents the first to ninth bytes in the VIN frame structure. For the introduction of other parameters in Formula 2, refer to the introduction of corresponding parameters in Formula 1. Formula 2 indicates that the value of RAND2 is the hash value obtained by concatenating VIN[1-9], Salt, and Day.
[0322] Optionally, in this embodiment, the length of the second random number can be the same as the sum of the lengths of the security random number, the model year, and the assembly plant, such as 8 bytes. Optionally, the 8 bytes can be any 8 bytes after encoding the hash value obtained by solving Formula 2, such as the first 8 bytes, the last 8 bytes, the middle 8 bytes, etc., and the 8 bytes can be continuous or discontinuous.
[0323] Then, a dynamic VIN may be generated according to the second random number and the first to ninth bytes in the VIN frame structure, for example, the second random number and the first to ninth bytes in the VIN frame structure are concatenated to generate a dynamic VIN.
[0324] It can be understood that in the embodiment of the present application, the hash function in the formula can also be presented as other functions, and the embodiment of the present application does not impose any limitation on the method of generating the dynamic VIN.
[0325] In other embodiments, the above random numbers, such as the first random number, the second random number, etc., may be generated according to the user key, the verification code, etc. to generate the dynamic VIN. Of course, in the case of an extended field, the length of the generated random number may also be determined according to, including but not limited to, the length of the extended field, etc., that is, the extended field may also be used to carry the generated random number.
[0326] Optionally, in the embodiment of the present application, the operation of generating a dynamic VIN may be performed by, for example Figure 4 The terminal device shown, and / or server 404, and / or server 406 execute. Server 404 and / or server 406 can generate dynamic VINs for some or all of the devices to be charged that have signed the plug-and-charge agreement. For a device to be charged that has signed the plug-and-charge agreement, server 404 and / or server 406 can also simultaneously generate a dynamic VIN corresponding to one or more preset usage times of the device to be charged. Optionally, for a terminal device, a dynamic VIN of a device to be charged that has established a binding relationship with itself can be generated. In some embodiments, the terminal device, and / or server 404, and / or server 406 can also receive a VIN from the device to be charged to facilitate the generation of a dynamic VIN for the device to be charged.
[0327] Optionally, after the terminal device, and / or server 404, and / or server 406 generates the dynamic VIN of the device to be charged, one or more dynamic VINs of preset usage time can be sent to the device to be charged at the same time. For example, taking the length of the preset usage time as one day, the dynamic VIN of the current day and the next three days can be sent to the device to be charged at the same time.
[0328] Optionally, the terminal device, and / or the server 404, and / or the server 406 may send one or more dynamic VINs of preset usage time to the device to be charged before the device to be charged receives the charging operation. Alternatively, one or more dynamic VINs of preset usage time may be sent to the device to be charged after the device to be charged receives the charging operation. The embodiment of the present application does not impose any restrictions on the timing of the terminal device, and / or the server 404, and / or the server 406 sending the dynamic VIN to the device to be charged.
[0329] Optionally, for the same preset usage time, the dynamic VINs of different devices to be charged are different. For different preset usage times, the dynamic VINs of different devices to be charged can be the same, and the dynamic VIN of the same device to be charged can also be the same. In this way, it can be ensured that the dynamic VINs of different devices to be charged at the same time are different, so that each device to be charged can use its own dynamic VIN to charge.
[0330] In some embodiments, after the terminal device, and / or the server 404, and / or the server 406 generates a dynamic VIN for a device to be charged, if it is determined that the dynamic VIN of the charging device is the same as that of other devices to be charged at the same time, the terminal device, and / or the server 404, and / or the server 406 can regenerate the dynamic VIN for the device to be charged, for example, by modifying the above-mentioned preset random number, etc., to regenerate the dynamic VIN of the device to be charged, so as to ensure that the dynamic VINs of different devices to be charged at the same time are unique.
[0331] In some embodiments, before the device to be charged executes step S1002, the device to be charged may also determine whether the dynamic VIN meets the validity condition. When the dynamic VIN meets the validity condition, the device to be charged may determine that the dynamic VIN is valid, that is, the dynamic VIN can be used for charging, that is, step S1002 is executed. When the dynamic VIN does not meet the validity condition, the device to be charged may determine that the dynamic VIN is invalid, that is, the dynamic VIN cannot be used for charging. Exemplarily, the validity condition may include at least one of the number of uses being less than or equal to a preset number threshold and the usage time being within a preset usage time.
[0332] Of course, the judgment operation can also be performed by the server, such as after executing step S1003, the server determines whether the dynamic VIN meets the validity condition. If so, execute step S1004. If not, execute step S1006, or re-send the dynamic VIN that meets the validity condition to the device to be charged. Alternatively, the server can also determine whether the dynamic VIN meets the validity condition after executing step S1004. If so, execute step S1005. If not, execute step S1006, etc., or re-send the dynamic VIN that meets the validity condition to the device to be charged.
[0333] In some embodiments, when the device to be charged determines that the dynamic VIN is invalid, the device to be charged may also request a valid dynamic VIN from the terminal device, and / or the server 404 , and / or the server 406 .
[0334] S1003: The power supply device sends a dynamic VIN to the server. Correspondingly, the server receives the dynamic VIN from the power supply device.
[0335] It can be understood that this embodiment takes the example of the device to be charged sending a dynamic VIN to the server through the power supply device. In other embodiments, the terminal device may also send the dynamic VIN to the server. For example: after the device to be charged executes step S1001, in response to the operation, the terminal device may report the dynamic VIN of the device to be charged to the server. Optionally, in this embodiment, a binding relationship such as that described above may also be established between the terminal device and the device to be charged, so that the terminal device can monitor whether the device to be charged receives a charging operation, or exchange information with the device to be charged. Optionally, in this embodiment, after generating the dynamic VIN of the device to be charged, the server 404 and / or the server 406 may also send the dynamic VIN of the device to be charged to the terminal device that has a binding relationship with the device to be charged, so that the terminal device can subsequently report the dynamic VIN.
[0336] Similarly, other operations performed by the charging device, such as but not limited to determining whether the dynamic VIN meets the validity conditions, requesting a valid dynamic VIN from server 404 and / or server 406 when determining that the dynamic VIN is invalid, reporting the first VIN, etc., etc., one or more operations, can also be performed by the terminal device.
[0337] S1004. The server determines whether the VIN corresponding to the dynamic VIN satisfies a second preset condition.
[0338] Exemplarily, the second preset condition may include a signed plug-and-charge service, where the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner. Alternatively, the second preset condition may also be described as being in a whitelist.
[0339] In some embodiments, a mapping relationship between the VIN and the dynamic VIN is stored in the server, and the server can determine the corresponding VIN according to the dynamic VIN and the mapping relationship.
[0340] In other embodiments, the server may also store a mapping relationship between a dynamic VIN, a preset usage time, and a VIN. The server may determine the corresponding VIN based on the dynamic VIN and the preset usage time corresponding to the dynamic VIN.
[0341] If the conditions are met, then step S1005 is executed. If the conditions are not met, then step S1006 is executed.
[0342] S1005: The server instructs the power supply device to charge the device to be charged. Correspondingly, after receiving the instruction, the power supply device charges the charging device.
[0343] S1006: The server instructs the power supply device not to charge the device to be charged. Correspondingly, after receiving the instruction, the power supply device does not charge the device to be charged.
[0344] It can be understood that the above embodiment is based on the example of the server executing steps S1003 to S1006, etc. In other embodiments, one or more of the above steps S1003 to S1006, etc., and other steps executed by the server can also be executed by the terminal device. Optionally, in this embodiment, when the terminal device executes step S003, in order to facilitate the power supply device to determine to which terminal device to send the received dynamic VIN, the power supply device (or the server corresponding to the power supply device, such as Figure 4 The server 405 shown in the figure may store the identifier of the terminal device corresponding to the dynamic VIN, such as the identifier of the terminal device may be a mobile phone number, a Huawei account, etc., so that the power supply device can determine to which terminal device the dynamic VIN is to be sent. Optionally, in this embodiment, if the dynamic VIN is generated by the terminal device, the terminal device may synchronize the generated dynamic VIN to the power supply device, so that the power supply device can establish a corresponding relationship between the terminal device identifier and the dynamic VIN.
[0345] Similarly, when the terminal device executes step S1004, the terminal device may also adopt the same method as the server. Optionally, in this embodiment, the terminal device may store a white list, or the terminal device may obtain a white list from other devices.
[0346] Combine the following Figure 4 , Figure 6 In the illustrated architecture, the server 404 generates a dynamic VIN and sends a plurality of dynamic VINs of preset usage time to the charging device before the charging device receives the charging operation. Fig.12 FIG. 2 shows a flow chart of another charging method provided by an embodiment of the present application. Fig.12 As shown, the method comprises the following steps:
[0347] S1201. The server 404 generates a dynamic VIN for the device to be charged.
[0348] Please refer to the above description for the specific generation method.
[0349] S1202 , the server 404 sends a dynamic VIN to a device management module (hereinafter referred to as the device management module) of the device to be charged. Correspondingly, the device management module receives the dynamic VIN from the server 404 .
[0350] Optionally, the server 404 may simultaneously send one or more dynamic VINs of preset usage time corresponding to the device to be charged to the device management module.
[0351] S1203, the device management module sends a dynamic VIN to a BMS module (hereinafter referred to as BMS module) of the device to be charged. Correspondingly, the BMS module receives the dynamic VIN from the device management module.
[0352] Among them, the BMS module can also cache dynamic VIN.
[0353] Exemplarily, the device management module may send the dynamic VIN to the BMS module via a controller area network (CAN) bus.
[0354] S1204 . In response to the charging operation, the power supply device performs a charging handshake with the BMS module.
[0355] S1205. The BMS module determines the current corresponding dynamic VIN (referred to as dynamic VIN in the following steps).
[0356] In some embodiments, the BMS module may store multiple dynamic VINs with different preset usage times (for example, the preset usage times are April 1, 2023, April 2, 2023, April 3, 2023, etc.), and the BMS module may determine the current corresponding dynamic VIN according to the preset usage time. For example, if the current time is April 3, 2023, the BMS module may determine that the current corresponding dynamic VIN is the dynamic VIN with a preset usage time of April 3, 2023.
[0357] In other embodiments, the BMS module may store only one dynamic VIN. In this case, the BMS module may not execute this step. For example, taking the preset usage time as one day, when the server 404 only sends the dynamic VIN of that day to the BMS module, the BMS module may not execute this step.
[0358] S1206: The BMS module executes a charging response and sends a dynamic VIN to the power supply device. Accordingly, the power supply device receives the dynamic VIN from the BMS module.
[0359] S1207: The power supply device sends the dynamic VIN to the server 405. Correspondingly, the server 405 receives the dynamic VIN from the power supply device.
[0360] S1208 , the server 405 sends the dynamic VIN to the server 404 . Accordingly, the server 404 receives the dynamic VIN from the server 405 .
[0361] S1209 , the server 404 determines whether the VIN corresponding to the dynamic VIN satisfies a second preset condition.
[0362] For the introduction of this step, please refer to the introduction of step S1004.
[0363] S1210: The server 404 instructs the power supply device to charge the device to be charged. Correspondingly, after receiving the instruction, the power supply device charges the charging device.
[0364] S1211, the server 404 instructs the power supply device not to charge the device to be charged. Correspondingly, after receiving the instruction, the power supply device does not charge the device to be charged.
[0365] It can be understood that the technical solutions provided in the above embodiments can be used alone or in combination.
[0366] In one possible combination, after receiving the dynamic VIN reported by the device to be charged, the server can also obtain the PDID corresponding to the dynamic VIN, and then obtain the charging event of the real device to be charged according to the PDID, and then determine whether to charge the device to be charged that reports the dynamic VIN according to the charging event. For example: when the charging event of the real device to be charged meets the first preset condition, it is determined to charge the device to be charged that reports the dynamic VIN. When the charging event of the real device to be charged does not meet the first preset condition, it is determined not to charge the device to be charged that reports the dynamic VIN. Combined with the dynamic VIN and PDID to determine whether to charge the device to be charged, the dynamic VIN is randomly generated, and the probability that three parties can impersonate the dynamic VIN is low. In addition, the PDID of each device to be charged is also unique and cannot be tampered with. In this way, double protection is provided for the charging process of the device to be charged, and the risk of stolen charging of the device to be charged, such as electric vehicles, can be further reduced.
[0367] For example, Fig.13 FIG. 2 shows a flow chart of another charging method provided by an embodiment of the present application. Fig.13 As shown, the method comprises the following steps:
[0368] S1301: In response to a charging operation, the device to be charged sends a dynamic VIN to the power supply device. Correspondingly, the power supply device receives the dynamic VIN from the device to be charged.
[0369] S1302: The power supply device sends a dynamic VIN to the server. Correspondingly, the server receives the dynamic VIN from the power supply device.
[0370] S1303: The server determines whether the VIN corresponding to the dynamic VIN satisfies a second preset condition.
[0371] If the conditions are met, step S1304 may be executed. If the conditions are not met, step S1307 may be executed.
[0372] S1304: The server obtains a charging event corresponding to the first PDID.
[0373] In some embodiments, the first PDID may be a PDID corresponding to a VIN, where the VIN is the VIN corresponding to the dynamic VIN described in step S1303 .
[0374] In some examples, there is a mapping relationship between the dynamic VIN and the VIN, and there is a mapping relationship between the VIN and the PDID. The server can first determine the VIN corresponding to the dynamic VIN according to the mapping relationship between the dynamic VIN and the VIN, and then determine the first PDID according to the mapping relationship between the VIN and the PDID.
[0375] In other examples, there is a mapping relationship between the dynamic VIN and the VIN, and there is a mapping relationship between the dynamic VIN and the PDID. The server can first determine the VIN corresponding to the dynamic VIN according to the mapping relationship between the dynamic VIN and the VIN, and then determine the PDID according to the mapping relationship between the dynamic VIN and the PDID, and the PDID is the first PDID.
[0376] In some other embodiments, the first PDID may be a PDID corresponding to a dynamic VIN.
[0377] In some examples, there is a mapping relationship between the dynamic VIN and the PDID, and the server can directly determine the first PDID based on the dynamic VIN and the mapping relationship.
[0378] In other examples, there is a mapping relationship between the dynamic VIN and the VIN, and there is a mapping relationship between the VIN and the PDID. The server can first determine the VIN corresponding to the dynamic VIN according to the mapping relationship between the dynamic VIN and the VIN, and then determine the PDID corresponding to the VIN according to the mapping relationship between the VIN and the PDID, which is also the first PDID.
[0379] Of course, in other embodiments, there may be a mapping relationship among the dynamic VIN, the VIN, and the PDID. The server may directly determine the first PDID according to the mapping relationship.
[0380] S1305: The server determines whether the charging event meets a first preset condition.
[0381] Optionally, step S1303 and step S1305 may be performed simultaneously or sequentially. In the case of sequential execution, the present application does not limit the sequence.
[0382] If the conditions are met, step S1306 may be executed. If the conditions are not met, step S1307 may be executed.
[0383] S1306: The server instructs the power supply device to charge the device to be charged. Correspondingly, after receiving the instruction, the power supply device charges the charging device.
[0384] S1307: The server instructs the power supply device not to charge the device to be charged. Correspondingly, after receiving the instruction, the power supply device does not charge the device to be charged.
[0385] about Fig.13 For an introduction to the steps shown, refer to Figure 8 as well as Fig.10 Description of the corresponding steps shown.
[0386] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. It is understandable that, in order to realize the above functions, the device includes a hardware structure and / or software module corresponding to the execution of each function. In combination with the units and algorithm steps of each example described in the embodiment disclosed in this application, the embodiment of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer-driven hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present application.
[0387] The present application is an embodiment that can divide the functional modules of the device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.
[0388] like Fig.14 1400 is a schematic diagram of a device provided in an embodiment of the present application. The device 1400 can be used to implement the methods described in the above method embodiments. Exemplarily, the device 1400 may include: a processing unit 1401 and a communication unit 1402.
[0389] In one possible example, the device 1400 may be Figure 4 The terminal device shown in , may also be a module (such as a chip) applied to the terminal device. The processing unit 1401 is used to support the device 1400 to execute Figures 1 to 13 The communication unit 1402 is used to support the device 1400 to perform Figures 1 to 13 The communication function of any of the terminal devices described above.
[0390] In another possible example, the device 1400 may be Figure 4 The device to be charged shown in the figure may also be a module (such as a chip) applied to the device to be charged. The processing unit 1401 is used to support the device 1400 to execute Figures 1 to 13 The communication unit 1402 is used to support the device 1400 to perform Figures 1 to 13 The communication function of any one of the devices to be charged.
[0391] In another possible example, the device 1400 may be Figure 4 The server described in the above may also be a module (such as a chip) applied to the server. The processing unit 1401 is used to support the device 1400 to execute Figures 1 to 13 The communication unit 1402 is used to support the device 1400 to execute Figures 1 to 13 The communication function of any of the servers described above.
[0392] Optional, Fig.14 The device 1400 shown may also include a storage unit 1403, which stores a program or instruction. When the processing unit 1401 executes the program or instruction, Fig.14 The device 1400 shown can execute the method described in the above method embodiment.
[0393] Fig.14 The technical effects of the device 1400 shown can refer to the technical effects described in the above method embodiments, and will not be repeated here. Fig.14 The processing unit 1401 involved in the device 1400 shown may be implemented by a processor or a processor-related circuit component, and may be a processor or a processing module. The communication unit 1402 may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module.
[0394] The present application also provides a chip system, such as Fig.15As shown, the chip system includes at least one processor 1501 and at least one interface circuit 1502. The processor 1501 and the interface circuit 1502 can be interconnected via lines. For example, the interface circuit 1502 can be used to receive signals from other devices. For another example, the interface circuit 1502 can be used to send signals to other devices (such as processor 1501). Exemplarily, the interface circuit 1502 can read instructions stored in the memory and send the instructions to the processor 1501. When the instructions are executed by the processor 1501, the device can execute the various steps executed by the device in the above embodiment. Of course, the chip system can also include other discrete devices, which are not specifically limited in the embodiments of the present application.
[0395] Optionally, the processor in the chip system may be one or more. The processor may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented by software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.
[0396] Optionally, the memory in the chip system may be one or more. The memory may be integrated with the processor or may be separately provided with the processor, which is not limited in the present application. Exemplarily, the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip or may be provided on different chips. The present application does not specifically limit the type of memory and the arrangement of the memory and the processor.
[0397] Exemplarily, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.
[0398] It should be understood that each step in the above method embodiment can be completed by an integrated logic circuit of hardware in a processor or by instructions in the form of software. The method steps disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware processor, or by a combination of hardware and software modules in a processor.
[0399] An embodiment of the present application also provides a computer storage medium, in which computer instructions are stored. When the computer instructions are executed on a device, the device executes the method described in the above method embodiment.
[0400] An embodiment of the present application provides a computer program product, which includes: a computer program or instructions, when the computer program or instructions are executed on a computer, the computer executes the method described in the above method embodiment.
[0401] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory so that the device executes the methods in the above-mentioned method embodiments.
[0402] Among them, the equipment, computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.
[0403] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0404] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The various embodiments can be combined with each other or referenced to each other without conflict. The device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0405] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0406] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0407] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.
[0408] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A charging method, It is characterized in that Applied to a first device, the method includes: receiving a first request message from a network device; In response to the first request message, the production device identification number PDID of the first device to be charged and a charging event are sent to the network device, wherein the charging event is used to characterize the charging status of the first device to be charged, and the PDID and charging event of the first device to be charged are used to determine whether to start the power supply device to charge the device to be charged that reports the first vehicle identification code VIN, and the first VIN is the VIN of the first device to be charged.
2. The method according to claim 1, It is characterized in that Before sending the PDID of the first device to be charged and the charging event to the network device, the method further includes: The charging event is encrypted using a private key corresponding to the PDID of the first device to be charged.
3. The method according to claim 1 or 2, It is characterized in that The charging event includes the geographic location of the first device to be charged. When the distance between the geographic location of the first device to be charged and the power supply device meets a preset distance range, the PDID of the first device to be charged and the charging event are used to determine to start the power supply device to charge the device to be charged that reports the first VIN.
4. The method according to any one of claims 1 to 3, It is characterized in that The charging event includes the state of the charging port of the first device to be charged. When the charging port of the first device to be charged is in an open state, the PDID of the first device to be charged and the charging event are used to determine to start the power supply device to charge the device to be charged that reports the first VIN.
5. The method according to any one of claims 1 to 4, It is characterized in that The charging event includes the state of the first device to be charged after the power supply device is started to charge the device to be charged that reports the first VIN. When the state of the first device to be charged is a non-charging state, the PDID of the first device to be charged and the charging event are used to determine to stop the power supply device from charging the device to be charged that reports the first VIN.
6. The method according to any one of claims 2 to 5, It is characterized in that The PDID of the first device to be charged and a private key corresponding to the PDID of the first device to be charged are stored in a chip of the first device to be charged.
7. The method according to any one of claims 1 to 6, It is characterized in that Before receiving the first request message from the network device, the method further includes: A second request message is sent to the network device, wherein the second request message includes the first VIN, and the second request message is used to request to sign up for a plug-and-charge service, wherein the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner.
8. A charging method, It is characterized in that Applied to the second device, the method includes: receiving, from a power supply device, a first message sent by a device to be charged, wherein the first message carries a first VIN, and the first message is used to instruct the power supply device to start charging the device to be charged; Acquire a charging event of a device corresponding to a target PDID, where the charging event is used to characterize a charging status of the device corresponding to the target PDID, and the target PDID corresponds to the first VIN; Determine whether to start the power supply device to charge the device to be charged according to the charging event.
9. The method according to claim 8, It is characterized in that The step of obtaining a charging event of a device corresponding to a target PDID includes: receiving, from a device corresponding to the target PDID, the charging event encrypted using a private key corresponding to the target PDID; The charging event is decrypted according to a public key corresponding to the target PDID.
10. The method according to claim 8 or 9, It is characterized in that The charging event includes a geographic location of a device corresponding to the target PDID; The step of determining whether to start the power supply device to charge the device to be charged according to the charging event includes: When the distance between the geographical location of the device corresponding to the target PDID and the power supply device satisfies a preset distance range, it is determined to start the power supply device to charge the device to be charged.
11. The method according to any one of claims 8 to 10, It is characterized in that The charging event includes the status of the charging port of the device corresponding to the target PDID; The step of determining whether to start the power supply device to charge the device to be charged according to the charging event includes: When the charging port of the device corresponding to the target PDID is in an open state, it is determined to start the power supply device to charge the device to be charged.
12. The method according to any one of claims 8 to 11, It is characterized in that The charging event includes the state of the device corresponding to the target PDID after the power supply device is started to charge the device to be charged; The step of determining whether to start the power supply device to charge the device to be charged according to the charging event includes: When the state of the device corresponding to the target PDID is a non-charging state, it is determined to stop the power supply device from charging the device to be charged.
13. The method according to any one of claims 8 to 12, It is characterized in that The target PDID and the private key corresponding to the target PDID are stored in the chip of the device corresponding to the target PDID; the public key corresponding to the target PDID is stored in the network device.
14. The method according to any one of claims 10 to 13, It is characterized in that Before determining to start the power supply device to charge the device to be charged, the method further includes: It is determined that the first VIN has signed a plug-and-charge service, and the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner.
15. A charging method, It is characterized in that Applied to a first device, the method includes: Sending a second message to the network device, wherein the second message carries a dynamically generated second VIN, and the second message is used to start the power supply device to charge the device to be charged; In the case that the first VIN corresponding to the second VIN has signed a plug-and-charge service, the power delivered by the power supply device is received, and the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner.
16. The method according to claim 15, It is characterized in that Before sending the second message to the network device, the method further includes: It is determined that the second VIN meets a validity condition, where the validity condition includes at least one of: the number of uses is less than or equal to a preset number threshold, and the use time is within a preset use time.
17. The method according to claim 16, It is characterized in that Before sending the second message to the network device, the method further includes: Sending the first VIN to the network device; The second VIN is received from the network device, where the second VIN is generated according to at least one of the first VIN, a preset random number, and the preset usage time.
18. The method according to any one of claims 15 to 17, It is characterized in that The second message includes a battery management system BMS and a vehicle identification message BRM message.
19. A charging method, It is characterized in that Applied to the second device, the method includes: receiving a second message, wherein the second message carries a dynamically generated second VIN, and the second message is used to start the power supply device to charge the device to be charged; In the case that the first VIN corresponding to the second VIN has signed a plug-and-charge service, the power supply device is instructed to charge the device to be charged, and the plug-and-charge service is used to start charging the power supply device in a plug-and-charge manner.
20. The method according to claim 19, It is characterized in that The second VIN satisfies a valid condition, and the valid condition includes at least one of: the number of uses is less than or equal to a preset number threshold, and the use time is within a preset use time.
21. The method according to claim 20, It is characterized in that Before receiving the second message, the method further includes: receiving the first VIN; Generate the second VIN according to at least one of the first VIN, a preset random number, and the preset usage time; The second VIN is sent to the device to be charged.
22. The method according to claim 21, It is characterized in that The first VIN includes a first field, a second field and a third field, the first field includes a world manufacturer identification code WMI and a vehicle description part VDS, the second field includes a model year and an assembly plant, and the third field includes a secure random number; The generating the second VIN according to at least one of the first VIN, a preset random number, and a preset usage time includes: Generate a target random number according to a reference field, the preset random number and the preset usage time; Generate the second VIN according to the reference field and the target random number; The reference field includes the first field and the second field, and the length of the target random number is the same as the length of the third field; Alternatively, the reference field includes a total length of the first field, the second field, and the third field, which is the same as the length of the target random number.
23. The method according to claim 22, It is characterized in that The generating a target random number according to the reference field, the preset random number and the preset usage time includes: The reference field, the preset random number and the hash value of the preset usage time are encoded to obtain the target random number.
24. The method according to claim 23, It is characterized in that The reference field includes the first field and the second field, and the length of the third field is 6 bytes; the target random number is the first 6 bytes after encoding RAND1, and RAND1 satisfies the following formula: RAND1=sha256(VIN[1-11]|Salt|Day) Among them, the VIN[1-11] is the first field and the second field, the Salt is the preset random number, the Day is the preset usage time, and the sha256 is a hash function.
25. The method according to claim 23, It is characterized in that The reference field includes the first field, and the total length of the second field and the third field is 8 bytes; the target random number is the first 8 bytes after encoding RAND2, and RAND2 satisfies the following formula: RAND2=sha256(VIN[1-9]|Salt|Day) Among them, the VIN[1-9] is the first field, the Salt is the preset random number, the Day is the preset usage time, and the sha256 is a hash function.
26. The method according to any one of claims 21 to 25, It is characterized in that Before sending the second VIN to the device to be charged, the method further includes: It is determined that within the preset usage time, the second VIN is different from VINs of other devices.
27. The method according to any one of claims 19 to 26, It is characterized in that Before instructing the power supply device to charge the device to be charged, the method further includes: Acquire a charging event of a device corresponding to a target PDID, where the charging event is used to characterize a charging status of the device corresponding to the target PDID, and the target PDID corresponds to the first VIN; Determining that the charging event satisfies a corresponding first preset condition; The charging event includes: the geographical location of the device corresponding to the target PDID, and the corresponding first preset condition includes: the distance between the geographical location of the device corresponding to the target PDID and the power supply device meets the preset distance range; And / or, the charging event includes: the state of the charging port of the device corresponding to the target PDID, and the corresponding first preset condition includes: the state of the charging port of the device corresponding to the target PDID is open.
28. The method according to claim 27, It is characterized in that After instructing the power supply device to charge the device to be charged, the method further includes: Obtain the status of the device corresponding to the target PDID; When the state of the device corresponding to the target PDID is a non-charging state, instruct the power supply device to stop charging the device to be charged.
29. The method according to claim 27 or 28, It is characterized in that The step of obtaining a charging event of a device corresponding to a target PDID includes: Receiving the charging event encrypted using a private key corresponding to the target PDID; The charging event is decrypted according to a public key corresponding to the target PDID.
30. The method according to claim 29, It is characterized in that The target PDID and the private key corresponding to the target PDID are stored in the chip of the device corresponding to the target PDID; the public key corresponding to the target PDID is stored in the network device.
31. The method according to any one of claims 19 to 30, It is characterized in that The second message includes a battery management system BMS and a vehicle identification message BRM message.
32. A device, It is characterized in that Comprising a module for executing each step of the method as claimed in any one of claims 1 to 7, or comprising a module for executing each step of the method as claimed in any one of claims 8 to 14, or comprising a module for executing each step of the method as claimed in any one of claims 15 to 18, or comprising a module for executing each step of the method as claimed in any one of claims 19 to 31.
33. A device, It is characterized in that The device comprises a processor and a memory, wherein the memory is coupled to the processor, the memory is used to store computer program code, the computer program code comprises computer instructions, the processor reads the computer instructions from the memory, so that the device executes the method according to any one of claims 1 to 7, or the method according to any one of claims 8 to 14, or the method according to any one of claims 15 to 18, or the method according to any one of claims 19 to 31.
34. A computer readable storage medium, It is characterized in that The computer-readable storage medium includes a computer program, which, when executed on a device, causes the device to execute the method as claimed in any one of claims 1 to 7, or causes the device to execute the method as claimed in any one of claims 8 to 14, or causes the device to execute the method as claimed in any one of claims 15 to 18, or causes the device to execute the method as claimed in any one of claims 19 to 31.
35. A computer program product, It is characterized in that The computer program product comprises: a computer program or instructions, which, when executed on a computer, causes the computer to execute the method as claimed in any one of claims 1 to 7, or causes the computer to execute the method as claimed in any one of claims 8 to 14, or causes the computer to execute the method as claimed in any one of claims 15 to 18, or causes the computer to execute the method as claimed in any one of claims 19 to 31.
Citation Information
Cited By
Non-contact wireless service joint and aircraft ground electric service equipment
CN121791874A
