JP2002259631A - Method and system for electronic library service, book user side terminal and book provider side terminal - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize timely book provision and to eliminate mediation charges by eliminating a mediator in electronic library services. SOLUTION: When book providers B1 -B3 set the identification information/ utilization conditions or the like of books to be provided by using applications 51 -53 for book provision, there are set to a semantic information network 3 as filters. On the other hand, a book user A prepares a book utilization request event containing the identification condition/utilization condition of a desired book by using an application 4 for book utilization and transmits it to the semantic information network 3. Then, the book utilization request event is received by the book provider side terminal of a book provider matched to the conditions set to its own filter by the book utilization request event among the book providers B1 -B3 . On the basis of request information in the event, book guide information or the like is inputted and returned to a book demander side terminal 1 by the book provider side terminal.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to an electronic library service method and system.

[0002]

2. Description of the Related Art In a conventional digital library service, a digital library operator intervenes as an intermediary between a book user and a book provider. Digital library operators obtain books by donating books from book providers or purchasing books on their own, and if possible, digitizing them, and widely covering books that they have not obtained. A library for sending and receiving digitized books, passing non-digitized books, and accessing books in other locations (OPAC) by forming a network with other (electronic) libraries to exchange book information
It provides search and interlibrary lending (ILL) services to meet the needs of book users. Using the search support function provided by the digital library, the book user sends a request for desired book attributes and usage conditions to the digital library operator, and requests the book presented by the digital library. If there is, you can receive digitized books or borrow non-digitized books, and if you do not have anything you want, OPAC or ILL
Use the services of Here, books refer to books, magazines, and all other items handled by libraries for users, and include those that can be digitized and those that are not. In addition, there may be various costs such as commissions, purchases, and digitization between digital library operators and their participants.

FIG. 12 is a block diagram of a conventional example of this kind of electronic library service system.

[0004] Library user side terminal 11 and the book provider side terminal to the network 14 _1, such as the Internet 12 _1, 12 ₂
Electronic Library 13 ₁ exists with. Also, book provider side terminal 1 also to the network 14 ₂ such as the Internet
2 _3, 12 ₄ and the electronic library 13 ₂ exists. The book user side terminal 11 has a book use application 15, the book provider side terminals 12 ₁ , 12 ₂ , 12 ₃ and 12 ₄ have book provision applications 16 ₁ , 16 ₂ , 16 ₃ and 16 ₄ , and an electronic library. Electronic library applications 17 ₁ and 17 ₂ are installed in 13 ₁ and 13 ₂ , respectively.

[0005] The book providers B ₁ and B ₂ respectively receive the book providing application 1 from the book provider terminals 12 ₁ and 12 _2.
Using 6 ₁ and 16 ₂ , the books to be provided can be stored in the electronic library 13 ₁
(1). Similarly, a library provider B _3, B ₄ are each book provider terminal 12 _3, 12 ₄ library providing application 16 _3, 16 _4, and registers the books to be provided to the digital library 13 ₂ (1 ). The library user A performs a search of the book to be their input to the electronic library 13 ₁ by using the library available for application 15 in library user terminal 11 (2). The electronic library application 17 ₁ of the electronic library 13 ₁ requests the electronic library 13 ₂ for a book search via OPAC / ILL for books not in its own (2 ′), and the electronic library application 17 ₁ of the electronic library 132 _{2 2} books available books information (books data, index data) as Library information (mainly index data) to the electronic library 13 ₁ (2 "). electronic Library application 17 ₁ of the electronic library 13 ₁ result Is transmitted to the client side terminal 11 (3).

[0006]

[Problems to be Solved by the Invention] The above-mentioned conventional electronic library service system has the following problems:-Real-time performance is reduced due to the presence of an intermediary.・ It is necessary to know the existence of intermediaries ・ There is a procedure for accessing books in other places ・ There is a problem that it is difficult to provide books in a timely manner.

[0007] An object of the present invention is to improve the real-time property of book access, eliminate the costs associated with mediation,
Even if the load is distributed and an unspecified number of book users or book providers can be met without knowing the existence of intermediaries or taking steps to access books elsewhere, An object of the present invention is to provide an electronic library service method and system capable of providing books.

[0008]

In order to achieve the above object, the present invention uses a semantic information network for distributing information based on semantic information given to information as a network, and performs the following processing. (1) The book use application on the book user terminal and the book provision application on the book provider terminal are connected to the semantic information network. (2) One or more book providers use the book providing application, and provide book identification information (eg, book name, author name, book classification code, etc.) and use conditions (eg, language used, age limit). , Occupation limitation, etc.), book guidance information (reference information indicating the contents of the book) and book acquisition information (digitized book access information, non-digitized book contact information, etc.) into the book provider's terminal and use the book. Start accepting requests. At this time, the book providing application sets information for selectively accepting the book use request as a filter in the semantic information network. (3) The book user uses the book use application to input a use request including book identification information and use conditions to the book user side terminal. At this time, the book use application sends a use request as an event to the semantic information network, and also includes return destination information for receiving a response to the request in the event. Here, the book identification information and usage conditions do not need to specify all the information, and there are various combinations of each information (such as union and intersection of information and a hierarchical structure between information). Names such as book names do not always match exactly. further,
Each item of the usage condition may be collected by the book use application receiving an input from the book user in advance or obtaining an estimated value from the book user's usage tendency. (4) In the semantic information network, the use request event is matched with each filter, and the event is received by the terminal of the book provider who has set a filter that matches the use request of the event. When the book providing application receives the use request event, the book provider confirms the request from the book user on the book providing application screen, and the book provider inputs book guide information and book obtaining information. Or the book providing application automatically sets book guide information and book acquisition information and returns the book to the book user. The reply destination information is extracted from the event by the book providing application. Here, when the use request event reaches the providing application via the semantic information network, it is not necessary to be aware of the location information other than the contact information of the non-electronic book, and the library for accessing the book in another place is not needed. It eliminates the need for conventional services of catalog (OPAC) retrieval and interlibrary lending (ILL) and the creation of a physical or virtual network for it. (5) When the book use application used by the book user receives the reply of the book content information and the book acquisition information,
The book guidance information and the book acquisition information are displayed to the book user on the application screen, and when access to the digitized book is instructed by the book user, the access of the information is performed based on the digitized book access information. Do. (6) As a part of the book search support function, the book use application is embedded in the book guide information or the digitized book accessed, for example, another book such as a so-called hypertext search for finding a related book. A new use request event is created and transmitted to the semantic information network in accordance with the book user's selection instruction based on the access information to the book. Here, the access information can be set, for example, between book providers, but is left to the policy of each book provider. The flow after the response to the event is the same as (4) and (5). (7) There is also an information providing form in which an event is transmitted from a book provider in preparation for notification of a newly-published book to a book user who has a preference. In this case, the book user's book is processed in step 2). In order for the use application to selectively accept the event, the preference information extracted from the information used to create the use request is set in the semantic information network as a filter. The notification by the event is transmitted to the book user when the book user is using or reusing the book use application program, and there may be a delay. If it has already been generated when replying to the use request, it may be sent together with the original reply information.

Before describing the embodiments of the present invention, a description will be given of a distributed network system in which the message of transmitted information is enhanced, which is a premise of the present invention.

[0010] As a distributed type network system, a system using Napster is known, and as a network system with enhanced dispersibility, Gnute is used.
One using lla is known.

First, a network system using Napster will be described. The Napster user sends a search request to the Napster server that stores the information of the file published by each Napster user, and the Napster server sends information such as the IP address of the Napster user who owns the searched file. Reply. The actual exchange of files is performed by the user who has obtained the IP address directly accessing the Napster user who owns the target file without going through a Napster server.

In the case of a network system using Gnutella, the terminal of the Gnutella user is:
The state of the connected partner terminal is periodically checked, and messages and file search requests are relayed. The search results are returned to the person who made the search request, and the subsequent file transfer is performed directly between the users, similar to Napster. As a result, a network is constructed without using a server.

[0013] Of these network systems,
The system using Napster does not achieve the object of the present invention because it requires a server corresponding to an intermediary which is a problem of the present invention.

In a network system using Gnutella, a search request for a message or a file is made without using a server, but the information to be transmitted is merely a file search request, and a user who confirms this response transfers the file. Is conducted between users.
It is not suitable for a form that requires exchange with a plurality.

There is a semantic information network system described below as a distributed network system in which the message of the information to be transmitted is enhanced, and the present invention is based on the use of such a semantic information network system.

First, a semantic information network (Semantic I
An outline of an nformation-Oriented Network (hereinafter, referred to as a SION) will be described. The SION is a network that can deliver an event to a destination based on semantic information. FIG. 13 shows a conceptual model of the SION. In FIG. 13, each terminal 22 has semantic information (Se
mantic Information (SI) is registered in the SION 21. On the other hand, the terminal 22 that transmits the event
An event composed of semantic information and data shown in FIG. The semantic information described here describes the characteristics of the data included in the event, and is positioned as meta information of the data. For example, the semantic information is as follows:-Deliver the data to "Tokyo residents". -Deliver the data to "People interested in classics". -Deliver the data to "people who have a communication environment of 1 Mbps or more".・ Deliver the data to "people who are traveling on Mejiro Street". Deliver the data to "content providers with content that matches the keyword (eg, travel)". Is used.

The SION 21 dynamically determines an object (terminal, person, software, etc.) to which data is to be delivered based on the semantic information as described above, and delivers the data to the specified target person. It is an autonomous decentralized meta-network that can make notifications. By using the SION 21, it is possible to directly propose own information only to a user who is appropriate for the information provider to provide without using a broker. In this case, a business model that enables peer-to-peer information proposals with a broker-independent type (non-broker model) is called a patronage model (or a patronage-type information proposal model or non-broker model). Call. Similarly, a real-time information search that allows a user to directly search for desired information without using a search service (broker) is also possible. In addition,
It is possible to apply to the following services and the like as a request-by-order information proposal service. (1) Manufacturing company: I want to send product information mainly to customers who are likely to be interested in their products. (2) Advertiser: I want to send a personalized advertisement for each customer. (3) Barter: I want to buy and sell or exchange products based on agreement between users.

Note that what information is set in the data part of the event depends on the service. For example, various usage forms such as an entity of information, a reference to information (URL, distributed object identifier, etc.), a proxy (Jini proxy, etc.), and a mobile agent are possible.

Next, the details of the SION will be described.

<SION Architecture> First, SIO
It will be described N21 network architecture. FIG. 15 shows a network model of the SION 21. Here, for convenience of explanation, the terminal 22 is separately described as a transmitting terminal 31 of the event sender and a receiving terminal 32 of the event receiver. The event receiver uses the receiving terminal 32 to register the semantic information (the type of the received event and the acquisition condition) of the event that the user wants to receive as metadata in the SION 21. Filter this (Fi
lter). On the other hand, the event sender is the sending terminal 31
By sending an event to the ION 21 using, the stimulus (Incentive) is given to the ION 21. This event is composed of semantic information and data describing the characteristics of the event, as shown in FIG. FIG. 16 shows the definition of the semantic information. The semantic information is event metadata and is an instance of a semantic information type (event type).

The SION 21 is an autonomous decentralized 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 matching, the filter that passes the event (responds to the event) is fired (Igniti
on), and the receiving terminal 32 of the corresponding event receiver starts autonomously. With this mechanism, it is possible to search for and find the target terminal 22 from the unspecified number of terminals 2 in a scalable and real-time manner.

Next, the event type will be described.
FIG. 17 shows an example of defining an event type which is an event template. As shown in FIG. 17, the event type includes an event type name (Event type name) and a condition name (in FIG. 17, “Service” and “CPU power” correspond to each other), and a data type ( A conditional expression (corresponding to == or> =) is defined. The event type name is a name for uniquely identifying the event type.

Note that the parent type of the event type can be inherited.

As shown in FIG. 18, an event is created in accordance with the data structure of the event type. The event is
It consists 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. However, the condition names used in the event may be a subset of the event type.

FIG. 19 shows a definition example of a filter. The filter accepts the event type name (Event type nam
e), attribute name (in FIG. 19, “CPU power” or “Ag
e ") and an attribute value (200 in FIG. 19).
And 25). Only events belonging to the event type defined by the event type name to be accepted are subject to filtering. here,
Multiple event type names can be defined, and by specifying a wildcard (*. *),
It is also possible to target all events. In addition,
If the attribute name defined by the filter does not exist in the condition name of the event type defined by the event type name to be accepted, an error occurs. However, a subset of the event type may be used.

Next, the configuration of the SION 21 will be described. FIG. 20 is a diagram illustrating the configuration of the SION 21. As shown in FIG. 20, the SION 21 is a semantic information switch (Semant
ic Information-Switch, shown as SI-SW in the drawing), Semantic Information-Route
r, shown as SI-R in the drawing), Semantic Information-Gateway (SI-R in the drawing)
GW).

The semantic information switch (SI-SW) collates the semantic information registered as a filter with the semantic information given to the event, and as a result, activates a switching mechanism for activating the terminal 2 of the event receiver that fired. provide. The semantic information switch (SI-SW) and each terminal 2 are connected in a star configuration.

The semantic information router (SI-R) selects an event route between the semantic information switches,
2 has a role of transferring an event sent to the semantic information switch to another semantic information switch. this is,
Achieved by dynamic event routing based on semantic information.

The semantic information gateway (SI-GW)
Transfer events between event places. Here, the event place is a minimum unit (ontology domain) that guarantees a common semantic information space. 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 the semantic information is described based on the common ontology. Basically, an event sent from the terminal 22 of the event sender is distributed only in the event place, but the semantic information gateway (SI
-GW), it is possible to exchange events between event places having different ontology systems. At this time, the semantic information gateway (SI-
After performing the ontology conversion of the event, the GW transfers the event to a different event place.

<Operation mechanism and interface specification>
As an example of a method of realizing the SION 21, a mounting method using a distributed object technology will be described. Here, SI-SW,
SI-R and SI-GW are an event place object (EPO), a shared link object (SLO), and a federation agent (FA), respectively.
It is implemented as a distributed object called. FIG.
The operation mechanism and control interface of the SION1 will be described in detail with reference to FIG. Also, SION-MT (Manag)
By using an element tool or a SION interfacer, the network interface of the SION 1 can be used. Also, using MT, E
Withdrawal / increase / decrease PO, dynamic change of physical link information, PO
Migration (dynamic change of the EPO to which the PO is bound), collection of the firing rate, and collection of statistical information of popular coastal information and popular information can be easily performed.

Startup and Initialization of Event Place Factory ((1) in FIG. 21) First, the SION operator starts an event place factory (EPF) on an arbitrary host, and subsequently, the EPF
Is initialized. At this time, a host name capable of generating an event place (EP) and a storage location of an executable file of the EP are given to the EPF. These are called EP generation information.

Request for Event Place Generation ((2) in FIG. 21) Next, the EP operator requests the EPF to generate an EP. At this time, an EP name and an EP attribute are given.
Here, the EP attribute indicates whether the generated EP is used for a purpose-built model or an inquiry model, and indicates the direction of the flow of the event.

Generation of Event Place ((3) in FIG. 21) Next, the EPF that has received the EP generation request generates an EP. Specifically, at this time, an event place management object (EPMO) that manages the EP is generated. That is, the processing request to the EP is EPMO
This is the same as the processing request to. The EPF returns the identifier of the generated EP (that is, EPMO) to the generation request source. The EPMO is generated for a dynamically determined host from among the hosts capable of generating an EP specified in (1) of FIG. As a method of determining the host to which the EPMO is activated, a method of cyclically determining the activation destination, deciding according to the traffic, or explicitly specifying the activation destination host can be selected.

An event place initialization request (FIG. 21)
(4)) Next, the EP operator requests the EPMO to initialize the EP. At this time, a single event place object or a multiple event place object is designated. When a multiple event place object is specified, it is necessary to provide physical link information (topology) of the event place object (EPO) together. Here, the physical link information of the EPO expresses which other EPO knows which other EPO exists.

For example, as shown in FIG.
42 is EPO1 · 41, EPO3 · 43, EPO4 ·
I know the existence of EPO44, but EPO3 • 43 is EPO2
・ It expresses that only the existence of 42 is known. As described above, the multiple EPO aims at improving the scalability by distributing the load of the event matching process in the EP.

The EPMO is executed by selecting an EP from a host list capable of generating an EP specified in (1) of FIG.
The host that generates O is dynamically determined, and EPO is generated there. At this time, each EPO is always accompanied by one filter factory (FF) and one statistical information collection object (SO), and these are generated by the SI-S
W. Further, a shared link object (SLO) is generated accompanying each EPO according to the number of physical links. For example, three SLOs are generated for EPO2 · 32 (SLO2,1, SLO2,3, SLO in the figure).
These correspond to SI-R). The method of determining the activation destination of EPO is the same as that of EPMO, but it is also possible to fix the EPO to be used for each event type. The EPMO generates an event type factory (ETF) in the EP. EP
Within, a unified event type namespace is guaranteed by the ETF.

Request for Session Establishment for Event Transmission to Event Place ((5) in FIG. 21) Next, a request is made to the EP to establish a session. EPMO
Is a proxy object (PO) for each session request
Generate The session identifier, which is the identifier of the PO, is returned to the request source.

It should be noted that the EPMO uses the PO
Is instructed which EPO to use (to bind with which EPO). This instruction is for multiple EPO
However, the method of determining the EPO to be bound is the same as that of the EPMO. When a session establishment request is made to the EP, it is necessary to specify whether the session is a session for event transmission or a session for event reception. In this example, a session for event transmission is specified.

Registration of Event Type ((6) in FIG. 21) Next, the PO is requested to register the event type. At this time, the PO requests the ETF to generate an event type object (ETO). Further, the event type is stored in the generated ETO. On the other hand, an event type registration can be requested from the EP. At this time,
EPMO requests the ETF to generate an ETO, and stores the event type in the generated ETO. Generally, an event sender registers an event type via a PO. On the other hand, the EP operator registers an event type in the EP. Note that registering an event type with the same name will result in an error.

Request for Establishing a Session for Event Reception for Event Place ((7) in FIG. 21) Next, a request is made to the EP to establish a session for receiving an event. At this time, the requester of the session establishment (event receiving object) sets the identifier of the event receiving object, which is the event notification destination, and the event notification method (firing type, look-in type) as parameters. Give as.

Subsequently, the EPMO generates a PO for each session request. The session identifier is returned to the request source. The EPMO instructs the PO to use the EPO when the PO is generated. This instruction is required in multiple EPO, but the method of determining the EPO to be bound is the same as that of EPMO.

Request for generation of filter object (FIG. 2)
1 (8)) Next, the PO is requested to generate a filter object (FO). At this time, the PO requests the FF to generate the FO. At this time, the FF attached to the EPO bound to the PO is used. The identifier of the generated FO is returned to the FO generation request source via the PO.

Setting of filter value ((9) in FIG. 21) Next, the PO is requested to set a filter value in the FO using the FO identifier as a parameter. Note that the event type name stored in the filter object (that is, the event type name to be filtered)
It is possible to selectively request the ETO to check whether the data structure (filter value) of the FO is correct, using the key as a key. If it is not correct, an error. However, when a wild card is specified, this check processing is not performed at all.

Filter Registration ((10) in FIG. 21) Next, after setting a filter value in the FO, the filter registration is requested to the PO using the filter identifier of the F as a parameter. At this time, the filter identifier is returned to the registration request source. With this as a trigger, it becomes possible to receive events. Note that a plurality of filters can be registered through one PO. (For this, a plurality of different FOs are registered as filters through one PO, or the same FO is registered as a filter a plurality of times. However, all filters registered for one PO have an “OR relationship”.

Event transmission ((A) in FIG. 21) Next, the event sender transmits an event to the PO. At this time, the PO can selectively request the ETO to check whether the data structure of the event is correct, using the event type name stored in the event as a key. When this check process is selected, if it is correct, the process proceeds to the next process ((B) in FIG. 27). If it is not correct, an error occurs.

Event collation request (B in FIG. 21) Next, the PO transfers the event to the EPO. At this time,
EPO creates a thread. Note that a thread is generated for each event, and each thread performs multiplex processing of the event.

Collation with Filter (FIG. 21C) Next, the thread (EPO) performs a filtering process by collating the event with the filter. These include exact, partial, and weighted matches,
Can be specified when setting the filter value.

Activation of Proxy Object ((D) in FIG. 21) Next, when an event passes through the filter as a result of comparison with the filter, the corresponding PO is activated and receives this event. At this time, the PO can selectively register the received event type, value, event ID, and the like in the SO. From this information, the SO can measure the firing rate of the event (for each event type and each event) and the highly reputed events that are prevalent in the EP.

Activation of event reception object (FIG. 2)
1 (E)) Next, the PO activates the event receiving object and passes the event to the event receiving object. This corresponds to the firing type (interrupt type) event notification.

Look-in type event notification (FIG. 21F) On the other hand, instead of the PO activating the event receiving object, the event receiving object itself is spooled in the PO corresponding to the event receiving object. Can be taken out. This corresponds to a look-in type event notification. There are various triggers for activating the event receiving object depending on the service form. As a typical example, a case in which an end user makes a content proposal request to the event receiving object is considered.

<Filter Management Method> Next, a filter management method in each EPO will be described.

First, a session for receiving an event is established. At this time, one PO is generated for each session request, and this PO is bound to any one EPO. Each EPO is accompanied by one FF. As a result, the EPO used by the PO is uniquely determined, and all subsequent processing is performed via the PO (event receiving session).

Next, an FO is generated, and a filter value (a type of an event to be received and an acquisition condition thereof) is set for the FO. Subsequently, a filter is registered using the FO identifier as a parameter. At this time, the FO identifier is stored in each filter. Each EPO manages the filters registered via the PO based on the following rules.

First, using the FO identifier stored in the filter, the “type of event to be received” set in the FO is referred to. Subsequently, the filters are classified for each type of event to be received, and the filters classified for each event type are further classified and managed for each PO.

Referring to FIG. 23 for this management rule,
A case where a filter is registered via PO1 will be described. Here, it is assumed that “event type X” is set as the type of the event to be received in the FO specified at the time of filter registration. At this time, EPO
Corresponds to the filter 1 in FIG. 23, and similarly, the filter registered via PO2 corresponds to the filter 2. In each PO, a plurality of filters can be registered. However, the registered filters have an “OR relationship”.

First, the event of the event type X is EP
When it arrives at O, matching with filter 1 is performed. As a result, when the filter 1 fires, the PO1 is activated.
Next, matching with filter 2 is performed, and as a result, when filter 2 fires, PO2 is activated. At this time, since the filters 2 and 3 have an “OR relationship”, the matching with the filter 3 is not performed. By using such a filter management method, each E for one event
The number of times of the collation processing at the PO can be basically made equal to or less than the number of POs (the number of reception sessions).

<Event Routing Method> Next, an event routing method will be described.

The EPO (SI-SW) accommodates event senders and receivers (entities such as terminals) in a star format via a session. Furthermore, EPO (SI-SW)
Matches the filter registered by the event receiver (event receiving object) with the event sent by the event sender, and as a result, notifies the event only to the event receiver corresponding to the fired filter (matching event reception (Delivery of the event only to the person).

Therefore, as the number of event senders (the number of events) and the number of event receivers (the number of filters) increase, the processing capability of the EPO becomes saturated in proportion thereto. Therefore, the SION architecture provides a multiple EPO as a means for realizing an EP with high scalability. Multiple EPO refers to the number of EPOs
The purpose of the present invention is to achieve a high scalability of EP from the following two viewpoints.

The first point is load distribution and autonomous distribution. This is to distribute the load of event filtering processing by distributing event senders and receivers to a plurality of EPOs, so as to prevent a bottleneck factor accompanying processing concentration. . Further, each EPO achieves distributed coordination by a mechanism that can operate autonomously without being affected by other EPOs.

The second point is reduction of network traffic and optimization of the filtering process. This is EP
This is to minimize the amount of communication by not transferring unnecessary events between Os, and to reduce unnecessary filtering processing.

In FIG. 22, for EPO3 · 43,
It is assumed that a filter of event type X is registered as a type of an event to be received. Here, when an event of the event type X is sent to EPO4 · 44, this event via EPO2 · 42 EPO3
-It is necessary to transfer to 43. At this time, the event must not be transferred to the EPO1 · 41 in which the filter of the event type X is not registered. What controls such event routing between EPOs is a shared link object (SLO),
This corresponds to SI-R described above.

Hereinafter, the SI-R will be described in detail.

First, at the time of initializing an EP, an SLO is generated in association with each EPO based on physical link information (EPO topology). For example, in FIG.
Three SLOs are generated for two. These correspond to SLO2,1, SLO2,3, SLO2,4 in the figure. This SLOi, j establishes a shared link (SLi, j) for transferring events from EPOj to EPOj. That is, as shown in FIGS. 22 and 24, SLOi, j is
Establish an event reception session for EPOj,
On the other hand, by establishing an event transmission session with EPOi, a shared link SLi, j, which is a logical link for event transfer, is established. Establishment, not including the filter registration process).

After the initialization of the EP, the event receiver sets the E
It is possible to establish a session to P and register a filter via the session. At this time, an event path is set according to the established shared link. For example, in FIG. 24, the event receiver (Event
When the receiver 3 registers a filter for performing event type X event reception in the EPO 3 via the PO 3, the PO 3 registers the event type X filter in the EPO 3 and notifies the SLO 3, j ( Here, SLO3,2) is notified, and SLO3,2 is SL3,2.
Is used to register a filter of event type X for EPO2. This is performed via the PO of the receiving session assigned to SLO3,2, as described above. Similarly, this PO indicates to that effect that SLO2,3
Is notified to other SLO2, j except for. SLO2, j
(J ≠ 3) registers the filter in EPO using SL2, j. The process is repeated in the same manner until all EPOs are set to the path for the event X.

A series of paths established for the event type X is called an event path. this is,
The filter registration via PO3 is a trigger, and the event path setting request for each event type sequentially and autonomously propagates to all EPOs. That is,
Each EPO needs to recognize only the adjacent EPO.
For this reason, it is possible to establish the event path with a simple and unified autonomous logic as compared with the event path setting / management method by centralized management and broadcast of the event path.

FIG. 25 shows the filter registration status in EPO1 at this time. As a result of the event receiver 3 registering the filter via PO3, filter 1 becomes EPO1.
Will be registered. Setting an event path refers to registering a filter for event transfer in a series of EPOs based on shared link information. Also,
In the filter registered by the SLO, only the event type name to be received is set, and the acquisition condition is not set.
Filter only the event type name.

In this situation, the event receiver 2 receives the P
Via O2, filter the event type X to EPO
When the event path is registered in EPO2, the setting of the new event path spreads to all EPOs as described above. As a result, the filter 2 is registered in EPO1, and the filter is registered every time an event path setting request is made. Will be done.

At this time, when an event of event type X is sent to EPO1, filter 1 fires and SLO
2,1 is activated. SLO2,1 reports this event as EPO
SLO3,2 is activated by sending to SLO2. Further, the event is transferred to EPO3 via SLO3,2. To prevent infinite transfer of events between SL2,3 and SL3,2, the event is
As one of the control information, a maximum of two identifiers of the passed EPO are stored in the latest order.

As described above, since the filter 1 and the filter 2 have an OR relationship, if the filter 1 fires, the filter 1 and the filter 2 are not collated. Therefore, it is possible to prevent the redundant overhead of the filtering process from being generated at all even when the filter 1 is newly registered even though the filter 1 exists. This means that when an event path is set, there is no need to rebuild all event paths including the existing event path, and a simple and unified event path autonomous setting becomes possible. .

If there is a session established by the event receiver in EPO 1 and a filter registration via the session (corresponding to the filter 3 of POn), after all the filtering processes corresponding to SLO are completed, Is performed. That is, the event transfer processing to another EPO is performed with priority, and then,
The collation processing in own EPO is started.

As a further effect of the event routing method described above, there is no need to reconstruct an event path when canceling filter registration. For example, when the event receiver 3 cancels the registration of the registered filter via the PO 3, the cancellation request sequentially and autonomously spreads, similarly to the case of the registration. As a result, in EPO1,
Only the registration of the filter 1 will be cancelled, but the filter 2 survives (hereinafter, the filter 2 forwards the event instead of the filter 1). Event path consistency is guaranteed.

By using such an autonomous decentralized routing control method, it is possible to easily realize interconnection and distributed coordination of EPO. Accordingly, a transition from a small network to a large network, a transition from a local network to a global network, and the like can be smoothly performed. Also,
Global networking with a bottom-up approach can be easily achieved with common logic.

FIGS. 26 to 29 are diagrams for explaining the SI-R in the physical link having the ring type coupling.

For example, as shown in FIG. 27, in a physical link having a ring-type connection, EPO2 is EPO1,
It expresses that you know the existence of EPO3. As described above, the multiple EPO aims at improving the scalability by distributing the load of the event matching process in the EP.

The EPMO is executed by selecting an EP from the host list capable of generating an EP specified in (1) of FIG.
The host that generates O is dynamically determined, and EPO is generated there. At this time, each EPO is always accompanied by one filter factory (FF) and one statistical information collection object (SO), and these are generated by the SI-S
W. Further, one shared link object (SLO) is generated for each EPO according to the physical link. For example, SLO2 and SLO3 in the figure are generated for EPO2. This corresponds to SI-R. The method of determining the activation destination of EPO is the same as that of EPMO, but it is also possible to fix the EPO used for each event type. Note that the EPMO generates an event type factory (ETF) in the EP. E
Within P, a unified event type namespace is guaranteed by the ETF.

Hereinafter, the SI-R will be described in detail.

First, at the time of EP initialization, an SLO is generated accompanying each EPO based on physical link information (EPO topology). For example, in FIG.
SLO2,3 is generated for O2. This SLOi, j
Establishes a shared link (SLi, j) for transferring events from EPOj to EPOi. That is, FIG.
29, SLOi, j establishes an event reception session with EPOj, while
By establishing an event transmission session for i, a shared link SLi, j, which is a logical link for event transfer, is established.
This means that the session is established by the SLO when the EP is initialized, and does not include the filter registration process.) As a result, a unidirectional ring-shaped shared link SLi, j is established.

After the initialization of the EP, the event receiver sets the E
It is possible to establish a session to P and register a filter via the session. At this time, an event path is set according to the established shared link. For example, in FIG. 28, the event receiver (Event
It is assumed that the Receiver 3 registers a filter for receiving an event of the event type X via the PO 3 in the EPO 3. At this time, the PO3 registers the event type X filter in the EPO3 and notifies the SLO to that effect.
Notify 3,1. At this time, SLO3,1 is given as a parameter that the source of the filter registration request is EPO3. SLO3,1 uses SL3,1 to register an event type X filter for EPO1. This is performed via the PO of the receiving session assigned to SLO3,1, as described above. Similarly,
This PO notifies the SLOs 1 and 2 of that fact.
SLO1,2 registers a filter in EPO2 using SL1,2. The process is repeated in the same manner until all EPOs are set to the path for the event X. Note that this processing is performed by a filter registration request source (here, EP
This is repeated until immediately before O3). That is, SLO2,3
Does not register the filter in EPO3.

FIG. 29 shows the filter registration status in EPO1 at this time. As a result of the event receiver 3 registering the filter via PO3, filter 1 becomes EPO1.
Will be registered. Setting an event path refers to registering a filter for event transfer in a series of EPOs based on shared link information. In addition,
In the filter registered by the SLO, only the event type name to be received is set, and the acquisition condition is not set.
Filter only the event type name.

In this situation, the event receiver 2 has a P
Via O2, filter the event type X to EPO
When the event path is registered in EPO2, the setting of the new event path spreads to all EPOs as described above. As a result, the filter 2 is registered in EPO1, and the filter is registered every time an event path setting request is made. Will be done.

At this time, when an event of event type X is sent to EPO1, filter 1 fires and SLO
3,1 is activated. SLO3,1 reports the event as EPO
SLO2,3 is activated by sending to SLO3. Further, the event is transferred to EPO2 via SLO2,3. In order to prevent the event from going infinitely, the event is one of the control information.
The identifier of the EPO in which the event has occurred is held, and when the event circulates and returns to the event-originating EPO (SLO), the event is discarded.

Next, an event routing method different from the above-described event routing method will be described. This routing method uses shared links (logical links).
Are established in the same manner as in the method described above.
This event routing method differs from the method described above in that no event path is established, and SLOi, j
At the same time as establishing the shared link SLi, j. At this time, a wild card is specified as a type of an event to be received in the registered filter. As a result, all events are set as transfer targets, and an event path for each event type is not established.

By specifying a wild card in the semantic information as described above, the ring-shaped shared link SL
Since the event circulates in i and j, the event can be delivered to all EPOs.

<Federation Method> Next, the federation method will be described with reference to FIG. The federation agent (FA) is an agent that establishes a federation between event places, and corresponds to the above-described SI-GW. For example, an event place (Event Place) A is an event place (Event Place)
Place) A case where a federation is established for B is considered. First, an FA belonging to event place A registers a filter for event place B. At this time, the event sender belonging to the event place B sends an event, and as a result, when this filter fires, the FA autonomously starts. This can regard the FA as one event recipient belonging to event place B. Next, the FA retransmits the acquired event to the event place A to which the FA belongs. this is,
FA can be considered as one event sender belonging to event place A.

As described above, the Federation between event places can be easily realized by using the FA having both roles. That is, it is possible to realize the federation between the event places with the same control logic as that of the single event place. Using this mechanism,
By interconnecting the event places, which are one basic configuration unit, a global collation network can be constructed by a bottom-up approach, and sharing of events across event places can be realized. Note that event place A and event place B
Have different ontologies, the FA belonging to the event place A converts the event acquired from the event place B into the ontology of the event place A, and then sends the event to the event place A.

When event transfer is performed across different ontology systems, ontology conversion is required.
As a conventional technique for performing this conversion, when a standard ontology is defined and an event is transferred to another event place, a method of transferring the event after temporarily converting the event to a format conforming to the standard ontology, and a method of transferring the event There are methods such as preparing an ontology conversion table for the number of combinations in advance.

However, in order to cope with dynamic federation of event places (dynamic start and release of federation), the conventional method lacks flexibility. Therefore, in the present invention, as shown in FIG.
Holds only the difference (conversion information) from the ontology information of the adjacent event place in the ontology conversion table. In other words, this is a method in which each FA stores the conversion information in a distributed manner, and assures the consistency of the ontology system as a whole. This makes it possible to easily cope with dynamic federation between event places, but on the other hand, every time an event crosses an event place, an ontology conversion process occurs. It has the feature that processing overhead increases.

<Community and Evolved Network> Next, a community service, which is one of the killer services of SION1, will be described. An entity in a community service is an autonomous decentralized operation entity that can dynamically determine an activity mode by repeating learning, evolution, degeneration, and disappearance based on its own policy. Communities provide an efficient forum for such entities to communicate. In other words, entities in the community dynamically search for and identify entities that should communicate with themselves or that affect their behavior.
It is possible to discover / specify and interact with the specified entity.

This community can handle entities having the following characteristics in particular.

(1) An extremely large number of entities are present in a community with an extremely small granularity (an unspecified number of entities).

(2) The attribute of the entity changes in real time. Typical entity attributes include location information, time, and the like.

(3) The behavior of the entities in the community is not regular, and it is difficult to predict the behavior.

(4) Participation in the community, departure from the community, disappearance, duplication, etc. occur frequently and irregularly.

(5) The entities in the community are:
It is necessary to meet each other in real time based on policies, attributes, scenarios, and the like.

It is not easy in terms of performance to manage entities having such characteristics by a server or a mediator (broker) and to search and discover each other in real time. S
The ION1 EP is positioned as an execution environment of a community having such characteristics. That is, the community is a meta execution environment of the EP, and provides a place of communication with a higher level of abstraction than directly using the EP. By using the EP in the execution environment of the community, all the entities in the community can directly find the entity to communicate with without going through the broker. This is because communication of entities in the community is implemented as sending and receiving events in the EP.

FIG. 31 shows a conceptual model of a community. A user agent (UA) and an information and service providing agent (ISA) correspond to entities in a community. The UA is an agent that behaves autonomously as a user's agent.
It dynamically determines its own behavior according to location information, situation, tendency, etc., and interacts with ISAs and other U
Search for A and interact with them. An ISA is an agent that acts autonomously as an agent of an information provider or a service provider.
Search for UAs and other ISAs to interact with.
That is, a user suitable for providing his / her information is searched for and specified.

On the other hand, the community agent (Com
A) is an agent that manages the community. The EP operator sets the SION-
Controls and operates the SION via MT. Therefore, C
The omA can be considered as an agent of the EP operator. Basically, the operational policy of the community is defined by ComA. For example, UA, ISA
Authorization, such as joining, leaving, extinction, duplication, etc. to the community for such entities, understanding and controlling the information distributed within the community (such as deleting unsuitable events), statistical information within the community (trend information, reputable information Etc.) based on their own management policies.

Further, in order to achieve the guarantee of high scalability and reliability of the community, SION control such as increase / decrease, withdrawal, and migration of EPs and EPOs is executed according to the load condition and the failure condition. That is, by combining the ION 21 and the ComA, the ION 21 evolves from an autonomous decentralized network to an evolved network capable of learning, growing, and evolving. In this way, the ComA controls the behavior of the entities in the community and plays a role in self-organizing SION1. Further, the collaboration between the communities enables the sharing of information between the communities. For example, among the information distributed in community A, only the top 10 most popular
It can be distributed to the community B. The processing flow is shown below.

First, the ComA of the community B instructs the FA of the event place B to “distribute only the top 10 most popular information among the information distributed in the community A to the community B”. I do.

Next, the FA inquires of the event place A about the top ten event types. In response to this, the event place A inquires the subordinate statistical information collection object (SO) and sends the result to the FA.
Return to.

Next, the FA creates an ontology conversion table based on the acquired event type, and sets a filter for the event place A. Hereafter, F
A can receive the event from the event place A.

Next, the FA converts the event obtained from the event place A into an ontology based on the ontology conversion table, and sends the event to the event place B.

According to the embodiment described above, the following two effects can be obtained.

First, an SIO on the distributed object environment
N network environments can be easily constructed.

Second, by allowing the service application to participate in the community as an entity,
It is possible to easily send out an event or to pick up a necessary event, so that mutual communication can be achieved.

As described above, the following effects can be obtained with the SION.

An event distributed only in another event place can be taken into its own event place by a federation mechanism between event places via the FA. Conversely, by sending an event to another event place, it is possible to advertise the event distributed in the own event place. in this way,
Events can be shared between different event places, and interoperability between event places taking into account the ontology makes it possible to construct a global autonomous decentralized collation network based on a bottom-up approach.

The multiple EPO mechanism makes it possible to distribute the load of the filtering process to a plurality of EPOs, and the event routing mechanism between EPOs that operates autonomously makes it possible to minimize network traffic. Become. This results in E
The total throughput of P can be scalably improved.

It becomes possible to directly search for and find an entity suitable for itself without going through a broker. For example, an information provider can specify a user who is suitable for the information provided by himself without knowing the existence of the user. Similarly, the user can search for and find an information provider suitable for his / her taste without knowing the existence of the information provider. That is, the user and the information provider are equivalent to each other. As a result, information can be transmitted in real time according to the own policy without relying on a specific broker. Further, when the number of entities to be searched is enormous or when the entities frequently enter and leave the search target domain, the search technique based on the non-broker model is particularly effective.

In the SION, the end point of the semantic information is a network. On the other hand, in a method of performing a peer-to-peer connection between terminals, the terminal of the semantic information is the terminal, so that the contents of the terminal are disclosed to the outside. Therefore, SION can realize higher security and privacy protection than the latter method.

[0112]

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a configuration diagram of an electronic library service system according to an embodiment of the present invention.

The electronic library service system according to the present embodiment comprises a book user terminal 1 and book provider terminals 2 ₁ , 2 ₂ , 2.
₃ and a semantic information network 3.

The book user application 1 is installed in the book user terminal 1, and the book provider terminal 2 is installed.
₁ , 2 ₂ , and 2 ₃ include the book providing application 5 ₁ ,
5 _2, 5 ₃ are installed, respectively. Each terminal _{1,2 1 ~2 3 CORBA (CommonObject Resource} Br
oken Architecture) compliant ORB (Object Resource B)
roken) Install the middleware and event place factory generation mechanism to create an event place on its own terminal and use it, or access an event place on another network system to establish a session, etc. And is connected to the semantic information network 3.

Next, the operation of the present embodiment will be described with respect to “cold”.
An example of searching for a book to be executed will be described. (1) Books and miscellaneous books generally handled by libraries for users
Book provider B who is a book provider such as a magazine₁, Book provider
B_Two, Book Provider B_ThreeIs a book providing application.
Option 5₁, 5_Two, 5_ThreeUsing the application shown in Fig. 2.
Screen displays the identification information, usage conditions,
The guide information and the access to the book if it has been digitized.
Information, or if it cannot be digitized, contact information
Report as book acquisition information, and accept a book use request.
Start. As an example, book provider B ₁Is an electronic book "Kaze
"Prevention of Evil" by Book Provider B_TwoIs a non-limited area
Electronic book "How to cure a cold", book provider B_ThreeIs electronic
Let's assume that you have set up each of the chemical books "The mechanism of colds". Figure
The input content of 2 is book provider B_TwoShows an example of what was entered
It is. Here, the book guidance information "Here"
Is Book Provider B_TwoOwned by itself or another book provider
A book that associates information for requesting related books.
Supports dynamic and timely search support function for users
Is what you do. At this time, the book providing application
5_TwoIs the event place as shown in FIG.
Event type and register a session for event reception.
Once established, a filter object is created and this
Set filter values as shown in Fig. 6 in the filter object
I do. The input contents in FIG._TwoBooks
Provision application 5_TwoShows an example of the setting
is there. (2) The book user A uses the book on his terminal 1
Using the application program 4 for
From the application screen on a simple terminal, for example, "cold"
Information about wanting to find the best home
Power. At this time, for the use of books used by book user A
The application program 4 includes an event as shown in FIG.
Generate event and send to event place. Where the house
The location information is provided by the book user A on another occasion.
Application 4

In the event place, the event is compared with each filter, and the event is transferred to the terminal of the book provider who has set a filter whose content matches the condition indicated by the filter value. An event place where a library providing application 5 ₁ to 5 ₃ are used, between events places the library available for application 4 is used, the federation function event place, since it is possible to cross-flow of information, the event certain The event is finally transferred to the event place used by the target book providing application via the event place. In the figure, among the unspecified number of book providers, finally, the book provider B ₁ , the book provider B ₂ , and the book provider B ₃ receive the event. (3) At the book provider terminal that has received the book use request event, the book providing application uses the book use request information included in the event to display the book guide that the book provider has already entered in FIG. Information and book acquisition information,
The book guide information and the book acquisition information are returned to the book user A based on the reply destination information during the event. (4) books available for application 4, a predetermined period has the reply information, the information received during that period (reply from book provider B ₁ and book provider B ₂ and book provider B ₃₎ Is displayed on the display of the terminal 1, and the book user A confirms the requested book guidance information on a screen as shown in FIG. 4, decides the book to be used, and selects the book on the screen if it is an electronic book. If it is a non-electronic book, a separate use request is made based on the contact information. As a result, the person who wants to use the book can use the book from the unspecified number of people who want to provide the book to the specific book provider related to the book he wants to use, but without recognizing the book provider. Requests can be transmitted in real time, and the results can be received to know the guide information and acquisition information of books.

Next, a method of specifying a search keyword or the like in a book search request according to the present embodiment will be described.

FIG. 8 shows an event type for using the events of FIGS. 9 and 10 and the filter of FIG. In this example, an event for searching for book information is shown. FIG. 9 shows an example of an event in a case where a search is performed using a “book name” that uniquely determines a book. On the other hand, FIG.
As shown in (1), a method of detecting a book by a keyword related to the contents of the book is also possible. In this case, since a large number of books may be detected with one keyword, a plurality of words are set in the property “keyword” to narrow down the search in more detail, and the keyword value is obtained by combining the words with “|”. The setting of AND connection between them can be performed.
A filter as shown in FIG. 11 corresponds to a search condition of an AND combination as shown in this event. It is possible to determine whether the property value satisfies the condition by comparing the number of keywords specified as a property value by the keyword search and the information searcher with the number of matching keywords. When setting the conditions of the OR combination, it is only necessary to use "|" between a plurality of search keyword values. Alternatively, it can be realized by sending an event a plurality of times.

[0120]

As described above, according to the present invention, the real-time property of the book use request and the response is improved, the costs related to the mediation are eliminated, and the load is not concentrated on the mediator. -An unspecified number of book providers and book users can send and receive book information without knowing the existence of intermediaries (eliminating procedures for accessing books in other places). The book provider can provide the latest books directly or by using search support functions such as hypertext search to enable timely provision of books. This has the effect of improving the security of the privacy and confidential information of the provider.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of an electronic library service system according to an embodiment of the present invention.

FIG. 2 is a book provider terminal 2 when a book provider B _{1 to} B ₃ starts accepting a book use request from a book user A;
It is a diagram showing an application screen in ₂₁ to _3.

FIG. 3 is a diagram showing an application screen on the book user terminal 1 when a book use request is transmitted from the book user A.

FIG. 4 is a diagram showing an application screen on the book user terminal 1 when a book to be used by the book user A is determined.

FIG. 5 is a diagram showing an example of an event type defined in the semantic information network 3 for transmitting and receiving book information.

FIG. 6 is a diagram showing an example of a filter condition set in the semantic information network 3 in order for the book providers B _{1 to} B ₃ to accept a book use request.

FIG. 7: A book user A sends a book use request to a book provider B ₁
For transmission to .about.B _3, a diagram illustrating an example of an event of transmitting the semantic information network 3.

FIG. 8 is a diagram showing an example of an event type for transmitting and receiving an event for searching for book information.

FIG. 9 is a diagram showing an example of an event (an event for searching for book information by book name) transmitted from the book use application 4 to the semantic information network 3.

FIG. 10 is a diagram showing an example of an event (an event for searching for book information with a keyword related to contents) transmitted from the book use application 4 to the semantic information network 3;

[11] Filter books provide application 5 ₁ to 5 ₃ are set to the semantic information network 3 (Books provider etc., a filter for receiving a search event book information) is a diagram showing an example of a.

FIG. 12 is a configuration diagram of a conventional electronic library service system.

FIG. 13 is a diagram showing a conceptual model of a semantic information network.

FIG. 14 is an explanatory diagram showing a configuration of an event.

FIG. 15 is a diagram showing a model of a semantic information network.

FIG. 16 is an explanatory diagram showing the definition of semantic information.

FIG. 17 is an explanatory diagram showing a definition example of an event type.

FIG. 18 is an explanatory diagram illustrating an example of an event.

FIG. 19 is an explanatory diagram illustrating a definition example of a filter.

FIG. 20 is a diagram showing a configuration of a semantic information network.

FIG. 21 is an explanatory diagram showing an operation mechanism and a control interface of the semantic information network.

FIG. 22 is an explanatory diagram showing physical links.

FIG. 23 is an explanatory diagram showing a filter management method.

FIG. 24 is an explanatory diagram showing an event routing method.

FIG. 25 is an explanatory diagram showing a registration state of a filter.

FIG. 26 is an explanatory diagram showing an operation mechanism and a control interface of the semantic information network.

FIG. 27 is an explanatory diagram showing physical links.

FIG. 28 is an explanatory diagram showing an event routing method.

FIG. 29 is an explanatory diagram showing a registration state of a filter.

FIG. 30 is an explanatory diagram showing a federation method.

FIG. 31 is an explanatory diagram showing a community model.

[Explanation of symbols]

1 library user terminal 2 ₁ to 2 ₃ book provider terminal 3 semantic information network 4 books available for application 5 ₁ to 5 ₃ for a library providing application 11 library user side terminal 12 _1, 12 _2, 12 _3, 12 ₄ Book provider's terminal 13 ₁ , 13 ₂ Digital library 14 ₁ , 14 ₂ Network 15 Book use application 16 ₁ , 16 ₂ , 16 ₃ , 16 ₄ Book supply application 17 ₁ , 17 ₂ Digital library application A Book User B _{1 to} B ₄ Book provider C ₁ , C ₂ Digital library operator 21 Semantic information network (SION) 22 Terminal SI-SW Semantic information switch SI-R Semantic information router SI-GW Semantic information gateway EPO Event place object SLO Shared Link Object FA Federation Age Cement

 ──────────────────────────────────────────────────続 き Continued on front page (72) Inventor Takanari Hoshiai 2-3-1 Otemachi, Chiyoda-ku, Tokyo Within Nippon Telegraph and Telephone Corporation (72) Inventor Takamichi Sakai 2-3-3, Otemachi, Chiyoda-ku, Tokyo No. 1 Inside Nippon Telegraph and Telephone Corporation (72) Keiichi Koyanagi, the inventor 2-3-1 Otemachi, Chiyoda-ku, Tokyo Nippon Telegraph and Telephone Corporation (72) Keiji Kanesugi, Nakahara-ku, Kawasaki City, Kanagawa Prefecture 4-1-1 Odanaka F-term in Fujitsu Limited (Reference) 5B075 KK07 ND20 NK44 PR08 UU11 UU40

Claims (6)

[Claims] At least one book usage request from at least one book user terminal is transmitted via a network.
An electronic library service method for transmitting to a library provider terminal, and the provider terminal returning, as a response to the use request, book guide information indicating the contents of the book to the library user terminal via the network Connecting the book providing application on the book provider side terminal and the book using application on the book user side terminal to the semantic information network which is the network, and providing the book to the book provider side terminal. Set the identification information and usage conditions of the book to be provided, input by the user, as a filter in the semantic information network, and input the desired book identification information and usage conditions input by the book user to the terminal of the book user. Is transmitted to the semantic information network as an event, and the book user included in the use request The book provider side terminal where the identification information and the use condition included in the filter of the input identification information and the use condition match with the use condition is the book guidance information, the digitized book access information, and the non-digitized book inquiry destination. Reply book acquisition information, which is information, to the book user side terminal. The book user side terminal receives the book guide information and the book acquisition information from the book provider side terminal and presents it to the book user. Electronic library service method. 2. A book guide that transmits a book use request from at least one book user side terminal to at least one book provider side terminal via a network, and indicates the contents of the book as a response to the use request. An electronic library service method for receiving information from the book provider side terminal, wherein a book use application on the book user side terminal is connected to a semantic information network which is the network, and the book user side terminal A use request input by the book user, including identification information and a use condition of a desired book, is transmitted to the semantic information network as an event, and the book user side terminal responds to the use request as the book provider side. Receives book guidance information, digitized book access information, and non-digitized book inquiry information that is book acquisition information from the terminal, An electronic library service method presented to book users. 3. The at least one book provider terminal includes:
A book use request from at least one book user side terminal is received via a network, and book guide information indicating the contents of the book is sent to the book user side terminal via the network as a response to the use request. An electronic library service method for transmitting, comprising: connecting a book providing application on the book provider side terminal to a semantic information network that is the network; and providing the book provider terminal input by the book provider. The identification information of the book to be used, the use condition is set as a filter in the semantic information network, and the identification information included in the use request, the identification information input by the book user and the identification information included in the use condition in the own filter are included. The book provider side terminal that matches the use condition is the book guide information, the digitized book access information, Electronic library services how to return the books to obtain information that is contact information in the book the user side terminal. 4. At least one book user terminal including a book using application, at least one book provider terminal including a book providing application, the book using application and the book providing application The book use application has a semantic information network for connecting the book use terminal, and the use request including the identification information and the use condition of the desired book input by the book user to the book user side terminal is used as the event. Processing for transmitting to the information network, book guidance information indicating the contents of the book as a response to the use request from the book provider side terminal, digitized book access information, and book acquisition information as non-digitized book inquiry information; Receiving and presenting to the book user, the book providing application , The input to the book provider side terminal by book provider, identification of books to provide a process of setting the semantic information network use conditions as a filter, included in the usage request,
When the identification information entered by the book user and the use condition match the identification information included in the own filter and the use condition, the book guide information and the book acquisition information are returned to the book user side terminal. Electronic library service system including processing. 5. A book utilization request wherein a book use request is transmitted to at least one book provider terminal via a network, and book guide information indicating the contents of the book is received from the book provider terminal in response to the request. A user terminal, a process of transmitting, as an event, a use request including identification information and a use condition of a desired book input by the book user from the book user terminal to the semantic information network that is the network. The book user terminal receives book guidance information, digitized book access information, and book acquisition information as non-digitized book contact information from the book provider side terminal in response to the use request, and uses the book. A book user terminal including a book use application connected to the semantic information network, including a process of presenting the book information to a user. 6. A book use request from at least one book user side terminal is received via a network, and book guide information indicating the contents of the book is received as a response to the use request via the network. A book provider side terminal to be transmitted to the user side terminal, wherein the identification information of the book to be provided, which is input by the book provider from the book provider side terminal, and a semantic information network, which is the network, using a use condition as a filter. When the identification information and the usage condition included in the filter match the identification information and the usage condition entered by the library user included in the usage request, the book guidance information and the digitization Including a process of inputting book access information and book acquisition information as non-electronic book inquiry destination information and returning it to the book user side terminal; Books provider side terminal having a library provided for applications connected to a semantic information network.