US20220144547A1 - Method and system for generating rfid labels using rfid encoder attachment - Google Patents
Method and system for generating rfid labels using rfid encoder attachment Download PDFInfo
- Publication number
- US20220144547A1 US20220144547A1 US17/506,514 US202117506514A US2022144547A1 US 20220144547 A1 US20220144547 A1 US 20220144547A1 US 202117506514 A US202117506514 A US 202117506514A US 2022144547 A1 US2022144547 A1 US 2022144547A1
- Authority
- US
- United States
- Prior art keywords
- rfid
- encoder
- label
- tag
- label printer
- 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.)
- Abandoned
Links
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B65—CONVEYING; PACKING; STORING; HANDLING THIN OR FILAMENTARY MATERIAL
- B65G—TRANSPORT OR STORAGE DEVICES, e.g. CONVEYORS FOR LOADING OR TIPPING, SHOP CONVEYOR SYSTEMS OR PNEUMATIC TUBE CONVEYORS
- B65G1/00—Storing articles, individually or in orderly arrangement, in warehouses or magazines
- B65G1/02—Storage devices
- B65G1/04—Storage devices mechanical
- B65G1/137—Storage devices mechanical with arrangements or automatic control means for selecting which articles are to be removed
- B65G1/1373—Storage devices mechanical with arrangements or automatic control means for selecting which articles are to be removed for fulfilling orders in warehouses
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B41—PRINTING; LINING MACHINES; TYPEWRITERS; STAMPS
- B41J—TYPEWRITERS; SELECTIVE PRINTING MECHANISMS, i.e. MECHANISMS PRINTING OTHERWISE THAN FROM A FORME; CORRECTION OF TYPOGRAPHICAL ERRORS
- B41J3/00—Typewriters or selective printing or marking mechanisms characterised by the purpose for which they are constructed
- B41J3/407—Typewriters or selective printing or marking mechanisms characterised by the purpose for which they are constructed for marking on special material
- B41J3/4075—Tape printers; Label printers
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B41—PRINTING; LINING MACHINES; TYPEWRITERS; STAMPS
- B41J—TYPEWRITERS; SELECTIVE PRINTING MECHANISMS, i.e. MECHANISMS PRINTING OTHERWISE THAN FROM A FORME; CORRECTION OF TYPOGRAPHICAL ERRORS
- B41J3/00—Typewriters or selective printing or marking mechanisms characterised by the purpose for which they are constructed
- B41J3/44—Typewriters or selective printing mechanisms having dual functions or combined with, or coupled to, apparatus performing other functions
- B41J3/50—Mechanisms producing characters by printing and also producing a record by other means, e.g. printer combined with RFID writer
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K1/00—Methods or arrangements for marking the record carrier in digital fashion
- G06K1/12—Methods or arrangements for marking the record carrier in digital fashion otherwise than by punching
- G06K1/121—Methods or arrangements for marking the record carrier in digital fashion otherwise than by punching by printing code marks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- G06K1/00—Methods or arrangements for marking the record carrier in digital fashion
- G06K1/20—Simultaneous marking of record carrier and printing-out of data, e.g. printing-punch
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B65—CONVEYING; PACKING; STORING; HANDLING THIN OR FILAMENTARY MATERIAL
- B65G—TRANSPORT OR STORAGE DEVICES, e.g. CONVEYORS FOR LOADING OR TIPPING, SHOP CONVEYOR SYSTEMS OR PNEUMATIC TUBE CONVEYORS
- B65G2203/00—Indexing code relating to control or detection of the articles or the load carriers during conveying
- B65G2203/04—Detection means
- B65G2203/042—Sensors
- B65G2203/046—RFID
Definitions
- Ultra High Frequency (UHF) Radio Frequency Identification (RFID) tags are commonly used for inventory tracking, storing data relevant to the product and origin, similar to barcodes.
- RFID tags have several benefits which make them an invaluable addition or replacement of barcodes. For example, whereas barcodes are read out optically and their data is fixed once created, RFID tags contain memory which is read wirelessly when interrogated by a UHF RFID reader, making their data more private and dynamic. Memory sectors can be updated, locked, and destroyed by users, depending on their administrative privileges.
- FIG. 3 is an exemplary method 300 for generating RFID labels using a non-RFID label printer, in accordance with an implementation of the present disclosure. It should be understood that the exemplary method 300 is presented solely for illustrative purposes, and that in other methods in accordance with the present disclosure can include additional, fewer, or alternative steps performed in similar or alternative orders, or in parallel.
- the exemplary method 300 starts at step 302 by arming an RFID encoder. As illustrated above in FIGS. 1A, 1B and 2 , the RFID encoder can comprise an RFID controller that is coupled to a network, one or more antennas, a label detector, an RFID reader, a marker label detector, and a marker apparatus.
- the RFID encoder can receive reader settings, encode settings and encode data via the one or more antennas, as illustrated in FIG. 2 .
- Table 1 illustrates an example of user selected encode data and corresponding RFIDs received by the RFID encoder.
- Flash memory 632 can be an electronic non-volatile computer storage medium or chip that can be used by the system 600 for storage and/or data transfer.
- the flash memory 632 can be electrically erased and/or reprogrammed. Flash memory 632 can include EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), ROM, NVRAM, or CMOS (complementary metal-oxide semiconductor), for example.
- the flash memory 632 can store the firmware 634 executed by the system 600 , when the system 600 is first powered on, along with a set of configurations specified for the firmware 634 .
- the flash memory 632 can also store configurations used by the firmware 634 .
- the firmware 634 of the system 600 can include a firmware configuration that defines how the firmware 634 controls various hardware components in the system 600 .
- the firmware configuration can determine the order in which the various hardware components in the system 600 are started.
- the firmware 334 can provide an interface, such as an UEFI, that allows a variety of different parameters to be set, which can be different from parameters in a firmware default configuration.
- a user e.g., an administrator
- firmware 634 is illustrated as being stored in the flash memory 632 , one of ordinary skill in the art will readily recognize that the firmware 634 can be stored in other memory components, such as memory 604 or ROM 606 .
Abstract
The present disclosure provides a system and method for generating RFID labels using a non-RFID label printer and an easy-to-attach RFID encoder. The RFID encoder comprises an RFID controller coupled to a network, one or more antennas, a label detector, and an RFID reader. The RFID encoder can be packed into two or more encoder units that are clipped onto the front and back of the non-RFID label printer. The RFID controller receives a packet of reader settings and a packet (array) of encode data via the one or more antennas. As unprinted labels pass through the non-RFID label printer and the RFID encoder, the label detector senses tags of the unprinted labels, and triggers the RFID controller and the non-RFID label printer to encode RFIDs onto the tags.
Description
- This application is a continuation of U.S. patent application Ser. No. 16/496,232, filed Sep. 20, 2019, which is a U.S. National Stage application under 35 U.S.C. § 371 of International Application No. PCT/US2018/023531, filed Mar. 21, 2018, which claims priority to U.S. Provisional Application 62/601,396, filed on Mar. 21, 2017, the disclosures of which are incorporated herein by reference in their entireties.
- The disclosure generally relates to generating RFID labels.
- Ultra High Frequency (UHF) Radio Frequency Identification (RFID) tags are commonly used for inventory tracking, storing data relevant to the product and origin, similar to barcodes. However, RFID tags have several benefits which make them an invaluable addition or replacement of barcodes. For example, whereas barcodes are read out optically and their data is fixed once created, RFID tags contain memory which is read wirelessly when interrogated by a UHF RFID reader, making their data more private and dynamic. Memory sectors can be updated, locked, and destroyed by users, depending on their administrative privileges.
- RFID tags are often distributed as “RFID labels,” which are regular printable labels with RFID tags embedded inside them. The labels feature a barcode or relevant graphics, and have corresponding data encoded in the embedded RFID tags. Conventionally, these labels are created in small batches using “RFID Printer Encoders,” which are normal label printers with integrated RFID encoders. These devices both print and encode RFID labels on demand.
- However, RFID printer encoders are sold at a premium, and often lack in performance and capabilities of standalone label printers. Furthermore, if a company would like to introduce RFID intelligence to their business, but have already invested in regular label printers, it may be uneconomical to reinvest in a new fleet or RFID printer encoders.
- Systems and methods, in accordance with various examples of the present disclosure, provide a solution to the above-mentioned problems by generating RFID labels using a non-RFID label printer and an easy-to-attach RFID encoder. The RFID encoder comprises an RFID controller coupled to a network, one or more antennas, a label detector, and an RFID reader. The RFID encoder can be packed into two or more encoder units that are clipped onto the front and back of the non-RFID label printer. The RFID controller receives a packet of reader settings and a packet (array) of encode data via the one or more antennas. As unprinted labels pass through the non-RFID label printer and the RFID encoder, the label detector senses tags of the unprinted labels, and triggers the RFID controller and the non-RFID label printer to encode RFIDs onto the tags.
- In accordance with one aspect of the present disclosure, a computer-implemented method for generating RFID labels using a non-RFID label printer and an RFID encoder that comprises an RFID controller, one or more antennas, a label detector, and an RFID reader, comprises: causing the RFID encoder to be armed; receiving, via the one or more antennas, reader settings, encode settings, and encode data; sensing, using the label detector, a specific tag of unprinted labels; encoding the specific tag with a corresponding RFID based upon the encode data; determining that the encoding of the specific tag is not successful; recording a tag index of the specific tag as bad; and initiating a bad label process.
- In some implementations, the encoder may further comprise a marker label detector, and a marker apparatus. In some examples, the marker apparatus is a hole punch apparatus.
- In some examples, the bad label process comprises: determining the tag index of the specific tag is bad; causing the marker apparatus to be armed; sensing the specific tag via the marker label detector; and marking the specific tag using the marker apparatus.
- In some implementations, the computer-implemented method for generating RFID labels further comprises a synchronization process between the non-RFID label printer and the RFID encoder. The synchronization process comprises: receiving, via the one or more antennas, encode settings and encode data; checking the encode data to determine a corresponding tag ID (TID) of a current tag sensed by the label detector; retrieving a TID list based upon the current TID; arming the encoder; and sending print data to the non-RFID label printer to generate the RFID labels.
- In some implementations, the RFID encoder further comprises one or more clips to attach to the non-RFID label printer (e.g., Epson™ 7500). The one or more clips are configured to accommodate at least one physical feature of the non-RFID label printer. For example, the one or more clips are adapted to a rear feed lip of the non-RFID label printer, a front exit lip of the non-RFID label printer, and/or expansion ports of the non-RFID label printer. In some implementations, the RFID encoder can include multiple RFID readers. The RFID readers can be embedded in a label unwinder or rewinder of the non-RFID label printer.
- In some implementations, the RFID controller of the RFID encoder can intercept printing and encoding jobs from non-RFID label software (e.g., bartender and loftware). A user of the RFID encoder can use common non-RFID label creation software to generate RFID labels.
- In some implementations, the label detector of the RFID encoder only senses one specific tag of RFID labels at a time. Tag singulation (isolation) can be important to ensuring the specific tag being encoded with a correct RFID. In some examples, a window shield is used for the tag singulation. The window shield is capable of being adjusted to accommodate various tag sizes.
- In accordance with another aspect of the present disclosure, a non-transitory computer-readable storage medium storing instructions is provided. The instructions, when executed by a processor of an RFID encoder that comprises an RFID controller, one or more antennas, a label detector, and an RFID reader, cause the processor to perform operations including: causing the RFID encoder to be armed; receiving, via the one or more antennas, reader settings, encode settings, and encode data; sensing, using the label detector, a specific tag of unprinted labels; encoding the specific tag with a corresponding RFID based upon the encode data; determining that the encoding of the specific tag is not successful; recording a tag index of the specific tag as bad; and initiating a bad label process.
- Additional features and advantages of the disclosure will be set forth in the description which follows, and in part, will be obvious from the description, or can be learned by practice of the herein disclosed principles. The features and advantages of the disclosure can be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the disclosure will become more fully apparent from the following description and appended claims, or can be learned by the practice of the principles set forth herein.
- In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific examples thereof which are illustrated in the appended drawings. These drawings depict only example aspects of the disclosure and are not therefore to be considered to be limiting of its scope. The principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
-
FIG. 1A is a schematic block diagram illustrating an exemplary RFID encoder attached to a non-RFID label printer, in accordance with an implementation of the present disclosure; -
FIG. 1B is a schematic block diagram illustrating example positions that the exemplary RFID encoder can be attached to the non-RFID label printer, in accordance with an implementation of the present disclosure; -
FIG. 2 is a schematic block diagram illustrating components of an exemplary RFID encoder interacting with RFID labels, in accordance with an implementation of the present disclosure; -
FIG. 3 is an exemplary method for generating RFID labels using a non-RFID label printer, in accordance with an implementation of the present disclosure; -
FIG. 4 is an exemplary method for synchronizing a non-RFID label printer and an exemplary RFID encoder, in accordance with an implementation of the present disclosure; -
FIG. 5 illustrates an example of synchronizing a print head of a non-RFID label printer and an RFID reader of an RFID encoder, in accordance with an implementation of the present disclosure; -
FIG. 6 illustrates an exemplary system, in accordance with various examples of the present disclosure; -
FIG. 7A-7D illustrate an example of TID-based encoding using an exemplary RFID encoder, in accordance with an implementation of the present disclosure; -
FIG. 7E illustrates an exemplary diagram of communications for synchronizing an Epson 7500™ and a speedway reader of an exemplary RFID encoder, in accordance with an implementation of the present disclosure; and -
FIG. 7F illustrates an exemplary diagram of communications for fetching a new TID list using an exemplary RFID encoder, in an event that TID is not found in a cached TID list, in accordance with an implementation of the present disclosure. - The present disclosure can be embodied in many different forms. Representative embodiments are shown in the drawings, and will herein be described in detail. The present disclosure is an example or illustration of the principles of the present disclosure, and is not intended to limit the broad aspects of the disclosure to the embodiments illustrated. To that extent, elements and limitations that are disclosed, for example, in the Abstract, Summary, and Detailed Description sections, but not explicitly set forth in the claims, should not be incorporated into the claims, singly or collectively, by implication, inference, or otherwise. For purposes of the present detailed description, unless specifically disclaimed, the singular includes the plural and vice versa; and the word “including” means “including without limitation.” Moreover, words of approximation, such as “about,” “almost,” “substantially,” “approximately,” and the like, can be used herein to mean “at,” “near,” or “nearly at,” or “within 3-5% of,” or “within acceptable manufacturing tolerances,” or any logical combination thereof, for example.
- Various examples of the present disclosure provide systems and methods for generating RFID labels using a non-RFID label printer and an easy-to-attach RFID encoder. The RFID encoder comprises an RFID controller coupled to a network, one or more antennas, a label detector, and an RFID reader. The RFID controller receives a packet of reader settings and a packet (array) of encode data via the one or more antennas. As unprinted labels pass through the non-RFID label printer and the RFID encoder, the label detector senses tags of the unprinted labels, and triggers the RFID controller and the non-RFID label printer to encode RFID onto the tags.
-
FIG. 1A is a schematic block diagram 100A illustrating anexemplary RFID encoder 102 attached to anon-RFID label printer 101, in accordance with an implementation of the present disclosure. In this example, theRFID encoder 102 can be packed into two or more encoder units that are clipped onto the front and back of the non-RFID label printer. Asunprinted labels 103 pass through thenon-RFID label printer 101 and theRFID encoder 102, theRFID encoder 102 senses tags of theunprinted labels 103, and encode RFIDs onto the tags. -
FIG. 1B is a schematic block diagram illustrating example positions 105 that the exemplary RFID encoder can be attached to thenon-RFID label printer 101, in accordance with an implementation of the present disclosure. In some examples, the RFID encoder comprises one or more clips to attach to thenon-RFID label printer 101. The one or more clips are configured to accommodate at least one physical feature of thenon-RFID label printer 101. For example, the one or more clips are adapted to a rear feed lip of thenon-RFID label printer 101, a front exit lip of thenon-RFID label printer 101, and/or expansion ports of thenon-RFID label printer 101. In some implementations, the RFID encoder can include multiple RFID readers. The RFID readers can be embedded in a label unwinder or rewinder of thenon-RFID label printer 101. -
FIG. 2 is a schematic block diagram 200 illustrating components of an exemplary RFID encoder interacting with RFID labels, in accordance with an implementation of the present disclosure. In this example, the RFID encoder comprises anRFID controller 111 that is coupled to a network, one ormore antennas 108, alabel detector 107, anRFID reader 112, amarker label detector 109, and amarker apparatus 110. - As
unprinted labels 103 pass through a non-RFID label printer and the RFID encoder, thelabel detector 107 senses tags of theunprinted labels 103, and triggers theRFID controller 108 and aprint head 106 of the non-RFID label printer to encode RFIDs onto the tags. In an event that encoding of aspecific tag 104 is not successful, themarker label detector 109 can sense the specific tag, and cause themarker apparatus 110 to mark the specific tag. For example, themarker apparatus 110 might punch a hole in the specific tag. - Although only certain components are shown within the
exemplary systems FIGS. 1A, 1B and 2 , respectively, various types of electronic or computing components that are capable of processing or storing data, receiving or transmitting signals, or providing fresh air to downstream components, can also be included in theexemplary systems exemplary systems - Depending on the desired implementation for the
exemplary systems exemplary systems FIGS. 1A, 1B and 2 , respectively, are used for purposes of explanation. Therefore, a network system can be implemented with many variations, as appropriate, yet still provide a configuration of network platform in accordance with various examples of the present disclosure. - In exemplary configurations of
FIGS. 1A, 1B and 2 , respectively, theexemplary systems - The above discussion is meant to be illustrative of the principles and various examples of the present disclosure. Numerous variations and modifications will become apparent once the above disclosure is fully appreciated.
-
FIG. 3 is anexemplary method 300 for generating RFID labels using a non-RFID label printer, in accordance with an implementation of the present disclosure. It should be understood that theexemplary method 300 is presented solely for illustrative purposes, and that in other methods in accordance with the present disclosure can include additional, fewer, or alternative steps performed in similar or alternative orders, or in parallel. Theexemplary method 300 starts atstep 302 by arming an RFID encoder. As illustrated above inFIGS. 1A, 1B and 2 , the RFID encoder can comprise an RFID controller that is coupled to a network, one or more antennas, a label detector, an RFID reader, a marker label detector, and a marker apparatus. - At
step 304, the RFID encoder can receive reader settings, encode settings and encode data via the one or more antennas, as illustrated inFIG. 2 . The following Table 1 illustrates an example of user selected encode data and corresponding RFIDs received by the RFID encoder. -
TABLE 1 RFID label Print Encode 1 Pg. 1 EPC1 2 Pg. 2 EPC2 3 Pg. 3 EPC3 4 Pg. 4 EPC4 EPC5 - At
step 306, the encode label detector (e.g., the encodelabel detector 107 illustrated inFIG. 2 ) can sense a specific tag of unprinted labels. Atstep 308, the encoder controller can add one count to an encode tag count. Atstep 310, the encoder can encode the specific tag with a corresponding RFID based upon received encode data. The following Table 2 illustrates an example of encode data and corresponding RFIDs sent to the non-RFID label printer by the RFID encoder. In this example, encode data “EPC5” is removed to match print data while an encode data count is cut short to match a print data count and an RFID label count. -
TABLE 2 RFID label Print Encode 1 Pg. 1 EPC1 2 Pg. 2 EPC2 3 Pg. 3 EPC3 4 Pg. 4 EPC4 - Upon encoding, the encoder can further determine whether encoding of the specific tag is successful, at
step 312. In an event that the encoding of the specific tag is successful, themethod 300 goes back tostep 302. In an event that the encoding of the specific tag is unsuccessful, the RFID encoder records a tag index of the specific tag as “bad,” atstep 314. - At
step 316, the RFID encoder determines whether the specific tag has the tag index as “bad.” In an event that the specific tag has the corresponding tag index recorded as “bad,” the RFID encoder can arm the marker apparatus, atstep 318. The marker label detector (e.g., themarker label detector 109 illustrated inFIG. 2 ) can sense the specific tag, atstep 320. - At
step 322, the encoder controller can add one count to a marker tag count. Atstep 324, the marker apparatus can mark the specific tag to indicate that the specific tag is bad. - In an event that the specific tag does not have a corresponding tag index recorded as “bad,” the
method 300 goes back tostep 302. -
FIG. 4 is anexemplary method 400 for synchronizing a non-RFID label printer and an exemplary RFID encoder, in accordance with an implementation of the present disclosure. Theexemplary method 400 starts atstep 402 by starting a printing job. Atstep 404, an RFID controller of the RFID encoder receives encode settings and encode data via one or more antennas of the RFID encoder. In some examples, the RFID encoder can further comprise a label detector, an RFID reader, a marker label detector, and a marker apparatus. - At
step 406, the RFID controller can check receive the encode data, and, determine a current tag sensed by the label detector. Atstep 408, the RFID controller can determine a corresponding TID of the current tag. Atstep 410, the RFID controller can retrieve a TID list based upon the TID of the current tag. In some implementations, the TID list can be stored on the RFID encoder. In some implementations, the TID list is stored on a server coupled to the network, or cloud. - At
step 412, the RFID controller can cause the RFID encoder to be armed. Atstep 414, the RFID controller can cause the non-RFID label printer to wait until the RFID encoder is ready. In response to determine that the RFID encoder is ready, the RFID controller can send print data to the non-RFID label printer, atstep 416, and cause the non-RFID label printer which is synchronized with the RFID encoder to start to print RFIDs, atstep 418. -
FIG. 5 illustrates an example of synchronizing a print head of a non-RFID label printer and an RFID reader of an RFID encoder, in accordance with an implementation of the present disclosure. In this example, theencoder 102 and thereader 112 are both triggered by thelabel detector 107. Synchronization between the print head and the RFID encoder can take into account of the encoding delay and the verification delay by the RFID encoder. In some implementations, the encoding delay and the verification delay can be calculated based upon sizes of tags to be encoded with RFIDs. -
FIG. 7A-7D illustrate an example of TID-based encoding using an exemplary RFID encoder, in accordance with an implementation of the present disclosure. In this example, the RFID encoder relies on TID filtering to ensure accurate, singulated, and high speed encoding. Before printing/encoding begins, the RFID reader receives a list of every EPC to encode, which can be selected by user. When the job starts, the RFID encoder can detect and discover which tag (TID) is directly underneath the print head, and, subsequently, use that information to determine all next TID's to be expected. The RFID Encoder can use the list of TID's to encode each tag accurately, which ultimately leaves no chance for duplicate encoding, missed encoding, or a registration error in encoding. - At
step 1, Window app sends EPC data to the RFID encoder, which is illustrated inFIG. 7A . Atstep 2, the RFID encoder can detect and discover tag (TID) immediately under antenna by executing a lower power read, which is illustrated inFIG. 7B . Atstep 3, the RFID encoder can generate an EPC/TID matched encode list using discovered TID immediately under antenna, which is illustrated inFIG. 7C . Atstep 4, the RFID encoder can cause a label printer to start print/encode job, and encode each tag that passes using a TID filtered EPC encode, which is illustrated inFIG. 7D . -
FIG. 7E illustrates an exemplary diagram 700E of communications for synchronizing anEpson 7500™ and a speedway reader of an exemplary RFID encoder, in accordance with an implementation of the present disclosure. -
FIG. 7F illustrates an exemplary diagram 700F of communications for fetching a new TID list using an exemplary RFID encoder, in an event that TID is not found in a cached TID list, in accordance with an implementation of the present disclosure. - A brief introductory description of example systems and networks, as illustrated in
FIG. 6 , is disclosed herein. These variations shall be described herein as the various examples are set forth. The present disclosure now turns toFIG. 6 . -
FIG. 6 illustrates anexample computing system 600, in which components of the computing system are in electrical communication with each other using abus 602. Thesystem 600 includes a processing unit (CPU or processor) 630, and asystem bus 602 that couples various system components, including the system memory 604 (e.g., read only memory (ROM) 606 and random access memory (RAM) 608), to theprocessor 630. Thesystem 600 can include a cache of high-speed memory connected directly with, in close proximity to, or integrated as part of theprocessor 630. Thesystem 600 can copy data from thememory 604 and/or thestorage device 612 to thecache 628 for quick access by theprocessor 630. In this way, the cache can provide a performance boost forprocessor 630 while waiting for data. These and other modules can control or be configured to control theprocessor 630 to perform various actions.Other system memory 304 may be available for use as well. Thememory 604 can include multiple different types of memory with different performance characteristics. Theprocessor 630 can include any general purpose processor and a hardware module or software module, such asmodule 1 614,module 2 616, andmodule 3 618 embedded instorage device 612. The hardware module or software module is configured to control theprocessor 630, as well as a special-purpose processor where software instructions are incorporated into the actual processor design. Theprocessor 630 may essentially be a completely self-contained computing system, and containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric. - To enable user interaction with the
computing device 600, aninput device 620 is provided as an input mechanism. Theinput device 620 can comprise a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, and so forth. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with thesystem 300. In this example, anoutput device 622 and adisplay 636 are also provided. Thecommunications interface 624 can govern and manage the user input and system output. -
Storage device 612 can be a non-volatile memory to store data that are accessible by a computer. Thestorage device 612 can be magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 608, read only memory (ROM) 306, and hybrids thereof. - The
controller 610 can be a specialized microcontroller or processor on thesystem 600, such as a baseboard management controller. In some cases, thecontroller 610 can be part of an Intelligent Platform Management Interface (IPMI). Moreover, in some cases, thecontroller 610 can be embedded on a motherboard or main circuit board of thesystem 600. Thecontroller 610 can manage the interface between system management software and platform hardware. Thecontroller 610 can also communicate with various system devices and components (internal and/or external), such as controllers or peripheral components, as further described below. - The
controller 610 can generate specific responses to notifications, alerts, and/or events, and communicate with remote devices or components (e.g., electronic mail message, network message, etc.) to generate an instruction or command for automatic hardware recovery procedures, etc. An administrator can also remotely communicate with thecontroller 610 to initiate or conduct specific hardware recovery procedures or operations, as further described below. - The
controller 610 can also include a system event log controller and/or storage for managing and maintaining events, alerts, and notifications received by thecontroller 610. For example, thecontroller 610 or a system event log controller can receive alerts or notifications from one or more devices and components, and maintain the alerts or notifications in a system event log storage component. -
Flash memory 632 can be an electronic non-volatile computer storage medium or chip that can be used by thesystem 600 for storage and/or data transfer. Theflash memory 632 can be electrically erased and/or reprogrammed.Flash memory 632 can include EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), ROM, NVRAM, or CMOS (complementary metal-oxide semiconductor), for example. Theflash memory 632 can store thefirmware 634 executed by thesystem 600, when thesystem 600 is first powered on, along with a set of configurations specified for thefirmware 634. Theflash memory 632 can also store configurations used by thefirmware 634. - The
firmware 634 can include a Basic Input/Output System or equivalents, such as an EFI (Extensible Firmware Interface) or UEFI (Unified Extensible Firmware Interface). Thefirmware 634 can be loaded and executed as a sequence program each time thesystem 600 is started. Thefirmware 634 can recognize, initialize, and test hardware present in thesystem 600 based on the set of configurations. Thefirmware 634 can perform a self-test, such as a POST (Power-on-Self-Test), on thesystem 600. This self-test can test functionality of various hardware components such as hard disk drives, optical reading devices, cooling devices, memory modules, expansion cards, and the like. Thefirmware 634 can address and allocate an area in thememory 604,ROM 606,RAM 608, and/orstorage device 612, to store an operating system (OS). Thefirmware 634 can load a boot loader and/or OS, and give control of thesystem 600 to the OS. - The
firmware 634 of thesystem 600 can include a firmware configuration that defines how thefirmware 634 controls various hardware components in thesystem 600. The firmware configuration can determine the order in which the various hardware components in thesystem 600 are started. The firmware 334 can provide an interface, such as an UEFI, that allows a variety of different parameters to be set, which can be different from parameters in a firmware default configuration. For example, a user (e.g., an administrator) can use thefirmware 634 to specify clock and bus speeds; define what peripherals are attached to thesystem 600; set monitoring of health (e.g., fan speeds and CPU temperature limits); and/or provide a variety of other parameters that affect overall performance and power usage of thesystem 600. Whilefirmware 634 is illustrated as being stored in theflash memory 632, one of ordinary skill in the art will readily recognize that thefirmware 634 can be stored in other memory components, such asmemory 604 orROM 606. -
System 600 can include one ormore sensors 626. The one ormore sensors 626 can include, for example, one or more temperature sensors, thermal sensors, oxygen sensors, chemical sensors, noise sensors, heat sensors, current sensors, voltage detectors, air flow sensors, flow sensors, infrared thermometers, heat flux sensors, thermometers, pyrometers, etc. The one ormore sensors 626 can communicate with the processor,cache 628,flash memory 632,communications interface 624,memory 604,ROM 606,RAM 608,controller 610, andstorage device 612, via thebus 602, for example. The one ormore sensors 626 can also communicate with other components in the system via one or more different means, such as inter-integrated circuit (I2C), general purpose output (GPO), and the like. Different types of sensors (e.g., sensors 626) on thesystem 600 can also report to thecontroller 610 on parameters, such as cooling fan speeds, power status, operating system (OS) status, hardware status, and so forth. - It can be appreciated that
example system 600 can have more than one processor (e.g., 630), or be part of a group or cluster of computing devices networked together to provide greater processing capability. - For clarity of explanation, in some instances, the present disclosure may be presented as including individual functional blocks including functional blocks, including devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
- In some embodiments, the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
- Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can include, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used, can be accessible over a network. The computer executable instructions may be, for example, binaries and intermediate format instructions, such as assembly language, firmware, or source code.
- Devices implementing methods according to these disclosures can include hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rack-mount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips, or different processes executing in a single device, by way of further example.
- The various examples can be further implemented in a wide variety of operating environments, which in some cases can include one or more server computers, user computers or computing devices which can be used to operate any of a number of applications. User or client devices can include any of a number of general purpose personal computers, such as desktop or laptop computers running a standard operating system, as well as cellular, wireless, and handheld devices running mobile software, and capable of supporting a number of networking and messaging protocols. Such a system can also include a number of workstations running any of a variety of commercially-available operating systems, and other known applications for purposes such as development and database management. These devices can also include other electronic devices, such as dummy terminals, thin-clients, gaming systems, and other devices capable of communicating via a network.
- To the extent examples, or portions thereof, are implemented in hardware, the present disclosure can be implemented with any, or a combination of, the following technologies: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals; an application specific integrated circuit (ASIC) having appropriate combinational logic gates; programmable hardware such as a programmable gate array(s) (PGA); and/or a field programmable gate array (FPGA); etc.
- Most examples utilize at least one network that would be familiar to those skilled in the art for supporting communications using any of a variety of commercially-available protocols, such as TCP/IP, OSI, FTP, UPnP, NFS, CIFS, AppleTalk etc. The network can be, for example, a local area network, a wide-area network, a virtual private network, the Internet, an intranet, an extranet, a public switched telephone network, an infrared network, a wireless network, and any combination thereof.
- Devices implementing methods, according to these technologies, can include hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include server computers, laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips, or different processes executing in a single device, by way of further example.
- In examples that utilize a Web server, the Web server can run any variety of server or mid-tier applications, including HTTP servers, FTP servers, CGI servers, data servers, Java servers, and business application servers. In response to requests from user devices, the Web server(s) can also be capable of executing programs or scripts. For example, the Web server can execute one or more Web applications, which can be implemented as one or more scripts or programs written in any programming language, such as Java®, C, C # or C++ or any scripting language, such as Perl, Python or TCL, as well as combinations thereof. The Web server(s) can also encompass database servers, including those commercially available on the open market.
- The system can include a variety of data stores and other memory and storage media, as discussed above. These can reside in a variety of locations, such as on a storage medium local to (and/or resident in) one or more of the computers, or remote from any or all of the computers across the network. In a particular set of examples, the information can reside in a storage-area network (SAN) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers, servers, or other network devices can be stored locally and/or remotely, as appropriate. Where a system includes computerized devices, each such device can include hardware elements that can be electrically coupled via a bus, the elements including, for example, at least one central processing unit (CPU), at least one input device (e.g., a mouse, keyboard, controller, touch-sensitive display element or keypad), and at least one output device (e.g., a display device, printer or speaker). Such a system can also include one or more storage devices, such as disk drives, optical storage devices, and solid-state storage devices such as random access memory (RAM) or read-only memory (ROM), as well as removable media devices, memory cards, flash cards, etc.
- Storage media and computer readable media for containing code, or portions of code, can include any appropriate media known or used in the art, including storage media and computing media. The storage media and computing media can include, but are not limited to, removable and non-removable media for storage and/or transmission of data or information. The removable and non-removable media comprise RAM, ROM, EPROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage devices that can be used to store the desired information and that can be accessed by a system device. The data or information can include computer readable instructions, data structures, program modules, or other data. Based on the technology and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the various aspects of the present disclosure.
- The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes can be made thereunto without departing from the broader spirit and scope of the patent application, as set forth in the claims.
Claims (20)
1. A computer-implemented method for generating RFID labels using a non-RFID label printer, comprising:
causing an RFID encoder to be armed, the RFID encoder attached to the non-RFID label printer, the RFID encoder comprising an RFID controller, one or more antennas, a label detector, and an RFID reader;
receiving, via the one or more antennas, reader settings, encode settings, and encode data;
sensing, using the label detector, a specific tag of unprinted labels;
encoding the specific tag with a corresponding RFID based upon the encode data;
determining that the encoding of the specific tag is not successful;
recording a tag index of the specific tag as bad; and
initiating a bad label process.
2. The computer-implemented method of claim 1 , wherein the RFID encoder further comprises a marker label detector, and a marker apparatus.
3. The computer-implemented method of claim 2 , wherein the marker apparatus is a hole punch apparatus.
4. The computer-implemented method of claim 2 , further comprising:
determining the tag index of the specific tag is bad;
causing the marker apparatus to be armed;
sensing the specific tag via the marker label detector; and
marking the specific tag using the marker apparatus.
5. The computer-implemented method of claim 1 , further comprising:
checking the encode data to determine a corresponding tag ID (TID) of a current tag sensed by the label detector;
retrieving a TID list based upon the current TID;
arming the RFID encoder; and
upon the RFID encoder being armed, sending print data to the non-RFID label printer to generate the RFID labels.
6. The computer-implemented method of claim 1 , wherein the RFID encoder is attached to the non-RFID label printer via one or more clips, the one or more clips configured to accommodate at least one physical feature of the non-RFID label printer.
7. The computer-implemented method of claim 6 , wherein the one or more clips are adapted to a rear feed lip of the non-RFID label printer, a front exit lip of the non-RFID label printer, and/or expansion ports of the non-RFID label printer.
8. The computer-implemented method of claim 1 , wherein the RFID encoder includes multiple RFID readers, the RFID readers embedded in a label unwinder or rewinder of the non-RFID label printer.
9. A system, comprising:
a processor; and
a computer-readable medium storing instructions that, when executed by the processor, cause the system to perform operations comprising:
causing an RFID encoder to be armed, the RFID encoder attached to a non-RFID label printer, the RFID encoder comprising an RFID controller, one or more antennas, a label detector, and an RFID reader;
receiving, via the one or more antennas, reader settings, encode settings, and encode data;
sensing, using the label detector, a specific tag of unprinted labels;
encoding the specific tag with a corresponding RFID based upon the encode data;
determining that the encoding of the specific tag is not successful;
recording a tag index of the specific tag as bad; and
initiating a bad label process.
10. The system of claim 9 , wherein the RFID encoder further comprises a marker label detector, and a marker apparatus.
11. The system of claim 10 , wherein the marker apparatus is a hole punch apparatus.
12. The system of claim 10 , wherein the computer-readable medium storing instructions that, when executed by the processor, further cause the system to perform operations comprising:
determining the tag index of the specific tag is bad;
causing the marker apparatus to be armed;
sensing the specific tag via the marker label detector; and
marking the specific tag using the marker apparatus.
13. The system of claim 9 , wherein the computer-readable medium storing instructions that, when executed by the processor, further cause the system to perform operations comprising:
checking the encode data to determine a corresponding tag ID (TID) of a current tag sensed by the label detector;
retrieving a TID list based upon the current TID;
arming the RFID encoder; and
upon the RFID encoder being armed, sending print data to the non-RFID label printer to generate the RFID labels.
14. The system of claim 9 , wherein the RFID encoder is attached to the non-RFID label printer via one or more clips, the one or more clips configured to accommodate at least one physical feature of the non-RFID label printer.
15. The system of claim 14 , wherein the one or more clips are adapted to a rear feed lip of the non-RFID label printer, a front exit lip of the non-RFID label printer, and/or expansion ports of the non-RFID label printer.
16. The system of claim 9 , wherein the RFID encoder includes multiple RFID readers, the RFID readers embedded in a label unwinder or rewinder of the non-RFID label printer.
17. A non-transitory computer-readable storage medium including instructions that, when executed by at least one processor of a system, cause the system to perform operations comprising:
causing an RFID encoder to be armed, the RFID encoder attached to a non-RFID label printer, the RFID encoder comprising an RFID controller, one or more antennas, a label detector, and an RFID reader;
receiving, via the one or more antennas, reader settings, encode settings, and encode data;
sensing, using the label detector, a specific tag of unprinted labels;
encoding the specific tag with a corresponding RFID based upon the encode data;
determining that the encoding of the specific tag is not successful;
recording a tag index of the specific tag as bad; and
initiating a bad label process.
18. The non-transitory computer-readable storage medium of claim 17 , wherein the RFID encoder further comprises a marker label detector, and a marker apparatus.
19. The non-transitory computer-readable storage medium of claim 18 , wherein the instructions, when executed by the at least one processor of the system, further cause the system to perform operations comprising:
determining the tag index of the specific tag is bad;
causing the marker apparatus to be armed;
sensing the specific tag via the marker label detector; and
marking the specific tag using the marker apparatus.
20. The non-transitory computer-readable storage medium of claim 17 , wherein the instructions, when executed by the at least one processor of the system, further cause the system to perform operations comprising:
checking the encode data to determine a corresponding tag ID (TID) of a current tag sensed by the label detector;
retrieving a TID list based upon the current TID;
arming the RFID encoder; and
upon the RFID encoder being armed, sending print data to the non-RFID label printer to generate the RFID labels.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/506,514 US20220144547A1 (en) | 2017-03-21 | 2021-10-20 | Method and system for generating rfid labels using rfid encoder attachment |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201762601396P | 2017-03-21 | 2017-03-21 | |
PCT/US2018/023531 WO2018175558A1 (en) | 2017-03-21 | 2018-03-21 | Method and system for generating rfid labels using rfid encoder attachment |
US201916496232A | 2019-09-20 | 2019-09-20 | |
US17/506,514 US20220144547A1 (en) | 2017-03-21 | 2021-10-20 | Method and system for generating rfid labels using rfid encoder attachment |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/496,232 Continuation US11161692B2 (en) | 2017-03-21 | 2018-03-21 | Method and system for generating RFID labels using RFID encoder attachment |
PCT/US2018/023531 Continuation WO2018175558A1 (en) | 2017-03-21 | 2018-03-21 | Method and system for generating rfid labels using rfid encoder attachment |
Publications (1)
Publication Number | Publication Date |
---|---|
US20220144547A1 true US20220144547A1 (en) | 2022-05-12 |
Family
ID=63586585
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/496,232 Active 2038-11-03 US11161692B2 (en) | 2017-03-21 | 2018-03-21 | Method and system for generating RFID labels using RFID encoder attachment |
US17/506,514 Abandoned US20220144547A1 (en) | 2017-03-21 | 2021-10-20 | Method and system for generating rfid labels using rfid encoder attachment |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/496,232 Active 2038-11-03 US11161692B2 (en) | 2017-03-21 | 2018-03-21 | Method and system for generating RFID labels using RFID encoder attachment |
Country Status (3)
Country | Link |
---|---|
US (2) | US11161692B2 (en) |
JP (1) | JP2020515997A (en) |
WO (1) | WO2018175558A1 (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018175558A1 (en) * | 2017-03-21 | 2018-09-27 | Flexstr8, Inc. | Method and system for generating rfid labels using rfid encoder attachment |
US11216713B2 (en) | 2020-03-16 | 2022-01-04 | Lundy Smith | Post printing RF tag assignment |
CN115503354B (en) * | 2022-09-14 | 2023-07-25 | 小彩牛智能技术(深圳)有限公司 | RFID label printer and label printing method thereof |
CN116451727B (en) * | 2023-06-16 | 2023-08-22 | 上海英内物联网科技股份有限公司 | Method for continuously coding RFID (radio frequency identification) tag based on artificial intelligence |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8159349B2 (en) * | 2005-08-19 | 2012-04-17 | Adasa Inc. | Secure modular applicators to commission wireless sensors |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6593853B1 (en) * | 2000-02-18 | 2003-07-15 | Brady Worldwide, Inc. | RFID label printing system |
JP4865151B2 (en) * | 2001-06-14 | 2012-02-01 | サトーホールディングス株式会社 | Printer |
US7609406B2 (en) | 2002-08-16 | 2009-10-27 | Avery Dennison Retail Information Services, Llc | Hand held portable printer with RFID read write capability |
US7114654B2 (en) * | 2004-04-15 | 2006-10-03 | Printronix | RFID encoder and verifier |
JP4223991B2 (en) * | 2004-05-14 | 2009-02-12 | 東芝テック株式会社 | Wireless communication apparatus and printer |
US20060071063A1 (en) * | 2004-09-29 | 2006-04-06 | Duckett Jeanne F | RFID printer system, method of printing and sets of record members |
US7416121B2 (en) * | 2004-12-17 | 2008-08-26 | Intermec Ip Corp. | Stand-alone proxy RFID read/write unit for print label encoding |
FR2888973B1 (en) * | 2005-07-22 | 2007-10-26 | K Sa As | OPTICAL READING AND RADIOFREQUENCY ENCODING DEVICE ADAPTABLE TO PRINTER OUTPUT OF IDENTIFICATION LABELS |
JP2007076067A (en) * | 2005-09-12 | 2007-03-29 | Ricoh Co Ltd | Image forming apparatus |
JP2010081371A (en) * | 2008-09-26 | 2010-04-08 | Nec Electronics Corp | Frame processing circuit |
US8154574B2 (en) * | 2008-10-23 | 2012-04-10 | Avery Dennison Corporation | Hand-held portable printer system and method |
JP5665695B2 (en) * | 2011-07-12 | 2015-02-04 | マイティカード株式会社 | RFID tag movement identification method and RFID tag movement identification program |
US8896425B1 (en) | 2011-08-23 | 2014-11-25 | Lawrence J Martin | Apparatus and method for serialized continuous encoding of RFID tags |
EP2746992A1 (en) * | 2012-12-20 | 2014-06-25 | Bernard Barink | Method and apparatus for providing printed and encoded RFID tags |
JP6250319B2 (en) * | 2013-07-12 | 2017-12-20 | サトーホールディングス株式会社 | RFID communication apparatus and communication method |
JP3199328U (en) * | 2015-03-24 | 2015-08-20 | 有限会社コスモシステム | RF tag label printing system and RF label printing system kit |
WO2018175558A1 (en) * | 2017-03-21 | 2018-09-27 | Flexstr8, Inc. | Method and system for generating rfid labels using rfid encoder attachment |
-
2018
- 2018-03-21 WO PCT/US2018/023531 patent/WO2018175558A1/en active Application Filing
- 2018-03-21 US US16/496,232 patent/US11161692B2/en active Active
- 2018-03-21 JP JP2020501420A patent/JP2020515997A/en active Pending
-
2021
- 2021-10-20 US US17/506,514 patent/US20220144547A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8159349B2 (en) * | 2005-08-19 | 2012-04-17 | Adasa Inc. | Secure modular applicators to commission wireless sensors |
Also Published As
Publication number | Publication date |
---|---|
WO2018175558A1 (en) | 2018-09-27 |
US20200290807A1 (en) | 2020-09-17 |
US11161692B2 (en) | 2021-11-02 |
JP2020515997A (en) | 2020-05-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20220144547A1 (en) | Method and system for generating rfid labels using rfid encoder attachment | |
US20190220340A1 (en) | System and method for remote system recovery | |
EP3470956A1 (en) | Dynamically adjust maximum fan duty in a server system | |
EP3460653A1 (en) | Preserving firmware setting during firmware update | |
US10110031B2 (en) | Charging method and charging apparatus for electronic device | |
US9703995B2 (en) | Portable terminal, imaging apparatus, communication system, communication method of portable terminal, communication method of imaging apparatus, and computer readable storage device | |
US11057762B2 (en) | Electronic device and method for switching electronic device between dual standby mode and single standby mode | |
US8156272B2 (en) | Multiple communication channels on MMC or SD CMD line | |
US9026629B2 (en) | Graceful out-of-band power control of remotely-managed computer systems | |
US10533563B2 (en) | Management of multiple fan modules | |
US9772863B2 (en) | Methods for copying information handling system configuration settings | |
CN110941323B (en) | Computer implementation method, computing device and computer readable storage medium | |
WO2017032112A1 (en) | Method for communicating with board having no central processing unit and communication device | |
EP3614570A1 (en) | Near filed communication (nfc) device and system | |
EP3442166B1 (en) | Composing by network attributes | |
US20170185462A1 (en) | System and method for synchronization using device pairings with docking stations | |
US8698629B1 (en) | RFID readers with encapsulating commands | |
US11681807B2 (en) | Information handling system with mechanism for reporting status of persistent memory firmware update | |
US11941127B2 (en) | Firmware password management | |
CN116126613A (en) | Position detection method and device of PCIe (peripheral component interconnect express) equipment, electronic equipment and storage medium | |
CN103428397A (en) | Image information processing method and device | |
US20160180122A1 (en) | Radio frequency identification (rfid) based defect detection in ssds | |
US20160086479A1 (en) | Method for controlling alarm and electronic device supporting the same | |
KR101028532B1 (en) | Mobile remote rfid tag data process terminal | |
US11431820B1 (en) | Method and system for implementing inter-process communications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |