Method for managing traceability of wood and application program used in the method

Abstract

To reliably register even information input in locations where radio waves cannot be received.SOLUTION: In a portable terminal device 3 incorporating a dedicated application 30, an input screen for inputting information on a wood is displayed in response to reading a unique identification code from an IC tag 1 attached to the wood, and the input information is combined with the identification code read immediately before the screen is displayed and stored in a memory of the own device. The stored information is transmitted to a management server 2 in an environment in which communication with the management server 2 is possible, and is set in a way that the information cannot be deleted until the transmission completes. The management server 2 stores, in a database 200, information transmitted from the portable terminal device by grouping the information that contains the same identification code, and, upon receiving a viewing request containing one of the stored identification codes, reads out the information corresponding to the requested identification code, and transmits the information to the terminal device 3 that has transmitted the viewing request.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information management technology that enables the tracing of information on lumber distributed in the market, back to the time of felling or even before felling. In particular, the present invention relates to an information management technology that attaches an information storage medium storing a unique identification code for identifying lumber to be managed, and enables the registration of new information and the reading of registered information via this information storage medium. [Background technology]

[0002] Known conventional management systems that use IC tags, which are a typical information storage medium, for managing the distribution of lumber include those described in Patent Documents 1 and 2 listed below.

[0003] Patent Document 1 describes a method in which an IC card (corresponding to an IC tag) on ​​which lumber identification information is written is fixed to the lumber, and each time processing or inspection is carried out, work is carried out based on information read from the IC card, and the details of the processing work and pass / fail results of the inspection are written on the IC card while the lumber is distributed. Patent Document 1 also describes that finally, based on the pass / fail judgment result read from the IC card, only lumber that passes the inspection is sorted and shipped, and that an external information storage device can be used in combination with the IC card.

[0004] Patent Document 2 describes how management information is written to an electronic tag (equivalent to an IC tag) attached to lumber, and how the management information is added to the electronic tag each time work is carried out thereafter, and how the same management information is also transmitted to a management device having a database for storage. Patent Document 2 further describes how the reliability of information related to traceability is ensured by embedding the electronic tag in the core of the lumber so that it cannot be removed between the time the log is cut and the time it is processed into lumber, and by making it impossible to erase information once written to the electronic tag.

[0005] In addition to these, as shown in Patent Document 3, a system is also known in which a label with a pattern code such as a barcode printed on it is affixed to lumber, and by reading the pattern code, a computer that stores traceability information can be accessed and management information can be confirmed. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-130853 [Patent Document 2] Japanese Patent Application Laid-Open No. 2007-26415 [Patent Document 3] Japanese Patent Application Laid-Open No. 2008-301783 Summary of the Invention [Problem to be solved by the invention]

[0007] In recent years, IC tags (commonly called "NFC tags") that use the NFC (Near Field Communication) communication standard have become widespread, and many general-purpose mobile terminal devices such as smartphones are now equipped with NFC communication functions, creating an environment in which information management using IC tags can be easily performed.

[0008] However, in order to provide end users with easy-to-understand information, rather than simply recording management information, it is necessary to record the free comments and image data of those involved, and it is difficult to record such information using only the memory capacity of an IC tag. Also, many general-purpose mobile terminal devices do not have the function to write information to IC tags, or can write information but cannot confirm the written information, so it is dangerous to rely on general-purpose mobile terminal devices to write important information.

[0009] In light of these circumstances, it seems appropriate to adopt a method of establishing an internet server that centrally manages traceability information, and sending and storing the information to be managed on this server. In this case, the method that usually comes to mind is to attach a label with a pattern code (two-dimensional code or barcode) that represents the identification code to the lumber, as described in Patent Document 3, and read the pattern code to access the server, allowing the information to be sent and the registered information to be confirmed.

[0010] However, to prevent information mix-ups and tampering, it is necessary to input information while checking the actual timber on-site. However, these sites are often located in the mountains, where radio waves cannot reach, making it difficult to send information from the site to the server.

[0011] To provide a method for easily registering traceability information at a site where lumber is placed using a general-purpose mobile terminal device, and to ensure that information entered in a place where radio waves cannot reach can also be reliably registered in a management server, by focusing on the above-mentioned problems. Furthermore, a second object of the present invention is to manage the traceability information of the wood after it has been divided into multiple pieces, and to ensure that the traceability information of the wood before it was divided is carried over to each piece of wood after it has been divided. [Means for solving the problem]

[0012] In order to solve the above problems, the present invention implements the following method using an information storage medium that stores a unique identification code for identifying lumber to be distributed on the market, a database that stores traceability information related to the lumber to which the information storage medium is attached, linked to the identification code, a management server that receives registration requests for registering information in the database and viewing requests for viewing information via the Internet and responds to the requests, and a mobile terminal device that has the function of reading information from the information storage medium and the long-distance wireless function for communicating with the management server, including transmitting each of the requests.

[0013] In response to reading the identification code from the information storage medium, the mobile terminal device first displays an input screen for inputting information to be registered in the database, and stores the information entered on this input screen in combination with the identification code read just before the screen is displayed in its memory, and prevents the stored information from being deleted until transmission to the management server is complete. Thereafter, in an environment where communication with the management server is possible, the mobile terminal device transmits a registration request including the unsent information stored in its memory to the management server.

[0014] The management server stores the information to be registered, acquired in response to registration requests from an unspecified number of the mobile terminal devices, in the database, each linked to an identification code included in the registration request. In addition, in response to receiving a browsing request containing one of the identification codes stored in the database from any communication terminal device (the mobile terminal device described above or another communication terminal device) via the Internet, the management server reads out the information linked to the identification code from the database and transmits the read out information to the communication terminal device that sent the browsing request.

[0015] According to the above method, by attaching an information storage medium storing a unique identification code for identifying the timber to the timber to be managed, a worker on-site can hold a mobile terminal device over the information storage medium to read the identification code, which displays an input screen on the mobile terminal device and allows the worker to immediately input the necessary information. Even if the work site is located in an area where long-distance wireless radio waves do not reach or are difficult to reach, the input information is stored in the memory of the mobile terminal device in combination with the identification code read just before. When the worker moves to a location where long-distance wireless communication is stable, the unsent information can be transmitted to the management server and stored in the database.

[0016] According to the above method, there is no need to write the information to be registered in the database to an information storage medium. Therefore, even if wood is moved to various locations and a large amount of information needs to be registered, or even if large amounts of data such as image data are to be registered, this can be easily handled by ensuring sufficient capacity in the memory device on which the management server's database is located.

[0017] In the above method, if an identification code to be used is registered in advance in the database of the management server, the management server can store the information to be registered in the registration request in the database, provided that the registration request received from the mobile terminal device includes an identification code registered in the database.

[0018] In the above method, in addition to IC tags, labels on which pattern codes such as bar codes and two-dimensional codes are printed can be used as information storage media.

[0019] According to the present invention, the traceability information of a single piece of wood is linked to an identification code stored in a single information storage medium and registered in a database. However, after a piece of wood is divided into multiple pieces by sawing or other processes, it is desirable to manage the traceability information of each piece of wood after the division, and to ensure that the traceability information before the division is carried over to each piece of wood after the division.

[0020] To enable the above management, In the present invention, an identification code is written on an information storage medium attached to the divided wooden piece, the identification code being the identification code of the information storage medium before division plus an additional code based on a predetermined rule; Mobile terminal device From the above The identification code registered in the database The above Unregistered identification code with additional code added On the management server that receives the registration request containing , the relevant registration request With additional code The identification code is registered in the database, and the information to be registered in the registration request is linked to the identification code and stored in the database. It was decided .

[0021] In the present inventionThe mobile terminal device is provided with a function for transmitting an ID issuance request including an identification code read from an information storage medium to a management server, and the management server, upon receiving the ID issuance request including an identification code registered in the database, generates an identification code configured by adding the aforementioned additional code to the identification code in the request, and transmits response information informing the mobile terminal device that transmitted the issuance request of the identification code. It is also possible .

