A blockchain-based credit evaluation method and related device

Abstract

The specification provides a blockchain-based credit evaluation method and related equipment. A plurality of distributed applications are deployed on a blockchain, and at least part of the plurality of distributed applications publish credit features on the blockchain. The method comprises: obtaining a credit feature of a target user corresponding to a first distributed application in the plurality of distributed applications; the credit feature comprises a credit feature calculated by a second distributed application in the at least part of the applications based on user data of the target user in the second distributed application and published on the blockchain; the user data is user data related to user credit generated in the second distributed application after the target user logs in the second distributed application by using a target distributed digital identity registered by the target user on the blockchain; converting the credit feature into a credit feature conforming to a credit evaluation strategy of the first distributed application, and evaluating a credit level of the target user in the first distributed application based on the converted credit feature.

Description

Technical Field

[0001] This specification relates to one or more embodiments in the field of blockchain technology, and in particular to a blockchain-based credit assessment method and related equipment. Background Technology

[0002] In a web3.0 distributed identity system built on blockchain, each user can log in to multiple distributed applications deployed on the blockchain based on their decentralized digital identity (DID) registered on the blockchain, and use the services provided by each distributed application.

[0003] As the number of distributed applications deployed on blockchains continues to increase, and the services they provide become increasingly diverse, the lack of constraints on user behavior within these applications can easily disrupt the blockchain's balance and compromise the fairness and security of the distributed applications. A common approach is to constrain user behavior based on their credit rating. Therefore, efficiently and accurately assessing user credit ratings within distributed applications is a pressing issue that needs to be addressed. Summary of the Invention

[0004] In view of this, one or more embodiments of this specification provide a blockchain-based credit assessment method and related equipment.

[0005] Firstly, this specification provides a blockchain-based credit assessment method, on which multiple distributed applications are deployed; wherein at least some of the multiple distributed applications publish credit characteristics on the blockchain; the method includes:

[0006] Obtain the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain;

[0007] The credit features are converted into credit features that conform to the credit assessment strategy of the first distributed application, and the credit rating of the target user in the first distributed application is assessed based on the converted credit features.

[0008] Secondly, this specification provides a login management method for distributed applications, wherein multiple distributed applications are deployed on a blockchain; wherein at least some of the multiple distributed applications have published credit features on the blockchain; the method includes:

[0009] Obtain the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain;

[0010] Based on the credit characteristics, assess the credit rating of the target user in the first distributed application;

[0011] In response to the target user logging into the first distributed application based on the target DID, based on the assessed credit rating of the target user, it is determined whether the target user has access to multiple services included in the first distributed application;

[0012] Provide the target user with at least a portion of the multiple services, of which the target user has access rights.

[0013] Thirdly, this specification provides a service management method for distributed applications, wherein multiple distributed applications are deployed on a blockchain; wherein at least some of the multiple distributed applications publish credit features on the blockchain; the method includes:

[0014] Obtain the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain;

[0015] Based on the credit characteristics, assess the credit rating of the target user in the first distributed application;

[0016] In response to the target user's access request for the target service provided by the first distributed application, the service level of the target service for the target user is determined based on the assessed credit rating.

[0017] Based on the service level, determine the service content corresponding to the service provided by the target service to the target user, and provide the service content to the target user.

[0018] Fourthly, this specification provides a blockchain-based credit assessment device, on which multiple distributed applications are deployed; wherein at least some of the multiple distributed applications publish credit characteristics on the blockchain; the device includes:

[0019] An acquisition unit is configured to acquire the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain;

[0020] A credit assessment unit is used to convert the credit features into credit features that conform to the credit assessment strategy of the first distributed application, and to assess the credit rating of the target user in the first distributed application based on the converted credit features.

[0021] Fifthly, this specification provides a login management device for distributed applications, wherein multiple distributed applications are deployed on a blockchain; wherein at least some of the multiple distributed applications have published credit features on the blockchain; the device includes:

[0022] An acquisition unit is configured to acquire the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain;

[0023] A credit assessment unit is used to assess the credit rating of the target user in the first distributed application based on the credit characteristics.

[0024] The login management unit is configured to respond to the target user's authorization to log in to the first distributed application based on the target DID, determine whether the target user has access to multiple services included in the first distributed application based on the assessed credit rating of the target user, and provide the target user with at least a portion of the multiple services for which the target user has access.

[0025] Sixthly, this specification provides a service management device for distributed applications, wherein multiple distributed applications are deployed on a blockchain; wherein at least some of the multiple distributed applications have published credit features on the blockchain; the device includes:

[0026] An acquisition unit is configured to acquire the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain;

[0027] A credit assessment unit is used to assess the credit rating of the target user in the first distributed application based on the credit characteristics.

[0028] The service management unit is configured to respond to the target user's access request for the target service provided by the first distributed application, determine the service level of the target service for the target user based on the assessed credit rating, determine the service content corresponding to the service provided by the target service for the target user based on the service level, and provide the service content to the target user.

[0029] Accordingly, this specification also provides a computer device, including: a memory and a processor; the memory stores a computer program that can be executed by the processor; when the processor runs the computer program, it executes the credit assessment method described in the first aspect above, or executes the login management method of the distributed application described in the second aspect above, or executes the service management method of the distributed application described in the third aspect above.

[0030] Accordingly, this specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the credit assessment method as described in the first aspect above, or the login management method for a distributed application as described in the second aspect above, or the service management method for a distributed application as described in the third aspect above.

[0031] In summary, this application allows multiple distributed applications deployed on a blockchain to calculate user credit characteristics based on their respective user data. Furthermore, these distributed applications can publish the calculated credit characteristics to the blockchain. Further, any distributed application deployed on the blockchain can obtain credit characteristics published by other distributed applications and, considering the differences in services provided by different distributed applications, can convert these credit characteristics into credit characteristics that conform to its own credit assessment strategy. Finally, the distributed application can assess the user's credit rating within that distributed application based on the converted credit characteristics. Thus, this application, leveraging the information-sharing capabilities of blockchain, can obtain a large number of credit characteristics published by distributed applications and, combined with the credit assessment strategy of each distributed application, efficiently and accurately calculate the user's credit rating in each distributed application. This achieves the construction of a distributed identity credit system based on distributed applications, enabling the constraint of user behavior in each distributed application after the user logs in with a distributed identity, effectively ensuring the fairness and security of the distributed applications. Attached Figure Description

[0032] Figure 1 This is a schematic diagram of a system architecture provided in an exemplary embodiment;

[0033] Figure 2 This is a schematic diagram of a blockchain-based credit assessment method provided in an exemplary embodiment;

[0034] Figure 3 This is a flowchart illustrating a service management method for a distributed application, provided in an exemplary embodiment.

