Independent Bluetooth component changing method and device

Abstract

The invention provides an independent Bluetooth component changing method, which is characterized in that on one hand, whether the information of new independent Bluetooth is wrong or not and whether the information is repeated or not is verified, on the other hand, the related information is synchronized to a supplier, the supplier can also verify the related information, and the component changing operation can be finally completed after all verification is completed. According to the method and the device, after the actual vehicle Bluetooth part is changed, the vehicle end calls the part changing process from the cloud end after the part is changed, so that relevant verification of information of a new part and an old Bluetooth part can be met, the requirement of a user on non-inductive Bluetooth relevant information replacement can be met, and the experience feeling of the user is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle information management, in particular to an independent Bluetooth replacement method and device. BACKGROUND

[0002] With the popularization of Internet of Vehicles technology, Bluetooth module as a key component of vehicle undertakes the core function of realizing user mobile phone and vehicle control interaction in a network-free environment. Currently, vehicle Bluetooth is mainly divided into two categories:

[0003] TBox (Telematics BOX, a kind of intelligent terminal equipment integrating vehicle body network and wireless communication technology, mainly used for realizing remote communication, data interaction and intelligent control function between vehicle and outside world) binding type Bluetooth: as a TBox sub-module, its life cycle is bound with TBox.

[0004] Independent Bluetooth module: as an independent hardware unit (such as cockpit Bluetooth key), deployed side by side with TBox, with independent MAC address and device number.

[0005] Independent Bluetooth module needs to be replaced separately (such as hardware failure, key update, etc.), and the reliability of its replacement process directly affects the user experience. However, the current industry generally adopted Bluetooth replacement method has the following technical bottlenecks.

[0006] (1) Lack of automatic triggering mechanism.

[0007] After replacing the hardware, manual triggering of cloud process is needed, and users need to actively contact service providers for operation, resulting in fragmented experience.

[0008] (2) Incomplete verification mechanism.

[0009] The legality of new Bluetooth MAC address (such as whether it has been bound to other vehicles) is not verified.

[0010] Old Bluetooth data is not checked whether it is synchronized to the supplier system, which may cause data conflict.

[0011] (3) Data consistency problem.

[0012] The replacement process does not use distributed lock, and multi-thread concurrent operation may cause vehicle binding relationship disorder.

[0013] The supplier end unbinding / binding operation is not synchronized with the cloud, causing "one vehicle with multiple Bluetooth" or "Bluetooth without master" state.

[0014] (4) Lack of traceability.

[0015] There is no full-link log for key operations (such as group table change, supplier interaction record), and fault positioning efficiency is low. SUMMARY

[0016] The present application aims to solve at least one of the technical problems existing in the prior art mentioned above, and proposes an independent Bluetooth replacement method and device.

[0017] In a first aspect, the present application provides an independent Bluetooth replacement method, comprising:

[0018] Receiving a replacement request parameter, checking the vehicle serial number and new Bluetooth physical address therein, and terminating the replacement process if the check fails;

[0019] Generating a unique serial number for the same replacement request;

[0020] Applying a distributed lock based on the vehicle serial number;

[0021] Querying the basic vehicle table to verify the validity of the vehicle serial number, and reporting an error and terminating the replacement process if it is invalid;

[0022] Checking in the Bluetooth reporting table whether the old Bluetooth information has been synchronized to the supplier, and reporting an error if not;

[0023] Querying the new Bluetooth information corresponding to the new Bluetooth physical address in the basic Bluetooth table, and reporting an error if it does not exist;

[0024] Querying the grouping binding relationship corresponding to the new Bluetooth device number in the basic grouping table, and reporting an error if it does not exist;

[0025] Comparing the device numbers of the new and old Bluetooth, and terminating the replacement process if they are the same; if they are different, unbinding the old Bluetooth and binding the new Bluetooth to the vehicle serial number;

[0026] Updating the replacement status to the basic data table, releasing the distributed lock, and recording the operation result to the replacement log table.

[0027] Further, comparing the device numbers of the new and old Bluetooth, if they are the same, directly returning a replacement success status and terminating the replacement process.

[0028] Further, unbinding the old Bluetooth comprises:

[0029] Notifying the supplier to unbind the vehicle from the old Bluetooth, and updating the basic grouping table after successful unbinding.

[0030] Further, binding the new Bluetooth to the vehicle serial number comprises:

[0031] Modifying the grouping number of the new Bluetooth to the grouping number corresponding to the vehicle serial number.

[0032] Further, updating the replacement status to the basic data table comprises:

[0033] According to the state code, the replacement state in the basic data table is updated, the replacement state is marked as the first flag if the replacement is successful, and the replacement state is marked as the second flag if the replacement fails.

[0034] Further, it is inquired in the basic grouping table whether the grouping binding relationship corresponding to the new Bluetooth device number exists, and if not, an error is reported, and further including:

[0035] According to the vehicle serial number, it is inquired in the basic grouping table whether the vehicle serial number and the related information of the old Bluetooth exist, and if not, the information is updated to the replacement log table.

[0036] Further, it is inquired in the basic grouping table whether the grouping binding relationship corresponding to the new Bluetooth device number exists, and if not, an error is reported, and further including:

[0037] The bound independent Bluetooth is acquired, it is inquired in the basic Bluetooth table whether the corresponding Bluetooth data exists according to the device number of the old Bluetooth, and if not, the related information is written into the replacement log table and an error is reported.

[0038] Further, further including:

[0039] The steps performed by the replacement process are recorded in the replacement log table;

[0040] The recording fields of the replacement log table include one or more of serial number, vehicle serial number, old Bluetooth physical address, new Bluetooth physical address, operation step, error code and time stamp.

[0041] Further, further including:

[0042] The replacement method is automatically triggered when the vehicle is started for the first time after completing the hardware replacement;

[0043] The triggering condition includes that the vehicle TBox detects the replacement of the independent Bluetooth, and sends a replacement request to the cloud through the Internet of Vehicles platform.

[0044] In a second aspect, the embodiments of the present application provide an electronic device, including: one or more processors;

[0045] A memory is configured to store one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors can implement the steps in the replacement method of any one of the preceding aspects.

[0046] The application provides an independent Bluetooth replacement method, which can check whether the information of the new independent Bluetooth is incorrect or repeated, and can synchronize the relevant information to the supplier, so that the supplier can also check the relevant information, and the replacement operation can be finally completed after all the checks are completed. The application occurs after the actual vehicle Bluetooth replacement, and the vehicle end calls the replacement process to the cloud after the replacement, which can meet the related check of the new and old Bluetooth information, and can meet the demand of the user for the Bluetooth information replacement without feeling, thereby improving the experience of the user. BRIEF DESCRIPTION OF DRAWINGS

[0047] Figure 1 A core flowchart of an independent Bluetooth replacement method provided by the embodiment of the application;

[0048] Figure 2 A structure block diagram of an electronic device provided by the embodiment of the application. DETAILED DESCRIPTION

[0049] In order for those skilled in the art to better understand the technical solutions of the present application, the exemplary embodiments of the present application are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to help understanding, and should be considered only as exemplary. Therefore, those skilled in the art should realize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, in order to be clear and concise, the description in the following description omits the description of well-known functions and structures.

[0050] In the case of no conflict, each embodiment of the present application and each feature in the embodiment can be combined with each other.

[0051] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0052] The terms used herein are only used to describe specific embodiments and are not intended to limit the present application. As used herein, the singular forms "a" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that when the terms "comprise" and / or "consist of" are used in the specification, the specified features, integers, steps, operations, elements, and / or components are present, but one or more other features, integers, steps, operations, elements, components, and / or groups thereof can be present or added. The terms "connected" or "connected" and the like are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect.

[0053] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure and will not be interpreted in an overly literal or overly formal sense unless expressly so defined herein.

[0054] The vehicle Bluetooth, as a component of the vehicle, mainly plays a role in the Internet of Vehicles to solve the problem that the mobile phone cannot complete the control of the vehicle in the offline state. In the offline state, the vehicle can be controlled through the connection between the mobile phone Bluetooth and the vehicle Bluetooth. There are two kinds of Bluetooth involved in the real production, one is the Bluetooth bound with the TBox, which can be regarded as an accessory on the TBox, and the other is the independent Bluetooth module, which can be regarded as a part at the same level as the TBox. The present application mainly relates to the operation of the independent Bluetooth in the cloud when the part is replaced, which occurs at the moment when the vehicle is started for the first time after the hardware replacement of the vehicle is successful.

[0055] The main problem solved by the present application is to form a set of standardized and logically complete replacement methods under the condition of meeting the needs of all parties. On the one hand, it can check whether the information of the new independent Bluetooth part is incorrect or repeated, and on the other hand, it also needs to synchronize the relevant information to the supplier, and the supplier also needs to check the relevant information. Only after all the checks are completed, the replacement operation can be finally completed.

[0056] In one embodiment, the independent Bluetooth replacement request parameters mainly involved in the whole process are shown in Table 1.

[0057] Table 1 Independent Bluetooth replacement request parameter table

[0058]

[0059] Among them, the database tables involved include replacement log table, basic vehicle table, basic Bluetooth table, basic grouping table, basic data table and Bluetooth reporting table, etc.

[0060] The replacement log table mainly records the steps of the replacement (the progress of the replacement), and the main parameters involved include the serial number, the vehicle serial number, the old Bluetooth physical address, the new Bluetooth physical address, the operation step, the error code, and the timestamp, etc. In some embodiments, the whole process operation is recorded in the replacement log table, including the serial number, the input parameter, the output parameter, the error code, and the timestamp, etc. For example, the replacement log table records: serial number = SN20241211001, input parameter = {Vin: LSVAA123456...}, output parameter = CODE_SUCCESS, and time = 2024-12-11 10:30:00. Such a setting can support full-link tracing, facilitating troubleshooting and auditing.

[0061] The basic vehicle table mainly records the relevant information of the vehicle, and the parameters related to the process mainly include the vin.

[0062] The basic Bluetooth table mainly records the information related to the Bluetooth, which includes the Bluetooth module mac address (physical address), the security chip serial number, the device number, and the Bluetooth module provider number, etc.

[0063] The basic grouping table mainly records the binding relationship between the vehicle and the part information, which mainly includes the device serial number and the grouping serial number.

[0064] The basic data table mainly records the replacement status information, which mainly includes the brand number, the replacement status, and the replacement result, etc.

[0065] The Bluetooth reporting table mainly records the data reported by the TBox, and synchronizes the data to the supplier at regular intervals.

[0066] Reference Figure 1 One embodiment of the present application proposes an independent Bluetooth replacement method based on a vehicle networking platform. The replacement method can specifically include some steps as follows.

[0067] Step 1: Automatically trigger the replacement method when the vehicle is started for the first time after completing the hardware replacement. The triggering conditions include that the vehicle TBox detects the replacement of the independent Bluetooth hardware, and sends a replacement request to the cloud through the vehicle networking platform. Such a setting can realize the automatic connection of hardware replacement to cloud processing, and can realize the completion of replacement without user awareness.

[0068] Then, the incoming replacement request parameters are verified. The incoming vin and newMac cannot be null values. If the verification fails, the replacement process is directly ended.

[0069] Step 2, create a serial number, the main function is to determine the same exchange request for the log. Because the online environment is mostly multi-threaded, when the threads are interleaved, it is very likely that the context logs before and after are the logs of two requests. This serial number is mainly to solve this problem, so that the problem can be effectively analyzed and analyzed in the later stage.

[0070] In some embodiments, the serial number is generated in the format of "SN+date+serial number", and the log entries associated with the same serial number are stored in the order of operation. More specifically, the serial number SN20241211001 is associated with 12 logs, and the complete operation sequence is displayed after sorting by timestamp. This setting can solve the problem of multi-threaded log interleaving and improve troubleshooting efficiency.

[0071] Step 3, write the incoming parameter information and Bluetooth exchange start information into the exchange log table to record the exchange start information.

[0072] Step 4, add a distributed lock at the start of the exchange to prevent other threads from invading the tasks that have not been completed by this thread, ensuring that only one thread is performing the exchange work for the same vin at the same time.

[0073] In some embodiments, in a multi-threaded environment, when the exchange request of vin = LSVAA123456 is triggered, the system locks the vin through Redis distributed lock, and other thread requests are blocked until the lock is released. This setting can avoid data conflicts caused by concurrent operations and ensure the atomicity of the exchange operation.

[0074] Step 5, query the vehicle information in the basic vehicle table according to the vin, if the basic information of the vehicle cannot be found, write the information into the exchange log table and save it, and return an error message, release the distributed lock, and end the exchange process. If it exists, continue to step 6.

[0075] Step 6, check if the old Bluetooth information is synchronized to the supplier in the Bluetooth reporting table, if the relevant information is not found, it means that the vehicle has not synchronized the information, and the error is also recorded in the exchange log table and saved, and an error message is returned. If the relevant information is found, proceed to step 7.

