JP2000112802A - Transmitter and its transmitting method, receiver and its receiving method, and transmitter-receiver and its transmitting/receiving method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a directory service of good quality based on a lightweight directory access protocol(LDAP) to many clients. SOLUTION: When a directory entry in a data base 32 is updated, a transmitting side duplicate synchronization management module 33 files a subject for executing the updating by an LDAP data interchange format(LDIF) file and transmits the filed subject through a broadcasting network 4 capable of simultaneously broadcasting information. An event for informing of the updating of the directory entry in which acquisition information for acquiring the subject is arranged, is also transmitted through the network 4. A receiving side duplicate synchronization management module 41 receives the event and receives the subject based on the acquisition information included in the event. Further, the module 41 updates a data base 42 by using the subject.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a transmitting apparatus and a transmitting method, a receiving apparatus and a receiving method, and a transmitting / receiving apparatus and a transmitting / receiving method, and more particularly to a transmitting apparatus suitable for use in a directory service system for providing a directory service. The present invention relates to an apparatus and a transmission method, a reception apparatus and a reception method, and a transmission / reception apparatus and a transmission / reception method.

[0002]

2. Description of the Related Art With the spread of networks such as the Internet and intranets in recent years, many companies and universities have established a messaging infrastructure centered on electronic mail (so-called E-mail). Furthermore, up to the present, the situation is being rebuilt and expanded. In such a situation, management of an e-mail address has become a problem.

In recent years, not only e-mail addresses, but also profiles such as names of employees, students, users, and other names, such as names, extension numbers, mobile phone numbers, IP (Internet Protocol) addresses, Based on personal attributes such as security permissions, organization names, domain names,
A lot of information, including group attributes such as mailing lists, is expected to be integrated as a directory service.

[0004] That is, for example, an extension number book or the like on which the extension number of each department in a company is printed is distributed to employees after the printing, bookbinding and the like are completed. It is possible that a transfer is taking place. As described above, when a printed matter such as an extension number book is distributed, information may become obsolete before the distribution is made. For this reason, in recent years, it is not limited to extension numbers,
Provided online, recognizing that the quality (speed and accuracy) of an online directory service that can be applied to the management of all shared information, such as within a company, is directly reflected in the cost competitiveness of the company The need for a directory service is being called out.

[0005] Further, the directory service will be
It is expected that it will develop as a board environment for general public service navigation systems that store not only extension number management and other information management within the company but also attributes of all multimedia contents and services. At present, as a standard of the directory service, for example, X.100 500 and LDAP (Lightwei
ght Directory Access Protocol).

X. 500 is an ITU-T (Internationa
l Telecommunication Union-Telecommunication Standa
This is an international standard for directory services recommended by the rdization sector, and defines the concept of directories, the definition of hierarchical structures, services, and objects. For example, NetWare 4.x NDS (NetWare Directory
Service) 500.

X. 500 is a very versatile directory service protocol, but has a very heavy implementation, and its implementation costs (software scale, development costs, etc.) are high. For this reason, LDAP has been developed as a lightweight and simplified service protocol so that it can be easily used from a WWW (World Wide Web) browser on the Internet, electronic mail software, and the like. LDA
P is RFC (Request For Comments) 1777, RF
Specified in C1778.

[0008]

[0005] LDAP is a server /
It is configured with a client-type model and defines a request / response message transfer protocol between a server (directory server) that stores directory information and a client that accesses it.

[0009] By the way, when the size of directory information centrally managed by the directory server increases, access from clients concentrates there and the quality of service (especially, speed) deteriorates. Distributed management of information is performed.

In this case, an entry managed by a certain directory server (minimum management unit of directory information)
Will exist on one or more other directory servers. Therefore, when an entry of a certain directory server is updated (including a case where the entry is newly added, a case where the entry is deleted, and a case where the entry is changed), it is necessary to update the copy in another directory server. Then, in a plurality of directory servers managing the same entry, the update of the copy is synchronized (1) so that the contents of the same entry are not different.
When an entry managed by one directory server is updated, another directory server manages the entry.
Update the copy of the entry immediately).

At present, when directory servers (LDAP servers) adopting LDAP are distributed at multiple points, in order to update copies between them in a synchronized manner, X.400 is used. Although 500 frameworks are about to be applied, the use of a connection-oriented two-way network is presumed, so that scalability is expected to be limited.

[0012] The present invention has been made in view of such a situation, and provides a large number of clients with LDAP.
To provide a high-quality directory service.

[0013]

A transmitting apparatus according to the present invention transmits broadcast data via a broadcast network capable of simultaneous broadcast, and transmits update data to an LDAP (LightWave).
LDIF (LDAP for eight Directory Access Protocol)
Data transmission format (Data Interchange Format) file is provided.

According to the transmission method of the present invention, broadcast data is transmitted through a broadcast network capable of simultaneous broadcast, and update data is transmitted to an LDAP (Lightweight Directory).
Access Protocol (LDIF) for LDAP Data Interchange
Format) file and send it.

The receiving apparatus according to the present invention includes a receiving means for receiving broadcast data transmitted via a broadcast network capable of simultaneous broadcast, and an LDAP (Lightweight Directory) based on acquired information included in the broadcast data. Access Pro
tocol) LDIF (LDAP Data Interchange Format)
Acquiring means for acquiring update data in a file.

A receiving method according to the present invention receives broadcast data transmitted via a broadcast network capable of simultaneous broadcast, and performs LD based on acquired information included in the broadcast data.
L for Lightweight Directory Access Protocol (AP)
It is characterized by acquiring update data in a DIF (LDAP Data Interchange Format) file.

In the transmitting / receiving apparatus of the present invention, the transmitting apparatus transmits broadcast data via a broadcast network capable of simultaneous broadcast, and transmits update data to an LDAP (Lightwei
ghtDirectory Access Protocol) LDIF (LDAP Dat
a receiving unit for receiving broadcast data, and an LDA based on the acquisition information included in the broadcast data.
Acquisition means for acquiring the update data in the P LDIF file.

According to the transmission / reception method of the present invention, in a transmission device, broadcast data is transmitted via a broadcast network capable of simultaneous broadcast, and update data is transmitted to an LDAP.
(Lightweight Directory Access Protocol) LDI
An F (LDAP Data Interchange Format) file is transmitted, the receiving device receives the broadcast data, and, based on the acquisition information included in the broadcast data, the LDAP LDI
It is characterized in that update data in an F file is obtained.

In the transmitting apparatus according to the present invention, the transmitting means transmits the broadcast data via a broadcast network capable of simultaneous broadcast, and transmits the update data as an LDAP LDIF file. ing.

The transmission method of the present invention is characterized in that the broadcast data is transmitted via a broadcast network capable of simultaneous broadcast, and the update data is transmitted as an LDAP LDIF file.

In the receiving apparatus according to the present invention, the receiving means receives the broadcast data transmitted via a broadcast network capable of simultaneous broadcast, and the obtaining means performs the processing based on the obtained information included in the broadcast data. Thus, the update data in the LDAP LDIF file is obtained.

According to the receiving method of the present invention, broadcast data transmitted via a broadcast network capable of simultaneous broadcast is received, and based on the acquisition information included in the broadcast data, an LDAP LDIF file is created. Updated data is obtained.

In the transmitting / receiving apparatus according to the present invention, the transmitting means transmits the broadcast data via a broadcast network capable of simultaneous broadcast, and transmits the update data as an LDAP LDIF file. ing.
The receiving means receives the notification data, and the obtaining means obtains the LDI of LDAP based on the obtained information included in the notification data.
The update data in the F file is obtained.

In the transmission / reception method of the present invention, broadcast data is transmitted via a broadcast network capable of simultaneous broadcast, and update data is transmitted as an LDAP LDIF file, while broadcast data is received. , Based on the acquired information included in the broadcast data, the LDAP LDI
The update data in the F file is obtained.

[0025]

FIG. 1 shows a configuration example of a directory service system according to an embodiment of the present invention.

In this directory service system,
A directory service based on LDAP is provided.

That is, a plurality of LDAP client terminals (terminals functioning as LDAP clients) 1 receiving the provision of the directory service are, for example, PSTN (Pu
blicSwitched Telephone Network), ISDN (Inte
gdas Services Digital Network), the Internet, a CATV (Cable Television) network, etc.
It is connected to a P server (server functioning as an LDAP server) 2. The plurality of LDAP servers 2 manage directory information in a distributed manner.
Each of the client terminals 1 has a two-way network 3
, Any access to any of the plurality of LDAP servers 2 can basically provide the same directory information.

Each of the plurality of LDAP servers 2 communicates with the plurality of L-
In addition to being connected to the DAP client terminal 1, for example, they are connected to each other via a broadcast network 4 capable of simultaneous broadcasting such as terrestrial broadcasting and satellite communication. Here, the broadcast network 4 is a network capable of one-way communication from one of the plurality of LDAP servers 2 to another LDAP server. Multiple existing L
It is sufficient that the broadcast data can be broadcast to the DAP server 2. Therefore, as the broadcast network 4, for example, a bidirectional network such as a CATV network capable of broadcast can be adopted. It is possible.

Next, processing of the directory service system configured as described above will be described. Here, for simplicity of description, as shown in FIG. Paying attention to only two, the two LDAP client terminals are respectively referred to as the transmitting LDAP client terminal 11 and the receiving LD.
Called the AP client terminal 12. In addition, multiple LDs
Similarly, only two of the AP servers 2 are focused on, and the two LDAP servers are referred to as a transmitting LDAP server 21 and a receiving LDAP server 22, respectively.

In the directory service system configured as described above, as shown in FIG. 3, first, the sending LDAP client terminal 11 is managed by the sending LDAP server 12 via the bidirectional network 3. A request for updating the directory entry is made (1).

The transmitting-side LDAP server 21 includes an update processing unit 31 for updating directory entries and the like, a database 32 for storing directory entries,
-Side replication synchronization management module 33 (synchronization means) for performing synchronization management of directory and directory entry replication
(Transmission means) (detection means). Here, the transmission-side replication synchronization management module 33 is software, and is executed by a processor (not shown).

In the sending LDAP server 21, the sending L
The update processing unit 31 receives a request for updating the entry transmitted from the DAP client terminal 11. The update processing unit 31 sends the database 3
The second directory entry is updated (2). This update is detected by the transmission-side replication synchronization management module 33 (3).

When the transmission-side replication synchronization management module 33 detects an update of the directory entry, the transmission-side replication synchronization management module 33 stores data (update data) (hereinafter, appropriately referred to as a subject) for performing the update in an LDAP LDAP (LDAP Data Integer).
rchange Format) file. Here, as the subject, not only the directory entry itself after the update is used, but also, for example, a difference between the directory entry after the update and the directory entry before the update can be used.

Note that LDIF is used for applications and O
Directory information described in text for expressing directory information across various platforms of S (Operating System). LDIF includes:
There is a standard LDIF (format) and a modified LDIF (format). In the standard LDIF, an entry's identification name (DN (Distinguished Name)) and a combination of the entry's attribute name and attribute value are listed. on the other hand,
In the modified LDIF, information such as the type of the modified operation, the format corresponding to the modified operation, and which part of which entry is to be modified is listed. The LDIF file can be generated using a command line tool for the LDAP server (here, the sending LDAP server 21).

Here, regarding LDAP and LDIF,
For example, "LDAP Internet Directory Programming", Prentice Hall (hereinafter referred to as Reference 1 as appropriate)
) Are described in detail.

Further, the transmission-side replication synchronization management module 3
3 generates data (notification data) for notifying the update of the database 32 (directory entry) including acquisition information for acquiring the generated subject (hereinafter, appropriately referred to as an event). Where the subject is
As will be described later, since the subject is transmitted via the broadcast network 4, as the acquisition information for acquiring the subject, a broadcast channel of the subject, a broadcast start time, a broadcast time, and the like can be adopted.

When the transmitting-side copy synchronization management module 33 generates (configures) a subject and an event including acquisition information on the subject, the transmitting-side replication synchronization management module 33 transmits the generated event via the broadcast network 4 (4).

[0038] The receiving LDAP server 22 is a
It has a copy of the directory information of the AP server 21, receives an event and a subject transmitted from the transmission-side copy synchronization management module 33 via the broadcast network 4, and updates the directory entry.

That is, the receiving-side LDAP server 22 performs the synchronization management for the copy of the directory entry. The receiving-side replication synchronization management module 41 (receiving means) (acquisition means) (update means) (selection means), directory entry ( And a query processing unit 43 that performs a process related to a request for directory information (directory entry) from the receiving LDAP client terminal 12. Here, the receiving-side replication synchronization management module 41 is also software, like the transmission-side replication synchronization management module 33, and is executed by a processor (not shown).

The event from the sending LDAP server 21 is received by the receiving copy synchronization management module 41.
The receiving-side replication synchronization management module 41 recognizes that the directory entry has been updated from the received event, and further obtains a subject for performing the update from the obtained information contained therein. The broadcast channel and the broadcast start time are recognized. Then, the receiving-side copy synchronization management module 41 receives (acquires) an LDIF file as a subject whose broadcast starts from the broadcast start time on the recognized broadcast channel.

As described above, the receiving-side replication synchronization management module 41 receives the event, and further, upon receiving the subject based on the event, updates the directory entry of the database 42 with the subject (5). ).

The subject is, as described above,
The directory entry is updated using the LDIF file using the command line tool of the LDAP server (here, the LDAP server 22 on the receiving side). For example, it is described in the above-mentioned document 1.)

