Vehicle charging control method and system, and vehicle-mounted TBOX and platform

Abstract

The invention discloses a vehicle charging control method and system, a vehicle-mounted TBOX and a platform, and the vehicle charging control method is applied to the vehicle-mounted TBOX and comprises the following steps: obtaining a login token, and logging in the platform through the login token; receiving configuration information issued by the platform, wherein the configuration information comprises a network access configuration command and a network exit configuration command; when a network access configuration command issued by the platform is received, responding to the network access configuration command, and feeding back a configuration state to the platform; when a network exit configuration command issued by the platform is received, the charging permission state of the current vehicle is judged, if the current vehicle is in a charging permission state, network exit is permitted, the network exit configuration command is responded, a network exit success result is fed back to the platform, and if the current vehicle is in a charging prohibition state, network exit is not permitted, and a network exit failure result is fed back to the platform; a charging control instruction issued by the platform is received, when the vehicle is in the network access state, whether the vehicle is allowed to be charged is judged, if yes, the charging control instruction is issued to the battery replacement controller so that the battery replacement controller can execute the charging control instruction, and when the vehicle is in the network exit state, the charging control instruction is not issued to the battery replacement controller.

Description

Technical Field

[0001] The present invention relates to the field of charging control technology, and in particular to a vehicle charging control method, system, and a vehicle-mounted TBOX and platform. Background Art

[0002] The large-scale popularization of new energy vehicles, especially electric vehicles (EVs), has brought new challenges to charging infrastructure and charging management technology, mainly including:

[0003] 1) Challenges in charging infrastructure construction: Although the number of charging stations is increasing, the uneven distribution of charging facilities, low charging efficiency, and insufficient coordination with the power grid are still prominent. Especially in urban centers and long-distance travel, the problems of difficult and slow charging have seriously affected the user experience and acceptance of electric vehicles.

[0004] 2) Challenges of energy consumption and grid load: If the large-scale charging demand of electric vehicles is not scientifically managed, it may cause a huge impact on the power grid, especially during peak hours. Disorderly charging will cause local grid overload, affect the stable operation of the power system, increase energy consumption and environmental pollution.

[0005] 3) Challenges in user charging experience: Users have increasingly higher expectations for the convenience, economy, and safety of charging. Traditional charging models often fail to provide personalized charging plans, cost optimization, and remote management functions, limiting the improvement of user experience.

[0006] 4) Challenges of intelligent management needs: In view of the above challenges, how to efficiently and intelligently manage the charging process of electric vehicles, optimize the allocation of charging resources, improve charging efficiency, and reduce the burden on the power grid has become a key issue that needs to be solved urgently. Summary of the invention

[0007] The present invention aims to solve at least one of the technical problems existing in the prior art, and proposes a vehicle charging control method, system, and a vehicle-mounted TBOX and platform.

[0008] In a first aspect, the present invention provides a vehicle charging control method, which is applied to a vehicle-mounted TBOX, comprising the following steps:

[0009] Get a login token and use it to log in to the platform;

[0010] Receive configuration information issued by the platform, including network entry configuration commands and network exit configuration commands;

[0011] When receiving the network access configuration command issued by the platform, respond to the network access configuration command and feedback the configuration status to the platform;

[0012] When receiving the network disconnection configuration command issued by the platform, the charging permission status of the current vehicle is determined. If the current vehicle is in a charging-allowed state, network disconnection is allowed, and the network disconnection configuration command is responded to, and the network disconnection success result is fed back to the platform. If the current vehicle is in a charging-prohibited state, network disconnection is not allowed, and the network disconnection failure result is fed back to the platform;

[0013] Receive the charging control instructions issued by the platform. When the vehicle is in the network state, determine whether the vehicle is allowed to charge. If so, send the charging control instructions to the battery swap controller for the battery swap controller to execute the charging control instructions. When the vehicle is in the off-grid state, do not send the charging control instructions to the battery swap controller.

[0014] Furthermore, the charging control instructions issued by the receiving platform are sent. When the vehicle is in the network state, if the vehicle is allowed to charge, it is also necessary to determine whether the current charging amount is greater than the preset value. When the current charging amount is greater than the preset value, the charging control instructions are sent to the battery swap controller.

[0015] Furthermore, obtaining a login token includes:

[0016] Determine whether it is necessary to obtain a login token;

[0017] If yes, a request message for obtaining a login token is sent to the server, including:

[0018] Obtain the key and the original message to be authenticated;

[0019] Process the message content: sort all non-empty request parameters in ascending order according to the request parameter name and generate a string in JSON format;

[0020] Padding key: If the key length is less than 64 bytes, it is padded to 64 bytes; if the key length is greater than 64 bytes, the MD5 hash value of the key is taken as the new key;

[0021] Perform an internal hash operation: perform a bitwise XOR operation on the padded key and the message to obtain a first result, and perform an AND operation on the padded key and the message to obtain a second result;

[0022] Calculate and output the result: concatenate the first result, the message, and the second result together and input them into the MD5 hash function for calculation to obtain the final 32-bit hash value as the message authentication code;

[0023] Send the message and the message authentication code to the server, so that after receiving the message and the message authentication code, the server uses the same key and message content, and the same message authentication code algorithm to recalculate the message authentication code, and compares the message authentication code calculated by itself with the message authentication code received from TBOX. If the two message authentication codes are consistent, the authentication is successful, and the login token is issued to TBOX.

[0024] Furthermore, the vehicle charging control method of the present invention further includes the following steps:

[0025] Push off-station charging energy messages to the platform at regular intervals, so that the platform can calculate the vehicle's remaining balance this month and off-station charging permission status based on the reported off-station charging energy messages, platform operation strategies and rules, and reply to the off-station charging energy response message to TBOX in real time, thus achieving real-time control of off-station charging of vehicles;

[0026] Off-site charging energy messages include subtotal off-site charging energy, battery charging status, accumulated charging energy, and current off-site charging permission status;

[0027] Receive the platform's off-site charging energy response message and send the corresponding off-site charging instruction to the battery swap controller in real time.

[0028] Furthermore, when receiving the off-network configuration command issued by the platform, the charging permission status of the current vehicle is determined. If the current vehicle is in a charging prohibited state, the off-network failure result is fed back to the platform. If no charging permission, charging prohibition, network access, or off-network instruction is re-issued by the platform within the set time period, a charging permission instruction is automatically initiated to the battery swap controller, and its own state is changed to the off-network state.

[0029] In a second aspect, the present invention provides a vehicle-mounted TBOX, comprising:

[0030] at least one processor; and

[0031] a memory communicatively connected to the at least one processor; wherein,

[0032] The memory stores one or more computer programs that can be executed by the at least one processor, and the one or more computer programs are executed by the at least one processor so that the at least one processor can execute the vehicle charging control method as described in the first aspect.

[0033] In a third aspect, the present invention provides a vehicle charging control method, which is applied to a platform and comprises the following steps:

[0034] Receive the user's network access command and network exit command, and send the network access configuration command and network exit configuration command to the vehicle-mounted TBOX in real time, so that when the vehicle-mounted TBOX receives the network access configuration command, it responds to the network access configuration command and feeds back the configuration status to the platform; when the vehicle-mounted TBOX receives the network exit configuration command, it determines the current vehicle's charging permission status. If the current vehicle is in a charging-allowed state, it allows network exit, responds to the network exit configuration command, and feeds back the network exit success result to the platform; if the current vehicle is in a charging-prohibited state, it does not allow network exit, and feeds back the network exit failure result to the platform;

[0035] Receive configuration results fed back by TBOX;

[0036] The charging control command is sent to the on-board TBOX so that when the vehicle is connected to the network and charging is allowed, the on-board TBOX sends the charging control command to the battery swap controller to realize the charging control function of the vehicle.

[0037] Further, receive the off-station charging energy message pushed by TBOX with scheduled changes, including subtotal off-station charging energy, battery charging status, accumulated charging energy, and current off-station charging permission status information;

[0038] According to the off-station charging energy information reported by TBOX, the platform operation strategy and rules, the vehicle's remaining balance this month and the off-station charging permission status are calculated, and the off-station charging energy response message is replied to TBOX in real time, so that TBOX can receive the platform's off-station charging energy response message and send the corresponding off-station charging instruction to the battery swap controller in real time, so as to realize real-time control of the vehicle's off-station charging.

[0039] In a fourth aspect, the present invention provides a platform, comprising:

[0040] at least one processor; and

[0041] a memory communicatively connected to the at least one processor; wherein,

