WO2020010767A1 - Alliance-based unified trust anchor system for whole network, and construction method - Google Patents

Abstract

Provided in the present invention are an alliance-based unified trust anchor system for the whole network, and a construction method. The system comprises: an alliance region, the alliance region comprising n trust root servers which are connected to each other; n top-level trust server sets, wherein each top-level trust server set is connected to a trust root server, each top-level trust server set comprises m top-level trust servers, and the m top-level trust servers are connected to the same trust root server; n*m authority trust server sets, wherein each authority trust server set is connected to a top-level trust server, each authority trust server set comprises j authority trust servers, and the j authority trust servers are connected to the same top-level trust server; and n*m*j terminal sets, wherein each terminal set is connected to an authority trust server, each terminal set comprises i terminals, and the i terminals are connected to the same authority trust server.

Description

Alliance-wide unified trust anchor system based on alliance and construction method

Cross-reference to related applications

This application claims the priority of Chinese Patent Application No. “2018107430314” filed by Beijing Information Science and Technology University on July 9, 2018, with the name of the invention “a unified alliance-based unified trust anchor system and construction method”.

Technical field

The present invention relates to the field of communications, and in particular, to an alliance-based unified trust anchor system and construction method for the entire network.

Background technique

Because the existing TCP / IP protocol does not have inherent security mechanisms such as address authenticity authentication, it is difficult to trace the source of the attack and the identity of the attacker. The routing device forwards packets based on the destination address, and does not verify the source of the data packet. A large number of address forgery-based attacks cannot be tracked, causing a large number of attacks such as source address spoofing, routing hijacking, and denial of service, which seriously threatens network security. Solving the problem of network naming security including address security and building a secure and trusted Internet environment have become important issues that need to be addressed urgently.

In the field of network naming security research, more and more attention has been paid to cryptographic-based address security mechanisms, including certificate-based public key cryptography and self-authentication mechanisms. Under the public key cryptosystem, public key digital signature technology needs to rely on the CA certificate issued by the Public Key Infrastructure (PKI) to bind the entity identity and the public key to ensure the authenticity of the entity's public key. Binding the user's public key and user identity in the form of a public key certificate forms a mature solution to network security issues. However, PKI introduces a trusted third-party CA, which brings the costs of certificate management, storage, and calculation: First, the process of issuing, issuing, obtaining, verifying, and revoking a certificate is complicated; second, it needs to be online The certificate directory provides users with certificate download and status query services at any time, which increases the maintenance overhead. Third, if users communicate with more objects, users must store and manage these certificates locally, which increases the user's overhead. Fourth, large-scale secrets The problem of key management is generally the method of physically adding CAs, and there are also problems of cross authentication and trust management among users of each CA.

With the rapid development of the mobile Internet and the Internet of Things, the number of sensors, wearable devices, and smart terminals connected to the Internet has increased dramatically. The number of public keys required for entity identification is huge. How to implement efficient public key management and how remote communication entities can obtain each other. And ensuring the authenticity of the public key will become a challenge and also an important issue related to the future landing of the Internet architecture.

Summary of the invention

The present invention aims to overcome at least one of the above-mentioned shortcomings and provide an alliance-based unified trust anchor system and construction method for the entire network to achieve efficient management of public keys.

To achieve the above object, the technical solution of the present invention is specifically implemented as follows:

One aspect of the present invention provides a federation-based unified trust anchor system for the entire network, including: federation area, the federation area includes n trusted root servers, and each trusted root server is connected to each other; n top-level trust server sets, each top-level The trust server set connects one trust root server, each top trust server set includes m top trust servers, and m top trust servers connect to one trust root server; n * m permission trust server sets, each permission trust server set Connects to a top-level trust server, each permission trust server set includes j permission trust servers, and j permission trust servers connect to the same top-level trust server; n * m * j terminal sets, each terminal set connects to a permission trust server Each terminal set includes i terminals, i terminals are connected to the same authority trust server; among them, each trusted root server is used to store the names and public key information of all trusted root servers, and stores the names of all top-level trusted servers , Address and public key information, and It is used to issue certificates, and the information stored in each trusted root server is exactly the same. The consensus information is used to ensure the consistency of the stored information. Each top-level trust server is used to store its own public key information and store the authority trusts connected to it. Server name, address, and public key information; each authority trusts the server to store its own public key information, and stores the name, address, and public key information of the terminal connected to it.

Another aspect of the present invention provides a method for constructing a unified trust anchor across the entire network based on a federation, which includes: building a federation area, configuring the federation area to include n trusted root servers, each trusted root server being connected to each other, and each trusted root The server stores the name and public key information of all trusted root servers, and stores the name, address, and public key information of all top-level trusted servers, as well as for issuing certificates, and the information stored by each trusted root server is exactly the same. Consistency of stored information; build n top-level trust server sets, and configure each top-level trust server set to connect a trusted root server, each top-level trust server set includes m top-level trust servers, and m top-level trust server connections are the same A trust root server, each top-level trust server stores its own public key information, and stores the name, address, and public key information of the authority trust server connected to it; builds a set of n * m authority trust servers and configures each authority trust Server collection connects to a top-level trusted server Server, each permission trust server set includes j permission trust servers, and j permission trust servers are connected to the same top-level trust server, each permission trust server stores its own public key information, and stores the name of the terminal connected to it, Address and public key information; n * m * j terminal sets are constructed, and each terminal set is connected to a permission trust server, each terminal set includes i terminals, and i terminals are connected to the same permission trust server.

It can be seen from the technical solution provided by the present invention that through the alliance-based unified trust anchor system and construction method based on the alliance provided by the embodiment of the present invention, the alliance trust anchor exists in a decentralized form, and the alliance region is ensured through a consensus algorithm. The data of each trust root server in the network is consistent. A unified trust anchor across the entire network is established in the alliance to jointly manage the public key. This decentralized organization and management method based on the alliance can ensure that the status of each trusted root server is consistent and effective. The ground avoids various disadvantages in the current centralization work, realizes the efficient management of public keys, enables remote communication entities to obtain the counterpart's public key, and ensures the authenticity of the public key.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic structural diagram of a trust model according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of an alliance-based unified trust anchor system throughout the network according to an embodiment of the present invention; FIG.

FIG. 3 is a flowchart of an alliance-based full-text unified trust anchor system and a construction method according to an embodiment of the present invention.

detailed description

The embodiments of the present invention will be described in detail below with reference to the drawings.

The foundation of the trust model is that all trusted users have a trusted root. In the trust model, as shown in Figure 1, this is a simple three-tier trust structure, which is a chain trust relationship. For example, the trusted entity A1 can be represented as such a trust chain: (R, C1, A1) It shows that A1 can be traced back to the root of trust R that generated it. There is a root node R as the starting point of trust. This point of establishing a trust relationship is called a trust anchor. The trust path of this model is that the path from the root node to the leaf node constitutes the trust path.

The present invention adopts a method of establishing an alliance trust anchor. As shown in FIG. 2, each country has a trust root server (data is consistent), and each country relies on each country's sub-cluster of trust root server to manage each country. The trusted root server is maintained by the country to which it belongs. The federation zone consists of the root server with the lowest depth of trust. All trusted root servers in the federation zone form an undirected graph. All trusted root servers have physical links and can communicate with each other. The trusted root server nodes shown in A, X, Y, and Z in FIG. 2 form the federation area.

Specifically, the alliance-based unified trust anchor system of the entire network provided by the embodiment of the present invention includes:

Alliance area, the alliance area includes n trusted root servers (as shown in Figure A, X, Y, Z), each trusted root server is connected to each other;

n top trusted server sets, each top trusted server set connected to a trusted root server, each top trusted server set includes m top trusted servers (as shown in the figure B1, B2, ...), and m top trusted servers are connected The same trusted root server;

n * m permission trust server sets, each permission trust server set is connected to a top-level trust server, and each permission trust server set includes j permission trust servers (as shown in the figure C1, C2 ... or C3, C4 ...) And j permission trust servers are connected to the same top-level trust server;

n * m * j terminal sets, each terminal set is connected to a rights trust server, each terminal set includes i terminals (as shown in the figure D1, D2 ... or D3, D4 ... or D5, D6 ...) , I terminals connect to the same permission trust server;

among them,

Each trusted root server is used to store the names and public key information of all trusted root servers, and stores the name, address, and public key information of all top-level trusted servers, and information used to sign certificates, and each trusted root server stores information Exactly the same, to ensure the consistency of the stored information through a consensus algorithm;

Each top-level trust server is used to store its own public key information and the name, address, and public key information of the authority trust server connected to it;

Each authority trust server is used to store its own public key information and store the name, address, and public key information of the terminal connected to it.

Specifically, the alliance trust anchor exists in a decentralized form. The consensus algorithm is used to ensure that the data of each trust root server in the alliance area is consistent. A unified trust anchor across the network is established in the alliance to jointly manage the public key. The decentralized organization and management of the alliance can ensure that the status of each trusted root server is consistent, effectively avoiding various disadvantages existing in the current centralization work, and achieve efficient management of public keys, so that remote communication entities can obtain each other's Public key, and ensure the authenticity of the public key. The consensus algorithm used is determined according to the specific situation. For example, the Epaxos consensus algorithm can be used. In the alliance area, each node is equal in sovereignty. Each node is only responsible for the work of the node. In principle, it is forbidden to apply, modify or bind other top-level trusts. Server information. Within the sub-cluster, each country can adopt, for example, multi-paxos-based cluster management. In the alliance area, each alliance node has equal rights, so no leader role is set.

Each trusted root server in the federation area adopts asymmetric encryption and owns the public keys of other trusted root servers. The public key update, query, and authentication process between terminal subjects need to pass the resolution of the federation. Each trusted root server stores the names, addresses, and public key information of all top-level trusted servers. The specific data stored by each server is shown in the following table.

Example of data stored on the root trust server:

Numbering	Top server name	Top server address information	Top-level server public key
1	B1	addr1	Public Key1
2	B2	addr2	Public Key 2
3	E1	Addr3	Public Key3
4	...	...	...

Numbering	Root server name	Root server public key
1	A	Public Key1
2	X	Public Key 2
3	Y	Public Key3
4	Z	Public Key 4
5	...	...

Example of data stored on the top-level trusted server (their own public key is also stored on the top-level server):

Numbering	Authorization server name	Authorization server address information	Authorization server public key
1	C1	addr1	Public Key1
2	C2	addr2	Public Key 2
3	...	...	...

Example of data stored on the authority trust server (the authority server also stores its own public key):

Numbering	Terminal entity name	Terminal entity address information	End entity public key
1	D1	addr1	Public Key1
2	D2	addr2	Public Key 2
3	...	...	...

As an optional embodiment of the present invention, each set of top-level trust servers is connected to all trusted root servers, and each top-level trust server set includes m top-level trust servers, and m top-level trust servers are connected to each trusted root server. This ensures that the top-level trusted server can connect to any trusted root server and perform data transmission.

As an optional embodiment of the present invention, the top-level trust server is further configured to send a change request to a trusted root server connected to the top-level trust server; the trust root server is further used to propose a change resolution to the federation area, and according to a preset resolution policy, After the resolution is passed, the trust root server responds to the change request of the top trust server and updates the data stored in all the trust root servers in the federation area through a consensus algorithm; the top trust server is also used to perform the change operation. In this way, the top-level trusted root server can apply for changes to the trusted root server connected to it. After accepting and making changes to the trusted root server connected to it, a resolution is made in the federation area, and only after the resolution in the federation area passes, can it be changed. When a change operation is performed, at the same time, all the root trust servers in the alliance area perform the same modification through a consensus algorithm to ensure data consistency.

Specifically, when the public key needs to be updated in the top-level trust server B1, the specific process includes:

1. The top-level trust server B1 sends a request to update its public key to its superior trust root server A.

2. Trust the root server A to make a decision to update the public key to the alliance.

3. After the resolution is passed, the public key of the top trusted server B1 is updated in the trusted root server A. Through the consensus algorithm, the data in each trusted root server is consistent.

4. The top trust server B1 updates its public key.

When the public key needs to be updated in the terminal entity D1, the specific process includes:

1. The terminal entity D1 sends a request to update its public key to its superior authority trust server C1.

2. After the audit is passed, the public key of the terminal entity D1 is updated in the authority trust server C1.

3. The terminal entity D1 updates its public key.

When the public key needs to be updated in the authority trust server C1, the specific process includes:

1. The authority trust server C1 sends a request to update its public key to its superior top-level trust server B1.

2. After passing the audit, the public key of the authority trust server C1 is updated in the top trust server B1.

3. The authority trust server C1 updates its public key.

As an optional embodiment of the present invention, the trusted root server is also used to propose a change resolution within the alliance, and after the resolution is passed according to a preset resolution policy, change its own data and update the area of the alliance through a consensus algorithm. All trust the data stored in the root server. In this way, if a trusted root server in the alliance region needs to make data changes, a resolution is made in the alliance region. Only after the resolution in the alliance region is passed can the change operation be performed. At the same time, all trusts in the alliance region The root server performs the same modification through a consensus algorithm to ensure data consistency.

Specifically, when the public key needs to be updated in the trusted root server A, the specific process includes:

1. Trust the root server A to propose a resolution to update the public key within the alliance.

2. After the resolution is passed, trust the root server A to update its public key. Through the consensus algorithm, the data in each trusted root server is consistent.

As an optional embodiment of the present invention, the terminal is further configured to send a query request to the peer terminal to the authority trust server connected to the terminal; the authority trust server is further configured to query the relevant information of the peer terminal without querying, Send a query request to the top-level trust server connected to it; the top-level trust server is also used to send a query request to the trusted root server connected to it when no related information of the peer terminal is queried; the trust root server is also used to When querying the related information of the peer terminal, it sends a query request to the trusted root server where the peer terminal connected to it, and receives the top-level trust server where the peer terminal connected in turn via the trusted root server where the peer terminal is located. 2. The authority trust server where the opposite terminal is located queries the relevant information of the opposite terminal, and sends the relevant information of the opposite terminal obtained by the query to the terminal through the top-level trust server and the authority trust server. In this way, if the terminal needs to query the related information of the peer terminal, it can query through the authority trust server, top-level trusted root server, and trusted root server connected to it. At this time, if the trusted root server does not query, then it passes The query is performed by another trusted root server in the federation area. After the query, the query is sent to the terminal through the trusted root server, the top-level trusted root server, and the permission trusted server.

Specifically, when the terminal body D1 wants to query the public key of the terminal body G1, the specific process includes:

1. The terminal body D1 queries its superior authority trust server C1.

2. When the public key of the terminal body G1 is not queried in the authority trust server C1, the authority trust server C1 queries its upper-level top trust server B1.

3. When the top-level trust server B1 does not query the public key of the terminal principal G1, the top-level trust server B1 queries its upper-level trust root server A.

4. When the public key of the terminal principal G1 is not found in the trusted root server A, there are two considerations:

(1) According to the consideration of management mode, only the trusted root server in the home country can access the subordinate servers in the home country.

(2) Based on efficiency considerations, the trusted root server in the home country can also access the subordinate servers in other countries.

By way of (1), the trusted root server A queries the trusted root server X where the public key of the terminal body G1 is located. By trusting the root server X, the subordinate top trust server E1 that trusts the root server X is queried, and then the top trust server E1 queries its subordinate authority trust server F1, and finally queries the public key of the terminal body G1.

From the method (2), the trust root server A can directly query the subordinate top trust server E1 that trusts the root server X, and then the top trust server E1 queries its subordinate authority trust server F1, and finally queries the public key of the terminal body G1. .

In addition, if you do not cross domains, perform the related operations through the following examples:

When the terminal body D1 wants to query the public key of the terminal body D2, the specific process includes:

1. The terminal body D1 queries its superior authority trust server C1.

2. When the public key of the terminal body D2 is queried in the authority trust server C1, it is returned to the public key of D2 queried by the terminal body D1.

When the terminal body D1 wants to query the public key of the terminal body D5, the specific process includes:

1. The terminal body D1 queries its superior authority trust server C1.

2. When the public key of the terminal body D5 is not queried in the authority trust server C1, the authority trust server C1 queries its upper-level top trust server B1.

3. When the top-level trust server B1 does not query the public key of the terminal subject D5, the top-level trust server B1 queries its upper-level trust root server A.

4. Trust the root server A through its subordinate top trust server B2, and then the top trust server B2 queries the authority trust server C3. The authority trust server C3 queries the public key of the terminal subject D5 and returns it to the terminal subject D1. D5 public key.

As an optional embodiment of the present invention, the terminal is further configured to query whether the identification information of the opposite terminal is cached locally, and to query the trust of the opposite terminal when the identification information of the opposite terminal is not cached locally. The root server sends a query request; the terminal is also used to query the trusted root server where the peer terminal is located to obtain the identity information of the peer terminal, and to the top level where the peer terminal connected to the trusted root server where the peer terminal is located is located. The trust server sends a query request; the terminal is also used for the permission of the peer terminal connected to the top-level trust server where the peer terminal is located when the top-level trust server where the peer terminal is located obtains the identification information of the peer terminal. The trust server sends a query request; the terminal is also used to receive the query response information sent by the authority trust server where the peer terminal is located when the authority trust server where the peer terminal is located obtains the identification information of the peer terminal. In this way, if the terminal needs to query the related information of the peer terminal, it can directly query the trusted root server, top-level trust server, and authority trust root server where the peer terminal is located to check whether there is identification information of the peer terminal. The query response information is obtained after the identification information is included, and the query information is included in the query response information and sent to the terminal, thereby improving the query efficiency.

Specifically, regardless of whether cross-domain issues are considered, the terminal can query the public terminal's public key on the network where the opposite terminal is located by recursively iteratively. For public key information, the specific operations are as follows:

1. The terminal body D1 first locally queries whether the public key information of the peer body (for example, the terminal body D2 or the terminal body G1) has been cached.

2. If the query is not performed locally, the terminal subject D1 requests the root trust server where the peer subject (for example, the terminal subject D2 or the terminal subject G1) is located to query the ID information of the peer subject through an iterative query. If no ID information is queried on the root trust server, the query is terminated and returned to the terminal without information. If the ID information is queried on the root trust server, the terminal body D1 continues to query the ID information of the gateway B on the top-level trust server where the opposite body (for example, the terminal body D2 or the terminal body G1) is located.

3. The terminal body D1 requests the top-level trust server to query the ID information of the opposite body (for example, the terminal body D2 or the terminal body G1). If the ID information is not queried on the top-level trusted server, the query is terminated and returned to the terminal body D1 with no information found. If the ID information is queried on the top-level trust server, the terminal body D1 continues to query the ID trust information of the gateway B from the authority trust server where the opposite body (for example, the terminal body D2 or the terminal body G1) is located.

4. The terminal body D1 requests the authority trust server to query the ID information of the opposite body (for example, the terminal body D2 or the terminal body G1). If the ID information is not queried on the authority trust server, the query is terminated and returned to the terminal D1. If the ID information is queried on the authority trust server, it returns the public key information of the opposite subject (for example, the terminal subject D2 or the terminal subject G1) requested by the terminal subject D1.

Specifically, an example of the name structure of the identity (ID) is as follows:

www.bistu.edu.cn

Example of data stored on the root trust server:

Numbering	first name	Address information
1	cn	addr1
2	org	addr2
3	com	add3
4	gov	addr4
5	net	addr5
...	...	...

Example of data stored on top trusted server under Cn:

Numbering	first name	Address information
1	com.cn	addr1
2	org.cn	addr2
3	gov.cn	addr3
4	net.cn	addr4
5	edu.cn	addr5
...	...	...

Example of data stored on the server with permission trust under Edu.cn:

Numbering	first name	Address information	Public key
1	bistu.edu.cn	addr1	Public Key1
2	bjut.edu.cn	addr2	Public Key 2
3	njtu.edu.cn	addr3	Public Key3
4	pku.edu.cn	addr4	Public Key 4
5	tsinghua.edu.cn	addr5	Public Key 5
...	...	...	...

Specifically, two methods of communication authentication between terminal bodies are considered:

1. Certification based on certificates issued by superiors;

2. Authentication based on public key between peers.

Therefore, as an optional implementation manner of the present invention, the terminal is further configured to send an authentication request to the peer terminal to the authority trust server connected to the terminal; the authority trust server is further configured to query the authentication information of the peer terminal without query. After that, it sends an authentication request to the top-level trust server connected to it; the top-level trust server is also used to send a query request to the trusted root server connected to it without querying the authentication information of the peer terminal; the trust root server is also used to When the authentication information of the peer terminal is not queried, a query request is sent to the trusted root server where the peer terminal connected to it is received, and the authentication information of the peer terminal obtained through the query of the trusted root server where the peer terminal is located passes the top level The trust server and authority trust server are sent to the terminal. In this way, if the terminal needs to authenticate the peer terminal, it can perform authentication through the authority trust server, top-level trust root server, and trust root server connected to it. At this time, when the trust root server does not query the authentication information, it passes the federation. Another trusted root server in the region queries the authentication information. After querying the authentication information, it sends it to the terminal through the trusted root server, the top-level trusted root server, and the authority trusted server.

Specifically, when the terminal body D1 wants to authenticate the public key of the terminal body D5, the terminal body D5 needs the public key of the authority trust server C3, and the top-level trust server B2 contains the public key information of the authority trust server C3. Therefore, only You need to find the data of the top trusted server B2. The specific process includes:

1. The terminal body D1 queries its superior authority trust server C1.

2. When the public key of the authority trust server C3 is not queried in the authority trust server C1, the authority trust server C1 queries its upper-level top trust server B1.

3. When the top trust server B1 does not query the public key of the authority trust server C3, the top trust server B1 queries its superior trust root server A.

4. In the trusted root server A, the data of the top trusted server B2 is queried, thereby obtaining the public key of the authority trusted server C3, and completing the authentication.

As an optional embodiment of the present invention, the terminal is further configured to send an authentication request to the peer terminal to the authority trust server connected to the terminal; the authority trust server is further configured to query the authentication information of the peer terminal without querying, Send an authentication request to the top-level trust server connected to it; the top-level trust server is also used to send a query request to the trusted root server connected to it when no authentication information of the peer terminal is queried; the trust root server is also used to When querying the authentication information of the peer terminal, it sends a query request to the trusted root server where the peer terminal connected to it, and receives the top-level trust server where the peer terminal connected in turn via the trusted root server where the peer terminal is located. 3. The authority trust server where the opposite terminal is located queries the authentication information of the opposite terminal, and sends the obtained authentication information of the opposite terminal to the terminal through the top-level trust server and the authority trust server. In this way, if the terminal needs to authenticate the peer terminal, it can perform authentication through the authority trust server, top-level trust root server, and trust root server connected to it. At this time, when the trust root server does not query the authentication information, it passes the federation. Another trusted root server in the region queries the authentication information. The other trusted root server queries the authentication information through the top-level trust server and authority trust server connected to itself, and passes the found authentication information through the trusted root server and top-level trusted root server. And the authority trust server sends it to the terminal.

Specifically, when the terminal body D1 wants to authenticate the public key of the terminal body D5, the terminal body D1 needs to authenticate the public key of the terminal body D5. The specific process includes:

1. The terminal body D1 queries its superior authority trust server C1.

2. When the public key of the terminal body D5 is not queried in the authority trust server C1, the authority trust server C1 queries its upper-level top trust server B1.

3. When the top-level trust server B1 does not query the public key of the terminal body D5, the top-level trust server B1 queries its upper-level trust root server A.

4. The trusted root server A makes a query through its subordinate top trusted server B2.

5. The subordinate authority of the top-level trust server B2 trusts the server C3, thereby obtaining the public key of the terminal body D5 and completing the authentication.

It can be seen that through the alliance-based unified trust anchor system of the entire network provided by the present invention, the alliance trust anchor exists in a decentralized form, and the consensus algorithm is used to ensure that the data of each trust root server in the alliance area is consistent, and Establish a unified trust anchor across the entire network and jointly manage the public key. This alliance-based decentralized organization and management method can ensure that the status of each trusted root server is consistent, effectively avoiding various disadvantages in the current centralization work. , To achieve efficient management of public keys, so that remote communication entities can obtain each other's public keys and ensure the authenticity of public keys.

FIG. 3 shows a method for constructing an alliance-based unified trust anchor of the entire network provided by an embodiment of the present invention. The solution is applied to the above system, and the method is only briefly described here. For other unresolved matters, please refer to the related system. Description. Referring to FIG. 3, a method for constructing a unified network-based unified trust anchor provided by an embodiment of the present invention includes:

S301. Construct a federation zone. The federation zone is configured to include n trusted root servers, and each trusted root server is connected to each other. Each trusted root server stores the names and public key information of all trusted root servers, and stores the names of all top trusted servers. , Address, and public key information, as well as for issuing certificates, and the information stored by each trusted root server is exactly the same, and the consistency of the stored information is guaranteed by a consensus algorithm;

S302. Build n top trusted server sets, and configure each top trusted server set to connect to one trusted root server, each top trusted server set includes m top trusted servers, and m top trusted servers connected to the same trusted root server. Each top-level trust server stores its own public key information, and stores the name, address, and public key information of the authority trust server connected to it;

S303. Build n * m permission trust server sets, and configure each permission trust server set to connect to a top-level trust server. Each permission trust server set includes j permission trust servers, and j permission trust servers are connected to the same top-level trust. Server, each authority trusts the server to store its own public key information, and stores the name, address, and public key information of the terminal connected to it;

S304. Construct n * m * j terminal sets, and configure each terminal set to connect to a permission trust server. Each terminal set includes i terminals, and i terminals connect to the same permission trust server.

It can be seen that through the alliance-based unified trust anchor construction method provided by the present invention, the alliance trust anchor exists in a decentralized form, and the consensus algorithm is used to ensure that the data of each trust root server in the alliance area is consistent. The alliance establishes a unified trust anchor across the entire network and jointly manages the public key. This alliance-based decentralized organization and management method can ensure that the status of each trusted root server is consistent, effectively avoiding the various existing existing centralized work. The disadvantage is that the efficient management of the public key is realized, so that the remote communication entity can obtain the public key of the other party and ensure the authenticity of the public key.

As an optional implementation manner of the embodiment of the present invention, the method for constructing a federation-based unified trust anchor for the entire network further includes: configuring each top-level trust server set to connect to all trusted root servers, and each top-level trust server set including m top-level trusts Server, and m top trusted servers connect to each trusted root server. This ensures that the top-level trusted server can connect to any trusted root server and perform data transmission.

As an optional implementation manner of the embodiment of the present invention, the method for constructing the alliance-based unified trust anchor of the entire network further includes: a change process of the top-level trust server;

The change process for the top trust server includes:

The top-level trust server sends a change request to the trusted root server connected to it;

The trust root server proposes a change resolution to the federation area. After the resolution is passed according to the preset resolution policy, the trust root server responds to the change request of the top trust server and updates the storage of all trusted root servers in the federation area through the consensus algorithm. The data;

The top-level trust server performs the change operation.

In this way, the top-level trusted root server can apply for changes to the trusted root server connected to it. After accepting and making changes to the trusted root server connected to it, a resolution is made in the federation area, and only after the resolution in the federation area passes, can it be changed. When a change operation is performed, at the same time, all the root trust servers in the alliance area perform the same modification through a consensus algorithm to ensure data consistency.

As an optional implementation manner of the embodiment of the present invention, the method for constructing the alliance-based unified trust anchor of the entire network further includes: a process of changing the trust root server:

The process of changing the trusted root server includes:

The trust root server proposes a change resolution in the alliance, and after the resolution is passed according to a preset resolution policy, changes its own data and updates the data stored in all trust root servers in the alliance area through a consensus algorithm.