Thereafter, the receiving side LDAP client terminal 12 sends the receiving side LDAP client terminal 12 via the bidirectional network 3.
When accessing the P server 22 and requesting an inquiry of a predetermined directory entry (6), the request is received by the inquiry processing unit 43. Inquiry processing unit 43 receives the LDAP
The directory entry corresponding to the request from the client terminal 12 is read from the database 42 (7) and transmitted to the receiving-side LDAP client terminal 12 via the bidirectional network 3. Examples of applications for the receiving LDAP client terminal 12 to access the receiving LDAP server 22 via the two-way network 3 and request a query for a predetermined directory entry include, for example, Internat Expolrer and Netscap.
A so-called directory browser such as eNavigator (both trademarks) can be used.

As described above, the sending LDAP server 21
In the event, the event and the subject in the form of an LDIF file are transmitted from the transmission-side copy synchronization management module 33 via the broadcast network 4, while the reception-side LDA
In the P server 22, the receiving-side replication synchronization management module 41
In, an event is received, and a subject is obtained based on the event. Then, the directory entry is updated based on the subject.

That is, as shown in FIG. 4, the transmission-side copy synchronization management module 33
Send events and subjects. In this case, the event includes acquisition information such as a channel on which the subject is broadcast and a broadcast start time. Therefore, the event includes a subject for updating a directory entry whose update is notified by the event, so to speak. Pointing (subject,
It plays a role as a pointer). As a result, after receiving the event, the receiving-side copy synchronization management module 41 recognizes the channel on which the subject corresponding to the event is broadcast, the broadcast start time, and the like, and can easily acquire the subject.

Therefore, the event and the subject are
Since the broadcast is transmitted via the broadcast network 4 that can be broadcast simultaneously, when the number of the LDAP client terminals 12 on the receiving side increases, many LDAP servers 22 on the receiving side are provided so as not to degrade the quality of the directory service.
Even if it takes the form of a large-scale distributed database, it is possible to efficiently update the replica of the directory entry synchronously. As a result, it is possible to provide a high-quality (especially fast-response) directory service by LDAP to a large number of users.

Also, by using the architecture of the existing LDAP directory service system as the basis of the distributed database and mounting the transmission-side replication synchronization management module 33 and the reception-side replication synchronization management module 41 on the directory server, It is possible to update the replica of the directory entry in the server in a synchronized manner.

Further, by making the subject for updating the directory entry an LDIF file, the data accumulated (or being accumulated) in the existing LDAP directory service can be utilized as it is.

The subject is transmitted via the broadcast network 4 as described with reference to FIGS.
As shown in FIG. 4, it is also possible to store the information in a predetermined database. In this case, the event includes, for example, a URL (Uniform Resource Locat) for accessing the database in which the subject is stored.
or) is acquired as acquisition information, and the receiving-side replication synchronization management module 41 can acquire the subject based on such a URL.

Next, as the format of the event,
For example, Japanese Patent Application No. Hei 10-114 proposed earlier by the present inventor.
No. 730 can be adopted.

That is, an event is represented by a variable eventMes
For example, the following format can be used as the format represented by sege.

[0052]

In the event eventMessage, the format version formatVersion is
Indicates the version of the ssage format. That is, considering that the format of the event eventMessage will be extended in the future, the receiving-side replication synchronization management module 41 needs to recognize the format in order to process the event eventMessage. Format version
formatVersion is information (format information) for specifying the format of the event eventMessage, and the receiving-side replication synchronization management module 41 uses the format version formatVersion to receive the received event e.
The format of the ventMessage is recognized and processed.

The filter mask filteringMasks is transmitted to the receiving-side replication synchronization management module 41 by the event ev.
Information that can be used as criteria for selecting entMessage (selection criteria information).
A bit string, which will be described later, indicates a DN (Distinguished Name) used as an identification name for identifying a parent directory of a directory entry for which the event eventMessage notifies an update. Here, DN is an identifier for specifying the position of a directory entry hierarchy, and its constituent element is a relative identifier (RDN).
uished Name)). The details of the DN are described in, for example, the above-mentioned document 1.

In the receiving-side replication synchronization management module 41,
The received event eventMessage is selected based on the filter mask filteringMasks placed there. That is, the receiving-side replication synchronization management module 41 includes:
The DN used for selecting the event eventMessage is set in advance (this DN is hereinafter referred to as a setting D as appropriate).
N), the receiving-side copy synchronization management module 41 selects only the event eventMessage having the filter mask filteringMasks that matches the setting DN, and discards other eventEventMessages. Then, the receiving-side replication synchronization management module 41 acquires the subject based on the selected event eventMessage and updates the directory entry.

Here, as the setting DN, for example, by operating the receiving LDAP client terminal 12, a value desired by the user of the receiving LDAP client terminal 12 can be set. Also, the receiving side LDA
The P server 22 manages the access history from the receiving-side LDAP client terminal 12, and based on the access history, the receiving-side LDAP client terminal 1
The preference of the second user is determined, and a value that matches the preference can be set as the setting DN. In this case, the receiving LDAP server 22 reflects only the update of the directory entry updated in the transmitting LDAP server 21 that matches the user's preference of the receiving LDAP client terminal 12. The storage cost of directory entries in the LDAP server 22 can be reduced, and as a result, the database 42 can be effectively used.

Next, the survival time (expiration date) timeToLive in the event eventMessage
Represents the expiration date. That is, in the receiving-side copy synchronization management module 41, the event eventMessage transmitted via the broadcast network 4 is received, but the received event eventMessage is not always processed immediately. For this reason, when trying to acquire a subject using the event eventMessage, the event eventMessage may already be in an unusable state.

That is, for example, in the event eventMessage,
In the case where the broadcast start time of the subject is arranged, the broadcast of the subject may already be finished even if the subject is to be received after the broadcast start time. In this case, since the receiving side replication synchronization management module 41 cannot receive the subject, it is not efficient to hold such an unusable event eventMessage.

Therefore, in the survival time timeToLive, a time at which the event eventMessage should be discarded is arranged as an index indicating the freshness of the event eventMessage.

In this case, in the receiving-side replication synchronization management module 41, if the time at which the subject is to be obtained based on the event has passed the time allocated to the lifetime timeToLive, the event cannot be used. As discarded.

Next, the object identifier "objectIdentifier" in the event "eventMessage"
Information (location information) on the location where the directory entry (object) for which tMessage reports the update exists
The receiving-side replication synchronization management module 41 identifies and recognizes the updated directory entry based on the object identifier objectIdentifier. Note that, for example, the DN of the updated directory entry is arranged in the object identifier objectIdentifier.

The object version objectVersion in the event “eventMessage”
Represents the updated version of the directory entry updated by the subject fetched based on age. As the object version objectVersion, for example, an integer value that is incremented each time a directory entry is updated can be used.

The subject link subjectLinks in the event eventMessage is a subject (object identifier) acquired based on the event eventMessage.
This is equivalent to acquisition information for acquiring a subject for updating the directory entry specified by the objectIdentifier, in which, for example, the name of an object carousel in which an LDIF file as a subject is stored is arranged. Here, the object carousel refers to a data transmission method that makes data on an on-air stream appear as if a file on a certain file system is being accessed.

Next, as described above, the event eventMessa
ge as filter mask filteringMasks in DN
Is adopted, for example, among the directory entries updated in the sending LDAP server 21, for example, the update of the directory entry frequently accessed by the receiving LDAP client terminal 12 is performed by the receiving LDAP server 22. It is possible to do it with priority.

That is, for example, it is assumed that directory information as shown in FIG. 5A is stored in the transmitting LDAP server 21. Here, in FIG. 5A, the root directory has two lower (child) directories D ₁ and D ₂ , and the directory D ₁
And it has a lower directory D _11. Then, the directory D ₁₁ has three directory entries. Further, the directory D ₂ is a lower directory D ₂₁
The lower directory D ₂₁ has two lower directories D ₂₁₁ and D ₂₁₂ . Then, the directory D ₂₁₁ or D _{2 12} each have two directory entries. In FIG. 5 (the same applies to FIG. 6 described later), a directory (directory node) is indicated by a circle and a directory entry is indicated by a circle.

In this case, if the three LDAP directory entries of the directory D ₁₁ are frequently accessed by the receiving LDAP client terminal 12, the receiving LDAP server 21 performs the processing shown in FIG. 5B. In the directory information shown in FIG. 5A, the root directory, the directories D ₁ and D ₁₁ , and the directory entries of the directory D ₁₁ are updated with priority. On the other hand, two LDAP directory entries in the directory D ₂₁₁ and the directory entry D
_{If the} two directory entries of ₂₁₂ are frequently accessed, the receiving-side LDAP server 21, as shown in FIG. 5C, stores the root directory, The directories D ₂ , D ₂₁ , D ₂₁₁ , D ₂₁₂ , the two directory entries of the directory D ₂₁₁ , and the two directory entries of the directory entry D ₂₁₂ are updated with priority.

Such preferential updating can be realized by, for example, performing the following bit assignment to the directory.

That is, for example, consider directory information (structure) as shown in FIG. Here, in FIG. 6, the root directory (root) has two lower directories a and b, and the directory a has three lower directories aa, ab, and ac. The directory aa has two directory entries, the directory ab has one directory entry, and the directory ac has one directory entry. The directory b is 2
The directory ba has two lower directory entries ba and bb. The directory ba has two directory entries, and the directory bb has three directory entries.

In FIG. 6, for example, 0 or 1 is assigned to each of the two directories a and b of the root directory. Also,
Three directories aa, a of directory a
For example, 00, 01, and 10 are assigned to b and ac, respectively. Further, for example, 0 is assigned to each of the two directories ba or bb of the directory b.
Or 1 is assigned.

