JP3987817B2 - Entity device, service sharing method, and computer program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an entity device, a service sharing method, and a computer program.
[0002]
[Prior art]
In recent years, a new concept of “brokerless search model” has been devised in the networking industry. This brokerless search model is equivalent to P2P (Peer-to-Peer) that has gained worldwide attention, such as Gnutella, which was announced in March 2000. JXTA, announced in April 2001, also corresponds to P2P, a brokerless search model. P2P is an innovative technology since the WWW and is called the third generation. In recent years, research and development of brokerless transmission models that apply the P2P concept to the transmission layer and brokerless policy models that apply the P2P concept to the policy layer have become active. The dimensions of the brokerless (distribution) model are shown in FIG. One of these brokerless search models is SIONet (Semantic Information-Oriented Network).
[0003]
SIONet is a meta network that delivers an event composed of data and semantic information of the data based on semantic information (metadata). As shown in FIG. 24, the event receiver registers semantic information indicating the condition of the event to be received in advance in SIONet. When an event is transmitted from the event sender to the SIONet, the SIONet collates the semantic information of the event with the registered semantic information, and transmits the event 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 notifying the event recipient who registered the semantic information of the event. It is called “ignition”.
[0004]
As a result, it is possible to dynamically search and discover a specific entity from among an unspecified number of entities that are super-distributed on the network. That is, SIONet is a network that delivers events based on semantic information (sending to whom) instead of the destination address (sending to whom) used in the conventional network.
[0005]
SIONet is an autonomous distributed cooperative network (autonomous distributed computer) in which all entities including the components of SIONet perform autonomous distributed cooperation to self-organize the network. Network components of SIONet include "Semantic Information Switch (SI-SW)", "Semantic Information Router (SI-R)", "Semantic Information Gateway (SI-GW)", "Event Place", "Session", etc. These can be self-organized as needed to build a secure and scalable P2P network with a bottom-up approach.
[0006]
The basic concept and principle of SIONet is simple and unified. Repeating the simple operation of “registering a filter by an entity and dispatching an event”, that is, “entity“ stimulation ”and“ ignition ”“ chain reaction ”between the network components of SIONet. The thing that controls the behavior of this chain reaction is the semantic information registered in the SIONet by the above-mentioned event receiver, and this is called the “filter”. The method of chain reaction of entities can be dynamically controlled by the filter value registered in the filter. Another basic concept in SIONet is event place. An event place is an entity group connected to each other by a shared link, thereby limiting the scope of a chain reaction.
Details of SIONet are described in Non-Patent Documents 1 and 2. The applicant of the present invention has previously filed an application relating to SIONet according to Japanese Patent Application No. 2001-394980.
[0007]
[Non-Patent Document 1]
Takanari Hoshiai, Keiichi Koyanagi, Birge Sukubatar, Kei Kubota, Hiroshi Shibata, Takamichi Sakai, "Semantic Information Network Architecture", IEICE Transactions B, Vol. J84-B, No. 3, pp. 4, 11- 4,2,4 (2000.7 reception, 2001-3 publication)
[Non-Patent Document 2]
Takanari Hoshiai, Hiroshi Shibata, Takamichi Sakai, Keiichi Koyanagi: "Semantic Information Network Architecture: SION Architecture", NTT R & D, Vol.50, No.3, pp.157-164 (Received 2000.12, published in 2001.3)
[0008]
[Problems to be solved by the invention]
SIONet advocates the concept of an event place. An event place is a spillover range of an event or an event path, in other words, a group of entities linked by a shared link. In this event place, each entity establishes a connection by connecting each included semantic information switch by a session or a shared link. Participation in the event place means that an entity group connected by a shared link is formed, and the participant shares the plug-in-completed application program. That is, an application plugged into another entity that is a member in the event place can be automatically used only by the entity participating in the event place. Conventionally, as a method of sharing an application among entities participating in an event place, there has been a method of downloading and holding an application program to all entities in the event place. However, this has a problem that application program copy processing, that is, overhead associated with download is applied. As another method, there is a method of holding an application program only in the plugged-in entity as in the conventional client-server system. However, this has a problem that it must always be aware of which entity the application program is implemented.
[0009]
The present invention has been made in view of such circumstances, and an application program is arranged according to the topology and the operating environment of the entity, and the application is arranged in the event place while hiding the arrangement and implementation method of the application program. It is an object to provide an entity device, a service sharing method, and a computer program that can be shared.
[0010]
[Means for Solving the Problems]
The present invention has been made to achieve the above object, and the invention according to claim 1 is an entity device constituting a semantic information network, which is a P2P network, and another entity device constituting an event place. A connection requesting unit for requesting participation in the event place, and a connection establishing unit for establishing a shared link with the other entity device as a participation request destination when the participation request is approved by another entity device. And a service for identifying and using the application software that constitutes a part of the application software plugged into the other entity device in the event place from the other entity device of the participation request destination Receive this entity transfer and make this service entity internal An automatic plug-in means for plug-in and a service executed by application software that is plugged into another entity device in the event place and that can be used by a service entity plugged in by the automatic plug-in means. Service providing means, wherein the automatic plug-in means is configured such that the number of hops between the own entity device and another entity device in the event place is the number of hops designated by the other entity device in the event place. Outside The other entity devices in the event place correspond to a branching point on the shared link topology, the other entity devices in the event place may have an entity processing capability, an application type, an entity execution form, Either the specified operating environment attribute indicated by one or more of the internal entity entity locations is satisfied, or the number of other entity devices that use the same service entity is less than the specified number In Is Service entity entity It is an entity device characterized by receiving the transfer.
[0011]
The invention according to claim 2 is an entity device that constitutes an event place in a semantic information network that is a P2P network, a participation request receiving unit that receives a request to participate in the event place from another entity device, When approving the participation of the other entity device that has made the request, connection establishment means for establishing a shared link with the other entity device, and the other entity device that has requested the participation in the event place Transfer means for transferring a service entity for identifying and using the application software, which constitutes a part of other entity devices or application software plugged into the device, The other entity that requested the participation I device, several stages of hops to specify other entity device or self entity device of the event in a place Outside If Self When an entity device is a branch point on the shared link topology, Self When the entity device satisfies a predetermined operating environment attribute indicated by any one or more of the processing capability of the entity, the application type, the entity execution form, and the location of the internal entity entity, or the same service entity is used. In any case where there are fewer other entity devices Is Service entity entity It is an entity apparatus characterized by transferring.
[0012]
The invention according to claim 3 is a service sharing method used for an entity device that participates in an event place in a semantic information network that is a P2P network, in which the participation request means configures an event place. Requesting participation in the event place to the other entity device, and the connection establishment means, when the participation request is approved by the other entity device, the other entity device of the participation request destination A connection establishment process for establishing a shared link with an automatic plug-in means constitutes a part of application software plugged into the other entity device in the event place from the other entity device of the participation request destination The application software An automatic plug-in process for receiving and transferring a service entity to be defined and used, and a service providing means are plugged into other entity devices in the event place, A service providing step of providing a service executed by application software that can be used by a service entity plugged in by the automatic plug-in means. In the automatic plug-in step, the automatic plug-in means The number of hops between the entity device and another entity device in the event place is the number of hops specified by the other entity device in the event place. Outside The other entity devices in the event place correspond to a branching point on the shared link topology, the other entity devices in the event place may have an entity processing capability, an application type, an entity execution form, Either the specified operating environment attribute indicated by one or more of the internal entity entity locations is satisfied, or the number of other entity devices that use the same service entity is less than the specified number In Is Service entity entity The service sharing method is characterized by receiving the transfer.
[0013]
The invention according to claim 4 is a service sharing method used for an entity device constituting an event place in a semantic information network which is a P2P network, in which the participation request receiving means is connected to another entity device. A participation request receiving process for receiving a request to participate in the event place, and when the connection establishment unit approves the participation request in another entity device, a shared link with the other entity device that has made the participation request is provided. A connection establishing process to be established, and the transfer means constitutes a part of application software plugged into the other entity device or the own entity device in the event place to the other entity device that has requested participation. Special application software And a transfer process for transferring a service entity for use, wherein in the transfer process, the transfer means sends the request for participation to another entity in the event place. Number of hops specified by the device or local entity device Outside If Self When an entity device is a branch point on the shared link topology, Self When the entity device satisfies a predetermined operating environment attribute indicated by any one or more of the processing capability of the entity, the application type, the entity execution form, and the location of the internal entity entity, or the same service entity is used. Either the number of other entity devices or the number of local entity devices is less than the specified number Is Service entity entity This is a service sharing method characterized by transferring data.
[0018]
According to a fifth aspect of the present invention, a computer used as an entity device that participates in an event place in a semantic information network that is a P2P network is requested to participate in the event place to another entity device that constitutes the event place. A step of establishing a shared link with the other entity device as a participation request destination when the participation request is approved by another entity device, and from the other entity device as a participation request destination, The service entity for identifying and using the application software that constitutes a part of the application software plugged in to another entity device in the event place is received, and the service entity is internally loaded. Providing a service executed by application software corresponding to this service entity, plugged into another entity device in the event place, and usable by the internally plugged service entity; In the step of plugging in the service entity, the number of hops between the own entity device and the other entity device in the event place is the other entity device in the event place. Number of hops specified by Outside The other entity devices in the event place correspond to a branching point on the shared link topology, the other entity devices in the event place may have an entity processing capability, an application type, an entity execution form, Either the specified operating environment attribute indicated by one or more of the internal entity entity locations is satisfied, or the number of other entity devices that use the same service entity is less than the specified number In Is Service entity entity A computer program characterized by receiving
[0019]
According to a sixth aspect of the present invention, a computer used as an entity device constituting an event place in a semantic information network that is a P2P network receives a request for participation in the event place from another entity device; When approving the request, establishing a shared link with the other entity device that has requested participation, and other entity device in the event place or itself to the other entity device that has requested participation And a step of transferring the service entity for identifying and using the application software that constitutes a part of the application software plugged in to the service software. In-up, the entity device performing the join request, the several stages of hops to specify other entity device or self entity device in the event place Outside If Self When an entity device is a branch point on the shared link topology, Self When the entity device satisfies a predetermined operating environment attribute indicated by any one or more of the processing capability of the entity, the application type, the entity execution form, and the location of the internal entity entity, or the same service entity is used. In any case where there are fewer other entity devices Is Service entity entity Is a computer program characterized by the above.
[0020]
In this specification, the entity device is a general term for all computers such as a personal computer, a workstation, an information portable terminal, a mobile phone, and a wearable computer.
An event place is a configuration in which a plurality of entities are connected by a shared link.
Shared link is software that connects two entities, and refers to software that can mutually set data transfer requirements.
A plug-in refers to a state where an application in an entity or software such as control software can transfer data to another entity through a shared link.
Further, the service entity obtained by virtualizing application software refers to data (including a program) for operating the application software.
[0021]
DETAILED DESCRIPTION OF THE INVENTION
[Details of SIONet]
<Definition of SIONet entity>
Here, all computers such as personal computers, workstations, portable information terminals, mobile phones, and wearable computers are collectively referred to as hosts. Furthermore, a host that implements SIONet software is called a “SIONet entity” or simply an “entity”. As shown in FIG. 2A, an entity (entity device) is a virtualized host in which SIONet software is implemented as a unit of autonomous distributed cooperation in SIONet. SIONet software provides a mechanism for individual entities to perform autonomous distributed cooperation. With this SIONet software, each host can become an autonomous distributed computer.
[0022]
Entities are mainly classified into the following three types as shown in FIG.
・ Applications that act as services (service entity: SE, service entity part) are included inside the entity.
· Modules that act as network components (network entity: NE) are included inside the entity
・ Including both SE and NE in the entity
[0023]
<Entity structure and state transition>
FIG. 3 is a diagram illustrating state transition of an entity. As shown in this figure, there are three states of an entity, “Non-Existent”, “Suspend”, and “Active”.
The “Non-Existent” state represents the entity state when the SIONet software is installed on the host.
By executing (launching) the SIONet software, transition from the “Non-Existent” state to the “Suspend” state. At this time, internal modules such as an entity control unit, a control panel, a network entity factory (NE factory), and a network entity (NE) are generated in the entity as shown in FIG. Below, each role is demonstrated easily.
[0024]
The entity control unit is an entity entity, and accepts various requests (session establishment request, shared link establishment request, etc., which will be described later) from other entities and the control panel. Note that a request for establishing a session, a request for establishing a shared link, etc. cannot be made from another entity to an entity in the “suspend” state.
[0025]
The control panel provides a GUI (Graphical User Interface) to owners of entities such as people. For example, the control panel prompts the owner of the entity to input the entity name, and the entity control unit assigns the entity name to the entity based on the input entity name. In the example of FIG. 4, the entity name is “entity 2”. This entity name may be referred to as a “local entity name”, particularly distinguished from a “global entity name” described later. The local entity name can be arbitrarily set by the owner of the entity.
[0026]
The NE (network entity) factory has a function of dynamically generating an NE.
NE (Network Entity) means SI-R (Semantic Information Router), SI-GW (Semantic Information Gateway), alive entity, fault handling entity, statistics collection entity, etc. It is a general term for modules that behave in order to achieve this.
[0027]
The SE (service entity) is an application embedded as an SE in an entity using a plug-in mechanism provided by the entity, and is a virtualized P2P application operating on SIONet. An application can be embedded in an entity as an SE using a plug-in 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 a session. SE is not involved in SIONet network construction and operation. A plug-in mechanism for incorporating SE into an entity will be described later.
[0028]
The entity (entity 2) in the “suspend” state in FIG. 3 generates an event place by itself as shown in FIG. 5, for example, or joins (joins) an existing event place as shown in FIG. When the entity (entity 2) belongs to an arbitrary event place and becomes a member of an entity group, the entity (entity 2) transitions from the “suspend” state to the “active” state. Only an entity in the “active” state advertises its existence (public, details will be described later), and can accept a session establishment request or a shared link establishment request from another entity.
[0029]
Here, after the software is installed in the host and the entity including the NE, the NE factory, the entity control unit, the control panel, and the like is generated, the operation until the entity enters the “active” state will be described. Assume that an entity receives an instruction to create an event place or participate in another event place via the control panel from the owner of the entity. The entity control unit of the entity requests the NE factory of the entity to generate SI-SW (Semantic Information Switch). When the NE factory generates SI-SW, the entity control unit establishes a session between the generated SI-SW and an internal module such as NE. This makes it possible to accept advertisements, session establishment requests from other entities, shared link establishment requests, and the like.
[0030]
Here, the role of SI-SW and session will be described with reference to FIG.
A session is a connection between SI-SW and SE, and SE can send and receive events only through the session. There are three types of sessions: event transmission sessions, reception sessions, and transmission / reception sessions.
SI-SW provides a switching mechanism that switches events based on semantic information. The SI-SW accommodates NEs and internal entities such as SEs and NEs incorporated in the entities by a plug-in mechanism through a session in a star shape. In the following, SE will be described as an example, but the same applies to other internal entities included in an entity such as NE.
[0031]
Here, the configuration of the event will be described. As shown in an example in FIG. 8, the event includes a control information part, a semantic information part, and a data part. Transmission data is stored in the data portion. Various data and programs such as text data, binary data, reference, proxy, and agent can be stored as transmission data.
[0032]
The semantic information portion stores semantic information (vocabulary and its value) of transmission data and a vocabulary concept (event type) of semantic information. Here, the semantic information is metadata describing the characteristics of transmission data and is an instance of an event type. The event type is a semantic information template. You can define inheritance relationships between event types. FIG. 9 shows an example of the semantic information system. In this figure, the meaning information “title; yesterday”, “price; $ 30”, “artist name; beatles” belongs to the event type “popular” and also belongs to the event type “music”. Yes. In addition, the meaning information “Title; Kiyoshi no Koto”, “Price; $ 20”, “Situation; Christmas” belongs to the event type “BGM”, and also belongs to the event type “Music”. .
[0033]
As a description language of the semantic information system, there is XML (Extensible Markup Language). Note that some event type names (all names starting with SIONet) are reserved for network entities.
The event control information part shown in FIG. 8 is a control field used for SIONet execution control, and only this is not open to the SE who is the user of SIONet. The control information section includes matched filter identifiers, matched filter verification scores, synchronous statistical information collection flags, TTL (Time To Live) values within event places, between event places, within event places, and between event places. Control information such as the number of hops and hop attributes is set.
[0034]
In the entity configuration as shown in FIG. 7, the function of the SE will be described. The SE registers event acquisition conditions in the SI-SW via the reception session. This is called a “filter”. In the filter, set the vocabulary concept (event type) of the event you want to acquire, and the matching condition with the semantic information (for example, the vocabulary “Price” is in the range of “$ 20 to $ 40”) . Note that collation conditions such as “complete match” with all vocabularies defined in the event type, “partial match” with some vocabularies, and “weighted match” can be selected in units of filters.
[0035]
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, for one event, one receiving session is fired at most once. If a wildcard is specified for the event type of the event to be acquired, all event types are targeted for acquisition. Further, when 1 (logical value is true) is set as the matching condition with the semantic information, it means that the matching condition with the semantic information is satisfied unconditionally.
[0036]
In addition, the SE transmits an event to the SI-SW via a transmission session. 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 the event type is desired to be received. If the event type is satisfied, the semantic information and the matching condition are checked. As a result of the collation, when the semantic information satisfies the collation condition, the entity that registered the matched filter is activated and the event is notified.
In SIONet, event transmission is referred to as “stimulation”, that the filter matches the event as “reaction”, and that the entity that registered the matched filter is activated to notify the event is referred to as “ignition”.
[0037]
<Entity name assignment method>
As shown in FIG. 5, the case where the entity 2 generates an event place named “event place A” will be described. The owner of the entity 2 inputs an event place name to the entity 2 through a control panel or the like. Here, the input event place name is “event place A”. Then, the entity control unit requests the NE factory to generate SI-SW, and establishes a session between the generated SI-SW and an internal module such as NE. Further, the entity control unit stores the name of the generated SI-SW as “event place name + local entity name”, that is, “event place A + entity 2”. This name is called “global entity name”. Creation of this global entity name corresponds to generation of an event place.
[0038]
That is, in SIONet, some management entity is not necessarily generated by generating an event place. That is, in SIONet, member management of entities belonging to an event place is realized by a shared link between entities described later, and therefore there is no centralized management unit itself that performs member management. For this reason, even if the entity that generated the event place leaves the event place, the entity remaining in the event place autonomously self-organizes, whereby the operation of the event place is continued. In other words, the removal of the last entity from the event place corresponds to the disappearance of the event place.
[0039]
This global entity name is used when a shared link or session is established. An operation in which the entity 2 as shown in FIG. 5 further generates an event place B and establishes a shared link from the entity 1 will be described with reference to FIG.
[0040]
First, an operation in which the entity 2 already participating in the event place A generates the event place B will be described. The entity control unit of entity 2 causes the NE factory to generate a new SI-SW, as described above. The entity control unit assigns “event place B + entity 2” as the global entity name to the generated new SI-SW. Thereby, the event place B is generated. At this time, the entity 2 has two global entity names (SI-SW names) “event place A + entity 2” and “event place B + entity 2”.
[0041]
Next, an operation in which the entity 1 joins (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. An entity in the “active” state can advertise (publish) its existence to other entities, in which case the global entity name is published.
[0042]
When entity 1 discovers entity 2 and makes a join request to entity 2, entity 1 indicates that the global entity name of entity 2 that is the join destination entity is “event place A + entity 2”. Entity 2 is notified.
[0043]
In this way, the global entity name can uniquely identify the SI-SW that establishes the shared link, and thus can participate in the event place A. In this way, the SI-SW, which is the shared link or session establishment destination, is virtualized as a global entity name, so that the entity owner or the like is not directly aware of the SI-SW.
[0044]
<SE plug-in method>
The operation of incorporating SE into the entity shown in FIG. 11 will be described below.
(1) The entity owner instructs an application plug-in to the control panel. 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 that the plug-in instruction has been received and the execution file name of the plug-in application.
[0045]
(3) The entity control unit stores an execution file name to be plugged in, starts an application using the given execution file name, and establishes a session between the SI-SW and the started application.
That is, the plug-in in SIONet is nothing but to establish a session between the application and SI-SW. In SIONet, all operation entities such as SE and NE cooperate through a session. Therefore, plug-in / plug-out (detachment) can be easily realized, and the plug-in / plug-out does not affect other operation entities (super loose coupling). By extending this concept, SE sharing between entities as described later can be realized.
[0046]
<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 society (a listening-oriented cyber society) in which semantic information is registered in a filter and distribution conditions (matching conditions) are set in an event semantic information section. Provides total solutions for less-less distribution model, broker-less search model, and broker-less policy model. Specifically, it consists of a stream interface, SIONet, COMNet, and the like.
SIONet is an event transmission layer and provides a network interface to higher layers. The middleware layer is a community (community network: COMNet), and corresponds to the intelligence layer of SIONet. In this layer, information localization, authentication, security, information right guarantee, policy control, and the like are performed. The highest layer is the application layer. SE is implemented in this application layer. Examples of the SE include a personal TV station and a smart messenger for a message exchange service.
[0047]
In this way, SIONet provides a common P2P network infrastructure and a plug-in mechanism for all P2P services (SEs provide services) such as distributed computing, information exchange, collaboration, and message delivery. To support efficient application development.
[0048]
<Role of entity in SIONet>
SIONet is a form of constructing a volunteer network by helping each other's entities to help each other, and each network is self-organizing through autonomous distributed cooperation. For example, in the configuration of FIG. 6, 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.
[0049]
In advance, the entity 1 generates an event place and participates in the event place. Here, when entity 2 makes a join request to event place for entity 1, as shown in FIG. 13, SI-SW is generated for entity 2, and SI-SW of entity 1 and entity 2 is further generated. A shared link is established between them and an entity group is formed.
In this way, after the shared link is established between the SI-SWs of the entity 1 and the entity 2 and the entity 2 participates in the event place, the entity 1 that is the creator of the event place leaves the event place. Then, the shared link between SI and SW is released, and thereafter, the event place construction / operation is continued only by entity 2. Thus, since each entity self-organizes, even if an entity leaves, disappears, etc., another entity performs the function of the entity.
[0050]
In SIONet, various forms of P2P networks can be constructed by arranging and combining entities according to the purpose. It is also possible to seamlessly link different forms of P2P networks. This is achieved by realizing:
(1) All entities are autonomously distributed and coordinated using a simple and simple mechanism called “chain reaction based on stimulation and firing”.
(2) Reducing the difference in P2P network form to the problem of entity placement and management
As described above, one of the features of SIONet is that various forms of P2P networks can be constructed with a single mechanism.
[0051]
<Shared link>
The “shared link” is a concept for performing bidirectional event sharing between a plurality of different entities. For example, as shown in FIG. 14, when entity 2 makes a request for establishment of a shared link (SL) to entity 1, as shown in FIG. 15, SI-SW2 and SI-SW1 A shared link is established between them and a new entity group is formed. That is, the shared link is a mechanism for forming an entity group, and is also a multi-hop route.
[0052]
In FIG. 14, the entity 2 that has successfully established the shared link includes the event place name (global entity name) from the entity 1, the event transfer method (routing method) in the event place, and the description (description) of the event place. Various information such as SE information that is plugged in is transmitted. Various event routing methods can be dynamically set between SI-SWs by setting filter values using SI-R, which will be 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.
[0053]
<Establishment of shared link>
A mechanism up to establishment of a shared link will be described with reference to FIGS. 14 and 15. First, in FIG. 14, consider a case where entity 2 issues a shared link establishment request to entity 1.
(1) The entity 2 issues a shared link establishment request to the entity 1.
[0054]
(2) As shown in FIG. 15, the entity control unit of entity 1 is SL _1,2 SI-R that performs event routing (event transfer) between SI and SW based on semantic information to NE factory to establish (shared link for receiving event from entity 2) _1,2 Are dynamically generated inside the entity 1. Further, 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.
[0055]
(3) SI-R _1,2 Establishes an event reception session for SI-SW 2 by making a request for establishment of an event reception session to entity 2. At this time, a filter indicating a condition of an event received by the entity 1 is registered in the SI-SW 2. In addition, SI-R _1,2 Establishes a session for event transmission to the SI-SW 1 to which it belongs. Such a combination of transmission and reception sessions established by SI-R is called a shared link. SL _1,2 For example, the event sent by SE4 to SI-SW2 is SI-R _1,2 Is also sent to SI-SW1.
[0056]
(4) At this time, SI-R _1,2 The event transfer method can be dynamically controlled according to the setting value of the filter registered in SI-SW2. An example is shown below.
(A) The event sent to SI-SW2 is unconditionally transferred to SI-SW1. That is, for all events, SI-R _1,2 Fires. This is made possible by setting “wildcard for the acquired vocabulary concept and true for the matching condition with semantic information (vocabulary)” as a filter that SI-R registers in SI-SW. This is called “unconditional routing”. This setting only needs to be performed once when the shared link is established. In this method, there is a possibility that unnecessary event transfer and event collation processing overhead at the transfer destination may occur. However, since there is no overhead for event path establishment (routing information setting) described later, the number of registered filters is small. This method is effective when it is sufficiently larger than the number of event transmissions. This routing method is mainly used for multi-hop broadcast communication.
[0057]
(B) Transfer only events necessary for entity 1 from SI-SW 2 to SI-SW 1. Thereby, unnecessary event transfer is not performed. That is, SI-R only for specific events _1,2 Fires. This is because SI-R sets only the vocabulary concept (matching condition is always true) in the filter as “event routing by vocabulary concept”, and sets the matching condition between the vocabulary concept and vocabulary as “filter”. It is divided roughly into. The former is mainly used for multicast communication with a multi-hop type attribute, and the latter is mainly used for multi-hop type unicast communication and multi-hop type multicast communication. This is used in failure processing notifications, statistical information notifications, alive notifications, reply notifications, advertisement notifications, and the like.
In addition to multi-hop communication such as multi-hop broadcast communication, multi-hop attribute multicast communication, multi-hop unicast communication, and multi-hop multicast communication, the communication destination can be set according to the filter value set by SI-R. Direct communication using entity entry points is also possible. Multi-hop broadcast communication, multi-hop attributed multicast communication, multi-hop unicast communication, and multi-hop multicast communication will be described later.
[0058]
(4) The procedures (2) to (3) described above are performed in the same way in the entity 2 that is the shared link establishment request source. That is, the entity control unit of entity 2 stores entity 1 (SI-SW1) as a shared link establishment request destination and SL. _2,1 SI-R to NE factory to establish _2,1 Is generated dynamically. This generated SI-R _2,1 Registers a filter in SI-SW1 in the same manner as described above, and establishes a shared link. Thereby, a bidirectional shared link is established between SI-SW1 and SI-SW2, and events can be shared among entities. Since SI-R does not register the filter, it is possible to establish a one-way shared link, that is, to prevent SI-R from being fired.
[0059]
<Establishing an event path>
Route selection information for event forwarding (event routing) (a set of filters that SI-R registers for event sharing) is called an “event path”. For example, as shown in FIG. 15, in a configuration in which entity 2 and entity 3 each establish a shared link with entity 1, consider a case where SE3 of entity 2 registers a filter for SI-SW2. At this time, SI-R of entity 2 _2,1 Registers the filter registered by SE3 to SI-SW1 of entity 1 via the reception session. Similarly, the SI-R of entity 1 _1,3 Registers the filter in the SI-SW 3 of the entity 3 via the reception session. In this way, with the filter registration by SE3 as a trigger, the SI-R registered filter sequentially spreads to adjacent SI-Rs based on the shared link, thereby establishing an event path. This is called “event path setting or spreading”.
[0060]
Here, the establishment of the event path for the above-described “event routing based on the vocabulary concept” will be described. In FIG. 15, in order to establish an event path for “event routing based on vocabulary concept”, in the filter registered by the SE3 of the entity 2 with respect to the SI-SW2, the SI-R _2,1 Sets only the event type (the matching condition is always true) as a filter to entity 1's SI-SW1. That is, the collation condition registered by SE3 as a filter is not used. In other words, by utilizing only the event type, for example, when SE1 of entity 1 sends an event, only the event type is collated in SI-SW1, and as a result, SI-R _2,1 When the fire ignites, SI-R _2,1 Sends the event to SI-SW 2 and collates with semantic information in SI-SW 2.
[0061]
In addition, establishment of an event path for the above-mentioned “event routing by vocabulary” will be described. In FIG. 15, when establishing an event path for “event routing by vocabulary”, the SI-R of entity 2 _2,1 Sets the filter value registered by SE3 as it is as the filter value to SI-SW1 of entity 1. That is, SI-R _2,1 Is a form in which both the event type and semantic information registered by SE3 as a filter are registered in SI-SW1 of entity 1 and complete filtering is performed in SI-SW1.
[0062]
Therefore, the event routing method based on vocabulary does not cause any unnecessary event transfer, but the event path setting overhead for routing becomes enormous, so this method is effective when the number of event transmissions is sufficiently larger than the number of registered filters. It is. On the other hand, the routing method based on the event type is positioned as a compromise between the two methods described above. In other words, it is effective when the number of filter registrations and the number of event transmissions are about the same, or when the ratio between the number of filter registrations and the number of event transmissions cannot be predicted. With these mechanisms, multi-hop communication of events based on semantic information is realized. An event routing method can be specified when generating an event place or registering a filter from an SE.
[0063]
The event path setting request is propagated to all SI-Rs in the event place, but the propagation range can be limited by the TTL value. The operation will be briefly described with reference to FIG. Here, for convenience of explanation, it is assumed that an event path is established for vocabulary concept routing, but the present invention is not limited to this. Further, each entity advertises (filter registration) the same vocabulary concept. The description will be made assuming that the TTL value is 2.
[0064]
In FIG. 16A, the SI-R of the entity 2 starts an event path setting request. Here, since the TTL value is 2, the event path setting request is propagated only to entity 1, entity 3, and entity 4, and as a result, the event path is established as shown in FIG. The
[0065]
Similarly to the above, when the SI-R of the entity 11 starts an event path setting request, an event path is established for the entity 10 and the entity 9. In the configuration shown in FIG. 16, when the SI-R of entity 2 and the SI-R of entity 11 make an event path setting request, the event path is not set in entity 5. Is not shared. That is, the event that has occurred from the entity 2 does not cause a chain reaction with the entities 5 to 11, and the event is not transferred to the entities 5 to 11.
[0066]
However, as shown in FIG. 16B, when the SI-R of the entity 5 initiates an event path setting request, the event path for the entity 4, the entity 5, the entity 6, the entity 7, and the entity 9 is determined. Is established. As a result, as shown in FIG. 16C, an event path is established for all entities in the event place except the entity 8.
[0067]
Thus, if the vocabulary concept is frequently used (reputed or popular) in the event place, the event path will eventually be established in the event place. Become. On the other hand, vocabulary concepts that are not so popular will eventually be deceived, which allows a mild chain reaction to be realized. Note that the numbers on the event path in FIG. 16 indicate the multiplicity.
[0068]
An entity can publish the multiplicity of event paths as an attribute of an entity property. On the other hand, an entity having a high multiplicity of event paths can be found by entity property discovery. At this time, by re-sharing the shared link with respect to the entity, it is possible to gradually gather like-minds (like entities) in the vicinity (localization of like-entities). Details of the entity property will be described later.
[0069]
From the viewpoint of distributed object technology, the event path can also be interpreted as follows. Entities that are super-distributed around the world have some “correlation” between them. There are various properties such as an entity name, a group name, and attributes (location, interest, reputation, fashion, service) that give a correlation. Based on the correlation, the entities have a connection between the entities and perform distributed cooperation. This entity that gives an entity correlation is called an entity property.
[0070]
In SIONet, this correlation is expressed by the vocabulary concept and vocabulary and set as an event path based on the shared link. The strength of the correlation corresponds to generalization / specialization of vocabulary concepts, multiplicity of event paths, and the like. That is, in SIONet, the correlation between entities is dynamically controlled and managed by an event path. This is the control of the chain reaction by the filter. Therefore, the entity does not have a fixed entity identifier.
[0071]
For example, an IP address is a fixed identifier of an entity based on a position. In SIONet, instead of this, an entity property described as a vocabulary concept / vocabulary is used as an entity identifier. Entities register these as filters in SI-SW, thereby declaring entity properties (entity identifiers) and advertising their properties based on shared links. This corresponds to the propagation of the event path. Thereby, an event path is established.
[0072]
As described above, SI-R is a network entity having both aspects of event transmission and event reception, and is not fundamentally different from a general service entity. In SIONet, an entity used for SIONet control such as SI-R is called a network entity (NE), particularly distinguished from a service entity (SE). In SIONet, all service entities and network entities are treated as a common entity, and autonomously operated according to a simple and consistent common logic of event transmission and event reception, that is, chain reaction of stimulus and firing. , Provide a super-distributed and super-loosely coupled architecture in which all entities can cooperate autonomously and distributedly.
[0073]
<Release and re-establish shared link>
In cases where an entity participating in the event place falls into a failure or leaves the event place, the remaining entity is not able to participate in the operation of the network for various reasons. By doing so, it is necessary to be able to continue the network service.
In such a case, SIONet releases the shared link established between SI and SW, and re-establishes the shared link. The operation will be described with reference to FIG.
[0074]
In FIG. 17, the first numbers (1) and (2) in the shared link establishment request indicate the order of those requests. That is, in order of the shared link establishment request, first, the shared link establishment request is made from the entity 2 to the entity 1. Next, a request for establishment of a shared link is made from entity 3 to entity 2. Finally, a shared link establishment request is made from entity 4 to entity 2. Here, “Each entity can make a shared link establishment request at most once in the same event place, but establishes a shared link based on a link topology that can accept an unlimited number of establishment requests. Propose a link establishment method. This guarantees that no loop will occur between entities linked by a shared link. That is, by using this method, an open link topology can be easily realized only by link re-establishment between adjacent entities.
[0075]
If the establishment request is successful in the above-described order, a shared link is established between each SI-SW by the above-described procedure. When the shared link is established, the entity control unit of each entity stores the entity that has made the 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 and the entities 3 and 4 that have accepted the establishment of the entity 2.
In this situation, for example, when the entity 2 is moved out or removed, a shared link release request is issued to its own SI-SW 2 to release the shared link. Thereafter, each entity establishes a new shared link. Hereinafter, the operation will be described.
[0076]
(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) that the shared link is released. This can be done by sending an event with the TTL value of the event set to 1. At this time, for the entity (entity 3 and entity 4) that has accepted the establishment of the shared link to itself, the entity 1 that has made the establishment request is used as the establishment request destination of the new shared link on behalf of itself. teach. If there is no entity that has made an establishment request, an arbitrary entity is selected from the establishment requesting entities (one hop ahead) to itself, and this is used for the shared link on behalf of itself. The establishment request destination.
[0077]
(2) The entity control unit of entity 2 uses the shared link (SL _2,1 , SL _2,3 , SL _2,4 ) _2,1 , SI-R _2,3 , SI-R _2,4 (Not shown). SI-R _2,1 , SI-R _2,3 , SI-R _2,4 Is the SI-R of entity 2, and as described above, shared link SL for entity 1, entity 3, and entity 4 _2,1 , SL _2,3 , SL _2,4 Is established. These SI-Rs use this as a trigger to release the session of entity 2 to SI-SW2.
[0078]
(3) The entity control unit of entity 1 is SI-R _1,2 (Not shown) Shared Link SL _1,2 Instruct to cancel. SI-R _1,2 Shared link SL _1,2 Is released. The entity 1 waits for establishment requests from the entities 3 and 4.
(4) Similar to entity 1, entity 3 and entity 4 share a shared link (SL) established for SI-SW 2 (SI-SW 2 of entity 2). _3,2 , SL _4,2 ) Are all released, a shared link establishment request is made to the new entity (entity 1) instructed as the shared link establishment request destination from the entity 2, and the shared link is reestablished. That is, as described above, each entity control unit sends an SI factory to the NE factory. _3,1 , SI-R _4,1 To generate the SI-R _3,1 , SI-R _4,1 Shared link SL _3,1 , SL _4,1 Establish.
[0079]
As described above, the shared link establishment process and re-establishment process are performed only between adjacent entities and do not affect other entities. That is, there is no need to reconstruct links for all entities.
[0080]
The shared link is not only requested to release the shared link by following proper procedures such as moving out or deinstalling the entity, but also due to an entity failure, power failure, session (physical communication path) failure, etc. There are cases where you must re-establish. However, in such cases, it may not be possible to teach alternative entities that are needed when reestablishing a shared link. In SIONet, in order to cope with such a situation, each entity transmits an event of n hops (n is an arbitrary natural number) to grasp an alternative establishment request destination entity. In SIONet, finer hop control is possible by using TTL values and hop attributes. Examples of hop attributes include:
[0081]
(1) Only the entity requesting shared link establishment is targeted for hopping.
(2) Only the entity requesting the establishment of a shared link is a hop target.
(3) All entities are targeted for hopping.
[0082]
An example of an event flow when the hop attribute of (1) is designated is indicated by a 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 made a shared link establishment request, while j indicates the entity that 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 accepts the establishment requests from the entities 5 and 6. Each entity holds shared link establishment information, so that, for example, when the entity 3 makes a further 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, entity 6 has 3 hops and sends an event having the above-mentioned hop attribute (1), so that it becomes possible to know the existence of entity 1 and entity 2, which are alternatives when entity 3 fails. Become an entity.
[0083]
The hop attribute described above 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 establishment of a shared link, and for searching for a top entity (nobody establishes a shared link). It is valid. In SIONet, only the top entity can establish a federation (corresponding to a shared link between event places) for other event places.
[0084]
<Purpose of online increase / decrease>
The purpose of the entity increase / decrease in SIONet is mainly divided 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 event filtering process is load-balanced. From the opposite point of view, the entity is reduced. This is mainly used in the operation of hybrid P2P and backbone P2P networks.
(2) A flexible and global P2P network is built from the bottom up by flexibly establishing a shared link for dynamically generated entities. This is mainly used in the operation of a pure P2P network.
[0085]
Note that a hybrid P2P network is a network that is configured by, for example, an operator such as a network provider generating an event place in advance on a host or the like, and a service entity such as a personal terminal connecting to the event place through a session. . The pure P2P network is a network configured by connecting entities that are individual transmission / reception terminals via shared links, and among these networks, the smallest unit for sharing an event is an event place. The backbone P2P network is a connection form between networks, for example, a network in a state where pure P2P networks in a plurality of regions are connected via a hybrid P2P network.
[0086]
<Type of increase / decrease>
SION provides several types of increase / decrease configurations, but here, typical configurations shown in FIGS. 19 and 20 will be described.
(1) Combining and separating event places
As shown in FIG. 19A, a plurality of event places can be synthesized. Here, composition refers to collecting 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.
[0087]
This is because a request for establishing a shared link is issued to any entity belonging to the event place or an entity in the event place where the request is made, by issuing a composition request. As a result, a shared link is established between SI and SW, and the combination of both is realized. The request source and the request destination of synthesis may be either an entity or an event place. On the other hand, in the case of division, the established shared link is released and separated into event places.
[0088]
(2) Participating in and leaving the event place
As shown in FIG. 19B, an SI-SW is generated in the request source entity by making a Join request to the entity in the event place or the event place. Then, by issuing a shared link establishment request to the request destination entity, the shared link is established between the SI and SW, and can 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 entity that has moved out transitions to the suspended state.
[0089]
By requesting the entity to establish a shared link from the event place side, the entity can be taken into the event place. This is called absorption. The opposite is called splitting.
(3) Increase / decrease of entities (SI-SW)
As shown in FIG. 20 (c), when an entity expansion request is made to an entity in an event place or an event place, an SI-SW is newly generated for the specified entity, and an existing SI-SW is generated. A shared link is established with the SW. On the other hand, when an entity reduction request is made to the event place, a shared link release request is issued to the specified entity, and after the shared link between SI and SW is released, the shared link is reestablished. , The entity is deleted. At this time, the state of the entity transitions to Non-Existent.
[0090]
(4) Federation between event places
As shown in Fig. 20 (d), a SI-GW that transfers events between event places is dynamically generated by making a federation (cooperation) request to the entities in the event place or to the event place. Both event places cooperate through the session. Note that the federation request source and request destination may be either an entity or an event place.
[0091]
<Entity advertisement>
With reference to FIGS. 21 and 22, the advertisement (publication) of an entity will be described. There are the following two aspects to entity advertisement in SIONet.
Viewpoint 1: Entrance advertisement
Viewpoint 2: Entity property advertisement
Hereinafter, each viewpoint will be described.
Viewpoint 1: Entrance advertisement
The base event place is an event place serving as a base (starting point) for searching for (discovering) an optimal event place based on an entity. In other words, the base event place is the entrance to SIONet. Therefore, entities participating in the base event place can make the SIONet entrance public. Here, opening the entrance means advertising the entry point and the global entity name of the entity that is the shared link establishment request destination. This public information is found by a search using a broadcast described later.
[0092]
Viewpoint 2: Entity property advertisement
In any entity group connected by a shared link (all event places including the base event place), each entity can advertise its entity properties. This corresponds to the propagation of the event path described above. This public information is discovered by sending out a discovery event described later.
[0093]
The flow from entity disclosure and search to entity group formation will be described below. In the following, base entity, entity 1, entity 2, entity 3, entity 4, entity 5, and entity 6 belong to the base event place, and entity 3, entity 11, entity 12, and entity 13 belong to event place α. It will be described as belonging.
[0094]
(1) Install SIONet software on the host as shown in FIG. The state of the entity at this point is “Non-Existent” as described above. For convenience of explanation, this entity is assumed to be entity Y.
(2) By executing the SIONet software, the entity Y transitions from the “Non-Existent” state to the “Suspend” state. An entity in this state has not yet been recognized by SIONet.
[0095]
{Circle around (3)} The entity Y in the “suspend” state searches for the entrance (entry point and global entity name) of other entities belonging to the base event place in order to participate in the network as a component of SIONet. Specifically, a nearby entity is searched from among entities participating in the base event place by broadcasting. The broadcast method depends on the implementation. For example, when implemented in a wireless network, all entities within the wireless reach are targeted for search. On the other hand, when implemented in an IP network, IP broadcast or IP multicast is performed. FIG. 21 shows that the entity 1 (entry point of the entity 1 and the global entity name) is found by the search by broadcast. If a nearby entity cannot be found by broadcasting, a well-known entity can be used. Well-known entities are called base entities. Note that the base entity can exist in all event places including the base event place.
[0096]
{Circle around (4)} The entity Y makes a join request to the base event place for the discovered entity 1. That is, the entity Y makes a Join request to the entry point of the entity 1 using the global entity name of the entity 1 as a parameter. The entity 1 that has received the join request from the entity Y accepts the join request only when the state transition of the entity 1 is “active” and the entrance and the entity property are in the public mode. The entity Y cannot issue a Join request exceeding 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 receives the join request of the entity Y, a shared link is established between the entity Y and the SI-SW of the entity 1 by the same operation as described above. Thereby, the entity Y is self-organized as a network component in the base event place. At this time, the entity Y transitions from the “suspend” state to the “active” state.
[0097]
Entity Y joined to the base event place can open the entrance. You can also advertise entity properties. Entity properties include global entity name (and entry point), nickname, group name, alive (only assertion exists, entry point and global entity name as shared link establishment information are not disclosed, entity is not disclosed (Even if it is a mode, there are disclosure targets), descriptions (descriptions of entities), attributes, etc. The attributes include plug-in SE information, event path multiplicity, event place information, and the like. The entity property description language includes XML.
[0098]
In FIG. 21, for example, the entity control unit of the entity 3 can publish the event place α in which the entity 3 participates simultaneously as an attribute of the entity property. Furthermore, the entity control unit can disclose not only the event place that is currently joined but also the event place information of the event place that has been joined in the past. This event place information is, for example, a description of the event place (description of the event place, explanation information), or the global entity name of the entity (semantic information switch) that established the shared link when participating in the event place ( Event place name + entity name, connection establishment information), entry point (entry point information), and the like. The number of entities that can hold the event place information joined in the past is arbitrary. For example, the entity owner or the like can be set by the control panel. The entity that has obtained the public event place information presents the event place information to the entity owner by outputting the event place information through a control panel or the like. Thereby, the entity owner can recognize the existence of another event place.
In SIONet, there is no function to centrally manage event place information such as where and what event place and what service is provided in that event place, so if you want to get event place information, Event place information needs to be obtained from entity properties of other entities. By making public the event place information that participated in the past as well as the event place that you are currently participating in, the chances of acquiring the event place information will increase, and the chances of participating in the event place that provides the service you want will increase. .
[0099]
When the entrance of the entity Y is released, these entity properties are registered as filters in the semantic information switch in the entity, whereby the entity properties are propagated to other entities based on the shared link, and an event path is established. Basically, the event path establishment request is propagated to all the entities in the event place, but the propagation range of the event path establishment request can be limited by the TTL value. The global entity name is used as an identifier during multi-hop type unicast communication, the group name is used as an identifier during multi-hop type multicast communication, and the attribute is used as an identifier during multicast communication with a multi-hop type attribute. For example, as a typical example of multi-hop unicast communication, there is a reply notification from an event reception entity to an event transmission source entity.
[0100]
In other words, the global entity name is multi-hop unicast communication, which is a communication method for transmitting an n-hop event from the SI-SW of the entity specified by the global entity name. Multi-hop multicast communication is a communication method for transmitting n-hop events to SI-SWs of entities belonging to a group specified by a group name. Multi-hop attributed multicast communication is a communication method for transmitting an n-hop event to an SI-SW of an entity having the same attribute as that of itself. Multi-hop broadcast communication is a communication method for transmitting an n-hop event to SI-SW of an arbitrary entity.
[0101]
(5) In FIG. 22, the entity Y who participated in the base event place releases “entity properties that meet his / her needs” by sending out a discovery event to search for the “event place where he / she wants to participate”. Search for the entity This discovery event is an event used for control of SIONet, and is equivalent to an event transmitted by SE. A discovery event is an event for igniting an NE, and a matching condition with an entity property is set in the semantic information portion of the event. In other words, adding a new function in SIONet means defining a new vocabulary concept and vocabulary (not adding a mechanism, but adding a chain reaction condition). As a result, various functions can be added only by a single mechanism (chain reaction).
[0102]
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 α simultaneously with the base event place. By discovering the entity 3, the entity Y can know the existence of the event place α.
(6) The entity Y issues a Join request to the event place α to the entity 3 and participates in the event place α. As described above, the entity 3 accepts a Join request (shared link establishment request) when its state transition is “active” and in the public mode.
[0103]
(7) Furthermore, the entity Y can send an event for the same search at the event place α. Thereby, it is possible to find a new entity that meets its own needs. For example, it is assumed here that the entity 12 has been discovered. That is, entity Y means that entity 12 that could not be found in the base event place can be found via entity 3. By repeating such an operation, it is possible to gradually reach an event place that meets its needs.
[0104]
The advertisement method shown here has the following effects.
(1) Since there is no broker (management unit) that manages public information of entities, it is possible to construct a self-organizing network that is strong in fault tolerance at low cost. In addition, it is not realistic to manage a huge number of public information (entry points and entity properties) with a broker.
(2) Since the event place suitable for the entity can be narrowed down to the formula to be determined, a desired event place can be efficiently searched. For example, even if the spillover range of the chain reaction (the hop number of the discovery event and the spillover range of the event path setting request for the entity property) is limited by the TTL value, as described above, the entity 12 via the entity 3 As a result, another event place to which the entity 12 belongs can be found. It should be noted that network traffic (event transfer count, event path setup request transfer count) can be reduced by limiting the spread range of the chain reaction.
[0105]
Note that entities that simply receive information from other entities without providing information (for example, without disclosing entity properties) will be forced to release the shared link as a penalty, As long as you are not satisfied, you can prevent them from participating in the event place again.
[0106]
<SE sharing method (automatic distribution)>
In the following, the mechanism of the SE sharing method will be described by taking SE (game application program) sharing in the game event place as an example.
(1) The owner of the entity 2 who is an operator of the game event place gives an event place name via the control panel of the entity 2. It is assumed that the event place name assigned here is “game”.
[0107]
(2) The entity control unit of entity 2 gives the global entity name “game + entity 2” to the SI-SW generated by the NE factory, as described above. Thereby, an event place is generated. At this time, the entity 2 that is the creator of the game event place automatically participates in the event place when the event place is generated.
(3) The owner of the entity 2 instructs the control panel of the entity 2 to plug in the game application program (SE). At this time, the executable file name of the application to be plugged in and the presence or absence of SE sharing are given as parameters.
[0108]
(4) The control panel of entity 2 notifies the entity control unit of this fact.
(5) The entity control unit of entity 2 stores the name of the executable file to be plugged in, and starts the application (SE) using the given executable file name, and between SI-SW and the application as described above Establish a session on That is, the plug-in in SIONet means establishing a session between the application and SI-SW.
[0109]
(6) The entity control unit of entity 2 advertises (publishes) the entity property of entity 2. Examples of the entity property public form of entity 2 include the following.
Entity 2 participates in the base event place and publishes the entity properties of entity 2 in the base event place.
Entity 2 discovers and participates in an event place that is closely related to the game event place by performing an expression search, and publishes the entity property of entity 2 in the event place.
-Entity 2 is a base entity. That is, the entity properties (entry point and global entity name) of entity 2 are made known.
[0110]
(7) The entity 1 that 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 requests entity 2 to establish a shared link. Then, a shared link is established between entity 1 and entity 2 as described above.
(9) When the shared link is established, the shared link establishment request destination (entity 2) returns information necessary for transmission / reception of the event in the event place to the establishment request source (entity 1). Specifically, for example, an event place name (global entity name), whether or not the event place that participated is a base event place, an event transfer method (routing method) in the event place, a description of the event place, a plug-in SE information (when there is SE sharing) and the like.
[0111]
Specifically, the SE information returned to the shared link establishment request source when sharing the SE share is, for example, an execution file name of the application to be plugged in or a file of the application.
(10) The entity control unit of the entity 1 that has received the file activates the application using the given executable file name as described above, and establishes a session between the SI-SW in the entity 1 and the application. Establish. As a result, the game application program is plugged into the entity 1 as SE.
[0112]
In other words, participation in an event place means that an entity group connected by a shared link is formed, and a participant shares a plug-in-completed application program. As a result, an entity that is a member in the event place can automatically use the plugged-in application simply by participating in the event place. Note that 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 continue to hold the received file, or the file may be deleted at the time of plug-out.
[0113]
The operation described above is application sharing in a pure P2P network environment. Therefore, the distribution of the application program is performed only between the two parties, that is, the shared link establishment destination entity and the establishment source entity, and thus does not affect other entities that are already coupled by the shared link. That is, since the processing is localized between the two parties for file transfer, scalable SE sharing can be achieved.
[0114]
<Business model>
Here, an embodiment in which the above-described SIONet is provided as a service will be described.
(1) Client server model
This is a form in which an event place is operated only by a predetermined entity. That is, only a predetermined entity can participate (Join) in the event place, and an entity permitted to participate constitutes an entity group by establishing a shared link between the entities. On the other hand, the other entities establish a session with the entity group, and send and receive events via the session. That is, an event place (a predetermined group of entities) is a server, and other entities correspond to clients. In this business model, each entity that is a member of an entity group behaves as an autonomous distributed computer, and when any entity falls into a failure, the remaining entities are self-organized and continue to operate the event place. In order to improve the processing capacity of the server, a new entity may be added to the event place. Therefore, it is possible to realize a scalable server that is strong in fault tolerance, inexpensive, and scalable as compared with the conventional server realization method.
[0115]
(2) Hybrid model
For example, an entity that is an operator of a game event place generates a game event place and becomes a base entity in the event place. On the other hand, an entity positioned as a user of a 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 the event place. In order to provide the user's own entity for service operation, the event place operator does not need new capital investment. Therefore, an inexpensive and scalable P2P service environment can be constructed. Note that the base entity can authenticate and charge a user (entity) participating in the event place. In addition, the base entity sends out a discovery event to discover an entity that can establish a shared link (alternate entity) from the entity group, and notifies the entity that wants to participate to the discovered entity. It is also possible to establish a shared link between the two.
[0116]
(3) Pure model
This is a business model in which all entities can freely participate (leave) in the event place.
As mentioned above, SIONet can realize various business models with a common mechanism by reducing to operation / placement problem. Therefore, it has a great effect on development man-hours, scale, debugging efficiency, ease of maintenance and the like.
[0117]
As described above, an entity in the “suspended” state cannot disclose an entrance or an entity property. An entity in the “suspend” state transitions to an “active” state by joining an arbitrary event place. Only entities in the “active” state can expose entrances and entity properties. Also, only the entities that are joined to the base event place can open the entrance. An entity can actually publish an entrance or an entity property when satisfying “publication is instructed by the control panel” and “the number of established sessions (shared link) for the entity does not exceed the default value”. For example, even if the owner of an entity instructs the disclosure using the control panel, if the shared link is established beyond the default value, the private mode is automatically set. The default value can be set on the control panel. For example, the entity owner can set the default value based on the ability of the entity.
[0118]
The network entity, network entity factory, entity control unit, control panel, service entity, semantic information switch, semantic information router, semantic information gateway may be realized by dedicated hardware, It may be configured by a CPU (Central Processing Unit), and the function may be realized by loading a program for realizing the function into a memory and executing it.
[0119]
In addition, a program for realizing the functions of a network entity, a network entity factory, an entity control unit, a control panel, a service entity, a semantic information switch, a semantic information router, and a semantic information gateway is recorded on a computer-readable recording medium, You may implement | achieve by making a computer system read the program recorded on this recording medium, and executing it. Here, the “computer system” includes an OS and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
[0120]
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case is also used to hold a program for a certain period of time. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.
[0121]
[Embodiment of the Invention]
Hereinafter, an embodiment of the present invention will be described.
In SIONet, when a service entity (SE) is plugged in to an entity, sharing (sharing) is selected using the control panel, etc., so that other entities in the same event place as this entity can change the plugged-in service entity. It can be used automatically. This is referred to as “service entity sharing (SE sharing)”. SE sharing is a concept born from the idea of reducing the P2P application distribution problem to the event place participation problem.
[0122]
Conventionally, for example, as shown in FIG. 28, it has been common to download and install application software on a computer terminal (host) to use a service (application).
On the other hand, in SIONet, one of the main purposes of becoming a member of an event place that is an entity group is to use a service distributed in the event place. Against this background, as an idea to solve these distribution problems, the concept of SE sharing that resulted in distribution problems as participation problems was born.
[0123]
FIG. 1 is a diagram for explaining the concept of this SE sharing. In the figure, an application program such as game software is abstracted as SE and plugged into an entity such as a general-purpose game machine body. When this entity receives a shared link establishment request for participating in the event place from another entity and establishes a shared link between both entities, the SE is copied to the shared link establishment request source entity. With this copied SE, the game provided by the application program can be used in the shared link establishment request source entity.
[0124]
By performing SE sharing, the following effects are produced.
(1) Hide the application program that is the entity of the SE. For example, an entity needs to be aware of implementation-dependent information such as whether an application program is an executable file, a distributed object, or a proxy (a minor application program for using an application program implemented by another entity). There is no.
(2) Conceal information such as which entity the application program that is the entity of the SE is located. In other words, copying SE means copying a virtualized concept and does not mean copying the application program itself that is the entity. The SE plug-in indicates that the entity can see and use the application providing the service.
[0125]
Next, an SE sharing mechanism will be described with reference to FIG. In FIG. 25 (a), after the entity X generates an event place, a plug-in mechanism is used to establish a session between this SE and SI-SW by incorporating P2P software into the entity X as an SE. is doing. Here, it is assumed that SE sharing is selected at the time of plug-in.
In this state, it is assumed that the entity Z requests the entity X to participate in the event place. When this participation request is approved by the entity X, as shown in FIG. 25B, a new SI-SW is dynamically generated in the entity Z, and the SI-SW inside the generated entity Z is A shared link is established with the SI-SW inside the entity X. Then, the SE is transferred from the entity X to the entity Z which is a shared link establishment request source entity, and a session is established between the transferred SE and the SI-SW in the entity Z. That is, SE sharing can be viewed as an “automatic plug-in” for entity Z. However, SE is a concept for abstracting P2P software as an internal entity, and transfer (copy) of SE does not involve transfer of P2P software that is the entity of SE.
Next, it is assumed that the entity Y makes a connection request to the entity X. At this time, the session is paid out from the entity X to the entity Y. Further, the SE is transferred from the entity X to the entity Y, and the transferred session is also provided to the transferred SE. As a result, a session paid out at the time of connection is established between the SE inside the entity Y and the SI-SW inside the entity X. The processing for sharing the SE is performed only between the SE providing source entity and the SE providing destination entity, and does not affect other entities.
[0126]
Next, a method for arranging SE entities when sharing an SE will be described. The SE entity indicates plug-in P2P software for providing an application (service).
As for the arrangement method of the SE entity, as in the past, the P2P software is downloaded to all the entities in the event place, and the SE entity is arranged in all the entities, or the SE entity is applied only to the entity that has performed the plug-in. There is a way to arrange.
FIG. 26 shows an SE entity arrangement method based on the number of hops. In the arrangement of SE entities based on the number of hop stages, SE entities are arranged in entities for each predetermined number of hop stages, that is, P2P software is plugged in as SE. Then, an entity that does not have an SE entity provides a service by using the SE entity of an entity within the predetermined number of hops by its own SE that is automatically plugged in. The figure shows a case where the number of hop stages is 2, and an SE entity is arranged in an entity for every two hops, and an SE of an entity not having an SE entity is implemented in two hops, that is, in an entity one hop ahead The SE entity is used.
FIG. 27 shows an arrangement method for arranging SE entities at branch points. In this method, an SE entity is arranged in an entity corresponding to a branch point on a shared link topology (hereinafter referred to as a link topology), that is, P2P software is plugged in as an SE. An entity that does not have an SE entity provides a service by using the SE entity of the entity corresponding to the branch point by its own SE that is automatically plugged in. In addition, the open link topology in SIONet can be realized by a unified mechanism based on the maximum number of accepted shared link establishment requests. An entity corresponding to a branch point is an entity whose maximum number of requests for establishing a shared link is two or more.
In addition, there are various implementation methods such as an SE entity arrangement method based on an operating environment attribute that is an entity property item, and an arrangement method based on the sharing degree of the SE entity. The entity arrangement method based on the operation environment attribute is, for example, a method of arranging an SE entity on an entity whose operation environment attribute satisfies a predetermined condition. In addition, the arrangement method based on the sharing degree of the SE entity is that the entity holding the SE entity limits the number of entities that use the SE entity to a predetermined number. This is a method of plugging in P2P software.
As described above, there are various SE entity implementation methods, but the abstraction concept of SE completely hides these implementation methods.
[0127]
The operating environment attribute that is one of the property items includes the following.
(1) Entity processing capacity (CPU power, memory capacity, communication bandwidth), etc.
(2) OS type, middleware type, etc. required for the entity to operate
(3) Execution form (implementation form) of an entity (internal entity): Implementation-dependent information such as whether it is an execution format file, distributed object, or proxy
(4) Location of internal entity entity (application program)
Then, using this operating environment attribute, the entity implements the following mechanism.
(1) P2P software is virtualized as a SIONet operation unit by a plug-in that incorporates P2P software as an internal entity (SE) inside the entity. At the same time, the SE hides the physical operation environment such as the application implementation form and the application location based on the operation environment attribute.
(2) The following SE sharing mechanism is realized.
・ Hide P2P application implementation information. For example, the operating environment, storage location, execution format, etc. of P2P applications are concealed and the applications are virtualized as SIONet computing resources. This makes it easy to attach and detach P2P applications.
-Select the SE entity to be shared based on the operating environment attributes (OS type, middleware type, etc. that are the operating environment of the shared SE).
-The SE implementation method is completely hidden by the abstraction concept of SE. That is, information such as where the application program that is the entity of the SE is arranged is concealed.
Conceal the application program that is the entity of the SE. For example, it is not necessary to be aware of implementation-dependent information such as whether an application program is an executable file, a distributed object, or a proxy.
(3) Used for SE search in which operating environment attributes are specified. That is, it is used for searching for an SE that matches the operating environment of the search source entity.
(4) Based on the operation environment attribute, the maximum acceptance value of basic operation requests such as a participation request is determined. For example, the maximum number of receptions is determined based on the processing capability of the entity. All open topologies (star type, tree type, bus type, etc.) can be constructed using the maximum value.
[0128]
The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like within a scope not departing from the gist of the present invention.
[0129]
【The invention's effect】
As described above, according to the present invention, the application program is arranged according to the topology and the operating environment of the entity, and the entity in the event place is configured to hide the application program while hiding the arrangement and implementation method of the application program. It becomes possible to share.
[Brief description of the drawings]
FIG. 1 illustrates a concept of SE sharing according to an embodiment of the present invention.
FIG. 2 is a diagram for explaining entities in SIONet (semantic information network), which is a prerequisite technology of the present invention.
FIG. 3 is a diagram for explaining entity state transition in SIONet;
FIG. 4 is a block diagram showing an internal configuration of an entity in SIONet.
FIG. 5 is a diagram for explaining generation of an event place in SIONet.
FIG. 6 is a diagram for explaining an operation in which an entity in SIONet participates in an event place.
FIG. 7 is a diagram for explaining a semantic information switch SI-SW and a session in SIONet.
FIG. 8 is a diagram showing a configuration of events in SIONet.
FIG. 9 is a diagram for explaining a semantic information system in SIONet.
FIG. 10 is a diagram for explaining an operation in which an entity participating in a certain event place further participates in another event place in SIONet.
FIG. 11 is a diagram for explaining a service entity plug-in in SIONet;
FIG. 12 is a diagram for explaining a reference model in SIONet.
FIG. 13 is a diagram for explaining a shared link in SIONet.
FIG. 14 is a diagram for explaining a shared link in SIONet.
FIG. 15 is a diagram for explaining a shared link in SIONet;
FIG. 16 is a diagram for explaining an event path in SIONet;
FIG. 17 is a diagram for explaining re-establishment of a shared link in SIONet.
FIG. 18 is a diagram for explaining a hop attribute in SIONet;
FIG. 19 is a diagram for explaining event place and entity increase / decrease in SIONet;
FIG. 20 is a diagram for explaining event place and entity increase / decrease in SIONet;
FIG. 21 is a diagram for explaining entity advertisement in SIONet;
FIG. 22 is a diagram for explaining entity advertisement in SIONet;
FIG. 23 is a diagram showing dimensions of a P2P model.
FIG. 24 is a diagram for explaining the concept of SIONet.
FIG. 25 is a diagram for explaining an SE sharing mechanism according to an embodiment of the present invention;
FIG. 26 is a diagram for explaining an SE entity arrangement method when sharing an SE according to an embodiment of the present invention;
FIG. 27 is a diagram for explaining a method for arranging an SE entity when sharing an SE according to an embodiment of the present invention;
FIG. 28 is a diagram for explaining a conventional service utilization method.

Claims (6)

An entity device constituting a semantic information network that is a P2P network,
Participation request means for making a request to participate in the event place to other entity devices constituting the event place;
Connection establishment means for establishing a shared link with the other entity device of the participation request destination when the participation request is approved by another entity device;
A service entity for identifying and using the application software that forms part of the application software plugged in to the other entity device in the event place from the other entity device to which participation is requested An automatic plug-in means to receive this transfer and plug this service entity into the inside,
Service providing means for providing a service executed by application software plugged into another entity device in the event place and usable by a service entity plugged in by the automatic plug-in means;
With
The automatic plug-in means includes
When the number of hops between the own entity device and another entity device in the event place is outside the number of hops designated by the other entity device in the event place,
When another entity device in the event place corresponds to a branch point on the shared link topology,
When other entity devices in the event place satisfy a predetermined operating environment attribute indicated by any one or more of the processing capability of the entity, the application type, the execution form of the entity, and the location of the internal entity entity, or
If the number of other entity devices using the same service entity is less than the predetermined number, the service entity entity is transferred in either case.
An entity device characterized by that. An entity device constituting an event place in a semantic information network that is a P2P network,
Participation request receiving means for receiving a request to participate in the event place from another entity device;
A connection establishment means for establishing a shared link with the other entity device when approving participation of the other entity device that has requested participation;
For identifying and using the application software that forms part of the application software plugged into the other entity device in the event place or to the other entity device that has requested participation A transfer means for transferring the service entity;
With
The transfer means includes
When the other entity device that made the participation request is outside the number of hops specified by the other entity device or the own entity device in the event place,
When the own entity device is a branch point on the shared link topology,
When the own entity device satisfies a predetermined operation environment attribute indicated by any one or more of the processing capability of the entity, the application type, the execution form of the entity, and the location of the internal entity entity, or
Transferring service entity entity if the same other entity devices by using the service entity of any case less than a predetermined number,
An entity device characterized by that. A service sharing method used for an entity device that participates in an event place in a semantic information network that is a P2P network,
In the entity device,
Participation requesting means for requesting participation to the event place to other entity devices constituting the event place;
A connection establishment process in which a connection establishment means establishes a shared link with the other entity device as a participation request destination when the participation request is approved by another entity device;
The automatic plug-in means identifies and uses the application software that forms part of the application software plugged into the other entity device in the event place from the other entity device requested to participate An automatic plug-in process for receiving a transfer of the service entity to plug in the service entity,
A service providing process in which service providing means provides a service executed by application software that is plugged into another entity device in the event place and that can be used by a service entity plugged in by the automatic plug-in means; ,
Have
In the automatic plug-in process, the automatic plug-in means is:
When the number of hops between the own entity device and another entity device in the event place is outside the number of hops designated by the other entity device in the event place,
When another entity device in the event place corresponds to a branch point on the shared link topology,
When other entity devices in the event place satisfy a predetermined operating environment attribute indicated by any one or more of the processing capability of the entity, the application type, the execution form of the entity, and the location of the internal entity entity, or
If the number of other entity devices using the same service entity is less than the predetermined number, the service entity entity is transferred in either case.
A service sharing method characterized by the above. A service sharing method used for an entity device constituting an event place in a semantic information network which is a P2P network,
In the entity device,
A participation request receiving means for receiving a participation request to the event place from another entity device;
A connection establishment process for establishing a shared link with the other entity device that made the participation request when the connection establishment means approves the participation request in the other entity device;
The transfer means specifies the application software that constitutes a part of application software plugged into the other entity device or the own entity device in the event place to the other entity device that has made the participation request, And a forwarding process for forwarding a service entity for use;
Have
In the transfer process, the transfer means
When the other entity device that made the participation request is outside the number of hops specified by the other entity device or the own entity device in the event place,
When the own entity device is a branch point on the shared link topology,
When the own entity device satisfies a predetermined operation environment attribute indicated by any one or more of the processing capability of the entity, the application type, the execution form of the entity, and the location of the internal entity entity, or
Transferring service entity entity if the same other entity devices by using the service entity or the own entity apparatus of any case less than a predetermined number,
A service sharing method characterized by the above. A computer used as an entity device for participating in an event place in a semantic information network which is a P2P network;
Making a request to participate in the event place to other entity devices constituting the event place;
Establishing a shared link with the other entity device to which participation is requested when the participation request is approved by another entity device;
A service entity for identifying and using the application software that forms part of the application software plugged in to the other entity device in the event place from the other entity device to which participation is requested Receiving the transfer and plugging this service entity inside;
Providing a service to be executed by application software corresponding to this service entity, plugged into another entity device in the event place, and usable by the service entity plugged therein;
To execute
In the step of plugging in the service entity internally,
When the number of hops between the own entity device and another entity device in the event place is outside the number of hops designated by the other entity device in the event place,
When another entity device in the event place corresponds to a branch point on the shared link topology,
When other entity devices in the event place satisfy a predetermined operating environment attribute indicated by any one or more of the processing capability of the entity, the application type, the execution form of the entity, and the location of the internal entity entity, or
If the number of other entity devices using the same service entity is less than the predetermined number, the service entity entity is transferred in either case.
A computer program characterized by the above. In a computer used as an entity device constituting an event place in a semantic information network which is a P2P network,
Receiving a request to participate in the event place from another entity device;
Establishing a shared link with the other entity device that made the join request when approving the join request;
For identifying and using the application software that forms part of the application software plugged into the other entity device in the event place or to the other entity device that has requested participation Transferring the service entity;
To execute
In the step of transferring the service entity,
When the entity device that made the participation request is outside the number of hops designated by another entity device in the event place or the own entity device,
When the own entity device is a branch point on the shared link topology,
When the own entity device satisfies a predetermined operation environment attribute indicated by any one or more of the processing capability of the entity, the application type, the execution form of the entity, and the location of the internal entity entity, or
The service entity entity is transferred in any of the cases where there are fewer than a predetermined number of other entity devices using the same service entity;
A computer program characterized by the above.

Images