JP2004355114A - Semantic information network system, session resume method, and session resume program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a semantic information network system capable of restoring a status before a line is disconnected in disconnecting and reconnecting the line in the semantic information network, and to provide a session resume method and a session resume program. <P>SOLUTION: This semantic information network 1 is configured by connecting a transmitting terminal 4 which transmits an event constituted of semantic information and data, a distributing terminal 2 which accepts the registration of a filter 3 constituted of the type and acquisition condition of the event and a receiving terminal 5 which registers the filter 3 in the distributing terminal 2, and receives the event. The receiving terminal 5 writes connection information with the distributing terminal 2 in a memory when connection with the distributing terminal 2 is established, and when the connection with the distributing terminal 2 is disconnected, the receiving terminal 5 reads the connection information from the memory, and restores the connection. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a semantic information network system, a session resume method, and a session resume program that can recover a state before disconnection when a connection is reestablished in a semantic information network.
In particular, a semantic information network that specifies information and content that match the interests of the end user from among information and content distributed on a network, or that identifies a terminal that transmits information and content to identify an optimal terminal to distribute the content to. For session resume processing.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, a mailing list service has been provided as a network for connecting friends having the same interests, hobbies, and purposes. The user can receive a message to the members of the mailing list by registering the mailing list with reference to the introduction of the mailing list (see Non-Patent Document 1).
Another object of the present invention is to provide an end user to specify optimum information from among a huge amount of information distributed on a network, and to specify an optimum user to whom an information provider should distribute information ( There is a Semantic Information-Oriented Network (hereinafter, referred to as a SIOnet) technology.
IONet is a network for delivering an event composed of semantic information and data, and determines an event delivery destination based on the contents of the semantic information, and sends an event to the determined delivery destination. It is realized by delivery.
[0003]
IONet is a meta network that delivers an event composed of data and semantic information of the data based on semantic information (metadata). The event receiver previously registers semantic information indicating the condition of the event to be received in IONet. When the event is transmitted from the event sender to the IONet, the IONet 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, transmitting an event to IONet is referred to as “stimulation” and means that the registered semantic information matches the semantic information of the event, and that the event recipient who registered the semantic information is notified of the event. It is called "ignition."
[0004]
As a result, a specific entity can be dynamically searched for and found from an unspecified large number of entities (terminals) super-dispersed on the network. That is, the IONet is a network that distributes events based on semantic information (to whom it is transmitted) instead of the destination address (to whom it is transmitted) used in the conventional network.
[0005]
Further, IONet is an autonomous decentralized cooperative network (autonomous decentralized computer) in which the network is self-organized by all entities including components of IONet performing autonomous decentralized coordination. The network components of IONet include "semantic information switch (SI-SW)", "semantic information router (SI-R)", "semantic information gateway (SI-GW)", "event place", "session" and the like. By self-organizing these as necessary, a secure and scalable P2P network can be constructed with a bottom-up approach.
[0006]
The basic concept / principle of SIONet is simple and unified. By repeating the simple operation of “registering a filter and sending an event by an entity”, ie, “stimulation” and “ignition” of an entity “chain-react” between the network elements of the IONet, all entities Is controlled by autonomous decentralized coordination. What 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 a “filter”. The chain reaction of the entities can be dynamically controlled by the filter value registered in the filter. Another basic concept in SIONet is an event place. Event places are entity groups interconnected by shared links, which can limit the scope of the chain reaction.
[0007]
[Patent Document 1]
JP-A-2002-94561
[Non-patent document 1]
"Mailing list", [online], [searched on May 28, 2003], Internet <URL: http: // www. egroup. co. jp>
[0008]
[Problems to be solved by the invention]
By the way, the setting and management of the above-described filter and the transmission and reception and control of the event are performed through a session set between the semantic information switch and the transmission / reception terminal. Here, "session" means a logical connection between the semantic information switch and the application on the transmitting / receiving terminal. The application can establish multiple sessions for the semantic information switch. The semantic information switch manages the filter for each session. The session establishment is executed, for example, when an application in the transmission / reception terminal requests an IONet control unit in the terminal to specify a event place name or an address of a semantic information switch to establish a session.
On the other hand, depending on the network environment (for example, dial-up or wireless LAN), a line (for example, a TCP connection) corresponding to a lower layer of the above-described session may be disconnected at any time. In the SIONEt, if the TCP connection is disconnected and the retry fails, both the semantic information switch and the transmitting / receiving terminal release the session for the purpose of garbage collection. The semantic information switch involves deleting a filter belonging to the session.
After that, if the application tries to enable event reception again, the event place name must be re-specified and the address of the semantic switch must be specified to re-establish the session, and the filter must be set again for the semantic switch. Is complicated.
[0009]
The present invention has been made in view of such circumstances, and an object of the present invention is to recover the state before the line was disconnected at the time of reconnection when the connection in the semantic information network is disconnected. It is an object of the present invention to provide a semantic information network system, a session resume method, and a session resume program.
[0010]
[Means for Solving the Problems]
The present invention has been made to solve the above problems, and the invention according to claim 1 includes a first terminal that transmits an event including semantic information and data, and a type and an acquisition condition of the event. Semantic information configured by connecting a second terminal that accepts registration of a filter and a third terminal that registers the filter in the second terminal and receives the event via the second terminal In the network, when the third terminal establishes a connection with the second terminal, the third terminal establishes a connection with the second terminal in a predetermined storage unit. Means for reading out the connection information from the storage means when the connection has been disconnected and restoring the connection with the second terminal.
[0011]
In the invention according to claim 2, in the invention according to claim 1, the third terminal further generates a unique identifier in an IP network when establishing a connection with the second terminal. Means for writing to the storage means and transmitting to the second terminal, and when the connection in the semantic information network is disconnected, when the connection with the second terminal is re-established, the storage means Means for reading out the generated identifier and re-establishing a session using the identifier, wherein the second terminal stores the identifier received from the third terminal in a predetermined storage unit of the second terminal. Means for writing, when the connection in the semantic information network is disconnected, when the connection with the third terminal is re-established, the received identifier is read from the storage means, If matches the identifier included in the session with the third terminal, characterized by comprising a means for recovering the authenticated connection that the a third terminal.
[0012]
Further, according to the invention described in claim 3, in the invention described in claim 1, the third terminal further includes connection information with the second terminal when establishing connection with the second terminal. Means for writing to the shared storage area in the storage means, and when the connection between the third terminal and the second terminal is disconnected, a terminal other than the third terminal is connected to the shared storage area in the storage means. Means for reading out the connection information and restoring the connection with the second terminal.
[0013]
The present invention according to claim 4, wherein a first terminal for transmitting an event composed of semantic information and data, a second terminal for accepting registration of a filter composed of the type of the event and an acquisition condition, and Is registered in the second terminal, and connected to a third terminal that receives the event via the second terminal, in the semantic information network, the third terminal, the second terminal At the time of establishing a connection with the terminal, the connection information with the second terminal is written in a predetermined storage means, and when the connection with the second terminal is disconnected, the connection information is read from the storage means. , Recovering the connection with the second terminal.
[0014]
According to a fifth aspect of the present invention, in the invention of the fourth aspect, the third terminal further generates a unique identifier in the IP network when establishing a connection with the second terminal. When writing to the storage means and transmitting to the second terminal, and the connection in the semantic information network is disconnected, when the connection with the second terminal is re-established, the Read the identifier, re-establish a session using the identifier, the second terminal writes the identifier received from the third terminal into a predetermined storage unit of the second terminal, the second terminal in the semantic information network When the connection with the third terminal is disconnected, when the connection with the third terminal is re-established, the received identifier is read from the storage means and included in the session with the third terminal. If consistent with that identifier, and wherein the recovering the authenticated connection that the a third terminal.
[0015]
According to a sixth aspect of the present invention, in the fourth aspect, the third terminal further includes connection information with the second terminal when establishing a connection with the second terminal. Is written to a shared storage area in the storage unit, and when the connection between the third terminal and the second terminal is disconnected, a terminal other than the third terminal stores the The method is characterized in that the connection information is read and the connection with the second terminal is restored.
[0016]
The present invention according to claim 7, wherein a first terminal for transmitting an event composed of semantic information and data, a second terminal for accepting registration of a filter composed of the type of the event and an acquisition condition, and Is registered in the second terminal, and the third terminal receiving the event via the second terminal is connected to the semantic information network. At the time of establishing a connection with the second terminal, a process of writing the connection information with the second terminal to a predetermined storage means, and when the connection with the second terminal is disconnected, the connection information is read from the storage means. And a process for reading and executing a process for restoring the connection with the second terminal.
[0017]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of a semantic information network system of the present invention will be described with reference to the drawings.
1 is a system configuration diagram of this embodiment, FIG. 2 is a system architecture diagram, FIG. 3 is a session establishment process flow (new connection) at the time of new connection, FIG. 4 is a session release process flow at the time of saving session information, and FIG. FIG. 6 shows a session release processing flow when session information is not stored, FIG. 6 shows a session establishment processing flow at the time of session re-establishment, and FIG. 7 shows a stored event information confirmation flow.
[0018]
<Network architecture>
First, the network architecture of the semantic information network system of the present embodiment will be described with reference to FIG. As shown in FIG. 1, the semantic information network system of the present embodiment is configured by connecting a delivery terminal 2, a transmitting terminal 4, and a receiving terminal 5 via a semantic information network 1. The delivery terminal 2, the transmission terminal 4, and the reception terminal 5 have the same system architecture except for different roles, and provide both functions. In this specification, for convenience of description, terminals (entities) are separately described as a delivery terminal 2 that delivers an event, a transmission terminal 4 of an event sender, and a reception terminal 5 of an event receiver.
[0019]
The event receiver registers the semantic information (the type of the received event and the acquisition condition) of the event that he or she wants to receive using the receiving terminal 5 as metadata in the semantic information network 1. This is called filter 3. The filter 3 includes a pair of an event type name and an attribute name and an attribute value to be accepted. Only events belonging to the event type defined by the event type name to be accepted are subject to filtering. In the present embodiment, a terminal on the semantic information network 1 on which the filter 3 is set is referred to as a delivery terminal 2. That is, the delivery terminal 2 is equivalent to the semantic information switch configuring the above-described IONet.
On the other hand, the event sender stimulates the semantic information network 1 by sending an event to the semantic information network 1 using the transmitting terminal 4.
[0020]
An event is composed of semantic information and data describing the characteristics of the event. The semantic information is metadata of an event and is an instance of a semantic information type (event type). The event type is an event template in which an event type name and a condition name, and a data type and a conditional expression for each condition name are defined. The event type name is a name for uniquely identifying the event type.
That is, an event is composed of an event type name, a combination of a condition name and a condition value, and a data part. If the condition name, condition expression, and condition value defined in the event do not match the event type, an error will occur.
[0021]
The semantic information network 1 is an autonomous distributed collation network for collating (filtering) an event sent by an event sender with a filter registered by an event recipient. As a result of the event collation by the delivery terminal 2, the filter 3 that has passed the event (in response to the event, that is, the event matches the filter) fires, and the receiving terminal 5 of the corresponding event receiver starts autonomously. With this mechanism, a target terminal is searched and found in a scalable and real-time manner from an unspecified number of terminals.
[0022]
The semantic information network 1 specifically includes a semantic information switch, a semantic information router, and a semantic information gateway.
The semantic information switch compares the semantic information registered as a filter with the semantic information given to the event, and as a result, provides a switching mechanism for activating the terminal of the event receiver that fired. The semantic information switch and each terminal are connected in a star type.
The semantic information router plays a role of selecting an event route between the semantic information switches and transferring an event sent from the terminal to the semantic information switch to another semantic information switch. This is achieved by dynamic event routing based on semantic information.
[0023]
The semantic information gateway transfers events between event places.
Here, the event place is a minimum unit that guarantees a common semantic information space in the semantic information network. In the event place, the uniqueness of the ontology system such as the name, concept, vocabulary, meaning, and association of the event type is guaranteed, and semantic information is described based on the common ontology.
Basically, the event sent from the terminal of the event sender is distributed only within the event place, but through the semantic information gateway, the event can be exchanged between event places having different ontology systems. Become. At this time, the semantic information gateway performs the ontology conversion of the event, and then transfers the event to a different event place.
That is, the shared link is a link for performing bidirectional event sharing between terminals. An event place is a network configured by connecting terminals via a shared link. The semantic information is a vocabulary and a value indicating characteristics of transmission data, and is an instance in a certain lexical concept.
Note that in this specification, the delivery terminal 2 implements an event delivery function realized by the meaning information switch, the meaning information router, and the meaning information gateway.
[0024]
Next, the configurations of the transmitting terminal 4 and the receiving terminal 5 of the present embodiment will be described with reference to FIG. As described above, the transmitting terminal 4 and the receiving terminal 5 of the present embodiment have the same architecture, and include the application unit 10, the control unit 11, and the session management unit 12.
The application unit 10 registers an information collection request (information search request) input by a user via an input unit (not shown) as a filter 3 in the delivery terminal 2 and receives an event via the delivery terminal 2. Here, the filter 3 includes an event type and an acquisition condition.
That is, the application unit 10 outputs an information collection request to the delivery terminal 2 via the control unit 11, receives the information collected from the delivery terminal 2 via the control unit 2, and displays the information on the screen unit (not shown). It is provided to the user by displaying.
[0025]
Further, the application unit 10 transmits, as an event, the arrangement information input by the user via an input unit (not shown). Here, the event includes semantic information and data.
That is, the application unit 10 outputs the arrangement information to the delivery terminal 2 via the control unit 11, receives the information collected from the delivery terminal 2 via the control unit 2, and displays the information on the screen unit (not shown). To provide it to the user.
[0026]
The control unit 11 executes a data communication process with the delivery terminal 2 based on the session management by the session management unit 12, and includes a transmission unit 21 and a reception unit 20. The control unit 11 functions as the transmitting terminal 4 when the transmitting unit 21 is used, and functions as the receiving terminal 5 when the receiving unit 20 is used.
The session management unit 12 provides a session resume function (reconnection establishment function) by operating in conjunction with the control unit 11 (described later).
The delivery terminal 2 receives the registration of the filter 3 from the reception terminal 5, matches the event transmitted from the transmission terminal 4 with the filter 3, and provides a function of delivering the event based on the matching result.
[0027]
Next, the operation of the semantic information network system of the present embodiment will be described with reference to the drawings. FIG. 3 shows the internal flow of the receiving terminal 5 and the flow of communication processing between the receiving terminal 5 and the delivery terminal 2 when the receiving terminal 5 newly creates a session with the delivery terminal 2 in the semantic information network system of the present embodiment. It is a flowchart which shows.
Hereinafter, when information is exchanged with the application or the delivery terminal 2, the control unit 11 and the session management unit 12 store the information in a memory (corresponding to the storage unit in FIG. 3 and hereinafter referred to as a memory). The description is based on the premise that information is stored.
[0028]
First, the application unit 10 issues an event place information collection request to the control unit 11 in the semantic information network 1 (step S1 in FIG. 3). The information collection request includes the name of the application that issued the request (corresponding to the APL name in FIG. 3, hereinafter referred to as the APL name), the IP address of the receiving terminal 5, and the port number in the TCP session.
The control unit 11 specifies the delivery terminal 2 based on the IP address and the port number input from the application unit 10, and acquires event place information from the delivery terminal 2 (Steps S2 and S3). The event place information includes the event place name, a description of the event place name, and the IP address of the delivery terminal.
After writing the collected event place information in the memory, the control unit 11 returns the obtained event place information to the application unit 10 and the number of existing event places (step S4).
Next, the application unit 10 issues an information collection request for all other event places, and the control unit 11 writes the information into the memory and returns the information to the application unit 10 (steps S5 and S6).
[0029]
When the information of the event place is acquired, the application unit 10 sends a reception session establishment request to the event place where the session is to be generated via the control unit 11 (step S7). The reception session establishment request includes the event place name of the delivery terminal 2 and the IP address of the delivery terminal 2. On the other hand, the application unit 10 does not specify the session ID to the control unit 11 at this time.
The control unit 11 notifies the session management unit 12 of a reception session establishment request from the application unit 10.
In response to the reception session establishment request, the session management unit 12 newly generates a session ID (step S8), writes it into the memory (step S9), and notifies the control unit 11 of the generated session ID (step S9). S10).
The generated session ID may be based on, for example, a terminal IP address and a randomly generated 128-bit Globally Unique Identifier (GUID), thereby ensuring uniqueness within the IP network. .
[0030]
The control unit 11 temporarily stores the session ID and the APL name (Step S11), sends a reception session establishment request issued by the application unit 10 to the delivery terminal 2, and establishes a session (Step S12).
Upon establishment of the reception session, the delivery terminal 2 receives the reception session establishment request, stores the session ID and the event place name (step S13), and then notifies the reception terminal 5 of the reception session establishment (step S14). . Here, since it is assumed that the session ID includes the IP address of the receiving terminal, it is not necessary to store the IP address of the receiving terminal in step S13.
Upon receiving the reception session establishment notification, the control unit 11 notifies the application unit 10 of the session establishment and the reception session ID (step S15).
[0031]
Next, a process in which the receiving terminal 5 disconnects the session while retaining the session information will be described. FIG. 4 is a flowchart showing a flow of processing in which the receiving terminal 5 disconnects the session with the delivery terminal 2 while retaining the session information.
When the application unit 10 issues a session disconnection request (session release shown in FIG. 4) to the control unit 11 when establishing a connection with the delivery terminal 2 (S20 in FIG. 4), the control unit 11 Then, the current session information is designated to be stored in the memory via the memory 12 (step S21). The storage designation includes a session ID and session information.
The session management unit 12 writes the session information (session ID, APL name, which is connection information with the delivery terminal 2) to the memory according to the save designation from the control unit 11 (step S22). Then, the session management unit 12 confirms that the storage of the session information has been completed, and notifies the control unit 11 of the storage of the session information (step S23).
The control unit 11 sends a session release notification to the application unit 10 (Step S24).
[0032]
Next, a process in which the receiving terminal 5 disconnects the session after deleting the session information will be described. FIG. 5 is a flowchart showing a flow of processing for disconnecting the session between the receiving terminal 5 and the delivery terminal 2 after the receiving terminal 5 deletes the session information.
When the application unit 10 issues a session disconnection request (session release shown in FIG. 5) to the control unit 11 (step S30), the control unit 11 sends the generated transmission session and reception session to the delivery terminal 2. Is requested (step S31).
[0033]
Upon receiving the release request for the transmission session and the reception session, the delivery terminal 2 issues a release completion notification to all the generated sessions (step S32).
Upon receiving the release completion notification from the delivery terminal 2, the control unit 11 instructs the session management unit 12 to delete the session information written in the memory (Step S33). The deletion designation includes a session ID and session information.
After deleting the session information by deleting the session information (step S34), the session management unit 12 notifies the control unit 11 of the completion of the deletion of the session information (step S35).
The control unit 11 receives the session information deletion notification from the session management unit 12, and notifies the application unit 10 that the session release has ended (step S36).
[0034]
Next, a process in which the receiving terminal 5 re-establishes a session after the session is generated will be described. FIG. 6 is a flowchart illustrating a process flow when a session re-establishment request is issued from the application unit 10 after the session is disconnected.
When the application unit 10 issues a session establishment request (reception session establishment in FIG. 6) (step S40 in FIG. 6), the control unit 11 sets the session ID (the last established reception session ID) included in the session establishment request. On the basis of this, a request for searching for session information in the memory is issued to the session management unit 12 (step S41).
When the session information corresponding to the session ID is stored, the session management unit 12 reads the corresponding session information (Step S42) and notifies the control unit 11 (Step S43).
[0035]
The control unit 11 receives the notification of the session information corresponding to the session ID from the session management unit 12, and requests the delivery terminal 2 to re-establish the session (step S44). At this time, the control unit 11 transmits a session re-establishment request together with the session ID notified from the application unit 10 (Step S44).
The delivery terminal 2 compares the session ID sent from the control unit 11 with the session ID written in the memory on the delivery terminal 2. When these session IDs match, the delivery terminal 2 authenticates the receiving terminal 5, and notifies the session re-establishment result using the session ID (step S45).
[0036]
On the other hand, when these session IDs do not match, the delivery terminal 2 returns a message indicating that the user has not been authenticated to the receiving terminal 5 and creates a new session with the receiving terminal 5. When a new session is generated, the delivery terminal 2 and the reception terminal 5 execute the same processing as steps S1 to S15 again.
When confirming the session re-establishment result notification from the delivery terminal 2, the control unit 11 sends a session generation end notification to the application unit 10 (step S46).
[0037]
Note that the receiving terminal 5 does not necessarily need to be a terminal that has previously established a session, and session rest can be resumed at a different receiving terminal 5 by copying session information between memories (described later).
[0038]
Next, a process in which the receiving terminal 5 acquires the event information stored in the delivery terminal 2 after the session is generated will be described. FIG. 7 is a flowchart illustrating a flow of a process of acquiring the event information stored in the delivery terminal 2 after the session is generated.
When the application unit 10 issues an event information acquisition request (Step S50 in FIG. 7), the control unit 11 requests the delivery terminal 2 to acquire a stored event (Step S51).
If there is an event stored, the delivery terminal 2 returns the stored event information to the receiving terminal 5 (Step S52), and deletes the event information stored in the delivery terminal 2 (Step S53).
When acquiring the event information from the delivery terminal 2, the control unit 11 outputs the event information to the application unit 10 (Step S54).
[0039]
As described above, according to the semantic information network system of the present embodiment, when a line is disconnected at a terminal connected using a dial-up line or a terminal connected using a wireless line, the communication is performed again. By automatically restoring the state before the line was disconnected upon connection, the trouble of setting a new session again becomes unnecessary.
That is, by using the semantic information network system of the present embodiment, it is possible to realize a session resume function which is a reconnection function required when a communication line between end terminals is assumed to be disconnected.
Specifically, the receiving terminal of the member who wants to obtain information stores the necessary information in advance, assuming that the communication line between the terminals will be disconnected, so that the previously stored information can be stored after disconnection. By withdrawing, the connection with the delivery terminal is restored, and the same effect as before the line disconnection can be received.
[0040]
Also, in the semantic information network system of the present embodiment, when the receiving terminal sets up a session with the delivery terminal, it is guaranteed that the receiving terminal is unique within the IP network so that both parties can identify each other. By generating a unique ID that can be generated and maintaining the IDs when the line is disconnected, it is possible to confirm that the session is with the same partner as before the line disconnection when re-establishing the session.
[0041]
Further, after the receiving terminal has set up a session with the delivery terminal, the receiving terminal saves information necessary and sufficient to reset the session later as a file, and after the line between the receiving terminal and the delivery terminal is disconnected, The saved file is read by a receiving terminal different from the receiving terminal that has set the session so far, the session is set with the delivery terminal on the receiving terminal that has newly read the file, and the information read from the file is used, so the Even at the receiving terminal, it is possible to restore under the same conditions as the session connected before the line disconnection, and to automatically reproduce the same environment as before the line connection.
[0042]
In the present embodiment, an example in which the session information is stored in any area of the storage unit is not particularly limited. However, the present invention is not limited to this. The connection information with the delivery terminal 2 may be written in a shared storage area in the storage unit.
[0043]
In this case, when the connection with the delivery terminal 2 is established, the receiving terminal 5 first generates a unique identifier in the IP network, writes it into the shared memory, and transmits the identifier to the delivery terminal 2.
[0044]
Then, when the session with the delivery terminal 2 is reestablished, the receiving terminal 5 reads the generated identifier from the shared memory and uses the identifier.
At this time, when re-establishing a session with the receiving terminal 5, the delivery terminal 2 reads the identifier from the memory, and if the identifier matches the identifier included in the session re-establishment request from the receiving terminal 5, the receiving terminal 5 Authenticate and restore connection
Therefore, when the connection between the receiving terminal 5 and the delivery terminal 2 is disconnected, a terminal other than the receiving terminal 5 reads the connection information from the shared memory (a shared storage area in the storage unit) and establishes a connection with the delivery terminal 2. You can also recover.
[0045]
Here, the terminal other than the receiving terminal 5 is a terminal equivalent to the transmitting terminal 4 and the receiving terminal 5 in the system architecture regardless of whether or not the receiving terminal is connected to the semantic information network 1 in advance. Just fine. Also, the terminal other than the receiving terminal 5 naturally includes a terminal physically different from the receiving terminal 5, but the present invention is not limited to this, and the present invention is not limited to this. Other applications are included.
[0046]
Next, a second embodiment of the semantic information network system of the present invention will be described with reference to the drawings. FIG. 7 is a flowchart illustrating a flow of a session release process in the semantic information network system according to the present embodiment.
The difference between the flow of the session release process in the semantic information network system of the present embodiment and the flow of the session release process in the semantic information network system of the first embodiment is that the session ID is directly returned to the application unit 10. Instead, the session management unit 12 generates a resume ID corresponding to the session ID, and the application unit 10 reestablishes a session using the resume ID.
[0047]
That is, when the application unit 10 issues a session disconnection request (session release shown in FIG. 8) to the control unit 11 at the time of establishing a connection with the delivery terminal 2 (corresponding to S20 in FIG. 8 and S20 in FIG. 4). The control unit 11 specifies the current session information to be stored in the memory via the session management unit 12 (step S21 in FIG. 8). The storage designation includes a session ID and session information.
The session management unit 12 writes the session information (session ID, APL name, which is connection information with the delivery terminal 2) to the memory according to the save designation from the control unit 11 (step S22 in FIG. 4). In the present embodiment, the session management unit 12 generates a resume ID corresponding to the session ID (step S60 in FIG. 8), and adds the session information (session ID, which is connection information with the delivery terminal 2; (APL name + resume ID) is written into the memory (step S22 in FIG. 8).
[0048]
Then, the session management unit 12 confirms that the storage of the session information has been completed, notifies the control unit 11 of the storage of the session information, and notifies the control unit 11 of the resume ID (step S23).
The control unit 11 notifies the application unit 10 of the session release and the resume ID (step S24).
[0049]
Next, a process in which the receiving terminal 5 reestablishes a session using the resume ID will be described. FIG. 9 is a flowchart showing the flow of processing when the connection is re-established using the resume ID after the session is disconnected.
When the application unit 10 issues a session establishment request (reception session establishment in FIG. 9), in the present embodiment, a resume ID is used instead of the session ID (step S40 in FIG. 9).
The control unit 11 issues a search request for session information on the memory to the session management unit 12 based on the resume ID included in the session establishment request (resume ID corresponding to the last established reception session ID). (Step S41).
[0050]
The session management unit 12 searches for the session information corresponding to the resume ID using the resume ID as a key instead of the session ID. When the session information corresponding to the resume ID is stored, the corresponding session information is read (step S42), and the control unit 11 is notified of the session information together with the session ID (step S43).
The control unit 11 receives the notification of the session information corresponding to the resume ID from the session management unit 12, and requests the delivery terminal 2 to re-establish a session (step S44). At this time, the control unit 11 transmits a session re-establishment request together with the session ID notified from the application unit 10 (Step S44).
[0051]
The delivery terminal 2 compares the session ID sent from the control unit 11 with the session ID written in the memory on the delivery terminal 2. When these session IDs match, the delivery terminal 2 authenticates the receiving terminal 5, and notifies the session re-establishment result using the session ID (step S45).
On the other hand, when these session IDs do not match, the delivery terminal 2 returns a message indicating that the user has not been authenticated to the receiving terminal 5 and creates a new session with the receiving terminal 5. When a new session is generated, the delivery terminal 2 and the reception terminal 5 execute the same processing as steps S1 to S15 again.
When confirming the session re-establishment result notification from the delivery terminal 2, the control unit 11 sends a session generation end notification to the application unit 10 (step S46).
[0052]
Therefore, according to the semantic information network system of the present embodiment, the session ID is not returned to the application unit 10, and the session ID is managed only by the session management unit 12 using the resume ID for managing the correspondence with the session ID. Since the session information is managed, even if the session ID is stolen, the effect of preventing impersonation by a third party can be obtained.
[0053]
The delivery terminal 2, the transmission terminal 4, and the reception terminal 5 have a computer system therein.
A series of processes relating to the above-described session resume process is stored in a computer-readable recording medium in the form of a program, and the program is read and executed by a computer to perform the process.
That is, each processing means and processing unit in the delivery terminal 2, the transmission terminal 4, and the reception terminal 5 is configured such that a central processing unit such as a CPU reads the above program into a main storage device such as a ROM or a RAM and processes the information. This is realized by executing arithmetic processing.
Here, the computer-readable recording medium refers to a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like. Alternatively, the computer program may be distributed to a computer via a communication line, and the computer that has received the distribution may execute the program.
[0054]
【The invention's effect】
As described above, the present invention provides a first terminal (for example, the transmitting terminal 4 in the embodiment) for transmitting an event including semantic information and data, and a filter (for example, A second terminal that receives registration of the filter 3) in the embodiment (for example, the delivery terminal 2 in the embodiment) and a second terminal that registers the filter in the second terminal and receives an event via the second terminal In a semantic information network (for example, the semantic information network 1 in the embodiment or the SIIONet) configured by connecting the third terminal (for example, the receiving terminal 5 in the embodiment), the third terminal When the connection with the second terminal is established, the connection information with the second terminal is written in a predetermined storage means (for example, the memory in the embodiment), and the second When the connection with the terminal is disconnected, the connection information is read from the storage means and the connection with the second terminal is restored, so that the state before the line was disconnected at the time of reconnection can be restored. Obtainable.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram showing a system configuration.
FIG. 2 is a system architecture diagram.
FIG. 3 Session establishment processing (new connection)
FIG. 4 is a session release processing flow (session information storage).
FIG. 5 is a session release processing flow (without storing session information).
FIG. 6 is a flowchart showing a session establishment process (session re-establishment).
FIG. 7 is a flow chart for confirming stored event information.
FIG. 8 is a flowchart showing a session release process (using a resume ID).
FIG. 9 is a flow of a session establishment process (using a resume ID).
[Explanation of symbols]
1. Semantic information network
2 ... Delivery terminal 2
3… Semantic information filter
4 ... Sending terminal
5 ... receiving terminal 5

Claims (7)

A first terminal transmitting an event composed of semantic information and data, a second terminal receiving registration of a filter composed of the type of the event and an acquisition condition, and registering the filter in the second terminal; In a semantic information network configured by connecting a third terminal that receives the event via a second terminal,
The third terminal,
Means for writing connection information with the second terminal to a predetermined storage means when establishing a connection with the second terminal;
Means for reading out the connection information from the storage means when the connection with the second terminal is disconnected, and restoring the connection with the second terminal. . The third terminal further comprises:
Means for generating a unique identifier in an IP network, writing the same in the storage means, and transmitting the identifier to the second terminal when establishing a connection with the second terminal;
Means for reading out the generated identifier from the storage means and re-establishing a session using the identifier when re-establishing a connection with the second terminal when the connection in the semantic information network is disconnected. Equipped,
The second terminal comprises:
Means for writing an identifier received from the third terminal into a predetermined storage unit of the second terminal;
When the connection in the semantic information network is disconnected, at the time of reestablishing the connection with the third terminal, the received identifier is read from the storage means, and the identifier included in the session with the third terminal is read. 2. The semantic information network system according to claim 1, further comprising: means for authenticating that the terminal is the third terminal, and recovering the connection if the two terminals match. The third terminal further comprises:
Means for writing connection information with the second terminal to a shared storage area in the storage means when establishing connection with the second terminal;
When the connection between the third terminal and the second terminal is disconnected, a terminal other than the third terminal reads the connection information from a shared storage area in the storage unit, and the second terminal 2. The semantic information network system according to claim 1, further comprising means for restoring the connection with the network. A first terminal transmitting an event composed of semantic information and data, a second terminal receiving registration of a filter composed of the type of the event and an acquisition condition, and registering the filter in the second terminal; In a semantic information network configured by connecting a third terminal that receives the event via a second terminal,
The third terminal,
When establishing a connection with the second terminal, the connection information with the second terminal is written in a predetermined storage means,
A session resume method, wherein when the connection with the second terminal is disconnected, the connection information is read from the storage unit to restore the connection with the second terminal. The third terminal further comprises:
At the time of establishing a connection with the second terminal, a unique identifier in the IP network is generated and written in the storage unit, and transmitted to the second terminal,
When the connection in the semantic information network is disconnected, at the time of re-establishing a connection with the second terminal, read the generated identifier from the storage means, and re-establish a session using the identifier,
The second terminal comprises:
Writing an identifier received from the third terminal in a predetermined storage unit of the second terminal,
When the connection in the semantic information network is disconnected, at the time of reestablishing the connection with the third terminal, the received identifier is read from the storage means, and the identifier included in the session with the third terminal is read. 5. The session resume method according to claim 4, wherein, if they match, the third terminal is authenticated to restore the connection. The third terminal further comprises:
At the time of establishing a connection with the second terminal, the connection information with the second terminal is written into a shared storage area in the storage means,
When the connection between the third terminal and the second terminal is disconnected, a terminal other than the third terminal reads the connection information from a shared storage area in the storage unit, and the second terminal The method according to claim 4, wherein the connection with the terminal is restored. A first terminal transmitting an event composed of semantic information and data, a second terminal receiving registration of a filter composed of the type of the event and an acquisition condition, and registering the filter in the second terminal; In a semantic information network configured by connecting a third terminal that receives the event via a second terminal,
In the third terminal,
When establishing a connection with the second terminal, a process of writing connection information with the second terminal to a predetermined storage unit;
A session resuming program for executing, when the connection with the second terminal is disconnected, reading the connection information from the storage means and restoring the connection with the second terminal.

Images