US7953870B1 - Dynamic HTTP service timeout adjustment - Google Patents
Dynamic HTTP service timeout adjustment Download PDFInfo
- Publication number
- US7953870B1 US7953870B1 US12/634,063 US63406309A US7953870B1 US 7953870 B1 US7953870 B1 US 7953870B1 US 63406309 A US63406309 A US 63406309A US 7953870 B1 US7953870 B1 US 7953870B1
- Authority
- US
- United States
- Prior art keywords
- timeout
- parameter
- timeout parameter
- new
- gateway server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/28—Flow control; Congestion control in relation to timing considerations
- H04L47/283—Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
Definitions
- HTTP communications between client applications in devices and servers include time limits for the client applications in the devices to respond or provide data. When the devices do not respond with the designated time limits, a timeout occurs which may result in the servers deciding to close or reset the connection with the devices.
- servers have a pre-configured, static timeout setting for any HTTP communication with any device.
- not all applications, content documents, terminals, or networks experience the same responsiveness, meaning that many of the applications or devices may exceed the static timeout setting when a response is due. This situation will result in the many of the applications or devices being disconnected and may result in multiple retry sessions between the application or device and the server. As a result, there is no viable means to control or notify the server that the application or device requires a longer wait time.
- media includes computer-useable instructions that are executed in a method for adjusting timeout parameters to enable communications between devices.
- a dynamic timeout management server monitors amounts of time for a gateway server to exchange information with devices.
- a centralized timeout database stores the amounts of time it takes for each of the devices to communicate with the gateway server.
- the dynamic timeout management server obtains a timeout parameter for each of the devices from the gateway server.
- the timeout parameter is an amount of time the gateway server waits for a response from a device.
- the dynamic timeout management sever receives an indication from the gateway server that the amount of time from the response from the device has reached a value of the timeout parameter.
- the gateway server terminates the communication with the device.
- the amount of time in the timeout parameter associated with the device is adjusted to be a new timeout parameter to prevent a timeout.
- the new timeout parameter is stored in place of the timeout parameter in the centralized timeout database.
- the new timeout parameter is associated with the device.
- the gateway server is instructed to use the new timeout parameter in place of the timeout parameter for the device.
- a system for preventing an occurrence of timeouts during a communication between devices in a network includes a gateway server, a dynamic timeout management server, and a centralized timeout database.
- the gateway server enforces timeouts when devices exceed an amount of time for a timeout parameter, enforces a unique timeout for each device wherein each device has its own timeout parameter, receives instructions from the dynamic timeout management server to adjust the timeout parameter to a new timeout parameter for each device, and provides statistical information to the dynamic timeout management server on the amount of time it takes for each device to communicate.
- the dynamic timeout management server monitors the amount of time it takes for each device to communicate with the gateway server, adjusts the timeout parameter to the new timeout parameter when the device exceeds the amount of time to communicate, and stores the timeout parameter and the new timeout parameter in a centralized timeout database.
- the centralized timeout database connects to the dynamic timeout management server and stores timeout information for devices that communicate with or connect to gateway servers.
- the gateway server is a member of the gateway servers.
- another media includes computer-useable instructions that are executed in a method for adjusting timeout parameters to enable communications between devices.
- a gateway server provides amounts of time for the gateway server to exchange information with devices to a dynamic timeout management server.
- the amounts of time are times it takes for each of the devices to communicate with the gateway server.
- the amounts of time are stored in a centralized timeout database connected to the dynamic timeout management server.
- a timeout parameter is provided for each of the devices to the dynamic timeout management server.
- the timeout parameter is an amount of time the gateway server waits for a response from a device.
- the timeout parameter is stored for each of the devices in the centralized timeout database.
- a determination is made when the timeout parameter is reached where the gateway server terminates the communication with the device.
- the communication is terminated with the device when the amount of time reaches a value of the timeout parameter.
- a new timeout parameter is received from the dynamic timeout management server to replace the timeout parameter for the device where the new timeout parameter represents the amount of time that has been adjusted in the timeout parameter to prevent a timeout.
- the new timeout parameter is stored in place of the timeout parameter in a locally managed database connected to the gateway server.
- the new timeout parameter is associated with the device.
- the gateway server implements the new timeout parameter in place of the timeout parameter for the device.
- FIG. 1 illustrates a block diagram of an exemplary network for dynamically adjusting timeout values of devices implemented in accordance with an embodiment of the present invention
- FIG. 2 illustrates a process for adjusting timeout parameters to enable communication between devices implemented in accordance with an embodiment of the present invention
- FIG. 3 illustrates a process preventing an occurrence of timeouts during a communication between devices in a network implemented in accordance with an embodiment of the present invention.
- AAA Authentication, Authorization, and Accounting AMS Application Management System APP Application AT Access Terminal AUD Authentication User Delegate BSS Business Supporting Systems CD-ROM Compact Disc—Read-Only Memory EEPROM Electronically Erasable Programmable Read-Only Memory IP Internet Protocol J2ME Java 2 Micro Edition JAD Java Application Description JAD Java Decompiler JVM Java Virtual Machine MIP Mobile Internet Protocol NAS Network Access Server RAM Random Access Memory ROM Read-Only Memory TCM Telecommunication Management TOdb Timeout Database
- Embodiments of the present invention may be embodied as, among other things: a method, system, or set of instructions embodied on one or more computer-readable media.
- Computer-readable media include both volatile and nonvolatile media, removable and nonremovable media, and contemplates media readable by a database, a switch, and various other network devices.
- Computer-readable media comprise media implemented in any method or technology for storing information. Examples of stored information include computer-useable instructions, data structures, program modules, and other data representations.
- Media examples include, but are not limited to information-delivery media, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD), holographic media or other optical disc storage, magnetic cassettes, magnetic tape, magnetic disk storage, and other magnetic storage devices. These technologies can store data momentarily, temporarily, or permanently.
- Implementations of embodiments of the present invention introduce a new set of protocol directives for the HTTP Expect request header for proxy/server control.
- http.proxy.timeout is used to indicate the timeout behavior for proxy gateways
- http.timeout is used to indicate the timeout behavior for all servers involved in satisfying the particular HTTP session on an end-to-end basis
- http.proxy.global.timeout is used to indicate the default timeout to be used by servers attending requests from the issuing clients.
- Implementations of embodiments of the present invention also introduce qualifying application protocol expectations for the http.proxy.global.timeout directive to control the extent of timeout behavior with a user agent, which would be used by an application to modify the server/proxy timeout behavior when serving a specific user agent; a terminal identifier, controlling server/proxy timeout logic when serving specific terminals; a user identifier, allowing control over server/proxy timeouts when serving a specific user; a content type, extending server/proxy timeout control into specific content types; and a location, which sets specific timeouts at the server/proxy for content located in specified hosts and/or paths.
- Implementations of embodiments of the present invention further defines Java Application Description (JAD) attributes that would force HTTP stacks for connections for a particular J2ME application to be qualified as instructed.
- the application management system (AMS) would verify that the J2ME application is authorized to use the new directives, and upon detecting launch of the application, convey session or global changes needed to meet the application's agreement.
- Implementations of embodiments of the present invention yet further creates a dynamic timeout management server (DTMS), which is trusted by proxy servers. Proxy servers also delegate responsibility to the DTMS to verify whether timeout modification directives are authorized.
- the DTMS is responsible for dynamically determining whether timeout adjustments must be performed based on recent system performance and behavior.
- Implementations of embodiments of the present invention finally modify compliant servers and proxies to have timeout databases (TOdb) replicated from a designated centralized timeout database connected to the DTMS.
- the servers' and proxies' timeout databases are locally-managed or regionally-managed timeout databases as opposed to the centralized timeout database, which is global timeout database.
- the servers and proxies, along with their respective locally-managed timeout databases enforce multiple timeout settings to accommodate user agents, terminal identifiers, user identifiers, content types, and locations at a global or session level.
- the locally-managed or regionally-managed timeout databases are controlled through replication of requests into the DTMS, which may exemplary look as follows:
- the DTMS determines conditions where timeouts cross preset thresholds and automatically instruct the proxy/server to change its behavior either by increasing times or decreasing times at the occurrence of an event.
- the DTMS is also responsible for stripping from HTTP requests new directives that are defined herein should the DTMS determine that a proxy/server does not support certain features.
- an exemplary network 100 for dynamically adjusting timeout values is shown with mobile devices 103 and 113 , servers 120 and 130 , timeout databases 125 and 135 , Internet 140 , a content provider 145 , a DTMS 150 , a centralized timeout database 155 , business supporting systems (BSS) 160 , and a computer 165 .
- Network 100 provides exemplary components to adjust timeout values for mobile devices 103 and 113 , and content provider 145 .
- mobile device 103 can include an AMS 104 , JAD 105 , JVM 106 , APP 107 , and TCM 108 .
- AMS 104 allows mobile device 103 to support an AUD-mode service.
- JAD 105 provides a decompiler for the Java programming language.
- JVM 106 provides a Java Virtual Machine that enables the execution of other computer programs, applications, or scripts in mobile device 103 .
- APP 107 represents a number of applications located on mobile device 103 .
- TCM 103 identifies the telecommunications or telephone aspects of mobile device 103 . It is noted that mobile device 113 has the same components as mobile device 103 . Thus, the internals of mobile device 113 are not repeated and discussed again.
- Mobile device 103 attempts to access web content from content provider 145 .
- Mobile device 103 connects to gateway server 120 , which connects through the Internet 140 to content provider 145 .
- Gateway server 120 keeps track of the amount of time for mobile device 103 and content provider 120 to respond to each other.
- the amounts of time expected for mobile device 103 and content provider 120 to respond are kept in respective time parameters which are stored in locally-managed or regionally-managed timeout database 125 connected to gateway server 120 .
- mobile device 113 connects to gateway server 130 , which is connected to timeout database 135 .
- DTMS 150 connects to gateway servers 120 and 130 .
- the DTMS 150 monitors the responses transmitted through gateway servers 120 and 130 . Over time, DTMS 150 can establish a behavior or baseline for the value of timeout parameters for mobile device 103 and content provider 145 . If the response time is exceeded over a period of time, DTMS 150 can modify the amount of time for a device to respond in its timeout parameter to a new value, minimizing the change for reaching the timeout value.
- the DTMS 150 works to increase and decrease timeout values in timeout parameters by monitoring the behavior of devices such as mobile device 103 and content provider 145 .
- mobile device 103 may send a request for web content from content provider 145 .
- Content provider 145 may respond in a faster time than normal.
- DTMS 150 may decrease the amount of time in the timeout parameter for content provider 145 .
- congestion may exist in the network causing content provider 145 to take more time than normal to respond to mobile device 103 .
- timeouts for content provider 145 may occur more frequently causing gateway server 120 to cut off communications with content provider 145 when the timeout parameter is reached.
- DTMS 150 may increase the amount of time that gateway server 120 waits for content provider 145 to respond.
- This new timeout parameter is stored in centralized timeout database 155 .
- This new timeout parameter is also replicated in timeout database 125 , but not replicated in timeout database 135 .
- Centralized timeout database 155 is a global database for all information while timeout database 125 is a locally-managed or regionally-managed database.
- DTMS 150 The efforts of DTMS 150 to dynamically change timeout parameters ensure an efficient operation of devices in their communications with each other. Timeouts of devices are reduced over time since DTMS 150 monitors the retry attempts as well as the timeout that occurs. Regular maintenance or servicing of DTMS 150 may occur through BSS 160 .
- DTMS 150 has a connection to BSS 160 for various business services that may require access to it. BSS 160 can be manipulated or accessed by a user operating computer 165 .
- DTMS 150 monitors amounts of time for gateway server 120 to exchange information between a set of devices such as mobile devices 103 and 113 , and content provider 145 .
- the amounts of time it takes for mobile device 103 , mobile device 113 , and content provider 145 to communicate with gateway servers 120 and 130 are stored in centralized timeout database 155 .
- a timeout parameter is obtained for each of the devices from gateway servers 120 and 130 .
- Each of the devices includes mobile device 103 , mobile device 113 , and content provider 145 .
- the timeout parameter for each of the devices is stored in centralized timeout database 155 in a step 220 . It is noted that although centralized timeout database 155 stores the amounts of time and timeout parameters for mobile device 103 , mobile device 113 , and content provider 145 on a global basis, timeout database 125 stores amounts of time and timeout parameters on a local or regional basis for mobile device 103 and content provider 145 . Timeout database 135 stores amounts of time and timeout parameters on a local or regional basis for mobile 113 and content provider 145 .
- a device (mobile device 103 ) exceeds its wait time defined in the timeout parameter, in a step 225 , communication is terminated with the device.
- an indication is received from gateway server 120 that the amount of time for the response from mobile device 103 has reached a value of the timeout parameter.
- mobile device 103 may make several attempts to connect to content provider 145 through gateway server 120 . Upon each attempt, the communication will be terminated if the value in the timeout parameter is exceeded.
- DTMS 150 monitors the behavior and interactions of mobile device 103 .
- DTMS 150 adjusts the amount of time in the timeout parameter associated with mobile device 103 to a new timeout parameter to prevent a timeout.
- DTMS 150 can make incremental increases in the new timeout parameter until a successful connection is made by mobile device 103 , preventing a timeout.
- the new timeout parameter is stored in centralized timeout database 155 in place of the original or previous timeout parameter.
- the new timeout parameter is associated with mobile device 103 .
- DTMS 150 instructs gateway server 120 to use the new timeout parameter in place of the original or previous timeout parameter for mobile device 103 .
- DTMS 150 interacts with gateway server 130 to monitor and manage a timeout parameter for mobile device 113 .
- DTMS 150 may interact with both gateway servers 120 and 130 to monitor and manage a timeout parameter for content provider 145 .
- one timeout parameter may exist for content provider 145 that is stored in centralized timeout database 155 , which can be monitored by DTMS 150 at both gateway servers 120 and 130 .
- two timeout parameters can exist for content provider 145 with both being stored in centralized timeout database 155 .
- One timeout parameter can exist for communications that occur through gateway server 120 and another timeout parameter can exist for communications that occur through gateway server 130 . The idea here is to note that communications through different parts of the network may evoke different responses.
- a successful communication by content provider through one part of the network may give rise to an entirely different response when the communication is made through an entirely different part of the network. For example, congestion may appear at some point of the communication with gateway server 130 that does not exist with communications with gateway server 120 . Therefore, an implementer may desire to have multiple timeout parameters for the same device (content provider 145 ) to address each communication situation.
- a timeout parameter can be changed for a device when the amount of time is more than sufficient in the timeout parameter.
- mobile device 103 may have a timeout parameter that is defined as twenty (20) milliseconds for a response.
- DTMS 150 may determine that it only takes mobile device 103 five (5) milliseconds or less to respond. As a result, DTMS 150 may lower the value in the timeout parameter to a new value of eight (8) milliseconds. This new value can be stored as a new timeout parameter in centralized timeout database 155 .
- DTMS 150 will instruct gateway server 120 to use the new timeout parameter for mobile device 103 .
- the new timeout parameter is also stored timeout database 125 .
- gateway server 120 provides amounts of time for gateway server 120 to exchange information between mobile device 103 and content provider 145 .
- the amounts of time are provided to DTMS 150 .
- the amounts of time are times it take for mobile device 103 and content provider 145 to communicate with each other through gateway server 120 .
- the amounts of time are collected by DTMS 150 and stored in centralized timeout database 155 .
- gateway server 120 provides a timeout parameter for mobile device 103 and content provider 145 to DTMS 150 .
- the timeout parameter for each device is an amount of time gateway server 120 waits for a response from mobile device 103 or content provider 145 .
- the timeout parameters are stored for each device in centralized timeout database 155 .
- gateway server 120 determines when a timeout parameter for a device is reached. When the timeout parameter is reached, gateway server 120 terminates communication with the device. More particularly in a step 320 , communication with the device is terminated when the amount of time reaches a value of the timeout parameter.
- a new timeout parameter is received from DTMS 150 to replace the original or previous timeout parameter for the device.
- the new timeout parameter represents the amount of time that has been adjusted in the timeout parameter to prevent a timeout.
- the new timeout parameter is stored in place of the timeout parameter in a locally-managed or regionally-managed timeout database 125 connected to gateway server 120 .
- the new timeout parameter is associated with the device.
- gateway server 120 implements the new timeout parameter in place of the original or previous timeout parameter for the device.
Abstract
Description
AAA | Authentication, Authorization, and Accounting | ||
AMS | Application Management System | ||
APP | Application | ||
AT | Access Terminal | ||
AUD | Authentication User Delegate | ||
BSS | Business Supporting Systems | ||
CD-ROM | Compact Disc—Read-Only Memory | ||
EEPROM | Electronically Erasable Programmable | ||
Read-Only Memory | |||
IP | Internet Protocol | ||
J2ME | Java 2 Micro Edition | ||
JAD | Java Application Description | ||
JAD | Java Decompiler | ||
JVM | Java Virtual Machine | ||
MIP | Mobile Internet Protocol | ||
NAS | Network Access Server | ||
RAM | Random Access Memory | ||
ROM | Read-Only Memory | ||
TCM | Telecommunication Management | ||
TOdb | Timeout Database | ||
Claims (12)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/634,063 US7953870B1 (en) | 2009-12-09 | 2009-12-09 | Dynamic HTTP service timeout adjustment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/634,063 US7953870B1 (en) | 2009-12-09 | 2009-12-09 | Dynamic HTTP service timeout adjustment |
Publications (1)
Publication Number | Publication Date |
---|---|
US7953870B1 true US7953870B1 (en) | 2011-05-31 |
Family
ID=44064165
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/634,063 Active US7953870B1 (en) | 2009-12-09 | 2009-12-09 | Dynamic HTTP service timeout adjustment |
Country Status (1)
Country | Link |
---|---|
US (1) | US7953870B1 (en) |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100257525A1 (en) * | 2009-04-03 | 2010-10-07 | Jianwen Yin | Dynamically Calculating And Applying A Timeout Value To A Manufacturer Update Service |
US20100309195A1 (en) * | 2009-06-08 | 2010-12-09 | Castleman Mark | Methods and apparatus for remote interaction using a partitioned display |
US20100310193A1 (en) * | 2009-06-08 | 2010-12-09 | Castleman Mark | Methods and apparatus for selecting and/or displaying images of perspective views of an object at a communication device |
US20100311393A1 (en) * | 2009-06-08 | 2010-12-09 | Castleman Mark | Methods and apparatus for distributing, storing, and replaying directives within a network |
CN102855311A (en) * | 2012-08-24 | 2013-01-02 | 乐视网信息技术(北京)股份有限公司 | Intelligent file resource loader and intelligent file resource loading method |
US8745245B1 (en) * | 2011-09-15 | 2014-06-03 | Google Inc. | System and method for offline detection |
WO2014047036A3 (en) * | 2012-09-18 | 2014-06-05 | Amazon Technologies, Inc. | Adaptive service timeouts |
US20140195861A1 (en) * | 2013-01-09 | 2014-07-10 | Microsoft Corporation | Implementing rate controls to limit timeout-based faults |
US8971908B1 (en) | 2012-12-11 | 2015-03-03 | Google Inc. | Apparatus and method for configuring network connection parameters of a mobile device |
US20160013968A1 (en) * | 2014-07-14 | 2016-01-14 | Dell Products, L.P. | Common information model (cim) object transfer via requestor statistical tracking |
US9703597B2 (en) | 2015-11-24 | 2017-07-11 | International Business Machines Corporation | Dynamic timeout period adjustment of service requests |
US9935730B1 (en) | 2014-05-12 | 2018-04-03 | Google Llc | Systems and methods for using radio layer information to enhance network transfer protocols |
US10075877B1 (en) * | 2014-05-12 | 2018-09-11 | Google Llc | Systems and methods for using radio layer information to enhance network transfer protocols |
US10212194B2 (en) * | 2014-01-20 | 2019-02-19 | Google Llc | Server controlled throttling of client to server requests |
CN110012093A (en) * | 2019-04-02 | 2019-07-12 | 北京奇艺世纪科技有限公司 | A kind of method and device of adjustment connection time-out time |
US10389513B2 (en) | 2017-01-26 | 2019-08-20 | Hewlett Packard Enterprise Development Lp | Dynamic adjustment of wait time values |
US10979896B2 (en) | 2018-11-20 | 2021-04-13 | International Business Machines Corporation | Managing dynamic lockouts on mobile computing devices |
US11249798B1 (en) * | 2020-09-16 | 2022-02-15 | International Business Machines Corporation | Personalized timeout control |
US11375023B2 (en) | 2019-12-02 | 2022-06-28 | International Business Machines Corporation | Dynamically configuring a web server timeout |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030084161A1 (en) * | 2001-09-17 | 2003-05-01 | Watson Thomas Lee | System and method for router keep-alive control |
US20030088677A1 (en) * | 2001-11-05 | 2003-05-08 | International Business Machines Corporation | Network system, server, client terminal, timeout information providing method, timeout information display method, and programs |
US20050102393A1 (en) * | 2003-11-12 | 2005-05-12 | Christopher Murray | Adaptive load balancing |
US20050240665A1 (en) * | 1999-06-11 | 2005-10-27 | Microsoft Corporation | Dynamic self-configuration for ad hoc peer networking |
US20060080410A1 (en) * | 2002-11-15 | 2006-04-13 | Maclarty Glen M | Method and apparatus for forming and maintaining a network of devices |
US20060184661A1 (en) * | 2000-12-01 | 2006-08-17 | Microsoft Corporation | Peer networking host framework and hosting API |
US20070074062A1 (en) * | 2005-09-27 | 2007-03-29 | Chang Nai-Chih | Universal timeout mechanism |
US20070083813A1 (en) * | 2005-10-11 | 2007-04-12 | Knoa Software, Inc | Generic, multi-instance method and GUI detection system for tracking and monitoring computer applications |
US20080104259A1 (en) * | 2006-10-28 | 2008-05-01 | Lefevre Marc | Methods and systems for communicating with storage devices in a storage system |
US20080288607A1 (en) * | 2002-03-07 | 2008-11-20 | Cisco Technology, Inc. | Method and apparatus for exchanging heartbeat messages and configuration information between nodes operating in a master-slave configuration |
US20100056109A1 (en) * | 2002-07-17 | 2010-03-04 | Research In Motion Limited | Method, system and apparatus for messaging between wireless mobile terminals and networked computers |
US20100211959A1 (en) * | 2009-02-13 | 2010-08-19 | Oracle International Corporation | Adaptive cluster timer manager |
-
2009
- 2009-12-09 US US12/634,063 patent/US7953870B1/en active Active
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050240665A1 (en) * | 1999-06-11 | 2005-10-27 | Microsoft Corporation | Dynamic self-configuration for ad hoc peer networking |
US20060184661A1 (en) * | 2000-12-01 | 2006-08-17 | Microsoft Corporation | Peer networking host framework and hosting API |
US20030084161A1 (en) * | 2001-09-17 | 2003-05-01 | Watson Thomas Lee | System and method for router keep-alive control |
US20030088677A1 (en) * | 2001-11-05 | 2003-05-08 | International Business Machines Corporation | Network system, server, client terminal, timeout information providing method, timeout information display method, and programs |
US20080288607A1 (en) * | 2002-03-07 | 2008-11-20 | Cisco Technology, Inc. | Method and apparatus for exchanging heartbeat messages and configuration information between nodes operating in a master-slave configuration |
US20100056109A1 (en) * | 2002-07-17 | 2010-03-04 | Research In Motion Limited | Method, system and apparatus for messaging between wireless mobile terminals and networked computers |
US20060080410A1 (en) * | 2002-11-15 | 2006-04-13 | Maclarty Glen M | Method and apparatus for forming and maintaining a network of devices |
US20050102393A1 (en) * | 2003-11-12 | 2005-05-12 | Christopher Murray | Adaptive load balancing |
US20070074062A1 (en) * | 2005-09-27 | 2007-03-29 | Chang Nai-Chih | Universal timeout mechanism |
US20070083813A1 (en) * | 2005-10-11 | 2007-04-12 | Knoa Software, Inc | Generic, multi-instance method and GUI detection system for tracking and monitoring computer applications |
US20080104259A1 (en) * | 2006-10-28 | 2008-05-01 | Lefevre Marc | Methods and systems for communicating with storage devices in a storage system |
US20100211959A1 (en) * | 2009-02-13 | 2010-08-19 | Oracle International Corporation | Adaptive cluster timer manager |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100257525A1 (en) * | 2009-04-03 | 2010-10-07 | Jianwen Yin | Dynamically Calculating And Applying A Timeout Value To A Manufacturer Update Service |
US10353683B2 (en) * | 2009-04-03 | 2019-07-16 | Dell Products L.P. | Dynamically calculating and applying a timeout value to a manufacturer update service |
US20100309195A1 (en) * | 2009-06-08 | 2010-12-09 | Castleman Mark | Methods and apparatus for remote interaction using a partitioned display |
US20100310193A1 (en) * | 2009-06-08 | 2010-12-09 | Castleman Mark | Methods and apparatus for selecting and/or displaying images of perspective views of an object at a communication device |
US20100311393A1 (en) * | 2009-06-08 | 2010-12-09 | Castleman Mark | Methods and apparatus for distributing, storing, and replaying directives within a network |
US8286084B2 (en) | 2009-06-08 | 2012-10-09 | Swakker Llc | Methods and apparatus for remote interaction using a partitioned display |
US8745245B1 (en) * | 2011-09-15 | 2014-06-03 | Google Inc. | System and method for offline detection |
CN102855311A (en) * | 2012-08-24 | 2013-01-02 | 乐视网信息技术(北京)股份有限公司 | Intelligent file resource loader and intelligent file resource loading method |
US9292039B2 (en) | 2012-09-18 | 2016-03-22 | Amazon Technologies, Inc. | Adaptive service timeouts |
WO2014047036A3 (en) * | 2012-09-18 | 2014-06-05 | Amazon Technologies, Inc. | Adaptive service timeouts |
US10263876B2 (en) | 2012-09-18 | 2019-04-16 | Amazon Technologies, Inc. | Adaptive service timeouts |
US8971908B1 (en) | 2012-12-11 | 2015-03-03 | Google Inc. | Apparatus and method for configuring network connection parameters of a mobile device |
US9229839B2 (en) * | 2013-01-09 | 2016-01-05 | Microsoft Technology Licensing, Llc | Implementing rate controls to limit timeout-based faults |
US20140195861A1 (en) * | 2013-01-09 | 2014-07-10 | Microsoft Corporation | Implementing rate controls to limit timeout-based faults |
US10212194B2 (en) * | 2014-01-20 | 2019-02-19 | Google Llc | Server controlled throttling of client to server requests |
US10075877B1 (en) * | 2014-05-12 | 2018-09-11 | Google Llc | Systems and methods for using radio layer information to enhance network transfer protocols |
US9935730B1 (en) | 2014-05-12 | 2018-04-03 | Google Llc | Systems and methods for using radio layer information to enhance network transfer protocols |
US9596158B2 (en) * | 2014-07-14 | 2017-03-14 | Dell Products, L.P. | Common information model (CIM) object transfer via requestor statistical tracking |
US20160013968A1 (en) * | 2014-07-14 | 2016-01-14 | Dell Products, L.P. | Common information model (cim) object transfer via requestor statistical tracking |
US9710302B2 (en) | 2015-11-24 | 2017-07-18 | International Business Machines Corporation | Dynamic timeout period adjustment of service requests |
US9703597B2 (en) | 2015-11-24 | 2017-07-11 | International Business Machines Corporation | Dynamic timeout period adjustment of service requests |
US10389513B2 (en) | 2017-01-26 | 2019-08-20 | Hewlett Packard Enterprise Development Lp | Dynamic adjustment of wait time values |
US10979896B2 (en) | 2018-11-20 | 2021-04-13 | International Business Machines Corporation | Managing dynamic lockouts on mobile computing devices |
CN110012093A (en) * | 2019-04-02 | 2019-07-12 | 北京奇艺世纪科技有限公司 | A kind of method and device of adjustment connection time-out time |
CN110012093B (en) * | 2019-04-02 | 2021-12-24 | 北京奇艺世纪科技有限公司 | Method and device for adjusting connection timeout |
US11375023B2 (en) | 2019-12-02 | 2022-06-28 | International Business Machines Corporation | Dynamically configuring a web server timeout |
US11249798B1 (en) * | 2020-09-16 | 2022-02-15 | International Business Machines Corporation | Personalized timeout control |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7953870B1 (en) | Dynamic HTTP service timeout adjustment | |
US8111631B2 (en) | Systems and methods for automatic configuration of customer premises equipments | |
US9521150B2 (en) | System and method for automatically regulating messages between networks | |
US7873733B2 (en) | Load distribution method, load distribution device, and system including load distribution device | |
JP4664977B2 (en) | Device management method for device management system | |
EP1940077B1 (en) | Remote activation of home devices | |
US10496397B2 (en) | System and method for providing automatic firmware update management | |
US20090112778A1 (en) | Method and Apparatus for Leveraging End User Terminals in Self-Learning Networks | |
KR20140091704A (en) | System comprising a publish/subscribe broker for a remote management of end-user devices, and respective end-user device | |
RU2533638C2 (en) | Data configuration method and device | |
US20070274314A1 (en) | System and method for creating application groups | |
US10153976B2 (en) | Adaptive load balancing in residential hybrid gateways | |
EP2374244B1 (en) | Communications system and method | |
WO2017125017A1 (en) | Method for adjusting cache content, device, and system | |
US20120331164A1 (en) | Load sharing method, system and access server | |
US20230224722A1 (en) | Dynamic Adjustment of Deployment Location of Software Within a Network | |
KR20170140812A (en) | A load balancing server for forwarding prioritized traffic from one or more prioritized autoconfiguration servers and to one or more prioritized autoconfiguration servers | |
CA2619051A1 (en) | Resource selection in a communication network | |
CN109600436B (en) | Distributed iscsi service implementation method, system and related device | |
EP2887580A1 (en) | Method and system for modifying configuration parameters on a user equipment and an Auto Configuration Server-Gateway | |
CN112217661A (en) | Port mode self-adaption method and device | |
KR20110059919A (en) | Network access management method and apparatus for access restriction of abnormal station using web redirect | |
JP4864128B2 (en) | Communication system and communication program | |
WO2009006770A1 (en) | Method of p2p node management | |
Cisco | Chapter 1: Cisco Cache Software Basic Configuration |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:REEVES, RAYMOND EMILIO;KARKI, PRABHAT;LAMSAL, SAILESH;AND OTHERS;SIGNING DATES FROM 20091202 TO 20091208;REEL/FRAME:023629/0196 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK Free format text: GRANT OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:SPRINT COMMUNICATIONS COMPANY L.P.;REEL/FRAME:041895/0210 Effective date: 20170203 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
AS | Assignment |
Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: TERMINATION AND RELEASE OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:052969/0475 Effective date: 20200401 Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNORS:T-MOBILE USA, INC.;ISBV LLC;T-MOBILE CENTRAL LLC;AND OTHERS;REEL/FRAME:053182/0001 Effective date: 20200401 |
|
AS | Assignment |
Owner name: T-MOBILE INNOVATIONS LLC, KANSAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SPRINT COMMUNICATIONS COMPANY L.P.;REEL/FRAME:055604/0001 Effective date: 20210303 |
|
AS | Assignment |
Owner name: SPRINT SPECTRUM LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINT INTERNATIONAL INCORPORATED, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINT COMMUNICATIONS COMPANY L.P., KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: SPRINTCOM LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: CLEARWIRE IP HOLDINGS LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: CLEARWIRE COMMUNICATIONS LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: BOOST WORLDWIDE, LLC, KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: ASSURANCE WIRELESS USA, L.P., KANSAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: T-MOBILE USA, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: T-MOBILE CENTRAL LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: PUSHSPRING, LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: LAYER3 TV, LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 Owner name: IBSV LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS;REEL/FRAME:062595/0001 Effective date: 20220822 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |