Context matching related information processing system and information processing method

Abstract

To allow a user on a receiving or transmitting side to receive or provide service information even when the user does not perform any special operation, if a preset situation is established in a communication area.SOLUTION: The present invention is used in a system that broadcasts a packet consisting of a header area including communication standard data and a user area in which a device ID being used and context data can be written, as a beacon signal. When the beacon signal is received and detection data is obtained indicating that the received data in the user area has a correspondence relationship with context data set by its own device, service information corresponding to the context data is output. A system includes an output unit for this service information.SELECTED DRAWING: Figure 2A

Description

[Technical Field]

[0001] The present invention relates to a context matching related information processing system and information processing method, and also relates to an information processing device, a receiving method, a transmitting method, a server, and the like. [Background technology]

[0002] Generally, there are several ways for a user to obtain some service information using a communication system: The user uses a personal computer (hereinafter referred to as a PC) or a mobile terminal (for example, a smartphone (hereinafter referred to as a smartphone)) to input search information or a uniform resource locator (URL) according to their needs, or clicks on a commercial screen displayed on the screen, establishing a communication environment with the corresponding server. The server then provides the service information to the PC or smartphone.

[0003] In this way, the method by which users obtain some service information is by operating a PC or smartphone according to their "needs," actively accessing a server, and obtaining the service information provided by the server. Because this method is initiated by the user, it will be referred to as the "user-initiated" method below.

[0004] There are special cases where service information can be obtained without using the "user-initiated" method described above. One such special case is when a specific organization (such as a public specialized organization like the Japan Meteorological Agency) issues an "emergency notification" simultaneously when an earthquake or other event occurs. With this method, the recipients (users) are not identified, and all users simultaneously receive the information on their smartphones. Providing this type of information is meaningful to users. On the other hand, there are also communication systems that send various types of service information (such as commercials that users do not intend to receive) to users' smartphones or PCs, and these communication systems often provide users with service information that they are not interested in.

[0005] As mentioned above, many conventional service information provision systems are based on a "user-driven" approach, providing service information in response to specific "needs" or "requests" from users. Furthermore, systems that adopt a "user-driven" approach provide service information only when the user presents a "need" or "request" that they are explicitly aware of. For this reason, conventional service information provision systems can be said to have a small number of opportunities to provide service information. Furthermore, service information provision systems that are not "user-driven," such as "earthquake early warning" systems, are limited to special cases and have limited flexibility. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent No. 6715501 [Patent Document 2] Patent Publication No. 2021-64394 [Patent Document 3] Patent Publication No. 2021-111164 [Patent Document 4] Japanese Patent Publication No. 2021-119488 Summary of the Invention [Problem to be solved by the invention]

[0007] Here, the inventors of the present invention have noticed that opportunities to provide a user with service information that responds to the user's "needs" or "requests," or for the user to receive service information, often arise even at times when the user is not explicitly aware of their "needs" or "requests."

[0008] This occurs when a combination of multiple states of multiple users or objects occurs in the vicinity, and this combination of multiple states is referred to here as a "situation." Note that a situation may also be referred to as an "environment," "atmosphere," "context scheme rule setting," or simply a "rule setting."

[0009] Furthermore, there are various "multiple states" depending on the purpose of the service. Typical examples of states are as follows: - A situation where multiple users have common goals - A state in which a specific object is in close proximity to the user - The user receiving the service and the user providing the service are in close proximity to each other - A state where a certain number of objects or users are gathered ·others.

[0010] Therefore, the present invention has devised a completely new method, device, and system that can provide or receive service information not in a "user-driven" manner but in a manner that is driven by a situation or situation rule (hereinafter, tentatively referred to as a "situation-driven" or "situation rule-driven" method).

[0011] In a first aspect of the embodiment, the object is to provide a context matching related information processing system that allows a user to receive at least service information or provide service information based on a situation rule. [Means for solving the problem]

[0012] According to one embodiment, a first information processor registers a first context in a context determination unit, and a second information processor registers a second context in the context determination unit, and the first information processor and the second information processor communicate with each other through beacon packets and include a determination unit that determines context-related information included in the beacon packets.

[0013] According to one embodiment, a first information processor that registers a first context in a context determination unit provided in the server; , a second information processor that registers a second context in the context determination unit; the first information processor and the second information processor perform beacon communication with each other; When the first context and the second context include a common word, which indicates a matching relationship, the first information processor includes a first processor that outputs result data indicating the matching relationship to another information processor as node notification data for providing a coupon; the second information processor comprises a second processor that receives the node notification data and processes the node notification data as a coupon; The first information processor counts the IDs of the second information processor and the other information processor with which the matching relationship has been established, and calculates the number of counted IDs (number of devices). The server means for transmitting to the server includes means for notifying the first information processor of the number of coupons to be issued based on the node notification data; Furthermore, the context determination unit forms group data including IDs of the first information processor and the second information processor in a group of contexts in the matching relationship at the time of the registration, The first information processor receives the group data from the context determination unit of the server in advance, and the determination of the matching relationship in the beacon communication is performed within the first information processor. An information processing system is provided, characterized in that:

[0014] According to another embodiment, the context may be pre-coded. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of an advertisement packet (beacon packet) in a common format used by an information processor including a beacon device according to an embodiment. [Figure 2A] FIG. 2A is a diagram showing an example of a configuration according to an embodiment. [Figure 2B] FIG. 2B is a diagram showing another configuration example of the embodiment. [Figure 2C] FIG. 2C is a flowchart showing an operation example of the embodiment. [Figure 2D] FIG. 2D is a diagram showing another configuration example of the embodiment. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of an embodiment in which various setting functions are further added to the embodiment of FIGS. 2A and 2B. [Figure 4A] FIG. 4A is a diagram showing an example of the external configuration of an agent used in the embodiment. [Figure 4B] FIG. 4B is a diagram showing another example of the external configuration of an agent used in the embodiment. [Figure 4C] FIG. 4C is a diagram showing yet another example of the external configuration of an agent used in the embodiment. [Figure 4D] FIG. 4D is a diagram showing an example of internal functional blocks of an agent. [Figure 5A] FIG. 5A is a diagram showing an example of the external configuration of a node used in the embodiment. [Figure 5B] FIG. 5B is a diagram showing yet another example of the external configuration of a node used in the embodiment. [Figure 5C] FIG. 5C is a diagram showing yet another example of the external configuration of a node used in the embodiment. [Figure 5D] FIG. 5D is a diagram showing yet another example of the external configuration of a node used in the embodiment. [Figure 5E] FIG. 5E is a diagram showing yet another example of the external configuration of a node used in the embodiment. [Figure 6A] FIG. 6A is a diagram showing an example of the functional configuration of the node shown in FIGS. 2A and 2B. [Figure 6B] 6B is a diagram showing another example of the functional configuration of the node shown in FIGS. 2A and 2B. FIG. [Figure 6C] FIG. 6C is a diagram showing another example of the functional configuration of the node shown in FIGS. 2A and 2B. [Figure 6D] FIG. 6D is a diagram showing another example of the functional configuration of the node shown in FIGS. 2A and 2B. [Figure 7A] FIG. 7A is an explanatory diagram showing an embodiment in which the basic system of the present invention is used for a product sales promotion system in the context area 20. FIG. [Figure 7B] FIG. 7B is an explanatory diagram showing an example of system operation when the basic system of the present invention is used for a product sales promotion system in the context area 20. [Figure 8A] FIG. 8A is an explanatory diagram showing an embodiment in which the basic system of the present invention is used for a child monitoring system. [Figure 8B] FIG. 8B is an explanatory diagram showing an example of system operation when the basic system of the present invention is used for a child monitoring system. [Figure 9A] FIG. 9A is an explanatory diagram showing an embodiment in which the basic system of the present invention is used for an elderly care and guidance system. [Figure 9B] FIG. 9B is an explanatory diagram showing an example of system operation when the basic system of the present invention is used for an elderly person monitoring and guidance system. [Figure 10A] FIG. 10A is an explanatory diagram showing an embodiment in which the basic system of the present invention is used in an encounter detection system. [Figure 10B] FIG. 10B is an explanatory diagram showing the procedure for a user to set prologue information when the basic system of the present invention is used in an encounter detection system. [Figure 10C] FIG. 10C is an explanatory diagram illustrating an example of system operation when the basic system of the present invention is used in an encounter detection system. [Figure 11] FIG. 11 is an explanatory diagram showing an embodiment in which the basic system of the present invention is used in a building management system. [Figure 12A] FIG. 12A is an explanatory diagram showing an embodiment in which the basic system of the present invention is applied to a spatial environment detection system. [Figure 12B] 12B is a diagram showing an example of the configuration of a node used in the embodiment of FIG. 12A. [Figure 13] FIG. 13 is an explanatory diagram showing an embodiment in which the basic system of the present invention is applied to a meeting detection system and / or a customer flow line system. [Figure 14] FIG. 14 is an explanatory diagram showing an example of the data structure of a beacon packet used in an embodiment of the present invention. [Figure 15] FIG. 15 is a diagram showing an embodiment in which the basic system of the present invention is further combined with the ifLink (registered trademark) system. [Figure 16] Figure 16 is a diagram for explaining an overview of the ifLink system. [Figure 17] FIG. 17 is a diagram showing an example of the configuration of an IF-THEN rule. [Figure 18] FIG. 18 is a diagram showing an example of the configuration of a frame type shown in FIG. [Figure 19] 19 is a diagram showing an example of setting values ​​of the frame type in FIG. 18. [Figure 20] FIG. 20 is a diagram showing an example of schema information according to the embodiment. [Figure 21] FIG. 21 is a diagram showing an example of the configuration of a parameter field in a beacon packet for notifying a sensor value. [Figure 22] FIG. 22 is a configuration diagram illustrating the basic configuration of one embodiment. [Figure 23] FIG. 23 is a configuration diagram showing the basic configuration of another embodiment. [Figure 24] FIG. 24 is a configuration diagram showing the basic configuration of another embodiment. [Figure 25] FIG. 25 is a configuration diagram showing the basic configuration of another embodiment. [Figure 26] FIG. 26 is a configuration diagram showing the basic configuration of another embodiment. [Figure 27] FIG. 27 is a configuration diagram showing the basic configuration of another embodiment. [Figure 28] FIG. 28 is a configuration diagram showing the basic configuration of another embodiment. [Figure 29] FIG. 29 is a configuration diagram showing the basic configuration of another embodiment. [Figure 30] FIG. 30 is a configuration diagram showing the basic configuration of another embodiment. [Figure 31] FIG. 31 is a configuration diagram showing the basic configuration of another embodiment. [Figure 32] FIG. 32 is a configuration diagram showing the basic configuration of another embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] The following describes embodiments with reference to the drawings. Several embodiments of the present invention will be described. However, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as set forth in the claims. Furthermore, the scope of the present invention also includes cases in which each component in the claims is expressed separately, as a combination of multiple components, or as a combination of these. Furthermore, multiple embodiments may be combined, and examples composed of such combinations are also within the scope of the invention.

[0017] In addition, to clarify the description, the drawings may show the width, thickness, shape, etc. of each part more schematically than in the actual embodiment. Furthermore, the device of the present invention is applied even when the claims are expressed as control logic, as a program including instructions for causing a computer to execute, or as a computer-readable recording medium containing the instructions. Furthermore, the names and terms used are not limited, and other expressions that have substantially the same content and intent are also included in the present invention.

[0018] In this embodiment, the term "information processor" is used, but it also includes the following devices, software, or equipment. It is made up of a semiconductor chip, has an input section for sensor signals, and includes a transmitter that transmits processed signals input from the sensor. The sensor signal input unit is directly connected to the sensor and includes a transmitter that transmits the processed signal from the sensor. The sensor signal input unit includes a transceiver that receives a wireless signal from the sensor and transmits a processed input signal from the sensor. The gateway has a hardware block configuration and is configured as a gateway, and includes the gateway having a function of performing short-range wireless communication and a function of being able to connect to a network. The gateway also includes the gateway when it acts as an agent. This also includes smartphones that have the appearance of a smartphone and function as a simple notification or receiving function or agent. Regardless of the external appearance, the information processor of the present application also includes a tape, card, board, etc. in which the semiconductor chip is embedded, and further includes a device that is operated by a program and is installed as a data processing program. <beacon signal> First, the beacon signal used in this embodiment will be described with reference to Fig. 1. An information processor equipped with a communication function uses an advertising packet used in a BLE (Bluetooth Low Energy) function as a beacon signal.

[0019] The Bluetooth Low Energy standard reserves 40 channels for communication, three of which are used as advertising channels. These advertising channels are used to transmit advertisement packets, sending data to inform surrounding devices of their presence. The advertising interval time is between 20 ms and 10.24 ms. Advertising broadcasts a beacon signal carrying the advertisement packet on each of the three configured channels.

[0020] There are various types of information processors with communication functions, including those that can connect to a server via the Internet and communicate with each other.

[0021] This embodiment focuses on the fact that "the advertisement packet has a portion of its area that can be used by the user as desired."

[0022] Furthermore, the information processor may be configured not only as a beacon device with a simplified configuration, but also as a combination chip or combination device combined with a sensor, or as a part thereof.Furthermore, the information processor may be configured as a combination device or combination system combined with a smartphone as a beacon module, or as a part thereof.Furthermore, the information processor may be configured as a combination device or combination system combined with an edge computer as a beacon module, or as a part thereof.

[0023] In this embodiment, the advertisement packet (hereinafter referred to as a beacon packet) is configured as follows so that it can be effectively applied to the above-mentioned combined chip, combined device, or combined system. <beacon packet> As shown in Figure 1, a beacon packet 21 in a common format used by the information processor is shown. The beacon packet 21 is composed of 32 bytes, with a 7-byte header area 22 and a 25-byte user area 23. The user area 23 includes an application ID / service ID area 24 and a communication data area 25. Data written in the user area 23 is related data for context matching. The information written in the service ID area 24 may be referred to in whole or in part as an application ID or service ID.

[0024] The header area 22 is in accordance with the Bluetooth Low Energy standard, and a detailed description thereof will be omitted here. In this embodiment, attention is focused on bytes 7 to 31, which are the range that can be used independently by the user.

[0025] Bytes 7 to 8 (area 24a) describe an application ID. Within this application ID, a member ID (identification information of a user of an electronic device) is described. The member ID (identification information of a user of an electronic device) is information that identifies a company or organization. If bytes 7 to 8 are a reserved value, for example, 0x0000, this is intended for special use and normal use is prohibited.

[0026] Bytes 9 to 10 (the area marked with a symbol 24b) describe a service ID. This service ID describes a module ID (identification information for a non-specific application). A module ID is internal identification information for a program module for each company or organization. For example, if a user's smartphone has multiple individual apps from a certain company or organization installed, a module ID can be assigned to each individual app so that the data structure of these apps can be identified.

[0027] Byte 11 (area marked 24c) describes the frame type. The frame type indicates the type of transmission. The frame type is used to increase the accuracy of communication between devices, and includes a flag and command that indicates whether a response is required or not to the other device. Examples of commands include notifying sensor values, notifying a job, and notifying job results. This ensures reliable communication between devices.

[0028] Bytes 12 to 31 (area marked with a symbol 25) are the parameter section (parameters: transmission information) known as the communication data section. The parameter section stores multiple parameters. Each parameter consists of a TL section and a VAL section. The TL section consists of one byte and is made up of a TYPE field and a LENGTH field. The TYPE field distinguishes the type of data in the VAL section (there are int, float, and string types) as int, float, or string (distinguishing this using a pre-set hexadecimal number). The LENGTH field indicates the data length of the data in the VAL section (shown using a pre-set hexadecimal number). The VAL section describes data of the type specified in the TYPE field and of the length specified in the LENGTH field.

[0029] Using the above description method, for example, the following information is described: Bytes 12 to 13 (area 25a) describe the node ID, Byte 14 (area 25b) describes the information ID, Bytes 15-16 (area 25c) describe the control code, and Bytes 17-31 (area 25d) describe the data section (status code, discrimination code, action instructions), etc.

[0030] The node ID is identification data of the device that transmits this beacon packet 21, and is identification data that identifies devices such as an agent, a node, a smartphone, a gateway, etc.

[0031] The information ID indicates the type of information being sent, such as GPS information, sensor information, etc.

[0032] The control code is used, for example, when a new situation rule is registered, when there is a change in a situation rule, or when the rule itself is conveyed.

[0033] The data in the data section (status code, discrimination code, action instruction code, etc.) uses schema information corresponding to the context. In other words, codes with meanings pre-agreed between the sender and receiver are used. Depending on the type of context matching service used, raw context data may also be used.

[0034] The information in the above area is generally called attribute information. The attribute information is not fixed or limited. The attribute information basically instructs how to handle so-called context data. Therefore, for system operators, the format and content of the attribute information vary, but what is important is that the attribute information exists in this area.

[0035] The data in the parameter section may be encrypted. In special cases, it may be compressed using a password. If a password is used between a first device of a first user and a second device of a second user, the users can register the password in advance on each device. This allows beacon communication between the first device and the second device to be automatically decompressed. <Outline of operation of the embodiment> Here, an example of an outline of the operation of one embodiment will be described. A service provider (a party that provides information) is assumed to have a first information processor (agent), while a service requester (a party that wants information or wants assistance in providing information) is assumed to have a second information processor (node).

[0036] Now, suppose that a service requester (store) registers the device ID 1 of a first information processor (hereinafter referred to as the first node) and first context data (for example, unsold melon bread) in a context determination unit (a register described later).

[0037] Assume that a service requester (customer) registers the device ID2 of a second information processor (hereinafter referred to as the second node) and second context data (for example, "I like melon bread") in a context determination unit (a register described later).

[0038] Furthermore, suppose that the first information processor (hereinafter referred to as the agent) registers the context data "Melon Bread Discount Coupon" in the context determination unit (a register described later). Note that the agent and the store node may be integrated.

[0039] With the above settings, the agent can prepare to send the context data "Melon Bread Discount Coupon" based on a command from the context determination unit.

[0040] At the time of the above-mentioned registration, the context determination unit determines that the keyword (melon bread) of (melon bread discount) and the keyword (melon bread) of (melon bread lover) are in a matching relationship.The context determination unit then manages the first node's device ID1 and the second node's device ID2 as the same group, with the keyword (melon bread) of the context data as the common word.In other words, the first node and the second node are linked.At this time, the agent is also linked and grouped with the first node and the second node, with "melon bread" as the common word.

[0041] An agent can receive device ID1 and ID2 of nodes in the same group from the context determination unit. Now, let's say that the first node (owned by a customer) enters the agent's communication area and broadcasts. In this case, the first node is not an agent, so it simply writes only its own device ID2 in the node ID field of the parameter section and broadcasts.

[0042] At this time, the agent has received device ID1 and ID2 of the same group from the context determination unit, so it can recognize that a device (first node) grouped by context matching has entered its communication area. The agent then automatically sends a "melon bread discount coupon" to the first node as one of its jobs or actions. The "melon bread discount coupon" data is written in the data section and sent. This data (i.e., context) can be coded (e.g., converted into a context number), which is possible if the system has a conversion processing function.

[0043] This allows the first node (customer) to automatically obtain the "melon bread discount coupon" without performing any operation or search.

[0044] As described above, the first node (customer) can detect that a predetermined situation rule (a state called context matching between multiple information devices) has been established because the parameter section 25 sent by the agent contains its own device ID and a "melon bread discount coupon" (or predetermined matching notification information).

[0045] On the other hand, the second node (store) can recognize that the agent has sent the "Melon Bread Discount Coupon" in response to the context "Melon Bread Discount Coupon" that it provides. In other words, it can recognize that the assistance (or CM) to the second node (store) was successful. This allows the system to further improve the matching effect (strengthen sales promotion).

[0046] On the other hand, when the agent detects the device ID1 of the first node from the received signal, it detects that a predetermined situation rule has occurred within its own communication area. In other words, the agent (first information processor) can determine that the first node (second information processor) is in a predetermined position (within its communication area), that the relationship with the first node (second information processor) is in a context matching state, and that there is a first node (second information processor) other than its own (a state in which multiple information processors exist).

[0047] In this embodiment, an area where such a situation rule may occur is called a context area.

[0048] In the above explanation, it was explained that the first information processor (agent) broadcasts its own device ID1 and the device ID1 and ID2 of the second information processor (first node, second node). The first information processor (agent) then further transmits context data (a melon bread discount coupon) as "predetermined matching notification information" (one of the jobs or notifications). Alternatively, it may simply transmit a comment such as "Matching" or voice data.

[0049] In this case, if the second information processor (node) has the ability to compare its own stored context data (or matching confirmation data) with the "predetermined matching notification information" sent from outside, it can display the context data (melon bread discount coupon) on the display unit. A smartphone can be fully equipped with this comparison and display ability by adding software.

[0050] The above explanation is a simple example of the operation of the embodiment, but the basic system of the present invention can perform a variety of operations as will be explained below. <Basic configuration and functions of information processing systems 1> FIG. 2A shows an example of a basic configuration of an embodiment of an information processing system. In an actual system, many context areas exist, but in this embodiment, an example in which two context areas 10 and 20 exist is shown.

[0051] The context area 10 is an area in which the agent 2000, the node 4100 owned by a customer, and the node 4200 owned by a store can communicate with each other by broadcasting. Note that the agent 2000 may be integrated with the node 4200 owned by the store.

[0052] The context area 20 is an area in which the agent 3000 and the node 4300 can communicate with each other by broadcasting. The node 4400 is a signage that can be controlled by the agent 3000, and is always treated as an entity with the device ID of the agent 3000. Alternatively, the signage 4400 may be set as a node that broadcasts.

[0053] Agents 2000 and 3000 are realized, for example, as gateways, smartphones, personal computers (PCs), tablet PCs, etc. Agents 2000 and 3000 can be installed in a variety of locations, such as supermarkets, convenience stores, department stores, offices, restaurants, factories, cars, hospitals, flying objects, roadsides, etc. Furthermore, the installation locations also include "objects" such as lighting fixtures, televisions, signage, pedestrian crossing signals, utility poles, and streetlights.

[0054] The nodes 4100, 4200, 4300, etc. are portable devices such as smartphones, personal computers (PCs), tablet PCs, accessories, wristwatches, bands, etc. Therefore, these nodes can move to different context areas. The node 4400 is a signage controlled by the agent 3000, but it goes without saying that it may also be a device that performs beacon communication.

[0055] If the agent is a mobile vehicle-mounted type, the node is used as a type that is placed in a fixed location. This type of node is, for example, a device with a sensor and is placed on a bridge, road, building, construction site, robot, etc.

[0056] The present invention can also be used in a system in which both an agent and multiple nodes are mounted or attached to a moving object, and when a node enters the context area of ​​an agent, mutual recognition is performed.

[0057] The agents 2000 and 3000 can communicate with the context determination unit 1000 to send and receive data. The context determination unit 1000 is installed in a server, for example. In some embodiments, the context determination unit 1000 is integrated with the agent 2000 or 3000.

[0058] The context determination unit 1000 includes a transmission / reception unit 1100, various file units (including memory and a controller) 1200, and a situation matching processing unit 1300. The transmission / reception unit 1100 communicates with the agents 2000 and 3000. When the context determination unit 1000 is deployed as a server in the cloud, the context determination unit 1000 and the agents 2000 and 3000 are connected via the Internet. When the context determination unit 1000 is integrated with the agent 2000, for example, the context determination unit 1000 is connected to the input / output unit of the agent by internal wiring (including a semiconductor substrate or a flexible substrate) or a cable.

[0059] The context determination unit 1000 includes a file unit 1200. The file unit 1200 can store various files (data, software, attribute data, etc.) and also includes a controller (not shown). The software includes programs for performing context matching processing, context grouping processing, reading processing, data import processing, writing processing, output processing, etc., and the files and their data are controlled by the controller (not shown).

[0060] The context data is registered in the context determination unit 1000 by a user of the agents 2000, 3000, nodes 4100-4400, etc. from a registration system, which will be described later.

[0061] In this case, the registration action is, for example, a case in which the user of node 4100 registers the context data "I like melon bread" and the user of node 4200 registers the context data "Unsold melon bread" in the file unit 1200. Furthermore, by this registration action, the file unit 1200 also stores the device IDs of the agents 2000, 3000, nodes 4100-4400, etc.

[0062] Now, let us assume that the following registration is made to the file unit 1200. Suppose that the user (customer) at node 4100 and the user (store) at node 4200 have registered "I like melon bread" and "Unsold melon bread", respectively. Also, suppose that the agent 2000 has registered a context called "Melon bread discount coupon" in order to issue a "Melon bread discount coupon" as an action.

[0063] Also, suppose that the user (customer) of node 4300 registers "I like red wine," and the user of agent 3000 (a store in this example) registers "red wine advertisement" as a context for the action. In this case, node 4400 is, for example, a signage (digital billboard near the store).

[0064] Then, the file unit 1200 classifies the agent IDs and node IDs (hereinafter collectively referred to as device IDs) for each context through context matching processing, and forms a device ID group for each context (i.e., keyword). This group data is stored in table 1201.

[0065] In the example shown in the figure, the melon bread group G1 is formed as a device ID group of the device ID of the agent 2000, the device ID of the node 4100, and the device ID of the node 4200.

[0066] The red wine group G2 is formed as a device ID group consisting of the device ID of the agent 3000, the device ID of the node 4300, and the device ID of the node 4400. It is desirable that the device ID of the node 4400 be registered in the context determination unit 1000 by the agent 3000 as a store as an associated device (signage).

[0067] These group data are stored in the file unit 1200 as a table 1201. This table 1201 is updated every few minutes, for example, by an update program. Alternatively, it is updated once or several times a day depending on the registered context content (this number of update processes can be changed separately by the system administrator). Newly registered data is temporarily saved in a buffer memory (not shown) until it is updated.

[0068] As described above, each piece of context data registered by each user can be said to be a context linked (belonging) to a specific agent, and also a context linked (belonging) to a specific node.

[0069] Furthermore, if the context determination unit 1000 is provided in a server, the group data related to the agent 2000 may be transmitted to the agent 2000 in advance and stored in its memory (this will be described later with reference to FIG. 2B). Similarly, the group data related to the agent 3000 may be transmitted to the agent 3000 in advance and stored in its memory (this will also be described later with reference to FIG. 2B).

[0070] Furthermore, the store node 4200 in the context area 10 and the agent 2000 are particularly closely related, and information such as the number of products sold and the sales price obtained at the store node 4200 is always notified to the corresponding agent 2000 as a job. Similarly, the store node (signage) 4400 in the context area 20 and the agent (store) 3000 are particularly closely related, and the agent (store) 3000 may be able to directly control the display of the store node (signage) 4400. Of course, the agent 3000 and the node 4400 may communicate by broadcast, so that the agent 3000 may issue a command to "conduct advertising" to the node 4400.

[0071] When the node 4300 enters the context area 30 through this system operation, the node (signage) 4400 displays an advertisement such as "Red wine available."

[0072] As described above, the agent 2000 transmits job data to the server or the context determination unit 1000, and also transmits discount coupons to the nodes 4100 within the area. The agent 3000 can also advertise to specific customers at appropriate times on the nodes (signage) 4400.

[0073] These actions, such as the fact that the agent 2000 has sent a discount coupon and the fact that the agent 3000 has advertised on the signage, are the subject of job data transmission to the server and the context determination unit 1000 . <System response to registration of "Melon Bread Discount Coupon"> When a "melon bread discount coupon" is registered in the context determination unit 1000, a discount coupon processing program in the file unit 1200 is started. Similarly, when a "discount coupon" for another product is registered in the context determination unit 1000, a coupon processing program is started.

[0074] The coupon processing program is started using, for example, "discount coupon" as a keyword. Then, it determines which agent sent the "discount coupon" and identifies the agent that sent it. Next, the program adds attribute information (discount amount or discount rate, issue deadline (start date and time)) set in the "discount coupon" to the agent that sent it, and sends it to the agent that sent it.

