Vehicle-mounted TBOX part changing system, method and equipment and storage medium

Abstract

The invention discloses a vehicle-mounted TBOX part changing system, method and device and a storage medium, and the system comprises the steps that a vehicle-mounted TBOX detects whether a local configuration VIN code is consistent with a remote configuration VIN code through a VIN code conflict detection unit, and if not, VIN code conflict is triggered; calling the TBOX S / N data by the TSP platform, matching the TBOX S / N data with the VIN code associated data built in the VIN code associated system, and after the matching succeeds; and the vehicle-mounted TBOX updates the remote configuration VIN code according to the VIN code remote configuration instruction, and returns VIN code conflict detection until the VIN codes are consistent, the VIN code conflict event is reported, and vehicle-mounted TBOX part changing is completed. According to the invention, VIN code conflict detection is carried out through the VIN code conflict detection unit, the vehicle-mounted TBOX, the TSP platform and the VIN code association system carry out data linkage, automatic matching of conflict events is realized, and the configuration efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of TBOX replacement, in particular to a vehicle-mounted TBOX replacement system, method, device and storage medium. BACKGROUND

[0002] As a core component of the Internet of Vehicles, the vehicle-mounted TBOX undertakes key functions such as vehicle data collection, remote control instruction transmission, TSP platform communication, etc., and its binding relationship with the vehicle ECU and TSP platform directly determines the availability of the Internet of Vehicles function. The existing TBOX replacement process needs manual cross-platform information input, and the binding and protocol adaptation of the TBOX and the TSP platform need to be operated in steps, which takes a long time for single vehicle replacement and is prone to TBOX binding replacement failure due to manual input errors. Therefore, how to improve the configuration efficiency while reducing the cost and ensuring the accuracy rate has become a problem to be solved.

[0003] The above content is only used to assist in understanding the technical solutions of the present application and does not represent the acknowledgement of the above content as prior art. SUMMARY The main purpose of the present application is to provide a vehicle-mounted TBOX replacement system, method, device and storage medium, which aims to solve the technical problem of how to improve the configuration efficiency while reducing the cost and ensuring the accuracy rate.

[0004] To achieve the above purpose, the present application provides a vehicle-mounted TBOX replacement system, which comprises a VIN code writing device, a vehicle-mounted TBOX, a TSP platform and a VIN code association system, and the vehicle-mounted TBOX comprises a VIN code conflict detection unit: The VIN code writing device is used to write the real vehicle VIN code based on the TBOX application scene, and send the real vehicle VIN code to the vehicle-mounted TBOX; The vehicle-mounted TBOX is used to take the real vehicle VIN code as a local configuration VIN code, detect whether the local configuration VIN code is consistent with a remote configuration VIN code through the VIN code conflict detection unit, if not, trigger a VIN code conflict, and report a VIN code conflict event to the TSP platform; The TSP platform is used to call pre-stored TBOX S / N data, match the pre-stored TBOX S / N data with the VIN code association data of the VIN code association system, after successful matching, send a VIN code remote configuration instruction to the vehicle-mounted TBOX; The vehicle-mounted TBOX is also used to update the remote configuration VIN code according to the VIN code remote configuration instruction, and returns the operation of detecting whether the locally configured VIN code is consistent with the remote configuration VIN code by the VIN code conflict detection unit until the locally configured VIN code is consistent with the remote configuration VIN code, the VIN code conflict event reporting is ended, and the vehicle-mounted TBOX replacement is completed.

[0005] Optionally, the writing of the real vehicle VIN code based on the TBOX application scenario comprises: The VIN code writing device is connected with the vehicle OBD interface; Based on the TBOX application scenario, the real vehicle VIN code is written through the vehicle OBD interface.

[0006] Optionally, the vehicle-mounted TBOX further comprises a VIN code storage unit; The VIN code storage unit is used to store the locally configured VIN code and the remote configuration VIN code in a partitioned manner.

[0007] Optionally, the vehicle-mounted TBOX further comprises a data reporting unit; The reporting of the VIN code conflict event to the TSP platform comprises: Based on the vehicle cloud protocol, the VIN code conflict event is reported to the TSP platform through the data reporting unit.

[0008] Optionally, the TSP platform comprises a conflict receiving unit and a data matching unit; The calling of the pre-stored TBOX S / N data, the matching of the pre-stored TBOX S / N data with the VIN code association data synchronized with the VIN code association system, comprises: After the conflict receiving unit receives the VIN code conflict event, the pre-stored TBOX S / N data is called through the data matching unit, and the pre-stored TBOX S / N data is matched with the VIN code association data synchronized with the VIN code association system.

[0009] Optionally, the TSP platform further comprises a remote configuration unit; The sending of the VIN code remote configuration instruction to the vehicle-mounted TBOX comprises: The VIN code remote configuration instruction is generated through the remote configuration unit according to the VIN code association data, and the VIN code remote configuration instruction is sent to the vehicle-mounted TBOX based on the MQTT protocol.

[0010] Optionally, the updating of the remote configuration VIN code according to the VIN code remote configuration instruction comprises: extracting a real vehicle VIN code from the VIN code remote configuration instruction; updating the remote configuration VIN code according to the real vehicle VIN code.

[0011] In addition, to achieve the above-mentioned purpose, the application further provides a vehicle TBOX replacement method, which comprises the following steps: The VIN code writing device writes a real vehicle VIN code based on a vehicle application scenario and sends the real vehicle VIN code to a vehicle TBOX; The vehicle TBOX takes the real vehicle VIN code as a local configuration VIN code, detects whether the local configuration VIN code is consistent with a remote configuration VIN code through a VIN code conflict detection unit, triggers a VIN code conflict if the local configuration VIN code is inconsistent with the remote configuration VIN code, and reports a VIN code conflict event to a TSP platform; The TSP platform calls pre-stored TBOX S / N data, matches the pre-stored TBOX S / N data with VIN code associated data of a VIN code association system, sends a VIN code remote configuration instruction to the vehicle TBOX after successful matching, and returns the operation of detecting whether the local configuration VIN code is consistent with the remote configuration VIN code through the VIN code conflict detection unit until the local configuration VIN code is consistent with the remote configuration VIN code, the VIN code conflict event reporting is ended, and the vehicle TBOX replacement is completed. The vehicle TBOX updates the remote configuration VIN code according to the VIN code remote configuration instruction and returns the operation of detecting whether the local configuration VIN code is consistent with the remote configuration VIN code through the VIN code conflict detection unit until the local configuration VIN code is consistent with the remote configuration VIN code, the VIN code conflict event reporting is ended, and the vehicle TBOX replacement is completed.

[0012] In addition, to achieve the above-mentioned purpose, the application further provides a vehicle TBOX replacement device, which comprises a memory, a processor, and a vehicle TBOX replacement program stored in the memory and executable on the processor, and the vehicle TBOX replacement program is configured to implement the steps of the vehicle TBOX replacement method as described above.

[0013] In addition, to achieve the above-mentioned purpose, the application further provides a storage medium, which stores a vehicle TBOX replacement program, and the vehicle TBOX replacement program implements the steps of the vehicle TBOX replacement method as described above when executed by a processor.

[0014] The application first writes the real vehicle VIN code based on the TBOX application scene by the VIN code writing device, and sends the real vehicle VIN code to the vehicle-mounted TBOX, then the vehicle-mounted TBOX takes the real vehicle VIN code as the local configuration VIN code, detects whether the local configuration VIN code is consistent with the remote configuration VIN code through the VIN code conflict detection unit, if not, triggers the VIN code conflict, and reports the VIN code conflict event to the TSP platform, then the TSP platform calls the pre-stored TBOX S / N data, matches the pre-stored TBOX S / N data with the VIN code associated data of the VIN code synchronization system, after successful matching, sends the VIN code remote configuration instruction to the vehicle-mounted TBOX, finally the vehicle-mounted TBOX updates the remote configuration VIN code according to the VIN code remote configuration instruction, and returns the operation of detecting whether the local configuration VIN code is consistent with the remote configuration VIN code through the VIN code conflict detection unit, until the local configuration VIN code is consistent with the remote configuration VIN code, the VIN code conflict event reporting ends, and the vehicle-mounted TBOX replacement is completed. The application realizes the active detection and standardized reporting of the VIN code conflict through the double-VIN code isolation storage and permission control logic of the local configuration VIN code and the remote configuration VIN code, combined with the conflict reporting mechanism of the vehicle cloud protocol, then constructs the three-party data linkage of TBOX-TSP platform-MES, realizes the automatic matching of the vehicle VIN code, TBOX S / N and conflict event, without manual intervention, and greatly improves the configuration efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 is a structural schematic diagram of the vehicle-mounted TBOX replacement device of the hardware running environment involved in the embodiment scheme of the application. Figure 2 is a structural block diagram of the first embodiment of the vehicle-mounted TBOX replacement system of the application. Figure 3 is a flowchart of the first embodiment of the vehicle-mounted TBOX replacement method of the application.

