Management method, apparatus and system for sensor-related data

Abstract

The present application relates to a management method, apparatus and system for sensor-related data. The method is applied to a management server, and comprises: acquiring transfer-related data of any tire pressure sensor, wherein the data is used for recording the transfer process of the sensor between owners from the completion of production to activation; receiving activation-related data generated by an activation event and uploaded by an activation client, wherein the data is used for activating a sensor mounted on a target tire of a target vehicle, and upon completion of activation, the sensor is used for submitting collected tire state data to the target vehicle; and using a sensor identifier as an index to maintain sensor-related data of the sensor, wherein the sensor-related data includes the transfer-related data and the activation-related data. The solution can enable refined management of sensor-related data, achieving full lifecycle tracking of tire pressure sensors.

Description

Sensor-related data management method, device and system Technical Field

[0001] The present application relates to the field of big data, and in particular to a method, device, and system for managing sensor-related data. Background Art

[0002] TPMS (Tire Pressure Monitor System) stands for Tire Pressure Monitoring System. It automatically monitors tire pressure in real time while the vehicle is driving and issues alerts for leaks and low tire pressure to ensure driving safety. TPMS primarily consists of a tire pressure sensor (also known as a tire pressure sensor or TPMS sensor), an MCU (Microcontroller Unit), a radio frequency module, and an antenna.

[0003] Current tire pressure sensors are typically wireless. This means that after collecting signals related to tire pressure and other parameters, the tire pressure sensor encodes and modulates them into a radio frequency signal, which is then transmitted via an antenna. The vehicle's computer system's receiver receives the signal and decodes it to obtain the parameter values ​​collected by the tire pressure sensor. After replacing a tire or the tire pressure sensor installed on it, the newly installed tire pressure sensor must be activated to ensure smooth communication with the vehicle's computer system.

[0004] In related technologies, users can obtain new tire pressure sensors through various distribution channels (such as purchasing them through sales channels), then install them on their vehicle tires and activate them to ensure their proper functioning. Each stage of this process is independent and requires a high level of involvement from relevant personnel. The data from each stage is fragmented and managed in a relatively extensive manner, which is not only detrimental to the efficient management and utilization of relevant data, but also poses certain data security risks.

[0005] Summary of the Invention

[0006] This application provides a method, device, electronic device, and storage medium for managing sensor-related data to at least solve the technical problems in the related art. The technical solution of this application is as follows:

[0007] According to a first aspect of an embodiment of the present application, a method for managing sensor-related data is provided, which is applied to a management server, including:

[0008] Obtaining data related to the transfer of any tire pressure sensor, wherein the data is used to record the transfer process of the tire pressure sensor between various ownership entities from the completion of production to activation;

[0009] receiving activation-related data of any tire pressure sensor uploaded by an activation client, wherein the activation-related data is generated by an activation event of any tire pressure sensor, the activation event being used to activate any tire pressure sensor installed on a target tire of a target vehicle, and after activation is completed, the any tire pressure sensor being used to submit the collected tire status data of the target tire to the target vehicle;

[0010] Sensor-related data of any tire pressure sensor is maintained using at least the sensor identifier of any tire pressure sensor as an index, where the sensor-related data includes the flow-related data and the activation-related data.

[0011] According to a second aspect of an embodiment of the present application, a sensor-related data management system is provided, the system including a management server, the management server being configured to:

[0012] Obtaining data related to the transfer of any tire pressure sensor, wherein the data is used to record the transfer process of the tire pressure sensor between various ownership entities from the completion of production to activation;

[0013] receiving activation-related data of any tire pressure sensor uploaded by an activation client, wherein the activation-related data is generated by an activation event of any tire pressure sensor, the activation event being used to activate any tire pressure sensor installed on a target tire of a target vehicle, and after activation is completed, the any tire pressure sensor being used to submit the collected tire status data of the target tire to the target vehicle;

[0014] Sensor-related data of any tire pressure sensor is maintained using at least the sensor identifier of any tire pressure sensor as an index, where the sensor-related data includes the flow-related data and the activation-related data.

[0015] According to a third aspect of an embodiment of the present application, a sensor-related data management device is provided, which is applied to a management server, including:

[0016] a data acquisition unit configured to acquire flow-related data of any tire pressure sensor, wherein the flow-related data is used to record the flow process of the tire pressure sensor between various ownership entities from the completion of production to activation;

[0017] a data receiving unit configured to receive activation-related data of any tire pressure sensor uploaded by an activation client, wherein the activation-related data is generated by an activation event of any tire pressure sensor, the activation event being used to activate any tire pressure sensor installed on a target tire of a target vehicle, and after activation is completed, the any tire pressure sensor being used to submit the collected tire status data of the target tire to the target vehicle;

[0018] The data maintenance unit is configured to maintain sensor-related data of any tire pressure sensor using at least a sensor identifier of the any tire pressure sensor as an index, wherein the sensor-related data includes the flow-related data and the activation-related data.

[0019] According to a fourth aspect of the embodiments of the present application, an electronic device is provided, including:

[0020] a processor; a memory for storing instructions executable by the processor;

[0021] The processor is configured to execute the instructions to implement the sensor-related data management method as described in any embodiment of the first aspect above.

[0022] According to the fifth aspect of the embodiments of the present application, a storage medium is proposed. When the instructions in the storage medium are executed by the processor of the management server, the management server can execute the sensor-related data management method described in any embodiment of the first aspect above.

[0023] The technical solutions provided by the embodiments of this application bring at least the following beneficial effects:

[0024] As can be seen from the aforementioned embodiments, the management server of this solution, on the one hand, obtains the flow-related data generated by any tire pressure sensor during the flow process, and on the other hand, receives the activation-related data generated by the sensor during the activation process uploaded by the activation client, and then uses the flow-related data and activation-related data as the sensor-related data of the sensor and maintains them with the sensor identifier as the index. In this way, the management server can uniformly maintain all data involved in each process of the tire pressure sensor from production completion to activation completion (at this time, it has also been installed and can work normally). It not only realizes the full-process efficient management of the relevant data involved in the entire life cycle of the sensor (from production to use), helps to realize the tracking of the entire life cycle of the sensor, but also can avoid data loss, confusion and other security risks to a certain extent through unified and refined management.

[0025] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application, and do not constitute an improper limitation on the present application.

[0027] FIG1 is a schematic diagram of a management system for sensor-related data according to an embodiment of the present application;

[0028] FIG2 is a schematic diagram of a tire pressure sensor flow network according to an embodiment of the present application;

[0029] FIG3 is a flowchart of a method for managing sensor-related data according to an embodiment of the present application;

[0030] FIG4 is a structural diagram of an electronic device according to an embodiment of the present application;

[0031] FIG5 is a schematic block diagram of a device for managing sensor-related data according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to enable ordinary people in the art to better understand the technical solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0033] It should be noted that the terms "first," "second," and the like in the specification and claims of this application and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments of the application described herein can be implemented in an order other than those illustrated or described herein. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0034] To solve the aforementioned technical problems in related technologies, this application proposes a sensor-related data management system and a sensor-related data management method implemented by a management server in the system, which are described in detail below with reference to the accompanying drawings.

[0035] This application proposes a sensor-related data management system (hereinafter referred to as the management system), which includes a management server, which is used to:

[0036] Obtaining data related to the transfer of any tire pressure sensor, wherein the data is used to record the transfer process of the tire pressure sensor between various ownership entities from the completion of production to activation;

[0037] receiving activation-related data of any tire pressure sensor uploaded by an activation client, wherein the activation-related data is generated by an activation event of any tire pressure sensor, the activation event being used to activate any tire pressure sensor installed on a target tire of a target vehicle, and after activation is completed, the any tire pressure sensor being used to submit the collected tire status data of the target tire to the target vehicle;

[0038] Sensor-related data of any tire pressure sensor is maintained using at least the sensor identifier of any tire pressure sensor as an index, where the sensor-related data includes the flow-related data and the activation-related data.

[0039] This solution only covers the management of data related to tire pressure sensors and does not cover other types of sensors. Therefore, for the sake of brevity, the following descriptions will refer to "tire pressure sensors" as "sensors" and "any tire pressure sensor" as "any sensor" or "the sensor."

[0040] As shown in Figure 1, the management system 10 includes a management server running on a management server 11 and an activation client running on a mobile phone 14. The following description uses the example of a management system 10 including both the management server and the activation client. The management server in the management system 10 may integrate tire pressure sensor transfer functionality; alternatively, the management system 10 may include a transfer server (with integrated tire pressure sensor transfer functionality) running on a transfer server 12, which coordinates with terminals within the system to transfer tire pressure sensors between various ownership entities. Specifically, the tire pressure sensor transfer functionality may include sales (involving the transfer of ownership of funds), transfers (not involving the transfer of ownership of funds), warehousing, logistics, and other functions, which will not be further described. Any tire pressure sensor produced by a sensor manufacturer can be transferred to a user via a transfer network for installation on a vehicle's tire (e.g., on a new tire or to replace a faulty sensor in an old tire). The user may be a clerk at a vehicle repair shop or an individual user (e.g., a vehicle owner).

[0041] During the circulation of any tire pressure sensor, if it is transferred to any natural person, organization or institution (such as the subject who purchased the sensor), the subject will own the sensor and become the corresponding ownership subject of the sensor (i.e. the subject that owns the sensor). It can be seen that the complete circulation process of the tire pressure sensor from the manufacturer to the user may pass through multiple ownership subjects, such as the manufacturer, agents (or dealers), independent chain stores, repair shops (such as self-employed repair shops, mobile repair shops, 4S shops that provide vehicle repair services, etc.), individual users, etc. Among them, the above-mentioned agents may include multiple levels, such as national agents selling sensors to provincial agents at the next level, and provincial agents selling sensors to municipal agents at the next level, etc. The above-mentioned independent chain stores can be physical stores or online stores, etc. The online stores can be established based on a general e-commerce platform, or based on the aforementioned management service end and circulation network.

[0042] All ownership entities that may be involved in the circulation process of tire pressure sensors can complete pre-registration at the management server. For example, the management client can be run on the mobile phone 13 used by the agent's operating personnel, and the agent's subject identity (i.e., account, the same below) can be registered at the management server through the client. For another example, the management client can be run on the mobile phone 15 used by the operating personnel of the maintenance shop, and the subject identity of the maintenance shop can be registered at the management server through the client. For another example, the management client can also be run on the mobile phone 14 used by an individual user, and the user's own subject identity can be registered at the management server through the client. In addition, the relevant personnel (managers, ordinary staff, etc.) of the ownership entities of the above-mentioned agency, independent chain stores, maintenance shops and other institutional types can register their own personal identities and bind them with the subject identity of their own ownership entity to realize that the personnel identity belongs to the institutional identity.

[0043] In one embodiment, all ownership entities registered with the management server may form a multi-layered flow network, where the upper layer of any two adjacent layers in the flow network includes at least one upper-level entity and the lower layer includes at least one lower-level entity. Sensors belonging to any lower-level entity are transferred from at least one upper-level entity and / or at least one other lower-level entity to any lower-level entity (e.g., sold to the lower-level entity), and any ownership entity has management authority over the sensor-related data of each sensor transferred to itself or from itself to another ownership entity.

[0044] The circulation network may include a sensor sales network. In this case, the various participants in the management system can sell sensors based on this sales network, i.e., circulate sensors between multiple levels of sellers and buyers. For example, any manufacturer has management authority over the sensor-related data generated by each sensor it produces and sells throughout its lifecycle. Any distributor has management authority over the sensor-related data of all sensors it purchases (including sold and / or unsold ones). Any individual user has management authority over the sensor-related data of all tire pressure sensors it purchases (including activated and / or inactivated ones). It is understood that in this multi-level circulation network, because any ownership entity at any level has management authority over the sensor-related data of any purchased or sold sensor, that ownership entity can track the entire process of these sensors. Furthermore, the existence of this multi-level circulation network enables higher-level entities to accurately track the sensors corresponding to lower-level entities.

[0045] As shown in Figure 2, there is a circulation network including three levels, in which the ownership entities shown include manufacturers at the first level (i.e., manufacturer 1 and manufacturer 2), agents at the second level (i.e., agent 1 and agent 2) and independent chain stores (i.e., independent chain store 1), and maintenance stores at the third level (i.e., store 1, store 2, and store 3) and individual users (i.e., individual user 1). The manufacturer 1 and manufacturer 2 may belong to the same brand (i.e., they produce sensors of the same brand) or different brands (i.e., they produce sensors of different brands). Of course, any manufacturer may only produce one brand of sensor, or may produce multiple brands of sensors (such as a foundry model), and this embodiment of the present application does not limit this. In addition, Figure 2 also shows maintenance personnel in the maintenance store (i.e., maintenance worker 1 in store 1, maintenance workers 2 and 3 in store 2, maintenance worker 4 in store 3, etc.). As mentioned above, each of the above-mentioned ownership entities and related personnel can complete identity registration in advance at the management service end. The direction of the arrows in Figure 2 indicates the direction of sensor flow, that is, an arrow from any ownership entity A to another ownership entity B is used to indicate that at least one tire pressure sensor flows from A to B. The sensor flow process can include a sales process, such as agent 1 selling a batch of sensors to store 1, independent chain store 1 selling a batch of sensors to store 3, etc.; the flow process can also include a non-sales transfer process, such as when agents 1 and 2 both sell the same brand of sensors, if agent 1's current inventory is insufficient, a batch of sensors of that brand can be temporarily transferred from agent 2. This transfer process can be completed through negotiation with the brand owner, or it can be completed independently by agents 1 and 2, and the transfer process may not involve the transfer of funds (i.e., agent 2 may not pay agent 1 for the goods, etc.). Of course, the specific logic of the above-mentioned sales and transfers can be reasonably set according to actual conditions, and this application does not limit this.

[0046] In one embodiment, the ownership entities that sequentially belong to any tire pressure sensor from the time it is manufactured to the time it is activated may include the manufacturer, the agent, and the repair shop. For example, manufacturer 1 sells at least one sensor to agent 1 (i.e., agent 1 purchases at least one sensor from manufacturer 1, the same applies hereinafter), and agent 1 sells at least one of the sensors to shop 1. Alternatively, the ownership entities may include the manufacturer, an independent chain store, and a repair shop. For example, manufacturer 1 sells at least one sensor to independent chain store 1, and independent chain store 1 sells at least one of the sensors to shop 3. Alternatively, the ownership entities may include the manufacturer, an independent chain store, and an individual user. For example, manufacturer 1 sells at least one sensor to independent chain store 1, and independent chain store 1 sells at least one of the sensors to individual user 1, etc. Of course, among the ownership entities that sequentially belong to any of the above sensors from the time it is manufactured to the time it is activated, there may be multiple ownership entities at the same level, such as agent 1 and agent 2 each transferring sensors to each other, agent 2 and independent chain store 1 each transferring sensors to each other, shop 1 and shop 2 each transferring sensors to each other, etc.

[0047] It should be noted that any tire pressure sensor described in this application is "produced", which means that the production stage and pre-factory testing stage of the sensor have been completed, and thereafter, the sensor can be circulated (such as stored, sold, transported, etc.), installed and activated; any tire pressure sensor described in this application is "before activation", which means that the sensor has been circulated to its user (that is, the sensor has been owned by its user), and thereafter the user can activate the sensor (at this time, the sensor may not have been installed or has been installed).

[0048] The operations involved in the above-mentioned flow process can be completed by relevant personnel through the management client. For example, the purchasing personnel of agent 1 can initiate a sensor purchase request to the management server through the management client running on mobile phone 13 according to the purchasing needs (the management server can regard the request as a request initiated by agent 1). The management server can generate a sales order in response to the request and send it to the corresponding ownership entity (such as manufacturer 1 or agent 2), so that the latter can sell the corresponding sensor to agent 1 according to the order. Alternatively, the purchasing personnel of store 1 can initiate a sensor purchase request to the management server through the management client running on mobile phone 15 according to the purchasing needs (the management server can regard the request as a request initiated by store 1). The management server can generate a sales order in response to the request and send it to the corresponding ownership entity (such as agent 1), so that the latter can sell the corresponding sensor to store 1 according to the order. Alternatively, individual user 1 can initiate a sensor purchase request to the management server through the management client running in mobile phone 14 according to purchasing needs. The management server can generate a sales order in response to the request and send it to the corresponding ownership entity (such as independent chain store 1 or store 3) so that the latter can sell the corresponding tire pressure sensor to individual user 1 according to the order.

[0049] In the process of circulating tire pressure sensors through the above-mentioned circulation network, corresponding circulation-related data will be generated. For example, the circulation-related data of any tire pressure sensor may include at least one of the following: the factory information of any tire pressure sensor, the sales order of any tire pressure sensor (including purchase time, model, quantity, price, total amount, etc.), the logistics information of any tire pressure sensor (including shipping place, receiving place, logistics timetable, etc.), the payment information of any tire pressure sensor (account information of the payer and the payee, transfer time, etc.), the identity information of the ownership subject, etc. Of course, the specific content of the circulation-related data can also be set according to actual conditions, and the embodiments of the present application are not limited to this. It can be understood that each sensor circulating through the circulation network can generate the above-mentioned circulation-related data. The circulation-related data of each sensor can be maintained by the management server and / or the circulation server, wherein any maintenance party can save the circulation-related data it maintains in a persistent storage space such as the local disk of the maintenance party or its associated external database. Accordingly, the management server may subsequently obtain the flow-related data of any sensor from the flow-related data maintained by itself or the flow server.

[0050] In addition, the management system 10 can be maintained by the sensor manufacturer to manage the sensor-related data generated by the sensors produced and sold by the manufacturer during their entire life cycle; or, the management system 10 can also be maintained by the brand of the sensor to manage the sensor-related data generated by the brand of sensors produced and sold by the manufacturer on behalf of the brand during their entire life cycle.

[0051] Through the above method, repair shops and individual users can purchase the required tire pressure sensors. Relevant personnel (such as repairman 1 or individual user 1) can then operate the activation client to program, learn, and match the tire pressure sensors, completing the sensor activation process. The activation event is achieved through the coordination of the activation terminal, the electronic device containing the activation client, the target vehicle, and any tire pressure sensor. As shown in Figure 1, the relevant personnel can operate the activation client running on a mobile phone 14 to coordinate with the activation terminal 21, the tire pressure sensor 22 (i.e., any sensor previously purchased by the repair shop or individual user), and the target vehicle 23 to complete the sensor activation process (i.e., coordinate to complete the sensor activation event). After the sensor is installed on the target tire of the target vehicle 23 and activated, the sensor can begin normal operation, namely, submitting the tire status data it collects from the target tire to the target vehicle 23 via wireless communication. The mobile phone 14, activation terminal 21, tire pressure sensor 22, and target vehicle 23 together constitute the activation system 20 for the tire pressure sensor 22.

[0052] It should be noted that the management client and activation client described in this application can actually be the same client, that is, the client can integrate data management functions and sensor activation functions; of course, it can also integrate sensor circulation functions to facilitate users to purchase or sell sensors, etc.

[0053] In activation system 20, tire pressure sensor 22 can communicate with target vehicle 23 by transmitting radio frequency signals to transmit data related to the target tire's status. Furthermore, mobile phone 14 can establish a first wireless connection (e.g., NFC, Bluetooth, etc.) with tire pressure sensor 22, a second wireless connection (e.g., Bluetooth, Wi-Fi, etc.) with activation terminal 21, and a third wireless connection (e.g., NFC, radio frequency, etc.) with tire pressure sensor 22. Target vehicle 23 is equipped with a communication antenna to facilitate this wireless connection with the tire pressure sensor. As can be seen, any two of the mobile phone 14, activation terminal 21, and tire pressure sensor 22 in this system can interact via wireless connections. This wireless connection between any two of these parties is effectively an end-to-end connection between them. Because the various devices in this activation system can interact via this wireless connection, the system can achieve the desired functionality of tire pressure sensor pairing without requiring special cables, simplifying the system architecture and reducing costs. In addition, the activation terminal 21 may establish a wired connection with the target vehicle 23 via an OBD (On-Board Diagnostics) interface.

[0054] Among them, when an NFC connection or wireless radio frequency connection is established between the activation terminal 21 (or mobile phone 14) and the tire pressure sensor 22, the two can achieve millisecond-level device connection (or pairing) through a wireless wake-up signal. The awakened device (i.e., the tire pressure sensor 22) is essentially equivalent to a passive device. During this connection process, there is no need for the user to manually perform "pairing" and "connection confirmation" operations similar to Bluetooth or Wi-Fi technology, which helps to achieve rapid connection and information exchange between devices. However, it should be noted that although the establishment process of the above-mentioned NFC connection or wireless radio frequency connection is extremely fast and is usually completed together with the data transmission process, the above-mentioned connection should still be regarded as a wireless connection, that is, the connection established between the activation terminal 21 and the tire pressure sensor 22 is a wireless connection (i.e., the aforementioned third wireless connection).

[0055] The following briefly describes the two stages of programming and learning involved in the activation process of the tire pressure sensor 22:

[0056] Programming stage: The mobile phone 14 determines the communication parameters of the target vehicle 23, which may include connection parameters and submission configuration parameters. In addition, the activation client (via the first wireless connection) writes the communication parameters to the tire pressure sensor 22 by itself, or the activation client (via the second wireless connection) instructs the activation terminal 21 (via the third wireless connection) to write the communication parameters to the tire pressure sensor 22. The process of writing the communication parameters to the tire pressure sensor 22 is the process of programming the sensor. The programmed tire pressure sensor 22 can be installed on the target tire of the target vehicle 23 (which can be any tire of the vehicle); of course, the above-mentioned programming can also be performed after the installation is completed, and this application does not limit this.

