A data resource positioning method and system based on identification resolution

Abstract

The application discloses a data resource positioning method and system based on identification analysis, relates to the technical field of data communication and resource management, and comprises the following steps: receiving a data resource positioning request, separating a global unique identification in the data resource positioning request into a prefix part and a suffix part; performing main domain analysis according to the prefix part; performing resource analysis according to the suffix part; the resource analysis sends the suffix part to a digital object warehouse gateway address; a gateway corresponding to the digital object warehouse gateway address searches and returns a target data resource from a corresponding digital object warehouse according to the suffix part, and verifies access authority at the same time. Through the hierarchical processing mechanism of the main domain analysis and the resource analysis, the application solves the technical problem of accurate positioning of massive heterogeneous data resources, adopts the technical means of prefix hierarchical query and suffix accurate matching, realizes unified management and efficient access of data resources, improves data sharing and exchange efficiency, and guarantees the safety of data access.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data communication and resource management, and particularly relates to a data resource positioning method and system based on identification resolution. BACKGROUND

[0002] The data resource identification and resolution system is a key component of digital economic infrastructure. The identification resolution system originated from the Internet domain name resolution system DNS, and then developed Handle system, DOI (Digital Object Identifier) and other identification resolution technologies. These systems assign global unique identifiers to digital objects and provide resolution services to map identifiers to resource location information, realizing permanent identification and reliable access of digital resources. In the field of industrial internet, the identification resolution system is regarded as the core technical foundation for realizing global product traceability, supply chain collaboration and resource sharing. At present, various identification resolution technologies coexist and develop, forming a diversified technology ecology represented by OID (Object Identifier), Ecode, Handle, etc. Especially in the Internet of Things and big data environment, identification resolution technology is evolving from traditional domain name resolution to more complex distributed identification resolution to adapt to the efficient positioning and management needs of cross-organizational and cross-industry data resources.

[0003] However, the existing identification resolution technology still has obvious deficiencies in handling cross-domain sharing and exchange of heterogeneous data resources. First, the traditional identification resolution system usually adopts a single resolution structure, lacks a hierarchical processing mechanism for identification prefixes and suffixes, and results in low efficiency of cross-domain resource positioning. Second, the existing technology lacks dynamic adjustment according to network status when implementing cross-industry and cross-organizational data resource access, and the system reliability is insufficient. Third, the current identification resolution technology has limited support for data interconnection and interconnection between different industries and fields, and the domain mapping relationship is simply processed, which makes it difficult to meet the efficient positioning needs of data resources in complex scenarios. Fourth, the existing solution lacks effective caching mechanisms and load balancing strategies when handling large-scale data resource access, and the system response speed and stability are difficult to guarantee. In addition, the existing technology often adopts a unified strategy for access control, which cannot realize fine-grained permission management for cross-domain access, and has potential security risks. SUMMARY

[0004] In view of the above problems, the present application is proposed.

[0005] Therefore, the present application provides a data resource positioning method and system based on identification resolution, which can solve the problems mentioned in the background art.

[0006] To solve the above technical problems, the present application provides the following technical solutions:

[0007] In a first aspect, the application provides a data resource positioning method based on identification resolution, comprising: receiving a data resource positioning request, separating a globally unique identification in the data resource positioning request into a prefix part and a suffix part; the prefix part is used to determine the domain to which the data resource belongs, and the suffix part is used to identify a unique target data resource; performing primary domain resolution according to the prefix part; the primary domain resolution determines the digital object warehouse gateway address corresponding to the data resource by querying the digital object registry step by step, and the step-by-step query locates from the root node downward along the hierarchical structure of the prefix part; performing resource resolution according to the suffix part; the resource resolution sends the suffix part to the digital object warehouse gateway address, and the gateway corresponding to the digital object warehouse gateway address retrieves and returns the target data resource from the corresponding digital object warehouse according to the suffix part, while verifying the access right.

[0008] Preferably, the separating of the globally unique identification in the data resource positioning request into the prefix part and the suffix part comprises: identifying the position of a preset separator in the globally unique identification; extracting the part before the preset separator as the prefix part; and extracting the part after the preset separator as the suffix part.

