Label information sending method and device, storage medium and program product

Abstract

The invention discloses a label information sending method and device, a storage medium and a program product, and belongs to the technical field of computers. The method comprises the following steps: receiving first tag information sent by a first electronic tag, wherein the first tag information comprises a first tag identifier and a first tag state; determining whether the first electronic tag satisfies a first preset abnormal condition according to the first tag state; under the condition that the first electronic tag meets a first preset abnormal condition, first tag information is sent to a cloud platform; and when the first label state does not meet the first preset abnormal condition, the first label information is not sent to the cloud platform. According to the invention, the gateway only sends the tag information of the electronic tag with the large probability of abnormity to the cloud platform for monitoring. Therefore, the processing pressure of the cloud platform can be reduced, the load of the cloud platform can be reduced, the electronic tag monitoring efficiency of the cloud platform can be improved, and the performance of the cloud platform can be ensured under the condition that the electronic tag monitoring requirement is met.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a tag information sending method, device, storage medium and program product. Background Art

[0002] Bluetooth low energy (BLE) e-ink electronic tags, due to their low power consumption, high-contrast display, and wireless update capabilities, have been widely used in logistics, warehousing, retail, healthcare, and industrial automation. When in operation, BLE e-ink electronic tags send tag information to the cloud platform. The cloud platform monitors the BLE e-ink electronic tags' operating status for any anomalies and notifies the user to address any such anomalies. However, an excessive number of BLE e-ink electronic tags can place excessive processing pressure on the cloud platform, impacting its performance. Summary of the Invention

[0003] This application provides a tag information sending method, device, storage medium, and program product that can reduce the processing pressure of the cloud platform and ensure the performance of the cloud platform. The technical solution is as follows:

[0004] In a first aspect, a tag information sending method is provided, which is applied to any one of n gateways, wherein the n gateways correspond one-to-one with n groups of electronic tags, and each of the n gateways communicates with a corresponding group of electronic tags, where n is an integer greater than or equal to 2. The method includes:

[0005] receiving first tag information sent by a first electronic tag, where the first tag information includes a first tag identifier and a first tag status;

[0006] determining whether the first electronic tag meets a first preset abnormal condition according to the first tag state;

[0007] When the first electronic tag meets the first preset abnormal condition, sending the first tag information to the cloud platform;

[0008] When the first tag state does not meet the first preset abnormal condition, the first tag information is not sent to the cloud platform.

[0009] In the present application, the first tag information sent by the first electronic tag is received, and the first tag information includes a first tag identifier and a first tag status. Afterwards, whether the first electronic tag meets the first preset abnormal condition is determined based on the first tag status. When the first electronic tag meets the first preset abnormal condition, the first tag information is sent to the cloud platform. When the first electronic tag does not meet the first preset abnormal condition, the first tag information is not sent to the cloud platform. In the present application, the gateway only sends the tag information of the electronic tags that are likely to be abnormal to the cloud platform for monitoring. In this way, the processing pressure of the cloud platform can be reduced, the load of the cloud platform can be reduced, the efficiency of the cloud platform in monitoring electronic tags can be improved, and the performance of the cloud platform can be guaranteed while meeting the electronic tag monitoring needs.

[0010] Optionally, the first tag information further includes a manufacturer identifier, and determining whether the first electronic tag meets a first preset abnormal condition according to the first tag status includes:

[0011] In a case where the manufacturer identifier is a preset manufacturer identifier, it is determined whether the first electronic tag meets the first preset abnormal condition according to the first tag state.

[0012] Optionally, determining whether the first electronic tag meets a first preset abnormal condition according to the first tag state includes:

[0013] If the first tag identifier exists in the first set, determining whether the first electronic tag meets the first preset abnormal condition according to the first tag state;

[0014] The method further comprises:

[0015] If the first tag identifier does not exist in the first set, adding the first tag information to the first set;

[0016] Send the first tag information to the cloud platform.

[0017] Optionally, after receiving the first tag information sent by the first electronic tag, the method further includes:

[0018] In a case where the first tag identifier exists in the first set, the tag status corresponding to the first tag identifier in the first set is updated according to the first tag status.

[0019] Optionally, the method further includes:

[0020] For any tag identifier in the first set, when the electronic tag identified by the tag identifier is offline, deleting the tag information to which the tag identifier in the first set belongs;

[0021] An offline reminder message is sent to the cloud platform, where the offline reminder message includes the tag identifier.

[0022] Optionally, the tag status includes a timestamp, and the method further includes:

[0023] For any tag identifier in the first set, if the time indicated by the timestamp in the tag state corresponding to the tag identifier is greater than or equal to the first preset time length from the current time, it is determined that the electronic tag identified by the tag identifier is offline.

[0024] Optionally, before receiving the first tag information sent by the first electronic tag, the method further includes:

[0025] After starting, the system enters a scanning mode, and the duration of the scanning mode is a second preset duration;

[0026] In the scanning mode, receiving second tag information sent by each of the one or more second electronic tags, the second tag information including a second tag identifier and a second tag status;

[0027] Whenever second label information sent by a second electronic label is received, if the second label identifier in the second label information does not exist in the first set, the second label information is added to the first set; if the second label identifier in the second label information exists in the first set, the label state corresponding to the second label identifier in the second label information in the first set is updated according to the second label state in the second label information;

[0028] When the scanning mode ends, all tag information in the first set is sent to the cloud platform.

[0029] In a second aspect, a device for sending tag information is provided, the device comprising:

[0030] A first receiving module is configured to receive first tag information sent by a first electronic tag, where the first tag information includes a first tag identifier and a first tag status;

[0031] a first determining module, configured to determine whether the first electronic tag satisfies a first preset abnormal condition according to the first tag state;

[0032] a first sending module, configured to send the first tag information to a cloud platform when the first electronic tag meets the first preset abnormal condition;

[0033] An end module is configured to not send the first tag information to the cloud platform when the first tag state does not meet the first preset abnormal condition.

[0034] In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the tag information sending method described in the first aspect.

[0035] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the tag information sending method described in the first aspect is implemented.

[0036] In a fifth aspect, a computer program product is provided. When the computer program product is run on a computer device, the computer device executes the tag information sending method described in the first aspect.

[0037] It can be understood that the beneficial effects of the second, third, fourth and fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0039] Figure 1 is a schematic diagram of an electronic tag system provided in an embodiment of the present application;

[0040] Figure 2 This is a schematic diagram of the structure of an electronic tag system provided in an embodiment of the present application;

[0041] Figure 3 This is a schematic diagram of the structure of another electronic tag system provided in an embodiment of the present application;

[0042] Figure 4 This is a flowchart of a tag information sending method provided by an embodiment of the present application;

[0043] Figure 5 This is a schematic diagram of a tag information synchronization process provided by an embodiment of the present application;

[0044] Figure 6 This is a structural diagram of a tag information sending device provided in an embodiment of the present application;

[0045] Figure 7It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0047] It should be understood that the “multiple” mentioned in this application refers to two or more. In the description of this application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; “and / or” in this article is merely a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in order to facilitate the clear description of the technical solution of this application, words such as “first” and “second” are used to distinguish between identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not necessarily limit them to be different.

[0048] The phrases "one embodiment" or "some embodiments" described in this application mean that the specific features, structures, or characteristics described in that embodiment are included in one or more embodiments of the application. Thus, the phrases "in one embodiment," "in some embodiments," "in other embodiments," and "in other embodiments" that appear in different places in this application do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. In addition, the terms "including," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0049] The application scenarios of the embodiments of the present application are described below.

[0050] In large-scale electronic tag applications (such as warehouse management, retail shelves, etc.), the gateway is responsible for communicating with the electronic tags and uploading data to the cloud platform to achieve centralized monitoring of the electronic tags through the cloud platform. Figure 1As shown, the gateway continuously receives broadcast messages from electronic tags, extracts tag information such as battery level, model, and error codes from these broadcast messages, and uploads it to the cloud platform, which then monitors the tag's operating status. However, when the number of electronic tags is very large, reaching hundreds of thousands or even millions, this approach requires the cloud platform to process massive amounts of data, which may cause the cloud platform's processing speed to be slower than the gateway's data transmission speed, resulting in excessive cloud platform load, data backlogs, processing delays, and other issues that affect cloud platform performance. Therefore, achieving low-load monitoring in large-scale electronic tag applications is a key issue that requires attention.

[0051] In related technologies, the time interval for the gateway to upload tag information to the cloud platform can be extended to reduce the load on the cloud platform. However, this approach will result in the cloud platform not being able to promptly know if an electronic tag has an anomaly, resulting in poor real-time performance.

[0052] To this end, the present invention provides a method for sending tag information, which is applied to the following Figure 2 Any gateway in the embodiment. The gateway receives the first tag information sent by the first electronic tag, and the first tag information includes a tag identifier and a tag status. Afterwards, it is determined whether the first electronic tag meets the first preset abnormal condition based on the first tag status. In the case that the first electronic tag meets the first preset abnormal condition, the first tag information is sent to the cloud platform. In the case that the first tag status does not meet the first preset abnormal condition, the first tag information is not sent to the cloud platform. In the embodiment of the present application, the gateway only sends the tag information of the electronic tags that are likely to be abnormal to the cloud platform for monitoring. In this way, while meeting the electronic tag monitoring needs, the processing pressure of the cloud platform can be reduced, the load of the cloud platform can be reduced, the efficiency of the cloud platform in monitoring electronic tags can be improved, and the performance of the cloud platform can be guaranteed.

[0053] The electronic tag system provided in the embodiment of the present application is described below.

[0054] Figure 2 This is a schematic diagram of an electronic tag system provided by an embodiment of the present application. Figure 2 The electronic tag system 20 includes n groups of electronic tags 201, n gateways 202 and a cloud platform 203. The n gateways 202 correspond to the n groups of electronic tags 201 on a one-to-one basis, and n is an integer greater than or equal to 2.

[0055] Any two groups of electronic tags in the n groups of electronic tags are not completely the same, that is, any two groups of electronic tags in the n groups of electronic tags are completely different, or any two groups of electronic tags may have at least one identical electronic tag.

[0056] Any of the n groups of electronic tags 201 can communicate with a corresponding gateway 202 of the n gateways 202 via a wired connection or a wireless connection. For example, the electronic tag 201 can be a BLE ink screen electronic tag, etc., which is not limited in this embodiment of the application.

[0057] For any one gateway 202 among the n gateways 202 , a group of electronic tags 201 corresponding to the gateway 202 is within the communication range of the gateway 202 .

[0058] Each of the n gateways 202 can communicate with the cloud platform 203 via a wired connection or a wireless connection. For example, the gateway 202 can be a Bluetooth gateway, etc., which is not limited in this embodiment of the present application.

[0059] The electronic tag 201 is used to broadcast tag information. For example, if the electronic tag 201 is a BLE ink screen electronic tag, the tag information can be carried in the Bluetooth broadcast packet.

[0060] Optionally, the electronic tag 201 may broadcast the tag message periodically. The period may be pre-set. For example, the period of the electronic tag 201 broadcasting the tag message may be set to 4 seconds (s), 5 seconds, or 6 seconds, etc., which is not limited in this embodiment of the present application.

[0061] For example, the tag information may include one or more of the tag identification, tag status, and manufacturer identification of the electronic tag 201 .

[0062] The tag identifier is used to identify the electronic tag 201 .

[0063] The manufacturer identifier is used to identify the manufacturer that produces the electronic tag 201 .

[0064] For example, the tag status may include one or more of battery value, error code information, device model, screen information (including but not limited to screen resolution, size information, color information, etc.), timestamp, etc., which is not limited in the embodiments of the present application.

[0065] The power value is used to indicate the remaining power of the electronic tag 201 .

[0066] The error code information indicates whether the electronic tag 201 has experienced one or more of the following anomalies: hardware anomaly, firmware anomaly, etc. For example, a hardware anomaly may be screen damage. Alternatively, if the electronic tag 201 has experienced a hardware anomaly or firmware anomaly, the error code information may include the error code. If the electronic tag 201 has not experienced either a hardware anomaly or a firmware anomaly, the error code information may be blank (None).

[0067] The screen resolution is used to indicate the resolution of the screen of the electronic tag 201 .

[0068] The size information is used to indicate the size of the screen of the electronic tag 201 .

[0069] The color information is used to indicate the colors that can be displayed on the screen of the electronic tag 201. For example, the color information can be black and white, black and white and red, black and white and red and yellow, or color, etc., which is not limited in the embodiment of the present application.

[0070] The timestamp is used to indicate the time when the electronic tag 201 generates the tag information.

[0071] Optionally, the tag information may be described by a tag file (also referred to as a data model). For example, the tag file may include the following content:

[0072]

[0073] The gateway 202 is used to receive the tag information sent by the electronic tag 201 . The gateway 202 can parse the tag information to obtain the tag identification and tag status of the electronic tag 201 .

[0074] Gateway 202 determines whether electronic tag 201 meets a first preset abnormality condition based on the tag status. If electronic tag 201 meets the first preset abnormality condition, gateway 202 sends the tag information to cloud platform 203. If electronic tag 201 does not meet the first preset abnormality condition, gateway 202 does not send the tag information to cloud platform 203.

[0075] The cloud platform 203 is used to receive the tag information sent by the gateway 202 and monitor whether the electronic tag 201 has any abnormality according to the tag information.

[0076] Optionally, after the cloud platform 203 determines that the electronic tag 201 is abnormal, it can send a reminder message to the user to remind the user that the electronic tag 201 is abnormal.

[0077] The cloud platform 203 can be a single server or a server cluster consisting of multiple servers. System software can run on the cloud platform 203 to coordinate and manage the electronic tags 201 and gateways 202 registered with the cloud platform 203. Optionally, the system software can also provide users with a management control interface or a third-party application programming interface (API).

[0078] Optionally, the cloud platform 203 may also send a control instruction to the gateway 202. After receiving the control instruction sent by the cloud platform 203, the gateway 202 may perform an operation according to the control instruction. For example, the control instruction may be a synchronization instruction, a configuration instruction, a firmware update instruction, a data read instruction, etc., which is not limited in this embodiment of the present application.

[0079] The following combination Figure 3 The working process of the electronic tag system 20 is described as follows. Figure 3 As shown, the electronic tag system includes gateway 1, gateway 2, and gateway 3. Gateway 1 communicates with electronic tag 1, electronic tag 2, and electronic tag 3 respectively. Gateway 2 communicates with electronic tag 4 and electronic tag 5 respectively. Gateway 3 communicates with electronic tag 6, electronic tag 7, and electronic tag 8 respectively.

[0080] After receiving the tag information from electronic tag 1, gateway 1 determines that electronic tag 1 meets the first preset abnormality condition and then sends the tag information to the cloud platform. After receiving the tag information from electronic tag 2, gateway 1 determines that electronic tag 2 does not meet the first preset abnormality condition and therefore does not send the tag information to the cloud platform. After receiving the tag information from electronic tag 3, gateway 1 determines that electronic tag 3 does not meet the first preset abnormality condition and therefore does not send the tag information to the cloud platform.

[0081] After receiving the tag information sent by electronic tag 4, gateway 2 determines that electronic tag 4 does not meet the first preset abnormality condition and therefore does not send the tag information to the cloud platform. After receiving the tag information sent by electronic tag 5, gateway 2 determines that electronic tag 5 meets the first preset abnormality condition and then sends the tag information to the cloud platform.

[0082] After receiving the tag information from electronic tag 6, gateway 3 determines that electronic tag 6 does not meet the first preset abnormality condition and therefore does not send the tag information to the cloud platform. After receiving the tag information from electronic tag 7, gateway 3 determines that electronic tag 7 meets the first preset abnormality condition and then sends the tag information to the cloud platform. After receiving the tag information from electronic tag 8, gateway 3 determines that electronic tag 8 does not meet the first preset abnormality condition and therefore does not send the tag information to the cloud platform.

[0083] Based on this, Gateways 1, 2, and 3 each shoulder a portion of the cloud platform's monitoring burden. The cloud platform no longer needs to monitor the tag information of eight electronic tags (e.g., tags 1 through 8). Instead, it only needs to monitor the tag information of three electronic tags (e.g., tags 1, 5, and 7). This significantly reduces the cloud platform's load and processing pressure, while meeting the electronic tag monitoring requirements and ensuring its performance.

[0084] The tag information sending method provided in the embodiment of the present application is explained in detail below.

[0085] In some embodiments, for any gateway, such as for the above Figure 2 Any gateway 202 in the embodiment can determine the electronic tags that need to be monitored.

[0086] The following is an exemplary description of the process of determining the electronic tags that need to be monitored. The determination process may include the following steps (1) to (4).

[0087] Step (1): The gateway enters a scanning mode after startup, and the duration of the scanning mode is a second preset duration.

[0088] The gateway may end the scanning mode after a second preset time period after entering the scanning mode.

[0089] For example, the gateway may enter the scanning mode after being started for the first time, or the gateway may enter the scanning mode after being restarted (ie, rebooted), which is not limited in the embodiments of the present application.

[0090] Optionally, after restarting, the gateway may first delete all tag information in the first set and then enter the scanning mode.

[0091] The scanning mode is a mode for determining electronic tags that need to be monitored.

[0092] The second preset duration can be pre-set. For example, the second preset duration can be set to 5 minutes, 10 minutes, or 15 minutes, etc., which is not limited in this embodiment of the present application.

[0093] Step (2): The gateway receives the second tag information sent by each of the one or more second electronic tags in the scanning mode.

[0094] The second tag information includes a second tag identifier and a second tag status. Optionally, the second tag information may also include a manufacturer identifier.

[0095] The second tag identifier is used to identify the second electronic tag. The second tag status is used to indicate the operating status of the second electronic tag. The manufacturer identifier is used to identify the manufacturer that produced the second electronic tag.

[0096] Step (3): Every time the gateway receives the second tag information sent by a second electronic tag, if the second tag identifier in the second tag information does not exist in the first set, the gateway adds the second tag information to the first set; if the second tag identifier in the second tag information exists in the first set, the gateway updates the tag status in the first set corresponding to the second tag identifier in the second tag information according to the second tag status in the second tag information.

[0097] If the second tag identifier in the second tag information does not exist in the first set, it means that the gateway has not previously received the tag information sent by the electronic tag identified by the second tag identifier. Therefore, the second tag information can be added to the first set so that the operating status of the second electronic tag can be monitored subsequently.

[0098] If the second tag identifier in the second tag information exists in the first set, it means that the gateway has previously received the tag information sent by the electronic tag identified by the second tag identifier. Therefore, after the gateway receives the second tag information sent by the electronic tag this time, it can update the tag status corresponding to the second tag identifier in the second tag information in the first set according to the second tag status in the second tag information, so that the first set can save the latest tag information of the electronic tag.

[0099] In some cases, after the gateway receives the second tag information sent by a second electronic tag, it can directly execute step (3).

[0100] In other cases, users typically use electronic tags produced by one or more specific manufacturers, while the gateway's communication range may include electronic tags produced by different manufacturers. Therefore, the gateway can filter electronic tags based on the manufacturer identification in the tag information to determine the electronic tags that need to be monitored.

[0101] In this case, after receiving the second tag information sent by a second electronic tag, the gateway can determine whether the manufacturer identifier in the second tag information is the preset manufacturer identifier; if the manufacturer identifier is the preset manufacturer identifier, execute step (3); if the manufacturer identifier is not the preset manufacturer identifier, discard the second tag information.

[0102] The preset manufacturer identifier can be pre-set. The number of preset manufacturer identifiers can be one or more.

[0103] If the manufacturer identifier is a preset manufacturer identifier, it means that the second electronic tag corresponding to the second tag information is an electronic tag that the gateway needs to monitor, so step (3) can be continued. If the manufacturer identifier is not a preset manufacturer identifier, it means that the second electronic tag corresponding to the second tag information is not an electronic tag that the gateway needs to monitor, so the second tag information can be discarded.

[0104] Step (4): The gateway sends all tag information in the first set to the cloud platform at the end of the scanning mode.

[0105] Generally, the gateway needs to scan all electronic tags within its communication range after the first startup or restart, in order to obtain all the electronic tags to be monitored. If the gateway directly sends the tag information sent by each electronic tag to the cloud platform, the frequency of tag information transmission will be too high. Therefore, in an embodiment of the present application, the gateway can continuously receive the second tag information sent by the second electronic tag within the second preset time period after entering the scanning mode and add it to the first set, and send all the tag information in the first set to the cloud platform at the end of the scanning mode. In this way, the frequency of data transmission can be reduced, the scanning and sending processes can be optimized, the efficiency of data interaction between the gateway and the cloud platform can be improved, and unnecessary system burden can be reduced.

[0106] Optionally, the cloud platform may include n second sets, each of which corresponds to the n gateways in a one-to-one manner. Each of the n second sets may include label information sent by a corresponding gateway.

[0107] Optionally, after the cloud platform receives tag information sent by a gateway, if the tag identifier in the tag information exists in the second set corresponding to the gateway, the tag status corresponding to the tag identifier in the second set can be updated according to the tag status in the tag information. If the tag identifier in the tag information does not exist in the second set corresponding to the gateway, the tag information can be added to the second set corresponding to the gateway. In this case, subsequent users can view the tag information of all electronic tags monitored by the gateway through the cloud platform. In this way, the user experience can be improved.

[0108] In this way, both the gateway and the cloud platform can know which electronic tags are currently being monitored. Moreover, for the electronic tags being monitored, after receiving the tag information sent by them, they can monitor their operating status accordingly.

[0109] In some cases, after the scanning mode is completed, the gateway can perform the following Figure 4 In other cases, the gateway may not execute the scanning mode, that is, the gateway may directly execute the following steps after startup. Figure 4The tag information sending method provided in the embodiment is not limited in the embodiment of the present application.

[0110] Figure 4 This is a flowchart of a tag information sending method provided by an embodiment of the present application. The tag information sending method can be applied to the above Figure 2 Any gateway 202 in the embodiment. Figure 4 , the method comprises the following steps:

[0111] Step 401: The gateway receives first tag information sent by a first electronic tag. The first tag information includes a first tag identifier and a first tag status.

[0112] The first electronic tag is any electronic tag within the communication range of the gateway.

[0113] The first tag identifier is used to identify the first electronic tag.