In this way, if a trusted root server in the alliance region needs to make data changes, a resolution is made in the alliance region. Only after the resolution in the alliance region is passed can the change operation be performed. At the same time, all trusts in the alliance region The root server performs the same modification through a consensus algorithm to ensure data consistency.

As an optional implementation manner of the embodiment of the present invention, the method for constructing the alliance-based unified trust anchor of the entire network further includes a query process of the terminal:

The query process of the terminal includes:

The terminal sends a query request to the opposite terminal to the authority trust server connected to the terminal;

The authority trust server sends a query request to the top-level trust server connected to the peer terminal without querying the relevant information of the peer terminal;

The top-level trust server sends a query request to the trusted root server connected to the peer terminal without querying the relevant information of the peer terminal;

When the trusted root server does not query related information of the peer terminal, it sends a query request to the trusted root server where the peer terminal connected to it and receives the peer terminal connected in turn through the trusted root server where the peer terminal is located. The top trust server and the authority trust server where the peer terminal is located query the related information of the peer terminal, and send the query related information of the peer terminal to the terminal through the top trust server and the authority trust server.

In this way, if the terminal needs to query the related information of the peer terminal, it can query it through the authority trust server, top-level trust root server, and trust root server connected to it. The query is performed by another trusted root server in the federation area. After the query, the query is sent to the terminal through the trusted root server, the top-level trusted root server, and the permission trusted server.

As an optional implementation manner of the embodiment of the present invention, the method for constructing the alliance-based unified trust anchor of the entire network further includes a query process of the terminal:

The query process of the terminal includes:

The terminal queries whether the identification information of the opposite terminal is cached locally;

In the case where the terminal has not locally cached the identification information of the opposite terminal, the terminal sends a query request to the trusted root server where the opposite terminal is located;

When the trusted root server where the peer terminal is located obtains the identification information of the peer terminal, the terminal sends a query request to the top trusted server where the peer terminal connected to the trusted root server where the peer terminal is located;

In the case where the top-level trust server where the peer terminal is located obtains the identification information of the peer terminal, the terminal sends a query request to the authority trust server where the peer terminal connected to the top-level trust server where the peer terminal is located;

When the authority trust server where the opposite terminal is located obtains the identification information of the opposite terminal, the terminal receives the query response information sent by the authority trust server where the opposite terminal is located.

In this way, if the terminal needs to query the related information of the peer terminal, it can directly query the trusted root server, top-level trust server, and authority trust root server where the peer terminal is located to check whether there is identification information of the peer terminal. The query response information is obtained after the identification information is included, and the query information is included in the query response information and sent to the terminal, thereby improving the query efficiency.

As an optional implementation manner of the embodiment of the present invention, the method for constructing the alliance-based unified trust anchor of the entire network further includes: an authentication process of the terminal;

The authentication process of the terminal includes:

The terminal is further configured to send an authentication request for the opposite terminal to the authority trust server connected to the terminal;

The authority trust server is also used to send an authentication request to the top-level trust server connected to the peer terminal without querying the authentication information of the peer terminal;

The top-level trust server is also used to send a query request to the trusted root server connected to the peer terminal without querying the authentication information of the peer terminal;

The trust root server is also used to send a query request to the trusted root server where the peer terminal to which it is connected when the authentication information of the peer terminal is not queried, and to receive the query obtained from the trusted root server where the peer terminal is located. The authentication information of the terminal is sent to the terminal through the top-level trust server and the authority trust server.

In this way, if the terminal needs to authenticate the peer terminal, it can perform authentication through the authority trust server, top-level trust root server, and trust root server connected to it. At this time, when the trust root server does not query the authentication information, it passes the federation. Another trusted root server in the region queries the authentication information. After querying the authentication information, it sends it to the terminal through the trusted root server, the top-level trusted root server, and the authority trusted server.

As an optional implementation manner of the embodiment of the present invention, the method for constructing the alliance-based unified trust anchor of the entire network further includes: an authentication process of the terminal;

The authentication process of the terminal includes:

The terminal is further configured to send an authentication request for the opposite terminal to the authority trust server connected to the terminal;

The authority trust server is also used to send an authentication request to the top-level trust server connected to the peer terminal without querying the authentication information of the peer terminal;

The top-level trust server is also used to send a query request to the trusted root server connected to the peer terminal without querying the authentication information of the peer terminal;

The trust root server is also used to send a query request to the trusted root server where the peer terminal is connected when no authentication information of the peer terminal is queried, and to receive connections through the trusted root server where the peer terminal is located in turn. The top-level trust server where the opposite terminal is located, and the authorization trust server where the opposite terminal is located query the authentication information of the opposite terminal, and send the obtained authentication information of the opposite terminal to the terminal through the top-level trust server and authority trust server. .

In this way, if the terminal needs to authenticate the peer terminal, it can perform authentication through the authority trust server, top-level trust root server, and trust root server connected to it. At this time, when the trust root server does not query the authentication information, it passes the federation. Another trusted root server in the region queries the authentication information. The other trusted root server queries the authentication information through the top-level trust server and authority trust server connected to itself, and passes the found authentication information through the trusted root server and top-level trusted root server. And the authority trust server sends it to the terminal.

Any process or method description in a flowchart or otherwise described herein can be understood as representing a module, fragment, or portion of code that includes one or more executable instructions for implementing a particular logical function or step of a process And, the scope of the preferred embodiments of the present invention includes additional implementations in which the functions may be performed out of the order shown or discussed, including performing the functions in a substantially simultaneous manner or in the reverse order according to the functions involved, which should It is understood by those skilled in the art to which the embodiments of the present invention pertain.

