CN117544916A

CN117544916A - Management method, device and system for sensor related data

Info

Publication number: CN117544916A
Application number: CN202410027146.9A
Authority: CN
Inventors: 张健儿; 余明光; 丁海军; 谢雪玲; 华利平; 吕承奇; 兰恩进; 谭俊杰; 葛鹏飞
Original assignee: Hamaton Automotive Technology Co ltd
Current assignee: Hamaton Automotive Technology Co ltd
Priority date: 2024-01-08
Filing date: 2024-01-08
Publication date: 2024-02-09
Anticipated expiration: 2044-01-08
Also published as: CN117544916B

Abstract

The application relates to a method, a device and a system for managing sensor related data. The method is applied to the management server and comprises the following steps: acquiring circulation related data of any tire pressure sensor, wherein the data is used for recording the circulation process of the sensor between each ownership main body from the completion of production to the activation; receiving activation related data generated by an activation event uploaded by an activation client, the data being used to activate the sensor mounted on a target tire of a target vehicle, the sensor being used to submit collected tire condition data to the target vehicle after activation is completed; sensor-related data for the sensor is maintained with the sensor identification as an index, including the flow-related data and the activation-related data. The scheme can finely manage the related data of the sensor and realize the tracking of the whole life cycle of the tire pressure sensor.

Description

Management method, device and system for sensor related data

Technical Field

The present disclosure relates to the field of big data, and in particular, to a method, an apparatus, and a system for managing sensor related data.

Background

TPMS (Tire Pressure Monitor System) tire pressure monitoring system is called fully, and TPMS's effect is in the automobile driving in-process to tire pressure carries out real-time automatic monitoring to leak gas and low pressure warning to the tire, in order to ensure driving safety. The TPMS mainly comprises a tire pressure sensor (or tire pressure sensor, TPMS sensor), an MCU (Microcontroller Unit, micro control unit), a radio frequency module and an antenna.

The tire pressure sensor at the present stage is usually a wireless sensor, that is, after the tire pressure sensor collects related signals of parameters such as tire pressure, the related signals are encoded and modulated into radio frequency signals, and the radio frequency signals are transmitted through an antenna, so that a receiving device of a vehicle machine system receives the radio frequency signals and decodes the radio frequency signals to obtain parameter values collected by the tire pressure sensor. After replacing a tire or a tire pressure sensor mounted thereon, it is necessary to activate a newly mounted tire pressure sensor so that it can communicate smoothly with a vehicle-machine system.

In the related art, a user may acquire a brand new tire pressure sensor through various circulation channels (e.g., purchased through sales channels) and then install it on a tire of a vehicle and activate it to ensure its normal operation. The steps of the process are independent of each other and high participation of related personnel is needed, the data of each step are mutually split, the management mode is rough, the efficient management and utilization of related data are not facilitated, and certain potential safety hazards of the data exist.

Disclosure of Invention

The application provides a management method, a management device, an electronic device and a storage medium of sensor related data, so as to at least solve the technical problems in the related technology. The technical scheme of the application is as follows:

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

acquiring circulation related data of any tire pressure sensor, wherein the circulation related data is used for recording circulation processes of the tire pressure sensor between ownership main bodies before production and activation;

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 the any tire pressure sensor, the activation event is used for activating any tire pressure sensor installed on a target tire of a target vehicle, and after activation is completed, the any tire pressure sensor is used for submitting collected tire state data of the target tire to the target vehicle;

and maintaining sensor related data of any one of the tire pressure sensors at least by taking a sensor identification of the any one of the tire pressure sensors as an index, wherein the sensor related data comprises the circulation related data and the activation related data.

According to a second aspect of embodiments of the present application, a management system for sensor related data is provided, where the system includes a management server, where the management server is configured to:

According to a third aspect of embodiments of the present application, a management device for sensor related data is provided, and the management device is applied to a management server, and includes:

a data acquisition unit configured to acquire circulation related data of any one of the tire pressure sensors, the circulation related data being used for recording circulation processes of the any one of the tire pressure sensors between the ownership subjects from production completion to activation;

A data receiving unit configured to receive activation related data of the any one of the tire pressure sensors uploaded by an activation client, wherein the activation related data is generated by an activation event of the any one of the tire pressure sensors, the activation event being used for activating the any one of the tire pressure sensors mounted on a target tire of a target vehicle, and the any one of the tire pressure sensors being used for submitting collected tire state data of the target tire to the target vehicle after the activation is completed;

and a data maintenance unit configured to maintain sensor-related data of the any one of the tire pressure sensors including the circulation-related data and the activation-related data with at least a sensor identification of the any one of the tire pressure sensors as an index.

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

a processor; a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the method for managing sensor related data according to any of the embodiments of the first aspect.

According to a fifth aspect of embodiments of the present application, a storage medium is provided, where instructions in the storage medium, when executed by a processor of a management server, enable the management server to perform the method for managing sensor-related data according to any one of the embodiments of the first aspect.

The technical scheme provided by the embodiment of the application at least brings the following beneficial effects:

as can be seen from the foregoing embodiments, the management server of the present disclosure obtains, on one hand, circulation related data generated in a circulation process by any tire pressure sensor, and on the other hand, receives, on the other hand, activation related data generated in an activation process by the sensor uploaded by an activation client, and further uses the circulation related data and the activation related data as sensor related data of the sensor, and maintains the sensor related data and the sensor identifier as an index. Through the mode, the management server can uniformly maintain all data related to each process from production completion to activation completion (at the moment, the tire pressure sensor can normally work) of the tire pressure sensor, so that not only is the full-flow efficient management of related data related to the full life cycle of the sensor (from production to use) realized, the tracking of the full life cycle of the sensor is facilitated, but also potential safety hazards such as data loss and confusion can be avoided to a certain extent through uniform refined management.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application and do not constitute an undue limitation on the application.

FIG. 1 is a schematic diagram of a management system for sensor-related data, shown in accordance with an embodiment of the present application;

FIG. 2 is a schematic diagram of a circulation network of tire pressure sensors, shown according to an embodiment of the present application;

FIG. 3 is a flow chart illustrating a method of managing sensor related data according to an embodiment of the present application;

FIG. 4 is a block diagram of an electronic device, shown in accordance with an embodiment of the present application;

fig. 5 is a schematic block diagram of a management device for sensor-related data according to an embodiment of the present application.

Detailed Description

In order to enable those skilled 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.

It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

In order to solve the foregoing technical problems in the related art, the present application proposes a management system for sensor related data, and a management method for sensor related data implemented by a management server in the system. The following detailed description refers to the accompanying drawings.

The application proposes a management system (hereinafter referred to as management system) of sensor related data, the system includes a management server, the management server is used for:

