Wood traceability management method and application program used for this 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 confirmation of information on lumber distributed in the market, tracing back to the time of felling or before felling. In particular, the present invention relates to an information management technology that attaches an information storage medium that stores 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] Conventional management systems that use IC tags, which are a typical information storage medium, for managing the distribution of lumber are known from the following Patent Documents 1 and 2.

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

[0004] Patent Document 2 describes how management information is written to an electronic tag (corresponding to an IC tag) attached to timber, and how thereafter management information is added to the electronic tag each time work is performed, while also transmitting similar management information to a management device having a database to store the information. 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 timber so that it will not be removed between felling of the log and processing into lumber, and by making it impossible to erase information once it has been 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 the pattern code is read to access a computer that holds traceability information and enable management information to be confirmed. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2006-130853 A [Patent Document 2] JP 2007-26415 A [Patent Document 3] JP 2008-301783 A Summary of the Invention [Problem to be solved by the invention]

[0007] In recent years, IC tags (commonly referred to as "NFC tags") that use the NFC (short for 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 it is easy to manage information using IC tags.

[0008] However, in order to provide end users with easy-to-understand information rather than simply recording management, 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 the 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] Considering these circumstances, it seems appropriate to set up an Internet server that centrally manages traceability information, and to adopt a method of sending and storing the information to be managed on this server. In this case, what usually comes to mind is a method described in Patent Document 3, in which a label with a pattern code (two-dimensional code or barcode) that represents the identification code is attached to the lumber, and the server is accessed by reading the pattern code, allowing the information to be sent and the registered information to be confirmed.

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

[0011] The present invention focuses on the above problems and aims to enable easy registration of traceability information at the site where timber is placed even using a general-purpose mobile terminal device, and to ensure that information entered in places where radio waves cannot reach can also be reliably registered in the management server. [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 timber to be distributed in the market, and a database that stores traceability information on the timber to which the information storage medium is attached, linked to the identification code, and 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 portable terminal device that has a function of 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.

[0013] First, in response to reading the identification code from the information storage medium, the mobile terminal device displays an input screen for inputting information to be registered in the database, combines the information entered from this input screen with the identification code read immediately before the screen is displayed, and stores the information in the memory of the device, and prevents the information from being deleted until transmission to the management server is complete. After that, in an environment in which communication with the management server is possible, a registration request including the unsent information stored in the memory is sent 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, linked to the identification code included in each registration request. In addition, in response to receiving a view request including 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 view request.

[0015] According to the above method, by attaching an information storage medium that stores a unique identification code for identifying timber to the timber to be managed, a worker at the site can hold a mobile terminal device over the information storage medium to read the identification code, thereby displaying an input screen on the mobile terminal device and immediately inputting the necessary information. Even if the site is in an area where long-distance wireless radio waves do not reach or reach poorly, the input information is combined with the identification code read immediately before and stored in the memory of the mobile terminal device, so that when the worker moves to a place where long-distance wireless communication can be performed reliably, 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 timber 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 in the database the information to be registered in the registration request received from the mobile terminal device, provided that the registration request contains 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 one piece of wood is linked to an identification code stored in one information storage medium and registered in a database. However, after a piece of wood is divided into several pieces by lumber processing or the like, it is desirable to manage the traceability information of each piece of wood after the division and to have the traceability information before the division be inherited by each piece of wood after the division.

[0020] In order to enable the above management, in the management server of the first embodiment of the present invention, when a registration request received from a mobile terminal device includes an unregistered identification code configured by adding an additional code based on a predetermined rule to an identification code already registered in the database, the management server registers the identification code in the registration request in the database, and links the information to be registered in the registration request to the identification code and stores it in the database.

[0021] In a second embodiment of the present invention, a mobile terminal device is provided with the function of sending an ID issuance request including an identification code read from an information storage medium to a management server, and when the management server receives an ID issuance request including an identification code registered in the database, it generates an identification code consisting of the identification code in the request plus the aforementioned additional code, and transmits response information informing the mobile terminal device that sent the issuance request of the identification code.

[0022] Furthermore, in the first and second embodiments, when an identification code included in a view request from a communication terminal device includes the additional code, information associated with the identification code of the view request in the database and information associated with an identification code obtained by removing the additional code from the identification code can be transmitted to the communication terminal device that sent the view request. These two types of information can be transmitted all at once or in multiple batches.

[0023] According to the first and second embodiments, when a piece of wood is split into several pieces at the midpoint of the distribution route, each piece of split wood is assigned an identification code that is the identification code of the information storage medium attached to the original wood plus an additional code with different content for each piece of wood, 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 accumulate 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 accumulated for that identification code, information accumulated for the identification code obtained by subtracting the additional code from that identification code, i.e., information about the wood before it was split, can also be transmitted to the communication terminal that transmitted 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 an authentication code of a user previously certified as a registrant of traceability information, and registers the information of the registration request in the database by linking it to information identifying the logged-in user. Furthermore, when the management server receives a listing request for lumber related to information registered in the database linked to information identifying 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, a person who has become authorized to sell timber in the timber distribution process can put up for sale by publishing the registered information after registering it in the management server. Also, without being bound by the existing distribution system, it is possible to directly link forest owners and intermediate sellers to 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-mentioned management method. Effect of the Invention

[0027] According to the present invention, by attaching to wood an information storage medium that stores a unique identification code for identifying the wood to be managed, transmitting the information entered into a management server from a mobile terminal device that reads this identification code and inputs information about the wood and the read identification code, and storing the information in the management server database linked to the identification code, it is possible to significantly increase the amount of data that can be registered as traceability information. Thus, in addition to information for management purposes, information for conveying detailed information about each piece of wood to end users in an easy-to-understand manner can be registered.

[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, it becomes possible to easily register traceability information at the site where the lumber 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, information input at a site where long-distance wireless communication is difficult can also be reliably registered in the management server. [Brief description of the drawings]

[0029] [Figure 1] 1 is an explanatory diagram illustrating a schematic configuration of a traceability management system to which the present invention is applied. [Diagram 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. [Diagram 3] FIG. 2 is a cross-sectional view illustrating an internal configuration of the IC tag. [Figure 4] FIG. 2 is a cross-sectional view showing the above IC tag attached to wood. [Diagram 5] FIG. 11 is a front view showing an example in which the above-mentioned IC tag is attached to each of a plurality of pieces of wood. [Figure 6] 1 is a functional block diagram of a management server used in the above traceability management system. [Figure 7] FIG. 2 is an explanatory diagram illustrating an example of a data structure 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] 11A to 11C 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] 11 is an explanatory diagram showing a transition of screens displayed when a browsing request is sent to a management server on the dedicated terminal device. FIG. [Figure 11]13 is a flowchart showing a procedure of a process executed by the management server when it receives a registration request. [Figure 12] 13 is a flowchart showing a procedure of a process executed by the management server when it receives a browse request. [Figure 13] 13 is a flowchart showing a procedure of a process executed by the management server when a listing request is received. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0030] (1) Overview of the traceability management system FIG. 1 shows a schematic configuration of a timber 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 timber 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 someone authorized to register information in this database 200.

[0031] 1 shows only one each of the IC tag 1 and the mobile terminal device 3, but in reality, any number of them may be included in the management system S. In this embodiment, the mobile terminal device 3 of the member user is a smartphone, but instead, a mobile terminal device such as a tablet terminal incorporating the same operating system as a smartphone may be used. A dedicated application 30 is incorporated in these mobile terminal devices to cause the devices 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 a management site and an EC site described below.

[0033] Hereinafter, the mobile terminal device 3 installed with the program of the dedicated application 30 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 devices 4". However, even the dedicated terminal device 3 can access the management server 2 via the management site without using the functions of the dedicated application 30.

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

[0035] The general terminal device 4 can usually only browse the EC site, but 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 browse the traceability information regarding the items before listing. Also, even a general user can install the program of the dedicated application 30 on their own 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 matching 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 front and back appearances of the IC tag 1 used in this embodiment, and FIG. 3 shows the internal configuration of the IC tag 1. 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, 11b by injection molding, and has a screw hole 10 formed in the center that passes through the thickness of the case body 11. 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 non-volatile 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 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 Fig. 4, the IC tag 1 having the above configuration is attached to the wooden piece 5 to be managed by a wood screw 6 inserted into a screw hole 10. As the wood screw 6 is embedded inside the wooden piece 5, the support protrusion 15 on the bottom surface also bites into the wooden piece 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 is possible to determine whether or not the IC tag 1 has been used based on 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 since it is stored in a write-protected area, 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, taking advantage of the above advantages, as shown in FIG. 5, an IC tag 1 is attached to each piece of wooden wood 5, and the manufacturing codes read out from the IC tags 1 are stored in the management server 2 as identification codes for identifying the wooden wood 5, linked to the traceability information of the wooden wood 5 to which the IC tag 1 is attached.

[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, and an IC tag 1 that has never been used before is attached to the wood 5 before it enters the distribution channel, and the tag ID is linked to the traceability information of the wood 5, thereby improving the reliability of the traceability information of the wood 5. 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 wood 5 with only one wood screw 6, the work of fixing it to the wood 5 can be made easier.

[0043] Although the IC tag 1 is often attached to logs or logs after felling, this is not limited to this. It is also possible to attach the IC tag 1 to trees 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 transported to a sawmill. Up until that point, the log is often maintained as a single log, but when it arrives at the sawmill, it is split into several pieces, and each piece is processed into new lumber (hereafter uncoded). New IC tags 1 are also 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 pass on the traceability information generated up until the log was split to the lumber after it is split, 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 (the configuration shown in Figures 2 and 3), but depending on the size and type of the wood after division, it will be changed to an IC tag such as a card type 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. As shown in FIG. The management server 2 includes one or more computers, and has in its memory a traceability database 200 for accumulating 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 for each piece of information relating to the same piece of wood, and are registered in association with the tag ID.

[0048] The user information storage unit 210 stores, for each user, information for identifying an 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. In addition, for member users, attribute information indicating the business name and the business type (forest owner, feller, transporter, processor, etc.) is also stored. For member users who are involved in felling of logs, information for 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 from registered users and accepts specific requests 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 comes into action, accepts the information necessary 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. For access from the dedicated terminal device 3, the authentication processing unit 23 performs login authentication and accepts various requests 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 those.

[0052] The request processing unit 25 analyzes requests 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 depending on the content of the requests to execute processing according to the requests.

[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 EC site lumber whose information has been 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 communications processing unit 22, while viewing requests and listing requests are accepted by both the dedicated terminal communications processing unit 22 and the management site processing unit 21.

[0054] In addition to the above, the management server 2 receives update requests for adding supplemental information to registered information, and comparison requests for comparing a tree-ring image obtained by actually photographing a piece of wood whose tree-ring image is 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 executes 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 by 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, 4 that sent the request.

[0057] The EC site processor 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. On this EC site, part of the traceability information of the lumber whose request to put up for sale has been accepted is posted, but when a request to read detailed information of a specific item is received from a terminal device 3 or 4 that has accessed the site, the EC site processor 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 including 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 specific lumber, the payment processing unit 29 cooperates with an external payment system to carry out processing for receiving payment from the applicant.

[0059] Although the EC site can be accessed from the general terminal device 4 without logging in, 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] Thus, a registered general user can log in to the management server 2, switch the site displayed in the browser as needed, and check some information on timber that is not on sale by searching the traceability database 200. Also, by installing the dedicated application 30 program on his / her mobile terminal device 4b, 4c, he / she can read the tag ID from the IC tag 1 of a specific piece of timber at a log market or the like, send a viewing request to the management server 2, and view the traceability information of the specific piece of timber. Furthermore, if an image of tree rings is registered for the specific piece of timber, he / she can take a picture of the actual piece of timber in front of him / her, send a matching request including the image to the management server 2, and receive the matching result from the management server, thereby checking 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 of 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 were included in a registration request and sent to the management server 2 and accepted by the process of Fig. 11 described below 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 stores therein a basic information table 204 in which basic information about the corresponding lumber is registered, and three types of subordinate folders 205, 206, 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, arrival date at the log market, lumber mill, 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 for saving information (hereinafter referred to as "posting records") that member users input from the operation screen in Fig. 9 described below and send to management server 2 together with a registration request. Folder 205 saves the main part of the posting records, folder 206 saves image files of tree-ring images to be matched by image matching unit 27, and folder 207 saves image files other than tree-ring images. The number of these folders 205, 206, and 207 is not limited to one each, but multiple folders can be set depending on the data capacity, the date and time of data generation, etc.

[0066] An html file including the text data in the transmitted information (including that stored in the basic information table) is stored in the posting record folder 205. If the transmitted information includes an image file, a hyperlink to the image file is set in the 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, so that both the text portion and the image of the posting record can be displayed on the terminal device 3, 4.

[0068] However, the data file of the posting record is not limited to an html file, but may be an XML file, a CSV file, or simply a text file or other format file. Even if the file format does not allow for a hyperlink to an image file, the association 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> Fig. 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 shown separated by a dashed frame. Although not shown in Fig. 8, an operation system exists between the dedicated application 30 and the hardware 300. As with the operation system, among the software that is standardly equipped 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 shooting 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 memory unit 37, a transmission data memory unit 38, and a reference data memory unit 39.

[0071] The user information storage unit 37 stores, for the user who uses this dedicated terminal device 3, substantially the same information as that registered in the user information storage unit 210 of the management server 2. Furthermore, the user information storage unit 37 in this embodiment stores history information of 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 of receiving a response from the management server 2).

[0072] The transmission data storage unit 38 stores information input from an input screen 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 even after transmission is complete, the information is retained unless the user performs an erase operation.

[0073] Information that may be useful for the user's business (such as a list of representative tree photos and explanations, map information showing the distribution range of forests, and a list of locations and contact information for forestry associations, log markets, lumber mills, etc.) is registered in the reference data storage unit 39. The registered information in this reference data storage unit 39 can be updated as needed by downloading it from an information providing 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 for setting an 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 a configuration as shown in Fig. 9 or 10 on the touch panel 302 and accepts operations on that screen.

[0075] The photography control unit 31 cooperates 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. As 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 was 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 transmits a request to the management server 2 via the long-distance wireless communication circuit 305 (compliant with standards such as Wi-Fi, 4G, and 5G) and receives 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 any of the above-mentioned requests, the request is read from the transmission data storage unit 38 by the data management unit 36 ​​and passed to the long-distance communication control unit 35, and then transmitted to the management server 2 by the long-distance wireless communication circuit 305.

[0079] (3) Main processing in the dedicated terminal device 3 Next, the flow of the registration and viewing of traceability information, which is the main process performed by the dedicated terminal device 3, will be described 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 of a specific piece of wood, and the second button, "View tag information," is a button for selecting the process of viewing traceability information of a specific piece of wood. The second button from the bottom on the menu screen, "Upload," is a button for selecting the process of transmitting information stored 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 information to be registered, and the content of the screen changes in response to user operation.

[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 start up, 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] Following the above instructions, the user holds the dedicated terminal device 3 over the target IC tag 1, and when 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 any of these text areas are tapped, the screen is ready to accept input of information for that item.

[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 among them. 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 that 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 write comments freely. 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 the camera module 301 are started, and the screen temporarily switches to one that displays the image being shot by the camera module 301. When the user performs a shooting operation here and performs a confirmation operation on the generated image, the image is displayed under the item as an image to be registered (FIG. 9-2(g)). "Other images" can be selected from images saved from the current time up to a certain time ago. Also, each image is not limited to one, but multiple images can be entered. However, neither tree-ring images nor other images are required information. Also, the function for inputting 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 photographs in advance.

[0087] As the amount of input information increases, items at the bottom of the screen cannot be displayed, but by scrolling appropriately, the hidden items can be moved to the main part of the screen, as shown in Fig. 9-2(g). Also, as the input of information progresses, the current location information (latitude and longitude) acquired by the GPS module 304 is replaced with a specific address by the location information processing unit 34, and the 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 switched 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 place where long-distance wireless communication is possible, the registration request saved in the transmission data storage unit 38 can be transmitted to the management server 2 by continuing to operate 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 transmitted 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> Fig. 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 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)) instructing reading of the IC tag 1. When reading of the tag ID is completed, the data management unit 36 ​​creates a viewing request including the read tag ID, and this is transmitted from the long-distance communication control unit 35 to the management server 2 via the long-distance wireless communication circuit 305. From this transmission until the response information of the management server 2 is received, the touch panel 302 is in a state of displaying a standby screen as shown in Fig. 10(c).

[0093] Thereafter, 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 FIG. 10(d).

[0094] For ease of explanation, in Fig. 10, 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 subject 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 similar configuration to the input screen that is the source of the record.