[0075] The attribute information (discount amount or discount rate, issue deadline (start date and time to end date and time) set in the "discount coupon" may be set by the sending agent (retailer) (specifically, the user operating the agent) or by the "wholesale store" of the product to be discounted (specifically, a special user who can operate the context determination unit 1000, or a system administrator). The system administrator sets the above attribute information based on instructions from the wholesale store. The issuance conditions (attribute information) of a "discount coupon" may also be determined according to the number of nodes in a context matching relationship within the context area. In other words, a "discount coupon" is issued when the number of nodes is equal to or greater than N (a set number).

[0076] <System operation example related to context area 10> Next, an example of system operation related to the context area 10 will be described. Here, an example will be described in which the context determination unit 1000 is arranged in a server and the table 1201 in the file unit 1200 is used.

[0077] Now, the context of the agent 2000 in the context area 10 is "Melon Bread Discount Coupon", and a case will be described where this context is registered in the file section 1200.

[0078] <Situation detection mode of agent 2000 in context area 10> Now, assume that a broadcast is performed between the agent 2000 and the nodes 4100 and 4200 in the context area 10 (the operating mode at this time is the agent's situation detection mode). The agent 2000 transmits its own device ID as well as at least the device IDs of the nodes 4100 and 4200 to the file unit 1200 of the context determination unit 1000 (this is called situation notification 201).

[0079] Then, the situation matching processing unit 1300 of the context determination unit 1000 references the data file (table 1201) in the file unit 1200 and searches for the multiple device IDs sent from among the device ID groups. Given the current situation in the context area 10, it is determined that the agent 2000, node 4100, and node 4200 belong to the melon bread group G1. It is also determined that the agent 3000 and node 4300 belong to the red wine group G2. In the example shown in the figure, the device ID of node 4400 is also integrated with the device ID of agent 3000 as signage under agent 3000.

[0080] Based on the above determination, the file unit 1200 notifies the agent 2000 of the device IDs belonging to the melon bread group (i.e., the device ID of the agent 2000 and the device IDs of the nodes 4100 and 4200) (this is called the establishment of the situation rule, i.e., a matching notification 202).

[0081] <Matching Report Mode for Agent 2000's Node in Context Area 10> Next, after the above-mentioned matching notification 202 (which may also be called a situation rule establishment notification) is made, a broadcast is made between the agent 2000 and the nodes 4100 and 4200 in the context area 10 (this operation is a matching report mode by the agent 2000).

[0082] Agent 2000, based on the function of its data processing unit, holds matching notification information (its own device ID and the device ID of node 4100), and writes this information in the parameter section explained in Figure 1 before broadcasting. Node 4100 can then detect its own device ID, the device ID of agent 2000, and "context matching related information" from the parameter section of the received advertisement packet.

[0083] This allows the node 4100 to respond in some way based on the function of its data processing unit and attract the user's attention. For example, it can automatically receive a "melon bread discount coupon" from the agent 2000. This can further increase the effectiveness of advertising and promote sales.

[0084] Other reactions of the node 4100 may include flashing light, outputting a notification sound, vibrating, or displaying text. This notification method can take various forms depending on the type and performance of the node 4100. A simple accessory-type node can provide a flashing, audio, or vibration notification.

[0085] Furthermore, if it is a smartphone type, it can also display text and images based on the functions of the data processing unit. For example, if the agent 2000 describes and transmits the context "Melon Bread Discount" in the parameter section, the user of the node 4100 can see the text display of "Melon Bread Discount" or hear the voice output, and even see an image of a melon. Of course, as explained above, it is possible to receive a "Melon Bread Discount Coupon."

[0086] Furthermore, if the node has a context comparison function, the agent 2000 may transmit predetermined matching notification information. The predetermined matching notification information may be, for example, "discount on melon bread." This allows the user who owns the node 4100 to easily recognize that a user who provides services related to at least "melon bread" is nearby.

[0087] Meanwhile, the agent 2000 can grasp how many users (such as node 4100) who "like melon bread" are within the communication area each time a "status notification" and a "matching notification" are executed. This allows the agent 2000 to collect data on the number of users who "like melon bread" and the sales volume of melon bread, and calculate the correlation between the number of users and the sales volume. Furthermore, this realizes direct advertising, and the agent notifies a specified server of the job information. The job information is the data collected by the agent and / or the calculation result of the correlation (such as a ratio) between the number of users and the sales volume.

[0088] When counting the nodes within its communication area, the agent 2000 is provided with a counting program that also counts the device ID of the node 4200 (store). However, the agent 2000 holds in advance the device ID of the node 4200 (store) that it manages and controls. For this reason, the counting program of the agent 2000 is configured to count the number of nodes that are actually "customers" by subtracting the device ID of the node 4200 (store).

[0089] <System operation example related to context area 20> Next, an example of system operation related to the context area 2 will be described.

[0090] Now, the context of the agent 3000 in the context area 20 is "red wine sales", and a case will be described where this context is registered in the file section 1200.

[0091] In the context area 20, it is assumed that a node 4300 owned by a customer has registered "red wine lover" in the file section 1200. It is also assumed that an agent 3000 owned by a store has registered "red wine sales" in the file section 1200. It is also assumed that the agent 3000 has registered a node (signage) 4400 in the file section 1200 as an associated device.

[0092] In this case, the agent 3000, the device ID of the node 4300, and the device ID of the node 4400 are classified into the red wine group G2.

[0093] <Situation detection mode of agent 3000 in context area 20> Now, assume that a broadcast is made between the agent 3000 and the node 4300 in the context area 20 (the operation at this time is in the agent's status detection mode). The agent 3000 transmits at least the device ID of the node 4300 together with its own device ID to the file unit 1200 of the context determination unit 1000 (this is called status notification 301).

[0094] Then, the situation matching processing unit 1300 of the context determination unit 1000 refers to the table 1201 of the file unit 1200 and searches for the multiple device IDs sent from among the device ID groups. In the current situation, it is determined that the agent 3000 and the node 4300 belong to the red wine group G2 (situation rule determination).

[0095] Based on this determination, the file unit 1200 notifies the agent 3000 of the multiple device IDs (the device ID of the agent 3000 and the device ID of the node 4300) belonging to the red wine group G2 as the red wine group (this is called a matching notification 302).

[0096] <Matching report mode for nodes by agent 3000> After the above-mentioned matching notification 302 is performed, a broadcast is made between the agent 3000 and the node 4300 in the context area 20 (this operation is a matching report mode by the agent 3000).

[0097] Agent 3000 holds matching notification information (its own device ID and the device ID of node 4300), and writes this information in the parameter section described in Figure 1 and broadcasts it. Node 4300 can then detect its own device ID and the device ID of agent 3000 from the parameter section of the received advertisement packet. This allows node 4300 to respond in some way and attract the user's attention. This method of attracting attention is similar to the method described above for node 4400.

[0098] Furthermore, in this case, the agent 3000 notifies the node (signage) 4400 to display "red wine for sale" as an automatic action. This allows a customer who owns the node 4300 to see the nearby signage and recognize with a high probability that a "store selling red wine" is nearby. This makes it possible to further increase the effectiveness of advertising and promote sales.

[0099] If the agent 3000 also "sells melon bread" and another node (not shown) has registered the context "I like melon bread," the agent 3000 will process a second matching notification. In such a case, these multiple matching notifications can be broadcast simultaneously or with a time lag.

[0100] Additionally, the agent 3000 notifies the file unit 1200 of the context determination unit 1000 or a separately designated server of the job information that a "red wine advertisement" has been placed. Here, the billing process may be performed by updating the billing data in the billing table for the "red wine seller" registered in the context determination unit 1000 or the designated server. The billing in this case is a direct commercial success fee.

[0101] <Pre-deployment of matching notification information> In the above explanation, it has been explained that the context determination unit 1000 is provided in the server, and that the context determination unit 1000 has table 1201 (a table in which agent IDs and node IDs are grouped by context). It has also been explained that the agents send status notifications 201, 301 and receive matching notifications 202, 302 from the context determination unit 1000.

[0102] However, the information of the matching notifications 202, 302 for the agents 2000, 3000 may be provided in advance to each agent 2000, 3000. This method can reduce the load on the server (context determination unit) and also speed up the transmission of matching reports and discount coupons by the agents to the nodes.

[0103] 2B shows an embodiment in which related matching notification information is pre-deployed to an agent. The same parts as in FIG. 2A are given the same reference numerals, and duplicated explanations will be omitted. This embodiment is characterized by the processing performed after the agents 2000, 3000, and nodes 4100, 4200, and 4300 register their own device IDs and contexts in the file unit 1200 of the context determination unit 1000.

[0104] As explained above, the file unit 1200 of the context determination unit 1000 creates the table 1201. A context matching process is performed to classify the device IDs of the agents and nodes for each context (keyword).

[0105] As explained above, when the situation notification 201, 301 is sent from the agent to the context determination unit 1000, the situation matching processing unit 1300 sends the matching notification 202, 203 to the agent 2000 or the agent 3000 as a reply operation.

[0106] However, the situation matching processing unit 1300 may notify the agents 2000 and 3000 of the matching in advance after the update processing of the table 1201 is executed. For agent 2000, a sub-table 2001 is pre-deployed, which includes the device IDs of the nodes belonging to the group of the context registered by agent 2000 and the device ID of agent 2000. In the example shown in the figure, the device IDs are those belonging to melon bread group G1 (ID 4100, ID 4200, ID 2000).

[0107] For agent 3000, a sub-table 3001 is pre-deployed, which includes the device IDs of the nodes belonging to the context group in which agent 3000 is registered, and the device ID of agent 3000. In the example shown in the figure, the device IDs belonging to red wine group G2 are the IDs of nodes 4300 and 4400, and the ID of agent 3000.

[0108] As described above, table 2001 is pre-deployed (or pre-arranged) to agent 2000, and table 3001 is pre-deployed (or pre-arranged) to agent 3000. In this state, when a broadcast is performed, each agent 2000, 3000 can immediately report a match and immediately send a "discount coupon." In addition, agent 3000 can immediately cause signage node 4400 to advertise.

[0109] That is, the operation of agent 2000 can be explained as follows. When agent 2000 broadcasts, it automatically writes the device IDs of the nodes in melon bread group G1 and its own device ID in the parameter section described in FIG. 1 and executes the broadcast. In this case, node 4100 exists in context area 20, so this node 4100 can get some kind of response. Node 4100 also broadcasts its own device ID.

[0110] The agent 2000 then recognizes that the node 4100 exists in the context area, and is therefore able to immediately send the "Melon Bread Discount Coupon" to the node 4100.

[0111] Now, suppose a user (i.e., a customer) of node 4100 uses a coupon at mode 4200 (i.e., a store) to purchase a melon bun. This sales information (job information or report information) is sent from node 4200 to agent 2000. Agent 2000 then sends the sales information to the context determination unit 1000, or to the server of a melon bun wholesaler or manufacturer. The melon bun wholesaler or manufacturer can request the context determination unit 1000 or the server operator or system administrator to adjust the number of discount coupons to be issued, the issuance deadline, the issuance time period, etc., depending on the sales situation. Therefore, in this system, coupons can be issued instantly or can be changed depending on the number of products sold, the time period, and the date and time.

[0112] When broadcasting, agent 3000 automatically writes the device IDs of the nodes in red wine group G2 and its own device ID in the parameter section described in Figure 1 and executes the broadcast. In this case, node 4300 exists in context area 20, so this node 4300 responds in some way. Node 4300 also broadcasts its own device ID.

[0113] Agent 3000 then recognizes that node 4300 exists in the context area, and can immediately send a message saying "red wine available" to node (signage) 4400. As a result, node (signage) 4400 immediately outputs a voice or displays "red wine for sale."

[0114] When a node (not shown) that has registered "red wine lover" moves from the context area 10 to the context area 20, the node can immediately receive a service from the agent 3000.

[0115] As described above, agents 2000 and 3000 send "discount coupons" to each node that matches the context as an automatic action for nodes detected within the context area, resulting in high CM effectiveness, directness, and CM efficiency.

[0116] FIG. 2C is a flowchart showing an example of the operation when agent 2000, node 4100, node 4501, and node 4503 are simultaneously present in the communication area (context area) and perform a broadcast.

[0117] Here, it is assumed that the agent 2000 possesses and can issue a "melon bread discount coupon." It is also assumed that the agent 2000 has registered, for example, "peach sales" in the context determination unit 1000.

[0118] It is also assumed that node 4100 has registered "I like melon bread" in the context determination unit 1000. It is also assumed that node 4501 has registered "I like peaches" in the context determination unit 1000, which is different from the coupon target. It is also assumed that node 4502 has registered "I love hamburgers" in the context determination unit 1000.

[0119] Assume now that agent 2000, node 4100, node 4501, and node 4503 simultaneously broadcast within the communication area (context area) (S01). Agent 2000 checks the received device IDs (the device IDs of nodes 4100, 4501, and 4503) and identifies device IDs that are in a context-matching relationship (S02).

[0120] The agent 2000 then determines that the device ID of the node 4100 is the "melon bread group G1," and further determines that the device ID (node ​​4100) is eligible for coupon distribution. Therefore, the agent 2000 writes data pairing the device ID of the node 4100 and the coupon data "melon bread discount coupon" in the parameter section shown in FIG. 1 and transmits the data. Specifically, the agent 2000 writes the device ID of the node 4100 and the "melon bread discount coupon" in the data section and transmits the data (S03). This allows the node 4100 to obtain the "melon bread discount coupon" (S05).

[0121] Agent 2000 also determines that the device ID of node 4501 is "Peach Loop GX." In this case, agent 2000 writes data pairing the device ID of node 4501 with "Peach Sale" in the data section shown in Fig. 1 and transmits the data to node 4501. As a result, node 4501 can acquire the "context matching related information" of "Peach Sale" (S06).

[0122] Furthermore, agent 2000 determines that the device ID of node 4502 is not a service target. In this case, data related to node 4502 is not written in the parameter section shown in FIG. 1. Therefore, node 4502 does not acquire any "context matching related information" from agent 2000 (S07). Then, the processing based on the broadcast (S01) ends (S11).

[0123] As described above, this embodiment comprises a first information processor (agent) that registers a first context in a context determination unit, and a second information processor (node ​​4100) that registers a second context in the context determination unit.

[0124] The first information processor and the second information processor perform beacon communication with each other, The information processing system further includes a determination unit that determines context-related information included in a beacon packet. If the result data of the determination indicates that the first context and the second context are in a matching relationship, the first information processor includes a data processor that processes the result data as node notification data, and the second information processor includes a data processor that processes the result data as output data for user notification (display, audio, or vibration). This embodiment also extends to an information processing system, a method related to this system, an apparatus related to this system, or a processing program related to this system.

[0125] In the systems of Figures 2A and 2B, after agent 2000 detects a node in a context matching state, it automatically distributes coupons and the like to that node in the next broadcast. Therefore, it can be said that this system accurately executes appropriate sales to people who are likely to be potential buyers. In the above example, a consumer who says "I like melon bread" can be reliably offered the service of a "melon bread discount coupon." Furthermore, the sales effect is strengthened.

[0126] However, the above-mentioned "discount coupons" may be sent not only to agents but also from the server to nodes. In other words, the server can grasp the status of multiple agents (for example, the number of context matchings that have been achieved). Therefore, by having the server manage the issuance of "discount coupons," the server can manage the total number of "discount coupons" issued or the allocation to each agent.

[0127] As described above, the discount coupon is transmitted to the node by broadcasting from the agent, but it is also possible for the server to transmit to the agent or node via a network such as the Internet.

[0128] FIG. 2D shows an example of a method by which the server 7A transmits to the agent or node over a network such as the Internet.

[0129] The server 7A has a context determination unit 1000, an application program interface (API) 7A1, a sales record management unit 7A2, and a coupon management unit 7A3. The API 7A1 functions as an interface between the context determination unit 1000 and the sales record management unit 7A2.

[0130] The sales record manager 7A2 receives job information (e.g., product sales numbers, sales volume, and sales data) from multiple agents 2000 and 3000 via the context determination unit 1000 and the API 7A1. The sales record manager 7A2 then determines the number of coupons to be issued, the agents to whom the coupons should be distributed, the distribution time period, and other attribute data (corresponding to the control code and data contents shown in FIG. 1). Based on this determination, the coupon manager 7A3 can send a coupon to, for example, node 4100 via the API 7A1 and the context determination unit 1000. Of course, in this case, the server 7A also keeps track of the device ID, email address, and other information of each agent or node. When each agent or node registers its own context (e.g., "I like melon bread") with the context determination unit 1000, it also registers its device ID, email address, and other information. This registered data is used indirectly by the coupon manager 7A2 via the API.

[0131] When the coupon manager 7A3 determines an agent to which the server 7A is permitted to issue a coupon, the server 7A may transmit a "discount coupon" to the agent directly via the network in advance. Also, when the context determination unit 1000 determines a context match, the server 7A may transmit a "discount coupon" directly to the corresponding node via the network.

[0132] <Configuration system for smooth operation of the basic system> As mentioned above, this system provides appropriate service information from "users who provide service information" to "users who want service information" based on the establishment of rules for the situation. In order to realize this mechanism in a variety of ways, the system will be even more valuable if the following setting systems are introduced.

[0133] Figure 3 shows the various configuration systems required to ensure smooth operation of the basic system. In the following drawings, the same parts as those in the previously explained drawings will be assigned the same reference numerals as those in the previously explained drawings, and duplicated explanations will be omitted. <Context scheme and rule setting system> To set the above-mentioned "situation rules," a context scheme and rule setting unit 5000 is used. The context scheme and rule setting unit 5000 is mainly used by a rule setter 5500 who uses this system to devise the form (type, etc.) of an information service, and by users (business owners, service managers, service initiators, etc.).

[0134] The rule setter 5500, in consultation with users (business owners, service managers, local governments, service planners, etc.), designs a mechanism for users who are "information providers" and "information seekers" to "provide information" and "receive information." The mechanism may also be called an information processing procedure.

[0135] The above-mentioned business owners, service operators, local governments, or service initiators may be retailers of various products, parents with children (Parent-Teacher Association (PTA)), public institutions such as local governments, committee members of school alumni associations, companies, etc., or may be the rule setter 5500 itself.

[0136] Retailers want to promote the sale of their products, including food, general merchandise, clothing, industrial products, parts, housing, securities, real estate, etc. Parents also want to check the safety of their children on their way to school. Public institutions also want to check the range of activities of the elderly. Also, the school alumni committee members may want to find members for the alumni association. Building managers also want to reduce the amount of energy used in their buildings. Furthermore, managers of large supermarkets and event venue operators want to set up customer flow lines to guide customers efficiently.

[0137] These services are called, for example, "unsold product sales service" or "product sales promotion service," "child monitoring service," "elderly monitoring service," "encounter detection service," "building energy saving management service," "customer flow setting service," "meeting service," and "matching information provision service for hobbies, clubs, class reunions, etc."

[0138] The rule setter 5500 designs a "rule execution program" that is suitable for each of the above-mentioned services and easy for users to use, and an "information input template" for inputting information for processing by the program.

[0139] The rule settings will differ depending on the user of this system, and the rule setter may also differ depending on the rule settings. For example, for a "product sales promotion service," the sales promotion method (elements that build the rule setting situation) may differ depending on the store, and the sales promotion method (elements that build the rule setting situation) may also differ depending on the product handled (everyday goods, precious metals, passenger cars, etc.).

[0140] For ease of understanding, an example of use of a "sales service for unsold items" will be described. The mechanism of the "unsold product sales service" is designed by a rule setter 5500 using the context scheme and rule setting unit 5000. To operate the "unsold product sales service", a "rule execution program" and a "template for information input" are required.

[0141] The user requesting the setting of the situation, i.e., the rule setter 5500, may be, for example, the manager of a convenience store, supermarket, or department store, or a public institution such as a PTA (Parent-Teacher Association), a local government, a school alumni association committee member, or a company.

[0142] The rule setter 5500 prepares his / her own agent. The multiple nodes are an unspecified number of people, such as customers visiting a store, children who need to be watched over, and elderly people.

[0143] The rule setter 5500 designs what kind of state (locational or positional relationship, mutual detection method between nodes and agents, detection content) is expected between multiple nodes and agents. For example, the rule setter designs that the agent 2000 mentioned above can set its communication area (context area) 10, and that nodes can be detected in this communication area. The rule setter also decides what kind of context matching is expected to make the nodes detectable. In the previous example, the context is "unsold melon bread" and the keyword is "melon bread."

[0144] However, supermarkets and department stores have a large number of products. Also, stores selling expensive precious metals and car dealerships may need to limit the number of customers allowed in. In such situations, it is necessary to devise a method for notifying users of matching.

[0145] For this purpose, discussions and agreements are held regarding ways to input product names into templates (for example, automatically fetching product names from a database, manually entering them, etc.). Furthermore, when the context determination unit 1000 sends a matching notification to an agent, an agreement is made to enable setting of notification conditions. Notification conditions include, for example, notification frequency and excluding certain notification recipients. Of course, as explained above, agreements are also made regarding the circumstances under which a "discount coupon" is issued, the date and time at which the issuance instruction is issued, whether it is possible to change or amend the instruction, etc.

[0146] As described above, a rule setter who is familiar with the user's (agent owner's) business type creates a rule execution program and templates for information input in the context scheme and rule setting unit 5000. The system is designed so that the user can then select the desired template and input the necessary setting data.

[0147] For this purpose, the rule setter may design a field in the template for inputting attribute information (such as the control code and data portion described in FIG. 1) that accompanies the service information (context).

[0148] The attribute information further includes information such as the advertising time period for the context "unsold melon bread" and the validity period of the context. It also includes specification information such as the length of the data section (length of the context) and the type of language. Furthermore, the context determination section may be used for various purposes other than context classification processing. In this case, information specifying the purpose is added to the attribute information. For example, there is information indicating whether the context is encrypted with a password. Furthermore, the attribute information may have a field for inputting matters to be entrusted to the system administrator 9500 described below. The entrusted matters include, for example, the frequency of sending advertisements (matching-related information).

[0149] The "rule execution program" and "information input template" created by the context scheme and rule setting unit 5000 are stored as rule setting data 501 in the data file unit 1200. The rule setting data 501 may also be transmitted in advance to the agent 2000 as rule setting data 502.

[0150] As described above, this embodiment includes a first information processor that registers a first context in a context determination unit, and a second information processor that registers a second context in the context determination unit. The first information processor and the second information processor communicate with each other through beacon packets, and each processor includes a determination unit that determines context-related information included in a beacon packet.

[0151] When the determination result data indicates that the first context and the second context are in a matching relationship, the first information processor includes a data processor that processes the result data as node notification data, and the second information processor includes a data processor that processes the result data as output data for user notification (display, audio, or vibration).Furthermore, a rule setting system connectable to the context determination unit for designing a user service form by setting rules that will result in the matching relationship includes a rule setting unit that provides an input unit for at least a context and a device ID as elements for setting the rule.

[0152] <Information Registration System 6000> As described above, various templates are created in the context scheme and rule setting unit 5000. The information registration system 6000 is a system for registering various data using templates and software designed by the rule setter. This information registration system 6000 is used by a user 6500 who wants information to input specific context data and the device ID of their own information processor using the input information template.

[0153] A "user who wants information" registers information (which may also be called profile information). In the previous example, the user at node 4100 would register "I like melon bread." Also, the user at node 4300 would register "I like red wine." And the user at node 4200 would register "Unsold melon bread." This information is registered in the data file unit 1200 as profile information 601.

[0154] The information registration system 6000 may also be used as follows for an automated marketing operator.

[0155] When context matching for "melon bread" is established in the context area 10, the agent 2000 notifies the context determination unit 1000 of job information. The job information also includes the number of melon breads sold within a certain time period after the "predetermined situation" is established.

[0156] Therefore, the automated marketing operator also prepares a "research agent" in the context determination unit 1000 that can count the number of "melon bread lover" nodes, just like the agent 2000. This "research agent" then receives data on the number of melon bread sales notified to the melon bread wholesaler from the agents of many convenience stores. Then, depending on the average sales number for the day or several days, or the time period, the automated marketing operator ("research agent") can notify each convenience store of the discount rate for melon bread, or issue instructions for "melon bread discount coupons" and the number to be issued.

[0157] The automated marketing operator and the melon bread wholesaler may be the same person. In this way, the "survey agent" can instruct the agents at each convenience store to issue coupons depending on the sales status of melon bread.

[0158] Alternatively, the "survey agent" can issue instructions to vary the discount rate for special items (such as boxed lunches or fresh food) at convenience stores depending on the time of day. Such instructions may also be input via the agent to a signage control system installed in front of or inside the convenience store.

[0159] The profile information 601 includes the device ID of the information processor used by the "user who wants service information." The profile information written in the template also includes a context related to the information desired. Examples of contexts include the aforementioned "I like melon bread" and "I like red wine."

[0160] Furthermore, attribute information indicating that the registration information is from a "user (information processor) who desires service information" is attached as attribute information to the profile information 601. Note that there are various types of attribute information, and therefore, predetermined codes or symbols exist as headers according to the type of attribute information (also referred to as schema information).

[0161] The attribute information may also include condition data, matching restriction data, etc. The condition data may include the validity period of the context.

[0162] The matching restriction data is data that treats the matching as not being established if a special condition exists, even if context matching is established between this information processor and another information processor. For example, the matching restriction data is data that allows the grouping program in the data file unit 1200 to determine that matching is not established if a predetermined device ID (particularly an agent) or the name of a predetermined rival store is attached to the context.

[0163] 2A and 2B, suppose that agents 2000 and 3000 are rival stores. In such a case, when the stores of agents 2000 and 3000 register their context data in file unit 1200, they may also register information about their rival stores.

[0164] If the stores of agents 2000 and 3000 sell the same product (for example, melon bread), the device IDs of agents 2000 and 3000 will be included in melon bread group G1. In this case, if information about a rival store is included in the context data, the context determination unit 1000 will manage melon bread group G1 by dividing it into melon bread group G1-1 for agent 2000 and melon bread group G1-2 for agent 3000.

[0165] When the context determination unit 1000 notifies the agent 2000 of a matching, it transmits the device ID included in the melon bread group G1-1, and when it notifies the agent 3000 of a matching, it transmits the device ID included in the melon bread group G1-2.

[0166] As a result, when sending a device ID within one group to one agent, the device ID within the group is sent so that the device ID of another agent does not coexist, which allows each agent to eliminate unnecessary processing steps.

[0167] The same applies when the present system pre-deploys table 2001 to agent 2000 as explained with reference to FIG. 2B.

[0168] As described above, this embodiment includes a first information processor that registers a first context in a context determination unit, and a second information processor that registers a second context in the context determination unit. The first information processor and the second information processor communicate with each other via beacon packets, and each processor includes a determination unit that determines context-related information included in a beacon packet.

[0169] If the determination result data indicates that the first context and the second context are in a matching relationship, The first information processor includes a data processor that processes the result data as node notification data, and the second information processor includes a data processor that processes the result data as output data for user notification (display, audio, or vibration).

[0170] Furthermore, a profile information input system for pre-setting profile information including the device IDs of the first information processor and the second information processor and their respective context data, which are specific determination factors for the matching relationship, can be connected to the context determination unit.

[0171] <Provided Information Input System 7000> The provided information input system 7000 is a system in which a "user who provides service information" uses a template to input "provided information" to the context determination unit 1000. The input programs and templates in this provided information input system 7000 are also created by the rule setter who set the situation.

[0172] The input information that the information providing user 7500 inputs to the context determination unit 1000 of this system includes at least the device ID of the information providing information processor (agent or node) used by the "information providing user." An example of a context is when the aforementioned agent 2000 registers a "melon bread discount coupon." Another example is when a user at node 4200 registers "unsold melon bread." Another example is when agent 3000 registers advertising data for signage (for example, "red wine included").

[0173] Furthermore, this input information may be accompanied by attribute information (a predetermined code) so that the context determination unit 1000 can determine that the information is from the user 7500 who provides the information.

[0174] Matching restriction data may be attached to the attribute information of the information providing information processor. Assume that there is a third information processor with which context matching is established with the information providing information processor. However, depending on the content of the attribute information of the third information processor, it may be preferable to make a final determination that matching is not established (that is, to not provide service information). For example, if the information to be provided is "discounted sales of alcoholic beverages," the attribute information of the user of the third information processor may describe age data of 14 or under or 20 or under, and "rubbing alcohol" may be described as the context. In such a case, the situation matching processing unit 1300 of the context determination unit 1000 determines that matching between the third information processor and the information providing information processor is not established.

[0175] Attribute information is also used to identify an agent to which "provided information" is to be sent, or conversely, to identify an agent to which "provided information" should not be sent. For example, in the examples of FIGS. 2A and 2B, when agent 2000 registers a "melon bread discount coupon," "agent 3000" may be identified in the attribute information as an agent to which "provided information" should not be sent. The attribute information may be written using, for example, the name, telephone number, or address of agent 3000.

[0176] The user providing the situation may be the rule setter 5500 himself, as described above.

[0177] As described above, this embodiment includes a first information processor that registers a first context in a context determination unit, and a second information processor that registers a second context in the context determination unit. The first information processor and the second information processor communicate with each other through beacon packets, and each processor includes a determination unit that determines context-related information included in a beacon packet.

[0178] If the determination result data indicates that the first context and the second context are in a matching relationship, The first information processor includes a data processor that processes the result data as node notification data, and the second information processor includes a data processor that processes the result data as output data for user notification (display, audio, or vibration).

[0179] Furthermore, the information providing device has a provision information input system that can be connected to the context determination unit and that inputs in advance that the result data to be provided to the information processor that is in a matching relationship is data of context content to be provided to the other party.

[0180] <General User Input System 4500> The general user input system 4500 is a system used by users who own nodes that are detected or not detected depending on the situation set by the agent or gateway. The input programs and templates used in this user input system 4500 are also created by the rule setter who set the situation.

[0181] The user input system 4500 is a system that allows the previously described nodes 4100, 4200, and 4300 to register contexts such as the aforementioned "melon bread lover," "unsold melon bread," "red wine lover," and "red wine sales, melon bread sales" together with their respective device IDs in the file unit 1200. The user input system 4500 is designed so that general users can register context data at any time. It is also possible to delete context data as needed.

[0182] A user who uses this user input system 4500 is a user who uses a template to input a context via the information registration system 6000 constructed by a rule setter, or inputs a context via the provided information input system 7000. The input information includes the device ID of the information processor used by the user and the context. Various types of attribute information may also be input.

[0183] <Sending management when sending matching notifications> Furthermore, this system is provided with a transmission management system 9000 when a system administrator 9500 issues matching notifications 202, 203 or status notifications. The transmission management system 9000 controls the transmitting / receiving unit 1100. When issuing matching notifications 202, 203, the transmitting / receiving unit 1100 executes action transmission based on the control of the transmission management system 9000. Action transmission refers to, for example, exclusive control of transmission operations, elimination of duplicate transmission operations, transmission based on priority, and transmission based on management of transmission frequency.

[0184] Regarding exclusive control: When the transmitting / receiving unit 1100 sends matching notifications to multiple agents and gateways, it basically sets an order and sends matching notifications at an equal frequency. However, depending on the agent or gateway, there may be some that want frequent matching notifications depending on the "time period" or "day," and others that do not need to receive them as frequently. In such cases, the system exclusively controls matching notifications for agents and gateways that do not need to receive matching notifications as frequently. For example, if a store is closed, matching notifications may not be necessary. Also, for a store that is only open in the afternoon, morning matching notifications may be unnecessary or may be set to a minimum. Therefore, each agent or rule setter discusses the details of the above-mentioned exclusive control with the system administrator 9500.

[0185] Deduplication controls: For example, there may be multiple similar agents (e.g., two) in the same context area. In this case, the two agents notify the context determination unit 1000 of the device ID of the same node from two locations. The context determination unit 1000 then transmits the device ID of the same node to the two agents. In such a case, deduplication control is performed to avoid duplicate transmission by alternately transmitting the device ID of the same node to the two agents at an interval.

[0186] Regarding priority control: For example, when multiple agents are connected to the context determination unit 1000, the scale of each agent may differ. Also, the service content and scale of each agent may differ, for example, there may be an emergency hospital agent (or gateway), a public institution agent (or gateway), a supermarket agent, a convenience store agent, etc. Also, depending on the season, some agents may be busy and others may be free. In such cases, matching notifications are sent preferentially to agents that require immediacy or busy agents.

[0187] Regarding frequency management controls: The context determination unit 1000 basically sets an order and sends matching notifications to each agent (or gateway) at an equal frequency. For this reason, it adjusts the number of matching notifications to each agent (or gateway) within a certain period so that they are sent evenly.

[0188] As described above, the embodiment includes a first information processor that registers a first context in a context determination unit, and a second information processor that registers a second context in the context determination unit. The first information processor and the second information processor perform beacon communication with each other, and include a determination unit that determines context-related information included in a beacon packet.

[0189] When the result data of the determination indicates that the first context and the second context are in a matching relationship, the first information processor includes a data processor that processes the result data as node notification data, and the second information processor includes a data processor that processes the result data as output data for user notification (display, audio, or vibration).

[0190] The device further includes a transmission management system that can be connected to the context determination unit and that inputs transmission management information to the context determination unit, the transmission management information specifying one of transmission frequency, exclusive control, and duplicate elimination as a method of sending the context-related information. <Examples of devices used as agents> 4A, 4B, and 4C show the external appearance of an information processor used as an agent, and FIG. 4D shows the internal functional blocks of the information processor. However, the present invention is not necessarily limited to the examples shown here.

[0191] FIG. 4A shows an example in which a smartphone is used as agent 2000 or 3000. This smartphone has a beacon communication unit 231 and a base station connection unit 232 for connecting to a telephone line or the Internet. FIG. 4B shows an example in which a personal computer (PC) is used as agent 2000 or 3000. This PC has a beacon communication unit 233 and a network connection unit 234 for connecting to the Internet. FIG. 4C shows an information processor created exclusively for agent 2000 or 3000. This information processor has a beacon communication unit 235 and a network connection unit 236.

[0192] 4D shows the functional blocks required for the above-mentioned agent 2000 or 3000. These may of course be used as nodes 4100-4300, or may be incorporated into signage.

[0193] The functional block includes a transceiver 2300, a beacon communication processor 2301, and a wireless or network communication processor 2302. When beacon communication is performed, the beacon communication processor 2301 and a data processor 2304 are connected by a switch 2303, and when wireless communication or network communication is performed, the wireless or network communication processor 2302 and the data processor 2304 are connected by the switch 2303.

[0194] The status data memory 2305 stores the data of tables 2001 and 3001 described in FIG. 2B as well as various attribute data. Therefore, when beacon communication is performed, the data processor 2304 reads the data from the memory 2305 and writes it as transmission data in the parameter section of the advertisement packet. The control unit 2306 comprehensively controls the transceiver unit 2300, beacon communication processor 2301, wireless or network communication processor 2302, switch 2303, data processor 2304, and memory 2305. Therefore, the control unit 2306 selectively uses various applications depending on the operating mode. The device is also equipped with a display 2307 and a power supply 2308.

[0195] The situation data memory 2305 described above may include a memory (RAM) with a rewritable area and a read-only memory (ROM) previously stored for context matching. The ROM may be a dedicated memory in which various context data is written to increase the utility value of the nodes 2000 and 3000, and may be removable. For example, convenience stores and department stores sell a large number of products, and a memory in which product names and contexts are previously stored may be used. The same can be said for the situation data memory of the nodes described below.

[0196] <Other examples of devices used as nodes> 5A, 5B, 5C, 5D, and 5E show examples of the external shapes of devices (information processors) used as nodes, but are not necessarily limited to those exemplified here.

[0197] FIG. 5A is an example of a smartphone 4510, which has a beacon communication unit 4511 and a base station connection unit 4512 for connecting to a telephone line or the Internet. FIG. 5B is an example of a wristwatch 4520, which has a beacon communication unit 4521 built in. FIG. 5C is an example of a pendant 4530, which has a beacon communication unit 4531 built in. FIG. 5D is an example of a bracelet 4540, which has a beacon communication unit 4541 attached to it. FIG. 5E is an example of a pair of glasses 4550, which has a beacon communication unit 4551 attached to it.

[0198] <Example of node functions> 6A, 6B, 6C, and 6D show examples of various functional blocks of nodes (or usable as agents). These information processors can also be registered as agents when they are registered in the context determination unit 1000.

[0199] Below, we will briefly explain it as a node. Various types of node function blocks are used, from simple to complex. The function block of node 4A00 in Figure 6A is the same as that of a smartphone, and has the same configuration as the agent described in Figure 4D. That is, The device includes a transceiver 4A10, a beacon communication processor 4A11, and a wireless or network communication processor 4A12. A switch 4A13 selectively connects a data processor 4A14 to the beacon communication processor 4A11 and the wireless or network communication processor 4A12 depending on the operation mode (beacon communication mode, wireless communication mode, or network communication mode).

[0200] The status data memory 4A15 stores the device's device ID, the context set by the device, attribute data, etc. The data processor 4A14 can read data from the memory 4A15 and write that data in the parameter section of an advertisement packet. The control unit 4A16 comprehensively controls the transceiver unit 4A10, beacon communication processor 4A11, wireless or network communication processor 4A12, switch 4A13, data processor 4A14, and memory 4A15. Therefore, the control unit 4A16 selectively uses various applications depending on the operating mode. The device is also equipped with a display 4A07 and a power supply 4A08.

[0201] By adding an application, this node 4A00 can autonomously execute context matching processing and situation matching processing, which allows it to have a function similar to that of the context determination unit 1000 described in Figures 2A and 2B on a smaller scale.

[0202] The functional blocks of node 4B00 in FIG. 6B are the same as those of node 4A00 in FIG. 6A except that the status data memory 4A15 and display 4A07 are removed. This node 4B00 can be used as a dedicated repeater. For example, it can be used as a device that transmits data (e.g., device ID) acquired through beacon communication to a server or agent via the Internet. Conversely, it can also notify other nodes or agents in a nearby communication area of ​​data acquired through the Internet via beacon communication.

[0203] The functional blocks of node 4C00 in FIG. 6C are the same as those of node 4A00 in FIG. 6A, except that the situation data memory 4A15, display 4A07, and wireless or network communication processor 4A12 are removed and a sensor 4A09 is added. The other functional blocks are the same as those of node 4A00. This node 4C00 only performs beacon communication and can be used, for example, to notify the detection signal level of sensor 4A09. Types of sensors include an illuminance sensor, temperature sensor, humidity sensor, gas sensor, odor sensor, gyro, altitude sensor, GPS, barometric pressure sensor, pressure sensor, water leak sensor, dust detection sensor, CO2 sensor, human presence sensor, and image sensor. The sensors are not limited to these.

[0204] The functional blocks of node 4D00 in FIG. 6D are the same as those of node 4A00 in FIG. 6A, except for the display 4A07 and wireless or network communication processor 4A12. This node 4D00 can perform simple context matching processing when beacon communication is performed. The results can be notified to the user via the display 4A15. While it is difficult to perform context matching processing on a large scale, it is possible to process simple keywords. The display of this node 4D00 is also effective for simple displays such as blinking LEDs.

[0205] Of course, the above-mentioned various nodes may also be provided with an audio output function.

[0206] <Examples of system usage in convenience stores, supermarkets, department stores, and various other stores> FIG. 7A shows an example in which an embodiment of the present invention is applied to a product sales promotion system in a convenience store 3A. The owner of the convenience store 3A has installed an agent 3000. The agent 3000 has a context area 20. The agent 3000 is also used as a node of the convenience store 3A. "Red wine sales" and "melon bread sales" are registered in the context determination unit 1000.

[0207] Customer 3B has node 4A00 and has registered "red wine lover" as a context. Customer 3C has node 4D00 and has registered "melon bread lover" as a context.

[0208] FIG. 7B shows an example of the operation of the sales promotion system over time T. Assume that customers 3B and 3C enter context area 20 and a broadcast is made (SA1). Then, agent 3000, node 4A00, and node 4D00 enter a context matching state and each detect the context matching state. This allows customer 3B and customer 3C to recognize that a product in which they are interested is being sold nearby (SA2, SA3). In other words, customer 3B recognizes that there is a store nearby that sells red wine, and customer 3C recognizes that there is a store nearby that sells melon bread.

[0209] Meanwhile, agent 3000 acquires the device IDs of nodes 4A00 and 4D00 when it broadcasts. This allows agent 3000 to recognize that it has directly advertised to customers 3B and 3C who are interested in the promoted product (SA4). Agent 3000 then counts the acquired device IDs and recognizes the number of devices (SA5). When counting, it excludes device IDs that have already been received within a specified time period. This is to avoid counting duplicate device IDs. Agent 3000 then transmits the counted number of device IDs to server 5A of the service operator.

[0210] The server 5A of the service administrator updates the data file for charging the agent 3000 as a reward for the "successful advertisement" (SA6).

[0211] Also, agent 3000 may recognize that the user of node 4D00 "likes melon bread" and may also recognize that agent 3000 can issue a "red wine discount coupon." In this case, the "melon bread discount coupon" is sent to node 4D00 (SA7). This allows node 4D to obtain the discount coupon (SA8).

[0212] Furthermore, agent 3000 recognizes that node 4A00 is a "red wine lover." If there is signage nearby, an advertisement such as "red wine for sale" can be displayed on the signage (SA9, SA10).

[0213] <Monitoring service 1> Figure 8A shows the service provider (e.g., local government or Parent-Teacher Association (PTA) 1 shows an example in which an embodiment of the present invention is applied to a monitoring service system provided by a company (eg, a public safety company) or a security company. An example of a monitoring service system for a child 6A commuting to school will be described.

[0214] Child 6A1 has smartphone 4510. In this case, agent 4B00 is placed at traffic light 6B1, for example at a pedestrian crossing, along child 6A1's route to school. When child 6A1's smartphone 4510 is within its communication area, agent 4B00 acquires the device ID of smartphone 4510 by broadcast. Agent 4B00 transmits the acquired device ID to server 7A of the service operator via the network.

[0215] Server 7A has table 7A10 for storing data for monitoring users, and records passing position data 6T1, 6T2, 6T3, etc. of each user 6A1, 6A2, 6A3, etc. in this table 7A10. The passing position data includes, for example, the location (address, street name, etc.) of traffic light 6B1 and the date and time data when the user (user 6A1 in the illustrated example) passed through. When agent 4B00 installed at traffic light 6B1 is registered in the file section, the location of traffic light 6B1 is simultaneously registered together with the device ID of agent 4B00.

[0216] Users who can check the data of user 6A1 on server 7A are, for example, parents 6C1 and 6D1 who have signed a contract with the service operator in advance. If parents 6C1 and 6D1 notice that child 6A1 is passing by in a different location than usual, they can use smartphone 4511 to call child 6A1's smartphone 4510 directly to check the situation.

[0217] The server 7A may also be provided with a service app that notifies the smartphones 4511 of the parents 6C1 and 6D1 if the user's passing location is different from usual or if the user's passing time is significantly different from usual.

[0218] FIG. 8B shows an example of the operation of part of the monitoring system described above over time T. When child 6A1 passes near traffic light 6B1, a broadcast is made between smartphone 4510 and agent 4B00 (SB1). Agent 6B1 detects the pre-registered device ID of smartphone 4510. Agent 6B1 then transmits the device ID of smartphone 4510 and data on the passing location, such as the number or address of traffic light 6B1, to server 7A (SB3). Server 7A records the passing location data in data recording section 6T1 for user 6A1 (child) in table 7A10 (SB4).

[0219] The parents 6C1 and 6D1 can access the server 7A at any time using the smartphone 4511 and check the passage position data 6T1 (SB5). The server 7A also has a program for checking the passage position data 6T1, and if the received passage position is different from usual, it sends a warning to the smartphones 4511 of the parents 6C1 and 6D1 (SB6, SB7).

[0220] This allows the parents 6C1 and 6D1 to use the smartphone 4511 to call the smartphone 4510 of the child 6A1 and request a status report (SB9).

[0221] <Monitoring Service 2> Fig. 9A shows an example in which a service operator (local government) implements an elderly monitoring and guidance system as an embodiment of the present invention. Fig. 9B shows an example of the operation of the elderly monitoring and guidance system over time T. The following description will be made with reference to Figs. 9A and 9B.

[0222] Along the walking path 6H for the elderly 6E, there are an ascending staircase 6F and a descending staircase 6G. Therefore, the local government has realized that when the elderly 6E approaches the ascending staircase 6F or the descending staircase 6G, the smartphone of the elderly 6E is controlled and a voice warning is issued to warn him.

[0223] There are also electric poles 2A01, 2A02, and 2A03 on old man 6E's walking path 6H. Agents 2A11, 2A12, and 2A13 are deployed on electric poles 2A01, 2A02, and 2A03, respectively. The diagram shows a representative example of the configuration of one agent. Agents 2A11, 2A12, and 2A13 are deployed by local governments. Note that in town, the appearances of these agents 2A11, 2A12, and 2A13 may be billboards, signage, or road signs.

[0224] Server 7A has a database (table) 7A13 for the guidance system in its file section. Table 7A13 manages the device IDs of agents 2A11, 2A12, and 2A13 registered by the local government in the same group. The device ID of elderly person 6E's smartphone 4515 is registered in the same group as the device IDs of agents 2A11, 2A12, and 2A13 registered by the local government. This registration is also performed by the local government.

[0225] Now, suppose that old man 6E approaches the stairs leading up 6F. At this time, agent 2A11 and old man 6E's smartphone 4515 enter the same context area. Agent 2A11 recognizes smartphone 4515 (old man 6E) through broadcasts from agent 2A11 and smartphone 4515 (SC1 in FIG. 9B). Agent 2A11 also controls the output of a voice message to smartphone 4515 through the next broadcast (SC2 in FIG. 9B). The voice message might be, for example, "There are stairs leading up, please be careful, if you need help, please press the # button on your smartphone."

[0226] Agent 2A11 also transmits passing position data indicating that smartphone 4515 has passed agent 2A11's position to server 7A, and server 7A records the passing position data in the recording unit (SC3 and SC5 in FIG. 9B). The processing method at this time is the same as the method described in FIG. 8A.

[0227] Next, suppose that old man 6E moves and arrives near agent 2A12. Due to broadcasts from agent 2A12 and smartphone 4515, agent 2A12 recognizes smartphone 4515 (old man 6E) (SC6 in FIG. 9B). Agent 2A11 transmits passing position data to server 7A indicating that smartphone 4515 has passed the position of agent 2A12, and server 7A records the passing position data in its recording unit (SC7 and SC8 in FIG. 9B).

[0228] Assume that old man 6E continues to move and approaches descending stairs 6G. Agent 2A13 and old man 6E's smartphone 4515 then enter the same context area. Agent 2A13 recognizes smartphone 4515 (old man 6E) through broadcasts from agent 2A13 and smartphone 4515 (SC9 in FIG. 9B). Agent 2A13 then controls the output of a voice message to smartphone 4515 through the next broadcast (SC10 in FIG. 9B). The voice message might be, for example, "There are stairs leading down. Please be careful. If you need help, press the # button on your smartphone." Agents 2A11, 2A12, and 2A13 have the same configuration as agent 2000 shown in FIG. 4D, but further include speaker 2301, and these agents 2A11, 2A12, and 2A13 may output voice guidance.

[0229] Agent 2A13 also transmits to server 7A passing position data indicating that smartphone 4515 has passed the position of agent 2A13, and server 7A records the passing position data in the recording unit (SC11, SC13 in FIG. 9B).

[0230] The above system can monitor elderly people and guide them on walks. The location data recorded on server 7A can be accessed and checked by local governments or family members via smartphones. This monitoring and guidance system can be used by elderly people or their families by submitting a system usage notification to the local government.

[0231] The above system can easily be adapted for use as a route guidance system. Each time the smartphone 4515 (elderly man 6E) approaches an agent 2A11, 2A12, or 2A13, it can provide the elderly man 6E with voice instructions about the next landmark or direction. <Dating service> Fig. 10A is an explanatory diagram showing an example of an image when an embodiment of the present invention is applied to a dating detection system. Fig. 10B is an explanatory diagram showing the procedure for registering a device ID in the dating detection system. Fig. 10C is an explanatory diagram of the operation when a wristwatch 4520 and a pendant 4530 are located in the same context area and broadcast.

[0232] In Fig. 10A, node 4A00 is built into wristwatch 4520, and node 4D00 is built into pendant 4530. The configurations of node 4A00 and node 4D00 are as described in Fig. 6A and Fig. 6D.

[0233] Nodes 4A00 and 4D00 have the function of comparing the context received by broadcast with their own context. The situation data memory 4A15 stores their own context. This context is called a catch context. There may be one or more catch contexts. For example, relatively short catch contexts such as graduating from AAA school, hobby skiing, hobby tennis, etc. are desirable. Furthermore, these requirements can be set as logical AND (simultaneous fulfillment) or logical OR (either fulfillment).

[0234] When node 4A00 and node 4D00 receive each other's contexts by broadcast, they can compare the received context with their own catch context. This comparison is performed by the data processor 4A14 under the control of the control unit 4A16. If the received context and the catch context match, some kind of display or audio output is obtained from the wristwatch 4520 or pendant 4530.

[0235] When a user registers a catch context for the above-mentioned nodes 4A00 and 4D00, the procedure is as follows. First, the user accesses a specified server using a smartphone or personal computer. The user also sets the smartphone or personal computer to a state where it can communicate with its own node 4A00 or node 4D00 via short-range wireless communication.

[0236] Then, as shown in Figure 10B, registration software is downloaded from a specified server to a smartphone or personal computer. In other words, the smartphone or personal computer can read the dating service template and deploy the registration software. At this time, the node is linked to the smartphone or personal computer via short-range wireless communication, enabling mutual communication. The server accessed by the smartphone or personal computer is set to accept the entry of information by the dating service user, and the server begins managing the dating service template (SE0, SE1).

[0237] The user enters the device ID of the node 4A00 or 4D00 to be used and the context data for meeting matching (or catching) into blank spaces in the template and registers them (SE2, SE3). If multiple (e.g., two) pieces of context data are entered, an attribute input field for logical conditions such as "either one of them is sufficient" or "both must be satisfied" may be provided. Exclusive condition data may also be added as attribute information to the context (SE4). Furthermore, time limit data for the context data may also be added as attribute information. The time limit data may specify, for example, a period or time during which matching is accepted, or an end date and time (SE5). The user confirms the input data (SE6) and completes the operation. The data entered into the template (context data and attribute data) is then registered on the server and wirelessly transmitted directly from the smartphone or personal computer operated by the user to the wristwatch 4520 or pendant 4530, where it is recorded in the memory 4A15 of the node 4A00 or 4D00.

[0238] Therefore, the control unit 4A16 of the node 4A00 or 4D00 is provided with an application that links with a smartphone or a personal computer and communicates with them. The communication supported by this application may be any of short-range wireless communication, beacon communication, and the like.

[0239] Next, suppose that node 4A00 of wristwatch 4520 and node 4D00 of pendant 4530 encounter each other at the same time in the same context area. As shown in Figure 10C, node 4A00 and node 4D00 broadcast (SF0) and detect each other (SF1, SF11). Then, each node compares the context data it holds with the received context data to determine whether a match is established.

[0240] However, nodes 4A00 and 4D00 each determine whether the received context data contains matching exclusive data (SF2, SF12). If the received context data contains matching exclusive data, they suspend further processing and reception for a certain period of time. However, if the received context data does not contain matching exclusive data, they notify the user by display or audio (SF3, SF13).

[0241] The above-mentioned dating services can be used in a variety of ways, such as "a committee member of a class reunion who wants to meet other class reunion members" or "a person with a certain hobby who wants to meet someone with the same hobby."

[0242] In special cases, data may be compressed using a password. If a password is used between a first device of a first user and a second device of a second user, the users can register the password in advance on each device. This allows data received through communication between the first and second devices to be automatically decompressed on each device.

[0243] FIG. 11 shows an example in which an embodiment of the present invention is introduced into a building management system. 8A shows, for example, a company building with 1F to 4F floors. Employees can use elevator 8A1 to go from the 2nd to 4th floors. An agent 3000 is placed at reception counter 8A2, and this agent 3000 stores the ID of a smartphone 4581 (or an employee card) assigned to the employee in a context determination unit.

[0244] Now, assume that employee 6H comes to work, receives his / her smartphone 4581 at reception counter 8A2, and turns it on. Employee 6H is employed in the department on the third floor.

[0245] The smartphone 4581 and the agent 3000 then broadcast a beacon signal. The agent 3000 determines that employee 6H has arrived at work and turns on the lights 3LD1 to 3LD6 in the department where employee 6H is located. It also sends a control signal to air conditioners 3AC1 and 3AC2 to start the air conditioning. Meanwhile, the smartphone 4581 displays the employee's name and the destination floor, 3F, on the screen of its display.

[0246] When the employee gets on the elevator 8A1, the elevator 8A1 is controlled by the elevator control device 8A3 that has received a notification from the agent 3000, and moves to the third floor and stops there.

[0247] In the above description, the agent 3000 is placed at the reception counter 8A2, but it may also be placed inside the elevator 3000.

[0248] When the employee goes home, he or she turns off the smartphone 4581 and returns it to the designated position at the reception counter 8A2. This allows the agent 3000 to check the employee's arrival and departure times. This is because the agent 3000 can manage the times when the smartphone 4581 is turned on and off.

[0249] The building management system described above can reduce unnecessary power consumption by turning on and off lights and air conditioning units where necessary. It can also manage employee attendance.

[0250] FIG. 12A is an explanatory diagram showing an example in which an embodiment of the present invention is applied to a spatial environment detection system.

[0251] For example, a node 4C00 having a sensor 4A09 that detects CO2 is used. This node 4C00 may be located, for example, inside a bus 11A, a train 12A, an office 13A, an airplane 14A, a bar 15A, a hospital room 16A, or a restaurant 17A.

[0252] When a user with smartphone 4519 enters a bus 11A, train 12A, office 13A, airplane 14A, bar 15A, hospital room 16A, restaurant 17A, etc., a broadcast is made between node 4C00 and smartphone 4519. This communication allows the user to receive a CO2 status report (service information) for each environment from node 4C00. In other words, smartphone 4519 can receive a CO2 detection signal from node 4C00. If the CO2 detection signal is below the reference value, smartphone 4519 displays a message such as "Sufficient ventilation is maintained" on its display. However, if the CO2 detection signal does not meet the reference value, smartphone 4519 displays a message such as "Please ventilate the room."

[0253] The above shows an example of using a node with a CO2 sensor, but various sensors can be used depending on the environment and purpose of use. Types of sensors include, but are not limited to, illuminance sensors, temperature sensors, humidity sensors, gas sensors, odor sensors, gyros, altitude sensors, GPS, barometric pressure sensors, pressure sensors, water leak sensors, and dust detection sensors.

[0254] 12B shows another example of the configuration of node 4C00. This node 4C00 can receive detection values ​​from multiple sensors 4AS1, 4AS2, and 4AS3. The detection values ​​of sensors 4AS1, 4AS2, and 4AS3 can be received wirelessly or via a wired connection. In the case of wireless sensors, sensors that are already installed in the vehicle or aircraft are used.

[0255] The sensors 4AS1, 4AS2, and 4AS3 are selectively used from various types depending on the environment in which the node 4C00 is used.

[0256] Node 4C00 equipped with such a sensor can simultaneously acquire the location (GPS) inside the car or airplane, as well as temperature, air pressure, etc., and notify the smartphone 1519.

[0257] FIG. 13 is an explanatory diagram showing an example in which an embodiment of the present invention is used in a meeting system, group inspection system, customer flow line system, etc. at the entrance of an event venue or shopping mall. Visitors often meet near the entrance of the venue. Tourists in groups may also conduct group inspections. Furthermore, because the venue is large, individuals have great difficulty finding their reserved seats on their own.

[0258] 20A is an event venue where various events are held. The meeting system can be used by people with the same hobby, members of the same fan club, etc.

[0259] Finding friends, fan club members, alumni, etc. by meeting up can be realized, for example, by the methods described with reference to FIGS. 10A, 10B, and 10C.

[0260] A guide robot 21A is placed near the main entrance of the event venue 20A. The guide robot 21A has an agent 3000 built in, and is equipped with a beacon communication unit 235 and a network communication unit 236.

[0261] The network communication unit 236 of the guide robot 21A can communicate with a predetermined server 23A via the base station 22A.

[0262] Server 23A has a transceiver 23A1, a controller 23A2, and at least a reservation data file 23A3 for the event venue. Reservation data file 23A3 records reservation data for each user who owns smartphones 4510, 4511, and 4515. The reservation data may include, for example, the user's smartphone device ID, smartphone phone number, reserved seat data, reservation date, and user age.

[0263] Now, when each user approaches the robot 21A, a broadcast is executed between the smartphones 4510, 4511, 4515 owned by each user and the agent 3000 built into the robot 21A.

[0264] The agent 3000 then transmits the device IDs of the smartphones 4510, 4511, and 4515 to the server 23A via the network.

[0265] Here, it is assumed that the server 23A has reservation data for the event venue 20A for each of the smartphones 4510, 4511, and 4515. To this end, the server 23A detects the telephone numbers, reservation dates, and reserved seat data of the smartphones 4510, 4511, and 4515 from the reservation data.

[0266] Furthermore, when the server 23A detects the reserved seat data, it starts a guidance program from the entrance of the event venue (the position of the robot 21A) to the reserved seat. This guidance program always includes information about the location of restrooms, but may also include information about souvenir shops.

[0267] The guidance voice and flow line information (for example, on-screen route guidance information) from the above guidance program are sent via individual lines from server 23A to each of smartphones 4510, 4511, and 4515 via base station 22A. This system allows customers to reach their reserved seats without worry.

[0268] The above example describes a customer flow line system for the event venue 20A, but it goes without saying that this embodiment can be applied not only to the event venue 20A, but also to large shopping malls, department stores, airports, etc. In this embodiment, instead of reserved seats, the context of the product to be purchased, the exit number, the entrance number, etc. are set in the server.

[0269] Furthermore, when this system is used as a meeting system, the following considerations are taken into account: Assume that "artwork appreciation" is registered as context data, and "date," "meeting," "number of people in the group," etc. are registered as attribute information.

[0270] In such a case, the times at which multiple users in a group gather around the robot (context area) will differ from one another. Therefore, when agent 3000 communicates with an arriving node, it determines whether the attribute information contains at least the purpose description "meeting up" in addition to the context data "artwork appreciation." If the node has attribute information of "meeting up," agent 3000 determines whether a user with the same context matching relationship has already arrived. It also writes the device ID of the newly arrived user to the group memory. It then broadcasts the current number of people gathered (actually the number of nodes) to the node of the newly arrived user.

[0271] FIG. 14 shows another example of using the user area of ​​a beacon packet.

[0272] In the user area 23, as explained in FIG. 1, Bytes 7 and 8 describe a member ID (identification information of a user of an electronic device). Bytes 9 and 10 describe a module ID (identification information of a non-specific application). Byte 11 describes a frame type. As explained above, the frame type indicates the type of transmission.

[0273] Furthermore, bytes 12 to 31 are the parameter section (parameters: transmission information). The parameter section stores multiple parameters. Each parameter consists of a TL section and a VAL section. The TL section consists of one byte and is made up of a TYPE field and a LENGTH field. As explained above, the TYPE field distinguishes the type of data in the VAL section (there are int type, float type, and string type), whether it is int type, float type, or string type.

[0274] 14 shows another example of parameters (which may also be called data) described in the parameter section, but the format is not limited to this. The data area of ​​the parameter section includes a header area b, an information ID description area c, a control code description area d, a device ID description area e, and a data description area f.

[0275] A specific code for the parameter section is assigned to the header section b. The following information ID description section c describes identification data that indicates the type of information being sent (particularly the type of data in the data section). Examples of types include GPS information, sensor information, etc. Furthermore, like a file system, information on the number of bytes allocated to the description area for each type of data may also be included.

[0276] The node ID description area e contains identification data of the device that transmits this beacon packet 21, such as identification data that identifies a device such as an agent, a node, a smartphone, or a gateway.

[0277] The control code area d is used to notify, for example, when a new situation rule is registered, when there is a change in the situation rule, or when notifying the rule itself. The data description field e uses schema information corresponding to the context. In other words, codes with meanings pre-agreed between the sender and receiver are used. Depending on the type of context matching service used, raw context data may also be used.

[0278] The information in the above area is generally called attribute information. The attribute information is not fixed or limited. The attribute information basically instructs how to handle so-called context data. Therefore, for system operators, the format and content of the attribute information vary, but what is important is that the attribute information exists in this area.

[0279] The control code area d may include a usage period description area. The usage period description area describes the usage period (year, month, date, day of the week, time period) during which this service is available. This usage period information can be rewritten as needed by the system or user. For example, if a contract between a user of the sales promotion system (described in Figures 7A and 7B) and the system operator expires, the system may automatically delete the usage period. Also, if a product is sold out due to the use of the sales promotion system, the user can delete the usage period from the registration system using a template. Also, in the encounter detection system (described in Figure 10A), if encounter detection is realized, the user can delete the usage period from the registration system using a template.

[0280] Furthermore, depending on the environment in which the agent is used, there may be some agents for whom frequent matching notifications are desired depending on the "time period" or "day," and others for whom less frequent notifications are not required. In this case, the usage period description area d2 can be used as an information area for automatically controlling matching notifications for agents for whom frequent matching notifications are not required depending on the time period.

[0281] Therefore, the data indicating the usage period may also include identification data indicating the usage pattern. The context determination unit 1000 is configured to recognize this identification data, determine the usage pattern of the usage period (year / month / day, day of the week, time period), and control the agent accordingly.

[0282] The control code area d includes an area d3 that describes device IDs for which data transmission should be excluded or denied. This area d3 is used when the agents 2000 and 3000 thin out the device IDs to be transmitted each time they broadcast.

[0283] For example, if the context areas of two agents overlap, one node may receive matching reports from two agents.

[0284] For example, if context areas 10 and 20 in FIG. 2A overlap, nodes 4100 and 4400 ("Melon Bread Lovers Group") will receive a matching report of "Melon Bread Discount" from two agents 2000 and 3000. In such a case, the context determination unit 1000 can control the devices (4100 and 4400) sent by agents 2000 and 3000 so that they thin out the device IDs sent each time they broadcast. In this example, the device IDs sent by 4100 and 4400 are rejected once every two broadcasts. For example, area d3 describes the device ID to be rejected and the frequency of each broadcast (e.g., 1 / 2 in this example). If three context areas overlap, a frequency of 1 / 3 is described.

[0285] The transmission data processing programs in the agents are set so that the agents 2000 and 3000 specify this frequency under their own control based on a notification from the context determination unit 1000 (duplication elimination can be performed).

[0286] To achieve the above processing, the context determination unit 1000 must detect that the context areas 10 and 20 overlap. This detection is performed as follows. That is, when the agent 2000 notifies the status, the notification data includes the device ID of the agent 3000, and when the agent 3000 notifies the status, the notification data includes the device ID of the agent 2000. In such a case, the context determination unit 1000 determines that the context areas 10 and 20 overlap. The context determination unit 1000 then controls each of the agents 2000 and 3000 so that the frequency is set in the above-mentioned area d3.

[0287] Furthermore, the control code area d includes a description area for context data that is not to be used in the matching process. For example, the description area contains terms that are clearly offensive to public order and morals.

[0288] Furthermore, the control code area d has a description area for a flag indicating whether or not there is further data to be transmitted. For example, this description area may contain "end" or "continue." As mentioned above, in this system, there is a limit to the amount of data that can be transmitted in the parameter section in one beacon communication. Therefore, if the amount of data to be transmitted exceeds the data capacity that can be transmitted in one (current) beacon communication, "continue" is written in the description area d5. The subsequent data will then be sent in the next beacon communication.

[0289] As described above, by providing the file system area c and the attribute data description area d in the parameter section, it is possible to realize diverse and comprehensive beacon communication.

[0290] Furthermore, a description field for the password "Use" or "Not Use" may be provided within the control code field d. The password is a password agreed upon in advance by specific users (e.g., 6C1 and 6D1) who will be performing beacon communication. Users 6C1 and 6D1 pre-register a common password in the memory of the data processor of, for example, a smartphone-type node. Then, when users 6C1 and 6D1 set the password "Use or ON" on the menu screen, the password "Use" symbol is automatically written in the password presence / absence description field d6. In this manner, only users 6C1 and 6D1 can exchange information with each other through beacon communication. In other words, when parameters acquired through beacon communication are compressed using a password, each node uses the password to decompress the other using the device ID or context. However, when users 6C1 and 6D1 set the password "Not Use or OFF" on the menu screen, context matching processing becomes possible through normal beacon communication. In this case, the same operation as in the embodiment described above can be obtained.

[0291] 15 shows an embodiment in which the information processor of this system is further integrated with the ifLink (registered trademark) system. The information processor may be an agent or a node, and will be described here as an agent 3000.

[0292] Meanwhile, the inventors have already developed a method for utilizing a smartphone when connecting the ifLink (registered trademark) system to an IoT (Internet of Things) system. Therefore, this time, the inventors have developed a new system in which a smartphone-type agent 3000 is further decoded with the ifLink system.

[0293] 15 is equipped with an ifLink application 3201 and an IBI (ifLink Beacon Interface) microservice 3202. Based on the microservice, the IBI microservice 3202 can act as a bridge between the ifLink application 3201 and the various information processors described in the previous embodiments. Therefore, the IBI macroservice 3202 can read data sent in a beacon signal format and has schema information for converting the data into data used in the ifLink application 3201. Conversely, the IBI macroservice 3202 can also convert data used in the ifLink application 3201 into data in a beacon signal format using the schema information.

[0294] In the example shown in the figure, a sensor-integrated node 4C11 is connected to the agent 3000 via an IBI, and a smartphone-type node 4C12 is connected to the edge computer 3000 via an IBI.

[0295] Node 4C11 transmits different messages as service information to agent 3000 depending on whether the CO2 level is below a specified value or above the specified value. When the CO2 level is below the specified value, the message (service information) may say, for example, "Ventilation is being maintained adequately," and when the CO2 level is above the specified value, the message (service information) may say, for example, "CO2 levels are high. Please ventilate immediately." These messages are written as packet data in the memory of node 4C11.

[0296] However, as the telegram, it is not limited to the above telegram, and it may be a symbol or code determined in advance. And these symbols and codes may be interpretable by the ifLink app 3201. In such a method, the data volume of the beacon signal may be small, and the response language (character output or voice output) of the ifLink app 3201 can be set according to the language used by the user using the agent 3000.

[0297] The smartphone-type node 4C12 has, for example, an IBI library and is configured to convert the unique language of the smartphone into a type of language that the IBI microservice 3202 can understand and send it. In this case, the data used for this conversion is called schema information. Thus, the smartphone-type node 4C12 can easily set by downloading and obtaining an application that functions as an IBI library from a predetermined server for a general smartphone.

[0298] <Overview of the ifLink System> FIG. 16 is a diagram for explaining the overview of the ifLink system. By combining and using this ifLink system, the above-described broadcast system, and further the unicast system, various functions can be realized.

[0299] In the ifLink system, an IF-THEN rule is used. The IF-THEN rule is a rule in which a "promised item" or "determined item" corresponding to a "condition item" is set such that if a condition IF = A is satisfied, then an action THEN = B is activated.

[0300] <Overview within Server 17> Various IF-THEN rules are stored, for example, in the data section 1703 of the server 17. Various IF-THEN rules are managed by a rule manager 1702. The rule manager 1702 manages the creators of IF-THEN rules, the sale and rental of rules, their prices, etc., and also manages the acceptance of new rules and the disposal of old rules.

[0301] The rule charge management unit 1704 can manage users who use IF-THEN rules and issue rule usage fees to those users. It can also manage the period during which users use IF-THEN rules.

[0302] <Overview of Agent (or Node) 3000> If the agent 3000 is a smartphone type, it has a smartphone application 3106. It also has a display control unit 3107 and an operation control unit 3108. The operation control unit 3108 often uses a touch panel integrated with the display unit.

[0303] Furthermore, here, ifLink application 3201 is installed in agent 3000 and controls the entire system. IfLink application 3201 further includes IF-THEN engine 3100.

[0304] The system control unit 3105 controls the smartphone application 3201, display control unit 3107, operation control unit 3108, ifLink application 3201, IF-THEN rule storage unit 3100, etc., and adjusts and controls the control timing and operation timing of each unit.

[0305] The agent 3000 includes a transmitter 3001 and a receiver 3002 connected to the network NETW. The ifLink application 301 can access the server 17 via the transmitter 3101 and request a desired IF-THEN rule. The IF-THEN rule is given, for example, a name (an identification name such as the name of an available facility or system name) and is introduced in a catalog or the like. The user can download the desired IF-THEN rule via the receiver 3102 by inputting the desired identification name into an input screen.

[0306] The IF-THEN rules are stored in IF-THEN rule storage unit 3109 via rule management unit and control unit 3207. Some IF-THEN rules are single, but many are IF-THEN rule sets that are a collection of multiple rules.

[0307] Multiple IF-THEN rule sets are identified by rule set IDs. When the same rule set is retrieved from server 17, the rule management and control unit 3207 adjusts the rules so that the most recently added rule is valid. The user is notified via display control unit 3107 that the rule has been updated.

[0308] When the IF monitor 3206 receives the first "condition" from the IBI microservice 3202, the rule management and control unit 3207 provides the "condition" to the rule management and control unit 3207. The rule management and control unit 3207 then reads out the rule set that first includes the "condition" from the IF-THEN rule storage unit 3109 and sets it in the THEN execution management unit 3208.

[0309] The THEN execution management unit 3208 has already received the first "condition = IF" in the set rule set. Therefore, the THEN execution management unit 3208 provides a command for "activation = THEN" corresponding to this "condition = IF" to the JOB control unit 3209. The JOB control unit 3209 provides this command to the IBI microservice 3202. The IBI microservice 3202 transmits the "detection data" corresponding to the command to an IBI-compatible external device using a beacon signal.

[0310] This results in one job being executed, and the information is sent to the rule manager 1702 and / or the rule charging management unit 1704 via the log output unit 3210 and the transmission unit 3101 .

[0311] The above-mentioned "detection data" is transmitted to, for example, node 4C12 via beacon transmitting / receiving unit 3103. Beacon transmitting / receiving unit 3103 may be integrated with transmitting / receiving units 3101 and 3102 described above.

[0312] The agent 3000 described above includes not only the IBI microservice 3202 but also a microservice (MS) 3204 for individual devices and a microservice (MS) 3205 for web, so that it can communicate with various individual devices.

[0313] For this reason, when sending a command, the JOB control unit 3208 adds a code for specifying a microservice to the command. In other words, by selectively specifying the IBI microservice 3202, the microservice for individual devices (MS) 3204, or the microservice for Web (MS) 3205, it is possible to switch between sending and receiving destinations.

[0314] When configured in this way, it becomes possible to reflect the execution command of TEHN, which is the response of IF obtained by broadcast with the beacon signal, on the device connected to MS311 for individual devices or the device connected to MS for the web. The external command to MS3204 for individual devices will be given by unicast.

[0315] Conversely, it is also possible to reflect the execution command of TEHN, which is the response of IF obtained via MS3204 for individual devices or MS3205 for the web, on the device connected to IBI microservice 3202.

[0316] <Configuration example of IF-TEN rule> Figure 17 is a diagram showing a configuration example of the IF-THEN rule. It is a configuration example as an example for explaining the basic concept of the rule set. For example, it is assumed that the rule set 6010 has four rules from rule 1 to rule 4. In the figure, the IF devices are shown distinguishing the devices as IF1, IF2, IF3, ···, and the THEN devices are shown distinguishing the devices as THEN1, THEN2, THEN3, ···.

[0317] Rule 1 coordinates IF1 of the IF device and THEN1 of the THEN device, and when the condition of the IF device IF1 (hereinafter, "condition" means operating condition, detection condition, etc.) is satisfied, the THEN device THEN1 is activated (hereinafter, "activated" means response, or startup, or stop, etc.). Rule 2 is a rule in which when the conditions of IF2 and IF3 of the IF device are simultaneously satisfied, the THEN device THEN2 is activated. Rule 3 is a rule in which when the condition of the IF device IF4 is satisfied, the THEN devices THEN3 and THEN4 are activated. Rule 4 is a rule in which when the conditions of IF5 and IF6 of the IF device are simultaneously satisfied, the THEN devices THEN5 and THEN6 of the THEN device are activated.

[0318] Here, the overall attribute information 6011 of the rule set includes an outline of the rule set (can be written in text), rule set identification data, and rule set name (can be written in text). In this case, information (identification data) of the microservice corresponding to this rule set may also be present. In other words, the overall attribute information may specify a microservice that is prepared to reflect the rules of the rule set in an external device. Furthermore, rule set priority information, rule set validity / invalidity setting information, and rule set usage environment information may also be present.

[0319] The rule set priority information determines the priority of competing rule sets and may be included together with the identification data of competing rule sets. The rule set validity / invalidity setting information determines whether the rule set should function. Therefore, by combining this with the period information, the validity period or invalidity period of the rule set can be set. Furthermore, rule set usage environment information may be included. This information describes, for example, specific conditions (environmental conditions) for adopting the rule set. For example, the weather may be clear, or the rule set may be used in a special facility. The environmental conditions may be automatically entered by, for example, an edge computer that stores the rule set. Furthermore, attribute information of a specific usage environment, such as the facility, user, assignment, and GPS information, may be included. This usage environment attribute information may also be automatically entered by the edge computer that stores the rule set, or it may be entered externally by a user who owns the edge computer.

[0320] The attribute information of each individual rule 6012 (rules 1, 2, 3, ...) includes the rule name (which can be written in text) and rule identification data. This attribute information may also include rule priority information and rule valid / invalid setting information. As with rule set usage environment information, each rule may also have its own rule usage environment information. In this case, the rule usage environment information defines a subordinate concept of rule set usage environment information.

[0321] Furthermore, the attribute information of each IF device 6013 (IF1-IF6) includes the IF device name (which may be a sensor name or a service name) (can be written in text), the serial number of the IF device, an overview of the IF device (can be written in text), conditions, etc. As conditions, the range of the operation state (detection) of the IF device, thresholds, suppression time, individual parameters, etc. can be set.

[0322] The operating state (detection) range, for example, for a temperature sensor, is information that determines whether a detection output is transmitted when it detects a temperature between 20 and 25 degrees, whether a threshold is information that determines whether a detection output is transmitted when it detects a temperature of 30 degrees or higher, and whether a suppression time is information that determines how many seconds after detection the detection output is transmitted. With this attribute information, even if the detection output from the same IF device has different values ​​(different value ranges or thresholds), it is possible to specify different THEN devices according to the respective value ranges and thresholds. It is also possible to issue different control commands to the same THEN device according to the different values ​​input from the IF device, even for the same THEN device.

[0323] The IF device is basically a preceding element that first produces an action, and has attribute information including preceding element identification information such as at least a sensor name and a serial number.

[0324] Attribute information 6014 of each THEN device includes the THEN device name (which may be a sensor name or a service name) (can be written in text), the THEN device serial number, an overview of the THEN device (can be written in text), conditions, and the like.

[0325] Conditions that can be set include the THEN device's suppression time, sensor name, control target, individual parameters, etc. The suppression time is information that determines the number of seconds after receiving a detection notification from an IF device before starting a response, or the waiting time to determine whether the operating environment of other THEN devices (or other IF devices) is ready. The sensor name (also called ifparam) is the name or number of the IF device as the corresponding preceding element, and is information that can reliably link with the corresponding IF device. The control target refers to a specific part or switch within the THEN device. Describing the control target is useful when you want to control the current or voltage in the power-on state, rather than simply controlling the power on / off of the THEN device.

[0326] The individual parameters are information for generating specific control information, such as specific information for setting the operating range (for example, information for limiting the height in the case of drone control). The attribute information also preferably includes data identifying the microservice that outputs commands to external devices. This prevents the edge computer (e.g., 300) from inadvertently controlling devices in other areas. In other words, a microservice can identify the IF and THEN devices that it is responsible for, and therefore does not respond to or control the IF and THEN devices under the jurisdiction of other microservices.

[0327] The THEN device is basically a subsequent element that executes a subsequent action in conjunction with a previous preceding action, and has attribute information including subsequent element identification information such as at least a device name and a serial number.

[0328] Furthermore, the attribute information may also include "event-related information." Event-related information is a field for describing the device name, serial number, or summary of an IF device, for example, if the operation of a THEN device affects other IF devices. A summary of the impact may also be described using a string. For example, if the THEN device emits a specific sound, it may affect an unrelated IF device that acts as a sound sensor. Similarly, if the THEN device emits light, it may affect an IF device that acts as a light sensor. Knowing such cases in advance allows users to consider replacing the THEN device or IF device with a different sensor. Event-related information is predefined by, for example, a manufacturer that sells a rule set, but it can also be intentionally defined by users themselves on the edge computer. This enables a variety of uses for rule sets.

[0329] Each piece of attribute information is provided with attribute identification information (which may be called a header) for identification. The rule execution program can read the attribute identification information and determine the type of attribute and whether or not the attribute information is present. If the rule execution program determines that attribute information is described, it can check the attribute contents, but if it determines that attribute information is not described, it will skip checking the attribute information.

[0330] If there is no attribute identification information, the rule execution program judges the content of the attribute information in order according to the order of the attribute description symbols (e.g., deviceserial=, id=, etc.). For attribute information whose content is not determined, for example, 0000 is written in a predetermined data area following the attribute information header or attribute description symbol. In this case, the judgment and processing of the attribute information is ignored.

[0331] The attribute information may further include information indicating (or recommending) the space in which the rule set is used (scene information in which the rule set is adopted), information about the user who uses the rule set, a theme related to the rule set, etc. The scene information, user information, theme, etc. may be selectively described in the attribute information of the IF device and the attribute information of the THEN device.

[0332] <Further explanation of how beacon signals are used> Figure 18 shows an example of the configuration of the frame type shown in Figure 1. Using frame types makes it possible to enhance the content of mutual communications using beacon signals. Therefore, using frame types is effective when sending and receiving important context data.

[0333] The frame type consists of one byte and includes a REQ / RES flag indicating a request / response, a REPLY flag indicating whether a response to a command is required, and an actual command (COMMAND).

[0334] For example, in the case of transmitting a sensor value, a "request" is transmitting the sensor value from a smartphone app (which may also be called an individual app) of a smartphone-type information processor 500 to the IBI microservice 302, and a "response" is transmitting a message from the IBI microservice 302 to the smartphone app saying "Sensor value received." Bit 7 is a field for the REQ / RES flag, and if the transmission type is a request, the flag is set to 0, and if the transmission type is a response, the flag is set to 1. Bit 6 is a field for the REPLY flag; if no reply is required, the flag is set to 0; if a reply is required, the flag is set to 1. The commands for bits 5 to 0 are: 1: Device registration (unused), 2: Device registration result (unused), 3: Sensor value notification, 4: Job notification, 5: Job result notification.

[0335] Figure 19 shows an example of the setting value of the frame type in Figure 18. For example, the frame type of a sensor value response (response not required) is 0x03. The frame type of a sensor value response (response required) is 0x43. An example of a sensor value notification is the transmission of a sensor value from a smartphone app (individual app) as a sensor to the IBI microservice 302.

[0336] The setting value of the frame type of the sensor value response is 0xC3. An example of a sensor value response is a sensor value notification (response required) in which the IBI microservice 302 sends a response stating "sensor value received" to the smartphone app as the sensor.

[0337] The frame type setting value for a job notification (no response required) is 0x04. The frame type for a job notification (response required) is 0x44. An example of a job notification is sending an instruction such as "Please perform XX operation" from the IBI microservice 302 to a smartphone app as a THEN module.

[0338] The frame type for a job result notification is 0xC4. An example of a job result notification is a response sent from a smartphone app (as a THEN module) to the IBI microservice 302 stating, "XX operation has been performed." <Schema information example> 20 shows an example of schema information according to an embodiment. First, this information describes device names that the IBI can support. In this example, for example, device names SampleDevie1 and SampleDevie2 are described.

[0339] The device name SampleDevie1 corresponds to, for example, the first smartphone, and the device name SampleDevie2 corresponds to, for example, the second smartphone. Schema information is written following each device name.

[0340] The properties include the device name, device serial number, timestamp, member ID, module ID, parameter 1 (param1) to parameter 4 (param4). The device name SampleDevie1 is Figure 21 shows an example of parameters in a beacon packet for sensor value notification. However, here we will explain the basic transmission pattern of context data.

[0341] For example, the parameters (which may be referred to as context data) used when notifying sensor values ​​are stored in the beacon packet in this order: parameter 1 to parameter 4. In this example, 0x20 in byte 12 indicates that the first parameter (param1) is an int type, 1 byte, and byte 13 indicates its value (0). 0x43 in byte 14 indicates that the next parameter (param2) is a float type, 4 bytes, and bytes 15 to 18 indicate its value (1.2). In this example, the individual application 34 has two sensors, for example, a temperature sensor and a humidity sensor, and the sensor values ​​are stored in param1 and param2, with param1 indicating the temperature and param2 indicating the humidity. The number of parameters is not limited to four and can be varied depending on the data to be transmitted.

[0342] A power supply system may be provided in the various information processors described above. In the case of smartphones, a charger is already provided. However, in the case of simple information processors, it is necessary to secure a power source when the power supply voltage drops. For this purpose, accessories such as a solar power generator, a piezoelectric power generator, or a vibration power generator may be added to the power supply unit. Furthermore, data in the user area may be encrypted or compressed using a password.

[0343] As described above, each embodiment and combinations thereof include various inventions.

[0344] 22 to 32 each show the basic configuration of an embodiment, and show only the parts with special features. The same components as those explained so far are given the same reference numerals, and duplicate explanations will be omitted. Here, agents 2000 and 3000 are assumed to be first information processors, and nodes 4100-4400 are assumed to be second information processors. Then, 22 includes first information processors 2000 and 3000 that register a first context in a context determination unit 1000, and second information processors 4100-4400 that register a second context in the context determination unit 1000. The first information processor and the second information processor perform beacon communication with each other, and each processor includes a determination unit that determines context-related information included in a beacon packet, and when the determination result data indicates that the first context and the second context are in a matching relationship, the first information processor comprises a data processor that processes the result data as node notification data; The information processing system is characterized in that the second information processor includes a data processor that processes the result data as output data for user notification (display, sound, or vibration).

[0345] 23 shows the basic configuration of yet another embodiment. In this embodiment, context determination units 1000A and 1000B are disposed in agents 2000 and 3000, respectively. Context determination units 1000A and 1000B are connected to server 7A via network NTW, and each can download and use the necessary software. When registering profile information, a user can also specify the context determination unit (or agent) to register.

[0346] 24 shows the basic configuration of yet another embodiment. In this embodiment, context determination units 1000A and 1000B are arranged in agents 2000 and 3000, respectively, and a context determination unit 1000C is arranged outside the agents (for example, on a server).

[0347] In this case, the usage method described in Fig. 2B is possible. Also, depending on the scale of the amount of data handled by the agent, it is possible to selectively use the external context determination unit 1000C and the context determination unit 1000A or 1000B within the agent. For example, a store that sells a small number of items would use the context determination units 1000A and 1000B within the agent, while a shopping mall that sells a large amount of products would use the external context determination unit 1000C.

[0348] FIG. 25 shows the basic configuration of yet another embodiment, highlighting specific features. In addition to the embodiment of FIG. 22, the system is accessible by a rule setter (a person, business operator, etc.) 5500 who sets situation rules. The rule setter 5500 operates a context scheme and rule setting system 5000. The context scheme and rule setting system 5000 is connectable to a context determination unit 1000 and designs and sets user service forms by setting situation rules that form matching relationships. Examples of service forms include the monitoring service and sales promotion service described above. The context scheme and rule setting unit 5000 has input units for at least a context and a device ID as elements for setting situation rules. In this example, situation rules are set for each agent 2000, 3000 via a context determination unit 1000 external to the agent.

[0349] Figure 26 is an example in which situation rule setting is performed directly in the situation rule setting section within the agent, as opposed to the type in Figure 25. However, information for setting situation rules may be sent to each agent 2000, 3000 via the server 7A.

[0350] Fig. 27 shows an example in which, in addition to the embodiment of Fig. 22, an information registration system 6000 into which a user actually inputs profile information is added, and which can be connected to the context determination unit 1000. That is, in this example, it is possible to preset profile information including the device IDs of the first information processor and the second information processor, and their respective context data, which are specific determination elements of the matching relationship.

[0351] Fig. 28 shows an example in which an information registration system 6000 for inputting profile information is directly connected to a context determination unit 1000A or 1000B in an agent in addition to the embodiment of Fig. 22. In this case, the profile information may also be sent to each agent 2000, 3000 via a server 7A.

[0352] 29 shows an example in which, in addition to the embodiment of FIG. 22, a provision information input system 7000 can be connected to the context determination unit 1000. This provision information input system 7000 is an input system that pre-enters result data (data on the context content to be provided to the other party) to be provided to the information processor that will be in a matching relationship. For example, the information includes information such as "discount on melon bread."

[0353] Fig. 30 shows an example in which a provision information input system 7000 for inputting provision information is directly connected to a context determination unit 1000A or 1000B in an agent in addition to the embodiment of Fig. 22. In this case, the provision information may also be sent to each agent 2000, 3000 via a server 7A.

[0354] FIG. 31 shows an example in which transmission management systems 9000A and 9000B are connected to the context determination unit 1000 in addition to the embodiment shown in FIG. 22. The transmission management systems 9000A and 9000B can control the transmission mode of each agent 2000 and 3000 by using one of the following methods: transmission frequency, exclusive control, and duplicate elimination. This is particularly effective when the context areas of the agents 2000 and 3000 partially overlap. In the example shown, for example, the agents 2000 and 3000 report information such as "red wine discount" to nodes 4200 and 4300. In this case, the job information of the agents 2000 and 3000 includes one extra advertisement in their advertising performance counts. This means that, for example, if a rule setter (or system administrator) were to charge the agents 2000 and 3000 for the successful execution of an advertisement, they would be overcharged.

[0355] Therefore, when the nodes 4200 and 4300 are included in the job information of both the agents 2000 and 3000, the transmission management systems 9000A and 9000B take the following measures, for example: For example, they may halve the charges, or reduce the beacon transmission frequency of the agents 2000 and 3000 to distribute the charges evenly.

[0356] FIG. 32 shows an example in which, in addition to the embodiment of FIG. 22, a provision information input system 7000 for inputting provision information is directly connected to the context determination unit 1000A or 1000B in the agent.

[0357] The transmission management systems 9000A and 9000B may be capable of controlling the transmission output power of the agents 2000 and 3000. For example, control may be performed to increase the output power of transmission power for a specific agent depending on the date or time of day. This control is possible, for example, if the automated marketing operator requests the system administrator in advance. When the output power of transmission power is controlled, the range of the context area can be expanded or reduced. This is particularly effective when conducting sales promotions. The operators of the transmission management systems 9000A and 9000B may also charge the agent administrator.

[0358] <The above-described embodiments include various inventions, and the basic configurations of each invention are summarized below.> A1] The registration system (including at least the information registration system 6000) registers a context indicating at least the needs or requests of each of a plurality of information processors (agents 2000, 3000, nodes 4100-4400) in a registration unit (context determination unit 1000), A context matching related information processing system or information processing device, wherein the transmission / reception system (transmission / reception unit 1100, transmission / reception units of agents 2000 and 3000) exchanges information with the registration system, recognizes the multiple information processors when the multiple information processors are simultaneously present in the same communication environment, and, when the registration system determines that the contexts are in a matching relationship between the multiple information processors, transmits information indicating the matching relationship to the multiple information processors.

[0359] A2] Furthermore, the above-mentioned context matching-related information processing system or the above-mentioned information processing device may include a server or an agent that performs context matching. The information processing device may also include a part or the whole of the registration system. The above-mentioned types of information processors may include a type that has a sensor, a type that is connected to a sensor, a type that has a display, or a type that has an audio output device. <Receiving side (agent or node) series> B1] This is used in a system that broadcasts a packet as a beacon signal, which includes a header area (22) containing communication standard data and a user area (23) in which the device ID and context data being used can be written, a device (2000, 3000) that receives the beacon signal, and when it acquires detection data indicating that the received data in the user area corresponds to context data set by the device, outputs service information corresponding to the context data; A service information receiving device is provided, which includes a receiving unit (2300, 2301) for the beacon signal, a detecting unit (2304) for obtaining the detection data, and an output unit (2307) for outputting the service information according to the context data when the detection data is obtained.