[0057] Learning Phase: Mobile phone 14 reads the sensor ID from tire pressure sensor 22 and sends it to activation terminal 21. Alternatively, activation terminal 21 automatically reads the sensor ID from tire pressure sensor 22. Then, after establishing a connection with the target vehicle 23 via the on-board diagnostics (OBD) interface, activation terminal 21 transmits the sensor ID to target vehicle 23 under the direction of mobile phone 14. The user can also specify the target location of the target tire on target vehicle 23 via mobile phone 14, and activation terminal 21 transmits the corresponding location information to target vehicle 23. In this way, target vehicle 23 learns the sensor ID (and possibly the location information) of tire pressure sensor 22.

[0058] After the above-mentioned programming and learning phases are completed, the activation process of the tire pressure sensor 22 is completed (e.g., the maintenance of the target vehicle 23 is completed). Thereafter, the tire pressure sensor 22 can cooperate with the target vehicle 23 to start normal operation, that is, for the tire status data collected by itself, the sensor can send status-related data including the target sensor identification and the tire status data to the target vehicle 23 according to the target communication parameters written locally, so that the target vehicle can receive and identify it. Among them, the activation-related data of any tire pressure sensor can include at least one of the following: activation time, communication parameters written into any tire pressure sensor during activation (i.e., the aforementioned connection parameters and), identity information of the activating user (such as the aforementioned maintenance worker 1 or individual user 1, etc.), characteristic information of the target vehicle, and owner information of the target vehicle.

[0059] It should be noted that any of the management server and transfer server in the management system 10 can be a physical server containing an independent host, or can also be a virtual server, cloud server, etc. carried by a host cluster, and the embodiments of the present application are not limited to this. Mobile phones 31 to 15 are only one type of electronic device that can be used by relevant personnel. In fact, users can use any type of electronic device to run the aforementioned management client, and use any type of electronic device with wireless connection function to run the aforementioned activation client. Exemplarily, the electronic devices used by users can also be: tablet devices, laptops, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), VR (Virtual Reality) devices, AR (Augmented Reality) devices, etc., and the embodiments of the present application are not limited to this.

[0060] In addition, any of the aforementioned management clients and activation clients can be native apps (applications), web applications (or web pages) implemented based on browsers, or mini-programs implemented based on other applications. Apps typically require pre-installation and startup, while web applications and mini-programs can be online "clients" built using HTML5 technology. These client programs typically do not require a specific "installation" step to run, but are integrated into browsers or other applications and run as independent pages or functional components (or plug-ins). Any of these clients can provide users with an operational human-machine interface, based on which users can perform corresponding operations in the human-machine interface to operate their phones to participate in the flow and / or activation functions for sensors. Taking mobile phone 14 as an example, because the phone can display a human-machine interface for user operation, the activation terminal 21 itself does not need to be equipped with a display component such as a screen. It only needs to execute corresponding response processing under the instructions (or control) of mobile phone 14, thereby simplifying the hardware structure and software logic of the terminal and facilitating the miniaturization of the terminal.

[0061] Corresponding to the aforementioned management system, the present application also proposes a method for managing sensor-related data, which is applied to a management server (in the aforementioned management system). As shown in FIG3 , the method may include the following steps 302 - 306 .

[0062] Step 302 : Acquire the flow-related data of any tire pressure sensor, where the flow-related data is used to record the flow process of the tire pressure sensor between various ownership entities from the completion of production to activation.

[0063] In the process of circulating tire pressure sensors through the circulation network, corresponding circulation-related data will be generated, wherein the circulation-related data of any tire pressure sensor is used to record the circulation process of the sensor between various ownership entities from the completion of production to activation; in other words, the circulation-related data of any tire pressure sensor is generated during the circulation process of the sensor to record (or represent) the circulation process. Based on this, the management server can obtain the circulation-related data of each tire pressure sensor that is circulated. For any of the sensors, its circulation-related data can be obtained in advance before obtaining the activation-related data of the sensor (i.e., executing step 302 first and then executing step 304), or its circulation-related data can be obtained after obtaining the activation-related data of the sensor (i.e., executing step 304 first and then executing step 302). The embodiment of the present application does not limit the execution order of step 302 and step 304.

[0064] In one embodiment, the management server can maintain the data associated with each tire pressure sensor being transferred. In this case, the management server can retrieve the data associated with any tire pressure sensor from this data. In this case, the management server maintains the sensor data itself. Retrieving the data associated with any tire pressure sensor can involve querying the persistent storage for the data associated with that sensor and writing the retrieved data to its own memory. Retrieving the data associated with the management server from its own maintained data is faster, facilitating efficient data acquisition.

[0065] Alternatively, if the transfer data for each tire pressure sensor being transferred is maintained by a transfer server pre-associated with the management server, the management server can obtain the transfer data for any tire pressure sensor from the transfer server. In this case, the transfer data is maintained by the transfer server, which helps reduce the data maintenance burden on the management server and separates the maintenance logic from the management logic of the transfer data, helping to improve the operational efficiency of the management server and the subsequent management efficiency of the transfer data.

[0066] The management server can use a variety of methods to obtain the flow-related data of any tire pressure sensor from the transfer server. For example, the management server can receive the flow-related data of any tire pressure sensor (proactively pushed) by the transfer server, such as the transfer server pushing the flow-related data of any tire pressure sensor to the management server in real time after generating it. Alternatively, the management server can periodically push the flow-related data of each tire pressure sensor generated within a recent period. This push can be implemented based on a message queue, with the transfer server acting as the producer of each message in the message queue and the management server acting as the consumer of the message. Each message can contain the flow-related data of at least one sensor. This method allows the management server to obtain the flow-related data asynchronously, helping to simplify subsequent processing logic. For another example, the management server can request and receive the flow-related data of any tire pressure sensor from the transfer server. This method only requests the flow-related data from the transfer server when needed, helping to reduce the data transmission workload of the transfer server.

[0067] In one embodiment, the management server can obtain the flow-related data of any tire pressure sensor in a variety of ways. For example, the flow-related data of any tire pressure sensor can be obtained according to the sensor identifier of the sensor. If the data acquisition request sent to the aforementioned flow server can only include the sensor identifier of any tire pressure sensor, then the flow server can specifically search for the flow-related data of the sensor according to the identifier and return it to the management server, so that the management server can obtain the flow-related data of the sensor in a targeted manner. For another example, the management server can also obtain the flow-related data of multiple tire pressure sensors in batches, and query the flow-related data of any tire pressure sensor according to the sensor identifier from the obtained flow-related data. For example, the data acquisition request sent to the aforementioned circulation server may include relevant information such as the model, batch, production date, etc. of multiple sensors (including any of the tire pressure sensors), and the circulation server may determine the circulation-related data of each tire pressure sensor that meets the relevant information and return it to the management server, so that the sensor can obtain the circulation-related data of each of the above-mentioned tire pressure sensors (including any of the tire pressure sensors) in batches, further improving the efficiency of obtaining the circulation-related data.

[0068] As mentioned above, all ownership entities registered at the management service end can constitute a circulation network including multiple levels, in which the upper level of any two adjacent levels in the circulation network contains at least one upper level entity, and the lower level contains at least one lower level entity, wherein the sensors belonging to any lower level entity are transferred from at least one upper level entity and / or at least one other lower level entity to any lower level entity (such as sold to the lower level entity), and any ownership entity has management authority over the sensor-related data of each sensor transferred to itself or from itself to other ownership entities.

