Product history management method based on on-site inspections

Abstract

A method for managing product history based on on-site inspection is disclosed. The method includes a step of providing origin information in which a mobile terminal of a user who visits a production site transmits product information and production site information to a management server, a step of the management server assigning a unique product code to the product identified through the received product information, and a step of generating history in which the management server maps and registers the product code, product information, and production site information.

Description

[Technical Field]

[0001] The present disclosure relates to techniques for product history management. [Background technology]

[0002] The food history management system is a system that enables the tracking and management of food history. This system records and manages traceability information for each stage of food production, from manufacturing and processing to sales, and provides it to consumers. This guarantees consumers' right to know for safe food selection and enables prompt distribution and recall measures in the event of problems with food stability. However, there are frequent cases of manipulation of origin labels, such as Chinese kimchi being disguised as Korean kimchi. In other words, the possibility of manipulation related to the product's place of origin inevitably reduces the reliability of product history tracking. Meanwhile, Korean Patent Publication No. 10-2010-0096510 discloses a system that enables systematic management of products by managing the entire process, from production and sales to consumption, in a single system. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Korean Patent Publication No. 10-2010-0096510 Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure aims to provide a solution that enables reliable product history tracking and management. [Means for solving the problem]

[0005] According to one embodiment, a method for managing product history based on on-site inspections may include an origin information providing step in which a mobile terminal of a user who has visited a production site for inspection transmits product information and production site information to a management server; a code assigning step in which the management server assigns a unique product code to the product confirmed through the received product information; and a history generating step in which the management server maps and registers the product code, product information, and production site information. [Effects of the Invention]

[0006] According to the disclosure, product history information is registered, updated, and managed based on the user's on-site inspection, which creates the effect of making it possible to provide reliable history information to requesters, such as consumers or users who are planning to purchase or have already purchased a product. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a block diagram of a product history management system based on field inspections according to one embodiment. [Figure 2] FIG. 2 is a block diagram of a mobile terminal and a management server according to one embodiment. [Figure 3] 10 is a process flowchart of a mobile device for product history management based on field inspection according to an embodiment. [Figure 4] 10 is a specific flowchart of S110 according to an embodiment. [Figure 5] 10 is a specific flowchart of S120 according to an embodiment. [Figure 6] 10 is a process flowchart of a management server for product history management based on on-site inspection according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] The above and additional aspects of the present invention will become more apparent from the following detailed description of preferred embodiments thereof, which are given with reference to the accompanying drawings, in which:

[0009] FIG. 1 is a block diagram of a product history management system based on on-site inspections according to one embodiment. A mobile terminal 100 is a communication-enabled computing device carried by a user, such as a smartphone. An application 200 for product history management based on on-site inspections (hereinafter referred to as an "inspection management app") can be installed and executed on the mobile terminal 100. A user is a person who visits production and logistics bases to conduct inspections for product history management. A single user may visit all of the sites and inspect them, or two or more users may be assigned sites to visit and inspect them. Incidentally, the logistics bases may be sites solely for the distribution of products, or may also be sites where processing of products is also performed.

[0010] The management server 300 is a server system including one or more server computing devices, and may operate under various operating systems, including or not including Windows operating systems, MacOS, Java, Unix, or Linux. The management server 300 communicates data with the mobile terminal 100 to manage product history, and more specifically, can manage product history by linking with the inspection management application 200.

[0011] FIG. 2 is a block diagram illustrating a mobile terminal and a management server according to an embodiment. The mobile terminal 100 includes at least a memory 110, a camera 120, a display 130, a communication unit 140, a GPS receiver 150, and a terminal control unit 160. The memory 110 may store data and programs for operating the mobile terminal 100, and the inspection management app 200 may be recorded and managed in the form of program code. The camera 120 can be used to capture visual codes such as barcodes and QR codes. The display 130 allows a user to use the inspection management app 200 and is integrated with a touch panel to receive inputs from the user as well as output to the user. The communication unit 140 is a transceiver used to transmit and receive data to and from the management server 300, and the GPS receiver 150 is a receiver that receives GPS signals from GPS (global positioning system) satellites.

[0012] The terminal control unit 160 controls the entire mobile terminal 100 and may include one or more processors. The terminal control unit 160 may load and execute the physical inspection management app 200 stored in the memory 110, thereby enabling the physical inspection management app 200 to perform a process for product history management based on on-site inspections. The physical inspection management app 200 may be granted limited access privileges to specific hardware and / or software resources configured in the mobile terminal 100. For example, the physical inspection management app 200 is not generally permitted to access the GPS receiver 150, but is permitted to access the GPS receiver 150 only when a visual code such as a barcode or QR code is scanned.

[0013] The management server 300 includes a database 310 and a server control unit 320, and also includes all essential components of a server, such as a communication module, which are not shown in FIG. 2. The database 310 stores and manages history information for each product. The server control unit 320 is configured with one or more processors in hardware and performs a process for managing product history based on on-site inspections in conjunction with the inspection management application 200. This will be described with reference to FIGS. 3 to 6.

[0014] FIG. 3 is a processing flowchart of a mobile device for product history management based on on-site inspections according to one embodiment. First, a user (inspector) visits a production site or a logistics site to directly confirm the production site (place of origin, production location) or logistics site (distribution location) of a product. That is, the user visits the site and inspects the site to ensure the reliability of the product's history tracking. Then, the inspection management app 200 of the mobile device 100 performs S110 or S120 while the user is located at the site. In one embodiment, the inspection management app 200 asks the user via the display 130, etc., whether this is the first inspection (S100), and performs S110 or S120 depending on the inspection result. Here, the first inspection refers to the first inspection for the same product, which is an inspection conducted by visiting the place of origin, which is the production site. The non-first inspection refers to an inspection for a product that has already been distributed, which is an inspection conducted by visiting the distribution location, which is the logistics site. That is, S100 is a step of asking the user whether the location to be visited for the inspection is a production site or a logistics site.

[0015] If the inspection management application 200 determines in S100 that the inspection is the first inspection, it regards the user as having visited the place of origin and conducted the inspection, and performs an origin information providing step (S110) of transmitting origin information to the management server 300. If the inspection management application 200 determines in S100 that the inspection is not the first inspection, it regards the user as having visited the distribution site and conducted the inspection, and performs a distribution site information providing step (S120) of transmitting distribution site information to the management server 300. The origin information transmitted to the management server 300 through the origin information providing step (S110) includes product information and production site information. The product information may include the product name, and the production site information may include origin location data (production location data). Here, the product information may be input by the user, or the product information may be acquired together with the production site information. The distribution site information transmitted to the management server 300 through the distribution site information providing step (S120) includes a product code and distribution site information. The product code is a code uniquely assigned to a product, and the logistics base information may include the logistics location name and / or logistics location data. Here, the product code may be input by the user.

[0016] 4 is a specific flowchart of S110 according to one embodiment. First, the inspection management application 200 acquires production location data by scanning a visual code (e.g., a QR code) captured by the camera 120 in response to a user operation (S111). Here, the visual code is pre-installed at the production site and may be installed on a wall in the production factory (e.g., printed or attached as a sticker) or on fixed equipment required for producing the product. Such a visual code contains production location data indicating the location of the production site for product origin authentication, and the production location data may be location coordinate data indicating latitude and longitude.

[0017] The physical inspection management app 200 acquires location data of the mobile terminal 100 (S112). In S112, the physical inspection management app 200 may acquire GPS location data using the GPS receiver 150. That is, the terminal location data acquired in S112 may be GPS location data. In one embodiment, the physical inspection management app 200 accesses the GPS receiver 150 to acquire GPS location data only when a visual code scan is performed. At this time, the GPS receiver 150 may be in an activated state or an inactivated state depending on a user setting. If the GPS receiver 150 is in an inactivated state, the physical inspection management app 200 may temporarily activate the GPS receiver 150 to acquire the GPS location data, and then switch it back to an inactivated state. Incidentally, the physical inspection management app 200 may have authority to activate the GPS receiver 150 only when a visual code is scanned, and such authority may be granted in advance by the user.

[0018] The inspection management application 200 compares the GPS location data acquired in S112 with the production location data acquired in S111 to determine whether the production location falls within the error range of the GPS location (S113). If it is determined through S113 that the production location falls within the error range of the GPS location, the inspection management application 200 certifies that the user has accurately visited the production site for the inspection (S114). In other words, it certifies that the user's inspection location is correct. Next, the inspection management application 200 transmits origin information to the management server 300 (S115). The origin information includes product information (e.g., product name) and production base information.

[0019] In one embodiment, when S114 is performed, the inspection management app 200 requests the user to input the product name and receives the input. In another embodiment, the inspection management app acquires not only the production location data but also the product name in S111. That is, the visual code can be scanned to acquire both the production location data and the product information. The production base information may include the production location data acquired in S111 or the terminal location data acquired in S112, or may include both. The origin information may also include inspection time information, which may be the time when the user's inspection location is successfully authenticated through S114.

[0020] Additionally, the inspection management application 200 may transmit a unique identifier for user identification together with the country of origin information to the management server 300 in S115. Here, the unique identifier may be an identifier (terminal ID) uniquely assigned to the mobile terminal 100. Meanwhile, if it is determined in S113 that the production location is outside the error range of the GPS location, the inspection management application 200 processes the authentication as unsuccessful (S116). In this case, the inspection management application 200 may report the authentication failure to the management server 300.

[0021] According to the above, if the visual code for country of origin authentication is installed at a location other than the production site, authentication will inevitably fail, so the user's on-site inspection visit can be accurately checked. In addition, since there is no need to install short-range communication resources such as beacons, and there is no need for continuous GPS location tracking, the use of GPS resources in the mobile terminal 100 can be minimized.

[0022] 5 is a specific flowchart of S120 according to one embodiment. First, the inspection management application 200 acquires production location data by scanning a visual code (e.g., a QR code) captured by the camera 120 in response to a user's operation (S111). Here, the visual code is pre-installed at the logistics base, and contains logistics location data indicating the location of the logistics base, which may also be location coordinate data indicating latitude and longitude.

[0023] The on-site inspection management app 200 acquires location data of the mobile terminal 100 (S122). In S122, the on-site inspection management app 200 may acquire GPS location data using the GPS receiver 150. That is, the terminal location data acquired in S122 may be GPS location data. In one embodiment, the on-site inspection management app 200 accesses the GPS receiver 150 to acquire GPS location data only when a visual code scan is performed. At this time, the GPS receiver 150 may be in an activated state or an inactivated state depending on a user setting. If the GPS receiver 150 is in an inactivated state, the on-site inspection management app 200 may temporarily activate the GPS receiver 150 to acquire GPS location data and then switch it back to an inactivated state.

[0024] The inspection management application 200 compares the GPS location data acquired in S122 with the logistics location data acquired in S121 to determine whether the logistics location falls within the error range of the GPS location (S123). If it is determined in S123 that the logistics location falls within the error range of the GPS location, the inspection management application 200 certifies that the user has accurately visited the logistics site for the inspection (S124). If the authentication is successful, the inspection management application 200 transmits logistics location information to the management server 300 (S125). The logistics location information includes a product code and logistics base information, and the logistics base information may include the logistics location data acquired in S121 and / or the terminal location data acquired in S122. The logistics location information may also include inspection time information, which may be the time when the user's inspection location is successfully authenticated in S124.

[0025] The product code included in the distribution location information is a unique code, such as a serial number, assigned to identify the product and can be input by the user. For example, if the user's inspection location is successfully authenticated, the inspection management application 200 may request the user to input the product code. As another example, the product code may be printed on the product in the form of a barcode, and the inspection management application 200 may acquire the product code by scanning the barcode after performing S214. Once the product code is input or acquired, the inspection management application 200 transmits the distribution location information to the management server 300. Meanwhile, if it is determined in S123 that the production location is outside the error range of the GPS location, the inspection management application 200 processes the authentication as unsuccessful (S126). In this case, the inspection management application 200 may report the authentication failure to the management server 300.

[0026] FIG. 6 is a processing flowchart of a management server for product history management based on a field inspection, according to an embodiment. The server control unit 320 of the management server 300 receives base information from the mobile terminal 100. The base information is origin information or logistics location information. Because the origin information does not include a product code, but the logistics location information does, it is easy to determine whether the received base information is origin information or logistics location information. When the server control unit 320 receives the origin information, it generates a unique product code to be assigned to the product (S200) (S210). The generated product code can be transmitted to the user's inspection management app 200 or provided to the origin manager via the user for use. For example, the user or the origin manager can attach the product code to the product in the form of a sticker or the like to be used for history management.

[0027] The server control unit 320 maps the generated product code with the received place of origin information and registers it as product history information in the database 310 (S220). At this time, if the production base information included in the place of origin information is location data, the server control unit 320 can convert it into place name information of the corresponding location and register it in the database 310. In other words, the location data of the production base information is converted into the place of origin name and registered in the database 310.

[0028] Thereafter, when the server control unit 320 receives the distribution location information, it updates the corresponding product history information registered in the database 310 with the received distribution location information (S230)(S240). Specifically, the server control unit 320 searches the corresponding product history information from the database 310 using the product code of the received distribution location information, and adds and registers the remaining information belonging to the distribution location information to the searched product history information. At this time, if the distribution base information belonging to the distribution location information is location data, the server control unit 320 can convert it into place name information of the location before adding it. In other words, the location data of the distribution base information is converted into the distribution location name and added and registered.

[0029] Next, the server control unit 320 checks whether the logistics base visited by the user is the final logistics base (S250). Information about the final logistics base can be registered and managed in advance in a database, so the server control unit 320 can check the logistics base information included in the logistics location information received from the mobile terminal 100 and determine whether the confirmed logistics base is the final logistics base. If the confirmed logistics base is not the final logistics base, the above-mentioned steps S230 and S240 are repeated until the product is transported to the final logistics base.

[0030] In one embodiment, when the server control unit 320 receives a unique identifier (e.g., a terminal ID) along with the place of origin information from the mobile terminal 100, it authenticates the user using the received unique identifier, and performs S210 only if the authentication is successful. In other words, the product history information is registered only after authenticating that the user who has been assigned inspection authority for the relevant location is correct. Furthermore, even when the server control unit 320 receives a unique identifier along with the place of origin information from the mobile terminal 100, it can perform a user authentication procedure and determine whether to perform S240.

[0031] Meanwhile, consumers and others can use the product code online to check the product's history recorded in the database 310 and confirm its origin and distribution route.

[0032] The present invention has been described above with a focus on its preferred embodiments. Those skilled in the art will understand that the present invention can be embodied in various forms without departing from the essential characteristics of the present invention. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the claims, not the foregoing description, and all variations within the scope of the claims should be construed as being within the scope of the present invention.

Claims

1. A product history management method based on on-site inspections in which an inspector visits production sites and logistics sites to inspect the products, A step of providing origin information in which the mobile terminal of the user who has visited the production site transmits product information and production site information to the management server; a code assigning step in which the management server assigns a unique product code to the product identified through the received product information; a history generation step in which the management server maps and registers product codes, product information, and production base information; a logistics location information providing step in which a mobile terminal of a user who has visited a logistics location transmits a product code and logistics location information to a management server; a history updating step in which the management server additionally maps and registers the logistics location information recognized as the received logistics base information to the corresponding product code; The mobile terminal asks the user whether the location to be visited is a production site or a logistics site, and confirms this; If the response indicates that the location of the inspection is a production base, the country of origin information provision stage will be carried out. If the location of the inspection is a logistics base, the logistics location information provision stage will be carried out. The stage of providing information on origin is as follows: acquiring production location data from code data obtained by scanning a visual code provided at a production site; obtaining location data of the mobile device; comparing the production location data with the terminal location data to determine whether the production location falls within an error range of the terminal location; If the determination result indicates that the production location is within the error range of the terminal location, it is authenticated that the user has visited the production site for product history management, and the product information and production site information are transmitted to a management server.

2. 2. The method for managing product history based on on-site inspection according to claim 1, wherein the step of acquiring terminal location data is automatically performed when the production location data is acquired.

3. acquiring logistics location data from code data obtained by scanning a visual code provided at the logistics base; acquiring location data of a mobile device when the logistics location data is acquired; comparing the distribution location data with the terminal location data to determine whether the distribution location falls within an error range of the terminal location; 2. The method for managing product history based on on-site inspections as described in claim 1, further comprising: if the determination result indicates that the logistics location is within the error range of the terminal location, authenticating the user's inspection visit and transmitting the product code and logistics base information to the management server.

4. 4. The method for managing product history based on on-site inspections according to claim 3, wherein the step of providing distribution location information and the step of updating history are repeated every time a user visits each distribution location for inspection.

Images