Network-specific arrangements or communication protocols supporting networked applications

HELECTRICITY H04Electric communication H04LTRANSMISSION OF DIGITAL INFORMATION

H04L67/00Network-specific arrangements or communication protocols supporting networked applications

H04L67/02involving the use of web-based technology H04L67/025for remote control or remote monitoring of the application H04L67/04adapted for terminals or networks with limited resources or for terminal portability H04L67/06adapted for file transfer H04L67/08adapted for terminal emulation H04L67/10in which an application is distributed across nodes in the network H04L67/1002for accessing one among a plurality of replicated servers H04L67/1004Server selection in load balancing H04L67/1006with static server selection H04L67/1008based on parameters of servers H04L67/101based on network conditions H04L67/1012based on compliance of requirements or conditions with available server resources H04L67/1014based on the content of a request H04L67/1017based on a round robin mechanism H04L67/1019based on random server selection H04L67/1021based on client or server locations H04L67/1023based on other criteria H04L67/1025dynamic adaptation of the criteria on which the server selection is based H04L67/1027Persistence of sessions during load balancing H04L67/1029using data related to the state of servers by a load balancer H04L67/1031Controlling of the operation of servers by a load balancer H04L67/1034Reaction to server failures by a load balancer H04L67/1036Load balancing of requests to servers for services different from user content provisioning H04L67/1038Load balancing arrangements to avoid a single path through a load balancer H04L67/104for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks H04L67/1042involving topology management mechanisms H04L67/1044Group management mechanisms H04L67/1046Joining mechanisms H04L67/1048Departure or maintenance mechanisms H04L67/1051Group master selection mechanisms H04L67/1053with pre-configuration of logical or physical connections with a determined number of other peers H04L67/1055involving connection limits H04L67/1057involving pre-assessment of levels of reputation of peers H04L67/1059Inter-group management mechanisms H04L67/1061involving node-based peer discovery mechanisms H04L67/1063Discovery through centralizing entities H04L67/1065Discovery involving distributed pre-established resource-based relationships among peers H04L67/1068Discovery involving direct consultation or announcement among potential requesting and potential source peers H04L67/107with limitation or expansion of the discovery scope H04L67/1072Discovery involving ranked list compilation of candidate peers H04L67/1074for supporting resource transmission mechanisms H04L67/1076Resource dissemination mechanisms or network resource keeping policies for optimal resource availability in the overlay network H04L67/1078Resource delivery mechanisms H04L67/108characterized by resources being split in blocks or fragments H04L67/1082involving incentive schemes H04L67/1085involving dynamic management of active down- or uploading connections H04L67/1087involving cross functional networking aspects H04L67/1089Hierarchical topologies H04L67/1091Interfacing with client-server systems or between P2P systems H04L67/1093Some peer nodes performing special functions H04L67/1095for supporting replication or mirroring of data H04L67/1097for distributed storage of data in a network H04L67/12adapted for proprietary or special purpose networking environments H04L67/125involving the control of end-device applications over a network H04L67/14for session management H04L67/141provided for setup of an application session H04L67/142provided for managing session state for stateless protocols; Signalling a session state; State transitions; Keeping-state mechanisms H04L67/143provided for session termination, e.g., event controlled end of session H04L67/145provided for avoiding end of session H04L67/146Markers provided for unambiguous identification of a particular session H04L67/147provided for signalling methods or particular messages providing extensions to IETF, ITU, ETSI or 3GPP protocols, e.g., additional proprietary messages, standard messages enhanced by additional header fields or standard messages being used for purposes other than originally intended H04L67/148provided for migration or transfer of sessions H04L67/16Service discovery or service management H04L67/18in which the network application is adapted for the location of the user terminal H04L67/20involving third party service providers H04L67/22Tracking the activity of the user H04L67/24Presence management H04L67/26Push based network services H04L67/28for the provision of proxy services H04L67/2804for adding application control or application functional data H04L67/2809for brokering H04L67/2814for data redirection H04L67/2819Enhancement of application control based on intercepted application data H04L67/2823for conversion or adaptation of application content or format H04L67/2828for reducing the amount or size of exchanged application data H04L67/2833for grouping or aggregating service requests H04L67/2838for integrating service provisioning from a plurality of service providers H04L67/2842for storing data temporarily at an intermediate stage H04L67/2847involving pre-fetching or pre-delivering data based on network characteristics H04L67/2852involving policies or rules for updating, deleting or replacing the stored data based on network characteristics H04L67/2857involving storage of data provided by user terminals H04L67/2861for providing operational support to end devices by emulation H04L67/2866Architectural aspects H04L67/2871Implementation details of a single intermediate entity H04L67/2876Pairs of interprocessing entities at each side of the network H04L67/288Distributed intermediate devices H04L67/2885Hierarchically arranged intermediate devices H04L67/289where the intermediate processing is functionally located closer to the data consumer application H04L67/2895where the intermediate processing is functionally located closer to the data provider application H04L67/30involving profiles H04L67/303Terminal profiles H04L67/306User profiles H04L67/32for scheduling or organising the servicing of application requests H04L67/322whereby quality of service [QoS] or priority requirements are taken into account H04L67/325whereby a time schedule is established for servicing the requests H04L67/327whereby the routing of a service request to a node providing the service depends on the content or context of the request H04L67/34involving the movement of software or configuration parameters H04L67/36involving the display of network or application conditions affecting the network application to the application user H04L67/38Protocols for telewriting; Protocols for networked simulations, virtual reality or games H04L67/40Protocols for remote procedure calls [RPC] H04L67/42Protocols for client-server architectures