[0016] The implementation, functional features and advantages of the application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0017] It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

[0018] Referring to Figure 1 , Figure 1 is a structural schematic diagram of the vehicle-mounted TBOX replacement device of the hardware running environment involved in the embodiment scheme of the application.

[0019] As Figure 1As shown, the vehicle-mounted TBOX replacement device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be high-speed random access memory (RAM) or stable non-volatile memory (NVM), such as a disk storage device. Optionally, the memory 1005 may also be a storage system independent of the aforementioned processor 1001.

[0020] Those skilled in the art will understand that Figure 1 The structure shown does not constitute a limitation on the vehicle-mounted TBOX replacement equipment and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0021] like Figure 1 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a network communication module, a user interface module, and a vehicle-mounted TBOX replacement program.

[0022] exist Figure 1 In the vehicle-mounted TBOX replacement device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the vehicle-mounted TBOX replacement device of the present invention can be set in the vehicle-mounted TBOX replacement device, and the vehicle-mounted TBOX replacement device calls the vehicle-mounted TBOX replacement program stored in the memory 1005 through the processor 1001 and executes the vehicle-mounted TBOX replacement method provided in the embodiment of the present invention.

[0023] This invention provides an in-vehicle TBOX replacement system, referring to... Figure 2 , Figure 2 This is a structural block diagram of the first embodiment of the vehicle-mounted TBOX replacement system of the present invention.

[0024] In this embodiment, the vehicle-mounted TBOX replacement system includes a VIN code writing device 2001, a vehicle-mounted TBOX 2002, a TSP platform 2003, and a VIN code association system 2004. The vehicle-mounted TBOX 2002 includes a VIN code conflict detection unit 2020. The VIN code writing device is either the production line assembly equipment or the after-sales diagnostic tool. In the passenger vehicle assembly process, the assembly equipment writes the actual vehicle VIN code to the TBOX via the OBD interface, and the VIN code storage unit of the vehicle TBOX saves the actual vehicle VIN code as the local configuration VIN code. In the after-sales parts replacement scenario, the after-sales diagnostic tool writes the actual vehicle VIN code to the new TBOX, and the VIN code storage unit of the vehicle TBOX saves the actual vehicle VIN code as the local configuration VIN code.

[0025] The vehicle-mounted TBOX has a built-in VIN code conflict detection unit, a data reporting unit, and a VIN code storage unit. The VIN code storage unit stores the local configuration VIN code (local writing only) and the remote configuration VIN code (i.e., TSP_VIN code, remote configuration only) in partitions. Both are set to a default value of all zeros at the factory. The VIN code conflict detection unit compares the local configuration VIN code and the remote configuration VIN code in real time. If they are inconsistent, a conflict event is triggered. The data reporting unit reports the VIN code conflict event to the TSP platform through the vehicle-cloud protocol. The VIN code conflict event includes conflict information, TBOX S / N, and the current VIN code status.

[0026] The TSP platform includes a conflict receiving unit, a data matching unit, a remote configuration unit, and a replacement rule verification unit. The conflict receiving unit receives VIN code conflict events reported by the TBOX. The data matching unit associates the vehicle VIN code and TBOX S / N information (i.e., "actual vehicle VIN code - TBOX S / N") entered into the MES / after-sales system, where "actual vehicle VIN code - TBOX S / N" is the VIN code associated data. The remote configuration unit issues VIN code configuration instructions based on the matching results. The replacement rule verification unit verifies the factory status of the new TBOX (confirming no historical binding records), allowing "new parts to replace old parts" and prohibiting "old parts to replace old parts".

[0027] The VIN code association system is either the production line MES system or the after-sales management system (i.e., MES / after-sales system): The assembly personnel use a barcode scanner to read the TBOX S / N and combine it with the vehicle VIN code to obtain the "actual vehicle VIN code - TBOX S / N" which is then entered into the MES / after-sales system. The MES / after-sales system synchronizes the "actual vehicle VIN code - TBOX S / N" association data to the data matching unit of the TSP backend module in real time.

[0028] VIN code writing device 2001 is used to write the actual vehicle VIN code based on the TBOX application scenario and send the actual vehicle VIN code to the vehicle TBOX 2002.

[0029] It should be noted that the application scenarios for TBOX can be either the replacement (activation) of TBOX parts after the production line of a new car OEM or the replacement of a brand new TBOX in an after-sales vehicle.

[0030] The vehicle-mounted TBOX2002 is used to use the actual vehicle VIN code as the local configuration VIN code. The VIN code conflict detection unit 2010 detects whether the local configuration VIN code and the remote configuration VIN code are consistent. If they are inconsistent, a VIN code conflict is triggered, and the VIN code conflict event is reported to the TSP platform 2003.

[0031] Furthermore, the VIN code writing device is connected to the vehicle's OBD interface; based on the TBOX application scenario, the actual vehicle VIN code is written through the vehicle's OBD interface; and the actual vehicle VIN code is stored as the local configuration VIN code.

[0032] It should be understood that the VIN code storage unit of the vehicle TBOX saves the actual vehicle VIN code as the local configuration VIN code, while the remote configuration VIN code is 0. The VIN code storage unit stores the local configuration VIN code and the remote configuration VIN code in separate partitions.

[0033] In a specific implementation, the vehicle-mounted TBOX also includes a data reporting unit; reporting VIN code conflict events to the TSP platform includes: based on the vehicle-cloud protocol, reporting VIN code conflict events to the TSP platform through the data reporting unit.

[0034] The TSP platform 2003 is used to call the pre-stored TBOX S / N data and match the pre-stored TBOX S / N data with the VIN code association data synchronized by the VIN code association system 2004. After a successful match, the VIN code remote configuration command is sent to the vehicle TBOX 2002.

[0035] Furthermore, the TSP platform includes a collision receiving unit and a data matching unit. After the collision receiving unit receives a VIN code collision event, it calls the pre-stored TBOX S / N data through the data matching unit based on the TBOX S / N in the VIN code collision event, and matches the pre-stored TBOX S / N data with the VIN code association data built into the VIN code association system. If the TBOX S / N in the VIN code association data matches the pre-stored TBOX S / N data, the match is successful; otherwise, the match fails.

[0036] The vehicle-mounted TBOX2002 is also used to update the remote configuration VIN code according to the VIN code remote configuration command, and return to the operation of checking whether the local configuration VIN code and the remote configuration VIN code are consistent through the VIN code conflict detection unit until the local configuration VIN code and the remote configuration VIN code are consistent. The VIN code conflict event reporting ends, and the vehicle-mounted TBOX replacement is completed.

[0037] Furthermore, the process of updating the remote configuration VIN code according to the VIN code remote configuration command is as follows: extract the actual vehicle VIN code from the VIN code remote configuration command; update the remote configuration VIN code according to the actual vehicle VIN code.

[0038] In the specific implementation, the VIN code in the instruction is updated to the TSP_VIN code partition of the VIN code storage unit; after the update is completed, the VIN code conflict detection unit compares the local configuration VIN code with the updated remote configuration VIN code again, and if the two are consistent, the reporting stops.

[0039] In this embodiment, the solution is illustrated through the following two scenarios: the replacement (activation) of the TBOX after the new vehicle OEM production line or the replacement of the TBOX with a brand new one in the aftermarket vehicle: I. Scenario for TBOX replacement (activation) after new car OEM production line: When a TBOX leaves the factory, its static data such as S / N and hardware version number are uploaded to the TSP backend module through the factory testing equipment to complete the pre-file. In the passenger vehicle final assembly process, the production line final assembly equipment writes the actual VIN code of the vehicle (i.e., the actual vehicle VIN code) to the TBOX through the OBD interface. The VIN code storage unit of the vehicle TBOX saves the actual vehicle VIN code as the local configuration VIN code. At this time, the remote configuration VIN code is 0. The VIN code storage unit stores the local configuration VIN code and the remote configuration VIN code in separate partitions. The VIN code conflict detection unit detects whether the local configuration VIN code and the remote configuration VIN code are consistent. If they are inconsistent, a VIN code conflict is triggered and the VIN code conflict event is reported to the TSP platform. After receiving a VIN code conflict event, the conflict receiving unit of the TSP platform calls the pre-stored TBOXS / N data and matches it with the "real vehicle VIN code - TBOXS / N" data synchronized with the MES system. After successful matching, the remote configuration unit generates a VIN code configuration command and sends it to the vehicle TBOX via the MQTT protocol. The vehicle-mounted TBOX extracts the actual vehicle VIN code from the remote configuration command of the VIN code, updates the VIN code in the command to the TSP_VIN code partition of the VIN code storage unit, and after the update is completed, the VIN code conflict detection unit compares the local configuration VIN code with the remote configuration code again. If the two are consistent, the reporting stops. Once the local configuration VIN code matches the remote configuration code, TBOX completes the production line offline activation, and the process ends.

[0040] II. Scenarios where a brand new TBOX is replaced on a vehicle after repair: The repair personnel removed the old TBOX from the original vehicle (the old TBOX was no longer working and was no longer bound to the vehicle), and installed the new TBOX (with both the local configuration VIN code and the remote configuration code being all 0s at the factory) in the designated location on the vehicle. They then connected the CAN bus, power supply, and communication interface. The repair personnel then connected the vehicle's OBD interface through the after-sales diagnostic tool and wrote the actual vehicle VIN code into the new TBOX. The VIN code storage unit of the vehicle TBOX saves the actual vehicle VIN code as the local configuration VIN code. At this time, the remote configuration VIN code is 0. The VIN code storage unit stores the local configuration VIN code and the remote configuration VIN code in separate partitions. The VIN code conflict detection unit detects whether the local configuration VIN code and the remote configuration VIN code are consistent. If they are inconsistent, a VIN code conflict is triggered and the VIN code conflict event is reported to the TSP platform. After receiving a VIN code conflict event, the TSP platform's conflict receiving unit enters the "actual vehicle VIN code - new TBOXS / N" into the after-sales management system and synchronizes it to the data matching unit of the TSP backend module. The replacement rule verification unit verifies the factory status of the new TBOX (confirming no historical binding records), allowing "new part to replace old part" and prohibiting "old part to replace old part". The TSP platform's data matching unit matches the "actual vehicle VIN code - new TBOXS / N" entered by after-sales with the TBOX S / N in the conflict event. After successful matching, the remote configuration unit sends a VIN code remote configuration command containing the actual vehicle VIN code to the vehicle TBOX based on the MQTT protocol. The vehicle-mounted TBOX extracts the actual vehicle VIN code from the remote configuration command of the VIN code, updates the VIN code in the command to the TSP_VIN code partition of the VIN code storage unit, and after the update is completed, the VIN code conflict detection unit compares the local configuration VIN code with the remote configuration code again. If the two are consistent, the reporting stops. After the local configuration VIN code matches the remote configuration code, the maintenance personnel use a diagnostic tool to verify the communication status between the TBOX and the TSP backend, confirming that the vehicle networking function is normal, and the process ends.

[0041] It should also be noted that the two core scenarios of "production line offline" and "after-sales parts replacement" are defined by the parts replacement rule verification unit, and the scope of "new parts for old parts" is defined to prevent VIN code confusion caused by the reuse of old parts.

