Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer's business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.
Examples described herein relate to systems and methods for tiered updating of configuration data. Updated configuration data is transmitted to different tiers of nodes. The nodes of a first tier are commanded to use the updated configuration data. After waiting to see if any nodes of the first tier communicate a fault after using the updated configuration data, for each of the additional tiers in the CDN it is sequentially repeated to: transmit a command to the nodes of that additional tier to use the updated configuration data; and after waiting to see if any nodes of any tier communicate a fault after using the updated configuration data, transmitting a command to the nodes of another additional tier to use the updated configuration data.
H04L 41/0859 - Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
A network interface system defines standardized network service requests and related abstracted tasks. In examples, commands needed to configure particular network elements are dependent on the network being utilized and/or the network element(s) being utilized. The network interface system may include a standardization layer, an abstraction layer, and an application programming interface for each of a variety of available networks. Upon a request for a network service, the related abstracted tasks may be translated into network-specific commands to configure network elements of disparate networks to provide the requested service.
H04L 41/5051 - Service on demand, e.g. definition and deployment of services in real time
H04L 41/022 - Multivendor or multi-standard integration
H04L 41/12 - Discovery or management of network topologies
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 41/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
4.
EDGE COMPUTE ENVIRONMENT AUTOMATIC SERVER CONFIGURATION TOOL
A server configuration tool is presented for autonomously configuring servers located in a network. The tool may autonomously configure multiple servers in parallel based on individual states of the servers, which may be periodically and simultaneously determined. For example, the tool may determine which action to take to begin or continue configuring the server based on the present state of each server. Server states (and corresponding actions) can be edited through a user interface to alter the server configuration process without code changes. At any one time, multiple servers may be in different states requiring different configuration operations to configure the servers to be ready for use. The present systems and methods can be used to move multiple servers iteratively through different configuration actions based on the individual state of each server and to perform non-conflicting configuration operations for multiple servers in parallel.
H04L 41/0806 - Configuration setting for initial configuration or provisioning, e.g. plug-and-play
H04L 41/0893 - Assignment of logical groups to network elements
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 43/0817 - Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
Systems and methods for recommending and implementing computing services at a provider network site are provided. A provider network may comprise multiple provider sites, such as edge computing sites. Edge computing sites may not be uniform ? e.g., they may differ in computing capability, security certification, capacity for expansion, data storage availability, type of network connectivity, etc. An optimization system uses both service information and optimization criteria to determine one or more optimized provider site(s) for hosting a computing service. Further, service information and optimization criteria may be stored and updated to allow the computing service to be dynamically moved in response to a change event, such as a site failure or a determination that an improvement metric exceeds a threshold for a minimum period of time.
H04L 41/5025 - Ensuring fulfilment of SLA by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
H04L 41/0896 - Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
H04W 48/18 - Selecting a network or a communication service
H04L 67/52 - Network services specially adapted for the location of the user terminal
A tool is provided to configure an edge compute environment of a network. The edge compute network configuration tool may generate a configuration process for instantiating an edge compute environment at an edge site of a network including configuring one or more of the components of the edge compute environment. The configuration process may include generating automatically executed configuration instructions that communicate with the devices of the edge compute environment to configure operational processes of the devices, provision communication ports, establish one or more network addresses with the devices, etc. In some instances, the edge compute configuration tool may execute one or more micro-services to communicate with and control configuration of the devices of the edge compute environment. In addition, in some instances, a content delivery network may be used to deliver configuration data to the device being configured.
H04L 41/5051 - Service on demand, e.g. definition and deployment of services in real time
H04L 41/0806 - Configuration setting for initial configuration or provisioning, e.g. plug-and-play
H04L 41/084 - Configuration by using pre-existing information, e.g. using templates or copying from other elements
H04L 41/04 - Network management architectures or arrangements
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
A system and method for providing on-demand edge compute. The system may include an orchestrator that provides a UI and controls an abstraction layer for implementing a workflow for providing on-demand edge compute. The abstraction layer may include a network configuration orchestration (NCO) system (e.g., a Network-as-a-Service (NaaS) system) and an API that may provide an interface between the orchestrator and the NCO. The API may enable the orchestrator to communicate with the NCO for receiving requests that enable the NCO to integrate with existing network controllers, orchestrators, and other systems and perform various network provisioning tasks (e.g., to build and provision a communication path between server instances). The various tasks, when executed, may provide end-to-end automated network provisioning services as part of providing on-demand edge compute service to users. The API may further enable the ECS orchestrator to receive information from the NCO, (e.g., network resource information, status messages).
H04L 41/5051 - Service on demand, e.g. definition and deployment of services in real time
H04L 41/04 - Network management architectures or arrangements
H04L 41/40 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 41/342 - Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
H04L 41/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
8.
SYSTEMS AND METHODS FOR PROVIDING ENHANCED SECURITY IN EDGE COMPUTING ENVIRONMENTS
Examples of the present disclosure describe systems and methods for providing enhanced security in edge computing environments. A first aspect describes a method for moving security features dynamically applied to an application at a first deployment location to an application at a second deployment location. A second aspect describes a method for locally expanding/contracting an instance of a deployed application. A third aspect describes a method for redirected network traffic associated with detected malicious conduct from a first application deployment environment to a secured second application deployment environment. A fourth aspect describes a method for performing multi-stage network traffic filtering.
A system and method for providing on-demand edge compute. The system may include an orchestrator that provides a UI and that contorls an abstraction layer for implementing a workflow for providing on-demand edge compute. The abstraction layer may include a server configuration orchestration (SCO) system (e.g., a Metal-as-a-Service (MaaS) system) and API that may provide an interface between the orchestrator and the SCO. The API may enable the orchestrator to communicate with the SCO for receiving requests that enable the SCO to integrate with existing compute resources to perform various compute provisioning tasks (e.g., to build and provision a server instance). The various tasks, when executed, may provide on-demand edge compute service to users. The SCO API may further enable the ECS orchestrator to receive information from the SCO (e.g., compute resource information, status messages).
H04L 41/5051 - Service on demand, e.g. definition and deployment of services in real time
H04L 41/04 - Network management architectures or arrangements
H04L 41/0895 - Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 41/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
10.
UPDATING CONFIGURATION DATA IN A CONTENT DELIVERY NETWORK
Examples described herein relate to systems and methods for updating configuration data. A method implemented by a computer may include receiving updated configuration data from a control core. Earlier configuration data with a time stamp may be stored in an archive storing additional earlier configuration data with respective time stamps. Responsive to the updated configuration data not being faulty, content may be distributed using the updated configuration data. Responsive to the updated configuration data being faulty, a fault may be communicated to a monitoring system, and commands from the monitoring system may be received and executed to: revert to an earlier configuration data corresponding to a specific earlier time, and disregard any further updated configuration data from the control core until instructed otherwise by the monitoring system. Content may be distributed using the earlier configuration data to which the computer is reverted.
Examples of the present disclosure relate to hostname pre-localization. In examples, a service uses a content distribution network (CDN) to provide at least a part of the computing functionality associated with the service. A pre-localized hostname may be used to direct the client computing device to a specific edge server of the CDN that is associated with the computing functionality. In examples, a service receives an initiation request from a client computing device for the computing functionality provided by the CDN. The service generates a pre-localization request comprising pre-localization information and provides the pre-localization request to the CDN. Accordingly, the CDN generates a pre-localized hostname associated with an edge server based on the pre-localization information. The pre-localized hostname is provided to the service, which is then provided to the client computing device, thereby directing the client computing device to the specific edge server of the CDN.
Examples described herein relate to systems and methods for containing a faulty stimulus in a Content Delivery Network, CDN. Every received stimulus including the faulty stimulus is listed in a suspect list, and is implicitly tested by acting upon those stimuli by a software application. Responsive to successfully acting upon a stimulus besides the faulty stimulus, each non-faulty stimulus is deleted from the suspect list and made available to a downstream node. Responsive to acting upon the faulty stimulus, the software application crashes which leaves the faulty stimulus listed in the suspect list. The software application then restarts and deems the faulty stimulus as being faulty based upon the faulty stimulus still being listed in the suspect list after the restart. The faulty stimulus is not made available to a downstream node. The stimuli relate for example to configuration commands to configure the nodes of the CDN.
A DNS resolution request for a hostname of a CDN is received. An edge server of the CDN may be identified, which may be associated with a subnet. The subnet is used to generate a response IP address, where the remaining bits of the response IP address may be used to store requestor information (e.g., a requestor IP address). When a client computing device uses the response IP address to access the edge server, requestor information is extracted and associated with client computing device information (e.g., an IP address and/or location, etc.) in an association record. Association records may be used to determine predicted characteristics for devices served by a requestor. When the authoritative DNS server resolves a request from the requestor, such predicted characteristics may be used rather than relying solely on information about a requestor. Thus, an edge server proximate to the predicted location may be returned instead.
Examples described herein relate to systems and methods for storing content items. The methods may be implemented by a computer comprising a processor, primary storage device, secondary storage, device and network interface. The primary storage device may receive, via the network interface, a plurality of content items responsive to respective requests from clients. The plurality of content items may be distributed, via the network interface, from the primary storage device to clients responsive to the respective requests from the clients. The processor may generate a dynamic priority list for the content items based on the respective requests from the clients over time, and may write, based on the dynamic priority list, only a subset of the content items to the secondary storage device.
Aspects of the present disclosure involve systems and methods for a service activation system in a telecommunications network that utilizes one or more generic container files for building the configuration file to instantiate the service on the network. A request for service may be received from an order entry system that includes specific information about the requested service. A collection of generic configuration files may be selected based on the information included in the service order and arranged to build a configuration file to be executed on the network. The service activation system may also include a component or group of components to verify a received service order and alter the service order with default information or data where applicable. The configuration file may also be executed on the network through one or more drivers communicating with the affected devices to configure the one or more network devices.
A security platform of a data network is provided that includes security services for computing devices in communication with the data network. The security platform may apply a security policy to the computing devices when accessing the Internet via a home network (or other customer network) and when accessing the Internet via a public or third party network. To provide security services to computing devices via the home network, the security platform may communicate with a security agent application executed on the router (or other gateway device) of the home network. In addition, each of the devices identified by the security profile for the home network may be instructed or otherwise be provided a security agent application for execution on the computing devices. The security agent application may communicate with the security platform when the computing device connects to the Internet over a third party or public access point.
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for an orchestrator device associated with a scrubbing environment of a telecommunications network that receives one or more announced routing protocol advertisements from a customer device under an attack. In response to receiving the announcement, the orchestrator may configure one or more scrubbing devices of the network to begin providing the scrubbing service to packets matching the received routing announcement. A scrubbing service state for the customer may also be obtained or determined by the orchestrator. With the received route announcement and the customer profile and state information, the orchestrator may provide instructions to configure the scrubbing devices of the network based on the received information to dynamically automate scrubbing techniques without the need for a network administrator to manually configure the scrubbing environment or devices.
A dynamic controller to automatically generate layer (3) network connections between devices and/or networks associated with a virtual computing environment in response to a request for such connections is provided such that communications associated with the computing environment may be transmitted between the endpoints. For example, the dynamic controller may connect one or more cloud service provider networks, one or more customer-controlled data centers, one or more customer networks, and the like, based on information provided in a connection request. A layer (3) communication controller may also be instantiated within a core network that manages the flow of communications between the connected networks, such as by translating messages between the connected networks so that messages intended for a connected network may match the supported communication protocols of that network and/or providing one or more security features to the transmitted communications.
H04L 69/325 - Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the network layer [OSI layer 3], e.g. X.25
Novel tools and techniques for predictive AI automated cloud service turn-up are provided. A system includes an AI pipeline and service orchestration server coupled to the Ai pipeline. The AI pipeline includes a processor and non-transitory computer readable media comprising instructions executable by the processor to obtain customer usage data associated with a first customer from one or more customer data sources, wherein the customer usage data is indicative of usage patterns of one or more cloud services by the first customer, and generate, via a predictive model, predicted usage data based on the customer usage data, wherein the predicted usage data includes a prediction of an individual cloud service of the one or more cloud services predicted to be used by the first customer. The service orchestration server may be configured to turn-up the individual cloud service based on the predicted usage data.
H04L 41/16 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
H04L 41/5054 - Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
Examples described herein relate to apparatuses and methods for managing caching for a content delivery system, which may include receiving a content request indicating that the caching agent is requesting content data for a client, filling the content data in a first cache storage of the business logic agent, providing the cached content data to the caching agent, and while a second cache storage of the caching agent is being filled with the content data, maintaining the cached content data in response to receiving additional content requests from the caching agent. The additional content requests may indicate that the caching agent is requesting the same content data for additional clients.
Implementations described and claimed herein provide systems and methods for intelligent node type selection in a telecommunications network. In one implementation, a customer set is obtained for a communications node in the telecommunications network. The customer set includes an existing customer set and a new customer set. A set of customer events is generated for a node type of the communications node using a simulator. The set of customer events is generated by simulating the customer set over time through a discrete event simulation. An impact of the customer events is modeled for the node type of the communications node. The node type is identified from a plurality of node types for a telecommunications build based on the impact of the customer events for the node type.
H04Q 9/00 - Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
22.
SERVICE AREA DETERMINATION IN A TELECOMMUNICATIONS NETWORK
Implementations described and claimed herein provide systems and methods for correlating one or more service areas of a network with one or more geolocation coordinates to determine available services for customers to the network. A service polygon may be generated that define an area in which a particular service offered by a communications network is available. The boundaries of the service polygons may be adjusted based on information corresponding to physical features of the initial area. The service polygons may aid a communications network in providing a list of available services to potential customers or devices connected to the network by determining one or more geolocation coordinate values of a potential connection site and comparing the values to the service polygons. A network management system may determine the available services, current or in the future, to offer such services to a customer to the network.
A method for providing telecommunications services in a telecommunications network is provided. Customer parameters are obtained for a customer population associated with the network. Site parameters are obtained for sites associated with the customer population. A site key having a subset of the customer parameters or a subset of the site parameters is generated, the site key providing a modeling input for a segment of the customer population associated with the telecommunication services. A simulation set including simulations for the site key is generated, each simulation having customer events for a telecommunications build type, the customer events generated by simulating a customer set for the site key over time through a discrete event simulation. The simulation set is stored in a database, each simulation in the simulation set selectable to generate a telecommunications build plan for providing the telecommunications services to a telecommunications buildable area of the network.
H04L 41/142 - Network analysis or design using statistical or mathematical methods
G06F 30/27 - Design optimisation, verification or simulation using machine learning, e.g. artificial intelligence, neural networks, support vector machines [SVM] or training a model
H04B 10/00 - Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
24.
SYSTEMS AND METHODS FOR COMMUNICATIONS NODE UPGRADE AND SELECTION
Implementations described and claimed herein provide systems and methods for identification of connection areas in a telecommunications network. In one implementation, a customer set is obtained for a communications node in the telecommunications network. The customer set includes an existing connection type and a collection of network sites including the connection type is generated from the customer set. An overlay of customer sites without the conneciton type may be applied to the collection of network sites to generate an intersection of non-connected customer sites within the collection of network sites including the connection type. The intersection provides an indication of underserviced sites connection to the telecommunication network for potential network growth.
A method for providing telecommunications services in a telecommunications network is provided. A site footprint having a plurality of sites associated with a customer population of the telecommunications network is obtained. A fully connected buildable area for the site footprint is generated. A validated buildable area is generated from the fully connected buildable area by validating each connection of a plurality of sites. A buildable subgroup is generated based on the buildable connections of the plurality of sites, the one or more buildable subgroups each defining a contiguous build area having a subset of the plurality of sites. At least one investment cluster in a buildable subgroup is generated by clustering the subset of the plurality of sites according to a site category. A telecommunications build plan is generated for providing the telecommunications services to the subset of the plurality of sites associated with the investment cluster.
Improved methods for retrieval of content from CDNs is provided that includes a rendezvous controller that receives information of an identification of content being requested and an estimated location of a content requesting device. Based on this information, the rendezvous system identifies a server within a CDN from which the requested content may be retrieved. The selected server may be based on a repeatable hash function such that the likelihood that the content being requested is cached at the selected server. Steering requests to a server of the CDN which may have the content cached may reduce the number of servers within the CDN with the same cached content, particularly for the highest requested content. The rendezvous system may then return a corresponding domain name associated with the selected server and that can be subsequently submitted to a DNS for resolution to the IP address of the identified server.
H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
H04L 61/4535 - Network directories; Name-to-address mapping using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
H04L 67/10 - Protocols in which an application is distributed across nodes in the network
H04L 67/1014 - Server selection for load balancing based on the content of a request
H04L 67/1021 - Server selection for load balancing based on client or server locations
H04L 67/52 - Network services specially adapted for the location of the user terminal
H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Examples described herein relate to apparatuses and methods for managing communications within a supercluster or across superclusters, including a first supercluster having a plurality of first machines and a publish-subscribe (Pub-Sub) channel to which each of the plurality of first machines is subscribed. A second supercluster has a plurality of second machines and a bridge between the first supercluster and the second supercluster. A first machine is configured to receive, via the bridge, an availability status and resource allocation information of each second machine and publish, on the Pub-Sub channel of the first supercluster, the availability status and the resource allocation information.
H04L 67/1008 - Server selection for load balancing based on parameters of servers, e.g. available memory or workload
H04L 67/1014 - Server selection for load balancing based on the content of a request
H04L 67/1021 - Server selection for load balancing based on client or server locations
H04L 67/1034 - Reaction to server failures by a load balancer
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
A content provider has a plurality of content provider domain names, and a content delivery network (CDN) allocates a plurality of CDN domain names to the particular content provider. The content provider domain names are mapped to the CDN domain names. CDN domain names are bound to corresponding CDN clusters. The binding of the of CDN domain names to corresponding CDN clusters is modified.
Examples described herein relate to associating a first account with a second account, the first account being hosted by a first server, the second account being hosted by a second server, authenticating, by the first server, first login credentials associated with the first account, wherein the first login credentials are received from a user device, receiving, by the first server from the user device, second login credentials associated with the second account, sending, by the first server, the second login credentials to the second server for authentication, in response to determining that the second login credentials are authenticated by the second server, associating, by the first server, the first account with the second account, and connecting, by the first server to the second server, to allow the user device to access services commensurate with the second account without prompting the user device for the second login credentials.
Systems, methods, computer program products, and the like, for mapping requests for content received at a CDN to multiple mid-tier content servers. In an example, a method involves utilizing one or more hashing algorithms to map a URL associated with the mid-tier devices to one or more hostnames that may be utilized by the CDN to route requests for content to a particular mid-tier device when an edge device cannot service the request. In this manner, one content device of a particular metro receives requests for particular content and serves that content. By limiting the requests for particular content to a particular mid-tier device, storage may be more efficiently allocated across the mid-tier devices and content not replicated at multiple mid-tier devices.
H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
H04L 67/1014 - Server selection for load balancing based on the content of a request
H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
H04L 67/563 - Data redirection of data network streams
H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
31.
STREAMING SERVER STATISTICS AND PREDICTIVE MITIGATION
Aspects of the present disclosure involve systems and methods for improving the performance of a telecommunications network by monitoring the performance of one or more storage drives. Operational data is received from a plurality of storage drives of a storage server of a telecommunications network. A plurality of operational coefficients for each of the plurality of storage drives is derived based on the operational data, and a cluster plot is created from the plurality of operational coefficients for each of the plurality of storage drives. A distance is calculated between a subset of operational coefficients of the plurality of operational coefficients of the cluster plot, and a remedial action is initiated on a storage drive of the plurality of storage drives when a calculated distance of an operational coefficient associated with the storage drive exceeds a distance value from a cluster of the cluster plot.
H04L 41/142 - Network analysis or design using statistical or mathematical methods
H04L 41/147 - Network analysis or design for predicting network behaviour
H04L 41/16 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
H04L 43/08 - Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
32.
PROGRESSIVE CONTENT UPLOAD IN A CONTENT DELIVERY NETWORK (CDN)
A computer-implemented method, in a content delivery (CD) network, wherein the CD network delivers content on behalf of multiple content providers. The method includes, at an edge server in the CD network: receiving, from a client, uploaded content for a particular content provider; and determining that the particular content provider is a subscriber to the CD network. Based on the determining, when the particular content provider is determined to be a subscriber to the CD network, uploading the content from the edge server to multiple origin server platforms (OSPs), the uploading being based on at least one policy associated with the particular content provider.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
33.
SYSTEM AND METHOD FOR IMPROVEMENTS TO A CONTENT DELIVERY NETWORK
Provided is a content delivery method and architecture for ways to improve the caching of content at one or more content providing devices of a Content Delivery Network (CDN). In particular, systems and methods are disclosed that vary the requirements to store resources or content within a caching device using a dynamic popularity threshold. This popularity threshold may be varied based on a measured fullness of the storage capacity of the cache device. In another example, the dynamic popularity threshold may be further varied based on a cache pressure, which is an indication of how often the cache replaces stored items with new items. The adjustment to the popularity threshold for caching particular content at the caching device may thus be based on a number of requests for content received at the device to tune the caching procedure for a particular region of the CDN.
G06F 12/0888 - Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches using selective caching, e.g. bypass
G06F 12/0802 - Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
G06F 12/0806 - Multiuser, multiprocessor or multiprocessing cache systems
34.
FRONT-END OPTIMIZATION IN A CONTENT DELIVERY NETWORK (CDN)
A computer-implemented method, operable on a device in a content delivery network (CDN), wherein the CDN delivers content on behalf of at least one content provider, the device implementing a content delivery (CD) service, the method includes, by the service on the device: receiving a request for a particular resource from a client; determining whether the client includes an optimization support mechanism;, when the client includes an optimization support mechanism, providing the client with a first version of the particular resource, optimized, at least in part, for the capabilities of the client in combination with the optimization support mechanism; otherwise providing the client with either (i) an un-optimized version of the particular resource, or (ii) a version of the particular resource optimized, at least in part, for the capabilities of the client without the capabilities of the optimization support mechanism.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
A computer-implemented method in a content delivery network (CDN) having multiple delivery servers. The CDN delivers content on behalf of at least one content provider. Distinct delivery servers are logically grouped into delivery server groups. One or more CDN name servers are associated with some of the delivery server groups. Network map data are determined using network data determined by the CDN name servers associated with at least some of the deliver server groups. The network data with respect to a CDN name server relative to a resolver is based on an estimated popularity of that CDN name server for that resolver. Responsive to a client request, including a hostname associated with a content provider, at least one CDN name server determines, using network map data, at least one delivery server to process the client request.
H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
H04L 67/1036 - Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
H04L 67/1042 - Peer-to-peer [P2P] networks using topology management mechanisms
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
H04L 67/1029 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers using data related to the state of servers by a load balancer
Methods of routing packets in a network comprising Autonomous Systems (ASs), next hop determiners for routing packets, systems for routing packets, and route indicator feeders for providing modified route indicators are provided. A method of routing packets in such a network includes obtaining route indicators each comprising an indicator of a network prefix and an indicator of an AS path for delivering packets to an AS having the network prefix. The method includes identifying at least one said route indicator having an AS path indicator comprising a predetermined AS identifier, storing the network prefix indicator of each said identified route indicator, receiving at least one packet having an address indicating a destination, and if the destination address of said packet is within an address range defined by a said stored prefix indicator, transmitting the packet on a non-peering connection to the AS having the predetermined AS identifier.
Aspects of the present disclosure involve systems and methods for monitoring and quantifying the performance of a content delivery network (CDN) from a client side perspective based on server side events. In one particular embodiment, one or more content servers of the CDN may provide connectivity or other performance information to a collector device or site. This information may be reported by each of the content servers for each request for content received at the server. The collector site may then store the received performance information in a database for analysis by one or more systems.
Aspects of the present disclosure involve a CDN utilizing a Direct Server Return (DSR) request command to create a tunnel from one content server to another content server of the CDN. Through the DSR tunnel, a request for content may be served from a content server that is more advantageous for the CDN for any number of reasons, such as from a content server that is logically closer to the content server. In determining when a DSR tunnel is created to provide the content, the CDN may access a database storing various information concerning the CDN, such as the location of egress gateways of the CDN in relation to one or more content servers, connecting network location information, the capabilities of one or more content servers, and/or load information of available content servers.
A network application may transmit data over a network connection. The application may require certain functionality for the network connection. An embodiment provides a method for the application to inform the network of its requirement. The application may use a control packet to inform the network of its functionality requirement for the connection it is using. The control packets may be sent to the network at the same time the application is transmitting its data. In an embodiment, a user using the application instructs the network to provide certain functionality using the control packet.
Disclosed are system, method, and computer-readable medium embodiments for a network to provide network applications and services and estimate network metrics for individual applications and services. In an embodiment, a first routing device receives a packet and determines that the packet is to be sampled. The first routing device samples the packet by storing first information associated with the packet and transmits the first information to a measurement server. The first routing device transmits the packet towards a destination according to routing information. A second routing device receives the packet and determines that the packet is to be sampled. The second routing device samples the packet by storing second information associated with the packet and transmitting the second information to the measurement server. The measurement server determines a measurement based on the first information and second information.
ABSTRACT The present invention relates to transmitting data through a communication network. Having a channel that is shared among different data streams presents a risk that critical data may be bottlenecked by non-critical data. To deal with this, embodiments disclosed here transmit user's critical data streams on a dedicated channel. Specifically, when a data stream is determined not to be critical, a forwarding device forwards a packet of the stream on the common channel that is shared with another non-critical data stream. When the data stream is determined to be critical, the forwarding device forwards the packet on a different channel that is dedicated to the data stream. In one example, a web content provider may send web content in different data streams to its customers across the network. Some of the data streams may be critical, and dedicated channels with specific capacities may be assigned to this critical data. Date Recue/Date Received 2021-05-19
H04L 47/2441 - Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
Disclosed herein are system, method, and computer program product embodiments for dynamically applying network functions to traffic flows based on heuristics, policy conditions and client-specified conditions. A network monitors a network traffic flow to determine whether the network traffic flow meets a first criterion of a first rule. The criterion specifies that when the first criterion is met a network function be used to analyze or process the network traffic flow. When the network traffic flow is determined to meet the first criterion, the network determines a first route through the network to a network function provider that provides the network function and configures one or more routers along the first route to forward the network traffic flow to the network function provider for analysis or processing.
Techniques are provided for blocking forgiveness in a system that mitigates distributed denial of service (DDoS) attacks on a network. A user's network address can be blocked as a result performing human behavior analysis on network resource request activity from the user's address. The system can block an address temporarily based on their behavior, classifying legitimate human users as a malicious attacker performing a DDoS attack. But subsequent behavioral analysis of network resource requests can identify that the user should not have been blocked. The system can automatically unblock the user's address, and allow further network resource requests. Previously blocked requests can also be unblocked. The number of infractions (e.g., action classified as malicious) can be tracked and compared to a threshold. If the number is less than the threshold, then that address is not blocked, thereby allowing forgiveness of a certain number of infractions.
Abstract A computer-implemented method for providing a service on a network is provided. The method includes: requesting, on a first router, instructions from a remote server specifying how the first router is to operate to provide the service requested; initializing a first thread to execute the received instructions; determining that a configuration of the first router has changed; executing, on the initialized thread, the instructions to apply the service in accordance with the change; receiving, at the first thread, a packet from a second thread running on a second router executing the instructions from the remote server; and determining, at the first thread, that the second thread is also participating in providing the service. This can be helpful with moving the functionality of providing a service from an orchestration server to a routing device, obviating the need for an orchestration server. Date Recue/Date Received 2021-02-23
H04L 12/16 - Arrangements for providing special services to substations
H04L 41/0813 - Configuration setting characterised by the conditions triggering a change of settings
H04L 41/5003 - Managing SLA; Interaction between SLA and QoS
H04L 41/5054 - Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
Implementations described and claimed herein provide systems and methods for custom-defined network routing. In one implementation, a set of custom defined network flow rules is received at an edge router of a primary network, which is in communication with a customer network. The set of custom defined network flow rules correspond to network traffic associated with the customer network. The set of custom defined network flow rules is stored in a forwarding table on the edge router. A packet of data is received at the edge router. The packet of data is attributed to the customer network. The set of custom defined network flow rules is applied to the pack of data using the forwarding table.
A method of serving content and apparatus therefor are provided. A portional use relationship between client devices within a first autonomous system and resolvers within it is obtained. A distance relationship between the client devices and content serving locations in a second autonomous system is obtained, the distance relationship with respect to at an egress gateway of the second autonomous system and to which content from the content serving devices of the second autonomous system egresses to the first autonomous system. The distance relationship includes information as to a distance measurement between the egress gateway and the content serving locations when the egress gateway and the content serving locations are not co-located. A network relationship between the resolvers and the content serving locations using the portional use relationship and the distance relationship is obtained, the network relationship used to resolve a content request from the client devices.
A system, computer network and method are provided for optimizing inbound traffic for the computer network. The system stores, in a server, a geographic area of a particular component of the computer network. The server obtains geographic areas for connections between the computer network and access networks. The server compares the geographic area and the geographic areas for the connections to determine a first subset of the access networks. The first subset of the access networks comprises the one or more access networks that connect to the computer network in the same geographic area as the geographic area of the particular component of the computer network. The server transmits a preferred access path for the particular component of the computer network to the first subset of the access networks. The particular component of the computer network provides content to an end user based on the preferred access path.
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for implementing a high-quality Video over Internet Protocol (VoIP) network accessible through a public network, such as the Internet. More particularly, a user of a telecommunication network may access the VoIP through an Internet connection or other public network connection and is then connected to a virtual local loop for transmission across the VoIP. As such, the public network may act as an egress and/or ingress to the VoIP allowing users with public network connectivity access to the network. Thus, a virtual local loop providing the desired services and quality from the telecommunications network may be created for a user of the network, without the need of the user to directly connect into the VoIP.
H04L 12/16 - Arrangements for providing special services to substations
H04N 21/2662 - Controlling the complexity of the video stream, e.g. by scaling the resolution or bitrate of the video stream based on the client capabilities
In an embodiment, a method exchanges routing data within a network including control and forwarding on separate devices. In the method, a first reachability information session is established between a forwarding device and a first control device and a second reachability information session is established between the forwarding device and a second control device. Also, a third reachability information session is established between the forwarding device and an external routing device. Finally, advertisements are exchanged between the first and second reachability information sessions and the third reachability information session such that the first and second control device appear to the external routing device to be a single device. System and computer program product embodiments are also disclosed.
Disclosed herein are system, method, and computer program product embodiments for increasingly applying network resources to traffic flows based on heuristics and policy conditions. In an embodiment, a network determines that a traffic flow satisfies a first condition and transmits a first portion of the traffic flow to a network service. A network service then inspects the first portion of the traffic flow at a first level of detail and determines that the traffic flow satisfies a second condition. The network may then transmit a second portion of the traffic flow to the network service based on the determining the traffic flow satisfies the second condition. The network service can inspect the second portion of the traffic flow at a second level of detail, wherein the inspecting at the second level of detail requires a different amount of computing resources than the inspecting at the fu-st level of detail.
H04L 47/24 - Traffic characterised by specific attributes, e.g. priority or QoS
H04L 47/2441 - Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
H04L 12/22 - Arrangements for preventing the taking of data from a data transmission channel without authorisation
In an embodiment, a system routes a new data stream from a source to a destination through a plurality of forwarding devices interconnected with links. The system includes a control device that receives a request to create a path through the plurality of interconnected forwarding devices for a new data stream and determines a type of the new data stream. A data flow database stores historical usage characteristics of data streams having the determined type. A path computation module determines, based on the historical usage characteristics of data streams having the determined type, the requested path through plurality of interconnected forwarding devices from the source to the destination.
A rule indicates that data having particular characteristics be automatically routed to a particular destination. When software on a switching device detects a new data stream, it is analyzed to determine whether it has characteristics specified by the rule. If it does, the packet is encapsulated with a special tag, indicating that the packet should be routed to the new destination. Also, an entry is added to a quick-lookup table in the switching device. The entry indicates that future packets in the data stream that have the same source and destination port and address should also be routed to the new destination.
Embodiments are disclosed that provision a cloud-based service together with a dedicated network connection to provision a cloud-based service element. In response to the request both the cloud-based service element and a dedicated network connection are provisioned. Provisioning the cloud-based service element together with the dedicated network connection enables the cloud-based service element to utilize the dedicated network connection.
H04L 41/0806 - Configuration setting for initial configuration or provisioning, e.g. plug-and-play
H04L 41/0896 - Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
H04L 41/12 - Discovery or management of network topologies
H04L 41/5054 - Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
H04L 47/72 - Admission control; Resource allocation using reservation actions during connection setup
H04L 67/10 - Protocols in which an application is distributed across nodes in the network
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 67/52 - Network services specially adapted for the location of the user terminal
A network includes a plurality of endpoint routers and intermediate routers. When a new data stream is detected at any endpoint router, the first packet is sent to a virtual routing server with knowledge of the entire network topology. Based on the topology, current usage, and historical usage, the virtual routing server determined a path for the data stream and begins to update the routing tables of the intermediate routers to reflect the determined path. Until the update is complete, all packets in the data stream are routed first to the virtual routing server and then to their destination. Once the update is complete, packets in the data stream are routed directly along the determined path.
H04L 41/0816 - Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
H04L 41/0896 - Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
Aspects of the present disclosure involve provisioning customers of an aggregator, such as a reseller, of a content delivery network (CDN). In one aspect, content requests to the CDN are processed in accordance with the virtual IP (VIP) address at which the request was received, according to a property template bound to the VIP selected by the customer and only involving discrete parameters for the reseller. In another aspect, cache fills of the network are processed without direct knowledge of the customer origin through a combination of some request attribute, e.g., alias host of the customer, and an attribute of the reseller to make a DNS request to a name server outside the CDN. Another aspect involves receiving a property template selection, an origin and an alias from a customer of the reseller, and providing appropriate DNS entries to validate the customer and provide origin information to the CDN.
A user of a network service (such as an Ethernet e-line) can specify rules defining changes to the network service under particular usage conditions (for example threshold bandwidth utilization). The network's usage is monitored. When particular usage conditions are detected, the network service is evaluated to determine what switches need to be configured and how to configure them, The switches are configured accordingly. When the usage conditions no longer exist, the switches are re-configured to their original service level.
H04L 41/0896 - Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
H04L 41/5041 - Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for grouping a plurality of content files in content delivery network (CDN) for easier storage and access. In one embodiment, the CDN may store related files in one or more container files within the CDN to reduce the number of stored files. In addition, a manifest provided to the requesting device relating to the content may be altered to point to the container files rather than the separate content files within the container. The manifest may also provide information to the requesting to extract and process the content files within the container file in the proper order for playing on the requesting device.
H04N 21/231 - Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers or prioritizing data for deletion
H04N 21/222 - Secondary servers, e.g. proxy server or cable television Head-end
58.
SELECTING A CONTENT PROVIDING SERVER IN A CONTENT DELIVERY NETWORK
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for managing the distribution of content from a content distribution network (CDN). In general, the system receives a request for content from the CDN from a user of the network and determines a server within the CDN to provide the content to the user. In addition, the system of the present disclosure may determine a preferred server or group of servers from which the content is provided to the user. This preference may be based on information received from a Border Gateway Protocol feed or Interior Gateway Protocol feed and one or more business determinations, such as the cost of providing the content through the CDN and particular egress port associated with the CDN.
H04L 45/64 - Routing or path finding of packets in data switching networks using an overlay routing layer
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
H04L 67/61 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
H04L 45/302 - Route determination based on requested QoS
H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
59.
REAL TIME APPLICATION PROGRAMMING INTERFACE IN A TELECOMMUNICATIONS NETWORK
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for implementing providing a web conferencing service. In one example, the system and methods involve a real-time application programming interface (RTAPI) component in the telecommunications network. The RTAPI is configured, in one embodiment, to provide a platform through which one or more users of the telecommunications network interfaces with one or more conferencing components of the network. In one example, the RTAPI may be configured to coordinate a dial-out to a participant of a conference at a designated time such that the participant is entered into the conference automatically.
A framework supporting content delivery includes multiple devices, each configured to run at least one content delivery service. The content delivery services include collector services, reducer services, and control services. Event information is provided from the services, and the control services provide control information to control operation or configuration of content delivery services.
H04L 12/16 - Arrangements for providing special services to substations
H04L 41/0816 - Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
H04L 41/0823 - Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
H04L 41/0869 - Validating the configuration within one network element
H04L 41/0893 - Assignment of logical groups to network elements
H04L 41/12 - Discovery or management of network topologies
H04L 41/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
H04L 41/5041 - Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
H04L 43/04 - Processing captured monitoring data, e.g. for logfile generation
H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
H04L 67/10 - Protocols in which an application is distributed across nodes in the network
H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
H04L 67/289 - Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
H04L 67/5682 - Policies or rules for updating, deleting or replacing the stored data
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
G06F 17/00 - Digital computing or data processing equipment or methods, specially adapted for specific functions
H04L 41/0813 - Configuration setting characterised by the conditions triggering a change of settings
H04L 43/08 - Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
H04L 43/10 - Active monitoring, e.g. heartbeat, ping or trace-route
H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
H04L 61/4535 - Network directories; Name-to-address mapping using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
61.
CENTRAL SERVICES HUB FOR A TELECOMMUNICATIONS NETWORK
Implementations of the present disclosure involve an apparatus, system and/or method for a central hub of a telecommunications network to provide varying services for a received communication intended for varying telecommunications networks. In one embodiment, the central service hub receives the communication and provides the varying services for the communication based on information concerning the communication, such as the intended telecommunication network. In another embodiment, the central service hub analyzes the communication and determines to which telecommunications network the communication should be routed to apply the appropriate network services. The central service hub may comprise a softswitch, media gateway controller device or other telecommunications device that includes programming, such as an application programming interface (API), configured to receive and process the incoming communications.
H04M 7/12 - Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
H04M 15/00 - Arrangements for metering, time-control or time-indication
H04Q 11/04 - Selecting arrangements for multiplex systems for time-division multiplexing
62.
SYSTEM AND METHOD FOR INTEGRATING VOIP CLIENT FOR AUDIO CONFERENCING
Aspects of the present disclosure disclose system, apparatus and methods for providing an integrated web conferencing. In various aspects, the disclosure is directed to integrating a VoIP client for audio conferencing with a web client. In particular, the system provides for integrating a web portion of a web conference with an audio portion of the web conference. More specifically, the system, apparatus and methods provide for connecting a VoIP client to an audio conferencing portion of the system to facilitate communications between client and server.
Implementations described and claimed herein provide systems and methods for balancing network loads across distrinct provider networks using enriched network traffic flow data. In one implementation, network traffic flow data representative of network traffic exchanged between a first provider network and a second provider network is generated. The network traffic flow data is enriched using at least one enrichment feed. A network load indication for the first provider network is calculated using the enriched network traffic flow data. The network load indication is a function of a bandwidth measurement and a distance measurement.
Aspects of the present disclosure describe systems and corresponding methods for storing and/or redistributing data within a network. In various aspects, data and/or sets of data stored in a database, data store, or other type of database storage system may be pulled, pushed, distributed, redistributed, or otherwise positioned at one or more data caches and/or servers strategically located across an enterprise network, a content delivery network ("CDN"), etc., and may be accessible over such networks, other networks, and/or the Internet.
G06F 16/90 - Information retrieval; Database structures therefor; File system structures therefor - Details of database functions independent of the retrieved data types
G06F 16/27 - Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
H04L 12/16 - Arrangements for providing special services to substations
65.
SYSTEM AND METHODS FOR IDENTIFYING AND REMEDYING TRAFFIC IMBALANCES AND INEQUITIES BETWEEN NETWORKS
Implementations described and claimed herein provide a system and methods for balancing network loads across distinct provider networks. In one implementation, a virtual network representative of at least a first provider network is established having at least one interconnection point where network traffic is exchanged between the first provider network and a second provider network and having at least one provider edge port and at least one potential interconnection point. A measurement of a bandwidth between the at least one provider edge port and the at least one interconnection point is obtained. A measurement of a distance between the at least one provider edge port and a geographically closest of the at least one potential interconnection point or the at least one interconnection point is obtained. A network load indication for the first provider network as a function of the bandwidth measurement and the distance measurement is obtained.
A load-balancing cluster includes a switch having ports connected to servers. Each of the servers are addressable by the same virtual Internet Protocol (VIP) address. Responsive to a connection request at the switch to connect a client computer to a server associated with the VIP address, a server establishing a Transmission Control Protocol (TCP) connection with the client computer, and, if the server does not have a copy of the particular resource it queries peers regarding the particular resource. Based at least in part on responses from the peers, the server either: obtains the particular resource from a peer if the peer has a copy of the particular resource; or migrates the TCP connection to a second peer; or serves the particular resource to the client request through a second server when a third peer indicates that the initial server should proxy the particular resource through the second server.
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for collaboration conferencing with multiple participants over a communications network, and more specifically for a conferencing routing service for managing and routing collaboration participants. In one embodiment, the conferencing system may utilize Session Initiation Protocol (SIP) to conduct the routing of the collaboration conferences within the telecommunications network. The SIP-based routing provides for the exchanging of information from one device of the conferencing system to another that is not available in non-IP based conferencing systems. Thus, through the use of IP-based telecommunication devices, the network provides beneficial features for collaboration conferencing.
H04L 41/0668 - Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
H04L 43/0876 - Network utilisation, e.g. volume of load or congestion level
A content delivery network (CDN) includes a control core; and a plurality of caches, each of said caches constructed and adapted to: upon joining the CDN, obtain global configuration data from the control core; and obtain data from other caches. Each of the caches is further constructed and adapted to, having joined the CDN, upon receipt of a request for a particular resource: obtain updated global configuration data, if needed; obtain a customer configuration script (CCS) associated with the particular resource; and serve the particular resource in accordance with the CCS.
H04L 41/0853 - Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
H04L 41/0893 - Assignment of logical groups to network elements
H04L 41/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
H04L 41/5061 - Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
H04L 67/5682 - Policies or rules for updating, deleting or replacing the stored data
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Implementations of the present disclosure involve a system and method for federating communications between a first network that transmits and receives messages formatted in a first format and a second network that transmits and receives messages formatted in a second format. The system and method are configured to receive a message from the first network formatted in the first format. The system then converts the message into a unified format that may be sent to the second network. After receiving the message in the unified format, the message may then be converted into the format of the second network and sent on the second network like any other message on the second network.
H04W 4/18 - Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
H04L 51/066 - Format adaptation, e.g. format conversion or compression
H04L 51/56 - Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
H04L 67/565 - Conversion or adaptation of application format or content
H04L 12/66 - Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
70.
CUSTOMIZED DOMAIN NAMES IN A CONTENT DELIVERY NETWORK (CDN)
A first domain name is obtained at a cache server in content delivery network (CDN), the CDN including a plurality of cache servers and domain name servers, the first domain name being part of a client request for a resource from the cache server. One or more values forming part of the client request are determined and in response to determining that the cache server has said requested resources, a second domain name is generated, including information from the first domain name and information determine from the values forming part of the client request. The second domain name is provided to the client.
A system and method of providing virtualized connectivity in a cloud services environment. A service provider network defines at least a first virtual private network and a second virtual private network for a respective first customer network and a second customer network. The service provider network includes at least one physical connection with a cloud services provider network where the at least one physical connection includes a first private virtual connection between the first virtual private network and the cloud services provider and a second private virtual connection between the second virtual private network and the cloud services provider.
A load-balancing cluster includes a switch having a plurality of ports; and a plurality of servers connected to at least some of the plurality of ports of the switch. Each server is addressable by the same virtual Internet Protocol (VIP) address. Each server in the cluster has a mechanism constructed and adapted to respond to connection requests at the VIP by selecting one of the plurality of servers to handle that connection, wherein the selecting is based, at least in part, on a given function of information used to request the connection; and a firewall mechanism constructed and adapted to accept all requests for the VIP address for a particular connection only on the server that has been selected to handle that particular connection. The selected server determines whether it is responsible for the request and may hand it off to another cluster member.
H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
H04L 67/101 - Server selection for load balancing based on network conditions
H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
H04L 67/1036 - Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
A content delivery network has at least a first tier of servers. A content delivery method includes, at a first server in the first tier of servers, obtaining a request from a client for a resource. If the resource is available at the first server or at a peer of the first server, then the resource is served to the client from the first server. Otherwise, if the resource is determined to be popular, then the first server obtains the resource and the first server serves the resource to the client. If the resource is determined not to be popular, the client is directed to a second server, not in the first tier of servers, and the second server serves the resource to the client. The second server may be in a second tier of servers or it may be an origin server.
A content delivery network (CDN) includes multiple cluster sites, including sites with streaming media servers, caching servers and storage devices accessible to the caching servers for storing streaming content. Interface software is configured to initiate retrieval, by a caching server, of electronic streaming resources from the one or more storage devices in response to requests for the electronic streaming resource received by the streaming media server.
H04N 21/231 - Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers or prioritizing data for deletion
H04N 21/482 - End-user interface for program selection
Provided are methods and systems for dynamic binding in the context of content delivery. For example, the methods and systems may be implemented as a dynamic binding process that maps a content provider to a first set of content servers in a content distribution network. The dynamic binding process may then facilitate the content to be received from the content provider so that the content can be distributed by the first set of content servers in the content distribution network. The dynamic binding process further monitors network traffic associated with the content from the content provider and determines at least one metric associated with the network traffic. Additionally, the dynamic binding process can remap the content provider to a second set of content servers in the content distribution network based on at least one of the metrics.
Embodiments generally disclosed include methods, systems and devices for providing an extensible content delivery platform. The methods, systems and devices include identifying a plurality of discrete events of a content delivery process of a content delivery network and providing a structured object model comprising a plurality of objects instantiated and available at the plurality of discrete events. The methods, systems and devices further include providing a programmatic grammar configured to provide a logical flow of actions being applied against the plurality of objects on occurrence of at least one of the plurality of discrete events of the content delivery process of the content delivery network.
An embodiment of a system for managing delivery of content to end users includes a semantics generator configured to generate name/value pair semantics for name/value pairs that can be included in flexible tokens, a semantics publisher configured to publish the name/value pair semantics in a menu, wherein the name/value pair semantics are selectable, a flexible token interpreter configured to interpret name/value pairs included in flexible tokens according to the name/value pair semantics, the flexible token interpreter further configured to determine responses to content requests based on the name/value pairs included in flexible tokens, and an edge server configured to generate token-dependent responses to content requests based on determined responses from the flexible token interpreter.
H04L 12/16 - Arrangements for providing special services to substations
H04N 21/25 - Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication or learning user preferences for recommending movies
Provided are computer-implemented methods and systems for performing media resource storage and management. The computer-implemented method and system implemented as a request manager is capable of monitoring requests for media resources in a content delivery network. For each monitored request, the request manager determines whether to generate a multifile for the requested media resource. For example, the request manager can first determine whether the media resource is eligible for multifile generation. If eligible, the request manager then determines whether the media resource has reached a popularity threshold. If the media resource has reached the popularity threshold, the request manager initiates generation of the multifile for the requested media resource. Generally, the generated multifile is stored in a storage system associated with the content delivery network.
A system for distributing content includes a content distribution platform (CDP) analysis module configured to determine an optimal combination of one or more CDP components for distributing a specified content item based on at least one content item profile. A method of distributing content includes determining an optimal combination of one or more content distribution platform (CDP) components for distributing a specified content item based on at least one content profile.
H04W 88/18 - Service support devices; Network management devices
H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
H04L 67/1097 - Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
H04L 67/61 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
H04L 67/5682 - Policies or rules for updating, deleting or replacing the stored data
An embodiment of a method includes receiving a request for the content from a requester, retrieving the content from a media access server, and while retrieving the content from the media access server, simultaneously streaming the content to the requester. An embodiment of a system includes an edge server having a media streaming server configured to receive the request and stream the specified content to a requester from a local memory, and a stream caching server configured to retrieve the requested content from a media access server while the media streaming server is streaming at least a specified portion of the content, and wherein the stream caching server is further configured to store the retrieved content in a local cache and notify the media streaming server that content is stored in local cache.
A content delivery network has at least a first tier of servers. A content delivery method includes, at a first server in the first tier or servers, obtaining a request from a client for a resource. If the resource is available at the first server or at a peer of the first server, then the resource is served to the client from the first server. Otherwise, it is determined whether the resource is popular, and if the resource is determined to be popular, then the first server obtains the resource and the first server serves the resource to the client. If the resource is determined not to be popular, the client is directed to a second server, not in the first tier of servers, and the second server serves the resource to the client. The second server may be in a second tier of servers or it may be an origin server.
A load-balancing cluster in-cludes a switch having a plurality of ports; and a plurality of servers connected to at least some of the plurality of ports of the switch. Each server is addressable by the same virtual Internet Protocol (VIP) ad-dress. Each server in the cluster has a mechanism constructed and adapted to re-spond to connection requests at the VIP by selecting one of the plurality of servers to handle that connection, wherein the select-ing is based, at least in part, on a given function of information used to request the connection; and a firewall mechanism con-structed and adapted to accept all requests for the VIP address for a particular connec-tion only on the server that has been select-ed to handle that particular connection. The selected server determines whether it is re-sponsible for the request and may hand it off to another cluster member.
H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
H04L 61/103 - Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
83.
SYSTEM AND METHOD FOR AGGREGATING AND REPORTING NETWORK TRAFFIC DATA
A method for analyzing traffic in a communications network includes sampling data packets at a plurality of network interconnection points, wherein sampling the data packets includes generating a plurality of sampled packet data in one or more standardized formats, converting the sampled packet data from the one or more standardized formats into a neutral format, and aggregating the sampled packet data in the neutral format from the plurality of network interconnection points. A system includes a communications node operable to sample data packets flowing through and generate sample packet data in a specified format, a collector node operable to convert the sampled packet data into a neutral format, the collector node further operable to map IP addresses of the sampled packet data to corresponding prefixes in a routing table; and an aggregator node operable to aggregate neutrally formatted sampled packet data from a plurality of collector nodes.
According to various embodiments of the present invention, systems and methods for mobile virtual network operator (MVNO) telephone number provisioning and voicemail routing by a mobile virtual network enabler (MVNE) are disclosed. In one embodiment, a method includes: provisioning a telephone number (TN) and its associated mobile subscriber identification (MSID) owned by a mobile virtual network operator (MVNO) on a home location register (HLR) of a third party carrier, the third party carrier is not the owner of the TN; routing a call to the provisioned TN from a calling party by utilizing the HLR, wherein a called party of the TN is at least one of providing no answer or unreachable; receiving an indication from a gateway mobile switching center (GW MSC) of the third party carrier that there is no voicemail transfer number associated with the TN; and initiating a new call to a voicemail server of the MVNO, the new call to provide voicemail associated with the TN to the calling party. Other embodiments are also disclosed.
A transmission relay circuit, a broadcast signal relay method, and a signal detection device are disclosed. Preferably, the transmission relay circuit includes a microcontroller, a broadcast signal sensing and discerning circuit configured for determining the broadcast signal selected from a group consisting of (NTSC, ASI, DS-3, SDI, and HD-SDI signals). The method preferably includes the steps of determining a signal type, directing the signal to an analog broadcast signal processing circuit when the signal is determined to be to be an analog video signal, directing the signal to a digital broadcast signal processing circuit when the signal is either a digital video signal, or a digital video transport signal, and relaying the processed signal to a local loop provider. The detection device preferably includes at least a multi-layer printed circuit board with an isolation/buffer amplifier and terminator, and a signal detection circuit for detecting and determining the broadcast signal type.
Ethernet-based networks for routing Internet Protocol (IP) traffic between source and destination sites. One embodiment includes a plurality of discrete data transmission backbones between the source and destination sites. The source site includes control means for distributing IP traffic at the source site to the plurality of backbones for transmission to the destination site.
patents