[0009] Preferably, the prefix part has a hierarchical structure, and each level in the hierarchical structure is connected by a level separator, which is different from the preset separator between the prefix part and the suffix part.

[0010] Preferably, the step-by-step query comprises: according to the first level of the prefix part, obtaining the identification resolution server address of the second level in the root node identification resolution server; according to the second level of the prefix part, obtaining the identification resolution server address of the third level in the identification resolution server of the second level; according to each subsequent level of the prefix part, obtaining the identification resolution server address of the next level in the corresponding identification resolution server; performing reachability verification on each identification resolution server accessed in the step-by-step query process, the reachability verification comprises sending a probe data packet to a target identification resolution server and monitoring the response time, when the response time exceeds a preset time threshold or no response data packet is received, it is determined that the target identification resolution server is unreachable, a backup path is selected from a backup server table to continue to perform the step-by-step query; dynamically adjusting the query path according to the current network topology state.

[0011] As preferred, the step-by-step query in the main domain resolution adopts a multi-level cache mechanism, which comprises: after completing the query, storing the mapping relationship between the level of the prefix part and the corresponding identification resolution server address or the digital object repository gateway address in the local cache; when performing the query, checking whether there is cache data corresponding to the level in the local cache; when there is cache data corresponding to the level in the local cache and it is not expired, using the cache data without performing actual query.

[0012] As preferred, the prefix part contains cross-domain access identification, which is used to indicate the access relationship between different industry domains or organization domains; in the main domain resolution: when the cross-domain access identification is detected, determining the cross-domain access path according to the pre-established inter-domain mapping relationship; the inter-domain mapping relationship contains direct mapping relationship and transfer mapping relationship, the transfer mapping relationship is used to realize the access of data resources between domains without direct access permission; performing permission decrement conversion according to the cross-domain access path; after completing the cross-domain access, recording the access log and updating the inter-domain mapping relationship.

[0013] As preferred, the resource resolution comprises: resolving the suffix part, extracting resource type identification and resource instance identification from the suffix part; determining the storage location and access mode of the target data resource according to the resource type identification; retrieving the target data resource from the digital object repository according to the resource instance identification; returning after format conversion and security processing of the retrieved target data resource.

[0014] In the second aspect, the application further provides a data resource positioning system based on identification resolution, comprising: an identification resolution module, configured to receive a data resource positioning request and separate a globally unique identification in the data resource positioning request into a prefix part and a suffix part; a main domain resolution module, configured to perform main domain resolution according to the prefix part; the main domain resolution determines a digital object repository gateway address corresponding to a data resource by step-by-step query in a digital object registry; a resource resolution module, configured to perform resource resolution according to the suffix part; the resource resolution sends the suffix part to the digital object repository gateway address, and a gateway corresponding to the digital object repository gateway address retrieves and returns a target data resource from a corresponding digital object repository according to the suffix part, while verifying access permission.

[0015] In a third aspect, the present application also provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the following steps when executing the computer program: receiving a data resource positioning request, separating a globally unique identifier in the data resource positioning request into a prefix part and a suffix part; the prefix part is used to determine a domain to which a data resource belongs, and the suffix part is used to identify a unique target data resource; performing primary domain resolution according to the prefix part; the primary domain resolution determines a digital object repository gateway address corresponding to the data resource by performing step-by-step query in a digital object registry, and the step-by-step query positions from a root node downward along a hierarchical structure of the prefix part; performing resource resolution according to the suffix part; the resource resolution sends the suffix part to the digital object repository gateway address, and a gateway corresponding to the digital object repository gateway address retrieves and returns the target data resource from a corresponding digital object repository according to the suffix part, while verifying access authority.

[0016] In a fourth aspect, the present application also provides a computer readable storage medium having a computer program stored thereon, wherein the computer program implements the following steps when executed by a processor: receiving a data resource positioning request, separating a globally unique identifier in the data resource positioning request into a prefix part and a suffix part; the prefix part is used to determine a domain to which a data resource belongs, and the suffix part is used to identify a unique target data resource; performing primary domain resolution according to the prefix part; the primary domain resolution determines a digital object repository gateway address corresponding to the data resource by performing step-by-step query in a digital object registry, and the step-by-step query positions from a root node downward along a hierarchical structure of the prefix part; performing resource resolution according to the suffix part; the resource resolution sends the suffix part to the digital object repository gateway address, and a gateway corresponding to the digital object repository gateway address retrieves and returns the target data resource from a corresponding digital object repository according to the suffix part, while verifying access authority.

[0017] The present application has the following beneficial effects: the present application provides a data resource positioning method and system based on identifier resolution, which separates a globally unique identifier into a prefix part and a suffix part, and adopts a two-level resolution architecture combining primary domain resolution and resource resolution, thereby solving the technical problem of efficient positioning of cross-domain data resources. The efficiency of data resource positioning is improved, and millisecond-level resource positioning response is achieved. The reliability of the system is enhanced, and the stability of the resolution service is ensured through reachability verification and dynamic path adjustment. Seamless access to data resources across industries and organizations is achieved, data silos are broken, and the sharing and circulation of data resources are promoted. At the same time, the security of cross-domain data access is ensured through the permission decrement conversion mechanism. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other related drawings can be obtained without creative labor based on these drawings.

[0019] Figure 1 is the overall flowchart of a data resource positioning method based on identification analysis related to the present application;

[0020] Figure 2 is the overall structure schematic diagram of a data resource positioning system based on identification analysis related to the present application;

[0021] Figure 3 is the computer device diagram of a data resource positioning method based on identification analysis related to the present application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solutions and advantages of the present application more clear, the present application will be further described in detail below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

[0023] The present application provides a data resource positioning method based on identification analysis, which includes the following steps S100 to S300, as shown in Figure 1

[0024] Step S100: receiving a data resource positioning request, separating the global unique identification in the data resource positioning request into a prefix part and a suffix part.

[0025] In the present embodiment, the data resource positioning request can be initiated by a user terminal and transmitted to an identification analysis system through a network. The data resource positioning request contains the global unique identification of the data resource to be positioned, which is a code used to uniquely identify the data resource in a distributed environment.

[0026] The prefix part is used to determine the domain to which the data resource belongs, and the suffix part is used to identify the unique target data resource. The prefix part is equivalent to the "partition number" in the identification system, which is used to indicate the industry domain or organization domain to which the data resource belongs; the suffix part is equivalent to the unique resource identifier within a specific domain, which is used to accurately position the specific data resource.

[0027] ​Specifically, the global unique identifier in the data resource positioning request is separated into a prefix part and a suffix part, including: identifying a preset separator position in the global unique identifier; extracting a part before the preset separator as the prefix part; and extracting a part after the preset separator as the suffix part.

[0028] For example, the global unique identifier of a certain data resource can be “88.123.456 / resource.data”, where “ / ” is the preset separator, “88.123.456” is extracted as the prefix part, and “resource.data” is extracted as the suffix part. This separation manner enables the identifier analysis system to determine the management domain to which the data resource belongs according to the prefix, and then determine the specific data resource according to the suffix.

[0029] The prefix part has a hierarchical structure, and each level in the hierarchical structure is connected by a level separator. The level separator is different from the preset separator between the prefix part and the suffix part.

[0030] In this embodiment, the prefix part is designed in a hierarchical structure, and each level is connected by a level separator (such as “.”). The prefix and the suffix are separated by a different preset separator (such as “ / ”). This design enables the identifier system to implement multi-level analysis. For example, “88” in “88.123.456” can represent an industry classification, “123” can represent an organization category, and “456” can represent a specific organization code. The distinction between the level separator and the preset separator enables the system to clearly distinguish the hierarchical structure of the identifier and the boundary between the prefix and the suffix.

[0031] For example, in a specific application scenario, a user needs to access a medical data stored in a distributed system. The user terminal sends a data resource positioning request, which contains a global unique identifier “10.25.789 / patient0012.record”. After receiving the request, the identifier analysis system first identifies the position of the preset separator “ / ”, then extracts “10.25.789” before the separator as the prefix part, and extracts “patient0012.record” as the suffix part. The hierarchical structure of the prefix part “10.25.789” is connected by the level separator “.”, where “10” represents the medical industry, “25” represents the hospital category, and “789” represents a specific hospital code.

[0032] By separating the global unique identifier into a prefix part and a suffix part, the application can realize hierarchical resolution and improve resolution efficiency. The prefix part is used to determine the domain to which the data resource belongs, which is equivalent to narrowing the search range in a broad data resource space; the suffix part is used to accurately locate the target data resource in a specific domain. This hierarchical mechanism greatly improves the positioning efficiency in a massive distributed data environment.

[0033] S200: performing main domain resolution according to the prefix part; the main domain resolution determines the digital object repository gateway address corresponding to the data resource by querying the digital object registry level by level, and the level-by-level query locates from the root node downward along the hierarchical structure of the prefix part.

[0034] After separating the global unique identifier into a prefix part and a suffix part in step S100, the main domain resolution phase is entered. The purpose of the main domain resolution is to determine the gateway address of the storage location of the target data resource. This process needs to be implemented with the help of the digital object registry, which is responsible for storing and maintaining the mapping relationship between the identification prefix and the digital object repository gateway address.

[0035] In this embodiment, the main domain resolution adopts a level-by-level query mechanism, which starts from the root node, locates layer by layer downward along the hierarchical structure of the prefix part, and finds the digital object repository gateway address where the target data resource is located.

[0036] Specifically, the level-by-level query includes: obtaining the identification resolution server address of the second level in the root node identification resolution server according to the first level of the prefix part; obtaining the identification resolution server address of the third level in the second level identification resolution server according to the second level of the prefix part; and obtaining the identification resolution server address of the next level in the corresponding identification resolution server according to each subsequent level of the prefix part.

[0037] Taking the aforementioned example "10.25.789" as an example, first, the address of the medical industry identification resolution server is obtained by querying the root node identification resolution server according to the first level "10" (representing the medical industry); then the identification resolution server address of the hospital of this category is obtained by querying the medical industry identification resolution server according to the second level "25" (representing the hospital category); finally, the digital object repository gateway address of the hospital is obtained by querying the identification resolution server of the hospital of this category according to the third level "789" (representing the specific hospital code). This level-by-level query mechanism ensures that even in a massive data resource environment, the gateway where the target resource is located can be quickly located.

[0038] To improve the reliability and stability of the resolution, the embodiment performs reachability verification on each identity resolution server accessed in the step-by-step query process. The reachability verification includes sending a probe data packet to the target identity resolution server and monitoring the response time. When the response time exceeds a preset time threshold or no response data packet is received, it is determined that the target identity resolution server is unreachable, and a backup path is selected from the backup server table to continue the step-by-step query; the query path is dynamically adjusted according to the current network topology state.

[0039] Reachability verification is an important mechanism to ensure the stability of resolution. In the actual network environment, the identity resolution server may be temporarily unavailable due to network fluctuations, hardware failures, or system maintenance. The reachability verification in the embodiment detects the state of the target server by sending a probe data packet (such as an ICMP request or a specific application layer probe message). A response time threshold (such as 500 milliseconds) is preset here. When the monitored response time exceeds the threshold or no response data packet is received at all, it is determined that the server is unreachable.

[0040] After determining that the server is unreachable, the resolution process does not interrupt, but selects an alternative path from the pre-configured backup server table. The backup server table stores multiple backup resolution server addresses for each level, sorted by reliability. The highest ranked available backup server in the current level is selected to continue the query. This mechanism ensures that the entire resolution process can be successfully completed even if some resolution servers are unavailable.

[0041] In addition, the embodiment also dynamically adjusts the query path according to the current network topology state. By periodically collecting network state information (such as delay between nodes, bandwidth utilization, and connection state, etc.), a real-time network topology graph is constructed. When performing step-by-step query, reference is made to this topology graph to select the optimal query path in the current network environment, such as preferentially selecting links with lower delay and sufficient bandwidth. This dynamic adjustment mechanism enables the resolution process to adapt to changing network environments, improving resolution efficiency and success rate.