[0069] In one embodiment, based on the aforementioned multi-level circulation network, the management server can participate in the circulation process of the sensor (i.e., participate in the realization of the circulation of the sensor). For example, the management server can receive a sensor purchase request initiated by the first ownership subject, wherein the first ownership subject can be any one of the multiple ownership subjects that have completed registration, and the request can be specifically initiated by the relevant personnel of the first ownership subject through the electronic device used by themselves. As shown in Figure 2, the employees of agent 1 can initiate a sensor purchase request through their own mobile phones, and the management server can regard the received request as initiated by agent 1; or, the employees of independent chain store 1 can also initiate a sensor purchase request through their own computers, and the management server can regard the received request as initiated by independent chain store 1.

[0070] Furthermore, if the management server itself is integrated with a circulation function, the management server can generate a sales order based on the sensor purchase request and send it (i.e., the sales order) to the ownership subject specified in the sensor purchase request (i.e., the recipient of the sensor purchased this time is specified in the request), or to the ownership subject pre-associated with the first ownership subject (i.e., the pre-associated ownership subject is used as the default recipient of the sensor purchased this time). Among them, the level of the ownership subject (that receives the sales order) in the circulation network should not be lower than (i.e., equal to or higher than) the level of the first ownership subject in the circulation network, thereby realizing the sales behavior of the lower-level ownership subject purchasing sensors from the upper-level (or same-level) ownership subject. The sales order is used to instruct the ownership subject to sell the corresponding (quantity and model) tire pressure sensors to the first ownership subject in accordance with the information recorded in the order to meet the subject's sensor purchase needs. This may involve circulation-related data such as logistics information and payment information, which will not be repeated here. Correspondingly, the management server can also maintain the sales data of the sensors sold by the ownership entity in accordance with the sales order (this data is generated during the above-mentioned circulation process and concentrated on the management server) as part of the circulation-related data of the sensor (i.e., the sensor sold by the ownership entity).

[0071] Continuing with the aforementioned embodiment, if a sensor purchase request is received from agent 1, the management server can determine the ownership entity specified in the request. For example, if the request includes the entity identifier of manufacturer 1, manufacturer 1 can be determined as the ownership entity specified in the request; if the request includes the entity identifier of agent 2, agent 2 can be determined as the ownership entity specified in the request. Alternatively, if the sensor purchase request does not include any entity identifier, the ownership entity pre-associated with the first ownership entity can be determined. For example, the management server can determine manufacturer 1 and / or agent 2 as the ownership entity pre-associated with agent 1 based on the pre-association relationships it maintains. Of course, the above method can determine at least one ownership entity of the first ownership entity, and can also determine order information such as sensor model, quantity, and price corresponding to each ownership entity. Furthermore, based on this order information, sales orders can be generated for each ownership entity and issued to the corresponding ownership entity.

[0072] Alternatively, if the management server does not have integrated circulation functionality, the management server may forward the sensor purchase request to a circulation server pre-associated with the management server (which has integrated slave sensor circulation functionality), so that the circulation server generates a sales order based on the sensor purchase request and issues it to the owner entity specified in the request or to an owner entity pre-associated with the first owner entity. Similarly, the ownership entity (receiving the sales order) must be at a level within the circulation network no lower than the first ownership entity's level within the circulation network. The sales order instructs the ownership entity to sell the corresponding (quantity and model) tire pressure sensors to the first ownership entity in accordance with the information recorded in the order to satisfy the first ownership entity's sensor purchase needs. Furthermore, the management server may receive and maintain sales data for tire pressure sensors sold by the ownership entity in accordance with the sales order (this data is generated during the circulation process and aggregated to the circulation server, and then sent by the circulation server to the management server for maintenance) as part of the circulation-related data for the tire pressure sensor.

[0073] Through the above method, the management server can obtain the flow-related data generated during the complete flow process of any tire pressure sensor from the completion of production to the start of installation.

[0074] Step 304: Receive activation-related data of any tire pressure sensor uploaded by the activation client, wherein the activation-related data is generated by an activation event of any tire pressure sensor, and the activation event is used to activate any tire pressure sensor installed on the target tire of the target vehicle. After the activation is completed, any tire pressure sensor is used to submit the collected tire status data of the target tire to the target vehicle.

[0075] In one embodiment, the aforementioned activation terminal, the electronic device (such as a mobile phone) where the activation client is located, the target vehicle and any tire pressure sensor can cooperate with each other to complete the activation event for the sensor, that is, the above parties cooperate with each other to activate any tire pressure sensor installed on the target tire of the target vehicle, so that the sensor can establish a normal wireless connection with the target vehicle (that is, the aforementioned first wireless connection), and upload the tire status data of the target tire detected by itself to the target vehicle based on the wireless connection. Among them, the successful completion of any activation event can indicate the completion of an assembly or maintenance for the target vehicle. Taking maintenance as an example, during the above maintenance process (that is, the activation event has not been completed) or after the maintenance is completed (that is, the activation event has been completed), the client can upload the corresponding activation-related data to the management server so that the latter can cache the data and prepare for subsequent data maintenance.

[0076] As shown in Figure 1, after the repairman 1 specifies the model information of the target vehicle in the activation client running on the mobile phone 14, the activation client determines the target communication parameters to be written to the tire pressure sensor 22 from the candidate communication parameters stored locally on the mobile phone 14. The activation client can then upload the parameters to the management server. Alternatively, if the activation client requests the management server to obtain the target communication parameters, the management server can return the parameters to the mobile phone 14 and record the parameters locally. If the repairman 1 specifies the model information of the target vehicle and the location information of the target tire (to be repaired) in the target vehicle in the activation client, the activation client can immediately upload the above-mentioned model information and location information to the management server, or it can upload the above-mentioned model information and location information after the above-mentioned activation event is completed. This embodiment of the present application is not limited to this.

[0077] Through the above method, the management server can obtain the activation-related data generated for the activation event of any tire pressure sensor, that is, the activation-related data generated during the installation of the sensor.

[0078] Step 306 : Maintain sensor-related data of any tire pressure sensor using at least the sensor identifier of any tire pressure sensor as an index, where the sensor-related data includes the flow-related data and the activation-related data.

[0079] After obtaining the flow-related data and activation-related data of any management server, the flow-related data and activation-related data can be used as sensor-related data of the sensor, and the data can be maintained with the sensor identifier of the sensor as the index, thereby establishing an association between the flow-related data and the activation-related data.

[0080] As can be seen from the aforementioned embodiments, the management server of this solution, on the one hand, obtains the flow-related data generated by any tire pressure sensor during the flow process, and on the other hand, receives the activation-related data generated by the sensor during the activation process uploaded by the activation client, and then uses the flow-related data and activation-related data as the sensor-related data of the sensor and maintains them with the sensor identifier as the index. In this way, the management server can uniformly maintain all data involved in each process of the tire pressure sensor from production completion to activation completion (at this time, it has also been installed and can work normally). It not only realizes the full-process efficient management of the relevant data involved in the entire life cycle of the sensor (from production to use), helps to realize the tracking of the entire life cycle of the sensor, but also can avoid data loss, confusion and other security risks to a certain extent through unified and refined management.

