Label data processing method, RFID middleware and storage medium

Abstract

The embodiment of the invention provides a tag data processing method, RFID middleware and a storage medium. The method comprises the following steps: receiving and caching tag data of a plurality of tags; compressing the label data according to a predetermined compression mode to obtain compressed data; wherein the compression mode is determined according to a data compression level and a label inventory rate; and sending the compressed data. According to the embodiment of the invention, the data processing efficiency is improved, the equipment resource occupancy rate, the data traffic and the bandwidth occupancy of network transmission of middleware at a high inventory rate are greatly reduced, and meanwhile, the mass data processing pressure of an upper platform is reduced. According to the embodiment of the invention, the platform side can receive total label data, and algorithm application development is facilitated. In addition, according to the embodiment of the invention, the packet number and the data compression level are adjusted according to different service requirements, and the method is suitable for service scene requirements with different data volume and time delay sensitivity.

Description

TECHNICAL FIELD

[0001] The present application relates to the mobile communication technical field, and in particular to a tag data processing method, a radio frequency identification (RFID) middleware and a storage medium. BACKGROUND

[0002] The RFID middleware plays an intermediary role between the reader and the application in the RFID system. The RFID middleware provides a set of application program interfaces or data interaction interfaces. The upper application program calls the set of interfaces, connects the RFID reader, reads or modifies the data in the tag, so that the upper application changes or the reader is updated, and the application end does not need to be modified too much to adapt to the change. The traditional RFID middleware is responsible for information interaction with the reader conforming to the Low Level Reader Protocol (LLRP) specification. For the sake of brevity, the RFID middleware is sometimes referred to as the middleware in this paper.

[0003] To meet the deployment requirements of public networks and private networks, the RFID middleware is usually run on the RFID reader side, and the RFID reads the tag data of the tag and sends it to the application end. Because the reading speed of the RFID tag is very fast, reaching hundreds to more than a thousand per second, it is easy to cause high occupation of device resources and network resources. For example, the RFID reader needs to process and send a large amount of tag data, which will cause great pressure on the processing capacity of the RFID reader and occupy a large amount of device processing resources. The RFID middleware also needs to send a large amount of data, which occupies a large amount of network resources and is easy to cause packet loss and message delay problems. In addition, when the number of RFID readers accessed by the platform (application end) side increases, the massive device data will also cause pressure on the processing of the platform. SUMMARY

[0004] At least one embodiment of the present application provides a tag data processing method, RFID middleware and storage medium, which are used to solve the problem of high occupation of device resources and network resources in the tag data processing of the RFID middleware.

[0005] To solve the above technical problems, the present application is implemented as follows:

[0006] In a first aspect, the embodiments of the present application provide a tag data processing method, which is executed by the RFID middleware and includes the following steps.

[0007] Receiving and caching the tag data of a plurality of tags;

[0008] Compress the tag data according to a predetermined compression mode to obtain compressed data; wherein the compression mode is determined according to a data compression level and a tag inventory rate;

[0009] Send the compressed data.

[0010] Optionally, the compression mode includes at least one of the following:

[0011] A first compression mode, wherein a plurality of tag data of the same tag received within a time window are merged into one tag merged data; wherein the length of the time window is determined according to the data compression level and the tag inventory rate;

[0012] A second compression mode, wherein M tag data and / or tag merged data are grouped into one data packet; wherein the value of M is determined according to the data compression level and the tag inventory rate.

[0013] Optionally, it further includes:

[0014] Receive the data compression level sent by an external device; or, determine the data compression level according to the data volume sensitivity and / or the time delay sensitivity of the business scenario of the tag data processing; wherein the data compression level includes a plurality of compression levels from low to high compression degree, the data compression level is positively correlated with the data volume sensitivity, and / or the data compression level is negatively correlated with the time delay sensitivity.

[0015] Optionally, the above method further includes:

[0016] Statistically count the number of tag data received within a unit time to obtain the tag inventory rate;

[0017] Determine the length of the time window and / or the value of M according to the data compression level and the tag inventory rate;

[0018] Wherein, under the same data compression level, the length of the time window is positively correlated with the tag inventory rate; under the same tag inventory rate, the length of the time window is positively correlated with the data compression level;

[0019] Under the same data compression level, the value of M is positively correlated with the tag inventory rate; under the same tag inventory rate, the value of M is positively correlated with the data compression level.

[0020] Optionally, compressing the tag data according to a predetermined compression mode to obtain compressed data includes:

[0021] In a case where the compression mode only includes the first compression mode, tag data of the same tag received in the same time window is merged into one tag merged data to obtain the compressed data;

[0022] In a case where the compression mode only includes the second compression mode, M tag data are grouped into one data packet according to the time sequence of the tag data to obtain the compressed data;

[0023] In a case where the compression mode includes the first compression mode and the second compression mode, tag data of the same tag received in the same time window is merged into one tag merged data, and M tag data and / or tag merged data of different tags in the time window are grouped into one data packet according to M tags to obtain the compressed data.

[0024] Optionally, merging the tag data of the same tag received in the same time window into one tag merged data includes:

[0025] In the case of merging the plurality of tag data of the same tag into one tag merged data, antenna information, received signal strength indication (RSSI) information and time information in each tag data are retained in the tag merged data according to the time sequence of the tag data, and only one tag ID is retained in the tag merged data to indicate the same tag.

[0026] In a second aspect, the embodiments of the present application provide an RFID middleware, comprising:

[0027] A receiving module configured to receive and cache tag data of a plurality of tags;

[0028] A compression module configured to compress the tag data according to a predetermined compression mode to obtain compressed data; wherein the compression mode is determined according to a data compression level and a tag inventory rate;

[0029] A sending module configured to send the compressed data.

[0030] Optionally, the compression mode includes at least one of the following:

[0031] A first compression mode, in which a plurality of tag data of the same tag received in a time window are merged into one tag merged data; wherein the length of the time window is determined according to the data compression level and the tag inventory rate;

[0032] A second compression mode, in which M tag data and / or tag merged data are grouped into one data packet; wherein the value of M is determined according to the data compression level and the tag inventory rate.

[0033] Optionally, the RFID middleware further comprises:

[0034] The first determining module is configured to receive the data compression level sent by an external device, or determine the data compression level according to the data volume sensitivity and / or the time delay sensitivity of a business scenario of tag data processing; wherein the data compression level comprises a plurality of compression levels from low to high, the data compression level is positively correlated with the data volume sensitivity, and / or the data compression level is negatively correlated with the time delay sensitivity.

[0035] Optionally, the RFID middleware further comprises:

[0036] The second determining module is configured to count the number of received tag data within a unit time to obtain the tag inventory rate, and determine the length of the time window and / or the value of M according to the data compression level and the tag inventory rate.

[0037] Wherein, under the same data compression level, the length of the time window is positively correlated with the tag inventory rate; under the same tag inventory rate, the length of the time window is positively correlated with the data compression level.

[0038] Under the same data compression level, the value of M is positively correlated with the tag inventory rate; under the same tag inventory rate, the value of M is positively correlated with the data compression level.

[0039] Optionally, the compression module is further configured to:

[0040] In the case where the compression mode only includes the first compression mode, the tag data of the same tag received within the same time window is merged into one tag merged data to obtain the compressed data.

[0041] In the case where the compression mode only includes the second compression mode, M tag data are grouped into one data packet according to the receiving time sequence of the tag data to obtain the compressed data.

[0042] In the case where the compression mode includes the first compression mode and the second compression mode, the tag data of the same tag received within the same time window is merged into one tag merged data, and M tag data and / or tag merged data of M different tags within the time window are grouped into one data packet to obtain the compressed data.

[0043] Optionally, the compression module is further configured to, when merging the multiple tag data of the same tag into one tag-merged data, retain the antenna information, the received signal strength indication (RSSI) information and the time information in each tag data in the tag-merged data in the order of the receiving time of the tag data, and retain only one tag ID in the tag-merged data to indicate the same tag.

[0044] In a third aspect, an embodiment of the present application provides an RFID middleware, comprising a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable in the processor; the processor executes the program or instructions to implement the steps of the method in any one of claims 1 to 6.

[0045] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a program, and the program, when executed by a processor, implements the steps of the method in any one of the first aspect.

[0046] In a fifth aspect, an embodiment of the present application provides a computer program product, which comprises computer instructions, and the computer instructions, when executed by a processor, implement the steps of the method in any one of the first aspect.

[0047] Compared with the prior art, the tag data processing method, the RFID middleware and the storage medium provided by the embodiments of the present application improve the data processing efficiency, greatly reduce the device resource occupancy rate, data flow and bandwidth occupancy of network transmission of the middleware at a high inventory rate, and reduce the pressure of mass data processing of the upper platform. The embodiments of the present application also enable the platform side to receive full-amount tag data, which is conducive to algorithm application development. In addition, the embodiments of the present application also adjust the packet grouping quantity and data compression level according to different business needs, to adapt to the needs of different business scenarios with different data volume and time delay sensitivity. BRIEF DESCRIPTION OF DRAWINGS

[0048] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The accompanying drawings are included to provide a description of the preferred embodiments, and are not intended to limit the scope of the present application. Moreover, like reference numerals designate like parts throughout the several views in the drawings. In the drawings:

[0049] Figure 1 An application scenario diagram of an embodiment of the present application;

[0050] Figure 2 A flowchart of a tag data processing method of an embodiment of the present application;

[0051] Figure 3An interactive flowchart of a tag data processing method according to an embodiment of the present application;

[0052] Figure 4 A structural schematic diagram of an RFID middleware according to an embodiment of the present application;

[0053] Figure 5 A structural schematic diagram of an RFID middleware according to another embodiment of the present application. DETAILED DESCRIPTION

[0054] The terms "first", "second", and the like in the present application are used to distinguish similar objects, and are not used to describe a particular order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second" are generally of a kind, and are not limited in number, for example, the first object can be one or more. In addition, the term "and / or" in the present application describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the three cases of A alone, A and B together, and B alone. The character " / " generally represents an "or" relationship between the associated objects before and after it.

[0055] The term "indication" in the present application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). Among them, the direct indication can be understood as that the sender explicitly informs the receiver of the specific information, the operation to be performed or the request result, etc. in the sent indication; the indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or judges and determines the operation to be performed or the request result according to the judgment result.

[0056] As described in the background, the RFID middleware running on the RFID reader / writer processes the tag data, which is prone to cause high occupation of device processing resources and network resources. In addition, the prior art may filter and de-duplicate the tag data, which reduces the number of message processing of the middleware, but the received tag data is not full-amount tag data, which is not conducive to the analysis and processing of the tag data by the upper layer application, for example, is not conducive to the application of tag positioning algorithm.

[0057] To solve at least one of the above problems, the embodiments of the present application provide a tag data processing method, which can reduce the occupation of device resources and network resources by tag data processing. In addition, some embodiments of the present application can also avoid the problem that the upper layer application cannot obtain full-amount tag data due to filtering / de-duplication processing.

[0058] Figure 1An application scenario of the tag data processing method of the present application is shown in FIG. 1. It includes a resource management platform (hereinafter sometimes referred to as "platform" for short), a reader / writer (i.e. RFID reader / writer, hereinafter sometimes referred to as "RFID reader / writer", "RFID reader / writer device", "reader / writer" or "reader / writer device") and tags. The number of tags is usually multiple. For the sake of brevity, Figure 1 Only one tag is shown in the figure. The middleware communicates with the platform based on the Message Queuing Telemetry Transport (MQTT) protocol, controls the radio frequency module to execute actual business commands through the device driver, and interacts with the tags based on the air interface protocol.

[0059] Please refer to Figure 2 The tag data processing method provided by the embodiments of the present application is executed by an RFID middleware, which is run / set on an RFID reader / writer. As shown in FIG. 2, the method includes the following steps. Figure 1

[0060] Step 21: Receiving and buffering tag data of multiple tags.

[0061] Here, the RFID middleware can receive and analyze the inventory task issued by the platform, then issue an inventory command to control the hardware module (such as the radio frequency module) to start inventory and interact with the tags over the air interface. In this way, the RFID middleware can receive and buffer the data packets (i.e. tag data) of the inventory tags.

[0062] Step 22: Compressing the tag data according to a predetermined compression mode to obtain compressed data; wherein the compression mode is determined according to the data compression level and the tag inventory rate.

[0063] Here, the compression mode includes a first compression mode and / or a second compression mode. That is, the embodiments of the present application can only use the first compression mode to compress the tag data, or only use the second compression mode to compress the tag data, or use both the first and second compression modes to compress the tag data. The first compression mode is to merge multiple tag data of the same tag received within a time window into one tag-merged data; wherein the length of the time window is determined according to the data compression level and the tag inventory rate. The second compression mode is to group M tag data and / or tag-merged data into one data packet; wherein the value of M is also determined according to the data compression level and the tag inventory rate.

[0064] ​In the embodiments of the present application, the data compression level is used to indicate the compression degree of the tag data, and generally includes multiple compression levels from low to high. Among them, the higher the data compression level, the greater the data compression degree, and the smaller the amount of compressed data; on the contrary, the lower the data compression level, the smaller the compression degree, and the greater the amount of compressed data. That is, the data compression degree is positively correlated with the data compression level.

[0065] In the embodiments of the present application, the data compression level can be obtained in various ways. For example, the RFID middleware receives the data compression level sent by an external device (such as a resource management platform or the like). For another example, the RFID middleware can determine the data compression level by itself, specifically, the data compression level can be determined according to the data volume sensitivity and / or latency sensitivity of the business scenario of the tag data processing. The data compression level is positively correlated with the data volume sensitivity of the business scenario, that is, the higher the data volume sensitivity, the higher the data compression level, so as to reduce the amount of data to be transmitted. The data volume sensitivity is used to indicate the influence degree of the data volume on the business scenario. The higher the data volume sensitivity, the greater the influence degree of the data volume on the business scenario; on the contrary, the lower the data volume sensitivity, the smaller the influence degree of the data volume on the business scenario. Generally, the data volume sensitivity is related to factors such as the transmission bandwidth between the resource management platform and the middleware, the energy consumption of the RFID reader, and the like. In addition, the data compression level is also negatively correlated with the latency sensitivity under the business scenario, that is, the higher the latency sensitivity, the lower the data compression level, so as to reduce the compression data processing delay. The latency sensitivity is generally related to the requirement of the business scenario on the latency.

[0066] In the embodiments of the present application, the tag inventory rate can be represented by the number of tag data received per unit time. The RFID middleware can count the number of tag data received per unit time to obtain the tag inventory rate.

[0067] After obtaining the data compression level and the tag inventory rate, the RFID middleware can determine the length of the time window and / or the value of M according to the data compression level and the tag inventory rate. Among them:

[0068] Under the same data compression level, the length of the time window is positively correlated with the tag inventory rate, that is, the higher the tag inventory rate, the longer the time window; on the contrary, the lower the tag inventory rate, the shorter the time window. Under the same tag inventory rate, the length of the time window is positively correlated with the data compression level, that is, the higher the data compression level, the longer the time window; on the contrary, the lower the data compression level, the shorter the time window.

[0069] The value of M is positively correlated with the label inventory rate at the same data compression level, that is, the higher the label inventory rate, the larger the value of M; otherwise, the lower the label inventory rate, the smaller the value of M. The value of M is positively correlated with the data compression level at the same label inventory rate, that is, the higher the data compression level, the larger the value of M; otherwise, the lower the data compression level, the smaller the value of M.

[0070] Step 23, sending the compressed data.

[0071] Here, the RFID middleware can send the compressed data obtained after compression in step 22, for example, to the resource management platform.

[0072] Through the above processing, the embodiments of the present application can compress the received label data by using the first compression mode and / or the second compression mode and then send the compressed data. Since compression processing is adopted, it is not necessary to send each received label data separately, thereby reducing the number of sending times and relieving the occupation of device resources by sending processing. In addition, since the amount of data after compression processing is reduced, the amount of data to be sent can be reduced, and therefore the above-mentioned method of the embodiments of the present application can reduce the occupation of device resources and network resources.

[0073] In the above step 22, the RFID middleware can have different processing according to different compression modes, which will be described in detail as follows:

[0074] (1) In the case where the compression mode only includes the first compression mode, the RFID middleware merges the label data of the same label received in the same time window into one label merged data to obtain the compressed data.

[0075] (2) In the case where the compression mode only includes the second compression mode, the RFID middleware groups M label data into one data packet according to the receiving time sequence of the label data to obtain the compressed data.

[0076] (3) In the case where the compression mode includes the first compression mode and the second compression mode, the RFID middleware merges the label data of the same label received in the same time window into one label merged data, and groups the label data and / or the label merged data of M different labels in the time window into one data packet according to M labels in a group to obtain the compressed data.

[0077] To reduce the problem of missing label data information caused by label data merging processing of the same label data, and ensure that the receiving side (such as a resource management platform) can receive all label information contained in the label data, in an embodiment of the present application, when the multiple label data of the same label are merged into one label merging data, the antenna information, received signal strength indication (RSSI) information and time information (such as label data receiving time) in each label data are retained in the label merging data in the order of receiving time of the label data, and only one label ID is retained in the label merging data to indicate the same label.

[0078] The above method will be further described below by taking a more specific inventory task as an example. Figure 1 And Figure 3 The above method will be further described below by taking a more specific inventory task as an example.

[0079] As shown in Figure 3 , the example includes:

[0080] Step 1: The platform issues an inventory task.

[0081] The platform issues an inventory task according to actual business needs. For businesses with different time delay sensitivities and data volume sensitivities, such as label inventory, entrance and exit recognition, sensor reading, etc., different data compression levels are set. The specific data compression levels include three levels, corresponding to no data compression, normal data compression and extreme data compression. The compression degree of the three levels increases in turn. The middleware receives and analyzes the inventory task issued by the platform and obtains the data compression level contained therein.

[0082] The label processing process of the middleware includes steps 2-7, and the specific process is as follows:

[0083] Steps 2-3: The middleware issues an inventory command to control the hardware module (such as the radio frequency module) to start inventory and interact with the label over the air interface.

[0084] Steps 4-5: The middleware receives the data packet of the inventory label, calculates the label inventory rate once per second, and sets the first compression mode and the second compression mode according to the label inventory rate and the data compression level.

[0085] Steps 6-7: The middleware completes the compression processing of the label data according to the first compression mode and the second compression mode, and reports to the platform. Among them, the middleware dynamically adjusts the packet number (i.e. the value of M of the second compression mode) and the data compression window (i.e. the size of the time window under the first compression mode) according to the data compression level and the label inventory rate.

[0086] The first compression mode and the second compression mode in the present example are described below.

[0087] (1) Dynamically adjusting time window to compress tag data (first compression mode)

[0088] The inventory business generally has a large amount of repeated tag data within a certain period of time. According to this feature, a strategy of dynamically adjusting the time window to compress tag data is designed in the present example to compress repeated tag data. First, a time window τ is created, and all tag data in the time window is traversed to compress the same tag data into the same json array, while the antenna, RSSI, and time information of the tag are preserved in order. The data compression is affected by the data compression level issued by the platform and the tag inventory rate. The specific situation is as follows:

[0089] 1. If the data compression level is data non-compression, the middleware does not compress the tag data.

[0090] 2. If the data compression level is data normal compression, the middleware will adjust the packet number of tag data according to the inventory rate index to make the data reporting quantity as small as possible. For example, when the inventory rate is 1-50 tags / s, the length of τ is 0; when the inventory rate is 51-100 tags / s, the length of τ is 100 ms; when the inventory rate is greater than 100 tags / s, the length of τ is 200 ms. The above rate interval parameters and time window length can be adjusted by the platform setting, and also have default values.

[0091] 3. If the data compression level is data limit compression, the middleware will adjust the time window τ according to the inventory rate index to make the data reporting quantity as small as possible. For example, when the inventory rate is 1-50 tags / s, the length of τ is 100 ms; when the inventory rate is 51-100 tags / s, the length of τ is 500 ms; when the inventory rate is greater than 100 tags / s, the length of τ is 1000 ms. The above rate interval parameters and time window length can be adjusted by the platform setting, and also have default values.

[0092] (2) Dynamically adjusting packet number (value of M in the second compression mode)

[0093] In the tag data processing of the RFID middleware, the MQTT message sending process consumes most of the machine resources, and the tag inventory data is discrete. Therefore, a strategy of dynamically adjusting the packet number is designed according to this feature to reduce the number of packets to reduce data flow and resource consumption. The adjustment of the packet number is affected by the data compression level issued by the platform and the tag inventory rate. The specific situation is as follows:

[0094] 1. If the data compression level is data non-compression, the middleware sends 1 data packet for each tag according to the data reporting mode.

[0095] 2. If the data compression level is data normal compression, the middleware adjusts the number of packet groups of the tag data according to the inventory rate index, while taking into account the real-time data reporting. For example, when the inventory rate is 1-50 tags / s, the number of packet groups is 1; when the inventory rate is 51-100 tags / s, the number of packet groups is 3; and when the inventory rate is greater than 100 tags / s, the number of packet groups is 5. The above rate interval parameters and packet group number parameters can be adjusted through platform settings, and also have default values.

[0096] 3. If the data compression level is data limit compression, the middleware adjusts the number of packet groups of the tag data according to the inventory rate index, so as to make the data reporting as small as possible. For example, when the inventory rate is 1-50 tags / s, the number of packet groups is 5; when the inventory rate is 51-100 tags / s, the number of packet groups is 10; and when the inventory rate is greater than 100 tags / s, the number of packet groups is 20. The above rate interval parameters and packet group number parameters can be adjusted. The above rate interval parameters and packet group number parameters can be adjusted through platform settings, and also have default values.

[0097] The following further provides specific descriptions of platform issued commands and compression processing:

[0098] The platform issues an inventory command and sets the data compression level to normal compression mode, with the compression parameter being the default value:

[0099]

[0100]

[0101] The middleware packet groups and compresses the json message body as follows, with the number of packet groups being 3 and the time compression window being 200 ms. As can be seen, through packet grouping and compression, the middleware sends 12 tag data packets in 1 data packet. Specifically, in this example, the middleware first merges 6 tag data with tag IDs 3000...f2d34 into 1 merged tag data, merges 4 tag data with tag IDs 3000...c3460 into 1 merged tag data, and merges 2 tag data with tag IDs 3000...2dcc2 into 1 merged tag data. Then, the above 3 tags form a data packet.

[0102]

[0103]

[0104] As can be seen from the above examples, the embodiments of the present application improve the data processing efficiency by dynamically adjusting the number of packet groups and the time window compression method, greatly reducing the machine resource occupancy rate, data flow and network transmission bandwidth occupancy of the middleware at high inventory rates, while reducing the massive data processing pressure of the upper platform. At the same time, the platform side receives full label data, which is beneficial to algorithm application development. In addition, the embodiments of the present application also adjust the packet group number and data compression level according to different business needs, to adapt to the needs of different business scenarios with different data volume and latency sensitivity.

[0105] The above introduces various methods of embodiments of the present application. The following will further provide a device for implementing the above method.

[0106] Please refer to Figure 4 The embodiments of the present application also provide an RFID middleware, comprising:

[0107] The receiving module 41 is configured to receive and cache label data of a plurality of tags;

[0108] The compression module 42 is configured to compress the label data according to a predetermined compression method to obtain compressed data; wherein the compression method is determined according to a data compression level and a tag inventory rate;

[0109] The sending module 43 is configured to send the compressed data.

[0110] Through the above modules, the embodiments of the present application can solve the problem of high occupation of device resources and network resources by RFID middleware in label data processing.

[0111] Optionally, the compression method comprises at least one of the following:

[0112] The first compression method combines a plurality of label data of the same tag received in a time window into one label combined data; wherein the length of the time window is determined according to the data compression level and the tag inventory rate;

[0113] The second compression method combines M label data and / or label combined data into one data packet; wherein the value of M is determined according to the data compression level and the tag inventory rate.

[0114] Optionally, the RFID middleware further comprises:

[0115] The first determining module is configured to receive the data compression level sent by the external device, or determine the data compression level according to the data volume sensitivity and / or the time delay sensitivity of the service scene of the tag data processing, wherein the data compression level comprises a plurality of compression levels from low to high compression degree, the data compression level is positively correlated with the data volume sensitivity, and / or the data compression level is negatively correlated with the time delay sensitivity.

[0116] Optionally, the RFID middleware further comprises:

[0117] The second determining module is configured to count the number of received tag data within a unit time to obtain the tag inventory rate, and determine the length of the time window and / or the value of M according to the data compression level and the tag inventory rate.

[0118] The length of the time window is positively correlated with the tag inventory rate under the same data compression level, and the length of the time window is positively correlated with the data compression level under the same tag inventory rate.

[0119] The value of M is positively correlated with the tag inventory rate under the same data compression level, and the value of M is positively correlated with the data compression level under the same tag inventory rate.

[0120] Optionally, the compression module is further configured to:

[0121] In the case where the compression mode only comprises the first compression mode, the tag data of the same tag received within the same time window is merged into one tag merged data to obtain the compressed data.

[0122] In the case where the compression mode only comprises the second compression mode, M tag data are grouped into one data packet according to the receiving time sequence of the tag data to obtain the compressed data.

[0123] In the case where the compression mode comprises the first compression mode and the second compression mode, the tag data of the same tag received within the same time window is merged into one tag merged data, and M tag data and / or tag merged data of M different tags within the time window are grouped into one data packet according to one group of M tags to obtain the compressed data.

[0124] Optionally, the compression module is further configured to, when merging the plurality of tag data of the same tag into one tag merged data, retain the antenna information, the received signal strength indication (RSSI) information and the time information in each tag data in the tag merged data according to the receiving time sequence of the tag data, and retain only one tag ID in the tag merged data to indicate the same tag.

[0125] It should be noted that the device in this embodiment corresponds to the method described above, and the implementation methods in each of the above embodiments are applicable to the device embodiment and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail here.

[0126] Another embodiment of this application provides an RFID middleware, such as... Figure 5 As shown, it includes a transceiver 510, a processor 500, a memory 520, and a program or instructions stored in the memory 520 and executable on the processor 500; when the processor 500 executes the program or instructions, it implements the various processes of the above method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0127] The transceiver 510 is used to receive and send data under the control of the processor 500.

[0128] Among them, Figure 5 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 500) and memory (memory 520). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 510 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 during operation.

[0129] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the above-described tag data processing method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0130] The embodiment of the present application further provides a computer program product comprising computer instructions, which, when executed by a processor, implement each process of the above-mentioned label data processing method embodiment and can achieve the same technical effects. To avoid repetition, details are not described herein.

[0131] It should be noted that in this document, the term "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that processes, methods, articles or apparatuses including a series of elements not only include those elements, but also include other elements not explicitly listed, or further include elements inherent to such processes, methods, articles or apparatuses. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus including the element.

[0132] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment method can be realized by means of software and necessary general hardware platform, of course, it can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of software products, and the computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the method described in each embodiment of the present application.

[0133] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, the above-mentioned specific embodiments are only illustrative, not restrictive, and those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the protection scope of the claims.

Claims

1. A method for processing tag data, characterized in that, Performed by RFID middleware, including: Receive and cache tag data for multiple tags; The tag data is compressed according to a predetermined compression method to obtain compressed data; wherein the compression method is determined based on the data compression level and the tag storage rate. Send the compressed data.

2. The method according to claim 1, characterized in that, The compression method includes at least one of the following: The first compression method merges multiple tag data of the same tag received within a time window into a single tag merged data; wherein the length of the time window is determined based on the data compression level and the tag storage rate; The second compression method combines M tag data and / or tag merged data into a single data packet; wherein the value of M is determined based on the data compression level and tag storage rate.

3. The method according to claim 2, characterized in that, Also includes: The system receives the data compression level from an external device; or, it determines the data compression level based on the data volume sensitivity and / or latency sensitivity of the business scenario for tag data processing; wherein the data compression level includes multiple compression levels from low to high, the data compression level is positively correlated with the data volume sensitivity, and / or the data compression level is negatively correlated with the latency sensitivity.

4. The method according to claim 3, characterized in that, Also includes: The number of tag data received per unit time is counted to obtain the tag inventory rate; The length of the time window and / or the value of M are determined based on the data compression level and the tag storage rate. Specifically, under the same data compression level, the length of the time window is positively correlated with the tag storage rate; under the same tag storage rate, the length of the time window is positively correlated with the data compression level. Under the same data compression level, the value of M is positively correlated with the tag storage rate; under the same tag storage rate, the value of M is positively correlated with the data compression level.

5. The method according to claim 2, characterized in that, The tag data is compressed according to a predetermined compression method to obtain compressed data, including: When the compression method only includes the first compression method, the tag data of the same tag received within the same time window is merged into a single tag merge data to obtain the compressed data; When the compression method only includes the second compression method, the compressed data is obtained by combining M tag data into a data packet according to the receiving time order of the tag data; When the compression method includes the first compression method and the second compression method, the tag data of the same tag received within the same time window is merged into a tag merge data, and the tag data of M different tags and / or tag merge data within the time window are grouped into a data packet according to M tags, to obtain the compressed data.

6. The method according to claim 5, characterized in that, Tag data with the same label received within the same time window will be merged into a single merged tag data, including: When merging multiple tag data of the same tag into one tag merge data, the antenna information, received signal strength index (RSSI) information and time information of each tag data are retained in the tag merge data according to the receiving time order of the tag data. In addition, only one tag ID is retained in the tag merge data to indicate the same tag.

7. An RFID middleware, characterized in that, include: The receiving module is used to receive and cache tag data from multiple tags; A compression module is used to compress the tag data according to a predetermined compression method to obtain compressed data; wherein the compression method is determined based on the data compression level and the tag storage rate. A sending module is used to send the compressed data.

8. The RFID middleware according to claim 7, characterized in that, The compression method includes at least one of the following: The first compression method merges multiple tag data of the same tag received within a time window into a single tag merged data; wherein the length of the time window is determined based on the data compression level and the tag storage rate; The second compression method combines M tag data and / or tag merged data into a single data packet; wherein the value of M is determined based on the data compression level and tag storage rate.

9. The RFID middleware according to claim 8, characterized in that, Also includes: The first determining module is used to receive the data compression level sent by the external device; Alternatively, the data compression level can be determined based on the data volume sensitivity and / or latency sensitivity of the business scenario for tag data processing; wherein the data compression level includes multiple compression levels from low to high, the data compression level is positively correlated with the data volume sensitivity, and / or the data compression level is negatively correlated with the latency sensitivity.

10. The RFID middleware according to claim 9, characterized in that, Also includes: The second determining module is used to count the number of tag data received per unit time to obtain the tag storage rate; and to determine the length of the time window and / or the value of M based on the data compression level and the tag storage rate. Specifically, under the same data compression level, the length of the time window is positively correlated with the tag storage rate; under the same tag storage rate, the length of the time window is positively correlated with the data compression level. Under the same data compression level, the value of M is positively correlated with the tag storage rate; under the same tag storage rate, the value of M is positively correlated with the data compression level.

11. The RFID middleware according to claim 8, characterized in that, The compression module is also used for: When the compression method only includes the first compression method, the tag data of the same tag received within the same time window is merged into a single tag merge data to obtain the compressed data; When the compression method only includes the second compression method, the compressed data is obtained by combining M tag data into a data packet according to the receiving time order of the tag data; When the compression method includes the first compression method and the second compression method, the tag data of the same tag received within the same time window is merged into a tag merge data, and the tag data of M different tags and / or tag merge data within the time window are grouped into a data packet according to M tags, to obtain the compressed data.

12. The RFID middleware according to claim 11, characterized in that, The compression module is further configured to, when merging multiple tag data of the same tag into one tag merged data, retain the antenna information, received signal strength index (RSSI) information and time information of each tag data in the tag merged data according to the receiving time order of the tag data, and retain only one tag ID in the tag merged data to indicate the same tag.

13. An RFID middleware, characterized in that, include: Transceiver, processor, memory, and programs or instructions stored in the memory and executable on the processor; When the processor executes the program or instructions, it implements the steps of the method as described in any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 6.

15. A computer program product, characterized in that, Includes computer instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 6.

Images