An identification resolution method, device and medium supporting multi-system identification sharing

Abstract

The present application discloses an identification resolution method, device and medium supporting multi-system identification sharing, the method comprising: obtaining identification data, determining registration data according to the identification data, and determining the registration node and the data format corresponding to the registration node according to the registration data, so as to register the identification according to the data format, and save the node address of the registration node to the database; obtaining a resolution request, determining the resolution node address according to the resolution request, and inputting the resolution node address into the database for search, and if the resolution node address is stored in the database, sending the resolution request to the resolution node corresponding to the resolution node address, so as to perform identification resolution according to the resolution request. The present application realizes the identification registration and identification resolution functions of different identification resolution systems, and realizes the interconnection and interoperability of data between multiple identification resolution systems.

Description

Technical Field

[0001] The present application relates to the field of industrial Internet technology, and in particular to an identification resolution method, device and medium that supports multi-system identification sharing. Background Art

[0002] The industrial Internet identification resolution system is an important part of the industrial Internet network system and the nerve center that supports the interconnection of the industrial Internet. Its function is similar to the Domain Name System (DNS) in the Internet field. Identification resolution technology can connect all production factors such as equipment, machines and materials in the industry by establishing a unified identification system. Through the resolution system, the fragmented data and applications can be connected to achieve the mastery of information such as the source, flow process, and purpose of the data.

[0003] At present, the mainstream identification resolution systems in China include the Handle system, the MA system, the VAA system, etc. Due to the parallel construction of multiple systems, the systems are currently unable to achieve data interconnection and interoperability, and the identification resolution node docking methods of each system, the required data structure and format are very different, resulting in extremely high enterprise docking costs. In addition, different regions choose to build different industrial Internet nodes, resulting in different identification resolution systems for enterprise access points in different regions. In the production process, upstream and downstream companies use different identification resolution systems, which makes it impossible to achieve data interconnection and interoperability, making the identification resolution system lose its original value. Summary of the invention

[0004] In order to solve the above problems, the present application proposes an identification resolution method that supports multi-system identification sharing, including: obtaining identification data, determining registration data based on the identification data, and determining a registration node and a data format corresponding to the registration node based on the registration data, so as to perform identification registration according to the data format, and save the node address of the registration node to a database; obtaining a resolution request, determining a resolution node address based on the resolution request, and inputting the resolution node address into the database for search, and if the resolution node address is stored in the database, sending the resolution request to the resolution node corresponding to the resolution node address, so as to perform identification resolution according to the resolution request.

[0005] In one example, the method further includes: determining node configuration information based on the registration data, wherein the node configuration information includes but is not limited to a node address, a node type, and authentication data; determining the registration node based on the node type and the node address, and performing authority authentication on the registration node based on the authentication data; if the authority authentication on the registration node is successful, initiating an identification registration request to the registration node based on the registration data to perform identification registration.

[0006] In one example, the method further includes: determining an original data format based on the registration data, and determining a registration node and a target data format corresponding to the registration node; comparing the original data format and the target data format; if the original data format and the target data format are consistent, performing identification registration based on the registration data; if the original data format and the target data format are inconsistent, converting the data format of the registration data into the target data format, and performing identification registration based on the converted registration data.

[0007] In one example, the method is applied in an identity resolution system that supports multi-system identity sharing, wherein the system includes multiple middleware systems; after registering the identity according to the data format, the method further includes: the middleware system determines a pre-set access address and adds the access address to the registration data; obtains the resolution request and determines whether the resolution request contains the access address of other middleware systems; if the resolution request contains the access address of the other middleware system, an access request is initiated through the middleware system to the access address of the other middleware system.

[0008] In one example, the method also includes: the middleware system obtains authorization information corresponding to the registration data, wherein the authorization information includes but is not limited to a whitelist, an identity identification code, and an authorization code, the whitelist is used for the user's resolution request, the identity identification code is used for the resolution request of other middleware systems, and the authorization code is used for the resolution request of a third-party platform; obtaining the resolution request, determining the authorization information in the resolution request, and verifying the authorization information; if the resolution request contains the whitelist, performing identity resolution according to the resolution request; if the resolution request contains the identity identification code, comparing the identity identification code with the identity of the middleware system, and if the comparison is successful, performing identity resolution according to the resolution request; if the resolution request contains the authorization code, performing the resolution request according to the authorization code.

