Cross-domain intercommunication and mutual trust method based on comprehensive code model

The cross-domain intercommunication and mutual trust method addresses non-interoperability and privacy issues by establishing secure digital identities and enabling seamless data sharing through a trusted identity system, ensuring reliable communication and trust across urban systems.

CN119071006APending Publication Date: 2024-12-03BEIJING ZHONGDUN ANXIN TECH DEV CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310651007.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-06-02
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Current cross-domain urban service systems face issues of non-interoperability, incomplete data, unknown data sources, lack of authoritative trust roots, and privacy concerns, leading to unreliable identity authentication and data sharing challenges.

Method used

A cross-domain intercommunication and mutual trust method based on a comprehensive code model, utilizing a trusted digital identity system to establish secure digital identities, manage and convert identities across platforms, and enable cross-domain data sharing through a unified authentication platform.

Benefits of technology

Enables secure, reliable, and interoperable cross-domain communication and trust between different urban systems, ensuring user privacy and authenticating identities across regions, thereby facilitating seamless data sharing and service access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071006A_ABST
    Figure CN119071006A_ABST
Patent Text Reader

Abstract

The invention relates to a cross-domain intercommunication and mutual trust method based on a comprehensive code model, which comprises a set of mature trusted digital identity safety cross-domain transmission communication method, and relates to two technologies, namely a cross-domain intercommunication technology based on the comprehensive code model and a cross-domain mutual trust technology based on the comprehensive code model. The cross-domain mutual trust technology based on the comprehensive code model mainly comprises a digital identity security trusted technology, a digital identity collaborative management technology and a digital identity identification conversion technology. The cross-domain intercommunication technology based on the comprehensive code model mainly comprises a cross-domain code verification technology and a cross-domain data sharing technology. According to the method, cross-domain intercommunication and mutual trust technology fusion based on the comprehensive code model is realized, so that intercommunication and mutual trust of comprehensive codes among cities can be realized, reliable and trusted digital transmission technology implementation is provided for one-code universality and multi-code fusion, and a specific application method is provided for privacy protection and cross-domain communication.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the field of data security technology (G06F21 / 71G16Y40 / 50), and specifically relates to a cross-domain intercommunication technology based on a comprehensive code model, including a set of mature trusted digital identity security cross-domain transmission communication methods. Background Art

[0002] As the construction and development of smart cities enter the deep water zone, urban interconnection is undoubtedly a new form of future urban development. In the current cross-system urban service application scenarios, there are problems such as independent urban services, lack of interoperability standards, and difficulty in data sharing. For this reason, this patent studies the cross-domain interoperability technology based on the comprehensive code model. By establishing a service association routing model, the association relationship between urban services is formed, and on this basis, the cross-domain interconnection routing forwarding capability is constructed to horizontally connect urban services and reengineer the process to achieve borderless access to urban services. For the cross-domain interoperability of the special achievement itself, it is not only a study of the technical implementation of cross-domain interoperability, but also an innovative exploration of the interconnection of domestic Internet industry services.

[0003] However, there are many identity authentication platforms on the market today. These platforms generally have problems such as incomplete data, unknown data sources, lack of authoritative trust roots, and illegal collection or excessive privacy of mobile phone users, which makes identity authentication unreliable and user privacy cannot be guaranteed. By introducing the national "Internet +" trusted identity authentication platform, public key infrastructure system and other technologies, trusted identity authentication can be achieved on the basis of ensuring personal privacy. At the same time, in order to solve the problem of non-interoperability between city platforms, the self-developed digital identity conversion technology is used to enable users of different city platforms to achieve cross-domain mutual trust. At the same time, cities cannot bypass this system to achieve digital identity conversion, which can prevent private cross-domain authentication without user authorization and protect user privacy.

[0004] Cross-domain mutual trust technology based on the comprehensive code model. The cross-domain mutual trust system based on trusted digital identity is a specific implementation of cross-domain mutual trust technology. Its purpose is to build a unified, authoritative, and mutually trusted identity and identity code authentication capability based on the national "Internet +" trusted identity authentication platform (CTID platform) (http: / / www.anicert.cn / platform.html), and use the authentication platform to give the trust root to create and manage trusted digital identities. By combining trusted digital identities with comprehensive code models, the identity code authentication capability is used to verify the authenticity of the digital identity carried by the comprehensive code in the cross-domain code verification scenario, and the digital identity conversion technology is used to associate the user identity of each city code, so as to achieve identity mutual trust in multiple places and scenarios. Through a unified management method and standardized service interface, it provides functions such as digital identity application, digital identity authentication, digital identity conversion, and digital identity life cycle management.