[0081] It should be noted that the sensor identifier of any tire pressure sensor described herein is global information (or a global identifier) ​​that uniquely characterizes the sensor. For example, during the production phase of any tire pressure sensor, the sensor identifier can be generated according to a preset rule or algorithm and written into the sensor's local storage (i.e., the identifier is written as the sensor's default configuration information). Based on this, during the subsequent learning phase for the sensor's activation event, the mobile phone or activation terminal can read the written sensor identifier from the sensor and then send the identifier to the target vehicle to complete the learning phase. Alternatively, the sensor identifier of any tire pressure sensor can be generated according to a preset rule or algorithm during the flow or activation process, and the sensor identifier can be included as part of the corresponding flow-related data and / or activation-related data, so that the data can be subsequently managed using the identifier as an index. Of course, the sensor identifier can also be generated in any other manner, and the embodiments of the present application are not limited thereto. However, regardless of the generation method used, the global uniqueness of any sensor identifier should be ensured, that is, the situation where "different sensors have the same sensor identifier" should be avoided. In addition, in addition to maintaining the sensor-related data of any tire pressure sensor using the sensor identifier as an index, other data can also be used as indexes for maintenance, such as the manufacturer name, agent name, store name, personal user account, and circulation time information in circulation-related data, or the sensor brand, sensor model, sensor price, and activation time information in activation-related data. Maintaining sensor-related data using the above-mentioned multiple data as indexes facilitates subsequent management of the sensor-related data. For example, data statistics can be performed based on the maintenance corresponding to the above-mentioned multiple indexes (such as counting the number of sensor activations in a store over a period of time, or counting the number of sensor sales in an independent chain store over a period of time), further improving the efficiency and quality of sensor-related data management from the storage, query, and statistical aspects.

[0082] In one embodiment, the management server can also perform statistical processing on the flow-related data it maintains and maintain corresponding statistical results for user query. Of course, the above statistical processing can be performed according to a pre-established statistical plan (i.e., pre-statistics, such as periodic statistics, or processing started when the amount of maintained flow-related data meets a threshold, etc.), so that the statistical results can be directly returned to the initiator when a data query request is received. Alternatively, the above statistical processing can be performed in response to a received data query request (i.e., temporary statistics), thereby reducing the workload of unnecessary statistical processing.

[0083] Specifically, for the target dimension corresponding to any data in the flow-related data and / or the activation-related data, the management server can (according to preset statistical rules) count the relevant indicators of each tire pressure sensor (which may include any tire pressure sensor) under the target dimension, and maintain the statistical results as the sensor-related data of each tire pressure sensor (of course, only one copy of the original data of the statistical results can be saved, and a mapping relationship between the statistical results and the each tire pressure sensor can be established). Taking the flow network shown in Figure 1 as an example, for the number of sensors sold (this target dimension) corresponding to the identity information of agent 1 (this flow-related data), the management server can count the number of tire pressure sensors sold by agent 1 in the past month (or the current month at the current moment) (i.e., the relevant indicators), and maintain the statistical results as the sensor-related data of this part of the tire pressure sensors. For another example, for the number of sensor activations (this target dimension) corresponding to the identity information of the user who performed the activation operation in Store 2 (this activation-related data), the management server can count and maintain the number of tire pressure sensors activated by the maintenance worker 2 in the past week (or the current week at the current moment) (i.e., the relevant indicator). This number can be used to characterize the workload of the maintenance worker 2 in completing the activation event in the past week (i.e., how many tire pressure sensors were activated). In addition, the statistical results can be maintained as the sensor-related data of this part of the tire pressure sensors. Of course, other relevant indicators can also be counted according to actual needs, which will not be repeated here.

[0084] Alternatively, in response to a statistical request initiated for a target dimension corresponding to the flow-related data and / or the activation-related data, the management server can count the relevant indicators of each tire pressure sensor under the target dimension according to the statistical range contained in the statistical request, and return the statistical results to the initiator of the statistical request. In this way, relevant indicators can be temporarily counted in response to a statistical request initiated by the user, which will not be repeated here.

[0085] Furthermore, since the management server maintains sensor-related data (including flow-related data and activation-related data, and possibly the aforementioned statistical results) for which each ownership entity has management authority, any ownership entity can query this data for user viewing. Accordingly, the management server can receive a data query request containing data query conditions initiated by a second ownership entity, then query the sensor-related data for which the second ownership entity has management authority for target data that meets the data query conditions, and return the target data to the second ownership entity. In this way, the second ownership entity can query the target data that meets the data query conditions from the sensor identifiers for which it has management authority, thereby satisfying its own data query needs.

[0086] Among them, similar to the first ownership entity, the second ownership entity can also be any ownership entity registered at the management service end. Therefore, the first ownership entity and the second ownership entity can be the same ownership entity or different ownership entities. The embodiment of this application does not limit this.

[0087] For a second-owner entity with a data query need, it can determine the corresponding data query conditions based on its needs and initiate a data query request containing these conditions. These data query conditions specify to the management server which tire pressure sensors and sensor-related data should be queried. For example, in a first data query request initiated by manufacturer 1, the data query conditions may include: the total number of tire pressure sensors with model xxx shipped (i.e., sold) in the first half of this year (i.e., January-June). Upon completion of the query, the management server may return this total number to the second-owner entity. In a second data query request initiated by dealer 2, the data query conditions may include: the total number of activated tire pressure sensors purchased (procured) from manufacturer 1 in May of this year. Upon completion of the query, the management server may return this total number to the second-owner entity. In a third data query request initiated by store 2, the data query conditions may include: the total number of tire pressure sensors with model yyy activated by repairman 3 last month, along with the sensor IDs of each sensor. Upon completion of the query, the management server may return this total number and a list of the sensor IDs of each tire pressure sensor to the second-owner entity.

[0088] Furthermore, if the tire pressure sensor being queried is circulated through the aforementioned multi-level circulation network, any tire pressure sensor for which any owner at the highest level has management authority will be transferred from that owner to at least one owner at the next lower level. For example, after manufacturer 1 sells certain tire pressure sensors to dealer 1, manufacturer 1 can query the sensor-related data of these tire pressure sensors; after dealer 1 sells certain tire pressure sensors to store 2, dealer 1 can query the sensor-related data of these tire pressure sensors. Of course, a lower-level owner may consider the sensor-related data for which they have management authority private and, for some reason, may not want it to be accessible to the owner at the next higher level. In this case, the lower-level owner can set query permissions for the sensor-related data for which they have management authority, such as allowing only themselves (i.e., members of their organization) to query this data while denying access to the data by the owner at the next higher level (or multiple levels). For example, store 1 can set permissions for each tire pressure sensor activated by repairman 1, allowing only store 1 personnel to query the data, while denying access to dealer 1 and manufacturer 1. Of course, the above-mentioned query permissions can also be set from multiple dimensions such as data type, time range, sensor model, sensor price, etc., to achieve refined management of sensor-related data query permissions and disclosure scope. This application does not limit the specific setting method.

[0089] It should be noted that the above-mentioned data query request can actually be initiated by members within the second ownership entity, such as the turnover personnel of manufacturer 1 can initiate the above-mentioned first data query request, the management personnel of agent 2 can initiate the above-mentioned second data query request, and the maintenance worker 3 of store 2 can initiate the above-mentioned third data query request, etc., which will not be repeated here. In addition, the electronic devices used by the above-mentioned relevant personnel can run a management client, so that the above-mentioned relevant personnel can initiate the above-mentioned data query request through the management client.

[0090] In one embodiment, the data query request can be initiated by any member of the second ownership entity (which can be a small group or a natural person within the entity). In this case, the management server can, based on the member's membership, identify candidate data for which the member has query permission from within the sensor-related data for which the second ownership entity has management permission, and then determine the target data that meets the data query criteria from within the candidate data. In this way, the second ownership entity can exercise more fine-grained query permission control (accurate to small groups or even natural persons within the entity) for the sensor-related data for which it has management permission, further achieving refined control over query permissions and data disclosure scope, thereby helping to improve data security.

[0091] The organizational structure of the second ownership entity may include multiple hierarchical levels. For sensor-related data for which the second ownership entity has management authority, at least some members of the second ownership entity may have query authority over this sensor-related data. The level of query authority granted to any member is positively correlated with their rank within the multiple hierarchical levels. For example, the hierarchical levels of employees at Store 1 are, from highest to lowest, store manager, team leader, and maintenance worker. In this case, the store manager has higher data query authority than the team leader, who in turn has higher data query authority than the maintenance worker. For example, the store manager can query the statistical results of all tire pressure sensors activated by all maintenance workers in the store; the team leader can view the statistical results of all tire pressure sensors activated by each maintenance worker in their team, as well as the individual statistical results and / or detailed data related to tire pressure sensor transactions; and any maintenance worker can view the statistical results of all tire pressure sensors activated by them, as well as the detailed data related to each tire pressure sensor within that team. This approach enables hierarchical management of query authority for transaction-related data.

[0092] Figure 4 is a schematic structural diagram of an electronic device shown in the present application. Please refer to Figure 4. At the hardware level, the server includes a processor 401, a network interface 402, a memory 403, a non-volatile memory 404, and an internal bus 405. Of course, it may also include hardware required for other services. One or more embodiments of the present application can be implemented based on software, such as the processor 401 reading the corresponding computer program from the non-volatile memory 404 into the memory 403 and then running it. Of course, in addition to software implementation, one or more embodiments of the present application do not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0093] FIG5 is a block diagram of a sensor-related data management device shown in this application. Referring to FIG5 , the device can be applied to the electronic device shown in FIG4 to implement the technical solution described in this application. The device is applied to the management server and includes:

[0094] The data acquisition unit 501 is configured to acquire flow-related data of any tire pressure sensor, wherein the flow-related data is used to record the flow process of the tire pressure sensor between various ownership entities from the completion of production to activation;

[0095] a data receiving unit 502 configured to receive activation-related data of any tire pressure sensor uploaded by an activation client, wherein the activation-related data is generated by an activation event of any tire pressure sensor, the activation event being used to activate any tire pressure sensor installed on a target tire of a target vehicle, and after activation is completed, the any tire pressure sensor being used to submit the collected tire status data of the target tire to the target vehicle;

[0096] The data maintenance unit 503 is configured to maintain sensor-related data of any tire pressure sensor using at least the sensor identifier of any tire pressure sensor as an index, where the sensor-related data includes the flow-related data and the activation-related data.

[0097] Optionally, the data acquisition unit 501 is specifically configured to:

[0098] Acquire the flow-related data of any tire pressure sensor from the flow-related data of each sensor maintained by the self; or

[0099] The flow-related data of any tire pressure sensor is obtained from the flow service end pre-associated with the management service end.

[0100] Optionally, the data acquisition unit 501 is specifically configured to:

[0101] receiving the flow-related data of any tire pressure sensor pushed by the flow service end; or,

[0102] Request the transfer service end and receive the transfer-related data of any tire pressure sensor returned by the transfer service end.

[0103] Optionally, the data acquisition unit 501 is specifically configured to:

[0104] Batch acquire the flow-related data of multiple tire pressure sensors, and query the flow-related data of any tire pressure sensor according to the sensor identifier from the acquired flow-related data; or

[0105] The flow-related data of any tire pressure sensor is obtained according to the sensor identification of any tire pressure sensor.

[0106] Optionally, also include:

[0107] The first statistical unit 504 is configured to, for a target dimension corresponding to the flow-related data and / or the activation-related data, collect statistics on relevant indicators of each tire pressure sensor under the target dimension, and maintain the statistical results as sensor-related data of each tire pressure sensor; or

[0108] The second statistical unit 505 is configured to respond to a statistical request initiated for a target dimension corresponding to the flow-related data and / or the activation-related data, count the relevant indicators of each tire pressure sensor under the target dimension according to the statistical range contained in the statistical request, and return the statistical results to the initiator of the statistical request.

[0109] Optionally, all ownership entities registered at the management server constitute a circulation network comprising multiple levels, wherein the upper level of any two adjacent levels in the circulation network comprises at least one upper level entity and the lower level comprises at least one lower level entity, wherein:

[0110] The tire pressure sensor belonging to any subordinate entity is sold to any subordinate entity by at least one superior entity and / or at least one other subordinate entity, and any ownership entity has management authority over the sensor-related data of the tire pressure sensor transferred to itself or from itself to other ownership entities.

[0111] Optionally, also include:

[0112] The purchase request receiving unit 506 is configured to receive a sensor purchase request initiated by the first ownership entity;

[0113] The first order generating unit 507 is configured to generate a sales order according to the sensor purchase request and send it to the ownership entity specified in the sensor purchase request or the ownership entity pre-associated with the first ownership entity; and maintain the sales data of the tire pressure sensors sold by the ownership entity according to the sales order as part of the flow-related data of the tire pressure sensors; or

[0114] The second order generating unit 508 is configured to forward the sensor purchase request to the sales server pre-associated with the management server, so that the sales server generates a sales order according to the sensor purchase request and sends it to the ownership entity specified in the sensor purchase request or the ownership entity pre-associated with the first ownership entity, and receives and maintains sales data of tire pressure sensors sold by the ownership entity according to the sales order as part of the flow-related data of the tire pressure sensor;

[0115] The level of the ownership entity in the circulation network is not lower than the level of the first ownership entity in the circulation network.

[0116] Optionally, also include:

[0117] The query request receiving unit 509 is configured to receive a data query request including data query conditions initiated by the second ownership entity;

[0118] The query and return unit 510 is configured to query target data that meets the data query condition from the sensor-related data that the second ownership subject has management authority over, and return the target data to the second ownership subject.

[0119] Optionally, the data query request is initiated by any member of the second ownership entity, and the data query and return unit 510 is specifically configured to:

[0120] determining, based on the membership identity of any one of the members, candidate data for which any one of the members has query authority, from the sensor-related data for which the second ownership subject has management authority;

[0121] Target data that meets the data query condition is searched from the candidate data.

[0122] Optionally, the organizational structure of the second ownership entity includes multiple levels, and for sensor-related data for which the second ownership entity has management authority, at least some members of the second ownership entity have query authority for this sensor-related data, wherein:

[0123] The level of query authority possessed by any member is positively correlated with the level of the member in the multiple levels.

[0124] Optionally, the activation event is completed by cooperation among the activation terminal, the electronic device where the activation client is located, the target vehicle, and any one of the tire pressure sensors.

[0125] Optionally, the ownership entities to which any tire pressure sensor belongs from the time of production completion to activation include any of the following:

[0126] Manufacturers, agents and repair shops;

[0127] Manufacturers, independent chains and repair shops;

[0128] Manufacturers, independent chains and individual users.

[0129] Optionally, the flow-related data includes at least one of the following: factory information of any tire pressure sensor, sales order of any tire pressure sensor, logistics information of any tire pressure sensor, payment information of any tire pressure sensor, and identity information of the ownership subject;

[0130] The activation-related data includes at least one of the following: activation time, communication parameters written into any tire pressure sensor during activation, identity information of the activation operation user, characteristic information of the target vehicle, and owner information of the target vehicle.

[0131] In addition, the present application also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of the method described in any of the aforementioned embodiments of the present application are implemented.

[0132] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0133] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

[0134] It should be noted that, in this application, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. The terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element.

[0135] The above is a detailed introduction to the methods and devices provided in the embodiments of the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the methods and core ideas of the present application. At the same time, for those skilled in the art, based on the ideas of the present application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for managing sensor-related data, characterized in that Applied to a management server, including: Obtain the transfer-related data of any tire pressure sensor, where the transfer-related data is used to record the transfer process of the any tire pressure sensor among various ownership entities from the completion of production to before activation; Receive the activation-related data of the any tire pressure sensor uploaded by an activation client. Among them, the activation-related data is generated by the activation event of the any tire pressure sensor, and the activation event is used to activate the any tire pressure sensor installed on a target tire of a target vehicle. After activation, the any tire pressure sensor is used to submit the tire status data of the target tire collected to the target vehicle; Maintain the sensor-related data of the any tire pressure sensor at least indexed by the sensor identifier of the any tire pressure sensor, where the sensor-related data includes the transfer-related data and the activation-related data.

2. The method according to claim 1, wherein The obtaining of the transfer-related data of any tire pressure sensor includes: Obtain the transfer-related data of the any tire pressure sensor from the transfer-related data of each sensor maintained by itself; or, Obtain the transfer-related data of the any tire pressure sensor from a transfer server pre-associated with the management server.

3. The method according to claim 2, characterized in that, The obtaining of the transfer-related data of the any tire pressure sensor from a transfer server pre-associated with the management server includes: Receive the transfer-related data of the any tire pressure sensor pushed by the transfer server; or, Request and receive the transfer-related data of the any tire pressure sensor returned by the transfer server.

4. The method according to claim 1, wherein The obtaining of the transfer-related data of any tire pressure sensor includes: Batch obtain the transfer-related data of multiple tire pressure sensors, and query the transfer-related data of the any tire pressure sensor from the obtained transfer-related data according to the sensor identifier; or, Obtain the transfer-related data of the any tire pressure sensor according to the sensor identifier of the any tire pressure sensor.

5. The method according to claim 1, wherein It further includes: For the target dimension corresponding to the transfer-related data and / or the activation-related data, count the relevant indicators of each tire pressure sensor under the target dimension, and respectively maintain the statistical results as the sensor-related data of each tire pressure sensor; Or, In response to a statistical request initiated for the target dimension corresponding to the transfer-related data and / or the activation-related data, count the relevant indicators of each tire pressure sensor under the target dimension according to the statistical range included in the statistical request, and return the statistical results to the initiator of the statistical request.

6. The method according to claim 1, wherein All ownership entities registered in the management server form a transfer network including multiple levels. In the transfer network, any adjacent two levels have at least one upper-level entity in the upper level and at least one lower-level entity in the lower level. Among them, The tire pressure sensors belonging to any lower-level entity are sold to the any lower-level entity by at least one upper-level entity and / or at least one other lower-level entity. Any ownership entity has the management right to the sensor-related data of the tire pressure sensor transferred to itself or transferred by itself to other ownership entities.

7. The method according to claim 6, wherein It further includes: Receive a sensor purchase request initiated by a first ownership entity; Generate a sales order according to the sensor purchase request and issue it to the ownership entity specified in the sensor purchase request or the ownership entity pre-associated with the first ownership entity; and, maintain the sales data of the tire pressure sensors sold by the ownership entity according to the sales order as part of the data related to the transfer of the tire pressure sensor; Or, Forward the sensor purchase request to the sales server pre-associated with the management server, so that the sales server generates a sales order according to the sensor purchase request and issues it to the ownership entity specified in the sensor purchase request or the ownership entity pre-associated with the first ownership entity, and, receive and maintain the sales data of the tire pressure sensors sold by the ownership entity according to the sales order as the flow Part of the relevant data; Wherein, the level of the ownership entity in the transfer network is not lower than the level of the first ownership entity in the transfer network.

8. The method according to claim 6, wherein It further includes: Receive a data query request including data query conditions initiated by a second ownership entity; Query target data that meets the data query conditions from the sensor-related data over which the second ownership entity has management authority, and return the target data to the second ownership entity.

9. The method according to claim 8, wherein The data query request is initiated by any member within the second ownership entity. Querying target data that meets the data query conditions from the sensor-related data over which the second ownership entity has management authority includes: Determine candidate data over which the any member has query authority from the sensor-related data over which the second ownership entity has management authority according to the membership of the any member; Query target data that meets the data query conditions from the candidate data.

10. The method according to claim 9, wherein The organizational structure of the second ownership entity includes multiple levels. For the sensor-related data over which the second ownership entity has management authority, at least some members within the second ownership entity have query authority for this part of the sensor-related data. Among them, The level of query authority of any member is positively correlated with the level of the member in the multiple levels.

11. The method according to claim 1, wherein The activation event is completed by the cooperation of the activation terminal, the electronic device where the activation client is located, the target vehicle, and any tire pressure sensor.

12. The method according to any one of claims 1 to 11, characterized in that Each ownership entity to which any tire pressure sensor belongs in sequence from production completion to activation includes one of the following: Manufacturer, agent, and repair shop; Manufacturer, independent chain store, and repair shop; Manufacturer, independent chain store, and individual user.

13. The method according to any one of claims 1 to 11, characterized in that The data related to the transfer includes at least one of the following: the factory information of any tire pressure sensor, the sales order of any tire pressure sensor, the logistics information of any tire pressure sensor, the payment information of any tire pressure sensor, the identity information of the ownership entity; The activation-related data includes at least one of the following: activation time, communication parameters written to any one of the tire pressure sensors during activation, identity information of the user performing the activation operation, feature information of the target vehicle, and owner information of the target vehicle.

14. A management system for sensor-related data, characterized in that, The system includes a management server, and the management server is configured to: Obtain the transfer-related data of any one of the tire pressure sensors, where the transfer-related data is used to record the transfer process of any one of the tire pressure sensors among various ownership entities from production completion to before activation; Receive the activation-related data of any one of the tire pressure sensors uploaded by an activation client, where the activation-related data is generated by an activation event of any one of the tire pressure sensors, and the activation event is used to activate any one of the tire pressure sensors installed on a target tire of a target vehicle. After activation, any one of the tire pressure sensors is used to submit the tire status data of the target tire collected to the target vehicle; Maintain the sensor-related data of any one of the tire pressure sensors at least indexed by the sensor identifier of any one of the tire pressure sensors, where the sensor-related data includes the transfer-related data and the activation-related data.

15. A management device for sensor-related data, characterized in that, Applied to the management server, it includes: A data acquisition unit configured to obtain the transfer-related data of any one of the tire pressure sensors, where the transfer-related data is used to record the transfer process of any one of the tire pressure sensors among various ownership entities from production completion to before activation; A data reception unit configured to receive the activation-related data of any one of the tire pressure sensors uploaded by an activation client, where the activation-related data is generated by an activation event of any one of the tire pressure sensors, and the activation event is used to activate any one of the tire pressure sensors installed on a target tire of a target vehicle. After activation, Any one of the tire pressure sensors is used to submit the tire status data of the target tire collected to the target vehicle; A data maintenance unit configured to maintain the sensor-related data of any one of the tire pressure sensors at least indexed by the sensor identifier of any one of the tire pressure sensors, where the sensor-related data includes the transfer-related data and the activation-related data.

16. An electronic device, characterized in that, It includes: A processor; A memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the management method of the sensor-related data as described in any one of claims 1 to 13.

17. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the management server, the management server is enabled to execute the management method of the sensor-related data as described in any one of claims 1 to 13.

Images