Source: https://patents.google.com/patent/US9374286B2/en
Timestamp: 2018-08-20 19:25:59
Document Index: 787756084

Matched Legal Cases: ['Application No. 200410088262', 'Application No. 200510008172', 'Application No. 200410088262', 'Application No. 200510008172', 'Application No. 200410088262', 'Application No. 200510008172', 'Application No. 04019631', 'Application No. 04019631', 'Application No. 05100716', 'Application No. 05100716', 'Application No. 05100716', 'Application No. 2004', 'Application No. 2004', 'Application No. 10', 'Application No. 10', 'Application No. 09822462', 'Application No. 09822462', 'Application No. 09822462', 'Application No. 200980142641', 'Application No. 200980142641', 'Application No. 2011', 'Application No. 2011', 'Application No. 05100716', 'Application No. 200980142641', 'Application No. 09822462', 'Application No. 200980142641', 'Application No. 200980142641', 'Application No. 200980142641', 'Application No. 098135996', 'Application No. 200980142641', 'Application No. 2011', 'Application No. 16155024', 'Application No. 200980142641', 'Application No. 098135996', 'Application No. 098135996', 'Application No. 200980142641']

US9374286B2 - Network classification - Google Patents
Network classification Download PDF
US9374286B2
US9374286B2 US14212128 US201414212128A US9374286B2 US 9374286 B2 US9374286 B2 US 9374286B2 US 14212128 US14212128 US 14212128 US 201414212128 A US201414212128 A US 201414212128A US 9374286 B2 US9374286 B2 US 9374286B2
US14212128
US20140280798A1 (en )
Christopher J. Corbett
Mohamed Jawad Khaki
Network DNA may be determined for a computer network that taxonomically classifies the computer network. Network DNA may include derived network DNA components and raw network DNA components. Raw network DNA components may be acquired from local or remote sources. Derived network DNA components may be generated according to derived network DNA component specifications. Derived network DNA component specifications may reference raw network DNA components. Network DNA determined for the computer network may include a network species component capable of indicating network species classifications for computer networks. Network species classifications may include enterprise network, home network and public place network. Network species classifications may be determined as a function of network security, network management and network addressing. One or more network DNA stores may be configured to store network DNA for computer networks. Network DNA stores may store network DNA history as well as current network DNA.
This application is a continuation of U.S. patent application Ser. No. 13/300,743, filed Nov. 21, 2011, entitled “Network Classification,” now U.S. Pat. No. 8,676,969, issued Mar. 18, 2014, which is a continuation of U.S. patent application Ser. No. 10/773,681, filed Feb. 6, 2004, entitled “Network Classification,” now U.S. Pat. No. 8,126,999, issued Feb. 28, 2012. The entirety of these afore-mentioned applications are incorporated herein by reference.
This invention pertains generally to computer networks and, more particularly, to computer network categorization.
Computer networks and computer networking have become widespread. Underlying this spread is an increasing variety of computer network types, components and configurations. As a result, a computer system and/or computer system user attempting to maintain computer network connectivity may be subjected to requests for a bewildering array of network configuration parameters or be provided with numerous network characteristics and required to make connectivity decisions either without sufficient information or lack of understanding of the same. Perhaps worse, connectivity may be lost, not because of technical unavailability but, for example, through the use of the wrong network connectivity procedure. Attempts to resolve connectivity troubles may be hindered by a lack of readily available network status indicators and/or a common vocabulary for communicating with expert help.
Even where network connectivity itself is nominally maintained between computers, applications hosted by networked computers may need to adapt to network changes in order, for example, to avoid performance penalties or to prevent security vulnerabilities. As a result of the vast array of conventional network attributes, few applications are able to take each conventional network attribute into account. Networked application users may find themselves in the position of having overcome network connectivity difficulties only to be frustrated by a networked application that was the motivation for establishing connectivity in the first place, or to unknowingly expose themselves to a security risk.
While the above issues are particularly encountered by mobile computers and mobile computer users, it is common for multiple computer networks to be available to even immobile computers over their lifetime, if not concurrently. For example, many urban locations have at least one wired network connection as well as one or more wireless network options. Where multiple computer networks are available, the decision of which computer network to choose for a particular data packet may be a complex process in which conventional network attributes may not be able to provide the deciding factor.
In an embodiment of the invention, network DNA is determined for a computer network that taxonomically classifies the computer network. Network DNA may include derived network DNA components and raw network DNA components. Raw network DNA components may be acquired from local or remote sources. Each raw network DNA component may correspond to an attribute of the computer network. Derived network DNA components may be generated according to derived network DNA component specifications. Derived network DNA component specifications may reference raw network DNA components.
In an embodiment of the invention, network DNA determined for the computer network includes a network species component. In an embodiment of the invention, the network species component is capable of indicating network species classifications for computer networks. Network species classifications may include enterprise network, home network and public place network. Network species classifications may be determined as a function of network security, network management, network addressing, the network's intended use, and other attributes.
In an embodiment of the invention, one or more computers are connected to one or more computer networks. One or more network DNA stores may be configured to store network DNA for the computer networks. Network DNA stores may store network DNA history as well as current network DNA.
FIG. 4 is a schematic diagram illustrating an example network DNA module architecture in accordance with an embodiment of the invention;
FIG. 5 is a block diagram depicting example network DNA in accordance with an embodiment of the invention;
FIG. 6 is a block diagram depicting an example network DNA policy in accordance with an embodiment of the invention;
FIG. 7 is a schematic diagram illustrating an example network DNA application programming interface in accordance with an embodiment of the invention;
FIG. 8A is a flowchart depicting example steps for acquiring network DNA in accordance with an embodiment of the invention;
FIG. 8B is a flowchart depicting example steps for asynchronously acquiring network DNA in accordance with an embodiment of the invention;
FIG. 9 is a flowchart depicting example steps for generating network DNA in accordance with an embodiment of the invention; and
FIG. 10 is a flowchart depicting example steps for enforcing network DNA policies in accordance with an embodiment of the invention.
The computer 102 preferably also contains communications connections 114 that allow the device to communicate with other devices such as remote computer(s) 116. A communication connection is an example of a communication medium. Communication media typically embody computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. By way of example, and not limitation, the term “communication media” includes wireless media such as acoustic, radio frequency (RF), infrared and other wireless media. The term “computer-readable medium” as used herein includes both computer storage media and communication media.
A computer networking environment suitable for incorporating aspects of the invention may include multiple computer networks. Suitable computer networks may be differentiated by a variety of factors, for example, extent and coverage scope, implementation technology, node management, network security, network connectivity, node addressing schemes, service infrastructure elements, network mobility, network purpose and intended use, network topology and topological location as well as network operational characteristics. Examples of computer network coverage scope designations include personal area network (PAN), local area network (LAN), metropolitan area network (MAN) and wide area network (WAN). Coverage scope of computer networks may be related to computer network physical extent. Computer networks with different physical extents may employ different implementation technologies.
Broadly, implementation technologies may include wireless and wire-line. Suitable wireless technologies may include wireless communications protocols such as wireless communication protocols in compliance with the Institute of Electrical and Electronic Engineers (IEEE) 802.1x series of standards (e.g., Wi-Fi), and wireless communication protocols in compliance with the European Telecommunication Standards Institute (ETSI) Global System for Mobile communications (GSM) series of standards including a general packet radio service (GPRS), an enhanced data GSM environment (EDGE) and a universal mobile telecommunications system (UMTS). Wireless technologies may further include wireless communications protocols in compliance with a code division multiple access (CDMA) series of standards including CDMA 1X and CDMA2000, as well as the Bluetooth (BT) series of standards and the like. Wireless technologies may also include switched multi-megabit data services (SMDS), multi-channel multipoint distribution services (MMDS), local multipoint distribution services (LMDS), ultra-wideband (UWB) wireless, low power wireless sensor networks such as ZigBee™, as well as satellite-based wireless communication technologies.
Suitable wire-line technologies may include Ethernet (e.g., communications protocols in compliance with the IEEE 802.3x series of standards), Token ring (e.g., communications protocols in compliance with the IEEE 802.5x series of standards), as well as dial-up communication protocols such as Serial Line Internet Protocol (SLIP), Point-to-Point Protocol (PPP) and Remote Access Service (RAS). Wire-line technologies may further include integrated services digital network (ISDN), asynchronous transfer mode (ATM) protocols, cable modems in compliance with data communication standards such as a data over cable service interface specification (DOCSIS) as well as digital subscriber line (xDSL) and compatible technologies. Higher layer, e.g., International Standards Organization (ISO) Open System Interconnection (OSI) model layer, communication protocols such as Transmission Control Protocols (TCP) and Internet Protocols (IP) are further examples of suitable computer network implementation technologies.
Nodes (e.g., computers and infrastructure elements) of computer networks may be managed or unmanaged. In an embodiment of the invention, managed nodes do grant authority (e.g., authority to enforce network policy) to computer network administrators of computer networks to which they belong. In an embodiment of the invention, each node of a managed computer network is a managed node. Infrastructure elements of unmanaged computer networks may be managed nodes. In an embodiment of the invention, unmanaged nodes may form an unmanaged computer network (e.g., an ad hoc network) where there is no central administrator to enforce higher reliability and security standards for the network. Secure computer networks may include infrastructure elements such as firewalls, may require encrypted and authenticated communications (e.g., with nodes of other networks), and may engage in active intrusion detection.
Computer networks may have varying levels of network connectivity, for example, full, limited or none. Computer networks with limited network connectivity may limit access within the network as well as to other computer networks. Limited network connectivity may occur by design (e.g., policy and/or filtering), through misconfiguration or because of host/network component failure (e.g., host network adaptor or switch/router failure). Computer networks may incorporate different addressing schemes, for example, internal (private) addressing or external (public) addressing. Computer networks incorporating internal addressing may require infrastructure elements capable of network address translation (NAT) in order to provide connectivity to computer networks incorporating external addressing. Computer networks incorporating internal addressing may benefit from improved security and/or privacy.
Computer networks may incorporate service infrastructure elements or “fixed services” such as domain name services (DNS), proxy services, dynamic host configuration protocol (DHCP) services, network address translation services, firewall services and remote authentication dial-in user services (RADIUS). Some computer networks, for example, ad hoc, mesh or peer-to-peer computer networks, may not incorporate fixed services although they may incorporate distributed analogues, for example, multicast DNS, universal plug and play (UPnP), link local addresses and link local multicast name resolution (LLMNR).
Computer networks may have varying degrees of mobility. Mobile computer networks may have mobile network infrastructure elements such as mobile routers. For example, vehicle LANs may include wireless mobile routers with changing public subnet prefixes that provide network address translation for vehicle LAN nodes with unchanging private network addresses.
Computer networks may have an intended use or access policy. For example, computer networks may be intended for private use or intended for public use. In an embodiment of the invention, computer networks intended for private use have nodes that are owned by an organization that owns the network (or subscribes for its use). Computer networks intended for private use may be managed enabling high levels of trust between nodes. Computer networks intended for public use may provide relatively anonymous service to any customer with the ability to pay, or even free of charge. In an embodiment of the invention, client nodes (e.g., customer nodes) of computer networks intended for public use are unmanaged. Trust between nodes in computer networks intended for public use may be low and varying demand may make technical management difficult, for example, resulting in wide variation in quality of service.
Computer networks may have topological placement or location with respect to other computer networks. For example, computer networks may be transit (core) networks (e.g., internet service providers) that route data traffic to and from other networks, or stub networks that route data traffic within themselves as well as to and from transit networks. Operational attributes and characteristics of computer networks (i.e., network operational attributes) include speed or throughput (e.g., from kilobits per second to gigabits per second), congestion (e.g., low, medium, high or severe), load (e.g., low or underutilized, medium, average or typical, high or near capacity, and critical or at capacity), transmission latency, throughput jitter, packet loss probability, quality of service (QoS) and operational cost (e.g., per byte or per hour).
Computer networks may be premise networks, that is, private networks at particular locations. For example, one or more connected college campus LANs may be a premise network. Computer networks may be proximity networks, that is, networks established by nodes because of their proximity to one another, for example, over one or more shared wireless channels. Proximity networks may be single or multi-hop and may be of an ad hoc nature, established, for example, upon coming into a classroom or deployment area.
FIG. 2 illustrates an example computer networking environment incorporating multiple computer networks. The example computer networking environment 200 includes several computers 202, 204, 206, 208, 210, 212, 214, 216, 218 (e.g., each may be the computer 102 as described above with reference to FIG. 1) communicating with one another over several computer networks 220, 222, 224, 226, 228, each represented by a cloud. Each computer network 220, 222, 224, 226, 228 may include many well-known components, such as routers, gateways, hubs, and may allow the computers 202, 204, 206, 208, 210, 212, 214, 216, 218 to communicate via wired and/or wireless media. When interacting with one another over computer networks 220, 222, 224, 226, 228, one or more of the computers 202, 204, 206, 208, 210, 212, 214, 216, 218 may act as clients, servers or peers with respect to other computers 202, 204, 206, 208, 210, 212, 214, 216, 218. Accordingly, the various embodiments of the invention may be practiced on clients, servers, peers or combinations thereof, even though specific examples contained herein may not refer to all of these types of computers.
The computer 202 is connected to the computer network 220. A resource server 204 is also connected to the computer network 220. For example, the resource server 204 may be a file server, a directory server, a database server, a print server, a collaboration server, a DNS server, a provisioning server such as a DHCP server, an authentication server such as a RADIUS server, or combinations thereof. A Microsoft® Windows® XP server is an example of a resource server.
A network gateway 206 is connected to the computer network 220 and the computer network 222. The network gateway 206 may limit or filter the passage of computer network traffic between the computer network 220 and the computer network 222. For example, the network gateway 206 computer may execute firewall software that enforces a computer network traffic policy, for example a security policy, with regard to computer network traffic arriving at the network gateway 206.
For example, the computer network 220 may be an enterprise network running over an Ethernet LAN and employing an internal addressing scheme. The computers 202, 204 and 206 may each be managed nodes of the computer network 220. The computer network 222 may be a public inter-network such as the Internet. The cloud representing computer network 222 is larger than the clouds representing computer networks 220, 224, 226 and 228 to indicate that the computer network 222 is a transit network for data traffic to and from computer networks 220, 224 and 226. The computer 214 may have a dial-up connection to the computer network 222.
The computer network 224 may be a public wireless network connected to the computer network 222 by a digital telecommunications link (e.g., T1). The computer 208 may be an unmanaged node of the computer network 224 but, for example, the computer network 224 may require the computer 208 to register with the resource server 210 before providing the computer 208 with full connectivity to the network 222. The computer network 226 may be a home LAN able to support a virtual private network (VPN) between the computer 212 and the resource server 204 across the computer network 222, the network gateway 206 and the computer network 220. The computer network 228 may be a wireless computer network instantiated ad hoc by the computers 216 and 218. In this example computer networking environment, the computer network 228 is not connected to the other computer networks 220, 222, 224, 226. However, if, for example, the computer 216 established a connection with the computer network 220 then the computer 216 may be capable of acting as a bridge or network gateway for the computer network 228.
FIG. 3 depicts an example high level systems architecture in accordance with an embodiment of the invention. Application programs 302 may utilize an operating system 304 to interact with computer hardware 306. For example, the computer hardware 306 may include any hardware components of the computer 102 described above with reference to FIG. 1. The operating system 304 may include device drivers 308 and a network DNA module 310. Each component of the computer hardware 306 may be associated with one or more of the device drivers 308. Each of the device drivers 308 may provide one or more software interfaces for interacting with the computer hardware 306.
The network DNA module 310 may dynamically gather network attributes from the computer hardware 306, the operating system 304 and the application programs 302. In an embodiment of the invention, the network DNA module 310 resides on one or more computers. Each computer may be connected to one or more computer networks. The network DNA module 310 may determine network DNA for each connected computer network. Network DNA may taxonomically classify the associated computer network. The network DNA for a particular computer network may change over time but, in an embodiment of the invention, such changes are infrequent. Computer network connections (e.g., communication connections 114 of FIG. 1) need not be active in order for the network DNA module 310 to determine network DNA for associated computer networks. The network DNA module 310 may provide network DNA, for example, upon request, or by publishing network DNA events to interested subscribers.
The network DNA module 310 may be incorporated into or may utilize (e.g., dynamically gather network attributes with) a network application programming interface, for example, the Windows Sockets 2 (Winsock) network application programming interface (API), as detailed in the Windows Sockets 2 section of the February 2003 Microsoft® Windows® Platform Software Development Kit (SDK) documentation in the Microsoft Developer Network (MSDN®) Library. The network DNA module 310 may be incorporated into or may utilize (e.g., dynamically gather network attributes from) a network location awareness module, for example, the network location awareness module detailed by the Network Location Awareness Service Provider section of the February 2003 Microsoft® Windows® Platform SDK documentation in the MSDN® Library. Although not shown in FIG. 3, the network application programming interface and/or the network location awareness module may be incorporated into the operating system 304.
FIG. 4 depicts an example network DNA module architecture in accordance with an embodiment of the invention. The example network DNA module 400 includes a network DNA acquirer 402, a network DNA generator 404, a current network DNA 406 store, a network DNA history 408 store, a network DNA policy store 410, a network DNA policy enforcer 412 and a network DNA application programming interface (API) 414. The network DNA generator 404 may include derived network DNA component specifications 416 and derived-raw network DNA component dependency lists 418. The current network DNA 406 store may include raw network DNA components 420 and derived network DNA components 422. The current network DNA 406 store, the network DNA history 408 store, the network DNA policy store 410 and/or other network DNA module 400 stores may be implemented with conventional database technologies, caching technologies and/or the like.
The network DNA acquirer 402 may acquire raw network DNA component values from the computer hardware 306 (FIG. 3), the operating system 304, the application programs 302 and from network DNA modules located on remote computers 116 (FIG. 1). The network DNA acquirer 402 may acquire raw network DNA component values from both trusted (e.g., authenticated) and untrusted sources. Some computer networks may incorporate network DNA provisioning servers to provide an explicit and efficient source of network DNA. Conventional provisioning schemas may be enhanced with network DNA.
Raw network DNA component values may be simple copies of static values, samples of dynamically changing values or the like. Examples of raw network DNA components include IP addresses, domain names, verified presence of network infrastructure elements (e.g., DNS servers, authentication servers, proxy servers, NAT), successful authentication, parameters received from DHCP servers (e.g., subnet mask), communications media type (e.g., wireless or wire-line), network traffic analysis (e.g., source address set or statistical traffic ‘fingerprint’ match), cost, service provider, roaming agreements, nominal available communications bandwidth, measured available communications bandwidth, logical and physical network location. Raw network DNA components may be any suitable (e.g., acquirable) conventional computer network attribute. Raw network DNA components may be input by a computer user utilizing a suitable user interface mechanism.
The network DNA acquirer 402 may update the raw network DNA components 420 area of the current network DNA 406 store. The network DNA acquirer 402 may copy current network DNA component values to the network DNA history 408 store before updating them. The network DNA acquirer 402 may notify the network DNA generator 404 of updates to the current network DNA 406 store.
The network DNA generator 404 may determine derived network DNA component values from raw network DNA component value. The network DNA generator 404 may determine derived network DNA component values according to the derived network DNA component specifications 416. For example, each of the derived network DNA component specifications 416 may specify a linear or non-linear combination and/or transformation of one or more raw network DNA component values. The derived-raw network DNA component dependency lists 418 may include, for each derived network DNA component, a list of raw network DNA components required to determine the derived network DNA component, and/or, for each raw network DNA component, a list of derived network DNA components that depend upon the raw network DNA component (e.g., the raw network DNA component is part of the derived network DNA component specifications for the derived network DNA components). The network DNA generator 404 may update the derived network DNA components 422 area of the current network DNA 406 store. The network DNA generator 404 may copy current network DNA component values to the network DNA history 408 store before updating them.
The network DNA policy enforcer 412 may enforce network DNA policies stored in the network DNA policy store 410. The network DNA policies may depend upon network DNA stored in the current network DNA 406 and/or network DNA history 408 stores, for example, network DNA policy actions may be triggered by network DNA components taking on particular values or crossing particular thresholds. The network DNA application programming interface 414 may enable, for example, application programs 302 (FIG. 3) to edit network DNA policies as well as get current network DNA and network DNA history.
Before describing procedures performed by the network DNA module in more detail, it will be helpful to describe further details of network DNA, network DNA policies and the network DNA application programming interface 414 (FIG. 4).
FIG. 5 depicts example network DNA in accordance with an embodiment of the invention. The example network DNA 500 includes a network species 502 component, a network name 504 component, a network cost 506 component, a core access 508 component, a core addressing 510 component, a network security 512 component and a network technology 514 component. Each network DNA component may be associated with one or more sub-components, for example, one or more raw network DNA components (e.g., raw network DNA components 420 of FIG. 4) and/or one or more derived network DNA components (e.g., derived network DNA components 422 of FIG. 4). Each network DNA component may be associated with a confidence level, for example, from 0% to 100% or a scale of 0 to 5.
In this example, the network species 502 component is associated with a network species confidence 516, the network name 504 component is associated with a network name confidence 518, the network cost 506 component is associated with a network cost confidence 520, the core access 508 component is associated with a core access confidence 522, the core addressing 510 component is associated with a core addressing confidence 524, the network security 512 component is associated with a network security confidence 526, and the network technology 514 component is associated with a network technology confidence 528. Each network DNA confidence 516, 518, 520, 522, 524, 526, 528 may indicate a level of confidence (e.g., a statistical confidence) in the accuracy and/or precision of the associated network DNA component value(s). Network DNA confidence levels may be updated by the network DNA generator 404 (FIG. 4) when derived network DNA components 422 are updated.
The network species 502 component of the network DNA 500 may indicate a network class (or species) for the associated computer network. For example, the network species 502 component may indicate that the associated computer network is an enterprise network, a home network or a public place (public) network. The network species 502 component of the network DNA 500 may be one of the derived network DNA components 422 (FIG. 4) and may be associated with one or more of the derived network DNA component specifications 416.
For example, one of the derived network DNA component specifications 416 (FIG. 4) associated with the network species 502 component may specify that the network species 502 component is to indicate that the associated computer network is an enterprise network if the attributes of the associated computer network include a specified combination of: is a secure network (i.e., has good network security), is a managed network (i.e., has good network management), provides connectivity to one or more specified enterprise resources (e.g., has good local area network connectivity), includes wireless LAN technology, is a mobile network (i.e., has good network mobility), is a private network (e.g., utilizes internal network addressing), is a premise network and is not a proximity network. Examples of computer networks that may have one or more combinations of such computer network attributes include corporate computer networks (e.g., for employees only), virtual private networks, fleet networks (e.g., fleet of corporate-owned vehicles), managed community networks, and warehouse networks.
The derived network DNA component specification may specify that the network species 502 component is to indicate that the associated computer network is a home network if the attributes of the associated computer network include a specified combination of: is an insecure network (i.e., has poor network security), is an unmanaged network (i.e., has poor network management), provides ad hoc and/or limited connectivity between network nodes and other computer networks (e.g., the internet), includes PAN, LAN and/or wireless LAN technology, is not a mobile network (i.e., has poor network mobility), is a private network (e.g., utilizes internal network addressing), is a premise network or a proximity network. Examples of computer networks that may have one or more combinations of such computer network attributes include home networks and residential networks.
The derived network DNA component specification may specify that the network species 502 component is to indicate that the associated computer network is a public place network if the attributes of the associated computer network include a specified combination of: is an insecure network, is an unmanaged network, includes PAN, LAN, wireless LAN and/or wireless WAN technology, provides connectivity to other computer networks (e.g., the internet), is not a mobile network, has an associated access cost, is not a private network, is not a premise network and is not a proximity network. Examples of computer networks that may have one or more combinations of such computer network attributes include computer networks at airports, restaurants and coffee houses, convention centers, hotels (particularly hotel lobbies), public libraries, corporate guest networks and some wireless wide area networks.
As shown in the above examples, derived network DNA component specifications 416 (FIG. 4) need not be mutually exclusive. Each derived network DNA component specification may include a network DNA confidence scoring specification. For example, a particular derived network DNA component specification may reference multiple raw network DNA components. The associated network DNA confidence scoring specification may specify that missing (e.g., not yet acquired) or unverified (e.g., acquired from untrusted sources) raw network DNA components result in a lower confidence and that some raw network DNA components have greater influence on confidence level than others. Where a total number of different derived network DNA component values is reasonable (e.g., 100, but depending upon computer processing power), each different value may have an associated confidence score. In such a case, requests for the value of a particular derived network DNA component may result in responses including one or more values with highest associated confidence scores.
The network name 504 component of the network DNA 500 may indicate a network name and/or network identifier for the associated computer network. The network name may, for example, be a simple alphanumeric character string or a more complex data structure. The network name may include, for example, a globally unique identifier (GUID) that uniquely identifies the associated computer network. However, neither the network name 504 component nor network DNA 500 as a whole, need be unique across computer networks. As for each derived network DNA component 502, 504, 506, 508, 510, 512 and 514, network name 504 component attributes and values may be specified by one or more of the derived network DNA component specifications 416 (FIG. 4). Where probabilistic network name resolution is utilized, the network name confidence 518 may indicate, for example, a confidence level of the determination so far due to progress of the probabilistic name resolution process.
The network cost 506 component of the network DNA 500 may indicate historical, future and current costs associated with utilizing the associated computer network. For example, the network cost 506 component may reference one or more computer network usage rate plans including per byte, per hour and other suitable bandwidth, time period and/or network resource pricing options. Cost determination may be probabilistic, for example, approximation techniques may be utilized where cost determination is complex, in which case the network cost confidence 520 may indicate a margin of error.
The core access 508 component of the network DNA 500 may indicate to what degree the associated computer network provides access to core or transit networks (e.g., the internet). For example, the core access 508 component may indicate that authentication with a particular resource server is required for core network access. Core network access determination may be probabilistic and/or progressive, particularly from computers connected to unmanaged networks. The core access confidence 522 may indicate the progress and/or degree of achievement of the determination procedure.
The core addressing 510 component of the network DNA 500 may indicate whether the associated computer network utilizes internal (private) or external (public or core) addressing. Internal addressing may reduce a set of suitable communications protocols available to applications. Core addressing determination may be probabilistic and/or progressive, or the core addressing confidence 526 may simply indicate a confirmed or unconfirmed status.
The network security 512 component of the network DNA 500 may indicate one or more security mechanisms available in the associated computer network, as well as, for example, which security mechanisms are mandatory for computers connected to the associated computer network. For example, the network security 512 component may indicate that authentication with one or more network infrastructure elements or resource servers is mandatory and that encryption is available but optional. The network security 512 component may also reference suitable authentication credentials and/or encryption keys. Determination of available and/or mandatory security mechanisms may be probabilistic and/or progressive, for example, additional encryption options may become available following authentication. The network security confidence 526 may indicate determination progress and/or confidence in the integrity of active security mechanisms in the associated computer network.
The network technology 514 component of the network DNA 500 may indicate one or more network implementation technologies utilized by the associated computer network. The network technology indication may include coarse grained classifications, for example, wireless or wire-line, as well as fine grained classifications, for example, IEEE 802.11a, IEEE 802.11b or IEEE 802.16a wireless. Determination of network technology classifications may be probabilistic and/or progressive. The network technology confidence 528 may include a confidence level for each determined network technology classification.
Network DNA policies may depend upon network DNA 500. FIG. 6 depicts an example network DNA policy in accordance with an embodiment of the invention. The example network DNA policy 600 includes a network DNA policy name 602, a network DNA policy condition 604, a network DNA policy action 606 and network DNA policy dependency lists 608. The network DNA policy dependency lists 608 include a derived network DNA components dependency list 610 and a raw network DNA components dependency list 612.
The network DNA policy name 602 may be a unique name (e.g., alphanumeric character string or a globally unique identifier) of the network DNA policy 600. The network DNA policy name 602 may serve as an identifier and/or reference for the network DNA policy 600. A condition specified by the network DNA policy condition 604 may reference derived network DNA components and/or raw network DNA components of current network DNA 406 (FIG. 4) and/or network DNA history 408. An action specified by the network DNA policy action 606 may be initiated by the network DNA module 400 if the condition specified by the network DNA policy condition 604 is satisfied.
The network DNA policy dependency lists 608 may list system aspects (e.g., components, modules, resource servers) that the network DNA policy 600 depends upon in order to determine if the network DNA policy condition 604 is satisfied and/or to initiate the network DNA policy action 606. The derived network DNA components dependency list 610 may list derived network DNA components referenced by the network DNA policy condition 604. The raw network DNA components dependency list 612 may list raw network DNA components referenced by the network DNA policy condition 604.
Examples of network DNA policies include polices for adapting to network changes and for selecting between multiple available networks. Network DNA policies may adapt system behavior in response to network DNA 500, for example, changes in the network technology 514 component of the network DNA 500 (e.g., when switching computer networks) may trigger reconfiguration of application programs 302 (FIG. 3) and/or the operating system 304 to avoid performance penalties. For example, a messaging application may download a specified portion of a message (e.g., as opposed to the whole message) or synchronize with a messaging server less aggressively (e.g., less often) for certain network technology 514 classifications and/or subcomponent values.
Changes in the network security 512 component of the network DNA 500 (e.g., when switching computer networks) may likewise trigger reconfiguration of application programs 302 and/or the operating system 304 to reduce the likelihood of security vulnerabilities. One or more network DNA policies may determine a choice between multiple available networks, for example, based on a combination of the network cost 506 and core access 508 components of the network DNA 500. Additional examples of network DNA components that may be utilized in deciding between multiple available networks (or any suitable network DNA policy decision) include: network security 512, speed, load, latency, congestion, radio frequency interference (e.g., noise) and network operator (not necessarily of the first hop, for example, the operator/owner of a GPRS network supplying connectivity to a Wi-Fi ‘hotspot’). While network DNA policies may reduce the probability of user intervention, choice between multiple computer networks need not be fully automated. Computer users may be presented with a filtered list of possible choices.
Network DNA policies may specify that system security settings be reconfigured depending on the network species 502 component of the network DNA 500. A computer with a particular network DNA policy that is connected to a home or public network (as indicated by the network species 502) may automatically attempt to establish a VPN connection to a specified enterprise network so that, for example, the computer has access to enterprise network resource and/or to become managed. Another network DNA policy may specify that bridging (or inter-network routing) be disabled if a computer with the policy is, for example, connected to both an enterprise network and a home or public network as indicated by the network species 502.
The network DNA application programming interface 414 (FIG. 4) may provide application programs 302 (FIG. 3) and operating system 304 access to network DNA and network DNA policies. In an embodiment of the invention, a human-oriented characteristic of network DNA makes network DNA particularly suited for network mapping (e.g., on graphical user interfaces) and network support applications (e.g., enterprise help desk, troubleshooting/diagnostics, and security breach post-mortem). Network DNA may enhance computer user (and application developer) understanding of connected computer networks which may enhance computer user experience and efficiency. In an embodiment of the invention, network DNA may be logged and communicated between computer network nodes to enhance both automatically and manually managed aspects of computer network efficiency, for example, reducing the likelihood of over/under allocation of upstream bandwidth by streaming data sources.
FIG. 7 depicts an example network DNA application programming interface in accordance with an embodiment of the invention. The example network DNA application programming interface 700 includes an edit network DNA policy 702 element, a subscribe to network DNA events 704 element, a get current network DNA 706 element, a get network DNA history 708 element and an edit derived network DNA component specifications 710 element. Each application programming interface element 702, 704, 706, 708 and 710 may include one or more interface specifications that specify the manner in which computer system modules and components may interact with the network DNA module 400. As will be apparent to one of skill in the art, the interface specifications may include function call specifications, program object specifications, message specifications such as request/response message pairs, and/or any other suitable programming interface specification.
The edit network DNA policy application programming interface element 702 may enable computer system modules and components to create, read, update, delete and temporarily disable or enable network DNA policies of the network DNA module 400 (FIG. 4), for example, network DNA policies stored in the network DNA policy store 410. Interface specification parameters may include one or more network DNA policies (e.g., as described above with reference to FIG. 6), network DNA policy actions, network DNA policy conditions, network DNA policy names, a date and time for a particular policy (or policy set) to take effect, a date and time range for the policy to remain in effect and/or a date and time range for the policy to remain disabled, and an event that triggers enabling or disabling of a particular policy. For example, network DNA policy conditions may be specified with a structured query language, an object oriented language (e.g., an object query language), a scripting language (e.g., Microsoft® VBSCRIPT), or any suitable condition specification language, and network DNA policy actions may be specified with a database stored procedure language, an object oriented language, a scripting language, or any suitable action specification language.
The subscribe to network DNA events application programming interface element 704 may enable computer system modules and components to subscribe to and unsubscribe from events published by the network DNA module 400 (FIG. 4). Interface specification parameters may include one or more network DNA event specifications (e.g., event identifiers, event range specifications) and one or more subscription addresses (e.g., reference to a network DNA event delivery mechanism). Examples of network DNA events published by the network DNA module 400 include current network DNA 406 changes, network DNA policy changes, occurrence of network DNA policy enforcement actions, and any suitable network DNA module 400 change event.
The get current network DNA application programming interface element 706 may enable computer system modules and components to retrieve a copy of the current network DNA 406 (FIG. 4). Interface specification parameters may include a set of network DNA components to retrieve and parallel programming (multithreaded) behavior specifiers such as wait and timeout flags. The get current network DNA history application programming interface element 708 may enable computer system modules and components to retrieve a copy of network DNA history 408. Interface specification parameters may include a set of network DNA components to retrieve, a range (e.g., a data and time range) of network DNA history entries to retrieve and parallel programming (multithreaded) behavior specifiers such as wait and timeout flags.
The edit derived network DNA component specifications application program interface element 710 may enable computer system modules and components to create, read, update and delete derived network DNA component specifications 416 (FIG. 4). Interface specification parameters may include one or more derived network DNA component specifications (e.g., as described above with reference to FIG. 4). For example, derived network DNA component specifications may be specified with a structured query language, an object oriented language, a scripting language, a database stored procedure language or any suitable component specification language.
Having described structural aspects of the network DNA module 400 (FIG. 4) above, behavioral aspects of the network DNA module 400 are now described in more detail.
The network DNA acquirer 402 (FIG. 4) may dynamically acquire raw network DNA components. The number of potential raw network DNA components to be acquired (acquisition targets) may be large. The network DNA acquirer 402 may prioritize acquisition targets according to network DNA policy needs. For example, network DNA policies in the network DNA policy store 410 may be ordered and the network DNA acquirer 402 may acquire network DNA components referenced by network DNA policies in accord with that order. Some raw network DNA components may require periodic re-acquisition (e.g., every 5 seconds) and may be given priority to prevent them becoming ‘stale’ in the current network DNA 406 store. Some raw network DNA components may require asynchronous acquisition triggered by an event. Acquisition of some raw network DNA components may need to take place after others, for example, following successful authentication with a network authentication server, and thus may be prioritized accordingly.
FIG. 8A depicts example steps that may be performed to acquire network DNA in accordance with an embodiment of the invention. At step 802, a derived network DNA acquisition priority list is generated. For example, the network DNA acquirer 402 (FIG. 4) may query the network DNA policy store 410 for the derived network DNA components dependency list 610 (FIG. 6) of each active network DNA policy. If the network DNA policies are ordered then the derived network DNA components may be added to the derived network DNA acquisition priority list in accord with that order.
At step 804, a raw network DNA acquisition priority list is generated. For example, the network DNA acquirer 402 (FIG. 4) may query the network DNA policy store 410 for the raw network DNA components dependency list 612 (FIG. 6) of each active network DNA policy. In addition, the network DNA acquirer 402 may determine any raw network DNA components required by each member of the derived network DNA acquisition priority list. For example, the network DNA acquirer 402 may query the network DNA generator 404 for the associated derived-raw network DNA component dependency lists 418. If the network DNA policies are ordered then the raw network DNA components may be added to the raw network DNA acquisition priority list in accord with that order. Each raw network DNA component may have an associated acquisition difficulty, for example, related to acquisition time or required refresh rate. Acquisition order may be modified so that the most easily acquired raw network DNA components tend to be acquired before components that are more difficult to acquire. In an embodiment of the invention, step 802 is performed as an integral part of step 804.
At step 806, a next acquisition target may be selected from the raw network DNA acquisition priority list. At step 808, an attempt is made to acquire the selected acquisition target as described above with reference to FIG. 4. There may be a limited time period allocated for the acquisition of each target. At step 810, a determination is made as to whether the selected acquisition target was successfully acquired. If the target was successfully acquired then the procedure progresses to step 812, otherwise the procedure progresses to step 814.
At step 812, the acquired raw network DNA component may be stored in the raw network DNA components 420 (FIG. 4) area of the current network DNA 406 and the associated reference removed from the raw network DNA acquisition priority list. At step 816, the network DNA generator 404 may be notified of the successful acquisition. For example, the network DNA acquirer may publish a raw network DNA acquisition event. At step 814, a length of the raw network DNA acquisition priority list may be checked. If the list is empty then there are no current acquisition targets and the procedure exits, otherwise, the procedure returns to step 806 to select the next acquisition target.
The procedure depicted in FIG. 8A may be invoked asynchronously or, for example, synchronously in accordance with a schedule. In the case of asynchronous acquisition of one or more raw network DNA components triggered by an event (i.e., a target acquisition event), the target acquisition event may specify one or more raw network DNA components to be acquired. The target acquisition event may even specify the raw network DNA acquisition priority list of step 804 which may enable step 802 and step 804 to be skipped. If the target acquisition event specifies a single raw network DNA component to be asynchronously acquired, step 806, step 812 and step 814 may also be skipped. FIG. 8B depicts example steps that may be performed to asynchronously acquire a single raw network DNA component in accordance with an embodiment of the invention, beginning with step 818 where the target acquisition event is generated and then progressing to a subset of steps similar to those described with reference to FIG. 8A.
The network DNA generator 404 (FIG. 4) may generate derived network DNA component values asynchronously (e.g., in response to raw network DNA acquisition events) or in accordance with a network DNA generation schedule. FIG. 9 depicts example steps that may be performed to generate network DNA in accordance with an embodiment of the invention. At step 902, a derived network DNA refresh list is generated. For example, the network DNA generator 404 (FIG. 4) may be notified of raw network DNA component updates and may add to the refresh list each derived network DNA component that depends upon a changed raw network DNA component (e.g., updated since a previous derived network DNA refresh). The derived-raw network DNA component dependency lists 418 may specify dependencies between derived and raw network DNA components.
At step 904, a next refresh target (i.e., a particular derived network DNA component) may be selected from the derived network DNA refresh list. At step 906, a value of the selected derived network DNA component may be derived (i.e., determined) in accordance with associated derived network DNA component specifications 416 (FIG. 4). For example, the network DNA generator 404 may retrieve current values of raw network DNA components 420 and transform them as specified by a particular derived network DNA component specification. At step 908, the derived network DNA refresh list is checked for more refresh targets. If there are more refresh targets then the procedure returns to step 904 to select the next target, otherwise, the procedure exits.
The network DNA policy enforcer 412 (FIG. 4) may enforce network DNA policies asynchronously (e.g., in response to current network DNA update events) or in accordance with a network DNA policy enforcement schedule. FIG. 10 depicts example steps that may be performed to enforce network DNA policies in accordance with an embodiment of the invention. At step 1002, the procedure resides in a wait state. The procedure may leave the wait state, for example, if a scheduled time period elapses and/or if an interesting (i.e., policy affecting) network DNA module event (e.g., published event) occurs.
At step 1004, a next active network DNA policy is selected, for example, from the network DNA policy store 410 (FIG. 4). The selected network DNA policy 600 (FIG. 6) may be associated with one or more derived network DNA components and/or one or more raw network DNA components, for example, as listed in the derived network DNA components dependency list 610 and the raw network DNA components dependency list 612 of the selected network DNA policy 600. At step 1006, it may be determined whether sufficient network DNA components associated with the selected network DNA policy 600 have been acquired, for example, by the network DNA acquirer 402 and stored in the current network DNA 406 store. For example, sufficient network DNA components may have been acquired if a confidence level (e.g., confidence levels 516, 518, 520, 522, 524, 526 and 528 of FIG. 5) associated with each network DNA component referenced by the selected network DNA policy 600 has a value greater than zero, or at least one confidence level is greater than a sufficient network DNA acquisition threshold (e.g., 50%), or some statistical function (e.g., average) of the confidence levels is greater than the sufficient network DNA acquisition threshold. If sufficient network DNA components have been acquired then the procedure progresses to step 1008, otherwise, the selected network DNA policy 600 is not tested and the procedure progresses to step 1010.
At step 1008, the network DNA policy condition 604 (FIG. 6) of the selected network DNA policy 600 may be tested. For example, if the network DNA policy condition 604 is specified with a structured query language statement then the structured query language statement may be submitted to a structured query language interpreter. If the network DNA policy condition 604 is satisfied (e.g., if an expression specified by the network DNA policy condition 604 evaluates to Boolean true or non-NULL) then the procedure progresses to step 1012, otherwise, the network DNA policy action 606 of the selected network DNA policy is not performed and the procedure progresses to step 1010.
At step 1012, execution of the network DNA policy action 606 of the network DNA policy 600 is initiated. For example, the network DNA policy enforcer 412 may make a procedure call (local or remote), invoke a method of a program object, send a message to a program module or a system user or administrator and/or initiate any suitable programmatic technique for performing an action on a computer (e.g., the computer 102 of FIG. 1). At step 1010, it is determined whether there are more active network DNA policies to test. If there are more active network DNA policies to test this cycle then the procedure returns to step 1004 to select the next active network DNA policy. Otherwise, the procedure returns to step 1002 and waits for the next scheduled or asynchronous wake-up event.
1. A method for managing network communications, the method comprising:
obtaining a classification of a type of a computer network from amongst multiple different types of computer networks, wherein obtaining the classification includes:
deriving the classification from multiple network attributes associated with the computer network, wherein:
the multiple network attributes include a domain name, a presence of a network infrastructure element, a parameter received from a network server, a communications media type, a service provider, a nominal available communications bandwidth, a measured available communications bandwidth, and/or a physical network location;
obtaining at least one network classification policy based on the obtained classification for the computer network; and
implementing a network classification policy action according to the at least one obtained network classification policy, wherein implementing the at least one network classification policy action includes:
configuring network security settings based on the obtained classification.
2. The method of claim 1, wherein the implementing the network classification policy action further includes:
configuring applications settings of a computing device for the network communications via the computer network.
3. The method of claim 1, wherein the implementing the network classification policy action further includes:
selecting the computer network from amongst multiple available networks.
the multiple network attributes include information received from a remote computer.
the obtained classification indicates the type of network selected from amongst a plurality of network types.
the plurality of network types comprise an enterprise network, a home network and a public network.
the obtained classification specifies a combination of network attributes of the multiple network attributes.
obtaining the classification also includes deriving the classification based on a structured query language statement, a scripting language statement, and/or an object-oriented language statement.
the classification is also derived based on each derived network characteristic referenced by a network characteristic list matching network attributes of the network, the network characteristic list referencing at least one network characteristic dependent upon two or more network attributes.
the classification is also derived based on confidence levels associated with each of at least two network attributes of the multiple network attributes.
11. A computing device that is connectable to at least one network, the computing device comprising:
a memory and at least one processor that are respectively configured to store and execute instructions that are organized into:
a classification store that stores network classifications, the network classifications classifying types of networks according to network characteristics;
a network classification policy enforcer that:
selects a network classification policy action to execute based on a determined network classification from the classification store; and
configures network security settings according to definitions of the selected network classification policy action;
a network attribute acquirer that receives indications of multiple network attributes associated with the network, wherein:
the multiple network attributes includes at least one of a domain name, a presence of a network infrastructure element, a parameter received from a network server, a communications media type, a service provider, a nominal available communications bandwidth, a measured available communications bandwidth, or a physical network location; and
a network characteristic generator that determines the network classification from the stored network classifications according to the received indications of the multiple network attributes associated with the network.
12. The computing device of claim 11, wherein the network classification policy enforcer also:
configures applications settings for communications via the network.
13. The computing device of claim 11, wherein:
the multiple network attributes include information received from an authenticated remote computer.
14. The computing device of claim 11, wherein:
the determined network classification indicates a type of network selected from amongst a plurality of network types.
16. The computing device of claim 11, wherein:
the determined network classification is at least partially defined by a combination of the multiple network attributes.
17. The computing device of claim 11, wherein the network characteristic generator also:
determines the network classification based on confidence levels associated with a plurality of network attributes from the multiple network attributes.
18. A computing device that is connectable to at least one network, the computing device comprising:
a network interface configured to connect the computing device to a network;
at least one memory and at least one processor that are respectively configured to store and execute computer-executable components, the computer-executable components including:
a classification store configured to store network classifications, the network classifications associating types of networks to network characteristics;
a network classification policy enforcer configured to:
select a network classification policy for the network connected to via the network interface based on a determined network classification for the network; and
configure network security settings for the network according to definitions of the selected network classification policy action for the network;
a network attribute acquirer configured to receive indications of multiple network attributes associated with the network from the network interface, wherein:
the multiple network attributes comprise at least one of a domain name, a presence of a network infrastructure element, a parameter received from a network server, a communications media type, a service provider, a nominal available communications bandwidth, a measured available communications bandwidth, or a physical network location; and
a network characteristic generator configured to determine the network classification for the network connected to via the network interface from the stored network classifications according to the received indications of the multiple network attributes associated with the network.
19. The computing device of claim 18, wherein:
the multiple network attributes include information received from a remote computing device.
20. The computing device of claim 18, wherein:
22. The computing device of claim 18, wherein the network characteristic generator is further configured to:
determine the network classification based a combination of the multiple network attributes.
23. The computing device of claim 18, wherein the network characteristic generator is further configured to:
determine the network classification based on confidence levels associated with a plurality of network attributes from the multiple network attributes.
24. The computing device of claim 18, wherein the network classification policy enforcer is further configured to:
configuring applications settings of the computing device for network communications via the network.
25. The computing device of claim 18, wherein the network characteristic generator is further configured to:
determine the network classification based on each derived network characteristic referenced by a network characteristic list matching network attributes of the network, the network characteristic list referencing at least one network characteristic with two or more network attributes.
US14212128 2004-02-06 2014-03-14 Network classification Active US9374286B2 (en)
US13300743 US8676969B2 (en) 2004-02-06 2011-11-21 Network classification
US14212128 US9374286B2 (en) 2004-02-06 2014-03-14 Network classification
US14943259 US9608883B2 (en) 2004-02-06 2015-11-17 Network classification
US13300743 Continuation US8676969B2 (en) 2004-02-06 2011-11-21 Network classification
US14943259 Continuation US9608883B2 (en) 2004-02-06 2015-11-17 Network classification
US20140280798A1 true US20140280798A1 (en) 2014-09-18
US9374286B2 true US9374286B2 (en) 2016-06-21
US10773681 Active 2027-07-18 US8126999B2 (en) 2004-02-06 2004-02-06 Network DNA
US13300743 Active US8676969B2 (en) 2004-02-06 2011-11-21 Network classification
US14212128 Active US9374286B2 (en) 2004-02-06 2014-03-14 Network classification
US14943259 Active US9608883B2 (en) 2004-02-06 2015-11-17 Network classification
JPH09238138A (en) 1996-02-28 1997-09-09 Nec Corp Network management device
JP2001144758A (en) 1999-11-12 2001-05-25 Fujitsu Ltd System for managing communication network
WO2001063447A2 (en) 2000-02-23 2001-08-30 Orillion International, Inc. Apparatus and method for network data modeling
US6298044B1 (en) 1998-03-31 2001-10-02 Hewlett-Packard Company Method and apparatus for determining if overloaded collision domains can be split to enhance network
US20010037384A1 (en) 2000-05-15 2001-11-01 Brian Jemes System and method for implementing a virtual backbone on a common network infrastructure
JP2002064561A (en) 2000-08-22 2002-02-28 Hitachi Ltd Network control apparatus and network control method
US20020124094A1 (en) 2000-12-15 2002-09-05 International Business Machines Corporation Method and system for network management with platform-independent protocol interface for discovery and monitoring processes
WO2002084951A1 (en) 2001-04-10 2002-10-24 Netvmg, Inc. System and method to assure network service levels with intelligent routing
US20030074359A1 (en) 2001-10-12 2003-04-17 Koji Tezuka Network management unit
WO2003058884A2 (en) 2002-01-09 2003-07-17 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for managing configuration of a network
JP2003258872A (en) 2002-02-08 2003-09-12 Shijin Kogyo Sakushinkai Matching network telephone distributor having exchange distribution function
US20030187631A1 (en) 2002-03-29 2003-10-02 Fujitsu Limited Host-terminal emulation program, a relay program, a host-terminal emulation method, a communication program, a communication method, and a client computer
US6640302B1 (en) 1999-03-16 2003-10-28 Novell, Inc. Secure intranet access
US6675209B1 (en) 1999-07-19 2004-01-06 Hewlett-Packard Development Company, L.P. Method and system for assigning priority among network segments
US20040006614A1 (en) 2002-07-03 2004-01-08 Difalco Robert A. Homogeneous monitoring of heterogeneous nodes
WO2004008693A1 (en) 2002-07-10 2004-01-22 Koninklijke Philips Electronics N.V. Interface selection from multiple networks
US20040068582A1 (en) 2000-04-03 2004-04-08 Mark Anderson Method and system to initiate geolocation activities on demand and responsive to receipt of a query
US20040095887A1 (en) 2000-01-18 2004-05-20 At&T Corp. Apparatus and method for designing a network
JP2004186751A (en) 2002-11-29 2004-07-02 Nec Infrontia Corp Communication system
US20050060328A1 (en) 2003-08-29 2005-03-17 Nokia Corporation Personal remote firewall
US20050086510A1 (en) 2003-08-15 2005-04-21 Fiberlink Communications Corporation System, method, apparatus and computer program product for facilitating digital communications
US20050138351A1 (en) 2003-12-23 2005-06-23 Lee Sok J. Server authentication verification method on user terminal at the time of extensible authentication protocol authentication for Internet access
US20050144314A1 (en) 2003-11-21 2005-06-30 Alcatel Dynamic system for communicating network monitoring system data to destinations outside of the management system
US20050149948A1 (en) 2003-12-30 2005-07-07 Intel Corporation System and method for monitoring and managing connection manager activity
US20050193129A1 (en) 2004-02-27 2005-09-01 International Business Machines Corporation Policy based provisioning of web conferences
US20050257267A1 (en) 2003-02-14 2005-11-17 Williams John L Network audit and policy assurance system
US6982960B2 (en) 2001-03-09 2006-01-03 Motorola, Inc. Protocol for self-organizing network using a logical spanning tree backbone
US20060129665A1 (en) 2004-12-01 2006-06-15 John Toebes Arrangement in a server for providing dynamic domain name system services for each received request
JP2006330877A (en) 2005-05-24 2006-12-07 Ricoh Co Ltd Communication method and communication system
US20070177524A1 (en) 2006-01-31 2007-08-02 Microsoft Corporation Network connectivity determination based on passive analysis of connection-oriented path information
US20070177499A1 (en) 2006-01-31 2007-08-02 Microsoft Corporation Network connectivity determination
US7277393B1 (en) 2002-03-13 2007-10-02 Packet Design, Inc. System and method for identifying cost metrics for a network
US20070271598A1 (en) 2006-05-16 2007-11-22 A10 Networks, Inc. Systems and methods for user access authentication based on network access point
EP1914956A1 (en) 2006-10-17 2008-04-23 Intel Corporation Enabling a secure platform
US20090086644A1 (en) 2001-06-25 2009-04-02 Kireeti Kompella Detecting data plane liveliness of a label-switched path
JP2004528775A (en) 2001-04-10 2004-09-16 ネットヴィエムジー， インコーポレーテッド Systems and methods to ensure the network service level for intelligent delivery
JP2003124931A (en) 2001-10-12 2003-04-25 Fujitsu Ltd Network managing system
JP2005532759A (en) 2002-07-10 2005-10-27 コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィＫｏｎｉｎｋｌｉｊｋｅ Ｐｈｉｌｉｐｓ Ｅｌｅｃｔｒｏｎｉｃｓ Ｎ．Ｖ． Selection of the interface from the plurality of network
US7448070B2 (en) 2003-10-17 2008-11-04 Microsoft Corporation Network fingerprinting
US20120066381A1 (en) 2004-02-06 2012-03-15 Microsoft Corporation Network dna
US20140280798A1 (en) 2004-02-06 2014-09-18 Microsoft Corporation Network Classification
JP2005278148A (en) 2004-02-06 2005-10-06 Microsoft Corp Network dna
"China First Office Action", Application No. 200410088262.4, Filed Date : Oct. 18, 2004, Mailed Date : Apr. 10, 2009, pp. 14.
"China First Office Action", Application No. 200510008172.4, Filed Date : Feb. 6, 2005, Mailed Date : Aug. 1, 2008, pp. 11.
"China Second Office Action", Application No. 200410088262.4, Filed Date : Oct. 18, 2004, Mailed Date : Oct. 16, 2009, pp. 12.
"China Second Office Action", Application No. 200510008172.4, Filed Date : Feb. 6, 2005, Mailed Date : Jan. 15, 2010, pp. 6.
"China Third Office Action", Application No. 200410088262.4, Filed Date : Oct. 18, 2004, Mailed Date : Jan. 8, 2010, pp. 8.
"China Third Office Action", Application No. 200510008172.4, Filed Date : Feb. 6, 2005, Mailed Date : Nov. 9, 2011, pp. 7.
"European Office Action", Application No. 04019631.3-2413, Filed Date : Aug. 18, 2004, Mailed Date : Dec. 21, 2006, pp. 3.
"European Office Action", Application No. 04019631.3-2413, Filed Date : Aug. 18, 2004, Mailed Date : Jul. 11, 2007, pp. 4.
"European Office Action", Application No. 05100716.9-2416, Filed Date : Feb. 2, 2005, Mailed Date : Aug. 10, 2007, pp. 4.
"European Office Action", Application No. 05100716.9-2416, Filed Date : Feb. 2, 2005, Mailed Date : Feb. 1, 2006, pp. 6.
"European Office Action", Application No. 05100716.9-2416, Filed Date: Feb. 2, 2005, Mailed Date: Dec. 29, 2006, pp. 4.
"Japanese Notice of Rejection", Application No. 2004-272461, Filed Date : Sep. 17, 2004, Mailed Date : Dec. 3, 2010, pp. 4.
"Japanese Notice of Rejection", Application No. 2004-272461, Filed Date : Sep. 17, 2004, Mailed Date : Feb. 26, 2010, pp. 19.
"Korea Notice of Preliminary Rejection", Application No. 10-2004-68591, Filed Date : Aug. 30, 2004, pp. 4.
"Korea Office Action", Application No. 10-2005-10370, Filed Date : Feb. 4, 2005, pp. 5.
"Notice of Allowance", U.S. Appl. No. 10/688,656, filed Oct. 17, 2003, Mailed Date : Jun. 16, 2008, pp. 6.
"Split-horizon DNS," downloaded Jan. 14, 2009, 1 page.
"US Non-Final Office Action", U.S. Appl. No. 10/688,656, filed Oct. 17, 2003, Mailed Date : Dec. 12, 2007, pp. 7.
"US Non-Final Office Action", U.S. Appl. No. 10/688,656, filed Oct. 17, 2003, Mailed Date : May 31, 2007, pp. 6.
Adoba et al., "Detecting Network Attachment in IPv4 (DNAv4)," Standards Track, Network Working Group, RFC 4436, Mar. 2006, 15 pages.
Advisory Action dated Dec. 10, 2008 in U.S. Appl. No. 10/773,681, 4 pages.
Advisory Action dated Jan. 12, 2011 in U.S. Appl. No. 10/773,681, 3 pages.
Ahmed, et al., "Modular Multilayer Perceptron for WLAN Based Localization", 2006 International Joint Conference on Neural Networks Sheraton Vancouver Wall Centre Hotel, Vancouver, BC, Canada Jul. 16-21, 2006, pp. 7.
Aula, E., "Zero Configuration Networking," Helsinki University of Technoogy, Espoo, Fall 2002.
Aura, T. et al., "Securing Network Location Awareness with Authenticated DHCP," Sep. 17-21, 2007, 12 pages.
EP Communication EP Application No. 09822462.9 dated Apr. 2, 2013, 1 pgs.
EP Communication from EP Application No. 09822462.9 dated Apr. 26, 2016, 7 pgs.
EP Search Report in EP Application No. 09822462.9 dated Mar. 12, 2013, 8 pgs.
European Office Action dated Apr. 11, 2006 in EP App. No. 04019631.3, 5 pages.
European Office Action dated Feb. 20, 2006 in EP App. No. 04019631.3, 4 pages.
Final Action dated Aug. 18, 2011 in U.S. Appl. No. 10/773,681, 17 pages.
Final Action dated Aug. 19, 2008 in U.S. Appl. No. 10/773,681, 25 pages.
Final Action dated Nov. 13, 2009 in U.S. Appl. No. 10/773,681, 28 pages.
Final Action dated Oct. 19, 2010 in U.S. Appl. No. 10/773,681, 27 pages.
Final Office Action dated Dec. 23, 2011 in U.S Appl. No. 12/357,812, 23 pages.
Final Office Action dated Feb. 21, 2015 in U.S. Appl. No. 12/357,812, 11 pages.
Final Office Action dated Mar. 28, 2016 in U.S. Appl. No. 12/357,812, 15 pages.
First Chinese Office Action in Chinese Application No. 200980142641.8 dated Jun. 5, 2013, 9 pgs.
Fourth Chinese Office Action in Chinese Application No. 200980142641.8 dated Mar. 9, 2015, 3 pgs.
Hong et al., "The COBRA-based unified event management framework in multi-layer networks," Computer Communications, 25(3):254-264, Feb. 15, 2002.
Indian Office Action dated Apr. 25, 2013 from IN App. No. 204/DEL/2005; 2 pages.
Int. Preliminary Report in PCT Application No. PCT/US2009/060876 dated Apr. 26, 2011, 4 pgs.
Japanese language article cited by Japanese Patent Office by Feb. 26, 2010 Japanese Notice of Rejection in Application 2004-272461, pp. 10.
Japanese Office Action for JP 2005-030904 dated Jun. 4, 2010.
Japanese Office Action for JP 2005-030904 dated Nov. 26, 2010.
Japanese Office Action in Japanese Application No. 2011-533241 dated Jan. 20, 2014, 9 pgs.
Kiesel, et al., "Communications Network for Manufacturing Applications (cnma): A European Initiative for Network Management in Industrial Communication," Conference Proceedings Article dated Mar. 16, 1992, pp. 165-173.
Labuschagne, et al. "The Use of Real-Time Risk Analysis to Enable Dynamic Activation of Countermeasures," Computers & Security, Elsevier Science Publishers, Amsterdam, NL vol. 17. No. 4, 1998, pp. 347-357.
Microsoft Tech Net, "Network Location Awareness," downloaded Sep. 15, 2008, 1 page.
Microsoft WindowsServer 2008, Network Access Protection, downloaded Sep. 15, 2008, 2 pages.
MSDN, "Network Location Awareness Service Provider (NLA)", Windows Sockets 2 SDK, printed at http://msdn.microsoft.com/library/default.asp?url=/library/enus/winsock/w- insockInetwork location awareness service provider nla 2.asp(Feb. 2003). pp. 8.
MSDN, "Network Location Awareness Service Provider (NLA)," Windows Sockets 2 SDK, 8 pages, Feb. 2003, http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/- winsock/network.sub.-location.sub.--awareness.sub.--service.sub.--provide- r.sub.--nla.sub.--2.asp.
Non-Final Action dated Apr. 26, 2010 in U.S. Appl. No. 10/773,681, 26 pages.
Non-Final Action dated Apr. 8, 2009 in U.S. Appl. No. 10/773,681, 25 pages.
Non-Final Action dated Feb. 13, 2008 in U.S. Appl. No. 10/773,681, 27 pages.
Non-Final Action dated Mar. 4, 2010 in U.S. Appl. No. 10/773,681, 22 pages.
Non-Final Action dated Nov. 21, 2012 in U.S. Appl. No. 13/300,743, 14 pages.
Non-Final Office Action dated Apr. 18, 2014 in U.S. Appl. No. 12/357,812, 22 pages.
Non-Final Office Action dated Jul. 22, 2011 in U.S. Appl. No. 12/357,812, 21 pages.
Non-Final Office Action dated Mar. 23, 2016 in U.S. Appl. No. 14/943,259, 15 pages.
Non-Final Office Action dated May 17, 2013 in U.S. Appl. No. 13/300,743, 13 pages.
Non-Final Office Action dated Oct. 13, 2015 in U.S. Appl. No. 12/357,812, 16 pages.
Notice of Allowance dated Jun. 16, 2008 in U.S. Appl. No. 10/688,656, 7 pages.
Notice of Allowance dated Nov. 7, 2011 in U.S. Appl. No. 10/773,681, 10 pages.
Notice of Allowance dated Oct. 28, 2013 in U.S. Appl. No. 13/300,743, 18 pages.
Notice of Allowance in Japanese Application No. 2011-533241 dated Mar. 19, 2014, 3 pgs.
Office Action in Argentina Patent Application No. P09104093 dated Feb. 4, 2016, 9 pgs.
Office Action Issued in European Patent Application No. 05100716.9, Mailed Date: Jul. 31, 2015, 4 Pages.
Office Action Received in Chinese Patent Application No. 200980142641.8, Mailed Date: Aug. 5, 2015, 8 pages.
ORiNOCO, "Using Windows XP With Wireless Networks," Technical Bulletin 054/A, Sep. 2002.
PCT Search Report dated May 14, 2010 for PCT/US2009/060876, 10 pages.
Reply EP Communication in EP Application No. 09822462.9 dated Oct. 11, 2013, 18 pgs.
Reply first Chinese Office Action in Chinese Application No. 200980142641.8 dated Oct. 17, 2013, 12 pgs.
Reply fourth Chinese Office Action in Chinese Application No. 200980142641.8 dated May 22, 2015, 10 pgs.
Reply second Chinese Office Action in Chinese Application No. 200980142641.8 dated May 4, 2014, 6 pgs.
Reply Taiwan Search Report in Taiwan Patent Application No. 098135996 dated Nov. 10, 2014, 6 pgs.
Reply third Chinese Office Action in Chinese Patent Application No. 200980142641.8, dated Nov. 10, 2014, 15 pgs.
Reply-Claims Japanese Office Action in Japanese Application No. 2011-533241 dated Mar. 2, 2014, 17 pgs.
Search Report dated May 17, 2005 for EP 0500716.
Search Report Issued in European Patent Application No. 16155024.9, Mailed Date: Apr. 28, 2016, 7 Pages.
Second Chinese Office Action in Chinese Application No. 200980142641.8 dated Feb. 21, 2014, 7 pgs.
Taiwan Notice of Allowance in Taiwan Application No. 098135996 dated Apr. 14, 2015, 4 pgs.
Taiwan Search Report in Taiwan Patent Application No. 098135996, Dated Aug. 11, 2014, 16 pgs.
Third Chinese Office Action in Chinese Patent Application No. 200980142641.8, dated Aug. 26, 2014, 8 pgs.
Valian et al., "NetReg: An Automated DHCP Registration System," Proc. LISA '99: 13th System Administration Conference and Exhibition, pp. 139-147 (1999).
Valian Peter, et al., "NetReg: An Automated DHCP Registration System", Proceedings of LISA'99: 13th System Administration Conference and Exhibition, pp. 139-147 (1999).
Yesberg, et al., "QuARC: Expressive Security Mechanisms" New Security Paradigms Workshop, 1995, pp. 34-40.
Yiu, et al., "Lateral Error Recovery for Media Streaming in Application-Level Multicast", IEEE Transactions on Multimedia, vol. 8, No. 2, Apr. 2006, pp. 14.
Yiu, et al., "VMesh: Distributed Segment Storage for Peer-to-Peer Interactive Video Streaming", IEEE Journal on Selected Areas in Communications, vol. 25, No. 9, Dec. 2007, pp. 15.
CN1652515A (en) 2005-08-10 application
US6466984B1 (en) 2002-10-15 Method and apparatus for policy-based management of quality of service treatments of network data traffic flows by integrating policies with application programs
US7155502B1 (en) 2006-12-26 Methods, apparatuses and systems facilitating distribution of updated traffic identification functionality to bandwidth management devices
US20050149204A1 (en) 2005-07-07 Configuring network settings using portable storage media
US6622170B1 (en) 2003-09-16 System and method for DEN/LDAP client database access with a backoff capability
US20050091357A1 (en) 2005-04-28 Network and interface selection on a computing device capable of establishing connections via multiple network communications media
US7849497B1 (en) 2010-12-07 Method and system for analyzing the security of a network
US7545748B1 (en) 2009-06-09 Classification and management of network traffic based on attributes orthogonal to explicit packet attributes
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAHL, PRADEEP;CORBETT, CHRISTOPHER J.;KHAKI, MOHAMED JAWAD;REEL/FRAME:033043/0783