[0022] moreover The present invention In the case where the identification code included in the browsing request from an arbitrary communication terminal device is configured to include the above additional code, the information linked to the identification code of the browsing request in the database is In addition, Information linked to the identification code consisting of the identification code excluding the additional code too These two types of information can be sent all at once, or can be sent in multiple batches.

[0023] Therefore, the present invention According to the method, when a piece of wood is split into multiple pieces at a midpoint in the distribution channel, each piece of split wood is assigned an identification code that adds a different additional code to the identification code of the information storage medium attached to the original piece of wood, and an information storage medium that stores these identification codes is attached to each piece of wood.The identification code is read from the information storage medium and a registration request is made, thereby making it possible to store information that is generated thereafter for each piece of split wood.Furthermore, when a viewing request is received that includes the identification code of one of these pieces of wood, in addition to the information stored for that identification code, information stored for the identification code obtained by removing the additional code from that identification code, i.e., information about the wood before it was split, can also be sent to the communication terminal that sent the viewing request.

[0024] In another embodiment of the present invention, the management server has a function of managing a website (EC site) for selling lumber whose traceability information is registered in the database, and accepts registration requests only from mobile terminal devices that have logged in with the authentication code of a user who has been pre-certified as a registrant of traceability information, and registers the information in the registration request in the database, linking it to information that identifies the user who logged in. Furthermore, when the management server receives a listing request for lumber related to information registered in the database, linked to information that identifies the user, from a mobile terminal device that has logged in with the authentication code, the management server creates a webpage including information corresponding to the request and uploads it to the website.

[0025] According to the above embodiment, anyone who has become authorized to sell timber during the timber distribution process can register the timber on the management server and then publish the registered information to put the timber up for sale. Furthermore, without being bound by existing distribution mechanisms, it is possible to directly link forest owners and intermediate sellers with end users and conclude contracts.

[0026] Furthermore, the present invention can provide an application program that is installed in a mobile terminal device to implement the above management method. [Effects of the Invention]

[0027] According to the present invention, an information storage medium storing a unique identification code for identifying the timber to be managed is attached to the timber, and the identification code is read from a mobile terminal device that inputs information about the timber. The information input and the read identification code are then transmitted to a management server, and the information is linked to the identification code and stored in the management server's database. This significantly increases the amount of data that can be registered as traceability information. This makes it possible to register not only information for management purposes, but also information that conveys detailed information about each timber to end users in an easy-to-understand manner.

[0028] Furthermore, by having the portable terminal device read the identification code from the information storage medium and then input the information immediately after reading, it becomes possible to easily register traceability information at the site where the timber is stored, and it is possible to prevent the registration of false information and the misregistration of registered information. Furthermore, by storing the input information in memory until transmission to the management server is complete, it is possible to reliably register information input at sites where long-distance wireless communication is difficult to establish with the management server. Furthermore, if a piece of wood is split into multiple pieces at an intermediate point in the distribution route, information generated after the splitting can be stored for each piece of wood using an information storage medium individually attached to each piece of split wood, and both information about the wood to which the information storage medium is attached and information about the wood before it was split can be transmitted to a communication terminal device that reads an identification code from the information storage medium attached to the split wood and sends a viewing request. [Brief explanation of the drawings]

[0029] [Figure 1] 1 is an explanatory diagram showing a schematic configuration of a traceability management system to which the present invention is applied; [Figure 2] FIG. 2 is a perspective view illustrating an example of the configuration of an IC tag used in the above-mentioned traceability management system. [Figure 3] FIG. 2 is a cross-sectional view illustrating the internal configuration of the IC tag. [Figure 4] FIG. 10 is a cross-sectional view showing the IC tag attached to wood. [Figure 5] FIG. 10 is a front view showing an example in which the above IC tag is attached to each of a plurality of pieces of wood. [Figure 6] This is a functional block of a management server used in the above traceability management system. [Figure 7] FIG. 2 is an explanatory diagram illustrating an example of the data configuration of a traceability database. [Figure 8] FIG. 2 is a functional block diagram of a dedicated terminal device used in the above traceability management system. [Figure 9-1] 10A to 10C are explanatory diagrams showing the transition of screens displayed when information to be included in a registration request is entered on the dedicated terminal device. [Figure 9-2] FIG. 9-1 is an explanatory diagram showing the transition of the screen following FIG. [Figure 10] 10A to 10C are explanatory diagrams showing the transition of screens displayed when a viewing request is sent to the management server on the dedicated terminal device. [Figure 11] 10 is a flowchart showing a procedure of a process executed by the management server when it receives a registration request. [Figure 12] 10 is a flowchart showing a procedure of a process executed by the management server when it receives a browse request. [Figure 13] 10 is a flowchart showing the procedure of a process executed by the management server when it receives a listing request. DETAILED DESCRIPTION OF THE INVENTION

[0030] (1) Overview of the traceability management system FIG. 1 shows a schematic configuration of a wood traceability management system S (hereinafter simply referred to as "management system S") to which the present invention is applied. This management system S includes an IC tag 1 attached to the wood to be managed, a management server 2 equipped with a traceability database 200, and a mobile terminal device 3 owned by a user (hereinafter referred to as a "member user") who is registered in the management server 2 as a person authorized to register information in this database 200.

[0031] 1 shows only one IC tag 1 and one mobile terminal device 3, but in reality, any number of these may be included in the management system S. In this embodiment, the member user's mobile terminal device 3 is a smartphone, but instead, a mobile terminal device such as a tablet device equipped with the same operating system as a smartphone can also be used. A dedicated application 30 is installed in these mobile terminal devices to enable them to function as terminal devices of the management system S.

[0032] The management server 2 can communicate with mobile terminal devices 3 that have the above-mentioned dedicated application 30 installed, as well as with general communication terminal devices 4 (personal computers 4a, smartphones 4b, tablet terminals 4c, etc.) that do not have the dedicated application 30 installed, via the management site and EC site described below.

[0033] Hereinafter, the mobile terminal device 3 in which the program of the dedicated application 30 is installed will be referred to as the "dedicated terminal device 3", and the other communication terminal devices 4 will be referred to as the "general terminal device 4". However, even the dedicated terminal device 3 can access the management server 2 via the management site without using the function of the dedicated application 30.

[0034] From the dedicated terminal device 3, a plurality of types of requests including a registration request for requesting registration of traceability information to the management server 2, a browsing request for requesting browsing of traceability information, and a listing request for requesting listing on the EC site can be transmitted via the Internet to the management server 2.

[0035] Normally, the general terminal device 4 can only browse the EC site. However, by logging in to the management server 2 based on the registration information registered as a general user in the management server 2, it becomes possible to submit a purchase application for the listed items (wood or logs before and after logging) and to browse the traceability information regarding the items before listing. Also, even a general user can install the program of the dedicated application 30 on his / her smartphone 4b or tablet terminal 4c, and by reading the information from the IC tag 1, can browse the traceability information regarding the wood to which the IC tag 1 is attached or perform the comparison of the annual ring images described later. However, in the dedicated application 30 of the general user's terminal devices 4b and 4c, the functions of the registration request and the listing request become invalid by the first login to the management server 2 for starting use.

[0036] (2) Basic Configuration and Functions of the Management System Hereinafter, the configurations and functions of the IC tag 1, the management server 2, and the dedicated terminal device 3, which are the main components of the above management system, will be described in sequence.

[0037] <Configuration of IC Tag 1> FIG. 2 shows the appearance of the front and rear sides of the IC tag 1 used in this embodiment, and FIG. This IC tag 1 has a structure in which an IC chip 12 and a circuit board 13 including an antenna coil are housed inside a hard plastic case body 11. The case body 11 is formed by molding and integrating a pair of upper and lower case halves 11a and 11b by injection molding, and has a screw hole 10 formed in the center that passes through the thickness. A through hole of a size corresponding to the screw hole 10 is also formed in the center of the internal circuit board 13, and an antenna coil is arranged along the outer periphery of the hole. The IC chip 12 incorporates a circuit and a nonvolatile memory for carrying out wireless communication based on the NFC standard.

[0038] As shown in Figures 2(A) and 3, four needle-like protrusions 14 with their tips facing forward are arranged at equal angular intervals on the inner wall surface of the screw hole 10 of the case body 11. As shown in Figure 2(B), four quadrangular pyramidal support protrusions 15 are arranged at equal angular intervals on the back surface of the case body 11. In addition, a recess 16 representing a symbol mark is formed on the front surface of the case body 11.

[0039] As shown in Figure 4, the IC tag 1 configured as described above is attached to the wood 5 to be managed by a wood screw 6 inserted into a screw hole 10. As the wood screw 6 is embedded inside the wood 5, the support protrusion 15 on the bottom surface also bites into the wood 5, increasing the support strength of the case body 10. Furthermore, since the needle-like protrusion 14 is crushed by the head of the wood screw 6 once it has been screwed in, it can be determined whether or not the IC tag 1 has been used by checking whether or not the needle-like protrusion 14 has been crushed.

[0040] A manufacturing code written by the manufacturer is stored in the memory of the IC chip 12. This manufacturing code is information unique to each IC chip 12 and is stored in a write-protected area, so it can be read but cannot be deleted or changed to a different code. Therefore, it is impossible to produce a counterfeit IC chip 12 with the same manufacturing code written in it.

[0041] In this embodiment, focusing on the above advantages, one IC tag 1 is attached to each piece of wood 5, as shown in Figure 5, and the manufacturing code read from each IC tag 1 is used as an identification code for identifying the wood 5, and is linked to the traceability information of the wood 5 to which the IC tag 1 is attached and stored in the management server 2.

[0042] Hereinafter, the identification code of this IC tag 1 will be referred to as the "tag ID." In this embodiment, a mechanism for identifying a new IC tag 1 based on the condition of the needle-like protrusions 14 is used to attach an IC tag 1 that has never been used before to lumber 5 before it enters the distribution channel, and by linking the tag ID to the traceability information of the lumber 5, the reliability of the traceability information of the lumber 5 can be increased. Even after attachment, the IC tag can be easily distinguished from other IC tags by the symbol mark represented by the recess 16 on the front. Furthermore, since it can be attached to the lumber 5 with only one wood screw 6, the process of fixing it to the lumber 5 can be simplified.

[0043] Although the IC tag 1 is often attached to logs or logs after felling, it is not limited to this. It is also possible to attach the IC tag 1 to a tree before felling in order to accumulate information from the growth stage, and to maintain this even after felling.

[0044] Logs removed from felled forests are generally transported to a log market, and once a buyer is found there, they are taken to a sawmill. Up until then, the log is often maintained as a single piece, but once at the sawmill, it is split into multiple pieces, and each piece is processed into new lumber (hereafter uncoded). A new IC tag 1 is attached to these pieces of lumber. A unique ID code is also stored in the new IC tag 1, but in this embodiment, in order to ensure that the traceability information generated up until the log was split is carried over to the split lumber, a tag ID consisting of the tag ID of the originally attached IC tag 1 plus an additional code based on a predetermined rule is written to the new IC tag 1.

[0045] Hereafter, the IC tag 1 attached to the log before splitting will be referred to as the "parent tag," the new IC tag 1 attached to the wood after splitting will be referred to as the "child tag," and the respective tag IDs will be referred to as the "parent tag ID" and "child tag ID." The child tag can have the same configuration as the parent tag (as shown in Figures 2 and 3), but depending on the size and type of wood after division, it may be changed to an IC tag such as a card or sticker type.

[0046] <Configuration and functions of management server 2> FIG. 6 is a functional block diagram showing the basic configuration of the management server 2. The management server 2 includes one or more computers, and has in its memory a traceability database 200 for collectively storing traceability information for an unspecified number of pieces of wood for each piece of wood, and a user information storage unit 210 for registering information on member users and general users. The management server 2 further has processing functions such as a management site processing unit 21, a dedicated terminal communication processing unit 22, an authentication processing unit 23, a registration information processing unit 24, a request processing unit 25, a data management unit 26, an image matching unit 27, an EC site processing unit 28, and a payment processing unit 29.

[0047] In the traceability database 200, various pieces of information transmitted in response to registration requests from the dedicated terminal device 3 are grouped together according to the type of wood, and are registered in association with tag IDs.

[0048] The user information storage unit 210 stores, for each user, information for identifying the individual, such as name, address, telephone number, and email address, as well as the user type (indicating whether the user is a member or general user), an identification code for login authentication (hereinafter referred to as "user ID"), and password. Furthermore, for member users, attribute information indicating the business name and type of business (forest owner, logger, transporter, processor, etc.) is also stored. Furthermore, for member users who are involved in the felling of logs, information identifying the accepted felling notification (such as a management number) or image data of the felling notification is stored.

[0049] The management site processing unit 21 accepts logins and specific requests from registered users via a user-dedicated portal site (hereinafter referred to as the "management site") set up on the Internet. The authentication processing unit 23 authenticates the logins using the registration information in the user information storage unit 210.

[0050] When a new user registration application is received from a general terminal device 4 that is not logged in, the registration information processing unit 24 is activated, accepts the information required for registration via an input form or the like, and registers the accepted information in the user information storage unit 210.

[0051] The dedicated terminal communication processing unit 22 is a function that communicates with the dedicated terminal device 3 without going through the management site. Even for access from the dedicated terminal device 3, the authentication processing unit 23 performs login authentication, and various requests are accepted after authentication. However, since a user ID and password are also registered in the dedicated terminal device 3, the dedicated terminal device 3 can be automatically logged in to the management server 2 based on these.

[0052] The request processing unit 25 analyzes the request received by the management site processing unit 21 or the dedicated terminal communication processing unit 22, and operates the data management unit 26 or the image matching unit 27 according to the content of the request to execute processing according to the request.

[0053] The main requests received in this embodiment are a registration request for registering traceability information, a view request for viewing information registered in the traceability database 200, and a listing request for listing on an e-commerce site lumber whose information is registered in the traceability database 200. Each request includes the tag ID of the IC tag 1 attached to the lumber that is the subject of the request and the user ID of the user who sent the request. Registration requests are accepted only by the dedicated terminal communication processing unit 22, while browsing requests and exhibition requests are accepted by both the dedicated terminal communication processing unit 22 and the management site processing unit 21.

[0054] In addition to the above, the management server 2 is sent update requests that request the addition of supplementary information to registered information, and comparison requests that request comparison of a tree-ring image obtained by actually photographing timber whose tree-ring images are registered in the traceability database 200 with the registered tree-ring image. Update requests can also be accepted by both the dedicated terminal communication processing unit 22 and the management site processing unit 21, but comparison requests are accepted only by the dedicated terminal reply processing unit 22.

[0055] The data management unit 26 executes specific information processing for requests other than the tree-ring image matching request among the various requests described above. The image matching unit 27 performs matching processing for the tree-ring image matching request.

[0056] The request processing unit 25 creates response information for the terminal device 3 or 4 that sent the request, based on the processing results of the data management unit 26 and the image matching unit 27. This response information is sent from the management site processing unit 21 or the dedicated terminal communication processing unit 22 that accepted the request to the terminal device 3 or 4 that sent the request.

[0057] The EC site processing unit 28 manages an EC site for selling lumber whose information has been registered in the traceability database 200 and for which a request to put up for sale has been accepted. This EC site lists some of the traceability information for lumber whose request to put up for sale has been accepted, but when a request to read detailed information about a specific item is received from a terminal device 3 or 4 that has accessed the site, the EC site processing unit 28 reads all of the relevant traceability information from the traceability database 200 (excluding any information that has been set to private), and transmits a web page containing that information to the terminal device 3 or 4 that issued the request.

[0058] When the EC site processing unit 28 receives an offer to purchase a specific piece of wood, the payment processing unit 29 cooperates with an external payment system to carry out processing to receive payment from the applicant.

[0059] It should be noted that the EC site can be accessed from the general terminal device 4 without logging in, but user registration is required to apply for a purchase. When user registration or login authentication becomes necessary to make a purchase, the management site processing unit 21, the registration information processing unit 24, and the authentication processing unit 23 handle these processes. In addition, when the general terminal device 4 is in a logged-in state, it is also possible to access the management site.

[0060] Therefore, a registered general user can log in to the management server 2, switch the site displayed in the browser as needed, and search the traceability database 200 to check some information about timber that is not being put up for sale. Furthermore, by installing the dedicated application 30 program on their own mobile terminal devices 4b, 4c, they can read the tag ID from the IC tag 1 of a specific piece of timber at a timber market or the like, send a viewing request to the management server 2, and view the traceability information for that specific piece of timber. Furthermore, if an image of the tree rings has been registered for that specific piece of timber, they can take a photo of the actual piece of timber in front of them, send a matching request including that image to the management server 2, and receive the matching results from the management server, thereby confirming the likelihood that the piece of timber is genuine.

[0061] 7 shows an example of the configuration of the traceability database 200 of the management server 2. The traceability database 200 in this example includes an ID management table 201 in which the tag ID of each IC tag 1 is registered, and an information storage unit 202 provided for each registered tag ID.

[0062] All tag IDs that are included in registration requests and sent to the management server 2 and accepted by the process of Fig. 11, which will be described later, are stored in the ID management table 201. The entity of the information storage unit 202 is a folder named after the corresponding tag ID, and inside this folder are stored a basic information table 204 in which basic information about the corresponding lumber is registered, and three types of subordinate folders 205, 206, and 207.

[0063] The basic information table 204 stores general traceability information such as the type of log (tree species), growing area, felling date, shipping date, and arrival date at the log market or sawmill, etc. Most of this information is entered by selecting from options displayed on the input screen of the dedicated terminal device 3, which will be described later.

[0064] Furthermore, the basic information table 204 in this embodiment stores history information regarding registration requests, history information regarding viewing requests, status information indicating the current state of the corresponding items, etc. The history information includes the date and time the request was sent, the user ID of the sender, the location where the information was entered or viewed (based on GPS information), the file name of the registered or viewed information, etc.

[0065] Subfolders 205, 206, and 207 included in information storage unit 202 are used to store information (hereinafter referred to as "posting history") that member users input from the operation screen in Fig. 9 described below and that is included in a registration request and sent to management server 2. Folder 205 stores the main part of the posting history, folder 206 stores image files of tree-ring images to be matched by image matching unit 27, and folder 207 stores image files other than tree-ring images. These folders 205, 206, and 207 are not limited to being one each, but multiple folders can be set depending on the data capacity, the date and time the data was generated, etc.

[0066] HTML files containing text data in the transmitted information (including data stored in the basic information table) are saved in the posting history folder 205. If the transmitted information includes an image file, a hyperlink to the image file is set in this HTML file.

[0067] According to the above data configuration, the HTML file of the posting record corresponding to the viewing request and the image file linked to it are read out, and these are sent to the terminal device 3, 4 that sent the viewing request, thereby allowing both the text portion and the image of the posting record to be displayed on the terminal device 3, 4.

[0068] However, the data file for the posting record is not limited to an html file, but can also be an XML file, a CSV file, or simply a text file or other file format. Even if the file format does not allow for a hyperlink to an image file, the link between the text data and the image file can be maintained by including the name of the image file or the folder name in the save destination file.

[0069] <Configuration and Functions of Dedicated Terminal Device 3> 8 is a functional block diagram showing the configuration of the dedicated terminal device 3, in which the configuration of the hardware 300 and the software (dedicated application 30) are separated by a dashed frame. Although not shown in FIG. 8, an operation system exists between the dedicated application 30 and the hardware 300. Similarly to the operation system, among the software that is standard equipment in the device before the dedicated application 30 is installed, software related to the control of the hardware 300 and a character input system (IME) also work in conjunction with the dedicated application 30.

[0070] The hardware 300 includes a camera module 301, a touch panel 302, an NFC communication circuit 303, a GPS module 304, a long-distance wireless communication circuit 305, and the like. The dedicated application 30 includes processing functions such as a photography control unit 31, a GUI control unit 32, an ID reading processing unit 33, a location information processing unit 34, a long-distance communication control unit 35, and a data management unit 36, as well as storage functions such as a user information storage unit 37, a transmission data storage unit 38, and a reference data storage unit 39.

[0071] The user information storage unit 37 stores information about the user who uses this dedicated terminal device 3 that is substantially the same as that registered in the user information storage unit 210 of the management server 2. Furthermore, the user information storage unit 37 of this embodiment stores history information about transmissions made from the dedicated terminal device 3 to the management server 2 (such as the type of request sent, the tag ID included in the request, the date and time of transmission, and the date and time a response was received from the management server 2).

[0072] The transmission data storage unit 38 stores information that is input from an input screen, which will be described later, as information to be registered in the management server 2. The information stored in this storage unit 38 is set so that it cannot be deleted until it is transmitted to the management server 2, and is retained even after transmission is complete unless the user performs a deletion operation.

[0073] Information that may be useful for the user's business (such as a list of representative tree descriptions with photographs, map information showing the distribution range of forests, and a list of locations and contact details for forestry associations, log markets, sawmills, etc.) is registered in the reference data storage unit 39. The registered information in this reference data storage unit 39 can be downloaded and updated as needed from an information provision function (not shown) of the management server 2.

[0074] Among the processing functions, the ID reading processing unit 33 cooperates with the NFC communication circuit 303 to perform a process of reading information from the IC tag 1. The GUI control unit 32 is used to set the operation screen of the dedicated application 30 on the touch panel 302, and when a code in a format that matches the tag ID is read by the above-mentioned reading process, the GUI control unit 32 displays a screen having the configuration shown in Fig. 9 or 10 on the touch panel 302 and accepts operations on that screen.

[0075] The photography control unit 31 works in cooperation with the camera module 301 to take photographs, and acquires the images generated by the photography as candidates for registration in the management server 2. In addition, for images other than tree-ring images, images generated by the camera module 301 within a certain period before and after the time of inputting the information to be registered (including images generated when the dedicated application 30 is not running) can also be set as candidates for registration.

[0076] The location information processing unit 34 acquires location information at that time from the GPS module 304 while the input screen is being operated, and adds the location information to the information input from the input screen.

[0077] The long-distance communication control unit 35 sends a request to the management server 2 via the long-distance wireless communication circuit 305 (compliant with standards such as Wi-Fi, 4G, 5G, etc.) and accepts a response to the request from the management server 2.

[0078] In conjunction with the operation of each of the above-mentioned processing units, the data management unit 36 ​​stores and reads information in each of the storage units 37, 38, and 39. When the GUI control unit 32 receives an instruction to transmit one of the above-mentioned requests, the data management unit 36 ​​reads the request from the transmission data storage unit 38, passes it to the long-distance communication control unit 35, and transmits it to the management server 2 via the long-distance wireless communication circuit 305.

[0079] (3) Main processing in the dedicated terminal device 3 Next, the flow of the process of registering and viewing traceability information, which is the main process performed by the dedicated terminal device 3, will be explained with reference to FIGS. 9 and 10, which show the transition of the screen displayed on the touch panel 302 by the GUI control unit 32.

[0080] Figure 9 (9-1) and Figure 10 (a) show the initial menu screen displayed on the touch panel 302. The top button on this menu screen, "Register tag information," is a button for selecting the process of registering traceability information for a specific piece of wood, and the second button, "View tag information," is a button for selecting the process of viewing the traceability information for a specific piece of wood. The second button from the bottom on the menu screen, "Upload," is a button for selecting the process of sending the information saved in the transmission data storage unit 38 by the "Register tag information" process to the management server 2.

