# US 2016/0366105 A1 · System, Apparatus and Method for Secure Network Bridging Using A Rendezvous Service and Multiple Key Distribution Servers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0366105 A1
- Document ID: US20160366105A1
- Status: Published application
- Kind: A1
- Application number: 14/864,940
- Filed: 2015-09-25
- Published: 2016-12-15
- Earliest claimed: 2015-06-09
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: NED M. SMITH; MATS G. AGERSTAM
- Web page: https://patentgrep.com/patent/US20160366105A1

## CPC

- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)}
- H04L 63/065: {for group communications (cryptographic mechanisms or cryptographic arrangements for key management involving conference or group key H04L9/0833)}
- H04L 67/1063: {Discovery through centralising entities}
- H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W 12/086: using security domains
- H04W 76/14: Direct-mode setup
- H04W 12/61: Time-dependent
- H04W 12/63: Location-dependent; Proximity-dependent
- H04W 88/16: Gateway arrangements
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

In one embodiment, a method includes: receiving, in a rendezvous server (RS), a first registration message (FRM) from a first registrar of a first network domain (FND), the FRM including a first device roster of a plurality of first devices of the FND; receiving, in the RS, a second registration message (SRM) from a second registrar of a second network domain (SND), the SRM including a second device roster of a plurality of second devices of the SND; and generating a first rendezvous point (RP) based at least in part on a plurality of key management server identifiers each associated with a key management server of the FND and SND, the first RP to enable the plurality of key management servers to perform key management exchange to generate at least one group key.

## Claims

### Claim 1

At least one computer readable storage medium comprising instructions that when executed enable a system to:
receive, in a rendezvous server, a first registration message from a first registrar of a first network domain, the first registration message including a first device roster of a plurality of first devices of the first network domain;
receive, in the rendezvous server, a second registration message from a second registrar of a second network domain, the second registration message including a second device roster of a plurality of second devices of the second network domain; and
generate a first rendezvous point based at least in part on a plurality of key management server identifiers each associated with a key management server of the first and second network domains, the first rendezvous point to enable the plurality of key management servers to perform key management exchange to generate at least one group key for communication between at least some of the first devices of the first network domain and at least some of the second devices of the second network domain.

### Claim 2 (depends on 1)

The at least one computer readable storage medium of claim 1, further comprising instructions that when executed enable the system to generate a second rendezvous point based at least in part on a plurality of gateway server identifiers each associated with a gateway server of the first and second network domains, the second rendezvous point to enable publication of an encrypted message to a subscriber list including one or more of the plurality of first devices and one or more of the plurality of second devices.

### Claim 3 (depends on 2)

The at least one computer readable storage medium of claim 2, further comprising instructions that when executed enable the system to:
receive, in the gateway server of the first domain, the at least one group key and the encrypted message from one or more of the plurality of first devices; and
decrypt, in the gateway server of the first domain, the encrypted message.

### Claim 4 (depends on 2)

The at least one computer readable storage medium of claim 2, further comprising instructions that when executed enable the system to form a roster that includes the first device roster, the second device roster, the plurality of key management server identifiers, and the plurality of gateway server identifiers.

### Claim 5 (depends on 4)

The at least one computer readable storage medium of claim 4, further comprising instructions that when executed enable the system to:
receive, in the rendezvous server, a request for the at least one group key from one of the plurality of key management servers that is: (a) associated with the second network domain, and (b) has a key management server identifier included in the roster; and
receive, in the rendezvous server, a reply to the request from one of the plurality of key management servers that is: (a) associated with the first network domain, and (b) has another key management server identifier included in the roster;
wherein the reply includes the at least one group key.

### Claim 6 (depends on 2)

The at least one computer readable storage medium of claim 2, further comprising instructions that when executed enable the system to receive, in the rendezvous server at the second rendezvous point, (a) the encrypted message from one or more of the plurality of second devices via the gateway server of the second network domain, and (b) another encrypted message from one or more of the plurality of first devices without using any gateway server of the first network domain.

### Claim 7 (depends on 6)

The at least one computer readable storage medium of claim 6, further comprising instructions that when executed enable the system to generate the second rendezvous point based at least in part on an identifier associated with the another of the one or more of the plurality of first devices.

### Claim 8 (depends on 6)

The at least one computer readable storage medium of claim 6, further comprising instructions that when executed enable the system to send, from the rendezvous server at the first rendezvous point, the at least one group key to one or more of the plurality of second devices via one of the plurality of key management servers associated with the second network domain.

### Claim 9 (depends on 2)

The at least one computer readable storage medium of claim 2, further comprising instructions that when executed enable the system to receive, in the rendezvous server, the at least one group key from one of the plurality of key management servers associated with the first network domain.

### Claim 10 (depends on 9)

The at least one computer readable storage medium of claim 9, further comprising instructions that when executed enable the system to send, from the rendezvous server, the at least one group key to one of the plurality of key management servers associated with the second network domain.

### Claim 11 (depends on 10)

The at least one computer readable storage medium of claim 10, further comprising instructions that when executed enable the system to receive the at least one group key from one of the plurality of key management servers associated with the first network domain while the at least one group key is encrypted with a symmetric key shared between the plurality of key management servers associated with the first and second networks, wherein the rendezvous server does not possess the symmetric key.

### Claim 12 (depends on 11)

The at least one computer readable storage medium of claim 11, further comprising instructions that when executed enable the system to:
receive, in the rendezvous server, the encrypted message from one or more of the plurality of second devices via the gateway server of the second network domain; and
communicate, from the rendezvous server, the encrypted message to one or more of the plurality of first devices;
wherein the encrypted message is encrypted with the at least one group key and the rendezvous server does not possess the at least one group key.

### Claim 13 (depends on 2)

