US 10,375,117 B2Granted

Apparatus and method for securely connecting to a remote server

AssigneeQUALCOMM Incorporated

InventorsJeffree Froelicher, Lalitha B. S. Suryanarayana, Giridhar Dhati Mandyam

Life of this patent

Estimating the term…

Loading patent…

Abstract

A method for securely connecting to a remote server that provides improved Internet security. In the method, a client receives a request to connect to a remote server associated with a domain name. The client, when resolving the domain name, determines whether the remote server supports at least one predetermined IP layer security protocol. The client performs a key exchange protocol with the remote server to generate at least one shared secret in response to determining that the remote server supports the at least one predetermined IP layer security protocol. The client connects to the remote server using the at least one shared secret in the IP layer security protocol.

Claims12

Dependent claims

A method for securely connecting to a remote server, comprising:

receiving, by a client, a request to connect to a remote server associated with a domain name;
in response to receiving the request to connect to the remote server associated with the domain name, obtaining a Domain Name System (DNS) resolution from a Domain Name System (DNS) server,
the DNS resolution obtained from the DNS server including an Internal Protocol (IP) address for the remote server,
the DNS resolution obtained from the DNS server further including a service (SRV) record,
the SRV record included in the DNS resolution obtained from the DNS server including at least one parameter indicating that the remote server supports at least one defined IP layer security protocol;
determining, by the client, that the remote server supports the at least one defined IP layer security protocol based on the at least one parameter indicating that the remote server supports the at least one defined IP layer security protocol included in the SRV record included in the DNS resolution obtained from the DNS server;
performing, by the client, a key generation protocol with the remote server to generate at least one shared secret in response to determining that the remote server supports the at least one defined IP layer security protocol;
and
connecting, by the client, to the remote server using a key that is based on the at least one shared secret in the at least one defined IP layer security protocol.

6 more elements

A non-transitory computer-readable medium, comprising:

code for causing a computer to receive a request to connect to a remote server associated with a domain name;
code for causing the computer to, in response to receiving the request to connect to the remote server associated with the domain name, obtain a Domain Name System (DNS) resolution from a Domain Name System (DNS) server,
the DNS resolution obtained from the DNS server including an Internal Protocol (IP) address for the remote server,
the DNS resolution obtained from the DNS server further including a service (SRV) record,
the SRV record included in the DNS resolution obtained from the DNS server including at least one parameter indicating that the remote server supports at least one defined IP layer security protocol;
code for causing the computer to determine that the remote server supports the at least one defined IP layer security protocol when resolving the domain name based on the at least one parameter indicating that the remote server supports the at least one defined IP layer security protocol included in the SRV record included in the DNS resolution obtained from the DNS server;
code for causing the computer to perform a key generation protocol with the remote server to generate at least one shared secret in response to determining that the remote server supports the at least one defined IP layer security protocol;
and
code for causing the computer to connect to the remote server using a key that is based on the at least one shared secret in the at least one defined IP layer security protocol.

6 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/150,122Filed 2 Oct 2018 · continuation
Priority: 24 Feb 2016
Published: US 2019/0036976 A131 Jan 2019
Granted: 6 Aug 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification7 codes

H04L 63/164
Implementing security features at a particular protocol layer: at the network layer
H04L 61/4511
Using standardised directories; using standardised directory access protocols: using domain name system [DNS]
H04L 63/06
Network architectures or network communication protocols for network security: for supporting key management in a packet data network
H04L 63/20
Network architectures or network communication protocols for network security: for managing network security; network security policies in general

Family

Application15/052,736Parent of this continuation · filed 24 Feb 2016
US 2019/0036976 A1Pre-grant publication · published 31 Jan 2019
US 10,091,243 B2Parent of this continuation
US 2017/0244758 A1Published application
US 10,375,117 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key