[0081] <Registration process of traceability information> Figure 9 (Figures 9-1 and 9-2) shows an example of how the display screen of the touch panel 302 changes from a menu screen (Figure 9-1 (a)) to an input screen for the information to be registered, and the content of the screen changes in response to user operations.

[0082] When the "Register tag information" button on the menu screen is tapped, the ID reading processing unit 33 and the NFC communication circuit 303 are activated, making it possible to read the identification code from the IC tag 1. In response to this, the GUI control unit 32 changes the screen to one that instructs the reading process from the IC tag 1 ((b) in FIG. 9-1).

[0083] When the user follows the instructions above and holds the dedicated terminal device 3 over the target IC tag 1, and the reading of the identification code is completed, the display switches to the initial input screen as shown in Figure 9-1(c). On this input screen, the read identification code (tag ID) is displayed at the top, along with text for each of the following items: "Model," "Type," "Registration Date," "Memo," "Tree Ring Image," and "Other Images." When these text areas are tapped, the screen enters a state where information for that item can be entered.

[0084] For "Model" and "Type," options are displayed as shown in Figure 9-1 (d) and Figure 9-2 (e), and input is completed by selecting the appropriate option from the displayed options. For the registration date, a scroll menu with today's date as the default is displayed, and input is completed by selecting a date from the menu.

[0085] When "Memo" is tapped, the screen temporarily switches to a text input screen and the character input system is called up, allowing the user to freely write a comment. When the user writes a comment on this screen and exits, the screen returns to the original input screen, and the comment entered is displayed in the memo field (Figure 9-2(f)).

[0086] When "Tree Ring Image" or "Other Images" is tapped, the shooting control unit 31 and camera module 301 are activated, and the screen temporarily switches to one displaying the image being captured by the camera module 301. When the user performs a shooting operation here and confirms the generated image, the image is displayed under the item as an image to be registered (Fig. 9-2(g)). For "other images," it is possible to select from images saved from the current time up to a certain time ago. In addition, each image is not limited to one, but multiple images can be entered. However, neither tree ring images nor other images are required information. Furthermore, the function to input tree ring images is only enabled on the dedicated terminal device 3 of member users (those involved in growing or felling logs) who have been given permission to take photos in advance.

[0087] As the amount of input information increases, items at the bottom of the screen become unable to be displayed, but by scrolling appropriately, hidden items can be moved to the main part of the screen, as shown in Figure 9-2(g). Also, as more information is input, the current location information (latitude and longitude) acquired by the GPS module 304 is converted into a specific address by the location information processing unit 34, and that address is displayed at the bottom of the screen. In addition, a registration button RB is also displayed below the location information.

[0088] When the registration button RB is tapped, the processing subject is changed from the GUI control unit 32 to the data management unit 36, and a registration request including the text data in the input screen, including the tag ID and item name, and the image file displayed on the same screen is created and saved in the transmission data storage unit 38. This text data of the registration request can also be an html file including a link to the image file, but is not limited to this and may be a file in another format.

[0089] When the above-mentioned saving is completed, the screen of the touch panel 302 returns to the initial screen of Fig. 9-1(a). At this time, if the dedicated terminal device 3 is in a location where long-distance wireless communication is possible, the registration request saved in the transmission data storage unit 38 can be sent to the management server 2 by subsequently operating the "Upload" button on the menu screen.

[0090] Even when the dedicated terminal device 3 is in an environment where long-distance wireless communication is impossible or difficult, the user can leave the site and move to a location where long-distance wireless communication is possible, then operate the "upload" button to send the saved registration request to the management server 2.

[0091] In the above, it has been explained that the registration request is stored in the transmission data storage unit 38, but the stored information may not completely match the registration request that is ultimately sent to the management server 2. For example, a code indicating the request type or a user ID may be added to the information stored in the transmission data storage unit 38.

[0092] <Traceability information viewing process> 10 shows an example of the transition of the screen when a viewing request is selected by operating the "View Tag Information" button. This selection operation is valid only when the dedicated terminal device 4 is located in a place where long-distance wireless communication is possible, and in response to the operation, the screen transitions from the initial menu screen (FIG. 10(a)) to a screen (FIG. 10(b)) that instructs reading of the IC tag 1. Once the tag ID has been read, the data management unit 36 ​​creates a viewing request including the read tag ID, and transmits this request to the management server 2 from the long-distance communication control unit 35 via the long-distance wireless communication circuit 305. From this transmission until response information from the management server 2 is received, the touch panel 302 displays a standby screen as shown in FIG. 10(c).

[0093] After this, when the long-distance communication control unit 35 receives a response from the management server 2, the response is passed to the GUI control unit 32 via the data management unit 36, and the information registered in the traceability database 200 of the management server 2 for the tag ID to be viewed is displayed, as shown in Figure 10(d).

[0094] 10, for ease of explanation, the information entered in the example of FIG. 9 is transmitted to management server 2, registered as a posting record, and then displayed as a target for viewing. In this embodiment, the information displayed on the input screen for the information to be registered, including the item names, is stored in transmission data storage unit 38, and then a registration request including all of the stored information is transmitted to management server 2. Management server 2 also stores all of the information included in the registration request in traceability database 200, making it possible to display the posting record corresponding to the viewing request on a screen with a configuration similar to the input screen that is the source of that record.

[0095] <Check and correct past processing> The third item on the menu screen above, "Tag List," is used to check the IC tags 1 that have been read by the device and the processing that has been performed after reading them. When this button is selected, a list display screen is displayed that shows the tag IDs that have been read in the past, the date and time when the tags were read, and the processing that has been performed after reading them (for example, "Register," "View," etc.).

[0096] If there is any information regarding "registration" that has not been sent to the management server 2, a marker or a landmark will be displayed in the corresponding column of the list display. When the user taps on the displayed area, the screen will switch to display the corresponding information, and the user can submit the registration request on that screen. They can also modify or add comments before submitting. Images other than tree ring images can also be added that were taken within a certain period before or after the creation of the registration request. A registration request that has been sent can be deleted by a user operation, but an operation to delete a registration request that has not been sent is invalid.

[0097] For information that has already been sent, by tapping on the display area, errors in the comment field can be corrected or added, and the updated information can be sent to the management server 2 as an update command.

[0098] Furthermore, for the registered information included in the tag list that has been sent, an operation can be performed to apply for listing on the EC site. When this operation is performed, the data management unit 36 ​​creates a listing request including the tag ID corresponding to the selected information and the user ID of the dedicated terminal device 3, and the listing request is transmitted to the management server 2 by the long-distance communication control unit 35 and the long-distance wireless communication circuit 305. However, if the dedicated terminal device 3 is located in a place where long-distance wireless communication is not possible, the listing request, like the registered information, is stored in the transmission data storage unit 38, and is transmitted to the management server 2 in response to a user operation or automatically after long-distance wireless communication becomes possible.

[0099] <Child tag ID registration process> "Assistance" at the bottom of the menu screen is a maintenance item, and tapping this button displays a submenu containing buttons for specific maintenance items. This submenu includes a write process for writing child tag IDs to the child tags attached to each piece of wood after a felled log is split into multiple pieces.

[0100] When writing child tag IDs, the parent tag ID is first read using a screen similar to that shown in Figure 9-1(b) or Figure 10(b). Once the reading is complete, the screen changes to one where the number of child tags (number of divisions of the wood) can be entered, and once the number is entered, the number of child tag IDs entered is automatically generated.

[0101] After this, the screen will again appear similar to that shown in Figure 9-1(b) or Figure 10(b) (however, the text displayed will be "Tag Write" instead of "Tag Read"), and the user will hold the dedicated terminal device 3 over each child tag in turn, causing the child tag ID to be written to those child tags. As mentioned in the section on prior art, it is difficult to check the results of writing to an IC tag 1 using a general-purpose mobile terminal device, but the dedicated application 30 of this embodiment is provided with a mechanism to check that the writing was successful, such as notifying a message that writing has been completed each time writing to a child tag, and displaying the written child tag ID and the original parent tag ID side by side.

[0102] When a read process is performed on a child tag after a child tag ID has been written, not only the child tag ID mentioned above but also the tag ID originally stored in the child tag is read. However, in the dedicated terminal device 3 of this embodiment, the ID reading processing unit 33 has a function of distinguishing the child tag ID from its data format, so that when two types of tag IDs are read, the child tag ID is selected. With this function, even if a read process is performed on a child tag using a dedicated terminal device 3 of a user other than the user who wrote the child tag ID, only the child tag ID is displayed in the tag ID column on the screen shown in Figures 9 and 10, and the tag ID included in a registration request or selection request can also be limited to the child tag ID.

[0103] <Other features> The "Assist" submenu also includes downloads for updating the reference data storage unit 39 and downloads of programs for updating the dedicated application 30. These processing functions are also enabled in locations where long-distance wireless communication is possible.

[0104] If a tree-ring image is included in the information sent in response to the viewing request, tapping on the image will take you to a screen for sending a tree-ring image matching request.

[0105] In a request to compare tree-ring images, the tag ID is read from the IC tag 1 attached to the wood to be compared, then the photography control unit 31 and camera module 301 are activated to photograph the tree rings, and request information including the image file and tag ID is generated by performing a confirmation operation on the generated image. This comparison request, like the registration request, is also stored in the transmission data storage unit 38 and transmitted to the management server 2 in an environment where long-distance wireless communication is possible.

[0106] The requests stored in the transmission data storage unit 38 are retained without being deleted until transmission to the management server 2 is complete, but the dedicated application 30 may also be provided with a function to output an alarm notification if an unsent registration request is not sent even after staying in a location where long-distance wireless communication is possible for a certain period of time or more. Alternatively, a function may be provided to automatically send unsent requests stored in the transmission data storage unit 38 when long-distance wireless communication becomes possible.

[0107] In addition to the above, the dedicated application 30 can be provided with functions such as communicating with other dedicated terminal devices 3 via the Internet to communicate with other member users and general users, receiving messages addressed to the user sent from general terminal devices via the management server 2, and requesting the management server 2 to relay replies to those messages.

[0108] (4) Processing flow on Management Server 2 Next, a flow chart will be used to explain the processing flow for three types of requests (registration request, viewing request, and verification request) in the management server 2. These processes are mainly executed by the request processing unit 25 and the data management unit 26 working together, but since other processing units such as the dedicated terminal communication processing unit 22 are also involved, the following explanation will be given with the management server 2 as the main processing unit.

[0109] <Processing for registration requests> FIG. 11 shows the procedure of the process executed when a registration request is received from the dedicated terminal device 3, focusing on the process related to the tag ID in the request.

[0110] The registration request from the dedicated terminal device 3 includes the tag ID read from the IC tag 1, the sender's user ID, and the information entered on the screen shown in Fig. 9. Upon receiving this request, the management server 2 first extracts the tag ID in the request (step S1) and compares this tag ID with the tag IDs registered in the ID management table 201 of the traceability database 200 (step S2).

[0111] If the above registration request is the first request sent since the IC tag 1 was attached to the timber to be managed, the above tag ID has not yet been registered in the ID management table 201. Therefore, the determination in step S3 is "NO", and the process proceeds to step S4, where it is determined whether the tag ID is an ID with an additional code, i.e., a child tag ID.

[0112] If the ID has a normal configuration without an additional code ("NO" in step S4), the management server 2 proceeds to step S6, and registers the tag ID extracted from the registration request as a new ID in the ID management table 201. Furthermore, the management server 2 sets up a folder with the new ID as the folder name in the traceability database 200, i.e., an information storage unit 202 corresponding to the new ID (step S7), and saves various information included in the registration request in this information storage unit 202 (step S8).

[0113] On the other hand, if the tag ID determined to be new has an additional code attached thereto indicating that it is a child tag ID, the management server 2 proceeds from step S4 to step S5, and checks whether the tag ID obtained by removing the additional code from the child tag ID, i.e., the parent tag ID, is registered in the ID management table 201. If it is confirmed that the parent tag ID has been registered (step S5 is "YES"), the management server 2 subsequently executes steps S6, S7, and S8 described above to register the new child tag ID in the ID management table 201, and also sets up a dedicated information storage unit 202 for the child tag ID, in which various information included in the request is saved.

[0114] If, due to some mistake, the parent tag ID corresponding to the child tag ID is not registered in the ID management table 201 (step S5 is "NO"), the management server 2 cancels the registration request and sends an error notification to the dedicated terminal device 3 that sent the request (step S10).

[0115] If the tag ID in the registration request has already been registered in the ID management table 201 (step S3 is "YES"), the management server 2 proceeds to step S11 regardless of the ID configuration, and saves the various information included in the registration request in the information storage unit 202 corresponding to the above tag ID.

[0116] In steps S8 and S11, the information to be registered in basic information table 204 is extracted from the text data in the request and written to basic information table 204, and the information in the format described above is saved in posting history folder 205 and image folders 206 and 207. Once all the information has been saved, management server 2 proceeds to step S9 and sends a registration completion notification to dedicated terminal device 3 that issued the request, and upon completion of this transmission, processing of the registration request is terminated.

[0117] According to the above processing procedure, it is possible to handle both cases where information about timber (log) before splitting is the target of registration, and cases where information about timber after splitting is the target of registration, without making any major changes to the processing procedure. However, when a new child tag ID is extracted from a registration request, in the registration process in the ID management table 201, a hierarchical setting may be made to position the child tag ID below the parent tag ID.

[0118] <Processing for viewing requests> FIG. 12 shows the processing procedure when a viewing request is sent from the dedicated terminal device 3.

[0119] In this case, the management server 2 extracts the tag ID in the request and checks whether it is registered in the ID management table 201, just as it does in the processing of a registration request (steps S21 and S22). If the IC tag 1 to be read by the dedicated terminal device 3 is a new IC tag 1 for which no registration request has been accepted or a fake IC tag 1, step S23 becomes "NO" and the process proceeds to step S29, where an error notification is sent to the dedicated terminal device 3 that issued the viewing request.

[0120] If the tag ID extracted from the viewing request is registered in the ID management table 201 (step S23: "YES"), the management server 2 proceeds to step S24 and reads out the information to be viewed from the information storage unit 202 corresponding to the tag ID.

[0121] If the tag ID extracted from the above viewing request does not have an additional code attached (step S25 is "NO"), that is, if it is a tag ID read from an IC tag 1 attached to the wood or raw wood before it is split, the management server 2 proceeds to step S28 and transmits the information read in step S24 to the dedicated terminal device 3 that issued the viewing request.

[0122] On the other hand, if the tag ID is a child tag ID with an additional code (step S25 is "YES"), the management server 2 also reads information from the information storage unit 202 of the parent tag ID of the child tag ID (step S26). Then, in the following step S27, the information read in step S26 is integrated as older information than the information read in step S24, and the integrated information is transmitted to the dedicated terminal device 3 that issued the viewing request.

[0123] According to the above processing procedure, even if the wood that is to be viewed is a piece of wood that has been split, it is possible to check the traceability information about the wood before it was split, so the viewer can check in detail how the wood that they requested to view came to be in its current form.

[0124] However, it is not necessarily necessary to send the child tag ID information and the parent tag ID information at once; it is also possible to send the information in multiple batches, such as first sending the child tag ID information and then sending the parent tag ID information in response to an additional request for transmission from the dedicated terminal device 3, or in the reverse order.

[0125] In step S28, if a large amount of information has been registered about the timber before it is divided, the information may be transmitted in multiple batches.

[0126] Also, in both steps S27 and S28, list information that lists only a portion of the relevant registered information, or information registered in the basic information table 204, can be first sent to the dedicated terminal device 3 that issued the viewing request, and when the user selects one of the displayed pieces of information on the dedicated terminal device 3, a request for the entire selected information to be sent from the dedicated terminal device 3 to the management server 2 can be sent, and the management server 2 can respond to the request.

[0127] The general terminal device 4 can also acquire the tag ID corresponding to the specified information by specifying the reading of detailed information for information published on the EC site, or by logging in to the management server 2 and specifying non-public information before the item is put up for sale, and send a viewing request to the management server 2. The management server 2 can receive these viewing requests using the management site processing unit 21 and handle them using the same procedure as in FIG. 12 .

[0128] <Processing for listing requests> A member user who has sent a registration request to the management server 2 can send a listing request by calling up the posting record already sent to the management server from the "Tag List" on the menu screen of the dedicated terminal device 3 and specifying "List," or by selecting the item to list from a list of posting records saved on the member user's own personal page (my page) on the management site.

[0129] The listing request also includes the tag ID of the IC tag 1 attached to the lumber to be listed and the user ID of the member user who made the request. In addition, information necessary for listing, such as the price of the lumber and the date it will be available for shipping, is also entered in advance by the user and included in the listing request.

[0130] 13 shows the processing procedure when the management server 2 receives a listing request by any of the above methods. In this case, as with a view request, the management server 2 extracts the tag ID in the listing request and compares it with the registration information in the ID management table 201 (steps S31 and S32), and if no matching registration is found, sends an error notification to the terminal device that sent the listing request (steps S33 and S40).

[0131] If it is confirmed that the tag ID extracted from the listing request is registered in the ID management table 201 (step S33 is "YES"), the management server 2 extracts a user ID from the listing request (step S34) and compares the extracted user ID with the basic information table 204 of the information storage unit 202 for the tag ID (step S35).

[0132] If this comparison confirms that the user ID in the listing request matches the user ID in the latest posting record (step S36 returns "YES"), the management server 2 proceeds to step S37 and checks the status information in the basic information table 204. 7 shows four types of status information: "Not yet in circulation," "In circulation," "On display," and "Deal completed." Each of these types of information is independent flag information.

[0133] If, among these flag information, "Not yet in circulation" or "In circulation" is on and "On sale" and "Deal completed" are both off, the management server 2 determines that the item can be put up for sale, proceeds to step S38, and switches the "On sale" flag from off to on. By switching this flag, the putting up request is accepted. After this, the management server 2 transmits an acceptance completion notice to the terminal device that sent the putting up request, and ends the processing of the putting up request upon completion of the transmission.

[0134] If the timber subject to the above-mentioned exhibition request has already left the management of the member user who sent the request, and the next member user who received the timber has registered a posting record regarding that acceptance, the user ID of the latest posting record registered in basic information table 201 will not match the user ID extracted from the exhibition request, and step S36 will return "NO." In this case, management server 2 proceeds to step S40 and sends an error notification to the terminal device that sent the exhibition request.

[0135] If a listing request is received from a member user who is upstream in the distribution channel from the member user who sent the listing request and the "listing" flag has not been cleared, step S37 will be "NO" and the process will similarly proceed to step S40 and an error notification will be sent.

[0136] As described above, the acceptance process for a listing request is completed by changing the status information in the basic information table 204. Separately, in the management server 2, the EC site processing unit 28 periodically accesses the traceability database 200, picks up information whose status information has been changed to "listing," and publishes that information on the EC site. Through this routine process, when a predetermined time has passed since the acceptance of the listing request was completed, the corresponding information is published on the EC site as "new information," thereby achieving the purpose of the member user who made the request.

[0137] Even after listing an item on the EC site, the member user who listed the item can add information by sending a registration request or an update request, and the added information can be reflected on the EC site.

[0138] In the example of Figure 13, the member user who made the most recent posting record has the authority to list items for sale, but this is not limited to this. For example, only member users in a specific industry or only specific member users who have been determined in advance may be allowed to list items, and only listing requests containing the user IDs of those users may be accepted.

[0139] As described above, in this embodiment, a member user who has the authority to register traceability information can register the wood under his / her management, and then list the wood on an e-commerce site for purchase by general users. This potentially allows for matching that would be unthinkable under existing distribution systems.

[0140] For example, a forest owner may attach an IC tag 1 to a growing tree, register information about the tree in traceability database 200, and then send a listing request; a furniture maker may see the information on an e-commerce site and apply to buy the tree; or a market participant may send a listing request for a log that is having difficulty finding a buyer at a raw timber market, setting a low price, and a construction company may see the information on an e-commerce site and apply to buy the log; and various other connections may occur.

[0141] As in the example above, even after a sales contract is concluded via an e-commerce site for logs or timber in a state close to logs, traceability information continues to be accumulated until the logs are delivered to the buyer after undergoing normal processes such as sawing.

[0142] In addition, the e-commerce site can have a function that allows general users to post comments, such as inquiries, about the lumber being sold, and forward the comments to the seller, who can then forward the seller's reply to the user who posted the comment.

[0143] (5) Processing other requests The processing of the management server 2 for requests other than the above three main types of requests will be briefly described below.

[0144] <Processing tree ring image matching requests> In the management server 2, which receives a request to compare tree-ring images from the dedicated terminal device 3, the image comparison unit 27 accesses the traceability database 200 using the tag ID in the request, reads the tree-ring image linked to that tag ID, and compares this image with the image in the comparison request. The result of this comparison is edited by the request processing unit 25 into text information such as "suitable" or "unsuitable" or numerical information indicating the degree of suitability, and is sent from the dedicated terminal communication processing unit 22 to the dedicated terminal device 3.

[0145] After sending the matching request, the dedicated terminal device 3 waits by displaying the same standby screen (Figure 10(c)) as when the viewing request was sent, but when it receives the above response from the management server 2, it switches the display to a screen showing the received information. Through this series of processes, the user can confirm the likelihood that the timber being compared is the same as when it was harvested.

[0146] <Processing a request to update a contribution> As with a listing request, member users can send a request to update a posting record to the management server 2 by calling up a posting record that has already been sent to the management server 2 from the "Tag List" on the menu screen of the dedicated terminal device 3 and specifying options such as "Edit Comment" or "Add Image," or by selecting the target posting record from a list of posting records saved on their personal page on the management site.

[0147] When management server 2 receives the update request, it accesses basic information table 204 in information recording unit 202 for the tag ID in the request and checks whether the history information contains a posting record corresponding to the user ID in the request. If matching history information is found, management server 2 accepts the update request and saves the updated posting record in the request in posting record folder 205 or image folder 207. However, the file of the posting record before the update is not deleted, but is saved in an archive file.

[0148] (6) Additional functions and modifications In the above example, wood and raw wood intended for distribution as wood were described as the subject of traceability management, but the scope of management can be broadened to include final products made from wood (furniture, miscellaneous goods, musical instruments, doors, flooring, etc.) that are subject to traceability management and can also be listed on e-commerce sites.

[0149] When the scope is expanded in this way, there will be more opportunities for the target items to be divided, but even in these divisions, IC tag 1 attached to the item before division will be used as the parent tag, and child tags such as sticker-type tags will be attached to each of the divided items, and a child tag ID consisting of the tag ID of the parent tag with an additional code written to it will be possible to form a hierarchical structure of child tag IDs due to hourly division, with the tag ID of IC tag 1 used first at the top.

[0150] Therefore, if rules are established regarding the configuration of the additional code of child tag IDs at each level and these rules are registered in the management server 2, the management server 2 can apply the above rules to the tag ID included in the viewing request to identify all tag IDs higher than the tag ID in question, read out the information registered in the traceability database 200 for those tag IDs, and send it to the terminal device that issued the request as a response to the viewing request.

[0151] One possible method for passing on information from a parent tag ID to a child tag ID is to duplicate the information storage unit 202 of the parent tag ID along with its internal information each time a child tag ID is registered, and use the duplicate as the information storage unit 202 of the child tag ID. However, as the number of divisions and the number of divisions increase, the same information will be registered multiple times, putting a strain on the memory of the management server 2.

[0152] However, according to the method described above, only the information of the item corresponding to the child tag ID is stored in the information storage unit 202 of the child tag ID, so there is no risk of unnecessary increase in the data capacity of the management server 2. Furthermore, there is no heavy load imposed on the process of identifying the connection between tag IDs, and it becomes possible to check information on the initial piece of timber or log for any item at any stage.

[0153] If the number of items after division increases due to repeated division, the child tag ID may be represented by a pattern code such as a two-dimensional code instead of the IC tag 1, and a label with the pattern code printed thereon may be affixed to the item to be managed. In this case, management similar to that in the above embodiment can be performed by adding a function to the dedicated application 30 for reading the pattern code to input information to be registered or to send a viewing request.

[0154] In addition, when a piece of wood is divided into multiple pieces at a processing site and then combined to create a single item, and the divided pieces of wood are then reunited, there is no need to attach new sub-tags to the pieces of wood, and the IC tag or pattern code of the wood before it was divided may be used for the combined item.

[0155] In the above embodiment, the child tag ID is generated by an auxiliary function of the dedicated application 30, but this is not limited to this. The dedicated terminal device 3 that reads the parent tag ID can send an ID issuance request including the parent tag ID and the number of child tags to the management server 2, and the child tag ID can be obtained from the response from the management server 2 to the request.

[0156] Furthermore, if a pattern code is used instead of the IC tag 1, an image of the pattern code may be generated by the management server 2 in response to the above ID issuance request, and the image file may be made available for download from a private page on the management site. In this case, the response to the ID issuance request may be, for example, by sending the URL of the download page to the registered email address of the member user.

[0157] In the above embodiment, the tag ID of the IC tag 1 to be used is not registered in the management server 2 until information is registered in accordance with the first registration request, but the tag ID of the IC tag 1 to be used may be registered in advance in the ID management table 201. In this way, the management server 2 can determine the appropriateness of the tag ID in the registration request from the time it receives the first registration request, thereby preventing the use of fake IC tags 1. In particular, in areas where the number of trees that can be cut down is limited from the perspective of forest protection, taking the above measures can highly reliably prevent the illegal cutting of more than the set number of trees.

[0158] In the above embodiment, the dedicated terminal device 3 is provided with a function for distinguishing child tag IDs, and when a viewing request is generated, only the child tag ID of the two types of tag IDs obtained by reading the child tag is included in the viewing request and sent to the management server 2. However, this is not limiting, and the dedicated terminal device 3 may include the two types of tag IDs read from the child tag in the viewing request and send it, and the management server 2 that receives it may select the tag IDs. Furthermore, if this method is adopted, when the management server 2 receives the first registration request by reading a child tag, the tag ID (manufacturing code) that was originally stored in the child tag is also linked to the child tag ID and registered in the ID management table 201, and thereafter the legitimacy of various requests received can be determined based on the combination of these two types of tag IDs.

[0159] If the management server 2 is given the function of identifying child tag IDs as described above, even general terminal devices 4b, 4c that do not have the dedicated application 30 installed can send a viewing request or a tree ring image matching request by reading the tag ID from the child tag, and can receive traceability information from the management server 2 regarding the item to which the child tag is attached. [Explanation of symbols]

[0160] S Traceability Management System 1. IC tag 2 Management Server 3 Dedicated terminal device (portable terminal device) 30 dedicated applications 32 GUI control section 33 ID reading processing unit 35 Telecommunications Control Unit 36 Data Management Department 38 Transmission data storage unit 200 Traceability Database 201 ID Management Table 202 Information storage section 302 Touch Panel 303 NFC communication circuit 305 Long-distance wireless communication circuit

Claims

1. A method using an information storage medium that stores an identification code for identifying timber to be distributed in the market and is attached to the timber and moves with the timber, a management server that includes a database that stores traceability information related to the timber to which the information storage medium is attached, linked to the identification code, and that receives registration requests for registering information in the database and viewing requests for viewing information via the Internet and responds to the requests, and a mobile terminal device that has a function for reading information from the information storage medium and a long-distance wireless function for communicating with the management server, including transmitting each of the requests, In the mobile terminal device, displaying an input screen for inputting information to be registered in the database in response to reading the identification code from the information storage medium; The information entered on the input screen is stored in a memory of the device in combination with an identification code read immediately before the screen is displayed, and the stored information cannot be deleted until transmission to the management server is completed; In an environment where communication with the management server is possible, a registration request including the unsent information stored in the memory is transmitted to the management server; In the management server, executes a process of storing the information to be registered acquired from registration requests from an unspecified number of the mobile terminal devices in the database by associating each of the information to be registered with an identification code included in the request, the process including, as a target of the process, a registration request including an unregistered identification code configured by adding an additional code based on a predetermined rule to an identification code already registered in the database; In response to receiving a viewing request including one of the identification codes stored in the database from any communication terminal device via the Internet, information linked to the identification code is read from the database, and the read information is transmitted to the communication terminal device that transmitted the viewing request, and when the identification code included in the viewing request is configured to include the additional code, information linked to an identification code in the database that is configured by removing the additional code from the identification code of the viewing request is also transmitted to the communication terminal device that transmitted the viewing request. A traceability management method characterized by:

2. In the management server, In response to receiving an ID issuance request including an identification code registered in the database from the mobile terminal device provided with a function for transmitting an ID issuance request including the identification code read from the information storage medium, generate an identification code configured by adding an additional code based on the rule to the identification code in the request, and transmit response information notifying the identification code to the mobile terminal device that transmitted the ID issuance request.

2. A traceability management method according to claim 1.

3. A program for causing a mobile terminal device having a function for reading information stored in an information storage medium attached to a timber object to be managed and a long-distance wireless function for internet communication to function as a terminal device for a management server having a database for storing traceability information related to the timber to which the information storage medium is attached, linked to a unique identification code for identifying the timber, means for displaying a menu screen including options for inputting information to be registered in the database and issuing a new identification code, and for accepting operations on this screen; a means for displaying an input screen for inputting the information to be registered in response to selection of inputting the information to be registered on the menu screen and reading the identification code from the information storage medium, storing the information inputted from this input screen in a memory of the device in combination with the read identification code, and preventing the stored information from being deleted until transmission to the management server is completed; a means for transmitting a registration request to the management server, in an environment where communication with the management server is possible, to request registration of the unsent information stored in the memory; means for generating an identification code by adding an additional code based on a predetermined rule to the read identification code in response to the selection of the new identification code issuing process on the menu screen and the reading of the identification code from the information recording medium; and a program for setting the functions of each of the above means in the mobile terminal device. An application program for traceability management.

4. A program for causing a mobile terminal device having a function for reading information stored in an information storage medium attached to a piece of timber to be managed and a long-distance wireless function for internet communication to function as a terminal device for a management server having a database for storing traceability information relating to the timber to which the information storage medium is attached, linked to a unique identification code for identifying the timber, means for displaying a menu screen including options for inputting information to be registered in the database and issuing a new identification code, and for accepting operations on this screen; a means for displaying an input screen for inputting the information to be registered in response to selection of inputting the information to be registered on the menu screen and reading the identification code from the information storage medium, storing the information inputted from this input screen in a memory of the device in combination with the read identification code, and preventing the stored information from being deleted until transmission to the management server is completed; a means for transmitting a registration request to the management server, in an environment where communication with the management server is possible, to request registration of the unsent information stored in the memory; means for transmitting an ID issuance request including the read identification code to the management server in response to the selection of a request for issuance of a new identification code on the menu screen and the reading of the identification code from the information storage medium, and receiving from the management server response information including an identification code obtained by adding an additional code based on a predetermined rule to the identification code in the ID issuance request; and a program for setting the functions of each of the above means in the mobile terminal device. An application program for traceability management.

Images