In this case, in the directory structure of FIG. 6, in each directory, bits (or bit strings) allocated to the directories that pass when considering the shortest path from the root directory to the lower hierarchy are sequentially arranged from the upper bits. For example, it is represented by a bit string of 1 byte (8 bits).

That is, the directory a in the lower hierarchy of the root directory is “0 *******”, and the directory aa in the lower hierarchy of the directory a (hereinafter abbreviated as a.aa) is “ 000 ***** ”, the directory ab in the lower hierarchy of the directory a (hereinafter abbreviated as a.ab) is“ 001 ***** ”and the directory ac in the lower hierarchy of the directory a ( Hereinafter, it is appropriately described as a.ac)
Are represented by “010 *****”, respectively. The directory b in the lower hierarchy of the root directory is “1 *****
** ", the directory ba in the lower hierarchy of the directory b
(Hereinafter referred to as b.ba as appropriate) is "10 ******"
The directory bb in the lower hierarchy of the directory b (hereinafter, appropriately described as b.bb) is “11 ******”,
Each is represented. In addition, * mark is don't care (don't c
are).

In the filtering mask filteringMasks, a bit string indicating a directory to which a directory entry to which an event in which the mask is assigned notifies the update is arranged. Therefore, here the filter mask filter
ingMasks is a one-byte word.

On the other hand, the receiving side replication synchronization management module 41
In, a mask value for filtering an event by the filter mask filteringMasks is set as the setting DN. That is, for example, the directory b. Receiver L for three directory entries of bb
If the access frequency from the DAP client terminal 12 is high, the directory b. A mask value “11xxxxxx” for masking other than bb is set as the setting DN.

In this case, the receiving side replication synchronization management module 41 ignores the x part of the set DN and ignores the filter mask filt which matches the 1 or 0 part.
Only events with eringMasks are selected. Therefore, when the setting DN is "11xxxxxx" as described above, the upper two bits are all 1 filter mask filt.
Only the event where the eringMasks were placed, ie, here, the directory b. Only the events in which the bit string representing bb is placed in the filter mask filteringMasks are selected. As a result, the directory b. The three directory entries of bb are updated with priority.

Further, for example, in the directory a. If the frequency of access to one directory entry of a.ab is high, the directory a.ab. A mask value “001xxxxx” for masking other than ab is set as the setting DN.

In this case, in the receiving-side copy synchronization management module 41, only the event in which the filter mask filteringMasks in which the upper three bits are 0, 0, 1 is arranged, that is, in this case, the directory a. Only events where the bit string representing ab is placed in the filter mask filteringMasks are selected. As a result, the directory a. The directory entry of ab is updated preferentially.

Further, for example, the directory a. aa has a directory entry, a directory a. ab has a directory entry and a directory a. a
If the frequency of access to the directory entry of c, that is, the directory entry having the directory a as a common directory is high, a mask value “0xxxxxxx” for masking other than the directory a
Is set as the setting DN.

In this case, in the receiving-side copy synchronization management module 41, only the event in which the filter mask filteringMasks whose most significant bit is 0 is arranged, that is, in this case, directories a, a. aa, a. ab, a. a
The bit string representing any one of c is a filter mask fi
Only events where lteringMasks are located are selected. As a result, the part with a high access frequency is also updated preferentially.

Next, in FIG. 3, the transmission-side replication synchronization management module 33 is caused to detect that the directory entry has been updated. It can be performed by any of the three detection methods.

In the first detection method, as shown in FIG.
The transmission-side LDAP client terminal 11 notifies the transmission-side replication synchronization management module 21 that the update transaction has been completed.

That is, the sending LDAP client terminal 1
1 requests the update processing unit 31 of the transmission-side LDAP server 21 to update the directory entry as described above, and this request causes the transmission-side LDAP client terminal 11 and the update processing unit 31 to update the directory entry. A transaction (update transaction) for updating the directory entry is performed. In the first detection method, after the completion of this update transaction, the completion is notified (transmitted) from the transmission-side LDAP client terminal 11, so that the transmission-side replication synchronization management module 33 is completed.
, An update of the directory entry is detected.

Here, according to the first detection method, it is easy to mount on the transmission-side replication synchronization management module 33.
Since the implementation of the sending-side LDAP client terminal 11 must notify the completion of the update transaction, it is difficult to use the existing directory browser as described above in the sending-side LDAP client terminal 11. Therefore, it is necessary to create a dedicated browser and mount it on the sending LDAP client terminal 11.

