Method for realizing one-to-one automatic binding between t-box and vehicle

Abstract

The application relates to a method for realizing one-to-one automatic binding of a T-BOX and a vehicle, which comprises the following steps: writing a first vehicle identification code into a vehicle-mounted T-BOX through an offline device; issuing a second vehicle identification code to the vehicle-mounted T-BOX through remote configuration of a cloud platform; detecting whether the identification codes conflict by the T-BOX; and reporting an identification code conflict message when the first vehicle identification code and the second vehicle identification code in the T-BOX are inconsistent. The application can automatically realize one-to-one binding relationship of the T-BOX and the vehicle, can avoid confusion, can avoid forming dirty data, and can solve the problem that the binding relationship is inconsistent and prone to occur.

Description

Technical Field

[0001] This invention relates to the field of vehicle T-BOX, and more specifically, to a method for achieving one-to-one automatic binding between a T-BOX and a vehicle. Background Technology

[0002] The Internet of Vehicles (IoV) requires a T-BOX (Telematics box) to enable functions such as remote control, financial credit, and vehicle locking. These functions must ensure a unique binding relationship between the T-BOX and the vehicle; otherwise, controlling or locking the wrong vehicle will lead to user complaints and market risks.

[0003] In traditional manufacturing processes, a single binding relationship is generated solely through on-site barcode scanning, which is highly prone to causing confusion in the binding relationships. At the factory, a barcode scanner scans the VIN (Vehicle Identification Number) and T-BOX barcode, entering the data into the MES (Manufacturing Execution System). This single manual barcode scanning and binding step means that if a scanning error occurs, neither the factory nor the cloud platform can detect the binding error, and manual verification of the actual binding relationship on the vehicle is required. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a method for automatically binding T-BOX to a vehicle one-to-one, which can automatically realize the one-to-one binding relationship between T-BOX and vehicle without confusion, avoid the formation of dirty data, and solve the problem of inconsistent binding relationship.

[0005] The technical solution adopted by this invention to solve its technical problem is: constructing a method for realizing one-to-one automatic binding between T-BOX and vehicle, comprising:

[0006] The first vehicle identification code is written to the vehicle-mounted T-BOX using offline equipment;

[0007] The second vehicle identification code is sent to the vehicle-mounted T-BOX via remote configuration through the cloud platform.

[0008] The T-BOX detects whether the identification codes conflict. When the first vehicle identification code and the second vehicle identification code in the T-BOX are inconsistent, the T-BOX reports an identification code conflict message.

[0009] According to the above scheme, the offline equipment includes factory writing devices or after-sales diagnostic instruments.

[0010] According to the above scheme, the triggering conditions for T-BOX to detect code conflicts include:

[0011] (1) Power on or restart the T-BOX;

[0012] (2) The power state of the T-BOX changes from OFF to non-OFF;

[0013] (3) Remotely configure and modify the second vehicle identification code on the cloud platform;

[0014] (4) Write the first vehicle identification code into the diagnostic tool used by the after-sales service;

[0015] If any of the above conditions are met, conflict detection will be triggered.

[0016] According to the above plan, the methods for automatically binding the T-BOX to the vehicle one-to-one when the new car rolls off the production line include:

[0017] The static data of T-BOX is transferred to the cloud platform when T-BOX leaves the factory;

[0018] During factory loading, the vehicle's actual identification code is written into the T-BOX using electrical testing equipment, forming the first vehicle identification code in the T-BOX's memory; at this time, the second vehicle identification code inside the T-BOX is all 0s.

[0019] During factory loading, the vehicle's real identification code and T-BOX product serial number are scanned and entered into the manufacturing execution system using an electronic inspection barcode scanner, and then transmitted to the cloud platform via the network.

[0020] The cloud platform performs remote configuration services, remotely configuring the vehicle's real identification code to the T-BOX; the T-BOX saves the vehicle's real identification code issued by the cloud platform, forming a local second vehicle identification code;

[0021] At this point, the first vehicle identification code and the second vehicle identification code on the T-BOX are consistent; the T-BOX and the vehicle are now bound together in a one-to-one relationship.

[0022] According to the above scheme, the static data of the T-BOX includes the product serial number, mobile device identification code, mobile user identification code and SIM card number, and the static data is transferred to the cloud platform via FTP.

[0023] According to the above scheme, when a vehicle replaces its T-BOX, the new T-BOX is automatically bound to the vehicle on a one-to-one basis using the following methods:

[0024] The original T-BOX was removed from the vehicle, and the old T-BOX ceased operation.

[0025] The first and second vehicle identification codes inside the new T-BOX are all 0; after the new T-BOX is installed, the vehicle's real identification code is written through the after-sales diagnostic tool to form the first vehicle identification code of the new T-BOX; at this time, the second vehicle identification code inside the new T-BOX is still all 0.

[0026] The cloud platform initiates a remote configuration application, remotely configuring and sending the vehicle's actual identification code to the new T-BOX. The new T-BOX saves the actual vehicle identification code sent by the cloud platform, forming a local second vehicle identification code. At this time, the first vehicle identification code and the second vehicle identification code on the new T-BOX are consistent.

[0027] The new T-BOX establishes a one-to-one binding relationship with the vehicle, replacing the binding relationship of the old T-BOX.

[0028] According to the above scheme, if the conflict reporting fails during the process of T-BOX reporting the identification code conflict message to the background, no special handling is required. The detection and reporting will be triggered again the next time T-BOX is powered on, restarted, or the power switch is changed from OFF to non-OFF.

[0029] According to the above scheme, during the process of T-BOX reporting the identification code conflict message to the background, under the condition of no network, T-BOX should wait for the network connection to be successfully established in the current operation cycle before sending the identification code conflict event message; if it still fails to send the message after the sleep conditions are met, it can directly go into sleep mode.

[0030] According to the above scheme, the methods by which T-BOX reports code conflict messages to the backend include:

[0031] T-BOX reports identification code conflicts to the cloud platform. The reported content includes: first vehicle identification code, second vehicle identification code, mobile device identification code, and mobile user identification code.

[0032] The cloud platform issues a new second vehicle identification code based on the mobile device identification code and the mobile user identification code;

[0033] The cloud platform responded with the configuration result.

[0034] The present invention also provides an electronic device, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory stores a computer program, and when the program is executed by the processor, the processor performs the steps of the method for implementing one-to-one automatic binding between T-BOX and vehicle.

[0035] The method for achieving one-to-one automatic binding between T-BOX and vehicle according to the present invention has the following beneficial effects:

[0036] 1. This invention, through the VIN conflict reporting process automatically initiated by T-BOX, can work with the cloud platform to correct the binding relationship between the factory and the vehicle, making the one-to-one binding relationship between T-BOX and vehicle more reliable and greatly saving manpower and time in troubleshooting after scanning binding errors.

[0037] 2. Based on the two VIN codes stored locally on the T-BOX, this invention achieves automatic one-to-one binding between the T-BOX and the vehicle's VIN code through software logic, solving the problem of failure to promptly identify and correct binding errors during factory scanning and after-sales parts replacement. Attached Figure Description

[0038] The present invention will be further described below with reference to the accompanying drawings and embodiments. In the accompanying drawings:

[0039] Figure 1 This is a flowchart of the method for automatically binding T-BOX to a vehicle one-to-one according to the present invention;

[0040] Figure 2 This is a flowchart of the T-BOX and VIN code binding process;

[0041] Figure 3 This is a flowchart of the T-BOX and cloud platform configuration process. Detailed Implementation

[0042] To provide a clearer understanding of the technical features, objectives, and effects of the present invention, specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0043] Example 1

[0044] like Figure 1-2 As shown, the method for achieving one-to-one automatic binding between T-BOX and vehicle according to the present invention includes the following steps:

[0045] S1. Write the first vehicle identification code (Production_VIN) to the vehicle-mounted T-BOX using offline equipment. The initial value of the first vehicle identification code (Production_VIN) is all 0. It is written by the factory equipment when the vehicle rolls off the production line, or by the repair shop using a diagnostic tool in the after-sales service.

[0046] S2. The second vehicle identification code (TSP_VIN) is remotely configured and written to the vehicle-mounted T-BOX via the cloud platform. The initial value of the second vehicle identification code (TSP_VIN) is all 0s, and it can only be written remotely via the cloud platform.

[0047] S3. T-BOX detects whether the identification codes conflict. When the first vehicle identification code Production_VIN and the second vehicle identification code TSP_VIN in T-BOX are inconsistent, T-BOX reports an identification code conflict message.

[0048] Preferably, in step S3, the triggering conditions for T-BOX to detect whether the identification code conflicts include:

[0049] (1) Power on or restart the T-BOX;

[0050] (2) The power state of the T-BOX changes from OFF to non-OFF;

[0051] (3) Remotely configure and modify the second vehicle identification code TSP_VIN on the cloud platform;