[0042] The memory stores one or more computer programs that can be executed by the at least one processor, and the one or more computer programs are executed by the at least one processor so that the at least one processor can execute the vehicle charging control method as described in the third aspect.

[0043] In a fifth aspect, the present invention provides a vehicle charging control system, comprising:

[0044] The vehicle-mounted TBOX adopts the vehicle-mounted TBOX as described in the second aspect;

[0045] A platform, using the platform as described in the fourth aspect;

[0046] A battery swap controller, which is connected to the vehicle-mounted TBOX and is used to perform charging operations according to instructions from the vehicle-mounted TBOX. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 A flow chart of a vehicle charging control method provided by an embodiment of the present invention;

[0048] Figure 2 An example of an error information table returned to the platform;

[0049] Figure 3 This is an example of a parameter description table;

[0050] Figure 4 This is an example of a common return code table;

[0051] Figure 5 An example of the message format for configuring network entry and exit. DETAILED DESCRIPTION

[0052] In order to enable those skilled in the art to better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiment of the present invention. Obviously, the described embodiment is a part of the embodiment of the present invention, not all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0053] Embodiment 1

[0054] See also Figure 1 The embodiment of the present invention discloses a vehicle charging control method, which is applied to a vehicle-mounted TBOX, and comprises the following steps:

[0055] Get a login token and use it to log in to the platform;

[0056] Receive configuration information issued by the platform, including network entry configuration commands and network exit configuration commands;

[0057] When receiving the network access configuration command issued by the platform, respond to the network access configuration command and feedback the configuration status to the platform;

[0058] When receiving the network disconnection configuration command issued by the platform, the charging permission status of the current vehicle is determined. If the current vehicle is in a charging-allowed state, network disconnection is allowed, and the network disconnection configuration command is responded to, and the network disconnection success result is fed back to the platform. If the current vehicle is in a charging-prohibited state, network disconnection is not allowed, and the network disconnection failure result is fed back to the platform;

[0059] Receive the charging control instructions issued by the platform. When the vehicle is in the network state, determine whether the vehicle is allowed to charge. If so, send the charging control instructions to the battery swap controller for the battery swap controller to execute the charging control instructions. When the vehicle is in the off-grid state, do not send the charging control instructions to the battery swap controller.

[0060] Vehicle de-networking usually means that the vehicle is removed from a network or system and no longer participates in the data transmission or function implementation of the network.

[0061] The steps for delisting a vehicle include:

[0062] 1) Identification and authentication: First, the system needs to identify the vehicle that needs to be delisted, which is usually achieved through the vehicle's unique identifier (such as the VIN code). Then, the vehicle is authenticated to ensure that only legitimate vehicles are allowed to be delisted.

[0063] 2) Data cleaning: Before a vehicle is de-networked, all relevant data stored in the network must be cleaned up, including vehicle status information, driving records, user information, etc., to protect user privacy and data security.

[0064] 3) Revocation of permissions: Revoke the vehicle’s access rights in the network, including data transmission permissions, service usage permissions, etc., to ensure that the vehicle can no longer access any resources in the network after it is delisted.

[0065] Vehicle network access means that the vehicle joins a network or system and begins to participate in the data transmission or function implementation of the network.

[0066] The steps for vehicle network access include:

[0067] 1) Registration and authentication: The vehicle must first be registered and provide the necessary vehicle information and user information. The system authenticates the vehicle to ensure its authenticity and legality.

[0068] 2) Authority allocation: Assign corresponding network access rights and service usage rights to the vehicle based on the vehicle type, purpose and user needs.

[0069] 3) Data synchronization: Synchronize the vehicle's basic information, status information, user information, etc. to the network so that other systems or devices can obtain and use this information.

[0070] TBOX is used for operating vehicles. The reasons for configuring the network entry and exit status of operating vehicles are mainly based on the following considerations: 1) Regulatory needs: Network entry means that operating vehicles transmit qualified dynamic data to the provincial or higher-level regulatory platform at least once. This is to ensure that the regulatory authorities can grasp the operating status of the vehicle in real time, including location, speed, driver behavior, etc., in order to carry out effective supervision. When an operating vehicle no longer meets the operating conditions or reaches the scrap standard, it needs to exit the network and no longer carry out operating activities. The setting of the exit status helps the management department to manage the vehicle throughout its life cycle. 2) Compliance needs: The calculation of indicators such as network entry rate helps the management department to evaluate the management level of operating vehicles and promptly discover and solve existing problems. According to relevant regulations, operating vehicles need to meet certain conditions before they can engage in operating activities such as online car-hailing. When the vehicle no longer meets these conditions, it needs to exit the operating market. The current status of allowing charging before de-networking is based on usage considerations. When some vehicles are converted from operating vehicles to non-operating vehicles (or need to be out of management for other reasons), they need to be de-networked. At this time, the normal use of the vehicle cannot be affected. Therefore, it is necessary to ensure that the vehicle can be charged normally. If it is in a charging prohibited state, the vehicle cannot be used normally after the battery is consumed.

[0071] The present invention provides a vehicle charging control method based on TBOX (Telematics Box), which aims to optimize the charging process of electric vehicles through highly integrated intelligent management technology. The core of the invention is to make full use of the communication capability, data processing capability and vehicle network interconnection characteristics of TBOX, combined with cloud computing and big data analysis, to provide a set of efficient, safe and convenient solutions for electric vehicle charging.

[0072] In the initial state, the vehicle is disconnected from the network by default.

[0073] One embodiment is: a charging quota is set in the configuration information of the platform, and the quota is not consumed when the vehicle is charged in the station, and the quota is consumed only when the vehicle is charged outside the station.

[0074] Furthermore, the charging control instructions issued by the receiving platform are sent. When the vehicle is in the network state, if the vehicle is allowed to charge, it is also necessary to determine whether the current charging amount is greater than the preset value. When the current charging amount is greater than the preset value, the charging control instructions are sent to the battery swap controller.

[0075] The preset value of the present invention is set as required. For example, the preset value is set to 0.

[0076] A login token consists of a username and a password.

[0077] Furthermore, obtaining a login token includes:

[0078] S101, determining whether it is necessary to obtain a login token;

[0079] If yes, execute step S102;

[0080] S102, connect to the http server and determine whether the login is successful;

[0081] If the login is unsuccessful, the process returns to step S102;

[0082] If the login is successful, execute step S103;

[0083] S103, sending a request message for obtaining a login token to the server. If the login token is successfully obtained, the login token is stored. If the login token is not obtained, the process returns to step S103.

[0084] In the field of computer network security, data integrity and identity authentication are crucial. The present invention adopts an improved signature algorithm to obtain a device login token. The algorithm adopts a message authentication code algorithm based on the MD5 hash function and a key. It generates a 32-bit hash value by combining the key and the message content to verify the integrity and identity of the message.

[0085] Further, sending a request message for obtaining a login token to the server specifically includes:

[0086] Prepare keys and messages: First, you need to prepare a key and the message to be authenticated. Combine the key and the original message to be authenticated to generate an encrypted field, where the encrypted field contains the current timestamp timestamp = now() and the unique random string nonce = random(), followed by the key. For example, the encrypted field contains the current timestamp timestamp = now() and the unique random string nonce = random(), followed by the key secret_key = cic027 (customize the exclusive field as needed) to improve the security of encryption.

[0087] Process the message content: Sort all non-empty request parameters (except sign itself) in ascending order according to the request parameter name (bubble sort is used here to facilitate automatic field expansion and sorting) to generate a json format string as follows:

[0088] stringA = "{"app_key":"aaapppkkk","name":"cic","nonce":"drowolleh","timestamp":1683860014000}"; app_key is a caller identification string used to identify and verify the caller (such as an application or developer). It is similar to an ID number or key and is used for identity authentication and authorization during API interface calls. It is provided by the demander. Name refers to the device name. It is generally recommended to use the vehicle frame number. timestamp refers to the timestamp, accurate to milliseconds. nonce refers to a unique random string.

[0089] Add the JSON format string to the encrypted field to form a new login token request message.

[0090] Padding key: If the key length is less than 64 bytes, it is padded to 64 bytes; if the key length is greater than 64 bytes, the MD5 hash value of the key is taken as the new key.

[0091] Perform an internal hash operation: perform a bitwise exclusive OR (XOR) operation on the padded key and the message, and the result is called the first result, called "ipad". Perform an AND operation on the padded key and the message, and the second result is called "opad".

