Programmable tire pressure sensor

Abstract

The one or more embodiments of the specification provide a programmable tire pressure sensor, which comprises a control module and a storage module and a radio frequency module connected thereto, the radio frequency module comprises an NFC module and a vehicle communication module, and the programmable tire pressure sensor stores a pre-written basic executable code therein; wherein: the NFC module is configured to receive a service executable code sent by a mobile terminal through an NFC signal, the service executable code is generated at least according to a first identifier of the programmable tire pressure sensor; the control module is configured to call the storage module to write the service executable code into a local storage space; and in a case that the programmable tire pressure sensor is assembled to a target tire of a vehicle, the service executable code and the basic executable code are executed to perform wireless communication with the vehicle through the vehicle communication module.

Description

Technical Field

[0001] This specification relates to one or more embodiments in the field of vehicles, and more particularly to a programmable tire pressure sensor. Background Technology

[0002] TPMS (Tire Pressure Monitor System), also known as a tire pressure sensor or TPMS sensor, is a system that automatically monitors tire pressure in real time while a vehicle is in motion. It alerts the driver to tire leaks and low pressure to ensure driving safety. Currently, tire pressure sensors are typically wireless. This means that after collecting signals related to tire pressure and other parameters, the sensor encodes and modulates them into a radio frequency signal, which is then transmitted through an antenna. The vehicle's infotainment system receives this signal, decodes it, and obtains the parameter values ​​collected by the tire pressure sensor.

[0003] For the programmable tire pressure sensors commonly used at present, in order to ensure that the radio frequency signals emitted by them can be accurately received and identified by the vehicle, they need to be programmed after being installed at the front and rear of the vehicle to write unique identifiers or configuration information into them, so that the sensor and the vehicle can recognize each other and achieve normal communication.

[0004] In related technologies, dedicated activation tools are typically used to program sensors. For example, operating specialized VCI (Vehicle Communication Interface) equipment writes a unique identifier to a brand-new sensor via LF (125kHz) / RF (315 / 433MHz) signals. However, this method has several drawbacks: dedicated activation tools (such as the aforementioned VCI equipment) are not only bulky and inconvenient to carry, but also expensive; the programming process is complex and cumbersome, not only taking a long time and affecting vehicle production / maintenance efficiency, but also requiring highly skilled operators and increasing labor costs; the slow response speed of LF / RF signals not only reduces the smoothness of operation and programming efficiency, but also these signals have weak anti-interference capabilities, making them prone to disconnections and signal interference during programming (especially when there are many electronic devices in the programming area), easily leading to programming failures or even rework. Summary of the Invention

[0005] In view of the above, one or more embodiments of this specification provide the following technical solutions:

[0006] According to a first aspect of one or more embodiments of this specification, a method for writing code to a tire pressure sensor is provided, applied to a mobile terminal, the method comprising:

[0007] Obtain the business executable code of the first tire pressure sensor, the business executable code being generated at least based on the first identifier of the first tire pressure sensor, and the first tire pressure sensor storing pre-written basic executable code;

[0008] The executable code for the service is written into the first tire pressure sensor via near-field communication (NFC) signal, so that the first tire pressure sensor can wirelessly communicate with the vehicle by executing the executable code for the service and the basic executable code when it is mounted on the target tire of the vehicle.

[0009] According to a second aspect of one or more embodiments of this specification, a code execution method is provided, applied to a first tire pressure sensor, the first tire pressure sensor storing pre-written basic executable code, the method comprising:

[0010] The system receives executable code for a service sent by a mobile terminal via an NFC signal and writes it into local storage space. The executable code for the service is generated at least based on the first identifier of the first tire pressure sensor.

[0011] When the first tire pressure sensor is mounted on the target tire of the vehicle, wireless communication is performed with the vehicle by executing the business executable code and the basic executable code.

[0012] According to a third aspect of one or more embodiments of this specification, a programming system for a tire pressure sensor is provided, comprising a mobile terminal and a first tire pressure sensor to be programmed, wherein:

[0013] The mobile terminal is used to acquire the business executable code of the first tire pressure sensor, the business executable code being generated at least based on the first identifier of the first tire pressure sensor, the first tire pressure sensor storing pre-written basic executable code; and to send the business executable code to the first tire pressure sensor via an NFC signal.

[0014] The first tire pressure sensor is used to write the received business executable code into local storage space, and when the first tire pressure sensor is mounted on the target tire of the vehicle, it wirelessly communicates with the vehicle by executing the business executable code and the basic executable code.

[0015] According to a fourth aspect of one or more embodiments of this specification, a programmable tire pressure sensor is provided, comprising a control module and a connected storage module and radio frequency module, the radio frequency module including an NFC module and a vehicle-to-everything communication module, wherein the programmable tire pressure sensor stores pre-written basic executable code; wherein:

[0016] The NFC module is used to receive service executable code sent by the mobile terminal via NFC signals, and the service executable code is generated at least based on the first identifier of the programmable tire pressure sensor;

[0017] The control module is used to call the storage module to write the business executable code into the local storage space; and, when the programmable tire pressure sensor is mounted on the target tire of the vehicle, to execute the business executable code and the basic executable code to wirelessly communicate with the vehicle through the vehicle communication module.

[0018] According to a fifth aspect of one or more embodiments of this specification, a tire pressure sensor code writing device is provided for a mobile terminal, the device comprising:

[0019] The code acquisition unit is configured to acquire the business executable code of the first tire pressure sensor, the business executable code being generated at least based on the first identifier of the first tire pressure sensor, and the first tire pressure sensor storing pre-written basic executable code.

[0020] The code writing unit is configured to write the business executable code into the first tire pressure sensor via near field communication (NFC) signals, so that the first tire pressure sensor can wirelessly communicate with the vehicle by executing the business executable code and the basic executable code when it is mounted on the target tire of the vehicle.

[0021] According to a sixth aspect of one or more embodiments of this specification, a code execution device is provided for use with a first tire pressure sensor, the first tire pressure sensor storing pre-written basic executable code, the device comprising:

[0022] The code writing unit is configured to receive executable business code sent by the mobile terminal via NFC signal and write it into local storage space, wherein the executable business code is generated at least based on the first identifier of the first tire pressure sensor;

[0023] The code execution unit is configured to wirelessly communicate with the vehicle by executing the business executable code and the basic executable code when the first tire pressure sensor is mounted on the target tire of the vehicle.

[0024] According to a seventh aspect of one or more embodiments of this specification, a mobile terminal is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor performs the steps of the method as described in the first aspect by executing the executable instructions.

[0025] According to an eighth aspect of one or more embodiments of this specification, a tire pressure sensor is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor performs the steps of the method as described in the second aspect by executing the executable instructions.

[0026] According to a ninth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the steps of the method as described in the first or second aspect.

[0027] According to a tenth aspect of one or more embodiments of this specification, a computer program product is provided, comprising a computer program / instructions that, when executed by a processor, implement the steps of the method as described in the first or second aspect.

[0028] Through the foregoing embodiments, the programming system proposed in this specification comprises a mobile terminal (such as a mobile phone, tablet computer, etc.) and a first tire pressure sensor to be programmed. When implementing the programming scheme described in this specification, the mobile terminal obtains the business executable code of the first tire pressure sensor, which is generated at least based on a first identifier of the first tire pressure sensor. The first tire pressure sensor stores pre-written basic executable code. The mobile terminal also sends the business executable code to the first tire pressure sensor via an NFC signal. The first tire pressure sensor writes the received business executable code into its local storage space, and when the first tire pressure sensor is mounted on a target tire of the vehicle, it wirelessly communicates with the vehicle by executing the business executable code and the basic executable code.

[0029] Compared with the aforementioned solutions in related technologies, this solution has the following advantages:

[0030] On the one hand, this solution does not require expensive and cumbersome dedicated activation tools. Programming can be achieved simply by the cooperation of the mobile terminal and the tire pressure sensor in the programming system (that is, writing the business executable code generated according to the first identifier into the sensor). Users only need to run the corresponding client on their mobile terminals such as mobile phones and tablets to operate the client to program the tire pressure sensor. This not only significantly reduces hardware costs but also reduces the difficulty of operation for users, which helps to improve programming efficiency and success rate.

[0031] On the other hand, the mobile terminal and the first tire pressure sensor in this solution achieve wireless data transmission through NFC technology. No complex connection process such as pre-pairing or handshake is required before interaction (the mobile terminal only needs to be near the first tire pressure sensor to interact), making operation convenient and efficient. Furthermore, NFC technology's short-range communication and encrypted transmission, along with its rapid response characteristics, make the programming process more efficient, helping to reduce maintenance time and avoid long customer wait times. In addition, NFC technology effectively enhances the anti-interference capability of the data interaction process, helping to ensure signal stability, improving the accuracy of data and command transmission during interaction, and significantly reducing abnormal situations such as programming failures or even rework. Attached Figure Description

[0032] Figure 1 This is a schematic diagram of the architecture of a programming system provided in an exemplary embodiment.

[0033] Figure 2 This is a schematic diagram of the architecture of another programming system provided in an exemplary embodiment.

[0034] Figure 3 This is an interactive flowchart of a programming method provided in an exemplary embodiment.

[0035] Figure 4 This is a flowchart of a method for writing code to a tire pressure sensor, provided in an exemplary embodiment.

[0036] Figure 5 This is a flowchart of a code execution method provided in an exemplary embodiment.

[0037] Figure 6 This is a schematic diagram of the structure of a device provided in an exemplary embodiment.

[0038] Figure 7 This is a block diagram of a code writing device for a tire pressure sensor provided in an exemplary embodiment.

[0039] Figure 8 This is a block diagram of a code execution apparatus provided in an exemplary embodiment. Detailed Implementation

[0040] To address the aforementioned technical problems in related technologies, this specification proposes a programming scheme for a tire pressure sensor. The scheme allows a mobile terminal to wirelessly interact with the first tire pressure sensor via NFC signals, writing executable code generated based on its first identifier into the sensor, thereby realizing the programming process. The scheme is described below with reference to the accompanying drawings and related embodiments.

[0041] Figure 1 This is a schematic diagram of the architecture of a programming system provided in an exemplary embodiment. For example... Figure 1 As shown, the programming system 10 includes a mobile phone 11 and a sensor 12. Mobile phone 11 is the mobile terminal described in this solution, and mobile phone 12 is the first tire pressure sensor described in this solution. Mobile phone 11 and sensor 12 can wirelessly connect via NFC (Near Field Communication) signals. Either mobile phone 11 or sensor 12 can also wirelessly connect to vehicle 13 via Bluetooth or Wi-Fi (Wireless Fidelity) signals. Vehicle 13 is the vehicle equipped with sensor 12; in other words, mobile phone 12 needs to be mounted on the target tire of vehicle 13. After installation and programming, sensor 12 can run locally written executable code to wirelessly upload the pressure data of the target tire it detects to the vehicle via Bluetooth or Wi-Fi.

[0042] In this specification, a mobile phone is just one type of electronic device that a user can use. In reality, users can use any electronic device with NFC and other wireless connectivity capabilities, including but not limited to tablets, laptops, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smartwatches, etc.), VR (Virtual Reality) devices, AR (Augmented Reality) devices, etc. One or more embodiments in this specification do not limit this. The mobile phone 11 runs a client program with a programming client. For example, this client program can be an APP (Application), a browser-based web application (or web page), or a mini-program based on other applications. The APP typically needs to be pre-installed and launched; while the web application and mini-program can be online "clients" built using HTML5 technology. These client programs usually do not require a specific "installation" step but are integrated into a browser or other applications and run as independent pages or functional components (or plugins). The programming client can provide users with a human-computer interaction interface (HCI Interface), in which users can perform corresponding interactive operations (such as selecting / inputting information, clicking triggerable controls, etc.) to achieve the programming scheme described below.

[0043] In addition to interacting with sensor 12 and vehicle 13, mobile phone 11 can also remotely access server 14 wirelessly to obtain necessary information such as the first identifier (see the embodiments below for details). As a unified sensor management and programming service platform, server 14 can simultaneously connect to multiple mobile terminals, such as mobile phones 15 and 16, to assist each mobile terminal in programming its corresponding tire pressure sensor. Server 14 can connect to a network via wired and / or wireless means to establish connections with the various mobile terminals it connects to, which will not be elaborated further. Of course, the mobile terminal described in the embodiments of this specification can be any mobile terminal connected to server 14, and the first tire pressure sensor described in the embodiments of this specification can be any tire pressure sensor that needs to be programmed by that mobile terminal, which will not be elaborated further.

[0044] The server 14 can be a physical server containing an independent host, or the server 16 can be a virtual server, cloud server, etc. hosted by a host cluster; this specification does not limit this. A server-side program running on the server 14 is used to interact with the programming client to complete corresponding functions (see the embodiments below for details). For example, from a software perspective, the programming client can interact and collaborate with the programming server to jointly complete the programming process of the first tire pressure sensor; in this case, the programming client needs to run online (or network-connected); or, the programming client can also complete the programming process of the first tire pressure sensor independently through local logic without interacting with the programming server; in this case, the programming client can run offline (or independently). Of course, the specific operating mode of the programming client depends on its client form. For example, if the client is an APP, it can run online or offline; while if the client is an H5 page, it often needs to run online, therefore, the programming server needs to complete the corresponding processing logic, etc., which will not be elaborated further.

[0045] It should be noted that the first tire pressure sensor described in this embodiment is a programmable sensor, meaning that its hardware and software support programming (i.e., data writing) by external devices. Furthermore, the sensor's hardware and software also support NFC communication, enabling data interaction with the mobile terminal through NFC signal transmission and reception to complete programming. Additionally, this embodiment does not limit the brand, size, installation location, installation method, or specific communication method of the sensor 12. Similarly, this embodiment does not limit the brand, model, number of tires, or specific communication method of the vehicle 13, and the target tire for mounting the sensor 12 can be any tire of the vehicle 13, which will not be elaborated further.

[0046] This application also proposes a programmable tire pressure sensor as the first tire pressure sensor in the programmable system. The programmable tire pressure sensor includes a control module and a connected storage module and radio frequency module. The radio frequency module includes an NFC module and a vehicle-to-grid communication module. The programmable tire pressure sensor stores pre-written basic executable code; wherein:

[0047] The NFC module is used to receive service executable code sent by the mobile terminal via NFC signals, and the service executable code is generated at least based on the first identifier of the programmable tire pressure sensor;

[0048] The control module is used to call the storage module to write the business executable code into the local storage space; and, when the programmable tire pressure sensor is mounted on the target tire of the vehicle, to execute the business executable code and the basic executable code to wirelessly communicate with the vehicle through the vehicle communication module.

[0049] In one embodiment, the vehicle-to-vehicle communication module may include at least one of the following: a Sub-1G module, a Bluetooth module, a Wi-Fi module, or a Zigbee module. Of course, it may also include other radio frequency modules besides those mentioned above to meet the diverse communication needs between the programmable tire pressure sensor and the vehicle.

[0050] In one embodiment, the control module is further configured to: verify the executable code of the service, wherein passing the code verification is a prerequisite for writing to the local storage space; or,

[0051] The NFC module is further configured to: receive a code writing instruction corresponding to the executable code of the service sent by the mobile terminal via an NFC signal; the control module is further configured to: verify the code writing instruction, wherein successful verification of the instruction is taken as a prerequisite for writing the executable code of the service into the local storage space.

[0052] In one embodiment, when the storage module writes the executable code of the service to the local storage space, it is specifically used for:

[0053] Write the executable code for the aforementioned service to local free storage space; or,

[0054] If historical business executable code exists in local storage, the business executable code is written to the storage space where the historical business executable code is located, thereby overwriting the historical business executable code.

[0055] In one embodiment, the programmable tire pressure sensor further includes a sensing module connected to the control module, used to collect pressure data of at least the target tire and send it to the control module; the control module is also used to send the pressure data to the vehicle via the wireless communication.

[0056] The executable code in the foregoing embodiments is generated based on the first identifier and configuration information of the first tire pressure sensor.

[0057] The specific functions of each module in the above embodiments can be found in the description of the embodiments below, and will not be repeated here.

[0058] Figure 2 This is a schematic diagram of the architecture of another programming system provided in an exemplary embodiment. For example... Figure 2 As shown, the programming system includes a mobile terminal and a first tire pressure sensor.

[0059] The mobile terminal is equipped with a programming app and an NFC module. The NFC module includes an antenna, an antenna matching network, and a signal processing circuit. The antenna receives NFC signals, the antenna matching network adjusts the impedance difference between the antenna and the transmission line, and the signal processing circuit demodulates (or decodes) the Bluetooth signal and sends the processing result to the running programming app for further processing (of course, the data interaction between the NFC module and the programming app may involve the mobile terminal's operating system, which will not be elaborated further).

[0060] The first tire pressure sensor houses a control module and its connected storage module and radio frequency (RF) module. The RF module includes an NFC module (which can be considered a communication module for mobile terminals) and a vehicle-to-everything (V2X) communication module (such as a Wi-Fi module, Sub-1G module, and / or Zigbee module). The structure and operation of the NFC module in this sensor are similar to those in a mobile terminal, and will not be described further. The signal processing circuit of the NFC module can send received data to the control module for processing, such as sending received executable code to the control module, which then calls the storage module to write the executable code into its local storage space.

[0061] It should be noted that both the NFC module in the mobile terminal and the NFC module in the first tire pressure sensor are signal transceiver modules. In other words, either of these NFC modules can both receive and send NFC signals. This is hereby clarified. Additionally, Figure 2 Each communication module shown has its own antenna. This is only to illustrate the difference between the modules. In reality, multiple communication modules can share a single antenna. This specification does not limit this in the embodiments.

[0062] In addition, the mobile terminal and the vehicle may also be equipped with Bluetooth modules, Wi-Fi modules, Sub-1G modules and / or Zigbee modules to communicate via the corresponding type of wireless signal or to communicate with the first tire pressure sensor, which will not be elaborated further.

[0063] In addition, the power supply module is used to supply power to other modules (besides the power supply module itself). For example, the power supply module is connected to the control module, so it can directly power the control module. As another example, since the control module is connected to various communication modules, the power supply module can also indirectly power the communication modules through the control module; of course, the power supply module can also power each communication module independently. Figure 2 (not shown), this manual does not impose any restrictions on the specific power supply method.

[0064] The power module includes a battery, which can be a disposable battery (such as a button cell battery); or it can be a rechargeable battery that can be charged and discharged multiple times to improve the sensor's battery life and reduce maintenance difficulty. Furthermore, if the battery is a disposable battery, it can be arranged in a removable manner for easy replacement by the user; while if the battery is a rechargeable battery, it can be arranged either in a removable manner for maintenance or in a non-removable manner to improve the sensor's compactness, thereby contributing to miniaturization.

[0065] This concludes the introduction to the tire pressure sensor programming system. This manual also proposes a programming scheme implemented by this system, which requires collaboration between a mobile terminal and the first tire pressure sensor to be programmed, wherein:

[0066] The mobile terminal is used to acquire the business executable code of the first tire pressure sensor, the business executable code being generated at least based on the first identifier of the first tire pressure sensor, the first tire pressure sensor storing pre-written basic executable code; and to send the business executable code to the first tire pressure sensor via an NFC signal.

[0067] The first tire pressure sensor is used to write the received business executable code into local storage space, and when the first tire pressure sensor is mounted on the target tire of the vehicle, it wirelessly communicates with the vehicle by executing the business executable code and the basic executable code.

[0068] In one embodiment, the programming scheme can be applied to a new car production line. For example, before installing tires on the assembly line, workers can program a brand-new tire pressure sensor using this scheme, then assemble it onto the tire, and finally mount the tire onto the chassis to form the vehicle; alternatively, after the tire is mounted on the vehicle, the brand-new tire pressure sensor can be assembled onto the tire, and then this scheme can be used to program the sensor. In this new car production scenario, the brand-new tire pressure sensor is the first tire pressure sensor to be programmed, and the worker is the user of the mobile terminal.

[0069] In another embodiment, the programming scheme can also be applied to the maintenance of vehicles that have already left the factory. For example, if an old tire pressure sensor installed on a tire of a vehicle malfunctions, the repair personnel can remove the sensor and install another tire pressure sensor on the tire. Before or after installation, the other sensor can be programmed using this scheme. In this vehicle maintenance scenario, the other sensor is the first tire pressure sensor to be programmed, and the repair personnel is the user of the mobile terminal. The repair personnel can be professional repair personnel from a vehicle repair shop; or, because this scheme has low hardware requirements and is simple to operate, it can also be used for the vehicle owner (e.g., the owner purchases a new tire pressure sensor to replace the old one and completes the repair). Furthermore, the other sensor can be a brand-new tire pressure sensor (i.e., manufactured but not yet installed on the tire) or an old tire pressure sensor removed from another tire (this type of sensor, although used, is functional and can still be used). This specification does not limit this.

[0070] It's worth noting that, regardless of whether it's a new car production scenario or a vehicle repair scenario, users can flexibly determine the timing of programming during the implementation of this solution, that is, flexibly determine the order of programming and installing the first tire pressure sensor. For example, the programmed sensor can be installed on the target tire, or the sensor already installed on the target tire can be programmed. Because the mobile terminal in this solution interacts with the first tire pressure sensor via NFC signals to achieve programming, it is only necessary to ensure that the distance between the two is no greater than the coverage range of the NFC signal (generally about 10cm) to ensure that both parties can successfully send and receive NFC signals to achieve programming. The order of programming and installing the first tire pressure sensor, as well as their orientation, angle, and distance, can be flexibly set, and this solution does not impose specific restrictions on them.

[0071] The first tire pressure sensor described in this embodiment has pre-written basic executable code stored before programming. This code is used to implement some basic functions. For example, the basic executable code may include hardware initialization code (initializing hardware and software interfaces, initializing system clock and peripheral clock, configuring power management functions, etc.), sensor calibration code (used to calibrate the reference output of the sensing device in the sensor to ensure the accuracy of sensor data, such as zero-point calibration, temperature compensation, etc.), basic data processing code (such as code corresponding to algorithm logic such as noise reduction algorithm and filtering algorithm, etc.), communication protocol code (such as NFC, Bluetooth, Wi-Fi protocol stack code, etc., used to implement basic data sending and receiving functions), error detection and handling code (such as hardware error detection, data verification, etc.), update support code (such as bootloader, firmware verification code, etc.), basic configuration management code (such as configuration storage and reading logic code, etc.), low power management code (such as sleep mode, wake-up mechanism code), security function code (such as encryption and authentication, secure boot code, etc.), etc.

[0072] The programming process described in this specification is the process of writing executable code into the sensor. The written executable code is generated at least based on the first identifier of the first tire pressure sensor. Since the first tire pressure sensor can run the executable code and basic executable code to wirelessly communicate with the vehicle after the executable code is written, the executable code can also be considered as the communication protocol code corresponding to the wireless communication code. The first identifier used to generate the executable code uniquely identifies the first tire pressure sensor. Because each tire typically has only one tire pressure sensor, meaning there is a one-to-one correspondence between tire pressure sensors and tires, when sending data messages to the vehicle after programming, the first identifier can be used to indicate which tire pressure sensor on which tire of the vehicle sent the data message, so that the vehicle can determine which tire's current tire pressure the pressure data in the data message represents.

[0073] In one embodiment, the mobile terminal can obtain the executable code for the first tire pressure sensor in various ways. For example, it can first obtain a first identifier, and then generate the executable code based at least on the first identifier (i.e., the mobile terminal obtains the identifier and generates the code itself); or, it can send a code generation request containing the first identifier to the server and receive the executable code returned by the server after generating the code based on the first identifier (i.e., the mobile terminal obtains the identifier and calls the server to generate the code). As another example, the mobile terminal can also directly send a code acquisition request for the first tire pressure sensor to the server, and then receive the executable code generated and returned by the server based at least on the first identifier it obtained (i.e., the mobile terminal calls the server to obtain the identifier and generate the code). It is understood that the entity generating the executable code based on the first identifier (i.e., the mobile terminal or the server) needs to pre-deploy corresponding code generation logic. For example, it can pre-save basic code locally, then fill the first identifier into the basic code, and compile the completed code to generate the executable code. It is understandable that the aforementioned code generation logic may be quite complex, and therefore generating executable business code may require a lot of resources. When implementing the solution, an appropriate method can be flexibly selected to obtain executable business code based on the actual situation such as the local computing power of the mobile terminal and the programming level of the user.

[0074] In one embodiment, the mobile terminal can acquire the first identifier in various ways. For example, it can read the identifier of the second tire pressure sensor from the second tire pressure sensor or the vehicle and use it as the first identifier of the first tire pressure sensor, wherein the first tire pressure sensor is installed on the target tire after the second tire pressure sensor is removed from the target tire. It is understood that the second tire pressure sensor is an old sensor removed from the target tire, while the first tire pressure sensor is a new sensor that needs to replace the old one. The mobile terminal can read the identifier of the second sensor from the vehicle via NFC, or wirelessly via Bluetooth or Wi-Fi. This solution, by reading the identifier from the second tire pressure sensor or the vehicle as the first identifier, ensures that the new sensor and the old sensor use the same identifier. Therefore, there is no need to adjust / modify the relevant configuration on the vehicle side; only programming the new sensor is required to ensure that the programmed new sensor can communicate smoothly with the vehicle. In addition, to ensure the smooth operation of the new sensor, the new sensor and the old sensor can be the same model; or, to update the function of the old sensor, the new sensor can be an upgraded version of the old sensor (such as with modified configuration or added new functions). The embodiments in this specification do not limit this.

[0075] For example, based on the aforementioned human-computer interaction interface provided by the client, the user can also directly specify the first identifier to the mobile terminal. In this case, the mobile terminal can respond to the detected identifier input operation (performed by the user) and use the input identifier as the first identifier of the first tire pressure sensor. The user can obtain the first identifier by viewing vehicle configuration information through the vehicle's infotainment system (e.g., through the vehicle's central control screen), or by determining the first identifier based on the position of the target tire (e.g., left front tire identifier is 1, right front tire identifier is 2, left rear tire identifier is 3, right rear tire identifier is 4, etc.), or by viewing the outer packaging of the first tire pressure sensor (e.g., the first identifier is assigned during the production stage and printed on the packaging box of the first tire pressure sensor). The user can then manually input the obtained first identifier through the identifier input operation so that the mobile terminal (i.e., the client) can obtain it.

[0076] For example, the identifiers of each tire pressure sensor can be pre-maintained by the server. Based on this, the mobile terminal can initiate a request to the server to obtain the identifier of the first tire pressure sensor and receive the first identifier of the first tire pressure sensor returned in response to the request. The first identifier can be allocated during the tire pressure sensor's production stage and pre-uploaded to the server by the sensor's manufacturer, agent, distributor, or user (e.g., if a user pre-purchases a large number of sensors, the identifiers of these sensors can be uploaded to the server in batches before use). Alternatively, the first tire pressure sensor can be uploaded to the server by the corresponding device during the programming of the aforementioned old sensors or by the vehicle during use. The user can then initiate the identifier acquisition request through the client's human-machine interface, such as scanning the QR code or barcode on the outer packaging of the first tire pressure sensor, or scanning the identifier or QR code of the target tire displayed on the vehicle's infotainment system.

[0077] For example, this solution is also compatible with programming schemes in related technologies. For instance, the mobile terminal can receive the identifier of the aforementioned second tire pressure sensor sent by the handheld device and use it as the first identifier of the first tire pressure sensor. This identifier is read by the handheld device from the second tire pressure sensor or the vehicle. The handheld device can be a dedicated activation tool such as a VCI device, which can read the identifier from the second tire pressure sensor via LF / RF signals or from the vehicle via a dedicated connection cable through the OBD interface. The handheld device can send the identifier to the mobile terminal via any wired (e.g., USB or Type-C interface) or wireless (Bluetooth, Wi-Fi, or NFC) method. In this way, this solution is fully compatible with identifier acquisition methods in related technologies, thereby reducing the difficulty of implementing this solution and expanding its application scope.

[0078] The foregoing embodiments only use the first identifier as an example for illustration. In reality, the code generator (such as the aforementioned mobile terminal or server) can also generate the executable code based on the first identifier and configuration information of the first tire pressure sensor. For example, the mobile terminal can also obtain configuration information from the server or receive configuration information manually entered by the user, and then generate executable code based on the first identifier and configuration information; or it can send a code generation request containing the first identifier and configuration information to the server and obtain the executable code generated and returned by the server in response to the request based on the first identifier and configuration information, which will not be elaborated further. In this way, parameter configuration functions can be integrated into the programming process for the first tire pressure sensor, thereby completing parameter configuration while writing code, further simplifying the user's production or maintenance process.

[0079] The executable code described in this specification is binary code that can be executed in the first tire pressure sensor. Specifically, it can be a code file in formats such as .gbl, .srec, .s19, .s37, .bin, .hex, .axf, or .elf. It is understood that this binary code can be directly executed by the hardware of the second tire pressure sensor without intermediate steps such as compilation, thus its execution efficiency is very high. However, the successful execution of the aforementioned binary code depends on the specific operating environment of the second tire pressure sensor. Therefore, the code generator can obtain the hardware and software environment description information of the second tire pressure sensor in advance and generate the executable code based on this information to ensure that the code, after being written into the second tire pressure sensor, can adapt to the sensor's hardware and software environment and thus run smoothly, avoiding operational errors.

[0080] As can be seen from the foregoing embodiments, the first identifier may be a newly assigned identifier, or it may be an identifier that has been used by an old sensor. Therefore, the vehicle itself may or may not have stored the first identifier. In this case, if the vehicle is not yet aware of the first identifier (e.g., the first identifier is assigned during the production stage of the first tire pressure sensor and uploaded to the server by the manufacturer for storage, or it is programmed and entered by the user), the mobile terminal can also write the first identifier into the vehicle via Bluetooth or Wi-Fi signals to ensure that the programmed first tire pressure sensor can communicate wirelessly with the vehicle normally.

[0081] After receiving the executable code sent by the mobile terminal, the first tire pressure sensor can write the code into its local storage space for later reading and execution.

[0082] In one embodiment, the first tire pressure sensor can verify the received executable code and write it to local storage if the verification is successful, thereby ensuring the correctness of the written code. Alternatively, the first tire pressure sensor can also receive executable code and its corresponding code writing instruction sent by the mobile terminal, and write the executable code to local storage if the code writing instruction is verified. The mobile terminal can send the code writing instruction after determining that the executable code has been sent (e.g., all data of the executable code has been sent) or after determining that the first tire pressure sensor has received the code (e.g., receiving a successful reception notification message from the sensor); or it can directly send a code writing instruction containing the executable code, thereby integrating the code sending and writing instructions into a single instruction, further simplifying the interaction logic between the two parties. The verification performed on the executable code or the code writing instruction may include, but is not limited to, data size verification, version verification, hash verification, signature verification, checksum verification, cyclic redundancy verification, parity verification, XOR verification, etc., which will not be elaborated further.

[0083] In one embodiment, the first tire pressure sensor can write the executable code to local free storage space to avoid interfering with already written executable code. Alternatively, as mentioned above, the first tire pressure sensor may be a previously used sensor, in which case it may already have historical executable code stored locally. Therefore, the executable code can be written to the storage space where the historical executable code is located to overwrite the historical executable code. That is, by overwriting, the old code is cleared while the new code is written, saving local storage space and avoiding any adverse effects that the old code may have on the operation of the new code. In addition, the aforementioned verification and writing process can be completed by the bootloader of the first tire pressure sensor.

[0084] In one embodiment, the process of the mobile terminal sending executable code to the first tire pressure sensor and the first tire pressure sensor writing the code takes a certain amount of time, especially when the executable code has a large amount of data (such as a lot of configuration information to generate the code) or the signal is unstable. In such cases, the user may need to wait for a period of time to complete the programming. To address this, and to help the user monitor the programming progress and improve their understanding of the process, the mobile terminal can obtain programming progress information from the first tire pressure sensor via NFC signals, such as the writing status information of the executable code, and display this information to the user.

[0085] In one embodiment, the mobile terminal can also instruct the first tire pressure sensor to update its operating status after the executable code is written; correspondingly, the sensor can update its operating status after the executable code is written. In this way, the first tire pressure sensor can update its operating status in a timely manner so that a wireless connection can be established with the vehicle promptly after programming, thereby activating the sensor.

[0086] After the executable code is written, the first tire pressure sensor can wirelessly communicate with the vehicle by executing the executable code and the basic executable code, provided that the first tire pressure sensor is mounted on the target tire of the vehicle. It should be noted that, in practice, the first tire pressure sensor can wirelessly communicate with the vehicle as long as it is activated after programming and establishes a wireless connection with the vehicle; whether the first tire pressure sensor is mounted on the target tire or not does not affect their communication. However, the sensor can only detect the internal air pressure (tire pressure) of the tire, i.e., it can only acquire the tire pressure data, when the first tire pressure sensor is mounted on the target tire.

[0087] In one embodiment, the first tire pressure sensor can execute the business executable code and the basic executable code to collect at least the pressure data of the target tire according to the acquisition logic recorded in the code, and transmit the pressure data to the vehicle via wireless communication. Of course, the first tire pressure sensor can also collect data corresponding to other physical indicators of the target tire; the specific data collected is determined by the sensing devices integrated into the sensor itself. For example, temperature data, humidity data, and eccentricity data (used to characterize the degree to which the target tire deviates from its geometric center during rotation) can also be collected, but this embodiment does not limit the scope of the invention.

[0088] Through the foregoing embodiments, the programming system proposed in this specification comprises a mobile terminal (such as a mobile phone, tablet computer, etc.) and a first tire pressure sensor to be programmed. When implementing the programming scheme described in this specification, the mobile terminal obtains the business executable code of the first tire pressure sensor, which is generated at least based on a first identifier of the first tire pressure sensor. The first tire pressure sensor stores pre-written basic executable code. The mobile terminal also sends the business executable code to the first tire pressure sensor via an NFC signal. The first tire pressure sensor writes the received business executable code into its local storage space, and when the first tire pressure sensor is mounted on a target tire of the vehicle, it wirelessly communicates with the vehicle by executing the business executable code and the basic executable code.

[0089] Compared with the aforementioned solutions in related technologies, this solution has the following advantages:

[0090] On the one hand, this solution does not require expensive and cumbersome dedicated activation tools. Programming can be achieved simply by the cooperation of the mobile terminal and the tire pressure sensor in the programming system (that is, writing the business executable code generated according to the first identifier into the sensor). Users only need to run the corresponding client on their mobile terminals such as mobile phones and tablets to operate the client to program the tire pressure sensor. This not only significantly reduces hardware costs but also reduces the difficulty of operation for users, which helps to improve programming efficiency and success rate.

[0091] On the other hand, the mobile terminal and the first tire pressure sensor in this solution achieve wireless data transmission through NFC technology. No complex connection process such as pre-pairing or handshake is required before interaction (the mobile terminal only needs to be near the first tire pressure sensor to interact), making operation convenient and efficient. Furthermore, NFC technology's short-range communication and encrypted transmission, along with its rapid response characteristics, make the programming process more efficient, helping to reduce maintenance time and avoid long customer wait times. In addition, NFC technology effectively enhances the anti-interference capability of the data interaction process, helping to ensure signal stability, improving the accuracy of data and command transmission during interaction, and significantly reducing abnormal situations such as programming failures or even rework.

[0092] Figure 3 This is an interactive flowchart of a programming method provided in an exemplary embodiment. For example... Figure 3 As shown, the method involves a mobile phone 31 (i.e., a mobile terminal), a sensor 32 (i.e., a first tire pressure sensor), and a vehicle 33 (the sensor 32 is installed on the target tire of the vehicle 33). The method includes the following steps 301-308.

[0093] Step 301: Mobile phone 31 obtains at least the business executable code generated based on the first identifier of sensor 32.

[0094] In one embodiment, mobile phone 31 can obtain service executable code through at least one of the following methods: obtaining the first identifier, and generating the service executable code based at least on the first identifier. Obtaining the first identifier and sending it to the server ( Figure 3 (Not shown) Initiates a code generation request containing the first identifier, and receives the executable code for the service generated by the server based on the first identifier. Initiates a code acquisition request for the sensor 32 to the server, and receives the executable code for the service generated and returned by the server based at least on the first identifier acquired by itself.

[0095] The mobile phone 31 can obtain the first identifier of the sensor 32 through at least one of the following methods: from the second tire pressure sensor ( Figure 3The identifier of the second tire pressure sensor (not shown) is read from the vehicle 33 or the vehicle 33 and used as the first identifier of the sensor 32, wherein the sensor 32 is mounted on the target tire after the second tire pressure sensor is removed from the target tire. The identifier of the second tire pressure sensor sent by the handheld device is received and used as the first identifier of the sensor 32, which is read by the handheld device from the second tire pressure sensor or the vehicle 33. A request to obtain the identifier of the sensor 32 is initiated to the server, and the first identifier of the sensor 32 is received from the server in response to the request. In response to a detected identifier input operation, the identifier entered by the user is used as the first identifier of the sensor 32.

[0096] In one embodiment, the executable code may also be generated based on the first identifier and configuration information of the sensor 32.

[0097] Step 302: The mobile phone 31 sends a code writing instruction for the business executable code to the sensor 32.

[0098] Step 303: Sensor 32 writes the received business executable code into local storage space.

[0099] In one embodiment, when writing executable code, sensor 32 may receive executable code sent by a mobile terminal and write the executable code into local storage space if the executable code is verified; or, it may receive executable code and its corresponding code writing instruction sent by a mobile terminal and write the executable code into local storage space if the code writing instruction is verified.

[0100] In one embodiment, when writing service executable code, sensor 32 can write the service executable code to local free storage space; or, if historical service executable code is stored locally, the service executable code can be written to the storage space where the historical service executable code is located, so as to overwrite the historical service executable code.

[0101] In one embodiment, the mobile phone 21 can obtain the write status information of the sensor 32 through NFC signals and display the write status information to the user so that the user can keep track of the programming progress.

[0102] Step 304: After the writing is completed, sensor 32 returns a programming success notification message to mobile phone 31.

[0103] Step 305: Sensor 32 updates its own operating status.

[0104] In one embodiment, the mobile phone 21 can instruct the sensor 32 to update its own operating status after the business executable code is written, so as to establish a wireless connection with the vehicle 33 such as Bluetooth or Wi-Fi.

[0105] In one embodiment, if the vehicle 33 has not yet learned of the first identifier, the mobile phone 31 can also write the first identifier into the vehicle via Bluetooth or Wi-Fi signal so that it can successfully establish a wireless connection with the programmed sensor 32.

[0106] Step 306: Sensor 32 runs the business executable code and basic executable code, and collects the pressure data of the target tire according to the corresponding logic.

[0107] Step 307: Sensor 32 sends pressure data to vehicle 33 via wireless connection.

[0108] In one embodiment, sensor 32 can collect pressure data of the target tire by executing the business executable code and the basic executable code, and transmit the data to vehicle 33 via wireless communication.

[0109] Step 308, vehicle 33 displays pressure data to the occupants and / or initiates a pressure alarm for the target tire to a preset location.

[0110] In one embodiment, the vehicle 33 can directly display the aforementioned pressure data to an occupant (such as a driver) so that the occupant is aware of the pressure status of the target tire. Specifically, a flat or 3D model of the vehicle can be displayed, and the pressure data can be shown in the area corresponding to the actual position of the target tire within the model, so that the user can view it accurately.

[0111] In addition, if the pressure data indicates that the current pressure of the target tire is higher than the upper pressure limit or lower than the lower pressure limit, a pressure alarm is initiated to a preset party (such as the current driver, the owner of vehicle 33, or the operator of vehicle 33 (which may be a commercial vehicle)) so that they can obtain the tire pressure status in a timely and accurate manner and specify a response strategy in advance, such as timely inflation or deflation, to reduce safety risks.

[0112] This concludes the introduction of the programming scheme implemented in the programming system. Corresponding to the aforementioned embodiments, this specification also proposes a method for writing code to a tire pressure sensor implemented by a mobile terminal and a method for executing code implemented by the first tire pressure sensor, which will be described below with reference to the accompanying drawings.

[0113] Figure 4 This is a flowchart illustrating a method for writing code to a tire pressure sensor, as provided in an exemplary embodiment. This method can be applied to a mobile terminal within the aforementioned programming system. Figure 4As shown, the method includes the following steps 402-404.

[0114] Step 402: Obtain the business executable code of the first tire pressure sensor. The business executable code is generated at least based on the first identifier of the first tire pressure sensor. The first tire pressure sensor stores pre-written basic executable code.

[0115] Step 404: Write the service executable code into the first tire pressure sensor via near field communication (NFC) signal, so that the first tire pressure sensor can wirelessly communicate with the vehicle by executing the service executable code and the basic executable code when it is mounted on the target tire of the vehicle.

[0116] In one embodiment, the executable code for acquiring the first tire pressure sensor includes one of the following:

[0117] Obtain the first identifier, and generate the executable code for the service based at least on the first identifier;

[0118] Obtain the first identifier and send a code generation request containing the first identifier to the server, and receive the executable code of the service generated by the server based on the first identifier;

[0119] A code acquisition request for the first tire pressure sensor is initiated to the server, and the executable code of the service generated and returned by the server based on at least the first identifier obtained by the server itself is received.

[0120] In one embodiment, obtaining the first identifier includes one of the following:

[0121] The identifier of the second tire pressure sensor is read from the second tire pressure sensor or the vehicle and used as the first identifier of the first tire pressure sensor, wherein the first tire pressure sensor is mounted on the target tire after the second tire pressure sensor is removed from the target tire;

[0122] The system receives an identifier from a second tire pressure sensor sent by a handheld device and uses it as a first identifier for the first tire pressure sensor, the identifier being read by the handheld device from the second tire pressure sensor or the vehicle.

[0123] Initiate an identifier acquisition request for the first tire pressure sensor to the server, and receive the first identifier of the first tire pressure sensor returned by the server in response to the request;

[0124] In response to the detected identifier input operation, the input identifier is used as the first identifier of the first tire pressure sensor.

[0125] In one embodiment, it further includes:

[0126] The write status information of the first tire pressure sensor is obtained through NFC signals and displayed to the user.

[0127] In one embodiment, it further includes:

[0128] The system instructs the first tire pressure sensor to update its operating status after the executable code for the service is written.

[0129] In one embodiment, it further includes:

[0130] If the vehicle is unaware of the first identifier, the first identifier is written into the vehicle via Bluetooth or Wi-Fi signal.

[0131] In one embodiment, the executable code is generated based on a first identifier and configuration information of the first tire pressure sensor.

[0132] Figure 5 This is a flowchart illustrating a code execution method as provided in an exemplary embodiment. The method can be applied to a first tire pressure sensor in the aforementioned programming system, which stores pre-written basic executable code. Figure 5 As shown, the method includes the following steps 502-504.

[0133] Step 502: Receive the executable code for the service sent by the mobile terminal via NFC signal and write it into the local storage space. The executable code for the service is generated at least based on the first identifier of the first tire pressure sensor.

[0134] Step 504: With the first tire pressure sensor mounted on the target tire of the vehicle, wireless communication is established with the vehicle by executing the business executable code and the basic executable code.

[0135] In one embodiment, receiving the service executable code sent by the mobile terminal and writing it to local storage space includes:

[0136] The system receives executable service code sent by a mobile terminal, and if the executable service code passes verification, writes the executable service code into local storage space; or,

[0137] The system receives executable code for a service and its corresponding code writing instruction from a mobile terminal, and writes the executable code for the service to the local storage space if the code writing instruction is verified.

[0138] In one embodiment, writing the executable code for the service to local storage includes:

[0139] Write the executable code for the aforementioned service to local free storage space; or,

[0140] If historical business executable code exists in local storage, the business executable code is written to the storage space where the historical business executable code is located, thereby overwriting the historical business executable code.

[0141] In one embodiment, it further includes:

[0142] After writing the executable code for the business logic, it updates its own running status.

[0143] In one embodiment, the step of wirelessly communicating with the vehicle by executing the service executable code and the basic executable code includes:

[0144] By executing the business executable code and the basic executable code, at least the pressure data of the target tire is collected, and the pressure data is sent to the vehicle via wireless communication.

[0145] In one embodiment, the executable code is generated based on a first identifier and configuration information of the first tire pressure sensor.

[0146] The above Figure 4 and Figure 5 The specific implementation methods of each step can be found in the previous embodiments, and will not be repeated here.

[0147] Figure 6 This is a schematic structural diagram of a device provided in an exemplary embodiment. Please refer to... Figure 6 At the hardware level, the device includes a processor 602, an internal bus 604, a network interface 606, memory 608, and non-volatile memory 610, and may also include other hardware required for its functions. One or more embodiments of this specification can be implemented in software, such as the processor 602 reading the corresponding computer program from the non-volatile memory 610 into memory 608 and then running it. Of course, in addition to software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0148] Please refer to Figure 7 The tire pressure sensor code writing device can be applied to, for example... Figure 6 The device shown implements the technical solution described in this specification. The tire pressure sensor code writing device may include:

[0149] The code acquisition unit 701 is used to acquire the business executable code of the first tire pressure sensor. The business executable code is generated at least based on the first identifier of the first tire pressure sensor. The first tire pressure sensor stores pre-written basic executable code.

[0150] The code writing unit 702 is used to write the business executable code into the first tire pressure sensor via near field communication (NFC) signal, so that the first tire pressure sensor can wirelessly communicate with the vehicle by executing the business executable code and the basic executable code when it is mounted on the target tire of the vehicle.

[0151] Optionally, the code acquisition unit 701 is specifically used for one of the following:

[0152] Obtain the first identifier, and generate the executable code for the service based at least on the first identifier;

[0153] Obtain the first identifier and send a code generation request containing the first identifier to the server, and receive the executable code of the service generated by the server based on the first identifier;

[0154] A code acquisition request for the first tire pressure sensor is initiated to the server, and the executable code of the service generated and returned by the server based on at least the first identifier obtained by the server itself is received.

[0155] Optionally, the code acquisition unit 701 is specifically used for one of the following:

[0156] The identifier of the second tire pressure sensor is read from the second tire pressure sensor or the vehicle and used as the first identifier of the first tire pressure sensor, wherein the first tire pressure sensor is mounted on the target tire after the second tire pressure sensor is removed from the target tire;

[0157] The system receives an identifier from a second tire pressure sensor sent by a handheld device and uses it as a first identifier for the first tire pressure sensor, the identifier being read by the handheld device from the second tire pressure sensor or the vehicle.

[0158] Initiate an identifier acquisition request for the first tire pressure sensor to the server, and receive the first identifier of the first tire pressure sensor returned by the server in response to the request;

[0159] In response to the detected identifier input operation, the input identifier is used as the first identifier of the first tire pressure sensor.

[0160] Optionally, a status acquisition unit 703 is also included, used for:

[0161] The write status information of the first tire pressure sensor is obtained through NFC signals, and the write status information is displayed to the user.

[0162] Optionally, an update indicator unit 704 is also included, for:

[0163] The system instructs the first tire pressure sensor to update its operating status after the executable code for the service is written.

[0164] Optionally, it also includes an identification synchronization unit 705, used for:

[0165] If the vehicle is unaware of the first identifier, the first identifier is written into the vehicle via Bluetooth or Wi-Fi signal.

[0166] Optionally, the executable code is generated based on the first identifier and configuration information of the first tire pressure sensor.

[0167] Please refer to Figure 8 Code execution devices can be applied to, for example Figure 6 The device shown is used to implement the technical solution of this specification. The code execution device may include:

[0168] The code receiving unit 801 is used to receive the service executable code sent by the mobile terminal via NFC signal and write it into the local storage space. The service executable code is generated at least based on the first identifier of the first tire pressure sensor.

[0169] The code execution unit 802 is used to wirelessly communicate with the vehicle by executing the business executable code and the basic executable code when the first tire pressure sensor is mounted on the target tire of the vehicle.

[0170] Optionally, the code receiving unit 801 is specifically used for:

[0171] The system receives executable service code sent by a mobile terminal, and if the executable service code passes verification, writes the executable service code into local storage space; or,

[0172] The system receives executable code for a service and its corresponding code writing instruction from a mobile terminal, and writes the executable code for the service to the local storage space if the code writing instruction is verified.

[0173] Optionally, the code receiving unit 801 is specifically used for:

[0174] Write the executable code for the aforementioned service to local free storage space; or,

[0175] If historical business executable code exists in local storage, the business executable code is written to the storage space where the historical business executable code is located, thereby overwriting the historical business executable code.

[0176] Optionally, a state update unit 803 is also included, used for:

[0177] After writing the executable code for the business logic, it updates its own running status.

[0178] Optionally, the code execution unit 802 is specifically used for:

[0179] By executing the business executable code and the basic executable code, at least the pressure data of the target tire is collected, and the pressure data is sent to the vehicle via wireless communication.

[0180] Optionally, the executable code is generated based on the first identifier and configuration information of the first tire pressure sensor.

[0181] Based on the same concept as the methods described above, this specification also provides an electronic device, including: a processor; a memory for storing processor-executable instructions; wherein the processor performs the steps of the method as described in any of the above embodiments by executing the executable instructions.

[0182] Based on the same concept as the methods described above, this specification also provides a computer-readable storage medium having computer instructions stored thereon that, when executed by a processor, implement the steps of the methods as described in any of the above embodiments.

[0183] Based on the same concept as the methods described above, this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the methods as described in any of the above embodiments.

Claims

1. A programmable tire pressure sensor, characterized in that, It includes a control module and its connected storage module and radio frequency module, wherein the radio frequency module includes an NFC module and a vehicle-to-everything (V2X) communication module, wherein: The storage module stores pre-written basic executable code, as well as business executable code generated based on at least the first identifier of the programmable tire pressure sensor; The NFC module is configured to establish an NFC communication connection with the mobile terminal via NFC signals. The vehicle communication module is configured to establish a wireless communication connection with the vehicle after the programmable tire pressure sensor is mounted on the target tire of the vehicle. The control module is configured to execute the business executable code and the basic executable code to drive the vehicle-to-vehicle communication module to communicate wirelessly with the vehicle.

2. The programmable tire pressure sensor according to claim 1, characterized in that, The vehicle communication module includes at least one of the following: a Sub-1G module, a Bluetooth module, a Wi-Fi module, or a Zigbee module.

3. The programmable tire pressure sensor according to claim 1, characterized in that, The control module is further configured to: verify the executable code of the service, and, if the verification passes, allow the code to be stored in the storage module; or, The NFC module is further configured to receive a code writing instruction corresponding to the executable code of the service sent by the mobile terminal via an NFC signal; the control module is further configured to verify the code writing instruction and, if the verification is successful, allow the code to be stored in the storage module.

4. The programmable tire pressure sensor according to claim 1, characterized in that, The executable code for the business is stored in: Within the local free storage space of the storage module; or, The storage module was located in the storage space where historical business executable code was previously stored.

5. The programmable tire pressure sensor according to claim 1, characterized in that, The programmable tire pressure sensor also includes a sensing module connected to the control module, configured to at least collect pressure data of the target tire and send it to the control module; The control module is also configured to send the pressure data to the vehicle via the wireless communication.

Images