CN218585344U - Product tracking device, cover and product tracking system - Google Patents
Product tracking device, cover and product tracking system Download PDFInfo
- Publication number
- CN218585344U CN218585344U CN202221189625.3U CN202221189625U CN218585344U CN 218585344 U CN218585344 U CN 218585344U CN 202221189625 U CN202221189625 U CN 202221189625U CN 218585344 U CN218585344 U CN 218585344U
- Authority
- CN
- China
- Prior art keywords
- information
- client device
- product tracking
- product
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Abstract
The present disclosure relates to a product tracking apparatus, a cap and a product tracking system. The product tracking device includes: a trigger lead configured to be broken when a packaging structure of a product is opened; a wake-up circuit connected to the trigger lead and configured to generate a wake-up signal in response to the trigger lead being disconnected; and communication circuitry configured to transmit the device information in response to the wake-up signal.
Description
Technical Field
The present disclosure relates to the field of computer technology, and more particularly, to a product tracking device, a cover, and a product tracking system.
Background
In consumer product industries such as the wine industry, luxury goods industry, food industry, etc., there are often problems of unclear inventory, fleeing goods by dealers, production of counterfeit articles from raw packaging, etc. Therefore, there is a need in these industries to locate consumer products in order to monitor the logistics, inventory, consumption status, etc. of the products. However, in the related art, the devices for localization tracking generally have a large size and high power consumption, and it is difficult to meet the requirements of miniaturization and low power consumption in many application scenarios.
SUMMERY OF THE UTILITY MODEL
In view of the above, the present disclosure provides a product tracking device, a cover and a product tracking system that may alleviate, reduce or even eliminate the above-mentioned problems.
According to an aspect of the present disclosure, there is provided a product tracking device for installation in a packaging structure for a product, the product tracking device comprising: a trigger lead configured to be broken when a packaging structure of a product is opened; a wake-up circuit connected to the trigger lead and configured to generate a wake-up signal in response to the trigger lead being disconnected; and communication circuitry configured to transmit the device information in response to the wake-up signal.
In some embodiments, the trigger lead includes two leads connected by a severable conductor that is severed when the packaging structure of the product is opened.
In some embodiments, the product tracking device further comprises: the circuit board is provided with a wake-up circuit and a communication circuit; and a housing surrounding the circuit board and including a lead opening through which the trigger lead extends from the circuit board to outside the case.
In some embodiments, the product tracking device further comprises: an electronic tag attached on an exterior surface of the housing. In some embodiments, the electronic tag comprises at least one of an RFID tag and an NFC tag.
In some embodiments, the product tracking device further comprises: an antenna connected to the communication circuit and configured to transmit device information from the communication circuit to a server. In some embodiments, the antenna is connected to the communication circuit through a pogo pin interface.
In some embodiments, the product tracking device further comprises: a battery configured to power at least one of the wake-up circuit and the communication circuit. In some embodiments, the battery is a lithium thionyl chloride battery.
In some embodiments, the communication circuit comprises a narrowband internet of things chip.
In some embodiments, the product tracking device further comprises: a clock circuit connected to the communication circuit and configured to generate a clock signal, wherein the communication circuit is further configured to transmit the device information in response to the clock signal indicating that a predetermined time interval has been reached since a last trigger.
According to another aspect of the present disclosure, there is provided a cap including a cap body; and a product tracking device attached to the cap body and including: a trigger lead configured to be disconnected when the cover main body is opened; a wake-up circuit connected to the trigger lead and configured to generate a wake-up signal in response to the trigger lead being disconnected; and communication circuitry configured to transmit the device information in response to the wake-up signal.
In some embodiments, the cap body comprises: an inner cover including an inner cover sidewall surrounding the cavity; an outer cover including an outer cover sidewall, the outer cover sidewall surrounding at least a portion of the inner cover sidewall; a severable conductor film extending at least between the outer cover sidewall and the inner cover sidewall, connected to the trigger lead, and configured to be severed when the cover body is opened.
In some embodiments, at least one of the inner cap sidewall, the outer cap sidewall, and the severable conductor film has a frangible hole forming a loop line.
In some embodiments, the trigger lead includes two leads, one of the two leads connected to the severable conductor film on one side of the frangible hole and the other of the two leads connected to the severable conductor film on the other side of the frangible hole.
In some embodiments, there is at least one lead slot between the severable conductor film and the cover sidewall, and wherein the trigger lead is received in the at least one lead slot.
In some embodiments, the outer lid further comprises an outer lid top wall enclosing the cavity at one end of the outer lid side wall, and wherein the product tracking device is attached to a side of the outer lid top wall facing the cavity.
In some embodiments, the lid further comprises a partition plate attached to the product tracking device, and the partition plate together with the outer lid top wall, the outer lid side walls define a sub-cavity containing the product tracking device.
According to yet another aspect of the present disclosure, there is provided a product tracking system including: the product tracking device described in accordance with the preceding aspect; a server configured to receive device information from the product tracking device and locate the product tracking device based on the device information.
In some embodiments, the product tracking system further comprises: a management platform configured to receive input instructions and manage a product tracking device based on the received input instructions.
These and other aspects of the disclosure will be apparent from and elucidated with reference to the embodiments described hereinafter.
Drawings
Further details, features and advantages of the disclosure are disclosed in the following description of exemplary embodiments, taken in conjunction with the accompanying drawings, in which:
fig. 1 schematically illustrates an example scenario in which aspects of some embodiments of the present disclosure may be applied;
FIG. 2 schematically illustrates an example flow diagram of a product tracking method for a client device, in accordance with some embodiments of the present disclosure;
3A-3B illustrate schematic diagrams of trigger structures in a product package, according to some embodiments of the present disclosure;
FIG. 4 illustrates a schematic diagram of a product package opening process according to some embodiments of the present disclosure;
fig. 5 schematically illustrates an example flow diagram of a product tracking method for a server-side device in accordance with some embodiments of the present disclosure;
fig. 6 schematically illustrates an example flow diagram of a client device management method in accordance with some embodiments of the present disclosure;
7A-7H schematically illustrate example interface diagrams for managing client devices, according to some embodiments of the present disclosure;
FIG. 8 schematically illustrates an example flow diagram of a product tracking process in accordance with some embodiments of this disclosure;
FIG. 9 schematically illustrates an example block diagram of a product tracking apparatus for a client device, in accordance with some embodiments of the present disclosure;
fig. 10 schematically illustrates an example block diagram of a product tracking apparatus for a server-side device, in accordance with some embodiments of the present disclosure;
fig. 11 schematically illustrates an example block diagram of a client device management apparatus in accordance with some embodiments of this disclosure;
FIG. 12 schematically illustrates an example block diagram of a product tracking system in accordance with some embodiments of the present disclosure;
fig. 13 schematically illustrates an example block diagram of a computing device in accordance with some embodiments of the disclosure;
FIG. 14 schematically illustrates an example block diagram of a product tracking device in accordance with some embodiments of this disclosure;
fig. 15 schematically illustrates an example circuit board, in accordance with some embodiments of the present disclosure;
fig. 16 schematically illustrates an example block diagram of a cover, in accordance with some embodiments of this disclosure; and
fig. 17 schematically illustrates an example block diagram of a product tracking system in accordance with some embodiments of this disclosure.
Detailed Description
Fig. 1 schematically illustrates an example application scenario 100 in which aspects of some embodiments of the present disclosure may be applied.
As shown in fig. 1, the application scenario 100 includes a client device 110. The client device 110 may be installed in a packaging structure of a product, for example, in a bottle or cap (or tank or cap, etc.) such as wine or other beverages, cosmetics, etc., a pilfer proof button such as clothing, jewelry, or bags, etc., and the like. The client Device 110 may be implemented by a Printed Circuit Board (PCB), a Flexible Circuit Board (FPC), a System on Chip (SoC), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), or a similar hardware structure, or may be implemented by a combination of one or more of the above structures.
In some embodiments, client device 110 may include one or more of a chip 111, an antenna 112, and a power supply 113, and may optionally include other devices or structures. Illustratively, the chip 111 may implement functions of switching from a sleep state to a communication state, monitoring the opening condition of a product packaging structure, sending device information, receiving feedback information, and the like, independently or together with peripheral circuits. For example, the chip 111 may be a miniaturized, low power consumption NB-IOT (Narrow Band-Internet of Things) chip or the like, such as an XY1100 chip or the like. The antenna 112 may be used for transceiving signals (e.g., NB signals), may be implemented as, for example, a custom FPC antenna, or the like. Power source 113 may be used to power chip 111, antenna 112, and/or other devices or structures of client device 110, and may be implemented as a disposable battery, a rechargeable battery, a solar cell, etc. For example, the power source 113 may be a custom made lithium thionyl chloride high energy density battery or the like.
In some embodiments, the client device 110 may be attached with an Identification code device such as a two-dimensional code, a barcode, a Radio Frequency Identification (RFID) tag, a Near Field Communication (NFC) tag, and the like, and the user 120 may scan the Identification code device using its terminal device 122 (e.g., a smart phone, a tablet computer, a smart watch, smart glasses, and the like) to read information related to the client device 110 or a product, such as a product name, a manufacturer, a production time, a historical transportation track, an open state, and the like, or may write information, such as purchase information, personal information, and the like related to the user 120. Alternatively, some or all of this readable or writable information may be stored in the identification code device itself, in the client device 110, or sent to a server-side device (or simply server).
The application scenario 100 also includes a server 130. Illustratively, the server 130 may receive device information from one or more client devices 110, locate, send feedback information to, or the like, the one or more client devices 110. The server 130 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, middleware service, a domain name service, a security service, a CDN, a big data and artificial intelligence platform, and the like. Further, it should be understood that server 130 is shown by way of example only and that other devices or combinations of devices having computing and storage capabilities may alternatively or additionally be used to provide corresponding services.
In some embodiments, the application scenario 100 may also include a management platform device 140. The management platform device 140 may be used to manage the client device 110, such as to obtain location information of the client device 110 from the server 130 and record and analyze the location information, receive various control inputs from the user 142 (such as viewing location data, adjusting communication latency of the client device, etc.), and send control instructions to the server 130 based on the control inputs, etc. The management platform device 140 may be implemented as various computing devices, such as a desktop computer, a notebook computer, a tablet computer, a smart phone, etc., depending on the particular application requirements. The management platform device 140 may be connected with the server 130 via a wired or wireless network, such as a wired network via cable, fiber, etc., or a wireless network via 2G, 3G, 4G, 5G, wi-Fi, bluetooth, zigBee, li-Fi, etc.
The client device 110 may be connected to the server 130 via a network 150. The network 150 may be a wired network connected via a cable, an optical fiber, or the like, or may be a wireless network such as 2G, 3G, 4G, 5G, wi-Fi, bluetooth, zigBee, li-Fi, or the like, or may be a combination of one or more of the above networks. In embodiments where client device 110 includes an NB-IOT chip, network 150 may be a cellular communication network such as 2G, 3G, 4G, 5G, and so forth.
Fig. 2 schematically illustrates an example flow diagram of a product tracking method 200 for a client device, where the client device may be installed in a packaging structure for a product, in accordance with some embodiments of the present disclosure. Illustratively, the product tracing method 200 may be deployed on the client device 110 in the scenario 100 shown in FIG. 1.
Specifically, in step 210, in response to reaching a predetermined time interval from the last trigger, the client device is switched from the sleep state to the communication state, and first device information is sent to the server, the first device information including a device identification of the client device.
Illustratively, when a client device is in a communication state, it may support a data transfer function, e.g., it may connect with and send or receive data to or from a server or other external device; when the client device is in a dormant state, it may not support data transfer functionality, but maintain only a small number of necessary functions, such as timing functionality, packaging structure monitoring functionality, and the like. Thus, when a client device is in a sleep state, its power consumption may be substantially reduced compared to the communication state, e.g., only about 1/100, 1/1000, 1/2000, 1/3000 or less of the power consumption of the communication state.
Illustratively, whether the predetermined time interval has been reached since the last trigger may be determined by various mechanical or electronic timing devices. For example, the timer device may be implemented by a crystal oscillator circuit, an RC (resistive-capacitive) oscillator, an MEMS (Micro-Electro-Mechanical System) clock oscillator, or the like. Alternatively, the predetermined time interval may be set or modified by a manufacturer of the client device, a product manager, a product consumer, and the like. The predetermined time interval may be set to, for example, 6 hours, 12 hours, 1 day, 2 days, or other time lengths, depending on actual demand. Alternatively, the predetermined time interval may be set indirectly by setting a frequency or the like.
Illustratively, the device identification of the client device may be a predetermined string of one or more of numbers, letters, symbols, or other characters that can be used to uniquely identify the corresponding client device, and thus the corresponding product. For example, the device identifier may be one or more of an IMEI (International Mobile Equipment Identity) number, an ICCID (integrated Circuit Card Identity) number, an IMIS (Internet Management Information System) number, and the like. Optionally, the first device information may include other information besides the device identification, such as device power information, monitored product package opening status, a timestamp, current signal strength information, and the like. Illustratively, the client device may store address information of the server in advance, such as a Uniform Resource Locator (URL) address, an Internet Protocol (IP) address, and the like, so that the server may be accessed and the first device information may be transmitted based on the address information.
In step 220, in response to receiving positioning feedback information from the server, the client device is switched from the communication state to the sleep state, wherein the positioning feedback information includes information indicating that the client device has been positioned. Illustratively, the positioning feedback information may include an identifier indicating whether the client device was successfully positioned, e.g., may be represented by one or more characters; alternatively, the positioning feedback information itself may indicate that the client device has been successfully positioned, for example, the server may send the positioning feedback information only when the client device has been successfully positioned, in which case, the positioning feedback information may include any character content, even not include any specific character content, according to the specific application requirements. For example, after receiving the first device information sent by the client device, the server may determine the location of the client device according to a base station, a gateway, and the like used when the client device connects to the server; alternatively, where the first device information includes signal characteristic information such as the current signal strength of the client device, the location of the client device may also be determined based on signal fingerprinting techniques; alternatively, in the case where the first device information includes information related to positioning, the position of the client device may be determined directly based on the positioning-related information; and so on. Furthermore, positioning the client device may refer to determining an accurate location (e.g., latitude and longitude coordinates, etc.) or a local area (e.g., latitude and longitude coordinate range, city, county, street or cell, etc.) of the client device according to actual application requirements.
After the client device reverts to the hibernation state, it may be triggered again when the trigger condition is satisfied. For example, when the client device is triggered by the satisfaction of the predetermined time interval condition, it may be triggered again after the predetermined time interval after being restored to the hibernation state, or may be triggered by the packaging structure being opened.
In step 230, in response to monitoring that the packaging structure is opened, the client device is switched from the dormant state to the communication state and/or the communication state is maintained, and second device information is sent to a server, wherein the second device information comprises a device identification of the client device and information indicating that the packaging structure is opened.
For example, monitoring whether the packaging structure is opened may be accomplished by mechanical and/or electrical circuit structures. For example, whether the packaging structure is opened or not may be monitored by an external monitoring device, which may send a trigger signal to trigger a state switch of the client device when the packaging structure is opened; alternatively, a lead structure connected to the client device may be arranged at the opening portion of the packaging structure, such that the lead is subsequently broken when the packaging structure is opened, thereby triggering the state switching of the client device; alternatively, sensing means, such as a light-sensitive sensor or the like, connected to the client device may be arranged in the packaging structure such that when the packaging is opened, the sensing means may generate an electrical signal to trigger a state switch of the client device; and so on.
For example, when the client device is triggered by the packaging structure being opened, if the client device is in a sleep state, the client device may be switched from the sleep state to a communication state; if the client device is in the communication state, the client device may maintain the communication state to transmit the second device information. After the second device information is sent, if the power of the device allows, the second device information may also be restored to the hibernation state to be triggered again when the predetermined time interval condition is met, or alternatively, the client device may also take other operations, such as automatically turning off, automatically destroying, or continuing to maintain the communication state until the power is exhausted. It should be understood that in embodiments of the present disclosure, the triggering condition that the packaging structure is opened occurs only once, e.g., whether the packaging structure is opened can be monitored by whether the associated lead is broken, which is irreversible, as will be described in detail below. Therefore, the product tracking method provided by the embodiment of the disclosure is beneficial to avoiding the phenomena that the packaging structure is recycled to manufacture fake products and the like.
Illustratively, the second device information may include an identifier indicating that the packaging structure is opened, and optionally a timestamp or the like representing the current time. Alternatively, the second device information may not include a timestamp, but rather the server determines the time at which the packaging structure was opened based on the time at which the second device information was received. Therefore, the function of monitoring the opening state and the opening time of the product package in real time can be realized.
With the product tracking method 200 provided by the present disclosure, when a timing condition is satisfied, a client device installed in a product packaging structure may be switched from a sleep state to a communication state and send first device information to a server, and then, when positioning feedback information from the server is received, the client device may be restored to the sleep state. And when the product package is monitored to be opened, the client device can be switched to the communication state from the dormant state and/or the communication state is maintained, and second device information is sent to the server, wherein the second device information can additionally comprise information indicating that the package structure is opened compared with the first device information. Thus, the function of regularly monitoring the position of the device can be realized, and whether the product package is opened or not (i.e., whether the product is used or not) can be monitored in real time. Meanwhile, the client device is triggered to be in a communication state only when the device information needs to be sent, and is in a dormant state when the device information is not triggered, so that the power consumption of the client device can be effectively reduced. This helps to extend the operating time of the client device in the case of disposable batteries. Furthermore, in the case where the client device is located by the server, there may be no need to deploy a more complicated or power-consuming locating device at the client device, which helps to simplify the structure of the client device and further reduce its power consumption.
It should be understood that although steps 210-230 of the product tracking method 200 are shown and described sequentially, this does not imply that these steps must be performed in the order shown or described, and that there may be other optional steps between the two steps shown or described sequentially.
Illustratively, the package structure can be monitored for opening via the structures shown in FIGS. 3A-3B. As shown, fig. 3A-3B illustrate a monitoring structure for monitoring whether a packaging structure is opened, taking a bottle cap (e.g., a wine bottle cap) as an example.
As shown in fig. 3A, the vial cap 300A includes an outer cap 310, an inner cap 320, and a severable conductor film 330 therebetween. Illustratively, the outer cover 310 and the inner cover 320 may be made of resin, glass, or other non-conductive material, and the severable conductor film 330 may be an aluminum film, such as a film made of aluminum or an aluminum alloy, which may have a thickness of, for example, 0.5 mm or other thickness. Alternatively, a thin film made of other electrically conductive material may be used in addition to the aluminum film. As shown, the inner lid 320 can include an inner lid sidewall surrounding a cavity, the outer lid 310 can include an outer lid sidewall surrounding at least a portion of the inner lid sidewall outside of the inner lid 320, and the severable conductor film 330 can extend at least between the outer lid sidewall and the inner lid sidewall.
At least one of the inner cover sidewall, the outer cover sidewall, and the severable conductor film may have a frangible hole 340. The breakable hole 340 may form a loop and divide the outer cap 310, the inner cap 320, and/or the severable conductor membrane 330 into upper and lower portions. Illustratively, the loop line formed by the breakable hole 340 may be in a plane perpendicular to the direction of elongation of the cover 300A, or may be in other planes or curved surfaces that do not include the direction of elongation. Frangible hole 340 can have a variety of forms. Illustratively, a circle of hole structures may be previously punched at the position indicated by reference numeral 340 so that the bottle cap 300A is easily broken thereat, or other operations may be performed at this position, such as processing the outer cap and/or the inner cap near this position into a hollow structure or a thin-walled structure so that the bottle cap 300A is easily broken thereat, and so on. Illustratively, the outer cap 310 and/or the inner cap 320 may be opened by breaking the outer cap 310 and/or the inner cap at the frangible hole 340 by rotating the vial cap 300A. As the outer cover 310 and/or the inner cover 320 are broken at the frangible hole 340, the severable conductor film 330 may be severed, thereby severing the trigger lead associated therewith. The client device 350 may be glued or otherwise secured to the inside top of the cover 310. There may also be at least one lead groove 360 between the outer cover 310 and the inner cover 320. The trigger lead may be received in at least one lead slot 360. Alternatively, the lead slots 360 may be an asymmetric slot configuration as shown in fig. 3A, with one side longer and the other shorter, or may be symmetrical, or there may be only a single lead slot.
Illustratively, the client device 350 may have a chip therein that includes a wake-up pin to which a wake-up circuit may be connected, which may extend out of a trigger lead that includes two leads that may extend through the lead slot 360 and be secured to the severable conductor film 330 by conductive glue, e.g., one lead may be secured to the severable conductor film 330 above the frangible hole 340 and the other lead may be secured to the severable conductor film 330 below the frangible hole 340. The wake-up circuit may be designed to: when the bottle cap 300A is not opened, the two leads may be shorted by the severable conductor film 330, causing the wake-up pin to be at a high level (or vice versa), causing the client device 350 to be in a dormant state; when the cap 300A is opened, the cap 300A is broken at the breakable hole 340, the breakable conductor film 330 is broken, and the connection between the two leads is broken, so that the level of the wake-up pin is pulled low by the pull-down resistor (or vice versa), thereby waking up the client device 350 to the communication state. Further, illustratively, the client device 350 can include an antenna (such as an NB antenna, etc.) that can be connected to a circuit board in the client device 350 via, for example, a pogo pin interface, and can be at least partially housed, for example, in the lead slot 360.
Alternatively, the client device 350 may include a housing that may be secured to the cover 310 by an adhesive glue. Illustratively, the housing may be made of a material such as a photosensitive resin and may have an opening such that the lead and/or antenna may extend from the housing through the opening into, for example, lead slot 360. Optionally, an RFID, NFC tag, or the like may also be affixed at the client device 350 so that a user may scan these tags using a terminal device such as a smartphone to obtain device information (e.g., device identification and/or other information such as an IMEI number) or write other information. Illustratively, the RFID, NFC tag may be affixed to the housing of the client device 350, e.g., on the top, sides, bottom, etc. thereof.
Illustratively, the outer lid 310 may include an outer lid top wall that encloses the cavity at one end of the outer lid side wall, and a product tracking device (e.g., a housing of the product tracking device) may be attached to a side of the outer lid top wall that faces the cavity. Optionally, the client device 350 or its housing may have a divider 370 thereunder that may be glued or otherwise attached to the product tracking device and may, together with the outer lid top wall, outer lid side walls, define an subcavity that houses the product tracking device. The isolation plate 370 may be made of the same material as the inner lid 320, or may be made of other glass or resin-like materials to isolate the client device 350 from the liquid, powder, paste, etc. in the bottle cavity, so as to protect the circuit structure in the client device 350 while ensuring that the contents of the bottle cavity are not contaminated. Optionally, the isolation plate 370 may be clear of the lead slot 360 or have an opening so that the lead may extend into the lead slot 360. Optionally, the client device 350 may further include or be connected to a sensing device that detects the usage or remaining amount of the product, so as to monitor the usage or remaining amount of the product; alternatively, the client device 350 may include or be connected to other means for obtaining more product-related information. Alternatively, the related information may be included in the first and/or second device information and transmitted to the server. Further, optionally, the cover 310 may be painted with identification codes such as two-dimensional codes or bar codes so that the user can acquire client device or product information or the like by scanning the identification codes.
Illustratively, fig. 3B schematically illustrates example dimensions of a vial cap 300B. As shown in the drawing, the diameter D1 of the first portion of the upper side of the outer cap may be 40 mm, the diameter D2 of the second portion of the lower side may be 35 mm, the height L1 of the first portion may be 16 mm, the height L2 of the bottom side of the second portion to the breakable hole may be 40 mm, and the height L3 of the top side of the second portion to the breakable hole may be 5 mm. In such an example, the client device is required to be of a smaller size in order to be accommodated in the bottle cap 300B. By simplifying the operation of the client device and reducing its power consumption requirements, various structures in the client device provided according to some embodiments of the present disclosure may be customized to the following dimensions. Illustratively, the chips and peripheral circuitry in the client device may be arranged on a circular or near-circular PCB, which may be fabricated to be less than or equal to 2 mm in thickness and less than or equal to 25 mm in diameter; the power supply for powering the PCB may be a custom button cell sized to 24 mm in diameter, 3 mm in thickness, 3.6V in output voltage, and 200 mAH in charge or higher; the housing may be 27 mm in diameter and 6 mm thick. It should be understood that the above dimensions are merely exemplary, and in fact, client devices and associated structures of different sizes may be designed depending on the particular application.
Fig. 4 schematically illustrates an opening process of the bottle cap 400. Similarly as described above, by rotating the upper portion of the vial cap 400, the outer cap 410 and/or the inner cap 420 may be broken at the frangible hole 450 such that the two leads 440 may be changed from a shorted state to an open state, thereby triggering the client device 430 to switch from the dormant state to the communication state.
In some embodiments, the first device information transmitted in step 210 may include first device connection information and first device state information, and step 210 may include: sending first device connection information to a server, wherein the first device connection information may include a device identifier; in response to receiving connection feedback information from the server, sending first device state information to the server, wherein the connection feedback information may include information indicating that the connection was successful, and the first device state information may include at least one of: equipment identification, network card identification, equipment electric quantity, current signal quality, current time and product use state. In these embodiments, after the client device switches from the sleep state to the communication state, the first device connection information may be sent to the server to establish a connection with the server. Optionally, the first device connection information may include server address information, device authentication information, etc., in addition to device identification such as device ID, IMEI, ICCID, etc. After receiving the first device connection information from the client device, the server may determine whether the client device is allowed to connect to the server based on a stored client device list or according to other preset verification mechanisms, and if the client device is allowed, may send connection feedback information to the client device to indicate that the connection is successful; and if the client equipment is not allowed, not sending the connection feedback information. The client device, upon receiving the connection feedback information from the server, may send first device status information to the server to report to the server a current status of the client device and/or the product, such as one or more of a remaining battery capacity, a current network signal quality, whether a product package has been opened, a product usage amount, and the like. In such an embodiment, by sending the first device connection information first and then sending the first device status information, it can be ensured that the first device status information is sent to the correct server, and the problem of information leakage or extra energy consumption due to transmission failure or transmission error is avoided.
In the foregoing embodiment where the first device information includes first device connection information and first device status information, step 210 may further include: and in response to that the connection feedback information is not received within the first waiting time threshold and the sending times of the first equipment connection information do not reach the first sending time threshold, resending the first equipment connection information to the server. And, in these embodiments, step 210 may further include: and in response to the connection feedback information not being received within the first waiting time threshold and the first device connection information sending times having reached the first sending times threshold, switching the client device from the communication state to the dormant state. For example, the first waiting time threshold and the first sending number threshold may be preset by a manufacturer of the client device or a manufacturer of the product, and optionally may be adjusted by a manager of the client device or the product according to needs, or may be adjusted by a consumer according to needs. For example, the first latency threshold may be set to 5 seconds, 10 seconds, 20 seconds, 30 seconds, etc., and the first transmission number threshold may be set to 1, 2, 3, 5, etc., according to the actual application requirements. By setting the first waiting time threshold and the first sending time threshold, the first device connection information can be further ensured to be successfully sent to the server, and unnecessary power consumption can be avoided. For example, when the network condition is not good, the connection information of the first device may not be successfully transmitted to the server or the connection feedback information from the server may not be transmitted to the client device, and at this time, by setting the first transmission time threshold, the reconnection times of the client device to the server may be limited, thereby avoiding power consumption caused by repeated reconnection. In this case, the client device may switch back to the sleep state, and then connect to the server and send the first device state information when the network condition is improved.
In the foregoing embodiment where the first device information includes first device connection information and first device status information, step 210 may further include: and in response to that the positioning feedback information is not received within the second waiting time threshold and the sending times of the first equipment state information do not reach the second sending time threshold, resending the first equipment state information to the server. And, in these embodiments, step 210 may further include: and in response to the positioning feedback information not being received within the second waiting time threshold and the number of times of sending the first device state information has reached a second sending time threshold, switching the client device from the communication state to the dormant state. For example, the second waiting time threshold and the second sending time threshold may be preset by a manufacturer of the client device or a manufacturer of the product, and optionally may be adjusted by a manager of the client device or the product according to needs, or may be adjusted by a consumer according to needs. For example, the second waiting time threshold may be set to 5 seconds, 10 seconds, 20 seconds, 30 seconds, etc., and the second transmission number threshold may be set to 1 time, 2 times, 3 times, 5 times, etc., according to the actual application requirements. Optionally, the second latency threshold may be the same as or different from the first latency threshold, and the second transmission time threshold may also be the same as or different from the first transmission time threshold. Similarly, by setting the second waiting time threshold and the second transmission number threshold, it can be further ensured that the first device status information is successfully transmitted to the server, while unnecessary power consumption can be avoided. For example, when the network condition is not good, the first device status information may be difficult to be successfully transmitted to the server or the positioning feedback information from the server may not be transmitted to the client device, and at this time, the number of times that the client device transmits the first device status information to the server may be limited by setting the second transmission number threshold, so as to avoid power consumption caused by repeated retransmission. In this case, the client device may switch back to the sleep state, reconnect to the server when the network condition improves, and send the first device state information.
In some embodiments, the positioning feedback information received in step 220 may further include at least one of: information indicating to modify the predetermined time interval, information indicating to modify the first latency threshold, information indicating to modify the second latency threshold, information indicating to modify the first transmission time threshold, information indicating to modify the second transmission time threshold. For example, the various information related to the modification indication may be generated at the server-side device based on management input of a manager or automatically determined by the server-side device according to historical device information and historical location uploaded by the client device, and added to the location feedback information at the server side to be sent to the client device. Upon receiving such information, the client device may modify one or more of the predetermined time interval, the first latency threshold, the second latency threshold, the first number of transmissions threshold, and the second number of transmissions threshold accordingly in accordance with the modification indication in the information. These modifications may be immediate in effect, i.e., the next triggering of the client device may be in accordance with a modified predetermined time interval, and the device connection/status information may be sent in accordance with a modified time and/or number threshold. Through the modification mechanism, the preset time interval, the first/second waiting time threshold and the first/second sending time threshold can be allowed to be adjusted according to actual requirements, so that the flexibility of client equipment management is increased. These time and/or time parameters may be adjusted, for example, based on information such as the remaining power of the client device, the location of the client device, the product on-state, etc. For example, when the remaining power is low, when the location of the client device has not changed for a period of time, or after the product has been turned on, the predetermined time interval may be extended, the first/second transmission number threshold may be lowered, etc., as appropriate, in order to conserve power.
In some embodiments, the operation of transmitting the second device information to the server in step 230 may be similar to the aforementioned operation of transmitting the first device information. Exemplarily, the second device information may similarly include second device connection information and second device state information, and the transmitting the second device information to the server may include: sending second equipment connection information to a server, wherein the second equipment connection information comprises equipment identification; in response to receiving connection feedback information from the server, sending second device status information to the server, wherein the second connection feedback information includes information indicating that the connection was successful, the second device status information includes information indicating that the wrapping structure is opened and at least one of: equipment identification, network card identification, equipment electric quantity, current signal quality, current time and product use state. Therefore, the second device state information can be sent to the correct server, and the problem of information leakage or extra energy consumption caused by sending failure or sending error is avoided. For example, a feedback mechanism similar to that described above with respect to the first device connection information and the first device state information may also exist in the sending process of the second device connection information and the second device state information, and for the sake of brevity, details are not described herein again. Alternatively, for example, the operation of sending the second device information to the server may be different from the aforementioned operation of sending the first device information, for example, the client device may maintain a communication state and continuously send the second device information to the server until the power is exhausted; or the client device may send the second device information to the server by preset times, and then perform operations such as closing, dormancy or destruction; and so on.
In some embodiments, step 210 may include sending the first device information to a server via a base station, which may be configured to forward the first device information from the client device to the server; and step 230 may include sending the second device information to the server via the base station, which may be configured to forward the second device information from the client device to the server. Illustratively, the base station may refer to a public mobile communication base station built by a mobile communication operator, such as a base station in a cellular network. Thus, wireless communication can be realized by using the existing base station, and a wide communication range can be realized with low cost input. Alternatively, the base station may be built by the producer or the consumer of the client device. In such embodiments, the client device may support a communication protocol associated with base station communications, e.g., a corresponding communication protocol in a cellular network, and may transmit signals to and/or receive signals from the base station via an antenna structure, such as a radio frequency antenna. One skilled in the art will appreciate that in communicating with the base station, upon receiving a signal from a client device, may determine the location of the client device based on the received signal via triangulation or other positioning algorithms. Therefore, the server can acquire the position information of the corresponding client device from the base station so as to complete the positioning of the client device.
In some embodiments, the method 200 may further include: sending registration information to a server, wherein the registration information can comprise equipment identification; registration feedback information is received from the server, which may include a device identification and a device key. In these embodiments, the first device information sent in step 210 and the second device information sent in step 230 may also include a device key. Illustratively, in an embodiment where the first device information includes first device connection information and first device state information, the device key may be included in the first device connection information; in an embodiment where the second device information includes second device connection information and second device state information, the device key may be included in the second device connection information. Illustratively, the device key may be a character string randomly generated by the server for the client device, or may be a character string determined according to a preset mechanism, or may be a character string pre-specified by a manager, and so on. In such embodiments, the client device may be automatically connected to the server through pre-stored server address information after first powering on, or may be manually connected to the server by an administrator. The client device may then send information such as a device identification (e.g., IMEI, ICCID, etc.) to the server, either wirelessly or by wire, and the server may store the device identification, generate and store a corresponding device key, and send the device key and other optional information to the client device, such as settings for the aforementioned predetermined time interval, first/second latency threshold, first/second number of transmissions threshold, etc. Through the registration mechanism, only the client device which is successfully registered can be connected to the server, so that malicious connection is avoided, and the safety of the whole product tracking system is ensured.
Fig. 5 schematically illustrates an example flow diagram of a product tracking method 500 for a server-side device in accordance with some embodiments of the present disclosure. Illustratively, the product tracing method 500 may be deployed on the server 130 in the scenario 100 shown in FIG. 1.
Specifically, at step 510, in response to receiving first device information from the client device, the client device may be located based on the first device information. The client device may be installed in a packaging structure of a product, and the first device information may include a device identification of the client device. Illustratively, the client device may switch from the sleep state to the communication state upon reaching a predetermined time interval from the last trigger and send the first device information to the server, as described with respect to method 200 of fig. 2. Upon receiving the first device information, the server may locate the respective client device based on the received first device information, and may send, at step 520, location feedback information to the client device, which may include information indicative of the located client device. At step 530, in response to receiving second device information from the client device, the client device is located based on the second device information and stores information indicating that the packaging structure of the product is opened at the current time, the second device information including a device identification of the client device and information indicating that the packaging structure is opened. This process has already been described in detail in the description of steps 210 to 230, and is not repeated here for the sake of brevity.
Further, the server may monitor and record when the packaging structure of the product is opened, via step 530. Illustratively, when the client device is triggered by monitoring that the packaging structure of the product is opened, the second device information transmitted by the client device may include information indicating that the packaging structure of the product is opened, which is also described in detail in the description of the method 200. After the server receives the second device information, the corresponding device identifier, the product opening identifier, the corresponding time information and the like can be stored. For example, the time information may be acquired from second device information transmitted from the client device, or may be determined based on a time at which the server receives the second device information. Alternatively, the stored information may be stored in the storage of the server, or may be stored in an external device. The stored information may be queried by an administrator of the client device or product, or may be queried by a consumer, such as may be queried by an administration platform device, by a logo code device at the client device, and so forth.
In some embodiments, the first device information may include first device connection information and first device state information. In these embodiments, step 510 may include: in response to receiving first device connection information from the client device, sending connection feedback information, wherein the first device connection information may include a device identification and the connection feedback information may include information indicating that the connection was successful; in response to receiving first device state information from the client device, storing the first device state information, wherein the first device state information may include at least one of: the device identification, the network card identification, the device electric quantity, the current signal quality, the current time and the product use state; and locating the client device based on the device identification. These embodiments and their advantages have been introduced in the foregoing description of the relevant embodiments with respect to step 210 and will not be repeated here. In addition, the server may store the received first device state information after receiving the first device state information from the client device, for example, in a storage of the server or in an external device. Similar to as described above, the stored first device state information may then be queried by an administrator or consumer of the client device or product. Optionally, the client device may be located based on a device identification and optionally other information contained in the first device connection information or the first device status information.
Similarly, in some embodiments, the second device information may include second device connection information and second device state information. In these embodiments, step 530 may include: in response to receiving second device connection information from the client device, sending connection feedback information, wherein the second device connection information may include a device identification and the connection feedback information may include information indicating that the connection was successful; in response to receiving second device state information from the client device, storing the second device state information, wherein the second device state information may include at least one of: the device identification, the network card identification, the device electric quantity, the current signal quality, the current time and the product use state; and locating the client device based on the device identification. These embodiments and their advantages have been introduced in the foregoing description of the related embodiments with respect to step 230 and will not be repeated here. In addition, the server may store the received second device state information, for example, in a storage device of the server or in an external device, upon receiving the second device state information from the client device. Similar to the foregoing, the stored second device state information may then be queried by an administrator or consumer of the client device or product. Optionally, the client device may be located based on the device identification and optionally other information contained in the second device connection information or second device status information.
It should be understood that the method steps described herein and elsewhere herein need not necessarily be performed in the order described, and some of the steps may be performed in parallel or in reverse order. Illustratively, the storing step and the positioning step described in this paragraph may be performed in parallel or in an order reverse to the order described.
In some embodiments, step 510 may include: receiving first device information from a client device via a base station, the base station configured to forward the first device information from the client device to a server; location information of the client device is queried at the base station based on the device identification of the client device. In some embodiments, step 530 may include: receiving second device information from the client device via a base station, the base station configured to forward the second device information from the client device to a server; location information of the client device is queried at the base station based on the device identification of the client device. These embodiments and their advantages have been described in the related embodiments related to steps 210 and 230, and are not described herein again. It will be appreciated that in such embodiments, the transceiving of other information may also be implemented based on the base station.
In some embodiments, the method 500 may further include: receiving a management instruction for a client device, the management instruction comprising at least one of: indicating a preset time interval between two state switching of the client equipment, indicating a first waiting time threshold value of the client equipment for connection feedback information modification, indicating a second waiting time threshold value of the client equipment for positioning feedback information modification, indicating a first sending time threshold value of the client equipment for first equipment connection information modification, and indicating a second sending time threshold value of the client equipment for first equipment state information modification; based on the management instruction, adding at least one of the following in the positioning feedback information: information indicating modification of the predetermined time interval, information indicating modification of the first latency threshold, information indicating modification of the second latency threshold, information indicating modification of the first transmission number threshold, information indicating modification of the second transmission number threshold. These embodiments and their advantages have been described in relation to the embodiments of steps 220 and 230 and will not be described further herein.
It is understood that the method 500 may be implemented in conjunction with the method 200, and may have the same or similar embodiments and advantages as the method 200.
Fig. 6 schematically illustrates an example flow diagram of a client device management method 600 in accordance with some embodiments of the present disclosure. Illustratively, the client device management method 600 may be deployed on the management platform device 140 in the scenario 100 shown in fig. 1, or may be deployed on the server 130 or another server and accessible and usable through the management platform device 140. Illustratively, stored information and/or various administrative inputs may be exposed and/or received through interface diagrams 700A-700H of a device management platform similar to that shown in FIGS. 7A-7H. Various embodiments of method 600 are described below in conjunction with fig. 7A-7H.
Specifically, the method 600 may include step 610: first device information and second device information sent by a client device to a server and location information of the client device determined by the server are recorded. The client device may be installed in a packaging structure of a product and may be configured to perform the product tracking method 200 described with reference to fig. 2. For example, the management platform device may obtain the first/second device information and the location information from a server. For example, the information newly added or updated may be acquired and stored from the server in real time, periodically, or based on management input of a manager.
As shown in the interface 700A in fig. 7A, at the device management platform, the device identifications (such as serial numbers, IMEIs, etc.) of the respective client devices may be recorded and presented, for example, in a list form, and optionally, the corresponding import times (such as the time of registration to the server or the time of importing from the server to the device management platform) may be presented. Furthermore, optionally, identifiers of the signpost devices provided at the respective client devices, such as the numbers of RFID and NFC shown in the figure, can also be presented. Further, as shown in the interfaces 700B, 700C, 700E, 700F, 700G in fig. 7B, 7C, 7E, 7F, 7G, at the device management platform, richer device information, such as location information, product on status, current signal quality, communication frequency, battery level, key, connected servers and ports, threshold parameters regarding waiting time/number of transmissions, etc., whether the client device connection is normal, etc., may also be recorded and presented. Such information may be sent by the client device to the server based on the various embodiments described above, or generated and/or stored by the server based on the various embodiments described above.
In some embodiments, method 600 may further include: receiving user management input, the user management input may include at least one of: modifying a preset time interval, modifying a first waiting time threshold, modifying a second waiting time threshold, modifying a first sending time threshold and modifying a second sending time threshold; based on the user management input, sending a management instruction to the server, so that the server adds at least one of the following in the positioning feedback information: information indicating to modify the predetermined time interval, information indicating to modify the first latency threshold, information indicating to modify the second latency threshold, information indicating to modify the first transmission number threshold, information indicating to modify the second transmission number threshold.
Illustratively, the administrator may select one or more client devices that are desired to be modified in interface 700B shown in fig. 7B and enter user management inputs in interface 700C shown in fig. 7C. As shown in fig. 7B, one or more client devices may be selected through a selection box before the serial number of each client device, and then, for example, a "bulk modify" option may be clicked. One or more of the modified predetermined time interval, the first latency threshold, the second latency threshold, the first number of transmissions threshold, the second number of transmissions threshold, etc. (i.e., the frequency of communications, the communications timeout time, the number of reconnections, etc. shown in fig. 7C) may then be set in the presented dialog box shown in fig. 7C. The modified parameters may be presented, for example, in parentheses following the corresponding current parameter. For example, after a manager modifies a parameter, the parameter may be transmitted to the server, and if the corresponding client device is just in a communication state at this time, the modified parameter may be sent to the corresponding client device through the positioning feedback information; if the corresponding client device is just in the dormant state at this time, the modified parameter may be stored at the server and sent to the client device through the positioning feedback information after the corresponding client device switches to the communication state.
In some embodiments, method 600 may further include: the client device is identified on the map based on the location information of the client device.
Illustratively, the administrator may view the location information of each client device and view its historical track in the interface 700E shown in fig. 7E. Illustratively, when clicking on a historical track of a client device, an interface 700F may be presented as shown in fig. 7F, in which all historical location data sent to the server by the corresponding client device is presented. And, optionally, the current location or historical location of the client device may be presented on a map. In addition, as shown in fig. 7H, in interface 700H, location information for a plurality or even all of the client devices may be presented in the map, e.g., presenting the number of client devices present in each location area, etc. Therefore, the administrator can more intuitively master the distribution situation of the client device, so that the distribution situation of related products can be more intuitively and comprehensively mastered.
Additionally, optionally, as shown in interface 700A, information for a particular client device may be manually added or imported via an "add-on" or "import" option, and some or all of the data for a particular client device may be downloaded in a particular format via a "data download" or "template download" option. Further, as shown in interfaces 700A-700E and 700G, information for a client device may be allowed to be filtered by filtering criteria to view information for a desired client device. Optionally, as shown in interface 700D, traffic conditions of each client device may also be presented, such as used traffic, total traffic, whether to include a year, card open time, expiration time, etc., and optionally, modification of such information may be allowed, such as modification of traffic packet size, options whether to include a year, expiration time, etc. Optionally, as shown in the interface 700G, product information and consumer information corresponding to each client device may also be acquired and displayed. Illustratively, the consumer information may be obtained from a shopping website or dealer after approval by the consumer, or may be uploaded by the consumer. For example, the consumer may scan the identification code device in the product and write the relevant information using their terminal device, or scan the identification code device using their terminal device to access the server and send the relevant information directly to the server.
To further facilitate understanding, fig. 8 schematically illustrates an example flow diagram of a product tracking process 800 in accordance with some embodiments of the present disclosure. As shown in fig. 8, after the client device is powered on, the client device may connect to the cloud platform server to obtain registration information, such as the device key described in the foregoing embodiments. After registration is complete, the client device may enter a sleep state. Subsequently, when the timing trigger condition is satisfied, e.g., a predetermined time interval has elapsed since the last trigger, the client device may switch from the sleep state to the communication state and connect to the cloud platform server, e.g., by sending the first device connection information. After receiving the connection feedback information, may send first device state information; if the connection feedback information is not received within the preset waiting time, the connection with the cloud platform server can be retried. After attempting the connection for a predetermined number of times, it may switch to the dormant state and wait for the next time the trigger condition is met. After the device state information (for example, the first device state information) is sent, if the positioning feedback information from the cloud platform server is received, switching back to the dormant state; if the connection feedback information is not received within the preset waiting time, the device state information can be retransmitted. After the number of times of sending the device state information reaches the preset number of times, the device state information can be switched to the dormant state, and the timing trigger condition of the next time is met. Further, upon monitoring that the packaging structure is opened, the client device may switch from the dormant state to the communication state and/or maintain the communication state and send device information (e.g., second device information) to the server to report that the packaging structure is opened. When the client device is in the sleep state, it may be triggered when a switch for monitoring whether the product packaging structure is opened is triggered or when a timing time is reached, and connect with the cloud platform server, transmit the first or second device status information, or may directly transmit the first or second device information to the cloud platform server. The above-described steps may be performed according to various embodiments described above and will not be described in detail herein.
Fig. 9 schematically illustrates an example block diagram of a product tracking apparatus 900 for a client device that may be installed in a packaging structure for a product in accordance with some embodiments of this disclosure. As shown in fig. 9, the product tracking device 900 includes a first sending module 910, a switching module 920, and a second sending module 930. Illustratively, the product tracking device 900 may be deployed on the client device 110 shown in FIG. 1.
Specifically, the first sending module 910 may be configured to, in response to reaching a predetermined time interval from a last trigger, cause the client device to switch from the sleep state to the communication state, and send first device information to the server, the first device information including a device identification of the client device; the switching module 920 may be configured to switch the client device from the communication state to the sleep state in response to receiving positioning feedback information from the server, wherein the positioning feedback information includes information indicating the positioned client device; the second sending module 930 may be configured to, in response to monitoring that the packaging structure is opened, cause the client device to switch from the sleep state to the communication state and/or maintain the communication state, and send second device information to the server, the second device information including a device identification of the client device and information indicating that the packaging structure is opened.
Fig. 10 schematically illustrates an example block diagram of a product tracking device 1000 for a server, in accordance with some embodiments of this disclosure. As shown in fig. 10, the product tracking device 1000 includes a first location module 1010, a transmission module 1020, and a second location module 1030. Illustratively, the product tracking device 1000 may be deployed on the server 130 shown in fig. 1.
In particular, the first location module 1010 may be configured to locate a client device based on first device information in response to receiving the first device information from the client device, wherein the client device may be installed in a packaging structure of a product, and the first device information may include a device identification of the client device; the sending module 1020 may be configured to send positioning feedback information to the client device, which may include information indicating the located client device; the second locating module 1030 may be configured to locate the client device based on second device information in response to receiving the second device information from the client device, the second device information including a device identification of the client device and information indicating that the packaging structure of the product is opened at the current time, and store the information indicating that the packaging structure is opened.
Fig. 11 schematically illustrates an example block diagram of a client device management apparatus 1100 in accordance with some embodiments of the present disclosure. As shown in fig. 11, the client device management apparatus 1100 includes a recording module 1110. Illustratively, the client device management apparatus 1100 may be deployed on the management platform device 140 or the server 130 shown in fig. 1, or on another server accessible by the management platform device 140.
In particular, the recording module 1110 may be configured to record first and second device information sent by the client device to the server and location information of the client device determined by the server.
It is to be understood that the apparatus 900, 1000, and/or 1100 may be implemented in software, hardware, or a combination of software and hardware. Several different modules may be implemented in the same software or hardware configuration, or one module may be implemented by several different software or hardware configurations.
Additionally, the apparatus 900, 1000, and/or 1100 may be used to implement the methods 200, 500, and/or 600 described above, the relevant details of which have been described in detail above and will not be repeated here for the sake of brevity. The apparatus 900, 1000 and/or 1100 may have the same features and advantages as described with respect to the previous method.
Fig. 12 schematically illustrates an example block diagram of a product tracking system 1200 in accordance with some embodiments of this disclosure. As shown in fig. 12, the product tracking system 1200 may include a product tracking device 900 and a product tracking device 1000. Further, optionally, the product tracking system 1200 may further include a client device management apparatus 1100. And, optionally, the product tracking system 1200 may further include an identification code means 1210, the identification code means 1210 may be scanned to read or write information related to the client device or product. Illustratively, the identification code device 1210 may be embodied as one or more of an RFID tag, an NFC tag, a two-dimensional code, a barcode, or the like. The consumer or manager may acquire and write information stored in the identification code devices themselves by scanning these identification code devices, or may acquire and write information stored on the respective client devices or servers by scanning these identification code devices.
Fig. 13 schematically illustrates an example block diagram of a computing device 1300 in accordance with some embodiments of this disclosure. For example, which may represent client device 110, server 130, management platform device 140, or other type of computing device that may be used to deploy apparatus 900, 1000, and/or 1100 provided by the present disclosure in fig. 1.
As shown, the example computing device 1300 can include a processing system 1301, one or more computer-readable media 1302, and one or more I/O interfaces 1303 communicatively coupled to each other. Although not shown, the computing device 1300 may also include a system bus or other data and command transfer system that couples the various components to one another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures, or that includes control and data lines.
Computer-readable medium 1302 is illustrated as including memory/storage 1305. Memory/storage 1305 represents memory/storage associated with one or more computer-readable media. Memory/storage 1305 may include volatile storage media (such as Random Access Memory (RAM)) and/or nonvolatile storage media (such as Read Only Memory (ROM), flash memory, optical disks, magnetic disks, and so forth). The memory/storage 1305 may include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., flash memory, a removable hard drive, an optical disk, and so forth). Memory/storage 1305 may be used to store various device connection information, device state information, etc., mentioned in the embodiments above, for example. Computer-readable media 1302 may be configured in various other ways as further described below.
One or more input/output interfaces 1303 represent functionality that allows a user to enter commands and information to computing device 1300, and also allows information to be presented to the user and/or sent to other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone (e.g., for voice input), a scanner, touch functionality (e.g., capacitive or other sensors configured to detect physical touch), a camera (e.g., motion that does not involve touch may be detected as gestures using visible or invisible wavelengths such as infrared frequencies), a network card, a receiver, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a haptic response device, a network card, a transmitter, and so forth. For example, in the above-described embodiments, the user may be allowed to view various data information and enter management input and the like through the input device.
Various techniques may be described herein in the general context of software, hardware, elements, or program modules. Generally, these modules include routines, programs, objects, elements, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The terms "module," "functionality," and the like, as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of computing platforms having a variety of processors.
An implementation of the described modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can include a variety of media that can be accessed by computing device 1300. By way of example, and not limitation, computer-readable media may comprise "computer-readable storage media" and "computer-readable signal media".
"computer-readable storage medium" refers to a medium and/or device, and/or a tangible storage apparatus, capable of persistently storing information, as opposed to mere signal transmission, carrier wave, or signal per se. Accordingly, computer-readable storage media refers to non-signal bearing media. Computer-readable storage media include hardware such as volatile and nonvolatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer-readable instructions, data structures, program modules, logic elements/circuits or other data. Examples of computer readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage devices, tangible media, or an article of manufacture suitable for storing the desired information and accessible by a computer.
"computer-readable signal medium" refers to a signal-bearing medium configured to transmit instructions to hardware of computing device 1300, such as via a network. Signal media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave, data signal or other transport mechanism. Signal media also include any information delivery media. By way of example, and not limitation, signal media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
As previously described, hardware element 1304 and computer-readable medium 1302 represent instructions, modules, programmable device logic, and/or fixed device logic implemented in hardware form that may be used in some embodiments to implement at least some aspects of the techniques described herein. The hardware elements may include integrated circuits or systems-on-chips, application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs), complex Programmable Logic Devices (CPLDs), and other implementations in silicon or components of other hardware devices. In this context, a hardware element may serve as a processing device that performs program tasks defined by instructions, modules, and/or logic embodied by the hardware element, as well as a hardware device for storing instructions for execution, such as the computer-readable storage medium described previously.
Combinations of the foregoing may also be used to implement the various techniques and modules described herein. Thus, software, hardware, or program modules and other program modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage medium and/or by one or more hardware elements 1304. Computing device 1300 may be configured to implement particular instructions and/or functions corresponding to software and/or hardware modules. Thus, implementing modules at least partially in hardware as modules executable by the computing device 1300 as software may be accomplished, for example, through the use of computer-readable storage media of a processing system and/or hardware elements 1304. The instructions and/or functions may be executed/operable by, for example, one or more computing devices 1300 and/or processing systems 1301 to implement the techniques, modules, and examples described herein.
The techniques described herein may be supported by these various configurations of computing device 1300 and are not limited to specific examples of the techniques described herein.
It should be understood that embodiments of the disclosure have been described with reference to different functional units for clarity. However, it will be apparent that the functionality of each functional unit may be implemented in a single unit, in a plurality of units or as part of other functional units without departing from the disclosure. For example, functionality illustrated to be performed by a single unit may be performed by multiple different units. Thus, references to specific functional units are only to be seen as references to suitable units for providing the described functionality rather than indicative of a strict logical or physical structure or organization. Thus, the present disclosure may be implemented in a single unit or may be physically and functionally distributed between different units and circuits.
The present disclosure provides a computer-readable storage medium having stored thereon computer-readable instructions which, when executed, implement the above-described product tracing method and/or client device management method for a client device or server.
The present disclosure provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The computer instructions are read by a processor of the computing device from a computer-readable storage medium, and the processor executes the computer instructions to cause the computing device to perform the product tracking method and/or the client device management method provided in the various embodiments described above.
According to some embodiments of the present disclosure, there is also provided a product tracking device. Illustratively, the product tracking device may include the client device 110 shown in FIG. 1. Schematically, fig. 14 shows an example block diagram of a product tracking device 1400. As shown in fig. 14, product tracking device 1400 includes trigger leads 1410, wake-up circuit 1420, and communication circuit 1430.
Specifically, the trigger lead 1410 may be configured to be broken when the packaging structure of the product is opened. Illustratively, the trigger lead 1410 may include a lead that may optionally electrically connect the wake-up circuit 1420 to a high or low level and may be disconnected as the package is opened, thereby severing the electrical connection; alternatively, the trigger lead 1410 may include two leads that may be connected by a severable conductor that may be severed when the packaging structure of the product is opened, which may be similar to the trigger structure described with reference to fig. 3A, where the severable conductor film 330 may serve as the severable conductor described above. In addition, other similar trigger lead configurations are also contemplated.
The wake-up circuit 1420 may be coupled to the trigger lead 1410 and configured to generate a wake-up signal in response to the trigger lead 1410 being disconnected. Alternatively, the wake-up signal may be a wake-up level, such as a high level, a low level, a rising or falling edge of a level, and the like. Illustratively, when the wake-up pin of wake-up circuit 1420 is connected to a high or low level via a trigger lead, it may monitor the level change at the wake-up pin and generate a corresponding wake-up signal when the level change occurs. Illustratively, wake-up circuit 1420 may include a switching device, such as a transistor. For example, in the case of using a field effect transistor, the source of the field effect transistor may be connected to a high level or a low level, and the source and the gate thereof may be connected by a trigger wire, so that when the trigger wire is disconnected, the state switching of the field effect transistor between the off state and the on state may be achieved, thereby triggering the generation of the wake-up signal. In addition, other types of wake-up circuits are also contemplated.
The communication circuit 1430 may be configured to transmit device information in response to the wake-up signal. In some embodiments, the communication circuit 1430 may switch from the sleep state to the communication state and transmit the device information in the communication state in response to the wake-up signal. In some embodiments, the communication circuit 1430 may also switch back from the communication state to the sleep state in response to receiving the feedback information. The operation of the communication circuit 1430 may be similar to the various embodiments of the product tracking method 200 described above with reference to fig. 2 and will not be described again. Optionally, the communication circuit 1430 may include a chip, such as the chip 111 shown in fig. 1.
In some embodiments, the communication circuit 1430 and the wake-up circuit 1420 may be disposed on a circuit board. Illustratively, fig. 15 shows a schematic diagram of a circuit board 1500. Illustratively, the trigger lead may be coupled to the circuit board 1500 at the recess 1510 of the circuit board 1500, and in turn, coupled to the wake-up circuit 1420 via a lead structure on the circuit board 1500. Exemplarily, the circuit board 1500 may be a PCB, an FPC, or the like.
In some embodiments, the product tracking device 1400 may also include an antenna connected to the communication circuit 1430 and configured to transmit device information from the communication circuit to a server. Optionally, the antenna may also receive feedback information from the server. The antenna may be, for example, the antenna 112 described with reference to fig. 1. Illustratively, the communication circuit may transmit the device information using an antenna and receive the feedback information using the antenna. In this case, an interface 1520 for connecting an antenna, such as a pogo pin interface, may also be provided on the circuit board 1500, so that the antenna may be connected to the circuit board through the interface 1520 and further connected to the communication circuit through a lead structure on the circuit board. Through the bullet needle interface, can assemble circuit board and antenna conveniently, this helps realizing the modularization manufacturing and the equipment of product tracking equipment, helps promoting equipment production efficiency. In some embodiments, the communication circuit may include an NB-IOT chip, such as the XY1100 chip mentioned previously. At this time, the antenna may include an NB antenna in order to access the NB network.
In some embodiments, the circuit board 1500 may be secured in a housing. The housing may comprise a lead opening such that the above-mentioned trigger lead may extend from the circuit board to the outside of the housing through the lead opening, e.g. to the severable conductor. In addition, the housing may also include an antenna opening such that the antenna may be connected to a circuit board within the housing through the open wire opening. Illustratively, the antenna may be attached, e.g., affixed, to an exterior surface of the housing. Further, illustratively, the product tracking device may also include an electronic tag, which may also be attached on an exterior surface of the housing. For example, as previously mentioned, the electronic tag may include at least one of an RFID tag and an NFC tag and may be available for scanning to obtain information related to the product or product tracking device. For example, the housing may be cylindrical, the antenna may be attached to one circular bottom surface of the housing, the NFC tag may be attached to another circular bottom surface of the housing, and the RFID tag may be attached to a side curved surface of the housing. Alternatively, the antenna and the electronic tag may be arranged in other ways.
In some embodiments, product tracking device 1400 may also include a battery. The battery may be configured to power at least one of the wake-up circuit and the communication circuit, which may be similar to the power supply 113 described with reference to fig. 1. For example, the battery may be the aforementioned lithium thionyl chloride battery, which has high energy density and can store a large amount of electricity in a small size, thereby contributing to miniaturization of the product tracking device 1400. Alternatively, the battery may be connected to a corresponding interface on the circuit board and further connected to at least one of the communication circuit and the wake-up circuit by a lead structure on the circuit board. Further alternatively, the battery may be stacked in the same housing as the circuit board.
Further, in some embodiments, the product tracking device 1400 may further include a clock circuit connected to the communication circuit and configured to generate a clock signal. In such embodiments, the communication circuit may be further configured to transmit the device information in response to the clock signal indicating that the predetermined time interval has been reached since the last trigger. In some embodiments, the communication circuit may switch from the sleep state to the communication state in response to the clock signal indicating that a predetermined time interval has been reached since the last trigger, which may be similar to the various embodiments of the product tracking method 200 described above with reference to fig. 2. The clock circuit may be implemented according to various embodiments of the aforementioned timing device, and is not described herein again.
According to some embodiments of the present disclosure, there is also provided a cover. Schematically, fig. 16 shows an example block diagram of a cover 1600. As shown in fig. 16, the cap 1600 includes a cap body 1610 and a product tracking device 1620. Wherein product tracking device 1620 may be similar to product tracking device 1400 described above. Here, the product packaging structure may be a cap body 1610, and the product tracking device 1620 may be attached to the cap body 1610. Further, optionally, the cover body 1610 may include: an inner lid 1611 comprising inner lid sidewalls surrounding the cavity; an outer cover 1613 comprising outer cover sidewalls surrounding at least a portion of the inner cover sidewalls; a severable conductor film 1612 extending at least between the outer lid side wall and the inner lid side wall, connected to the trigger lead, and configured to be severed when the lid body is opened.
Alternatively, the cap 1600 may be the cap of a bottle, jar, bucket, or other container, such as a wine bottle cap, cosmetic bottle cap, or the like. Illustratively, the cover 1600 may have the form of the embodiment described with reference to fig. 3A-3B, or may have other similar forms as well.
According to some embodiments of the present disclosure, a product tracking system is also provided. Schematically, fig. 17 shows an example block diagram of a product tracking system 1700. As shown in fig. 17, product tracking system 1700 includes product tracking device 1400 and server 1710 as described above. Server 1710 may be configured to, in response to receiving device information from product tracking device 1400, locate product tracking device 1400 based on the device information, and optionally may send corresponding feedback information to product tracking device 1400. The interaction process between the server 1710 and the product tracking device 1400 may be performed according to various embodiments of the product tracking method described with reference to fig. 2, fig. 5, and the like, and will not be described herein again. Further, optionally, product tracking system 1700 may also include a management platform 1720 configured to receive input instructions and manage product tracking device 1400 based on the received input instructions. The management platform 1720 may have functionality in various embodiments described with reference to fig. 6-7H, and so on, and will not be described further herein.
Variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed subject matter, from a study of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
Claims (16)
1. A product tracking device for installation in a packaging structure for a product, the product tracking device comprising:
a trigger lead configured to be broken when a packaging structure of the product is opened;
a wake-up circuit connected to the trigger lead and configured to generate a wake-up signal in response to the trigger lead being disconnected; and
communication circuitry configured to transmit device information in response to the wake-up signal.
2. The product tracking device of claim 1, wherein the trigger lead comprises two leads connected by a severable conductor that is severed when a packaging structure of the product is opened.
3. The product tracking device of claim 1, further comprising:
a circuit board on which the wake-up circuit and the communication circuit are disposed; and
a housing surrounding the circuit board and including a lead opening, wherein the trigger lead extends from the circuit board to outside the housing through the lead opening.
4. The product tracking device of claim 3, further comprising:
an electronic tag attached on an exterior surface of the housing, the electronic tag including at least one of an RFID tag and an NFC tag.
5. The product tracking device of claim 1, further comprising:
an antenna connected to the communication circuit through a pogo pin interface and configured to transmit device information from the communication circuit to a server.
6. The product tracking device of claim 1, wherein the communication circuit includes a narrowband internet of things chip.
7. The product tracking device of claim 1, further comprising:
a clock circuit connected to the communication circuit and configured to generate a clock signal,
wherein the communication circuit is further configured to transmit device information in response to the clock signal indicating that a predetermined time interval has been reached since a last trigger.
8. A lid, characterized in that the lid comprises:
a cover main body; and
a product tracking device attached to the cap body and comprising:
a trigger lead configured to be disconnected when the cap body is opened;
a wake-up circuit connected to the trigger lead and configured to generate a wake-up signal in response to the trigger lead being disconnected; and
communication circuitry configured to transmit device information in response to the wake-up signal.
9. The cap of claim 8, wherein the cap body comprises:
an inner cover including an inner cover sidewall surrounding the cavity;
an outer cap comprising an outer cap sidewall surrounding at least a portion of the inner cap sidewall;
a severable conductor film extending at least between the outer cover sidewall and the inner cover sidewall, connected to the trigger lead, and configured to be severed when the cover body is opened.
10. The cap recited in claim 9 wherein at least one of the inner cap sidewall, the outer cap sidewall and the severable conductor film has a frangible hole that constitutes a loop line.
11. The cap recited in claim 10 wherein the trigger lead comprises two leads, one of the two leads connected to the severable conductor film on one side of the frangible hole and the other of the two leads connected to the severable conductor film on the other side of the frangible hole.
12. The cover of claim 9, wherein there is at least one lead slot between the severable conductor film and the outer cover sidewall, and wherein the trigger lead is received in the at least one lead slot.
13. The cap recited in claim 9 wherein the outer cap further includes an outer cap top wall that closes the cavity at one end of the outer cap side wall, and wherein the product tracking device is attached to a side of the outer cap top wall that faces the cavity.
14. The cap of claim 13, wherein the cap further comprises a spacer plate attached to the product tracking device, and wherein the spacer plate, together with the outer cap top wall and the outer cap side wall, define a sub-cavity containing the product tracking device.
15. A product tracking system, comprising:
the product tracking device of any one of claims 1 to 7;
a server configured to receive the device information from the product tracking device and locate the product tracking device based on the device information.
16. The product tracking system of claim 15, further comprising:
a management platform configured to receive input instructions and manage the product tracking device based on the received input instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202221189625.3U CN218585344U (en) | 2022-05-18 | 2022-05-18 | Product tracking device, cover and product tracking system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202221189625.3U CN218585344U (en) | 2022-05-18 | 2022-05-18 | Product tracking device, cover and product tracking system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN218585344U true CN218585344U (en) | 2023-03-07 |
Family
ID=85358014
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202221189625.3U Active CN218585344U (en) | 2022-05-18 | 2022-05-18 | Product tracking device, cover and product tracking system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN218585344U (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023221768A1 (en) * | 2022-05-18 | 2023-11-23 | 京东方科技集团股份有限公司 | Product tracking method and apparatus, and computing device, storage medium and program product |
-
2022
- 2022-05-18 CN CN202221189625.3U patent/CN218585344U/en active Active
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023221768A1 (en) * | 2022-05-18 | 2023-11-23 | 京东方科技集团股份有限公司 | Product tracking method and apparatus, and computing device, storage medium and program product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10108892B2 (en) | Wireless tag apparatus and related medication compliance monitoring techniques | |
| US10108893B2 (en) | Sensor array, method of making same, and related medication compliance monitoring techniques | |
| US11836563B2 (en) | Programmable network node roles in hierarchical communications network | |
| US11775797B2 (en) | Hierarchical combination of distributed statistics in a monitoring network | |
| US9396369B1 (en) | Electronic tag transmissions corresponding to physical disturbance of tag | |
| US10456326B2 (en) | Systems and methods for monitoring medication adherence and compliance | |
| US11594120B2 (en) | Low-power electronic tape for tracking items | |
| CN109791649A (en) | Mobile transceiver and operating method with the alarm profile based on assets | |
| CN218585344U (en) | Product tracking device, cover and product tracking system | |
| WO2016165609A1 (en) | Recyclable logistic appliance and method and system for processing empty and full signals thereof | |
| US11392885B1 (en) | Hierarchical aggregation system with electronic tracking labels containing sensors | |
| US20110199192A1 (en) | Reconfiguration of a radio frequency tag | |
| US11232390B1 (en) | Item tracking system with electronic tracking labels containing sensors | |
| WO2015191159A2 (en) | Wireless medication compliance sensing device, system, and related methods | |
| US20230196038A1 (en) | Method for activating an electronic tracking label via label printing | |
| US20230128550A1 (en) | Item tracking system that switches between short-range and long-range location services | |
| WO2023221768A9 (en) | Product tracking method and apparatus, and computing device, storage medium and program product | |
| CN107708077B (en) | Electronic student identity card and short message issuing system | |
| US20230196267A1 (en) | Electronic tracking label with a fold-over battery attachment | |
| AU2019320791B2 (en) | Programmable network node roles in hierarchical communications network | |
| US20210295247A1 (en) | Handheld tape node dispenser and method | |
| LU102750B1 (en) | Printable smart tag | |
| WO2023198705A1 (en) | Electronic tag | |
| US20240135134A1 (en) | Hierarchical combination of distributed statistics in a monitoring network | |
| AU2019308300B2 (en) | Hierarchical combination of distributed statistics in a monitoring network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| GR01 | Patent grant | ||
| GR01 | Patent grant |