[0114] The first tag state is used to indicate the operating state of the first electronic tag.

[0115] Optionally, the first label information may further include a manufacturer identifier, which is used to identify the manufacturer that produced the first electronic label.

[0116] In some cases, after receiving the first tag information, the gateway may directly execute the following step 402 .

[0117] In other cases, after receiving the first tag information, the gateway may perform the following step 402 if the manufacturer identifier in the first tag information is the preset manufacturer identifier, or discard the first tag information if the manufacturer identifier in the first tag information is not the preset manufacturer identifier.

[0118] Step 402: The gateway determines whether the first electronic tag meets a first preset abnormal condition according to the first tag state.

[0119] The first preset abnormal condition can be preset. For example, the first preset abnormal condition can be set by a technician according to needs.

[0120] Since the first tag status indicates the operating status of the first electronic tag, the gateway can determine whether the first electronic tag may be abnormal, that is, whether the first electronic tag meets the first preset abnormality condition. If the first electronic tag does not meet the first preset abnormality condition, the gateway can execute the following step 403. If the first electronic tag meets the first preset abnormality condition, the gateway can execute the following step 404.

[0121] In some embodiments, the operation of the gateway determining whether the first electronic tag meets the first preset abnormal condition based on the first tag status can be: when the first tag identifier exists in the first set, the gateway determines whether the first electronic tag meets the first preset abnormal condition based on the first tag status.

[0122] If the first tag identifier does not exist in the first set, the gateway adds the first tag information to the first set and then sends the first tag information to the cloud platform.

[0123] If the first tag identifier exists in the first set, it indicates that the first electronic tag is the electronic tag being monitored by the gateway. Therefore, it can be determined whether the first electronic tag meets the first preset abnormal condition according to the first tag status.

[0124] If the first tag identifier does not exist in the first set, it means that the gateway is not currently monitoring the first electronic tag. For example, the first electronic tag may be a newly added electronic tag (such as one added by a user). In this case, both the gateway and the cloud platform need to know the first electronic tag that can be monitored. Therefore, the gateway can add the first tag information to the first set and send the first tag information to the cloud platform.

[0125] For example, after receiving the first tag information, the cloud platform may add the first tag information to the second set corresponding to the gateway, and the user may subsequently determine whether the first electronic tag is added successfully by checking the second set.

[0126] In some cases, when there is a first tag identifier in the first set, the gateway can update the tag status corresponding to the first tag identifier in the first set according to the first tag status, so that the first set stores the latest tag information of the first electronic tag.

[0127] In some embodiments, the first tag status includes a power value, and the operation of the gateway determining whether the first electronic tag meets the first preset abnormal condition based on the first tag status can be: when the power values ​​received from the first electronic tag in the last m times are all less than or equal to the preset power value, the gateway determines that the first electronic tag meets the first preset abnormal condition, where m is a positive integer.

[0128] The preset power value can be pre-set. For example, the preset power value can be set to 10%, 15%, or 20%, etc., which is not limited in the embodiment of the present application.

[0129] If the power values ​​received by the gateway from the first electronic tag during the most recent m times are all less than or equal to the preset power value, it indicates that the power level of the first electronic tag is low, and therefore the gateway can determine that the first electronic tag meets the first preset abnormality condition. In particular, when m is greater than or equal to 2, the gateway determines that the first electronic tag meets the first preset abnormality condition only if the power values ​​received from the first electronic tag during the most recent multiple consecutive times are all less than or equal to the preset power value. This is because if the power values ​​received from the first electronic tag during the multiple consecutive times are all less than or equal to the preset power value, it indicates that the power value reported by the first electronic tag is relatively accurate, and thus the accuracy of determining that the first electronic tag meets the first preset abnormality condition is relatively high.

[0130] In some embodiments, the first tag status includes error code information, and the operation of the gateway to determine whether the first electronic tag meets the first preset abnormal condition based on the first tag status can be: when the error code in the error code information is a preset error code, determine that the first electronic tag meets the first preset abnormal condition.

[0131] The preset error code can be pre-set. For example, the preset error code can be set by a technician according to needs.

[0132] If the error code in the error code information is a preset error code, it indicates that an abnormality exists in the first electronic tag (such as a hardware abnormality, a firmware abnormality, etc.), so it can be determined that the first electronic tag meets the first preset abnormality condition.

[0133] Step 403: When the first electronic tag does not meet the first preset abnormal condition, the gateway does not send the first tag information to the cloud platform.

[0134] If the first electronic tag does not meet the first preset abnormal condition, it means that the first electronic tag is most likely not abnormal, so the first tag information is not sent to the cloud platform.

[0135] Step 404: When the first electronic tag meets the first preset abnormal condition, the gateway sends the first tag information to the cloud platform.

[0136] If the first electronic tag meets the first preset abnormal condition, it means that the first electronic tag is likely to be abnormal, so the gateway sends the first tag information to the cloud platform.

[0137] In an embodiment of the present application, after the gateway receives the first tag information sent by the first electronic tag, it does not directly send the first tag information to the cloud platform, but determines whether the first electronic tag meets the first preset abnormal condition based on the first tag status in the first tag information. In the case that the first electronic tag does not meet the first preset abnormal condition, that is, when the first electronic tag is most likely not abnormal, the first tag information is not sent to the cloud platform; in the case that the first electronic tag meets the first preset abnormal condition, that is, when the first electronic tag is most likely abnormal, the first tag information is sent to the cloud platform. In an embodiment of the present application, the gateway only sends the tag information of the electronic tags that are most likely to be abnormal to the cloud platform for monitoring. In this way, the processing pressure of the cloud platform can be reduced, the load of the cloud platform can be reduced, the efficiency of the cloud platform in monitoring electronic tags can be improved, and the performance of the cloud platform can be guaranteed. In addition, since the load of the cloud platform is reduced, the cloud platform can manage more gateways and electronic tags, which can improve the scalability of the electronic tag system.

[0138] Optionally, after receiving the first tag information, the cloud platform may monitor the first electronic tag according to the first tag information.

[0139] Optionally, the operation of the cloud platform monitoring the first electronic tag according to the first tag information can be: the cloud platform determines whether the first tag information meets the second preset abnormal condition, and determines that the first electronic tag is abnormal if the first tag information meets the second preset abnormal condition.

[0140] For example, the second preset abnormal condition may include at least one of the following conditions: the battery level is greater than 10% and less than or equal to 20%, the battery level is less than or equal to 10%, and the error code in the error code information is a preset error code. Of course, the second preset abnormal condition may also include other conditions, and this embodiment of the application is not limited thereto.

[0141] Optionally, when the cloud platform determines that the first electronic tag is abnormal, it can send a reminder message to the user account to remind the user that the first electronic tag is abnormal. Optionally, the reminder message can include the first tag identifier and abnormality information, where the abnormality information is used to indicate the abnormality of the first electronic tag.

[0142] For example, if the battery value in the first tag information is less than or equal to 10%, the cloud platform can send a very low battery reminder message to the user account. The very low battery reminder message includes the first tag identifier and the battery value to remind the user that the battery of the electronic tag identified by the first tag identifier is too low. If the battery value in the first tag information is greater than 10% and less than or equal to 20%, the cloud platform can send a low battery reminder message to the user account. The low battery reminder message includes the first tag identifier and the battery value to remind the user that the battery of the electronic tag identified by the first tag identifier is low.

[0143] For another example, if the error code in the error code information in the first tag information is an error code indicating a firmware abnormality, a firmware abnormality reminder message can be sent to the user account. The firmware abnormality reminder message includes the first tag identifier, the error code and the firmware abnormality indication information to remind the user that a firmware abnormality has occurred in the first electronic tag identified by the first tag identifier.

[0144] In some cases, for any tag identifier in the first set, the gateway can detect whether the electronic tag identified by the tag identifier is offline, so as to promptly inform the cloud platform that the electronic tag is offline if there is an offline electronic tag in the first set.

[0145] For example, for any tag identifier in the first set, the gateway can determine that the electronic tag identified by the tag identifier is offline if the time indicated by the timestamp in the tag status corresponding to the tag identifier is greater than or equal to the first preset time length from the current time.

[0146] The first preset duration can be pre-set. For example, the first preset duration can be set to 30s, 31s, or 32s, etc., which is not limited in this embodiment of the present application.

[0147] If the time indicated by the timestamp in the tag status corresponding to the tag identifier is greater than or equal to the first preset time length from the current time, it means that the electronic tag identified by the tag identifier has not sent tag information within the first preset time length after the time indicated by the timestamp, so it can be determined that the electronic tag is offline; if the time indicated by the timestamp in the tag status corresponding to the tag identifier is less than the first preset time length from the current time, it means that the electronic tag identified by the tag identifier has sent tag information within the first preset time length after the time indicated by the timestamp, so it can be determined that the electronic tag is online.

[0148] In some embodiments, for any tag identifier in the first set, the gateway deletes the tag information belonging to the tag identifier in the first set when the electronic tag identified by the tag identifier is offline; and sends an offline reminder message to the cloud platform, and the offline reminder message includes the tag identifier.

[0149] In some cases, after receiving the offline reminder message sent by the gateway, the cloud platform may delete the tag information to which the tag identifier belongs in the second set corresponding to the gateway.

[0150] In other cases, after the cloud platform receives the offline reminder message sent by the gateway, if the tag identifier only exists in the second set corresponding to the gateway, the tag information to which the tag identifier belongs in the second set corresponding to the gateway may be deleted.

[0151] For any tag identifier, if the tag identifier exists in multiple second sets, when the cloud platform receives offline reminder messages for the tag identifier sent by at least two gateways within the third preset time period, it can delete the tag information belonging to the tag identifier in the second set corresponding to each of the at least two gateways.

[0152] The third preset duration can be set in advance.

[0153] An electronic tag may be within the communication range of multiple gateways. Each of these multiple gateways can receive tag information sent by the electronic tag, and the multiple second sets corresponding to these multiple gateways all include the tag information of the electronic tag. In this case, if the cloud platform receives offline reminder messages for the tag identifier of the electronic tag from at least two gateways within a third preset time period, it indicates that the electronic tag is likely offline, and therefore the tag information corresponding to the tag identifier in the second set corresponding to each of the at least two gateways can be deleted.

[0154] If the cloud platform only receives an offline reminder message for the tag identifier from one gateway within the third preset time period, it means that the electronic tag identified by the tag identifier may not be offline, so the tag information belonging to the tag identifier in the second set corresponding to the gateway will not be deleted for the time being.

[0155] Optionally, if a tag identifier exists in multiple second sets corresponding to multiple gateways, the cloud platform can delete the tag information belonging to the tag identifier in the second set corresponding to each gateway in the multiple gateways when it receives offline reminder messages for the tag identifier sent by all gateways in the multiple gateways within a third preset time period.

[0156] Optionally, for any one of the n gateways, such as Figure 5As shown, the cloud platform can send a synchronization instruction to the gateway. After receiving the synchronization instruction, the gateway sends all the tag information in the first set to the cloud platform. After receiving the tag information sent by the gateway, the cloud platform can update the tag information in the second set corresponding to the gateway accordingly. In this way, the consistency of the tag information in the first set and the second set can be guaranteed.

[0157] For example, the time when the cloud platform sends the synchronization instruction can be pre-set. For example, the gateway can send the synchronization instruction at relatively idle times such as 2 o'clock, 3 o'clock, and 4 o'clock every day, which is not limited in this embodiment of the present application.

[0158] In an embodiment of the present application, the gateway receives the first tag information sent by the first electronic tag, and the first tag information includes a first tag identifier and a first tag status. Afterwards, it is determined whether the first electronic tag meets the first preset abnormal condition based on the first tag status. In the case that the first electronic tag meets the first preset abnormal condition, the first tag information is sent to the cloud platform; in the case that the first electronic tag does not meet the first preset abnormal condition, the first tag information is not sent to the cloud platform. In an embodiment of the present application, the gateway only sends the tag information of the electronic tags that are likely to be abnormal to the cloud platform for monitoring. In this way, while meeting the electronic tag monitoring needs, the processing pressure of the cloud platform can be reduced, the load of the cloud platform can be reduced, the efficiency of the cloud platform in monitoring electronic tags can be improved, and the performance of the cloud platform can be guaranteed.

[0159] Figure 6 This is a schematic diagram of the structure of a tag information sending device provided by an embodiment of the present application. The device can be implemented as part or all of a computer device by software, hardware, or a combination of both. The computer device can be the following Figure 7 Computer equipment shown. Figure 6 The device includes: a first receiving module 601, a first determining module 602, a first sending module 603, and an ending module 604.

[0160] A first receiving module 601 is configured to receive first tag information sent by a first electronic tag, where the first tag information includes a first tag identifier and a first tag status;

[0161] A first determining module 602 is configured to determine whether the first electronic tag satisfies a first preset abnormal condition according to the first tag state;

[0162] A first sending module 603 is configured to send first tag information to the cloud platform when the first electronic tag meets a first preset abnormal condition;

[0163] The end module 604 does not send the first tag information to the cloud platform when the first tag state does not meet the first preset abnormal condition.

[0164] Optionally, the first tag information further includes a manufacturer identifier, and the determining module 602 is configured to:

[0165] In a case where the manufacturer identifier is a preset manufacturer identifier, it is determined whether the first electronic tag meets a first preset abnormal condition according to the first tag state.

[0166] Optionally, the determining module 602 is configured to:

[0167] When the first tag identifier exists in the first set, determining whether the first electronic tag meets a first preset abnormal condition according to the first tag state;

[0168] Optionally, the device further comprises:

[0169] A first adding module, configured to add the first tag information to the first set if the first tag identifier does not exist in the first set;

[0170] The second sending module is used to send the first tag information to the cloud platform.

[0171] Optionally, the device further comprises:

[0172] The updating module is configured to update the tag state corresponding to the first tag identifier in the first set according to the first tag state when the first tag identifier exists in the first set.

[0173] Optionally, the device further comprises:

[0174] a deleting module configured to, for any tag identifier in the first set, delete the tag information belonging to the tag identifier in the first set when the electronic tag identified by the tag identifier is offline;

[0175] The third sending module is used to send an offline reminder message to the cloud platform, where the offline reminder message includes the tag identifier.

[0176] Optionally, the tag state includes a timestamp, and the apparatus further includes:

[0177] The second determination module is used to determine that the electronic tag identified by any tag identifier in the first set is offline when the time indicated by the timestamp in the tag state corresponding to the tag identifier is greater than or equal to the first preset time length from the current time.

[0178] Optionally, the device further comprises:

[0179] A startup module, configured to enter a scanning mode after startup, wherein the duration of the scanning mode is a second preset duration;

[0180] A second receiving module is configured to receive, in the scanning mode, second tag information sent by each of the one or more second electronic tags, where the second tag information includes a second tag identifier and a second tag status;

[0181] a second adding module, configured to, upon receiving second tag information sent by a second electronic tag, add the second tag information to the first set if the second tag identifier in the second tag information does not exist in the first set, and update the tag state in the first set corresponding to the second tag identifier in the second tag information according to the second tag state in the second tag information if the second tag identifier in the second tag information exists in the first set;

[0182] The fourth sending module is used to send all tag information in the first set to the cloud platform when the scanning mode ends.

[0183] In an embodiment of the present application, first tag information sent by a first electronic tag is received, and the first tag information includes a first tag identifier and a first tag status. Afterwards, whether the first electronic tag satisfies a first preset abnormal condition is determined based on the first tag status. If the first electronic tag satisfies the first preset abnormal condition, the first tag information is sent to the cloud platform. If the first electronic tag does not satisfy the first preset abnormal condition, the first tag information is not sent to the cloud platform. In an embodiment of the present application, the gateway only sends the tag information of electronic tags that are likely to be abnormal to the cloud platform for monitoring. In this way, while meeting the electronic tag monitoring needs, the processing pressure of the cloud platform can be reduced, the load of the cloud platform can be reduced, the efficiency of the cloud platform in monitoring electronic tags can be improved, and the performance of the cloud platform can be guaranteed.

[0184] It should be noted that the label information sending device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example when sending label information. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0185] The functional modules in the above embodiments may be integrated into a single processing unit, or each functional module may exist physically as a separate processing unit, or two or more functional modules may be integrated into a single processing unit. The above processing unit may be implemented in either hardware or software. Furthermore, the specific names of the functional modules are merely for the purpose of distinguishing them from one another and are not intended to limit the scope of protection of the embodiments of this application.

[0186] The tag information sending device and the tag information sending method provided in the above embodiments belong to the same concept. The specific working process of the functional modules in the above embodiments and the technical effects brought about can be found in the method embodiment part and will not be repeated here.

[0187] Figure 7 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. Figure 7 As shown, the computer device 7 includes: a processor 70, a memory 71, and a computer program 72 stored in the memory 71 and executable on the processor 70. When the processor 70 executes the computer program 72, the steps of the tag information sending method in the above embodiment are implemented.

[0188] The computer device 7 may be a gateway. Those skilled in the art will appreciate that Figure 7 This is merely an example of the computer device 7 and does not constitute a limitation on the computer device 7 . The computer device 7 may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the computer device 7 may also include input and output devices, network access devices, etc.

[0189] The processor 70 may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0190] In some embodiments, the memory 71 may be an internal storage unit of the computer device 7, such as a hard disk or memory of the computer device 7. In other embodiments, the memory 71 may also be an external storage device of the computer device 7, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the computer device 7. Furthermore, the memory 71 may include both an internal storage unit of the computer device 7 and an external storage device. The memory 71 is used to store an operating system, application programs, a boot loader, data, and other programs. The memory 71 may also be used to temporarily store data that has been output or is about to be output.

[0191] An embodiment of the present application also provides a computer device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor implements the steps of any of the above-mentioned method embodiments when executing the computer program.

[0192] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0193] An embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the steps in the above-mentioned various method embodiments.

[0194] If the integrated unit is implemented as a software functional unit and sold or used as a standalone product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application can implement all or part of the processes in the above-mentioned method embodiments by using a computer program to instruct the relevant hardware. The computer program can be stored in a computer-readable storage medium. When executed by a processor, the computer program can implement the steps of each of the above-mentioned method embodiments. The computer program includes computer program code, which can be in source code form, object code form, an executable file, or some intermediate form. The computer-readable medium can include at least: any entity or device capable of carrying the computer program code to a camera / terminal device, a recording medium, computer memory, ROM (read-only memory), RAM (random access memory), CD-ROM (compact disc read-only memory), magnetic tape, floppy disk, and optical data storage device. The computer-readable storage medium mentioned in the present application can be a non-volatile storage medium, in other words, a non-transitory storage medium.

[0195] It should be understood that all or part of the steps for implementing the above embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the steps may be implemented in the form of a computer program product. The computer program product may include one or more computer instructions. The computer instructions may be stored in the above-mentioned computer-readable storage medium.

[0196] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0197] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0198] In the embodiments provided in this application, it should be understood that the disclosed apparatus / computer equipment and methods can be implemented in other ways. For example, the apparatus / computer equipment embodiments described above are merely schematic. For example, the division of modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of the apparatus or unit, which can be electrical, mechanical or other forms.

[0199] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0200] It should be noted that the user information (including but not limited to user tag information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant regulations and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0201] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A tag information sending method, characterized in that: Applied to any one of n gateways, the n gateways corresponding one-to-one to n groups of electronic tags, each of the n gateways communicating with a corresponding group of electronic tags, where n is an integer greater than or equal to 2, the method comprising: receiving first tag information sent by a first electronic tag, where the first tag information includes a first tag identifier and a first tag status; determining whether the first electronic tag meets a first preset abnormal condition according to the first tag state; When the first electronic tag meets the first preset abnormal condition, sending the first tag information to the cloud platform; If the first electronic tag does not meet the first preset abnormal condition, the first tag information is not sent to the cloud platform.

2. The method according to claim 1, wherein The first tag information further includes a manufacturer identifier. Determining whether the first electronic tag meets a first preset abnormal condition based on the first tag status includes: In a case where the manufacturer identifier is a preset manufacturer identifier, it is determined whether the first electronic tag meets the first preset abnormal condition according to the first tag state.

3. The method according to claim 1, wherein The determining, according to the first tag state, whether the first electronic tag meets a first preset abnormal condition includes: If the first tag identifier exists in the first set, determining whether the first electronic tag meets the first preset abnormal condition according to the first tag state; The method further comprises: If the first tag identifier does not exist in the first set, adding the first tag information to the first set; Send the first tag information to the cloud platform.

4. The method according to claim 3, wherein After receiving the first tag information sent by the first electronic tag, the method further includes: In a case where the first tag identifier exists in the first set, the tag status corresponding to the first tag identifier in the first set is updated according to the first tag status.

5. The method according to claim 3, wherein The method further comprises: For any tag identifier in the first set, when the electronic tag identified by the tag identifier is offline, deleting the tag information to which the tag identifier in the first set belongs; An offline reminder message is sent to the cloud platform, where the offline reminder message includes the tag identifier.

6. The method according to claim 5, wherein The tag state includes a timestamp, and the method further includes: For any tag identifier in the first set, if the time indicated by the timestamp in the tag state corresponding to the tag identifier is greater than or equal to the first preset time length from the current time, it is determined that the electronic tag identified by the tag identifier is offline.

7. The method according to any one of claims 1 to 6, characterized in that: Before receiving the first tag information sent by the first electronic tag, the method further includes: After starting, the system enters a scanning mode, and the duration of the scanning mode is a second preset duration; In the scanning mode, receiving second tag information sent by each of the one or more second electronic tags, the second tag information including a second tag identifier and a second tag status; Whenever second label information sent by a second electronic label is received, if the second label identifier in the second label information does not exist in the first set, the second label information is added to the first set; if the second label identifier in the second label information exists in the first set, the label state corresponding to the second label identifier in the second label information in the first set is updated according to the second label state in the second label information; When the scanning mode ends, all tag information in the first set is sent to the cloud platform.

8. A computer device, characterized in that: The computer device includes a memory, a processor, and a computer program stored in the memory and running on the processor, and when the computer program is executed by the processor, the method according to any one of claims 1 to 7 is implemented.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer program product, characterized in that When the computer program product is run on a computer device, the computer device is caused to perform the method according to any one of claims 1 to 7.

Images