[0042] The step-by-step query in the main domain resolution adopts a multi-level cache mechanism, which includes: after completing the query, the mapping relationship between the prefix part level and the corresponding identity resolution server address or digital object repository gateway address is stored in the local cache; when performing the query, it is checked whether there is cache data corresponding to the level in the local cache; when there is cache data corresponding to the level in the local cache and it has not expired, the cache data is used instead of performing actual query.

[0043] Multi-level cache mechanism is an important means to improve the resolution efficiency. In practical applications, users often access different resources under the same domain multiple times in a short period of time, or multiple users access the same domain resources. Through the cache mechanism, repeated queries can be significantly reduced, network load can be reduced, and response speed can be improved.

[0044] The multi-level cache used in this embodiment includes a local cache and a distributed cache of each level of identification resolution server. When a complete step-by-step query is completed, the mapping relationship between each level of the prefix part and the corresponding resolution server address (or the final gateway address) is stored in the local cache. The cache entry contains mapping information, cache time, and expiration period, and other data. The expiration period can be dynamically set according to the resource type, domain characteristics, and network environment, and is usually several minutes to several hours.

[0045] When performing a query subsequently, it is first checked whether the local cache contains cache data of the corresponding level. If valid cache data (i.e., not expired) is found, the cache data is directly used to avoid actual network query, thereby greatly reducing the resolution delay. For example, if the mapping relationship of the prefix "10.25" is already in the cache, the query of the root node and the medical industry identification resolution server can be skipped, and the query can be directly started from the hospital category resolution server.

[0046] In order to handle some relatively complex cross-domain access scenarios, the embodiment provides a cross-domain resolution mechanism: the prefix part contains a cross-domain access identifier, the cross-domain access identifier is used to indicate the access relationship between different industry domains or organization domains; in the main domain resolution: when the cross-domain access identifier is detected, the cross-domain access path is determined according to the pre-established inter-domain mapping relationship; the inter-domain mapping relationship includes a direct mapping relationship and a transfer mapping relationship, the transfer mapping relationship is used to realize the data resource access between domains without direct access permission; the permission decrement conversion is performed according to the cross-domain access path; after completing the cross-domain access, the access log is recorded and the inter-domain mapping relationship is updated.

[0047] In practical applications, data resources often need to be shared between different industry domains or organization domains. The embodiment supports such cross-domain access requirements by including a cross-domain access identifier in the prefix part. The cross-domain access identifier can be a specific symbol or coding mode, for example, using the "+" symbol to connect the identifiers of different domains in the prefix, such as "10+30.45", which indicates accessing a specific organization (45) under the financial industry (30) from the medical industry (10).

[0048] When the cross-domain access identifier is detected, a pre-established inter-domain mapping table is queried. This table stores access permissions and routing rules between different domains, including two types of mapping relationships: direct mapping relationship and transitive mapping relationship. Direct mapping relationship refers to the access channel directly established between two domains without the need for intermediate domain forwarding; transitive mapping relationship refers to the indirect access channel established through one or more intermediate domains, suitable for data sharing between domains without direct access permissions.

[0049] For example, if the medical industry (10) and the financial industry (30) do not have a direct mapping relationship, but they both have a direct mapping relationship with the government regulatory domain (20), then a transitive mapping relationship can be used to achieve access to the financial industry data by the medical industry through the government regulatory domain as an intermediary, i.e., the access path "10→20→30.45".

[0050] After determining the cross-domain access path, permission reduction conversion is performed. This is a security mechanism to ensure that access permissions are gradually reduced during cross-domain data transmission. Specifically, when data is transmitted from the source domain to the target domain, access permissions are adjusted according to inter-domain protocols and security policies, usually taking the intersection of the source domain's permissions and the target domain's allowed maximum permissions. This prevents users of high-privilege domains from obtaining excessively high access permissions in low-privilege domains.

[0051] After completing cross-domain access, detailed access logs are recorded, including access time, source domain, target domain, resource identifier, access path, user information, and operation type. These logs are crucial for security audits, problem troubleshooting, and performance optimization. At the same time, inter-domain mapping relationships are updated based on access conditions, such as adjusting access frequency statistics, updating path weights, and optimizing cache strategies, to provide more efficient services for subsequent cross-domain access.

[0052] Through the above mechanisms, the main domain resolution process of this embodiment can efficiently and reliably determine the digital object repository gateway address of the data resource, laying the foundation for subsequent resource resolution.

[0053] S300: Perform resource resolution according to the suffix part; the resource resolution sends the suffix part to the digital object repository gateway address, and the gateway corresponding to the digital object repository gateway address retrieves and returns the target data resource from the corresponding digital object repository according to the suffix part, while verifying access permissions.

[0054] After completing the main domain resolution and obtaining the digital object repository gateway address, the resource resolution phase is entered. Resource resolution is the final link of the identifier resolution process, responsible for accurately locating and obtaining the target data resource from the specific digital object repository according to the suffix part.

[0055] The resource resolution first needs to send the suffix part in the globally unique identifier to the primary domain resolution determined digital object repository gateway. The gateway serves as a bridge connecting external requests and internal data repositories, responsible for request forwarding, permission control, and resource access functions. After receiving the suffix part, the gateway will determine the specific operation process according to the internal mapping rules, including permission verification, resource location, and data acquisition.

[0056] Specifically, resource resolution includes: parsing the suffix part, extracting resource type identifier and resource instance identifier from the suffix part; determining the storage location and access method of the target data resource according to the resource type identifier; retrieving the target data resource from the digital object repository according to the resource instance identifier; and returning after format conversion and security processing of the retrieved target data resource.

[0057] The first step is to parse the suffix part. In this embodiment, the suffix part contains two key pieces of information: resource type identifier and resource instance identifier. These two pieces of information may be combined in a specific format, such as "patient0012.record", where "record" represents the resource type (medical record) and "patient0012" represents the number of a specific patient (resource instance). The digital object repository gateway will identify and extract these two pieces of information according to the preset parsing rules.

[0058] The resource type identifier is the category information of the data resource, such as documents, images, videos, datasets, etc. In large organizations, different types of data may be stored in different physical or logical locations, using different storage technologies and access methods. For example, structured data may be stored in a relational database, unstructured data may be stored in an object storage system, and streaming media content may be located on a dedicated media server.

[0059] According to the extracted resource type identifier, the digital object repository gateway determines the specific storage location and appropriate access method of the target data resource. This step involves querying the internal resource type mapping table, which maintains the correspondence between resource types and storage locations, access protocols, data formats, etc. For example, for "record" type resources, the system may determine that it is stored in a medical record database, needs to use SQL query language to access, and the data is stored in encrypted XML format.

[0060] Next, according to the resource instance identifier, the target data resource is retrieved from the determined storage location. The resource instance identifier is usually a unique identifier of the data resource in its storage system, such as a database record ID, file name, or object key value. The digital object repository constructs an appropriate query or access request according to this identifier and the previously determined storage location, accurately locates and acquires the target data resource.

[0061] Access permission verification is performed simultaneously during the retrieval process. Permission verification is a key link to ensure data security, including identity authentication and authorization check. Identity authentication confirms the identity of the requester, which can be achieved through digital certificates, tokens or credentials; authorization check determines whether the requester has the right to access the target resource, usually based on access control list (ACL), role permission or policy rules mechanism. Only requests that pass the permission verification can obtain the target data resource, otherwise a permission denied response will be returned.

[0062] Finally, the successfully retrieved target data resource is returned to the requester after format conversion and security processing. Format conversion refers to converting data into appropriate formats according to the needs of the requester or the compatibility requirements of the system. For example, converting database records to JSON format, or converting proprietary format documents to standard PDF files. Security processing includes data desensitization, encrypted transmission, digital signature and other measures to ensure the integrity and confidentiality of data during transmission.

[0063] Taking medical record query as an example, assuming that the hospital's digital object repository gateway address is determined after completing the primary domain resolution, the resource resolution stage will send the suffix part "patient0012.record" to the gateway. The gateway first resolves the suffix and identifies that it is a query for the medical records of "patient0012". Then it determines that such records are stored in the electronic medical record system and need to be accessed through a specific API. Then it verifies whether the requester has the right to access the patient's records, such as doctors can only access their own patient's records, while hospital administrators may have more extensive access rights. After verification, the patient's records are retrieved from the electronic medical record system and converted to appropriate formats (such as HL7 standard format or PDF document) according to the request requirements, and finally returned to the requester after encryption.