The present solution relates only to the management of data related to "tyre pressure sensors" and not to other types of sensors. For brevity, therefore, the following section describes "tire pressure sensor" simply referred to as "sensor", and "any tire pressure sensor" simply referred to as "any sensor" or "the sensor", etc., and this is described here.

As shown in fig. 1, the management system 10 includes a management server running in the management server 11, and may further include an activation client running in the mobile phone 14, and the management system 10 will be described below by taking the foregoing management server and the activation client as examples. The management server in the management system 10 may integrate a circulation function of the tire pressure sensor; alternatively, the management system 10 may also include a circulation server (integrated with the circulation function of the tire pressure sensor) running in the circulation server 12 for circulating the tire pressure sensor between the ownership principals in cooperation with the terminals in the system. The circulation function of the tire pressure sensor may specifically include sales (involving ownership transfer of funds), goods transfer (not involving ownership transfer of funds), warehouse, logistics, etc., which are not described herein. Any tire pressure sensor produced by the sensor manufacturer may be streamed to the user via the network for installation by the user on a tire of the vehicle (e.g., on a new tire being replaced, or for replacement of a faulty sensor in a worn tire, etc.). The user may be a clerk of a vehicle repair shop or an individual user (e.g. a car owner), etc.

In the process of transferring any tire pressure sensor, the tire pressure sensor is transferred to any body such as a natural person, organization or organization (e.g. the body purchases the sensor), and the body has ownership of the sensor, and the body becomes the corresponding ownership body of the sensor (i.e. the body having ownership of the sensor). It can be seen that the complete circulation of the tire pressure sensor from the manufacturer to the user may be through multiple ownership entities such as manufacturers, agents (or dealers), independent chain stores, service stores (e.g., individual service stores, mobile service stores, 4S stores providing vehicle service, etc.), individual users, etc. The agent may include multiple levels, such as a national agent selling sensors to a next level provincial agent, a provincial agent selling sensors to a next level municipal agent, etc. The independent chain stores can be physical stores, online stores and the like, and the online stores can be established based on a general e-commerce platform or based on the management server and the circulation network.

Each ownership subject possibly involved in the circulation process of the tire pressure sensor can be registered in advance at the management server. For example, a management client may be run on a cell phone 13 used by an operator of an agent, and the identity of the agent's principal (i.e., account, infra) may be registered at the management server through the client. As another example, a management client may be run on a cell phone 15 used by an operator of a repair shop and the identity of the principal of the repair shop is registered at the management server through the client. For another example, a management client may also be run on the handset 14 used by an individual user and the identity of the user's own principal is registered at the management server through the client. In addition, the relevant personnel (management personnel, common staff and the like) of the ownership subject of the agency types such as the agent, the independent chain store, the maintenance store and the like can register the personal identity of the person and bind the personal identity with the subject identity of the ownership subject to which the person belongs so as to realize the attribution of the personal identity to the identity of the agency.

In an embodiment, all ownership principals registered at the management server may form a circulation network including a plurality of levels, wherein a level above any two adjacent levels in the circulation network includes at least one upper level principal and a level below the level includes at least one lower level principal. Wherein the sensor belonging to any subordinate body flows from at least one superior body and/or at least one other subordinate body to the any subordinate body (such as sold to the subordinate body), and any ownership body has management authority for the sensor related data of each sensor which flows to itself or flows from itself to other ownership bodies.

Wherein the circulation network may include a sales network of sensors, at which time each participant of the management system may realize sales of the sensors based on the sales network, i.e., circulate the sensors between the multi-level seller and the purchaser. For example, any manufacturer has management authority over sensor-related data generated in the full life cycle of each sensor that is produced and sold by itself, any agent has management authority over sensor-related data of all sensors purchased by itself (including sold portions and/or unsold portions), and any person user has management authority over sensor-related data of all tire pressure sensors purchased by itself (including activated portions and/or unactivated portions). It will be appreciated that in the streaming network described above, which includes multiple levels, any ownership entity of any level may implement full flow tracking of the portion of the sensor because the ownership entity has administrative rights to sensor related data of the sensor purchased or sold by itself. And because of the circulation network of the multiple levels, the upper-level main body can accurately track each sensor corresponding to the lower-level main body.

As shown in fig. 2, a circulation network comprising three tiers is illustrated, wherein the ownership agents shown include manufacturers (i.e., manufacturer 1 and manufacturer 2) at a first tier, agents (i.e., agent 1 and agent 2) and independent chain stores (i.e., independent chain store 1) at a second tier, maintenance stores (i.e., store 1, store 2 and store 3) and individual users (i.e., individual user 1) at a third tier. The manufacturer 1 and the manufacturer 2 may belong to the same brand party (i.e. produce the same brand of sensor) or different brand parties (i.e. produce different brands of sensor), and of course, any manufacturer may produce only one brand of sensor, or may also produce multiple brands of sensor (e.g. substitution pattern), which is not limited in this embodiment of the present application. In addition, fig. 2 also shows maintenance personnel in the repair store (i.e., maintenance person 1 in store 1, maintenance persons 2 and 3 in store 2, maintenance person 4 in store 3, etc.). As described above, each of the above-mentioned ownership principals and related personnel may complete identity registration at the management server in advance. The arrow direction in fig. 2 indicates the direction of flow of the sensors, i.e., the arrow pointing from any ownership body a to another ownership body B is used to indicate the flow of at least one tire pressure sensor from a to B. The sensor circulation process may include a sales process, such as the agent 1 selling a batch of sensors to store 1, the independent chain store 1 selling a batch of sensors to store 3, etc.; the transfer process may also include a non-sales transfer process, such as where agents 1 and 2 are both brokered selling the same brand of sensor, if the current inventory of agent 1 is insufficient, a batch of this brand of sensor may be temporarily transferred from agent 2, this transfer process may be completed by the brand party of the brand participating in the negotiation, or by agents 1 and 2 themselves, and the transfer process may not involve funds transfer (i.e., agent 2 may not pay for the payment of the money to agent 1, etc.). Of course, the specific logic of sales and goods transferring can be reasonably set according to the actual situation, which is not limited in the application.

In one embodiment, each ownership entity to which any tire pressure sensor sequentially belongs from completion of production to activation may include a manufacturer, an agent, and a repair shop, such as manufacturer 1 selling at least one sensor to agent 1 (i.e., agent 1 purchases at least one sensor from manufacturer 1, the same applies below), agent 1 selling at least one sensor to store 1. Alternatively, the manufacturer, the independent chain store and the maintenance store may be included, for example, the manufacturer 1 sells at least one sensor to the independent chain store 1, and the independent chain store 1 sells at least one sensor to the store 3. Still alternatively, the manufacturer, the independent chain store, and the individual user may be included, for example, the manufacturer 1 sells at least one sensor to the independent chain store 1, the independent chain store 1 sells at least one sensor to the individual user 1, and so on. Of course, among the ownership principals belonging to any of the above sensors in turn from the completion of production to the activation, there may be a plurality of ownership principals at the same level, for example, agent 1 and agent 2 respectively facing the counterpart flow sensor, agent 2 and independent chain store 1 respectively facing the counterpart flow sensor, store 1 and store 2 respectively facing the counterpart flow sensor, and the like.

It should be noted that, any of the tire pressure sensors described herein is "production completed" to indicate that the production phase and testing phase before shipment of the sensor have been completed, after which the sensor may be circulated (e.g., stored, sold, transported, etc.), installed, and activated; the "pre-activation" of any one of the tire pressure sensors indicates that the sensor has been circulated to its user (i.e., the sensor has been owned by its user), after which the user may activate the sensor (at which time the sensor may not have been installed or has been installed).

The operations involved in the above circulation process may be completed by related personnel through a management client, for example, a purchasing personnel of the agent 1 may initiate a sensor purchase request to the management server through the management client running in the mobile phone 13 according to the purchasing requirement (the management server may treat the request as a request initiated by the agent 1), and the management server may generate a sales order in response to the request and issue the sales order to a corresponding ownership entity (such as the manufacturer 1 or the agent 2), so that the latter sells a corresponding sensor to the agent 1 according to the order. Alternatively, the purchasing personnel of store 1 may initiate a sensor purchase request to the management server via the management client running in the mobile phone 15 according to the purchasing requirement, and the management server may treat the request as a request initiated by store 1, in response to the request, generate a sales order and issue the sales order to the corresponding ownership entity (e.g. agent 1), so that the latter sells the corresponding sensor to store 1 according to the order. Still alternatively, the individual user 1 may initiate a sensor purchase request to the management server via a management client running in the cell phone 14 according to the purchase demand, and the management server may generate a sales order in response to the request and issue the sales order to a corresponding ownership entity (e.g., the independent chain store 1 or the store 3) so that the latter sells the corresponding tire pressure sensor to the individual user 1 according to the order.

Corresponding circulation related data can be generated in the process of circulating the tire pressure sensor by depending on the circulation network, for example, the circulation related data of any tire pressure sensor can comprise at least one of the following: factory information of any one of the tire pressure sensors, sales orders (including information such as purchase time, model number, quantity, price, total amount and the like) of any one of the tire pressure sensors, logistics information (including information such as delivery places, receiving places, logistics schedules and the like) of any one of the tire pressure sensors, payment information (account information of payers and payee, transfer time and the like) of any one of the tire pressure sensors, identity information of ownership subjects and the like. Of course, the specific content of the circulation related data may also be set according to the actual situation, which is not limited by the embodiment of the present application. It will be appreciated that each sensor circulated through the circulation network may generate circulation related data as described above. The circulation related data of each sensor can be maintained by the management server and/or the circulation server, wherein any maintenance party can store the circulation related data maintained by the maintenance party in a persistent storage space such as a local disk of the maintenance party or an associated external database thereof. Correspondingly, the management server can acquire the circulation related data of any sensor from the circulation related data maintained by the management server or the circulation server.

Additionally, the management system 10 may be maintained by the manufacturer of the sensor for managing sensor-related data generated by the sensor manufactured and sold by the manufacturer during its full life cycle; alternatively, management system 10 may be maintained by a branding party of a sensor for managing sensor-related data or the like generated by the brand of sensor that the branding party delegates to a manufacturer to produce and sell during its full lifecycle.

In the above manner, the maintenance store and the individual user can purchase the required tire pressure sensor, so that related personnel (such as the maintenance worker 1 or the individual user 1) can program, learn and match the tire pressure sensor through the operation activation client to complete the activation process of the sensor. The activation event is completed by the mutual cooperation of an activation terminal, electronic equipment where the activation client is located, the target vehicle and any tire pressure sensor. As shown in fig. 1, the associated person may operate an activation client running in the handset 14 to cause the handset 14 to interact with the activation terminal 21, the tire pressure sensor 22 (i.e., any sensor purchased previously by a service shop or individual user), and the target vehicle 23 to complete the activation process for that sensor (i.e., to interact to complete the activation event for that sensor). After the sensor is mounted on the target tire of the target vehicle 23 and activation is completed, the sensor may start to operate normally, i.e., the tire state data of the target tire collected by itself may be submitted to the target vehicle 23 by means of wireless communication. The mobile phone 14, the activation terminal 21, the tire pressure sensor 22 and the target vehicle 23 together form an activation system 20 for the tire pressure sensor 22.

It should be noted that, the management client and the activation client described in the present application may be the same client in practice, that is, the client may integrate a data management function and a sensor activation function; of course, a sensor circulation function may be integrated so that a user purchases or sells a sensor or the like.

In the activation system 20, the tire pressure sensor 22 may communicate with the target vehicle 23 by way of transmitting a wireless radio frequency signal to transmit status-related data of the target tire thereto. In addition, the mobile phone 14 may establish a first wireless connection (such as NFC connection, bluetooth connection, etc.) with the tire pressure sensor 22, the mobile phone 14 may establish a second wireless connection (such as bluetooth connection, wifi connection, etc.) with the activation terminal 21, and the activation terminal 21 may establish a third wireless connection (such as NFC connection, wireless radio frequency connection, etc.) with the tire pressure sensor 22. Wherein the target vehicle 23 itself is equipped with a communication antenna so as to achieve the wireless connection with the tire pressure sensor. It can be seen that any two parties in the system, namely the mobile phone 14, the activation terminal 21 and the tire pressure sensor 22, can interact through a wireless connection, and the wireless connection established between the two parties is actually an end-to-end connection between the two parties. Because the interaction between the devices in the activation system can be realized based on the wireless connection, the system can realize the expected function of matching the tire pressure sensor without a special connecting wire, thereby simplifying the system structure and contributing to the cost reduction. In addition, the activation terminal 21 may establish a wired connection with the target vehicle 23 through an OBD (On-Board Diagnostics, on-board automatic diagnostic system) interface.

When the NFC connection or the wireless radio frequency connection is established between the activation terminal 21 (or the mobile phone 14) and the tire pressure sensor 22, the two may implement millisecond-level device connection (or pairing) through a wireless wake-up signal, and the awakened device (i.e. the tire pressure sensor 22) is essentially equivalent to a passive device, so that in this connection process, a user does not need to manually implement "pairing" and "connection confirmation" operations similar to bluetooth or Wifi technology, thereby facilitating quick connection and information interaction between devices. However, it should be noted that, although the above-mentioned establishment process of the NFC connection or the wireless radio frequency connection is extremely fast and is generally completed together with the data transmission process, the above-mentioned connection should still be regarded as a wireless connection, that is, the wireless connection (that is, the above-mentioned third wireless connection) is established between the activation terminal 21 and the tire pressure sensor 22.

The following briefly describes the programming and learning phases involved in the activation process of the tire pressure sensor 22:

programming: the handset 14 determines communication parameters of the target vehicle 23, which may include connection parameters and submit configuration parameters. And an activation client (via a first wireless connection) writing the communication parameters to the tire pressure sensor 22 itself, or an activation client (via a second wireless connection) instructs the activation terminal 21 (via a third wireless connection) to write the communication parameters to the tire pressure sensor 22. The process of writing the communication parameters into the tire pressure sensor 22 is a process of programming the sensor. The programmed tire pressure sensor 22 can be mounted on a target tire (which may be any tire of the vehicle) of the target vehicle 23; of course, the above programming may also be performed after the installation is completed, which is not limited in this application.

Learning phase: the mobile phone 14 reads its sensor identification from the tire pressure sensor 22 and transmits to the activation terminal 21, or the activation terminal 21 itself reads its sensor identification from the tire pressure sensor 22. The activation terminal 21 then sends this sensor identification to the target vehicle 23 under the direction of the mobile phone 14 after establishing a connection with said target vehicle 23 via the on-board diagnostic system OBD interface. The user may also specify a target location of the target tire in the target vehicle 23 in the cell phone 14 and send corresponding location information to the target vehicle 23 by the activation terminal 21. In this way, the target vehicle 23 can learn the sensor identification (or the position information as well) of the tire pressure sensor 22.

After the programming and learning phases described above 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 may cooperate with the target vehicle 23 to begin normal operation, i.e., for itself to collect tire condition data, the sensor may send condition-related data including a target sensor identification and the tire condition data to the target vehicle 23 in accordance with the locally written target communication parameters for receipt and identification by the target vehicle. Wherein the activation related data of any one of the tire pressure sensors may include at least one of: the activation time, the communication parameters (namely the connection parameters and the connection parameters) written in any tire pressure sensor during activation, the identity information of an activation operation user (such as the maintainer 1 or the personal user 1, etc.), the characteristic information of the target vehicle and the owner information of the target vehicle.

It should be noted that any one of the management server and the circulation server in the management system 10 may be a physical server including an independent host, or may also be a virtual server, a cloud server, or the like, which is carried by a host cluster, which is not limited in this embodiment of the present application. The mobile phones 31 to 15 are only one type of electronic device that can be used by related personnel, and in fact, a user can use any type of electronic device to run the aforementioned management client, and use any type of electronic device with a wireless connection function to run the aforementioned activation client. Illustratively, the electronic device used by the user may be: tablet devices, notebook computers, palm top computers (PDAs, personal Digital Assistants), wearable devices (e.g., smart glasses, smart watches, etc.), VR (Virtual Reality) devices, AR (Augmented Reality ) devices, etc., as embodiments of the present application are not limited thereto.

In addition, any one of the management client and the activation client may be a native APP (Application), a Web Application (or Web page) implemented by a browser, an applet (Mini program) implemented by another Application, or the like. Wherein the APP typically requires pre-installation and start-up operations; while the Web applications and applets may be online "clients" built using HTML5 technology, such client programs typically do not require specific "install" steps to run, but rather are integrated into a browser or other application to run as separate pages or functional components (or plug-ins). The user can implement corresponding operation in the man-machine interface so as to operate the mobile phone to participate in realizing the circulation function and/or the activation function aiming at the sensor. Taking the mobile phone 14 as an example, since the mobile phone can display a man-machine interface for user operation, the activation terminal 21 does not need to be equipped with display components such as a screen, and only needs to execute corresponding response processing under the instruction (or control) of the mobile phone 14, thereby simplifying the hardware structure and software logic of the terminal and being beneficial to realizing the miniaturization of the terminal.

Corresponding to the management system, the application also provides a management method of the sensor related data, which is applied to the management server (in the management system). As shown in FIG. 3, the method may include the following steps 302-306.

Step 302, obtaining circulation related data of any tire pressure sensor, wherein the circulation related data is used for recording circulation process of the tire pressure sensor between ownership subjects before production completion and activation.

Corresponding circulation related data are generated in the process of circulating the tire pressure sensors through a circulation network, wherein the circulation related data of any tire pressure sensor are used for recording the circulation process of the sensors between ownership subjects before the completion of production and activation; in other words, the flow related data of any one of the tire pressure sensors is generated during the flow process of that sensor for recording (or characterizing) the flow process. Based on the above, the management server can acquire the circulation related data of each circulated tire pressure sensor. For any sensor, the circulation related data may be obtained in advance before the activation related data of the sensor is obtained (i.e. step 302 is performed before step 304 is performed), or the circulation related data may be obtained after the activation related data of the sensor is obtained (i.e. step 304 is performed before step 302 is performed), which is not limited in the execution sequence of step 302 and step 304 in the embodiment of the present application.

In an embodiment, the circulation related data of each tire pressure sensor to be circulated may be maintained by the management server, and at this time, the management server may obtain the circulation related data of any tire pressure sensor from the circulation related data maintained by the management server. At this time, the management server maintains the sensor related data, and the obtaining of the circulation related data of any tire pressure sensor may be querying the circulation related data of the sensor from the persistent storage space, and writing the queried data into the own memory space. At this time, the management server acquires the circulation related data maintained by itself, so that the acquisition speed is high, and the efficient acquisition of the data is facilitated.

Or, in the case that the circulation related data of each tire pressure sensor to be circulated is maintained by the circulation server pre-associated with the management server, the management server may acquire the circulation related data of any tire pressure sensor from the circulation server. At this time, the circulation related data is maintained by the circulation server, which is helpful to reduce the data maintenance pressure of the management server, separate the maintenance logic and the management logic of the circulation related data, and is helpful to improve the operation efficiency of the management server and the subsequent management efficiency of the circulation related data.

When the management server obtains the circulation related data of any tire pressure sensor from the circulation server, various modes can be adopted. For example, the circulation related data of any tire pressure sensor (actively) pushed by the circulation server may be received, for example, the circulation server may push the data to the management server in real time after generating the circulation related data of any tire pressure sensor, or may periodically push the circulation related data of each tire pressure sensor generated in a last period of time. The pushing may be implemented based on a message queue, that is, the circulation server is used as a producer of each message in the message queue, and the management server is used as a consumer of the messages, where any message may include circulation related data of at least one sensor. By the method, the management server can asynchronously acquire the circulation related data, and the follow-up processing logic is facilitated to be simplified. For another example, the management server may request and receive the circulation related data of any tire pressure sensor returned by the circulation server. The method requests the circulation related data to the circulation server only when needed, and is helpful for reducing the data sending workload of the circulation server.

In one embodiment, the management server may obtain the circulation related data of any tire pressure sensor in a plurality of ways. For example, the circulation related data of any tire pressure sensor can be obtained according to the sensor identification of the sensor. The data acquisition request sent to the circulation server may only include the sensor identifier of any tire pressure sensor, and at this time, the circulation server may search the circulation related data of the sensor according to the identifier in a targeted manner and return the circulation related data to the management server, so that the management server may acquire the circulation related data of the sensor in a targeted manner. For another example, the management server may obtain the circulation related data of the tire pressure sensors in batches, and query the circulation related data of any tire pressure sensor from the obtained circulation related data according to the sensor identifier. The data acquisition request sent to the circulation server may include relevant information such as a model number, a lot, a production date, etc. of a plurality of sensors (including any one of the tire pressure sensors), and the circulation server may determine circulation related data of each tire pressure sensor conforming to the relevant information and return the circulation related data to the management server, so that the sensors may acquire the circulation related data of each of the tire pressure sensors (including any one of the tire pressure sensors) in batch, thereby further improving the acquisition efficiency of the circulation related data.

As described above, all ownership principals registered at the management server may constitute a circulation network including a plurality of levels, wherein a level immediately preceding any adjacent two levels in the circulation network includes at least one upper level principal and a level immediately succeeding the level includes at least one lower level principal, wherein a sensor belonging to any lower level principal circulates from at least one upper level principal and/or at least one other lower level principal to any lower level principal (e.g., is sold to the lower level principal), and any ownership principal has management authority for sensor-related data of each sensor circulating to itself or circulating from itself to other ownership principal.

In an embodiment, based on the multi-level circulation network, the management server may participate in the circulation process of the sensor (i.e. participate in implementing the circulation sensor). For example, the management server may receive a sensor purchase request initiated by a first ownership entity, where the first ownership entity may be any one of a plurality of ownership entities that complete registration, and the request may specifically be initiated by an electronic device used by a person associated with the first ownership entity through the electronic device. As shown in fig. 2, an employee of the agent 1 may initiate a sensor purchase request through a mobile phone used by the employee, and the management server may consider the received request as being initiated by the agent 1; alternatively, the employee of the independent chain store 1 may initiate a sensor purchase request through a computer used by the employee, and the management server may consider the received sensor purchase request as being initiated by the independent chain store 1.

Further, if the management server integrates the circulation function, the management server may generate a sales order according to the sensor purchase request and issue the sales order (i.e., the sales order) to the ownership entity specified by the sensor purchase request (i.e., the receiver of the sensor purchased this time is specified in the request), or issue the sales order to the ownership entity pre-associated with the first ownership entity (i.e., the pre-associated ownership entity is used as the default receiver of the sensor purchased this time). Wherein the level of ownership subject (receiving the sales order) in the circulation network should be no lower (i.e., equal to or higher) than the level of the first ownership subject in the circulation network, thereby enabling the sales behavior of a lower ownership subject to purchase a sensor with an upper (or peer) ownership subject. The sales order is used for indicating the ownership subject to sell corresponding (number and model) tire pressure sensors to the first ownership subject according to the information recorded in the order so as to meet the sensor purchase requirement of the subject. The related data may relate to logistics information, payment information and the like, and will not be described in detail. Accordingly, the management server may also maintain sales data of the sensor sold by the ownership entity according to the sales order (this data is generated and collected to the management server during the above-mentioned circulation process) as a part of circulation related data of the sensor (i.e. the sensor sold by the ownership entity).

With the foregoing embodiment, if a sensor purchase request initiated by the agent 1 is received, the management server may determine an ownership entity specified by the request, e.g., if the request includes an entity identifier of the vendor 1, the vendor 1 may be determined as the ownership entity specified by the request; in the case where the request includes the principal identification of agent 2, agent 2 may be determined to be the ownership principal specified by the request. Or if the sensor purchase request does not contain any principal identifier, the first ownership principal pre-associated ownership principal may be determined, e.g., the management server may determine, according to the pre-association relationship maintained by the management server, vendor 1 and/or agent 2 as the agent 1 pre-associated ownership principal. Of course, at least one ownership subject of the first ownership subject can be determined according to the above manner, and order information such as a sensing model number, a quantity, a price and the like corresponding to each ownership subject can also be determined. Further, sales orders for each ownership subject may be generated based on the order information and placed to the corresponding ownership subject, respectively.

Or if the management server does not integrate the circulation function, the management server may forward the sensor purchase request to the circulation server pre-associated with the management server (the circulation server integrates the circulation function of the slave sensor), so that the circulation server generates a sales order according to the sensor purchase request and issues the sales order to the ownership subject specified by the request or the ownership subject pre-associated with the first ownership subject. Likewise, the level of ownership subject (receiving the sales order) in the circulation network is no lower than the level of the first ownership subject in the circulation network. The sales order is used for indicating the ownership subject to sell corresponding (number and model) tire pressure sensors to the first ownership subject according to the information recorded in the order so as to meet the sensor purchase requirements of the subject. Further, the management server may receive and maintain sales data of the tire pressure sensor sold by the ownership subject according to the sales order (the data is generated and collected in the circulation process and then sent to the management server for maintenance by the circulation server), as a part of circulation related data of the tire pressure sensor.

By the mode, the management server can acquire circulation related data generated in the complete circulation process from the completion of production to the beginning of installation of any tire pressure sensor.

And step 304, 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 is used for activating any tire pressure sensor installed on a target tire of a target vehicle, and after the activation is completed, the any tire pressure sensor is used for submitting collected tire state data of the target tire to the target vehicle.

In an embodiment, the activation terminal, the electronic device (such as a mobile phone) where the activation client is located, the target vehicle, and the any tire pressure sensor may cooperate with each other to complete an activation event for the sensor, that is, the above parties cooperate with each other to activate the any tire pressure sensor installed on the target tire of the target vehicle, so that the sensor may establish a normal wireless connection (i.e., the first wireless connection) with the target vehicle, and upload, based on the wireless connection, tire state data of the target tire detected by the sensor to the target vehicle. Wherein, any one activation event is successfully completed, which can indicate that the assembly or maintenance of the target vehicle is completed once. Taking maintenance as an example, during the maintenance process (i.e. the activation event is not completed) or after the maintenance is completed (i.e. the activation event is completed), the client may upload corresponding activation related data to the management server, so that the latter caches the data and prepares for subsequent data maintenance.

As shown in fig. 1, if the serviceman 1 designates the model information of the target vehicle in the activation client running on the mobile phone 14, and then the activation client determines the target communication parameter to be written into the tire pressure sensor 22 from the candidate communication parameters stored locally in the mobile phone 14, the activation client may upload the parameter to the management server; or if the activation client requests to acquire the target communication parameters from the management server, the management server may return the parameters to the mobile phone 14 on one hand, and may record the parameters locally on the other hand. If the serviceman 1 designates the model information of the target vehicle and the position information of the target tire (to be repaired) in the target vehicle in the activation client, the activation client may immediately upload the model information and the position information to the management server, or may upload the model information and the position information after the activation event is completed, which is not limited in the embodiment of the present application.

By the mode, the management server can acquire the activation related data generated by the activation event of any tire pressure sensor, namely the activation related data generated in the process of installing the sensor.

At step 306, maintaining sensor-related data of the any one of the tire pressure sensors, including the circulation-related data and the activation-related data, with at least a sensor identification of the any one of the tire pressure sensors as an index.

After the circulation related data and the activation related data of any management server are acquired, the circulation related data and the activation related data can be used as sensor related data of the sensor, and the sensor identification of the sensor is used as an index to maintain the data, so that the association between the circulation related data and the activation related data is established.

It should be noted that, the sensor identifier of any tire pressure sensor described in the present application is global information (or referred to as global identifier) that is used to uniquely characterize the sensor. For example, during the production phase of any tire pressure sensor, a sensor identifier of the sensor may be generated according to a preset rule or algorithm, and the identifier may be written into a local storage space of the sensor (i.e., the identifier is written as default configuration information of the sensor); based on this, in the subsequent learning phase of the activation event for the sensor, the mobile phone or the activation terminal may read the written sensor identifier from the sensor, and then send the identifier to the target vehicle, so as to complete the processing of the learning phase. Alternatively, the sensor identifier of any tire pressure sensor may be generated for the sensor according to a preset rule or algorithm during the circulation or activation process, and the sensor identifier is used as a part of corresponding circulation related data and/or activation related data, so that the data is managed by using the identifier as an index later. Of course, the sensor identifier may also be generated in any other manner, and the embodiment of the present application is not limited to this, but no matter what manner is used for generating, the global uniqueness of any sensor identifier should be ensured, that is, the occurrence of the situation that "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 with the sensor identifier as an index, other data may be used for maintenance, such as manufacturer name, agent name, store name, personal user account, circulation time information, etc. in circulation-related data, or such as sensor brand, sensor model, sensor price, activation time information, etc. in activation-related data. The multiple data are used as indexes to maintain the sensor related data, so that the subsequent management of the sensor related data is facilitated, for example, data statistics (such as counting the activation quantity of a sensor in a store in a period of time or counting the sales quantity of a sensor in an independent chain store in a period of time) can be carried out from the maintenance corresponding to the multiple indexes, and the efficiency and quality of managing the sensor related data in the aspects of storage, inquiry, statistics and the like are further improved.

In an embodiment, the management server may further perform statistical processing on the circulation related data maintained by the management server and maintain a corresponding statistical result, so as to facilitate user query. Of course, the foregoing statistical processing (i.e., pre-statistics, such as periodic statistics, or starting processing when the number of maintained circulation-related data meets a threshold, etc.) may be performed according to a pre-established statistical plan, so that the statistical result may be directly returned to the initiator when the data query request is received. Alternatively, the above-described statistical processing (i.e., temporary statistics) may be performed in response to a received data query request, thereby reducing the workload of unnecessary statistical processing.

Specifically, for the target dimension corresponding to any one of the circulation related data and/or the activation related data, the management server may (according to a preset statistics rule) count related indexes of each tire pressure sensor (including any one of the tire pressure sensors) in the target dimension, and maintain the statistics result as sensor related data of each tire pressure sensor respectively (of course, the original data of the statistics result may be saved only in one portion, and a mapping relationship between the statistics result and each tire pressure sensor is established). Taking the circulation network shown in fig. 1 as an example, for the number of sensor sales (the target dimension) corresponding to the identity information (the circulation related data) of the agent 1, the management server may count the number of tire pressure sensors (i.e. related indexes) sold by the agent 1 in the last month (or the current month in which the current moment is located), and maintain the counted result as the sensor related data of the tire pressure sensors. For another example, for the number of sensor activations (this target dimension) corresponding to the identity information (this activation-related data) of the user performing the activation operation in the store 2, the management server may count and maintain the number of tire pressure sensors (i.e., related indicators) that the serviceman 2 has activated in the last week (or the current week in which the current time is located), which may be used to characterize the related workload (i.e., how many tire pressure sensors have been activated) of the serviceman 2 that has completed the activation event in the last week. In addition, the statistical result may be maintained as sensor-related data of the portion of the tire pressure sensor. Of course, other relevant indexes can be counted according to actual needs, and details are not repeated.

Or, in response to a statistics request initiated for the circulation related data and/or the target dimension corresponding to the activation related data, the management server may count related indexes of each tire pressure sensor in the target dimension according to a statistics range included in the statistics request, and return a statistics result to an initiator of the statistics request.

Further, in view of the fact that the management server maintains the sensor related data (including the circulation related data and the activation related data, and possibly including the statistics result) having the management authority of each ownership subject, any ownership subject can query the data for the user to view. Correspondingly, the management server side can receive a data query request containing data query conditions initiated by a second ownership body, then query target data meeting the data query conditions from sensor related data of which the second ownership body has management rights, and return the target data to the second ownership body. By the method, the second ownership body can inquire target data meeting data inquiry conditions from the sensor identification with the management authority, so that the data inquiry requirement of the second ownership body is met.

The second ownership body may be any ownership body registered at the management server, similar to the first ownership body, so that the first ownership body and the second ownership body may be the same ownership body or different ownership bodies, which is not limited in the embodiment of the present application.

For a second ownership entity that has a data query requirement, it can determine a corresponding data query condition according to the requirement and initiate a data query request containing the condition. The data query condition is used for specifying which sensor related data of which tire pressure sensors should be queried to the management server. For example, in the first data query request initiated by vendor 1, the data query conditions may include: the total number of tire pressure sensors shipped (i.e., sold) in the last half of the year (i.e., 1-6 months) and having a model number xxx; in this regard, the management server may return the total to the second ownership body after the query is completed. In the second data query request initiated by the agent 2, the data query condition may include: the total number of tire pressure sensors that have been activated out of all tire pressure sensors purchased (purchased) from manufacturer 1 in the 5 th month of the present year; in this regard, the management server may return the total to the second ownership body after the query is completed. In the third data query request initiated by the store 2, the data query conditions may include: the total number of tire pressure sensors with the model yyy which are activated from the maintenance worker 3 in the last month, and the sensor identification of each sensor; in this regard, the management server may return the total number and the sensor identification list of each tire pressure sensor to the second ownership subject after the query is completed.

In addition, if the queried tire pressure sensor is circulated based on the circulation network including a plurality of levels, any one of the high-level ownership subjects has the tire pressure sensor corresponding to the sensor related data of the management authority, namely, the subject circulates to at least one ownership subject of the next level. If the manufacturer 1 sells some tire pressure sensors to the agent 1, the manufacturer 1 can inquire the sensor related data of the tire pressure sensors; after agent 1 sells certain tire pressure sensors to store 2, agent 1 may query sensor-related data for such tire pressure sensors. Of course, the next-level ownership entity may regard the sensor-related data that own owns the management authority as private data of itself, and for some reasons is not willing to be known by the ownership entity of the next-level ownership entity, where the next-level ownership entity may set the query authority for the sensor-related data that own the management authority, e.g., only allow itself (i.e., its organization members) to query the data, and reject the previous-level (or multi-level) ownership entity to query the data. If store 1 can set authority for each tire pressure sensor that is activated by serviceman 1, only the personnel of store 1 are allowed to inquire, and inquiry of agent 1 and manufacturer 1 is not allowed. Of course, the query authority can also be set from multiple dimensions such as data types, time ranges, sensor models, sensor prices and the like, so that the refined management of the query authority and the disclosure range of the related data of the sensor is realized, and the specific setting mode is not limited.

It should be noted that, the data query request may actually be initiated by a member in the second ownership body, for example, a circulation person of the manufacturer 1 may initiate the first data query request, a manager of the agent 2 may initiate the second data query request, a serviceman 3 of the store 2 may initiate the third data query request, and so on, which will not be described in detail. In addition, a management client can be operated in the electronic equipment used by the related personnel, so that the related personnel can initiate the data query request through the management client.

In an embodiment, the data query request may be initiated by any member in the second ownership principal (may be a small group or a natural person in the principal), at this time, the management server may determine candidate data of the query authority possessed by any member from the sensor-related data of the management authority possessed by the second ownership principal according to the membership of any member, and then determine target data satisfying the data query condition from the candidate data. By the mode, the second ownership main body can conduct finer-granularity query authority management and control on the sensor related data with the management authority (the accuracy is to small groups in the main body and even natural people), further fine management and control on the query authority and the data disclosure range is achieved, and data security is improved.

The organization structure of the second ownership body may include a plurality of levels, for the second ownership body to possess sensor related data of management authority, at least some members in the second ownership body may possess query authority for the sensor related data, where the level of the query authority possessed by any member is positively correlated with the level of the level in which the member is located in the plurality of levels. For example, the levels of the staff of the store 1 are, in order from high to low: store long, group leader, maintenance man, at this time, the data inquiry right of store long is higher than the group leader, the data inquiry right of group leader is higher than the maintenance man to the circulation related data of all tire pressure sensors designed in store 1. If the store length can inquire the statistics of all tire pressure sensors activated by all maintenance workers of the store; the group leader can check the statistics results of all the tire pressure sensors activated by each serviceman in the group, and the personal statistics results of each serviceman and/or the detailed circulation related data of the tire pressure sensors; any maintenance worker can check the statistical result of all the tire pressure sensors activated by the maintenance worker and the detailed circulation related data of each tire pressure sensor. By the method, hierarchical management of the circulation related data query authorities can be achieved.

Fig. 4 is a schematic structural diagram of an electronic device shown in the present application. Referring to fig. 4, at the hardware level, the server includes a processor 401, a network interface 402, a memory 403, a nonvolatile memory 404, and an internal bus 405, and may also include hardware required by other services. One or more embodiments of the present application may be implemented in a software-based manner, such as by the processor 401 reading a corresponding computer program from the non-volatile memory 404 into the memory 403 and then running. Of course, in addition to software implementation, one or more embodiments of the present application do not exclude other implementation, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following process flows is not limited to each logic unit, but may also be hardware or a logic device.

Fig. 5 is a block diagram of a management apparatus for sensor-related data. Referring to fig. 5, the device may be applied to the electronic apparatus shown in fig. 4 to implement the technical solution described in the present application. The device is applied to a management server and comprises:

a data acquisition unit 501 configured to acquire circulation related data of any one of the tire pressure sensors for recording circulation processes between the individual ownership subjects from the completion of production to the activation of the any one of the tire pressure sensors;

A data receiving unit 502 configured to receive activation related data of the any one of the tire pressure sensors uploaded by an activation client, wherein the activation related data is generated by an activation event of the any one of the tire pressure sensors, the activation event being used for activating the any one of the tire pressure sensors mounted on a target tire of a target vehicle, and the any one of the tire pressure sensors being used for submitting collected tire state data of the target tire to the target vehicle after the activation is completed;

a data maintenance unit 503 configured to maintain sensor-related data of the any one of the tire pressure sensors including the circulation-related data and the activation-related data with at least a sensor identification of the any one of the tire pressure sensors as an index.

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

acquiring the circulation related data of any tire pressure sensor from the circulation related data of each sensor maintained by the tire pressure sensor; or,

and acquiring circulation related data of any tire pressure sensor from the circulation server pre-associated with the management server.

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

Receiving circulation related data of any tire pressure sensor pushed by the circulation server; or,

and requesting and receiving the circulation related data of any tire pressure sensor returned by the circulation server.

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

acquiring circulation related data of a plurality of tire pressure sensors in batches, and inquiring circulation related data of any tire pressure sensor from the acquired circulation related data according to a sensor identifier; or,

and acquiring circulation related data of any tire pressure sensor according to the sensor identification of the any tire pressure sensor.

Optionally, the method further comprises:

a first statistics unit 504, configured to, for a target dimension corresponding to the circulation related data and/or the activation related data, count related indexes of each tire pressure sensor in the target dimension, and respectively maintain the statistical results as sensor related data of each tire pressure sensor; or,

and the second statistics unit 505 is configured to respond to a statistics request initiated for the circulation related data and/or the target dimension corresponding to the activation related data, count related indexes of each tire pressure sensor in the target dimension according to a statistics range included in the statistics request, and return a statistics result to an initiator of the statistics request.

Optionally, all ownership principals registered at the management server form a circulation network comprising a plurality of levels, wherein an upper level of any two adjacent levels in the circulation network comprises at least one upper level principal and a lower level comprises at least one lower level principal, wherein,

the tire pressure sensor belonging to any subordinate body is sold to the any subordinate body by at least one superior body and/or at least one other subordinate body, and any ownership body has management authority for sensor-related data of the tire pressure sensor which flows to itself or flows from itself to other ownership bodies.

Optionally, the method further comprises:

a purchase request receiving unit 506 configured to receive a sensor purchase request initiated by the first ownership body;

a first order generation unit 507 configured to generate a sales order from the sensor purchase request and issue it to an ownership subject specified by the sensor purchase request or an ownership subject pre-associated with the first ownership subject; and maintaining sales data of the tire pressure sensor sold by the ownership subject according to the sales order as part of circulation related data of the tire pressure sensor; or,

A second order generation unit 508 configured to forward the sensor purchase request to the sales service side pre-associated with the management service side, so that the sales service side generates a sales order according to the sensor purchase request and issues the sales order to an ownership subject specified by the sensor purchase request or an ownership subject pre-associated with the first ownership subject, and receives and maintains sales data of the tire pressure sensor sold by the ownership subject according to the sales order as a part of circulation related data of the tire pressure sensor;

wherein the level of ownership subject in the circulation network is not lower than the level of first ownership subject in the circulation network.

Optionally, the method further comprises:

a query request receiving unit 509 configured to receive a data query request including a data query condition initiated by the second ownership body;

and a query and return unit 510 configured to query target data satisfying the data query condition from among the sensor-related data having the management authority of the second ownership subject, and return the target data to the second ownership subject.

Optionally, the data query request is initiated by any member in the second ownership body, and the data query and return unit 510 is specifically configured to:

according to the membership of any member, determining candidate data of any member having query authority from the sensor related data of the second ownership subject having management authority;

and querying target data meeting the data query condition from the candidate data.

Optionally, the organization structure of the second ownership body comprises a plurality of levels, sensor related data having management rights for the second ownership body, at least some members within the second ownership body having query rights for the portion of sensor related data, wherein,

the query authority possessed by any member is positively correlated with the level of the hierarchy in which the member is located in the plurality of hierarchies.

Optionally, the activation event is completed by the interaction of an activation terminal, an electronic device where the activation client is located, the target vehicle and the any tire pressure sensor.

Optionally, each ownership body to which any tire pressure sensor sequentially belongs from production completion to activation comprises one of the following:

Manufacturers, agencies, and maintenance stores;

manufacturers, independent chain stores, and maintenance stores;

manufacturers, independent chain stores, and individual users.

Optionally, the circulation related data includes at least one of: factory information of any one of the tire pressure sensors, sales orders of any one of the tire pressure sensors, logistics information of any one of the tire pressure sensors, payment information of any one of the tire pressure sensors, and identity information of an ownership subject;

the activation related data includes at least one of: the activation time, the communication parameters written in any tire pressure sensor during activation, the identity information of an activation operation user, the characteristic information of the target vehicle and the owner information of the target vehicle.

In addition, the present application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of the method according to any of the previous embodiments of the present application.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

It is noted that in this application relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing has outlined the detailed description of the method and apparatus provided in the embodiments of the present application, wherein specific examples are provided herein to illustrate the principles and embodiments of the present application, the above examples being provided solely to assist in the understanding of the method and core ideas of the present application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.

Claims

1. The management method of the sensor related data is characterized by being applied to a management server and comprising the following steps:

2. The method of claim 1, wherein the acquiring the flow related data of any one of the tire pressure sensors comprises:

3. The method according to claim 2, wherein the obtaining the circulation related data of the any one of the tire pressure sensors from the circulation server pre-associated with the management server includes:

4. The method of claim 1, wherein the acquiring the flow related data of any one of the tire pressure sensors comprises:

5. The method as recited in claim 1, further comprising:

counting the related indexes of each tire pressure sensor in the target dimension according to the circulation related data and/or the target dimension corresponding to the activation related data, and respectively maintaining the counting result as the sensor related data of each tire pressure sensor; or,

and responding to a statistical request initiated for the circulation related data and/or the target dimension corresponding to the activation related data, counting the related indexes of each tire pressure sensor in the target dimension according to a statistical range contained in the statistical request, and returning a statistical result to an initiator of the statistical request.

6. The method of claim 1, wherein all ownership principals registered at the management server form a streaming network comprising a plurality of tiers, an upper tier of any two adjacent tiers in the streaming network comprising at least one upper level principal and a lower tier comprising at least one lower level principal, wherein,

7. The method as recited in claim 6, further comprising:

receiving a sensor purchase request initiated by a first ownership subject;

generating a sales order according to the sensor purchase request and issuing the sales order to an ownership subject specified by the sensor purchase request or an ownership subject pre-associated with the first ownership subject; and maintaining sales data of the tire pressure sensor sold by the ownership subject according to the sales order as part of circulation related data of the tire pressure sensor; or,

forwarding the sensor purchase request to a sales service side pre-associated with the management service side, so that the sales service side generates a sales order according to the sensor purchase request and issues the sales order to an ownership subject specified by the sensor purchase request or an ownership subject pre-associated with the first ownership subject, and receiving and maintaining sales data of the tire pressure sensor sold by the ownership subject according to the sales order as a part of circulation related data of the tire pressure sensor;

8. The method as recited in claim 6, further comprising:

receiving a data query request containing data query conditions initiated by a second ownership body;

and inquiring target data meeting the data inquiry conditions from the sensor related data of the second ownership subject with the management authority, and returning the target data to the second ownership subject.

9. The method of claim 8, wherein the data query request is initiated by any member within the second ownership principal, wherein querying the sensor-related data having administrative rights from the second ownership principal for target data satisfying the data query condition comprises:

10. The method of claim 9, wherein the organization structure of the second ownership principal comprises a plurality of hierarchies for which at least some members within the second ownership principal possess sensor related data of administrative rights, wherein at least some members within the second ownership principal possess query rights for the portion of sensor related data,

11. The method of claim 1, wherein the activation event is completed by an activation terminal, an electronic device in which the activation client is located, the target vehicle, and any of the tire pressure sensors cooperating with one another.

12. The method according to any one of claims 1 to 11, wherein each ownership body to which any one of the tire pressure sensors sequentially belongs from completion of production to activation, comprises one of the following:

manufacturers, agencies, and maintenance stores;

manufacturers, independent chain stores, and maintenance stores;

manufacturers, independent chain stores, and individual users.

13. The method according to any one of claim 1 to 11, wherein,

the flow related data includes at least one of: factory information of any one of the tire pressure sensors, sales orders of any one of the tire pressure sensors, logistics information of any one of the tire pressure sensors, payment information of any one of the tire pressure sensors, and identity information of an ownership subject;

14. A management system for sensor related data, the system comprising a management server for:

15. A management device for sensor related data, which is applied to a management server, comprising:

16. An electronic device, comprising:

a processor; a memory for storing the processor-executable instructions;

Wherein the processor is configured to execute the instructions to implement the method of managing sensor-related data according to any one of claims 1 to 13.

17. A computer readable storage medium, wherein instructions in the computer readable storage medium, when executed by a processor of a management server, enable the management server to perform the method for managing sensor-related data according to any one of claims 1 to 13.