Next, in the second detection method, as shown in FIG.
The database 33 is periodically accessed to acquire the hierarchical structure (directory structure) of the directory entry. Then, the transmission-side replication synchronization management module 33 compares the hierarchical structure of the directory entry acquired this time with the hierarchical structure of the directory entry acquired last time, and detects whether or not the directory entry has been updated based on the comparison result. Let it.

Here, the second detection method uses the transmission side LDA.
Since this can be realized regardless of the implementation of the P client terminal 11, an existing (widespread) LDAP client can be used as the transmitting-side LDAP client terminal 11.

Next, in the third detection method, as shown in FIG. 9, a message of the end of the update transaction transmitted from the update processing unit 31 to the transmission-side LDAP client terminal 11 is transmitted to the transmission-side replication synchronization management module 33. Is detected.

That is, the sending LDAP client terminal 1
Here, the update transaction is performed by exchanging an LDAP protocol data unit between the update processing unit 31 and the update processing unit 31. Therefore, by causing the transmission-side replication synchronization management module 33 to trace (monitor) this exchange and detect a message indicating the end of the update transaction, it is possible to detect that the directory entry has been updated.

Here, the third detection method has high detection accuracy, and furthermore, similarly to the second detection method, the transmitting side LDAP.
Since the process can be performed regardless of the implementation of the client terminal 11, an existing LDAP client can be used as the transmitting-side LDAP client terminal 11. However, because of the need to implement the protocol data unit of LDAP as a process on the machine where the LDAP server runs, such as a message tracer over a port / a packet monitor at the network interface, this constraint generally causes It is not suitable for implementation of monitoring for the detection of a typical update (for example, remotely monitoring the detection of the update in any LDAP server).

Note that whether or not the directory entry has been updated can be detected by a method other than the above-described three detection methods. However, the above-described first to third
Can be basically implemented without changing the implementation part of the existing LDAP server.

The directory service system to which the present invention has been applied has been described above.
It can be used when distributing data to a large number of databases in a distributed database, when distributing data by IP (Internet Protocol) multicast, or when distributing data to an unspecified large number.

[0090]

As described above, according to the transmitting apparatus and the transmitting method of the present invention, broadcast data is transmitted through a broadcast network capable of simultaneous broadcast, and update data is transmitted in an LDAP LDIF file. Sent and sent.
Therefore, it is possible to provide a high-quality directory service by LDAP to a large number of clients.

Further, according to the receiving apparatus and the receiving method of the present invention, broadcast data transmitted via a broadcast network capable of simultaneous broadcast is received, and based on the acquired information included in the broadcast data, Update data in an LDAP LDIF file is acquired. Therefore, it is possible to provide a high-quality directory service by LDAP to a large number of clients.

Further, according to the transmitting / receiving apparatus and the transmitting / receiving method of the present invention, broadcast data is transmitted via a broadcast network capable of simultaneous broadcast, and update data is transmitted in the form of an LDAP LDIF file. Is done.
On the other hand, the notification data is received, and the update data in the LDAP LDIF file is obtained based on the acquisition information included in the notification data. Therefore, it is possible to provide a high-quality directory service by LDAP to a large number of clients.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a configuration example of a directory service system according to an embodiment of the present invention;

FIG. 2 is a diagram for explaining processing of the directory service system of FIG. 1;

FIG. 3 is a diagram for explaining processing of the directory service system of FIG. 1;

FIG. 4 is a diagram for explaining transmission of an event and a subject.

FIG. 5 is a diagram for explaining preferential updating of a directory entry.

FIG. 6 is a diagram for explaining bit assignment to a directory;

FIG. 7 is a diagram for explaining a first detection method for detecting an update of a directory.

FIG. 8 is a diagram for explaining a second detection method for detecting a directory update.

FIG. 9 is a diagram for explaining a third detection method for detecting a directory update.

[Explanation of symbols]

1 LDAP client terminal, 2 LDAP server, 3 bidirectional network, 4 broadcast network, 11 sending LDAP client terminal, 12
Receiving side LDAP client terminal, 21 Sending side LD
AP server, 22 receiving LDAP server, 31 update processing unit, 32 database, 33 transmitting copy synchronization management module (constructing means) (transmission means) (detection means), 41 receiving copy synchronization management module (receiving means) (acquisition) Means) (update means) (selection means), 4
2 database, 43 query processing unit

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Yoshihisa Gonno, Inventor 6-7-35 Kita-Shinagawa, Shinagawa-ku, Tokyo Inside Sony Corporation (72) Inventor Kazuo Haraoka 6-7-1, Kita-Shinagawa, Shinagawa-ku, Tokyo No. 35 Inside Sony Corporation (72) Inventor Ikuhiko Nishio 6-35 Kita Shinagawa, Shinagawa-ku, Tokyo F-term inside Sony Corporation (reference) 5B082 GB02 5B089 GB03 HB10 JA00 JB23 KA13 KB06 KC23 KC30 KC51 KE07 MC02 5K030 GA11 HB16 KA07 LD02 LD17