[0042] This embodiment eliminates manual intervention by having the TBOX actively detect and report, and automatically match and configure in the background. The time required to assess after-sales parts replacement configuration is reduced from 2 hours to within 15 minutes. The MES system, after-sales management system and TSP platform are linked in real time to ensure rapid synchronization of vehicle VIN code and TBOX S / N, avoid TSP configuration command lag, realize closed-loop matching of data synchronization, and improve the safety and accuracy of parts replacement. The software development for TBOX and TSP association requires less modification and has a lower cost.

[0043] In this embodiment, the VIN code writing device first writes the actual vehicle VIN code based on the TBOX application scenario and sends the actual vehicle VIN code to the vehicle TBOX. Then, the vehicle TBOX uses the actual vehicle VIN code as the local configuration VIN code and checks whether the local configuration VIN code is consistent with the remote configuration VIN code through the VIN code conflict detection unit. If they are inconsistent, a VIN code conflict is triggered, and the VIN code conflict event is reported to the TSP platform. After that, the TSP platform calls the pre-stored TBOX S / N data and matches the pre-stored TBOX S / N data with the VIN code association data synchronized by the VIN code association system. If the match is successful, the VIN code remote configuration command is sent to the vehicle TBOX. Finally, the vehicle TBOX updates the remote configuration VIN code according to the VIN code remote configuration command and returns to the operation of checking whether the local configuration VIN code is consistent with the remote configuration VIN code through the VIN code conflict detection unit. This process continues until the local configuration VIN code is consistent with the remote configuration VIN code, the VIN code conflict event reporting ends, and the vehicle TBOX replacement is completed. This embodiment solves the problems of excessive manual intervention and low efficiency in existing TBOX replacement by using a dual VIN code isolation storage and access control logic of "local configuration of VIN code local writing + remote configuration of VIN code remote configuration" combined with the conflict reporting mechanism of the vehicle cloud protocol. Then, a three-party data linkage of "TBOX-TSP platform-MES" is built to realize the automatic matching of vehicle VIN code, TBOX S / N and conflict events without manual intervention, which greatly improves configuration efficiency.

[0044] Reference Figure 3 , Figure 3 This is a flowchart illustrating the first embodiment of the vehicle-mounted TBOX replacement method of the present invention.

[0045] like Figure 3 As shown, the vehicle-mounted TBOX replacement method proposed in this embodiment of the invention includes the following steps: Step S1: The VIN code writing device writes the actual vehicle VIN code based on the TBOX application scenario and sends the actual vehicle VIN code to the vehicle TBOX; Step S2: The vehicle-mounted TBOX uses the actual vehicle VIN code as the local configuration VIN code. The VIN code conflict detection unit detects whether the local configuration VIN code is consistent with the remote configuration VIN code. If they are inconsistent, a VIN code conflict is triggered, and the VIN code conflict event is reported to the TSP platform. Step S3: The TSP platform calls the pre-stored TBOX S / N data, matches the pre-stored TBOX S / N data with the VIN code association data synchronized by the VIN code association system, and after successful matching, sends the VIN code remote configuration command to the vehicle TBOX; Step S4: The vehicle-mounted TBOX updates the remote configuration VIN code according to the VIN code remote configuration command, and returns to the operation of detecting whether the local configuration VIN code and the remote configuration VIN code are consistent through the VIN code conflict detection unit, until the local configuration VIN code and the remote configuration VIN code are consistent, the VIN code conflict event reporting ends, and the vehicle-mounted TBOX replacement is completed.

[0046] Other embodiments or specific implementations of the vehicle-mounted TBOX replacement method of the present invention can be referred to the above system embodiments, and will not be repeated here.

[0047] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0048] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0049] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory / random access memory, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0050] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A vehicle-mounted TBOX replacement system, characterized in that, The system includes a VIN code writing device, an in-vehicle TBOX, a TSP platform, and a VIN code association system. The in-vehicle TBOX includes a VIN code collision detection unit. The VIN code writing device is used to write the actual vehicle VIN code based on the TBOX application scenario, and send the actual vehicle VIN code to the vehicle TBOX; The vehicle-mounted TBOX is used to use the actual vehicle VIN code as the locally configured VIN code. The VIN code conflict detection unit detects whether the locally configured VIN code is consistent with the remotely configured VIN code. If they are inconsistent, a VIN code conflict is triggered, and the VIN code conflict event is reported to the TSP platform. The TSP platform is used to call the pre-stored TBOX S / N data, match the pre-stored TBOX S / N data with the VIN code association data synchronized by the VIN code association system, and send the VIN code remote configuration command to the vehicle TBOX after successful matching. The vehicle-mounted TBOX is also used to update the remote configuration VIN code according to the VIN code remote configuration instruction, and return to the operation of detecting whether the local configuration VIN code and the remote configuration VIN code are consistent through the VIN code conflict detection unit, until the local configuration VIN code and the remote configuration VIN code are consistent, the VIN code conflict event reporting ends, and the vehicle-mounted TBOX replacement is completed.

