Abstract:
Greater network utilization is implemented through dynamic network reconfiguration and allocation of network services and resources based on the data to be transferred and the consumer transferring it. A hierarchical system is utilized whereby requests from lower layers are aggregated before being provided to upper layers, and allocations received from upper layers are distributed to lower layers. To maximize network utilization, paths through the network are reconfigured by identifying specific types of packets that are to be flagged in a specific manner, and then by further identifying specific routing rules to be applied in the transmission of such packets. Network reconfiguration is performed on an incremental basis to avoid overloading a path, and capacity can be reserved along one or more paths to prevent such overloading. Background data is agnostic as to specific transmission times and is utilized to prevent overloading due to reconfiguration.
Abstract:
A bid-based network sells network capacity on a transaction-by-transaction basis in accordance with bids placed on transactions. A transaction is the transmission of a quantum of data across at least some portion of the network, where the quantum of data can be as small as a single packet. Bids for network capacity are ranked in order of monetary value, or other criteria relevant to the network service provider. The amount charged to the highest bidder is based on the maximum bid of the next highest bidder. Bids are evaluated on a real-time basis at the time when the link is ready to transmit data. An automated system makes individual bids at each link through which data is transmitted and can take into account additional criteria that can be specified as part of the bid information, including latency and routing requirements. Bid information is passed with data through the network.
Abstract:
An environment is described in which a processing system provides application-level usage information to users. In one scenario, for example, the processing system may provide personal usage information to a user who is operating a user device. The personal usage information itemizes the amount of data (and/or other resources) that has been consumed by each application run by the user device. In another scenario, the processing system may provide expected usage information associated with at least one candidate application provided by a marketplace system. The expected usage information describes an expected consumption of data (and/or other resources) by the candidate application upon running the candidate application by the user device. The processing system can tailor the expected usage information that it sends to a particular user based on user profile data. The user profile data describes a manner in which users operate applications.
Abstract:
An exemplary system includes a front-end component, one or more distributed computation and storage (DCS) components, and a location services component. The front-end component is configured to receive requests for resources in a data center, associate each request with identifying information, locate resources for each request and store, in a log file, the identifying information. The DCS components are configured to acquire and analyze log file information to decide if resources associated with requests should be migrated to a data center in a different geographical location. The location service component is configured to receive decisions made by the DCS components and inform the front-end component of decisions to migrate resources to a data center in a different geographical location, thereby allowing the front-end component to re-direct future requests for the migrated resources to the data center in the different geographical location.
Abstract:
An exemplary system includes a front-end component, one or more distributed computation and storage (DCS) components, and a location services component. The front-end component is configured to receive requests for resources in a data center, associate each request with identifying information, locate resources for each request and store, in a log file, the identifying information. The DCS components are configured to acquire and analyze log file information to decide if resources associated with requests should be migrated to a data center in a different geographical location. The location service component is configured to receive decisions made by the DCS components and inform the front-end component of decisions to migrate resources to a data center in a different geographical location, thereby allowing the front-end component to re-direct future requests for the migrated resources to the data center in the different geographical location.
Abstract:
Using location-independent names to identify content, a service for mapping endpoint requests to requested content. Content requested by an endpoint of the network is mapped to a dynamic "swarm" of server, peer, or other endpoints capable of supporting the content download. Content names are mapped to a dynamically generated content swarm, presenting a current set of hosts, which can provide the requested content. Optionally, varying degrees of explicit visibility into routing paths and the performance tradeoffs between those routing paths is supported. Based on a set of class of service parameters for a given request for content, a host can initiate route selection based on class of service parameters, predicated on routing metrics maintained by the network by cooperating endpoints and/or network routers.
Abstract:
In a network management system, dependency relationships of network clients and network elements are computed. In an implementation, a dependency graph is generated based on the relationships, and the probabilities of problems associated with the network client and network element are determined based on the dependency graph.
Abstract:
An exemplary system includes a front-end component, one or more distributed computation and storage (DCS) components, and a location services component. The front-end component is configured to receive requests for resources in a data center, associate each request with identifying information, locate resources for each request and store, in a log file, the identifying information. The DCS components are configured to acquire and analyze log file information to decide if resources associated with requests should be migrated to a data center in a different geographical location. The location service component is configured to receive decisions made by the DCS components and inform the front-end component of decisions to migrate resources to a data center in a different geographical location, thereby allowing the front-end component to re-direct future requests for the migrated resources to the data center in the different geographical location.