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 an information processing method, and further relates to an information processing device, a receiving method, a transmitting method, a server, and the like. [Background technology]

[0002] Generally, there are the following methods 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 URL (Uniform Resource Locator) according to needs, or clicks on a commercial screen displayed on the screen, and establishes 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 a user obtains some service information is by operating a PC or smartphone according to "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 above "user-initiated" method. One such special case is when a specific organization (e.g., a public specialized organization such as the Japan Meteorological Agency) issues an "emergency notification" all at once when an earthquake or other event occurs. With this method, the recipient (user) is not identified, and the users receive the information all at once on their smartphones. The provision of such information is meaningful to the user. On the other hand, there are also communication systems that send various types of service information (such as commercials that the user does not intend to receive) to the user's smartphone or PC, and with these communication systems, the user is often provided with service information that he or she is not interested in.

[0005] As mentioned above, many conventional service information provision systems are based on a "user-driven" approach, and provide service information in response to the user's specific "needs" or "requests." 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 alerts," are limited to special cases and can be said to 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] JP 2021-111164 A [Patent Document 4] 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 noted that opportunities to provide a user with service information that responds to a user's "needs" or "requests," or for a user to receive service information, often arise even at times when the user is not explicitly aware of their "needs" or "requests."

[0008] This timing 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 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, the "multiple states" can be various states depending on the purpose of the service. Representative 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 based on a situation or situation rule (hereinafter, tentatively referred to as a "situation-driven" or "situation rule-driven" manner).

[0011] In a first aspect of the embodiment, an object is to provide a context matching related information processing system that enables 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 registering a first context in a context determination unit and a second information processor registering a second context in the context determination unit are provided, and the first information processor and the second information processor perform beacon communication with each other and include a determination unit for determining context-related information included in a beacon packet.

[0013] Here, when indicating that the first context and the second context are in a matching relationship, the first information processor includes a first processor that processes the result data of the matching relationship as coupon issuance data; the second information processor includes a second processor that receives the coupon issuance data and processes the coupon as a received coupon; the first information processor includes a means for transmitting the issuance status of the coupon issuance data to the server; The server manages the coupon issuance data sent from a plurality of information processors and includes a management means for managing at least the number of coupons issued. An information processing system is provided.