2. The system as described in claim 1, characterized in that, The process of writing the VIN code of a real vehicle based on the TBOX application scenario includes: The VIN code writing device is connected to the vehicle's OBD interface; Based on the TBOX application scenario, the actual vehicle VIN code is written through the vehicle's OBD interface.

3. The system as described in claim 1, characterized in that, The vehicle-mounted TBOX also includes a VIN code storage unit; The VIN code storage unit is used to partition and store the local configuration VIN code and the remote configuration VIN code.

4. The system as described in claim 1, characterized in that, The vehicle-mounted TBOX also includes a data reporting unit; The process of reporting VIN code conflict events to the TSP platform includes: Based on the vehicle-cloud protocol, the VIN code conflict event is reported to the TSP platform through the data reporting unit.

5. The system as described in claim 1, characterized in that, The TSP platform includes a collision receiving unit and a data matching unit; The step of calling the pre-stored TBOX S / N data and matching the pre-stored TBOX S / N data with the VIN code association data synchronized by the VIN code association system includes: After the conflict receiving unit receives the VIN code conflict event, the data matching unit calls the pre-stored TBOX S / N data and matches the pre-stored TBOX S / N data with the VIN code association data synchronized by the VIN code association system.

6. The system as described in claim 1, characterized in that, The TSP platform also includes a remote configuration unit; Sending the VIN code remote configuration command to the vehicle-mounted TBOX includes: Based on the VIN code association data, the remote configuration unit generates a VIN code remote configuration command and sends the VIN code remote configuration command to the vehicle-mounted TBOX based on the MQTT protocol.

7. The system as described in claim 1, characterized in that, The step of updating the remote configuration VIN code according to the remote configuration instruction includes: Extract the actual vehicle VIN code from the VIN code remote configuration command; The remote configuration VIN code is updated based on the actual vehicle VIN code.

8. A method for replacing a vehicle-mounted TBOX, characterized in that, The method includes: The VIN code writing device writes the actual vehicle VIN code based on the TBOX application scenario and sends the actual vehicle VIN code to the vehicle TBOX; The vehicle-mounted TBOX uses the actual vehicle VIN code as the local configuration VIN code. The VIN code conflict detection unit detects whether the local configuration VIN code is consistent with the remote configuration VIN code. If they are inconsistent, a VIN code conflict is triggered, and the VIN code conflict event is reported to the TSP platform. The TSP platform calls the pre-stored TBOX S / N data, matches the pre-stored TBOX S / N data with the VIN code association data synchronized by the VIN code association system, and after a successful match, sends the VIN code remote configuration command to the vehicle TBOX. The vehicle-mounted TBOX updates the remote configuration VIN code according to the VIN code remote configuration command, and returns to the operation of checking whether the local configuration VIN code and the remote configuration VIN code are consistent through the VIN code conflict detection unit, until the local configuration VIN code and the remote configuration VIN code are consistent, the VIN code conflict event reporting ends, and the vehicle-mounted TBOX replacement is completed.

9. A vehicle-mounted TBOX replacement device, characterized in that, The device includes: a memory, a processor, and an in-vehicle TBOX replacement program stored in the memory and executable on the processor, the in-vehicle TBOX replacement program being configured to implement the steps of the in-vehicle TBOX replacement method as described in claim 8.

10. A storage medium, characterized in that, The storage medium stores a vehicle TBOX replacement program, which, when executed by a processor, implements the steps of the vehicle TBOX replacement method as described in claim 8.

Images