[0005] The present invention aims to address the difficulties of multi-code compatibility, application non-intercommunication, and data non-trust, and to study the cross-domain intercommunication technology of codes based on the comprehensive code model. By parsing and identifying the code information, indexing the associated source city code platform, and forwarding the request using the code exchange route, the intercommunication and mutual recognition of comprehensive codes in different regions and different systems can be realized. In view of the non-trust of user identities across regions and systems, the cross-domain mutual trust technology based on trusted digital identities is studied. The trusted identity authentication platform grants a trust root and creates a digital identity based on it. The cross-regional and cross-system mutual trust of comprehensive codes is realized through the trusted digital identity authentication technology. Thus, the cross-domain intercommunication and cross-domain mutual trust methods are integrated to form a cross-domain intercommunication and mutual trust technology based on the comprehensive code model, which has high guiding significance and application value. Summary of the invention

[0006] In view of the existing deficiencies in the research on one-code universal technology and the imperfections of the current existing methods, the present invention constructs a cross-domain intercommunication and mutual trust method based on a comprehensive code model, studies the cross-domain intercommunication step and the cross-domain mutual trust step respectively, and combines them to form a cross-domain intercommunication and mutual trust method based on a comprehensive code model that has practical guiding significance for the comprehensive code model.

[0007] The cross-domain intercommunication and mutual trust method based on the comprehensive code model of the present invention includes a cross-domain intercommunication step based on the comprehensive code model and a cross-domain mutual trust step based on the comprehensive code model. The two steps are mutually based and complementary. The cross-domain mutual trust step based on the comprehensive code model provides a basis for identity authentication for the cross-domain intercommunication step based on the comprehensive code. The cross-domain intercommunication step based on the comprehensive code provides data source and identity information for the cross-domain mutual trust step based on the comprehensive code model, forming a cross-domain intercommunication and mutual trust method based on the comprehensive code model, including the following steps:

[0008] Step S01: The user applies for a digital identity in the target city in the system;

[0009] Step S02: Submit the user request within the system, and the system enters the cross-domain mutual trust step based on the comprehensive code model.

[0010] If the system cross-domain mutual trust verification is passed, then go to step S03; if the system cross-domain mutual trust verification is not passed,

[0011] Then proceed to step S04;

[0012] Step S03: the system enters the cross-domain intercommunication step based on the comprehensive code model;

[0013] Step S04: The system returns the cross-domain intercommunication result to the user, and returns the digital identity of the user in the target city.

[0014] Among them, the cross-domain mutual trust step based on the comprehensive code model and the cross-domain intercommunication step based on the comprehensive code model mainly include the following sub-steps:

[0015] Step 1: The cross-domain mutual trust technology based on the comprehensive code model involves multiple key sub-steps, including the secure and reliable digital identity generation step, the digital identity collaborative management step, and the digital identity conversion step:

[0016] (1) Steps for generating a secure and reliable digital identity

[0017] The steps for generating a secure and reliable digital identity are to connect to the national "Internet+" trusted identity authentication platform, use real identity documents such as identity cards and passports issued by specific administrative agencies and used by the whole society with legal validity as data sources in accordance with relevant laws and regulations, and desensitize user information to ensure that user information is not leaked, thereby achieving digital identity credibility; the digital identity is signed through the national secret algorithm to prevent the digital identity from being forged and tampered with, thereby achieving digital identity security.

[0018] (2) Steps for collaborative digital identity management

[0019] Digital identity has differences and uniformity. By assigning different digital identity identifiers to different city platforms, each city platform can develop its own business, which is the difference; the digital identity identifiers of different city platforms can correspond to the same digital identity, which is the uniformity. In order to effectively manage digital identities, we have developed digital identity collaborative management technology. Since the digital identity identifiers of each city platform and the digital identity are in a many-to-one relationship, a unique digital identity can be found through the digital identity identifier. By managing this unique digital identity, the purpose of managing one city platform and synchronizing various city platforms can be achieved, that is, collaborative management.

[0020] (3) Digital identity conversion steps

[0021] The digital identity conversion steps can convert different city identities to each other. The specific process is as follows:

[0022] First, convert the city A ID into a unique trusted identity, then combine the unique trusted identity with the city code, and generate the city B ID through a self-developed algorithm. This technology can solve the problem of cross-domain digital identity.

[0023] The overall steps satisfy the following functions:

[0024] 1. Digital identity application, including digital identity application, digital identity application request, digital identity application verification code sending, and digital identity application secondary request.

[0025] 2. Digital identity management, including digital identity management application, digital identity freezing, digital identity thawing, digital identity cancellation, and digital identity status inquiry.

[0026] 3. Trusted identity code generation, including trusted identity code generation application and trusted identity code generation request.

[0027] 4. Trusted identity verification code.

[0028] Step 2: The cross-domain intercommunication step based on the comprehensive code model divides the cross-domain request of urban services into three stages: registration / subscription stage, health check stage, and cross-domain application stage.

[0029] City service registration / subscription stage: You can register or subscribe to city services on the web. The city service will first register the service in the system. When the service is subscribed successfully, the city service routing data will be processed according to the city service routing association coordination rules.

[0030] Monitoring and detection phase: The system will query the health detection interface based on the city service routing data, and call the interface through HTTP to complete the health detection. The time period of the health detection is set to seconds, such as 3 seconds, 5 seconds or 10 seconds. After detecting a service abnormality, the service status will be set to unavailable in the system until it is detected that the service status has been restored.

[0031] Cross-domain application stage: The city service submits a cross-domain request to the system. The system determines whether there are corresponding routing rules and whether the city service status is normal. When all routing conditions are met, the cross-domain request is forwarded to the target city service, and the cross-domain request result is responded to the source city service.

[0032] The overall steps satisfy the following functions:

[0033] 1. Cross-domain code verification: Provides cross-domain code verification function. By identifying the city identifier of the comprehensive code, it can complete the query of routing resources associated with the city service, and forward the code verification request to the corresponding city service according to the routing resources, ultimately realizing the cross-domain code verification function of the comprehensive code.

[0034] 2. Cross-domain data sharing, providing data sharing channels between city services. By identifying the city service digital identity and the city identity, it can complete the digital identity conversion between cities and query the routing resources associated with the city service. According to the routing resources, the data sharing request is forwarded to the corresponding city service. After receiving the data sharing request, the city service responds to the requester through the data sharing service, ultimately realizing the data sharing function.

[0035] The beneficial effects of the present invention are:

[0036] 1. The present invention studies the steps of cross-domain intercommunication of codes based on the comprehensive code model, and realizes the intercommunication and mutual recognition of comprehensive codes between different regions and different systems.

[0037] 2. The present invention studies the cross-domain mutual trust steps based on trusted digital identities. The trusted identity authentication platform grants a trust root and uses it to create a digital identity. Through the trusted digital identity authentication steps, the cross-regional and cross-system mutual trust of the comprehensive code is realized.

[0038] 3. Based on the above effects, the present invention integrates the cross-domain intercommunication and cross-domain mutual trust steps to form a cross-domain intercommunication and mutual trust method based on a comprehensive code model, which has high guiding significance and application value. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 This is an overview of the cross-domain mutual trust steps based on the comprehensive code model.

[0040] Figure 2 The following is an overview of the steps for cross-domain intercommunication based on the integrated code model.

[0041] Figure 3 This is a flowchart of the sub-steps of applying for digital identity in the cross-domain mutual trust step based on the comprehensive code model.

[0042] Figure 4 The flowchart of the digital identity collaborative management sub-steps of the cross-domain mutual trust step based on the comprehensive code model.

[0043] Figure 5 The flowchart of the digital identity conversion sub-steps of the cross-domain mutual trust step based on the comprehensive code model.

[0044] Figure 6 The flowchart is a cross-domain code verification sub-step of the cross-domain intercommunication step based on the comprehensive code model.

[0045] Figure 7 The flowchart is a cross-domain data sharing sub-step of the cross-domain intercommunication step based on the comprehensive code model. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention is further described in detail below in combination with specific implementation methods and with reference to the accompanying drawings. It should be understood that the embodiments provided below are only for the purpose of fully and comprehensively disclosing the present invention and fully conveying the technical concept of the present invention to those skilled in the art, but are not intended to limit the scope of the present invention.

[0047] The cross-domain intercommunication and mutual trust steps based on the comprehensive code model of the present invention mainly include the following functions:

[0048] Step 1: Cross-domain mutual trust technology based on the comprehensive code model. It mainly includes the secure and reliable digital identity generation sub-step, the digital identity collaborative management sub-step, and the digital identity conversion sub-step. It mainly meets the following requirements:

[0049]

[0050]

[0051] The steps of cross-domain mutual trust based on the comprehensive code model are as follows:

[0052] Step S11: The system provides a secure and reliable digital identity through user identity information

[0053] Step S111: The user submits an application for digital identity in the system;

[0054] Step S112: the system performs desensitization processing on the submitted user information;

[0055] Step S113: The system signs the digital identity using the national encryption algorithm;

[0056] Step S114: The system assigns a digital identity to the user.

[0057] Step S12: The system maintains the digital identity of users between different city systems and collaboratively manages the digital identity of users between different city platforms:

[0058] Step S121: The system associates the digital identity of each city platform with the digital identity of the user through a relational database;

[0059] Step S122: the system searches for the city platform digital identity identifier corresponding to the user's unique digital identity;

[0060] Step S123: The system manages the user's unique digital identity and implements synchronous and collaborative management of various city platforms. Step S13: The system provides a digital identity conversion identifier between different cities:

[0061] Step S131: The system converts the digital identity of the user in city A into a unique and trusted identity;

[0062] Step S132: The system combines the unique trusted identity with the city code;

[0063] Step S133: The system generates a target city B identifier to implement digital identity conversion.

[0064] In the cross-domain mutual trust step based on the comprehensive code model, the system provides a secure and reliable digital identity step through user identity information, including the following sub-steps:

[0065] Step S21: The user submits an application for digital identity in the system;

[0066] Step S22: the system front end sends a digital identity application request to the back end;

[0067] Step S23: The system determines whether the digital identity application request is successful. If successful, it proceeds to step S24.

[0068] Otherwise, the application fails.

[0069] Step S24: The system verifies whether the network certificate is cancelled or not activated. If successful, it proceeds to step S25.

[0070] Otherwise, the application fails.

[0071] Step S25: The system sends a digital identity application verification code to the user, and then proceeds to step S26 after the user returns the verification code;

[0072] Step S26: the system front end sends a secondary request for digital identity application to the back end;

[0073] Step S27: The system determines whether the digital identity application is successful and returns the corresponding result.

[0074] In the cross-domain mutual trust step based on the comprehensive code model, the system maintains the digital identity of users between different city systems and collaboratively manages the digital identity identification of users between different city platforms, including the following sub-steps:

[0075] Step S31: The system performs parameter verification on the request sent by the front end

[0076] Step S32: The system determines whether the parameter verification is passed. If it is passed, the digital identity management result is returned; if it is not passed, the system proceeds to step S33.

[0077] Step S33: Send a trusted digital identity authentication application interface request within the system

[0078] Step S34: The system returns the digital identity management application result

[0079] In the cross-domain mutual trust step based on the comprehensive code model, the system provides a digital identity conversion identification step between different cities, including the following sub-steps:

[0080] Step S41: The system performs parameter verification on the request sent by the front end

[0081] Step S42: The system determines whether the parameter verification is passed. If it is passed, the digital identity conversion result is returned; if it is not passed, the system proceeds to step S43.

[0082] Step S43: Send a trusted digital identity conversion application interface request within the system

[0083] Step S44: The system returns the result of the digital identity conversion application

[0084] Among them, the flowcharts of digital identity security and trustworthiness steps, digital identity collaborative management steps, and digital identity conversion steps can refer to the attached drawings in the specification.

[0085] Step 2: The cross-domain intercommunication step based on the comprehensive code model is based on the identity authentication function provided by the cross-domain mutual trust step based on the comprehensive code model. It mainly includes the cross-domain code verification step and the cross-domain data sharing step. It mainly meets the following requirements:

[0086]

[0087]

[0088] In the cross-domain mutual trust step based on the comprehensive code model, the cross-domain intercommunication step based on the comprehensive code model includes the following sub-steps:

[0089] Step S51: The system applies to the corresponding city platform for cross-domain data sharing services;

[0090] Step S52: The system enters the cross-domain code verification step to verify the user comprehensive code information between different city platforms.

[0091] If the cross-domain verification is passed, the process proceeds to step S53; otherwise, the result indicating that the cross-domain verification failed is returned;

[0092] Step S53: The system enters the cross-domain data sharing step.

[0093] In the cross-domain mutual trust step based on the comprehensive code model, the cross-domain code verification step includes the following sub-steps:

[0094] Step S61: the system performs parameter verification on the request sent by the front end;

[0095] Step S62: The system determines whether the parameter verification is passed. If not, the system returns a cross-domain verification failure; if passed, the system proceeds to step S63;

[0096] Step S63: The system analyzes the user identity comprehensive code returned by the city platform;

[0097] Step S64: The system determines whether the user's signature verification in the city platform has passed. If so, the system proceeds to step S65; otherwise, the system returns a cross-domain verification failure.

[0098] Step S66: the system queries routing resources between city platforms;

[0099] Step S67: The system determines whether it has the cross-domain code verification permission. If it has the permission, it proceeds to step S68; otherwise, it returns that the cross-domain code verification failed;

[0100] Step S68: The system forwards the cross-domain verification code request to the target city platform;

[0101] Step S69: The system verifies the comprehensive code of the target city platform user and determines whether the cross-domain code verification is passed. If the cross-domain code verification is passed, the system proceeds to step S610; otherwise, the system returns a cross-domain code verification failure.

[0102] Step S610: The system converts the user's digital identity BID on the target city platform;

[0103] Step S611: The system returns the cross-domain code verification request result.

[0104] In the cross-domain mutual trust step based on the comprehensive code model, the cross-domain data sharing step includes the following sub-steps:

[0105] Step S71: the system performs parameter verification on the request sent by the front end;

[0106] Step S72: The system determines whether the parameter verification is passed, and if so, proceeds to step S73; otherwise, a cross-domain data sharing failure result is returned;

[0107] Step S73: the system performs routing resource query;

[0108] Step S74: The system determines whether the cross-domain data sharing authority is available. If so, the system proceeds to step S75; otherwise, the system returns a result indicating that the cross-domain data sharing fails.

[0109] Step S75: The system converts the digital identity BID of the user in the source city into the BID of the user in the target city;

[0110] Step S76: The system forwards the data sharing request to the target city and applies for the digital identity of the user in the target city;

[0111] Step S77: The system returns the data sharing request result.

[0112] Among them, the cross-domain code verification steps and cross-domain data sharing steps can refer to the attached drawings of the specification.

Claims

1. A cross-domain intercommunication and mutual trust method based on a comprehensive code model, The following steps are involved: Step S11: The user applies for a digital identity in the target city in the system; Step S12: Submit the user request in the system, and the system enters the cross-domain mutual trust step based on the comprehensive code model. If the system cross-domain mutual trust verification is passed, it enters step S13; if the system cross-domain mutual trust verification is not passed, it enters step S14; Step S13: the system enters the cross-domain intercommunication step based on the comprehensive code model; Step S14: The system returns the cross-domain intercommunication result to the user, and returns the digital identity of the user in the target city.

2. The cross-domain mutual communication and mutual trust method according to claim 1, wherein the cross-domain mutual trust step based on the comprehensive code model comprises the following sub-steps: Step S21: The system provides a secure and reliable digital identity through user identity information: Step S211: The user submits an application for digital identity in the system; Step S212: the system performs desensitization processing on the submitted user information; Step S213: The system signs the digital identity using the national encryption algorithm; Step S214: the system assigns a digital identity to the user; Step S22: The system maintains the digital identities of users between different city systems and collaboratively manages the digital identities of users between different city platforms: Step S221: The system associates the digital identity of each city platform with the digital identity of the user through a relational database; Step S221: the system searches for the city platform digital identity identifier corresponding to the user's unique digital identity; Step S221: the system manages the user's unique digital identity to achieve synchronous collaborative management of various city platforms; Step S23: The system provides a digital identity conversion identifier between different cities: Step S231: The system converts the digital identity of the user in city A into a unique and trusted identity; Step S231: The system combines the unique trusted identity with the city code; Step S231: The system generates a target city B identifier to implement digital identity conversion.

3. The cross-domain intercommunication and mutual trust method according to claim 2, wherein the system provides a secure and reliable digital identity step through user identity information, comprising the following sub-steps: Step S31: The user submits an application for digital identity in the system; Step S32: the system front end sends a digital identity application request to the back end; Step S33: The system determines whether the digital identity application request is successful. If successful, the system proceeds to step S34. Otherwise, the system returns that the application failed. Step S34: The system verifies whether the network certificate is cancelled or not activated. If successful, it proceeds to step S35, otherwise it returns application failure; Step S35: The system sends a digital identity claim verification code to the user, and then waits for the user to return the verification code before proceeding to step S36; Step S36: the system front end sends a secondary request for digital identity application to the back end; Step S37: The system determines whether the digital identity application is successful and returns the corresponding result.

4. The cross-domain intercommunication and mutual trust method according to claim 2, wherein the system maintains the digital identity of users between different city systems and collaboratively manages the digital identity identification of users between different city platforms, including the following sub-steps: Step S41: the system performs parameter verification on the request sent by the front end; Step S42: The system determines whether the parameter verification is passed, and if so, returns the digital identity management result; If not passed, proceed to step S44; Step S43: Sending a trusted digital identity authentication application interface request within the system; Step S44: The system returns the digital identity management application result.

5. The cross-domain intercommunication and mutual trust method according to claim 2, wherein the system provides a digital identity conversion identification step between different cities, including the following sub-steps: Step S51: the system performs parameter verification on the request sent by the front end; Step S52: The system determines whether the parameter verification is passed. If it is passed, the digital identity conversion result is returned; if it is not passed, the process proceeds to step S53; Step S53: Sending a trusted digital identity conversion application interface request within the system; Step S54: The system returns the digital identity conversion application result.

6. The cross-domain intercommunication and mutual trust method according to claim 1, wherein the cross-domain intercommunication step based on the integrated code model comprises the following sub-steps: Step S61: The system applies to the corresponding city platform for cross-domain data sharing services; Step S62: The system enters the cross-domain code verification step to verify the user comprehensive code information between different city platforms. If the cross-domain code verification passes, it enters step S63; otherwise, it returns a result that the cross-domain code verification fails; Step S63: The system enters the cross-domain data sharing step.

7. The cross-domain intercommunication and mutual trust method according to claim 6, wherein the cross-domain code verification step comprises the following sub-steps: Step S71: the system performs parameter verification on the request sent by the front end; Step S72: The system determines whether the parameter verification is passed. If not, the system returns a cross-domain verification failure; if passed, the system proceeds to step S73; Step S73: The system analyzes the user identity comprehensive code returned by the city platform; Step S74: The system determines whether the user's signature verification in the city platform has passed. If passed, the system proceeds to Step S75: Otherwise, the cross-domain verification fails. Step S76: the system queries routing resources between city platforms; Step S77: The system determines whether it has the cross-domain code verification permission. If it has the permission, it proceeds to step S78; Otherwise, the cross-domain verification code fails. Step S78: The system forwards the cross-domain verification code request to the target city platform; Step S79: The system verifies the comprehensive code of the target city platform user and determines whether the cross-domain code verification is passed. If the cross-domain code verification is passed, the system proceeds to step S710; otherwise, the system returns a cross-domain code verification failure. Step S710: The system converts the user's digital identity BID on the target city platform; Step S711: The system returns the result of the cross-domain code verification request.

8. The cross-domain intercommunication and mutual trust method according to claim 6, wherein the cross-domain data sharing step comprises the following sub-steps: Step S81: the system performs parameter verification on the request sent by the front end; Step S82: The system determines whether the parameter verification is passed, and if so, proceeds to step S83; otherwise, a cross-domain data sharing failure result is returned; Step S83: the system performs routing resource query; Step S84: The system determines whether the cross-domain data sharing authority is available. If so, the system proceeds to step S85; otherwise, the system returns a result indicating that the cross-domain data sharing fails. Step S85: The system converts the digital identity BID of the user in the source city into the BID of the user in the target city; Step S86: The system forwards the data sharing request to the target city and applies for the user's digital identity in the target city; Step S87: The system returns the data sharing request result.