[0095] <Check and correct past processing> The third "Tag List" on the above menu screen is for checking 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 tag was read, and the processing that was performed after reading (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 relevant field of the list display to draw attention to the information. When the user taps on the displayed area, the screen will switch to display the relevant information, and the user can send the registration request on that screen. In addition, comments can be modified or added before sending. 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 completely sent can be deleted by a user operation, but an operation to delete a registration request that has not been completely sent is invalid.

[0097] For information that has already been sent, by tapping on the display area, errors can be corrected or additions can be made in the comment field, 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 already been transmitted, 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, when the dedicated terminal device 3 is located in a place where long-distance wireless communication is not possible, the listing request is stored in the transmission data storage unit 38 as well as the registered information, 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 contains a write process for writing child tag IDs to 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 (the number of divisions of the wood) can be entered, and once the number of child tag IDs entered is entered, they are automatically generated.

[0101] After this, the screen will again look like that of 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 prior art section, it is difficult to check the results of writing to the IC tag 1 using a general-purpose mobile terminal device, but the dedicated application 30 of this embodiment is provided with a mechanism for checking that the writing has been completed successfully, such as by notifying a message that writing has been completed each time writing is performed to a child tag, and by 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, in addition to the above child tag ID, the tag ID originally stored in the child tag is also 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 the registration request or selection request can also only be 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, the user can tap on the image to move to a screen for sending a tree-ring image matching request.

[0105] For a tree-ring image matching request, the tag ID is read from the IC tag 1 attached to the wood to be matched, then the photography control unit 31 and camera module 301 are started to photograph the tree rings, and the generated image is confirmed to generate request information including the image file and tag ID. This matching request is also stored in the transmission data storage unit 38, like the registration request, and is 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 the transmission to the management server 2 is completed, but the dedicated application 30 may be provided with a function for outputting an alarm notification when an unsent registration request is not sent even after staying in a place where long-distance wireless communication is possible for a certain period of time or more. Alternatively, a function for automatically sending an unsent request in the transmission data storage unit 38 when long-distance wireless communication becomes possible may be provided.

[0107] In addition to the above, the dedicated application 30 can be provided with a function for communicating with other dedicated terminal devices 3 via the Internet in order to communicate with other member users and general users, a function for receiving messages addressed to the user sent from general terminal devices via the management server 2, and a function for 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 process flow for three types of requests (registration request, viewing request, and comparison request) in the management server 2. Note that these processes are mainly executed by the request processing unit 25 and the data management unit 26 in cooperation with each other, 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 unit of the processes.

[0109] <Processing 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 of Fig. 9. When the management server 2 receives this request, it 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 (step S4 is "NO"), 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 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 resulting from 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 above steps S6, S7, and S8 are subsequently executed to register the new child tag ID in the ID management table 201, and a dedicated information storage unit 202 is set for the child tag ID, and various information included in the request is stored therein.

[0114] If, due to some mistake, the parent tag ID corresponding to the child tag ID has not been 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: "YES"), the management server 2 proceeds to step S11 regardless of the ID configuration, and stores 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. When saving of all the information has been completed, management server 2 proceeds to step S9 to transmit 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 a timber (log) before it is split and cases where information about a timber after it is split, 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 browsing requests> FIG. 12 shows a 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, similar to the processing for a registration request (steps S21, 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 out 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 object of viewing is a piece of wood that has been split, it is possible to check traceability information about the wood before it was split, allowing the viewer to check in detail how the piece of 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 parent tag ID information at once. It is also possible to send the information in multiple installments, 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 sending in the reverse order.

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

[0126] Also, in both steps S27 and S28, list information in which only a portion of the relevant registered information is extracted and listed, or information registered in the basic information table 204, is 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 transmission of all of the selected information is sent from the dedicated terminal device 3 to the management server 2, and the management server 2 responds to the request.

[0127] The general terminal device 4 can also acquire a 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 unpublished information before listing, and send a viewing request to the management server 2. The management server 2 can receive these viewing requests by the management site processing unit 21 and handle them in the same manner as in FIG.

[0128] <Processing 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 "Listing," or by selecting the item to be listed 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 timber 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 timber and the date it will be available for shipping, is also input 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 checks it against 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: "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 above tag ID (step S35).

[0132] If this comparison confirms that the user ID in the listing request matches the user ID in the most recent posting record ("YES" in step S36), the management server 2 proceeds to step S37 and checks the status information in the basic information table 204. 7, four types of status information are shown: "Not in circulation," "In circulation," "On sale," and "Sold." Each of these types of information is an independent flag information.

[0133] Of these flag information, if "not yet in circulation" or "in circulation" is on and "on sale" and "sold" 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 that, the management server 2 transmits an acceptance completion notice to the terminal device that transmitted the putting up request, and ends the processing of the putting up request upon completion of the transmission.

[0134] If the timber that is the subject of the above-mentioned putting up request has already left the management of the member user who sent the request, and the next member user who receives 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 putting up request, and step S36 will return "NO." In this case, management server 2 proceeds to step S40 and transmits an error notification to the terminal device that sent the putting up request.

[0135] If a listing request is accepted from a member user upstream in the distribution channel from the member user who sent the listing request and the "listing" flag has not been released, 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 of the listing request is completed by changing the status information in the basic information table 204. Separately from this, 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 an item, but this is not limited to the above. For example, only member users in a specific industry or only specific member users determined in advance may be allowed to list items, and only listing requests that include 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 or her management, and then list the wood on the EC site for purchase by general users. This may enable matching that would not be possible 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 an exhibition request; a furniture maker who sees the information on an EC site may offer to buy the tree; or a market participant may send an exhibition request for a log that is struggling to sell at a raw timber market, setting a low price, and a construction company who sees the information on the EC site may offer to buy the log. Various connections may occur.

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

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

[0143] (5) Processing other requests The processing by 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 out 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" and / or numerical information indicating the degree of suitability, and is transmitted 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 submission update requests> As with a listing request, a member user 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 the member user's personal page on the management site.

[0147] Upon receiving the update request, management server 2 accesses basic information table 204 in information recording unit 202 for the tag ID in the request, and checks whether a posting record corresponding to the user ID in the request is included in the history information. 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 are described as the subject of traceability management, but the subject 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 be listed on e-commerce sites.

[0149] When the target 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 plus an additional code will be written to each child tag, thereby forming 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 codes of child tag IDs at each stage and these rules are registered in the management server 2, the management server 2 can identify all tag IDs higher than the tag ID included in the viewing request by applying the above rules, read out 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 of 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, if the number of times division is performed or the number of divisions increases, the same information will be registered multiple times, putting a strain on the memory of the management server 2.

[0152] However, according to the above-mentioned method, 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. In addition, there is no heavy load imposed on the process of identifying the tag ID connections, and it becomes possible to check information on the initial timber or log for items at any stage.

[0153] If the number of divided items increases after 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. Even in this case, management similar to that in the above embodiment can be performed by adding a function to the dedicated application 30 for inputting information to be registered and sending a viewing request by reading the pattern code.

[0154] In addition, when a piece of wood is divided into several pieces at a processing site and then the divided pieces of wood are combined to make a single item, or when the divided pieces of wood are reintegrated, there is no need to attach new child 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 integrated 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 the above. 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, when 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 that case, the response to the ID issuance request may be, for example, a notification of the URL of the download page sent 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 based on the first registration request is registered, 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 suitability of the tag ID in the registration request from the stage of receiving the first registration request, thereby preventing the use of a fake IC tag 1. In particular, in areas where the number of trees that can be cut is limited from the viewpoint of forest protection, taking the above measures can highly reliably prevent 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 transmitted to the management server 2. However, this is not limiting, and the dedicated terminal device 3 may transmit the viewing request including the two types of tag IDs read from the child tag, and the management server 2 that receives the request 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) 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 validity 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 viewing requests or tree ring image matching requests by reading the tag ID from the child tag, and 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. The method uses an information storage medium which 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 which includes a database which stores traceability information on the timber to which the information storage medium is attached in association with the identification code, and which receives, via the Internet, registration requests for registering information in the database and viewing requests for viewing information and responds to the requests, and a portable terminal device which 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 inputted from 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; transmitting a registration request including the unsent information stored in the memory to the management server in an environment in which communication with the management server is possible; In the management server, the information to be registered, acquired from registration requests from an unspecified number of the mobile terminal devices, is stored in the database in association with an identification code included in each of the registration requests, and in response to receiving a viewing request including one of the identification codes stored in the database from any of the communication terminal devices via the Internet, the information associated with the identification code is read from the database, and the read information is transmitted to the communication terminal device which transmitted the viewing request; A traceability management method comprising the steps of:

2. In the management server, storing, in the database, the information to be registered in the registration request received from the mobile terminal device, on condition that the identification code registered in the database is included in the registration request; 2. A traceability management method according to claim 1.

3. In the management server, when a registration request received from said mobile terminal device includes an unregistered identification code configured by adding an additional code based on a predetermined rule to an identification code already registered in said database, registering said identification code in said registration request in said database, and storing said information to be registered in said registration request in said database in association with said identification code; when the identification code included in the viewing request from the arbitrary communication terminal device is configured to include the additional code, information linked to the identification code of the viewing request in the database and information linked to an identification code obtained by removing the additional code from the identification code can be transmitted to the communication terminal device that is the source of the viewing request.

2. A traceability management method according to claim 1.

4. In the management server, in response to receiving an ID issuance request including an identification code registered in the database from the portable terminal device provided with a function for transmitting an ID issuance request including the identification code read from the information storage medium, generating an identification code configured by adding an additional code based on a predetermined rule to the identification code in the request, and transmitting response information notifying the portable terminal device that transmitted the issuance request of the identification code; when the identification code included in the viewing request from the arbitrary communication terminal device is configured to include the additional code, information linked to the identification code of the viewing request in the database and information linked to an identification code obtained by removing the additional code from the identification code can be transmitted to the communication terminal device that is the source of the viewing request.

2. A traceability management method according to claim 1.

5. 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 wood 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 on the piece of wood to which the information storage medium is attached, in association with a unique identification code for identifying the piece of wood, the program comprising: a means for 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, and accepting input of information by operating the screen; a means for storing information inputted from said input screen in a memory of said device in combination with an identification code read immediately before said screen is displayed, and for preventing said stored information from being deleted until transmission to said management server is completed; a means for transmitting, to the management server, a registration request for requesting registration of the untransmitted information stored in the memory, under an environment in which communication with the management server is possible; A program for setting the functions of each of the above means in the mobile terminal device is included. An application program for traceability management.

Images