[0052] (4) Write the first vehicle identification code Production_VIN using an after-sales diagnostic tool;

[0053] If any of the above conditions are met, conflict detection will be triggered.

[0054] Preferably, when a new car rolls off the production line, the T-BOX is automatically bound to the vehicle one-to-one, including the following methods:

[0055] Step 1: The static data of T-BOX is transferred to the cloud platform when T-BOX leaves the factory; the static data of T-BOX includes product serial number SN, mobile device identification code IMEI, mobile user identification code IMSI and SIM card number ICCID, and the static data is transferred to the cloud platform via FTP.

[0056] Step 2: During factory loading, the vehicle's real VIN code is written into the T-BOX using electrical testing equipment, forming the first vehicle identification code Production_VIN in the T-BOX memory; at this time, the second vehicle identification code TSP_VIN inside the T-BOX is all 0s, and the T-BOX triggers a VIN conflict.

[0057] Step 3: When loading the vehicle at the factory, the vehicle's real VIN code and T-BOX product serial number SN are scanned and entered into the Manufacturing Execution System (MES) using an electronic inspection barcode scanner, and then transmitted to the cloud platform via the network.

[0058] Step 4: When the cloud platform receives the VIN conflict message from the T-BOX, the VIN code from Step 3 and the T-BOX product serial number SN are generated in the background. The cloud platform performs remote configuration and remotely configures the vehicle's real VIN code to the T-BOX. The T-BOX saves the vehicle's real VIN code issued by the cloud platform to form a local second vehicle identification code TSP_VIN.

[0059] Step 5: At this point, the first vehicle identification code (Production_VIN) and the second vehicle identification code (TSP_VIN) on the T-BOX are consistent; the T-BOX and the vehicle have completed a one-to-one binding relationship.

[0060] Preferably, when a vehicle replaces its T-BOX, the new T-BOX is automatically bound to the vehicle on a one-to-one basis using the following methods:

[0061] Step 1: Remove the original T-BOX from the vehicle and stop the old T-BOX from working;

[0062] Step 2: The first vehicle identification code (Production_VIN) and the second vehicle identification code (TSP_VIN) inside the new T-BOX are all 0s; after the new T-BOX is installed, the vehicle's real VIN code is written through the after-sales diagnostic tool to form the first vehicle identification code (Production_VIN) of the new T-BOX; at this time, the second vehicle identification code (TSP_VIN) inside the new T-BOX is still all 0s, and the T-BOX triggers a VIN conflict.

[0063] Step 3: After receiving the VIN conflict message reported by the T-BOX, the cloud platform initiates a remote configuration application to remotely configure and send the vehicle's real VIN code to the new T-BOX. The new T-BOX saves the real VIN code sent by the cloud platform to form a local second vehicle identification code TSP_VIN. At this time, the local first vehicle identification code Production_VIN and second vehicle identification code TSP_VIN of the new T-BOX are consistent.

[0064] Step 4: The new T-BOX completes a one-to-one binding relationship with the vehicle, and the binding relationship of the old T-BOX is replaced.

[0065] Preferably, if the VIN conflict reporting fails during the process of T-BOX reporting identification code conflict messages to the background, no special handling is required. According to the procedure, the detection and reporting will be triggered again the next time T-BOX is powered on, restarted, or the power setting is changed from OFF to non-OFF.

[0066] Preferably, during the process of T-BOX reporting identification code conflict messages to the backend, under the condition of no network, T-BOX should wait for the network connection to be successfully established in the current operation cycle before sending the VIN conflict event message; if it still fails to send the message after the sleep conditions are met, it can simply go into sleep mode.

[0067] Preferred, such as Figure 3 As shown, in step S3, the method by which T-BOX reports the identification code conflict message to the backend includes:

[0068] Step 1: T-BOX reports the identification code conflict to the cloud platform. The reported content includes: the first vehicle identification code Production_VIN, the second vehicle identification code TSP_VIN, the mobile device identification code IMEI, and the mobile user identification code IMSI.

[0069] Step 2: The cloud platform issues a new second vehicle identification code (TSP_VIN) based on the mobile device identification code and the mobile user identification code;

[0070] Step 3: The cloud platform will reply with the configuration results.

[0071] Example 2

[0072] The present invention also provides an electronic device, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory stores a computer program, and when the program is executed by the processor, the processor performs the steps of the method for implementing one-to-one automatic binding between T-BOX and vehicle.

[0073] Example 3

[0074] The present invention also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to implement the method for automatically binding T-BOX to a vehicle one-to-one.

[0075] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0076] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0077] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0078] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0079] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

Claims

1. A method for achieving one-to-one automatic binding between a T-BOX and a vehicle, characterized in that, Includes the following steps: S1. Write the first vehicle identification code to the vehicle-mounted T-BOX via offline equipment; Step S1 includes: the static data of the T-BOX is transmitted to the cloud platform when the T-BOX leaves the factory; when the vehicle is loaded at the factory, the actual vehicle identification code is written to the T-BOX through an electronic inspection device, forming the first vehicle identification code in the memory of the T-BOX; at this time, the second vehicle identification code inside the T-BOX is all 0s; when the vehicle is loaded at the factory, the actual vehicle identification code and the product serial number of the T-BOX are scanned and entered into the manufacturing execution system through an electronic inspection barcode scanner, and transmitted to the cloud platform via the network; S2. Remotely configure the cloud platform to send the second vehicle identification code to the vehicle T-BOX; Step S2 includes: the cloud platform performs remote configuration services to remotely configure the actual vehicle identification code to the T-BOX; the T-BOX saves the actual vehicle identification code sent by the cloud platform to form a local second vehicle identification code. S3. T-BOX detects whether the identification codes conflict. When the first vehicle identification code and the second vehicle identification code in T-BOX are inconsistent, T-BOX reports an identification code conflict message. The triggering conditions for T-BOX to detect whether the identification codes conflict include: (1) T-BOX is powered on or restarted; (2) T-BOX's power state changes from OFF to non-OFF; (3) The second vehicle identification code is modified remotely by the cloud platform; (4) The first vehicle identification code is written by the after-sales diagnostic tool. If any of the above conditions are met, the conflict detection is triggered.

2. The method for automatically binding a T-BOX to a vehicle on a one-to-one basis according to claim 1, characterized in that, The offline devices include factory writing devices or after-sales diagnostic instruments.

3. The method for automatically binding a T-BOX to a vehicle on a one-to-one basis according to claim 1, characterized in that, The static data of the T-BOX includes the product serial number, mobile device identification code, mobile user identification code, and SIM card number, and the static data is transferred to the cloud platform via FTP.

4. The method for automatically binding a T-BOX to a vehicle on a one-to-one basis according to claim 1, characterized in that, When the T-BOX is replaced in the vehicle, steps S1 and S2 include: The original T-BOX was removed from the vehicle, and the old T-BOX ceased operation. The first and second vehicle identification codes inside the new T-BOX are all 0; after the new T-BOX is installed, the vehicle's real identification code is written through the after-sales diagnostic tool to form the first vehicle identification code of the new T-BOX; at this time, the second vehicle identification code inside the new T-BOX is still all 0. The cloud platform initiates a remote configuration application, remotely configuring and sending the vehicle's actual identification code to the new T-BOX. The new T-BOX saves the actual vehicle identification code sent by the cloud platform, forming a local second vehicle identification code. At this time, the first vehicle identification code and the second vehicle identification code on the new T-BOX are consistent.

5. The method for automatically binding a T-BOX to a vehicle on a one-to-one basis according to claim 1, characterized in that, If the conflict reporting fails during the process of T-BOX reporting identification code conflict messages to the backend, no special handling is required. The detection and reporting will be triggered again the next time T-BOX is powered on, restarted, or the power switch is changed from OFF to OFF.

6. The method for automatically binding a T-BOX to a vehicle on a one-to-one basis according to claim 1, characterized in that, During the process of T-BOX reporting identification code conflict messages to the backend, in the absence of network conditions, T-BOX should wait for a successful network connection before sending the identification code conflict event message during this operation cycle; if it still fails to send the message after the sleep conditions are met, it can simply go into sleep mode.

7. The method for automatically binding a T-BOX to a vehicle on a one-to-one basis according to claim 2, characterized in that, The methods by which T-BOX reports code conflict messages to the backend include: T-BOX reports identification code conflicts to the cloud platform. The reported content includes: first vehicle identification code, second vehicle identification code, mobile device identification code, and mobile user identification code. The cloud platform issues a new second vehicle identification code based on the mobile device identification code and the mobile user identification code; The cloud platform responded with the configuration result.

8. An electronic device, comprising: The system comprises a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; characterized in that the memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the method for implementing one-to-one automatic binding between a T-BOX and a vehicle as described in any one of claims 1 to 7.

Images