Patent Grant
11546312
The embodiments discussed in the present disclosure are related to dynamic disassociated channel encryption key distribution.
The use of networks is a useful tool in allowing communication between distinct computing devices. Despite the proliferation of computers and networks over which computers communicate, there still remains various limitations to current network technologies.
The subject matter claimed in the present disclosure is not limited to embodiments that solve any disadvantages or that operate only in environments such as those described above. Rather, this background is only provided to illustrate one example technology area where some embodiments described in the present disclosure may be practiced.
One or more embodiments of the present disclosure may include a method that may include determining, by a first network device, a type of control channel to open across a transport in a software-defined network (SDN). The method may also include establishing the control channel with a control device via a control plane that is separate from a data plane. The method may further include advertising first security association parameters to the control device via the control channel. The method may include receiving, from the control device via the control channel, second security association parameters associated with a second network device. The method may also include establishing a data plane connection with the second network device using the second security association parameters.
One or more embodiments of the present disclosure may additionally include systems and/or non-transitory computer readable media for facilitating the performance of such methods.
The object and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims.
It is to be understood that both the foregoing general description and the following detailed description are merely examples and explanatory and are not restrictive of the invention, as claimed.
Example embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Encryption is a cornerstone function of a majority of data exchanges taking place across modern communications networks. Challenges involved in authenticating endpoints, establishing secure control and data paths along with the exchange of encryption keys are significant. One of the many challenges in establishing secure communications channels is to provide the ability for authentication information and encryption keys to be exchanged between endpoints without the exchange being subject to a so called man-in-the-middle attack. A man-in-the-middle attack involves the eavesdropping and potential modification of the exchanged information by a third party such that the third party may intercept the exchanged information. Some conventional technologies that are used to mitigate man-in-the-middle attacks include Diffie-Hellman and Elliptic Curve Digital Signature Algorithm (ECDSA).
Aspect of the present disclosure address these and other shortcomings of conventional approaches to mitigate various security flaws in conventional networks. For example, the present disclosure addresses a challenge of having to provide secure communications across an insecure medium by using a relatively secure and disassociated channel for authentication and encryption key exchanges. The disassociated channel provides the same functionality as the insecure channel from a data and control protocol handling point of view with the added benefit that the implementer of a given network can decide that a communications channel be used that provides a certain trust level, reducing the likelihood of a man-in-the-middle attack. Since most any private communications network (e.g. an MPLS, Leased Line TDM or private Frame/ATM network) typically may provide a better level of security and integrity than the open Internet, the present disclosure may significantly improve the security of any exchange of encryption and authentication information by using the private network as a disassociated channel for the Internet. Since hardly any network can be deemed to be absolutely secure, a given set of authentication and secure exchange functions may still be used without relaxing any requirements.
The present disclosure provides a protocol that has the ability to identify a specific path that it is carrying information about, specifically local communications path information of the originator of a given protocol advertisement and associated messages. The present disclosure may also provide an out-of-band mechanism to gather information about local communications paths that is to be advertised across a channel disassociated from those aforementioned paths of communication. The present disclosure may further provide a protocol that carries all the information required to establish encrypted communications channels across paths where the protocol is not specifically operational, i.e. disassociated paths. The present disclosure may also provide an ability within the aforementioned protocol to uniquely identify each advertised local path and the shared or unique encryption parameters associated with each local path. The present disclosure may further provide an ability for a local encryption endpoint to establish encrypted communications across paths that may or may not be subject to Network Address Translation (NAT, IETF RFC2663) while managing those paths as disassociated from the control channel path. Another benefit of the present disclosure may include the use of a control protocol different from the protocol running on the disassociated channel or path, for the purpose of discovering potential Network Address Translation conditions for other local paths.
In at least some embodiments, a system may include a network that uses a private network and a public Internet for interconnecting sites, where the private network and/or the Internet can be used in either a primary or backup capacity as suitable for site-to-site connectivity or specific applications making use of different communication path profiles. Communication across both networks may be secured and may be encrypted. An example deployment may engage both a control plane protocol and a data plane protocol in an identical (or close to identical) fashion for both networks, where the parameters specific to both networks may be exchanged over each individual network.
Embodiments of the present disclosure may provide improvements to computer networks and to the operation of computers themselves. For example, using one or more embodiments of the present disclosure, network traffic may be more secure and less vulnerable to sniffing and man-in-the-middle attacks. Embodiments of the present disclosure are explained with reference to the accompanying drawings.
For ease and clarity in explanation, some examples of the present disclosure are described with respect to a WAN where the network is managed at least partially by software rather than controlled by hardware. As such, the SDN may support multiple types of connections or communication links, such as the Internet, MultiProtocol Label Switching (MPLS) connections, and/or cellular connections (such as Long Term Evolution (LTE), LTE Advanced, Worldwide Interoperability for Microwave Access (WiMAX), Evolved High Speed Packet Access (HSPA+), and/or others). Additionally, the SDN may support load balancing or load sharing between the various connections. Further, because of the distributed nature of some networks, the SDN may support virtual private networks (VPNs), firewalls, and other security services. In an SD-WAN, for example, a control plane may be functionally separated from the physical topology. In some embodiments, the SDN may separate the control plane of the network (to be managed via software) from a data plane of the network (operating on the hardware of the network). As used herein, the term control plane may refer to communications and connections used in the control and administration of a network itself, rather than the transmission of data through the network, which may occur at the data plane. As used herein, the term data plane may refer to communications and connections used in the transmission and reception of data through the network. For example, the control plane may include administrative traffic directed to a network device within a network, while the data plane may include traffic that passes through network devices within the network.
In some embodiments, the control device 120 may be configured to manage the control plane of an internal network domain 105 by directing one or more aspects of the operation of the edge network devices 110. For example, the control device 120 may generate and/or distribute policies to one or more of the edge network devices 110. A policy may include a rule or set of rules bearing on the handling of network traffic, such as routing, priority, media, etc. The internal network domain 105 may operate as a secured and controlled domain with specific functionality and/or protocols. In some embodiments, the edge network devices 110 may operate based on one or more policies created and/or propagated by the control device 120. In these and other embodiments, the edge network devices 110 may route data traffic within the internal network domain 105 based on the policies created and/or propagated by the control device 120.
In some embodiments, the control device 120 may form a control plane connection with each of the edge network devices 110. The control plane connection may facilitate the exchange of data between the edge network devices 110 and the control device 120 for management and control of the internal network domain 105. The control plane connection may operate via a tunnel through the communication network 130, such as a Datagram Transport Layer Security (DTLS) tunnel. In some embodiments, data transmitted over the control plane connection may facilitate the control device 120 determining topology of the communication network 130. For example, the control device 120 may communicate with the edge network devices 110 to determine what physical connections exist between and among the edge network devices 110 in the communication network 130. Additionally or alternatively, data transmitted over the control plane connection may facilitate the control device 120 determining available, optimal or desired paths across the communication network 130 between and among the edge network devices 110. Additionally or alternatively, data transmitted over the control plane connection may facilitate the edge network devices 110 determining available, optimal or desired paths across the communication network 130 between and among the edge network devices 110. Additionally or alternatively, the control device 120 may communicate route information to the edge network devices 110 over the control plane connection. In these and other embodiments, the control plane connection may include a permanent connection between the control device 120 and the edge network devices 110 such that if the connection between the control device 120 and a given edge network device 110 is broken, the edge network device 110 may be unable or otherwise disallowed from communicating over the internal network domain 105.
In some embodiments, the control device 120 may maintain a central route table that stores route information within the internal network domain 105. For example, the control device 120 may communicate with various edge network devices 110 to determine the physical and/or logical connections available to the edge network devices 110 through the communication network 130. In some embodiments, the edge network devices 110 may include one or more physical and/or logical connections to each other. In these and other embodiments, the control device 120 may generate and/or update one or more policies in conjunction with the central route table to help the edge network devices 110 to determine data traffic routes through the internal network domain 105. For example, the control device 120 may provide policies and other configuration preferences related to traffic flows to the edge network devices 110 rather than being involved with every individual flow through the internal network domain 105.
In these and other embodiments, the edge network devices 110 may not have stored the topology and/or route paths of the entire system 100. Each of the edge network devices 110 may not need to query each other individually to determine reachability. Instead, the control device 120 may provide such information to the edge network devices 110. In these and other embodiments, the edge network devices 110 may route traffic through a most direct route, a most cost effective route, a most reliable route, or through some other route based on one or more other policies received from of the control device 120, characteristics of the traffic, characteristics of the route path, a source edge network device 110, and a destination (e.g., edge network device 110).
In some embodiments, the one or more policies may include guidance regarding determining next-hop and route path instructions. For example, a particular policy may instruct a particular edge network device 110 where to route the traffic next for a particular category, class, or group of traffic flows, rather than providing a complete end-to-end route for the traffic. For example, the edge network device 110a may receive data from an external network device 140a directed to an address of the external network device 141c. The edge network device 110a may have stored a first policy that the network device 110a may use to determine the route path for the data, including that a “next-hop” for network traffic destined for the address of the external network device 141c is to be routed to the edge network device 110d.
In some embodiments, the control device 120 may generate policies to cause certain network traffic flows within the internal network domain 105 to be routed over certain types of connections or communication links (e.g., LTE, Internet, MPLS) and/or through certain edge network devices 110. In some embodiments, a link classification may indicate a type of communication link. The edge network devices 110 may make routing decisions in fast path (e.g., as a packet is travelling through the network). The edge network devices 110 may use a policy to determine an action. For example, for a given set of data, the policy may indicate that a first routing path may be selected based on a configuration preference and based on a type or classification of a communication link. The edge network devices 110 may also determine an action (e.g., determine a route path) for all packets from a particular source, all packets that originated from a particular computer laptop, a type of traffic (e.g., voice), etc. In another example, a policy have a configuration preference that may indicate that all flows with IP addresses in the range 100.1/16 may be categorized as voice flows. When the edge network devices 110 is connected to three different communication links (e.g., an Internet link an MPLS link, a cellular link). The configuration preference may indicate that voice traffic is to be routed over the Internet link. Thus, the edge network devices 110 may route all flows with IP addresses in the range 100.1/16 over the Internet link. Other examples of configuration preferences may include costs (e.g., monetary, time, route, hops, transport health (such as loss, latency, and/or jitter), bandwidth, path geography, source (e.g., device, geography, user), destination (e.g., device, geography, user), applications (e.g., business, social), user groups (e.g., finance on a first subnet IP, HR on a second subnet IP, engineering on a third subnet IP, among others. Any type of data or information may be used as a configuration preference. In an example, the edge network device 110 may identify metadata associated with the traffic, such as a header. The header may include a DSCP value in the header to indicate a predefined routing path. The edge network device 110 may also make routing decisions based on a specific application (which may sometimes be referred to as a layer 7 header or http header). For example, the edge network device 110 may route OFFICE365 traffic on a first path and SALESFORCE traffic on a second path.
In some embodiments, the control device 120 may facilitate authentication of an edge network device 110. The control device 120 may also facilitate the configuration of the data plane. In at least some embodiments, to setup the data plane, the edge network device 110 may generate a set of security association parameters for the edge network device 110. The security association parameters may include information that other edge network devices may use to authenticate with and/or connect to the edge network device 110. For example, the security association parameters may include one or more keys, certificates, etc. The edge network device 110 may send the security association parameters to the control device 120. The control device 120 may send the security association parameters to other edge network devices that are allowed to connect to the edge network device 110. Further details of the control device 120 being use to facilitate the configuration of the control plane and the data plane are described in conjunction with
In some embodiments, traffic among the edge network devices 110 and traffic between the edge network devices 110 and the control device 120 may be encrypted, such as with two-way authentication using Advanced Encryption Standard (AES) with a 256-bit length key over one or more Datagram Transport Layer Security (DTLS) and/or Transport Layer Security (TLS) connections between edge network devices 110.
In some embodiments, the control device 120 may store authentication information for one or more (or all) of the edge network devices 110 within the internal network domain 105. In these and other embodiments, a device may be prevented from communicating within the internal network domain 105 unless the device has authentication information that matches or otherwise corresponds to the stored authentication information of the control device 120. In some embodiments, the authentication information may be used when the edge network devices 110 first comes on line to establish the control plane connection, and any device without a control plane connection with the control device 120 may be prevented from communicating within the internal network domain 105.
The edge network devices 110 may operate at a boundary of the internal network domain 105. The edge network devices 110 may include one or more physical and/or logical connections that may operate within the internal network domain 105. Such connections may be illustrated as part of the communication network 130. Additionally or alternatively, the edge network devices 110 may include one or more physical and/or logical connections operating outside of the internal network domain 105. For example, the edge network devices 110 may be connected to the external network device(s) 140 and/or 141.
In some embodiments, the edge network devices 110 may operate to route traffic from associated external network devices 140 and 141 into the internal network domain 105. Additionally or alternatively, the edge network devices 110 may operate to route traffic from the internal network domain 105 to the associated external network devices 140 and 141. In some embodiments, the edge network devices 110 may communicate with associated external network devices 140 and 141 using typical communication protocols, such as Open Shortest Path First (OSPF), Border Gateway Protocol (BGP), Virtual Router Redundancy Protocol (VRRP), Bi-directional Forwarding Detection (BFD), among others. Additionally or alternatively, the edge network devices 110 may support other network functionalities such as differentiated services code point (DSCP) tagging or type of service (TOS) tagging, Quality of Service (QoS) monitoring, Service Level Agreements (SLA), Internet Protocol (IP) forwarding, Internet Protocol Security (IPsec), Access Control Lists (ACL), among others.
For example, with DSCP or TOS tagging, the edge network devices 110 may be configured to insert a DSCP or TOS tag into a packet header. Such a DSCP or TOS tag may identify one (or a preferences for one) communication link of multiple communication links on which to send certain types of network traffic. Based on the DSCP or TOS tag, the edge network devices 110 may route the network traffic via one or more types of communication link.
As an additional example, with IPsec, the edge network devices 110 may use IPsec to authenticate and/or encrypt network traffic. For example, a given edge network device 110 may authenticate one or more computing devices to communicate with the given edge network device 110 and/or encrypt one or more packets communicated between the computing device and the given edge network device 110.
As another example, with ACLs, the edge network devices 110 may include a set of rules indicative of one or more addresses, hosts, and/or networks that may be permitted to use a given port or a particular communication link. In these and other embodiments, the edge network devices 110 may include ACLs that are applicable to inbound traffic, outbound traffic, or both.
In some embodiments, the edge network devices 110 may locally maintain one or more route tables. In some embodiments, the edge network devices 110 may adjust or modify the route tables based on one or more policies sent from the control device 120. For example, one or more entries may be removed, discarded, or otherwise not added to the route tables by the edge network devices 110 based on the one or more policies. In some embodiments, the edge network devices 110 may include logic to update, modify, and/or generate the route tables based on policies from the control device 120 and/or from traffic handled by the edge network devices 110. The one or more route tables may be automatically populated by the edge network devices 110 based on direct interface routes, static routes, and/or dynamic routes learned using one or more network protocols such as BGP and/or OSPF. In some embodiments, routing decisions for data outside of the internal network domain 105 may be performed by a particular edge network device 110 without specific direction, input, or control from the control device 120. For example, the particular edge network device 110 may compute a routing decision based on the one or more policies that the particular edge network device 110 has received from the control device 120.
In some embodiments, one or more of the edge network devices 110 and/or the control device 120 may be implemented as one or more virtual machines operating on one or more physical computing devices. Additionally or alternatively, the edge network devices 110 and/or the control device 120 may each include an individual stand-alone computing device.
Modifications, additions, or omissions may be made to
The system 200 may include an internal network domain 205 in and between the edge network devices 210, in a similar or comparable manner to that described with respect to the system 100 of
In some embodiments, the system 200 may include one or more external resources 280 (such as the external resources 280a-280c). The external resources 280 may be operated by the same entity or organization that operates the internal network domain 205, or may be operated by a different entity. In these and other embodiments, the system 200 may include an edge network device 210 that may be associated with a particular external resource 280. For example, the system 200 may include an edge network device 210 located within a regional co-location facility. A regional co-location facility may include a location with directed or guaranteed access to the Internet or other communication protocols at a given physical location. In some embodiments, a regional co-location facility may include a prioritized or improved connection to one or more of the external resources 280. In some embodiments, the regional co-location facility may be at a designated geographical location that may be physically proximate one or more of the external network domains. For example, the data center 240 may be located in New York, and the branch 260 may be located in Dallas Tex., and the edge network device 210n may be in a regional co-location facility in Houston, Tex.
The external resources 280 may include any computing service available for consumption by the system 200. For example, the external resources 280 may include a cloud-based service such as a software subscription or software as a service (SaaS) (such as Microsoft Office 365®, Azure®, Google Apps®, Workforce®, Amazon Web Services®, WorkDay®, DocuSign®, GoToMeeting®, WebEx®, QuickBooks®, and/or others), media services (such as YouTube®, NetFlix®, Pandora®, Spotify®, and/or others), and/or others. In these and other embodiments, the external resources 280 may include a third party network to facilitate access to the external resource 280 with one or more access points at various geographical locations. For example, a SaaS may include an access server in Austin, Tex.; Palo Alto, Calif.; and New York, N.Y. for accessing the third party network.
In some embodiments, the system 200 may be geographically distributed. For example, the data center 240 may be located in St. Paul, Minn.; the campus 250 may be located in Des Moines, Iowa; there may be branches 260 in Seattle, Wash.; Los Angeles, Calif.; Atlanta, Ga.; and Orlando, Fla.; and there may be remote sites 270 in London, England; Berlin, Germany; and Seoul, Korea. In these and other embodiments, the system 200 may use the communication networks 230 and the internal network domain 205 to facilitate communication between all of these distributed physical locations as a single network.
In some embodiments, one or more of the external network domains may use one or more applications with resources in the data center 240, such as Microsoft Exchange®, SharePoint®, Oracle e-Business Suite®, and/or others. For example, a workstation operating at the campus 250 may operate Microsoft Exchange®. The operation of the application may include a data flow that goes from the workstation to the edge network device 210e in the external network domain of the campus 250. The data flow may go from the edge network device 210e to one of the edge network devices 210b, 210c, and/or 210d associated with the data center 240 through the internal network domain 205. The one of the edge network devices 210b, 210c, and/or 210d may route the traffic to the Microsoft Exchange® server in the external network domain of the data center 240. Additionally or alternatively, the operation of the application may include a data flow in the reverse order of data flowing from the Microsoft Exchange® server to the workstation.
In some embodiments, the system 200 may include a network management device 290 that may communicate with the control devices 220 over a management network 232. The network management device 290 may provide management and control of one or more devices associated with the internal network domain 205, including the edge network devices 210, the control devices 220, and/or others. For example, the network management device 290 may provide a graphical user interface (GUI) that provides a network administrator with access to control or observe operation of the internal network domain 205. In some embodiments, the network administrator may input policies via the network management device 290 that may be communicated to the control devices 220 for implementation via the edge network devices 210. In some embodiments, the network management device 290 may provide a GUI dashboard with a visual and/or textual description of one or more properties of the internal network domain 205, such as a number and/or status and/or health of edge network devices 210, a number and/or status of control devices 220, a number of and/or last time of reboot, transport health (such as loss, latency, and/or jitter), a number of sites that are operating or not operating, application consumption of network resources, application routing, and/or others.
In some embodiments, the network management device 290 may be configured to authenticate and/or recognize approved edge network devices 210 and/or control device 220. For example, the network management device 290 may maintain a list of serial numbers, MAC addresses, or security association parameters, other uniquely identifying information for the edge network devices 210 and/or the control devices 220. In these and other embodiments, communication in the internal network domain 205 may be restricted to edge network devices 210 and/or control devices 220 with identifying information on the list maintained by the network management device 290.
In some embodiments, the network management device 290 may be configured to generate and/or store configurations of one or more edge network devices 210 and/or control devices 220. For example, a network administrator may use the network management device 290 to configure a particular edge network device 210 and may store that configuration as a template that may be applied to future edge network devices. Additionally or alternatively, a template for the edge network devices 210 may be provided by a third party and applied to a new edge network device 210. In these and other embodiments, a template for the control devices 220 may be generated, stored, and/or applied to a new control device 220. Additionally or alternatively, such a template may be used to automatically configure a newly deployed edge network device 210. For example, the newly deployed edge network device 210 may be brought online and connected to a corresponding control device 220. The corresponding control device 220 may verify the serial number of the edge network device 210 with the network management device 290, and may obtain a template from the network management device 290 for the edge network device 210. The control device 220 may send the template to the edge network device 210 to be automatically installed to configure the edge network device 210 according to the template.
In some embodiments, the network management device 290 may be implemented as a physical device or a virtualized machine. In these and other embodiments, the network management device 290 may be physically located proximate a centralized location, such as within the data center 240 or at the campus 250.
Modifications, additions, or omissions may be made to
The control device 320 may support the control plane 305 between the edge network devices 310. The control device 320 may receive and advertise routing and encryption information between the edge network devices 310. The edge network devices 310 may not establish control plane channels between each other, but may establish a data plane connection between each other, as further described in conjunction with
In at least some embodiments, the system 300 may include a network management device 390 that may communicate with the control devices 220 over a management network 232. The network management device 290 may provide management and control of one or more devices via a passive portion of the control plane 315, including the edge network devices 310, the control devices 320, and/or others. Devices may connect to and communicate with the network management device 390 via the passive portion of the control plane 315. The network management device 390 may be similar or comparable to the network management device 290 of
In at least some embodiments, the network management device 390 may be responsible for assisting with the discovery of network address translation (NAT) traversal information for each connecting endpoint (e.g., edge network devices 310, the control devices 320, and/or others). The network management device 390 may also provide location and session information for the control device 320 and may share the session information with the edge network devices 310 and/or other control devices (not illustrated in
In at least some embodiments, the edge network device 310 may receive one or more keys associated with other edge network devices 310 from the control device 310 via the control plane 305. For example, one or more data packets may use one or more keys for security purposes in transmitting data from one edge network device 310 to another edge network device 310. In these and other embodiments, the control device 320 may reflect the received keys to one or more other edge network devices 310 based on a central route table and/or the policies implemented by the control device 320. In these and other embodiments, a given edge network device 310 may generate symmetrical keys to facilitate establishment of a data plane (e.g., data plane 405 of
Modifications, additions, or omissions may be made to
The control plane 305 may be implemented in the private network 365 and may use active signaling. The data plane 405 may be independent and separate from the control plane and may be implemented in the public network 370. The control plane 305 may provide a disassociated path function relative to the data plane 405. For purposes of example, the system 300 includes the private network 365 and the public network 370, although both networks could be the same type, such as both being private or both being public.
For paths that use the private network 365, each edge network device 310 may authenticate with the network management device 390 (if the network management device is part of the system 400) and then with the control device 320. Encryption keys are advertised by the edge network device 310 to the control device 320. The control device may then advertise endpoint information (e.g., security association parameters), inclusive of encryption keys, to each edge network device 310 for all other edge network devices 310 except for the target for the advertisement. The edge network device 310 may actively establish the data plane 405, including establishing encryption along the data plane 405, with all other endpoints attached to the private network 365 based on the information received from the control device 320.
For paths that use the public network 370, each edge network device 310 may authenticate with the network management device 390, which may provide the edge network devices 310 with potential NAT traversal information. Encryption keys for the Internet path may be advertised by the edge network devices 310 to the control device 320. The control device 320 may advertise this additional endpoint information, inclusive of encryption keys, to each endpoint for all other endpoints except the target edge device 310 for the advertisement. Each edge network device 310 is now in a position to also establish the encrypted data plane 405 across the public (e.g., Internet) paths, without having sent information related to the encryption across that same path.
Modifications, additions, or omissions may be made to
The method 500 may begin at block 505, where the processing logic may determine a type of control channel to open across a transport in a software-defined network (SDN). The processing logic may locally discover the type of the control channel by identifying one or more transports that are communicatively coupled to the processing logic and/or to a respective edge network device. The type of transport may influence the type of control channel. The processing logic may also determine how many control channels to open across each transport. In at least some embodiments, the processing logic may establish one control channel across each transport. In at least some embodiments, the processing logic may establish multiple control channels across one or more transports. In at least some embodiments, the processing logic may establish a particular number of control channels based on the transport type. For example, a transport type with higher security and/or bandwidth may have more control channels as compared to other transport types.
At block 510, the processing logic may establishing the control channel with a control device via a control plane that is separate from a data plane. In at least some embodiments, the processing logic may establish the types and numbers of control channels as determined at block 505. The control channels may include secure control channels. The processing logic may also establish one or more control channels with one or more network management devices, such as the network management device 290 or 390 of
At block 515, the processing logic may determine a potential network address translation (NAT) for an upstream path toward the control device and/or toward the network management device. In at least some embodiments, the processing logic may determine the NAT for a public network. The processing logic may trace one or more paths to the control device and/or the network management device, while noting any NAT that may occur along the path. The processing device may store the NAT in a data storage.
At block 520, the processing logic may advertise first security association parameters to the control device via the control channel. In at least some embodiments, the processing logic may generate the first security association parameters. The first security association parameters may be associated with a first edge network device. The processing logic may authenticate with the control device using an authentication protocol. In at least some embodiments, the processing logic may authenticate with a network management device prior to authenticating with the control device. The first security association parameters may include a key, a key pair, a set of keys, a certificate, a token, or any other object that may be used by another device to identify, authenticate with, and connect to the first edge network device via a channel other than the control channel. The control device may receive the first security association parameters and may receive other security association parameters from other devices. The control device may send some, any or all of the received security association parameters to permitted device, as further described in conjunction with
At block 525, the processing logic may receive, from the control device via a control channel, second security association parameters associated with a second network device. At block 530, the processing logic may establish a data plane connection with the second network device using the second security association parameters
One skilled in the art will appreciate that, for these processes, operations, and methods, the functions and/or operations performed may be implemented in differing order. Furthermore, the outlined functions and operations are only provided as examples, and some of the functions and operations may be optional, combined into fewer functions and operations, or expanded into additional functions and operations without detracting from the essence of the disclosed embodiments.
The method 600 may begin at block 605, where the processing logic may receive, via a first control channel associated with a control plane, first security association parameters from a first network device. Similarly, at block 610, the processing logic may receive, via a second control channel associated with the control plane, second security association parameters from a second network device. The processing logic may receive any number of security association parameters from any number of network devices.
At block 615, the processing logic may determine that the first network device and the second network device are associate with each other. For example, the processing logic may determine that the first network device and the second network device are associated with a single entity (e.g., corporation) and are thus permitted to connect to each other via a data plane.
At block 620, the processing logic may send the first security association parameters to the second network device. Similarly, at block 625, the processing logic may end the second security association parameters to the first network device. Using the exchange of security association parameters that were shared via the control plane (and not a data plane), the first network device and the second network device may establish the data plane between each other.
One skilled in the art will appreciate that, for these processes, operations, and methods, the functions and/or operations performed may be implemented in differing order. Further, the outlined functions and operations are only provided as examples, and some of the functions and operations may be optional, combined into fewer functions and operations, or expanded into additional functions and operations without detracting from the essence of the disclosed embodiments.
For ease in explanation, the processing logic may be associated with an edge network device with two transport connections—one to a private network, and one to a public network (e.g., the Internet). Under method 700, a list of transport connections may be generated and later used to establishment of data plane sessions with various devices, as described below. The data plane sessions may be established serially, or at least partially in parallel.
The method 700 may begin at block 705, where the processing logic may determine whether a management device is configured for a particular transport. When a management device is not configured for a particular transport (e.g., “NO”) at block 705, the processing logic may determine whether any additional transports are available at block 710. When any additional transports are available at block 710 (e.g., “YES”) at block 710, the processing logic may configure the management device with the other transports and advance to block 705.
When a management device is configured for a particular transport (e.g., “YES”) at block 705, the processing logic may establish a connection with the management device and may begin to gather network address translation (NAT) information at block 715. At block 720, the processing logic may determine whether a control device is present with a network. When a control device is present with the network (e.g., “YES”) at block 720, the processing logic may establish a control plane session with the control device at block 725. The processing logic may proceed to block 710.
When a control device is not present with the network (e.g., “NO”) at block 705, the processing logic may determine whether additional transports are available at block 710. When any additional transports are not available at block 710 (e.g., “NO”) at block 710, the processing logic may determine whether a control session has been established for all transports at block 730.
When a control session has been established for all transports (e.g., “YES”) at block 730, the processing logic may establish a data plane connection with other authorized edge network devices. When a control session has not been established for all transports (e.g., “NO”) at block 730, the processing logic may wait for additional transports to become available at block 740.
One skilled in the art will appreciate that, for these processes, operations, and methods, the functions and/or operations performed may be implemented in differing order. Furthermore, the outlined functions and operations are only provided as examples, and some of the functions and operations may be optional, combined into fewer functions and operations, or expanded into additional functions and operations without detracting from the essence of the disclosed embodiments.
Generally, the processor 810 may include any suitable special-purpose or general-purpose computer, computing entity, or processing device including various computer hardware or software modules and may be configured to execute instructions stored on any applicable computer-readable storage media. For example, the processor 810 may include a microprocessor, a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a Field-Programmable Gate Array (FPGA), or any other digital or analog circuitry configured to interpret and/or to execute program instructions and/or to process data.
Although illustrated as a single processor in
After the program instructions are loaded into the memory 820, the processor 810 may execute the program instructions, such as instructions to perform the methods 500, 600, and/or 700
The memory 820 and the data storage 830 may include computer-readable storage media or one or more computer-readable storage mediums for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable storage media may be any available media that may be accessed by a general-purpose or special-purpose computer, such as the processor 810. In some embodiments, the computing system 800 may or may not include either of the memory 820 and the data storage 830.
By way of example, and not limitation, such computer-readable storage media may include non-transitory computer-readable storage media including Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory devices (e.g., solid state memory devices), or any other storage medium which may be used to carry or store desired program code in the form of computer-executable instructions or data structures and which may be accessed by a general-purpose or special-purpose computer. Combinations of the above may also be included within the scope of computer-readable storage media. Computer-executable instructions may include, for example, instructions and data configured to cause the processor 810 to perform a certain operation or group of operations.
The communication unit 840 may include any component, device, system, or combination thereof that is configured to transmit or receive information over a network, such as an MPLS connection, the Internet, a cellular network (e.g., an LTE network), etc. In some embodiments, the communication unit 840 may communicate with other devices at other locations, the same location, or even other components within the same system. For example, the communication unit 840 may include a modem, a network card (wireless or wired), an optical communication device, an infrared communication device, a wireless communication device (such as an antenna), a chipset (such as a Bluetooth device, an 802.6 device (e.g., Metropolitan Area Network (MAN)), a WiFi device, a WiMax device, cellular communication facilities, or others), and/or the like, or any combinations thereof. The communication unit 840 may permit data to be exchanged with a network and/or any other devices or systems described in the present disclosure. For example, the communication unit 840 may allow the system 800 to communicate with other systems, such as network devices, control devices, and/or other networks.
Modifications, additions, or omissions may be made to the system 800 without departing from the scope of the present disclosure. For example, the data storage 830 may be multiple different storage mediums located in multiple locations and accessed by the processor 810 through a network.
As indicated above, the embodiments described in the present disclosure may include the use of a special purpose or general purpose computer (e.g., the processor 810 of
As used in the present disclosure, the terms “module” or “component” may refer to specific hardware implementations configured to perform the actions of the module or component and/or software objects or software routines that may be stored on and/or executed by general purpose hardware (e.g., computer-readable media, processing devices, or some other hardware) of the computing system. In some embodiments, the different components, modules, engines, and services described in the present disclosure may be implemented as objects or processes that execute on the computing system (e.g., as separate threads). While some of the systems and methods described in the present disclosure are generally described as being implemented in software (stored on and/or executed by general purpose hardware), specific hardware implementations or a combination of software and specific hardware implementations are also possible and contemplated. In this description, a “computing entity” may be any computing system as previously defined in the present disclosure, or any module or combination of modulates running on a computing system.
In accordance with common practice, the various features illustrated in the drawings may not be drawn to scale. The illustrations presented in the present disclosure are not meant to be actual views of any particular apparatus (e.g., device, system, etc.) or method, but are merely idealized representations that are employed to describe various embodiments of the disclosure. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may be simplified for clarity. Thus, the drawings may not depict all of the components of a given apparatus (e.g., device) or all operations of a particular method.
Terms used in the present disclosure and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including, but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes, but is not limited to,” among others).
Additionally, if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations.
In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” or “one or more of A, B, and C, etc.” is used, in general such a construction is intended to include A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B, and C together, etc.
Further, any disjunctive word or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” should be understood to include the possibilities of “A” or “B” or “A and B.”
However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to embodiments containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations.
Additionally, the use of the terms “first,” “second,” “third,” etc., are not necessarily used herein to connote a specific order or number of elements. Generally, the terms “first,” “second,” “third,” etc., are used to distinguish between different elements as generic identifiers. Absence a showing that the terms “first,” “second,” “third,” etc., connote a specific order, these terms should not be understood to connote a specific order. Furthermore, absence a showing that the terms “first,” “second,” “third,” etc., connote a specific number of elements, these terms should not be understood to connote a specific number of elements. For example, a first widget may be described as having a first side and a second widget may be described as having a second side. The use of the term “second side” with respect to the second widget may be to distinguish such side of the second widget from the “first side” of the first widget and not to connote that the second widget has two sides.
All examples and conditional language recited in the present disclosure are intended for pedagogical objects to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Although embodiments of the present disclosure have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the present disclosure.
This application is a continuation and claims the benefit of U.S. Non-Provisional patent application Ser. No. 16/021,281, filed Jun. 28, 2018, which claims the benefit of U.S. Provisional Patent Application No. 62/539,431, filed Jul. 31, 2017, the full disclosures of which are incorporated herein by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5481613 | Ford et al. | Jan 1996 | A |
| 6611913 | Carroll et al. | Aug 2003 | B1 |
| 7181620 | Hur | Feb 2007 | B1 |
| 7350076 | Young | Mar 2008 | B1 |
| 8582777 | Urivskiy et al. | Nov 2013 | B2 |
| 9100346 | Voit et al. | Aug 2015 | B2 |
| 9954743 | Lee et al. | Apr 2018 | B2 |
| 20030048905 | Gehring et al. | Mar 2003 | A1 |
| 20050114518 | McMahon | May 2005 | A1 |
| 20080115199 | Young et al. | May 2008 | A1 |
| 20090144541 | Kim et al. | Jun 2009 | A1 |
| 20120283992 | Ji | Nov 2012 | A1 |
| 20150058954 | Shah et al. | Feb 2015 | A1 |
| 20160014127 | Mohebbi | Jan 2016 | A1 |
| 20160119299 | Amulothu et al. | Apr 2016 | A1 |
| 20160344471 | Meng et al. | Nov 2016 | A1 |
| 20160366105 | Smith | Dec 2016 | A1 |
| 20180262473 | Viquez Calderon et al. | Sep 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 101697528 | Apr 2010 | CN |
| 104734954 | Jun 2015 | CN |
| 104917750 | Sep 2015 | CN |
| 105052113 | Nov 2015 | CN |
| 108028831 | May 2018 | CN |
| 3662632 | Jun 2020 | EP |
| 2016-528630 | Sep 2016 | JP |
| WO 2016000160 | Jan 2016 | WO |
| WO 2016202269 | Dec 2016 | WO |
| 2017052507 | Mar 2017 | WO |
| Entry |
|---|
| International Search Report and Written Opinion from the International Searching Authority, dated Oct. 8, 2018, 11 pages, for corresponding International Application PCT/US2018/043622. |
| Liyanage, Madhusanka, et al., “Secure communication channel architecture for Software Defined Mobile Networks,” Computer Networks, Elsevier, Amsterdam NL, Jan. 16, 2017, pp. 32-50. |
| First Office Action and Search Report dated Sep. 29, 2021, 13 pages, issued by the China National Intellectual Property Administration for corresponding Chinese Patent Application No. 201880049784.3. |
| Reasons for Refusal with English translation, dated May 14, 2021, 11 pages, issued by the Japan Patent Office for corresponding Japanese Patent Application No. 2020-503029. |
| Number | Date | Country | |
|---|---|---|---|
| 20210006546 A1 | Jan 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62539431 | Jul 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16021281 | Jun 2018 | US |
| Child | 17027424 | US |
