JP2003196249A - Entity device, designation applying method, recording medium and its program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an entity device capable of discriminating at least one meaning information switch included in an entity. <P>SOLUTION: An event is constituted of data and the meaning information of the data. An event place indicates the repercussion range of the event. An entity device is constituted of an entity control part and a meaning information switch for transmitting/receiving data based on the meaning information of the event. The entity control part of the entity device sets the designation of the meaning information switch from the designation of the entity device and the designation of the event place where the entity device participates. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an entity device, a naming method, a recording medium and a program capable of distinguishing one or more semantic information switches included in an entity.

[0002]

2. Description of the Related Art The Internet based on the experimental network (ARPANET) started by the US Department of Defense in 1969 is now indispensable to our lives.
The Internet, which interconnects all computers in the world, has undergone several technological innovations to provide us with a network environment where anyone can easily access information on the network anytime, anywhere.

As shown in FIG. 23, in the first generation Internet, information distribution based on a "broker type distribution model" has been common. In this business model, an information distributor (for example, a personal computer communication company) positioned as a broker centrally manages information of information providers and distributes the information to users as necessary. That is, the broker played a role of connecting the user and the information provider. Therefore, the broker has a storage (a storage such as a hard disk) to store a huge amount of information, a high-performance computing device (such as a high-performance workstation) to process the information, and a sufficient communication band with the user. , A huge capital investment was needed.

On the other hand, WWW (World Wide Web) announced in 1992 is an innovative technology that dramatically improves the convenience of the Internet and expands the base of users. This opened the door to the second generation of the Internet. While users can use all information (contents) in the world via browsers, information providers have become able to disseminate information without going through a broker (information distributor).

In the WWW, individual information providers manage information in a super-distributed manner, and hyperlink information to each other.
Only the information provider can build a super distributed database of information. This has made it possible to "build an information distribution network" that does not require an information distributor. This is the true form that the Internet was aiming for, the WWW
Is the reason why it is said to be the second generation of innovative technology. Here, the new business model made possible by distribution technologies such as WWW is called the "brokerless distribution model".

While information distribution based on a brokerless distribution model, that is, information distribution led by an information provider, becomes possible, it is possible to easily specify the information desired by the user from among the information flooding the world. , It has become an important issue to be able to identify a user who is suitable for delivering information to an information provider. Unfortunately, the WWW doesn't provide a solution to this challenge. Therefore, portal site, search service, recommendation service,
A new broker called Directory Services, Trader has arrived. This business model is called a "broker type search model". In the broker-type search model, information (source) search or information distribution destination search is performed via the broker, but information distribution with a discovered partner is done by end-to-end (peer-to- peer) directly, ie based on a brokerless distribution model. Therefore, Napster, which was announced in January 1999 and became a hot topic, can be positioned as a broker-type search model.

However, in the broker-type search model, since the broker manages the metadata of information collectively, it is difficult to meet the diverse needs of users and information providers in real time. You have more freedom because you must entrust it to the operation policy, all services will stop if the system (server) operated by the broker goes down, and it is difficult to protect the privacy of users and information providers. , A new business model that is not dominated by a specific broker has been demanded. In other words, the broker (centralized administrator) that has been generally used in the business model up to now is excluded, and the entities (for example, the user and the information provider) are directly searched and found for each other. A business model capable of doing so has come to be demanded.

From the recognition of such problems, a new concept of "brokerless search model" has been devised. This brokerless search model was announced in March 2000.
P2P, like nutella, has been gaining attention around the world
Corresponds to (Peer-to-Peer). JXTA, which was announced in April 2001, also corresponds to P2P, that is, a brokerless search model. P2P is an innovative technology since WWW and is called the third generation. In recent years, research and development of a brokerless transmission model that applies the concept of P2P to the transmission layer and a brokerless policy model that applies the concept of P2P to the policy layer have become active. The dimensions of the brokerless (delivery) model are shown in FIG.

[0009] As a brokerless policy model, for example, COMNet (Community Network) or SIONet (Seman
tic Information-Oriented Network). The details of SIONet are described in the following papers.

Takanari Hoshiai, Keiichi Koyanagi, Bilge Scubatar, Minoru Kubota, Hiroshi Shibata, Takamichi Sakai: "Semantic Information Network Architecture", IEICE Transactions B, Vo
l.J84-B, No.3, pp.4,11-4,2,4 (2000.7 Reception, 2001-3). Takanari Hoshiai, Hiroshi Shibata, Takamichi Sakai, Keiichi Koyanagi: “Semantic Information Network Architecture: SION Architecture ”, NTT
R & D, Vol.50, No.3, pp.157-164 (2000.12 reception, 2001.3.
Published).

Brokerless type search model (P2P model)
Is a vision / concept / idea, and the world it aims at is very simple and clear. Specifically, we aim to build the following world.・ Traditional brokers (intermediaries, operators, centralized management departments, etc.)
By having each entity share the role played by, as a volunteer, it is possible to build and operate various network services without assuming the existence of a specific operator, administrator, or centralized management unit. -The remaining entities are autonomous so that even if any entity participating in the operation as a volunteer leaves the operation due to various reasons such as failure or withdrawal, it will not affect the entire network service. Be able to continue the service by self-organizing.

The following briefly describes how SIONet implements the brokerless search model. SIONet is a meta-network that delivers an event consisting of data and the semantic information of the data based on the semantic information (metadata). As shown in FIG. 25, the event receiver registers in advance the semantic information indicating the condition of the event to be received in SIONet. When the event sender sends an event to SIONet, SIONet
The semantic information of the event is collated with the registered semantic information, and the event is transmitted to the event receiver based on the collation result. In this way, sending an event to SIONet is called "stimulation", and the registered semantic information matches the semantic information of the event, and the event receiver who registered the semantic information is notified of the event. It is called "ignition".

Thus, a specific entity can be dynamically searched / discovered from a large number of unspecified entities that are super-distributed on the network. Ie SI
ONet is a network that delivers events based on semantic information (who is sent) instead of the destination address (who is sent) used in conventional networks.

The SIONet is an autonomous distributed cooperative network (autonomous distributed computer) in which all the entities including the constituent elements of the SIONet are autonomously distributed and coordinated to self-organize the network. SIONet's network components include the Semantic Information Switch (SI-S
W) ”,“ Semantic Information Router (SI-R) ”,“ Semantic Information Gateway (SI-GW) ”,“ Event Place ”,“ Session ”, etc. By self-organizing these as necessary , A secure and scalable P2P network can be built with a bottom-up approach.

The basic concept / principle of SIONet is simple and unified. By repeating the simple operation of “registering a filter by an entity and sending an event”, that is, “stimulation” and “firing” of an entity “chain reaction” between network components of SIONet, all entities The thing that controls the behavior of this chain reaction is the semantic information registered in SIONet by the above event receiver, which is called a "filter". By the filter value registered in the filter, it is possible to dynamically control the chain reaction method of the entities. Another basic concept in SIONet is event place. Event Places are entity groups that are interconnected by shared links,
This can limit the range of chain reactions.

Specifically, the event routing, event transfer mode (unicast, broadcast, multicast, attributed multicast, reply notification), firewall mechanism, online addition / removal mechanism of entities, failure processing mechanism, statistical information collection mechanism, etc. , Designed and implemented based on these ideas.

[0017]

As described above, the concept of an entity including network components for autonomously distributed cooperation of a SIONet network has been proposed. However, the functions that can actually realize the concept are not enough to actually apply them to business etc. only by the currently proposed functions.

For example, in SIONet, the concept of event place is proposed. An event place is a spread range of an event or an event path, in other words, a group of entities linked by a shared link. Each entity establishes a connection by connecting the semantic information switches included in each entity by a session or a shared link, and this semantic information switch allows each entity to participate in an event place. There are as many as there are. For example, when an entity participates in the event place A and the event place B at the same time, the entity includes two semantic information switches. One of the semantic information switches establishes a connection only with the semantic information switch for the event place A of the entity participating in the event place A,
The other semantic information switch establishes a connection only with the semantic information switch for the event place B of the entity participating in the event place B. In this way, since the semantic information switch included in the entity differs for each event place, even the semantic information switch included in the same entity establishes a connection with the semantic information switch that can participate in the event place desired by the entity owner. Must. The present invention has been made in view of such circumstances, and is included in an entity 1
It is an object to provide an entity device, a naming method, a recording medium, and a program capable of distinguishing one or more semantic information switches.

[0019]

The present invention has been made to achieve the above object, and is an entity device for transmitting and receiving an event consisting of data and semantic information of the data, the meaning of the event A semantic information switch that sends the event to another entity device based on the information, a name of the entity device, and an event place name of the event place in which the entity device participates, the event place indicating the spread range of the event. To control means for setting the name of the meaning information switch.

Thus, a name for uniquely identifying the semantic information switch can be set. When an entity participates in an event place, it needs to connect with another entity that has already participated in the event place. At this time, the entity identifies the semantic information switch included in the other entity by name. However, the name can be used to establish a connection with another entity. As an effect, the entity owner can establish a connection with another entity without being directly aware of the semantic information switch.

The present invention is also a method of naming by an entity device that transmits and receives an event consisting of data and semantic information of the data, wherein the name of the entity device and the event place in which the entity device participates. And a name assigning method having a step of setting the name of a semantic information switch for transmitting the event to another entity device based on the semantic information of the event from the name of the event place indicating the spread range of the event. ..

The present invention is also a name giving program by an entity device for transmitting and receiving an event consisting of data and semantic information of the data, the name of the entity device and an event place in which the entity device participates. A built-in program that causes a computer to execute the step of setting the name of a semantic information switch that transmits the event to another entity device based on the semantic information of the event, based on the name of the event place indicating the spread range of the event Is.

The present invention is also a name giving program by an entity device for transmitting and receiving an event consisting of data and semantic information of the data, the name of the entity device and an event place in which the entity device participates. A built-in program that causes a computer to execute the step of setting the name of a semantic information switch that transmits the event to another entity device based on the semantic information of the event, based on the name of the event place indicating the spread range of the event Is a computer-readable recording medium in which is recorded.

[0024]

DETAILED DESCRIPTION OF THE INVENTION An embodiment of the present invention will be described below with reference to the drawings. <Definition of SIONet Entity> Here, all computers such as personal computers, workstations, portable information terminals, mobile phones, and wearable computers are generically called hosts. Furthermore, a host that implements SIONet software is called a "SIONet entity".
Or simply called "entity". An entity (entity device) is a SION, as shown in the example in FIG.
It is a virtualized host that implements et software as a unit of autonomous distributed cooperation in SIONet. SIONet
Software provides a mechanism for individual entities to perform autonomous distributed coordination. This SIONet software allows each host to become an autonomous distributed computer.

As shown in FIG. 2, entities are mainly classified into the following three types. -An application that acts as a service (service entity: SE, service entity part) is included inside the entity- A module that acts as a network component (network entity: NE) is included inside the entity- Both SE and NE are entities Included inside

<Entity Structure and State Transition> FIG.
It is a figure which shows the state transition of an entity. As shown in this figure, the state of the entity is “Non-Existen
There are three states: "t", "suspend", and "active". The "Non-Existent" state represents the entity state when SIONet software is installed on the host. Execute SIONet software (launch) ), The state transitions from the “Non-Existent” state to the “suspend” state.At this time, in the entity, an entity control unit, a control panel, a network entity factory (NE factory), as shown in FIG. , Network entity (N
E), etc. internal modules are generated. The respective roles will be briefly described below.

The entity control unit is an entity of an entity, and receives various requests (requests for establishing a session, requests for establishing a shared link, etc., which will be described later) from other entities and the control panel. In addition, "
Other entities cannot make a request to establish a session, a request to establish a shared link, etc. to an entity in the “suspend” state.

The control panel is a GUI (Graphical User Interface) for owners of entities such as people.
e) to provide. With the control panel, for example,
Prompt the entity owner to enter the entity name,
Based on the input entity name, the entity control unit gives the entity name to the entity.
In the example of FIG. 4, the entity name is “entity 2”. This entity name may be referred to as a "local entity name" in particular distinction from a "global entity name" described later. This local entity name can be arbitrarily set by the owner of the entity.

The NE (network entity) factory has a function of dynamically generating an NE. NE
(Network Entity) means SI-R (Semantic I
nformation Router, Semantic Information Router), SI-GW (Seman)
tic Information Gateway, semantic information gateway),
It is a generic term for modules that behave for network control, such as alive entities, fault handling entities, and statistical information collection entities.

SE (service entity) is an application incorporated as an SE in the entity using a plug-in mechanism provided by the entity, and is a virtualized P2P application operating on SIONet. Applications can be embedded as SEs within an entity using the plugin mechanism provided by the entity. Also, the SE can establish an arbitrary number of sessions with the SI-SW.
The SE can send and receive events only through the session. SE is not involved in SIONet network construction and operation. The plug-in mechanism for incorporating SE into an entity will be described later.

The entity (entity 2) in the "suspended" state in FIG. 3 generates an event place by itself as shown in the example of FIG. 5, or joins the existing event place as shown in the example of FIG. When (Joining), etc., belongs to any event place and becomes a member of the entity group, the entity (entity 2) changes from "suspend" state to "active"
Transition to the state. Only an entity in the "active" state advertises its existence (public, details will be described later), and can accept a session establishment request and a shared link establishment request from another entity.

The operation until the entity becomes "active" after the software is installed in the host and the entity including the NE, NE factory, entity control unit, control panel, etc. is generated will be described. It is assumed that the entity receives an instruction to generate an event place or participate in another event place from the owner of the entity via the control panel. The entity control unit of the entity requests the NE factory of the entity to generate an SI-SW (Semantic Information Switch). When the NE factory generates the SI-SW, the entity control unit will generate the SI-SW.
And an internal module such as NE. This makes it possible to receive advertisements, session establishment requests from other entities, shared link establishment requests, and the like.

Here, the roles of the SI-SW and the session will be described with reference to FIG. A session is a connection between SI-SW and SE, and SE can send and receive an event only through the session. There are three types of sessions: an event sending session, a receiving session, and a sending / receiving session. SI-SW provides a switching mechanism that switches events based on semantic information. SI-SW has a session
The NE and internal entities such as SE and NE incorporated in the entity by the plug-in mechanism are accommodated in a star type. In the following description, SE is taken as an example, but NE
The same applies to other internal entities contained in the entity.

Here, the structure of the event will be described. As shown in an example in FIG. 8, the event includes a control information part, a meaning information part, and a data part. Transmission data is stored in the data section. As transmission data, various data such as text data, binary data, reference, proxy, agent, etc., programs can be stored.

The semantic information section stores the semantic information (vocabulary and its value) of the transmission data and the vocabulary concept (event type) of the semantic information. Here, the semantic information is metadata that describes the characteristics of the transmission data, and is an instance of the event type. The event type is a template of semantic information. You can define inheritance relationships between event types. FIG. 9 shows an example of the semantic information system. In this figure, "Title;Yesterday","
The price: $ 30 ", the meaning information of" artist name: Beatles "belongs to the event type" popular "and also belongs to the event type" music ". Also," title: Kiyoshi no Yoru " , "Price: $ 20", "Situation: Christmas" meaning information belongs to the event type "BGM" and also to the event type "Music".

As a description language of the semantic information system, XML (Ext
ensible Markup Language). Note that some event type names (SION
All names beginning with et) are reserved. The control information part of an event, an example of which is shown in FIG. 8, is a control field used for execution control of SIONet, and only this is the control field.
It is not open to SE who is a user of SIONet.
The control information part includes the identifier of the matched filter, the matching score of the matched filter, the synchronous statistical information collection flag, the TTL in the event place, and between the event places.
Control information such as (Time To Live) value, number of hops between event places, and between event places, and hop attribute is set.

The function of the SE in the entity structure shown in FIG. 7 will be described. The SE registers the event acquisition condition in the SI-SW via the reception session. This is called a "filter". In the filter, the vocabulary concept (event type) of the event to be acquired and the matching condition with the semantic information (for example, the vocabulary "Price" is "$ 20 to $ 40")
The range "of" is targeted for acquisition) etc. Note that "exact match" with all vocabularies defined in the event type, "partial match" with some vocabulary, "weighted match" , Etc., the matching condition can be selected in filter units.

The SE can register a plurality of filters from one reception session, but the filters registered through the same session have an "or" relationship. That is, one reception session fires at most once for one event. If a wildcard is specified for the event type of the event to be acquired, all event types will be the targets of acquisition. Further, when the matching condition with the semantic information is set to 1 (logical value is true), it means that the matching condition with the semantic information is unconditionally satisfied.

Further, the SE uses the transmission session to
Send an event to SI-SW. At this time, the SI-SW collates the semantic information part of the event with the filter. Specifically, first, it is checked whether or not it is the event type to be received, and if it is satisfied, the semantic information and the matching condition are checked. As a result of this matching, when the semantic information satisfies the matching condition, the entity that registered the matched filter is activated and the event is notified. In SIONet, transmission of an event is called "stimulation", that a filter matches an event is called "reaction", and activation of an entity that registered the matched filter and notification of the event are called "fire".

<Entity Naming Method> As shown in FIG. 5, a case where the entity 2 creates an event place named “event place A” will be described.
The owner of the entity 2 inputs the event place name in the entity 2 through the control panel or the like. Here, the input event place name is referred to as “event place A”. Then, the entity control unit requests the NE factory to generate the SI-SW, and establishes a session between the generated SI-SW and an internal module such as the NE. Further, the entity control unit changes the name of the generated SI-SW to “event place name + local entity name”, that is, “event place A
+ "Entity 2". This name is called the "global entity name". Creation of this global entity name corresponds to generation of event place.

That is, in SIONet, some kind of management entity is not always generated by the generation of the event place. In other words, in SIONet, member management of the entities belonging to the event place is realized by a shared link between the entities, which will be described later, and thus there is no centralized management unit itself for managing the members. Therefore, even if the entity that created the event place leaves the event place, the entities left in the event place autonomously self-organize and the operation of the event place is continued. That is, the last entity leaving the event place corresponds to the disappearance of the event place.

This global entity name is used when establishing a shared link or session.
An operation in which the entity 2 as shown in FIG. 5 further generates the event place B and establishes the shared link from the entity 1 will be described with reference to FIG.

First, the operation in which the entity 2 already participating in the event place A creates the event place B will be described. The entity control unit of the entity 2 causes the NE factory to generate a new SI-SW as described above. The entity controller is responsible for creating the new SI
-Add "Event Place B + Entity 2" to SW as a global entity name. As a result, the event place B is generated. At this point, the entity 2 has two global entity names (SI-SW names) of "event place A + entity 2" and "event place B + entity 2".

Next, the operation in which the entity 1 joins the event place A will be described. As described above, the entity 2 participating in the event place A and the event place B is in the “active” state.
Entities in the "active" state can advertise their existence to other entities, at which time the global entity name is published.

When the entity 1 discovers the entity 2 and makes a Join request to the entity 2,
The entity 1 notifies the entity 2 that the global entity name of the entity 2 which is the join destination entity is “event place A + entity 2”.

As described above, the SI-SW that establishes the shared link can be uniquely identified by the global entity name, and by extension, the event place A
It becomes possible to participate in. In this way, the SI-SW, which is the shared link or the establishment destination of the session, is virtualized as the global entity name, so that the owner of the entity or the like is not directly aware of the SI-SW.

<SE plug-in method> FIG.
The operation of incorporating the SE into the entity shown in FIG. (1) The owner of the entity instructs the control panel to plug in the application. At this time, the executable file name of the application to be plugged in is given as a parameter. (2) The control panel notifies the entity control unit of the fact that the plug-in instruction has been received and the execution file name of the application to be plugged in.

(3) The entity control unit stores the name of the executable file to be plugged in, activates the application using the given executable file name, and executes the SI
-Establish a session between SW and the launched application. That is, the plugin in SIONet is
It is nothing but establishing a session between the application and the SI-SW. In SIONet, all operating entities such as SE and NE cooperate through a session. Therefore, plug-in / plug-out (attachment / detachment) can be easily realized, and the plug-in / plug-out does not affect other operation entities (super loose coupling). By extending this idea, S
E sharing can be realized.

<PREFERENCE ARCHITECTURE> SIONet adopts the concept of a reference model as shown in FIG. The PREFERENCE architecture shown in Fig. 12 is an architecture for building a listening-only society (need-listening type cyber society) in which semantic information is registered in a filter and distribution conditions (matching conditions) are set in the semantic information part of an event. We provide a total solution for the less distribution model, brokerless search model, and brokerless policy model. Specifically, it consists of a stream interface, SIONet, COMNet, etc. SIONet is an event transmission layer and provides a network interface to upper layers.
The middleware layer is the community (community network: COMNet) and corresponds to the intelligence layer of SIONet. In this layer, information localization, authentication,
Security, information rights guarantee, policy control, etc. are performed. The top layer is the application layer. SE is implemented in this application layer. Examples of SE include personal TV stations and smart messengers of message exchange services.

As described above, SIONet provides a common P2P network platform for all P2P services (SE provides services) such as distributed computing, information exchange, collaboration, and message distribution, and plug-ins. Supporting the efficiency of application development by providing a mechanism.

<Role of Entity in SIONet> SI
ONet is a form in which individual entities help each other to build a volunteer-type network, and each self-organizes the network through autonomous distributed coordination. For example, in the configuration of FIG.
An operation in which the entity 2 participates in the event place generated by the entity 1 and then the entity 1 leaves the event place will be described.

The entity 1 creates an event place in advance and participates in the event place. Here, when the entity 2 requests the entity 1 to join the event place, an SI-SW is generated in the entity 2, as shown in FIG. A shared link is established between them to form an entity group. In this way, SI-S of entity 1 and entity 2
After the shared link is established between Ws and the entity 2 joins the event place, the entity 1 who is the creator of the event place leaves the event place. Then, the shared link between SI-SW is released, and after that, the construction and operation of the event place is continued only by entity 2. In this way, since each entity self-organizes, even if one entity leaves or disappears, another entity functions as the entity.

In SIONet, P2P networks of various forms can be constructed by arranging and combining entities according to the purpose. Also, different forms of P2
P networks can be linked seamlessly. This is achieved by implementing the following: (1) Autonomous decentralized cooperation of all entities by a unified and simple mechanism called "chain reaction based on stimulus and fire" (2) Reduction of differences in P2P network form to entity placement / management problem As described above, one of the features of SIONet is that it is possible to build various forms of P2P networks with a single mechanism.

<Shared Link> “Shared link (shared link)” is a concept for bidirectional event sharing between a plurality of different entities.
For example, as shown in FIG. 14, the entity 2 and the entity 1 share a shared link (SL).
As shown in FIG. 15, the SI is
-A shared link is established between SW2 and SI-SW1,
A new entity group is created. That is,
The shared link is a mechanism for forming an entity group, and is also a multi-hop route.

In FIG. 14, for the entity 2 that has successfully established the shared link, the event place name (global entity name) from the entity 1, the event transfer method (routing method) in the event place, and the description of the event place ( And various information such as plugged-in SE information is transmitted. It should be noted that various event routing methods can be dynamically set between SI-SWs by setting filter values by SI-R described later. In the following, the operation of establishing a shared link will be described, and the role and mechanism of SI-R will be described in detail.

<Establishment of Shared Link> A mechanism up to establishment of a shared link will be described with reference to FIGS. 14 and 15. First, consider a case in which the entity 2 issues a shared link establishment request to the entity 1 in FIG. (1) Entity 2 issues a shared link establishment request to entity 1.

(2) As shown in FIG. 15, the entity control unit of the entity 1 has a meaning to the NE factory to establish SL _1,2 (shared link for receiving an event from the entity 2). Informed
SI-R _1,2 that performs event routing (event transfer) between SI-SWs is dynamically generated inside entity 1. Furthermore, the entity control unit stores that the entity 2 is a shared link establishment request source.
Strictly speaking, the entry point of the entity 2 and the global entity name (SI-SW2) are stored as a shared link establishment request source.

(3) The SI-R ₁ , 2 requests the entity 2 to establish an event reception session, and the SI-S ₁ , 2
An event reception session is established for W2. At this time, the filter indicating the condition of the event received by the entity 1 is registered in the SI-SW2. In addition, SI-R _1,2
Establishes a session for event transmission to SI-SW1 to which it belongs. Such a combination of transmission / reception sessions established by SI-R is called a shared link. This establishes SL _1,2 , for example SE4 is SI
-The event sent to SW2 is also sent to SI-SW1 via SI-R _1,2 .

(4) At this time, the event transfer method can be dynamically controlled by the setting value of the filter registered by the SI-R _{1, 2} with respect to the SI-SW ₂ . An example is shown below. (A) Unconditionally transfer the event sent to SI-SW2 to SI-SW1. That is, SI-R _1,2 is fired for all events. This is a filter that SI-R registers in SI-SW as follows: "A wild card is added to the vocabulary concept to be acquired, and the matching condition with the semantic information (vocabulary) is true."
It becomes possible by setting. This is called "unconditional routing". This setting only needs to be done once when the shared link is established. In this method, unnecessary event transfer and event matching process overhead at the transfer destination may occur, but since the overhead for event path establishment (setting of routing information) described later does not occur, the number of registered filters is reduced. This method is effective when it is sufficiently larger than the number of events sent. This routing method is mainly used for multi-hop type broadcast communication.

(B) Transfer only the necessary events for the entity 1 from SI-SW2 to SI-SW1. As a result, unnecessary event transfer is not performed. That is, SI-R _1,2 is fired only for a specific event. this is,
SI-R sets only the vocabulary concept (the matching condition is always true) in the filter as "event routing by vocabulary concept",
It is roughly divided into "event routing by vocabulary" which sets a matching condition between the vocabulary concept and vocabulary in a filter. The former is mainly used for multi-hop type multicast communication with attributes, and the latter is mainly used for multi-hop type unicast communication and multi-hop type multicast communication. This is fault handling notification, statistic information notification, alive notification, reply notification,
Used in advertisement notifications. In addition,
In addition to multi-hop communication such as multi-hop broadcast communication, multi-hop attributed multicast communication, multi-hop unicast communication, and multi-hop multicast communication, the filter value set by SI-R allows Direct communication using an entry point is also possible. Further, the multi-hop type broadcast communication, the multi-hop type attribute-added multicast communication, the multi-hop type unicast communication, and the multi-hop type multicast communication will be described later.

(4) The above procedures (2) to (3) are similarly performed in the entity 2 which is the source of the shared link establishment request. That is, the entity control unit of the entity 2 stores the entity 1 (SI-SW1) as a shared link establishment request destination, and
To establish the SL _2,1, dynamically generate the SI-R _2,1 to NE factory. The generated SI-R _2,1 registers a filter in the SI-SW ₁ and establishes a shared link as in the above. As a result, a bidirectional shared link is established between SI-SW1 and SI-SW2, and it becomes possible to share events between entities. SI-R
By not registering the filter, the unidirectional shared link can be established, that is, SI-R cannot be fired.

<Establishment of Event Path> The route selection information for event transfer (event routing) (set of filters registered by the SI-R for event sharing) is called an “event path”. For example, as shown in FIG. 15, let us consider a case where the entity 3 and the entity 3 each establish a shared link with the entity 1, and the SE 3 of the entity 2 registers a filter with the SI-SW 2. At this time, SI-R _{2,1 of} entity 2
Registers the filter registered by SE3 in SI-SW1 of entity 1 via the reception session. Similarly, the SI-R _1,3 of the entity 1 registers the filter with the SI-SW 3 of the entity 3 via the reception session.
In this way, SI-R is triggered by the filter registration by SE3.
The event path is established by the filters registered in (1) propagate to adjacent SI-Rs in sequence based on the shared link. This is called "event path setting or ripple".

Here, the establishment of the event path for the above-mentioned "event routing based on the vocabulary concept" will be described. In FIG. 15, in order to establish an event path for “event routing according to the vocabulary concept”, in the filter registered by the SE3 of the entity 2 with respect to the SI-SW2, SI-R _2,1 is the event type only. Set (matching condition is always true) as a filter to SI-SW1 of entity 1. That is, the matching condition registered by SE3 as a filter is not used. That is, by utilizing only the event type, for example, entity 1
When SE1 sends an event, only the event type is checked in SI-SW1. As a result, when SI-R _2,1 fires, SI-R _2,1 sends the event to SI-SW2, SI-SW2 collates with the semantic information.

Further, the establishment of an event path for the above-mentioned "event routing by vocabulary" will be described. In FIG. 15, when the event path for “event routing by vocabulary” is established, the SI-R _2,1 of the entity 2 uses the filter value registered by the SE 3 as it is as the filter value to the SI-SW 1 of the entity 1. Set. That is, SI-R _2,1 is a form in which both the event type and the semantic information registered by SE3 as a filter are registered in SI-SW1 of entity 1 as a filter, and complete filtering is performed in SI-SW1.

Therefore, in the vocabulary event routing method, no unnecessary event transfer occurs, but
Since the event path setting overhead for routing becomes enormous, this method is effective when the number of event transmissions is sufficiently larger than the number of filter registrations. On the other hand, the routing method based on the event type is positioned as a compromise between the above-mentioned two methods. That is, it is effective when the number of registered filters and the number of sent events are about the same, or when the ratio of the number of registered filters and the number of sent events cannot be predicted. With these mechanisms, event multi-hop communication based on semantic information is realized. In addition, when the event place is generated, or S
When registering the filter from E, the event routing method can be specified.

The request for setting the event path spreads to all SI-Rs in the event place, but the spread range can be limited by the TTL value. The operation will be briefly described with reference to FIG. Here, for convenience of explanation, the establishment of an event path for vocabulary concept routing is assumed, but the present invention is not limited to this. Further, each entity advertises (registers a filter) the same vocabulary concept. Also, the TTL value will be described as 2.

In FIG. 16A, the entity 2
SI-R starts the request for setting the event path. here,
Since the TTL value is 2, the event path setting request spreads only to the entity 1, the entity 3, and the entity 4, and as a result, the event path is established as shown in FIG.

Similarly to the above, when the SI-R of the entity 11 initiates the event path setting request, the entity 1
An event path is established for 0 and entity 9. In the configuration shown in FIG. 16, when the SI-R of the entity 2 and the SI-R of the entity 11 request the setting of the event path, the event path is not set in the entity 5, so that between the entity 2 and the entity 11,
Events are not shared. That is, entity 2
The event generated from does not cause a chain reaction to the entities 5 to 11, and the event is not transferred to the entities 5 to 11.

However, as shown in FIG. 16B, when the SI-R of the entity 5 starts the event path setting request, the entity 4, the entity 5, the entity 6, the entity 7, and the entity 9 are sent to the entity 4. The event path is established. as a result,
As shown in FIG. 16C, the event path is established for all entities in the event place except the entity 8.

In this way, the vocabulary concept is frequently used in the event place (having a high reputation,
Eventually, establishment of the event path will be prevalent in the event place. On the contrary, less popular vocabulary concepts will eventually be filtered out, which allows a gradual chain reaction to be realized. The number on the event path in FIG. 16 indicates the multiplicity.

The entity can disclose the multiplicity of the event path as an attribute of the entity property. On the other hand, the entity property discovery can discover an entity with a high event path multiplicity. At this time, by resharing the shared link for the entity, like-minded people (like-minded entities) can gently gather in the vicinity (localization of like-minded entities). Details of entity properties will be described later.

From the perspective of distributed object technology, the event path can also be interpreted as follows. Entities that are hyperdispersed around the world have some "correlation" between them. There are various properties such as entity name, group name, and attributes (position, interest, reputation, fashion, service) that give the correlation. Entities have a connection between the entities and cooperate in a distributed manner based on the correlation. This entity correlation is called an entity property.

In SIONet, this correlation is expressed by a vocabulary concept and a vocabulary, and is set as an event path based on the shared link. The strength of the correlation corresponds to generalization / specialization of the vocabulary concept, multiplicity of event paths, and the like. That is, in SIONet, the correlation between entities is dynamically controlled and managed by the event path. This is the control of the chain reaction by the filter. Therefore, the entity does not have a fixed entity identifier.

For example, the IP address is a fixed identifier of the entity based on the position, but in SIONet, instead of this, what describes the entity property as the vocabulary concept / vocabulary is used as the entity identifier. By registering these as filters in SI-SW, the entity declares the property (entity identifier) of the entity and advertises its property based on the shared link. This corresponds to the spread of the event path. This establishes the event path.

As described above, SI-R is a network entity having both aspects of event transmission and event reception, and is essentially the same as a general service entity. In SIONet, an entity used for controlling SIONet such as SI-R is a service entity (S
E) and the network entity (N
E). In SIONet, all entities, service entities and network entities, are treated as a common entity, and further, they operate autonomously according to a simple and consistent common logic of event transmission and event reception, that is, a chain reaction of stimulus and fire. , Provides a super-distributed and super-loosely coupled architecture in which all entities can be autonomously distributed and cooperated.

<Disconnection and Reestablishment of Shared Link> When an entity participating in the event place falls into a failure or leaves the event place, the entity cannot participate in the network operation for various reasons. In some cases, it will be necessary for the remaining entities to be able to continue network services by self-organizing. In such a case, SIONet releases the shared link established between SI-SW and re-establishes the shared link. The operation will be described with reference to FIG.

In FIG. 17, the leading numerals (in the figure, etc.) of the shared link establishment request indicate the order of those requests. That is, regarding the order of the shared link establishment request, first, the entity 2 makes a shared link establishment request to the entity 1. Next, the entity 3 requests the entity 2 to establish a shared link. Finally, it is assumed that the entity 4 requests the entity 2 to establish a shared link. Here, "each entity establishes a shared link based on a link topology that can request an establishment request for a shared link at most once within the same event place, but can accept the establishment request indefinitely. We propose a link establishment method. This ensures that no loops occur between the entities linked by the shared link. That is, by using this method, the open link topology can be easily realized only by reestablishing the link between adjacent entities.

When the establishment requests are successful in the above order, the shared link is established between the SI-SWs by the procedure described above. When the shared link is established, the entity control unit of each entity stores the entity that has made an establishment request and the entity that has accepted the establishment to itself. For example, the entity 2 holds a list of the entity 1 that has requested establishment by itself and the entities 3 and 4 that have received the establishment request from itself. In this situation, for example, when the entity 2 leaves or is removed, the shared link release request is issued to the SI-SW 2 of its own, and the shared link is released. After that, each entity establishes a new shared link. Less than,
The operation will be described.

(1) When the entity 2 leaves, the entity control unit of the entity 2 notifies the one-hop entity (entity 1, entity 3, entity 4) of releasing the shared link of itself. . This can be achieved by setting the TTL value of the event to 1 and sending the event. At this time, for the entity (entity 3, entity 4) that has accepted the establishment of the shared link to itself, the entity 1 that itself has made the establishment request as the destination of the new shared link establishment request in place of itself. teach. If the entity that has made the establishment request does not exist, the establishment request source entity (1
(Hop destination entity), and selects an arbitrary entity as a request destination for establishing a shared link in place of itself.

(2) The entity control unit of the entity 2 has shared links (SL _2,1 , SL _2,3 established by itself).
, SL _2,4 ), to that effect SI-R _2,1 , SI-R
Notify _{2, 3} and SI-R _{2, 4} (not shown). SI-R
₂ , ₁ , SI-R _2,3 , and SI-R _2,4 are the SI-Rs of the entity 2, and as described above, the shared link SL _2,1 for the entity 1, the entity 3, and the entity 4. ,
SL _2,3 and SL _2,4 are established. These SI-R
Using this as a trigger, the session of entity 2 to SI-SW2 is released.

(3) The entity control unit of entity 1 uses SI-R _1,2 (not shown) and shared link SL _1,2
Instruct to cancel. SI-R _1,2 is shared link SL
Release ₁ and ₂ . Entity 1 is entity 3,
Wait for the establishment request from the entity 4. (4) The entity 3 and the entity 4 are SI-SW2 (SI-SW of the entity 2) as in the case of the entity 1.
2) The established shared link (SL _3,2 , S
L _{4, 2} ) are all released, and a request for establishing a shared link is made to the new entity (entity 1) that has been taught by the entity 2 as a request destination for establishing a shared link, and the shared link is reestablished. That is,
Similar to the above, each entity control unit causes the NE factory to generate SI-R _3,1 and SI-R _{4,1 respectively,} and
_Establish shared links SL _3,1 and SL _4,1 to _3,1 and SI-R _4,1 .

As described above, the shared link establishment process and the re-establishment process are performed only between adjacent entities and do not affect other entities. That is, there is no need to rebuild links for all entities.

Note that not only the shared link release request that has taken a proper procedure such as the removal of the entity or the removal of the entity but also the failure of the entity, the power interruption, the failure of the session (physical communication path), etc. , There are cases where shared links have to be reestablished. However, in such cases, it may not be possible to teach the alternate entity that is needed when re-establishing the shared link. In SIONet, in order to deal with such a situation, each entity sends out an event of n hops (n is an arbitrary natural number) to grasp an alternative establishment request destination entity. In addition, SIONet
Then, more detailed hop control can be performed by using the TTL value and the hop attribute. Examples of hop attributes are:

Only the entity requested to establish the shared link is the hop target. Only the entity requesting the establishment of the shared link is targeted for hop. All entities are hop targets.

An example of the event flow when the hop attribute of is specified is shown by the broken line in FIG. In FIG. 18, (i / j) is shared link establishment information stored in each entity. i indicates the entity to which the entity has issued the shared link establishment request, while j indicates the entity from which the entity has accepted the shared link establishment request. For example, (2/5, 6) of the entity 3 indicates that the entity 3 makes an establishment request to the entity 2 and receives the establishment request from the entities 5 and 6. Since each entity holds the shared link establishment information, for example, when the entity 3 makes another shared link establishment request to another entity, the request can be rejected as an error. This guarantees the consistency of the open link topology described above. In this situation, the entity 6 can detect the existence of the entity 1 and the entity 2 by sending out the event having the above-mentioned hop attribute in 3 hops, and these become alternative entities when the failure of the entity 3 occurs. .

The above-mentioned hop attribute is used not only for searching for an alternative entity at the time of failure but also for searching for an entity that can accept the establishment of the shared link, and for the top entity (who has not established the shared link). It is effective for searching. With SIONet, only the top entity can establish a federation (corresponding to a shared link between event places) to other event places.

<Purpose of Adding / Decreasing Online> The purpose of adding / decreasing entities in SIONet is mainly classified into the following two. (1) From the viewpoint of improving the total processing capacity of the event place, the number of entities in the event place is increased and the load of the event filtering process is distributed. From the opposite viewpoint, the number of entities is reduced. It is mainly used in the operation of hybrid P2P and backbone P2P networks. (2) A flexible and global P2P network is constructed in a bottom-up manner by flexibly establishing shared links for dynamically generated entities. It is mainly used in the operation of pure P2P networks.

The hybrid P2P network is configured, for example, by an operator such as a network provider generating an event place in a host or the like in advance, and a service entity such as a personal terminal connecting with the event place by a session. It is a network. A pure P2P network is a network configured by connecting entities, which are individual transmission / reception terminals, by shared links, and the minimum unit for sharing an event is an event place. The backbone type P2P network refers to a connection form between networks, and for example, a network in a state where pure type P2P networks in a plurality of regions are connected via a hybrid type P2P network.

<Form of increase / decrease> Although several types of increase / decrease are provided in SION, typical forms shown in FIGS. 19 and 20 will be described here. (1) Combining and Separation of Event Places As shown in FIG. 19A, a plurality of event places can be combined. Here, “synthesis” refers to gathering entities belonging to a plurality of event places as members in one event place.
As a typical example, service integration (information sharing) based on a business alliance between different service operators can be considered.

In this case, by issuing a combining request to an arbitrary entity belonging to the event place or the event place, a shared link establishment request is issued to the entity in the combining request destination event place. As a result, a shared link is established between SI and SW, and both can be combined. It should be noted that the request source and the request destination of composition may be either entities or event places. On the other hand, in the case of division, the established shared link is released and the event places are separated.

(2) Joining and leaving the event place As shown in FIG. 19B, an entity in the event place or a join to the event place is joined.
By making a (join) request, the requesting entity
SI-SW is generated. Then, the shared link establishment request is issued to the requesting entity, the shared link is established between the SI and SW, and it is possible to participate in the event place. When the entity leaves the event place, the shared link between the entities is released, the shared link is reconstructed, and the entity leaves the event place, as described above. At this time, the state of the withdrawn entity transits to the suspend state.

It is also possible to incorporate the entity into the event place by requesting the entity to establish a shared link from the event place side. This is called absorption. The opposite is called division. (3) Increasing / decreasing the number of entities (SI-SW) As shown in FIG. 20 (c), when an entity expansion request is made to an entity in the event place or to the event place, SI is added to the specified entity. -SW is newly created and a shared link is established with the existing SI-SW. On the other hand, when an entity deletion request is made to the event place, a shared link cancellation request is issued to the specified entity, and SI-S
After the shared link between W is released, the shared link is reestablished and the relevant entity is deleted. At this time, the state of the entity transits to Non-Existent.

(4) Federation between Event Places As shown in FIG. 20 (d), by issuing a federation (cooperation) request to an entity in an event place or to an event place, an event is generated between event places. The SI-GW that transfers the event is dynamically generated, and both event places work together via the session. The federation request source and the request destination may be either an entity or an event place.

<Entity Advertisement> The entity advertisement (publication) will be described with reference to FIGS. Entityet advertisement in SIONet has the following two viewpoints. Viewpoint 1: Entrance Advertisement Viewpoint 2: Entity Property Advertisement Each view is described below. Viewpoint 1: The advertisement-based event place at the entrance is an event place that is a base (starting point) for an entity to search for an optimal event place using a formula. In other words, the base event place is the entrance to SIONet. Therefore, the entities participating in the base event place can open the entrance of SIONet. Here, opening the entrance means advertising the entry point and global entity name of the entity that is the request destination for establishing the shared link. This public information is discovered by a search using broadcast described later.

Viewpoint 2: Advertisement of Entity Properties In each entity group (all event places including the base event place) connected by a shared link, each entity can advertise its own entity property.
This corresponds to the spread of the event path described above. This public information is discovered by sending a discovery event described later.

From the disclosure and search of entities,
The flow up to entity group formation will be described. In the following, the base entity, entity 1,
Entity2, Entity3, Entity4, Entity5, Entity6 belong to the base event place, and Entity3, Entity11,
The entity 12 and the entity 13 will be described as belonging to the event place α.

As shown in FIG. 21, the SIONet software is installed on the host. The state of the entity at this point is "Non-Existent" as described above. For convenience of explanation, this entity is referred to as entity Y.
And By executing the SIONet software, the entity Y transits from the "Non-Existent" state to the "suspend" state. Entities in this state have not yet been acknowledged by SIONet.

Entity Y in "suspended" state
Searches for the entrances (entry points and global entity names) of other entities belonging to the base event place to join the network as a component of SIONet. Specifically, by broadcasting, a nearby entity is searched from among the entities participating in the base event place. The method of broadcasting depends on the implementation. For example, when implemented in a wireless network, all entities in the wireless reach are targets of the search.
On the other hand, if implemented in an IP network, I
P broadcast or IP multicast will be performed. FIG. 21 shows that entity 1 (entry point of entity 1 and global entity name) is discovered by the search by broadcast. If a nearby entity cannot be found by broadcasting, a Well-Known (well-known) entity can be used. Well-Kno
The wn entity is called the base entity. In addition,
The base entity can be in any event place, including the base event place.

The entity Y requests the discovered entity 1 to join the base event place. That is, the entity Y is
Make a Join request with the global entity name of as a parameter. The entity 1 that has received the join request from the entity Y accepts the join request only when its own state transition is “active” and the entrance and entity properties are in the open mode. Note that the entity Y cannot issue more Join requests than the maximum number of Joins. The maximum number of joins can be set by the owner of the entity Y or the like on the control panel of the entity Y. When the entity 1 accepts the join request of the entity Y, the shared link is established between the entity Y and the SI-SW of the entity 1 by the same operation as described above. This causes Entity Y to self-organize as a network component within the base event place. At this time, the entity Y transits from the “suspend” state to the “active” state.

The entity Y that has joined the base event place can open the entrance. Also,
You can also advertise entity properties. In the entity properties, global entity name (and entry point), nickname, group name, alive (assertion of existence only, do not disclose the entry point and global entity name that is the information to establish the shared link, entity is not disclosed. Even in mode, it is published), description (description of entity), and attributes. The attributes include SE information plugged in, event path multiplicity, event place information, and the like. XML is a description language for entity properties.

In FIG. 21, for example, the entity control unit of the entity 3 can publish the event place α in which the entity 3 participates at the same time as an attribute of the entity property. Further, the entity control unit can publish not only the event place that is currently joined, but also the event place information of the event place that was previously joined. This event place information is, for example, a description of the event place (description of the event place, explanation information),
The global entity name (event place name + entity name, connection establishment information), entry point (entry point information), etc. of the entity (semantic information switch) that established the shared link when participating in the event place. The number of event place information items that have been joined in the past can be held by the entity arbitrarily. For example, the entity owner or the like can set the information through the control panel. The entity that has acquired the published event place information presents it to the entity owner by outputting the event place information through a control panel or the like. This allows the entity owner to recognize the existence of another event place. SIONet does not have a function to centrally manage event place information such as where and what kind of event place is provided and what kind of service is provided in that event place, so when trying to acquire event place information, Event place information needs to be fetched from entity property of other entity. Not only the event place you are currently participating in but also the information about the event place you participated in in the past is disclosed, increasing the chances of acquiring event place information and increasing the probability of participating in the event place that provides the service you want .

When the entrance of the entity Y is published, these entity properties are registered as a filter in the semantic information switch in the entity, so that the entity properties are propagated to other entities based on the shared link and the event path is established. To be done. Basically, the event path establishment request propagates to all the entities in the event place, but the TTL value can limit the scope of the event path establishment request. The global entity name is used as an identifier for multi-hop unicast communication.
The group name is used as an identifier in the multi-hop type multicast communication, and the attribute is used as an identifier in the multi-hop type attribute-added multicast communication. For example, as a typical example of multi-hop unicast communication, there is reply notification from an event receiving entity to an event transmitting entity.

That is, the multi-hop type unicast communication with global entity name is a communication method in which an SI-SW of the entity specified by the global entity name transmits an event of n hops. Also, the multi-hop type multicast communication is a communication method of transmitting an event of n hops to the SI-SW of the entity belonging to the group specified by the group name. Multi-hop attributed multicast communication is a communication method in which an n-hop event is transmitted to the SI-SW of an entity having the same attribute as itself. Also, the multi-hop type broadcast communication is a communication method of transmitting an n-hop event to the SI-SW of an arbitrary entity.

In FIG. 22, the entity Y participating in the base event place publishes the "entity property that meets its own needs" by sending out a discovery event for searching for the "event place in which he / she wants to participate". Search for the entity that is doing. This discovery event is an event used for controlling SIONet, and is equivalent to the event sent by SE. The discovery event is an event for firing the NE, and a matching condition with the entity property is set in the meaning information part of the event. That is, adding a new function in SIONet means defining a new vocabulary concept and vocabulary (not adding a mechanism but adding a chain reaction condition).
This makes it possible to add various functions with a single mechanism (chain reaction).

Here, it is assumed that the entity 3 is found as a result of the search. As described above, the entity 3 participates in the event place α at the same time as the base event place. By discovering the entity 3, the entity Y can know the existence of the event place α. Entity Y issues a Join request to event place α to entity 3, and event place α
attend to. As described above, the entity 3 accepts a Join request (shared link establishment request) when its own state transition is “active” and in the open mode.

Further, the entity Y can send an event for a similar search at the event place α. This allows you to discover new entities that meet your needs. For example, here, it is assumed that the entity 12 has been discovered. That is, the entity Y means that the entity 12 that could not be found in the base event place can be found via the entity 3. By repeating such an operation, it becomes possible to gradually reach an event place that meets one's own needs.

The advertisement system shown here has the following effects. (1) Since there is no broker (management unit) that manages the public information of the entity, it is possible to construct a self-organizing network with high fault tolerance at low cost. Also,
It is not realistic for a broker to manage a huge number of public information (entry points and entity properties). (2) Since the event places suitable for the entity can be narrowed down to the potato expression, the desired event place can be efficiently searched. For example, even if the spread range of the chain reaction (the hop count of the discovery event and the spread range of the event path setting request for the entity property) is limited by the TTL value, as described above, the entity 12 is transmitted via the entity 3. , And consequently another event place to which entity 12 belongs at the same time. In addition, by limiting the spread range of the chain reaction,
It is possible to reduce network traffic (the number of times an event is transferred, the number of times an event path setting request is transferred).

It should be noted that, without providing information (for example, without exposing the entity property),
As a penalty, an entity that only receives information from other entities may be prohibited from participating in the event place again unless the shared link is forcibly released and a certain condition is satisfied.

<SE sharing method (automatic delivery)>
An example of SE (game application program) sharing in a game event place will be described as to how the SE is shared. (1) The owner of the entity 2, which is the operator of the game event place, gives the event place name via the control panel of the entity 2. Note that the event place name given here will be described as "game".

(2) The entity control part of the entity 2 is generated by the NE factory as described above.
The global entity name "Game + Entity 2" is assigned to SI-SW. As a result, the event place is generated. At this time, the entity 2, which is the creator of the game event place, automatically participates in the event place when the event place is created. (3) The owner of the entity 2 is the entity 2
To the control panel of the game application program (SE). At this time, the execution file name of the application to be plugged in and the presence / absence of SE sharing are given as parameters.

(4) The control panel of the entity 2 notifies the entity control unit of this fact. (5) The entity control unit of the entity 2 stores the name of the executable file to be plugged in and activates the application (SE) using the given executable file name. Establish a session with. That is, the plug-in in SIONet means establishing a session between the application and SI-SW.

(6) The entity control unit of the entity 2 advertises (publishes) the entity property of the entity 2. Examples of the disclosure form of the entity property of the entity 2 are as follows.・ Entity 2 participates in the base event place,
Expose the entity properties of entity 2 in the base event place. -By the entity 2 performing a potato-based expression search,
Discover and participate in an event place closely related to the game event place, and publish the entity property of the entity 2 in the event place. -The entity 2 is the base entity. That is, the entity properties (entry point and global entity name) of the entity 2 are known.

(7) The entity 1, which knows the existence of the entity 2, requests the entity 2 to participate in the game event place. (8) If this request is approved, Entity 1
The entity 2 is requested to establish the shared link. Then, similarly to the above, the shared link is established between the entity 1 and the entity 2. (9) When the shared link is established, the shared link establishment request destination (entity 2) returns the information necessary for transmitting and receiving the event in the event place to the establishment request source (entity 1). Specifically, for example, the event place name (global entity name), whether or not the participating event place is the base event place, the event transfer method (routing method) in the event place, the event place description, the plug-in SE being done
Information (when there is SE sharing) and the like.

When the SE sharing is shared, the SE information returned to the shared link establishment request source is, for example, the execution file name of the application to be plugged in or the file of the application. (10) Upon receipt of the file, the entity control unit of the entity 1 starts the application using the given executable file name and establishes a session between the SI-SW in the entity 1 and the application, as described above. Establish. As a result, the game application program is plugged into the entity 1 as an SE.

That is, participation in the event place means that the participants share the application program that has been plugged in by forming an entity group linked by a shared link. As a result, just by participating in the event place, the entity that is a member in the event place can automatically use the plug-in application. When the entity 1 leaves the game event place, the plugged-in game application program is plugged out.
At that time, the entity 1 can keep the received file, and at the time of plug-out,
The file may be deleted.

The above-described operation is application sharing in a pure P2P network environment. for that reason,
Since the distribution of the application program is performed only between the shared link establishment destination entity and the establishment source entity, it does not affect other entities already linked by the shared link. That is, since the processing is localized between two parties for file transfer, scalable SE sharing can be achieved.

<Business model> Here, the above-mentioned SION
An example of providing et as a service will be described. (1) Client server model In this mode, the event place is operated only by a predetermined entity. That is, only a predetermined entity can participate (Join) in the event place, and the entity permitted to participate can establish a shared link between the entities,
Configure an entity group. On the other hand, the other entities establish a session with the entity group and send and receive events via the session. That is, the event place (a group of predetermined entities) is a server, and the other entities are clients. In this business model, each entity that is a member of the entity group behaves as an autonomous distributed computer, and when an arbitrary entity fails, the remaining entities self-organize and continue to operate the event place. Also, if it is desired to improve the processing capacity of the server, a new entity may be allowed to participate in the event place. Therefore, as compared with the conventional server implementation method, it is possible to realize a server that is more resistant to faults, inexpensive, and scalable.

(2) Hybrid Model For example, the entity that is the operator of the game event place creates the game event place and becomes the base entity in the event place. on the other hand,
The entity positioned as the user of the game event place enjoys the service at the event place by participating in the event place. In the conventional client server model, new capital investment (CPU power, storage, communication bandwidth, etc.) was required in proportion to the increase in the number of users, but this business model is based on the fact that users participate in event places. Since the user's own entity is provided for the service operation, the event place operator does not need a new capital investment. Therefore, it is cheap and scalable.
Can build a P2P service environment. The base entity can authenticate and charge a user (entity) participating in the event place. In addition, the base entity discovers an entity (alternative entity) capable of establishing a shared link from the entity group by sending out a discovery event, and notifies the discovered entity to the entity wishing to participate, It is also possible to establish a shared link between them.

(3) Pure model This is a business model in which all entities can freely participate in (leave) the event place. As mentioned above, in SIONet, various business models can be realized with a common mechanism by returning to the operation / location problem. Therefore, it has a great effect on development man-hours, scale, debugging efficiency, easiness of maintenance and the like.

As described above, the entity in the "suspend" state cannot expose the entrance or the entity property. An entity in the "suspend" state transitions to the "active" state by joining an arbitrary event place. Only entities in the “active” state can expose entrances and entity properties. Also,
Only the entity joining the base event place can open the entrance. When satisfying "publication is instructed by control panel" and "the number of established sessions (shared links) for the entity does not exceed the default value",
Entities can actually expose entrances and entity properties. For example, even if the owner of the entity uses the control panel to instruct publication, if the shared link has been established beyond the default value, the private mode is automatically entered. The default value can be set on the control panel, and for example, the owner of the entity can set the default value according to the capability of the entity.

A network entity, a network entity factory, an entity control unit,
The control panel, the service entity, the semantic information switch, the semantic information router, and the semantic information gateway may be realized by dedicated hardware, and are composed of a memory and a CPU (central processing unit) and have their functions. The function may be realized by loading a program for realizing it into a memory and executing it.

Also, a network entity, a network entity factory, an entity control unit,
A program for realizing the functions of a control panel, a service entity, a semantic information switch, a semantic information router, and a semantic information gateway is recorded in a computer-readable recording medium, and the program recorded in this recording medium is read into a computer system. It may be realized by executing. The “computer system” mentioned here includes an OS and hardware such as peripheral devices. In addition, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.

The "computer-readable recording medium" means a flexible disk, a magneto-optical disk,
A portable medium such as a ROM or a CD-ROM, or a storage device such as a hard disk built in a computer system. Furthermore, "computer-readable recording medium"
Means a program that dynamically holds a program for a short period of time, such as a communication line for transmitting a program through a network such as the Internet or a communication line such as a telephone line, and a server or client in that case. Such a volatile memory inside a computer system that holds a program for a certain period of time is also included. Further, the above program may be one for realizing some of the functions described above, and may be one that can realize the above functions in combination with a program already recorded in the computer system. The embodiment of the present invention has been described in detail above with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like without departing from the scope of the present invention.

[0124]

As described above, according to the entity device, the naming method, the recording medium, and the program according to the present invention, even if any entity leaves or joins,
It is possible to provide an entity whose function as an event place is not hindered.

[Brief description of drawings]

FIG. 1 is a diagram illustrating an entity according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating classification of entities in the same embodiment.

FIG. 3 is a diagram illustrating state transition of an entity in the same embodiment.

FIG. 4 is a diagram illustrating an internal configuration of an entity in the same embodiment.

FIG. 5 is a diagram illustrating generation of an event place in the same embodiment.

FIG. 6 is a diagram illustrating an operation in which an entity participates in an event place in the embodiment.

FIG. 7 is a diagram illustrating a semantic information switch and a session in the same embodiment.

FIG. 8 is a diagram illustrating a configuration of an event in the same embodiment.

FIG. 9 is a diagram illustrating a semantic information system in the same embodiment.

FIG. 10 is a diagram illustrating a global entity name in the same embodiment.

FIG. 11 is a diagram illustrating a plug-in of a service entity in the same embodiment.

FIG. 12 is a diagram illustrating a reference model in the embodiment.

FIG. 13 is a diagram illustrating a shared link in the same embodiment.

FIG. 14 is a diagram illustrating a shared link in the same embodiment.

FIG. 15 is a diagram illustrating a shared link in the same embodiment.

FIG. 16 is a diagram illustrating an event path in the same embodiment.

FIG. 17 is a diagram illustrating reestablishment of a shared link in the same embodiment.

FIG. 18 is a diagram illustrating a hop attribute in the same embodiment.

FIG. 19 is a diagram for explaining image reduction of event places and entities in the embodiment.

FIG. 20 is a diagram illustrating event place and image deletion of an entity in the same embodiment.

FIG. 21 is a diagram explaining an advertisement of an entity in the same embodiment.

FIG. 22 is a diagram for explaining an advertisement of an entity in the same embodiment.

FIG. 23 is a diagram showing a transition of a business model of a communication network.

FIG. 24 is a diagram showing dimensions of a P2P model.

FIG. 25 is a diagram illustrating the concept of SIONet.

Claims (4)

[Claims] 1. An entity device that transmits and receives an event consisting of data and semantic information of the data, and a semantic information switch that transmits the event to another entity device based on the semantic information of the event. And a control unit that sets the name of the semantic information switch from the name of the entity device and the name of the event place that is the event place in which the entity device participates and that indicates the spread range of the event. The entity device to perform. 2. A naming method by an entity device for transmitting and receiving an event comprising data and semantic information of the data, wherein the name of the entity device and an event place in which the entity device participates, and the event And a name of an event place indicating a spread range of the event place, and a name assigning method including a step of setting a name of a semantic information switch for transmitting the event to another entity device based on the semantic information of the event. 3. A name giving program by an entity device for transmitting and receiving an event consisting of data and semantic information of the data, the name of the entity device and an event place in which the entity device participates, the event being the event place. Embedded program that causes a computer to execute the step of setting the name of a semantic information switch that transmits the event to another entity device based on the semantic information of the event based on the name of the event place indicating the spread range of the event place. 4. A name giving program by an entity device for transmitting and receiving an event consisting of data and semantic information of the data, wherein the name of the entity device and an event place in which the entity device participates and the event And a name of the event place indicating the spread range of the event place, a computer recording an embedded program for causing the computer to execute the step of setting the name of the semantic information switch for transmitting the event to another entity device based on the semantic information of the event. A readable recording medium.