Printer, program, information processing method
The printer efficiently generates log information for wireless tags by parallel processing of data writing and printing, allowing identification of the printer and optimizing storage use, addressing the lack of centralized log management in existing RFID printers.
Patent Information
- Application Number
- PCT/JP2024/044180
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-01-12
- Filing Date
- 2024-12-13
- Publication Date
- 2025-07-17
AI Technical Summary
Existing RFID printers lack efficient mechanisms to generate log information regarding data written to wireless tags, including when, where, and to which inlay the data was written, and to centrally manage this information.
A printer that issues a printing medium with a wireless tag, equipped with a communication unit for writing data, a printing unit for print information, and a control unit that executes parallel processes for data writing and generating log information, including a writing result, associated with tag identification information.
Efficient generation of log information regarding data written to wireless tags, enabling identification of the printer and specifying the printing medium based on log information, and ensuring effective utilization of storage space by deleting log data upon successful transmission.
Smart Images

Figure JP2024044180_17072025_PF_FP_ABST
Abstract
Description
Printer, program, and information processing method
[0001] The present invention relates to a printer.
[0002] Conventionally, there is known an RFID printer that prints on a label (RFID label) incorporating an RFID (Radio Frequency Identification) inlay (hereinafter simply referred to as an "inlay" or "tag") having an IC chip and an antenna. When printing on a label, the RFID printer writes (encodes) data into the inlay incorporated in the label using an RFID unit such as a reader / writer mounted on the printer (see JP 2020-157521 A).
[0003] There is a demand for RFID printers to transmit log information, including when, where, and to which inlay what data was actually written, to a server, and for the server to centrally manage the log information.
[0004] Therefore, an object of the present invention is to efficiently generate log information relating to data written to a wireless tag.
[0005] One aspect of the present invention is a printer that issues print media having a wireless tag, comprising: a first communication unit that communicates to write data to the wireless tag; a print unit that prints print information on the print media; and a control unit that executes a first process that controls the print unit to print the print information on the print media after the first communication unit writes data to the wireless tag; and a second process that generates log information including a write result indicating whether the writing of data to the wireless tag was successful, in association with tag identification information that identifies the wireless tag, wherein the control unit executes at least a portion of the first process and the second process in parallel.
[0006] According to one aspect of the present invention, log information regarding data written to a wireless tag can be efficiently generated in association with tag identification information that identifies the wireless tag.
[0007] FIG. 1 is a diagram showing a schematic configuration of a printer according to an embodiment; FIG. 2 is a block diagram of a label log system according to an embodiment; FIG. 3 is a diagram showing an example of the data configuration of an issuance instruction database; FIG. 4 is a flowchart showing issuance processing of a printer according to an embodiment; FIG. 5 is a diagram explaining the configuration of log data before and after a change; FIG. 6 is a sequence chart showing processing of a label log system according to an embodiment; and FIG. 7 is a diagram showing an example of the data configuration of a log database.
[0008] The embodiments described below are not limited to the drawings described by the brief description of the drawings.
[0009] A first aspect of the present invention is a printer that issues printing media having a wireless tag, comprising: a first communication unit that communicates to write data to the wireless tag; a printing unit that prints printing information on the printing medium; and a control unit that executes a first process that controls the printing unit to print the printing information on the printing medium after the first communication unit writes data to the wireless tag; and a second process that generates log information including a writing result indicating whether the writing of data to the wireless tag was successful, in association with tag identification information that identifies the wireless tag, wherein the control unit executes at least a portion of the first process and the second process in parallel.
[0010] According to a first aspect of the present invention, log information relating to data written to a wireless tag can be efficiently generated in association with tag identification information for identifying the wireless tag.
[0011] A second aspect of the present invention is a printer according to the first aspect, in which the data written to the wireless tag includes print identification information that identifies the print information, and the log information includes the print identification information, the writing result, and printer identification information that identifies the printer.
[0012] According to a second aspect of the present invention, the printer that issued the print medium can be identified based on the log information.
[0013] A third aspect of the present invention is the printer according to the first or second aspect, wherein the second process is started before the first process is completed.
[0014] According to the third aspect of the present invention, log information can be generated efficiently.
[0015] A fourth aspect of the present invention is the printer according to any one of the first to third aspects, wherein the second process is completed before the first process is completed.
[0016] According to a fourth aspect of the present invention, log information can be generated efficiently.
[0017] A fifth aspect of the present invention is a printer described in any one of the first to fourth aspects, which includes a memory unit that stores log information generated by the control unit and a second communication unit that transmits the log information to an external information processing device, and the control unit deletes the log information from the memory unit when the transmission of the log information to the information processing device is successful.
[0018] According to a fifth aspect of the present invention, the storage area of the storage unit can be effectively utilized.
[0019] A sixth aspect of the present invention is a printer according to any one of the first to fifth aspects, wherein the printer identification information includes at least one of the name of the printer, location information of the printer, a MAC (Media Access Control address) address of the printer, and a serial number of the printer.
[0020] According to a sixth aspect of the present invention, the printer that issued the print medium can be more specifically identified based on the log information.
[0021] A seventh aspect of the present invention is a program installed in a printer that issues printing media having a wireless tag, the program causing a computer to execute the steps of: executing a first process that controls the printer to print printing information on the printing media after writing data to the wireless tag by the printer; and executing a second process that generates log information including a write result indicating whether the writing of data to the wireless tag was successful, in association with tag identification information that identifies the wireless tag; and the program causing the computer to execute at least a portion of the first process and the second process in parallel.
[0022] According to a seventh aspect of the present invention, log information regarding data written to a wireless tag can be efficiently generated in association with tag identification information for identifying the wireless tag.
[0023] An eighth aspect of the present invention is an information processing method by a printer that issues a print medium having a wireless tag, comprising: a step of executing a first process that controls the printing of print information on the print medium after writing data to the wireless tag; and a step of executing a second process that generates log information including a write result indicating whether the writing of data to the wireless tag was successful, in association with tag identification information that identifies the wireless tag, wherein at least a portion of the first process and the second process are executed in parallel.
[0024] According to an eighth aspect of the present invention, log information regarding data written to a wireless tag can be efficiently generated in association with tag identification information for identifying the wireless tag.
[0025] The printer of the present invention is an RFID printer that issues labels (an example of a print medium) incorporating inlays (an example of a wireless tag). The printer can communicate with a management server (described later) and issues labels based on an issuance instruction received from the management server.
[0026] First, the configuration of the printer will be described with reference to Fig. 1, which is a schematic side view of the printer with the interior visible. Referring to Fig. 1, the printer 2 includes a control unit 10, an RFID unit 16, a label position detection sensor 17, a platen roller 20, a print head 21, a paper supply unit 36, a ribbon supply unit 37, and a ribbon take-up unit 38. In Fig. 2, the exchange of signals between the control unit 10 and each unit is indicated by dashed lines.
[0027] The paper supply unit 36 is loaded with roll paper R. As shown in FIG. 1 , the roll paper R is a roll of continuous paper CP. The continuous paper CP includes a strip-shaped backing paper PM and a plurality of labels PL removably attached to the backing paper PM at intervals. The surface (front side) of the backing paper PM that contacts the adhesive surface of the labels PL is coated with a release agent such as silicone, allowing the labels PL to be easily removed. The labels PL incorporate RFID inlays IL (hereinafter simply referred to as "inlays IL"). Position detection marks IM indicating the position of the labels may be formed at predetermined intervals along the longitudinal direction on the surface (back side) of the backing paper PM where the labels PL are not attached.
[0028] The labels PL may be made of either thermal paper or plain paper. In the case of thermal paper, a thermosensitive coloring layer is formed on the surface of the label, which changes color to a specific color (black, red, etc.) when it reaches a predetermined temperature. Although not shown, the paper supply unit 36 can also be loaded with roll paper, which is a roll of linerless labels with an adhesive surface coated on the reverse side of the printing surface.
[0029] 1, in the printer 2, the continuous paper CP is pulled out from the roll paper R as the platen roller 20 rotates, and after printing on each label PL on the continuous paper CP, the labels PL are sequentially ejected from the issuing port 25. A damper 43 is provided on the transport path of the continuous paper CP. The damper 43 has a predetermined pivot shaft and is installed in a state where it can freely pivot around the predetermined pivot shaft so that tension can be applied to the continuous paper CP.
[0030] The platen roller 20 is connected to the motor 19 and is installed so that it can rotate in both forward and reverse directions in response to the operation of the motor 19. Based on a control signal sent to the motor 19 from the control unit 10, the platen roller 20 rotates together with the print head 21 while sandwiching the continuous paper CP during printing. If the continuous paper CP is plain paper, the platen roller 20 rotates together with the print head 21 while sandwiching the continuous paper CP and an ink ribbon RB coated with printing ink during printing. In this case, the ink ribbon RB is transported from a ribbon supply unit 37 and taken up by a ribbon take-up unit 38. The ribbon take-up unit 38 is driven to rotate by the motor 19.
[0031] The print head 21 includes a plurality of heating resistors (heating elements) that generate heat when energized, and prints on the labels PL of the continuous paper CP based on control signals from the control unit 10. The plurality of heating resistors are arranged in a line along the width direction of the continuous paper CP (a direction perpendicular to the transport direction of the continuous paper CP).
[0032] A label position detection sensor 17 is installed along the transport path of the continuous paper CP to detect the edge of each label PL in the transport direction of the continuous paper CP. The detection result (output signal) of the label position detection sensor 17 is sent to the control unit 10 and used to control the transport of the continuous paper CP. In one embodiment, the label position detection sensor 17 is a light transmission sensor having a light-emitting element disposed above or below the transport path of the continuous paper CP and a light-receiving element disposed above or below the other of the transport path. The label position detection sensor 17 is disposed upstream of the print head 21 and is capable of detecting the label PL. When the light-receiving element receives light emitted from the light-emitting element, the label position detection sensor 17 detects the edge of each label PL in the transport direction of the continuous paper CP based on the difference in received light intensity between light that has passed through the label PL and the liner PM and light that has passed only through the liner PM. In one embodiment, label position detection sensor 17 is a light reflective sensor having a light emitting element and a light receiving element, and detects the presence or absence of position detection marks IM on the back surface of the continuous paper CP. In this case, when light emitted from the light emitting element is reflected by the back surface of the continuous paper CP and the reflected light is received by the light receiving element, label position detection sensor 17 detects the end of each label PL in the transport direction of the continuous paper CP based on the difference in received light intensity between the light reflected by the position detection marks IM on the back surface of the continuous paper CP and the light reflected by parts of the back surface of the continuous paper CP other than the position detection marks IM.
[0033] An RFID unit 16 is installed on the transport path of the continuous paper CP. The RFID unit 16 (an example of a first communication unit) reads data from the inlay IL of each label PL on the transported continuous paper CP, or writes data to the inlay IL of each label PL, based on a control signal from the control unit 10. An RFID antenna is fixed to the print head 21 and is electrically connected to the RFID unit 16.
[0034] Next, a label log system including a printer and a management server will be described with reference to FIG. 2. FIG. 2 is a block diagram showing the configuration of the label log system 1. As shown in FIG. 2, the label log system 1 includes a printer 2 and a management server 5. In the label log system 1, the printer 2 and the management server 5 can communicate with each other via a network NW. The network NW is not limited to, but may be, for example, a wireless or wired local area network (LAN), a wide area network (WAN), a mobile communication network, or the Internet. A terminal device 3 is not essential to the label log system 1, but can communicate with the management server 5. The terminal device 3 remotely instructs the management server 5 to send an issuance instruction to the printer 2. For example, an administrator can input information into the terminal device 3, which causes the management server 5 to send a label issuance instruction to the printer 2.
[0035] As shown in FIG. 2 , the control unit 10 of the printer 2 includes a control unit 11, a storage 12, a motor control circuit 13, a head control circuit 14, a real-time clock (RTC) 15, a communication unit 18, an RFID interface (I / F) 26, and a sensor interface (I / F) 27. The control unit 11 includes a central processing unit (CPU), a read-only memory (ROM), and a random access memory (RAM) and controls various operations of the printer 2. The ROM, which is a non-volatile memory, stores firmware and an RFID log application. The firmware and RFID log application are executed, for example, upon startup of the printer 2. The RAM temporarily stores data when each program is executed. The control unit 11 generates log data that includes a write result indicating whether the RFID unit 16 successfully wrote data to the inlay IL and EPC (Electronic Product Code) data included in the data written to the inlay IL, and associates the log data with a TID (an example of tag identification information) that identifies the inlay IL. The EPC data is an international standard identification code established by GS1, and is a code that identifies, for example, the item to which the label is affixed. In this embodiment, the EPC data can be used as print identification information that identifies, for example, print data printed on a label to be affixed to each individual item.
[0036] The RFID log application is a program that works with the firmware when printing each label PL to generate log data (an example of log information) for each label PL. The log data includes a TID for identifying the inlay IL of the label PL, EPC data (an example of written data) written to the EPC area of the inlay IL, and a write result indicating whether the writing was successful. The RFID log application may also include information such as the printer name (e.g., model) of the printer 2 and the installation location of the printer 2 (e.g., a specific factory or floor where the printer 2 is installed).
[0037] The storage 12 stores a log data set. The log data set includes log data generated corresponding to one or more labels PL. As will be described later, the log data corresponding to each label PL is sent to the management server 5 for centralized management by the management server 5. For example, the log data can be temporarily recorded in RAM (an example of a storage unit) of the control unit 11 until a confirmation message is received by the management server 5. If the printer 2 is turned off without receiving a confirmation message, the log data recorded in the RAM can be sent to the storage 12 and saved as a log data set for retransmission the next time the printer is turned on.
[0038] The motor control circuit 13 includes a drive circuit that drives the motor 19 based on a control signal sent from the firmware. The control signal includes, for example, information regarding the transport distance of the continuous paper CP. The head control circuit 14 (an example of a printing unit) includes an image buffer and, based on a control signal (e.g., a strobe signal) sent from the firmware, controls the flow of current selectively to multiple heating elements included in the print head 21 according to print data, thereby printing information on the label. The real-time clock 15 is a circuit that generates digital time data and sequentially supplies it to the control unit 11. The communication unit 18 (an example of a second communication unit) is a communication interface that communicates with the management server 5. The communication protocol between the communication unit 18 and the management server 5 is not important. The communication unit 18 receives issuance instructions from the management server 5 and transmits log data to the management server 5 under the control of the control unit 11.
[0039] The RFID interface 26 is an interface between the control unit 10 and the RFID unit 16, and transmits control signals for reading and writing from the firmware to the RFID unit 16. Based on the control signal, the RFID interface 26 receives the TID read from the inlay IL from the RFID unit 16, and transmits data to be written to the EPC area of the inlay IL (referred to as "EPC data") to the RFID unit 16. The sensor interface 27 receives the output signal of the label position detection sensor 17, converts it into a digital value, and transmits it to the control unit 11. The firmware of the control unit 11 controls the transport of the continuous paper CP based on the output signal of the label position detection sensor 17.
[0040] 2, the management server 5 includes a control unit 51, a storage 52, and a communication unit 53. The control unit 51 has a CPU, a ROM, and a RAM. For example, the control unit 51 executes a server program stored in the ROM to control various operations of the management server 5. The storage 52 (an example of a memory unit) stores an issuance instruction database (issuance instruction DB) and a log database (log DB). The issuance instruction database and the log database are accessed as appropriate by the server program.
[0041] The communication unit 53 is a communication interface for communicating with both the printer 2 and the terminal device 3. The control unit 51 (an example of an issuance instruction unit) sends label issuance instructions to the printer 2 via the communication unit 53. The issuance instructions include print data to be printed on each label and data to be written in the EPC area of the inlay IL of each label (EPC data). As will be described later, the control unit 51 associates, from the multiple print data in the issuance instruction database, print data that corresponds to EPC data included in the log data received from the printer 2 with the log data received from the printer 2.
[0042] FIG. 3 shows an example of the data configuration of the issuance instruction database stored in the storage 52 of the management server 5. Each record in the issuance instruction database shown in FIG. 3 contains values for the fields "user ID," "user name," "EPC data," and "print data." Each record corresponds to one label. The user ID is identification information that identifies the user. Here, a "user" refers to an issuer, such as an individual or company, that issues the labels. The issuance instruction database manages labels to be issued for each issuer that issues the labels. The user name is a name that identifies the user who issues the labels. In the example of FIG. 3, the user name is indicated by a URL. "EPC data" is data to be written in the EPC area of the inlay of the corresponding label, and is an example of print identification information that identifies the print data. "Print data" is data to be printed on the corresponding label (an example of print information).
[0043] Next, referring to Fig. 4, the issuance process executed when the printer 2 receives an issuance instruction from the management server 5 will be described. Fig. 4 is a flowchart showing the issuance process executed by the control unit 11 of the printer 2. The control unit 11 executes the issuance process in cooperation with the firmware and the RFID log application. Fig. 4 is written so that the processes executed by the firmware and the RFID log application can be clearly identified.
[0044] 4, when the printer 2 receives an issuance instruction from the management server 5, the firmware in the control unit 11 acquires the issuance instruction (step S2). The issuance instruction includes print data to be printed on the label and EPC data to be written in the label inlay. The firmware feeds the continuous paper until the inlay of the label to be printed reaches a predetermined position appropriate for communication with the RFID unit 16, and reads the TID from the inlay (step S4). The firmware then writes the EPC data included in the issuance instruction to the EPC area of the inlay (step S6) and performs verification processing (step S8). Note that in step S6, the EPC area may be locked and protected after the data has been written.
[0045] In the verification process in step S8, data is read from the EPC area of the inlay and verified to see if the read data matches the EPC data included in the issuance instruction. If the data matches, the firmware determines the write result as "success." If the data does not match, the firmware determines the write result as "fail." Next, the firmware generates log data (step S10). The log data generated in step S10 includes the TID read in step S4, the data read from the EPC area of the inlay in the verification process in step S8 (an example of read information), and a value indicating the write result in the verification process in step S8 (a value corresponding to "success" or "failure"). If the writing in step S6 was successful, the data read from the EPC area of the inlay in the verification process matches the EPC data included in the issuance instruction. The log data generated in step S10 is passed to the RFID log application.
[0046] Next, the firmware executes a printing process (an example of a first process) (step S12). In the printing process, image data is created based on the print data included in the issuance instruction, and based on the image data, printing is performed on the label to be printed while the continuous paper is being fed. In parallel with the firmware executing the printing process, the RFID log application modifies the log data passed from the firmware (step S14) and executes a process of recording the modified log data in memory (i.e., RAM in the control unit 11) (an example of a second process) (step S16).
[0047] An example of the log data change in step S14 is shown in FIG. 5. FIG. 5 shows an example of the data structure of the log data (log data before change) generated by the firmware in step S10 of FIG. 4 and passed from the firmware to the RFID log application (log data before change), and the log data after change by the RFID log application. In the example shown in FIG. 5, the following information is displayed in relation to the log data before change: identification information ("ID") that identifies the log data added by the RFID log application; the time of writing of the EPC data ("time"); the printer name of printer 2 ("printer name"); the serial number of printer 2 ("printer S / N"); the installation location of printer 2 ("printer installation location"); the IP (Internet Protocol) address of printer 2 ("printer IP address"); and the MAC (Media Access Control) address of printer 2 ("printer MAC address"). While not all of this information is required, the information (additional information) added to the log data adds information about when and / or which printer wrote the data, in addition to information about which inlay (TID) was written to which data.
[0048] The printer name, serial number, IP address, and MAC address of printer 2 are examples of printer identification information that identifies printer 2. By adding the printer identification information to the log data, it becomes possible to identify the printer that issued the label based on the log data. In other words, it becomes possible to identify which inlay (TID) the EPC data was written to and where based on the log data.
[0049] The additional information shown in Figure 5 is merely an example. For example, it is sufficient if the log data contains at least one of the following information: the serial number, installation location, IP address, and MAC address of the printer 2. By including at least one of the following information in the log data: the serial number, installation location, IP address, and MAC address of the printer 2, it is possible to specifically identify the printer that printed the label based on the log data. In other words, the updated log data is data that includes at least one of the following information for each TID: the serial number, installation location, IP address, and MAC address of the printer 2 compared to the log data before the update.
[0050] Referring again to FIG. 4 , in one embodiment, the RFID log application of the control unit 11 executes at least a portion of the log data modification and recording process of steps S14 and S16 in parallel with the printing process of step S12 by the firmware of the control unit 11. In one embodiment, the RFID log application starts adding or modifying the log data to include the additional information before the firmware completes the label printing process, and records the modified log information in RAM. Preferably, the RFID log application completes the log data modification and recording process of steps S14 and S16 before the firmware completes the label printing process. Label issuance throughput is not reduced when the RFID log application completes the log data modification and recording process of steps S14 and S16 before the firmware completes the label printing process. Even if the RFID log application does not complete the log data modification and recording process of steps S14 and S16 before the firmware completes the label printing process, the log data can be generated efficiently by executing the process in parallel with the printing process.
[0051] By executing steps S2 to S16 in the issuance process, one label is issued and log data is generated and recorded. The RFID log application may send log data to the management server 5 each time it generates the updated log data shown in FIG. 5 described above, or it may send log data to the management server 5 each time it accumulates log data corresponding to a predetermined number of labels (e.g., 10 to 50 labels). The printer 2 temporarily stores issuance instructions sequentially received from the management server 5 in the RAM of the control unit 11. The firmware sequentially retrieves and processes the issuance instructions stored in the RAM.
[0052] Once log data corresponding to a predetermined number of labels has been accumulated, the RFID log application transmits the updated log data shown in FIG. 5 to the management server 5 (step S18). If the management server 5 has received the log data (i.e., if the log data has been successfully transmitted), it transmits a confirmation message ACK to the printer 2. Therefore, if the RFID log application receives a confirmation message ACK from the management server 5 in response to the transmission of the log data in step S18 (step S20), it deletes the log data from the RAM of the control unit 11 (step S22). By deleting the log data if the transmission of the log data has been successful, the storage area of the memory in the printer 2 can be used more effectively.
[0053] The RFID log application does not delete the log data if it does not receive an ACK confirmation message, but may resend the log data to the management server 5 if it does not receive an ACK confirmation message within a predetermined time after sending the log data. An example of a case in which an ACK confirmation message is not sent from the management server 5 is when the management server 5 stops functioning due to a failure. In that case, the ACK confirmation message is sent after the management server 5 is restored.
[0054] Next, the processing between the printer 2 and the management server 5 will be described with reference to FIG. 6. FIG. 6 is a sequence chart showing the processing of the label log system 1. The management server 5 sends an issuance instruction to the printer 2 (step S30), and the printer 2, having received the issuance instruction, executes the issuance process shown in FIG. 4 (step S32). Step S30 is performed consecutively for each label to be printed. The printer 2 executes the issuance process based on the received issuance instruction and sends log data corresponding to a predetermined number of labels (the changed log data shown in FIG. 5) to the management server 5 (step S34). If the management server 5 has successfully received the log data from the printer 2, it sends a confirmation message ACK to the printer 2 (step S36). If the printer 2 receives the confirmation message ACK from the management server 5, it deletes the log data sent in step S34.
[0055] Next, the management server 5 executes steps S38 to S44. This process is executed by, for example, a server program in the control unit 51. The control unit 51 performs EPC matching (step S38) using the log data (the changed log data shown in FIG. 5) acquired from the printer 2 in step S34. In this EPC matching process, the control unit 51 determines whether the EPC data included in the changed log data corresponding to each label shown in FIG. 5 matches the EPC data included in a record in the issuance instruction database (FIG. 3) that served as the basis for the issuance instruction used in step S30. If the EPC data included in the log data matches the EPC data included in any record in the issuance instruction database (step S40: YES), the control unit 51 then determines whether a record with the same EPC data already exists in the log database (step S41). Here, the existence of a record with the same EPC data already exists in the log database in step S41 means that two or more labels with the same EPC data written in the inlay have been issued by the printer 2. Printing two or more labels with the same EPC data written in the inlay can occur, for example, when the printer cover is opened while printing a label on the printer 2. If a record of the same EPC data already exists in the log database (step S41: YES), the control unit 51 sends a warning message to an administrator terminal such as the terminal device 3 (step S44). By sending the warning message, the administrator can be made aware that two or more labels with the same EPC data have been printed.
[0056] If the control unit 51 does not find a record with the same EPC data in the log database (step S41: NO), it adds a record corresponding to the log data to be processed to the log database (step S42). The log database is, for example, an issuance instruction database (FIG. 3) to which the changed log data acquired from the printer 2 has been added. This record is added by searching the issuance instruction database for a record containing the EPC data in the log data received from the printer 2, and associating the data group (user ID, user name, print data, etc.) contained in the corresponding record in the issuance instruction database with the log data received from the printer 2. In other words, from the perspective of EPC matching, the control unit 51 identifies a record in the issuance instruction database that corresponds to the log data received from the printer 2, and combines the identified record with the log data received from the printer 2 to add a record to the log database.
[0057] FIG. 7 shows an example of the data structure of the log database. Each record in the log database shown in FIG. 7 is the log data received from the printer 2 plus the user ID, user name, and print data from the issuance instruction database shown in FIG. 3 . That is, in one embodiment, the control unit 51 associates, among the multiple records in the issuance instruction database, a record containing EPC data included in the log data received from the printer 2 with the log data received from the printer 2. For example, if the EPC data included in the log data received from the printer 2 is "2345xxxxx" as shown in FIG. 5 , the control unit 51 identifies a record in the issuance instruction database ( FIG. 3 ) that contains the same EPC data. The control unit 51 creates the first record in the log database shown in FIG. 7 by associating the user ID, user name, and print data included in the identified record with the log data received from the printer 2. By associating not only the print data but also the user ID and user name, it is possible to extract records corresponding to a specific issuer from the log database.
[0058] Referring again to FIG. 6, if the EPC data included in the log data does not match the EPC data included in any record in the issuance instruction database (step S40: NO), the printer 2 has generated log data that does not match the issuance instruction. In this case, the control unit 51 notifies a warning message to an administrator terminal, such as the terminal device 3 (step S44). By notifying the warning message, the administrator can be made aware that the log data contains inappropriate EPC data. Note that, in the EPC matching process of step S38, instead of using the issuance instruction database ( FIG. 3 ), a log database ( FIG. 7 ) created by combining the above-described issuance instruction database ( FIG. 3 ) with the changed log data ( FIG. 5 ) acquired from the printer 2 may be used.
[0059] As described above, in the label log system 1, the printer 2 generates log data associated with the inlay TID so that the log data includes not only the write result indicating whether the data was successfully written to the inlay, but also information about when and / or where the data was written. The control unit 11 of the printer 2 executes a process to control the printing of print data on the label, and a process to generate log data, and executes at least part of these two processes in parallel. This allows the printer 2 to efficiently generate log data related to the data written to the label.
[0060] Furthermore, in the label log system 1, the management server 5 has an issuance instruction database referenced in label issuance instructions, and sequentially transmits print data and EPC data corresponding to each record in the issuance instruction database to the printer 2 for each label to be issued. The management server 5 sequentially receives log data corresponding to the issued labels and associates the log data received from the printer 2 with the issuance instruction database using the EPC data contained in the log data. This allows the management server 5 to centrally manage the log data and print data for each label without the printer 2 sending print data for each label to the management server 5. By associating the log data with the print data and centrally managing it on the management server 5, sufficient traceability is ensured for issued RFID labels. This allows manufacturers or distributors who distribute RFID labels affixed to goods to prove that the encoding was reliable even if the RFID label becomes unreadable, and also allows the printed information printed on the label to be revealed in a timely manner even if the goods to which the label was affixed are lost.
[0061] In the label log system 1, the management server 5 determines whether the EPC data included in the log data received from the printer 2 matches any of the EPC data included in the issuance instruction database. If the log data contains EPC data not included in the issuance instruction, this means that the printer 2 wrote inappropriate EPC data into the label inlay. Therefore, by performing this determination, it is possible to determine whether the printer 2 wrote the EPC data appropriately and ensure unique EPC data for each label. In one embodiment, when recording log data received from the printer 2 in the log database, the management server 5 determines whether the EPC data included in the log data matches EPC data included in any log data already recorded in the log database. If the EPC data included in the log data matches EPC data included in any log data already recorded in the log database, this means that two or more labels with the same EPC data written into the inlay have been printed. Issuing a warning in this case more reliably ensures unique EPC data for each label.
[0062] In the above-described embodiment, the write data written to the inlay is EPC data, but this is not limited to this. Because the inlay includes a USER area that can be freely written by the user, the write data may include data to be written to the USER area (USER data) in addition to the EPC data. Because the user can freely set the data format of the USER data, in one embodiment, the USER data is composed of multiple items of information associated with a user name or user ID. For example, if the user is a retailer, the USER data may be composed of information on items such as the product ID (e.g., JAN code), expiration date, and content volume. If the user is a pharmaceutical manufacturer, the USER data may be composed of information on items such as the product ID, expiration date, pharmaceutical classification, and ingredients. If the user is a manufacturer, the USER data may be composed of information on items such as the product ID, manufacturing date, and lot number.
[0063] The management server 5 may extract information for items corresponding to the user ID from the log data received from the printer 2 and record the information in the log database. For example, the management server 5 may record information such as the product's expiration date in each record of the log database shown in FIG. 7. This allows the data recorded in the log database to be changed for each user, even if the format of the log data sent from the printer 2 to the management server 5 is the same, allowing users to make effective use of the log database. The printer 2 may also edit the changed log data shown in FIG. 5 described above, for example, according to the user ID included in the print instruction, and send the edited log data to the management server 5. Alternatively, the printer 2 may send edited log data for each food item with an expiration date or for each item to the management server 5. This allows the management server 5 to centrally manage the log data and print data written on each label using log data edited for each user or for each user data.
[0064] In one embodiment, the program is installed in the printer 2 and causes a computer to execute the following steps at least partially in parallel. This program is executable by one or more processors: (I) a procedure for executing a first process that controls the printer 2 to print print information on a label after writing data to the inlay by the printer 2; and (II) a procedure for executing a second process that generates log data that includes a writing result indicating whether writing of data to the inlay was successful, in association with a TID. In this case, at least a portion of the first process and the second process are executed in parallel. In one embodiment, the program is stored on a non-transitory recording medium.
[0065] In one embodiment, the information processing method is performed by a printer 2 that issues print media having a wireless tag, and includes the following steps: (I) a step of executing a first process that controls the printer 2 to print print information on a label after writing data to an inlay by the printer 2, and (II) a step of executing a second process that generates log data that includes a writing result indicating whether or not writing of data to the inlay was successful, in association with a TID. In this case, at least a part of the first process and the second process are executed in parallel.
[0066] Although the printer, program, and information processing method according to the present invention have been described above, the present invention is not limited to the above-described embodiments. Furthermore, various improvements and modifications can be made to the above-described embodiments without departing from the spirit and scope of the present invention.
[0067] The above-described processing by the printer 2 and the management server 5 is merely an example. At least a portion of the processing by the printer 2 described above may be executed by the management server 5, or at least a portion of the processing by the management server 5 described above may be executed by the printer 2. At least a portion of the functions implemented by the printer 2 may be executed by the management server 5, or at least a portion of the functions implemented by the management server 5 may be executed by the printer 2. In other words, functions may be distributed as appropriate between the printer 2 and the management server 5. In the above-described embodiment, the management server 5 is configured to include an issuance instruction database and a log data set. However, this is not limited to this, and the issuance instruction database and the log data set may be stored in a database server provided separately from the management server. In this case, processing for each database is performed in cooperation between the management server and the database server.
[0068] The present invention is related to patent application No. 2024-3632, filed with the Japan Patent Office on January 12, 2024, the entire contents of which are incorporated herein by reference.
Claims
1. A printer that issues a printing medium having a wireless tag, comprising: a first communication unit that performs communication for writing data to the wireless tag; a printing unit that prints print information on the printing medium; a first process that controls the printing unit to print the print information on the printing medium after the data is written to the wireless tag by the first communication unit; and a control unit that executes a second process of generating log information including a writing result indicating whether the writing of data to the wireless tag was successful, in association with tag identification information for identifying the wireless tag, wherein the control unit executes at least a part of the first process and the second process in parallel.
2. The printer according to claim 1, wherein the data written to the wireless tag includes print identification information for identifying the print information, and the log information includes the print identification information, the writing result, and printer identification information for specifying the printer.
3. The printer according to claim 1 or 2, wherein the control unit starts the second process before the first process ends.
4. The printer according to claim 1 or 2, wherein the control unit ends the second process before the first process ends.
5. The printer according to claim 1 or 2, further comprising: a storage unit that stores the log information generated by the control unit; and a second communication unit that transmits the log information to an external information processing device, wherein the control unit deletes the log information from the storage unit when the transmission of the log information to the information processing device is successful.
6. The printer according to claim 2, wherein the printer identification information includes at least one of information on the name of the printer, the position information of the printer, the MAC (Media Access Control address) address of the printer, and the serial number of the printer.
7. A program installed in a printer that issues a printing medium having a wireless tag, the program causing a computer to execute procedures for: performing a first process of controlling to print print information on the printing medium after writing data to the wireless tag by the printer; and performing a second process of generating log information including a writing result indicating whether the writing of data to the wireless tag was successful, in association with tag identification information for identifying the wireless tag, the program causing the computer to execute at least a part of the first process and the second process in parallel.
8. An information processing method by a printer that issues a printing medium having a wireless tag, the method including steps of: performing a first process of controlling to print print information on the printing medium after writing data to the wireless tag; and performing a second process of generating log information including a writing result indicating whether the writing of data to the wireless tag was successful, in association with tag identification information for identifying the wireless tag, at least a part of the first process and the second process being performed in parallel.
Citation Information
Patent Citations
Brake caliper
JP2024003632A
Label printer
JP2003159838A
Printer for RFID (radio frequency identification) paper
JP2008126456A
Label printer, computer program for label printer, computer program and data transmitting method
JP2009083459A
Tag label creation system and operation terminal
JP2009294761A