[0076] In some embodiments, further, query whether there is a successful synchronization record of the old Bluetooth MAC address in the Bluetooth reporting table, and the synchronization time is within 72 hours before the exchange request. Old MAC = AA:BB:CC:DD:EE:FF, the last synchronization time in the Bluetooth reporting table is 2024-12-10 14:30:00 (current request time 2024-12-11 10:00:00), then it is determined to be valid. This setting can ensure the timeliness of the old independent Bluetooth part data and prevent expired data from interfering with binding.

[0077] Step 7, according to the incoming newMac, query whether the Bluetooth information corresponding to the newMac exists in the basic Bluetooth table, if the Bluetooth information corresponding to the newMac does not exist, write the information into the replacement log table and report an error, if it exists, return Bluetooth, continue step 8.

[0078] In some embodiments, input newMac=00:1A:2B:3C:4D:5F, if there is no Bluetooth information corresponding to newMac record in the basic Bluetooth table, the system writes error information ERR_BLUETOOTH_NOT_FOUND in the replacement log table. This setting can prevent invalid Bluetooth devices from being bound and ensure hardware compatibility.

[0079] Step 8, according to the new Bluetooth device number, query whether the group binding relationship corresponding to the new Bluetooth device number exists in the basic group table, if it does not exist, update the new Bluetooth binding device information to the replacement log table and save, return error information. If it exists, continue step 9.

[0080] Step 9, then start to check the related situation of the old Bluetooth part. First, according to the incoming vin, query whether the vin and the related information of the old Bluetooth part exist in the basic group table, if the vin does not exist in the basic group table, update the information to the replacement log table, continue step 10.

[0081] Step 10, query whether the independent Bluetooth is bound in the returned device information of the same group, if it is not bound, directly proceed to step 13, if it is bound, proceed to step 11.

[0082] Step 11, get the bound independent Bluetooth, according to the device number of the old Bluetooth, query whether the corresponding Bluetooth data exists in the basic Bluetooth table, if the corresponding Bluetooth data does not exist, write the related information into the replacement log table and report an error, if it exists, proceed to step 12.

[0083] Step 12, compare the device id (device number) of the new and old Bluetooth, if the two values are the same, it means that the two Bluetooths are actually the same Bluetooth, then no additional operation is needed, directly return the replacement success and end the replacement process. If they are not consistent, write the device numbers of the new and old parts to the replacement log table, continue step 13.

[0084] In some embodiments, if the old Bluetooth device ID=BT_OLD123 is consistent with the new Bluetooth device ID=BT_OLD123, the system will skip the binding / unbinding operation and directly return the success code CODE_SUCCESS. This setting can avoid redundant operation and improve processing efficiency.

[0085] Step 13, according to the new Bluetooth mac address, query whether there is a bound vehicle information in the returned device group information, if not, directly proceed to step 14, if there is, first query whether the information corresponding to the vin exists in the basic vehicle table according to the vehicle vin, if not, write the information into the replacement part log table, report error, if there is vehicle related information, proceed to the unbinding operation of the vehicle and Bluetooth. The specific operation is: synchronize the vin to the supplier, notify it to unbind the vehicle and Bluetooth, after successful unbinding, update the basic group table. Then proceed to step 14.

[0086] In some embodiments, a disbinding request {vin:LSVAA123456, oldMac:AA:BB:CC:DD:EE:FF} is sent to the supplier system, and the supplier returns success, and the group ID in the basic group table is empty. Such setting can realize the synchronization of the supplier end data and ensure global consistency.

[0087] Step 14, then bind the vin with the new Bluetooth part, the operation in the database is to modify the group id of the new Bluetooth to the group id of the vin, so that the new Bluetooth part can be associated with the vin. If the binding fails in the process, update the failure content to the replacement part log table and return an error, if the binding succeeds, proceed to step 15.

[0088] In some embodiments, the group number of the device number DEV2024B002 in the basic group table is updated to the group number GROUP_1001 of VIN=LSVAA123456. The vehicle and Bluetooth are associated through the group number, which simplifies the data binding logic.

[0089] Step 15, according to the returned status code, judge whether the independent Bluetooth is replaced successfully, if failed, write the failure information into the replacement part log table and save, then return the error information. If the replacement is successful, update the replacement success state and return the correct code.

[0090] In some embodiments, according to the status code, update the replacement state in the basic data table, SUCCESS if successful, FAIL if failed. For example, after the replacement is successful, the replacement state field of VIN=LSVAA123456 in the basic data table is updated to SUCCESS. Such setting can provide clear state identification, which is convenient for subsequent operation and maintenance monitoring.

[0091] Step 16, release the distributed lock after the replacement process is completed, to avoid occupying too many resources. After the replacement operation is successfully completed, write the replacement success information into the replacement part log table, and return the operation completion after all processes are completed.

[0092] In some embodiments, when the vehicle VIN=LSVAA123456 is started for the first time after replacing the independent Bluetooth module, the cloud receives the following parameters: newMac=00:1A:2B:3C:4D:5E, serialNumber=AA:BB:CC:DD:EE

[0093] :FF. After the system verifies that it is not empty, it generates a serial number SN20241211001 and adds a distributed lock to the VIN through Redis. After verifying the existence of the vehicle, confirm that the old MAC has been synchronized to the supplier, and the new MAC is recorded in the basic Bluetooth table. After comparison, it is found that the new and old device IDs are different, and the supplier is notified to unbind the old Bluetooth, and the new Bluetooth group ID is updated to the group ID corresponding to the VIN, and finally the replacement status is marked as successful. An embodiment of the present application realizes fully automated triggering of the replacement process; multi-level verification prevents incorrect binding; distributed locks ensure data consistency; and supplier collaborative unbinding ensures global data synchronization.

[0094] This application provides a method for replacing independent Bluetooth components. On the one hand, this method verifies whether the information of the new independent Bluetooth is incorrect or duplicated. On the other hand, it synchronizes the relevant information to the supplier, and the supplier can also verify the relevant information. Only after all the verifications are completed can the replacement operation be finally completed. This application occurs after the actual vehicle Bluetooth component is replaced. After the component is replaced, the vehicle side calls the replacement process on the cloud, which can not only meet the relevant verification of the new and old Bluetooth component information, but also meet the user's needs for the replacement of Bluetooth related information without feeling, thereby improving the user experience.

[0095] Based on the same inventive concept, an embodiment of the present application also provides an electronic device. Figure 2 This is a structural block diagram of an electronic device provided in an embodiment of the present application. Figure 2 As shown, an electronic device provided in an embodiment of the present application includes: one or more processors 101, a memory 102, and one or more I / O interfaces 103. The memory 102 stores one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement any of the independent Bluetooth component replacement methods in the above embodiments; the one or more I / O interfaces 103 are connected between the processor and the memory and are configured to implement information exchange between the processor and the memory.

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

[0097] In some embodiments, the processor 101, the memory 102, and the I / O interface 103 are connected to each other through the bus 104, and further connected to other components of the computing device.

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

[0099] The embodiments of the present application also provide a computer readable medium. The computer readable medium stores a computer program, wherein the program is executed by a processor to implement the steps in any of the above-mentioned independent Bluetooth component replacement methods. The computer readable storage medium can be a volatile or non-volatile computer readable storage medium.

[0100] The embodiments of the present application also provide a computer program product, including computer readable code or a non-volatile computer readable storage medium carrying computer readable code, when the computer readable code is run in a processor of an electronic device, the processor in the electronic device executes the above-mentioned independent Bluetooth component replacement method.

[0101] Those skilled in the art can understand that all or some of the steps in the above-mentioned methods, the functions of the modules / units in the systems and devices can be implemented as software, firmware, hardware, and appropriate combinations thereof. In the hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component can have multiple functions, or one function or step can be performed by several physical components in cooperation. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer readable storage medium, which can include computer storage media (or non-transitory media) and communication media (or transitory media).

[0102] As those skilled in the art will appreciate, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable program instructions, data structures, program modules or other data. Computer storage media include, but are not limited to, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), static random access memory (SRAM), flash memory or other memory technology, portable compact disc read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Further, as those skilled in the art will appreciate, communication media typically embodies computer readable program instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics changed or set in a manner so as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as wireless networks, cellular telephone networks, code division multiple access (CDMA) networks, and other terrestrial and satellite radio frequency communication networks. Thus the computer readable program instructions and / or other program modules can be embodied in a computer readable storage medium, which can be any device or article that is enab!ed to store and / or carry computer readable program instructions and / or data structures. The computer readable storage medium can also be distributed over networked computer systems so that the computer readable program instructions and / or other program modules are stored and executed in a distributed fashion.

[0103] Computer readable program instructions described herein can be downloaded to respective computing / processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network can comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing / processing device.

