CN102402614B - Cross-domain data analysis method and system for directory service - Google Patents

Cross-domain data analysis method and system for directory service Download PDF

Info

Publication number
CN102402614B
CN102402614B CN 201110433436 CN201110433436A CN102402614B CN 102402614 B CN102402614 B CN 102402614B CN 201110433436 CN201110433436 CN 201110433436 CN 201110433436 A CN201110433436 A CN 201110433436A CN 102402614 B CN102402614 B CN 102402614B
Authority
CN
China
Prior art keywords
server
directory service
list server
query requests
service data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN 201110433436
Other languages
Chinese (zh)
Other versions
CN102402614A (en
Inventor
樊俐
段文良
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CVIC Software Engineering Co Ltd
Original Assignee
CVIC Software Engineering Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by CVIC Software Engineering Co Ltd filed Critical CVIC Software Engineering Co Ltd
Priority to CN 201110433436 priority Critical patent/CN102402614B/en
Publication of CN102402614A publication Critical patent/CN102402614A/en
Application granted granted Critical
Publication of CN102402614B publication Critical patent/CN102402614B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention provides a cross-domain data analysis method and a cross-domain data analysis system for directory service. The method comprises the following steps of: sending a query request of directory service data to a local directory server, and querying whether the directory service data which corresponds to the query request exists in the local directory server or not; if the directory service data which corresponds to the query request does not exist in the local directory server, judging whether the local directory server is a top-level domain directory server in a level domain directory server cluster or not; if the local directory server is not the top-level domain directory server in the level domain directory server cluster, forwarding the query request to the top-level domain directory server, and querying an address of a directory server where the directory service data corresponding to the query request is stored from the top-level domain directory server; and according to the address of the directory server, accessing the directory server where the directory service data is stored, and acquiring the directory service data which corresponds to the query request. By the method and the system, on the basis of hanging of the directory service, cross-domain data analysis is performed, and a data access speed is improved.

Description

A kind of directory service cross-domain data analysis method and system
Technical field
The application relates to the directory service field, particularly a kind of directory service cross-domain data analysis method and system.
Background technology
Growing along with computer network, the particularly development of Internet, resource on the network is increasing, and for these resources of energy unified management, beginning is used for Directory Service Technology the ground such as various resources, user, equipment, application software on the network are managed.Directory service has become a kind of basic platform software on the current network, and becomes gradually server.And LDAP (Light Directory Access Protocol, lightweight access protocal) provides simple and easy, efficient directory service as a kind of lightweight access protocal of directory information, and its efficient reading property of data is widely used.
Directory service uses ldap protocol to optimize query manipulation, and stored data adopts tree to store, in order to reduce the inquiry load, different information can be stored in the different directory services according to different classifications, the different piece of different directory server stores catalogues, when carrying out cross-domain data query, connect by articulating technology between catalogue.
In traditional data query system, database will carry out a large amount of issued transaction, so inquiry velocity has reduced an order of magnitude than the directory service of using the Ldap agreement.And mainly be read operation to data when inquiring about for cross-domain data, and lower to the Modification Frequency of data, therefore cross-domain access does not require the issued transaction of large load.
Summary of the invention
The application's technical matters to be solved provides the method that a kind of directory service cross-domain data is resolved, in order to solve the slow-footed problem of cross-domain data inquiry in the existing technology.
The system that the application also provides a kind of directory service cross-domain data to resolve is in order to guarantee said method implementation and application in practice.
In order to address the above problem, the application discloses the method that a kind of directory service cross-domain data is resolved, and the method is applied to a grade territory LIST SERVER cluster, has locking relation between the territory between each LIST SERVER in the LIST SERVER cluster of described level territory;
Method comprises:
Send the request of directory service data query to the local directory server, and inquire about whether there are the directory service data corresponding with described query requests in the described local directory server;
When not existing, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described query requests is forwarded to described TLD LIST SERVER, from described TLD LIST SERVER, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests, according to the LIST SERVER that described directory service data place is accessed in described LIST SERVER address, obtain the directory service data corresponding with described query requests.
Preferably, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests from the TLD LIST SERVER, the LIST SERVER of accessing described directory service data place according to described LIST SERVER address comprises:
As the target data server, the inquiry catalogue data corresponding with described query requests when finding the catalogue data corresponding with described query requests, obtains described catalogue data in described target data server with described TLD LIST SERVER;
Otherwise, inquire about the referral clauses and subclauses of the directory service data place catalogue corresponding with described query requests;
Described query requests is forwarded to the sub level territory LIST SERVER of described target data server according to described referral clauses and subclauses;
Described sub level territory LIST SERVER as new target data server, is searched the catalogue data corresponding with described query requests in described new catalogue data server.
Preferably, when determining that described local directory server is TLD LIST SERVER in the LIST SERVER cluster of described level territory, described TLD LIST SERVER as the target data server, is inquired about the catalogue data corresponding with described query requests in described target data server.
Preferably, also comprise: when in the LIST SERVER cluster of described level territory, not finding the directory service data corresponding with described query requests, return the information of not finding to client.
The application discloses a kind of directory service cross-domain data resolution system, and described system applies has between territory locking relation between each LIST SERVER in level territory LIST SERVER cluster in the LIST SERVER cluster of described level territory;
Described system comprises:
Transmitting element is used for sending the request of directory service data query to the local directory server, and inquires about whether be present in the corresponding directory service data of described query requests in the described local directory server;
Retransmission unit, be used for when described local directory server is not present in the corresponding directory service data of described query requests, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described query requests is forwarded to described TLD LIST SERVER, from described TLD LIST SERVER, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests, according to the LIST SERVER that described directory service data place is accessed in described LIST SERVER address, obtain the directory service data corresponding with described query requests.
Preferably, described retransmission unit comprises: judgment sub-unit;
Described judgment sub-unit is used for judging whether described local directory server is the TLD LIST SERVER of described level territory LIST SERVER cluster.
Preferably, described retransmission unit comprises: the feedback subelement;
Described feedback subelement is used for returning the information of not finding to client when when described level territory LIST SERVER cluster does not find the directory service data corresponding with described query requests.
As can be seen from the above technical solutions, the method of the cross-domain parsing of a kind of directory service is provided among the present invention, carry out data query between the LIST SERVER of finishing articulating, client sends the request of directory service data query to the local directory server, and whether there are the directory service data corresponding with affiliated query requests in the inquiry local directory server, when not existing, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described query requests is forwarded to described TLD LIST SERVER, from described TLD LIST SERVER, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests, the LIST SERVER that described directory service data place is accessed in the described LIST SERVER of foundation address, obtain the directory service data corresponding with described query requests, therefore inquire about the issued transaction that does not require large load for the directory service cross-domain data, improved the speed of cross-domain data inquiry.
Description of drawings
In order to be illustrated more clearly in the technical scheme in the embodiment of the present application, the accompanying drawing of required use was done to introduce simply during the below will describe embodiment, apparently, accompanying drawing in the following describes only is some embodiment of the application, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the process flow diagram of a kind of directory service cross-domain data analysis method embodiment 1 among the application;
Fig. 2 is the process flow diagram of a kind of directory service cross-domain data analysis method embodiment 2 among the application;
Fig. 3 is the process flow diagram of a kind of directory service cross-domain data analysis method embodiment 3 among the application;
Fig. 4 is the synoptic diagram that a kind of directory service cross-domain data is resolved concrete access among the application;
Fig. 5 is the structured flowchart of a kind of directory service cross-domain data resolution system embodiment 1 among the application;
Fig. 6 is the structured flowchart of a kind of directory service cross-domain data resolution system embodiment 2 among the application.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present application, the technical scheme in the embodiment of the present application is clearly and completely described, obviously, described embodiment only is the application's part embodiment, rather than whole embodiment.Based on the embodiment among the application, those of ordinary skills are not making the every other embodiment that obtains under the creative work prerequisite, all belong to the scope of the application's protection.
The application can be used in numerous general or special purpose calculation element environment or the configuration.For example: personal computer, server computer, handheld device or portable set, plate equipment, multi-processor device, comprise distributed computing environment of above any device or equipment etc.
The application can describe in the general context of the computer executable instructions of being carried out by computing machine, for example program module.Usually, program module comprises the routine carrying out particular task or realize particular abstract data type, program, object, assembly, data structure etc.Also can in distributed computing environment, put into practice the application, in these distributed computing environment, be executed the task by the teleprocessing equipment that is connected by communication network.In distributed computing environment, program module can be arranged in the local and remote computer-readable storage medium that comprises memory device.
The application is applied to a grade territory LIST SERVER cluster, has locking relation between the territory between each LIST SERVER in the LIST SERVER cluster of described level territory,
Main thought can comprise, sends the request of directory service data query to the local directory server, and inquires about whether there are the directory service data corresponding with described query requests in the described local directory server;
When not existing, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described query requests is forwarded to described TLD LIST SERVER, from described TLD LIST SERVER, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests, according to the LIST SERVER that described directory service data place is accessed in described LIST SERVER address, obtain the directory service data corresponding with described query requests.
With reference to figure 1, show the process flow diagram of a kind of directory service cross-domain data analysis method of the application embodiment 1, can may further comprise the steps:
Step S101: send the request of directory service data query to the local directory server, and inquire about whether there are the directory service data corresponding with described query requests in the described local directory server;
When client sends the request of directory service data query to the local directory server, and inquire about whether there are the directory service data corresponding with described query requests in the described local directory server.
Step S102: when not existing, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described query requests is forwarded to described TLD LIST SERVER, from described TLD LIST SERVER, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests, according to the LIST SERVER that described directory service data place is accessed in described LIST SERVER address, obtain the directory service data corresponding with described query requests.
When not being present in the corresponding directory service data of described query requests, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described Query Information is forwarded to the TLD LIST SERVER, with described TLD LIST SERVER as the target data server, the inquiry catalogue data corresponding with described query requests in described target data server, when finding the catalogue data corresponding with described query requests, obtain described catalogue data, otherwise, inquire about the referral clauses and subclauses of the catalogue at the directory service data place corresponding with described query requests, described query requests is forwarded to the sub level territory LIST SERVER of described target data server according to the referral clauses and subclauses, described sub level territory LIST SERVER as new target data server, is searched the catalogue data corresponding with described query requests in described new catalogue data server.
With reference to figure 2, Fig. 2 shows among the application, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests from the TLD LIST SERVER, the LIST SERVER of accessing described directory service data place according to described LIST SERVER address comprises:
Step S201: send the request of directory service data query to the local directory server, and inquire about whether there are the directory service data corresponding with described query requests in the described local directory server;
Step S202: when not existing, judge the whether TLD LIST SERVER in the LIST SERVER cluster of described level territory of described local directory server;
Step S203: if not, described Query Information is forwarded to the TLD LIST SERVER, with described TLD LIST SERVER as the target data server, the inquiry catalogue data corresponding with described query requests in described target data server, when finding the catalogue data corresponding with described query requests, obtain described catalogue data;
Step S204: if do not inquire described catalogue data, then inquire about the referral clauses and subclauses of the directory service data place catalogue corresponding with described query requests;
Step S205: the sub level territory LIST SERVER that described query requests is forwarded to described target data server according to described referral clauses and subclauses;
Step S206: described sub level territory LIST SERVER as new target data server, is searched the catalogue data corresponding with described query requests in described new catalogue data server.
Step S207: when in the LIST SERVER cluster of described level territory, not finding the directory service data corresponding with described query requests, return the information of not finding to client.
With reference to figure 3, Fig. 3 shows among the application, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests from the TLD LIST SERVER, the LIST SERVER of accessing described directory service data place according to described LIST SERVER address comprises:
Step S301: send the request of directory service data query to the local directory server, and inquire about whether there are the directory service data corresponding with described query requests in the described local directory server;
Step S302: judge the whether TLD LIST SERVER in the LIST SERVER cluster of described level territory of described local directory server;
Step S303: if, with described TLD LIST SERVER as the target data server, the inquiry catalogue data corresponding with described query requests when finding the catalogue data corresponding with described query requests, obtains described catalogue data in described target data server;
Step S304: if do not inquire described catalogue data, then inquire about the referral clauses and subclauses of the directory service data place catalogue corresponding with described query requests;
Step S305: the sub level territory LIST SERVER that described query requests is forwarded to described target data server according to described referral clauses and subclauses;
Step S306: described sub level territory LIST SERVER as new target data server, is searched the catalogue data corresponding with described query requests in described new catalogue data server.
Step S307: when in the LIST SERVER cluster of described level territory, not finding the directory service data corresponding with described query requests, return the information of not finding to client.
For aforesaid each embodiment of the method, for simple description, so it all is expressed as a series of combination of actions, but those skilled in the art should know, the application is not subjected to the restriction of described sequence of movement, because according to the application, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in the instructions all belongs to preferred embodiment, and related action and module might not be that the application is necessary.
Be directed to the concrete operations environment, in Fig. 4,
When access node at the D point, the D point is second-level domain, sends the request of directory service data query to the LIST SERVER of the D of second-level domain, and whether has the directory service data corresponding with described query requests in the LIST SERVER of the inquiry D of second-level domain.
When not existing, described query requests is forwarded to described TLD A LIST SERVER, with described TLD A LIST SERVER as the target data server, the inquiry catalogue data corresponding with described query requests in described target data server, when finding the catalogue data corresponding with described query requests, obtain described catalogue data.
If when in the target data server of TLD A, not inquiring the catalogue data corresponding with described query requests, the referral clauses and subclauses of the catalogue at the directory service data place that inquiry is corresponding with described query requests, be the address information of the one-level territory C that is included in the TLD bar directory service data place corresponding with query requests now, described query requests be forwarded to the one-level territory C LIST SERVER of described target data server according to described referral clauses and subclauses.
With one-level territory C LIST SERVER as new target data server, in the catalogue data server of described one-level territory C, search the catalogue data corresponding with described query requests, if when in the target data server of one-level territory C, not inquiring the catalogue data corresponding with described query requests, the referral clauses and subclauses of the catalogue at the directory service data place that inquiry is corresponding with described query requests, namely be included in the address information of the F of second-level domain at the one-level territory C bar directory service data place corresponding with query requests now, described query requests be forwarded to the F of the second-level domain LIST SERVER of described target data server according to described referral clauses and subclauses.
With the F of second-level domain LIST SERVER as new target data server, in the catalogue data server of the described F of second-level domain, search the catalogue data corresponding with described query requests, if when in the target data server of the F of second-level domain, not inquiring the catalogue data corresponding with described query requests, the referral clauses and subclauses of the catalogue at the directory service data place that inquiry is corresponding with described query requests, namely be included in the address information in the next stage territory at the F of the second-level domain bar directory service data place corresponding with query requests now, inquire about in the next stage territory according to above-mentioned querying method.
If still do not inquire needed directory service data, inquire about step by step using similar above-mentioned method, until when inquiring the address information that does not comprise next stage under the catalogue entry, if in this process, inquire required directory service data, then return the directory service data that inquire to client, if when not inquiring the directory service data corresponding with described query requests, also return the information of not finding to client.
Be directed to the concrete operations environment, in Fig. 4,
When access node at the A point, the A point is TLD, sends the request of directory service data query to the LIST SERVER of TLD A, and whether has the directory service data corresponding with described query requests in the LIST SERVER of inquiry TLD A.
If when in the target data server of TLD A, not inquiring the catalogue data corresponding with described query requests, the referral clauses and subclauses of the catalogue at the directory service data place that inquiry is corresponding with described query requests, be the address information of the one-level territory B that is included in the TLD bar directory service data place corresponding with query requests now, described query requests be forwarded to the LIST SERVER of the one-level territory B of described target data server according to described referral clauses and subclauses.
With one-level territory B LIST SERVER as new target data server, in the catalogue data server of described one-level territory B, search the catalogue data corresponding with described query requests, if when in the target data server of one-level territory B, not inquiring the catalogue data corresponding with described query requests, the referral clauses and subclauses of the catalogue at the directory service data place that inquiry is corresponding with described query requests, namely be included in the now address information of the E of second-level domain that is sitting in of the corresponding directory service data of region query requests of one-level territory B bar, described query requests be forwarded to the E of the second-level domain LIST SERVER of described target data server according to described referral clauses and subclauses.
With the E of second-level domain LIST SERVER as new target data server, in the catalogue data server of the described E of second-level domain, search and the described corresponding catalogue data of new request of looking into, if when in the catalogue data server of the E of second-level domain, not inquiring the catalogue data corresponding with described query requests, the referral clauses and subclauses of the catalogue at the directory service data place that inquiry is corresponding with described query requests, namely be included in the address information in the next stage territory at the E of the second-level domain bar directory service data place corresponding with query requests now, inquire about in the next stage territory according to above-mentioned querying method.
If still do not inquire needed directory service data, inquire about step by step using similar above-mentioned method, until when inquiring the address information that does not comprise next stage under the catalogue entry, if in this process, inquire required directory service data, then return the directory service data that inquire to client, if when not inquiring the directory service data corresponding with described query requests, also return the information of not finding to client.
Corresponding with the method that a kind of directory service cross-domain data analysis method of above-mentioned the application embodiment 1 provides, referring to Fig. 5, the application also provides a kind of directory service cross-domain data resolution system embodiment 1, and in the present embodiment, this system can comprise:
Transmitting element 501 and retransmission unit 502;
Wherein:
Transmitting element 501 is used for sending the request of directory service data query to the local directory server, and inquires about whether be present in the corresponding directory service data of described query requests in the described local directory server;
Retransmission unit 502 is used for when described local directory server is not present in the corresponding directory service data of described query requests, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described query requests is forwarded to described TLD LIST SERVER, from described TLD LIST SERVER, inquire about the LIST SERVER address at the directory service data place corresponding with described query requests, according to the LIST SERVER that described directory service data place is accessed in described LIST SERVER address, obtain the directory service data corresponding with described query requests.
The described system of present embodiment can be integrated on the LIST SERVER of client.
Referring to Fig. 6, preferred, in the directory service cross-domain data resolution system described in the embodiment of the present application 2, retransmission unit 502 comprises: judgment sub-unit 503;
Judgment sub-unit 503 is used for when determining that described local directory server is the TLD LIST SERVER of described level territory LIST SERVER cluster, described TLD LIST SERVER as the target data server, is inquired about the catalogue data corresponding with described query requests row in described target data server.
Preferably, in the directory service cross-domain data resolution system described in the embodiment of the present application 2, retransmission unit 502 comprises: feedback subelement 504;
Described feedback subelement 504 is used for returning the information of not finding to client when when described level territory LIST SERVER cluster does not find the directory service data corresponding with described query requests.
Preferably, the directory service cross-domain data resolution system synoptic diagram described in the embodiment of the present application 3 is similar to the system schematic among the embodiment 2.
Need to prove that each embodiment in this instructions all adopts the mode of going forward one by one to describe, what each embodiment stressed is and the difference of other embodiment that identical similar part is mutually referring to getting final product between each embodiment.For device class embodiment because itself and embodiment of the method basic simlarity, so describe fairly simple, relevant part gets final product referring to the part explanation of embodiment of the method.
At last, also need to prove, in this article, relational terms such as the first and second grades only is used for an entity or operation are made a distinction with another entity or operation, and not necessarily requires or hint and have the relation of any this reality or sequentially between these entities or the operation.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thereby not only comprise those key elements so that comprise process, method, article or the equipment of a series of key elements, but also comprise other key elements of clearly not listing, or also be included as the intrinsic key element of this process, method, article or equipment.Do not having in the situation of more restrictions, the key element that is limited by statement " comprising ... ", and be not precluded within process, method, article or the equipment that comprises described key element and also have other identical element.
For the convenience of describing, be divided into various unit with function when describing above device and describe respectively.Certainly, when implementing the application, can in same or a plurality of softwares and/or hardware, realize the function of each unit.
As seen through the above description of the embodiments, those skilled in the art can be well understood to the application and can realize by the mode that software adds essential general hardware platform.Based on such understanding, the part that the application's technical scheme contributes to prior art in essence in other words can embody with the form of software product, this computer software product can be stored in the storage medium, such as ROM/RAM, magnetic disc, CD etc., comprise that some instructions are with so that a computer equipment (can be personal computer, server, the perhaps network equipment etc.) carry out the described method of some part of each embodiment of the application or embodiment.
More than a kind of directory service cross-domain data analysis method and system that the application is provided be described in detail, used specific case herein the application's principle and embodiment are set forth, the explanation of above embodiment just is used for helping to understand the application's method and core concept thereof; Simultaneously, for one of ordinary skill in the art, the thought according to the application all will change in specific embodiments and applications, and in sum, this description should not be construed as the restriction to the application.

Claims (6)

1. a directory service cross-domain data analysis method is characterized in that, the method is applied to a grade territory LIST SERVER cluster, has locking relation between the territory between each LIST SERVER in the LIST SERVER cluster of described level territory;
Described method comprises:
Send the request of directory service data query to the local directory server, and inquire about whether there are the directory service data corresponding with described query requests in the described local directory server;
When not existing, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described query requests is forwarded to described TLD LIST SERVER, and inquires about whether there are the directory service data corresponding with described query requests in the described TLD LIST SERVER;
When not existing, inquire about the referral clauses and subclauses of the directory service data place catalogue corresponding with described query requests; And described referral clauses and subclauses are forwarded to described query requests the sub level territory LIST SERVER of described target data server; Described sub level territory LIST SERVER as new target data server, is searched the directory service data corresponding with described query requests in described new target data server.
2. method according to claim 1, it is characterized in that, when determining that described local directory server is TLD LIST SERVER in the LIST SERVER cluster of described level territory, described TLD LIST SERVER as the target data server, is inquired about the catalogue data corresponding with described query requests in described target data server.
3. method according to claim 1 is characterized in that, also comprises: when not finding the directory service data corresponding with described query requests in the LIST SERVER cluster of described level territory, return the information of not finding to client.
4. a directory service cross-domain data resolution system is characterized in that, described system applies has between territory locking relation between each LIST SERVER in level territory LIST SERVER cluster in the LIST SERVER cluster of described level territory;
Described system comprises:
Transmitting element is used for sending the request of directory service data query to the local directory server, and inquires about whether be present in the corresponding directory service data of described query requests in the described local directory server;
Retransmission unit, be used for when described local directory server is not present in the corresponding directory service data of described query requests, determine whether described local directory server is the described grade of TLD LIST SERVER in the LIST SERVER cluster of territory, if not, described query requests is forwarded to described TLD LIST SERVER, and inquires about whether there are the directory service data corresponding with described query requests in the described TLD LIST SERVER;
When not existing, inquire about the referral clauses and subclauses of the directory service data place catalogue corresponding with described query requests; And described referral clauses and subclauses are forwarded to described query requests the sub level territory LIST SERVER of described target data server; Described sub level territory LIST SERVER as new target data server, is searched the directory service data corresponding with described query requests in described new target data server.
5. system according to claim 4 is characterized in that, described retransmission unit comprises: judgment sub-unit;
Described judgment sub-unit is used for judging whether described local directory server is the TLD LIST SERVER of described level territory LIST SERVER cluster.
6. system according to claim 4 is characterized in that, described retransmission unit comprises: the feedback subelement;
Described feedback subelement is used for returning the information of not finding to client when when described level territory LIST SERVER cluster does not find the directory service data corresponding with described query requests.
CN 201110433436 2011-12-21 2011-12-21 Cross-domain data analysis method and system for directory service Active CN102402614B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN 201110433436 CN102402614B (en) 2011-12-21 2011-12-21 Cross-domain data analysis method and system for directory service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN 201110433436 CN102402614B (en) 2011-12-21 2011-12-21 Cross-domain data analysis method and system for directory service

Publications (2)

Publication Number Publication Date
CN102402614A CN102402614A (en) 2012-04-04
CN102402614B true CN102402614B (en) 2013-10-23

Family

ID=45884814

Family Applications (1)

Application Number Title Priority Date Filing Date
CN 201110433436 Active CN102402614B (en) 2011-12-21 2011-12-21 Cross-domain data analysis method and system for directory service

Country Status (1)

Country Link
CN (1) CN102402614B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109587191B (en) * 2017-09-29 2022-04-05 杭州海康威视系统技术有限公司 Cross-cloud-domain data transmission method, interconnected cloud center, cloud domain and interconnected cloud system
CN108595512A (en) * 2018-03-23 2018-09-28 华迪计算机集团有限公司 A kind of information retrieval method and equipment across security domain

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1808429A (en) * 2004-10-25 2006-07-26 国际商业机器公司 Method and system of disposal search queries
CN101335742A (en) * 2007-06-25 2008-12-31 中兴通讯股份有限公司 Directory access system and method under lightweight directory access protocol

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6587856B1 (en) * 1998-12-07 2003-07-01 Oracle International Corporation Method and system for representing and accessing object-oriented data in a relational database system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1808429A (en) * 2004-10-25 2006-07-26 国际商业机器公司 Method and system of disposal search queries
CN101335742A (en) * 2007-06-25 2008-12-31 中兴通讯股份有限公司 Directory access system and method under lightweight directory access protocol

Also Published As

Publication number Publication date
CN102402614A (en) 2012-04-04

Similar Documents

Publication Publication Date Title
US7895176B2 (en) Entry group tags
CN102647482B (en) Method and system for accessing website
JP6074514B2 (en) Feature information acquisition method, apparatus, network apparatus, program, and recording medium
JP6880131B2 (en) Methods, devices and systems for data processing
US8126916B2 (en) Priority based LDAP service publication mechanism
CN101969468B (en) Inquiry server cluster system and inquiry method
CN104378452B (en) A kind of method, apparatus and system for domain name mapping
CN100421070C (en) Method and system for managing dynamic configuration data
US8745088B2 (en) System and method of performing risk analysis using a portal
EP2361465B1 (en) Retrieving configuration records from a configuration management database
CN105574054A (en) Distributed cache range query method, apparatus and system
CN109669980A (en) The inter-library access method of data and device
CN101060539B (en) A method and system integrated with the unified access website address and providing the content of multiple website
CN103139314B (en) Based on distributed Web services discover method and the system thereof of P2P
CN102402614B (en) Cross-domain data analysis method and system for directory service
CN102103606A (en) Technology for realizing advanced search of commodities on mobile phone client
CN102378407A (en) Object name resolution system and method in internet of things
CN105978744A (en) Resource allocation method, device and system
US7689584B2 (en) Hybrid groups
CN104021192A (en) Database renewing method and device
KR20100062442A (en) System and method for accessing to file storage
CN101640701B (en) Method for inquiring telephone number mapping domain name server Enumdns
CN100543685C (en) A kind of J2EE application server high-performance JNDI service implementing method
CN102404342B (en) Method and system for articulation of directory service domains
US8606832B2 (en) Dynamic management of groups

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant