Patent Application
20180278478
The subject matter of this disclosure relates in general to the field of computer networks, and more specifically for management of entities and resources within a computer network.
A managed network, such as an enterprise private network (EPN), may contain a large number of entities distributed across the network. These entities include, for example, nodes, endpoints, machines, virtual machines, containers (an instance of container-based virtualization), and applications. In addition to being different types, these entities may be grouped in different departments, located in different geographical locations, and/or serve different functions.
An expansive or thorough understanding of the network can be critical for network management tasks such as anomaly detection (e.g., network attacks and misconfiguration), network security (e.g., preventing network breaches and reducing network vulnerabilities), asset management (e.g., monitoring, capacity planning, consolidation, migration, and continuity planning), and compliance (e.g. conformance with governmental regulations, industry standards, and corporate policies). Traditional approaches for managing large networks require comprehensive knowledge on the part of highly specialized human operators because of the complexities of the interrelationships among the entities.
In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
The detailed description set forth below is intended as a description of various configurations of embodiments and is not intended to represent the only configurations in which the subject matter of this disclosure can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the subject matter of this disclosure. However, it will be clear and apparent that the subject matter of this disclosure is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject matter of this disclosure.
Large networks often require comprehensive knowledge on the part of highly specialized human operators (e.g., network administrators) to effectively manage. However, controls available to the human operators are not very flexible and the human operators with the specialized knowledge able to manage the network(s) are often not the individuals with a higher level understanding of how the network should operate with respect to certain applications or functionalities. Furthermore, once a change in network management is executed, it is often difficult to roll back the changes, make alterations, or understand the changes, even for network operators.
The disclosed technology addresses the need in the art for a more intuitive way to manage a network and a way to manage the network in a more targeted manner. For example, many networks may be secured using access control lists (ACLs) implemented by routers and switches to permit and restrict data flow within the network. When an ACL is configured on an interface, the network device examines data packets passing through the interface to determine whether to forward or drop the packet based on the criteria specified within the ACLs. Each ACL includes entries where each entry includes a destination target internet protocol (IP) address, a source target IP address, and a statement of permission or denial for that entry.
The ACLs, however, may be difficult for application developers and other users with limited knowledge of network engineering to understand and use. A development team that builds a particular application, set of applications, or function(s) (e.g., an “application owner”) is typically not responsible for managing an enterprise network and are not expected to have a deep understanding of the network. The application owner understands at a high level how certain applications or functions should operate, which entities should be allowed or restricted from communicating with other entities, and how entities should be allowed or restricted from communicating with other entities (e.g., which ports and/or communication protocols are allowed or restricted). In order to implement desired network policies, the application owner must contact a network operator and communicate their objectives to the network operator. The network operator tries to understand the objectives and then creates ACL entries that satisfy the application owner's objectives.
Even relatively simple network policies take hundreds, thousands, or more ACL entries to implement and ACLs often end up containing millions of entries. For example, to implement a simple network rule where a first subnet of machines cannot communicate with a second subnet of machines requires 2(m×n) ACL entries for a number of m endpoints in the first subnet and a number of n endpoints in the second subnet to explicitly list out each IP address in the first subnet that cannot send data to each IP address in the second subnet and each IP address in the second subnet cannot send data to each IP address in the first subnet. The size of the ACLs can further complicate matters making intelligently altering the ACLs increasingly difficult. For example, if an application owner wants to alter the implemented network policies, it is difficult for the application owner or the network operator to know which ACL entries were created based on the original network policy and, as a result, difficult to identify ACL entries to add, delete, or modify based on the alteration of the network policies.
Furthermore, traditional ACLs permit and restrict data flow within the network at the machine level. For example, ACL entries permit or restrict communication based on a destination target internet protocol (IP) address and a source target IP address. However, in some cases, applications on one network entity (e.g., a physical server, virtual machine, container, etc.) should be able to communicate with other applications on a different network entity, but other communications between the entities should be restricted for security reasons (e.g., some hackers may take advantage of broad traditional ACL entries and use applications to gain access to other areas of the network). Traditional ACL entries are unable to accommodate for more tailored control of network traffic.
Various embodiments of the subject technology address these and other technical problems by providing an intent driven network policy platform that allows both application owner and network operators to define network policies in a more understandable manner and provides these users with finer levels of controls.
Detailed Description
Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustrative purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without departing from the spirit and scope of the disclosure.
Various embodiments relate to an intent driven network policy platform configured to ingest network data and generate an inventory of network entities. The network policy platform receives a user intent statement, translates the intent into network policies, and enforces the network policies.
The network environment 100 includes one or more network agents 105 configured to communicate with an intent driven network policy platform 110 via enforcement front end modules (EFEs) 115. The intent driven network policy platform 110 is shown with one or more EFEs 115, a user interface module 120, a coordinator module 125, an intent service module 130, an inventory store 150, and a policy store 155. In other embodiments, the intent driven network policy platform 110 may include additional components, fewer components, or alternative components. The network policy platform 110 may be implemented as a single machine or distributed across a number of machines in the network.
Each network agent 105 may be installed on a network entity and configured to receive network policies (e.g., enforcement policies, configuration policies, etc.) from the network policy platform 110 via the enforcement front end modules 115. After an initial installation on a network entity (e.g., a machine, virtual machine, or container, etc.), a network agent 105 can register with the network policy platform 110 and communicate with one or more EFEs to receive network policies that are configured to be applied to the host on which the network agent 105 is running. In some embodiments, the network policies may be received in a high-level, platform independent format. The network agent 105 may convert the high-level network policies into platform specific policies and apply any number of optimizations before applying the network policies to the host network entity. In some embodiments, the high-level network policies may be converted at the network policy platform 110.
Each network agent 105 may further be configured to observe and collect data and report the collected data to the intent driven network policy platform 110 via the EFEs 115. The network agent 105 may collect policy enforcement related data associated with the host entity such as a number of policies being enforced, a number of rules being enforced, a number of data packets being allowed, dropped, forwarded, redirected, or copied, or any other data related to the enforcement of network policies. The network agent 105 may also collect data related to host entity performance such as CPU usage, memory usage, a number of TCP connections, a number of failed connection, etc. The network agent 105 may also collect other data related to the host such as an entity name, operating system, entity interface information, file system information, applications or processes installed or running, or disks that are mounted.
The enforcement front end modules (EFEs) 115 are configured to handle the registration of the network agents 105 with the network policy platform 110, receive collected data from the network agents 105, and store the collected data in inventory store 150. The EFEs may be further configured to store network policies (high-level platform independent policies or platform specific policies) in memory, periodically scan a policy store 155 for updates to network policies, and notify and update network agents 105 with respect to changes in the network policies.
The user interface 120 receives input from users of the network policy platform 110. For example, the user interface 120 may be configured to receive user configured data for entities in the network from a network operator. The user configured data may include IP addresses, host names, geographic locations, departments, functions, a VPN routing/forwarding (VRF) table, or other data for entities in the network. The user interface 120 may be configured to collect the user configured data and store the data in the inventory store 150.
The user interface 120 may also be configured to receive one or more user intent statements. The user intent statements may be received from a network operator, application owner, or other administrator or through another entity via an application programming interface (API). A user intent statement is a high-level expression of one or more network rules that may be translated into a network policy.
The user interface 120 may pass a received user intent statement to the intent service 130 where the intent service 130 is configured to format the user intent statements and transform the user intent statement into network policies that may be applied to entities in the network. According to some embodiments, the intent service 130 may be configured to store the user intent statements, either in formatted or non-formatted form, in an intent store. After the user intent statements are translated into network policies, the intent service 130 may store the network policies in policy store 155. The policy store 155 is configured to store network policies. The network policies may be high-level platform independent network policies or platform specific policies. In some embodiments, the policy store 155 is implemented as a NoSQL database.
The intent service 130 may also track changes to intent statements and make sure the network policies in the policy store are up-to-date with the intent statements in the intent store. For example, if a user intent statement in the intent store is deleted or changed, the intent service 130 may be configured to located network policies associated with the deleted user intent statement and delete or update the network policies as appropriate.
The coordinator module 125 is configured to assign network agents 105 to EFEs. For example, the coordinator 125 may use a sharding technique to balance load and improve efficiency of the network policy platform 110. The coordinator 125 may also be configured to determine if an update to the policy store is needed and update the policy store accordingly. The coordinator 125 may further be configured to receive data periodically from the network agents 105 via the EFEs 115, store the data in the inventory store 150, and update the inventory store 150 if necessary.
The inventory store 200 may receive user configured data from the user interface 120 and data received from the network agents 105 via the EFEs 115 and store the data in records or entries associated with network entities managed by the network policy platform 110. Each record in the inventory store 200 may include attribute data for a network entity such as one or more entity identifiers (e.g., a host name, IP address, MAC addresses, hash value, etc.), a geographic location, an operating system, a department, interface data, functionality, a list of one or more annotations, file system information, disk mount information, top-of-rack (ToR) location, and a scope.
In some embodiments, the inventory store 200 may also include entity performance and network enforcement data either together with the attribute data or separately in one or more separate data stores. The performance and network enforcement data may include CPU usage, memory usage, a number of TCP connections, a number of failed connections, a number of network policies, or a number of data packets that have been allowed, dropped, forwarded, or redirected. The inventory store 200 may include historical performance or enforcement data associated with network entities or metrics calculated based on historical data.
A user intent statement is a high-level expression of that may be translated into one or more network policies. A user intent statement may be composed of one or more filters and at least one action. The filters may include inventory filters that identify network entities on which the action is to be applied and flow filters that identify network data flows on which the action is to be applied.
For example, if a user wished to identify all network entities located in Mountain View, Calif. (abbreviated MTV in the location column of the inventory store), the inventory filter “Location==MTV” may be used. If a user wished to identify all network entities located in a Research Triangle Park facility in North Carolina (abbreviated RTP in the location column of the inventory store), the inventory filter “Location==RTP” may be used. Inventory filters may also identify relationships between two or more sets of entities (e.g., a union or intersection of sets). For example, if a user wished to identify all network entities located in Mountain View, Calif. and running Windows 8 operating system, the inventory filter “Location==MTV and OS==Windows8” may be used.
A flow filter identifies network data flows. For example, if a user wished to identify all data flows from network entities in Mountain View to network entities in the Research Triangle Park facility, the following flow filter may be used:
Source:Location==MTV
Destination:Location==RTP
Each filter may further be defined beforehand and assigned a name for more convenient use. For example, the inventory filter “Location==MTV” may be assigned the name “MTV_entities” and the inventory filter “Location==RTP” may be assigned the name “RTP_entities.” As a result, a user may use the following to achieve the same result as the above example flow filter:
Source:MTV_entities
Destination:RTP_entities
Different actions may be applied to different filters. For example, actions applicable to inventory filters may include annotation and configuration actions. Annotating actions adds tags or labels to network items in the inventory store or flow data. Annotations may help network operators identify network entities. Configuration actions may be used to configure network entities. For example, some configuration actions may be used to set a CPU quota for certain applications, processes, or virtual machines. Other configuration actions may enable or disable monitoring of certain metrics, collection and transmittal of certain data, or enforcement of certain network policies. Some configuration actions may also be able to enable or disable certain modes within a network entity. For example, some entities may be configured to run in a “high visibility mode” in which most metrics and data (e.g., full time series data) are collected and transmitted to the network policy platform for analysis or in “low visibility mode” in which only a small subset of the available metrics and data are collected and transmitted. Some configuration actions are able to enable or disable these modes.
Actions applicable to flow filters may include annotation or network enforcement actions. Network enforcement actions include, for example, allowing data packets, dropping data packets, copying data packets, redirecting data packets, encrypting data packets, or load balance across network entities.
Using the above examples, a user that wishes to drop all data flowing from entities in Mountain View to entities in Research Triangle Park may use the following user intent statement:
Source:MTV_entities
Destination:RTP_entities
Action:Drop
User intent statements may further specify types of communications or communication protocols used, ports used, or use any other filter to identify a network entity or network flow on which to apply an action. For example, if the user only wishes to drop transmission control protocol (TCP) communications out of port 80 for these network entities, the following user intent statement may be used instead:
Source:MTV_entities
Destination:RTP_entities
Action:Drop
Protocol:TCP
Port:80
In another example, to disable all incoming connections to network entities running a Windows 8 operating system, a user can utilize the following user intent statement:
Source:*
Destination:Win8_Filter
Action:Drop
In the above user intent statement, “Win_Filter” is the name of an inventory filter that includes “OS==Windows8.”
The example user intent statements above are presented for illustrative purposes. In some embodiments, user intent statements, inventory filters, flow filters, or actions may appear in different formats or even in a natural language format. For example,
At operation 505, the system may generate an inventory store that includes records for network entities in the network. The records may be created or updated based on configuration data received from a network operator. The configuration data may include various attributes of certain network entities. The attributes may include, for example, an internet protocol (IP) address, a host name, a geographic location, or a department. The configuration data may also include annotations, labels, VPN routing/forwarding (VRF) information, interface information, or any other data that may be used to identify one or more network entities.
The records may further be created, updated, or supplemented with information observed by network agents and reported to the network policy system by the network agents. This information may include operating system information, hostnames, interface information, entity identifiers, policy enforcement information, or data related to entity performance. Policy enforcement information may include a number of policies being enforced, a number of rules being enforced, a number of data packets being allowed, dropped, forwarded, redirected, or copied, or any other data related to the enforcement of network policies. Data related to entity performance may include CPU usage, memory usage, a number of TCP connections, a number of failed connection, applications or processes installed or running, disks that are mounted, or other time series data.
At operation 510, the system receives a user intent statement that includes at least one filter and an action. The user intent statement may be received from a network operator, application owner, or other administrator via a user interface or through another party or service via an application program interface (API). The filter may be an inventory filter configured to help identify network entities on which the action is to be applied or a flow filter configured to help identify network data flows on which the action is to be applied. The action may be an enforcement action, a configuration action, or an annotation action.
The system may query the inventory store to identify network entities to which the user intent statement applies at operation 515. For example, system may query the inventory store using the one or more filters found in the user intent statement to identify network entities that match the conditions of the filters. The filters may include one or more attributes that can be used to narrow down the network entities to only those to which the action is to be applied. The attributes may be, for example, an entity type (e.g., machine, virtual machine, container, process, etc.), an IP subnet, an operating system, or any other information that may be found in the inventory store and used to identify network entities.
At operation 520, the system generates network policies that apply the action to the network entities identified by the query. According to some embodiments, the network policies for user intent statements that include a flow filter or an enforcement action may be implemented in the form of one or more access control lists (ACLs). In some embodiments, network policies for user intent statements that include an annotation action or configuration action may be implemented in the form of instructions to the network entity or a network agent to implement the actions.
The system then enforces the network policies at operation 525. According to some embodiments, some network policies may be enforced on the system. However, in some embodiments, the system transmits the network policies to one or more network agents configured to implement the network policies on the network entities.
According to various embodiments of the disclosure, a user or service is able to provide a user intent statement that the system uses to generate multiple network policies. Accordingly, the user need not spend time and resources explicitly crafting each network policy. Instead, the user may specify a reduced number of user intent statements that express the user's network management desires. Furthermore, the user intent statements are more understandable to network operators and application owners and the system is configured to take the user intent statements and translate the statements into network policies that network agents or network entities may use to implement the user's network management desires.
In some embodiments, the user intent statements are translated into platform independent network policies and stored in the policy store. To enforce these network policies, the network policy system transmits the platform independent network policies to network agents running on network entities, where the platform independent network policies are converted into platform specific network policies and implemented.
After an initial installation on a network entity 605, a network agent 610 can register with the network policy system 650. According to some embodiments, the network agent 610 may read the Basic Input/Output System (BIOS) universally unique identifier (UUID) of the network entity 605, gather other host specific information, and access an agent identifier for the network agent 610. The network agent 610 generates a registration request message containing the agent identifier, host specific information (invluding the BIOS UUID) and transmits the registration request message to an EFE module 655. In some cases (e.g., when a network agent is just installed), the network agent 610 may not have an agent identifier. Accordingly, this field in the registration request message may be kept blank until one is assigned.
The EFE module receives the registration request message and, if the request message contains an agent identifier, the EFE module will validate that the BIOS UUID is the same as the BIOS UUID for the entry associated with the agent identifier in the inventory store. If the information matches, the agent identifier in registration request is validated and the network agent 610 is registered. The EFE module may generate a registration response message with the validated agent identifier and transmit the registration response message to the network agent. A BIOS UUID that does not match may indicate that the network agent's identity has changed. Accordingly, the EFE module may generate a new agent identifier, create an entry in the inventory store for the new agent identifier and transmit the new agent identifier to the network agent in the registration response message. If the network agent receives a registration response message that includes an agent identifier which is different from the agent identifier the network agent sent in the registration request message, the network agent will update its agent identifier and adopt the received agent identifier.
An EFE module 655 may send network policy configuration messages as a separate message or part of the registration response message. The network policy configuration messages may contain platform independent network policies to implement on the network entity 605 as well as version information. The network agent 610 receives a network policy configuration message and checks the currently applied policy version. If the policy version for the received network policy configuration message is lower than or equal to the applied version, the network agent 610 does not need to update the applied policies. If, on the other hand, the policy version is higher than the applied version, the network agent 610 will process the received network policy configuration message. In some embodiments, the network policies in the network policy configuration message may be in a platform independent format. The network agent 610 may convert the platform independent network policies into platform specific policies and apply any number of optimizations before applying the network policies to the network entity 605.
The network agent 610 may further be configured to observe and collect data and report the collected data to the network policy system 650 via the EFE modules 655. The network agent 610 may collect policy enforcement related data associated with the host entity such as a number of policies being enforced, a number of rules being enforced, a number of data packets being allowed, dropped, forwarded, redirected, or copied, or any other data related to the enforcement of network policies. The network agent 610 may also collect data related to host entity 605 performance such as CPU usage, memory usage, a number of TCP connections, a number of failed connection, etc.
According to some embodiments, some of the information collected by the network agent 610 may be obtained by one or more sensors 625 of the network entity 605. The sensors 625 may be physical sensors or logical sensors and, in some embodiments, may be a part of the network agent 610 (e.g., a part of the agent enforcer 615 shown in
According to some embodiments, the network agent 610 may be partitioned into two or more portions with varying permissions or privileges in order to provide additional protections to the network entity 605. For example, in
The agent controller 620 is associated with an unprivileged status that does not grant the agent controller 620 certain privileges and may be unable to directly access system protected resources. The agent controller 620 is configured to communicate with the EFE modules 655 of the network policy system 650 via a Secure Sockets Layer (SSL) channel and pass critical data to the agent enforcer via an interprocess communication (IPC) channel 630. Interprocess communications (IPC) are communication channels provided by an operating system running on the network entity 605 that enable processes running on the network entity 605 to communicate and share data.
For example, the agent controller 620 may receive platform independent network policies from one or more EFE modules 655 and pass the network policies to the agent enforcer 615 via the IPC channel 630. The agent controller 620 may also receive data collected by the agent enforcer 615 (e.g., policy enforcement related data, data related to entity performance, or other data related to the network entity 605) via the IPC channel 630, generate a message containing the collected data, and transmit the message to one or more EFE modules 655.
The agent enforcer 615 is associated with a privileged status that provides the agent enforcer 615 with additional privileges with respect to the network entity 605. For example, the agent enforcer may directly access or manipulate the network entity's protected resources such as a system firewall, CPU usage, memory usage, sensors 625, or system interfaces. The agent enforcer 615 may be configured to manage registration of the network agent 610 and select which EFE modules 655 with which to communicate. The agent enforcer 615 may further validate network policies received from the network policy system 650 to ensure that the network policies do not violate any sanity checks or golden rules (e.g., a network policy that blocks communication from a port that communicates with EFE modules 655 may be ignored) and translate platform independent network policies received from the network policy system 650 to platform specific policies. The agent enforcer 615 may also maintain a policy cache, enforce platform specific network policies, and determine whether a network policy has been altered. The agent enforcer 615 may also monitors system metrics and policy enforcement metrics so that the data may periodically be sent to the network policy system 650 for analysis.
According to some embodiments, the agent enforcer 615 and the agent controller 620 may run independently and the separation of the agent enforcer 615 and the agent controller 620 allow for a more secure network agent 610 and network entity 605. For example, the agent enforcer 620 may have no external socket connections in order to reduce the number of vulnerable areas that malicious actors (e.g., hackers) may attack. Although the agent controller 620 communicates with the network policy system 650 via a SSL channel, damage caused by the corruption of the agent controller 620 is limited since the agent controller 620 is unable to directly access privileged resources and cannot enforce arbitrary network policies.
At operation 705, an agent controller of the network agent may receive a platform independent network policy from a network policy system. The platform independent network policy may be generated by the network policy system based on, for example, a user intent statement. The agent controller may transmit the platform independent network policy to an agent enforcer via an interprocess communication at operation 710. At operation 715, the agent enforce may determine implementation characteristics of the network entity. The implementation characteristics may include, for example, the operating system information of the network entity, port configurations, storage available to the network entity, accessories attached to the network entity, file system information, applications or processes installed or running on the network entity, etc.
At operation 720, the agent enforcer may generate one or more platform specific policies from the platform independent network policy based on the implementation characteristics and, at operation 725, implement the platform specific policies on the network entity. Once the platform specific policies are implemented, the agent enforcer may further monitor the network entity to collect data to be reported back to the network policy system or to identify policies that have been altered.
An altered network policy may indicate that a user (e.g., a system administrator) or a malicious actor (e.g., a hacker or malicious code) may be trying to change the network policies and a report should be sent to the network policy system for notification purposes. For example, an agent enforcer may identify that a policy in the platform specific policies has been altered and revert the altered policy back to a previous state. The agent enforcer may generate a report detailing the alteration of the network policy and transmit the report, via the IPC channel, to the agent controller where the agent controller may transmit the report to the network policy system.
According to some embodiments, the network agent is able to monitor the network entity and collect data to be sent to the network policy system for analysis.
At operation 805, an agent enforcer of a network agent may implement the network policies on the network entity. As described above, the agent enforcer may have a privileged status with respect to the network entity and have permission to take certain actions, access more sensitive resources, and make privileged system calls. The agent enforcer may also be allowed to access certain data that is to be reported to the network policy system at operation 810.
This information may include, for example, policy enforcement data associated with the implementation of the network policies on the network entity, system performance data associated with operation of the network entity, or other entity data. The policy enforcement data may include, for example, a number of policies being enforced, a number of times each network policy is enforced, a number of data packets being allowed, dropped, forwarded, redirected, or copied, or any other data related to the enforcement of network policies. The performance data may include, for example, central processing unit (CPU) usage, memory usage, a number of inbound and/or outbound connections over time, a number of failed connection, etc. Entity data may include, for example, an agent identifier, an operating system, a hostname, entity interface information, file system information, applications or processes installed or running, or disks that are mounted. In some embodiments, one or more sensors are configured to collect and store the data and the agent enforcer is able to access the data via an application programming interface (API) for the sensors.
At operation 815, the agent enforcer may transmit the data to an agent controller on the system via an interprocess communication (IPC) channel. The agent controller receives the data and generates a report that includes the data at operation 820 and transmits the report to the network policy system at operation 825.
According to various embodiments, the network policy system may use the data to provide network administrators with reports on a whole network ecosystem and/or individual network entities. The network policy system may also use the data to monitor network performance, identify threats to the network, and/or manage the network policies for the network. For example, depending on which policy rules being violated and/or whether they are being violated on one, a small group, or across the network, the network policy system may be able to characterize of identify the threat to the network. Based on historical policy enforcement data, the network policy system may be able to determine whether a threat is new or active.
According to some embodiments, the network policy system may determine that a policy is never violated based on the policy enforcement data. The larger number of rules increases the computational overhead of the network, the network policy system, and the network entities. To increase efficiency, the network policy system may remove the policy that is never violated.
To enable user interaction with the computing system 900, an input device 945 can represent any number of input mechanisms, such as a microphone for speech, a touch-protected screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 935 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing system 900. The communications interface 940 can govern and manage the user input and system output. There may be no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
Storage device 930 can be a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 925, read only memory (ROM) 920, and hybrids thereof.
The storage device 930 can include software modules 932, 934, 936 for controlling the processor 910. Other hardware or software modules are contemplated. The storage device 930 can be connected to the system bus 905. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 910, bus 905, output device 935, and so forth, to carry out the function.
The chipset 960 can also interface with one or more communication interfaces 990 that can have different physical interfaces. The communication interfaces 990 can include interfaces for wired and wireless LANs, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 955 analyzing data stored in the storage device 970 or the RAM 975. Further, the computing system 900 can receive inputs from a user via the user interface components 985 and execute appropriate functions, such as browsing functions by interpreting these inputs using the processor 955.
It will be appreciated that computing systems 900 and 950 can have more than one processor 910 and 955, respectively, or be part of a group or cluster of computing devices networked together to provide greater processing capability.
For clarity of explanation, in some instances the various embodiments may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.