[0035] Figure 4 This is a schematic diagram of the structure of a blockchain-based credit assessment device provided in an exemplary embodiment;

[0036] Figure 5 This is a schematic diagram of the structure of a computer device provided in an exemplary embodiment. Detailed Implementation

[0037] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0038] It should be noted that the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification in other embodiments. In some other embodiments, the methods may include more or fewer steps than described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments.

[0039] It should be noted that "multiple" as used in this application refers to two or more.

[0040] Furthermore, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. The collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0041] (1) Distributed applications (DApps), also known as decentralized applications, are a type of application that differs from traditional centralized applications. Traditional centralized applications typically use a centrally deployed server as the service backend, while distributed applications use service contracts deployed on the blockchain as the service backend. For example, a typical distributed application usually consists of two parts: the service contract as the service backend and the user interface (UI) at the front end.

[0042] (2) Distributed Digital Identity (DID), also known as decentralized identity, is a globally unique, persistently stored, and tamper-proof personal identifier. A distributed identity is entirely controlled by its owner (individual or organization) and does not rely on a centralized platform or identity provider. Building a decentralized unified identity authentication system based on DID is one of the important practices in the development of Web3.0.

[0043] As described above, users can log in to multiple distributed applications deployed on the blockchain based on a distributed identity registered (or created) on the blockchain, and use the services provided by each distributed application. For example, the multiple distributed applications may include financial applications, whose services may include money transfer services, deposit services, and investment and wealth management services. For example, the multiple distributed applications may also include game applications, whose services may include game services, in-game instant messaging services, and the purchase of game skins, etc., which are not specifically limited in this specification.

[0044] However, as the number of distributed applications deployed on the blockchain continues to increase, and the services they provide become more diverse, the lack of constraints on user behavior within these applications can easily disrupt the blockchain's balance and compromise the fairness and security of the distributed applications. A common approach is to constrain user behavior based on their credit rating; for example, users with lower credit ratings could be prohibited from accessing certain services within the distributed application.

[0045] Based on this, this specification provides a technical solution in which any distributed application on the blockchain can efficiently and accurately assess a user's credit rating based on the user credit characteristics shared by other distributed applications and combined with its own credit assessment strategy.

[0046] In its implementation, this application can be applied to a first distributed application among multiple distributed applications deployed on a blockchain; wherein the blockchain can store credit features published by at least some of the multiple distributed applications. First, the first distributed application can obtain the credit features of a target user; wherein the credit features of the target user can include credit features calculated and published by a second distributed application within the aforementioned at least some applications, based on the target user's user data in the second distributed application. The user data can be user credit-related data generated in the second distributed application after the target user logs in using their registered target distributed identity on the blockchain. Further, the first distributed application can convert the obtained credit features published by the second distributed application into credit features conforming to the first distributed application's credit assessment strategy, and assess the target user's credit rating in the first distributed application based on the converted credit features.

[0047] In the above technical solution, multiple distributed applications deployed on the blockchain can calculate user credit characteristics based on their respective user data. Furthermore, these distributed applications can publish the calculated credit characteristics on the blockchain. Further, any distributed application deployed on the blockchain can obtain credit characteristics published by other distributed applications on the blockchain. Considering the differences in services provided by different distributed applications, it can convert the credit characteristics published by other distributed applications into credit characteristics that conform to its own credit assessment strategy. Finally, the distributed application can assess the user's credit rating within that distributed application based on the converted credit characteristics. Thus, this application can leverage the information sharing capabilities of the blockchain to obtain a large number of credit characteristics published by distributed applications. Combined with the credit assessment strategy of each distributed application, it can efficiently and accurately calculate the user's credit rating in each distributed application, thereby realizing the construction of a distributed identity credit system based on distributed applications. This allows for the subsequent constraint of user behavior in each distributed application after the user logs in based on their distributed identity, effectively ensuring the fairness and security of the distributed applications.

[0048] Please see Figure 1 , Figure 1 This is a schematic diagram of a system architecture provided in an exemplary embodiment. One or more embodiments provided in this description can be used... Figure 1 The specific implementation is within the system architecture shown or a similar system architecture. For example... Figure 1 As shown, the system can include multiple blockchain nodes in a blockchain network, specifically blockchain node a, blockchain node b, and blockchain node c. Blockchain nodes a, b, and c can establish communication connections with each other via any possible wired or wireless means.

[0049] like Figure 1 As shown, the system architecture also includes computer devices that interface with the aforementioned multiple blockchain nodes, such as computer device 100a interfaced with blockchain node a, computer device 100b interfaced with blockchain node b, computer device 100c interfaced with blockchain node c, and so on. Figure 1 As shown, the aforementioned computer devices can be located outside the chain.

[0050] In one of the illustrated embodiments, the deployer (or operator) of the distributed application can deploy the corresponding distributed application on the blockchain, including deploying a service contract on the blockchain as the service backend of the distributed application. The service contract can be responsible for the core on-chain logic of the distributed application. For details, please refer to the description of the following embodiments, which will not be elaborated here.

[0051] It should be noted that this manual does not impose any specific limitations on the implementation methods for deploying distributed applications.

[0052] In one illustrated implementation, the deployer of the distributed application can deploy the corresponding distributed application on a computer device that interfaces with the blockchain node. For example... Figure 1 As shown, a distributed application a can be deployed on a computer device 100a that interfaces with blockchain node a. Correspondingly, a client a corresponding to the distributed application a can be installed on the computer device 100a. Client a provides the front-end user interface for the distributed application a. Figure 1 As shown, a distributed application b can be deployed on computer device 100b, which interfaces with blockchain node b. Correspondingly, a client b corresponding to this distributed application b can be installed on computer device 100b. For example... Figure 1 As shown, a distributed application c can be deployed on a computer device 100c that interfaces with the blockchain node c. Correspondingly, a client c corresponding to the distributed application c can be installed on the computer device 100c, and so on.

[0053] In one of the illustrated embodiments, the deployer of the distributed application can also directly deploy the corresponding distributed application on the blockchain node in the blockchain network. For example, the distributed application a can be directly deployed on blockchain node a, the distributed application b can be directly deployed on blockchain node b, and so on. This specification does not make any specific limitations in this regard.

[0054] It should be noted that this manual does not specifically limit the types of distributed applications.

[0055] In some possible implementations, the distributed applications a, b, and c described above can be game applications, video applications, financial applications, recruitment applications, or instant messaging applications, etc., and this specification does not make any specific limitations on them.

[0056] It should be understood that different types of distributed applications can provide different services to users. For example, taking distributed application A as a game application, distributed application A can provide game services with multiple game modes, in-game instant messaging services, and the purchase of game skins, etc., without specific limitations in this specification. For example, taking distributed application A as a financial application, distributed application B can provide transfer services, deposit services, investment and wealth management services, and advance asset services, etc., without specific limitations in this specification. For example, taking distributed application C as a recruitment application, distributed application C can provide instant messaging services and resume submission services, etc., without specific limitations in this specification.

[0057] In some possible implementations, users can log in to the aforementioned distributed applications a, b, and c based on their distributed identities registered on the blockchain and use the services provided by each distributed application.

[0058] Furthermore, each distributed application can assess a user's credit rating and limit the services provided to the user based on the assessed credit rating, thus constraining the user's operational behavior in the distributed application and ensuring the fairness and security of the distributed application.

[0059] In one illustrated implementation, each distributed application can calculate the user's credit characteristics based on the user data generated in the distributed application after the user logs in with their corresponding distributed identity, and then assess the user's credit rating in each distributed application based on the calculated credit characteristics.

[0060] For example, taking distributed application a among the above distributed applications as an example, distributed application a can obtain user data related to user credit generated in distributed application a after the target user logs in to distributed application a with a distributed identity, calculate the target user's credit feature a, and evaluate the target user's credit rating in distributed application a based on the calculated credit feature.

[0061] For example, taking distributed application b among the above distributed applications as an example, distributed application b can obtain user data related to user credit generated in distributed application b after the target user logs in to distributed application b with a distributed identity, calculate the target user's credit feature b, and evaluate the target user's credit rating in distributed application b based on the calculated credit feature.

[0062] It is understandable that because different distributed applications have different service characteristics, their credit requirements for users will also differ, leading to different credit ratings for the same user in different distributed applications. For example, taking distributed application A as a financial application and distributed application B as a game application, generally, financial applications have higher credit requirements for users. Therefore, the credit rating of the aforementioned target user in distributed application A may often be lower than their credit rating in distributed application B. This specification does not make specific limitations in this regard.

[0063] In one illustrated implementation, in addition to using its own calculated credit features to assess a user's credit rating, a distributed application can also use credit features shared by other distributed applications to assess a user's credit rating.

[0064] In one illustrated implementation, at least some of the distributed applications deployed on the blockchain can publish calculated credit features to the blockchain, and correspondingly, the credit features published by these at least some applications can be stored on the blockchain.

[0065] Furthermore, any one of the multiple distributed applications can obtain credit features published by other distributed applications and assess the user's credit rating based on the credit features published by other distributed applications.

[0066] For example, the distributed application a can publish the calculated credit feature a to the blockchain. Furthermore, the distributed application b can obtain the credit feature a and evaluate the credit rating of the target user in the distributed application b based on the credit feature a.

[0067] In one illustrated implementation, since distributed application a and distributed application b have different service characteristics, their credit assessment strategies will also differ. Directly using credit feature a calculated by distributed application a to assess the target user's credit rating in distributed application b may not be accurate enough. Therefore, when distributed application b assesses the target user's credit rating based on the aforementioned credit feature a, it may specifically include: first converting credit feature a into a credit feature that conforms to the credit assessment strategy of distributed application b, and then assessing the target user's credit rating in distributed application b based on the converted credit feature, in order to ensure the accuracy of the credit assessment. For details, please refer to the description of the following embodiments, which will not be repeated here.

[0068] It should be noted that this specification does not specifically limit the specific implementation methods for distributed applications to publish their own calculated credit features on the blockchain, or to obtain credit features published by other distributed applications.

[0069] In one illustrated embodiment, this application can achieve the publication and acquisition of the aforementioned credit features through a publish-subscribe model.

[0070] For example, consider distributed application b and distributed application c, each subscribing to a credit feature a to be published by distributed application a. Once the event of distributed application a successfully publishing credit feature a on the blockchain is detected, it can broadcast the credit feature a to multiple subscribers (i.e., distributed application b and distributed application c). Correspondingly, distributed application b and distributed application c can receive the broadcast credit feature a.

[0071] It is understandable that when a distributed application a publishes credit feature a on the blockchain, it often needs to reach a consensus on the credit feature a to be published through the consensus nodes in the blockchain. After the consensus is completed, the credit feature a can be successfully published on the blockchain, and so on. This will not be elaborated on here.

[0072] In one of the illustrated embodiments, the blockchain nodes a, b, and c can be consensus nodes or non-consensus nodes, and this specification does not specifically limit them.

[0073] In one illustrated embodiment, the computer devices 100a, 100b, and 100c described above may be smartphones, smart wearable devices, tablets, laptops, desktop computers, servers, or server clusters with the above-described functions, etc., and this specification does not specifically limit them.

[0074] Please see Figure 2 , Figure 2 This is a schematic diagram illustrating a blockchain-based credit assessment method as provided in an exemplary embodiment. This method can be applied to... Figure 1 In the system architecture shown.

[0075] In one illustrated implementation, the method can be specifically applied to a first distributed application among multiple distributed applications deployed on a blockchain; for example, Figure 1 Any one of the distributed applications a, b, and c shown is equal to the given value. For example, Figure 2 The execution logic of steps S201-S202 in the method flow shown can be built into the first distributed application as a plugin.

[0076] In one illustrated embodiment, the method can also be applied to the computer device running the first distributed application; for example, Figure 1 The method can be applied to any one of the computer devices 100a, 100b, and 100c shown; or, the method can also be applied to other computer devices that interface with the first distributed application; for example, the other computer device can specifically be a separate service device that interfaces with the computer device running the distributed application. Figure 2 The execution logic of steps S201-S202 in the method flow shown can be deployed in a computer device in the form of a centralized service. This centralized service is mainly used to manage the user credit rating of users in the first distributed application.

[0077] like Figure 2 As shown, the method may specifically include the following steps S201-S202.

[0078] Step S201: Obtain the credit characteristics of the target user corresponding to the first distributed application among the multiple distributed applications; wherein at least some of the multiple distributed applications have published credit characteristics on the blockchain; the credit characteristics of the target user include credit characteristics published on the blockchain by the second distributed application among the at least some of the applications.

[0079] As mentioned above, multiple distributed applications can be deployed on a blockchain, and at least some of these applications can publish credit features on the blockchain. Correspondingly, the blockchain also stores the credit features published by these at least some applications.

[0080] In one illustrated implementation, when it is necessary to evaluate the target user in the first distributed application among the aforementioned multiple distributed applications (e.g., the one described above) Figure 1 When determining the credit rating in the distributed application a), the first distributed application can first obtain the credit characteristics of the target user.

[0081] It should be noted that, for the sake of convenience in describing the technical solution provided in this application, the following description will take the first distributed application as the execution subject.