[0360] B2] A receiving device for service information as described in B1 is provided, wherein the detection data indicating that the received data in the user area corresponds to the context data set by the device itself is detection data obtained from an external context matching node (with advanced matching judgment) 1000.

[0361] B3] There is provided a receiving device for service information described in B1, wherein the detection data indicating that the received data in the user area corresponds to the context data set by the device itself is detection data obtained by processing of a control unit of the device itself (an agent or PC having matching firmware, 2304, 2305, 2306).

[0362] B4] The detection data indicating that the received data in the user area corresponds to the context data set by the device itself is detection data obtained by the control unit of the device using data in a replaceable memory as the context data set by the device itself (the device's context data can be stored in a replaceable memory (2305) and compared with the received context data: memory chips for data of various genres can be replaced), and a receiving device for service information as described in B1 is provided.

[0363] <Configuration of the convenience store agent with a transmitter and receiver... using the examples of melon bread and red wine> C1] It is used in a system that broadcasts a packet as a beacon signal, which includes a header area including communication standard data and a user area in which the device ID and context data being used can be written, A service information transmitting and receiving device is provided, which includes a transmitting unit that transmits a beacon signal of the device itself, a receiving unit that receives a beacon signal of another device, and a control unit that receives the beacon signal of the other device, and, if the received data in the user area of ​​the other device is detection data indicating that the data corresponds to context data set by the device itself, transmits (notifies) data via the transmitting unit to cause the other device to output service information corresponding to the context data set by the device itself.

[0364] C2] There is provided a service information transmitting device as described in claim C1, wherein the detection data indicating that the received data in the user area of ​​the other device is in the corresponding relationship with the context data set by the own device is detection data obtained from an external context matching node (a node with advanced matching judgment: a server).

[0365] C3] There is provided a service information transmitting device as described in claim C1, wherein the data for outputting the service information in the other device is data describing the content of the service information in the user area of ​​the beacon signal of the own device (for example, a discount on melon bread, or a coupon).

[0366] C4] There is provided a service information transmitting device as described in claim C1, wherein the detection data indicating that the received data in the user area of ​​the other device is in the corresponding relationship with the context data set by the own device is detection data obtained by processing of the control unit of the own device (in the case where the own device is an agent or PC having matching firmware). <Contents of the transmission and reception system> D1] This is used in a system that broadcasts a packet as a beacon signal, which consists of a header field containing communication standard data and a user field in which the device ID and context data being used can be written, The transmitting device includes a transmitting unit that transmits the beacon signal of the device itself, a receiving unit that receives the beacon signal of other devices, and a control unit that, when obtaining detection data indicating that the data of the user area of the other device received is in a corresponding relationship with the context data set by the device itself, transmits, via the transmitting unit, data for causing the other device to perform an operation according to the service indicated by the context data set by the device itself. It is provided with The receiving device as the other device is a device that receives the beacon signal from the transmitting device and detects the data for obtaining the service, and includes a receiving unit for the beacon signal a detection unit for obtaining the data, and an output unit for performing an output according to the service indicated by the context data of the device itself when the data is obtained. A service information transmission and reception system is provided.

[0367] <Linkage with the <ifLink system>> E1] It includes IF data as a condition and THEN data for responding to the condition, and a rule set for obtaining the THEN data when the IF data is given is defined. An IF-THEN engine for setting the rule set a plurality of microservices including an IBI microservice and a microservice for individual devices that give a command for instructing a specified "JOB". The IBI microservice is connected to a beacon transceiver The beacon transceiver is a transceiver that broadcasts, as a beacon signal, a packet composed of a header area including communication standard data and a user area in which the device ID and context data being used can be written. A transmission and reception device that enables broadcast of a beacon signal and unit cast using the microservice for individual devices is provided.

[0368] <00,01359><Basic system> F1) A first information processor that registers a first context in a context determination unit, a second information processor that registers a second context in the context determination unit, and the first information processor and the second information processor perform beacon communication with each other; a determination unit that determines context-related information included in a beacon packet, and if the result data of the determination indicates that the first context and the second context are in a matching relationship, the first information processor comprises a data processor that processes the result data as node notification data; There is provided an information processing system, wherein the second information processor comprises a data processor that processes the result data as output data for user notification (display, sound, or vibration).

[0369] F2) In addition to F1), the device can be connected to the context determination unit; A situation setting system for designing a user service form by setting a situation that will result in the matching relationship, There is provided an information processing system comprising a situation setting system that is provided with an input unit for at least a context and a device ID as elements for setting the situation.