[0064] Through the above resource resolution process, the embodiment realizes accurate positioning and secure access to data resources in a distributed environment, completing the complete resolution process from global unique identification to specific data resources.

[0065] The application solves the technical problem of accurate positioning of massive heterogeneous data resources through the hierarchical processing mechanism of primary domain resolution and resource resolution, adopts the technical means of prefix hierarchical query and suffix accurate matching, realizes unified management and efficient access of data resources, improves the efficiency of data sharing and exchange, and guarantees the security of data access.

[0066] It should be understood that although the steps in the flowcharts involved in the embodiments described above are shown in sequence according to the arrows, the steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, the execution of the steps is not strictly limited in sequence, and the steps can be executed in other orders. Moreover, at least some of the steps in the flowcharts involved in the embodiments described above can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of the steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least part of other steps or steps or stages in other steps.

[0067] Based on the same inventive concept, the embodiments of the present application also provide a data resource positioning system based on identification resolution. The implementation scheme for solving the problem provided by the system is similar to the implementation scheme described in the above method, so the specific limitations in one or more data resource positioning systems based on identification resolution provided below can refer to the limitations of the data resource positioning method based on identification resolution in the above, which will not be repeated here.

[0068] In an exemplary embodiment, as shown in Figure 2 A data resource positioning system based on identification resolution is provided, comprising:

[0069] An identification resolution module is configured to receive a data resource positioning request and separate a globally unique identifier in the data resource positioning request into a prefix part and a suffix part.

[0070] A primary domain resolution module is configured to perform primary domain resolution according to the prefix part. The primary domain resolution determines the digital object repository gateway address corresponding to the data resource by querying the digital object registry level by level.

[0071] A resource resolution module is configured to perform resource resolution according to the suffix part. The resource resolution sends the suffix part to the digital object repository gateway address, and the gateway corresponding to the digital object repository gateway address retrieves and returns the target data resource from the corresponding digital object repository according to the suffix part, while verifying the access right.

[0072] The modules in the above data resource positioning system based on identification resolution can be all or part of software, hardware and their combinations. The above modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory in the computer device in software form, so as to be called and executed by the processor to perform the operations corresponding to the above modules.

[0073] In an exemplary embodiment, a computer device, which can be a terminal, is provided, and an internal structure diagram of the computer device can be as shown in FIG. 1. Figure 3 The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for running the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is configured to exchange information between the processor and external devices. The communication interface of the computer device is configured to perform wired or wireless communication with external terminals. The wireless communication can be achieved through Wi-Fi, mobile cellular network, Near Field Communication (NFC) or other technologies. The computer program is executed by the processor to implement a data resource positioning method based on identification resolution. The display unit of the computer device is configured to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer overlaid on the display screen, or a key, trackball or touchpad arranged on the shell of the computer device, or an external keyboard, touchpad or mouse, etc.

[0074] Those skilled in the art can understand that Figure 3 The structure shown in the above embodiment is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can include more or fewer components than those shown in the diagram, or combine certain components, or have a different arrangement of components.

[0075] In an embodiment, a computer device is also provided, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0076] In an embodiment, a computer readable storage medium is provided, which stores a computer program. The computer program is executed by a processor to implement the steps in the above method embodiments.

[0077] In an embodiment, a computer program product is provided, which includes a computer program. The computer program is executed by a processor to implement the steps in the above method embodiments.

[0078] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations.

[0079] It can be understood by those skilled in the art that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments of each method. In the embodiments provided in the present application, any reference to memory, database or other medium can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0080] Any technical features in the above embodiments can be combined, and for the sake of brevity, not all possible combinations are described above, however, any combination of these technical features is deemed to be within the scope of the present application.

[0081] The above embodiments only express several implementation manners of the present application, and the description is relatively specific and detailed, but it should not be understood as a limitation on the patent scope of the present application. It should be pointed out that, for ordinary skilled persons in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A data resource location method based on identity resolution, characterized in that: include: receiving a data resource location request, and separating a globally unique identifier in the data resource location request into a prefix portion and a suffix portion; The prefix part is used to determine the domain to which the data resource belongs, and the suffix part is used to identify a unique target data resource; Performing primary domain resolution based on the prefix portion; the primary domain resolution determines the digital object repository gateway address corresponding to the data resource by querying the digital object registry level by level, the querying being located downward from the root node along the hierarchical structure of the prefix portion; Perform resource resolution based on the suffix part; the resource resolution sends the suffix part to the digital object repository gateway address, and the gateway corresponding to the digital object repository gateway address retrieves and returns the target data resource from the corresponding digital object repository based on the suffix part, and verifies access rights at the same time; The prefix part includes a cross-domain access identifier, and the cross-domain access identifier is used to indicate the access relationship between different industry domains or organizational domains; In the primary domain resolution: when the cross-domain access identifier is detected, a cross-domain access path is determined according to a pre-established inter-domain mapping relationship; the inter-domain mapping relationship includes a direct mapping relationship and a transfer mapping relationship, the transfer mapping relationship being used to implement data resource access between domains without direct access rights; and permission reduction conversion is performed according to the cross-domain access path; After completing the cross-domain access, recording the access log and updating the inter-domain mapping relationship; The resource parsing includes: parsing the suffix part, extracting the resource type identifier and resource instance identifier from the suffix part; determining the storage location and access method of the target data resource based on the resource type identifier; retrieving the target data resource from the digital object warehouse based on the resource instance identifier; and performing format conversion and security processing on the retrieved target data resource before returning it.

2. The data resource location method based on identity resolution according to claim 1, characterized in that: The separating of the globally unique identifier in the data resource location request into a prefix part and a suffix part includes: identifying a preset separator position in the globally unique identifier; extracting the part before the preset separator as the prefix part; and extracting the part after the preset separator as the suffix part.

3. The data resource location method based on identity resolution according to claim 2, characterized in that: The prefix part has a hierarchical structure, and each level in the hierarchical structure is connected by a hierarchical separator, and the hierarchical separator is different from a preset separator between the prefix part and the suffix part.

4. The data resource location method based on identity resolution according to claim 3, characterized in that: The step-by-step query includes: obtaining the second-level identity resolution server address in the root node identity resolution server according to the first level of the prefix part; obtaining the third-level identity resolution server address in the second-level identity resolution server according to the second level of the prefix part; obtaining the next-level identity resolution server address in the corresponding identity resolution server according to each subsequent level of the prefix part; performing reachability verification on each identity resolution server accessed during the step-by-step query process, the reachability verification including sending a probe data packet to the target identity resolution server and monitoring the response time, when the response time exceeds a preset time threshold or no response data packet is received, determining that the target identity resolution server is unreachable, selecting a backup path from the backup server table to continue executing the step-by-step query; and dynamically adjusting the query path according to the current network topology status.

5. The data resource location method based on identity resolution according to claim 4, characterized in that: The level-by-level query in the primary domain resolution adopts a multi-level cache mechanism, which includes: after completing the query, storing the mapping relationship between the level of the prefix part and the corresponding identity resolution server address or the digital object warehouse gateway address in the local cache; when executing the query, checking whether there is cache data of the corresponding level in the local cache; when there is cache data of the corresponding level in the local cache and it has not expired, using the cache data without performing an actual query.

6. A data resource location system based on identity resolution, using the data resource location method based on identity resolution according to any one of claims 1 to 5, characterized in that: An identifier resolution module, configured to receive a data resource location request and separate a globally unique identifier in the data resource location request into a prefix portion and a suffix portion; A primary domain resolution module is configured to perform primary domain resolution based on the prefix portion; the primary domain resolution determines the digital object repository gateway address corresponding to the data resource by querying the digital object registry level by level; A resource resolution module is used to perform resource resolution based on the suffix part; the resource resolution sends the suffix part to the digital object warehouse gateway address, and the gateway corresponding to the digital object warehouse gateway address retrieves and returns the target data resource from the corresponding digital object warehouse based on the suffix part, and verifies access rights at the same time.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the data resource locating method based on identity resolution according to any one of claims 1 to 5 are implemented.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the data resource locating method based on identity resolution according to any one of claims 1 to 5 are implemented.

Images