CN113094373B - Resource directory management method and device - Google Patents
Resource directory management method and device Download PDFInfo
- Publication number
- CN113094373B CN113094373B CN202110449106.XA CN202110449106A CN113094373B CN 113094373 B CN113094373 B CN 113094373B CN 202110449106 A CN202110449106 A CN 202110449106A CN 113094373 B CN113094373 B CN 113094373B
- Authority
- CN
- China
- Prior art keywords
- directory
- directory system
- system node
- resource
- node
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
- G06F16/2246—Trees, e.g. B+trees
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The application provides a resource directory management method and a device, and the method can comprise the following steps: acquiring a resource directory issued by a second directory system node in the data cascade directory system; determining an affiliation between the first directory system node and the second directory system node; and under the condition that the second directory system node and the first directory system node belong to the same alliance, generating a virtual local resource directory according to the resource directory, and setting the next hop address of the virtual local resource directory as the second directory system node. According to the technical scheme, the resources corresponding to the resource directories issued by other directory system nodes in the alliance can be directly acquired without application and approval, time waste caused by the approval process is avoided, and resource acquisition efficiency is improved.
Description
Technical Field
The application relates to the technical field of big data, in particular to a resource directory management method and device.
Background
With the development of technologies such as big data and cloud computing, data resources of departments such as enterprises and governments are usually large in quantity and distributed dispersedly, in order to give full play to data value, bring convenience to users to find and locate required resource data, and simultaneously promote resource data sharing and business cooperation among all subordinate departments, a data cascading directory system associates directory system nodes corresponding to all subordinate departments through a cascading function, manages resource directories issued by different directory system nodes in a unified mode, and therefore sharing of resource data among different directory system nodes is achieved.
In the related technology, a data cascading directory system adopts a centralized management mode to collect resource directories issued by various directory system nodes to one directory system node for storage, and when a user wants to acquire the resource directories issued by other directory system nodes across departments, the user needs to apply and be checked by an administrator of an issuing party.
Disclosure of Invention
In view of this, the present application provides a resource directory management method and apparatus, so as to directly acquire resources corresponding to resource directories issued by other directory system nodes in a federation, avoid time waste caused by an approval process, and improve resource acquisition efficiency.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of the present application, a resource directory management method is provided, which is applied to a first directory system node in a data cascading directory system, where the data cascading directory system has multiple hierarchical directory system nodes distributed according to a tree topology structure, and the first directory system node and at least one other directory system node in the data cascading directory system belong to a same federation, and the method includes:
acquiring a resource directory issued by a second directory system node in the data cascade directory system;
determining an affiliation between the first directory system node and the second directory system node;
and under the condition that the second directory system node and the first directory system node belong to the same alliance, generating a virtual local resource directory according to the resource directory, and setting the next hop address of the virtual local resource directory as the second directory system node.
According to a second aspect of the present application, a resource directory management apparatus is provided, which is applied to a first directory system node in a data cascade directory system, where the data cascade directory system has multiple hierarchical directory system nodes distributed according to a tree topology structure, and the first directory system node and at least one other directory system node in the data cascade directory system belong to a same federation, and the resource directory management apparatus includes:
the acquisition unit is used for acquiring a resource directory issued by a second directory system node in the data cascade directory system;
a determining unit, configured to determine an affiliation between the first directory system node and the second directory system node;
and the generating unit is used for generating a virtual local resource directory according to the resource directory and setting the next hop address of the virtual local resource directory as the second directory system node under the condition that the second directory system node and the first directory system node belong to the same alliance.
According to a third aspect of the present application, there is provided an electronic apparatus comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method as described in the embodiments of the first aspect above by executing the executable instructions.
According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method as described in the embodiments of the first aspect above.
According to the technical scheme provided by the application, the resource directories issued by other directory system nodes in the alliance are stored in the form of the virtual local resource directory aiming at the directory system nodes belonging to the same alliance in the data cascade directory system, and the next hop address of the virtual local resource directory is set as the corresponding resource directory issuing party, so that any directory system node in the alliance can directly acquire the resources corresponding to the resource directories issued by other directory system nodes in the alliance, the approval operation does not need to be executed, the time waste caused by approval is avoided, and the resource acquisition efficiency is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
FIG. 1 is a network architecture diagram illustrating a data cascading directory system according to an exemplary embodiment of the present application;
FIG. 2 is a flow chart illustrating a resource directory management method according to an exemplary embodiment of the present application;
FIG. 3 is a schematic diagram of a network architecture of a resource directory management system to which embodiments of the present application are applied;
FIG. 4 is a flow chart illustrating a method for resource directory management according to an exemplary embodiment of the present application;
FIG. 5 is a flow chart illustrating another resource inventory management method according to an exemplary embodiment of the present application;
FIG. 6 is a schematic view of a resource catalog management electronic device shown in accordance with an exemplary embodiment of the present application;
fig. 7 is a block diagram illustrating a resource directory management apparatus according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Next, examples of the present application will be described in detail.
Referring to fig. 1, a network architecture diagram of a data cascading directory system is shown. The data cascade catalog system mainly comprises the basic functions of catalog cataloging, registration, release, inquiry, maintenance and the like, the characteristics of the resource data are described according to the unified specification, and the resource data are mounted under the compiled resource catalog through cataloging and management of the resource data so that the resource data are associated with the compiled resource catalog, and a user can conveniently access and obtain corresponding message resources through querying the resource catalog. Aiming at massive resource data, through effective organization and management of directory contents, a user can conveniently discover, locate and share the required resource data in different departments and different regions, and the resource data can be data table resources, data API service resources and the like, and the method is not limited by the application. As shown in fig. 1, the data cascade directory system includes multi-level directory system nodes, the first level directory system node, the second level directory system node 1, the second level directory system node 2, the third level directory system node 1, and the third level directory system node 2 are arranged according to a tree topology structure, and the directory system nodes are only in communication connection with the directory system nodes having a relationship between the upper and lower levels. A user can access data resources corresponding to resource directories released by other directory system nodes in the data cascading directory system in a cross-node mode at any directory system node. Different directory system nodes in the data cascading directory system can represent different departments and different regions in reality, for example, in an enterprise, a first-level directory system node can refer to a general group, a second-level directory system node can refer to each branch company, and a third-level directory system node can refer to each subordinate department of each branch company; for government affair information, the first-level directory system node may refer to a country region, the second-level directory system node may be each province, the third-level directory node may be each city, and a user may obtain required resource data across departments and regions by cascading nodes in the directory system across data. It should be understood that the present application is not limited to the number and names of the tiers and directory system nodes included in a data cascading directory system.
For the data cascade directory system shown in fig. 1, in the prior art, resource directories issued by each directory system node are reported layer by layer, and are finally collected and stored in the first-level directory system node, when a user cross-node acquires data resources according to the resource directories aggregated by the first-level directory system node, the user needs to apply for the resource directories and perform approval by the issuer of the resource directories, and for directory system nodes with frequent business in the past, the approval process causes a lot of time waste.
In order to solve the above problems, the present application proposes to make some nodes in the data cascade directory system logically form a federation relationship in advance by creating a node federation manner, so that nodes of the directory system in the same federation do not need to be examined and approved when crossing nodes, but can directly obtain data resources corresponding to the resource directory. Fig. 2 is a flowchart illustrating a resource directory management method according to an exemplary embodiment of the present application. As shown in fig. 2, the method is applied to a first directory system node in a data cascading directory system, where the data cascading directory system has multiple hierarchical directory system nodes distributed according to a tree topology structure, and the first directory system node and at least one other directory system node in the data cascading directory system belong to the same federation, and may include the following steps:
step 202: and acquiring a resource directory issued by a second directory system node in the data cascade directory system.
In an embodiment, the obtaining a resource directory issued by a second directory system node in the data cascade directory system includes: receiving a resource directory issued by a second directory system node through a communication connection established between the resource directory and the second directory system node; and establishing communication connection between every two directory system nodes in the alliance. Directory system nodes within a federation can be connected in a number of ways, with different connections resulting in different ways of synchronizing resource directories when any of the directory system nodes within the federation publish a resource directory. If every two directory system nodes in the alliance are connected with each other to form alliance neighbors, when any directory system node issues a resource directory, the resource directory can be synchronously provided for the alliance neighbors of any directory system node in a point-to-point mode, so that the resource directory can be synchronously provided for every directory system node in the alliance at one time, participation of other directory system nodes is not needed, and the resource directory synchronization efficiency is high.
In another embodiment, the obtaining the resource directory issued by the second directory system node in the data cascade directory system includes: receiving a resource directory sent by a alliance host node through communication connection established between the alliance host node and the alliance host node, wherein the resource directory is issued to the alliance host node by the second directory system node; and the alliance main node is connected with each catalogue system node in the alliance. The federation master node may be generated manually or by election of each directory system node in the federation, which is not limited in the present application. The election of the directory system nodes may be to compare alliance registration time points, data storage amounts, node hierarchies and the like of each directory system node in an alliance according to a preset election rule. For example, the election rule is preset as a node hierarchy, each directory system node needs to compare the hierarchies of each directory system node in the data cascade directory system after being determined to be in the same alliance, and the directory system node with the highest hierarchy, namely the closest to the root node, is determined to be the principal node of the alliance, so that other directory system nodes in the alliance are connected with the principal node of the alliance. Information such as a federation registration time point, data storage amount, node hierarchy and the like of each directory system node in a federation can be acquired from federation information, and the federation information is described in detail in the following related description. By electing the alliance host node in the alliance, when any directory system node in the alliance issues the resource directory, the resource directory can be sent to the alliance host node, and then the alliance host node synchronizes each directory system node in the alliance. Because of the existence of the alliance master node, the alliance master node does not need to contact every two directory system nodes in the alliance any more, but judges whether the received resource directory needs to be synchronized to other resource directories in the alliance or not, if the illegal directory system node tries to send the wrong resource directory, the alliance master node can discard the wrong resource directory in time, so that the wrong resource directory is prevented from being synchronized to other directory system nodes, and the safety of resource data can be effectively improved.
Step 104: determining a home relationship between the first directory system node and the second directory system node.
In an embodiment, the determining a home relationship between the first directory system node and the second directory system node comprises: receiving alliance information, wherein the alliance information is used for recording alliances of all directory system nodes in the data cascade directory system; and determining whether the second directory system node and the first directory system node belong to the same alliance or not according to the alliance information. The federation information may record the federation to which each directory system node belongs in other ways, such as by recording the federation number configured by each directory system node, or by recording the name of a directory system node in a set, and recording the directory system node set as the same federation in the same set, and the like, which is not limited in this application. The federation number is used to identify a federation to which the directory system node belongs, and may be manually configured in advance by a node administrator, or may be automatically generated by the data cascade directory system according to a node characteristic, for example, a same hierarchy is set as a same federation, which is not limited in this application. For example, if the third-level directory system node 2, the second-level directory system node 2, and the second-level directory system node 1 in the directory management system shown in fig. 1 have close business with each other and frequent information interaction, the federation numbers of the third-level directory system node 2, the second-level directory system node 2, and the second-level directory system node 1 may all be manually configured as "1" and recorded in the federation information. When the second-level directory system node 1 receives the resource directory issued by the third-level directory system node 2, whether the federation number configured by the third-level directory system node 2 is the same as the self federation number can be judged by inquiring the federation information, and if the federation numbers are the same, it can be determined that the third-level directory system node 2 and the second-level directory system node 1 belong to the same federation. In addition to the information of the federation to which each directory system node belongs, the federation information may also include specific information of each directory system node, such as a node IP address, a node name, a federation registration time point of the node, a data storage amount, a node hierarchy, and the like, which is not limited in this application.
In an embodiment, the federation information is generated by counting, by a root node of the data cascade directory system, federation registration information reported by each target system node stage by stage and is sent to the first target system node. In the process of generating the federation, any directory system node reports the self-federation registration information and the received federation registration information reported by the subordinate directory system nodes to the corresponding superior directory system node, so that the primary directory system node can summarize the received federation registration information of all directory system nodes in the data cascade directory system to generate the federation information, and the federation information can be in the form of a tree topology graph or can be used for constructing the corresponding relationship between each directory system node and the federation registration information in other forms such as a relationship table, and the application does not limit the corresponding relationship. After the alliance information is generated, the first-level directory system node can send the alliance information to each directory system node in the data cascade directory system synchronously; alternatively, federation registration information for directory system nodes having the same federation number may be synchronized to the various directory system nodes within the federation. For example, in the resource directory management network architecture shown in fig. 1, the third-level directory system node 2, the second-level directory system node 2, and the second-level directory system node 1 are configured with the same federation number, and then the first-level directory system node may issue federation registration information of five directory system nodes in the data cascade directory system to each directory system node, or may issue only information about three directory system nodes, namely, the third-level directory system node 2, the second-level directory system node 2, and the second-level directory system node 1, in the federation information to the three directory system nodes individually. In another embodiment, the federation information may also be generated by the first target system node counting federation registration information synchronized between directory system nodes in the data cascading directory system, which is not limited in this application.
In one embodiment, whether a third directory system node in a federation where the first directory system node is located holds a key corresponding to the federation is judged; and when the information is not held, deleting the information related to the third directory system node in the federation information. In the resource directory management process, illegal directory system nodes which may have malicious pretend are mixed into the alliance, for this reason, keys can be configured for the directory system nodes in the process of forming the alliance, when the keys held by the directory system nodes are not matched with the legal keys of the alliance, the directory system nodes are considered as the illegal directory system nodes, matching failure messages can be sent to the first-level directory system nodes, the first-level directory system nodes delete the messages related to the directory system nodes in the alliance information and resynchronize the updated alliance information to other directory system nodes, or the matching failure messages can be directly sent to other directory system nodes in the data cascade directory system, so that the other directory system nodes synchronously delete the operation, and the illegal directory system nodes are prevented from being added into the alliance to steal the data resources of the other directory system nodes, or provide the wrong resource directory to other directory system nodes, thereby improving the security of the data resource.
In an embodiment, the determining whether a third directory system node in a federation in which the first directory system node is located holds a key corresponding to the federation includes: matching the key held by the third directory system node with a legal key, and if the matching is successful, determining that the third directory system node holds the key corresponding to the union; the legal key is a key held by a directory system node which is recorded in the federation information and registered with the federation earliest. For example, the federation information includes federation registration time of each directory system node, and the key held by the directory system node that registers the federation earliest is determined to be a legal key by comparing the morning and the evening of the registration time of each directory system node of the same federation. For example, in the data cascade directory system shown in fig. one, if the second-level directory system node 1, the second-level directory system node 2 and the third-level directory system node 2 belong to the same federation, where the directory system node registered at the earliest in the federation is the second-level directory system node 1, it is determined that the key a held by the second-level directory system node 1 is a legal key, and the other destinations are the same as the legal keysThe recording system node needs to match the key held by the recording system node with the key A direction when the recording system node wants to prove the validity of the recording system node, and the key is legal when the matching is successful. The key matching process may refer to related content of an encryption algorithm in the prior art, which is not specifically limited in this application. For example, if matching the key B held by the secondary directory system node 2 with the key a, the secondary directory system node 1 may encrypt a random number using the key a, send the encrypted value to the secondary directory system node 2, the secondary directory system node 2 decrypts the received encrypted value using its own key B, and return the decrypted data to the secondary directory system node 1, and if the returned data is identical to the random number used by the secondary directory system node 1, it is determined that the key B matches the key a; or, the secondary directory system node 2 may perform hash calculation on the key B of itself, and obtain a hashBSending the hash to a secondary directory system node 1, and sending the received hash to the secondary directory system node 1BHash with hash calculation of key aAMaking a comparison if the hash isBAnd hashAIf the key A is the same as the key B, determining that the key A is matched with the key B; or, the key may be matched in other encryption manners in the prior art, which is not described herein again. The key held by the directory system node which registers the alliance earliest recorded in the alliance information is regarded as the legal key of the alliance, the legal key is determined in a simple and convenient mode, and in the matching process, the keys held by other directory system nodes in the alliance are matched with the legal key one by one, so that the legality of other directory system nodes can be determined conveniently.
In an embodiment, the determining whether a third directory system node in a federation in which the first directory system node is located holds a key corresponding to the federation includes: and matching the key held by the third directory system node with the keys held by other directory system nodes in the alliance, and if the percentage of the matching success times in the total matching times is greater than a preset threshold value, determining that the third directory system node holds the key corresponding to the alliance. For example, there are 4 directory system nodes in the federation, where a directory system node matches a key held by itself with keys held by other 3 directory system nodes, and if 2 matches succeed and 1 fails, the directory system node corresponding to the directory system node and the two keys that match successfully is considered as the directory system node holding the key corresponding to the federation, and the directory system node corresponding to the key that fails to match does not hold the key corresponding to the federation. For the method of key matching, reference may be made to the related description in the above embodiments, and details are not repeated here.
Step 206: and under the condition that the second directory system node and the first directory system node belong to the same alliance, generating a virtual local resource directory according to the resource directory, and setting the next hop address of the virtual local resource directory as the second directory system node.
In an embodiment, when the second directory system node is a lower directory system node of the first directory system node, determining a summarizing mode of a resource directory issued by the second directory system node, and generating a virtual local resource directory according to the resource directory when the summarizing mode is a federation summarizing; and reporting the resource directory to an upper-layer directory system node of a first directory system node under the condition that the summarizing mode is root node summarizing until the root node in the data cascade directory system acquires the resource directory. In the prior art, the resource directories are reported layer by layer, so that the first-level directory system nodes summarize the resource directories issued by each directory system node in the data cascade directory system. Therefore, when the first directory system node acquires the resource directory issued by the second directory system node, if the second directory system node is exactly a subordinate directory system node of the first directory system node, it needs to determine whether the first directory system node reports the resource directory layer by layer in the prior art, or stores the resource directory in a virtual local manner according to the technical scheme of the application, or both, and different summarizing modes can be selected for different resource directories, so that flexibility of issuing and acquiring the resource directory is improved.
In an embodiment, the determining a manner of summarizing the resource directories published by the second directory system node includes: and determining a summarizing mode of the resource directory according to the indication identifier which is issued by the second directory system node and corresponds to the resource directory. In order to distinguish a summarizing mode of the resource directory, the indication identifier may be issued at the same time as the resource directory is issued, or the indication identifier may be added to the resource directory, where the indication identifier may be valid for a long time, or may be temporarily issued and valid for one time, and the present application is not limited to this. For example, the third directory system node 2 may temporarily generate an indication identifier for the resource directory to be published each time the resource directory is published, and mark different indication identifiers according to different published resource directories, or may also set a long-term indication identifier for intra-federation summary for the second directory system node in advance, so that the manner of summarizing the resource directory published by the second directory system node is defaulted to intra-federation summary.
In one embodiment, a query instruction of a user for a target resource directory is obtained; and when a target virtual local resource directory corresponding to the target resource directory exists, accessing the second directory system node according to the next hop address of the target virtual local resource so as to obtain resource data corresponding to the query instruction from the second directory system node. In the process of inquiring the resource directory by the user, if the resource directory issuer selected by the user is in the same alliance with the directory system node executing the inquiry command, the directory system node of the resource directory issuer can be directly accessed through the virtual local resource directory stored by the directory system node to acquire the resource data related to the resource directory without an approval process, thereby improving the acquisition rate of the resource.
In an embodiment, when there is no target virtual local resource directory corresponding to the target resource directory, sending an approval application to the second directory system node; accessing the second directory system node if approval passes to obtain resource data corresponding to the query instruction from the second directory system node. By examining and approving the query request for obtaining the resource directory without generating the virtual local resource directory, only the user or the directory system node which is examined and verified by the administrator has the qualification of obtaining the data resource, and the resource data can be prevented from being leaked to a certain extent.
According to the technical scheme provided by the application, the jump addresses of the resource directories distributed by the directory system nodes forming the alliance and stored in the directory system nodes in the alliance are set as the virtual local of the distributor, so that a user can directly obtain the resources corresponding to the resource directories distributed by other directory system nodes in the same alliance with the directory system nodes at any directory system node, the time waste caused by approval is avoided, the directory resources distributed by the directory system nodes in the data cascade directory system do not need to be collected to the root node for storage, and the storage pressure of the root node is reduced to a certain extent.
Fig. 3 is a schematic diagram of a data cascading directory system to which the embodiment of the present application is applied. As shown in fig. 3, the data cascade directory system is a three-level directory system, and includes five directory system nodes, i.e., a first-level directory system node, a second-level directory system node 1, a second-level directory system node 2, a third-level directory system node 1, and a third-level directory system node 2, where each directory system node can issue directory information of a corresponding data resource, and the third-level directory system node 2, the second-level directory system node 2, and the second-level directory system node 1 are in communication connection, and belong to the same federation. The second-level directory system node 1 is a first directory system node 301, the third-level directory system node 2 is a second directory system node 302, and the third-level directory system node 1 is a third directory system node 303.
In the technical solution of the present application, by setting an alliance in a data cascade directory system, a directory system in the alliance can save resource directories issued by other directory system nodes in the same alliance in a virtual local, so that the directory system nodes can directly acquire the resource directories issued by the directory system nodes in the same alliance without performing approval when acquiring the resource directories, which is described in detail below with reference to fig. 4. Fig. 4 is a flowchart illustrating a resource directory management method according to an exemplary embodiment of the present application. As shown in fig. 4, the process of publishing the resource directory in the data concatenation directory system includes the following steps:
in step 401, the first directory system node 301 receives the federation information and determines directory system nodes with the same federation number.
Each directory system node is configured with an alliance number when joining the data cascade directory system, in the data cascade directory system, a second-level directory system node 1, a second-level directory system node 2, a third-level directory system node 1 and a third-level directory system node 2 are configured with an alliance number '1', and a first-level directory system node is configured with an alliance number '2'. When each target system node is added into the data cascade directory system, the respective alliance registration information can be reported to the first-level directory system node step by step, and the first-level directory system node counts and generates alliance information. The federation information includes federation numbers configured for each directory system node and information such as node IP, federation number registration time, node hierarchy and the like of each directory system node.
The second-level directory system node 1 receives the alliance information issued by the first-level directory system node, and determines a directory system node sea oil second-level directory system node 2 and a third-level directory system node 2 with the alliance number of 1 which are also configured in the data cascade directory system according to the alliance information.
Each directory system node is configured with a key corresponding to the alliance number while configuring the alliance number, and the keys corresponding to the same alliance number are the same. In order to prevent an illegal directory system node from being mixed into the alliance to acquire the data resource corresponding to the resource directory issued by other directory system nodes, the key held by the directory system node with the same alliance number can be verified, and if the key of the directory system node is not matched, the directory system node is kicked out of the alliance.
For example, the second-level directory system node 1 holds a key a, the second-level directory system node 2 holds a key B, the third-level directory system node 2 holds a key C, the second-level directory system node 1 matches the key held by the second-level directory system node 1 with the key B, and the second-level directory system node 1 receives a hash obtained by performing hash calculation on the key B sent by the second-level directory system node 2BWill hashBHash obtained by carrying out hash calculation on the key A held by the userAMaking a comparison at hashBAnd hashAIn the same case, it is determined that key a matches key B.
In this embodiment, if the hash values of the key a, the key B, and the key C are the same, and are different from the hash value of the key D, the number of times of key matching success of the second-level directory system node 2 is relatively large, the key corresponding to the federation number "1" is determined to be held, and meanwhile, the third-level directory system 1 corresponding to the key D can be considered as an illegal directory system node, and the first-level directory system is notified to delete the information corresponding to the third-level directory system 1 in the federation information, and the updated federation information is resynchronized to other directory system nodes in the data cascade directory system.
In step 403, the first directory system node 301 connects with other directory system nodes belonging to the same federation to generate a federation.
In this embodiment, the second-level directory system node 1, the second-level directory system node 2, and the third-level directory system node 2 are configured with the same federation number "1" and hold the key corresponding to the federation number "1", and these directory systems may be connected two by two to form a federation.
In step 404, the first directory system node 301 obtains the resource directory published by the second directory system node 302.
In this embodiment, the secondary directory system node 1 receives the resource directory issued by the tertiary directory system node 2.
In step 405, the first directory system node 301 determines whether the second directory system node 302 and the first directory system node belong to the same federation.
In this embodiment, the second-level directory system node 1 may obtain that the federation number configured by the third-level directory system node 2 and the federation number configured by itself are both "1" by querying the federation information sent by the first-level directory system node, and determine that the third-level directory system node 2 and itself belong to the same federation.
The third-level directory system node 2 marks the relevant indication marks for the issued resource directories, and can determine the summarizing mode of the corresponding resource directories according to the indication marks.
And 407a, under the condition that the summarizing mode is in-alliance summarizing, generating a virtual local resource catalog according to the resource catalog.
In this embodiment, if the aggregation mode corresponding to the indication identifier of the resource directory is intra-alliance aggregation, the secondary directory system node 1 generates a virtual local resource directory to store the received resource directory, and sets the next hop address of the virtual local resource directory as the tertiary directory system node 2.
Step 407b, reporting the resource directory to an upper-layer directory system node of the first directory system node when the aggregation mode is root node aggregation.
In this embodiment, if the aggregation mode corresponding to the indication identifier of the resource directory is root node aggregation, the secondary directory system node 1 reports the received resource directory to the primary directory system node of the upper level.
FIG. 5 is a flow chart illustrating another resource inventory management method according to an exemplary embodiment of the present application. As shown in fig. 5, the process of publishing the resource directory in the data cascade directory system includes the following steps:
The user browses the resource directories at the secondary directory system node 1 and sends a query instruction aiming at a certain resource directory.
In step 503a, when there is a target virtual local resource directory corresponding to the target resource directory, the second directory system node 302 is accessed according to the next hop address of the target virtual local resource.
In this embodiment, if the target resource directory selected by the user is the resource directory issued by the third-level directory system node 2, the virtual local resource directory of the resource directory exists in the second-level directory system node 1. And accessing the third-level directory system node 2 according to the next-hop address of the virtual local resource directory, and acquiring resource data corresponding to the query instruction from the third-level directory system node 2.
If the target resource directory selected by the user is the resource directory issued by the third-level directory system node 1, the virtual local resource directory of the resource directory does not exist in the second-level directory system node 1. And the second-level directory system node 1 sends an acquisition approval application about the resource corresponding to the resource directory to the third-level directory system node 1.
And 504, accessing the second directory system node under the condition of passing the approval to obtain the resource data corresponding to the query instruction from the second directory system node.
And if the administrator of the third-level directory system node 1 approves the approval application, accessing the third-level directory system node 1 to obtain the resource data corresponding to the query instruction.
Corresponding to the method embodiments, the present specification also provides an embodiment of an apparatus.
Fig. 6 is a schematic structural diagram of an electronic device for managing a resource directory according to an exemplary embodiment of the present application. Referring to fig. 6, at the hardware level, the electronic device includes a processor 602, an internal bus 604, a network interface 606, a memory 608, and a non-volatile memory 610, but may also include hardware required for other services. The processor 602 reads the corresponding computer program from the non-volatile memory 610 into the memory 608 and runs the computer program, thereby forming a device for solving the problem of resource directory management on a logical level. Of course, besides the software implementation, the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Fig. 7 is a block diagram illustrating a resource directory management apparatus according to an exemplary embodiment of the present application.
Referring to fig. 7, the apparatus includes an acquisition unit 702, a determination unit 704, and a generation unit 706, wherein:
the obtaining unit 702 is configured to obtain a resource directory issued by a second directory system node in the data cascade directory system;
the determining unit 704 is configured to determine a home relationship between the first directory system node and the second directory system node;
the generating unit 706 is configured to generate a virtual local resource directory according to the resource directory and set a next-hop address of the virtual local resource directory as the second directory system node when the second directory system node and the first directory system node belong to the same federation.
Optionally, the determining the affiliation between the first directory system node and the second directory system node includes: receiving alliance information, wherein the alliance information is used for recording alliances of all directory system nodes in the data cascade directory system; and determining whether the second directory system node and the first directory system node belong to the same alliance or not according to the alliance information.
Optionally, the federation information is generated after a root node of the data cascade directory system counts federation registration information reported by each target system node step by step and is sent to the first target system node; or, the first target system node counts and generates the alliance registration information synchronized among all directory system nodes in the data cascade directory system.
Optionally, the apparatus further comprises:
the determining unit 708 is configured to determine whether a third directory system node in a federation in which the first directory system node is located holds a key corresponding to the federation;
the deleting unit 710 is configured to delete, when not holding, information related to the third directory system node in the federation information.
Optionally, the determining whether a third directory system node in a federation where the first directory system node is located holds a key corresponding to the federation includes: matching the key held by the third directory system node with a legal key, and if the matching is successful, determining that the third directory system node holds the key corresponding to the alliance; the legal key is a key held by a directory system node which is recorded in the alliance information and is earliest registered to the alliance; or matching the key held by the third directory system node with the keys held by other directory system nodes in the federation, and if the percentage of the matching success times in the total matching times is greater than a preset threshold, determining that the third directory system node holds the key corresponding to the federation.
Optionally, the obtaining a resource directory issued by a second directory system node in the data cascade directory system includes: receiving a resource directory issued by a second directory system node through a communication connection established between the resource directory and the second directory system node; wherein, the communication connection is established between every two directory system nodes in the alliance; or, through the communication connection established between the second directory system node and the alliance host node, receiving the resource directory sent by the alliance host node, wherein the resource directory is issued to the alliance host node by the second directory system node; and the alliance main node is connected with each catalogue system node in the alliance.
Optionally, the generating a virtual local resource directory according to the resource directory under the condition that the second directory system node and the first directory system node belong to the same alliance includes: when the second directory system node is a lower-layer directory system node of the first directory system node, determining a summarizing mode of a resource directory issued by the second directory system node, and generating a virtual local resource directory according to the resource directory under the condition that the summarizing mode is intra-alliance summarizing;
optionally, the apparatus further comprises:
the reporting unit 712 is configured to report the resource directory to an upper-layer directory system node of the first directory system node when the aggregation manner is root node aggregation until the root node in the data cascade directory system acquires the resource directory.
Optionally, the determining a summarizing manner of the resource directories issued by the second directory system node includes: and determining a summarizing mode of the resource directory according to the indication identifier which is issued by the second directory system node and corresponds to the resource directory.
Optionally, the apparatus further comprises:
the instruction obtaining unit 714 is configured to obtain a query instruction of a user for the target resource directory;
the first accessing unit 716 is configured to, when there is a target virtual local resource directory corresponding to the target resource directory, access the second directory system node according to a next hop address of the target virtual local resource to obtain resource data corresponding to the query instruction from the second directory system node.
Optionally, the apparatus further comprises:
the approval unit 718 is configured to send an approval application to the second directory system node when there is no target virtual local resource directory corresponding to the target resource directory;
the second accessing unit 720 is configured to access the second directory system node in case of approval pass, to obtain resource data corresponding to the query instruction from the second directory system node.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
In an exemplary embodiment, there is also provided a non-transitory computer readable storage medium, e.g. a memory, comprising instructions executable by a processor of a resource directory management apparatus to implement a method as described in any of the above embodiments, such as the method may comprise:
acquiring a resource directory issued by a second directory system node in the data cascade directory system; determining an affiliation between the first directory system node and the second directory system node; and under the condition that the second directory system node and the first directory system node belong to the same alliance, generating a virtual local resource directory according to the resource directory, and setting the next hop address of the virtual local resource directory as the second directory system node.
The non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, which are not limited in this application.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (13)
1. A resource directory management method is applied to a first directory system node in a data cascade directory system, wherein the data cascade directory system is distributed with a plurality of levels of directory system nodes according to a tree topology structure, and the first directory system node and at least one other directory system node in the data cascade directory system belong to the same alliance in terms of logical relationship, and the method comprises the following steps:
acquiring a resource directory issued by a second directory system node in the data cascade directory system;
determining an affiliation between the first directory system node and the second directory system node;
and under the condition that the second directory system node and the first directory system node belong to the same alliance, generating a virtual local resource directory according to the resource directory, and setting the next hop address of the virtual local resource directory as the second directory system node.
2. The method of claim 1, wherein determining the affiliation between the first directory system node and the second directory system node comprises:
receiving alliance information, wherein the alliance information is used for recording alliances of all directory system nodes in the data cascade directory system;
and determining whether the second directory system node and the first directory system node belong to the same alliance or not according to the alliance information.
3. The method of claim 2,
the alliance information is generated after the alliance registration information reported by each directory system node step by step is counted by a root node of the data cascade directory system and is sent to the first directory system node; alternatively, the first and second electrodes may be,
and the first directory system node counts and generates the alliance registration information which is mutually synchronized among the directory system nodes in the data cascade directory system.
4. The method of claim 2, further comprising:
judging whether a third directory system node in a alliance where the first directory system node is located holds a key corresponding to the alliance or not;
and when the information is not held, deleting the information related to the third directory system node in the federation information.
5. The method of claim 4, wherein determining whether a third directory system node in a federation in which the first directory system node is located holds a key corresponding to the federation comprises:
matching the key held by the third directory system node with a legal key, and if the matching is successful, determining that the third directory system node holds the key corresponding to the union; the legal key is a key held by a directory system node which is recorded in the alliance information and is earliest registered to the alliance;
or matching the key held by the third directory system node with the keys held by other directory system nodes in the federation, and if the percentage of the matching success times in the total matching times is greater than a preset threshold, determining that the third directory system node holds the key corresponding to the federation.
6. The method of claim 1, wherein the obtaining the resource directory published by the second directory system node in the data cascading directory system comprises:
receiving a resource directory issued by a second directory system node through a communication connection established between the resource directory and the second directory system node; establishing communication connection between every two directory system nodes in the alliance; alternatively, the first and second electrodes may be,
receiving a resource directory sent by a alliance host node through communication connection established between the alliance host node and the alliance host node, wherein the resource directory is issued to the alliance host node by the second directory system node; and the alliance main node is connected with each catalogue system node in the alliance.
7. The method of claim 1,
under the condition that the second directory system node and the first directory system node belong to the same alliance, generating a virtual local resource directory according to the resource directory, wherein the method comprises the following steps: when the second directory system node is a lower-layer directory system node of the first directory system node, determining a summarizing mode of a resource directory issued by the second directory system node, and generating a virtual local resource directory according to the resource directory under the condition that the summarizing mode is in-alliance summarizing;
the method further comprises the following steps: and reporting the resource directory to an upper-layer directory system node of a first directory system node under the condition that the summarizing mode is root node summarizing until the root node in the data cascade directory system acquires the resource directory.
8. The method of claim 7, wherein the determining a manner of summarizing the resource directories published by the second directory system node comprises:
and determining a summarizing mode of the resource directory according to the indication identifier which is issued by the second directory system node and corresponds to the resource directory.
9. The method of claim 1, further comprising:
acquiring a query instruction of a user for a target resource directory;
and when a target virtual local resource directory corresponding to the target resource directory exists, accessing the second directory system node according to the next hop address of the target virtual local resource so as to obtain resource data corresponding to the query instruction from the second directory system node.
10. The method of claim 9, further comprising:
when a target virtual local resource directory corresponding to the target resource directory does not exist, sending an approval application to the second directory system node;
accessing the second directory system node if approval passes to obtain resource data corresponding to the query instruction from the second directory system node.
11. An apparatus for resource directory management, applied to a first directory system node in a data cascading directory system, where the data cascading directory system has multiple levels of directory system nodes distributed according to a tree topology, and the first directory system node and at least one other directory system node in the data cascading directory system belong to a same federation in terms of logical relationship, the apparatus comprising:
the acquisition unit is used for acquiring a resource directory issued by a second directory system node in the data cascade directory system;
a determining unit, configured to determine an affiliation between the first directory system node and the second directory system node;
and the generating unit is used for generating a virtual local resource directory according to the resource directory and setting the next hop address of the virtual local resource directory as the second directory system node under the condition that the second directory system node and the first directory system node belong to the same alliance.
12. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any one of claims 1-10 by executing the executable instructions.
13. A computer-readable storage medium having stored thereon computer instructions, which, when executed by a processor, carry out the steps of the method according to any one of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110449106.XA CN113094373B (en) | 2021-04-25 | 2021-04-25 | Resource directory management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110449106.XA CN113094373B (en) | 2021-04-25 | 2021-04-25 | Resource directory management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113094373A CN113094373A (en) | 2021-07-09 |
| CN113094373B true CN113094373B (en) | 2022-05-31 |
Family
ID=76680234
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110449106.XA Active CN113094373B (en) | 2021-04-25 | 2021-04-25 | Resource directory management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113094373B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1820451A (en) * | 2003-10-23 | 2006-08-16 | 微软公司 | System and method for virtual folder and item sharing |
| CN102385633A (en) * | 2011-12-13 | 2012-03-21 | 方正国际软件有限公司 | File management system using virtual storage directory |
| CN103455583A (en) * | 2013-08-26 | 2013-12-18 | 小米科技有限责任公司 | Method and device for establishing virtual directory and electronic equipment |
| CN109471839A (en) * | 2018-10-29 | 2019-03-15 | 杭州数梦工场科技有限公司 | Inventory management of resources method and device |
| CN111241363A (en) * | 2020-01-15 | 2020-06-05 | 深圳市华傲数据技术有限公司 | Method and system for creating information resource directory system and electronic equipment |
| CN112540980A (en) * | 2020-01-02 | 2021-03-23 | 北京融信数联科技有限公司 | Government affair data co-construction sharing method based on block chain technology |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2418267A (en) * | 2004-09-08 | 2006-03-22 | Qinetiq Ltd | Shared resource management |
| US11102214B2 (en) * | 2018-08-27 | 2021-08-24 | Amazon Technologies, Inc. | Directory access sharing across web services accounts |
-
2021
- 2021-04-25 CN CN202110449106.XA patent/CN113094373B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1820451A (en) * | 2003-10-23 | 2006-08-16 | 微软公司 | System and method for virtual folder and item sharing |
| CN102385633A (en) * | 2011-12-13 | 2012-03-21 | 方正国际软件有限公司 | File management system using virtual storage directory |
| CN103455583A (en) * | 2013-08-26 | 2013-12-18 | 小米科技有限责任公司 | Method and device for establishing virtual directory and electronic equipment |
| CN109471839A (en) * | 2018-10-29 | 2019-03-15 | 杭州数梦工场科技有限公司 | Inventory management of resources method and device |
| CN112540980A (en) * | 2020-01-02 | 2021-03-23 | 北京融信数联科技有限公司 | Government affair data co-construction sharing method based on block chain technology |
| CN111241363A (en) * | 2020-01-15 | 2020-06-05 | 深圳市华傲数据技术有限公司 | Method and system for creating information resource directory system and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 水利大数据目录服务与资源共享关键技术研究;陆佳民等;《水利信息化》;20170815;正文第18-20页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113094373A (en) | 2021-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102577139B1 (en) | Smart contract-based data processing methods, devices, and storage media | |
| CN108124502B (en) | Top-level domain name management method and system based on alliance chain | |
| CN110910138B (en) | Block chain data supervision method and device | |
| CN110958117B (en) | Block chain interoperability with support for zero knowledge proof | |
| US10230526B2 (en) | Out-of-band validation of domain name system records | |
| WO2018228331A1 (en) | Service data storage method, device, storage medium, and electronic device | |
| CN108134764B (en) | Distributed data sharing and exchanging method and system | |
| CN113421097B (en) | Data processing method and device, computer equipment and storage medium | |
| CN109714239B (en) | Management message issuing method, VNFM (virtual network management frequency) equipment and server | |
| US20210160067A1 (en) | Method for bidirectional authorization of blockchain-based resource public key infrastructure | |
| CN113824563B (en) | Cross-domain identity authentication method based on block chain certificate | |
| CN108566449A (en) | Domain name mapping data managing method, system and storage system based on block chain | |
| CN110730081B (en) | Block chain network-based certificate revocation method, related equipment and medium | |
| WO2022237497A1 (en) | Data storage method and apparatus based on blockchain network | |
| CN113067897B (en) | Cross-chain interaction method and device | |
| CN110796329A (en) | Asset transaction monitoring method | |
| CN113922971A (en) | Cross-chain interaction method and device | |
| Wang et al. | Blockzone: A blockchain-based dns storage and retrieval scheme | |
| CN113259454B (en) | Cross-chain interaction method and device | |
| CN116668408B (en) | IPv6 container cloud platform real address coding verification and tracing method and system | |
| CN113259453A (en) | Cross-chain interaction method and device | |
| CN113094373B (en) | Resource directory management method and device | |
| Song et al. | Smart contract-based trusted content retrieval mechanism for NDN | |
| CN113067838A (en) | Cross-chain interaction method and device | |
| CN106470248A (en) | The hot spare method of DNSSEC Digital signature service and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |