CN114329091A

CN114329091A - Data directory generation method, device and equipment

Info

Publication number: CN114329091A
Application number: CN202111658097.1A
Authority: CN
Inventors: 张海生
Original assignee: Hangzhou Dt Dream Technology Co Ltd
Current assignee: Hangzhou Dt Dream Technology Co Ltd
Priority date: 2021-12-30
Filing date: 2021-12-30
Publication date: 2022-04-12
Also published as: WO2023124209A1

Abstract

The specification discloses a data directory generation method, a data directory generation device and data directory generation equipment. The method is applied to any local handle service in a cross-industry data system; the cross-industry data system comprises different local handle services respectively corresponding to different industry users; an original data directory is preset for an industry user corresponding to any local handle service; in the original data directory, different data objects respectively correspond to different original data identifiers; the method comprises the following steps: any local handle service acquires a corresponding handle prefix, and different local handle services in the cross-industry data system respectively correspond to different handle prefixes; and aiming at an original data directory preset by a corresponding industry user, splicing an original data identifier corresponding to each data object as a handle suffix with an acquired corresponding handle prefix to obtain a new data identifier corresponding to each data object, and generating a new data directory according to the obtained new data identifier.

Description

Data directory generation method, device and equipment

Technical Field

The embodiment of the specification relates to the field of retrieval, in particular to a data directory generation method, a data directory generation device and data directory generation equipment.

Background

At present, with the continuous development of informatization technology, a data directory meeting the industry standard is generally formed inside each industry, and the data retrieval inside the industry is facilitated.

With the development of big data, cross-industry data fusion between different industries is more and more needed, but data catalogs between different industries are difficult to summarize due to the fact that the specifications of the data catalogs between different industries are different.

Disclosure of Invention

In order to solve the technical problem, embodiments of the present specification provide a data directory generation method, apparatus, and device. The technical scheme is as follows.

A data directory generation method is applied to any local handle service in a cross-industry data system; the cross-industry data system comprises different local handle services respectively corresponding to different industry users; an original data directory is preset for an industry user corresponding to any local handle service; in the original data directory, different data objects respectively correspond to different original data identifiers; the method comprises the following steps:

any local handle service acquires a corresponding handle prefix, and different local handle services in the cross-industry data system respectively correspond to different handle prefixes;

and aiming at an original data directory preset by a corresponding industry user, splicing an original data identifier corresponding to each data object as a handle suffix with an acquired corresponding handle prefix to obtain a new data identifier corresponding to each data object, and generating a new data directory according to the obtained new data identifier.

Optionally, the method further comprises:

and sending the obtained new data identifier to a global handle register, wherein the global handle register is used for summarizing the new data identifier obtained by each local handle service in the cross-industry data system.

Optionally, the obtaining, by any local handle service, a corresponding handle prefix includes:

any local handle service acquires a handle prefix applied by a corresponding industry user as a corresponding handle prefix, and the applied handle prefix uniquely corresponds to the industry user.

Optionally, the method further comprises:

updating catalog metadata information according to information of corresponding industry users aiming at an original data catalog preset by the corresponding industry users;

the generating of the new data directory according to the obtained new data identifier includes:

generating a new data directory according to the updated directory metadata information and the obtained new data identifier;

the generated directory metadata information of the new data directory is updated directory metadata information, and the directory number is the obtained new data identifier.

A data retrieval method based on the above data directory generation method is applied to management equipment; the management equipment is newly added equipment aiming at the cross-industry data system;

the data retrieval method comprises the following steps:

receiving a retrieval request sent by a target user, wherein the retrieval request at least comprises retrieval conditions; the retrieval request is used for requesting to acquire a data object meeting the retrieval conditions;

searching a target local handle service capable of responding to the retrieval request;

and searching the data object which meets the searching condition aiming at the new data directory of the searched target local handle service, and returning the searching result to the target user.

Optionally, the management device stores a first set of correspondence between an identifier of a local handle service in the cross-industry data system and corresponding industry user information;

the searching for the target local handle service capable of responding to the retrieval request comprises the following steps: and under the condition that the retrieval request contains any industry user information, searching a local handle service identifier corresponding to the contained industry user information in the stored first corresponding relation set, and determining the local handle service corresponding to the searched local handle service identifier as a target local handle service.

Optionally, the management device stores a second set of correspondence between an identifier of a local handle service in the cross-industry data system and a corresponding handle prefix;

the searching for the target local handle service capable of responding to the retrieval request comprises the following steps: and under the condition that the retrieval request comprises the target data identification, searching a local handle service identification corresponding to the handle prefix in the target data identification in the stored second corresponding relation set, and determining the local handle service corresponding to the searched local handle service identification as the target local handle service.

Optionally, the global handle registration stores a third correspondence set between the identifier of the local handle service in the cross-industry data system and the obtained new data identifier;

the searching for the target local handle service capable of responding to the retrieval request comprises the following steps:

and under the condition that the retrieval request comprises the target data identifier, the management device searches a local handle service identifier corresponding to the target data identifier from the third corresponding relation set registered by the global handle, and determines the local handle service corresponding to the searched local handle service identifier as the target local handle service.

Optionally, the method further comprises:

and under the condition that the target local handle service capable of responding to the retrieval request cannot be found, retrieving the data object meeting the retrieval condition aiming at the new data directory of each local handle service in the cross-industry data system, and returning the retrieval result to the target user.

Optionally, the management device stores directory metadata information of a new data directory generated by a local handle service in the cross-industry data system;

the returning of the retrieval result to the target user comprises:

determining directory metadata information of a new data directory generated by the target local handle service in case that the retrieval result includes any data object;

and displaying the data object contained in the retrieval result to the target user by combining the determined directory metadata information.

Optionally, the management device is configured to receive a new data directory generated by a local handle service in the cross-industry data system, and merge the received new data directories of different local handle services into the cross-industry data directory.

A data directory generation device is applied to any local handle service in a cross-industry data system; the cross-industry data system comprises different local handle services respectively corresponding to different industry users; an original data directory is preset for an industry user corresponding to any local handle service; in the original data directory, different data objects respectively correspond to different original data identifiers; the device comprises:

the acquisition unit is used for acquiring corresponding handle prefixes, and different local handle services in the cross-industry data system respectively correspond to different handle prefixes;

and the splicing unit is used for splicing the original data identifier corresponding to each data object as a handle suffix with the acquired corresponding handle prefix aiming at the original data directory preset by the corresponding industry user to obtain a new data identifier corresponding to each data object, and generating a new data directory according to the obtained new data identifier.

Optionally, the apparatus further comprises:

and the sending unit is used for sending the obtained new data identifier to a global handle register, and the global handle register is used for summarizing the new data identifier obtained by each local handle service in the cross-industry data system.

Optionally, the obtaining unit is configured to: and acquiring the handle prefix applied by the corresponding industry user as the corresponding handle prefix, wherein the applied handle prefix is uniquely corresponding to the industry user.

Optionally, the apparatus further comprises:

the updating unit is used for updating the catalog metadata information according to the information of the corresponding industry user aiming at the original data catalog preset by the corresponding industry user;

the splicing unit is used for: generating a new data directory according to the updated directory metadata information and the obtained new data identifier;

A data retrieval device based on the data catalog generating device is applied to management equipment; the management equipment is newly added equipment aiming at the cross-industry data system;

the device comprises:

the system comprises a receiving unit, a searching unit and a searching unit, wherein the receiving unit is used for receiving a searching request sent by a target user, and the searching request at least comprises a searching condition; the retrieval request is used for requesting to acquire a data object meeting the retrieval conditions;

the searching unit is used for searching a target local handle service capable of responding to the searching request;

and the result unit is used for searching the data object which meets the searching condition aiming at the new data directory of the searched target local handle service and returning the searching result to the target user.

the search unit is specifically configured to: and under the condition that the retrieval request contains any industry user information, searching a local handle service identifier corresponding to the contained industry user information in the stored first corresponding relation set, and determining the local handle service corresponding to the searched local handle service identifier as a target local handle service.

the search unit is specifically configured to: and under the condition that the retrieval request comprises the target data identification, searching a local handle service identification corresponding to the handle prefix in the target data identification in the stored second corresponding relation set, and determining the local handle service corresponding to the searched local handle service identification as the target local handle service.

the search unit is specifically configured to:

Optionally, the apparatus further comprises:

and the returning unit is used for searching the data object which meets the searching condition aiming at the new data directory of each local handle service in the cross-industry data system under the condition that the target local handle service which can respond to the searching request cannot be found, and returning the searching result to the target user.

the result unit is to: determining directory metadata information of a new data directory generated by the target local handle service in case that the retrieval result includes any data object; and displaying the data object contained in the retrieval result to the target user by combining the determined directory metadata information.

According to the technical scheme, the handle prefix which is globally unique in the cross-industry data system and corresponds to one local handle service is spliced with the original data identifier which is unique in the local handle service and corresponds to one data object, so that the new data identifier which is unique in the cross-industry data system and corresponds to one data object is obtained, and therefore the new data catalog generated by different industries in the cross-industry data system based on the new data identifier can be conveniently collected subsequently.

Drawings

In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present specification, and other drawings can be obtained by those skilled in the art according to the drawings.

Fig. 1 is a schematic flowchart of a data directory generation method provided in an embodiment of the present specification;

fig. 2 is a schematic flow chart of a data retrieval method provided in an embodiment of the present specification;

FIG. 3 is a schematic diagram illustrating a data retrieval method according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a data directory generation apparatus provided in an embodiment of the present specification;

fig. 5 is a schematic structural diagram of a data retrieval device provided in an embodiment of the present specification;

fig. 6 is a schematic structural diagram of an apparatus for configuring a method according to an embodiment of the present disclosure.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments derived by one of ordinary skill in the art from the embodiments given herein are intended to fall within the scope of the disclosure.

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 invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, 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 invention. As used in this specification 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 is to be understood that although the terms first, second, third, etc. may be used herein to describe various objects, this information should not be limited to these terms. These terms are only used to distinguish objects of the same type from each other. For example, a first object may also be referred to as a second object, and similarly, a second object may also be referred to as a first object, without departing from the scope of the present invention. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

For example, for the patent industry, a data directory inside the industry is usually formed according to the numbering specification of the patent number, so that data retrieval is convenient for a patent, and a unique corresponding patent file can be specifically and directly searched according to the patent number.

Aiming at the retail industry, the commodity code can be generally used as a numbering specification to form a data catalogue in the retail industry, so that the unique corresponding commodity data in the retail industry can be conveniently and quickly retrieved according to the commodity code.

For the publishing industry, the version number can be used as a numbering specification to form a data directory in the publishing industry, so that unique corresponding books can be conveniently and quickly searched according to the version number.

With the development of big data, cross-industry data fusion between different industries is more and more in demand, but because the specifications of data directories between different industries are different, repeated directory numbers may exist, so that the data directories between different industries are difficult to summarize.

For ease of understanding, an example of cross-industry data fusion is given below. For example, in a department store, publications, home appliances, electronic products, and the like are sold in addition to retail products, and product data of different industries are usually merged for facilitating retrieval of goods, wherein the product data includes products in different industries and are uniformly numbered, so that a goods number uniquely corresponds to one goods in the department store.

When data fusion is carried out in the publishing industry and the retail industry, due to the fact that the commodity code is usually in an industry internal agreed format, repeated numbers can exist with the edition number, if the catalog number in the industry is directly used as the commodity number of a department supermarket, the commodity code cannot uniquely correspond to one commodity, a publication and the commodity can be searched through one commodity number, and therefore the data catalog is difficult to form when cross-industry data fusion is carried out.

Through the analysis of the problems, the directory number in the industry only corresponds to one data object in the industry, and when cross-industry data fusion is carried out, the directory number still only corresponds to one data object after the data fusion, so that a data directory can be conveniently formed.

One approach is to select only non-repeating directory numbers for cross-industry data fusion, but this approach would result in a reduction of data objects in the industry; the other method is to uniformly number all data objects subjected to cross-industry data fusion, but the method consumes more resources and modifies the original data directory in the industry.

In order to solve the above problem, an embodiment of the present specification provides a data directory generation method.

In the method, the original data directory inside the industry is considered to be formed and uniquely corresponds to one data object inside the industry, so that a uniquely corresponding identification prefix can be directly allocated to the industry, the target number of the data directory inside the industry is used as an identification suffix, the identification prefix and the identification suffix are spliced, and the obtained splicing result is the identification.

Even if the target numbers of the internal data directories in different industries have repeated numbers, the identification prefixes in the corresponding splicing results are different due to different industries, so that the splicing results can still uniquely correspond to the data objects in the industries after cross-industry data fusion, and a new data directory is conveniently formed.

For example, a merchandise code exists 111 in the retail industry and a version number also exists 111 in the publishing industry. While a unique corresponding identification prefix 10 is assigned for the retail industry and a unique corresponding identification prefix 11 is assigned for the publishing industry. After splicing, aiming at the repeated catalog number, the commodity code 111 in the retail industry is modified into 10111, and the version number 111 in the publishing industry is modified into 11111, so that different splicing results can be obtained, and the data objects uniquely correspond to one industry.

The method can reuse the original data directory in the industry, obtains the splicing result which uniquely corresponds to one data object across the industry by simply distributing the uniquely corresponding identification prefix to the industry and further simply splicing, thereby saving resources, facilitating the generation of the data directory across the industry, having small change on the original data directory in the industry, having no need of reducing the data object and improving the generation efficiency of the data directory.

In addition, aiming at a new industry needing cross-industry data fusion, a unique corresponding identification prefix can be directly distributed, and the expandability is strong.

In the method, Local Handle Service (Local Handle Service) and Global Handle registration (Global Handle registration) in the Handle system can be directly used to help generate the data directory, and the development efficiency is further improved. It should be noted that both the local handle service and the global handle registration may be regarded as a server or a service function deployed on the server.

Specifically, a Data Object Architecture (DOA) may be utilized to help produce the data directory, and a local handle service and a global handle registration structure and an interaction protocol, such as doip (Digital Object Interface protocol) and DO-irp (Digital Object Identifier Resolution protocol), may be utilized to further improve development efficiency. The DOIP is used for stipulating an interactive protocol between a client and a server, and the DO-IRP is based on an early Handle System and is used for stipulating the creating, modifying and analyzing processes of a digital object.

In addition, after the data directory is generated according to the method, cross-industry data retrieval capability can be further conveniently provided, and the subsequent cross-industry data retrieval is convenient according to the data directory obtained by cross-industry fusion.

A data directory generation method provided in the embodiments of the present specification is explained in detail below with reference to the accompanying drawings. Fig. 1 is a schematic flow chart of a data directory generation method provided in an embodiment of the present disclosure. The method can be applied to any local handle service in a cross-industry data system.

Wherein the cross-industry data system may include different local handle services corresponding to different industry users, respectively.

In an optional embodiment, a plurality of different merchants may exist in a single industry, even if uniform numbering specifications are formed among the merchants in the industry, product data produced by each merchant is usually difficult to share, cross-industry data fusion is facilitated, more data objects are integrated to facilitate subsequent retrieval, data of a plurality of merchants need to be integrated, and therefore local handle service needs to be deployed for each merchant.

Moreover, for the interior of the industry which does not unify the numbering specifications, the product numbers generated by different merchants may be repeated. For this case, each merchant needs to be assigned an identification prefix separately.

For ease of description, individual merchants are referred to as industry users, a single industry user uniquely corresponding to an industry may maintain portions of data objects in the industry, and an industry may correspond to one or more industry users.

In another alternative embodiment, one industry user may uniquely correspond to one industry, and different industry users correspond to different industries, so as to avoid resource waste of the identification prefix due to repeated allocation of different identification prefixes to different merchants in the industry under the condition that a uniform numbering specification is formed in the industry.

Alternatively, the industry user may be a data integration platform within the industry, which may interface with multiple merchants within the industry, thereby facilitating integration of directory numbers for multiple merchants.

Therefore, optionally, since one industry user uniquely corresponds to one industry, and different industry users correspond to different industries, the cross-industry data system may include different local handle services respectively corresponding to different industries, and an industry corresponding to any one local handle service is preset with an original data directory.

In an optional embodiment, an industry user may actively request to participate in cross-industry data fusion, and after a local handle service in a cross-industry data system is deployed, the industry user may construct a corresponding relationship with the local handle service, so as to generate a new data directory based on the local handle service, and obtain a globally unique directory number after the cross-industry data fusion.

Optionally, an original data directory may be preset for an industry user corresponding to any local handle service; in the original data directory, different data objects respectively correspond to different original data identifiers. In other words, in the original data directory, the original data identification uniquely corresponds to one data object.

It should be noted that the following method flow is only executed by any local handle service in the cross-industry data system, and each local handle service in the cross-industry data system can execute the following method flow to generate a new data directory, and a directory number in the new data directory globally and uniquely corresponds to one data object in the cross-industry data system.

The method may include the following steps.

S101: any local handle service obtains a corresponding handle prefix.

Optionally, different local handle services in the cross-industry data system correspond to different handle prefixes, respectively. A handle prefix in a cross-industry data system uniquely corresponds to one local handle service.

The method for acquiring the handle prefix by the local handle service is not limited in the process of the method, and the method can be directly acquired from the local or can be applied to allocate the corresponding handle prefix.

Optionally, the local handle service may locally store a handle prefix that is applied for allocation in advance, or may directly apply for the handle prefix that is allocated in advance for the local handle service, and there is no need to apply for the handle prefix.

Optionally, the specific application may be an industry user application or a local handle service self-application.

Optionally, any local handle service acquiring a corresponding handle prefix may include: any local handle service acquires a handle prefix applied by a corresponding industry user as a corresponding handle prefix, and the applied handle prefix is uniquely corresponding to the industry user corresponding to the local handle service.

Optionally, any local handle service acquiring a corresponding handle prefix may include: any local handle service applies for acquiring a corresponding handle prefix, and the applied handle prefix uniquely corresponds to the local handle service.

In an alternative embodiment, the global handle registration may be used to manage the handle prefixes, and assign unique corresponding handle prefixes to local handle services or industry users applying for the handle prefixes. The global handle registration may store a corresponding relationship set between a handle prefix and a local handle service, or a corresponding relationship set between a handle prefix and an industry user.

Thus, optionally, applying for a handle prefix may include: and registering the unique corresponding handle prefix of the application to the global handle.

In an alternative embodiment, in the architecture of DOA, there is a DONA MPA member for maintaining global handle registration and assigning handle prefixes to various industry users.

S102: and aiming at an original data directory preset by a corresponding industry user, splicing the original data identifier corresponding to each data object as a handle suffix with the acquired corresponding handle prefix to obtain a new data identifier corresponding to the data object, and generating a new data directory according to the obtained new data identifier.

Optionally, since the corresponding handle prefix acquired by the local handle service is globally unique in the cross-industry data system, a globally unique concatenation result in the cross-industry data system can be obtained by concatenating the handle prefix with the original data identifier in the original data directory. Thus, the resulting new data identification uniquely corresponds to one data object in the cross-industry data system.

Optionally, the handle may be obtained by splicing the handle prefix and the handle suffix together, and the handle may be used as a new data identifier corresponding to the data object.

Optionally, since the new data identifier globally and uniquely corresponds to one data object in the cross-industry data system, the new data directory can be regarded as a part of the cross-industry data directory, and the cross-industry data directory is convenient to generate later.

Optionally, the flow of the method does not limit the storage location of the generated new data directory, and the new data directory may be stored in each local handle service in a distributed manner, that is, any local handle service is stored locally after the new data directory is generated, or the new data directory generated by each local handle service of the cross-industry data system may be synthesized.

In an alternative embodiment, because a local handle service in the handle system is used, the joined handle generally needs to be registered, and specifically, the joined handle may be registered with a global handle registration.

Optionally, the method flow may further include: s103: and sending the obtained new data identification to the global handle registration. Optionally, the global handle registration may be used to aggregate new data identifications obtained across various local handle services in the industrial data system.

Optionally, the global handle registration may register and store a handle (i.e., an obtained new data identifier) spliced by each local handle service in the cross-industry data system, and specifically, may store relevant information of the handle and the local handle service, for example, address information of the local handle service, so as to facilitate subsequent retrieval.

It should be noted that, alternatively, the global handle registration may be included in the cross-industry data system, or may not be included in the cross-industry data system.

In addition, when cross-industry data fusion is performed, metadata information of a data directory is unclear.

The metadata information may specifically be field information of the data object. Since a uniform specification may be formed inside an industry, a meaning can be uniquely represented for a partial field inside the industry, but in a cross-industry scenario, partial field information may be ambiguous in the cross-industry scenario due to the different specifications of different industries.

For example, inside the vehicle industry, the "identification" field may unambiguously characterize the identification of the vehicle, but after cross-industry data fusion, the "identification" field itself has a broad meaning that may be misinterpreted by users of other industries as the identification of other products.

Also, there may be terms of identity that differ in their actual meaning between industries, e.g., within the software industry, "recall" may be used to measure performance of an algorithm, and within the retail industry, "recall" may be used to measure quality of a product.

Therefore, when performing cross-industry data fusion, it is also necessary to further clarify the actual meaning represented by metadata information between different industries without complying with the original uniform specification inside the industry.

For example, an "identification" field internal to the vehicle industry may be updated with "vehicle identification" for easy viewing by users of other industries.

Of course, if the original metadata information is already sufficient to represent the actual meaning, no update is necessary.

In an optional embodiment, S102 in the above method flow may further include: and updating the catalog metadata information aiming at the original data catalog preset by the corresponding industry user.

Optionally, the catalog metadata information may be specifically updated according to the information of the corresponding industry user for an original data catalog preset by the corresponding industry user.

The method for updating the directory metadata information is not particularly limited in the process flow, and the updated directory metadata information can show the actual business meaning and cannot be misunderstood by people in other industries.

As an exemplary illustration, the catalog metadata information may optionally be updated by business personnel of the corresponding industry user for a preset original data catalog. And specifically may be the actual meaning of the update to the catalog metadata information.

Optionally, since the metadata information of the uniform specification in the industry is usually ambiguous due to omission of the industry information, specifically updating the catalog metadata information may be to add information corresponding to the industry user on the basis of the catalog metadata information of the original data catalog. The information of the industry users can include at least industry information.

For example, for an "identification" field inside a vehicle industry user, vehicle industry information "vehicle" can be added to obtain "vehicle identification", so as to clarify the actual meaning of the field; aiming at the recall rate field in the software industry user, software industry information software algorithm can be added to obtain the software algorithm recall rate, so that the actual meaning of the field can be clarified.

Of course, since the industry user may be a merchant, the information corresponding to the industry user may also include a merchant brand.

In addition, the embodiment can also keep the directory metadata information in the original data directory, avoid modification as much as possible, and also can improve the updating efficiency.

Correspondingly, after updating the directory metadata information, a new data directory needs to be generated by using the updated directory metadata information.

Thus, optionally, generating a new data directory from the resulting new data identification may include: and generating a new data directory according to the updated directory metadata information and the obtained new data identifier, wherein the directory metadata information of the generated new data directory is the updated directory metadata information, and the directory number is the obtained new data identifier.

Through the embodiment, the problem caused by non-uniform metadata information specifications can be further solved in a cross-industry scene, and people in other industries in the cross-industry scene can conveniently understand the metadata information of one industry.

In a specific embodiment, in the DOA architecture, the Type mechanism provided by the DOA architecture can be used to redefine the directory metadata information, so as to facilitate generation of a new data directory according to the defined Type.

In addition, the corresponding handle prefix of the local handle service and the defined Type set (i.e., the updated directory metadata information) can be directly bound by means of a Type mechanism, so that the updated directory metadata information can be conveniently acquired subsequently. In addition, due to the fact that updating is carried out by means of the existing mechanism, development cost can be saved, and development efficiency is improved.

The process of the method is that a handle prefix which is globally and uniquely corresponding to a local handle service in the cross-industry data system is spliced with an original data identifier which is uniquely corresponding to a data object in the local handle service to obtain a new data identifier which is uniquely corresponding to the data object in the cross-industry data system, so that a new data directory can be generated according to the obtained new data identifier, a directory label in the new data directory can be uniquely corresponding to the data object in the cross-industry data system, cross-industry data fusion is facilitated, and cross-industry data directories are conveniently generated.

And because the original data identification is multiplexed, on one hand, the original data identification can be reserved as much as possible, the modification of the original data catalog is reduced, the original data catalog can be accessed rapidly without invasion, on the other hand, resources can be saved, the generation efficiency of the data catalog is improved, and the construction of the cross-industry data catalog is conveniently and rapidly completed.

In addition, by updating the directory metadata information, the interpretability of the directory metadata information in the cross-industry scene is improved, and people in other industries can conveniently understand the directory metadata information of a certain industry.

For ease of understanding, a specific application example is given below.

Global handle registration and local handle services may be included in the architecture of the DOA.

Global handle registration: maintained by the DONA MPA member and is responsible for distributing Handle prefixes for users in various industries.

Local handle service: maintained by industry users, the ability to submit catalog reports to GHS and implement DOIP services is needed.

The industry catalog: i.e., the original data catalog, may be maintained by an industry user, typically the original catalog system or asset management system within the industry.

The DO-IRP is the core of DOA, which is essentially a Key, Value database, providing the ability to resolve values according to Key. In DO-IRP, Key is also called handle, and the protocol specifies a handle format as follows: prefix/suffix, wherein prefixes are uniformly managed by MPA members, a prefix is allocated to only one user, and a suffix is managed by the user himself.

In DOA handles can be used to uniquely mark a digital object. Under the scene of a cross-industry data directory, the global directory number can be regarded as a handle, a prefix can be allocated to each industry user, and the internal directory number of the industry user is unique, so that the globally unique handle can be formed only by splicing the intra-industry directory number as a suffix.

This way a globally unique directory number is generated, non-intrusive to industry users.

Thus, specific steps may be as follows.

1. And the industry user applies the corresponding handle prefix to the MPA.

2. Industry users deploy local handle services within the corresponding industry.

3. An industry user defines the catalog metadata information for an industry catalog on a local handle service through a DOA Type mechanism.

4. Industry catalog information is obtained from an original data catalog or asset management system.

5. And importing the industry directory into the deployed local handle service, wherein a handle prefix is allocated by the MPA, and a suffix is an original industry directory number.

6. The local handle service registers the handle to the global handle registration via the handle protocol.

The DOA framework may be composed of global handle registration and local handle service, where the global handle registration aggregates all handle information, and the local handle service is used to store specific contents of digital objects corresponding to handles. The global handle registration can be considered as a large routing table, the mapping relationship from the handle to the local handle service is recorded, the position of the local handle service can be found through the handle subsequently, and then specific data corresponding to the handle is acquired from the local handle service.

In the scenario of a cross-industry data directory, aggregation of all directory numbers (handles) can be completed through global handle registration, and meanwhile, a specific industry directory can be stored by using a local handle service.

Aiming at the DOA Type mechanism, the DOA protocol does not care about the specific content of data, the DOA protocol gives the definition of the data format to a user, the DOIP protocol provides the Type mechanism, and the definition of the data format can be completed through the Type, so that an industry user can easily define the catalog metadata information of the industry through the Type mechanism, and the catalog aggregation can be completed with low cost.

The whole process is relatively simple. The development cost is low, the capacity of DOA is used, the rapid completion of the gathering work of the directories in each industry can be rapidly promoted, the directory numbers are gathered in the global handle registration, and the industry directories of users in each industry can be stored in each local handle service.

After the new data directory is generated by the method flow, the searching capability of cross-industry data can be provided according to the generated new data directory.

In an alternative embodiment, the global handle registration may store new data identifiers obtained across various local handle services in the industrial data system, so that the new data identifiers stored in the global handle registration may be retrieved.

Optionally, for a retrieval request including a new data identifier, the global handle registration may first determine whether the new data identifier included in the request exists, and in the case that the new data identifier exists, may further determine a corresponding local handle service, and continue to perform retrieval from the local handle service, obtain a data object corresponding to the new data identifier, and return the data object.

In other words, retrieval requests for different industries can be processed uniformly by global handle registration, and data retrieval capability across industries is provided.

Therefore, the embodiment of the present specification further provides a data retrieval method based on the above method flow, which can provide the retrieval capability of the cross-industry data according to the generated new data directory. Fig. 2 is a schematic flow chart of a data retrieval method provided in an embodiment of the present specification.

In an optional embodiment, since global handle registration is usually maintained by a member of the DONA MPA, development is usually difficult to perform, and for convenience of development, optionally, a management device may be added for the cross-industry data system, and the management device may interface a plurality of local handle services in the cross-industry data system to provide a retrieval capability of cross-industry data. Alternatively, the management device may be maintained by a management user, and the management user may specifically be a service party providing the retrieval capability.

The method can be applied to management equipment and specifically can comprise the following steps.

S201: receiving a retrieval request sent by a target user; the retrieval request includes at least a retrieval condition.

The retrieval request is used for requesting to acquire the data object which meets the contained retrieval condition.

Alternatively, the target user may be any user with retrieval requirements, such as an individual, a business, an organization, and so on. For ease of description, any user with a search requirement will be referred to as a target user.

S202: the target local handle service that can respond to the retrieval request is looked up.

Alternatively, the target local handle service capable of responding to the retrieval request may be a local handle service that may store data objects meeting the contained retrieval conditions, and specifically, the target local handle service may be a local handle service specified according to the retrieval request, or may be a local handle service meeting the retrieval conditions.

S203: and searching the data object which meets the searching condition aiming at the new data directory of the searched target local handle service, and returning the searching result to the target user.

The method flow does not limit the form of the retrieval request or the retrieval condition, and optionally, the target user may perform retrieval in the form of a retrieval formula or a keyword, etc. to generate the retrieval request and the retrieval condition.

Since the data directory itself can provide a retrieval capability, specifically, a data object meeting a retrieval condition can be retrieved according to the data directory, for example, a corresponding data object is directly retrieved according to a directory number (i.e., a new data identifier), or a data object having an attribute value is retrieved according to an attribute value of a data object (for example, an attribute value of a product type is an electronic product).

The method can quickly search by determining the target local handle service capable of responding to the search request by means of the search capability of the new data directory generated by the local handle service, thereby providing various search capabilities according to the new data directory of different local handle services, and further providing the search capability of cross-industry data.

In addition, because the management device serves as an intermediate party, on one hand, the management device is in butt joint with the local handle services, and on the other hand, the management device corresponds to the target users, so that connection resources can be saved, and connection between the target users and the local handle services is avoided being established independently aiming at each retrieval request. The management device may maintain connections with a number of local handle services, receiving retrieval requests of a number of target users.

In addition, the management device can provide the relevant information of the local handle service, and avoids the situation that the target user does not know the local handle service required to be retrieved or does not know the address information of the local handle service required to be retrieved, so that the connection cannot be established.

For a specific target local handle service capable of responding to the retrieval request, the method flow does not limit a specific implementation method, and as an exemplary description, the target local handle service may be searched according to the content included in the retrieval request.

In an alternative embodiment, the management device may store a first set of correspondence between the identity of the local handle service in the cross-industry data system and the corresponding industry user information.

Optionally, the first correspondence set may be obtained by the management device interacting with a number of local handle services that are docked, and the first correspondence set may include an identifier of one or more local handle services in the cross-industry data system.

Alternatively, the identifier of the local handle service may specifically be information uniquely corresponding to the local handle service, for example, address information of the local handle service, which may facilitate establishing a connection according to the address information of the local handle service, and specifically may be a physical address or an IP of the local handle service.

Optionally, the corresponding industry user information may be an industry identifier, an industry user identifier, address information of an industry user, and the like.

Finding a target local handle service capable of responding to the retrieval request may include: and under the condition that the retrieval request contains any industry user information, searching a local handle service identifier corresponding to the contained industry user information in the stored first corresponding relation set, and determining the local handle service corresponding to the searched local handle service identifier as a target local handle service.

The embodiment can determine the industry users to which the retrieval request is directed by retrieving the industry user information in the request, and the determined industry users can be one or more. Correspondingly, the searched target local handle service can be one or more.

For example, the search request may include industry user information as "retail industry", and thus, the local handle service corresponding to each industry user of the "retail industry" may be determined as the target local handle service.

In another alternative embodiment, the management device may store a second set of correspondences between identities and corresponding handle prefixes for local handle services in the cross-industry data system.

Optionally, the second correspondence set may be obtained by the management device interacting with several docked local handle services, and the second correspondence set may include an identifier of one or more local handle services in the cross-industry data system.

Optionally, since the handle prefix may uniquely correspond to one local handle service, the unique corresponding local handle service may be found according to the handle prefix and determined as the target local handle service.

Finding a target local handle service capable of responding to the retrieval request may include: and under the condition that the retrieval request comprises the target data identifier, searching a local handle service identifier corresponding to the handle prefix in the target data identifier in the stored second corresponding relation set, and determining the local handle service corresponding to the searched local handle service identifier as the target local handle service.

In this embodiment, the unique corresponding local handle service can be quickly found by retrieving the handle prefix of the target data identifier in the request.

In another alternative embodiment, the global handle registration may store a third set of correspondences between the identity of the local handle service in the cross-industry data system and the resulting new data identity.

Optionally, the global handle registration may be a third correspondence set obtained by interacting with a local handle service in the cross-industry data system, and the third correspondence set may include an identifier of one or more local handle services in the cross-industry data system.

Finding a target local handle service capable of responding to the retrieval request may include: and under the condition that the retrieval request comprises the target data identifier, the management equipment searches the local handle service identifier corresponding to the target data identifier from the third corresponding relation set registered by the global handle, and determines the local handle service corresponding to the searched local handle service identifier as the target local handle service.

Alternatively, the target data identifier may be any new data identifier, and for convenience of description, any new data identifier is referred to as a target data identifier.

In this embodiment, by retrieving the target data identifier in the request, the third correspondence set stored in the global handle registration may be utilized, on one hand, whether the target data identifier is successfully registered in the global handle registration is determined, and on the other hand, the local handle service uniquely corresponding to the target data identifier may also be quickly found.

Optionally, the global handle registration may also store a fourth set of correspondence between the identity of the local handle service in the cross-industry data system and the corresponding handle prefix. The specific method for finding the target local handle service can be referred to the above embodiments.

Optionally, the target data identification and/or the industry user information may be included in the search condition.

In addition, in an optional embodiment, if the target local handle service cannot be found, for example, the content included in the retrieval request is less, and there is no data capable of determining the target local handle service, the retrieval may be directly performed for each local handle service in the cross-industry data system.

Optionally, in a case that a target local handle service capable of responding to the retrieval request cannot be found, retrieving the data object meeting the retrieval condition for the new data directory of each local handle service in the cross-industry data system, and returning the retrieval result to the target user.

It should be noted that the above embodiments of the lookup target local handle service can be used simultaneously, so that the search can be performed for different types of search requests.

For ease of understanding, a specific application example is given below.

Fig. 3 is a schematic diagram illustrating a principle of a data retrieval method according to an embodiment of the present disclosure.

The retrieval request can be firstly judged whether the retrieval request contains the target data identification, and if the retrieval request contains the target data identification, the target local handle service uniquely corresponding to the target data identification can be directly retrieved, so that the retrieval can be conveniently carried out according to the retrieval condition.

If the target data identification is not contained, whether the industry user information is contained or not is continuously judged, and if the industry user information is contained, the target local handle service corresponding to the industry user information can be directly retrieved, so that the subsequent retrieval is conveniently carried out according to the retrieval condition. The industry user information may correspond to one or more target local handle services.

If no industry user information is contained, retrieval can be performed according to retrieval conditions for each local handle service.

In an alternative embodiment, for the retrieval result, if the data object meeting the retrieval condition is retrieved, the retrieved data object can be directly returned to the target user; if no data object meeting the retrieval condition is retrieved, a retrieval result for characterizing the non-retrieved result may be returned to the target user.

Alternatively, there may be several data objects that meet the search criteria during the search process. Several data objects that meet the search criteria may be subsequently sorted or filtered.

For example, for a retail product whose search condition is "price is 50 or less", a data object that meets the search condition in whole or in part may be returned.

In addition to the above retrieval, the management device may also summarize new data directories of each local handle service in the cross-industry data system to obtain a cross-industry data directory.

Specifically, the new data directory sent by each local handle service in the cross-industry data system can be directly obtained for summarizing to obtain the cross-industry data directory, so that the cross-industry data directory is conveniently displayed.

In addition, because the directory number in the data directory usually has no actual meaning, only the metadata information in the data directory may be selected for presentation, for example, the attribute type of the data object, the value range of the attribute value, the service type and the description information of each field, and the like.

Therefore, optionally, the method flow may further include: s204: receiving new data directory information sent by each local handle service in the cross-industry data system, and summarizing to obtain a cross-industry data directory; the new data directory information includes at least new data directory metadata information.

Optionally, the management device may also be used to expose the resulting cross-industry data catalog.

Optionally, the management device may be configured to receive a new data directory generated by a local handle service in the cross-industry data system, and merge the received new data directories of different local handle services into the cross-industry data directory. In particular, a new data directory generated across one or more local handle services in an industrial data system may be received.

The catalog number (i.e., the new data identifier) of the new data catalog is globally unique in the cross-industry data system, so that the catalog number can be directly merged to obtain the cross-industry data catalog.

The cross-industry data directory may contain data objects of different industry users and corresponding directory numbers.

For the cross-industry data directory, the management device can also display the cross-industry data directory to users with requirements, and the management device is affected by the aspect of data security or insufficient in display resources.

For example, in a cross-industry shopping scenario, a shopping platform may interface several industries, retail industries, appliance industries, service industries, and so forth. When the user does not perform commodity retrieval, the user may wish to randomly acquire recommended commodities, so that a part of the products or a part of the field values of the products in the cross-industry data directory can be displayed to the user by the management device.

When the cross-industry data directory is specifically displayed, optionally, in order to facilitate viewing by a user, the management device may acquire directory metadata information of a new data directory serviced by the local handle, and may further display a data object in the cross-industry data directory after being combined with corresponding directory metadata information.

Optionally, the directory metadata information may include field information, and the field value of the data object may be presented to the user after being combined with the corresponding field information, so that the user may view the correspondence between the field value and the field information, thereby determining the actual business meaning of the field value.

For example, a user views the field value 60 in the data object, and it is often difficult to understand that the actual business meaning of the field value can be clarified after incorporating the corresponding field information "retail product price".

Of course, in the previous embodiment, the original data catalog metadata information for the industry users may be updated, so that it is also convenient for people in other industries to understand the updated catalog metadata information in the cross-industry scenario.

Thus, the directory metadata information here may alternatively be updated directory metadata information.

In an alternative embodiment, the management device may store directory metadata information for a new data directory generated across local handle services in an industrial data system.

Optionally, any local handle service updates the directory metadata information according to the information of the corresponding industry user for an original data directory preset by the corresponding industry user, and generates a new data directory according to the updated directory metadata information and the obtained new data identifier; the generated directory metadata information of the new data directory is updated directory metadata information, and the directory number is the obtained new data identifier. In this case, the directory metadata information of the new data directory stored by the management apparatus may be updated directory metadata information.

Optionally, the management device may receive a new data directory generated by a local handle service in the cross-industry data system, merge the received new data directories of different local handle services into the cross-industry data directory, determine a required data object in the cross-industry data directory according to a user requirement, and return the required data object to the user with the user requirement by combining the required data object with directory metadata information (specifically, field information) of the new data directory where the required data object is located. Specifically, the information can be presented to the user with the user requirement.

For example, for the requirement of obtaining a recommended product by a user, the management device determines product data recommended by the user in the cross-industry data directory, and returns the product data to the user in combination with field information of a new data directory in which the product data is located, which may specifically be "product type: electrical appliances, product brand: xx brand, product price: 60 yuan.

And optionally, the search result can be directly shown to the target user when the search result is specifically returned to the target user.

Optionally, in the case that the retrieval result contains the retrieved data object, the retrieval result may be further returned to the target user in combination with the catalog metadata, so as to facilitate the viewing of the target user. Reference may be made in particular to the above-mentioned examples.

Thus, in an alternative embodiment, the management device may store directory metadata information for a new data directory generated across local handle services in an industrial data system.

Optionally, the management device may store directory metadata information for a new data directory generated across one or more local handle services in the industrial data system. Alternatively, the management device may obtain directory metadata information for the new data directory from a local handle service in the cross-industry data system.

Optionally, the management device may store a fourth set of correspondences between the local handle service identification and the generated directory metadata information for the new data directory. The local handle service identifier may specifically be a handle prefix or address information corresponding to the local handle service. The corresponding directory metadata information can be directly determined according to the local handle service identifier.

Optionally, returning the search result to the target user may include: in the event that the results of the retrieval include any data object, directory metadata information for the new data directory generated by the target local handle service is determined. And sending the data object contained in the retrieval result to the target user by combining the determined directory metadata information.

Optionally, the data object included in the search result may be presented to the target user in combination with the determined directory metadata information.

Alternatively, the directory metadata information may be field information, specifically, in combination with the data object and the directory metadata information, the data object field value included in the search result may be filled into the corresponding field information.

Further, optionally, the determined directory metadata information may be updated directory metadata information. Reference may be made in particular to the above-mentioned examples.

The embodiment can facilitate the target user to check the retrieval result by combining the directory metadata information.

In a specific embodiment, in the DOA architecture, after a business user can redefine directory metadata information (i.e., updated directory metadata information) using a Type mechanism of the DOA, a Type set corresponding to a local handle service can be obtained, where the Type set includes the updated directory metadata information. The Type sets defined by the industry users can be stored in the management device, and because the Type sets directly correspond to the local handle services, and specifically, the Type sets can correspond to the handle prefixes allocated to the local handle services, the management device can directly acquire the directory metadata information (i.e., updated directory metadata information) of the new data directory generated by the local handle services in the cross-industry data system by using a Type mechanism.

Corresponding to the method flow, the embodiment of the specification also provides an embodiment of a device.

Fig. 4 is a schematic structural diagram of a data directory generation apparatus provided in an embodiment of the present specification. The device can be applied to any local handle service in a cross-industry data system.

The cross-industry data system may include different local handle services corresponding to different industry users, respectively; an original data directory is preset for an industry user corresponding to any local handle service; in the original data directory, different data objects respectively correspond to different original data identifiers.

The apparatus may include the following elements.

An obtaining unit 401, configured to obtain corresponding handle prefixes, where different local handle services in the inter-industry data system correspond to different handle prefixes, respectively.

And a splicing unit 402, configured to, for an original data directory preset by a user in a corresponding industry, splice the original data identifier corresponding to each data object as a handle suffix with the acquired corresponding handle prefix to obtain a new data identifier corresponding to the data object, and generate a new data directory according to the obtained new data identifier.

Optionally, the apparatus may further include: a sending unit 403, configured to send the obtained new data identifier to a global handle registration, where the global handle registration is used to summarize new data identifiers obtained by each local handle service in the inter-industry data system.

Optionally, the obtaining unit 401 may be configured to: and acquiring the handle prefix applied by the corresponding industry user as the corresponding handle prefix, wherein the applied handle prefix is uniquely corresponding to the industry user.

Optionally, the apparatus may further include: an updating unit 403, configured to update the catalog metadata information according to the information of the corresponding industry user for the original data catalog preset by the corresponding industry user.

The stitching unit 402 may be configured to: generating a new data directory according to the updated directory metadata information and the obtained new data identifier; the generated directory metadata information of the new data directory is updated directory metadata information, and the directory number is the obtained new data identifier.

Fig. 5 is a schematic structural diagram of a data retrieval device according to an embodiment of the present disclosure.

The device is based on the data catalog generating device, and the data searching device can be applied to the management equipment; the management equipment is newly added equipment for the cross-industry data system.

The apparatus may include the following elements.

A receiving unit 501, configured to receive a retrieval request sent by a target user, where the retrieval request at least includes a retrieval condition; the retrieval request is used for requesting to acquire the data object which meets the contained retrieval condition.

A lookup unit 502, configured to lookup a target local handle service capable of responding to the retrieval request.

A result unit 503, configured to retrieve, for the new data directory of the found target local handle service, the data object that meets the retrieval condition, and return the retrieval result to the target user.

Optionally, the management device stores a first set of correspondence between the identifier of the local handle service in the cross-industry data system and the corresponding industry user information.

The search unit 502 is specifically configured to: and under the condition that the retrieval request contains any industry user information, searching a local handle service identifier corresponding to the contained industry user information in the stored first corresponding relation set, and determining the local handle service corresponding to the searched local handle service identifier as a target local handle service.

Optionally, the management device stores a second set of correspondence between the identifier of the local handle service in the cross-industry data system and the corresponding handle prefix.

The search unit 502 is specifically configured to: and under the condition that the retrieval request comprises the target data identifier, searching a local handle service identifier corresponding to the handle prefix in the target data identifier in the stored second corresponding relation set, and determining the local handle service corresponding to the searched local handle service identifier as the target local handle service.

Optionally, the global handle registration stores a third set of correspondence between the identifier of the local handle service in the cross-industry data system and the obtained new data identifier.

The search unit 502 is specifically configured to: and under the condition that the retrieval request comprises the target data identifier, the management equipment searches the local handle service identifier corresponding to the target data identifier from the third corresponding relation set registered by the global handle, and determines the local handle service corresponding to the searched local handle service identifier as the target local handle service.

Optionally, the apparatus may further include: a returning unit 504, configured to, in a case that a target local handle service capable of responding to a search request cannot be found, retrieve, for a new data directory of each local handle service in the cross-industry data system, a data object that meets a search condition, and return a search result to a target user.

Optionally, the apparatus may further include: a summarizing unit 505, configured to receive new data directory information sent by each local handle service in the cross-industry data system, and summarize to obtain a cross-industry data directory; the new data directory information at least comprises new data directory metadata information; the management device is also used for displaying the obtained cross-industry data catalogue.

Optionally, the management device stores directory metadata information for a new data directory generated across local handle services in the industrial data system.

The result unit 503 may be used to: determining directory metadata information of a new data directory generated by a target local handle service when a retrieval result includes any data object; and displaying the data object contained in the retrieval result to the target user by combining the determined directory metadata information.

Optionally, the management device may be configured to receive a new data directory generated by a local handle service in the cross-industry data system, and merge the received new data directories of different local handle services into the cross-industry data directory.

For a detailed explanation of the above device embodiment, reference may be made to the above explanation of the method flow.

An embodiment of the present specification further provides an electronic device, including a processor and a memory; the memory stores a program that can be called by the processor; when the processor executes the program, the data directory generation method or the data retrieval method according to any one of the above method embodiments is implemented.

The embodiments of the present specification further provide a machine-readable storage medium, on which a program is stored, and when the program is executed by a processor, the program implements the data directory generation method or the data retrieval method according to any of the above method embodiments.

The present specification further provides a computer device, which at least includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the data directory generation method or the data retrieval method according to any of the above method embodiments.

Fig. 6 is a schematic diagram illustrating a more specific hardware structure of a computer device according to an embodiment of the present disclosure, where the device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.

The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.

The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.

The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.

The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present apparatus and other apparatuses. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).

Bus 1050 includes a path that transfers information between various components of the device, such as processor 1010, memory 1020, input/output interface 1030, and communication interface 1040.

It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.

The present specification also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the data directory generation method or the data retrieval method according to any one of the above method embodiments.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present disclosure. And part or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

The foregoing is only a detailed description of the embodiments of the present disclosure, and it should be noted that, for those skilled in the art, many modifications and decorations can be made without departing from the principle of the embodiments of the present disclosure, and these modifications and decorations should also be regarded as protection for the embodiments of the present disclosure.

Claims

1. A data directory generation method is applied to any local handle service in a cross-industry data system; the cross-industry data system comprises different local handle services respectively corresponding to different industry users; an original data directory is preset for an industry user corresponding to any local handle service; in the original data directory, different data objects respectively correspond to different original data identifiers; the method comprises the following steps:

2. The method of claim 1, further comprising:

3. The method of claim 1, further comprising:

4. A data retrieval method based on the method of any one of claims 1 to 3, applied to a management device; the management equipment is newly added equipment aiming at the cross-industry data system;

the method comprises the following steps:

5. The method of claim 4, the management device storing a first set of correspondence between an identification of a local handle service in the cross-industry data system and corresponding industry user information;

6. The method of claim 4, the management device storing a second set of correspondences between identities and corresponding handle prefixes of local handle services in the cross-industry data system;

7. The method of claim 4, the global handle registration storing a third set of correspondences between an identity of a local handle service in the cross-industry data system and the resulting new data identity;

8. The method of claim 4, further comprising:

9. The method of claim 4, the management device storing directory metadata information for a new data directory generated by a local handle service in the cross-industry data system;

the returning of the retrieval result to the target user comprises:

and sending the data object contained in the retrieval result to the target user by combining the determined directory metadata information.

10. The method of claim 4, the management device to receive a new data directory generated by a local handle service in the cross-industry data system and merge the received new data directories of different local handle services into a cross-industry data directory.

11. A data directory generation device is applied to any local handle service in a cross-industry data system; the cross-industry data system comprises different local handle services respectively corresponding to different industry users; an original data directory is preset for an industry user corresponding to any local handle service; in the original data directory, different data objects respectively correspond to different original data identifiers; the device comprises:

12. A data retrieval device based on the device of claim 11, applied to a management device; the management equipment is newly added equipment aiming at the cross-industry data system;

the device comprises:

13. An electronic device comprising a processor and a memory; the memory stores a program that can be called by the processor; wherein the processor, when executing the program, implements the data catalog generation method of any one of claims 1 to 3 or the data retrieval method of any one of claims 4 to 10.

14. A machine-readable storage medium on which a program is stored, which when executed by a processor implements the data catalog generation method according to any one of claims 1 to 3 or the data retrieval method according to any one of claims 4 to 10.