[0104] Computer readable program instructions for carrying out operations of the present application can be assembly instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate array (FPGA), or programmable logic array (PLA) can execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present application.

[0105] The computer program product described herein can be embodied in a specific manner by hardware, software, or a combination thereof. In an optional embodiment, the computer program product is embodied as a computer storage medium. In another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK), and the like.

[0106] The various aspects of the present application are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present application. It will be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer readable program instructions.

[0107] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0108] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0109] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the system, method and computer program product according to multiple embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and the part of the module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes 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 by a special hardware-based system that performs the function or action of the specification, or can be implemented by a combination of special hardware and computer instructions.

[0110] Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for purposes of limitation. In some embodiments, it will be apparent to those skilled in the art that, unless otherwise expressly stated, features, characteristics, and / or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in conjunction with other embodiments. Therefore, it will be understood by those skilled in the art that various changes in form and detail may be made without departing from the scope of the present application as set forth in the appended claims.

Claims

1. A method for replacing an independent Bluetooth component, characterized in that: include: Receive the replacement request parameters and verify that the vehicle serial number and the new Bluetooth physical address are not empty. If the verification fails, terminate the replacement process; Generate a unique serial number for the same replacement request; Apply for a distributed lock based on the vehicle serial number; Query the basic vehicle table to verify the validity of the vehicle serial number. If it is invalid, an error will be reported and the replacement process will be terminated; Verify in the Bluetooth report whether the old Bluetooth information has been synchronized to the supplier. If not, an error will be reported. Check the basic Bluetooth table to see if the new Bluetooth information corresponding to the new Bluetooth physical address exists. If not, report an error. Check the basic group table to see if the group binding relationship corresponding to the new Bluetooth device number exists. If not, report an error. Compare the device numbers of the new and old Bluetooth devices. If they are the same, terminate the replacement process. If they are different, unbind the old Bluetooth device and bind the new Bluetooth device to the vehicle serial number. Update the replacement status to the basic data table, release the distributed lock and record the operation results to the replacement log table.

2. The component replacement method according to claim 1, wherein: Compare the device numbers of the new and old Bluetooth devices. If they are the same, the device will return to the replacement success status and terminate the replacement process.

3. The component replacement method according to claim 1, characterized in that: Unbinding the old Bluetooth includes: Notify the supplier to unbind the vehicle from the old Bluetooth and update the basic group table after the unbinding is successful.

4. The component replacement method according to claim 1, characterized in that: Binding a new Bluetooth to the vehicle serial number includes: Change the group number of the new Bluetooth to the group number corresponding to the vehicle serial number.

5. The component replacement method according to claim 1, characterized in that: Updating the replacement status to the basic data table includes: The replacement status in the basic data table is updated according to the status code. If the replacement is successful, the replacement status is marked as the first mark; if the replacement fails, the replacement status is marked as the second mark.

6. The component replacement method according to claim 1, characterized in that: Check the basic group table to see if the group binding relationship corresponding to the new Bluetooth device number exists. If not, the error message also includes: According to the vehicle serial number, the basic group table is checked to see whether there is relevant information about the vehicle serial number and the old Bluetooth. If the vehicle serial number does not exist in the basic group table, the information is updated to the replacement log table.

7. The component replacement method according to claim 1, characterized in that: Check the basic group table to see if the group binding relationship corresponding to the new Bluetooth device number exists. If not, the error message also includes: Get the bound independent Bluetooth, and query whether there is corresponding Bluetooth data in the basic Bluetooth table according to the device number of the old Bluetooth. If the corresponding Bluetooth data does not exist, write the relevant information into the replacement log table and report an error.

8. The component replacement method according to claim 1, characterized in that: Also includes: Record all steps of the replacement process in the replacement log sheet; The record fields of the replacement log table include one or more of a serial number, a vehicle serial number, an old Bluetooth physical address, a new Bluetooth physical address, an operation step, an error code, and a timestamp.

9. The component replacement method according to claim 1, characterized in that: Also includes: Automatically triggering the replacement method when the vehicle is started for the first time after completing the hardware replacement; Among them, the triggering conditions include: after the vehicle TBox detects the independent Bluetooth replacement, it sends a replacement request to the cloud through the Internet of Vehicles platform.

10. An electronic device, characterized in that: include: one or more processors; a memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors are enabled to implement the steps of the component replacement method according to any one of claims 1 to 9.

Images