[0009] In one example, the middleware system includes a collection module and a processing module; the method also includes: the collection module collects the identification data and sends the identification data to the processing module; the processing module determines a pre-set mapping rule, maps the identification data according to the mapping rule, and performs identification registration according to the mapped identification data.

[0010] In one example, the middleware system also includes a security module and a docking module; the security module is used to encrypt the identification data and to verify the authorization information; the docking module is used to register the identification to multiple registration nodes according to the registration data, and to perform identification resolution to multiple resolution nodes according to the resolution request.

[0011] In one example, the middleware system further includes a visualization interface; the method further includes: acquiring authorization information and mapping rules through the visualization interface, and visually managing the authorization information and the mapping rules through the visualization interface.

[0012] On the other hand, the present application also proposes an identification resolution device that supports multi-system identification sharing, comprising: at least one processor; and a memory that is communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the identification resolution device that supports multi-system identification sharing can execute: obtaining identification data, determining registration data based on the identification data, and determining a registration node and a data format corresponding to the registration node based on the registration data, so as to perform identification registration according to the data format, and save the node address of the registration node to a database; obtaining a resolution request, determining a resolution node address based on the resolution request, and inputting the resolution node address into the database for search, and if the resolution node address is stored in the database, sending the resolution request to the resolution node corresponding to the resolution node address, so as to perform identification resolution according to the resolution request.

[0013] On the other hand, the present application also proposes a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured to: obtain identification data, determine registration data based on the identification data, and determine a registration node and a data format corresponding to the registration node based on the registration data, so as to perform identification registration according to the data format, and save the node address of the registration node to a database; obtain a resolution request, determine a resolution node address based on the resolution request, and input the resolution node address into the database for search, and if the resolution node address is stored in the database, send the resolution request to the resolution node corresponding to the resolution node address, so as to perform identification resolution according to the resolution request.

[0014] This application is adaptable to multiple identification resolution systems, and can realize indirect intercommunication of multi-system identification data when the data of multiple identification resolution systems are not intercommunication. It helps enterprises using different identification resolution systems to realize mutual recognition and intercommunication of identification data, and enhance the use value of the identification resolution system.

[0015] This application ensures the security of identification data while ensuring its interconnection and interoperability by encrypting identification data, adding authorized access to identification content, etc., which helps eliminate companies' concerns about the security of sensitive data and encourages companies to upload valuable data to the identification resolution system, thereby maximizing the advantages and value of the identification resolution system.

[0016] This application provides support for multiple network communication protocols and data formats, making it easy for enterprises to choose the appropriate access method based on their own circumstances. After completing a single connection, they can access multiple identification resolution systems, reducing the enterprise's access costs and facilitating the promotion of the identification resolution system.

[0017] This application implements the identification registration and identification resolution functions of different identification resolution systems according to the docking requirements and specifications of various identification resolution systems such as Handle and VAA, breaks down the data barriers between different systems, and realizes the interconnection and interoperability of data between various identification resolution systems. This application supports the encryption of identification data, protects enterprise data security, eliminates enterprise concerns, and provides multiple authorization methods to facilitate authorization to other supply chain enterprises to achieve data interconnection and interoperability. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 A flowchart of an identification resolution method supporting multi-system identification sharing in an embodiment of the present application;

[0020] Figure 2 A schematic diagram of the structure of the middleware system in the embodiment of the present application;

[0021] Figure 3 This is a schematic diagram of an identity resolution device that supports multi-system identity sharing in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0023] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0024] like Figure 1 As shown, in order to solve the above problems, an identification resolution method supporting multi-system identification sharing is provided in an identification resolution system supporting multi-system identification sharing, such as Figure 2 As shown, the system includes multiple middleware systems, each of which can perform identity registration and identity resolution with different types of identity resolution systems. Among them, the middleware system includes an acquisition module, a processing module, a security module, a docking module, an open API (not shown in the figure), and a visual interface (not shown in the figure). The acquisition module is used to collect identification data, supports multiple data formats and multiple network protocols, and sends the identification data to the processing module. The processing module is used to process the data collected by the acquisition module, supports user-defined data models, can identify structured and semi-structured data and convert them into structured data required for identity registration of each system. The security module supports fine-grained data access control strategies, which are used to provide identity authentication, data verification, authorization verification, data encryption and other functions. The docking module is adapted to multiple identity resolution systems and has the ability to register and resolve multiple identity resolution system nodes. The open API is used for enterprise docking and supports multiple data formats and multiple network protocols. The method includes:

[0025] S101. Acquire identification data, determine registration data according to the identification data, and determine a registration node and a data format corresponding to the registration node according to the registration data, perform identification registration according to the data format, and save the node address of the registration node to a database.

[0026] The middleware system is between the enterprise platform and the identity resolution node that needs to be connected, and usually acts between the enterprise's internal system and the node responsible for identity registration and identity resolution in the identity resolution system. For example, between the enterprise ERP system and the enterprise node of the VAA system, or between the enterprise comprehensive management platform and the third-level node of the MA system. The middleware system implements the functions of identity registration and identity resolution for multiple systems based on the access requirements and access specifications of identity resolution systems such as Handle, VAA, and MA. Enterprises can select appropriate protocols to connect internal systems, industrial equipment, etc. to the middleware system to realize the collection of identity data by the middleware system. Identification data is the application data of the enterprise, such as ERP order information, MES production information, personnel management information, warehouse in and out information, product production information, etc. When performing identity registration, the acquisition module obtains the identification data and determines the registration data therein according to the identification data. The processing module determines the registration node and the data format required by the registration node according to the registration data, performs identity registration according to the data format, and saves the node address of the registration node to the database. For example: for the Handle system, the data to be registered is converted into the XML format required by the Handle system, and the WebSocket protocol is used to push the data to the corresponding node of the Handle system to complete the identity registration; for the VAA system, the data to be registered is converted into the JSON format data required by the VAA system, and the RESTful HTTP protocol is used to push the data to the secondary node or enterprise node of the VAA system to complete the identity registration.

[0027] S102, obtaining a resolution request, determining a resolution node address according to the resolution request, and inputting the resolution node address into the database for search; if the resolution node address is stored in the database, sending the resolution request to the resolution node corresponding to the resolution node address to perform identity resolution according to the resolution request.

[0028] Different identity resolution systems have different resolution methods. For example, both the VAA system and the MA system resolve data from recursive nodes, but the resolution request addresses and request methods are different. The middleware system has built-in resolution node addresses for each system in its database. When a user initiates a resolution request, it automatically identifies the system corresponding to the identity and enters the resolution node address into the database for search. If the resolution node address is stored in the database, a resolution request is initiated to the corresponding resolution node. The resolution node address of the middleware system supports user modification and can be updated and replaced at any time.

[0029] In one embodiment, the middleware system supports users to configure node addresses, node types and authentication data to register identification data with designated nodes. The registration data includes node configuration information, wherein the node configuration information includes node address, node type and authentication data. The middleware system needs to connect to the identification registration nodes of various identification resolution systems, so it is necessary to save the access addresses of these nodes. The types of nodes include VAA secondary nodes, VAA enterprise nodes, MA third-level nodes, Handle third-level nodes, etc. In addition, the identity authentication information of the enterprise on the node is required, such as account passwords, etc. After obtaining the above information, the middleware can use the identity of the enterprise to initiate a request to register the identity to these identification registration nodes. The registration node can be determined according to the node type and node address, and the authority authentication is performed on the registration node according to the authentication data. If the authority authentication on the registration node is successful, an identification registration request is initiated to the registration node according to the registration data to perform identification registration.

[0030] In one embodiment, the middleware system supports data conversion, supports conversion between JSON structure and XML structure, and supports network or communication protocols such as HTTP, WebSocket, MQTT, ModBus, etc. Different data upload interfaces are provided for different protocols and different data structures. The middleware system will open different APIs for docking and calling with the business system of the enterprise, and the business system includes production management systems such as MES and ERP. Develop a variety of API interfaces to provide different network protocols and data format combinations, for example: provide an API interface using JSON format transmission and HTTP network protocol; provide an API interface using XML format transmission and WebSocket network protocol; provide an API interface using JSON format transmission and MQTT network protocol, etc. The specific process is: determine the original data format according to the registration data, and determine the target data format corresponding to the registration node and the registration node. Compare the original data format with the target data format. If the original data format is consistent with the target data format, the registration is identified according to the registration data; if the original data format is inconsistent with the target data format, the data format of the registration data is converted to the target data format, and the registration is identified according to the converted registration data.

[0031] In one embodiment, in the process of promoting the implementation of the identity resolution system in industrial production, there are still data security issues with the public disclosure of identification data. Therefore, a large number of enterprises are unwilling to register valuable production data into the identity resolution system, resulting in slow promotion and implementation of the identity resolution system. The middleware system supports encryption of identification data. The middleware system will encrypt the identification data when registering the identification. The encryption method uses the SM2 national secret algorithm to ensure data security. The encrypted public and private keys are stored locally in the middleware system. When the identification is resolved through the middleware system, the relevant data will be decrypted according to the authority, and the identification can only be obtained by resolving the identification through other systems or identity resolution nodes. The encrypted data. For example, the enterprise's identification is 88.117.0 / abc123, and its registration data is {name:1, age:18}. The enterprise chooses to encrypt "age", then the general user resolves it as {name:1, age:dau2314klhfzxc21jk312da89z123}, where "age" is ciphertext garbled, and the authorized user resolves it as {name:1, age:18}.

[0032] In one embodiment, an enterprise can have an independent middleware system. In the entire identity resolution system, multiple enterprises have multiple middleware systems. In order to ensure the interconnection and interoperability of identification data, the middleware system that registers the identification will add the access address of the current middleware system to the identification. Other external users can access the address to apply for identification resolution. The middleware system will return different data according to the requester's authority, and unauthorized users will return ciphertext. For ease of use, when the middleware system requests the identification registered by the middleware system of other enterprises, it will automatically resolve the access address and request data without manual operation by the user. The middleware system determines the pre-set access address and adds the access address to the registration data. The specific process is: obtain the resolution request, and determine whether the resolution request contains the access address of other middleware systems. If the resolution request contains the access address of other middleware systems, an access request is initiated to the access address of other middleware systems through the middleware system. For example, the registration data submitted by the enterprise with the identification 88.117.0 / abc123 is {name:1,age:18}, and the "age" field is encrypted. When registering with the identity resolution system, middleware system A will add the "_analysis_url_" field, and the registration data will become {name:1, age:dau2314klhfzxc21jk312da89z123, _analysis_url_:https: / / middleware A's deployment address}. If a general user wants to obtain the decrypted field of "age", they need to manually access "https: / / middleware A's deployment address" and carry relevant identity authentication information. When other middleware system B finds that the identifier contains the "_analysis_url_" field, it will automatically carry the identity of middleware system B to initiate a request to "https: / / middleware A's deployment address". If middleware system B has access to the "age" field, it will directly obtain {name:1, age:18}. If not, it will return {name:1, age:dau2314klhfzxc21jk312da89z123}.

[0033] In one embodiment, in order to ensure the interconnection and interoperability of identification data, the middleware system supports multiple fine-grained data access strategies. The middleware system receives the authorization model created by the user, which is one or more identification fields. When there is a parsing request for the model's permissions, the middleware system will decrypt the corresponding fields according to the field conditions of the model and return the decrypted data to the requester. The middleware system obtains the authorization information corresponding to the registration data, wherein the authorization information includes but is not limited to a whitelist, an identity identification code, and an authorization code. Different external applications contain different authorization information. The whitelist is used for the user's parsing request. The identity identification code is used for the parsing request of other middleware systems. Each middleware system contains a corresponding identity code, and the identity identification code is used for mutual authorization between middleware systems. The authorization code is used for the parsing request of a third-party application or platform. The user can configure multiple authorization policies for the authorization model, for example, the authorization model includes multiple combinations of IP whitelist authorization and identity identification code authorization, and the authorization model only includes authorization code authorization. The middleware system obtains the parsing request, determines the authorization information in the parsing request, and verifies the authorization information. If the parsing request contains a whitelist, the decrypted data of the field contained in the corresponding authorization model is returned. If the parsing request contains an identity code, the identity code is configured in the authorization model of the middleware system that needs to be parsed. The identity code is verified during parsing to obtain the decrypted data of the fields contained in the authorization model. If the parsing request contains an authorization code, that is, the parsing request initiated by a third-party application or platform contains an authorization code, the decrypted data of the fields contained in the corresponding authorization model can be obtained.

[0034] In one embodiment, the data generated by industrial computers such as PLC, ERP, MES and other systems are very likely to contain sensitive information, and the enterprise will not upload all production data. The middleware system can process and map the collected identification data. The middleware system provides users with a mapping model so that users can configure the data mapping model for the identification data and map different types of data into structured data for easy identification registration. For example: for a piece of data containing five fields a, b, c, d, and e generated by an enterprise, the enterprise configures the mapping relationship of a->A, b->B, c->C. After data processing and mapping, the data containing the three fields A, B, and C are finally registered as identifiers in the corresponding identification resolution system. Configuring mapping can ensure that enterprises select part of the data for upload identification registration according to their own needs, meeting the needs of enterprises to protect their own data security and data privacy.

[0035] In one embodiment, the middleware system provides a visual interface through which users can visually manage the above authorization models, authorization policies, and data mapping models. The middleware system provides different open APIs for the above different networks or communication protocols and data formats. Enterprise users only need to select the corresponding API for access according to their own situation to obtain the ability to connect to multiple identity resolution systems.

[0036] like Figure 3 As shown, the embodiment of the present application also provides an identity resolution device supporting multi-system identity sharing, including:

[0037] at least one processor; and,

[0038] a memory communicatively connected to the at least one processor; wherein,

[0039] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the identity resolution device supporting multi-system identity sharing to execute:

[0040] Acquire identification data, determine registration data according to the identification data, and determine a registration node and a data format corresponding to the registration node according to the registration data, so as to perform identification registration according to the data format, and save the node address of the registration node to a database;

[0041] Obtain a resolution request, determine a resolution node address according to the resolution request, and input the resolution node address into the database for search; if the resolution node address is stored in the database, send the resolution request to the resolution node corresponding to the resolution node address to perform identity resolution according to the resolution request.

[0042] The embodiment of the present application further provides a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured as follows:

[0043] Acquire identification data, determine registration data according to the identification data, and determine a registration node and a data format corresponding to the registration node according to the registration data, so as to perform identification registration according to the data format, and save the node address of the registration node to a database;

[0044] Obtain a resolution request, determine a resolution node address according to the resolution request, and input the resolution node address into the database for search; if the resolution node address is stored in the database, send the resolution request to the resolution node corresponding to the resolution node address to perform identity resolution according to the resolution request.

[0045] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0046] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0047] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0048] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0049] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0050] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0051] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0052] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0053] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0054] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0055] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. An identity resolution method supporting multi-system identity sharing, characterized in that: include: Acquire identification data, determine registration data according to the identification data, and determine a registration node and a data format corresponding to the registration node according to the registration data, so as to perform identification registration according to the data format, and save the node address of the registration node to a database; Obtaining a resolution request, determining a resolution node address according to the resolution request, and inputting the resolution node address into the database for search; if the resolution node address is stored in the database, sending the resolution request to a resolution node corresponding to the resolution node address, so as to perform identity resolution according to the resolution request; The invention is applied in an identity resolution system supporting multi-system identity sharing, wherein the system includes a plurality of middleware systems; After performing identification registration according to the data format, the method further includes: The middleware system determines a preset access address and adds the access address to the registration data; Obtaining the resolution request, and determining whether the resolution request contains access addresses of other middleware systems; If the resolution request includes the access address of the other middleware system, initiating an access request to the access address of the other middleware system through the middleware system; The middleware system obtains the authorization information corresponding to the registration data, wherein the authorization information includes but is not limited to a whitelist, an identity identification code, and an authorization code. The whitelist is used for the user's resolution request, the identity identification code is used for the resolution request of other middleware systems, and the authorization code is used for the resolution request of a third-party platform; Obtaining the resolution request, determining the authorization information in the resolution request, and verifying the authorization information; If the resolution request contains the whitelist, performing identity resolution according to the resolution request; If the resolution request contains the identity code, the identity code is compared with the identity identifier of the middleware system, and if the comparison is successful, the identifier is resolved according to the resolution request; If the resolution request includes the authorization code, the resolution request is performed according to the authorization code.

2. The method according to claim 1, characterized in that The method further comprises: Determine node configuration information according to the registration data, wherein the node configuration information includes but is not limited to node address, node type, and authentication data; Determining the registration node according to the node type and the node address, and performing authority authentication on the registration node according to the authentication data; If the authority authentication on the registration node is successful, an identification registration request is initiated to the registration node according to the registration data to perform identification registration.

3. The method according to claim 1, characterized in that The method further comprises: Determine the original data format according to the registration data, and determine the registration node and the target data format corresponding to the registration node; Comparing the original data format with the target data format; If the original data format is consistent with the target data format, performing identification registration according to the registration data; If the original data format is inconsistent with the target data format, the data format of the registration data is converted into the target data format, and the identification registration is performed according to the converted registration data.

4. The method according to claim 1, characterized in that: The middleware system includes a collection module and a processing module; The method further comprises: The acquisition module acquires the identification data and sends the identification data to the processing module; The processing module determines a preset mapping rule, maps the identification data according to the mapping rule, and performs identification registration according to the mapped identification data.

5. The method according to claim 1, characterized in that The middleware system also includes a security module and a docking module; The security module is used to encrypt the identification data and also to verify the authorization information; The docking module is used to register identifiers with the multiple registration nodes according to the registration data, and is also used to perform identifier resolution with the multiple resolution nodes according to the resolution request.

6. The method according to claim 1, characterized in that The middleware system also includes a visualization interface; The method further comprises: The authorization information and the mapping rules are acquired through the visualization interface, and the authorization information and the mapping rules are visually managed through the visualization interface.

7. An identification resolution device supporting multi-system identification sharing, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the identity resolution device supporting multi-system identity sharing to execute: Acquire identification data, determine registration data according to the identification data, and determine a registration node and a data format corresponding to the registration node according to the registration data, so as to perform identification registration according to the data format, and save the node address of the registration node to a database; Obtaining a resolution request, determining a resolution node address according to the resolution request, and inputting the resolution node address into the database for search; if the resolution node address is stored in the database, sending the resolution request to a resolution node corresponding to the resolution node address, so as to perform identity resolution according to the resolution request; The invention is applied in an identity resolution system supporting multi-system identity sharing, wherein the system includes a plurality of middleware systems; After the identification is registered according to the data format, The middleware system determines a preset access address and adds the access address to the registration data; Obtaining the resolution request, and determining whether the resolution request contains access addresses of other middleware systems; If the resolution request includes the access address of the other middleware system, initiating an access request to the access address of the other middleware system through the middleware system; The middleware system obtains the authorization information corresponding to the registration data, wherein the authorization information includes but is not limited to a whitelist, an identity identification code, and an authorization code. The whitelist is used for the user's resolution request, the identity identification code is used for the resolution request of other middleware systems, and the authorization code is used for the resolution request of a third-party platform; Obtaining the resolution request, determining the authorization information in the resolution request, and verifying the authorization information; If the resolution request contains the whitelist, performing identity resolution according to the resolution request; If the resolution request contains the identity code, the identity code is compared with the identity identifier of the middleware system, and if the comparison is successful, the identifier is resolved according to the resolution request; If the resolution request includes the authorization code, the resolution request is performed according to the authorization code.

8. A non-volatile computer storage medium storing computer executable instructions, characterized in that: The computer executable instructions are configured to: Acquire identification data, determine registration data according to the identification data, and determine a registration node and a data format corresponding to the registration node according to the registration data, so as to perform identification registration according to the data format, and save the node address of the registration node to a database; Obtaining a resolution request, determining a resolution node address according to the resolution request, and inputting the resolution node address into the database for search; if the resolution node address is stored in the database, sending the resolution request to a resolution node corresponding to the resolution node address, so as to perform identity resolution according to the resolution request; The invention is applied in an identity resolution system supporting multi-system identity sharing, wherein the system includes a plurality of middleware systems; After the identification is registered according to the data format, The middleware system determines a preset access address and adds the access address to the registration data; Obtaining the resolution request, and determining whether the resolution request contains access addresses of other middleware systems; If the resolution request includes the access address of the other middleware system, initiating an access request to the access address of the other middleware system through the middleware system; The middleware system obtains the authorization information corresponding to the registration data, wherein the authorization information includes but is not limited to a whitelist, an identity identification code, and an authorization code. The whitelist is used for the user's resolution request, the identity identification code is used for the resolution request of other middleware systems, and the authorization code is used for the resolution request of a third-party platform; Obtaining the resolution request, determining the authorization information in the resolution request, and verifying the authorization information; If the resolution request contains the whitelist, performing identity resolution according to the resolution request; If the resolution request contains the identity code, the identity code is compared with the identity identifier of the middleware system, and if the comparison is successful, the identifier is resolved according to the resolution request; If the resolution request includes the authorization code, the resolution request is performed according to the authorization code.

Images