Claims (15)

[Claims] 1. A transmitting device for transmitting notification data for notifying an update of a database including acquisition information for obtaining update data for updating a database, comprising: a configuration unit configured to configure the notification data; Transmitting the broadcast data via a broadcast network capable of simultaneous broadcast, and transmitting the update data to an LDA.
LD of P (Lightweight Directory Access Protocol)
A transmitting means for transmitting the data in an IF (LDAP Data Interchange Format) file. 2. The transmitting apparatus according to claim 1, wherein the broadcast data further includes selection criterion information that can be used as a criterion for selecting the broadcast data. 3. The transmission according to claim 2, wherein the selection criterion information included in the broadcast data is information for identifying the update data acquired by the acquisition information included in the broadcast data. apparatus. 4. The transmission according to claim 1, further comprising a detection unit configured to detect an update of the database, wherein the configuration unit configures the notification data when the update of the database is detected. apparatus. 5. The apparatus according to claim 4, wherein the detecting means detects the update of the database by receiving a message indicating that the update has been performed from the apparatus which instructed the update of the database. Transmission device. 6. The transmitting apparatus according to claim 4, wherein said detecting means detects an update of the database by periodically referring to the database. 7. The transmitting apparatus according to claim 4, wherein said detecting means detects an update of the database by monitoring an exchange with a device instructing the update of the database. 8. The transmission apparatus according to claim 1, wherein the transmission unit transmits the update data in the form of the LDIF file via the broadcast network. 9. A transmission method for transmitting notification data for notifying update of a database including acquisition information for obtaining update data for updating a database, comprising: the notification data; The data is transmitted via a broadcast network capable of simultaneous broadcasting, and the updated data is transmitted to an LDA.
LD of P (Lightweight Directory Access Protocol)
A transmission method characterized by transmitting an IF (LDAP Data Interchange Format) file. 10. A receiving apparatus for receiving notification data for notifying update of a database including acquisition information for obtaining update data for updating a database, wherein the broadcast network is capable of simultaneous broadcast. Receiving means for receiving the notification data transmitted via the communication device; and L based on the acquisition information included in the notification data.
L for DAP (Lightweight Directory Access Protocol)
A receiving apparatus comprising: an acquiring unit that acquires the update data in a DIF (LDAP Data Interchange Format) file; and an updating unit that updates a database based on the update data. 11. The broadcast data further includes selection criterion information that can be used as a criterion for selecting the broadcast data, and based on the selection criterion information included in the broadcast data, the broadcast data The receiving apparatus according to claim 10, further comprising a selection unit that selects the data. 12. The reception according to claim 11, wherein the selection criterion information included in the broadcast data is information for identifying the update data acquired by the acquisition information included in the broadcast data. apparatus. 13. A receiving method for receiving broadcast data for notifying update of a database including acquisition information for obtaining update data for updating a database, wherein the broadcast network is capable of simultaneous broadcast. Receiving the notification data transmitted through the communication device, based on the acquisition information included in the notification data,
L for DAP (Lightweight Directory Access Protocol)
A receiving method comprising: obtaining the update data in a DIF (LDAP Data Interchange Format) file; and updating a database based on the update data. 14. A transmitting device for transmitting notification data for notifying update of a database, including a obtaining information for obtaining update data for updating a database, and a receiving device for receiving the notification data. A transmission / reception device, wherein the transmission device transmits the notification data via a broadcast network capable of simultaneous broadcasting, and transmits the update data to an LDA.
LD of P (Lightweight Directory Access Protocol)
Transmitting means for transmitting an IF (LDAP Data Interchange Format) file; the receiving device receiving the broadcast data; and receiving the broadcast data based on the acquisition information included in the broadcast data.
A transmission / reception apparatus, comprising: acquisition means for acquiring the update data in an LDIF file of a DAP; and update means for updating a database based on the update data. 15. A transmitting device for transmitting notification data for notifying the update of the database, including transmission information for obtaining update data for updating the database, and a receiving device for receiving the notification data. A transmission / reception method for a transmission / reception device, wherein the transmission device configures the broadcast data, transmits the broadcast data via a broadcast network capable of simultaneous broadcast, and transmits the update data to an LDA.
LD of P (Lightweight Directory Access Protocol)
An IF (LDAP Data Interchange Format) file is transmitted. The receiving device receives the broadcast data. Based on the acquired information included in the broadcast data,
A transmission / reception method, comprising: obtaining the update data in an LDIF file of a DAP; and updating a database based on the update data.