[0082] In one illustrated embodiment, the credit characteristics of the target user can be a second distributed application (e.g., the aforementioned) in at least a portion of the applications described above. Figure 1 The distributed application shown in section b) publishes the credit features corresponding to the target user on the blockchain. Specifically, the second distributed application can calculate the target user's credit features based on the user data generated in the second distributed application after the target user logs in using their registered target DID on the blockchain, and then publish these credit features on the blockchain.

[0083] For example, taking the second distributed application as a financial application, the aforementioned user data related to user credit could be the target user's transfer records, loan records, repayment records, and deposit amounts, etc., which are not specifically limited in this specification. For example, taking the second distributed application as a recruitment application, the user data could be the target user's resume submission records, etc., which are not specifically limited in this specification.

[0084] The credit feature can be a credit feature calculated based on the aforementioned user data that conforms to the service characteristics of the second distributed application itself. For example, taking the second distributed application as a financial application, the credit feature calculated based on the aforementioned user data could be a user's good repayment record within 3 months, or a good repayment record within 6 months, etc. This specification does not make specific limitations on this.

[0085] In one illustrated embodiment, in addition to directly obtaining the credit characteristics of the target user published by other distributed applications (such as the second distributed application), the first distributed application can also calculate the credit characteristics of the target user based on its own user data, etc. This specification does not specifically limit this.

[0086] In one illustrated implementation, the first distributed application can calculate the credit characteristics of the target user based on the user data related to user credit generated in the first distributed application after the target user logs in with the target DID.

[0087] Understandably, when the first distributed application has limited user data, especially credit-related data, while the second distributed application has more credit-related data, the first distributed application can directly obtain the credit features calculated and published by the second distributed application, thus providing reliable data support for subsequent credit assessments by the first distributed application. Conversely, when the first distributed application has sufficient credit-related data, it can also directly calculate user credit features based on its own user data.

[0088] Furthermore, it should be noted that this specification does not specifically limit the particular implementation method for calculating credit features based on user data.

[0089] In one illustrated embodiment, each distributed application may also include a pre-built credit model for calculating credit features. It should be noted that this specification does not specifically limit the type of this credit model; in one illustrated embodiment, the credit model may be a neural network model, etc., and this specification does not specifically limit its application.

[0090] For example, the first distributed application may carry a pre-built first credit model. Furthermore, the first distributed model can input user data related to user credit generated in the first distributed application after the target user logs in using the target DID into the first credit model for credit feature calculation, thereby obtaining the target user's credit characteristics.

[0091] For example, a pre-built credit model can also be implemented in the second distributed application. Furthermore, the second distributed model can input the user data generated by the target user in the second distributed application into the credit model of the second distributed application to calculate credit features, thereby obtaining the credit features of the target user, and can publish the calculated credit features on the blockchain for use by other distributed applications (such as the first distributed application mentioned above).

[0092] In one illustrated embodiment, the credit models carried by the aforementioned distributed applications can be built into the distributed applications. Alternatively, in one illustrated embodiment, the credit models carried by the aforementioned distributed applications can also be deployed on the computer device running the distributed application, or on other computer devices that interface with the distributed application. The distributed application can then have a built-in interface for calling the credit model. The distributed application can use this interface to call the credit model deployed on the aforementioned computer device to perform subsequent credit feature calculations, etc. This specification does not impose specific limitations on this.

[0093] In one illustrated implementation, the distributed application can also publish its own credit model to the blockchain. Correspondingly, the blockchain can store credit models published by at least some of the multiple distributed applications. Thus, the distributed application can obtain credit models published by other distributed applications and input its own user data into these models to calculate credit features, thereby obtaining the user's credit characteristics.

[0094] For example, a third distributed application among multiple distributed applications can publish its second credit model on the blockchain. Correspondingly, the first distributed application can obtain the second credit model published on the blockchain by the third distributed application. Then, the user data generated by the target user in the first distributed application is input into the second credit model to calculate the credit features, thereby obtaining the credit features of the target user.

[0095] In some possible implementations, the third distributed application may be the second distributed application described above, or it may be other distributed applications among multiple distributed applications. This specification does not specifically limit this.

[0096] It should be noted that this specification does not impose any specific limitations on the implementation methods of distributed applications publishing their own credit models on the blockchain, or obtaining credit models published by other distributed applications.

[0097] In one illustrated embodiment, as described above Figure 1 Similar to the credit feature publishing process described in the corresponding embodiments, this application can also implement the publishing and acquisition of the above-mentioned credit model through a publish-subscribe model.

[0098] For example, consider a first distributed application subscribing to a second credit model to be published by a third distributed application. Once the event that the third distributed application successfully publishes the second credit model on the blockchain is detected, the second credit model can be broadcast to its subscribers (e.g., the first distributed application). Correspondingly, the first distributed application can receive the broadcast second credit model.

[0099] It is understandable that when a third distributed application publishes a second credit model on the blockchain, it often needs to reach a consensus on the second credit model to be published through consensus nodes in the blockchain. After the consensus is completed, the second credit model can be successfully published on the blockchain, and so on. This will not be elaborated on here.

[0100] Furthermore, in one of the illustrated implementations, corresponding system smart contracts are also deployed on the blockchain.

[0101] In one illustrated implementation, the system smart contract can be used to manage the credit features published on the blockchain by at least some of the aforementioned applications. Correspondingly, the second distributed application can publish its calculated credit features corresponding to the target user on the blockchain by invoking the system smart contract.

[0102] In one illustrated embodiment, the system smart contract can be used to manage the credit model published on the blockchain by at least a portion of the aforementioned applications. Correspondingly, the second distributed application can publish a second credit model on the blockchain by invoking the system smart contract.

[0103] Step S202: Convert the credit features into credit features that conform to the credit assessment strategy of the first distributed application, and assess the credit rating of the target user in the first distributed application based on the converted credit features.

[0104] Given the differences in the services provided by different distributed applications, their credit assessment strategies will also differ. Therefore, in one illustrated embodiment, after obtaining the credit characteristics of the target user calculated and published by the second distributed application, the first distributed application can first convert these credit characteristics into credit characteristics that conform to the credit assessment strategy of the first distributed application, and then assess the target user's credit rating in the first distributed application based on the converted credit characteristics, in order to ensure the accuracy of the credit assessment.

[0105] For example, taking the first distributed application as a recruitment application and the second distributed application as a financial application, the credit characteristics published by the second distributed application could be that the target user has a good repayment record within 6 months. Then, the credit characteristics obtained by converting the above credit characteristics based on the credit assessment strategy of the first distributed application could be that the target user has good work ability, etc. This specification does not make specific limitations on this.

[0106] For example, if both the first distributed application and the second distributed application are financial applications, but the first distributed application has higher credit requirements for users, the credit feature published by the second distributed application can be that the target user has a good repayment record within 6 months. Then, the credit feature obtained by converting the above credit feature based on the credit assessment strategy of the first distributed application can be that the target user has a good repayment record within 3 months, etc. This specification does not make specific limitations in this regard.