The at least one computer readable storage medium of claim 2, further comprising instructions that when executed enable the system to:
generate the first rendezvous point based at least in part on a hash of the plurality of key management server identifiers; and
generate the second rendezvous point based at least in part on a hash of the plurality of gateway server identifiers.

### Claim 14 (depends on 1)

The at least one computer readable storage medium of claim 1, further comprising instructions that when executed enable the system to:
receive, in the rendezvous server, a request for the at least one group key from one of the plurality of key management servers associated with the second network domain; and
receive, in the rendezvous server, a reply to the request from one of the plurality of key management servers associated with the first network domain;
wherein the reply includes the at least one group key and context indicating the at least one group key corresponds to cross domain device-to-device interactions.

### Claim 15 (depends on 1)

The at least one computer readable storage medium of claim 1, further comprising instructions that when executed enable the system to receive, in the rendezvous server at the second rendezvous point, the encrypted message from one or more of the plurality of second devices; wherein the one or more of the plurality of second devices are constrained.

### Claim 16 (depends on 1)

The at least one computer readable storage medium of claim 1, further comprising instructions that when executed:
receive, in the rendezvous server, a third registration message from a third registrar of a third network domain, the third registration message including a third device roster of a plurality of third devices of the third network domain; and
generate the first rendezvous point based at least in part on a key management server identifier associated with a key management server of the third network domain;
wherein the at least one group key is for communication between (a) at least some of the first and second devices of the first and second network domains, and (b) at least some of the third devices of the third network domain.

### Claim 17 (depends on 16)

The at least one computer readable storage medium of claim 16, further comprising instructions that when executed enable the system to receive the at least one group key from one of the plurality of key management servers associated with the first network domain while the at least one group key is encrypted with a symmetric key shared between the plurality of key management servers associated with the first, second, and third networks, wherein the rendezvous server does not possess the symmetric key.

### Claim 18 (depends on 16)

The at least one computer readable storage medium of claim 16, further comprising instructions that when executed enable the system to:
receive, in the rendezvous server, the encrypted message from one or more of the plurality of second devices via the gateway server of the second network domain; and
communicate, from the rendezvous server, the encrypted message to one or more of the plurality of first devices and one or more of the plurality of third devices;
wherein the encrypted message is encrypted with the at least one group key and the rendezvous server does not possess the at least one group key.

### Claim 19 (depends on 16)

The at least one computer readable storage medium of claim 16, further comprising instructions that when executed enable the system to:
receive the at least one group key from one of the plurality of key management servers associated with the first network domain while the at least one group key is encrypted with a symmetric key shared between the plurality of key management servers associated with the first, second, and third networks;
wherein the rendezvous server does not possess the symmetric key.

### Claim 20 (depends on 16)

The at least one computer readable storage medium of claim 16, further comprising instructions that when executed enable the system to:
receive, in the rendezvous server, a request for the at least one group key from one of the plurality of key management servers associated with the second network domain;
receive, in the rendezvous server, a reply to the request from one of the plurality of key management servers associated with the first network domain;
receive, in the rendezvous server, an additional request for the at least one group key from one of the plurality of key management servers associated with the third network domain;
receive, in the rendezvous server, an additional reply to the additional request from one of the plurality of key management servers associated with the first network domain;
wherein the reply and the additional reply each include the at least one group key.

### Claim 21

At least one computer readable storage medium comprising instructions that when executed enable a system to:
receive, in a rendezvous server, a first registration message including a first device roster corresponding to a first device of a first network domain;
receive, in the rendezvous server, a second registration message including a second device roster corresponding to a second device of a second network domain; and
generate a first rendezvous point based at least in part on key management server identifiers associated with first and second key management servers of the first and second network domains, the first rendezvous point to enable the first and second key management servers to perform key management exchange to generate a key for communication between the first device and the second device.

### Claim 22 (depends on 21)

The at least one computer readable storage medium of claim 21, further comprising instructions that when executed enable the system to generate a second rendezvous point based at least in part on gateway server identifiers associated with first and second gateway servers of the first and second network domains, the second rendezvous point to enable communication of an encrypted message between the first and second devices.

### Claim 23 (depends on 21)

The at least one computer readable storage medium of claim 21, further comprising instructions that when executed enable the system to:
receive, in the rendezvous server, the key from the first key management server while the key is encrypted with a symmetric key shared between the first and second key management servers; and
send, from the rendezvous server, the key to the second key management server;
wherein the rendezvous server does not possess the symmetric key.

### Claim 24

At least one computer readable storage medium comprising instructions that when executed enable a system to:
couple a first key management server of a first network domain to a rendezvous server at a first rendezvous point;
couple the first key management server to the rendezvous server at a second rendezvous point;
receive, in the first key management server, a request for a group key from a first device of the first network domain;
receive, in the first key management server, a reply to the request from the second key management server;
wherein the reply includes the group key;
wherein (a) the first rendezvous point is based on: (a)(i) a first key management server identifier associated with the first key management server, and (a)(ii) a second key management server identifier associated with a second key management server of a second network domain; and (b) the second rendezvous point is based on: (b)(i) a first gateway server identifier associated with a first gateway server of the first network domain, and (b)(ii) a second gateway server identifier associated with a second gateway server of the second network domain;
wherein (c) the first rendezvous point is to enable the first and second key management servers to perform key management exchange to generate a group key for communication between a first device of the first network domain and a second device of the second network domain; and (d) the second rendezvous point is to enable publication of an encrypted message to a subscriber list including devices from the first and second network domains.

### Claim 25 (depends on 24)

The at least one computer readable storage medium of claim 24, further comprising instructions that when executed enable the system to receive, in the first key management server, the group key from second key management server while the group key is encrypted with a symmetric key shared between the first and second key management servers.
