Mobile terminal access methods, devices, equipment and media for multi-network collaborative credit authorization

By receiving the terminal device's identity identifier and compressed historical certificate chain credentials, and using the local historical roaming database and blockchain network devices for rapid verification, the problem of low identity authentication efficiency when the terminal device roams across domains is solved, achieving efficient identity authentication and secure access.

CN123123903APending Publication Date: 2026-11-17CHINA UNITED NETWORK COMM GRP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611096470.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-22
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

When a terminal device roams across domains, the authentication efficiency of the visited network device is low, mainly due to the excessive time required to transmit historical certificate chains.

Method used

By receiving the terminal device's identity identifier and compressed historical certificate chain credentials, and using the local historical roaming database and blockchain network devices for rapid verification, the trustworthiness of the terminal device is determined, avoiding the transmission of the complete certificate chain.

Benefits of technology

It improves the efficiency of terminal device identity authentication, reduces authentication time, and ensures network security and communication quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123903A_ABST
    Figure CN123123903A_ABST
Patent Text Reader

Abstract

This application provides a method, apparatus, device, and medium for mobile terminal access with multi-network collaborative trust, relating to the field of electronic technology, and is used to improve the efficiency of identity authentication for terminal devices. The specific technical solution is as follows: receiving an access request sent by a terminal device, the access request carrying the terminal device's identity identifier and first credential information, the first credential information including the terminal device's private key credential or historical roaming aggregation credential, the historical roaming aggregation credential being a compressed historical certificate chain of the terminal device, the historical certificate chain including network authorization credentials of the visited networks previously accessed by the terminal device; determining a first judgment result based on the identity identifier and the first credential information, the first judgment result indicating whether the terminal device is a trusted device; and determining whether to establish a connection with the terminal device based on the first judgment result. This application is applied to scenarios requiring identity authentication of terminal devices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of electronic technology, and in particular to a method, apparatus, device and medium for mobile terminal access with multi-network collaborative trust. Background Technology

[0002] With the development of communication technology, cross-domain roaming scenarios where terminal devices roam from their home network to their visited network are becoming increasingly common. In these cross-domain roaming scenarios, efficient authentication of terminal devices is becoming increasingly important.

[0003] In related technologies, when a terminal device needs to roam from its home network to a visited network, the terminal device sends an access request to the visited network device. After receiving the access request, the visited network device sends an authentication request to the home network device. After receiving the authentication request, the home network device transmits the historical certificate chain corresponding to the terminal device to the visited network device, so that the visited network device can authenticate the terminal device based on the historical certificate chain and determine whether to grant access to the terminal device based on the authentication result.

[0004] However, in the above scheme, as the number of roaming trips of the terminal device increases, the size of the required historical certificate chain grows linearly, increasing the time required to transmit the historical certificate chain. This, in turn, significantly prolongs the time required for the visited network device to authenticate the terminal device. Thus, in related technologies, the authentication efficiency of the visited network device for the terminal device is low when the terminal device is roaming across domains. Summary of the Invention

[0005] This application provides a mobile terminal access method, apparatus, device, and medium for multi-network collaborative trust, which improves the efficiency of identity authentication for terminal devices.

[0006] In a first aspect, embodiments of this application provide a mobile terminal access method for multi-network collaborative trust. The method includes: receiving an access request sent by a terminal device, the access request carrying the terminal device's identity identifier and first credential information, the first credential information including the terminal device's private key credential or historical roaming aggregation credential, the historical roaming aggregation credential being a compressed historical certificate chain of the terminal device, the historical certificate chain including network authorization credentials of visited networks previously accessed by the terminal device; determining a first judgment result based on the identity identifier and the first credential information, the first judgment result indicating whether the terminal device is a trusted device; and determining whether to establish a connection with the terminal device based on the first judgment result.

[0007] The technical solution provided in this application brings at least the following beneficial effects: In this solution, after receiving an access request, the first network device can authenticate the terminal device based on the terminal device's identity identifier and first credential information embedded in the access request, without having to send an authentication request to the home network device corresponding to the terminal device. This saves the time for the first network device to send historical certificate chains to the visited network device and improves the efficiency of authenticating the terminal device.

[0008] One possible implementation involves determining the first judgment result based on the aforementioned identity identifier and the aforementioned first credential information, including: retrieving historical roaming records corresponding to the aforementioned identity identifier and the aforementioned first credential information from the historical roaming database; determining, based on the retrieval result, whether the aforementioned terminal device is a recent historical roaming device, wherein the recent historical roaming device is a terminal device that has accessed the network corresponding to the aforementioned first network device within a first time period; if the aforementioned terminal device is a recent historical roaming device, determining that the aforementioned terminal device is a trusted device; or, if the aforementioned terminal device is not a recent historical roaming device, determining whether the aforementioned terminal device is a trusted device through a second network device based on the aforementioned identity identifier and the aforementioned first credential information, wherein the aforementioned second network device is a blockchain network device.

[0009] Another possible implementation is that the first credential information includes a private key credential; the determination of whether the terminal device is a trusted device by the second network device based on the identity identifier and the first credential information includes: sending a first verification request to the second network device, the first verification request carrying the identity identifier; receiving a public key credential sent by the second network device, the public key credential being a credential retrieved by the second network device from a trusted device public key database based on the identity identifier; and determining whether the terminal device is a trusted device based on the public key credential and the private key credential.

[0010] Another possible implementation is that the first credential information includes historical roaming aggregation credentials; the determination of whether the terminal device is a trusted device by the second network device based on the identity identifier and the first credential information includes: sending a second verification request to the second network device, the second verification request carrying the identity identifier; receiving historical roaming verification information sent by the second network device, the historical roaming verification information being retrieved by the second network device from a trusted historical roaming database based on the identity identifier; and determining whether the terminal device is a trusted device based on the historical roaming verification information and the historical roaming aggregation credentials.

[0011] Another possible implementation is that, based on the first judgment result, determining whether to establish a connection with the terminal device includes: establishing a connection with the terminal device if the first judgment result indicates that the terminal device is a trusted device; or refusing to establish a connection with the terminal device if the first judgment result indicates that the terminal device is not a trusted device.

[0012] In another possible implementation, the first credential information further includes a self-trust score, which is used to characterize the trustworthiness of the historical roaming aggregation credential. The determination of whether to establish a connection with the terminal device based on the first judgment result includes: if the first judgment result indicates that the terminal device is a trustworthy device, determining the trust level of the terminal device based on the self-trust score, a first threshold, and a second threshold. This trust level includes any one of the following: a first trust level, a second trust level, and a third trust level, wherein the first trust level is higher than the second trust level, and the second trust level is higher than the third trust level; and establishing a connection with the terminal device based on its trust level.

[0013] Another possible implementation, based on the trust level of the terminal device, establishes a connection with the terminal device, including: establishing an unrestricted connection with the terminal device when the trust level is the first trust level; establishing a restricted connection with the terminal device when the trust level is the second trust level, wherein the restricted connection represents a connection that limits the network rate; and sending an authentication request to a third network device of the terminal device when the trust level is the third trust level, and establishing a restricted connection with the terminal device upon receiving authentication success information from the third network device, wherein the third network device is the home network device of the terminal device.

[0014] Another possible implementation is that, after establishing a restricted connection with the terminal device when the trust level is the second trust level, the method further includes: sending an authentication request to the third network device; and, upon receiving authentication success information from the third network device, switching the connection with the terminal device to an unrestricted connection.

[0015] Secondly, embodiments of this application provide a mobile terminal access device for multi-network collaborative trust, comprising: a receiving module and a determining module; the receiving module is configured to receive an access request sent by a terminal device, the access request carrying the identity identifier of the terminal device and first credential information, the first credential information including the private key credential or historical roaming aggregation credential of the terminal device, the historical roaming aggregation credential being a compressed historical certificate chain of the terminal device, the historical certificate chain including network authorization credentials of the visited networks previously accessed by the terminal device; the determining module is configured to determine a first judgment result based on the identity identifier and the first credential information, the first judgment result indicating whether the terminal device is a trusted device; and, based on the first judgment result, determine whether to establish a connection with the terminal device.

[0016] One possible implementation is that the aforementioned determining module is specifically used to: retrieve historical roaming records corresponding to the aforementioned identity identifier and the aforementioned first credential information from the historical roaming database; based on the retrieval results, determine whether the aforementioned terminal device is a recent historical roaming device, wherein the aforementioned recent historical roaming device is a terminal device that has accessed the network corresponding to the first network device within a first time period; if the aforementioned terminal device is a recent historical roaming device, determine that the aforementioned terminal device is a trusted device; or, if the aforementioned terminal device is not a recent historical roaming device, determine whether the aforementioned terminal device is a trusted device through a second network device based on the aforementioned identity identifier and the aforementioned first credential information, wherein the aforementioned second network device is a blockchain network device.

[0017] In another possible implementation, the first credential information includes a private key credential; the determining module is specifically configured to: send a first verification request to the second network device, the first verification request carrying the identity identifier; receive a public key credential sent by the second network device, the public key credential being a credential retrieved by the second network device from a trusted device public key database based on the identity identifier; and determine whether the terminal device is a trusted device based on the public key credential and the private key credential.

[0018] In another possible implementation, the first credential information includes historical roaming aggregation credentials; the determining module is specifically configured to: send a second verification request to the second network device, the second verification request carrying the identity identifier; receive historical roaming verification information sent by the second network device, the historical roaming verification information being retrieved by the second network device from a trusted historical roaming database based on the identity identifier; and determine whether the terminal device is a trusted device based on the historical roaming verification information and the historical roaming aggregation credentials.

[0019] Another possible implementation is that the aforementioned determining module is specifically used to: establish a connection with the terminal device when the first judgment result indicates that the terminal device is a trusted device; or, refuse to establish a connection with the terminal device when the first judgment result indicates that the terminal device is not a trusted device.

[0020] In another possible implementation, the first credential information mentioned above also includes a self-credibility score, which is used to characterize the credibility of the historical roaming aggregation credential. The determining module is specifically used to: determine the credibility level of the terminal device based on the self-credibility score, a first threshold, and a second threshold when the first judgment result indicates that the terminal device is a trustworthy device. The credibility level includes any one of the following: a first credibility level, a second credibility level, and a third credibility level, wherein the first credibility level is higher than the second credibility level, and the second credibility level is higher than the third credibility level; and establish a connection with the terminal device based on the credibility level of the terminal device.

[0021] Another possible implementation is that the aforementioned determining module is specifically used to: establish an unrestricted connection with the terminal device when the aforementioned trust level is the first trust level; establish a restricted connection with the terminal device when the aforementioned trust level is the second trust level, wherein the restricted connection represents a connection that limits the network rate; and send an authentication request to a third network device of the terminal device when the aforementioned trust level is the third trust level, and upon receiving authentication success information sent by the third network device, establish a restricted connection with the terminal device, wherein the third network device is the home network device of the terminal device.

[0022] In another possible implementation, the above apparatus further includes: a sending module and a switching module; the sending module is used to send an authentication request to the third network device after the determining module establishes a restricted connection with the terminal device when the trust level is the second trust level; the switching module is used to switch the connection with the terminal device to an unrestricted connection upon receiving the authentication success information sent by the third network device.

[0023] Thirdly, this application provides an electronic device comprising: a processor and a memory; the memory stores a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the method of the first aspect described above.

[0024] Fourthly, this application provides a readable storage medium on which a program or instructions are stored, which, when executed by a computer, implement the method of the first aspect described above.

[0025] Fifthly, this application provides a computer program product stored in a storage medium, which, when executed by a computer, implements the method described in the first aspect.

[0026] In a sixth aspect, embodiments of this application provide a chip including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect.

[0027] The beneficial effects of the second to sixth aspects mentioned above are described in the corresponding description of the first aspect and will not be repeated here. Attached Figure Description

[0028] Figure 1 A schematic diagram of the network architecture for a mobile terminal access method with multi-network collaborative trust provided in an embodiment of this application;

[0029] Figure 2 A flowchart illustrating a mobile terminal access method for multi-network collaborative trust provided in an embodiment of this application;

[0030] Figure 3 A flowchart illustrating another mobile terminal access method for multi-network collaborative trust provided in this application embodiment;

[0031] Figure 4 A flowchart illustrating another mobile terminal access method for multi-network collaborative trust provided in this application embodiment;

[0032] Figure 5 A schematic diagram of the structure of a mobile terminal access device for multi-network collaborative trust provided in an embodiment of this application;

[0033] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0034] The following will describe in detail, with reference to the accompanying drawings, the mobile terminal access method, apparatus, device and medium for multi-network collaborative credit provided in this application.

[0035] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0036] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0037] The terms "at least one," "at least one of," etc., used in the specification and claims of this application refer to any one, any two, or a combination of two or more of the included items. For example, at least one of a, b, and c can mean: "a," "b," "c," "a and b," "a and c," "b and c," and "a, b, and c," where a, b, and c can be single or multiple. Similarly, "at least two" refers to two or more items, and its meaning is similar to that of "at least one."

[0038] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0039] The embodiments of this application provide a mobile terminal access method, apparatus, device, and medium for multi-network collaborative trust, which can be applied to scenarios requiring identity verification of terminal devices.

[0040] Roaming and handover in mobile communication networks are fundamental functions to ensure service continuity for users across different operator coverage areas. With the development of 5G and future network technologies, heterogeneous network convergence and edge computing architectures are becoming increasingly prevalent, requiring user terminals (UEs) to frequently access different home network (HPLMN) and visited network (VPLMN). In this process, identity authentication and trust negotiation are core mechanisms to ensure secure access. Currently, the industry primarily uses 3GPP-based authentication systems and blockchain-based distributed authentication schemes for roaming management.

[0041] In related technologies, a trusted channel is established between the home network and the visited network through a secure edge protection proxy. When a terminal roams to the visited network, the visited network sends an authentication request to the home network. The unified data management network element and authentication server function element of the home network generate an authentication vector and send it back to the visited network, where the security anchor function element executes the specific authentication process. This mechanism relies on roaming protocols between operators and real-time signaling interaction in the core network to verify the legitimacy of the terminal's identity.

[0042] However, the aforementioned schemes typically require the terminal to transmit a complete chain of historical certificates or a list of signatures when verifying a user's historical credit history. As the number of times a user roams between different operator networks increases, the size of the data packets required for transmission grows linearly, consuming limited 5G air interface spectrum resources and significantly increasing the transmission latency of authentication data. Therefore, in these related technologies, the authentication of terminal devices by the visited network equipment is inefficient.

[0043] To address the aforementioned technical problems, this application provides a mobile terminal access method, apparatus, device, and medium for multi-network collaborative trust. The method involves receiving an access request from a terminal device, the access request carrying the terminal device's identity identifier and first credential information. The first credential information includes the terminal device's private key credential or historical roaming aggregation credential, which is a compressed historical certificate chain of the terminal device. The historical certificate chain includes network authorization credentials of visited networks previously accessed by the terminal device. Based on the identity identifier and the first credential information, a first judgment result is determined, indicating whether the terminal device is a trusted device. Based on the first judgment result, it is determined whether to establish a connection with the terminal device. This application is applied to scenarios requiring terminal device authentication. In this solution, after receiving an access request, the first network device can authenticate the terminal device based on the terminal device's identity identifier and first credential information embedded in the access request, without needing to send an authentication request to the terminal device's home network device. This saves the time the first network device spends sending historical certificate chains to visited network devices, improving the efficiency of terminal device authentication.

[0044] The following description, in conjunction with the accompanying drawings, details the mobile terminal access method, apparatus, device, and medium for multi-network collaborative trust provided in the embodiments of this application.

[0045] Figure 1 This illustration shows the network architecture of a mobile terminal access method using multi-network collaborative trust provided in an embodiment of this application. For example... Figure 1As shown, the network architecture includes a mobile terminal access device 101 with multi-network collaborative trust and a terminal device 102. The mobile terminal access device 101 and the terminal device 102 are interconnected.

[0046] In some embodiments, the mobile terminal access device 101 for multi-network collaborative authorization can be a server, a computer, or a processor or processing unit within a server or computer. The server can be a single server or a server cluster consisting of multiple servers. It should be noted that the embodiments of this application do not limit the specific device form of the mobile terminal access device 101 for multi-network collaborative authorization. Figure 1 The mobile terminal access device 101, which provides multi-network collaborative credit authorization, is illustrated using a single server as an example.

[0047] In some embodiments, the terminal device may be a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, personal computer (PC), ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc., and the embodiments of this application do not specifically limit it. Figure 1 The example shown is a mobile phone, with terminal device 102 as an example.

[0048] It should be noted that the network architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As network architectures evolve, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0049] See Figure 2 This is a flowchart illustrating a mobile terminal access method for multi-network collaborative trust provided in an embodiment of this application. Figure 2 As shown, the mobile terminal access method for multi-network collaborative trust provided in this application embodiment can be implemented through a first network device, specifically including the following steps 201 to 203.

[0050] Step 201: The first network device receives the access request sent by the terminal device.

[0051] In some embodiments, the first network device described above may be a visited network device.

[0052] In some embodiments, the access request carries the identity identifier of the terminal device and first credential information. The first credential information includes the private key credential or historical roaming aggregation credential of the terminal device. The historical roaming aggregation credential is a compressed historical certificate chain of the terminal device, which includes network authorization credentials of the visited networks that the terminal device has historically accessed.

[0053] In some embodiments, the aforementioned identity identifier may be a decentralized identifier (DID).

[0054] In some embodiments, the terminal device described above has a built-in security module that securely stores the DID generated by the manufacturer.

[0055] Step 202: The first network device determines the first judgment result based on the aforementioned identity identifier and the aforementioned first credential information.

[0056] In some embodiments, the first determination result indicates whether the terminal device is a trusted device.

[0057] In some embodiments, the first network device may determine whether the terminal device is a trusted device based on the aforementioned identity identifier and the aforementioned first credential information.

[0058] It should be noted that the specific implementation process of the first network device determining whether the terminal device is a trusted device based on the aforementioned identity identifier and the aforementioned first credential information can be found in the relevant description in the following embodiments. To avoid repetition, this application will not elaborate on it here.

[0059] In some embodiments, combined with Figure 2 ,like Figure 3 As shown, step 202 can be implemented through steps 202a, 202b, and 202c. Alternatively, step 202 can be implemented through steps 202a, 202b, and 202d.

[0060] Step 202a: The first network device retrieves historical roaming records corresponding to the aforementioned identity identifier and the aforementioned first credential information from the historical roaming database.

[0061] In some embodiments, the aforementioned historical roaming database refers to a local database used to store access records of recently accessed terminal devices.

[0062] Step 202b: Based on the search results, the first network device determines whether the aforementioned terminal device is a recent historical roaming device.

[0063] In some embodiments, the search result refers to whether the first electronic device retrieves historical roaming records corresponding to the identity identifier and the first credential information from the historical roaming database.

[0064] In some embodiments, the search results include any one of the following: a result that a historical roaming record corresponding to the above-mentioned identity identifier and the above-mentioned first credential information was successfully retrieved, or a result that a historical roaming record corresponding to the above-mentioned identity identifier and the above-mentioned first credential information was not retrieved.

[0065] In some embodiments, the aforementioned recent historical roaming device is a terminal device that has accessed the network corresponding to the aforementioned first network device within a first time period.

[0066] In some embodiments, the first time period can be a fixed value, such as 7 days. Of course, the first time period can also be other values ​​preset by the system, which can be determined according to actual needs, and this application does not limit it.

[0067] In some embodiments, the first electronic device may determine that the terminal device is a recent historical roaming device if the search result is that a historical roaming record corresponding to the identity identifier and the first credential information has been successfully retrieved; or, the first electronic device may determine that the terminal device is not a recent historical roaming device if the search result is that a historical roaming record corresponding to the identity identifier and the first credential information has not been retrieved.

[0068] Step 202c: If the terminal device is a recently roaming device, the first network device determines that the terminal device is a trusted device.

[0069] In some embodiments, the aforementioned trusted device refers to a secure device that can be trusted.

[0070] It is understandable that if the aforementioned terminal device is a recently roaming device, it means that the aforementioned terminal device has recently passed the security test of the first network device and successfully accessed the network corresponding to the first network device. At this time, the first network device can consider the aforementioned terminal device as a trustworthy and secure device.

[0071] Step 202d: If the terminal device is not a recently roaming device, the first network device determines whether the terminal device is a trusted device based on the identity identifier and the first credential information through the second network device.

[0072] In some embodiments, the second network device described above is a blockchain network device.

[0073] In some embodiments, the aforementioned blockchain network device refers to a consortium blockchain node cluster jointly maintained by multiple operators.

[0074] In some embodiments, the aforementioned blockchain network device is deployed with a decentralized identity smart contract, which only needs to synchronize the block header and Merkel root data, and can complete the legality verification of terminal identity and historical roaming aggregation certificate through Merkel existence proof.

[0075] It is understandable that if the aforementioned terminal device is not a recently roaming device, it means that the aforementioned terminal device has not recently accessed the network corresponding to the first network device and is an unfamiliar terminal device. In this case, the first network device needs to perform a security check on the aforementioned terminal device.

[0076] In some embodiments, the first credential information mentioned above includes a private key credential. Step 202d can be specifically implemented through steps 202d1 to 202d3.

[0077] Step 202d1: If the terminal device is not a recently roaming device, the first network device sends a first verification request to the second network device.

[0078] In some embodiments, the first verification request carries the aforementioned identity identifier.

[0079] In some embodiments, the second network device may be the home network device corresponding to the terminal device.

[0080] Step 202d2: The first network device receives the public key certificate sent by the second network device.

[0081] In some embodiments, the public key credential is a credential retrieved by the second network device from a trusted device public key database based on the identity identifier.

[0082] In some embodiments, the aforementioned trusted device public key database refers to a distributed identity registry deployed on a blockchain consortium blockchain.

[0083] In some embodiments, the aforementioned distributed identity registry is jointly maintained by multiple operators and confirmed by consensus. It stores the DID and corresponding public key information written by the manufacturer when the terminal is manufactured or activated for the first time. The data is immutable and authorized query services are provided only through smart contracts. It is the trusted foundation for verifying the legitimacy of the terminal identity.

[0084] Step 202d3: The first network device determines whether the terminal device is a trusted device based on the aforementioned public key certificate and the aforementioned private key certificate.

[0085] In some embodiments, the first network device may determine whether the terminal device is a trusted device based on whether the public key certificate and the private key certificate match.

[0086] Specifically, the first network device can determine that the terminal device is a trusted device if the public key certificate and the private key certificate match. Alternatively, the first network device can determine that the terminal device is not a trusted device if the public key certificate and the private key certificate do not match.

[0087] In this way, the first network device can directly verify the security of the terminal device based on the private key carried in the access request sent by the terminal device, avoiding the problem of long authentication time for the terminal device due to the long time required to transmit the historical certificate chain, thus improving the efficiency of terminal device authentication.

[0088] In some embodiments, the first credential information mentioned above includes historical roaming aggregation credentials. Step 202d can be specifically implemented through steps 202d4 to 202d6.

[0089] Step 202d4: The first network device sends a second authentication request to the second network device.

[0090] In some embodiments, the second verification request carries the aforementioned identity identifier.

[0091] In some embodiments, the aforementioned historical roaming aggregation certificate refers to a fixed-size aggregation signature certificate generated by a terminal device by compressing the trust endorsement signatures obtained by the device in multiple historical visited networks over time, based on the linear homomorphic properties of Schnorr aggregation signatures.

[0092] Step 202d5: The first network device receives the historical roaming verification information sent by the second network device.

[0093] In some embodiments, the aforementioned historical roaming verification information is retrieved by the second network device from a trusted historical roaming database based on the aforementioned identity identifier.

[0094] In some embodiments, the aforementioned trusted historical roaming database refers to a distributed trust-endorsed ledger deployed on a multi-carrier consortium blockchain.

[0095] Step 202d6: The first network device determines whether the terminal device is a trusted device based on the aforementioned historical roaming verification information and the aforementioned historical roaming aggregation certificate.

[0096] In some embodiments, the first network device may determine whether the terminal device is a trusted device based on whether the historical roaming verification information and the historical roaming aggregation certificate match.

[0097] Specifically, the first network device can determine that the terminal device is a trusted device if the historical roaming verification information and the historical roaming aggregation certificate match. Alternatively, the first network device can determine that the terminal device is not a trusted device if the historical roaming verification information and the historical roaming aggregation certificate do not match.

[0098] In some embodiments, the first credential information further includes a self-credibility score, which characterizes the credibility of the historical roaming aggregation credential. Step 202d6 can be specifically implemented through steps 302a and 302b.

[0099] Step 302a: When the first judgment result indicates that the terminal device is a trusted device, the first network device determines the trust level of the terminal device based on its own trust score, the first threshold and the second threshold.

[0100] In some embodiments, the trust level includes any one of the following: a first trust level, a second trust level, and a third trust level, wherein the first trust level is higher than the second trust level, and the second trust level is higher than the third trust level.

[0101] In some embodiments, the first threshold can be a fixed value, such as 60 points. Of course, the first threshold can also be other values ​​preset by the system, which can be determined according to actual needs, and this application does not limit this.

[0102] In some embodiments, the second threshold can be a fixed value, such as 80 points. Of course, the second threshold can also be other values ​​preset by the system, which can be determined according to actual needs, and this application does not limit this.

[0103] Step 302b: The first network device establishes a connection with the terminal device based on the trust level of the terminal device.

[0104] In some embodiments, the first network device may select a specific connection method and establish a connection with the terminal device based on the trust level of the terminal device.

[0105] It should be noted that the specific implementation process of the first network device selecting a specific connection method and establishing a connection with the aforementioned terminal device based on the trust level of the terminal device can be found in the relevant descriptions in the following embodiments. To avoid repetition, this application will not elaborate further here.

[0106] In some embodiments, step 302b can be implemented by steps 302b1, 302b2, or 302b3.

[0107] Step 302b1: When the trust level is the first trust level, the first network device establishes an unrestricted connection with the terminal device.

[0108] In some embodiments, the above-mentioned unrestricted connection characterizes the allocation of full bandwidth resources, full QoS guarantee rights, and full-featured network access rights to the above-mentioned terminal device.

[0109] Step 302b2: When the trust level is the second trust level, the first network device establishes a restricted connection with the terminal device.

[0110] In some embodiments, the aforementioned restricted connection represents a connection that limits the network rate.

[0111] In some embodiments, the aforementioned restricted connection may also represent a connection that restricts network access permissions.

[0112] Step 302b3: When the trust level is the third trust level, the first network device sends an authentication request to the third network device of the terminal device, and upon receiving the authentication success information sent by the third network device, establishes a restricted connection with the terminal device.

[0113] In some embodiments, the third network device is the home network device of the terminal device.

[0114] In some embodiments, the aforementioned home network equipment refers to the core network authentication and authorization node cluster of the operator to which the terminal equipment is contracted.

[0115] In some embodiments, the authentication information includes the DID of the terminal device and the real-time access behavior characteristics of the terminal device.

[0116] In some embodiments, the access behavior features described above characterize the multi-dimensional contextual information collected by the first network device during the access process of the terminal device.

[0117] In this way, the first network device can match corresponding connection policies for terminal devices with different trust levels, directly granting unrestricted permissions to high-trust level terminals, and setting access restrictions or triggering home location secondary verification for medium and low-trust level terminals. This satisfies the fast access needs of high-trust terminals while reducing the security risks brought by low-trust terminals, achieving a balance between security and efficiency.

[0118] In this way, based on the premise that the terminal device is a trusted device, different trust levels are assigned to the terminal device, allowing the first network device to execute different access policies for terminal devices with different trust levels, thus ensuring network security while also ensuring network communication quality.

[0119] In this way, the first network terminal device can retrieve the corresponding historical roaming verification information through the blockchain network, and combine it with the historical roaming aggregation certificate carried in the access request sent by the terminal device to verify the security of the terminal device. This avoids the problem of long authentication time for the terminal device caused by the long time required to transmit the historical certificate chain, and improves the efficiency of the terminal device authentication.

[0120] In this way, by setting up a historical roaming database, the first network device can detect whether the terminal device is a trusted device that has recently been accessed based on the historical roaming database, without having to check the security of the terminal device based on the blockchain device every time. This shortens the authentication time of the terminal device and improves the efficiency of identity authentication of the terminal device.

[0121] Step 203: Based on the first judgment result, the first network device determines whether to establish a connection with the terminal device.

[0122] In some embodiments, the first network device may establish a connection with the terminal device or refuse to establish a connection with the terminal device based on the first determination result.

[0123] In some embodiments, combined with Figure 2 ,like Figure 4 As shown, step 203 above can be implemented through step 203a or step 203b.

[0124] Step 203a: If the first judgment result indicates that the terminal device is a trusted device, the first network device establishes a connection with the terminal device.

[0125] In some embodiments, if the terminal device is a trusted device, the first network device may respond to the access request by sending access consent information to the terminal device, thereby establishing a connection with the terminal device.

[0126] Step 203b: If the first judgment result indicates that the terminal device is not a trusted device, the first network device refuses to establish a connection with the terminal device.

[0127] In some embodiments, if the terminal device is not a trusted device, the first network device may respond to the access request by sending an access denial message to the terminal device, thereby refusing to establish a connection with the terminal device.

[0128] In this way, the first terminal device can determine whether to establish a connection with the terminal device based on whether the terminal device is a trustworthy device, thereby improving the security of terminal roaming.

[0129] In the mobile terminal access method for multi-network collaborative trust provided in this application, after receiving an access request, the first network device can authenticate the terminal device based on the terminal device's identity identifier and first credential information embedded in the access request, without having to send an authentication request to the home network device corresponding to the terminal device. This saves the time for the first network device to send historical certificate chains to the visited network device and improves the efficiency of authenticating the terminal device.

[0130] The following specific embodiments illustrate the mobile terminal access method for multi-network collaborative trust in this application.

[0131] The implementation process of the mobile terminal access method with multi-network collaborative trust provided in this application embodiment includes the following S1 to S8:

[0132] S1. The terminal device generates and sends an access request containing an identity identifier and first credential information.

[0133] S2. After receiving the access request, the first network device first searches the local historical roaming database to determine whether the terminal is a recently accessed historical roaming device within the first time period.

[0134] If the device is determined to be a recent historical roaming device, the terminal is directly identified as a trusted device and the process proceeds to step S7; if the device is not determined to be a recent historical roaming device, the process proceeds to step S3.

[0135] S3. The first network device calls the second network device to verify the aforementioned terminal device based on the identity identifier and the first credential information.

[0136] S4. If the first credential information is a private key credential, the first network device sends a first verification request carrying an identity identifier to the blockchain. The blockchain retrieves the corresponding public key credential from the trusted device public key database and returns it. The first network device uses the public key to verify the validity of the terminal's private key signature and zero-knowledge identity proof. If the verification is successful, the terminal is determined to be a trusted device.

[0137] S5. If the first credential information is a historical roaming aggregate credential, the first network device sends a second verification request carrying an identity identifier to the blockchain. The blockchain generates a Merkel existence proof and historical roaming verification information and returns it. The first network device verifies the on-chain existence of the aggregate credential and the validity of the zero-knowledge score proof. If the verification is successful, the terminal is determined to be a trusted device.

[0138] S6. If the verification in step S4 or step S5 fails, the first network device determines that the terminal is an untrusted device and refuses to establish a connection.

[0139] S7. If the terminal is a trusted device, the first network device determines the trust level of the terminal device.

[0140] S8. The first network device executes a differentiated connection policy based on the trust level of the terminal device.

[0141] It should be noted that the descriptions of each step S1 to S8 in this embodiment can be found in the descriptions in the above embodiments, and will not be repeated here.

[0142] The mobile terminal access method with multi-network collaborative trust proposed in this application can include two scenarios: scenario A, where a historically unauthenticated terminal device roams and accesses the roaming network, and scenario B, where a historically authenticated terminal device roams and accesses the roaming network. The following detailed embodiments illustrate the mobile terminal access method with multi-network collaborative trust proposed in this application.

[0143] Scenario A: A scenario where a previously unauthenticated terminal device is roaming.

[0144] Step 1: Initiate authentication and submit digital signature

[0145] The terminal (UE) sends an access request to the base station of the serving network C. Since there is no historical backing, the terminal needs to prove that it is the legitimate holder of the on-chain registered identity. The terminal uses its local private key sk to generate a zero-knowledge proof (ZKP) credential proving "I possess the private key corresponding to the on-chain DID," and simultaneously digitally signs the request message (including a timestamp and a random number).

[0146] Data content: { DID, Timestamp, Nonce, Sig_sk(Request), ZKP_Proof_Identity}.

[0147] Step 2: Query local cache

[0148] Upon receiving the request, the H-Agent of the service network C first queries the terminal's identity information in its local light node cache. Since this is the first roaming visit and there is no historical record, the local cache is not found (Hit: No).

[0149] Step 3: Query on-chain identity

[0150] H-Agent initiates a query request to the blockchain network to retrieve the public key and whether there is a basic credit record based on the DID provided by the terminal.

[0151] Step 4: Query the terminal DID and public key

[0152] The smart contract on the blockchain executes query logic to retrieve the public key pk corresponding to the DID in the ledger.

[0153] If the DID does not exist on the blockchain (i.e., the query fails), the smart contract will report an unregistered status. At this time, H-Agent can choose to initiate a verification request to the terminal manufacturer's server (as a fallback mechanism). If it is confirmed that the device is legitimate but not on the blockchain, the on-chain process will be completed; if the manufacturer confirms that it is illegitimate, the request will be rejected directly.

[0154] Step 5: Return DID and public key

[0155] The smart contract returns the retrieved terminal DID and public key pk to the H-Agent of the service network C.

[0156] Step 6: Verify digital signature and ZKP credentials

[0157] After the Agent obtains the public key PK, it performs two-factor authentication:

[0158] ZKP verification: Run the zero-knowledge proof verification function to confirm that the terminal does indeed possess the private key that matches the DID and has not leaked the private key itself.

[0159] Signature verification: Verifies the validity of the digital signature Sig_sk to ensure that the message content (timestamp, random number) has not been tampered with during transmission.

[0160] Step 7: Authentication successful

[0161] If both the ZKP credential and digital signature are verified, H-Agent confirms the terminal's legitimate identity and that it is a manufacturer-registered device. Since the terminal lacks historical endorsement, H-Agent initializes the M-TAD algorithm to "baseline mode," using a common template of normal user behavior as the comparison benchmark, and sets the initial trust score to the default value (60 points). H-Agent then sends an authentication success command to the base station.

[0162] Step 8: Establish connection

[0163] The service network C formally establishes a wireless link connection with the terminal, allocates network resources, and allows the terminal to conduct data communication. H-Agent begins to collect the terminal's physical, signaling, and traffic data in real time. The M-TAD algorithm calculates the reconstruction error of the input sequence in real time. If the terminal's behavior deviates too much from the general benchmark (such as initiating a large-volume scan immediately after access), the real-time score St drops sharply, triggering a connection interruption.

[0164] Step 9: Authentication and Endorsement on the Blockchain

[0165] After the communication session ends, H-Agent outputs the final behavioral score Sfinal for this session. H-Agent signs the evaluation result and packages this endorsement onto the blockchain, thus giving the terminal its first historical record.

[0166] Scenario B: A scenario where roaming access is performed by terminal devices with historical authentication.

[0167] Step 1: Initiate authentication and submit digital signature (including aggregated endorsement)

[0168] The UE initiates a roaming request to the serving network B. The UE's security module (such as in an eSIM or TEE environment) stores historical aggregated endorsement credentials σagg. When initiating roaming, the UE calls its local lightweight cryptography library to generate a Claimed_Score and a zero-knowledge proof credential based on the current σagg and publicly available operator weight parameters.

[0169] Note: Since σagg has a space complexity of O(1) (fixed size) and the ZKP algorithm is optimized for mobile devices, this process will not cause significant power consumption or processing latency. For ultra-low power IoT terminals, pre-generated credentials can also be used to reduce the real-time computing pressure.

[0170] Data content: { DID, Timestamp, Nonce, Sig_sk(Request), σ_agg, Claimed_Score, ZKP_Proof_Score}.

[0171] Step 2: Query local cache

[0172] After receiving the request, the H-Agent of the service network B first searches its local cache database based on the terminal DID to determine whether a match is found.

[0173] If the H-Agent detects that the terminal has recently accessed the network and that the locally stored identity credentials are still valid, it is determined to be a "trusted familiar customer". At this point, the system believes that there is no need to verify its historical endorsement with the blockchain again and directly jumps to step 7 (authentication successful).

[0174] If no match is found: If the H-Agent cannot find the terminal record locally, or the record has expired, it means that the terminal is a "new customer" or "long-inactive customer" for the current base station. In this case, the system cannot determine its legitimacy based solely on local information and needs to execute step 3 to initiate a verification with the blockchain.

[0175] Step 3: Query on-chain endorsements

[0176] H-Agent requests blockchain nodes to provide Merkle Proof of the existence of the aggregate endorsement.

[0177] Step 4: Check endorsement signature

[0178] The smart contract retrieves the aggregated endorsement record associated with the DID from the on-chain ledger, checks whether the public key set {Op1, Op2, ..., Opn} corresponding to the aggregated signature consists of legitimate operators, and confirms that the signature status has not been revoked.

[0179] Step 5: Return the signature status

[0180] The smart contract returns the queried latest aggregated signature status, Merkle proof and relevant parameters to the H-Agent.

[0181] Step 6: Verify the endorsement signature and ZKP credential

[0182] After receiving the on-chain data, the H-Agent performs verification on the edge side as a light node.

[0183] Merkle existence verification: Verify that the aggregated endorsement root hash claimed by the terminal indeed exists in the historical state tree of the blockchain.

[0184] ZKP score verification: The H-Agent runs the zero-knowledge verification function Verify(Proof, Claimed_Score, Public_Params) to confirm that the Claimed_Score submitted by the terminal is authentic and credible.

[0185] Step 7: Multi-dimensional access decision

[0186] Path A (hit from Step 2): Direct authentication succeeds based on locally cached trust, and the H-Agent issues an access instruction to the base station.

[0187] Path B (passed verification from Step 6): The H-Agent executes differentiated access control and algorithm configuration strategies based on the verified Claimed Score in combination with the preset trust thresholds (Th_high, Th_low):

[0188] High reputation range (Score≥Th_high): The authentication is determined to be passed. The H-Agent immediately generates a session key for the terminal and allows the establishment of a full-bandwidth connection. The anomaly sensitivity coefficient α of the M-TAD engine is lowered to prioritize ensuring the user's seamless roaming experience.

[0189] Medium reputation range (Th_low≤Score<Th_high): The H-Agent establishes a restricted connection and performs traffic monitoring. The anomaly sensitivity coefficient α of the M-TAD engine is increased, and a fuse is triggered immediately once an anomaly is detected. While allowing access, the H-Agent asynchronously initiates a proxy authentication request in the background to query the latest status from the home network of the terminal.

[0190] If the home location returns confirmation: Maintain the connection and upgrade to full bandwidth if necessary.

[0191] If the home network returns a rejection (or times out): immediately force disconnection and record the event on the blockchain.

[0192] Low reputation range (Score < Th_low): Access requests are temporarily suspended, and no wireless connection is established. H-Agent acts as a proxy, simultaneously initiating a home location authentication request.

[0193] If the home location returns confirmation: Access is allowed, but the anomaly sensitivity coefficient α of the M-TAD engine is increased, and the object is marked as a high-risk object.

[0194] If the home location returns a rejection: directly refuse access and generate a rejection receipt on the blockchain.

[0195] Step 8: Establish connection

[0196] The service network B establishes a high-speed 5G connection with the terminal, allocates an IP address and QoS resources, and the user begins normal communication. H-Agent runs the M-TAD algorithm, at which point the model focuses on whether "the current behavior matches its historical persona".

[0197] If the behavior remains excellent (high multimodal consistency), the real-time score St steadily increases, which can dynamically improve QoS bandwidth.

[0198] If an anomaly is detected (such as the physical layer showing a static state, but the traffic characteristics showing typical mobile P2P download behavior), it is considered a "modal conflict anomaly" and a score will be deducted.

[0199] Step 9: Add Trust Endorsement and Rating

[0200] After the communication session ends, H-Agent outputs the final behavioral score Sfinal for this session. H-Agent signs the evaluation result and packages this new endorsement onto the blockchain. Simultaneously, the terminal uses homomorphic encryption locally to aggregate it with the original σagg, realizing the dynamic evolution of trust.

[0201] It should be noted that the above-described method embodiments, or the various possible implementations of the method embodiments, can be executed individually, or, provided there is no conflict, they can be combined with each other. The specific implementation can be determined according to actual usage requirements, and this application embodiment does not impose any restrictions on this.

[0202] As can be seen, the above mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the embodiments of this application provide corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0203] This application embodiment can divide the mobile terminal access device for multi-network collaborative trust into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0204] In some embodiments, this application also provides a mobile terminal access device for multi-network collaborative trust. This mobile terminal access device for multi-network collaborative trust may include one or more functional modules for implementing the mobile terminal access method for multi-network collaborative trust described in the above method embodiments.

[0205] For example, Figure 5 This is a schematic diagram of the structure of a mobile terminal access device for multi-network collaborative trust provided in an embodiment of this application. Figure 5 As shown, the mobile terminal access device 900 with multi-network collaborative credit authorization includes: a receiving module 901 and a determining module 902.

[0206] The receiving module 901 is configured to receive an access request sent by a terminal device. The access request carries the terminal device's identity identifier and first credential information. The first credential information includes the terminal device's private key credential or historical roaming aggregation credential. The historical roaming aggregation credential is a compressed historical certificate chain of the terminal device, which includes network authorization credentials of the visited networks previously accessed by the terminal device. The determining module 902 is configured to determine a first judgment result based on the identity identifier and the first credential information. The first judgment result indicates whether the terminal device is a trusted device. Based on the first judgment result, the module determines whether to establish a connection with the terminal device.

[0207] In the mobile terminal access device with multi-network collaborative trust provided in this application, after receiving an access request, the first network device can authenticate the terminal device based on the terminal device's identity identifier and first credential information embedded in the access request, without having to send an authentication request to the home network device corresponding to the terminal device. This saves the time for the first network device to send historical certificate chains to the visited network device and improves the efficiency of authenticating the terminal device.

[0208] In one possible implementation, the determining module 902 is specifically used to: retrieve historical roaming records corresponding to the identity identifier and the first credential information from the historical roaming database based on the identity identifier and the first credential information; determine whether the terminal device is a recent historical roaming device based on the retrieval results, wherein the recent historical roaming device is a terminal device that has accessed the network corresponding to the first network device within a first time period; if the terminal device is a recent historical roaming device, determine that the terminal device is a trusted device; or, if the terminal device is not a recent historical roaming device, determine whether the terminal device is a trusted device through a second network device based on the identity identifier and the first credential information, wherein the second network device is a blockchain network device.

[0209] In another possible implementation, the first credential information mentioned above includes a private key credential; the determining module 902 is specifically used to: send a first verification request to the second network device, the first verification request carrying the identity identifier; receive a public key credential sent by the second network device, the public key credential being a credential retrieved by the second network device from a trusted device public key database based on the identity identifier; and determine whether the terminal device is a trusted device based on the public key credential and the private key credential.

[0210] In another possible implementation, the first credential information mentioned above includes historical roaming aggregation credentials; the determining module 902 is specifically used to: send a second verification request to the second network device, the second verification request carrying the identity identifier; receive historical roaming verification information sent by the second network device, the historical roaming verification information being retrieved by the second network device from a trusted historical roaming database based on the identity identifier; and determine whether the terminal device is a trusted device based on the historical roaming verification information and the historical roaming aggregation credentials.

[0211] Another possible implementation is that the determining module 902 is specifically used to: establish a connection with the terminal device when the first judgment result indicates that the terminal device is a trusted device; or refuse to establish a connection with the terminal device when the first judgment result indicates that the terminal device is not a trusted device.

[0212] In another possible implementation, the first credential information mentioned above also includes a self-credibility score, which is used to characterize the credibility of the historical roaming aggregation credential. The determining module 902 is specifically used to: determine the credibility level of the terminal device based on the self-credibility score, a first threshold, and a second threshold when the first judgment result indicates that the terminal device is a trustworthy device. The credibility level includes any one of the following: a first credibility level, a second credibility level, and a third credibility level, wherein the first credibility level is higher than the second credibility level, and the second credibility level is higher than the third credibility level; and establish a connection with the terminal device based on the credibility level of the terminal device.

[0213] In another possible implementation, the determining module 902 is specifically used to: establish an unrestricted connection with the terminal device when the trust level is the first trust level; establish a restricted connection with the terminal device when the trust level is the second trust level, wherein the restricted connection represents a connection that limits the network rate; and send an authentication request to a third network device of the terminal device when the trust level is the third trust level, and establish a restricted connection with the terminal device upon receiving authentication success information sent by the third network device, wherein the third network device is the home network device of the terminal device.

[0214] In another possible implementation, the mobile terminal access device 500 with multi-network collaborative trust further includes: a sending module 503 and a switching module 504; the sending module 503 is used to send an authentication request to the third network device after the determining module 902 establishes a restricted connection with the terminal device when the trust level is the second trust level; the switching module 504 is used to switch the connection with the terminal device to an unrestricted connection when it receives the authentication success information sent by the third network device.

[0215] It should be noted that the mobile terminal access device with multi-network collaborative credit authorization can implement all the processes implemented in the above method embodiments and achieve the same beneficial effects. To avoid repetition, it will not be described again here.

[0216] In the case where the functions of the integrated modules described above are implemented in hardware, this application provides a possible structural schematic diagram of the electronic device involved in the above embodiments. For example... Figure 6 As shown, the electronic device 90 includes: a processor 92, a communication interface 93, and a bus 94. Optionally, the electronic device 90 may also include a memory 91.

[0217] Processor 92 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 92 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 92 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0218] Communication interface 93 is used to connect with other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0219] The memory 91 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0220] As one possible implementation, the memory 91 can exist independently of the processor 92. The memory 91 can be connected to the processor 92 via a bus 94 and is used to store instructions or program code. When the processor 92 calls and executes the instructions or program code stored in the memory 91, it can implement the mobile terminal access method with multi-network collaborative trust provided in this application embodiment.

[0221] In another possible implementation, memory 91 can also be integrated with processor 92.

[0222] Bus 94 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 94 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0223] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the service calling device can be divided into different functional modules to complete all or part of the functions described above.

[0224] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described multi-network collaborative trust mobile terminal access method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0225] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0226] This application also provides a readable storage medium storing a program or instructions. When executed by a computer, the program or instructions implement the mobile terminal access method for multi-network collaborative trust provided in the above embodiments. It is understood that all or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware. The readable storage medium can be any of the foregoing embodiments or memory. The readable storage medium can also be an external storage device of the service invocation device, such as a pluggable hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the service invocation device. Further, the readable storage medium can include both internal storage units of the service invocation device and external storage devices. The readable storage medium is used to store the computer program and other programs and data required by the service invocation device. The readable storage medium can also be used to temporarily store data that has been output or will be output.

[0227] This application also provides a computer program product, which is stored in a storage medium. When the computer program product is executed by a computer, it implements the mobile terminal access method for multi-network collaborative trust provided in the above embodiments.

[0228] It should be noted that, in this document, 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 limitations, 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 that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0229] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0230] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A mobile terminal access method for multi-network collaborative credit authorization, executed by a first network device, characterized in that, include: The system receives an access request sent by a terminal device. The access request carries the terminal device's identity identifier and first credential information. The first credential information includes the terminal device's private key credential or historical roaming aggregation credential. The historical roaming aggregation credential is the terminal device's compressed historical certificate chain. The historical certificate chain includes network authorization credentials of the visited networks that the terminal device has historically accessed. Based on the identity identifier and the first credential information, a first judgment result is determined, wherein the first judgment result indicates whether the terminal device is a trusted device; Based on the first judgment result, determine whether to establish a connection with the terminal device.

2. The mobile terminal access method for multi-network collaborative credit authorization according to claim 1, characterized in that, The step of determining the first judgment result based on the identity identifier and the first credential information includes: Based on the identity identifier and the first credential information, retrieve the historical roaming record corresponding to the identity identifier and the first credential information from the historical roaming database; Based on the search results, it is determined whether the terminal device is a recent historical roaming device. The recent historical roaming device is a terminal device that has accessed the network corresponding to the first network device within the first time period. If the terminal device is a recently used roaming device, then the terminal device is determined to be a trusted device; or, If the terminal device is not a recently roaming device, based on the identity identifier and the first credential information, a second network device is used to determine whether the terminal device is a trusted device, whereby the second network device is a blockchain network device.

3. The mobile terminal access method for multi-network collaborative credit authorization according to claim 2, characterized in that, The first credential information includes a private key credential; the step of determining whether the terminal device is a trusted device through a second network device based on the identity identifier and the first credential information includes: Send a first verification request to the second network device, wherein the first verification request carries the identity identifier; Receive a public key certificate sent by the second network device, wherein the public key certificate is a certificate retrieved by the second network device from a trusted device public key database based on the identity identifier; Based on the public key certificate and the private key certificate, determine whether the terminal device is a trusted device.

4. The mobile terminal access method for multi-network collaborative credit authorization according to claim 2, characterized in that, The first credential information includes historical roaming aggregation credentials; the step of determining whether the terminal device is a trusted device through a second network device based on the identity identifier and the first credential information includes: Send a second authentication request to the second network device, the second authentication request carrying the identity identifier; The system receives historical roaming verification information sent by the second network device, wherein the historical roaming verification information is retrieved by the second network device from a trusted historical roaming database based on the identity identifier; Based on the historical roaming verification information and the historical roaming aggregation certificate, it is determined whether the terminal device is a trusted device.

5. The mobile terminal access method for multi-network collaborative credit authorization according to claim 1, characterized in that, The step of determining whether to establish a connection with the terminal device based on the first judgment result includes: If the first determination result indicates that the terminal device is a trusted device, then establish a connection with the terminal device; or... If the first determination result indicates that the terminal device is not a trusted device, then the connection with the terminal device is refused.

6. The mobile terminal access method for multi-network collaborative credit authorization according to claim 4, characterized in that, The first credential information also includes a self-credibility score, which is used to characterize the credibility of the historical roaming aggregation credential; the step of determining whether to establish a connection with the terminal device based on the first judgment result includes: If the first judgment result indicates that the terminal device is a trusted device, the trust level of the terminal device is determined based on its own trust score, the first threshold and the second threshold. The trust level includes any one of the following: a first trust level, a second trust level and a third trust level, wherein the first trust level is higher than the second trust level and the second trust level is higher than the third trust level. A connection is established with the terminal device based on its trust level.

7. The mobile terminal access method for multi-network collaborative credit authorization according to claim 6, characterized in that, The step of establishing a connection with the terminal device based on the trust level of the terminal device includes: When the trust level is the first trust level, an unrestricted connection is established with the terminal device; When the trust level is the second trust level, a restricted connection is established with the terminal device, wherein the restricted connection represents a connection that limits the network rate; When the trust level is the third trust level, an authentication request is sent to the third network device of the terminal device, and upon receiving the authentication success information sent by the third network device, a restricted connection is established with the terminal device, wherein the third network device is the home network device of the terminal device.

8. The mobile terminal access method for multi-network collaborative credit authorization according to claim 7, characterized in that, After establishing a restricted connection with the terminal device when the trust level is the second trust level, the method further includes: Send an authentication request to the third network device; Upon receiving a successful verification message from the third network device, the connection with the terminal device is switched to an unrestricted connection.

9. A mobile terminal access device for multi-network collaborative credit authorization, characterized in that, include: Receive module and determine module; The receiving module is used to receive an access request sent by a terminal device. The access request carries the identity identifier of the terminal device and first credential information. The first credential information includes the private key credential or historical roaming aggregation credential of the terminal device. The historical roaming aggregation credential is a compressed historical certificate chain of the terminal device. The historical certificate chain includes network authorization credentials of the visited networks that the terminal device has accessed in the past. The determining module is used to determine a first judgment result based on the identity identifier and the first credential information, wherein the first judgment result indicates whether the terminal device is a trusted device; And, based on the first judgment result, determine whether to establish a connection with the terminal device.

10. The mobile terminal access device for multi-network collaborative credit authorization according to claim 9, characterized in that, The determining module is specifically used for: Based on the identity identifier and the first credential information, retrieve the historical roaming record corresponding to the identity identifier and the first credential information from the historical roaming database; Based on the search results, it is determined whether the terminal device is a recent historical roaming device. The recent historical roaming device is a terminal device that has accessed the network corresponding to the first network device within the first time period. If the terminal device is a recently used roaming device, then the terminal device is determined to be a trusted device; or, If the terminal device is not a recently roaming device, based on the identity identifier and the first credential information, a second network device is used to determine whether the terminal device is a trusted device, whereby the second network device is a blockchain network device.

11. The mobile terminal access device for multi-network collaborative credit authorization according to claim 10, characterized in that, The first credential information includes a private key credential; the determining module is specifically used for: Send a first verification request to the second network device, wherein the first verification request carries the identity identifier; Receive a public key certificate sent by the second network device, wherein the public key certificate is a certificate retrieved by the second network device from a trusted device public key database based on the identity identifier; Based on the public key certificate and the private key certificate, determine whether the terminal device is a trusted device.

12. The mobile terminal access device for multi-network collaborative credit authorization according to claim 10, characterized in that, The first credential information includes historical roaming aggregation credentials; the determining module is specifically used for: Send a second authentication request to the second network device, the second authentication request carrying the identity identifier; The system receives historical roaming verification information sent by the second network device, wherein the historical roaming verification information is retrieved by the second network device from a trusted historical roaming database based on the identity identifier; Based on the historical roaming verification information and the historical roaming aggregation certificate, it is determined whether the terminal device is a trusted device.

13. The mobile terminal access device for multi-network collaborative credit authorization according to claim 9, characterized in that, The determining module is specifically used for: If the first determination result indicates that the terminal device is a trusted device, then establish a connection with the terminal device; or... If the first determination result indicates that the terminal device is not a trusted device, then the connection with the terminal device is refused.

14. The mobile terminal access device for multi-network collaborative credit authorization according to claim 12, characterized in that, The first credential information also includes a self-credibility score, which is used to characterize the credibility of the historical roaming aggregation credential; the determining module is specifically used for: If the first judgment result indicates that the terminal device is a trusted device, the trust level of the terminal device is determined based on its own trust score, the first threshold and the second threshold. The trust level includes any one of the following: a first trust level, a second trust level and a third trust level, wherein the first trust level is higher than the second trust level and the second trust level is higher than the third trust level. A connection is established with the terminal device based on its trust level.

15. The mobile terminal access device for multi-network collaborative credit authorization according to claim 14, characterized in that, The determining module is specifically used for: When the trust level is the first trust level, an unrestricted connection is established with the terminal device; When the trust level is the second trust level, a restricted connection is established with the terminal device, wherein the restricted connection represents a connection that limits the network rate; When the trust level is the third trust level, an authentication request is sent to the third network device of the terminal device, and upon receiving the authentication success information sent by the third network device, a restricted connection is established with the terminal device, wherein the third network device is the home network device of the terminal device.

16. The mobile terminal access device for multi-network collaborative credit authorization according to claim 15, characterized in that, The device further includes: a transmitting module and a switching module; The sending module is configured to send an authentication request to the third network device after the determining module establishes a restricted connection with the terminal device when the trust level is the second trust level. The switching module is used to switch the connection with the terminal device to an unrestricted connection upon receiving a successful verification message sent by the third network device.

17. An electronic device, characterized in that, It includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the mobile terminal access method for multi-network collaborative trust as described in any one of claims 1 to 8.

18. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions, which, when executed by a computer, implement the mobile terminal access method for multi-network collaborative trust as described in any one of claims 1 to 8.