A person of ordinary skill in the art can understand that all or part of the steps carried by the methods in the foregoing embodiments may be implemented by a program instructing related hardware. The program may be stored in a computer-readable storage medium. The program is When executed, one or a combination of the steps of the method embodiment is included.

The above embodiments only describe the preferred embodiments of the present invention, and do not limit the scope of the present invention. Without departing from the design spirit of the present invention, various ordinary technical personnel in the field make various technical solutions of the present invention. Variations and improvements shall fall within the protection scope determined by the claims of the present invention.

Claims (16)

1. An alliance-based unified trust anchor system for the entire network, which is characterized by:

   A federation area, where the federation area includes n trusted root servers, and each of the trusted root servers is connected to each other;

   n top-level trust server sets, each of which is connected to one of the trusted root servers, each of the top-level trust server sets includes m top-level trust servers, and the m top-level trust servers are connected to the same trust Root server

   n * m sets of permission trust servers, each of which is connected to one of the top-level trust servers, each set of permission trust servers includes j permission trust servers, and the j permission trust servers are connected to the same A top-level trust server;

   n * m * j terminal sets, each said terminal set is connected to one said authority trust server, each said terminal set includes i terminals, and said i terminals are connected to the same authority trust server;

   among them,

   Each of the trusted root servers is configured to store the names and public key information of all trusted root servers, and stores the name, address, and public key information of all top-level trusted servers, and is used to issue certificates, and each of the trusted roots The information stored on the server is exactly the same, and the consistency of the stored information is guaranteed by a consensus algorithm;

   Each of the top-level trust servers is configured to store its own public key information, and store the name, address, and public key information of an authority trust server connected to it;

   Each authority trust server is configured to store its own public key information and store the name, address, and public key information of the terminal connected to it.
2. The system of claim 1, wherein:

   Each of the top-level trust server sets is connected to all the trusted root servers, each of the top-level trust server sets includes m top-level trust servers, and the m top-level trust servers are connected to each of the trusted root servers.
3. The system of claim 1, wherein:

   The top-level trust server is further configured to send a change request to the trusted root server connected to the top-level trust server;

   The trusted root server is further used to propose a change resolution to the alliance region. After the resolution is passed according to a preset resolution policy, the trusted root server responds to the change request of the top-level trusted server and passes the consensus algorithm. Update data stored in all trusted root servers in the federation area;

   The top-level trust server is further configured to perform a change operation.
4. The system of claim 1, wherein:

   The trusted root server is also used to propose a change resolution in the alliance, and after the resolution is passed according to a preset resolution policy, change its own data, and update all trusted root servers in the alliance area through the consensus algorithm. Data stored in it.
5. The system of claim 1, wherein:

   The terminal is further configured to send a query request for the opposite terminal to the authority trust server connected to the terminal;

   The authority trust server is further configured to send the query request to a top-level trust server connected to the peer terminal after the related information of the peer terminal is not queried;

   The top-level trust server is further configured to send the query request to a trusted root server connected to the peer terminal after the related information of the peer terminal is not queried;

   The trusted root server is further configured to send the query request to a trusted root server where the peer terminal connected to it is located when no related information of the peer terminal is queried, and receive the trust via the peer terminal where the peer terminal is located. The root server queries the related information of the opposite terminal through the top-level trust server where the opposite terminal is located, and the authority trust server where the opposite terminal is located, and passes the related information of the opposite terminal obtained by the query through The top-level trust server and the authority trust server are sent to the terminal.
6. The system of claim 1, wherein:

   The terminal is also used to query whether the identification information of the opposite terminal is cached locally, and when the identification information of the opposite terminal is not cached locally, sending a query request to the trusted root server where the opposite terminal is located;

   The terminal is further configured to query the trusted root server where the peer terminal is located to obtain the identification information of the peer terminal, and to the top level where the peer terminal connected to the trusted root server where the peer terminal is located is located. Trust the server to send the query request;

   The terminal is further configured to, when the top-level trusted server where the peer terminal is located query for the identification information of the peer terminal, the permission to the peer terminal connected to the top-level trusted server where the peer terminal is located Trust the server to send the query request;

   The terminal is further configured to receive query response information sent by the authority trust server where the peer terminal is located when the authority trust server where the peer terminal is located obtains the identification information of the peer terminal.
7. The system of claim 1, wherein:

   The terminal is further configured to send an authentication request for the opposite terminal to the authority trust server connected to the terminal;

   The authority trust server is further configured to send the authentication request to a top-level trust server connected to the peer terminal without querying the authentication information of the peer terminal;

   The top-level trust server is further configured to send the query request to a trusted root server connected to the peer terminal after no authentication information of the peer terminal is queried;

   The trusted root server is further configured to: when the authentication information of the opposite terminal is not queried, send the query request to the trusted root server where the connected opposite terminal is located, and receive the trust via the opposite terminal. The authentication information of the peer terminal obtained by the root server query is sent to the terminal through the top-level trust server and the authority trust server.
8. The system of claim 1, wherein:

   The terminal is further configured to send an authentication request for the opposite terminal to the authority trust server connected to the terminal;

   The authority trust server is further configured to send the authentication request to a top-level trust server connected to the peer terminal without querying the authentication information of the peer terminal;

   The top-level trust server is further configured to send the query request to a trusted root server connected to the peer terminal after no authentication information of the peer terminal is queried;

   The trusted root server is further configured to: when the authentication information of the opposite terminal is not queried, send the query request to the trusted root server where the connected opposite terminal is located, and receive the trust via the opposite terminal. The root server sequentially queries the authentication information of the opposite terminal through the top-level trust server where the opposite terminal is located and the authority trust server where the opposite terminal is located, and passes the obtained authentication information of the opposite terminal through the query. The top-level trust server and the authority trust server are sent to the terminal.
9. A method for constructing a unified trust anchor for the entire network based on alliance, which is characterized by:

   Construct a federation area, and configure the federation area to include n trusted root servers, each of which is connected to each other, and each of the trusted root servers stores the names and public key information of all trusted root servers, and stores all top-level servers The name, address, and public key information of the trust server, as well as the certificate used to sign the certificate, and the information stored by each said trust root server is exactly the same, and the consistency of the stored information is guaranteed by a consensus algorithm;

   Constructing n top trust server sets, configured to connect one said trust root server to each said top trust server set, each said top trust server set including m top trust servers, and said m top trust servers connected The same trusted root server, each of the top-level trusted servers stores its own public key information, and stores the name, address, and public key information of the authority trusted server connected to it;

   Constructing n * m permission trust server sets, configured to connect one of the top trust servers to each of the permission trust server sets, each of the permission trust server sets including j permission trust servers, and the j permission trusts The server is connected to the same top-level trust server, and each said authority trust server stores its own public key information, and stores the name, address, and public key information of the terminal connected to it;

   Build n * m * j terminal sets, and configure each terminal set to connect to one of the authority trust servers, each terminal set includes i terminals, and the i terminals are connected to the same authority trust server.
10. The method according to claim 9, further comprising:

    Each of the top-level trust server sets is configured to connect to all the trusted root servers, each of the top-level trust server sets includes m top-level trust servers, and the m top-level trust servers connect to each of the trust root servers.
11. The method according to claim 9, further comprising: a change process of the top-level trust server;

    The change process of the top-level trust server includes:

    The top-level trust server sends a change request to the trusted root server connected to the top-level trust server;

    The trusted root server proposes a change resolution to the alliance region, and after the resolution is passed according to a preset resolution policy, the trusted root server responds to the change request of the top-level trusted server and updates the consensus algorithm through the consensus algorithm. The data stored in all trusted root servers in the federation area;

    The top-level trust server performs a change operation.
12. The method according to claim 9, further comprising: a change process of the trusted root server:

    The process of changing the trusted root server includes:

    The trusted root server proposes a change resolution in the alliance, and after the resolution is passed according to a preset resolution policy, changes its own data, and updates the data stored in all trusted root servers in the alliance area through the consensus algorithm. .
13. The method according to claim 9, further comprising: a query process of the terminal:

    The query process of the terminal includes:

    The terminal sends a query request to the opposite terminal to the authority trust server connected to the terminal;

    The authority trust server sends the query request to the top-level trust server connected to the peer terminal after it has not queried the relevant information of the peer terminal;

    The top-level trust server sends the query request to a trusted root server connected to the top-end trust server after the related information of the opposite terminal is not queried;

    When the trusted root server does not query related information of the opposite terminal, the trusted root server sends the query request to the trusted root server where the opposite terminal is connected, and receives the request through the trusted root server where the opposite terminal is located. The top-level trust server where the peer terminal is located, and the authority trust server where the peer terminal is located query related information of the peer terminal, and query the related information of the peer terminal through the top-level trust. The server and the authority trust server send to the terminal.
14. The method according to claim 9, further comprising: a query process of the terminal:

    The query process of the terminal includes:

    Querying, by the terminal, whether the identification information of the opposite terminal has been cached locally;

    In a case where the terminal queries the identity information of the opposite terminal without being cached locally, the terminal sends a query request to the trusted root server where the opposite terminal is located;

    In the case where the trusted root server where the peer terminal is located obtains the identification information of the peer terminal, the terminal sends the IP address to the top trusted server where the peer terminal connected to the trusted root server where the peer terminal is located The query request;

    In a case where the top-level trust server where the peer terminal is located obtains the identification information of the peer terminal, the terminal sends the identity trust server to the authority trust server where the peer terminal connected to the top-level trust server where the peer terminal is located. The query request;

    In a case where the authority trust server where the opposite terminal is located obtains the identification information of the opposite terminal, the terminal receives the query response information sent by the authority trust server where the opposite terminal is located.
15. The method according to claim 9, further comprising: an authentication process of the terminal;

    The authentication process of the terminal includes:

    The terminal is further configured to send an authentication request for the opposite terminal to the authority trust server connected to the terminal;

    The authority trust server is further configured to send the authentication request to a top-level trust server connected to the peer terminal without querying the authentication information of the peer terminal;

    The top-level trust server is further configured to send the query request to a trusted root server connected to the peer terminal after no authentication information of the peer terminal is queried;

    The trusted root server is further configured to: when the authentication information of the opposite terminal is not queried, send the query request to the trusted root server where the connected opposite terminal is located, and receive the trust via the opposite terminal. The authentication information of the peer terminal obtained by the root server query is sent to the terminal through the top-level trust server and the authority trust server.
16. The method according to claim 9, further comprising: an authentication process of the terminal;

    The authentication process of the terminal includes:

    The terminal is further configured to send an authentication request for the opposite terminal to the authority trust server connected to the terminal;

    The authority trust server is further configured to send the authentication request to a top-level trust server connected to the peer terminal without querying the authentication information of the peer terminal;

    The top-level trust server is further configured to send the query request to a trusted root server connected to the peer terminal after no authentication information of the peer terminal is queried;

    The trusted root server is further configured to: when the authentication information of the opposite terminal is not queried, send the query request to the trusted root server where the connected opposite terminal is located, and receive the trust via the opposite terminal. The root server sequentially queries the authentication information of the opposite terminal through the top-level trust server where the opposite terminal is located and the authority trust server where the opposite terminal is located, and passes the obtained authentication information of the opposite terminal through the query. The top-level trust server and the authority trust server are sent to the terminal.

Images