[0092] Calculate and output the result: concatenate the first result "ipad", the message and the second result "opad" together and input them into the MD5 hash function for calculation to obtain the final 32-bit hash value. Convert the calculated 32-bit hash value to uppercase as the authentication result of the algorithm.

[0093] Then the message and the message authentication code are sent to the server, so that after receiving the message and the message authentication code, the server uses the same key and message content to recalculate the message authentication code through the same message authentication code algorithm, and compares the message authentication code calculated by itself with the message authentication code received from the TBOX. If the two message authentication codes are consistent, the authentication is successful, and the login token is issued to the TBOX. If the two message authentication codes are inconsistent, the authentication fails. The server and the platform of the present invention can be different platforms.

[0094] In the field of computer network security, data integrity and authentication are crucial. An improved signature algorithm is used here to obtain a device login token.

[0095] The algorithm uses a message authentication code algorithm based on the MD5 hash function and a key. It generates a 32-bit hash value by combining the key and the message content to verify the integrity and identity of the message.

[0096] The improved signature algorithm of the present invention has the following advantages:

[0097] 1) Strong security: It can effectively prevent messages from being tampered with or forged, and ensure data integrity and identity authentication.

[0098] 2) Fast and efficient: It has fast computing speed and is suitable for encrypting and authenticating large amounts of data.

[0099] 3) Simple algorithm: The implementation is relatively simple and takes up less computing resources.

[0100] Furthermore, the vehicle charging control method of the present invention further includes the following steps:

[0101] Push off-station charging energy messages to the platform at regular intervals, so that the platform can calculate the vehicle's remaining balance this month and off-station charging permission status based on the reported off-station charging energy messages, platform operation strategies and rules, and reply to the off-station charging energy response message to TBOX in real time, thus achieving real-time control of off-station charging of vehicles;

[0102] Off-site charging energy messages include subtotal off-site charging energy, battery charging status, accumulated charging energy, and current off-site charging permission status;

[0103] Receive the platform's off-site charging energy response message and send the corresponding off-site charging instruction to the battery swap controller in real time.

[0104] In order to avoid the situation where the vehicle cannot be charged outside the station after being de-energized, it must be ensured that the vehicle is allowed to charge outside the station before being de-energized.

[0105] Furthermore, when receiving the off-network configuration command issued by the management end (platform side), the vehicle status is verified and the charging permission status of the current vehicle is determined. If the current vehicle is in a charging prohibited state, the off-network failure result is fed back to the platform. If no charging permission, charging prohibition, or network access or off-network instruction is re-issued by the platform within the set time period, a charging permission instruction is automatically initiated to the battery swap controller, and its own status is changed to the off-network state.

[0106] After receiving the network exit instruction from the management side (platform side), the TBOX side clearly interprets the network exit request.

[0107] Verify vehicle status: Before executing the disconnection command, TBOX needs to verify the current status of the vehicle to confirm whether it is in a charging prohibited state. This can be achieved by communicating with the vehicle to obtain its real-time status information.

[0108] If the vehicle status is abnormal (such as unable to communicate, inconsistent status information, etc.), TBOX should be able to identify and take corresponding processing measures, such as delaying the exit from the network and feeding back the failure information to the platform. The specific implementation is: 1) If TBOX loses the network when the platform issues an instruction, the next time TBOX logs in to the platform again, the platform side will try to re-issue the exit command based on the current status reported by TBOX. 2) When the platform issues an instruction, the status obtained is a charging prohibited state. TBOX needs to feedback the exit failure to the platform and inform the platform that the current charging state is prohibited. If the platform does not re-issue the permission, prohibition of charging, or entry and exit instructions to the TBOX within the set time period (such as 12 hours), TBOX automatically initiates a charging permission instruction to BMS and changes its own status to the exit state.

[0109] Based on the same inventive concept, the embodiment of the present disclosure provides a vehicle-mounted TBOX, including: one or more processors, a memory, and one or more I / O interfaces. One or more programs are stored in the memory, and when the one or more programs are executed by the one or more processors, the one or more processors implement the vehicle charging control method described above in this embodiment; one or more I / O interfaces are connected between the processor and the memory, and are configured to implement information interaction between the processor and the memory.

[0110] Based on the same inventive concept, the embodiment of the present disclosure further provides a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the steps in the vehicle charging control method described above are implemented.

[0111] Embodiment 2

