SYSTEMS AND METHODS FOR BLOCKING RADIO FREQUENCY TAGS

Abstract

A method in a media processing device, wherein the method comprises: obtaining a parameter set corresponding to a radio frequency tag (RF tag) associated with a media stock; receiving a first command to lock the radio frequency tag (RF tag); generating a second command, the second command comprising the parameter set; and initiating an operation to lock the RF tag based on the second command.

Description

RELATED REGISTRATIONS

[0001] The present application claims the priority and benefits of the preliminary US application No. 63 / 703,024, filed on October 3, 2024, which is incorporated in full by reference into the present application. BACKGROUND

[0002] Radio frequency tags (RF tags) can be used to store a wide variety of data, such as product identifiers and the like. RF tags can have multiple memory banks and implement functionality to lock these memory banks in response to lock commands. The variable implementation of this functionality in different types of RF tags can cause lock commands to fail. BRIEF DESCRIPTION OF THE MULTIPLE VIEWS OF THE DRAWINGS

[0003] The accompanying figures, in which the same reference numerals denote identical or functionally similar elements in the individual views, are included in the document together with the detailed description below and form an integral part thereof, and they serve to illustrate embodiments of concepts which include the claimed invention and to explain various principles and advantages of these embodiments. Fig. Figure 1 is a schematic view of a media processing device. Fig. 2 is a cross-sectional view of the media processing device of Fig. 1. Fig. Figure 3 is a flowchart of a procedure for blocking radio frequency tags. Fig. Figure 4 is a schematic view illustrating an exemplary implementation of blocks 310, 312, 315 and 320 of the procedure of Fig. 3 represents. Fig. Figure 5 is a schematic view showing an exemplary implementation of Block 340 of the procedure of Fig. 3 represents. Fig. Figure 6 is a flowchart of an additional part of the procedure of Fig. 3.

[0004] Experts will recognize that elements in the figures are depicted for the sake of simplicity and clarity and are not necessarily drawn to scale. For example, the dimensions of some elements in the figures may have been exaggerated in relation to other elements to help improve the understanding of embodiments of the present disclosure.

[0005] The apparatus and process components have been represented in the drawings, where appropriate, by conventional symbols, showing only those specific details relevant to understanding the embodiments of the present disclosure, so as not to overburden the disclosure with details that are readily apparent to persons skilled in the art who have access to the present description. DETAILED DESCRIPTION

[0006] Examples disclosed in this document relate to a method in a media processing device, the method comprising: obtaining a parameter set corresponding to a radio frequency tag (RF tag) associated with a media stock; receiving a first command to lock the radio frequency tag (RF tag); generating a second command, the second command comprising the parameter set; and initiating an operation to lock the RF tag based on the second command.

[0007] Other examples disclosed in this document relate to a device comprising: a housing; a printhead arranged in the housing, the printhead being configured to print a media supply; a radio frequency transcoder (RF transcoder) (e.g., encoder / reader) arranged in the housing; and a controller configured to: obtain a parameter set corresponding to a radio frequency tag (RF tag) associated with a media supply; receive a first command to lock the radio frequency tag (RF tag); generate a second command, the second command comprising the parameter set; and initiate an operation to lock the RF tag based on the second command.

[0008] Fig. Figure 1 shows an exemplary device in the form of a media processing device 100, such as a label printer (also referred to in this document as the printer 100). The printer 100 can be configured as a desktop printer, as shown. The printer 100 can also be configured in a wide variety of other forms, including as a mobile printer, tabletop or industrial printer, or the like. The printer 100 has various components configured to apply characters to media such as individual labels, a continuous paper strip, identity cards, or the like. The characters can be applied, for example, by direct thermal printing, thermal transfer printing, or the like. In other examples, the media processing device 100 can include an array of a radio frequency transcoder (RF transcoder) (e.g.,have encoders / readers configured to read data from RF tags embedded in the labels, to write data to RF tags embedded in labels or other media, in addition to or instead of applying characters to the media.

[0009] The printer 100 has a housing 104 that accommodates a media supply, a printhead, and other components, as well as a cover or flap 108 configured to open (e.g., in one direction 112) to provide access to the interior of the printer 100. Furthermore, the printer 100 has an outlet 116 from which processed media (e.g., labels with characters applied inside the housing 104 of the printer 100) are ejected.

[0010] Fig. Figure 2 shows a simplified cross-sectional view of printer 100 along the in Fig. 1 depicted plane 120. As in Fig. As can be seen in Figure 2, the housing 104 and the cover 108 define a chamber 200 for receiving one or more media supplies, such as a roll 208 of paper, labels, or the like, a media cassette 204 (also referred to in this document as a supply 204) containing a roll 208 of paper, labels, or the like, or other media supplies. In other examples, the media supplies received in the chamber 200 may include packages of zigzag-folded labels, identification cards, or the like. In still other examples, the printer 100 may have an inlet in the housing 104 for receiving media from an external supply, for example, so that it can be fed through the chamber 200 for processing.

[0011] Media 212 from the supply 204 (e.g., from the roll 208 in the illustrated example) move along a media path from the supply 204 to a roller gap formed by a printhead 216 and a pressure roller 220. The media path can be defined by surfaces, rollers, and the like, for example, by a guide roller 218 (e.g., a passive or non-driven roller). The pressure roller 220 can be driven, e.g., to pull the media 212 along the media path and through the roller gap, where the printhead 216 applies characters to the media 212. The processed media (e.g., those bearing characters applied by the printhead 216) are then output at the outlet 116.The device 100 also includes an RF transcoder 224, which, for example, has one or more antennas and associated controllers and is configured to read data from and / or write data to RF tags embedded in the media. For example, the supply 204 can be a roll of labels, from which an exemplary label 225 with an embedded RF tag 226 is taken. Fig. 2 is shown as a top view.

[0012] In some examples, the printhead 216 can be omitted, and the device 100 can be configured as an RF read and / or write device, which, for example, includes the RF transcoder 224 and does not require pigment-based printing functionality.

[0013] Furthermore, the device 100 has a control subsystem 228. As in Fig. As shown in Figure 2, the control subsystem 228 can include a controller 230, such as a central processing unit (CPU), an application-specific integrated circuit (ASIC), or the like, which is connected to and / or integrated with a memory 234 that stores multiple computer-executable instructions. The instructions can, for example, include a control application 236, which may be executed as firmware or the like. The memory 234 can also store one or more repositories, such as lookup tables or the like. In this example, the memory 234 stores a repository 238 with RF tag attributes. The repository 238 can be a structured file based, for example, on an extensible markup language (XML) schema or the like.

[0014] The subsystem 228 may also include a communication interface 240, which may have, for example, one or more antennas and / or data ports and associated control hardware, enabling the device 100 to communicate with other computer devices. For example, the device 100 may receive media processing commands from a host computer device (e.g., a desktop computer, a smartphone, a server, or the like) containing data such as text, images, or the like to be printed on media from the supply 204 (e.g., on a specific label). The device 100 may also receive data to be written to an RF tag embedded in the media. For example, the command may include an electronic product identifier (EPC) to be written to the RF tag 226 of a specific label 225.

[0015] To execute a media processing command, the controller 230 can control the printhead 216 to apply characters to the media 212, for example by activating thermal elements of the printhead 216 to apply heat to corresponding sections of the media 212. As will be evident to experts in this field, with direct thermal printers, such as in Fig. As shown in Figure 2, applying heat to a section of the media 212 activates a thermochromic pigment in the media 212. In thermal transfer printers, a pigment-carrying ribbon (not shown) can cross the roller gap containing the media 212, and applying heat to a section of the media 212 and the ribbon can cause the transfer of pigment from the ribbon to the media 212.

[0016] Furthermore, the controller 230 can control the RF transcoder 224 to read data from the RF tag 226 and / or write data from a media processing command to the RF tag 226. For example, the controller 230 can be configured to operate the RF transcoder 224 to read data stored in a tag identifier memory bank (TID memory bank) of the RF tag 226. The TID data may include a model number of the RF tag 226 (which may be the same for each RF tag 226 in role 208, for example), a serial number corresponding to the RF tag 226, or the like.

[0017] Furthermore, the controller 230 can be configured to operate the RF transcoder 224 in such a way that it writes data contained in the aforementioned command to a memory location of the RF tag 226. A wide variety of data can be written to the RF tag 226, including, for example, an electronic product code (EPC) or other article identifier. The RF tag 226 can have an EPC memory bank onto which such information can be written. In some application scenarios, it may be desirable to lock the contents of one or more memory banks of the RF tag 226, for example, to prevent manipulation or unintentional overwriting of data. The RF tag 226 can be configured to place each memory bank into one of several predefined access states. For example, a specific memory bank can be locked so that it cannot be written to until it has been (e.g.,The memory bank can be unlocked with an access password. It can also be permanently locked (also called permanently locked), so that it can no longer be written to under any circumstances. In some examples, memory banks can also be unlocked (and therefore writable) and permanently unlocked (e.g., writable but not lockable).

[0018] Locking or permanently locking an RF tag 226 involves, for example, executing a lock command via the RF transcoder 224. Although different types of RF tags 226 (e.g., different RF tag models from different manufacturers) can support locked and permanently locked states, locking or permanently locking different types of RF tags 226 may require the use of different lock or permanently locking commands. For example, a lock or permanently locking command may include multiple parameters that (independently) specify which memory banks are to be locked. If the device 100 is intended to use multiple types of RF tags, locking errors may occur if the operator does not include all parameters corresponding to the banks to be locked. For example, the operator may intend to issue a permanently locking command to permanently lock all memory banks in the RF tag 226.However, if the operator omits a parameter for permanently locking one of the memory banks, the memory bank corresponding to the omitted parameter will not be locked, and the operator will not notice that the memory bank is unlocked (without attempting to write to the memory bank). Furthermore, some RF tags 226 may omit certain memory banks (for example, an auxiliary or "user" memory bank) that are included in other RF tags. Other RF tags 226 may not support certain locking parameters, such as a parameter that identifies the TID memory bank. If a lock command that identifies the TID bank or an omitted memory bank is executed on such an RF tag 226, the command may fail (for example, causing the RF tag 226 to remain unlocked and / or generating an error).

[0019] The aforementioned lock or persistent lock commands can, in some examples, be received by device 100 from a host application running on another computer device. In such implementations, the host application may be responsible for providing device 100 with a correctly formatted lock or persistent lock command. The range of host applications and the companies that develop and maintain such applications, as well as the variety of available RF tags, can result in incorrectly formatted lock or persistent lock commands and thus failed or inadequate lock operations.

[0020] As discussed below, Device 100 is configured to implement tag-lock functionality, which allows Device 100 to receive a generic or universal command, for example, to permanently lock an RF tag 226 (although this functionality may also be used for locking in addition to or instead of permanent locking). The command received by Device 100 can be described as generic or universal because the same command can be used for multiple types of RF tags 226 with heterogeneous permanent-lock command formats.The device 100 is further configured to generate a specific permanent lock command, based on the generic or universal command and on a parameter set specific to the RF tag 226, which, for example, was obtained from the repository 238 or is based on certain properties read from the RF tag 226, which is to be applied to the specific RF tag 226 to be locked.

[0021] Now on Fig. 3. With reference to this, a method 300 for locking or permanently locking RF tags is presented. The method 300 is described in connection with its implementation in the device 100 and, in particular, by the controller 230, through the execution of the application 236. The following discussion refers to commands for permanently locking the RF tag 226; however, it is understood that the functionality described below can also be used to perform other state changes on the RF tag 226, including locking (e.g., temporary locking).

[0022] In block 305, device 100 is configured to receive a command, for example, from another computer device that is in communication with device 100. The command may be called a media processing command and may include a command to read data, such as TID data, from RF tag 226. In other examples, the command may include data to be written to RF tag 226 and / or data to be printed on label 225. In some examples, the command may also include a persistent lock command configured to permanently lock the memory banks of RF tag 226.

[0023] At block 310, device 100 is configured to determine whether lock configuration data has been set on device 100. For example, device 100 can manage current lock configuration data that defines a set of memory banks to be identified in persistent lock commands applied to RF tag 226. The lock configuration data can be stored in a buffer, register, or the like on device 100 and can be reset (e.g., discarded) when device 100 powers on, cover 108 is closed, or the like. In other words, device 100 can be configured to discard or otherwise reset the lock configuration data in response to any event that might coincide with the installation of a new media supply 204 in device 100.

[0024] If the determination at block 310 is affirmative, meaning that current lock configuration data is available, then device 100 can proceed to execute the command from block 305. In other words, an affirmative determination at block 310 means that a previous execution of procedure 300 has resulted in the storage of current lock configuration data for the current media supply 204.

[0025] If the determination at block 310 is negative, then device 100 is configured to obtain a parameter set corresponding to RF tag 226 for use in generating a permanent lock command. Device 100 is configured to read one or more tag attributes at block 312. For example, device 100 may be configured to read TID data from a TID memory bank of RF tag 226. Fig. 4. For reference, exemplary components of the RF tag 226 are shown therein. The RF tag 226 has an antenna 400, e.g., a wire coil, conductor tracks, or the like, as well as an integrated circuit 404 comprising one or more memory banks. The memory of the integrated circuit 404 can be, as in Fig. Figure 4 shows a TID bank 408 containing the aforementioned TID data. The memory may also include an EPC bank 412, which is configured, for example, to be written to by the RF transcoder 224. The EPC bank 412 can also be referred to as writable memory for the RF tag 226, insofar as the EPC bank 412 can be the primary destination for data written by the device 100. The memory may also contain a reserved bank 416, which stores, for example, access data (e.g., a "kill" password used to disable RF tag 226 and an access password used to unlock RF tag 226) used to disable RF tag 226 or to lock or unlock the EPC bank or other parts of the memory (though not necessarily TID bank 408, which, as noted above, may be permanently locked).

[0026] Some RF tags (226) may also have a writable auxiliary bank (420), which can be referred to as a "user" bank. The auxiliary bank (420) may have a smaller writable capacity than the EPC bank and may be used for specific application data. Some RF tags (226) do not have auxiliary banks (420).

[0027] Now back on Fig. 3 With reference to block 312, device 100 can be configured to read TID data 424, such as a tag serial number “123456” and a model number “00991”, from TID bank 408, as shown in Fig. 4 is shown. Again on Fig. 3. With reference to block 315, device 100 can be configured to determine whether repository 238 contains locking configuration data corresponding to RF tag 226, for example by searching for the model number in repository 238. If the determination at block 315 is affirmative, as in Fig. If this is the case, device 100 proceeds to block 320. At block 320, device 100 sets the current lock configuration data according to the stored configuration retrieved from repository 238.

[0028] As in Fig. As shown in Figure 4, the model number "00991" appears in the repository. Device 100 is therefore configured to retrieve the parameter set "k,a,e" from block 320 and update current lock configuration data 428 (which was previously empty or unassigned) to current lock configuration data 428a so that it contains the parameter set from repository 238. A wide variety of parameters can be implemented. The in Fig. The four example parameters shown include "k", which corresponds to part of bank 416 containing a "kill password", "a", which corresponds to part of bank 416 containing an access password, "e", which corresponds to EPC bank 412, and "u", which corresponds to auxiliary bank 420. Other parameters can also be used, for example, a parameter "t", which corresponds to TID bank 408.

[0029] Device 100 can also include, for example in the lock configuration data 428a, a specification of the source of the active parameters (e.g., in this example, repository 238). (Repeatedly on) Fig. 3 With reference to this, after setting the lock configuration data 428a at block 320, device 100 is configured to proceed to execute the command from block 305, as discussed in more detail below.

[0030] If the determination at block 315 is negative, then device 100 is configured to proceed to block 325. If no preconfigured lock configuration data is available, device 100 is configured to attempt to derive lock configuration data for RF tag 226 (which can then be retained and used for any further RF tags 226 until the media supply 204 is replaced). At block 325, device 100 is configured to determine whether RF tag 226 has an auxiliary memory bank 420. For example, device 100 may attempt to read auxiliary memory bank 420, and if the read operation fails, then the determination at block 325 is negative.

[0031] If the determination at block 325 is affirmative, then the device 100 is configured at block 330 to set the current lock configuration 428 so that it contains a first predefined parameter set, which is contained, for example, within the application 236 or stored separately from the repository 238 in some other way. For example, the device 100 can be configured to set the lock configuration data 428 so that it includes the parameters "k, a, e, u", which include the parameter "u" because the RF tag 226 has a user bank 420.

[0032] If the determination at block 325 is negative, then device 100 is configured to set the current lock configuration 428 at block 335 to include a second predefined parameter set. For example, device 100 may be configured to set the lock configuration data 428 to include the parameters "k, a, e", omitting the parameter "u" because the RF tag 226 does not have a user bank 420.

[0033] After executing block 330 or 335, or after executing block 320 as mentioned above, device 100 is configured to proceed to block 340. At block 340, device 100 is configured to generate and execute a new command based on the command from block 305 and the lock configuration data set by block 320, 330, or 335. As will be evident, in some cases the command from block 305 is a read command or the like, and device 100 can execute the command unchanged. However, if the command from block 305 is a lock command or includes a lock command, then device 100 is configured to generate a new, corresponding lock command based on receiving the lock command and the lock configuration data 428, which is specific to RF tag 226 (e.g., the type of RF tag 226). For example, as in Fig. As shown in Figure 5, the command from block 305 includes a command 500 containing a generic or universal permanent lock command "RL-P". For example, the parameter "P" can indicate that command 500 is intended to permanently lock the RF tag 226. However, command 500 does not identify any specific memory banks of the RF tag 226 to be locked by the command. Thus, it is not necessary for the operator of device 100 to specify or have knowledge of the individual memory banks of the RF tag to be permanently locked.

[0034] Device 100 is configured to generate a new persistent lock command 504 at block 340 in response to the generic or universal persistent lock command by inserting the aforementioned parameter set from the lock configuration data 428a. Device 100 can then execute persistent lock command 504 with respect to RF tag 226. Thus, Device 100 can generate a specific persistent lock command that includes the parameters for locking the memory banks for a particular RF tag. The generated specific new persistent lock command, which is generated in response to the general or universal persistent lock command, is based on the device identifying the media installed in the device and the type or model of RF tags contained in the media.

[0035] If the instruction from block 305 is a continuous locking instruction, and if executing the instruction at block 340 therefore includes initiating a locking operation, the device 100 can then evaluate whether the locking operation was successful, as shown in Fig. Figure 6 shows a continuation of procedure 300. At block 605, the device 100 determines whether the locking operation initiated at block 340 failed, for example, based on feedback signals from the RF tag 226 in response to the locking operation. If the determination at block 605 is negative, then the execution of procedure 300 can be terminated, and the device 100 can return to block 305 to wait for another instruction (e.g., for the next RF tag 226).

[0036] If the determination at block 605 is affirmative, then device 100 can proceed to block 610. At block 610, device 100 is configured to determine whether the source of the parameters stored in the current lock configuration data 428 is repository 238. If the determination at block 610 is affirmative, then device 100 may be configured at block 615 to generate an error message, for example, via communication interface 240, a local output device (e.g., an indicator light), or the like. An affirmative determination at block 610 means that the lock operation failed even though the parameters used in the lock operation are present in repository 238, which may indicate physical damage to the RF tag 226 or a problem other than incorrect lock parameters.

[0037] If the determination at block 610 is negative, for example, if the source of the current lock configuration data 428 is the aforementioned first or second parameter set used in blocks 330 and 335, then device 100 is configured to proceed to block 620. At block 620, device 100 is configured to set the current lock configuration data 428 to a third parameter set. For example, the third parameter set can include a parameter that identifies TID bank 408. Although many or all RF tags 226 can have a TID bank 408, some RF tags 226 may not support a lock parameter that explicitly identifies TID bank 408. Therefore, if the first or second parameter set of block 330 or 335 fails, the reason for the failure may be that the RF tag 226 is of a type that supports the explicit identification of the TID bank 408.The third parameter set might, for example, include the parameters "k, a, e, u, t". In other examples, the third parameter set might depend on whether the first or second set was used at block 330 or block 335. For instance, the "source" attribute of the current lock configuration data might specify 428, which is selected from the first and second sets. Thus, after executing block 335, the third set might append the parameter "t", resulting in the parameters "k, a, e, u, t". However, after executing block 330 and appending the parameter "t" at block 620, the third parameter set might be "k, a, e, t".

[0038] Furthermore, device 100 is configured to repeat the locking operation at block 620, with the third parameter set as described above. Device 100 is configured to determine at block 625 whether the repeated locking operation was successful. If the determination at block 625 is negative, device 100 can return to block 305 to wait for another instruction. If the determination at block 625 is positive, device 100 can delete the locking configuration data 428 at block 630 and generate an error message at block 615. Reaching block 630 means that RF tag 226 is not represented in repository 238 and that attempts to derive locking parameters for RF tag 226 failed.

[0039] In some examples, such as in response to the detection of successful permanent locking at block 605 or at block 625, the device 100 can generate a message (e.g. to the host computer device via interface 240) recommending to an operator of the device 100 that they obtain an updated repository 238 and / or update the repository 238 with the locking parameters that successfully locked the RF tag 226.

[0040] Specific embodiments were described in the preceding description. However, those skilled in the art will recognize that various modifications and alterations can be made without deviating from the scope of protection of the invention as set forth in the following claims. Accordingly, the description and the figures are to be understood in an illustrative rather than a limiting sense, and all such modifications are to be considered as included within the scope of protection of the present teachings.

[0041] The benefits, advantages, problem solutions, and any element(s) that may cause a benefit, advantage, or solution to arise or become more apparent are not to be understood as decisive, necessary, or essential features or elements of any claim or all claims. The invention is defined exclusively by the attached claims, including any amendments made during the pendency of this application, and all equivalents of these claims as published.

[0042] Furthermore, in this document, relational terms such as first and second, above and below, and the like may only be used to distinguish one entity or action from another, without necessarily implying or implying any actual relationship or order of such a relationship or order between those entities or actions. The terms "includes," "comprising," "exhibiting," "incorporating," "including," "containing," or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, procedure, article, or apparatus comprising, exhibiting, including, or containing a list of elements may not only include those elements but may also include other elements not expressly listed or inherent in such process, procedure, article, or apparatus.An element preceded by the phrases "comprises a," "has a," "includes a," or "contains a" does not, without further limitations, preclude the presence of other identical elements in the process, method, article, or device that includes, has, incorporates, or contains the element. The terms "a," "an," and "a" are defined as one or more unless expressly stated otherwise in this document.The terms “essentially”, “essentially”, “approximately”, “about”, or any other version thereof are defined to be as close as possible to what an average person skilled in the art would understand. For one non-restrictive embodiment, the term is defined as being within 10%, for another embodiment within 5%, for another embodiment within 1%, and for yet another embodiment within 0.5%. The term “coupled”, as used in this document, is defined as connected, though not necessarily directly and not necessarily mechanically. A device or structure that is “configured” in a certain way is configured at least in that way, but may also be configured in other ways not specified.

[0043] This document may use certain expressions to list combinations of elements. Examples of such expressions include: "at least one of A, B, and C"; "one or more of A, B, and C"; "at least one of A, B, or C"; "one or more of A, B, or C". Unless explicitly stated otherwise, the above expressions include any combination of A and / or B and / or C.

[0044] It will be apparent that some embodiments may include one or more specialized processors (or “processing devices”) such as microprocessors, digital signal processors, custom processors and field-programmable gate arrays (FPGAs) and unique stored program instructions (comprising both software and firmware) that control the one or more processors in order to implement, in conjunction with certain non-processor circuitry, some, most or all of the functions of the method and / or device described in this document.Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application-specific integrated circuits (ASICs) where each function, or some combinations of certain functions, are implemented as custom logic. Of course, a combination of the two approaches could also be used.

[0045] Furthermore, an embodiment can be implemented as a computer-readable storage medium on which computer-readable code is stored to program a computer (e.g., one comprising a processor) to perform a method described and claimed in this document. Examples of such computer-readable storage media include, but are not limited to: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (read-only memory), a PROM (programmable read-only memory), an EPROM (erasable programmable read-only memory), an EEPROM (electrically erasable programmable read-only memory), and flash memory.Furthermore, it is assumed that average professionals, regardless of potentially considerable effort and many design decisions based on factors such as available time, current technology, and economic considerations, will be able to create such software instructions, programs, and ICs with minimal experimentation, based on the concepts and principles disclosed in this document.

[0046] The summary of the disclosure is provided to enable the reader to quickly gain an understanding of the nature of the technical disclosure. It is presented with the understanding that it is not to be used to interpret or limit the scope of protection or the meaning of the claims. Furthermore, it is evident from the preceding detailed description that, for the sake of simplifying the disclosure, various features have been grouped together in the case of several embodiments. This type of disclosure is not to be understood as indicating an intention that the claimed embodiments require more features than are expressly listed in the respective claim. Rather, as the following claims demonstrate, the subject matter of the invention may consist of fewer than all the features of a single disclosed embodiment.Therefore, the following claims are hereby included in the detailed description, each claim representing a separately claimed subject matter. QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] US 63 / 703,024

[0001]

Claims

[1] Method in a media processing device, the method comprising: Procurement of a parameter set corresponding to a radio frequency tag (RF tag) associated with a media inventory; Receiving an initial command to lock the radio frequency tag (RF tag); Generating a second command in response to receiving the first command, the second command replacing the first command and including the parameter set; and Initiate a process to lock the RF tag based on the second command. [2] Method according to claim 1, wherein the first instruction is generic for several types of RF tag. [3] Method according to claim 1, wherein the parameters in the parameter set correspond to the respective memory banks of the RF tag. [4] Method according to claim 1, wherein the configuration of the parameter set comprises: Storing a repository with parameter sets corresponding to the respective types of RF tag on the media processing device; Determining the type of RF tag; and Procurement of the parameter set based on the specified type. [5] Method according to claim 4, wherein determining the type of RF tag comprises reading an identifier from the RF tag. [6] Method according to claim 4, wherein providing the parameter set based on the specified type comprises retrieving the parameter set from the repository. [7] Method according to claim 4, wherein providing the parameter set based on the specified type comprises: Determine that the repository does not contain a parameter set that matches the specified type; and Selecting a predefined set of parameters. [8] Method according to claim 7, wherein selecting the predefined parameter set comprises: Reading an auxiliary memory bank of the RF tag; and If the read is successful, select an initial parameter set that includes an auxiliary bank lock parameter; and If the read fails, select a second parameter set in which the auxiliary bank lock parameter has been omitted. [9] The method of claim 8, further comprising: If the blocking process fails, select a third parameter set that includes a tag identifier bank blocking parameter (TID bank blocking parameter); and Repeat the locking process. [10] Device comprising: a case; a printhead located in the housing, the printhead being configured to print a media supply; a radio frequency transcoder (RF transcoder) located in the housing; and a controller who is trained to: to obtain a parameter set corresponding to a radio frequency tag (RF tag) associated with a media repository; to receive an initial command to lock the radio frequency tag (RF tag); to generate a second command in response to the first command, where the second command replaces the first command and includes the parameter set; and to initiate a process to lock the RF tag based on the second command. [11] Device according to claim 10, wherein the first command is generic for several types of RF tag. [12] Device according to claim 10, wherein the parameters in the parameter set correspond to the respective memory banks of the RF tag. [13] Device according to claim 10, wherein the controller is configured to obtain the parameter set by: Storing a repository with parameter sets corresponding to the respective types of RF tag on the media processing device; Determining the type of RF tag; and Procurement of the parameter set based on the specified type. [14] Device according to claim 13, wherein the controller is configured to determine the type of RF tag by reading an identifier from the RF tag. [15] Device according to claim 13, wherein the controller is configured to obtain the parameter set based on the specified type by retrieving the parameter set from the repository. [16] Device according to claim 13, wherein the controller is configured to obtain the parameter set based on the specified type by: Determine that the repository does not contain a parameter set that matches the specified type; and Selecting a predefined set of parameters. [17] Device according to claim 16, wherein the controller is configured to select the predefined parameter set by: Reading an auxiliary memory bank of the RF tag; and If the read is successful, select an initial parameter set that includes an auxiliary bank lock parameter; and If the read fails, select a second parameter set in which the auxiliary bank lock parameter has been omitted. [18] Device according to claim 17, wherein the controller is further configured to: If the blocking process fails, select a third parameter set that includes a tag identifier bank blocking parameter (TID bank blocking parameter); and to repeat the locking process.

Images