[0014] According to another embodiment, the context may be pre-coded. [Brief description 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 a configuration example of 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. [Diagram 3] FIG. 3 is a diagram showing a configuration example of an embodiment in which various setting functions are further added to the embodiment of FIG. 2A and FIG. 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 the 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 the 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 a 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 FIG. 2A and FIG. 2B. [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 a 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 integrated 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 a configuration of an IF-THEN rule. [Figure 18] FIG. 18 is a diagram showing an example of a configuration of a frame type shown in FIG. [Figure 19] FIG. 19 is a diagram showing an example of setting values ​​of the frame type in FIG. [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 parameters area in a beacon packet for notifying a sensor value. [Figure 22] FIG. 22 is a configuration diagram showing a basic configuration of one embodiment. [Figure 23] FIG. 23 is a configuration diagram showing a basic configuration of another embodiment. [Figure 24] FIG. 24 is a configuration diagram showing a basic configuration of another embodiment. [Diagram 25] FIG. 25 is a configuration diagram showing a basic configuration of another embodiment. [Figure 26] FIG. 26 is a configuration diagram showing a basic configuration of another embodiment. [Figure 27] FIG. 27 is a configuration diagram showing a basic configuration of another embodiment. [Figure 28] FIG. 28 is a configuration diagram showing a basic configuration of another embodiment. [Figure 29] FIG. 29 is a configuration diagram showing a basic configuration of another embodiment. [Diagram 30] FIG. 30 is a configuration diagram showing a basic configuration of another embodiment. [Diagram 31] FIG. 31 is a configuration diagram showing a basic configuration of another embodiment. [Diagram 32] FIG. 32 is a configuration diagram showing a basic configuration of another embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, the embodiments will be described with reference to the drawings. Although several embodiments of the present invention will be described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These new embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims. Furthermore, even if each component of the claims is expressed by dividing the components, or expressing a plurality of components together, or expressing them in combination, it is within the scope of the present invention. In addition, a plurality of embodiments may be combined, and examples composed of this combination are also within the scope of the invention.

[0017] In addition, in order to clarify the description, the drawings may be schematic in terms of the width, thickness, shape, etc. of each part compared to the actual embodiment. The device of the present invention is also applied when the claims are expressed as control logic, when expressed as a program including instructions for causing a computer to execute the program, and when expressed as a computer-readable recording medium containing the instructions. In addition, 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. The device is made up of a semiconductor chip, has an input section for sensor signals, and includes a transmitter that transmits the 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 input 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 an external appearance composed of hardware blocks and is configured as a gateway, and includes the gateway having a function of performing short-range wireless communication and a function of being connectable to a network. Also includes the gateway when it acts as an agent. This also includes smartphones that have the appearance of a smartphone and have a simple notification function, a simple receiving function, or function as an agent. Regardless of the 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, a 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, of which three are used as advertising channels. These advertising channels are used to transmit advertisement packets, and transmit data to inform the surrounding area of ​​the device's presence. The advertising interval time is between 20 ms and 10.24 ms. Advertising broadcasts a beacon signal carrying an advertisement packet on each of the three configured channels.

[0020] There are various types of information processors equipped with communication functions, including those that can be connected 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 the user can use as desired."

[0022] In addition, the information processor may be configured not only as a beacon device with a simplified configuration, but also as a composite chip or a composite device combined with a sensor, or as a part thereof. Furthermore, the information processor may be configured as a composite device or a composite system combined with a smartphone as a beacon module, or as a part thereof. Furthermore, the information processor may be configured as a composite device or a decryption 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 the advertisement packet can be effectively applied to the above-mentioned combination chip, combination device, or combination system. <beacon packet> As shown in Fig. 1, a beacon packet 21 in a common format used by the above information processor is shown. The beacon packet 21 is composed of 32 bytes, with a header area 22 of 7 bytes and a user area 23 of 25 bytes. The user area 23 includes an application ID / service ID area 24 and a communication data section 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 as an application ID or a service ID in whole or in part.

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

[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 for identifying 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] A service ID is described in bytes 9 to 10 (the area of ​​code 24b). In this service ID, a module ID (identification information of a non-specific application) is described. A module ID is internal identification information of a program module for each company or organization. For example, when multiple individual applications of a certain company or organization are installed in a user's smartphone, a module ID can be assigned to each individual application so that the data structure of these applications can be identified.

[0027] Byte 11 (area marked with symbol 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 indicating whether a response is requested or not to the other party. Examples of commands include notifying a sensor value, notifying a JOB, and notifying the JOB results. This ensures that mutual communication is carried out reliably.

[0028] Bytes 12 to 31 (area marked with 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 consists of a TYPE field and a LENGTH field. The TYPE field distinguishes the type of data in the VAL section (there are int type, float type, and string type) as int type, float type, or string type (distinguished by a preset hexadecimal number). The LENGTH field indicates the data length of the data in the VAL section (shown by a preset 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) describes the control code, Bytes 17-31 (area 25d) describes the data portion (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 a device such as an agent, a node, a smartphone, or a gateway.

[0031] The information ID indicates the type of information being sent. Examples of the type include 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 previously agreed upon 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 above attribute information is not fixed and is not limited. The attribute information basically instructs how to handle so-called context data. Therefore, for system operators, the format and contents of the attribute information are various, and 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, the data may be compressed using a password. When 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 the beacon communication between the first device and the second device to be automatically decompressed. <Overview of operation of 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 person who wants information, or a party that wants assistance in providing information) is assumed to have a second information processor (node).

[0036] Now, assume that a service requester (shop) 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 (e.g., "I like melon bread") in a context determination unit (a register described later).

[0038] Furthermore, suppose that the first information processor (hereinafter, agent) registers the context data "Melon Bread Discount Coupon" in the context determination unit (register, which will be 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 (discount on melon bread) and the keyword (melon bread) of (melon bread lover) are in a matching relationship. The context determination unit then manages the device ID1 of the first node and the device ID2 of the second node as being in the same group, with the keyword (melon bread) of the context data being the common word. In other words, the first node and the second node are linked together. At this time, the agent is also linked to the first node and the second node, with "melon bread" being the common word, and grouped together.

[0041] An agent can receive device ID1 and ID2 of nodes in the same group from the context determination unit. Now, assume that a first node (owned by a customer) enters the agent's communication area and broadcasts. In this case, since the first node is not an agent, 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, and is therefore able to 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 data for the "Melon Bread Discount Coupon" is written in the data section and sent. This data (i.e., the context) may be coded (e.g., converted into a context number), which is possible if the system possesses 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 specified 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 specified 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 assist (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, the agent detects that a predetermined situation rule has occurred within its own communication area when it detects the device ID1 of the first node from the received signal. In other words, the agent (first information processor) can determine that the first node (second information processor) is in a predetermined position (within the communication area), that the relationship with the first node (second information processor) is in a context matching state, and that a first node (second information processor) exists other than the agent (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 has been 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). In addition, it may simply transmit "Matching" or voice data as a comment.

[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 the 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 description 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 described below. <Basic configuration and functions of information processing system 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 broadcast. 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 integral part of the device ID of the agent 3000. Alternatively, the signage 4400 may be set as a node that performs broadcasting.

[0053] The agents 2000 and 3000 are realized, for example, by a gateway, a smartphone, a personal computer (PC), a tablet PC, etc. The installation locations of the agents 2000 and 3000 can be various locations, for example, a supermarket, a convenience store, a department store, an office, a restaurant, inside a factory, inside a car, inside a hospital, inside an aircraft, along a road, etc. The installation locations also include "objects" such as lighting fixtures, televisions, signage, pedestrian crossing signals, electric poles, streetlights, etc.

[0054] The nodes 4100, 4200, 4300, etc. are, for example, portable devices such as smartphones, personal computers (PCs), tablet PCs, accessories, watches, 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 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 at 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] In addition, the agent and multiple nodes can be mounted or attached to a moving object, and can be used in a system that recognizes each other when a node enters the context area of ​​the agent.

[0057] The agents 2000 and 3000 can communicate with the context determination unit 1000 to transmit 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 a 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 arranged in a cloud as a server, 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 an input / output unit of the agent by internal wiring (including a semiconductor board or a flexible board) 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 who uses the agents 2000, 3000, the 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 "I like melon bread" as context data, and the user of node 4200 registers "unsold melon bread" as context data, 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, it is assumed that the following registration is made to the file unit 1200. It is assumed that the user (customer) of node 4100 and the user (store) of node 4200 have registered "melon bread lover" and "unsold melon bread", respectively. It is also assumed that the agent 2000 has registered a context called "melon bread discount coupon" 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 ID and node ID (hereinafter collectively referred to as device ID) for each context by a context matching process, and forms a device ID group for each context (i.e., keyword). This group data is stored in a table 1201.

[0065] In the example of 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 is 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, the table is updated once or several times a day depending on the registered context contents (the number of update processes can be changed separately by the system administrator). Newly registered data is temporarily stored in a buffer memory (not shown) until it is updated.

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

[0069] Furthermore, when 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 in 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 in FIG. 2B).

[0070] Furthermore, the store node 4200 and the agent 2000 in the context area 10 in particular are in a close relationship, and information such as the number of products sold and the selling price obtained at the store node 4200 is always notified to the corresponding agent 2000 as a job. Similarly, the store node (signage) 4400 and the agent (store) 3000 in the context area 20 in particular are in a close relationship, 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 with each other by broadcasting, so that a command to "conduct advertising" may be given from the agent 3000 to the node 4400.

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

[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 timing on the node (signage) 4400.

[0073] These actions, such as the fact of sending a discount coupon by the agent 2000 and the fact of advertising on the signage by the agent 3000, are subject to job data transmission to the server and the context determination unit 1000. <System response to registration of "Melon Bread discount coupon"> When a "discount coupon for melon bread" is registered in the context determination unit 1000, a program for discount coupon processing in the file unit 1200 is started. When a "discount coupon" for another product is registered in the context determination unit 1000, a program for coupon processing is also started in the same manner.

[0074] The coupon processing program is started using, for example, "discount coupon" as a keyword. It then determines which agent sent the "discount coupon" and identifies the agent that sent it. Next, the program adds attribute information set in the "discount coupon" (discount amount or discount rate, issue deadline (start date and time to end date and time)) 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. In addition, the issuance conditions (attribute information) of the "discount coupon" may be determined according to the number of nodes in a context matching relationship within the context area. In other words, when the number of nodes is equal to or greater than N (set number), a "discount coupon" is issued.

[0076] <System operation example related to context area 10> Next, a description will be given of an example of the system operation related to the context area 10. 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 broadcasting has been 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 at least the device IDs of the nodes 4100 and 4200 together with its own device ID 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 refers to the data file (table 1201) of the file unit 1200, and searches for the transmitted multiple device IDs from among the device ID groups. Given the current situation of 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 illustrated example, the device ID of node 4400 is further integrated with the device ID of agent 3000 as a signage under agent 3000.

[0080] Based on the above-mentioned determination, the file unit 1200 notifies the agent 2000 of the device IDs belonging to the melon bread group (that is, 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, that is, a matching notification 202).

[0081] <Matching report mode for node of agent 2000 in context area 10> Next, after the above-mentioned matching notification 202 (which may be called a situation rule establishment notification) is performed, it is assumed that a broadcast is performed between the agent 2000 and the nodes 4100 and 4200 in the context area 10 (this operation is the matching report mode by the agent 2000).

[0082] Agent 2000 holds matching notification information (its own device ID and the device ID of node 4100) based on the function of the data processing unit, and writes this information in the parameter section explained in Fig. 1 and broadcasts it. Then, node 4100 can 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, a "melon bread discount coupon" can be automatically received from the agent 2000. This makes it possible to further increase the effectiveness of advertising. It also allows for sales promotion.

[0084] Other reactions of the node 4100 may include flashing light, outputting a notification sound by voice, vibration, or displaying text. This notification method can take various forms depending on the type and performance of the node 4100. If it is a simple accessory type, flashing, voice notification, or vibration notification is possible.

[0085] Furthermore, if it is a smartphone type, text display, image display, etc. are also possible based on the function of the data processing unit. For example, if the agent 2000 describes and transmits a context of "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 can even see a melon image. 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 a service for at least "melon bread" is nearby.

[0087] Meanwhile, agent 2000 can grasp how many "melon bread like" users (node ​​4100, etc.) are within its communication area each time a "status notification" and a "matching notification" are executed. This allows agent 2000 to collect data on the number of "melon bread like" users and the sales volume of melon bread, and calculate the correlation between the number of users and the sales volume. Furthermore, this is the realization of 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 (ratio, etc.) between the number of users and the sales volume.

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

[0089] <System operation example related to context area 20> Next, an example of the 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 unit 1200.

[0091] In the case of 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 has been made between the agent 3000 and the node 4300 in the context area 20 (the operation at this time is in the status detection mode by the agent). 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 transmitted multiple device IDs 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 a plurality of 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 performed 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 explained in FIG. 1 and broadcasts it. Then, node 4300 can 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 react in some way and attract the user's attention. This method of attracting attention is similar to the method explained above for node 4400.

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

[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 further processes 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 "red wine advertising" has been carried out. Here, the charging process may be carried out by updating the charging data in the charging table of the "red wine seller" registered in the context determination unit 1000 or the designated server. The charging 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 a table 1201 (a table in which agent IDs and node IDs are grouped by context). And it has been explained that the agent issues status notifications 201, 301, and receives 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 of the agents 2000, 3000. This method can reduce the load on the server (context determination unit) and can speed up the transmission of matching reports and discount coupons by the agents to the nodes.

[0103] Fig. 2B shows an embodiment in which related matching notification information is pre-deployed to the agent. The same parts as in Fig. 2A are given the same reference numerals, and duplicated explanations are omitted. This embodiment is characterized by the processing performed after the agents 2000, 3000 and the nodes 4100, 4200, and 4300 register their own device IDs and contexts in the file section 1200 of the context determination section 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 a situation notification 201, 301 is sent from an agent to the context determination unit 1000, the situation matching processing unit 1300 sends a matching notification 202, 203 to the agent 2000 or 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 the 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 the agent 2000 and the device ID of the agent 2000. In the example shown in the figure, the device IDs are those belonging to the melon bread group G1 (ID 4100, ID 4200, ID 2000).

[0107] For agent 3000, 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, 4400, and 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 broadcasting is performed, each of agents 2000 and 3000 can immediately report matching and can immediately transmit "discount coupons." Agent 3000 can also have node 4400, which is signage, immediately carry out advertising.

[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 explained in FIG. 1 and executes the broadcast. Then, in this case, since node 4100 exists in context area 20, this node 4100 can get some kind of response. Also, node 4100 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 transmit the “Melon Bread Discount Coupon” to the node 4100 .

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

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

[0113] Then, the agent 3000 recognizes that the node 4300 exists in the context area, and can immediately transmit the message "Red wine available" to the node (signage) 4400. As a result, the 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 services from the agent 3000.

[0115] As described above, agents 2000 and 3000 transmit "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 good CM efficiency.

[0116] FIG. 2C is a flowchart showing an example of the operation when the agent 2000, node 4100, node 4501, and node 4503 are simultaneously present in a 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, “peaches for sale” in the context determination unit 1000.

[0118] It is also assumed that the node 4100 has registered “I like melon bread” in the context determination unit 1000. It is also assumed that the 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 the node 4502 has registered “I love hamburgers” in the context determination unit 1000.

[0119] Assume that the agent 2000, node 4100, node 4501, and node 4503 simultaneously broadcast in a communication area (context area) (S01). The agent 2000 checks the received device IDs (the device IDs of the 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 node 4100 is "Melon Bread Group G1", and further determines that the device ID (node ​​4100) is a coupon distribution target. Therefore, the agent 2000 writes data pairing the device ID of 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 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] Furthermore, agent 2000 determines that the device ID of node 4501 is "Peach Loop GX." In this case, agent 2000 transmits to node 4501 data pairing the device ID of node 4501 with "Peach sales" in the data section shown in Fig. 1. This enables node 4501 to acquire "context matching related information" of "Peach sales" (S06).

[0122] Furthermore, the agent 2000 determines that the device ID of the node 4502 is not a service target. In this case, data related to the node 4502 is not described in the parameter section shown in Fig. 1. Therefore, the node 4502 does not acquire any "context matching related information" from the 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. 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, sound, 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 Figs. 2A and 2B, after the agent 2000 detects a node in a context matching state, it automatically distributes a coupon or the like to that node in the next broadcast. Therefore, it can be said that this system accurately performs appropriate sales to people who are likely to be business partners. In the above example, a service such as a "melon bread discount coupon" can be reliably provided to a consumer who says "I like melon bread." In addition, the sales effect is strengthened.

[0126] However, the above-mentioned "discount coupon" may be sent from the server to the node, not limited to the agent. In other words, the server can grasp the status of multiple agents (for example, the number of times context matching has 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 method of transmitting discount coupons to nodes is a method in which the agent broadcasts the coupons, but it is also possible for the server to transmit the coupons to agents or nodes via a network such as the Internet.

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

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

[0130] The sales record manager 7A2 receives job information (sales numbers, sales volumes, sales data, etc.) from the multiple agents 2000 and 3000 from the context determination unit 1000 via the API 7A1, grasps the sales record, and determines attribute data (corresponding to the control code and description in the data section shown in FIG. 1) such as the number of coupons to be issued, the agents to whom the coupons should be distributed, and the distribution time period. In response to this determination, the coupon manager 7A3 can transmit a coupon to, for example, the node 4100 via the API 7A1 and the context determination unit 1000. Of course, in this case, the server 7A grasps the device ID, email address, etc. of each agent or node. When each agent or node registers its own context (I like melon bread) in the context determination unit 1000, it registers its device ID, email address, etc. This registered data is indirectly used by the coupon manager 7A2 via the API.

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

[0132] <Settings system for smooth operation of the basic system> As described above, this system provides appropriate service information from the "user providing the service information" to the "user wanting the service information" based on the establishment of a rule 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 system is introduced into the system.

[0133] Figure 3 shows the various configuration systems required to ensure smooth operation of the basic system. In the following figures, the same parts as those in the previously explained figures are designated by the same reference numerals as those in the previously explained figures, and duplicated explanations will be omitted. <Context scheme and rule setting system> In order 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 a user (business owner, service manager, service initiator, etc.).

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

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

[0136] A retailer wants to promote the sale of its products, which may include 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 agencies also want to check the range of movement of the elderly. Also, the school alumni committee may want to find new 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 will want to set up customer flow routes in order 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", "meeting detection service", "building energy saving management service", "customer traffic 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 service as described above and easy for users to use, and an "information input template" for inputting information for processing by the program.

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

[0140] For ease of understanding, an example of the use of a "sales service for unsold goods" will be described. The mechanism of the "sales service for unsold products" is designed by a rule setter 5500 in the context scheme and rule setter 5000. In order to operate the "sales service for unsold products", 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 owner of a convenience store, supermarket, or department store, or a public institution such as a PTA (Parent-Teacher Association), a local government, a committee member of a school alumni association, 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, and elderly people.

[0143] The rule setter 5500 designs what state (layout or positional relationship, mutual detection method between nodes and agents, detection contents) is expected between multiple nodes and agents. For example, the above-mentioned agent 2000 designs that its communication area (context area) 10 can be set, that nodes can be detected in this communication area, etc. In order to make the nodes detectable, it is also decided what kind of context matching is expected. In the above 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. In addition, stores selling expensive precious metals and car dealerships may need to limit the number of customers entering the store. 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, or manually entering them, etc.). Also, when the context determination unit 1000 sends a matching notification to the agent, an agreement is made such that notification conditions can be set. Notification conditions include, for example, notification frequency and excluding certain notification recipients. Of course, as explained above, agreements are made regarding the circumstances under which a "discount coupon" will be issued, the date and time at which the issuance instruction will be issued, whether changes or modifications will be possible, etc.

[0146] As described above, in the context scheme and rule setting unit 5000, a rule setter who is familiar with the user's (agent owner's) business creates a rule execution program and a template for inputting information. The system is designed so that the user can 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. There is also designation 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 utilized for various purposes other than context classification processing. In this case, information designating 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 be provided with a field for inputting matters to be entrusted to the system administrator 9500 described later. Matters to be entrusted 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 be transmitted in advance to the agent 2000 as rule setting data 502.

[0150] As described above, the present 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.

[0151] 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, sound, or vibration).Furthermore, a rule setting system connectable to the context determination unit and for designing a user service form by setting a rule that results 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 a rule setter. This information registration system 6000 is used by a user 6500 who is "desiring information" to input specific context data and the device ID of his / her own information processor using the input information template.

[0153] A "user wanting information" registers information (which may be called profile information or profiling 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 period of time after the "predetermined situation" is established.

[0156] Therefore, the automated marketing manager also prepares a "research agent" in the context determination unit 1000 that can count the number of "melon bread lover" nodes, just like 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 manager (the "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 manager and the melon bread wholesaler may be the same person. In this way, the "research 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 and fresh foods) at the convenience store depending on the time of day. Such instructions may be further inputted 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 includes a context related to the information desired. Examples of the context are 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 of the profile information 601. Note that since there are various types of attribute information, there are predetermined codes or symbols as headers according to the type of attribute information (also called 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 established when a special state exists even if the 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 of the data file unit 1200 to determine that the matching is not established when a specific device ID (particularly an agent) or the name of a specific rival store is attached to the context.

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

[0164] If the stores of agents 2000 and 3000 sell the same product (for example, melon bread), then 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 the melon bread group G1 by dividing it into a melon bread group G1-1 for agent 2000 and a melon bread group G1-2 for agent 3000.

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

[0166] As a result, when a device ID within a group is sent to an agent, the device ID within the group is sent so that the device IDs of other agents do not coexist, which allows each agent to eliminate unnecessary processing steps.

[0167] The same applies to the case where the present system pre-allocates table 2001 in agent 2000 in advance 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 perform beacon communication with each other, and include a determination unit that determines context-related information included in a beacon packet.

[0169] 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).

[0170] Furthermore, a profile information input system for pre-setting profile information including the device IDs and respective context data of the first information processor and the second information processor, which are specific judgment 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 for a "user providing service information" to input "provided information" to the context determination unit 1000 by using a template. The input program and templates in this provided information input system 7000 are also created by the rule setter who set the situation.

[0172] The input information input by the information providing user 7500 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 agent 2000 registers a "discount coupon for melon bread." Or when a user at node 4200 registers "unsold melon bread." Or when the agent 3000 registers advertising data for signage (for example, red wine available).

[0173] Furthermore, this input information may be accompanied by attribute information (a predetermined code) so that the context determining 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 processor for providing information. Assume that there is a third information processor with which context matching is established with the information processor for providing information. 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 (not provide service information). For example, when the information to be provided is "discounted sales of alcoholic beverages," there may be cases where age data of 14 years or younger or 20 years or younger is described in the attribute information of the user of the third information processor, and "rubbing alcohol" is 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 processor for providing information is not established.

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

[0176] Incidentally, 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 perform beacon communication with each other, and include a determination unit that determines context-related information included in a beacon packet.

[0178] 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).

[0179] The information processing device further includes a provision information input system that is connectable 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 on the 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 for the previously described nodes 4100, 4200, and 4300 to register, together with their respective device IDs, contexts such as the aforementioned "melon bread lover," "unsold melon bread," "red wine lover," and "red wine sales, melon bread sales" 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 necessary.

[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 previously described provided information input system 7000. The input information includes the device ID of the information processor used by the user and the context. In addition, various kinds of attribute information may be input.

[0183] <Sending management when sending matching notifications> Furthermore, this system is provided with a transmission management system 9000 when matching notifications 202, 203 or status notifications are issued by a system administrator 9500. The transmission management system 9000 controls the transmitting / receiving unit 1100. When the transmitting / receiving unit 1100 issues matching notifications 202, 203, action transmission is executed 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 many agents and gateways, it is basically a system in which an order is set and matching notifications are sent at an equal frequency. However, depending on the agent or gateway, there are some that want matching notifications frequently and others that do not need to be sent so frequently depending on the "time period" or "day". In such cases, the system exclusively controls matching notifications for agents and gateways that do not need to be sent 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, matching notifications in the morning may be unnecessary or may be set to a minimum number. Therefore, each agent or rule setter discusses with the system administrator 9500 to determine the contents of the above-mentioned exclusive control.

[0185] Deduplication controls: For example, there may be a plurality of 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, the control by deduplication is to avoid duplicate transmission by alternately transmitting the device ID of the same node to the two agents at a time 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, and the like. Also, depending on the season, some agents may be busy and some agents may be free. In such cases, matching notifications are preferentially sent to agents that require immediacy or busy agents.

[0187] About 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, the number of matching notifications to each agent (or gateway) within a certain period is adjusted 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 connectable to the context determination unit and inputs, to the context determination unit, transmission management information that performs 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 an internal functional block of the information processor, but the present invention is not necessarily limited to those exemplified here.

[0191] FIG. 4A is an example in which a smartphone is used as the 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 is an example in which a personal computer (PC) is used as the 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 the 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 necessary for the above-mentioned agent 2000 or 3000. Of course, these may be used as nodes 4100-4300. Also, of course, they 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 memory 2305 of the situation data stores the data of the table 2001 and the table 3001 described in FIG. 2B and various attribute data. Therefore, when beacon communication is performed, the data processor 2304 reads the data of the memory 2305 and describes it as transmission data in the parameter section of the advertisement packet. The control unit 2306 comprehensively controls the above-mentioned transmitting / receiving unit 2300, the beacon communication processor 2301, the wireless or network communication processor 2302, the switch 2303, the data processor 2304, and the memory 2305. Therefore, the control unit 2306 selectively uses various applications depending on the operation mode. A display unit 2307 and a power supply 2308 are also provided.

[0195] The above-mentioned memory 2305 of the situation data may include a memory (RAM) having a rewritable area and a read-only memory (ROM) for context matching. The ROM may be a dedicated memory in which various context data are written to increase the utility value of the nodes 2000 and 3000, and may be removable. For example, there are many products for sale in convenience stores and department stores, and a memory in which product names and contexts are written in advance may be used. The same can be said about the memory of the situation data of the node described later.

[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 using a wristwatch 4520, which has a beacon communication unit 4521 built in. FIG. 5C is an example of using a pendant 4530, which has a beacon communication unit 4531 built in. FIG. 5D is an example of using a bracelet 4540, which has a beacon communication unit 4541 attached to it. FIG. 5E is an example of using glasses 4550, which has a beacon communication unit 4551 attached to it.

[0198] <Examples 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 FIG. 6A is the same as that of a smartphone, and has the same configuration as the agent described in FIG. 4D. That is, The device includes a transceiver 4A10, a beacon communication processor 4A11, and a wireless or network communication processor 4A12. The switch 4A13 selectively connects the 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 memory 4A15 for status data stores the device ID of the device itself, the context set by the device itself, attribute data, and the like. The data processor 4A14 can read the data in the memory 4A15 and write the data in the parameter section of the advertisement packet. The control unit 4A16 comprehensively controls the transceiver unit 4A10, the beacon communication processor 4A11, the wireless or network communication processor 4A12, the switch 4A13, the data processor 4A14, and the memory 4A15. Therefore, the control unit 4A16 selectively uses various applications depending on the operation mode. The device is also equipped with a display unit 4A07 and a power supply 4A08.

[0201] This node 4A00 can autonomously execute context matching processing and situation matching processing by adding an application, and therefore can have a function similar to that of the context determination unit 1000 described in Figures 2A and 2B on a small 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 memory 4A15 for situation data and the 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 by beacon communication to a server or agent via the Internet. Conversely, it is possible to notify other nodes or agents in a nearby communication area of ​​data acquired via the Internet by beacon communication.

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

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

[0205] Of course, the various nodes described above may also be provided with a voice output function.

[0206] <Examples of system usage at convenience stores, supermarkets, department stores, and various other stores> 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 introduced 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. And, "red wine sales" and "melon bread sales" are registered in the context determination unit 1000.

[0207] A customer 3B has a node 4A00 and has registered "red wine lover" as a context. A customer 3C has a 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 the context area 20 and a broadcast is performed (SA1). Then, the agent 3000, node 4A00, and node 4D00 enter a context matching state and each detect the context matching state. This allows customers 3B and 3C to recognize that a product they are interested in 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 enables 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 performing this count, the number of device IDs that have already been received within a specified time is excluded. This is to avoid counting duplicate device IDs. Furthermore, agent 3000 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 "established advertisement" (SA6).

[0211] Also, agent 3000 may recognize that the user of node 4D00 "likes melon bread" and 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, then an advertisement such as "red wine for sale" can be displayed on the signage (SA9, SA10).

[0213] <Monitoring service 1> FIG. 8A shows the service provider (e.g., a local government or a 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 private company) or a security company. A monitoring service system for a child 6A commuting to school will be described as an example.

[0214] Child 6A1 has smartphone 4510. In this case, agent 4B00 is placed at traffic light 6B1, for example at a pedestrian crossing, along the 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, ... of each user 6A1, 6A2, 6A3, ... in this table 7A10. The passing position data includes, for example, the location (house number, street name, etc.) of traffic light 6B1 and the date and time data when the user (user 6A1 in the figure) passed through. The location of traffic light 6B1 is registered in the file section together with the device ID of agent 4B00 when agent 4B00 installed in traffic light 6B1 is registered at the same time.

[0216] Users who can check the data of user 6A1 in server 7A are, for example, parents 6C1 and 6D1 who have signed a contract with the service operator in advance. If the child 6A1 passes through a different location than usual, the parents 6C1 and 6D1 can use their smartphones 4511 to call the smartphone 4510 of the child 6A1 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 a part of the monitoring system described above over time T. When the child 6A1 passes near the traffic light 6B1, a broadcast is performed between the smartphone 4510 and the agent 4B00 (SB1). The agent 6B1 detects the device ID of the smartphone 4510 that is registered in advance. The agent 6B1 then transmits the device ID of the smartphone 4510 and data on the passing position, such as the number or address of the traffic light 6B1, to the server 7A (SB3). The server 7A records the passing position data in the data recording section 6T1 of the user 6A1 (child) in the table 7A10 (SB4).

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

[0220] This allows the parents 6C1, 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 manager (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 given 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. 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 to warn him by voice.

[0223] There are also electric poles 2A01, 2A02, and 2A03 on the walking path 6H of the old man 6E. Agents 2A11, 2A12, and 2A13 are deployed on the electric poles 2A01, 2A02, and 2A03, respectively. The figure 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 exteriors 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 the 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 smartphone 4515 of elderly person 6E 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. Then, agent 2A11 and smartphone 4515 of old man 6E enter the same context area. Through broadcasts from agent 2A11 and smartphone 4515, agent 2A11 recognizes smartphone 4515 (old man 6E) (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 is, for example, "There are stairs leading up, please be careful, if you need help, press the # button on your smartphone."

[0226] Also, the agent 2A11 transmits to the server 7A passing position data indicating that the smartphone 4515 has passed the position of the agent 2A11, and the server 7A records the passing position data in the recording unit (SC3, 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. Agent 2A12 recognizes smartphone 4515 (old man 6E) through broadcasts from agent 2A12 and smartphone 4515 (SC6 in FIG. 9B). Agent 2A11 transmits passing position data to server 7A indicating that smartphone 4515 has passed agent 2A12's position, and server 7A records the passing position data in the recording unit (SC7, SC8 in FIG. 9B).

[0228] Assume that the old man 6E moves further and approaches the descending staircase 6G. Then, the agent 2A13 and the smartphone 4515 of the old man 6E enter the same context area. By the broadcast of the agent 2A13 and the smartphone 4515, the agent 2A13 recognizes the smartphone 4515 (old man 6E) (SC9 in FIG. 9B). In addition, the agent 2A13 controls the output of a message voice to the smartphone 4515 by the next broadcast (SC10 in FIG. 9B). The message voice is, for example, "There are descending stairs, please be careful, if you need help, please press the # button on your smartphone." The configuration of the agents 2A11, 2A12, and 2A13 is the same as that of the agent 2000 shown in FIG. 4D, and further includes a speaker 2301, and the agents 2A11, 2A12, and 2A13 may output a guidance voice.

[0229] Furthermore, agent 2A13 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 a recording unit (SC11, SC13 in FIG. 9B).

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

[0231] The above system can easily be used as a route guidance system. Each time the smartphone 4515 (old man 6E) approaches an agent 2A11, 2A12, or 2A13, it is possible to provide the old 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 a procedure for registering a device ID in a dating detection system. Fig. 10C is an explanatory diagram of an 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] These nodes 4A00 and 4D00 have a function of comparing the received context with their own context by broadcast. Their own context is stored in the situation data memory 4A15. This context is called a catch context. There may be not only one type of catch context, but also multiple types. For example, a relatively short catch context such as graduating from AAA school, hobby skiing, hobby tennis, etc. can be set for these requirements as logical AND (simultaneous occurrence) and logical OR (any of the two occurs).

[0234] When the node 4A00 and the node 4D00 receive each other's context by broadcasting, 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. Then, if the received context and the catch context match, some kind of display or audio output is obtained from the wristwatch 4520 and the 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 in which the user can communicate with the node 4A00 or node 4D00 via short-range wireless communication.

[0236] Then, as shown in FIG. 10B, software for registration 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 software for registration. At this time, the node is linked to the smartphone or personal computer by short-distance wireless communication, and can communicate with each other. The server accessed by the smartphone or personal computer is set so that users of the dating service will now enter information, and the server starts managing the dating service template (SE0, SE1).

[0237] The user inputs the device ID of the node 4A00 or node 4D00 to be used and the context data for meeting matching (or catching) into the blanks of the template and registers them (SE2, SE3). At this time, if multiple (e.g., two) context data are input, there may be an attribute input field for a logical condition such as "either one of them is sufficient" or "or both must be satisfied". In addition, exclusive condition data may be added as attribute information to the context (SE4). Furthermore, time limit data for the context data may also be added as attribute information. For example, the time limit data may specify a period or time for accepting matching, or an end date and time may be specified (SE5). The user checks the input data (SE6) and ends the operation. Then, the data input into the template (context data and attribute data) is registered in the server, and is also wirelessly transmitted from the smartphone or personal computer operated by the user directly to the wristwatch 4520 or pendant 4530, and is recorded in the memory 4A15 of the node 4A00 or 4D00.

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

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

[0240] However, node 4A00 and node 4D00 each determine whether matching exclusive data is included in the received context data (SF2, SF12). If matching exclusive data is included in the received context data, subsequent processing and reception are suspended for a certain period of time. However, if matching exclusive data is not included in the received context data, a display or audio notification is given to the user (SF3, SF13).

[0241] The above-mentioned dating services can be used in various ways, for example, "alumni association committee members want to meet alumni association members" or "people with a certain hobby want to meet people with the same hobby."

[0242] In special cases, compression processing using a password may be performed. When 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 device and the second device to be automatically decompressed on each device.

[0243] Fig. 11 shows an example in which an embodiment according to the present invention is introduced into a building management system. 8A shows, for example, a company building with floors 1 (1F) to 4 (4F). Employees can use elevator 8A1 to go from floor 2 to floor 4. 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 an employee in a context determination unit.

[0244] Assume now that employee 6H has come to work, received his / her smartphone 4581 at reception counter 8A2, and turned it on. Employee 6H is assumed to be employed in the department on the 3rd floor.

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

[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 3rd floor and stops there.

[0247] In the above description, the agent 3000 is arranged at the reception counter 8A2, but it may be arranged 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 time when the smartphone 4518 is turned on and off.

[0249] The building management system described above can control the power supply of lighting and air conditioning equipment in the necessary places, reducing wasteful power consumption. It can also manage the attendance of employees.

[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. The node 4C00 is, for example, in a bus 11A, a train 12A, an office 13A, an airplane 14A, a bar 15A, a hospital room 16A, a restaurant 17A, and the like.

[0252] When a user with a smartphone 4519 enters a bus 11A, a train 12A, an office 13A, an airplane 14A, a bar 15A, a hospital room 16A, a restaurant 17A, or the like, a broadcast is performed between the node 4C00 and the smartphone 4519. This communication allows the user to receive a status report (service information) of the Co2 in each environment from the node 4C00. That is, the smartphone 4519 can receive a Co2 detection signal from the node 4C00. If the Co2 detection signal is equal to or lower than the reference value, the smartphone 4519 displays, for example, "Sufficient ventilation is maintained" on the display. However, if the Co2 detection signal does not meet the reference value, the smartphone 4519 displays, for example, "Please ventilate the room" on the display.

[0253] The above shows an example of using a node with a CO2 sensor, but various sensors are 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, air pressure sensors, pressure sensors, water leak sensors, and dust detection sensors.

[0254] 12B shows another example of the configuration of the node 4C00. This node 4C00 can receive detection values ​​of a plurality of sensors 4AS1, 4AS2, and 4AS3. The detection values ​​of the sensors 4AS1, 4AS2, and 4AS3 may be received wirelessly or wired. In the case of a wireless sensor, a sensor that is pre-installed in the vehicle or airplane is used.

[0255] The types of sensors 4AS1, 4AS2, and 4AS3 are selectively used depending on the usage environment of the node 4C00.

[0256] A node 4C00 having such a sensor can simultaneously acquire the position (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 the embodiment of the present invention is used in a meeting system, a group inspection system, a customer flow line system, etc. at the entrance of an event venue or a shopping mall. Visitors often meet near the entrance of the venue. Tourists in a group may also carry out group inspections. Also, because the venue is large, individuals have a hard time 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 clubs, alumni, etc. through rendezvous can be realized, for example, by the methods described in 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] Further, the network communication unit 236 of the guide robot 21A can communicate with a predetermined server 23A via the base station 22A.

[0262] The server 23A has a transmission / reception unit 23A1, a control unit 23A2, and at least a reservation data file 23A3 for the event venue. The reservation data file 23A3 records reservation data for each user who owns a smartphone 4510, 4511, or 4515. The reservation data may include, for example, the device ID of the user's smartphone, the smartphone's phone number, reserved seat data, reservation date, and the user's 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 each smartphone 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] 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 necessarily includes information on the toilet locations, but may also include information on souvenir shops.

[0267] The guidance voice and flow line information (for example, route guidance information on a screen) by the above guidance program are transmitted to each smartphone 4510, 4511, 4515 from the server 23A via the base station 22A on individual lines. This system allows customers to go to 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 group," and so on are registered as attribute information.

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

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

[0272] In the user area 23, as described in FIG. 1, a member ID (identification information of a user of an electronic device) is described in bytes 7 to 8. A module ID (identification information of a non-specific application) is described in bytes 9 to 10. A frame type is described in byte 11. It has been described that the frame type indicates the transmission type.

[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 consists of a TYPE field and a LENGTH field. As explained above, the TYPE field distinguishes whether the type of data in the VAL section is int type, float type, or string type (there are int type, float type, and string type).

[0274] 14 shows another example of parameters (which may be called data) described in the parameter section, but is not limited to this format. 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] In the header area b, a specific code of the parameter section is assigned. In the following information ID description area c, identification data is described that indicates what type of information (particularly the type of data in the data section) is being sent. Examples of types include GPS information, sensor information, etc. Furthermore, like a file system, information on the number of bytes assigned to the description area of ​​various data may be present.

[0276] The node ID description area e contains identification data of the device that transmits this beacon packet 21, for example, 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, for example, when a new situation rule is registered, when there is a change in the situation rule, or when the rule itself is conveyed. The control code also includes the following: The data description field e uses schema information corresponding to the context. In other words, a code with a meaning predefined between the sender and receiver is 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 above attribute information is not fixed and is not limited. The attribute information basically instructs how to handle so-called context data. Therefore, for system operators, the format and contents of the attribute information are various, and 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, day, day of the week, time period) during which this service can be used. This usage period information can be rewritten as necessary by the system or the user. For example, when a contract between a user of the sales promotion system (described in FIG. 7A and FIG. 7B) and the system operator expires, the usage period may be automatically deleted by the system. Also, when 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 FIG. 10A), when 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 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 form. The context determination unit 1000 is configured to recognize this identification data, determine the usage form of the usage period (year / month / date, day of the week, time period), and control the agent.

[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 the context areas 10 and 20 in FIG. 2A overlap, the nodes 4100 and 4400 "group of melon bread lovers" will receive a matching report of "discount on melon bread" from the two agents 2000 and 3000. In such a case, the context determination unit 1000 can control the devices IDs (4100, 4400) sent by the agents 2000 and 3000 to be thinned out every time they broadcast. For example, in this example, the transmission of the device IDs 4100 and 4400 is denied once every two broadcasts. For example, the device ID to be denied and the frequency of each broadcast (for example, 1 / 2 in this example) are described in the area d3. If three context areas overlap, the frequency 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 realize the above process, the context determination unit 1000 needs to detect that the context areas 10 and 20 overlap. This detection is performed as follows. That is, when the agent 2000 notifies a status, the notification data includes the device ID of the agent 3000, and when the agent 3000 notifies a 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. Then, the context determination unit 1000 controls each of the agents 2000, 3000 so that the frequency is set in the above-mentioned area d3.

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

[0288] Furthermore, the control code area d includes a description area for a flag indicating whether there is further data to be transmitted. For example, this description area may describe "end" or "continue." As described above, in one beacon communication in this system, there is a limit to the amount of data that can be transmitted in the parameter section. Therefore, if the amount of data to be transmitted exceeds the amount of data that can be transmitted in one (current) beacon communication, "continue" is described 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 area for the password "Use" or "Not Use" may be provided in the control code area d. The password is a password that is determined in advance by specific users (for example, 6C1 and 6D1) who will perform beacon communication. The users 6C1 and 6D1 register a common password in advance, for example, in the memory of a data processor of a smartphone-type node. Then, when the users 6C1 and 6D1 set the password "Use or ON" on the menu screen, the symbol for the password "Use" is automatically written in the description area d6 for password presence or absence. In this way, only the users 6C1 and 6D1 can exchange information with each other through beacon communication. In other words, when the parameters acquired through beacon communication are compressed by a password, each node uses the password to decompress the other with a device ID or context. However, when the users 6C1 and 6D1 set the password "Not Use or OFF" on the menu screen, the context matching process becomes possible through normal beacon communication. In this case, the same operation as that of 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 as an agent 3000 here.

[0292] Meanwhile, the inventors have already developed a method of utilizing a smartphone when connecting an 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 into the ifLink system.

[0293] 15 includes an ifLink application 3201 and an IBI (ifLink Beacon Interface) microservice 3202. The IBI microservice 3202 can act as a bridge between the ifLink application 3201 and the various information processors described in the previous embodiments based on the microservice. 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 the beacon signal format based on the schema information.

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

[0295] Node 4C11 transmits different messages as service information to agent 3000, for example, when CO2 is below a specified value and when it is detected to be above the specified value. When CO2 is below the specified value, the message (service information) is, for example, "Sufficient ventilation is being maintained," and when it is detected to be above the specified value, the message (service information) is, for example, "CO2 is 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, but may be a symbol or code determined in advance. And this symbol or code may be interpretable by the ifLink application 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 application 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 language type that the IBI microservice 3202 can understand and send it. In this case, the data used for this conversion is referred to as schema information. In this way, the smartphone-type node 4C12 can easily set an application that functions as an IBI library for a general smartphone by downloading and obtaining it from a predetermined server.

[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 "agreed item" corresponding to a "condition item" is set such that if a condition of IF = A is satisfied, then an action of THEN = B is activated.

[0300] <Overview within Server 17> Various IF-THEN rules are stored in, for example, data section 1703 of server 17. Various IF-THEN rules are managed by rule manager 1702. Rule manager 1702 manages the creators of IF-THEN rules, the sale and lending 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 have used IF-THEN rules and issue rule usage fees to those users, and can also manage the period during which a user uses an IF-THEN rule.

[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. For the operation control unit 3108, a touch panel integrated with the display unit is often used.

[0303] Furthermore, here, an ifLink application 3201 is installed in the agent 3000 and performs overall control. The ifLink application 3201 further includes an 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 transmitting unit 3001 and a receiving unit 3002 connected to the network NETW. The ifLink application 301 can access the server 17 via the transmitting unit 3101 and request a desired IF-THEN rule. The IF-THEN rule is given, for example, a name (an identification name such as a name of available equipment or a system name) and is introduced in a catalog or the like. The user can download the desired IF-THEN rule via the receiving unit 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 and control unit 3207. Although there are some IF-THEN rules that are single rules, many IF-THEN rule sets are made up of 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 a 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. Then, the rule management and control unit 3207 reads out the rule set that initially 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" of 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 the command to the IBI microservice 3202. The IBI microservice 3202 transmits "detection data" corresponding to the command to an IBI-compatible external device by beacon signal.

[0310] In this way, one JOB is executed, and the information about the execution is transmitted 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 the transmitting / receiving units 3101 and 3102 described above.

[0312] The above-mentioned agent 3000 includes not only the IBI microservice 3202, but also a microservice (MS) 3204 for individual devices and a microservice (MS) 3205 for the web so as to be able to communicate with various individual devices.

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

[0314] When configured in this way, it is possible to reflect the execution command of TEHN, which is the response of IF obtained by broadcast with the beacon signal, on the individual device MS311 or the device connected to the MS for the web. The external command to the individual device MS3204 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 the individual device MS3204 or the web MS3205, on the device connected to the IBI microservice 3202.

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

[0317] Rule 1 associates IF1 of the IF device with THEN1 of the THEN device, and when the condition of the IF device IF1 (hereinafter, "condition" means an operating condition, a detection condition, etc.) is satisfied, the THEN device THEN1 is activated (hereinafter, "activated" means a 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 a 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 is information for determining the priority when other rule sets compete, and may be described together with the identification data of other competing rule sets. The rule set valid / invalid setting information is information for setting whether or not the rule set should function. Therefore, by combining with the period information, the valid period and invalid period of the rule set can be set. There may also be rule set usage environment information, which is information describing, for example, a predetermined condition (environmental condition) for adopting the rule set. For example, when the weather is fine, or when the rule set is used in a special facility. The environmental condition may be automatically described by, for example, an edge computer that stores the rule set. Furthermore, attribute information of a specific usage environment, such as a facility, a user, a task, and GPS information, may be described. This attribute information of the usage environment may also be automatically described by the edge computer that stores the rule set, or may be described from outside the edge computer by a user having 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. Similarly to the rule set usage environment information, each rule may have its own rule usage environment information. In this case, the rule usage environment information defines a subordinate concept of the rule set usage environment information.

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

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

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

[0324] The 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), and conditions.

[0325] Conditions that can be set include the THEN device inhibition time, sensor name, control target, individual parameters, etc. The inhibition time is information that determines the number of seconds to wait 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 object refers to a further specified part or switch within the THEN device. If the control object is described, it 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 an operating range (for example, information for limiting the height of a drone in the case of controlling the drone). It is preferable that the attribute information also includes data that identifies 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 devices and THEN devices that it should manage, and therefore does not respond to or control the IF devices and THEN devices that are managed by other microservices.

[0327] The THEN device is basically a subsequent element that executes a subsequent action in cooperation with a previous 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 include "event-related information." The event-related information is a field for describing the device name, serial number, or summary of the IF device when, for example, the THEN device operates and the operation affects other IF devices. The type of effect may also be described in a character string as an overview. For example, if the THEN device is a device that emits a specific sound, it may affect an IF device that is a sound sensor that is not originally related. Also, if the THEN device is a device that outputs light, it may affect an IF device that is a light sensor. If such a case is known in advance, the user can consider replacing the THEN device or the IF device with another sensor. The event-related information is described in advance by, for example, a manufacturer that sells and provides a rule set, but it may also be written consciously by the user himself on the edge computer. This enables various uses of the rule set.

[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 there is attribute information. If the rule execution program determines that attribute information is described, it can confirm and check the attribute contents, and if it determines that no attribute information is described, it will skip checking the attribute information.

[0330] If there is no attribute identification information, the rule execution program judges the contents of the attribute information in sequence according to the order of the attribute description symbols (e.g., deviceserial=, id=, etc.). In the case of attribute information whose contents are 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), user information using 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. By using the frame type, it is possible to make the mutual communication using the beacon signal more advanced. Therefore, using the frame type is effective when transmitting and receiving important context data.

[0333] The frame type is made up of 1 byte and includes a REQ / RES flag indicating a request / response, a REPLY flag indicating whether a response to the command is required, and the 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 processing device 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 a REQ / RES flag. 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 the REPLY flag field; if no reply is required, the flag is set to 0; if a reply is required, the flag is set to 1. The commands from bit 5 to bit 0 are: 1: device registration (unused), 2: device registration result (unused), 3: sensor value notification, 4: job notification, and 5: job result notification.

[0335] Fig. 19 shows an example of the setting value of the frame type in Fig. 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 response "sensor value received" sent from the IBI microservice 302 to the smartphone app as a sensor in the case of a sensor value notification (response required).

[0337] The setting value of the frame type of a job notification (no response required) is 0x04. The frame type of 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 of the job result notification is 0xC4. An example of a job result notification is a response from a smartphone app as a THEN module to the IBI microservice 302 saying "XX operation was 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 to parameter 4. 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, parameters (which may be called context data) when notifying a sensor value 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, where param1 indicates the temperature and param2 indicates the humidity. The number of parameters is not limited to 4, and the number can be changed 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 a smartphone type, a charger is already available. However, in the case of a simplified information processor, if the power supply voltage drops, it is necessary to secure a power supply. For this purpose, an accessory such as a solar power generator, a piezoelectric power generator, or a vibration power generator may be added to the power supply unit. In addition, data in the user area may be subjected to encryption processing or data compression processing involving a password.

[0343] As described above, each of the embodiments and combinations thereof include various inventions.

[0344] 22 to 32 each show the basic configuration of an embodiment, and show only the parts where special ingenuity has been applied. 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 the first information processors, and nodes 4100-4400 are the second information processors. Then, 22, the system 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 include a determination unit that determines context-related information included in a beacon packet. 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 second information processor includes a data processor that processes the result data as output data for user notification (display, sound, or vibration).

[0345] Fig. 23 shows a basic configuration as yet another embodiment. This embodiment is an example in which context determination units 1000A and 1000B are arranged in agents 2000 and 3000, respectively. The context determination units 1000A and 1000B are connected to a server 7A via a network NTW, and each of them can download and use necessary software, etc. When registering profile information, the user can also specify the context determination unit (or agent) to be registered.

[0346] 24 shows a 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, in a server).

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

[0348] FIG. 25 shows a basic configuration as yet another embodiment, and shows a part in which a unique innovation has been made. In addition to the embodiment of FIG. 22, a rule setter (a person, a business operator, etc. who sets rules for a situation) 5500 can access the system. The rule setter 5500 operates the context scheme and rule setting system 5000. The context scheme and rule setting system 5000 can be connected to the context determination unit 1000, and designs and sets a user service form by setting rules for a situation that is in a matching relationship. Examples of the service form include the monitoring service and sales promotion service described above. The context scheme and rule setting unit 5000 prepares at least an input unit for a context and a device ID as elements for setting situation rules. In this example, the rule setting for a situation is performed for each agent 2000, 3000 via the context determination unit 1000 outside the agent.

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

[0350] Fig. 27 shows an example in which an information registration system 6000 into which a user actually inputs profile information is added to the embodiment of Fig. 22, and which can be connected to the context determination unit 1000. That is, in this example, it becomes possible to set in advance 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 for 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 in Fig. 22. In this case, the profile information may be sent to each agent 2000, 3000 via a server 7A.

[0352] Fig. 29 shows an example in which a provision information input system 7000 can be connected to the context determination unit 1000 in addition to the embodiment of Fig. 22. This provision information input system 7000 is an input system for inputting in advance result data (data of context contents to be provided to the other party) to be given to the information processor that will be in a matching relationship. For example, there is 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 in Fig. 22. In this case, the provision information may 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 of FIG. 22. The transmission management systems 9000A and 9000B can control the transmission form of each agent 2000 and 3000 by performing any one of transmission frequency, exclusive control, and duplicate elimination as a method of sending the context-related information. This is particularly effective when the context areas of the agents 2000 and 3000 partially overlap. In the example shown in the figure, for example, information such as "red wine discount" is reported from both agents 2000 and 3000 to node 4200 and node 4300. In such a case, one extra advertisement is added to the advertising performance number in the JOB information of the agents 2000 and 3000. This means that, for example, when a rule setter (or a system operator) charges the agents 2000 and 3000 for the establishment of an advertisement, excessive charges are made.

[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 measures such as the following: For example, the charges are halved, or the beacon transmission frequency of the agents 2000 and 3000 is reduced and the charges are distributed 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 a context determination unit 1000A or 1000B in an agent.

[0357] The transmission management systems 9000A, 9000B may enable control of the transmission output power of the agents 2000, 3000. For example, control may be performed to strengthen the output power of transmission power for a specific agent depending on the date or time of day. This control is possible, for example, by an automatic marketing operator requesting the system administrator in advance. When the output power of transmission power is controlled, it is possible to expand or reduce the range of the context area. This is particularly effective when conducting sales promotion. The operators of the transmission management systems 9000A, 9000B may also charge the agent administrator.

[0358] <The above-described embodiment includes 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 contents that each of the multiple information processors (agents 2000, 3000, nodes 4100-4400) needs or requests 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 context is 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 executes context matching. The information processing device may include a part or the whole of the above-mentioned registration system. The above-mentioned types of information processors may include a type having a sensor, a type to which a sensor is connected, a type having a display, and a type having 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, the packet consisting of a header area (22) including 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; There is provided a service information receiving device comprising a beacon signal receiving unit (2300, 2301), a detection 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] 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 is in correspondence with the context data set by the device itself is detection data acquired from an external context matching node (having advanced matching judgment).

[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 is in correspondence with 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 are replaceable), and a receiving device for service information described in B1 is provided.

[0363] <Construction of the agent on the convenience store side, with a transmitter and a receiver. Using the examples of melon bread and red wine> C1] is used in a system that broadcasts a packet as a beacon signal, the packet consisting 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 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 detection data indicates that the received data in the user area of ​​the other device corresponds to context data set by the device itself, transmits (notifies) data via the transmitting unit for causing the other device to output service information corresponding to the context data set by the device.

[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 correspondence with the context data set by the device is detection data acquired 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 a user area of ​​the beacon signal of the 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 correspondence with the context data set by the own device is detection data obtained by processing of a control unit of the own device (in the case where the own device is an agent or a PC having matching firmware). <Contents of the transmission and reception system> D1] A system for broadcasting a packet as a beacon signal, the packet comprising a header area including communication standard data and a user area 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 its own device, a receiving unit that receives the beacon signal of other devices, and a control unit that, when obtaining detection data indicating that the data in the user area of the other device received matches the context data set by its own device, transmits, via the transmitting unit, data for causing the other device to perform an operation corresponding to the service indicated by the context data set by its own device. 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 corresponding to the service indicated by the context data of its own device when the data is obtained, and 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, and an IF-THEN engine in which the rule set is set, a plurality of microservices including an IBI microservice and a microservice for individual devices that are given a command for instructing a specified "JOB". The IBI microservice is connected to the beacon transceiver unit. The beacon transceiver unit is a transceiver unit 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, and a transmission and reception device that enables broadcast of the beacon signal and unicast using the microservice for individual devices is provided.

[0368] <Basic system> F1) A first information processor registering a first context in a context determination unit, and a second information processor registering 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 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 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 includes 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 in which the matching relationship is established, There is provided an information processing system comprising a situation setting system which is provided with an input section 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 connectable to a profile information input system for pre-setting profile information including the device IDs and respective context data of the first information processor and the second information processor, which are specific judgment 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 having 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), there is provided an information processing system, further comprising a transmission management system connectable to the context determination unit and inputting transmission management information to the context determination unit, the transmission management information performing 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 and reception method. The above-mentioned device also has characteristics in terms of categories such as a transmission method, a reception method, and a transmission and reception method. The following are the claims as filed: [1] a first information processor having a first context registered 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 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 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] An information processing system according to claim 1, wherein the node notification data is data that provides 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] An information processing system as described in 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 a third context and the fourth context sent from another third information processor and a fourth information processor, and is provided with a table that classifies the device ID of each information processor for each context. [6] A context determination unit enables a first context of the first information processor to be registered; 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 result data of the determination 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; 23. 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 having a second context registered 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, 4. An information processing device that processes the result data as node notification data. [8] The node notification data is data for giving 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 specified context determination unit is provided in an external server.

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

[0374] 10, 20...context area, 21...beacon packet, 23...user area, 1000...context determination section, 1100...transmission / reception section, 1200...file section, 1201...table, 1300...situation matching processing unit, 2000, 3000...agent, 2001, 3001...subtable, 4200, 4300, 4400...node, 5000: Situation setting system, 5500: Rule setter, 6000···Information registration system, 6500···Users who want information, 7000···Information provided 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 indicate a matching relationship, the first information processor includes a first processor that processes the result data of the matching relationship as coupon issuance data; the second information processor includes a second processor for receiving the coupon issuance data and processing the coupon as a received coupon; the first information processor includes a means for transmitting the coupon issuance status to the server; The server manages the coupon issuance data sent from a plurality of information processors and includes a management means for managing at least the number of coupons issued. An information processing system comprising:

2. the context determination unit forms group data including IDs of the first information processor and the second information processor in a group of contexts having the matching relationship at the time of the registration, 2. The information processing system according to claim 1, wherein 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 is performed within the first information processor.

3. 2. The information processing system according to claim 1, wherein said server comprises a sales record manager for grasping sales records, and a means for controlling at least the number of coupons issued to said plurality of information processors.

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 indicate a matching relationship, The first information processor processes the result data of the matching relationship as coupon issuance data; the second information processor processes the coupon issuance data as a received coupon; the first information processor transmits the coupon issuance status to the server; the server manages the coupon issuance data sent from a plurality of information processors and manages at least the number of coupons issued; 1. An information processing method comprising:

5. 5. The information processing method according to claim 4, wherein said server includes a sales record manager for grasping sales records and controls at least the number of coupons issued to said plurality of information processors.

Images