System and information processing method

Abstract

To provide a system and information processing method that can display various information websites on a display unit of a user terminal according to certain conditions when a code attached to an object is read by an imaging unit of the user terminal.SOLUTION: When a code 60 attached to an object is read by an imaging unit 16 of a user terminal 10, a URL request command attached to the code 60 is transmitted from the user terminal 10 to a computer (management server 20). A control node is provided for switching pages corresponding to the URL request command attached to the code 60 according to predetermined conditions without changing the code 60.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a system and an information processing method. [Background technology]

[0002] Various systems have been known in the past that allow a user to read a two-dimensional code attached to an advertisement using a user terminal, and then display a website on the user terminal with more detailed information about the advertisement (see, for example, Patent Document 1, etc.). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-140218 Summary of the Invention [Problem to be solved by the invention]

[0004] In conventional systems, when a user scans a two-dimensional code attached to an advertisement with a user terminal, the content of the website displayed on the user terminal is fixed, which makes it difficult to provide a variety of information to users.

[0005] The present disclosure has been made with these points in mind, and aims to provide a system and information processing method that can display websites with various information on the display unit of a user terminal depending on conditions when a code attached to an object is read by the imaging unit of the user terminal. [Means for solving the problem]

[0006] The system of the present disclosure comprises: an object having a code attached thereto that can be read by an imaging unit of a user terminal; A computer, A system comprising: When the code attached to the object is read by the imaging unit of the user terminal, a request command for a URL assigned to the code is transmitted from the user terminal to the computer, the computer transmits a database search command to a database storing information about a website page when it receives a URL request command from the user terminal, and displays the website page corresponding to the URL request command on a display unit of the user terminal based on the search results returned from the database in response to the transmitted database search command; A control node is provided for switching the page corresponding to the request command of the URL assigned to the code in accordance with predetermined conditions without changing the code.

[0007] In the system of the present disclosure, The computer may create a control node when it receives an instruction to create a control node from an administrator terminal.

[0008] The computer may also set the predetermined conditions in the control node in accordance with the contents of the predetermined conditions in the control node creation instruction received from the administrator terminal.

[0009] The computer may also modify the control node upon receiving an instruction to modify the control node from an administrator terminal.

[0010] A parent control node that manages the plurality of control nodes is further provided, The parent control node may be configured to change the operation of each control node collectively when the computer receives a predetermined command.

[0011] The computer may also create a parent control node upon receiving an instruction to create a parent control node from an administrator terminal.

[0012] In addition, when the computer receives a specified command, the parent control node may change the operation of each control node collectively so that the page corresponding to the request command of the URL assigned to the code becomes the specified page.

[0013] The information processing method of the present disclosure includes: An information processing method using a system including an object having a code attached thereto that can be read by an imaging unit of a user terminal, and a computer, When the code attached to the object is read by the imaging unit of the user terminal, a request command for a URL assigned to the code is transmitted from the user terminal to the computer, a step in which the computer transmits a database search command to a database storing information about a website page when receiving a URL request command from the user terminal, and displays the website page corresponding to the URL request command on a display unit of the user terminal based on search results returned from the database in response to the transmitted database search command; a step of the computer switching, by a control node, a page corresponding to a request command of a URL assigned to the code in accordance with a predetermined condition without changing the code; The present invention is characterized by the following. [Effects of the Invention]

[0014] According to the system and information processing method of the present disclosure, when a code attached to an object is read by the imaging unit of a user terminal, websites with various information can be displayed on the display unit of the user terminal depending on the conditions. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a block diagram showing a configuration of a system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is an explanatory diagram showing a utility pole wrapped with an advertisement having a code such as a two-dimensional code attached thereto. [Figure 3] 1 is an explanatory diagram showing a medium such as a card, coupon, or point ticket to which a code such as a two-dimensional code is attached. [Figure 4] FIG. 10 is an explanatory diagram showing a map showing the positions of utility poles, displayed on the display unit of a user terminal. [Figure 5] FIG. 2 is an explanatory diagram showing the relationship between nodes and edges. [Figure 6] 1 is a table showing various parameters of nodes and their descriptions. [Figure 7] 1 is a table showing various parameters of edges and their descriptions. [Figure 8] 10 is a table showing settings for actions. [Figure 9] 10 is a table showing settings for branch actions (action_branch). [Figure 10] FIG. 10 is a chart showing the operation of the system when a code attached to an object is read by an imaging unit of a user terminal. [Figure 11] FIG. 10 is an explanatory diagram showing how the information processing means constructs a screen from node information based on search results returned from a database, and prompts the user to "remember" the action. [Figure 12] This is a screen that is displayed on the display unit of the user terminal and prompts the user to "remember" the information. [Figure 13] This is a list of recently learned nodes displayed on the display of the user terminal. [Figure 14] FIG. 10 is an explanatory diagram showing a set of nodes that are connected by the repeated "remember" relationship. [Figure 15] FIG. 10 is a chart showing the operation of the system when the user reads the code attached to the object with the user terminal for the second or subsequent time. [Figure 16] This is an explanatory diagram showing the operation when the information processing means of the management server creates a link between the acquired owner node and the target node identified as a search result searched in the database, and links them with an edge of the "remember" type. [Figure 17] FIG. 10 is a chart showing the operation of the system when a system administrator creates a guidebook using an administrator terminal. [Figure 18] FIG. 10 is an explanatory diagram showing how a guide and a page, called a "member," are connected by an edge. [Figure 19] FIG. 10 is an explanatory diagram showing how multiple guides can be connected to form a larger guide, and how nodes created for bookmarks can be used for guides. [Figure 20] FIG. 10 is a chart showing the operation of the system when a system administrator creates a stamp rally using the administrator terminal. [Figure 21] This is an explanatory diagram showing a situation where a larry and a page are connected by an edge called "member." [Figure 22] FIG. 10 is a chart showing the operation of the system when a user participates in a stamp rally using a user terminal. [Figure 23] FIG. 10 is a diagram showing a stamp rally screen displayed on the display unit of the user terminal. [Figure 24] 10 is a diagram showing how the three parties, Page and Larry, are connected by edges. [Figure 25] FIG. 10 is a diagram showing how a stamp rally is configured by nodes of the stamp rally, their members, and stamp statuses. [Figure 26] FIG. 10 is a chart showing the operation of the system when an administrator creates a control node. [Figure 27] FIG. 10 is an explanatory diagram showing an example in which a guide is switched depending on the time of day (morning, afternoon, or evening) by a control node. [Figure 28] FIG. 10 is a chart showing the operation of the system when the code of the control node is read by the imaging unit of the user terminal. [Figure 29A] FIG. 10 is an explanatory diagram showing the delegation of each guide to a node. [Figure 29B] 10 is a control node creation screen displayed on the display unit of the administrator terminal when the administrator creates a control node. [Figure 30]FIG. 10 is a chart showing the operation of the system when an administrator creates a parent control node. [Figure 31] FIG. 10 is an explanatory diagram showing a configuration in which a parent control node and a control node are connected by an edge. [Figure 32] FIG. 10 is a chart showing the operation of the system when an emergency situation such as a disaster occurs. [Figure 33A] FIG. 1 is an explanatory diagram showing the operation of the system when an emergency situation such as a disaster occurs. [Figure 33B] FIG. 10 is an explanatory diagram showing the operation of a parent control node for achieving flexible centralized management using weighting and categories when controlling control nodes. [Figure 33C] FIG. 10 is a chart showing the operation of the system when an administrator creates a weighting centralized control node. [Figure 33D] FIG. 10 is an explanatory diagram showing the connection between the control node and edges when an administrator creates a weighting centralized control node. [Figure 33E] FIG. 10 is an explanatory diagram showing the control node, edges, and node connections when an administrator creates a weighted centralized control node. [Figure 33F] FIG. 10 is a chart showing the operation of the system when an emergency situation such as a disaster occurs, using a weighted centralized control node. [Figure 34] FIG. 10 is a chart showing the operation of an action (point awarding) using a code such as a two-dimensional code. [Figure 35] FIG. 10 is an explanatory diagram of an aspect in which a code such as a two-dimensional code is read by an imaging unit of a user terminal and points are awarded to a user who possesses the user terminal. [Figure 36] FIG. 10 is a chart showing the operation of an action (title assignment) using a code such as a two-dimensional code. [Figure 37] FIG. 10 is an explanatory diagram showing an aspect in which an owner node and a title node are connected by an edge. [Figure 38] FIG. 10 is a chart showing the operation of the system when a user participates in multiple stamp rallies consecutively using a user terminal. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. FIG. 1 is a diagram showing a system 1 according to the present embodiment and each component of the system 1. FIG. 2 is an explanatory diagram showing a utility pole 62 wrapped with an advertisement 64 bearing a code 60 such as a two-dimensional code, and FIG. 3 is an explanatory diagram showing a medium 66 such as a card, coupon, or point ticket bearing a code 60 such as a two-dimensional code. FIG. 4 is an explanatory diagram showing a map indicating the location of each utility pole 62, displayed on the display unit 14 of a user terminal 10. FIG. 5 is an explanatory diagram showing the relationship between nodes and edges.

[0017] [Overall configuration of System 1] As shown in Fig. 1, the system 1 of this embodiment includes a management server 20, an administrator terminal 30, and a database 40. In the system 1 of this embodiment, a user terminal 10 such as a smartphone or a PC tablet carried by a user is communicably connected to the management server 20 via a communication network 50 such as the Internet. Furthermore, in the system 1 of this embodiment, each of the administrator terminal 30 and the database 40 is communicably connected to the management server 20 via the communication network 50 such as the Internet. Each component of the system 1 and the user terminal 10 will be described in detail below.

[0018] [Configuration of user terminal 10] The configuration of user terminal 10 will be described with reference to Fig. 1. As described above, user terminal 10 includes, but is not limited to, a smartphone, a PC tablet, etc. As shown in Fig. 1, user terminal 10 has a control unit 12, a display unit 14, an operation unit 15, an imaging unit 16, a storage unit 17, and a communication unit 18. Control unit 12 is connected to each of display unit 14, operation unit 15, imaging unit 16, storage unit 17, and communication unit 18 via bus 11.

[0019] The control unit 12 is composed of a circuit including a CPU and a semiconductor memory, and controls the operation of the user terminal 10 by executing a program stored in the storage unit 17. The display unit 14 is composed of, for example, a liquid crystal display or the like, and functions as a means for displaying various information. The display unit 14 displays various information in response to instructions from the control unit 12. The operation unit 15 functions as a means for inputting various instructions by the user. For example, a touch panel or the like is used as the operation unit 15. When the operation unit 15 is a touch panel, such a touch panel is superimposed on the display unit 14, and an operation signal is input to the control unit 12 when the user touches the touch panel.

[0020] The imaging unit 16 is, for example, a camera or the like, and captures an image or video by capturing an image of an object. In this embodiment, the imaging unit 16 is capable of reading a code 60, such as a two-dimensional code, attached to the object. The storage unit 17 is composed of a flash memory, a memory card, or the like. The storage unit 17 stores a program executed by the control unit 12. The storage unit 17 also stores information input by a user via the operation unit 15, images and videos captured by the imaging unit 16, and the like. The communication unit 18 includes a communication interface that transmits and receives various data between the control unit 12 and an external device, such as the management server 20, via a communication network.

[0021] [Configuration of management server 20] The configuration of the management server 20 will be described with reference to FIG. 1. The management server 20 includes a control unit 22, a storage unit 28, and a communication unit 29. The management server 20 displays various types of websites on a browser or the like displayed on the display unit 14 of the user terminal 10. As shown in FIG. 1, the management server 20 includes a control unit 22, a storage unit 28, and a communication unit 29. The control unit 22 is connected to the storage unit 28 and the communication unit 29 via a bus (not shown). The control unit 22 is configured with a circuit including a CPU and semiconductor memory, and controls the operation of the management server 20 by executing a program stored in the storage unit 28. Specifically, the control unit 22 functions as an information receiving means 23, an information processing means 24, a transmission means 25, a control node setting means 26, and a parent control node setting means 27 by executing a program stored in the storage unit 28. The information receiving means 23 receives various information from the user terminal 10, the administrator terminal 30, the database 40, etc. via a communication network 50. The information processing means 24 performs various processes on the information etc. received by the information receiving means 23. The transmission means 25 transmits the information received by the information receiving means 23 and the information processed by the information processing means 24 to the user terminal 10, the administrator terminal 30, the database 40 etc. via the communication network 50. The control node setting means 26 creates a control node which will be described later. The parent control node setting means 27 creates a parent control node which will be described later.

[0022] The storage unit 28 is configured with a hard disk drive (HDD), random access memory (RAM), read only memory (ROM), or solid state drive (SSD), etc. The storage unit 28 stores programs executed by the control unit 22. The storage unit 28 also stores various website information (specifically, HTML information that constructs websites, etc.) in association with URL information.

[0023] The communication unit 29 includes a communication interface for transmitting and receiving various data between the control unit 22 and each of the user terminal 10, the administrator terminal 30, and the database 40 via a communication network.

[0024] [Configuration of administrator terminal 30] The configuration of the administrator terminal 30 will be described with reference to FIG. 1. The administrator terminal 30 is installed in an office of a business company that manages the management server 20, and is operated by an administrator who manages the management server 20. The administrator terminal 30 includes, but is not limited to, a personal computer, a smartphone, a PC tablet, etc. As shown in FIG. 1, the administrator terminal 30 has a control unit 32, a display unit 34, an operation unit 35, a printing unit 36, a storage unit 37, and a communication unit 38. The control unit 32 is connected to each of the display unit 34, the operation unit 35, the printing unit 36, the storage unit 37, and the communication unit 38 via a bus 31.

[0025] The control unit 32 is composed of a circuit including a CPU and a semiconductor memory, and controls the operation of the administrator terminal 30 by executing a program stored in the storage unit 37. The display unit 34 is composed of, for example, a liquid crystal display or the like, and functions as a means for displaying various information. The display unit 34 displays various information in response to instructions from the control unit 32. The operation unit 35 functions as a means for inputting various instructions by the user. For example, a keyboard, a mouse, a touch panel, etc. are used as the operation unit 35. When the operation unit 35 is a touch panel, such a touch panel is superimposed on the display unit 33, and an operation signal is input to the control unit 32 when the user touches the touch panel.

[0026] The printing unit 36 ​​is, for example, a printer, and is configured to print a code 60, such as a two-dimensional code described below, on paper, a sticker, etc. The storage unit 37 is composed of a hard disk drive (HDD), random access memory (RAM), read only memory (ROM), or solid state drive (SSD), etc. The storage unit 37 stores programs executed by the control unit 32. The communication unit 38 includes a communication interface that transmits and receives various data between the control unit 32 and external devices such as the management server 20 via a communication network.

[0027] [Database 40 configuration] The database 40 stores various information related to websites displayed on the display unit 14 of the user terminal 10. The database 40 stores various nodes and edges. Details of the nodes and edges stored in the database 40 will be described later.

[0028] Next, an object to which a code 60 according to this embodiment can be attached will be described with reference to FIGS. 2 and 3. FIG. 2 shows a utility pole 62 wrapped with an advertisement 64 to which a code 60, such as a two-dimensional code, is attached. A plurality of such utility poles 62 are installed, for example, at a tourist spot. This allows tourists visiting the tourist spot to participate in a stamp rally, visiting each utility pole 62 and reading the code 60 with the user terminal 10. Furthermore, a website displayed on the display unit 14 of the user terminal 10 may display a map showing the locations of the utility poles 62, as shown in FIG. 4, for example.

[0029] 3 shows a medium 66 such as a card, coupon, or point ticket with a code 60, such as a two-dimensional code, attached thereto. Such medium 66 is distributed to customers as a special gift by a store clerk when they purchase a product, for example. By reading the code 60 printed on the distributed medium 66 with the user terminal 10, the customer can access a website or the like that contains details about the purchased product, and the website can be displayed on the display unit 14 of the user terminal 10.

[0030] Next, a process performed by the control unit 22 of the management server 20 according to this embodiment will be described. The process described below is performed by the information processing means 24 of the control unit 22 executing a program stored in the storage unit 28. In this embodiment, the control unit 22 represents data as nodes and relationships as edges, and the process performed by the control unit 22 is based on the relationship between two nodes. Specifically, when "Taro" performs the action of "remembering" "Store A" in the node-edge relationship shown in FIG. 5, the node ID (node_id1) of "Taro" (the subject) and the node ID (node_id2) of "Store A" are connected by an edge type of "remember" (edge_type=0). In this embodiment, the node ID is set, for example, as shown in FIG. 6. The edge type is set, for example, as shown in FIG. 7.

[0031] In addition, in the control unit 22 of this embodiment, an action is executed in response to some kind of trigger. For example, an action is defined as an operation to be executed when the code 60 is read by the imaging unit 16 of the user terminal 10. FIG. 8 is a table showing the settings for actions. For example, for the code 60, a code is created by displaying an action_key (a public random character string) in the URL. Specifically, the URL becomes "actions / {action_key}". Also, the above-mentioned edge has an action_id, and an action is executed when two nodes are connected by the edge. The definition of the action is defined in action_data. In this embodiment, for example, distribution of points or coupons is defined as an action. Furthermore, a branch action (action_branch) can be defined for the action. FIG. 9 is a table showing the settings for the branch action (action_branch). For example, in the case of a "point ticket that becomes unusable after one use," an action is executed, but the branch action (action_branch) is used as disposable data. For example, if you want to use a coupon that can only be used once to award 10 points, perform the action and then create a branch action and assign it to a URL such as "branches / {branch_key}".

[0032] Next, we will explain the operation when the image capture unit 16 of the user terminal 10 reads a code 60 attached to an object, such as an advertisement 64 wrapped around a utility pole 62 or a medium 66. When the image capture unit 16 of the user terminal 10 reads the code 60 attached to the object, a request command for the URL attached to the code 60 is transmitted from the user terminal 10 to the management server 20 (computer). Furthermore, when the management server 20 receives a URL request command from the user terminal 10, it transmits a database search command to a database 40 that stores information about website pages, and causes the display unit 14 of the user terminal 10 to display the website page corresponding to the URL request command based on the search results returned from the database 40 in response to the transmitted database search command. This operation will be explained in more detail using Figure 10.

[0033] When the code 60 attached to the object is read by the imaging unit 16 of the user terminal 10 ("(1) Code Reading" in FIG. 10), a signal related to a URL request is transmitted from the user terminal 10 to the management server 20 based on the information in the read code 60 ("(2) URL Request" in FIG. 10). Here, the information in the code 60 read by the user terminal 10 is, for example, URL information such as "xx-memory.jp / memory / abcdefc," where "abcdefc" is the node_key. Furthermore, the signal related to the URL request transmitted from the user terminal 10 to the management server 20 includes this URL information.

[0034] When the information receiving means 23 of the management server 20 receives a signal related to a URL request from the user terminal 10, the transmitting means 25 of the management server 20 transmits a database search command to the database 40 ("(3) Database Search" in FIG. 10). At this time, the database search command includes the above-mentioned URL information, which is information of the code 60 read by the user terminal 10. In the database 40, based on the database search command transmitted from the management server 20, more specifically, based on the node_key (specifically, the character string "abcdefc") extracted from the above-mentioned URL information, the nodes table is searched to identify the node. That is, since the node_key is a key for uniquely accessing a node in the database 40, it is possible to search the nodes table in the database 40 by extracting the node_key from the URL information. The search result (specifically, the identified target node (the node to be remembered (e.g., id=2345678))) is returned from the database 40 to the recording screen ("(4) Search result return" in FIG. 10).

[0035] The information processing means 24 of the management server 20 constructs a record page based on the search results. The transmission means 25 transmits a screen display command to the user terminal 10 to display the constructed record page on the display unit 14 of the user terminal 10 ("(5) Screen display" in Figure 10). Specifically, the information processing means 24 constructs a screen from node information based on the search results returned from the database 40, and prompts the user to perform a "memorize" action (see Figure 11). At that time, the node_key extracted from the above URL information is hidden in a hidden field or the like. Figure 12 shows a screen displayed on the display unit 14 of the user terminal 10 to prompt the user to perform a "memorize" action.

[0036] When "Save" is selected on the screen shown in FIG. 12 displayed on the display unit 14 by the operation unit 15 of the user terminal 10, a request is made from the user terminal 10 to the recording screen based on the result ("(6) Select 'Save'" in FIG. 10). Thereafter, the management server 20 checks whether or not a guest_key exists in the cookie ("(7) Cookie Search" in FIG. 10). When the user first reads the code 60 attached to an object such as an advertisement 64 or a medium 66 using the user terminal 10, an owner node, which is the user's alter ego, does not exist and no guest_key exists in the cookie, so the information processing means 24 determines that "this is the user's first use." In this case, the management server 20 sends an owner creation command to the database 40 ("(8) Create Owner" in FIG. 10). Specifically, a node for the user (owner node (e.g., 1234567), owner nodes are consecutively numbered) is created in database 40, and a guest_key (e.g., a1b2c3d4) is issued. As described above, in system 1 of this embodiment, people, things, places, videos, and websites are all represented as data called nodes. For this reason, a node is also required for the subject user. Also, since there is no owner node in database 40, a subject owner node is created as data, and a unique key called guest_key is set (see Figure 11). The guest_key is also saved in a cookie. In other words, the "guest_key" is set in the URL of My Memory, which will be described later, and this serves as a substitute for the person's ID.

[0037] Next, the information processing means 24 of the management server 20 creates a link between the created owner node and the target node identified as a search result searched for in the database 40, linking them with an edge of the "memory" type ("(9) Create link (edge)" in FIG. 10). At this time, the link is created with edge_type=memory. More specifically, as shown in FIG. 11, the ID of the owner node is set in the node_id1 field, and the ID of the target node is set in node_id2, and the data of the edges connected with edge_type=memory is created as a record in the database 40.

[0038] Next, the information processing means 24 of the management server 20 issues a dedicated URL (My Memory) based on the guest_key and redirects ("(10) Redirect based on guest_key" in FIG. 10). The issued dedicated URL (My Memory) is, for example, "XX-memory.jp?guest_key=a1b2c3d4".

[0039] The information processing means 24 of the management server 20 then searches the database 40 based on the guest_key ("a1b2c3d4" in the above example) of the redirect destination URL ("(11) Bookmark Search" in Figure 10). Since the guest_key is a unique key, the owner can be identified by searching the node with this key. In addition, the list of nodes pointed to by the memory edges connected to the owner is targeted.

[0040] In the database 40, the newly created owner node of the user is identified based on the guest_key. A list of the "memorized" nodes associated with it is returned from the database 40 to My Memory ("(12) Search Result Response" in FIG. 10). The information processing means 24 of the management server 20 creates a "My Memory" screen from the list and displays a list of "recently memorized" nodes in descending order of updated_at of edges. Thereafter, by accessing this URL, all memorized nodes can be displayed on the display unit 14 of the user terminal 10 ("(13) My Memory Screen Display" in FIG. 10). FIG. 13 shows a list of recently memorized nodes displayed on the display unit 14 of the user terminal 10. When each node shown in FIG. 13 is tapped, the corresponding page is accessed. In addition, the number of times each node is read is counted, and the update_at of the edge is updated (the "order of recently accessed" displayed on the display unit 14 of the user terminal 10 uses this update_at).

[0041] In this way, in the processing of system 1 shown in FIG. 10, the owner node and an existing node (node_key=abcdefc) are connected by a "remember" relationship (see FIG. 11). Also, in the processing of system 1 shown in FIG. 10, since this is the user's first time using the system, an owner node is created as the user's alter ego, and a relationship is then created between the owner node and the target node. Also, as shown in FIG. 14, a collection of nodes that have repeatedly connected by a "remember" relationship is displayed in "My Memory." This allows the user to perform online bookmarking by simply reading a code 60, such as a two-dimensional code, attached to an object with the imaging unit 16 of the user terminal 10, without having to register as a user or download an app on the user terminal 10.

[0042] FIG. 15 is a chart showing the operation of the system 1 when the user reads the code 60 attached to an object such as an advertisement 64 or a medium 66 using the user terminal 10 for the second or subsequent time. In the operation of the system 1 shown in FIG. 15, unlike the operation of the system 1 shown in FIG. 10, when the management server 20 checks whether the guest_key exists in the cookie ("(7) Cookie Search" in FIG. 15), the guest_key already exists, and therefore an owner node exists in the database 40. Therefore, the information processing means 24 of the management server 20 acquires a user node (owner node) representing the user's alter ego from the database 40 based on the guest_key. Unlike the operation of the system 1 shown in FIG. 10, the operation of the system 1 shown in FIG. 15 does not require the creation of an owner node. Then, as shown in FIG. 16, the information processing means 24 of the management server 20 creates a link between the acquired owner node and the target node identified as the search result searched for in the database 40, and links them with a "remember" type edge ("(9) Link (Edge) Creation" in FIG. 15).

[0043] As shown in Figure 15, when a user reads a code 60 attached to an object such as an advertisement 64 or a medium 66 for the second or subsequent time using the user terminal 10, the other operations of the system 1 are the same as those of the system 1 shown in Figure 10, so they will be omitted.

[0044] In the processing of system 1 shown in Figure 15, when a person who is already using the service of this embodiment reads a new code 60, such as a two-dimensional code, attached to an object using the imaging unit 16 of the user terminal 10, the person can add the code to a bookmark (my memory).

[0045] Next, the operation when an administrator of the system 1 of this embodiment creates a guidebook using the administrator terminal 30 will be described with reference to FIG. 17. The administrator logs in to the administration screen using the administrator terminal 30 ("(1) Display administration menu" in FIG. 17). This administration screen is constructed by the administration server 20, and the administration screen transmitted from the administration server 20 to the administrator terminal 30 is displayed on the display unit 34 of the administrator terminal 30. Next, using this administration screen, the administrator moves to a "page registration screen" using the administrator terminal 30 ("(2) Move to page registration screen" in FIG. 17). This page registration screen is also displayed on the display unit 34 of the administrator terminal 30. Then, using this page registration screen, the administrator creates individual pages using the administrator terminal 30 and stores them in the database 40 ("(3) Create individual page" in FIG. 17). Specifically, the administrator registers necessary information, such as URLs, page names, and page images, for pages to be included in the guidebook, for example, store pages and product pages, on the administrator terminal 30, and stores them in the database 40 as "nodes." The administrator repeats this operation for as many pages as necessary.

[0046] Next, the administrator moves to the "guide registration screen" on the management screen using the administrator terminal 30 ("(4) Move to guide registration screen" in Figure 17). This type of guide registration screen is also displayed on the display unit 34 of the administrator terminal 30. Then, on this type of guide registration screen, the administrator creates a guidebook node on the administrator terminal 30. In this embodiment, the guidebook also becomes a node, and pages created using this system also become nodes, making it possible to issue codes 60 such as two-dimensional codes. The issued codes 60 can be printed on various objects by the printing unit 36 ​​of the administrator terminal 30. The created guidebook node is saved in the database 40 ("(5) Create guide" in Figure 17).

[0047] The administrator then adds the node registered in the database 40 in "(3) Create individual page" in Figure 17 to the members of the guidebook ("Place the page created in (6)(3) in the guide" in Figure 17). When adding a member, the guide and page are connected by an edge, as in bookmarks, as shown in Figure 18. In this case, the edge connects the nodes as "member" rather than "memory." In this way, the guidebook and the member's edge are connected by a member relationship and saved in the database 40.

[0048] The administrator then downloads a recording code 60 from the guide screen (see "(8) Download recording code from guide screen" in Figure 17). Because the guide itself is a node, it is possible to issue a code 60 such as a two-dimensional code, bookmark it, or make it a "stamp rally member" (described later). In this way, stamp rallies where guides are collected can also be held in the same way, making it easy to combine services to build higher-level services.

[0049] Figure 18 shows a diagram illustrating how a guide and a page are connected by an edge called "member." As shown in Figure 18, many-to-many connections are possible, allowing existing nodes to be used in other guides. The relationship between a guide and a page can also be expressed using nodes and edges. Multiple members can participate in a guide, and each is represented as a node. The only difference between a guide and a bookmark is the edge_type. In Figure 18, the "member" edge indicates an inclusion relationship. Because a guide is also a node, it can be used as a record code 60. Furthermore, as shown in Figure 19, multiple guides can be connected to form a larger guide, or a node created for a bookmark can be used for a guide or a stamp rally. Furthermore, by wrapping the URL of an existing homepage in a node, it is possible to freely rearrange and create a guide without recreating the existing homepage, and to use it as a record code 60.

[0050] In this way, in the processing of System 1 shown in Figure 17, multiple nodes are combined to create a large node (guide). Even in this case, no new data structure is required, and it is possible to build it using the relationship between "nodes" and "edges."

[0051] Next, the operation when an administrator of system 1 of this embodiment creates a stamp rally using administrator terminal 30 will be described with reference to FIG. 20. The administrator logs in to the administration screen using administrator terminal 30 ("(1) Display administration menu" in FIG. 20). This administration screen is constructed by administration server 20, and the administration screen transmitted from administration server 20 to administrator terminal 30 is displayed on display 34 of administrator terminal 30. Next, using this administration screen, the administrator moves to the "page registration screen" using administrator terminal 30 ("(2) Move to page registration screen" in FIG. 20). This page registration screen is also displayed on display 34 of administrator terminal 30. Then, using this page registration screen, the administrator creates a rally page using administrator terminal 30 and stores it in database 40 ("(3) Create rally page" in FIG. 20). Specifically, the administrator registers the necessary information for the rally page, including the URL, page name, page image, etc., using administrator terminal 30, and stores it in database 40 as a "node." The administrator repeats this operation for as many rally pages as necessary.

[0052] Next, the administrator moves to the "Rally Registration Screen" on the administration screen using administrator terminal 30 ("(4) Move to Rally Registration Screen" in FIG. 20). This type of rally registration screen is also displayed on display unit 34 of administrator terminal 30. Then, on this type of rally registration screen, the administrator creates a rally node on administrator terminal 30. In this embodiment, rallies also become nodes, and pages created using this system also become nodes, making it possible to issue QR codes (registered trademark). The created rally node is saved in database 40 ("(5) Create Rally Node" in FIG. 20). By creating rallies as nodes, they can also be used for a variety of purposes.

[0053] After that, the administrator adds the node registered in the database 40 in "(3) Create a rally page" in Figure 20 to the members of the rally ("Add the node created in (6)(3) to the members of the rally" in Figure 17). When adding a member, the rally and the page are connected by an edge, just like bookmarks, as shown in Figure 21. In this case, too, the node is connected by an edge as "member" rather than "memory". In this way, the rally and the page are connected by a member relationship and saved in the database 40.

[0054] The administrator then downloads the rally code 60 for each point from the rally screen (see "(8) Download rally code for each point from the rally screen" in Figure 20). Because the rally itself is a node, it is possible to issue a code 60 such as a two-dimensional code. In this way, stamp rallies where people collect guides can also be held in the same way.

[0055] Figure 21 shows a situation in which a rally and a page are connected by an edge called "member." As shown in Figure 21, many-to-many connections are possible, allowing existing pages to be used in other rallies. Furthermore, since each node has a URL if it was registered when the guide was created, it is possible to navigate to the URL's linked destination. This makes it possible to create a "guide-assisted stamp rally" in which a stamp rally doubles as a guide. In this way, even with the same inclusion relationship using "member," different services can be created if the connected parent nodes are different. Furthermore, stamp rally nodes can be bookmarked or "stamp rally locations." Furthermore, by using the "action" described above, it is possible to set the completion of a stamp rally as a stamp condition for another stamp rally. This makes it theoretically possible to create an infinite number of stamp rallies that are higher in level than one another. This will be explained in more detail later.

[0056] In the processing of System 1 shown in Figure 20, multiple rallies are combined to create a large node. Even in this case, no new data structure is required, and it is possible to build it using the relationship between "nodes" and "edges."

[0057] Next, the operation of the user terminal 10 when the user participates in a stamp rally will be described with reference to FIG.

[0058] When the stamp rally code 60 is read by the imaging unit 16 of the user terminal 10 ("(1) Code reading" in FIG. 22), a signal for a URL request is sent from the user terminal 10 to the management server 20 based on the information in the read code 60 ("(2) URL request" in FIG. 22). This causes access to the management server 20. The stamp rally URL is, for example, "xx-memory.jp / stamps / {encrypted value of edge_id}". The information processing means 24 of the management server 20 decrypts the encrypted value and acquires the edge_id.

[0059] The information processing means 24 of the management server 20 searches for edges in the database 40 based on the decrypted edge_id ("(3) Search database based on decrypted edge_id" in Figure 22). The relationships represented by edges are also entities that have attributes, since they are data in the database 40. In this embodiment, a member edge is searched for. As shown in Figure 21, the member edge contains the stamp rally sheet ID (node_id1) and the location ID (node_id2). In other words, edges contains information on "in which stamp rally" and "at which location" the stamp was taken. In this way, a corresponding record of edges is searched for in the database 40 based on the decrypted edge_id, and if a corresponding record is found, the respective nodes are obtained from the corresponding node_id1 (rally ID) and node_id2 (location ID), and the search results are returned to the management server 20 ("(4) Return result" in Figure 22).

[0060] Then, the information processing means 24 of the management server 20 checks whether an owner node exists in the database 40 ("(5) Check whether an owner exists" in FIG. 22). If an owner node exists, it is used, and if not, a new owner node is created.

[0061] Next, the information processing means 24 of the management server 20 checks the database 40 to see if the code 60 captured by the imaging unit 16 of the user terminal 10 during the stamp rally has already been stamped. Specifically, a search is performed using edge_type=stamp, with root_node_id being the stamp rally ID, node_id1 being the owner node ID, and node_id2 being the location ID. If this is the first time that a stamp has been applied to the code 60 captured by the imaging unit 16 of the user terminal 10 during the stamp rally, an edge is created with root_node_id being the stamp rally ID, node_id1 being the owner node ID, node_id2 being the location ID, and edge_type=stamp (specifically, an edge saying "stamped" is created). This clarifies "who (node_id1)," "which stamp rally (root_node_id)," "which location (node_id2)," and "who stamped (edge_type=stamp)," and this information is stored in the database 40 ("(7) Stamping" in FIG. 22). On the other hand, if a stamp has already been applied to the code 60 captured by the imaging unit 16 of the user terminal 10 during the stamp rally, the operation of "(7) Execute stamp" in FIG. 22 is skipped.

[0062] Furthermore, when the stamp rally is being carried out by the user for the first time, the information processing means 24 of the management server 20 bookmarks the stamp rally in My Memory ("(8) Register My Memory" in FIG. 22). The information processing means 24 of the management server 20 then redirects the stamp rally screen ("(9) Redirect to Stamp Rally Screen" in FIG. 22). The transmission means 25 then transmits a display instruction to the user terminal 10 to display the redirected stamp rally screen on the display unit 14 of the user terminal 10. As a result, the stamp rally screen as shown in FIG. 23 is displayed on the display unit 14 of the user terminal 10.

[0063] When a user as shown in FIG. 22 participates in a stamp rally using the user terminal 10, the owner, page, and rally are connected by edges as shown in FIG. 24. The root_node_id is used to indicate which user (owner node) stamped which page in which stamp rally. As a result, even if a user who has registered the same location in a stamp rally has already stamped the same location in another stamp rally, it cannot be said that the user stamped in this stamp rally. This is because even if the same person stamps the same location, if the root_node_id is different, it is considered that the stamp has not yet been made.

[0064] As shown in Figure 25, a stamp rally consists of a stamp rally node (stamp rally page), its members, and the stamp status. A rally has multiple members, and those connected by the owner (participant) and stamp relationship are stamped nodes. In the above example, a simple method of stamping by reading code 60 was explained, but by using the actions mentioned above, it is also possible to stamp based on various other conditions. In this way, since what is connected with "edge_type=stamp" is a "stamp," connecting this relationship results in "stamping." In this way, actions such as "marking something as stamped after answering a quiz" or "marking something as stamped after answering a specific questionnaire" are possible.

[0065] The processing of System 1 shown in Figure 22 presents a method for stamping in a stamp rally. In the example shown in Figure 10, etc., an edge was created for Code 60 with the relationship "remember," but in this processing, it is converted to "stamp." In other words, by replacing the edge, it is possible to create a new service.

[0066] Next, the operation of an administrator creating a control node will be described with reference to FIG. 26. A control node is a gateway node that can change the navigation destination depending on certain conditions. More specifically, a control node switches the page corresponding to the request command of the URL assigned to code 60 in accordance with predetermined conditions without changing the content of code 60. The administrator logs in to the management screen using the administrator terminal 30 ("(1) Display of management menu" in FIG. 26). This management screen is constructed by the management server 20, and the management screen transmitted from the management server 20 to the administrator terminal 30 is displayed on the display unit 34 of the administrator terminal 30. Next, on this management screen, the administrator moves to the "control node registration screen" using the administrator terminal 30 ("(2) Screen transition" in FIG. 26). This control node registration screen is also displayed on the display unit 34 of the administrator terminal 30. Then, on this control node screen, the administrator creates a control node using the administrator terminal 30 and stores it in the database 40 ("(3) Creation of control node" in FIG. 26). The control node does not have any function on its own, but acts as a gateway to transfer processing to each node. The control node can also be a code 60 such as a two-dimensional code. The operation of the control node is changed by the control data written in JSON in node_data and each node connected by edges.

[0067] Next, the administrator registers the guides, rallies, etc. that have already been registered as members of the control node on the control node registration screen ("(4) Member Registration" in Figure 26). The administrator registers the nodes to which processing is to be transferred as members based on the conditions. The administrator also describes the conditions for the control node in node_data in JSON on the control node registration screen ("(5) Condition Description" in Figure 26). Specifically, the conditions for transferring processing are described. Various conditions, such as time and date, can be described. The following example describes an example in which the guide switches depending on the time of day (morning, afternoon, or evening). The administrator can download the code 60 for the control node from the control node registration screen ("(6) Download Code" in Figure 26). The downloaded code 60 itself has no functionality, but it serves as a contact point. Therefore, since processing is transferred to another node based on the conditions, the operation of the management server 20 can, in principle, be automatically switched by conditional branching without changing the code 60 itself. In other words, in the past, the content of processing by the information processing means 24 changed depending on the type of node and the type of connection by the edge, so it was necessary to change the code 60, but in this embodiment, the control node can change the content of processing by the information processing means 24 without changing the code 60.

[0068] Next, using FIG. 27, an example will be described in which a control node switches the guide depending on the time of day (morning, afternoon, or evening). As shown in FIG. 27, nodes for "morning guide," "afternoon guide," and "evening guide" are created, and each node is connected to the control node by an edge called "member." This makes it possible to change the guide displayed on the display unit 14 of the user terminal 10 depending on the time of day. This makes it possible to prepare, for example, a "morning stamp rally," a "afternoon stamp rally," and a "evening stamp rally," and change the content of the stamp rally depending on the time of day (for example, it becomes possible for the guide to change to a "monster stamp rally" at night).

[0069] As described above, in this embodiment, the control node setting means 26 is configured to create a control node when it receives an instruction to create a control node from the administrator terminal 30. This allows the administrator to create a control node using the administrator terminal 30. The control node setting means 26 is also configured to set predetermined conditions for the control node in accordance with the contents of the predetermined conditions in the instruction to create a control node received from the administrator terminal 30. This allows the administrator to set the contents of the predetermined conditions for the control node using the administrator terminal 30. The control node setting means 26 may also be configured to modify the control node when it receives an instruction to modify the control node from the administrator terminal 30. This allows the administrator to modify the control node using the administrator terminal 30.

[0070] Next, the operation when the code 60 of the control node is read by the imaging unit 16 of the user terminal 10 will be described with reference to FIG. 28. When the code 60 of the control node is read by the imaging unit 16 of the user terminal 10 ("(1) Code Reading" in FIG. 28), a signal related to a URL request is sent from the user terminal 10 to the management server 20 based on the information of the read code 60 ("(2) URL Request" in FIG. 28). The information processing means 24 of the management server 20 searches the database 40 for the control node using the acquired node_key ("(3) Database Search" in FIG. 28). In this way, the information processing means 24 of the management server 20 acquires the control method of the control node and determines the redirect destination ("(4) Condition-Based Redirect" in FIG. 28). For example, if it is daytime, the daytime guide node is determined to be the redirect destination. Then, the transmitting means 25 of the management server 20 transmits a display instruction to the user terminal 10 to display the corresponding page on the display unit 14 of the user terminal 10 ("(5) Page display" in FIG. 28). In this way, the code 60 created as a control node does not have its own page, but rather serves as a gateway that redirects to subordinate pages according to conditions.

[0071] This type of operation will be explained in detail using Figure 29A. For example, if node_data is set to {"time":{"6-10":"Morning guide ID", "11-16":"Afternoon guide ID", "17-24,1-5":"Evening guide ID"}}, then the user will be navigated to the guide with the appropriate ID during that time period. In this way, the code 60 read (control node code 60) is the same, but depending on the conditions, the user will be redirected to a page managed by a different node. Note that while the example shown in Figure 29A shows the transfer of each guide to a node, any node can be set as the transfer destination as long as it is registered as a node, such as a stamp rally.

[0072] Next, a control node creation screen displayed on the display unit 34 of the administrator terminal 30 when the administrator creates a control node will be described with reference to FIG. 29B. The control node creation screen shown in FIG. 29B creates a control node that can control which node to delegate processing to depending on the specified time. Specifically, the creation screen shown in FIG. 29B creates a control node that redirects the navigation destination to "XX Morning Guide Page" when the control node code 60 is read by the imaging unit 16 of the user terminal 10 between midnight and 11:00, redirects the navigation destination to "XX Lunch Guide Page" when the control node code 60 is read by the imaging unit 16 of the user terminal 10 between 11:01 and 15:00, and redirects the navigation destination to "XX Evening Guide Page" when the control node code 60 is read by the imaging unit 16 of the user terminal 10 between 15:01 and 22:00. Furthermore, with regard to time control, if all conditions are not met, the default navigation destination is set to "XX Tourist Guide." In this way, if none of the conditions are met, the process can be delegated to the default. This characteristic can also be used to add the same process as the control node to other nodes. The node screen in Figure 29B displays a code 60, such as a two-dimensional code, of the control node to be created.

[0073] Because the parent control node (described later) can basically only control the control node, in order to have the same processing in other nodes, that processing (redirect processing) must be added to the other nodes as well (for example, if centralized control of stamp rally nodes is desired, redirect processing must also be added to the stamp rally nodes). In contrast, the control node of this embodiment can redirect to other nodes via the control node, so if a stamp rally is registered only as the default, it will always be redirected to the stamp rally only, and as a result, the same stamp rally will be displayed (in other words, the control node wraps other nodes). This technical feature removes the restriction that "the parent control node can only control the control node." Because the control of the parent control node can be limited to the control node only, changes can be kept to a minimum, the parent control node only needs to control the control node, and nodes other than the control node do not need to consider the parent control node. This simultaneously achieves the following effects: (1) there is no need to reprint the code 60 such as a two-dimensional code, and the content can be changed according to conditions; (2) centralized management is possible (the operation of subordinate nodes can be changed all at once by changing the mode); and (3) anything can be made the target of navigation without any modification, allowing for flexible switching of dynamic operations with minimal effort.

[0074] Next, the operation of an administrator creating a parent control node will be described with reference to FIG. 30. A parent control node manages multiple control nodes and, upon receiving a predetermined command, can change the operation of each control node collectively. The administrator logs in to the management screen using the administrator terminal 30 ("(1) Display of management menu" in FIG. 30). This management screen is constructed by the management server 20, and the management screen sent from the management server 20 to the administrator terminal 30 is displayed on the display unit 34 of the administrator terminal 30. Next, on this management screen, the administrator moves to the "control node registration screen" using the administrator terminal 30 ("(2) Screen transition" in FIG. 30). This control node registration screen is also displayed on the display unit 34 of the administrator terminal 30. Then, on this control node screen, the administrator creates a parent control node using the administrator terminal 30, registers a redirect destination, and saves it in the database 40 ("(3) Creation of parent control node" in FIG. 30). The administrator also registers the target control node using the administrator terminal 30 ("(4) Registration of control node" in FIG. 30). This makes it possible to change the control node transfer destination all at once in an emergency, for example.

[0075] FIG. 31 is an explanatory diagram showing a configuration in which a parent control node and a control node are connected by an edge. Although the parent control node does not use a code 60 such as a two-dimensional code, the control node's ability to change its behavior can be utilized to simultaneously change each control node to a specific behavior without changing the code 60. Specifically, an emergency URL for use in the event of a disaster is entered in the "emergency_url" field of the parent control node's node_data. Then, in the event of an emergency, when the administrator sends a command to the management server 20 via the administrator terminal 30 to set "emergency_flag" to "true," the "emergency_mode" field of the subordinate control nodes becomes "true." Therefore, reading the code 60 of any subordinate control node displays the URL (emergency URL for use in the event of a disaster) registered in "emergency_url" on the display unit 14 of the user terminal 10. Thus, once the code 60 of the control node is printed, its behavior can be changed as many times as necessary, eliminating the need to reprint the code 60. In addition, by using the parent control node to enable the operation to be replaced all at once in an emergency, it is possible to change all at once so that code 60 for utility pole advertisements that is normally used for advertisements will link to a disaster prevention page in an emergency.

[0076] FIG. 32 is a chart showing the operations of each terminal, the management server 20, and the database 40 when an emergency such as a disaster occurs. When an emergency such as a disaster occurs, the administrator logs in to the management screen using the administrator terminal 30 ("(1) Log in to management screen" in FIG. 32). This management screen is constructed by the management server 20, and the management screen transmitted from the management server 20 to the administrator terminal 30 is displayed on the display unit 34 of the administrator terminal 30. Next, using this management screen, the administrator moves to the "control node management screen" using the administrator terminal 30. This control node management screen is also displayed on the display unit 34 of the administrator terminal 30. Then, using this control node management screen, the administrator changes the emergency_flag of the parent control node from "false" to "true" using the administrator terminal 30 ("(2) Set emergency_flag=true" in FIG. 32). As a result, the emergency_mode of all control nodes connected to the parent control node becomes true ("(3) Automatically update subordinate nodes" in FIG. 32).

[0077] Thereafter, when the image capturing unit 16 of the user terminal 10 reads the code 60 of the control node attached to an object such as an advertisement 64 wrapped around a utility pole 62 or a medium 66 ("(4) Read code" in FIG. 32), a signal requesting the URL of the control node is sent from the user terminal 10 to the management server 20 based on the information of the read code 60 ("(5) To URL of control node" in FIG. 32). This allows access to the management server 20. The information processing means 24 of the management server 20 searches the database 40 for the control node ("(6) Search database for control node" in FIG. 32) and acquires data of the control node ("(7) Acquire control node" in FIG. 32). Here, as described above, since the emergency_mode of the control node is true, the information processing means 24 of the management server 20 further traces back to the parent to search for the parent control node ("(8) Get parent because emergency_mode is true" in Figure 32), and obtains the data of the parent control node ("(9) Get parent control node" in Figure 32).

[0078] Then, the information processing means 24 of the management server 20 redirects to the emergency URL in emergency_url and sends a display instruction to the user terminal 10 to display the website of the redirected URL on the display unit 14 of the user terminal 10 ("(10) Redirect to emergency URL in emergency_url" in FIG. 32). As a result, the website of the emergency URL will be displayed on the user terminal 10 regardless of which control node's code 60 is read.

[0079] After that, when the emergency is no longer present, the administrator changes emergency_flag from "true" to "false" on the control node management screen using the administrator terminal 30 ("(11) Set emergency_flag=false" in FIG. 32). As a result, emergency_mode of all control nodes connected to the parent control node becomes false ("(12) Automatically update subordinate nodes" in FIG. 32).

[0080] Thereafter, when the image capturing unit 16 of the user terminal 10 reads the code 60 of the control node attached to an object such as an advertisement 64 wrapped around a utility pole 62 or a medium 66 ("(13) Read code" in FIG. 32), a signal requesting the URL of the control node is sent from the user terminal 10 to the management server 20 based on the information of the read code 60 ("(14) To URL of control node" in FIG. 32). This allows access to the management server 20. The information processing means 24 of the management server 20 searches the database 40 for the control node and acquires the data of the control node. Here, because the emergency_mode of the control node has been returned to false as described above, the access is redirected to the URL of the normal conditional branch of the control node ("(15) Redirect to URL of normal conditional branch" in FIG. 32).

[0081] This operation will be described in detail with reference to FIG. 33A. As described above, the parent control node is a control node that centrally manages multiple control nodes. For example, control node codes 60 are affixed to utility poles in various locations, and various uses such as advertising and stamp rallies can be created so that they can be switched depending on various conditions. In this case, the control node may also serve as a timely guide. In the event of an emergency such as a disaster, by setting the emergency_flag of the parent control node to true, the emergency_mode of the mode_data of the subordinate control nodes connected to the parent control node is saved as true. A control node whose emergency_mode is set to true traces the parent control node's links in reverse, obtains its emergency_url, and redirects to that URL. This allows codes 60, such as two-dimensional codes for advertising, that are normally used for various purposes to be simultaneously changed in the event of an emergency. Furthermore, when the emergency is no longer present, it is sufficient to simply set the emergency_flag of the parent control node to false. This causes the emergency_mode of the subordinates connected to the parent control node to become false, and the node returns to its normal role as a control node with code 60.

[0082] Furthermore, in this embodiment, when a parent control node controls a control node, it is possible to flexibly perform centralized management using weighting and categories. Such an operation will be described with reference to Fig. 33B.

[0083] As shown in FIG. 33B, in this embodiment, when a parent control node controls a control node, it can assign weights (weight) and categorize (edge_category) to edges. For example, when a parent control node controls a control node, if the application of centralized control is limited to nodes with a weight of 1, only nodes connected to edges with a weight of 1 are affected by the change, while others remain unchanged. Furthermore, the redirect destination can be changed for each weight. Multiple navigation destinations can be registered based on the level or purpose, such as "for example, if a connection is made with a weight of 1, navigate to a destination with a weight of 1." (Note that if emergency_mode='all' is specified, the behavior of all control nodes under the parent control node can be changed.) In this way, by assigning weights (weight) and categorizing (edge_category) to edges, it is possible to precisely control "what node," "in what circumstances," and "to which page" a control node is redirected, thereby diversifying the uses of control nodes.

[0084] FIG. 33C is a chart showing the operation of the system when an administrator creates a weighted centralized control node. FIG. 33D is an explanatory diagram showing the connection between control nodes and edges when an administrator creates a weighted centralized control node. FIG. 33E is an explanatory diagram showing the connection between control nodes, edges, and nodes when an administrator creates a weighted centralized control node. The administrator logs in to the management screen using the administrator terminal 30 ("(1) Display of management menu" in FIG. 33C). This management screen is constructed by the management server 20, and the management screen transmitted from the management server 20 to the administrator terminal 30 is displayed on the display unit 34 of the administrator terminal 30. Next, on this management screen, the administrator moves to the "control node registration screen" using the administrator terminal 30 ("(2) Screen transition" in FIG. 33C). This control node registration screen is also displayed on the display unit 34 of the administrator terminal 30. Then, on this control node screen, the administrator creates a parent control node on the administrator terminal 30, registers a redirect destination, and stores the results in the database 40 ("(3) Creation of control node" in FIG. 33C). Next, the administrator registers the target control node on the control node registration screen ("(4) Register control node" in Figure 33C). This type of control node registration is repeated for each weight. The administrator also registers the target redirect destination on the control node registration screen ("(5) Register redirect destination" in Figure 33C). This type of redirect destination registration is repeated for each weight.

[0085] The administrator also registers members on the administrator terminal 30 in a similar manner, but registers different members according to their weights. Next, a redirect destination is registered for each member. There is one redirect destination for each weight. The members registered for each weight converge to one redirect destination (see Figure 33D). Furthermore, similar weighted members are added to the redirect edge of the parent control node (see Figure 33E). Note that this does not have to be added to the control node; it can also be added to a node that directly links to a URL. If the parent control node's emergency_flag is set to 1, only members with a value of 1 are written with emergency_mode set to 1 along with the parent control node's ID. The control node under the parent control node queries the parent control node based on the given weight and the parent control node's ID. The parent control node, upon receiving the query, follows the redirect edge connected by the target weight and delegates processing to that node. After that, the screen or app responsible for the node to which processing has been delegated will be displayed. If emergency_flag is set to all, all nodes are targeted. Each node will be delegated processing to the redirect destination with the same weight as the connected node, and as a result, it will be possible to change the processing of multiple nodes simultaneously with one centralized control. The same is true when using edge_category, and you can set the target to only a specific weight of a specific category or to the whole at once. If the category has a weight of 1 and 1, it will be 1.1, if all weights are 1, it will be 1.all, if all categories have a weight of 1, it will be all.1, and if all are all, it will be all.all, or all for short.

[0086] FIG. 33F is a chart showing the operation of the system when an emergency such as a disaster occurs due to the weighted centralized control node. When an emergency such as a disaster occurs, the administrator logs in to the management screen using the administrator terminal 30 ("(1) Log in to management screen" in FIG. 33F). This management screen is constructed by the management server 20, and the management screen transmitted from the management server 20 to the administrator terminal 30 is displayed on the display unit 34 of the administrator terminal 30. Next, using this management screen, the administrator moves to the "control node management screen" using the administrator terminal 30. This control node management screen is also displayed on the display unit 34 of the administrator terminal 30. Then, using this control node management screen, the administrator changes the emergency_flag of the parent control node from "false" to "true" using the administrator terminal 30 ("(2) Set emergency_flag=true" in FIG. 33F). As a result, the emergency_mode of all control nodes connected to the parent control node becomes true ("(3) Automatically update subordinate nodes" in FIG. 33F).

[0087] Thereafter, when the image capturing unit 16 of the user terminal 10 reads the code 60 of the control node attached to an object such as an advertisement 64 wrapped around a utility pole 62 or a medium 66 ("(4) Read code" in FIG. 33F), a signal requesting the URL of the control node is sent from the user terminal 10 to the management server 20 based on the information of the read code 60 ("(5) To URL of control node" in FIG. 33F). This allows access to the management server 20. The information processing means 24 of the management server 20 searches the database 40 for the control node ("(6) Search database for control node" in FIG. 33F) and acquires data of the control node ("(7) Acquire control node" in FIG. 33F). Here, as described above, since the emergency_mode of the control node is true, the information processing means 24 of the management server 20 further traces back to the parent to search for the parent control node ("(8) Get parent because emergency_mode is true" in Figure 33F), and obtains the data of the parent control node ("(9) Get parent control node" in Figure 33F).

[0088] Next, the information processing means 24 of the management server 20 searches for a node to which the redirect edge is connected based on the weight. Specifically, the information processing means 24 of the management server 20 searches for a redirect destination node connected with a weight of 1 ("(10) Search for a node to which the redirect edge is connected based on the weight" in FIG. 33F). Then, the management server 20 executes processing of that node. For example, if it is a URL node, it redirects to that URL and sends a display instruction to the user terminal 10 to display the website of the redirected URL on the display unit 14 of the user terminal 10 ("(11) Execute processing of that node" in FIG. 33F). As a result, regardless of which control node's code 60 is read, the emergency URL website will be displayed on the user terminal 10.

[0089] After that, when the emergency is no longer present, the administrator changes emergency_flag from "true" to "false" on the control node management screen using the administrator terminal 30 ("(12) Set emergency_flag=0" in Figure 33F). Then, the target is identified from the original weight, and the subordinate nodes are automatically updated. In other words, emergency_mode is set to 0 or empty ("(13) Identify the target from the original weight, and automatically update the subordinate nodes" in Figure 33F).

[0090] When the image capturing unit 16 of the user terminal 10 reads the code 60 of the control node attached to an object such as an advertisement 64 wrapped around a utility pole 62 or a medium 66 ("(14) Read code" in Figure 33F), a signal requesting the URL of the control node is sent from the user terminal 10 to the management server 20 based on the information of the read code 60 ("(15) To URL of control node" in Figure 33F). This allows access to the management server 20. The information processing means 24 of the management server 20 searches the database 40 for the control node and acquires the data of the control node. Here, because the emergency_mode of the control node has been returned to false as described above, the access is redirected to the URL of the normal conditional branch of the control node ("(16) Redirect to URL of normal conditional branch" in Figure 33F).

[0091] Next, the operation of an action (point allocation) using a code 60 such as a two-dimensional code will be described with reference to Fig. 34. As mentioned above, Fig. 8 is a table showing the settings for actions. The definition of an action is defined in action_data, and in this embodiment, for example, distribution of points or distribution of coupons is defined as an action.

[0092] When a code 60 attached to an object such as an advertisement 64 wrapped around a utility pole 62 or a medium 66 is read by the imaging unit 16 of the user terminal 10 ("(1) Code reading" in FIG. 34), a signal related to a URL request is transmitted from the user terminal 10 to the management server 20 based on the information in the read code 60 ("(2) URL request" in FIG. 34). Here, the information in the code 60 read by the user terminal 10 is URL information such as "○○-memory.jp / actions / {action_key}", and a command is transmitted from the user terminal 10 to the management server 20 requesting a URL for awarding points from the management server 20 in accordance with the URL in the read code 60.

[0093] When the information receiving means 23 of the management server 20 receives a signal related to a URL request from the user terminal 10, the transmitting means 25 of the management server 20 sends a database search command to the database 40 according to the action_key acquired from the URL ("(3) Database Search" in FIG. 34). Then, based on this action_key, action information is acquired from the database 40 ("(4) Search Result Response" in FIG. 34). Then, if the action_data is {point1:100}, for example, points are assigned to the corresponding field of the acquired owner ("(5) Action Execution" in FIG. 34). The transmitting means 25 sends a display instruction signal to the user terminal 10 to display the point assignment information on the display unit 14 of the user terminal 10 ("(6) Result Display" in FIG. 34).

[0094] In the processing example shown in Figure 34, we have explained the most basic action definition, which is the distribution of points by reading code 60. We have presented the actions of "read code 60" and "distribute points" as the simplest actions, but because actions are data in database 40 that have independent entities, the action of "reading code 60" can be replaced with another action.

[0095] In the above example, a code 60, such as a two-dimensional code, is scanned by the imaging unit 16 of the user terminal 10 to award points to the user who owns the user terminal 10. However, message exchange between different services is also possible. An example of this is described using Figure 35. By defining the actual action of "point distribution," a similar mechanism can be implemented for other actions, not just code 60. Because the actions themselves are independent, the triggering events can be freely defined. For example, an action can be triggered by "registering for an event" or "collecting a stamp in a stamp rally," and points can be awarded. Furthermore, while the above example uses point distribution, connecting edges instead of point distribution is also possible. Each service can be defined in a simple format, such as connecting edges between nodes. Defining actions in this way enables various services to be linked using only actions, without additional development.

[0096] Next, the operation of an action (title assignment) using a code 60 such as a two-dimensional code will be described with reference to Figure 36. When the image capture unit 16 of the user terminal 10 reads the code 60 attached to an object such as an advertisement 64 wrapped around a utility pole 62 or a medium 66 ("(1) Code Reading" in Figure 36), a signal related to a URL request is transmitted from the user terminal 10 to the management server 20 based on the information of the read code 60 ("(2) URL Request" in Figure 36). Here, the information of the code 60 read by the user terminal 10 is URL information such as "xx-memory.jp / actions / {action_key}", and a command is transmitted from the user terminal 10 to the management server 20 requesting a URL for title assignment from the management server 20 according to the URL of the read code 60.

[0097] When the information receiving means 23 of the management server 20 receives a signal related to a URL request from the user terminal 10, the transmission means 25 of the management server 20 sends a database search command to the database 40 according to the action_key acquired from the URL ("(3) Database Search" in FIG. 36). Then, based on this action_key, action information is acquired from the database 40 ("(4) Search Result Response" in FIG. 36). Then, if the action_data is {medal:300}, for example, a title node is assigned to the corresponding field of the acquired owner ("(5) Action Execution" in FIG. 36). The transmission means 25 sends a display instruction signal to the user terminal 10 to display information such as the assigned title on the display unit 14 of the user terminal 10 ("(6) Result Display" in FIG. 36).

[0098] More specifically, as shown in Figure 37, all relationships between nodes are treated as tangible edge data. Titles are assigned by connecting the title node and the owner node with an edge. In this case, an action is initiated by reading a two-dimensional code (e.g., code 60), and the title node is assigned to the owner, defining the acquisition of the title. In this way, edges are indirectly connected by actions triggered by some kind of trigger, enabling the bridging of completely different services, both real and virtual, such as reading a two-dimensional code (e.g., code 60) or completing a stamp rally. For example, the stamp rally function is contained within the stamp rally, but the stamps can be freely defined externally. Specifically, by creating a process for reading a code 60 and "stamping (connecting with an edge)," the triggering action can be expanded beyond reading the code 60. For example, by triggering an action to "connect a specific stamp rally edge" within the action "registering for an event," a stamp from the stamp rally can be stamped.

[0099] In the processing example shown in FIG. 35, a "function that can create edges" is presented as "title assignment" as a mechanism with a wide range of application for actions. Since system 1 of this embodiment is entirely built on the relationship between nodes and edges, the ability to create edges makes it possible to link with other services beyond the scope of each service. In the above example, it is "reading code 60," but if actions are defined to be driven as the results of various services such as "completing a stamp rally," "answering a quiz correctly," or "registering for an event," other operations can be created beyond the scope of the service.

[0100] Next, the operation when a user participates in multiple stamp rallies consecutively using the user terminal 10 will be described with reference to FIG.

[0101] When the stamp rally code 60 is read by the imaging unit 16 of the user terminal 10 ("(1) Code reading" in FIG. 38), a signal for a URL request is sent from the user terminal 10 to the management server 20 based on the information in the read code 60 ("(2) URL request" in FIG. 38). This causes access to the management server 20. The stamp rally URL is, for example, "○○-memory.jp / stamps / {encrypted value of edge_id}". The information processing means 24 of the management server 20 decrypts the encrypted value and acquires the edge_id.

[0102] The information processing means 24 of the management server 20 searches for edges in the database 40 based on the decrypted edge_id ("(3) Search database based on decrypted edge_id" in Figure 38). The relationships represented by edges are also entities that have attributes, since they are data in the database 40. In this embodiment, a member edge is searched for. The member edge contains the stamp rally sheet ID (node_id1) and the location ID (node_id2). In other words, edges contains information on "which stamp rally" and "which location" the stamp was taken at. In this way, the database 40 is searched for a corresponding record of edges based on the decrypted edge_id, and if a corresponding record is found, the respective nodes are obtained from the corresponding node_id1 (rally ID) and node_id2 (location ID), and the search results are returned to the management server 20.

[0103] Next, the information processing means 24 of the management server 20 checks the database 40 to see if the code 60 captured by the imaging unit 16 of the user terminal 10 during the stamp rally has already been stamped. Specifically, a search is performed using edge_type=stamp, with root_node_id being the stamp rally ID, node_id1 being the owner node ID, and node_id2 being the location ID. If this is the first time that a stamp has been applied to the code 60 captured by the imaging unit 16 of the user terminal 10 during the stamp rally, an edge is created with root_node_id being the stamp rally ID, node_id1 being the owner node ID, node_id2 being the location ID, and edge_type=stamp (specifically, an edge saying "stamped" is created). This clarifies "who (node_id1)," "which stamp rally (root_node_id)," "which location (node_id2)," and "who stamped (edge_type=stamp)," and this information is stored in the database 40 ("(5) Stamping" in FIG. 38). Furthermore, the information processing means 24 of the management server 20 acquires the number of connected stamp edges ("(6) Acquire number of stamps" in FIG. 38).

[0104] In the aspect shown in Figure 38, the information processing means 24 of the management server 20 determines whether the number of connected stamp edges has reached a predetermined complete number (complete_num of node_data) ("(7) Return result and determine" in Figure 38). If the number of connected stamp edges has reached the predetermined complete number, it is determined that the stamp rally has been completed, and the information processing means 24 of the management server 20 searches for action data from the database 40 based on the ID of the action that has been set ("(8) Search for action set to complete" in Figure 38). Then, when the information processing means 24 of the management server 20 acquires the action data, it analyzes the contents of this action data. In the aspect shown in Figure 38, action_data is {"unlock": ID of new stamp rally} ("(9) Acquire action" in Figure 38).

[0105] Thereafter, the information processing means 24 of the management server 20 executes the action based on the action definition. At this time, an edge with node_id1:owner, node_id2:ID of the new stamp rally, and edge_type:unlock is created ("(10) Execute action (unlock new rally)" in FIG. 38). In this way, a new stamp rally begins after a previous stamp rally is completed. Then, the results are returned to the user terminal 10 from the stamp rally screen ("(11) Return result" in FIG. 38). Specifically, a display instruction is sent to the user terminal 10 to display the message "A new stamp rally has been unlocked!" on the display unit 14 of the user terminal 10.

[0106] The processing example shown in Figure 38 is one application of actions, where a series of stamp rallies is carried out. When an action is triggered upon completion of a certain stamp rally, other stamp rallies can be unlocked. Note that the node publish is changed so that other stamp rallies cannot be started unless the lock is released. This makes it easy to create services such as those that allow a new stamp rally to be started when certain conditions are met. Because actions can create edges, it is possible to add various operations across multiple services later.

[0107] According to the system 1 and information processing method of the present embodiment configured as described above, when the code 60 attached to an object is read by the imaging unit 16 of the user terminal 10, a request command for the URL assigned to the code 60 is transmitted from the user terminal 10 to the management server 20 (computer). Upon receiving the URL request command from the user terminal 10, the management server 20 transmits a database search command to a database 40 storing information about website pages. Based on the search results returned from the database 40 in response to the transmitted database search command, the management server 20 displays the website page corresponding to the URL request command on the display unit 14 of the user terminal 10. A control node is also provided for switching the page corresponding to the URL request command assigned to the code 60 in accordance with predetermined conditions without changing the code 60. According to the system 1 and information processing method described above, the operation of the management server 20 can be automatically switched by conditional branching without changing the code 60 itself, in principle. In other words, in the past, the content of processing by the information processing means 24 changed depending on the type of node and the type of connection by the edge, so it was necessary to change the code 60, but in this embodiment, the control node can change the content of processing by the information processing means 24 without changing the code 60.

[0108] Furthermore, in the system 1 and information processing method of this embodiment, as described above, the control node setting means 26 is configured to create a control node upon receiving an instruction to create a control node from the administrator terminal 30. This allows the administrator to create a control node using the administrator terminal 30.

[0109] Furthermore, in the system 1 and information processing method of this embodiment, as described above, the control node setting means 26 sets the predetermined conditions in the control node in accordance with the contents of the predetermined conditions in the control node creation instruction received from the administrator terminal 30. This allows the administrator to set the contents of the predetermined conditions in the control node using the administrator terminal 30.

[0110] Furthermore, in the system 1 and information processing method of this embodiment, as described above, the control node setting means 26 modifies the control node upon receiving an instruction to modify the control node from the administrator terminal 30. This allows the administrator to modify the control node using the administrator terminal 30.

[0111] Furthermore, as described above, the system 1 and information processing method of this embodiment further include a parent control node that manages multiple control nodes, and the parent control node is configured to change the operation of each control node collectively when the management server 20 (computer) receives a predetermined command. This allows each control node to be collectively converted to a certain predetermined operation without changing the code 60. Specifically, for example, by allowing the parent control node to collectively replace the operation in an emergency, it becomes possible to simultaneously change the code 60 for utility pole advertisements that are normally used for advertisements to a disaster prevention page in an emergency.

[0112] Furthermore, in the system 1 and information processing method of this embodiment, as described above, the parent control node setting means 27 creates a parent control node upon receiving an instruction to create a parent control node from the administrator terminal 30. This allows the administrator to create a parent control node using the administrator terminal 30.

[0113] Furthermore, in the system 1 and information processing method of this embodiment, as described above, when the management server 20 (computer) receives a predetermined command, the parent control node collectively changes the operation of each control node so that the page corresponding to the request command of the URL assigned to the code 60 becomes the predetermined page. This allows each control node to be collectively converted to a certain predetermined operation without changing the code 60.

[0114] The system and information processing method according to the present invention are not limited to the above-described aspects, and various modifications can be made.

[0115] For example, in the event of an emergency such as a disaster, instead of the administrator changing the emergency_flag of the parent control node from "false" to "true" on the control node management screen using the administrator terminal 30, emergency information may be transmitted from an external weather information providing server or earthquake information providing server that is API-linked to the management server 20 of the system 1 of this embodiment, and the information receiving means 23 may receive such emergency information, causing the information processing means 24 to change the emergency_flag of the parent control node from "false" to "true." In this case, even if the administrator is unable to respond in the event of an emergency such as a disaster, it becomes possible to simultaneously change the behavior of codes 60, such as two-dimensional codes for advertising that are normally used for various purposes, in the event of an emergency. [Explanation of symbols]

[0116] 1 System 10 User terminal 11 Bus 12 Control Unit 14 Display section 15 Control section 16 Imaging unit 17 Memory section 18 Communications Department 20 Management Server 22 Control Unit 23 Information Reception Method 24 Information Processing Means 25 Transmission Method 26 Control node setting method 27 Parent control node setting method 28 Memory section 29 Communications Department 30 Administrator terminal 32 Control section 33 Display section 34 Display section 35 Control section 36 Printing section 37 Memory section 38 Communications Department 40 databases 50 Communication Network 60 Code 62 Electric pole 64 Advertisements 66 Medium

Claims

1. an object having a code attached thereto that can be read by an imaging unit of a user terminal; A computer, A system comprising: When the code attached to the object is read by the imaging unit of the user terminal, a request command for a URL assigned to the code is transmitted from the user terminal to the computer, When the computer receives a URL request command from the user terminal, it sends a database search command to a database in which information about a website page is stored, and displays the website page corresponding to the URL request command on a display unit of the user terminal based on the search results returned from the database in response to the sent database search command; The system is provided with a control node for switching the page corresponding to the request command of the URL assigned to the code in accordance with a predetermined condition without changing the code.

2. The system according to claim 1 , wherein the computer creates a control node upon receiving an instruction to create a control node from an administrator terminal.

3. 3. The system according to claim 2, wherein the computer sets the predetermined conditions in the control node in accordance with the contents of the predetermined conditions in the control node creation instruction received from the administrator terminal.

4. 3. The system according to claim 2, wherein said computer modifies the control node when receiving an instruction to modify the control node from an administrator terminal.

5. a parent control node that manages the plurality of control nodes is further provided; 2. The system according to claim 1, wherein the parent control node is capable of collectively changing the operation of each control node when said computer receives a predetermined command.

6. 6. The system according to claim 5, wherein the computer creates a parent control node upon receiving an instruction to create a parent control node from an administrator terminal.

7. The system of claim 5, wherein when the computer receives a specified command, the parent control node collectively changes the operation of each control node so that the page corresponding to the request command of the URL assigned to the code becomes the specified page.

8. An information processing method using a system including an object having a code attached thereto that can be read by an imaging unit of a user terminal, and a computer, comprising: When the code attached to the object is read by the imaging unit of the user terminal, a request command for a URL assigned to the code is transmitted from the user terminal to the computer, a step in which the computer transmits a database search command to a database storing information about a website page when receiving a URL request command from the user terminal, and displays the website page corresponding to the URL request command on a display unit of the user terminal based on search results returned from the database in response to the transmitted database search command; a step of the computer switching, by a control node, a page corresponding to a request command of a URL assigned to the code in accordance with a predetermined condition without changing the code; An information processing method comprising:

Images