[0112] The embodiment of the present invention provides a vehicle charging control method, which is applied to a platform and includes the following steps:

[0113] Receive the user's network access command and network exit command, and send the network access configuration command and network exit configuration command to the vehicle-mounted TBOX in real time, so that when the vehicle-mounted TBOX receives the network access configuration command, it responds to the network access configuration command and feeds back the configuration status to the platform; when the vehicle-mounted TBOX receives the network exit configuration command, it determines the current vehicle's charging permission status. If the current vehicle is in a charging-allowed state, it allows network exit, responds to the network exit configuration command, and feeds back the network exit success result to the platform; if the current vehicle is in a charging-prohibited state, it does not allow network exit, and feeds back the network exit failure result to the platform;

[0114] Receive configuration results fed back by TBOX;

[0115] The charging control command is sent to the on-board TBOX so that when the vehicle is connected to the network and charging is allowed, the on-board TBOX sends the charging control command to the battery swap controller to realize the charging control function of the vehicle.

[0116] Further, receive the off-station charging energy message pushed by TBOX with scheduled changes, including subtotal off-station charging energy, battery charging status, accumulated charging energy, and current off-station charging permission status information;

[0117] According to the off-station charging energy information reported by TBOX, the platform operation strategy and rules, the vehicle's remaining balance this month and the off-station charging permission status are calculated, and the off-station charging energy response message is replied to TBOX in real time, so that TBOX can receive the platform's off-station charging energy response message and send the corresponding off-station charging instruction to the battery swap controller in real time, so as to realize real-time control of the vehicle's off-station charging.

[0118] Based on the same inventive concept, the embodiment of the present disclosure provides a platform, including: one or more processors, a memory, and one or more I / O interfaces. One or more programs are stored in the memory, and when the one or more programs are executed by the one or more processors, the one or more processors implement the vehicle charging control method described above in this embodiment; one or more I / O interfaces are connected between the processor and the memory, and are configured to implement information interaction between the processor and the memory.

[0119] Based on the same inventive concept, an embodiment of the present disclosure further provides a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the steps in the vehicle charging control method described above in the embodiment are implemented.

[0120] Embodiment 3

[0121] The embodiment of the present invention provides a vehicle charging control system, including a vehicle-mounted TBOX (Telematics Box), a battery replacement controller BMS and a platform TSP (Telematics Service Provider);

[0122] The vehicle-mounted TBOX adopts the vehicle-mounted TBOX as described in the first embodiment; the TBOX is a telematics processor installed on the vehicle, which is a bridge between the vehicle and the TSP. The TBOX is responsible for receiving instructions from the TSP and performing corresponding charging control operations.

[0123] The platform is TSP (Telematics Service Provider), which adopts the platform described in Example 2; the platform is TSP (Telematics Service Provider), which serves as a telematics service provider and is responsible for receiving user instructions, communicating with TBOX through the MQTT protocol, and transmitting charging instructions.

[0124] The battery swap controller BMS is connected to the vehicle-mounted TBOX, and is used to perform charging operations according to the instructions of the vehicle-mounted TBOX.

[0125] T-BOX obtains the MQTT device login token through the HTTP API interface on the platform side, and T-BOX provides IMEI as the unique device ID. Figure 2 An example of an error information table returned to the platform.

[0126] T-BOX login token logs in to the MQTT link and interacts with the platform.

[0127] T-BOX performs authentication through the connect message of the MQTT protocol. All parts of the information for constructing the clientId must be included. When the platform receives the connect message, it will determine the device's authentication type and password digest algorithm. When the "HMACSHA256" timestamp verification method is used, the message timestamp will be checked first to see if it is consistent with the platform time, and then the password will be determined to be correct. When the "HMACSHA256" timestamp non-verification method is used, the authentication message must also have a timestamp, but the time is not checked for accuracy, and only the password is determined to be correct. When the connect message authentication fails, the platform will return an error and automatically disconnect the MQTT link. Figure 3 This is an example of a parameter description table. Figure 4 This is an example of a common return code table.

[0128] When the vehicle is in the network state, TBOX accepts and responds to the charging control instructions issued by the platform; when the vehicle is in the network-off state, TBOX does not respond to the charging control instructions of the platform. In the initial state, the vehicle is in the network-off state by default. The platform receives the user's network access and network-off instructions (the user issues instructions by clicking the network access and network-off buttons), and issues network access and network-off configuration commands to the vehicle TBOX in real time; after receiving the network access and network-off configuration commands issued by the platform, TBOX needs to reply with the configuration result and the current TBOX software version number. In order to avoid the vehicle being unable to charge outside the station after the network is off, it must be ensured that the vehicle is allowed to charge outside the station before the network is off. When TBOX receives the network-off configuration issued by the platform, it determines that if the current charging permission status allows charging, it can be off the network and reply that the network is successful, otherwise it is not allowed to be off the network and reply that the network is failed. Correspondingly, when the platform sends the network-off configuration, if the current vehicle allows charging outside the station, it starts to send the network-off configuration to TBOX, otherwise it prompts that the network is failed.

[0129] The platform sends the network status and quota configuration to TBOX, indicating whether the vehicle has been connected to the platform or disconnected from the platform and the off-station charging quota; TBOX determines whether to respond to the charging control command issued by the platform based on this configuration. When connected to the network, it receives the charging control command and transmits it to BMS. When disconnected from the network, it does not respond or forward the charging control command; the network connection and disconnection configuration needs to be saved by TU. The specific message format is as follows: Figure 5 shown.

[0130] TBOX pushes off-site charging energy messages to the platform at regular intervals, including subtotal off-site charging energy, battery charging status, cumulative charging energy, current off-site charging permission status and other information. Based on the off-site charging energy messages reported by TBOX, the platform's operating strategies and rules, the platform calculates the vehicle's remaining quota this month and the off-site charging permission status, and replies to TBOX in real time, thereby achieving real-time control of the vehicle's off-site charging. TBOX receives the off-site charging energy response message from the platform and sends the corresponding off-site charging instructions to BMS in real time. At the same time, the platform also needs to send remote control charging, charging current, monthly charging quota configuration and other instructions to TBOX to achieve the charging control function of the vehicle.

[0131] Among them, the processor is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.; the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); the I / O interface (read-write interface) is connected between the processor and the memory, and can realize information exchange between the processor and the memory, including but not limited to a data bus (Bus), etc.

[0132] In some embodiments, the processor, memory, and I / O interface are connected to each other and, in turn, to other components of the computing device via a bus.

[0133] In some embodiments, the one or more processors include a field programmable gate array.

[0134] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, including a computer program carried on a machine-readable medium, the computer program containing a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication part, and / or installed from a removable medium. When the computer program is executed by a central processing unit (CPU), the above-mentioned functions defined in the system of the present disclosure are executed.

[0135] It should be noted that the computer-readable medium shown in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0136] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of the code, and the aforementioned module, program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0137] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present disclosure, but the present disclosure is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and substance of the present disclosure, and these modifications and improvements are also considered to be within the scope of protection of the present disclosure.

Claims

1. A vehicle charging control method, characterized in that: Applied to vehicle-mounted TBOX, including the following steps: Get a login token and use it to log in to the platform; Receive configuration information issued by the platform, including network entry configuration commands and network exit configuration commands; When receiving the network access configuration command issued by the platform, respond to the network access configuration command and feedback the configuration status to the platform; When receiving the network disconnection configuration command issued by the platform, the charging permission status of the current vehicle is determined. If the current vehicle is in a charging-allowed state, network disconnection is allowed, and the network disconnection configuration command is responded to, and the network disconnection success result is fed back to the platform. If the current vehicle is in a charging-prohibited state, network disconnection is not allowed, and the network disconnection failure result is fed back to the platform; Receive the charging control instructions issued by the platform. When the vehicle is in the network state, determine whether the vehicle is allowed to charge. If so, send the charging control instructions to the battery swap controller for the battery swap controller to execute the charging control instructions. When the vehicle is in the off-grid state, do not send the charging control instructions to the battery swap controller.

2. The vehicle charging control method according to claim 1, characterized in that: Receive the charging control instructions issued by the platform. When the vehicle is in the network state, if the vehicle is allowed to charge, it is also necessary to determine whether the current charging amount is greater than the preset value. When the current charging amount is greater than the preset value, the charging control instructions are sent to the battery swap controller.

3. The vehicle charging control method according to claim 1, characterized in that: Get the login token, including: Determine whether it is necessary to obtain a login token; If yes, a request message for obtaining a login token is sent to the server, including: Obtain the key and the original message to be authenticated; Process the message content: sort all non-empty request parameters in ascending order according to the request parameter name and generate a string in JSON format; Padding key: If the key length is less than 64 bytes, it is padded to 64 bytes; if the key length is greater than 64 bytes, the MD5 hash value of the key is taken as the new key; Perform an internal hash operation: perform a bitwise XOR operation on the padded key and the message to obtain a first result, and perform an AND operation on the padded key and the message to obtain a second result; Calculate and output the result: concatenate the first result, the message, and the second result together and input them into the MD5 hash function for calculation to obtain the final 32-bit hash value as the message authentication code; Send the message and the message authentication code to the server, so that after receiving the message and the message authentication code, the server uses the same key and message content, and the same message authentication code algorithm to recalculate the message authentication code, and compares the message authentication code calculated by itself with the message authentication code received from TBOX. If the two message authentication codes are consistent, the authentication is successful, and the login token is issued to TBOX.

4. The vehicle charging control method according to claim 1, characterized in that: The following steps are also included: pushing off-station charging energy messages to the platform at regular intervals, so that the platform can calculate the vehicle's remaining quota this month and off-station charging permission status based on the reported off-station charging energy messages, platform operation strategies and rules, and reply to the off-station charging energy response message to TBOX in real time, so as to realize real-time control of the vehicle's off-station charging; Off-site charging energy messages include subtotal off-site charging energy, battery charging status, accumulated charging energy, and current off-site charging permission status; Receive the platform's off-site charging energy response message and send the corresponding off-site charging instruction to the battery swap controller in real time.

5. The vehicle charging control method according to claim 1, characterized in that: When receiving the off-grid configuration command issued by the platform, the charging permission status of the current vehicle is determined. If the current vehicle is in a charging prohibited state, the off-grid failure result is fed back to the platform. If no charging permission, charging prohibition, network access, or off-grid command is received from the platform again within the set time period, a charging permission command is automatically initiated to the battery swap controller, and its own state is changed to the off-grid state.

6. A vehicle-mounted TBOX, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores one or more computer programs that can be executed by the at least one processor, and the one or more computer programs are executed by the at least one processor to enable the at least one processor to execute the vehicle charging control method according to any one of claims 1 to 5.

7. A vehicle charging control method, characterized in that: Applied to the platform, including the following steps: Receive the user's network access command and network exit command, and send the network access configuration command and network exit configuration command to the vehicle-mounted TBOX in real time, so that when the vehicle-mounted TBOX receives the network access configuration command, it responds to the network access configuration command and feeds back the configuration status to the platform; when the vehicle-mounted TBOX receives the network exit configuration command, it determines the current vehicle's charging permission status. If the current vehicle is in a charging-allowed state, it allows network exit, responds to the network exit configuration command, and feeds back the network exit success result to the platform; if the current vehicle is in a charging-prohibited state, it does not allow network exit, and feeds back the network exit failure result to the platform; Receive configuration results fed back by TBOX; The charging control command is sent to the on-board TBOX so that when the vehicle is connected to the network and charging is allowed, the on-board TBOX sends the charging control command to the battery swap controller to realize the charging control function of the vehicle.

8. The vehicle charging control method according to claim 7, characterized in that: Receive off-station charging energy messages pushed by TBOX on a scheduled basis, including subtotal off-station charging energy, battery charging status, accumulated charging energy, and current off-station charging permission status information; According to the off-station charging energy information reported by TBOX, the platform operation strategy and rules, the vehicle's remaining balance this month and the off-station charging permission status are calculated, and the off-station charging energy response message is replied to TBOX in real time, so that TBOX can receive the platform's off-station charging energy response message and send the corresponding off-station charging instruction to the battery swap controller in real time, so as to realize real-time control of the vehicle's off-station charging.

9. A platform, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores one or more computer programs that can be executed by the at least one processor, and the one or more computer programs are executed by the at least one processor to enable the at least one processor to execute the vehicle charging control method as described in any one of claims 7-8.

10. A vehicle charging control system, characterized in that: include: The vehicle-mounted TBOX adopts the vehicle-mounted TBOX as claimed in claim 6; A platform, comprising the platform as claimed in claim 9; A battery swap controller, which is connected to the vehicle-mounted TBOX and is used to perform charging operations according to instructions from the vehicle-mounted TBOX.

Images