[0370] F3) In addition to F1), the context determination unit: An information processing system is provided, characterized in that it is possible to connect a profile information input system for pre-setting profile information including the device IDs of the first information processor and the second information processor, and their respective context data, which are specific determination factors for the matching relationship.

[0371] F4) In addition to F1), the device can be connected to the context determination unit; a provision information input system for inputting in advance that the result data to be provided to the information processor in the matching relationship is data of context content to be provided to the other party; An information processing system is provided.

[0372] F5) In addition to F1), an information processing system is provided, further comprising a transmission management system connectable to the context determination unit and inputting transmission management information into the context determination unit, the transmission management information specifying one of transmission frequency, exclusive control, and duplicate elimination as a method of sending the context-related information.

[0373] The above-mentioned device also has characteristics in terms of categories such as a transmission method, a reception method, and a transmission / reception method. The above-mentioned device also has characteristics in the categories of transmission method, reception method, and transmission / reception method. The following are the claims as filed in this application. [1] a first information processor that registers a first context in a context determination unit; a second information processor that registers a second context in the context determination unit; the first information processor and the second information processor perform beacon communication with each other; a determination unit that determines context-related information included in a beacon packet, and if the result data of the determination indicates that the first context and the second context are in a matching relationship, the first information processor comprises a first processor that processes the result data as node notification data; the second information processor includes a second processor that processes the result data as output data for user notification; An information processing system comprising: [2] The information processing system according to claim 1, wherein the node notification data is data for providing a coupon to the second information processor. [3] The context determination unit is connected to the first information processor via the Internet. 2. The information processing system according to claim 1. [4] The context determination unit is built into the first information processor. 2. The information processing system according to claim 1. [5] The information processing system of claim 2, 3 or 4, wherein the context determination unit performs a matching process between the first context and the second context sent from the first information processor, the second information processor, and the third context and the fourth context sent from another third information processor, a fourth information processor, and is provided with a table that classifies the device ID of each information processor for each context. [6] The context determination unit is configured to be able to register a first context of the first information processor; the context determination unit is capable of registering a second context of a second information processor; When the first information processor and the second information processor perform beacon communication with each other, a determination unit determines context-related information included in a beacon packet; If the determination result data indicates that the first context and the second context are in a matching relationship, the first information processor processes the result data as node notification data; the second information processor processes the result data as output data for user notification; An information processing method comprising: [7] An information processing device that registers a first context in a context determination unit and operates as an agent, When another information processing device that has registered a second context in the context determination unit is within a communication area, the information processing devices perform beacon communication using beacon packets with each other; When the context-related information obtained from the context determination unit indicates that the first context and the second context are in a matching relationship, An information processing device characterized in that the result data is processed as node notification data. [8] The node notification data is data for providing a coupon to the other information processor. 8. The information processing device according to claim 7. [9] An information processing device as described in claim 7, wherein the predetermined context determination unit is provided in an external server.

[10] An information processing device as described in claim 7, wherein the predetermined context determination unit is provided inside the device itself. [Explanation of symbols]

[0374] 10, 20... Context area, 21... Beacon packet, 23... User area, 1000... Context determination section, 1100... Transmitting / receiving section, 1200... File section, 1201···Table, 1300···Situation matching processing unit, 2000, 3000···Agent, 2001, 3001···Sub-table, 4200, 4300, 4400···Node, 5000···Situation setting system, 5500···Rule setter, 6000...Information registration system, 6500...Users who want information, 7000...Information input system, 7500...Users who provide information, 9000...Transmission management system, 9500...System administrator.

Claims

1. a first information processor that registers a first context in a context determination unit provided in the server; a second information processor that registers a second context in the context determination unit; the first information processor and the second information processor perform beacon communication with each other; If the first context and the second context include a common word, which indicates a matching relationship, the first information processor includes a first processor that outputs result data indicating the matching relationship to another information processor as node notification data for providing a coupon; the second information processor comprises a second processor that receives the node notification data and processes the node notification data as a coupon; the first information processor comprises means for counting IDs of the second information processor and the other information processor with which the matching relationship has been established, and transmitting the counted number of IDs (number of devices) to the server; the server includes means for notifying the first information processor of the number of coupons to be issued based on the node notification data; Furthermore, the context determination unit forms group data including IDs of the first information processor and the second information processor in a group of contexts in the matching relationship at the time of the registration, the first information processor receives the group data in advance from the context determination unit of the server, and the determination of the matching relationship in the beacon communication is performed within the first information processor; An information processing system comprising:

2. An information processing system as described in claim 1, wherein the second information processor is a smartphone.

3. The information processing system described in claim 1, wherein the first information processor is a gateway installed in a signage, a convenience store, a department store, or a factory.

4. a first information processor that registers a first context in a context determination unit provided in the server; a second information processor that registers a second context in the context determination unit; an information processing method in which the first information processor and the second information processor perform beacon communication with each other, If the first context and the second context include a common word, which indicates a matching relationship, the first information processor outputs result data indicating the matching relationship to another information processor as node notification data for providing a coupon; the second information processor receives the node notification data and processes the node notification data as a coupon; the first information processor counts IDs of the second information processor and the other information processor with which the matching relationship has been established, and transmits the counted number of IDs (number of devices) to the server; the server notifies the first information processor of the number of coupons to be issued based on the node notification data; Furthermore, the context determination unit forms group data including IDs of the first information processor and the second information processor in a group of contexts in the matching relationship at the time of the registration, the first information processor receives the group data in advance from the context determination unit of the server, and the determination of the matching relationship in the beacon communication is performed within the first information processor. An information processing method comprising:

Images