[0107] Understandably, the longer a user maintains a good repayment history, the higher their credit rating will be.

[0108] Furthermore, in one illustrated embodiment, service contracts, which serve as service backends for the aforementioned multiple distributed applications, are also deployed on the blockchain.

[0109] In one illustrated implementation, the first distributed application can convert the credit features obtained from the second distributed application published on the blockchain into credit features that conform to the credit assessment strategy of the first distributed application by calling the service contract corresponding to the first distributed application, and assess the credit rating of the target user in the first distributed application based on the converted credit features.

[0110] The service contract can be responsible for the on-chain core logic of the distributed application. For example, this core logic may include feature conversion logic for performing the aforementioned credit feature conversion, and credit assessment logic for performing credit rating assessment based on credit features, etc., which are not specifically limited in this specification.

[0111] In one illustrated implementation, the first distributed application may invoke the feature conversion logic contained in the service contract corresponding to the first distributed application to convert the credit features published by the second distributed application into credit features that conform to the credit assessment strategy of the first distributed application.

[0112] After converting the aforementioned credit characteristics into credit characteristics that conform to the credit assessment strategy of the first distributed application, the first distributed application can further call the credit assessment logic contained in the service contract corresponding to the first distributed application to assess the credit rating of the target user in the first distributed application based on the converted credit characteristics.

[0113] Furthermore, in some possible implementations, the first distributed application may also acquire multiple second distributed applications (e.g., as described above). Figure 1The distributed applications b and c) shown in the figure publish credit features, and convert the credit features published by multiple second distributed applications into credit features that conform to the credit assessment strategy of the first distributed application. Then, based on the converted credit features, the credit rating of the target user in the first distributed application is assessed, etc. This specification does not make specific limitations on this.

[0114] It should be understood that the multiple second distributed applications described in one or more embodiments of this specification refer to other distributed applications that are different from the first distributed application, and do not specifically refer to any one distributed application.

[0115] In one illustrated implementation, if the credit features are calculated based on the first distributed application's own user data, then the aforementioned credit feature conversion is unnecessary, and the calculated credit features can be directly used to assess the target user's credit rating in the first distributed application.

[0116] In one illustrated implementation, if the first distributed application uses a credit model published by another distributed application (such as the second credit model published by the second distributed application mentioned above) when calculating credit features based on its own user data, the calculated credit features can still be converted to obtain credit features that conform to the credit assessment strategy of the first distributed application. Specifically, whether feature conversion is needed can be determined based on the actual service differences between different distributed applications; this specification does not impose specific limitations on this. For example, if both the first and second distributed applications are financial applications, and the differences in the services they provide are small, the credit features calculated by the first distributed application based on the second credit model published by the second distributed application will often conform to the credit assessment strategy of the first distributed application, and therefore feature conversion is not required. For example, if the first distributed application is a game application and the second distributed application is a financial application, and the differences in the services they provide are large, the credit features calculated by the first distributed application based on the second credit model published by the second distributed application often do not conform to the credit assessment strategy of the first distributed application, and therefore feature conversion is required, and so on; this specification does not impose specific limitations on this.

[0117] Furthermore, after the first distributed application assesses and obtains the credit rating of the target user in the first distributed application, the first distributed application can constrain the target user's operations in the first distributed application based on the credit rating, etc. For details, please refer to the description of the following embodiments, which will not be elaborated here.

[0118] Please see Figure 3 , Figure 3 This is a flowchart illustrating a service management method for a distributed application, provided in an exemplary embodiment. This method can be applied to... Figure 1 The system architecture shown can be specifically applied to Figure 1 The system architecture shown illustrates a distributed application. For example... Figure 3 As shown, the method may specifically include the following steps S301-S308.

[0119] Step S301: Obtain the credit features corresponding to the target user published by the second distributed application.

[0120] In one illustrated embodiment, step S301 may refer to the above. Figure 2 The description of step S201 in the corresponding embodiment will not be repeated here.

[0121] Step S302: Convert the credit features into credit features that conform to the credit assessment strategy of the first distributed application.

[0122] In one illustrated embodiment, step S302 may refer to the above. Figure 2 The description of step S202 in the corresponding embodiment will not be repeated here.

[0123] Step S303: Based on the transformed credit characteristics, assess the credit rating of the target user in the first distributed application.

[0124] In one illustrated embodiment, step S303 may refer to the above. Figure 2 The description of step S202 in the corresponding embodiment will not be repeated here.

[0125] Step S304: In response to the target user logging into the first distributed application based on the target DID, determine the target user's access permissions to multiple services included in the first distributed application based on the target user's credit rating.

[0126] In one illustrated implementation, the first distributed application may include multiple services, and the first distributed application may determine the access rights of a target user to the multiple services based on the assessed credit rating.

[0127] In one illustrated implementation, in response to a target user authorizing login to a first distributed application based on a target DID registered on the blockchain, the first distributed application can determine, based on an assessed credit rating, whether the target user has access to multiple services included in the first distributed application.

[0128] For example, if the target user has a low level, the target user may not have access to some of the services among the multiple services. Accordingly, the first distributed application may only provide the target user with the services that he or she has access to (i.e., prohibit the target user from accessing the services that he or she does not have access to).

[0129] For example, taking the first distributed application as a financial application, the services it provides may include: deposit services, transfer services, investment and wealth management services, and asset advance services, etc., where different services may have different credit rating requirements. For example, in the credit assessment strategy of the first distributed application, credit ratings can be divided into four levels: A1, A2, A3, and A4, where level A1 is higher than level A2, level A2 is higher than level A3, and level A3 is higher than level A4.

[0130] For example, if the target user has a credit rating of A1 in the first distributed application, the first distributed application can determine that the target user has access to all services included in the first distributed application, such as deposit services, transfer services, investment and wealth management services, and pre-drawn asset services.

[0131] For example, if the target user has a credit rating of A2 in the first distributed application, the first distributed application can determine that the target user does not have access to the aforementioned prepaid asset services.

[0132] For example, if the target user's credit rating in the first distributed application is A3, the first distributed application can determine that the target user does not have access to the aforementioned pre-drawn asset services and investment and wealth management services. For example, if the target user's credit rating in the first distributed application is A4, the first distributed application can determine that the target user only has access to the aforementioned deposit services, and so on. This specification does not make specific limitations in this regard.

[0133] In one illustrated implementation, if the assessment determines that the target user's credit rating in the first distributed application is extremely low, for example, if the target user's credit characteristics do not meet the conditions of the aforementioned level A4, the target user can be directly prohibited from logging into the first distributed application, etc. This specification does not make specific limitations in this regard.

[0134] Step S305: In response to the target user's access request for the target service provided by the first distributed application, determine whether the target user has access rights to the target service.

[0135] In one illustrated implementation, after a target user logs into the first distributed application based on the target DID, the target user can access the various services contained in the first distributed application.

[0136] In one illustrated embodiment, in response to a target user's access request for a target service among a plurality of services included in a first distributed application, the first distributed application may further determine whether the target user has access to the target service based on the assessed credit rating of the target user.

[0137] For example, if it is determined that the target user does not have access to the target service, then step S306 is executed; if it is determined that the target user has access to the target service, then step S307 is executed.

[0138] Step S306: Prohibit the target user from accessing the target service.

[0139] In one illustrated implementation, if the target user does not have access to the target service, the user's access request for the target service can be denied, i.e., the target user is prohibited from accessing the target service, in order to avoid security issues arising from providing services to users with low credit ratings.

[0140] In one illustrated embodiment, if it is determined that the target user does not have access to the target service, the user interface provided by the first distributed application may not even display the icon corresponding to the target service or the control for accessing the target service to the user, or the control for accessing the target service may be set to an invalid control so that the target user cannot perform a valid click operation on the control, etc. This specification does not make specific limitations in this regard.

[0141] In one illustrated implementation, if the first distributed application contains few services, or even only one service, the first distributed application can by default open all of its services to users of all credit levels. That is, users of all credit levels have access to all services contained in the first distributed application. In other words, the first distributed application does not need to determine the user's access rights for each service based on the assessed credit level, etc. This specification does not make specific limitations in this regard.

[0142] Step S307: Determine the service level of the target service for the target users based on the assessed credit rating.

[0143] In one illustrated implementation, if the first distributed application determines that the target user has access to the target service based on the target user's credit rating, it can receive the target user's access request and provide the target service to the target user.

[0144] Furthermore, when providing target services to target users, the first distributed application can also provide service content corresponding to the target user's credit level within the target service, thereby further constraining the service usage behavior of users with different credit levels and ensuring the fairness and security of the distributed application.

[0145] In one illustrated implementation, the first distributed application may first determine the service level of the target service for the target user based on the assessed credit rating. Further, the first distributed application may provide the target user with the service content included in the target service that corresponds to the service level, based on the determined service level.

[0146] For example, similar to the credit rating classification mentioned above, in the credit assessment strategy of the first distributed application, the service level of the target service can be divided into four levels: B1, B2, B3, and B4, where level B1 is higher than level B2, level B2 is higher than level B3, and level B3 is higher than level B4.

[0147] For example, if the target user's credit rating is A1, then the service level of the target service provided to the target user can be determined to be B1; if the target user's credit rating is A2, then the service level of the target service provided to the target user can be determined to be B2, and so on.

[0148] For example, the service level of the target service can also be divided into two levels, B1 and B2, where level B1 is higher than level B2. Accordingly, if the credit rating of the target user is A1 or A2, the service level of the target service provided to the target user can be determined to be B1; if the credit rating of the target user is A4 or A4, the service level of the target service provided to the target user can be determined to be B2. This specification does not make specific limitations in this regard.

[0149] It should be noted that when the first distributed application contains multiple services, the service level classification strategy for different services can be different, and this specification does not make specific restrictions on this.

[0150] Step S308: Provide the target user with the service content included in the target service that corresponds to the determined service level.

[0151] Furthermore, in one of the illustrated embodiments, after determining the service level of the target user for the target service, the first distributed application can further determine the service content corresponding to the service provided by the target service to the target user based on the determined service level, and provide the service content to the target user.

[0152] For example, taking the first distributed application as a financial application, the target service as an asset prepayment service, and the target service corresponding to the four service levels B1, B2, B3, and B4 mentioned above, the available credit limit in the target service can vary depending on the service level. If the target user's service level is B1, the maximum amount of assets the target user can prepay is 1 million; if the target user's service level is B2, the maximum amount of assets the target user can prepay is 500,000; if the target user's service level is B3, the maximum amount of assets the target user can prepay is 200,000; if the target user's service level is B4, the maximum amount of assets the target user can prepay is 50,000, and so on. This specification does not impose specific limitations on this.

[0153] For example, taking the first distributed application as a recruitment application, the target service as a resume submission service, and the target service corresponding to the two service levels B1 and B2 mentioned above, if the target user's service level is B1, then the target user can submit a maximum of 10 resumes per day; if the target user's service level is B2, then the target user can submit a maximum of 5 resumes per day, and so on. This specification does not make specific limitations in this regard.

[0154] In summary, this application allows multiple distributed applications deployed on the blockchain to calculate user credit characteristics based on their respective user data. Furthermore, these distributed applications can publish the calculated credit characteristics on the blockchain. Further, any distributed application deployed on the blockchain can obtain credit characteristics published by other distributed applications and, considering the differences in services provided by different distributed applications, can convert these credit characteristics into credit characteristics that conform to its own credit assessment strategy. Finally, the distributed application can assess the user's credit rating within that distributed application based on the converted credit characteristics. Thus, this application can leverage the information-sharing capabilities of the blockchain to obtain a large number of credit characteristics published by distributed applications, and, combined with the credit assessment strategy of each distributed application, efficiently and accurately calculate the user's credit rating in each distributed application. This achieves the construction of a distributed identity credit system based on distributed applications, enabling the constraint of user behavior in each distributed application after the user logs in with a distributed identity, effectively ensuring the fairness and security of the distributed applications.

[0155] Corresponding to the above-described method and process, embodiments of this specification also provide a blockchain-based credit assessment device. Please refer to... Figure 4 , Figure 4This is a schematic diagram of a blockchain-based credit assessment device provided in an exemplary embodiment. In one illustrated embodiment, the device 40 can be applied to a first distributed application among multiple distributed applications deployed on the blockchain, or to a centralized service that manages the credit ratings of users in the first distributed application. This service can be deployed on a computer device running the first distributed application or other computer devices that interface with the first distributed application. Figure 4 As shown, the device 40 includes:

[0156] The acquisition unit 401 is used to acquire the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain;

[0157] The credit assessment unit 402 is used to convert the credit features into credit features that conform to the credit assessment strategy of the first distributed application, and to assess the credit rating of the target user in the first distributed application based on the converted credit features.

[0158] In one illustrated embodiment, the device further includes a login management unit 403, for:

[0159] In response to the target user logging into the first distributed application based on the target DID, based on the assessed credit rating of the target user, it is determined whether the target user has access to multiple services included in the first distributed application;

[0160] Provide the target user with at least a portion of the multiple services, of which the target user has access rights.

[0161] In one illustrated embodiment, the apparatus further includes a service management unit 404, configured to:

[0162] In response to the target user's access request for the target service provided by the first distributed application, the service level of the target service for the target user is determined based on the assessed credit rating.

[0163] Based on the service level, determine the service content corresponding to the service provided by the target service to the target user, and provide the service content to the target user.

[0164] In one illustrated embodiment, a system smart contract is deployed on the blockchain for managing credit features published on the blockchain by at least some of the applications; the second distributed application publishes the credit features of the target user on the blockchain by invoking the system smart contract.

[0165] In one illustrated embodiment, the credit feature further includes a credit feature calculated by the first distributed application based on user data generated by the target user in the first distributed application; the user data is user data related to user credit generated in the first distributed application after the target user logs in with the target DID registered on the blockchain.

[0166] In one illustrated embodiment, the first distributed application carries a pre-built first credit model; the device 40 further includes a first feature calculation unit 405, used for:

[0167] The user data generated by the target user in the first distributed application is input into the first credit model to calculate the credit features of the target user.

[0168] In one illustrated embodiment, at least some of the plurality of distributed applications also publish a credit model on the blockchain; the device 40 further includes a second feature calculation unit 406, for:

[0169] Obtain the second credit model published by the third distributed application in at least some of the applications;

[0170] The user data generated by the target user in the first distributed application is input into the second credit model to calculate the credit features of the target user.

[0171] In one illustrated embodiment, the system smart contract is also used to manage the credit model published on the blockchain by at least a portion of the application; the third distributed application publishes the second credit model on the blockchain by invoking the system smart contract.

[0172] In one illustrated embodiment, service contracts, which serve as service backends for the plurality of distributed applications, are also deployed on the blockchain.

[0173] The credit assessment unit 402 is specifically used for:

[0174] The feature conversion logic contained in the service contract corresponding to the first distributed application is invoked to convert the credit feature into a credit feature that conforms to the credit assessment strategy of the first distributed application. After converting the credit feature into a credit feature that conforms to the credit assessment strategy of the first distributed application, the credit assessment logic contained in the service contract corresponding to the first distributed application is further invoked to assess the credit rating of the target user in the first distributed application based on the converted credit feature.

[0175] For details on the implementation process of the functions and roles of each unit in the aforementioned device 40, please refer to the above. Figures 1-3 The description of the corresponding embodiments will not be repeated here. It should be understood that the above-described device 40 can be implemented by software, hardware, or a combination of software and hardware. Taking software implementation as an example, as a logical device, it is formed by the processor (CPU) of the device loading the corresponding computer program instructions into memory and running them. From a hardware perspective, in addition to the CPU and memory, the device typically includes other hardware such as chips for wireless signal transmission and reception, and / or other hardware such as boards for implementing network communication functions.

[0176] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the units or modules can be selected to achieve the purpose of the solution described in this specification, depending on actual needs. Those skilled in the art can understand and implement this without any inventive effort.

[0177] The devices, units, and modules described in the above embodiments can be implemented by computer chips or physical entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, in-vehicle computer, or any combination of these devices.

[0178] Corresponding to the above method embodiments, embodiments of this specification also provide a computer device. Please refer to... Figure 5 , Figure 5 This is a schematic diagram of the structure of a computer device provided in an exemplary embodiment. Figure 5 The computer device shown can be the one described above. Figure 1Any one of computer devices 100a, 100b, and 100c in the system architecture shown. This computer device can deploy a first distributed application among the multiple distributed applications on the aforementioned blockchain; wherein, the blockchain stores credit features published by at least some of the multiple distributed applications. Figure 5 As shown, the computer device includes a processor 1001 and a memory 1002, and may further include an input device 1004 (e.g., a keyboard) and an output device 1005 (e.g., a display). The processor 1001, memory 1002, input device 1004, and output device 1005 can be connected via a bus or other means. Figure 5 As shown, the memory 1002 includes a computer-readable storage medium 1003 storing a computer program executable by the processor 1001. The processor 1001 may be a CPU, a microprocessor, or an integrated circuit for controlling the execution of the above method embodiments. When the processor 1001 runs the stored computer program, it can execute various steps of the credit assessment method in the embodiments of this specification, including: obtaining the credit characteristics of a target user; wherein the credit characteristics include credit characteristics published on the blockchain by a second distributed application in at least a portion of the applications; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data is user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain; converting the credit characteristics into credit characteristics that conform to the credit assessment strategy of the first distributed application, and assessing the credit rating of the target user in the first distributed application based on the converted credit characteristics.

[0179] For a detailed description of each step in the above credit assessment method, please refer to the previous content, which will not be repeated here.

[0180] Corresponding to the above-described method embodiments, embodiments of this specification also provide a computer-readable storage medium storing computer programs that, when run by a processor, execute the various steps of the credit assessment method described in this specification. Please refer to the above for details. Figures 1-3 The description of the corresponding embodiments will not be repeated here.

[0181] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

[0182] In a typical configuration, a terminal device includes one or more CPUs, input / output interfaces, network interfaces, and memory.

[0183] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0184] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data.

[0185] 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transient media, such as modulated data signals and carrier waves.

[0186] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0187] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of computer program products implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

Claims

1. A blockchain-based credit assessment method, wherein multiple distributed applications are deployed on the blockchain; wherein, At least some of the distributed applications have published credit features on the blockchain; a system smart contract for managing the credit features published by the at least some applications on the blockchain is deployed on the blockchain; The blockchain also deploys service contracts that serve as service backends for the multiple distributed applications; the method includes: Obtain the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications through calling the system smart contract; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain; The feature conversion logic contained in the service contract corresponding to the first distributed application is invoked to convert the credit feature into a credit feature that conforms to the credit assessment strategy of the first distributed application. After converting the credit feature into a credit feature that conforms to the credit assessment strategy of the first distributed application, the credit assessment logic contained in the service contract corresponding to the first distributed application is further invoked to assess the credit rating of the target user in the first distributed application based on the converted credit feature.

2. The method according to claim 1, further comprising: In response to the target user logging into the first distributed application based on the target DID, based on the assessed credit rating of the target user, it is determined whether the target user has access to multiple services included in the first distributed application; Provide the target user with at least a portion of the multiple services, of which the target user has access rights.

3. The method according to claim 1, further comprising: In response to the target user's access request for the target service provided by the first distributed application, the service level of the target service for the target user is determined based on the assessed credit rating. Based on the service level, determine the service content corresponding to the service provided by the target service to the target user, and provide the service content to the target user.

4. The method according to claim 1, wherein the credit feature further includes a credit feature calculated by the first distributed application based on user data generated by the target user in the first distributed application; the user data is user data related to user credit generated in the first distributed application after the target user logs in to the first distributed application using the target DID registered on the blockchain.

5. The method according to claim 4, wherein the first distributed application carries a pre-built first credit model; the method further includes: The user data generated by the target user in the first distributed application is input into the first credit model to calculate the credit features of the target user.

6. The method of claim 4, wherein at least some of the plurality of distributed applications also publish a credit model on the blockchain; The method further includes: Obtain the second credit model published by the third distributed application in at least some of the applications; The user data generated by the target user in the first distributed application is input into the second credit model to calculate the credit features of the target user.

7. The method according to claim 6, wherein the system smart contract is further used to manage the credit model published on the blockchain by at least some of the applications; the third distributed application publishes the second credit model on the blockchain by invoking the system smart contract.

8. A login management method for a distributed application, wherein multiple distributed applications are deployed on a blockchain; wherein, At least some of the distributed applications have published credit features on the blockchain; a system smart contract for managing the credit features published by the at least some applications on the blockchain is deployed on the blockchain; The blockchain also deploys service contracts that serve as service backends for the multiple distributed applications; the method includes: Obtain the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications through calling the system smart contract; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain; Based on the credit characteristics, assessing the credit rating of the target user in the first distributed application includes: invoking feature conversion logic contained in the service contract corresponding to the first distributed application to convert the credit characteristics into credit characteristics that conform to the credit assessment strategy of the first distributed application; and after converting the credit characteristics into credit characteristics that conform to the credit assessment strategy of the first distributed application, further invoking the credit assessment logic contained in the service contract corresponding to the first distributed application to assess the credit rating of the target user in the first distributed application based on the converted credit characteristics. In response to the target user logging into the first distributed application based on the target DID, based on the assessed credit rating of the target user, it is determined whether the target user has access to multiple services included in the first distributed application; Provide the target user with at least a portion of the multiple services, of which the target user has access rights.

9. A service management method for distributed applications, wherein multiple distributed applications are deployed on a blockchain; wherein, At least some of the distributed applications have published credit features on the blockchain; a system smart contract for managing the credit features published by the at least some applications on the blockchain is deployed on the blockchain; The blockchain also deploys service contracts that serve as service backends for the multiple distributed applications; the method includes: Obtain the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications through calling the system smart contract; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain; Based on the credit characteristics, assessing the credit rating of the target user in the first distributed application includes: invoking feature conversion logic contained in the service contract corresponding to the first distributed application to convert the credit characteristics into credit characteristics that conform to the credit assessment strategy of the first distributed application; and after converting the credit characteristics into credit characteristics that conform to the credit assessment strategy of the first distributed application, further invoking the credit assessment logic contained in the service contract corresponding to the first distributed application to assess the credit rating of the target user in the first distributed application based on the converted credit characteristics. In response to the target user's access request for the target service provided by the first distributed application, the service level of the target service for the target user is determined based on the assessed credit rating. Based on the service level, determine the service content corresponding to the service provided by the target service to the target user, and provide the service content to the target user.

10. A blockchain-based credit assessment device, wherein multiple distributed applications are deployed on the blockchain; wherein, At least some of the distributed applications have published credit features on the blockchain; a system smart contract for managing the credit features published by the at least some applications on the blockchain is deployed on the blockchain; The blockchain also deploys service contracts that serve as service backends for the multiple distributed applications; the device includes: An acquisition unit is configured to acquire the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications through calling the system smart contract; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain; The credit assessment unit is used to call the feature conversion logic contained in the service contract corresponding to the first distributed application to convert the credit features into credit features that conform to the credit assessment strategy of the first distributed application. After converting the credit features into credit features that conform to the credit assessment strategy of the first distributed application, it further calls the credit assessment logic contained in the service contract corresponding to the first distributed application to assess the credit rating of the target user in the first distributed application based on the converted credit features.

11. A login management device for a distributed application, wherein multiple distributed applications are deployed on a blockchain; wherein, At least some of the distributed applications have published credit features on the blockchain; a system smart contract for managing the credit features published by the at least some applications on the blockchain is deployed on the blockchain; The blockchain also deploys service contracts that serve as service backends for the multiple distributed applications; the device includes: An acquisition unit is configured to acquire the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications through calling the system smart contract; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain; A credit assessment unit is used to assess the credit rating of the target user in the first distributed application based on the credit features. The unit includes: invoking feature conversion logic contained in the service contract corresponding to the first distributed application to convert the credit features into credit features that conform to the credit assessment strategy of the first distributed application; and after converting the credit features into credit features that conform to the credit assessment strategy of the first distributed application, further invoking the credit assessment logic contained in the service contract corresponding to the first distributed application to assess the credit rating of the target user in the first distributed application based on the converted credit features. The login management unit is configured to respond to the target user's authorization to log in to the first distributed application based on the target DID, determine whether the target user has access to multiple services included in the first distributed application based on the assessed credit rating of the target user, and provide the target user with at least a portion of the multiple services for which the target user has access.

12. A service management device for distributed applications, wherein multiple distributed applications are deployed on a blockchain; wherein, At least some of the distributed applications have published credit features on the blockchain; a system smart contract for managing the credit features published by the at least some applications on the blockchain is deployed on the blockchain; The blockchain also deploys service contracts that serve as service backends for the multiple distributed applications; the device includes: An acquisition unit is configured to acquire the credit characteristics of a target user corresponding to a first distributed application among the plurality of distributed applications; wherein, the credit characteristics include credit characteristics published on the blockchain by a second distributed application among at least some of the applications through calling the system smart contract; the credit characteristics are credit characteristics calculated by the second distributed application based on user data generated by the target user in the second distributed application; the user data are user data related to user credit generated in the second distributed application after the target user logs in to the second distributed application using their target distributed digital identity (DID) registered on the blockchain; A credit assessment unit is used to assess the credit rating of the target user in the first distributed application based on the credit features. The unit includes: invoking feature conversion logic contained in the service contract corresponding to the first distributed application to convert the credit features into credit features that conform to the credit assessment strategy of the first distributed application; and after converting the credit features into credit features that conform to the credit assessment strategy of the first distributed application, further invoking the credit assessment logic contained in the service contract corresponding to the first distributed application to assess the credit rating of the target user in the first distributed application based on the converted credit features. The service management unit is configured to respond to the target user's access request for the target service provided by the first distributed application, determine the service level of the target service for the target user based on the assessed credit rating, determine the service content corresponding to the service provided by the target service for the target user based on the service level, and provide the service content to the target user.

13. A computer device, comprising: Memory and processor; The memory stores computer programs that can be executed by the processor; When the processor runs the computer program, it performs the method as described in any one of claims 1 to 7, or the method as described in claim 8, or the method as described in claim 9.

14. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method as claimed in any one of claims 1 to 7, or performs the method as claimed in claim 8, or performs the method as claimed in claim 9.

Images