Patent Grant
9647950
Embodiments of the present disclosure relate generally to data processing and, more particularly, but not by way of limitation, to systems and methods of site traffic control.
Online services (e.g., websites) can suffer from a high volume of user traffic (e.g., requests). High volume traffic can overwhelm an online service and result in a server shutdown or other service failure.
Some embodiments of the present disclosure are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like reference numbers indicate similar elements.
The headings provided herein are merely for convenience and do not necessarily affect the scope or meaning of the terms used.
The description that follows includes illustrative systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art that embodiments of the inventive subject matter can be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques have not been shown in detail.
The present disclosure provides technical solutions for managing traffic for an online service. In some example embodiments, a traffic control system implements a queueing system around an application of an online service. When traffic control system determines that the application has reached its capacity or is within a predetermined range of reaching its capacity, the traffic control system can then issue, to a user submitting a request to the online service, a token and an estimated time parameter, such as a window of time, for the user to attempt submitting another request. The estimated time can correspond to a time determined by the traffic control system to be when the application can better handle the request (e.g., when the application is not at capacity). When the user with the token submits a subsequent request in accordance with the time parameter (e.g., within the window of time), the traffic control system can service that request ahead of other requests. In this fashion, the traffic control system can avoid overloading the online service and can provide an estimated wait time for the user. The traffic control system can also notify the user, at the occurrence of or at a predetermined amount of time before the estimated time parameter, that the user can attempt to submit the request again and expect a quick response.
In some example embodiments, the traffic control system can determine a level of the degree to which the online service is overloaded. The traffic control system can then generate different types of overload notifications to present to a user based on the determined level. The traffic control system can also determine a standard of restriction based on the determined level, and then apply the determined standard of restriction in determining which user requests to satisfy and which user requests to temporarily deny.
Systems and methods of site traffic control are disclosed herein. In some example embodiments, a first request for an online service to perform an operation is received from a first user on a first client device, and at least one overload condition for the online service is detected, or otherwise determined, with the overload condition(s) corresponding to a first request time of the first request. A first token and a first return time parameter for the first user are determined based on the determination of the overload condition, and the first token is stored in association with the first return time parameter. The first token and the first return time parameter are transmitted to the first client device. A second request for the online service to perform the operation is received from the first user. The second request has a corresponding time and comprises the first token. The first return time parameter is identified based on the first token. A determination is made that the corresponding time of the second request satisfies the first return time parameter, and the operation is performed in response to, or otherwise based on, the determination that the corresponding time of the second request satisfies the first return time parameter. Variations on the operations recited above, as well as other embodiments, are also within the scope of the present disclosure.
In some example embodiments, the operation comprises enabling the first user to access a page of the online service. In some example embodiments, the overload condition(s) comprises at least one of a traffic level of the online service satisfying one or more predetermined traffic level criteria, a network connection speed of the online service satisfying one or more predetermined network connection speed criteria, and a server speed of the online service satisfying one or more predetermined server speed criteria.
In some example embodiments, the first return time parameter comprises a specified time or a specified window of time. In some example embodiments, determining the first return time parameter comprises estimating a load level of the online service for a future time, the future time being subsequent to the first request time, determining that the estimated load level satisfies one or more return time criteria, and defining the first return time parameter to include the future time based on the determining that the estimated load level satisfies the one or more return time criteria.
In some example embodiments, transmitting the first token to the first client device comprises transmitting a cookie to the first client device, the cookie comprising the first token.
In some example embodiments, a determination is made that a current time is within a predetermined amount of time of the first return time parameter, and a return time notification is transmitted to the first user based on the determining that the current time is within the predetermined amount of time of the first return time parameter, with the return time notification being configured to indicate to the first user to request the operation again.
In some example embodiments, an overload level is selected from a plurality of overload levels based on the at least one overload condition, an overload notification is generated based on the selected overload level, with the overload notification comprising an indication of the overload level, and the overload notification is caused to be displayed on the first client device.
In some example embodiments, a standard of restriction is selected from a plurality of standards of restriction based on the at least one overload condition, the first user is denied access to the operation of the online service based on the selected standard of restriction, and a second user is allowed access to the operation of the online service based on the selected standard of restriction.
The methods or embodiments disclosed herein can be implemented as a computer system having one or more modules (e.g., hardware modules or software modules). Such modules can be executed by one or more processors of the computer system. The methods or embodiments disclosed herein can be embodied as instructions stored on a machine-readable medium that, when executed by one or more processors, cause the one or more processors to perform the instructions.
With reference to
The client device 110 may comprise, but are not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), smart phones, tablets, ultra books, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may utilize to access the networked system 102. In some embodiments, the client device 110 may comprise a display module (not shown) to display information (e.g., in the form of user interfaces). In further embodiments, the client device 110 may comprise one or more of a touch screens, accelerometers, gyroscopes, cameras, microphones, global positioning system (GPS) devices, and so forth. The client device 110 may be a device of a user that is used to perform a transaction involving digital items within the networked system 102. In one embodiment, the networked system 102 is a network-based marketplace that responds to requests for product listings, publishes publications comprising item listings of products available on the network-based marketplace, and manages payments for these marketplace transactions. One or more users 106 may be a person, a machine, or other means of interacting with client device 110. In embodiments, the user 106 is not part of the network architecture 100, but may interact with the network architecture 100 via client device 110 or another means. For example, one or more portions of network 104 may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular telephone network, a wireless network, a WiFi network, a WiMax network, another type of network, or a combination of two or more such networks.
Each of the client device 110 may include one or more applications (also referred to as “apps”) such as, but not limited to, a web browser, messaging application, electronic mail (email) application, an e-commerce site application (also referred to as a marketplace application), and the like. In some embodiments, if the e-commerce site application is included in a given one of the client device 110, then this application is configured to locally provide the user interface and at least some of the functionalities with the application configured to communicate with the networked system 102, on an as needed basis, for data and/or processing capabilities not locally available (e.g., access to a database of items available for sale, to authenticate a user, to verify a method of payment, etc.). Conversely if the e-commerce site application is not included in the client device 110, the client device 110 may use its web browser to access the e-commerce site (or a variant thereof) hosted on the networked system 102.
One or more users 106 may be a person, a machine, or other means of interacting with the client device 110. In example embodiments, the user 106 is not part of the network architecture 100, but may interact with the network architecture 100 via the client device 110 or other means. For instance, the user provides input (e.g., touch screen input or alphanumeric input) to the client device 110 and the input is communicated to the networked system 102 via the network 104. In this instance, the networked system 102, in response to receiving the input from the user, communicates information to the client device 110 via the network 104 to be presented to the user. In this way, the user can interact with the networked system 102 using the client device 110.
An application program interface (API) server 120 and a web server 122 are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers 140. The application servers 140 may host one or more publication systems 142 and payment systems 144, each of which may comprise one or more modules or applications and each of which may be embodied as hardware, software, firmware, or any combination thereof. The application servers 140 are, in turn, shown to be coupled to one or more database servers 124 that facilitate access to one or more information storage repositories or database(s) 126. In an example embodiment, the databases 126 are storage devices that store information to be posted (e.g., publications or listings) to the publication system 120. The databases 126 may also store digital item information in accordance with example embodiments.
Additionally, a third party application 132, executing on third party server(s) 130, is shown as having programmatic access to the networked system 102 via the programmatic interface provided by the API server 120. For example, the third party application 132, utilizing information retrieved from the networked system 102, supports one or more features or functions on a website hosted by the third party. The third party website, for example, provides one or more promotional, marketplace, or payment functions that are supported by the relevant applications of the networked system 102.
The publication systems 142 may provide a number of publication functions and services to users 106 that access the networked system 102. The payment systems 144 may likewise provide a number of functions to perform or facilitate payments and transactions. While the publication system 142 and payment system 144 are shown in
The traffic control system 150 may provide functionality operable to perform various traffic control operations, as will be discussed in further detail below. The traffic control system 150 may access the data from the databases 126, the third party servers 130, the publication system 120, and other sources. In some example embodiments, the traffic control system 150 may analyze the data to perform traffic control operations. In some example embodiments, the traffic control system 150 may communicate with the publication systems 120 (e.g., accessing item listings) and payment system 122. In an alternative embodiment, the traffic control system 150 may be a part of the publication system 120.
Further, while the client-server-based network architecture 100 shown in
The web client 112 may access the various publication and payment systems 142 and 144 via the web interface supported by the web server 122. Similarly, the programmatic client 116 accesses the various services and functions provided by the publication and payment systems 142 and 144 via the programmatic interface provided by the API server 120. The programmatic client 116 may, for example, be a seller application (e.g., the Turbo Lister application developed by eBay® Inc., of San Jose, Calif.) to enable sellers to author and manage listings on the networked system 102 in an off-line manner, and to perform batch-mode communications between the programmatic client 116 and the networked system 102.
Additionally, a third party application(s) 128, executing on a third party server(s) 130, is shown as having programmatic access to the networked system 102 via the programmatic interface provided by the API server 114. For example, the third party application 128, utilizing information retrieved from the networked system 102, may support one or more features or functions on a website hosted by the third party. The third party website may, for example, provide one or more promotional, marketplace, or payment functions that are supported by the relevant applications of the networked system 102.
The publication system 142 can provide a number of publishing, listing, and/or price-setting mechanisms whereby a seller (also referred to as a first user) can list (or publish information concerning) goods or services for sale or barter, a buyer (also referred to as a second user) can express interest in or indicate a desire to purchase or barter such goods or services, and a transaction (such as a trade) can be completed pertaining to the goods or services. To this end, the publication system 142 can comprise at least one publication engine 202 and one or more selling engines 204. The publication engine 202 can publish information, such as item listings or product description pages, on the publication system 142. In some embodiments, the selling engines 204 can comprise one or more fixed-price engines that support fixed-price listing and price setting mechanisms and one or more auction engines that support auction-format listing and price setting mechanisms (e.g., English, Dutch, Chinese, Double, Reverse auctions, etc.). The various auction engines can also provide a number of features in support of these auction-format listings, such as a reserve price feature whereby a seller can specify a reserve price in connection with a listing and a proxy-bidding feature whereby a bidder can invoke automated proxy bidding. The selling engines 204 can further comprise one or more deal engines that support merchant-generated offers for products and services.
A listing engine 206 allows sellers to conveniently author listings of items or authors to author publications. In one embodiment, the listings pertain to goods or services that a user (e.g., a seller) wishes to transact via the publication system 142. In some embodiments, the listings can be an offer, deal, coupon, or discount for the good or service. Each good or service is associated with a particular category. The listing engine 206 can receive listing data such as title, description, and aspect name/value pairs. Furthermore, each listing for a good or service can be assigned an item identifier. In other embodiments, a user can create a listing that is an advertisement or other form of information publication. The listing information can then be stored to one or more storage devices coupled to the publication system 142 (e.g., databases 126). Listings also can comprise product description pages that display a product and information (e.g., product title, specifications, and reviews) associated with the product. In some embodiments, the product description page can include an aggregation of item listings that correspond to the product described on the product description page.
The listing engine 206 can also allow buyers to conveniently author listings or requests for items desired to be purchased. In some embodiments, the listings can pertain to goods or services that a user (e.g., a buyer) wishes to transact via the publication system 142. Each good or service is associated with a particular category. The listing engine 206 can receive as much or as little listing data, such as title, description, and aspect name/value pairs, that the buyer is aware of about the requested item. In some embodiments, the listing engine 206 can parse the buyer's submitted item information and can complete incomplete portions of the listing. For example, if the buyer provides a brief description of a requested item, the listing engine 206 can parse the description, extract key terms and use those terms to make a determination of the identity of the item. Using the determined item identity, the listing engine 206 can retrieve additional item details for inclusion in the buyer item request. In some embodiments, the listing engine 206 can assign an item identifier to each listing for a good or service.
In some embodiments, the listing engine 206 allows sellers to generate offers for discounts on products or services. The listing engine 206 can receive listing data, such as the product or service being offered, a price and/or discount for the product or service, a time period for which the offer is valid, and so forth. In some embodiments, the listing engine 206 permits sellers to generate offers from the sellers' mobile devices. The generated offers can be uploaded to the publication system 142 for storage and tracking.
Searching the publication system 142 is facilitated by a searching engine 208. For example, the searching engine 208 enables keyword queries of listings published via the publication system 142. In example embodiments, the searching engine 208 receives the keyword queries from a device of a user and conducts a review of the storage device storing the listing information. The review will enable compilation of a result set of listings that can be sorted and returned to the client device 110 of the user. The searching engine 208 can record the query (e.g., keywords) and any subsequent user actions and behaviors (e.g., navigations).
The searching engine 208 also can perform a search based on the location of the user. A user can access the searching engine 208 via a mobile device and generate a search query. Using the search query and the user's location, the searching engine 208 can return relevant search results for products, services, offers, auctions, and so forth to the user. The searching engine 208 can identify relevant search results both in a list form and graphically on a map. Selection of a graphical indicator on the map can provide additional details regarding the selected search result. In some embodiments, the user can specify as part of the search query a radius or distance from the user's current location to limit search results.
The searching engine 208 also can perform a search based on an image. The image can be taken from a camera or imaging component of a client device or can be accessed from storage.
In a further example, a navigation engine 210 allows users to navigate through various categories, catalogs, or inventory data structures according to which listings can be classified within the publication system 142. For example, the navigation engine 210 allows a user to successively navigate down a category tree comprising a hierarchy of categories (e.g., the category tree structure) until a particular set of listings is reached. Various other navigation applications within the navigation engine 210 can be provided to supplement the searching and browsing applications. The navigation engine 210 can record the various user actions (e.g., clicks) performed by the user in order to navigate down the category tree.
In some example embodiments, the overload determination module 310 is configured to receive, from a first user (e.g., user 106 in
In some example embodiments, the overload determination module 310 is further configured to detect at least one overload condition for the online service. The overload condition(s) can comprise any condition that would cause the online service to have reduced performance of one or more specified functions to at least a predetermined degree in response to the online service performing the specified function(s) for an additional user. Such overload conditions can include, but are not limited to, conditions related to a status and/or capacity of one or more databases of the online service, conditions related to a status and/or capacity of one or more servers of the online service, and conditions related to a status and/or capacity of a network of the online service. For example, in some example embodiments, the overload condition(s) can comprise at least one of a traffic level of the online service (e.g., a number of requests being processed during a particular time period, a number of requests being congested or stagnant during a particular time period) satisfying one or more predetermined traffic level criteria (e.g., exceed a predetermined threshold), a network connection speed of the online service satisfying one or more predetermined network connection speed criteria (e.g., the network connections speed is below a predetermined threshold), a server speed of the online service satisfying one or more predetermined server speed criteria (e.g., the server speed is below a predetermined threshold), and a determination of the number of available resources (e.g., databases, servers) of the online service. However, other types of overload conditions are also within the scope of the present disclosure.
In some example embodiments, the overload condition(s) corresponds to a request time at which the corresponding request is received by the overload determination module 310. For example, if a request is received by the overload determination module 310 at 8:43 AM, the overload condition(s) can be determined for 8:43 AM. In another example, overload conditions can be determined periodically by the overload determination module 310 independent of receiving a request, and then the overload condition(s) that have been determined at a time nearest to the reception of a request can be determined to be the overload condition(s) for that request.
In some example embodiments, the overload determination module 310 is further configured to perform one or more monitoring operations to determine any overload conditions. Examples of monitoring techniques that can be employed within the scope of the present disclosure include, but are not limited to, synthetic monitoring techniques. Synthetic monitoring comprises monitoring that is performed using a browser emulation or scripted recordings of web transactions, where behavioral scripts (or paths) are used to simulate an action or path that an end-user would take on a website or other online service. Those paths are then continuously monitored at specific intervals for performance (e.g., availability). Other types of monitoring techniques are also within the scope of the present disclosure. It is contemplated that the overload determination module 410 can perform monitoring techniques, such as synthetic monitoring, itself, or can alternatively receive an indication of an overload condition from an external source that performs such monitoring techniques.
In some example embodiments, the overload determination module 310 is configured to prevent the performance of the requested operation by the online service in response to, or otherwise based on, the determination of the overload condition(s). In some example embodiments, the overload determination module 310 is further configured to determine a first token and a first return time parameter for the first user based on the determination of the overload condition(s). The first token can comprise an identifier, such as a randomly generated number or alpha-numeric text. The first return time parameter can comprise any time condition that is to be satisfied in order for the online service to perform the requested operation for the first user. In some example embodiments, the first return time parameter comprises a specified time (e.g., 10:30 AM), such that the online service will perform the requested operation for the first user if the first user requests the operation again after the specified time has been reached. In some example embodiment, the first return time parameter comprises a specified window of time (e.g., 10:30 AM-12:30 PM), such that the online service will perform the requested operation for the first user if the first user requests the operation again within the specified window of time. However, it is contemplated that other return time parameters are also within the scope of the present disclosure.
In some example embodiments, the overload determination module 310 is further configured to determine the first return time parameter based on a determination of the soonest time at which one or more return time criteria can be satisfied. The return time criteria can represent criteria that indicated that the online service can adequately process the first user's request. This determination can be based on one or more factors, such as an estimated prediction of traffic flow, activity level, or other status indicators of the online service at future times. For example, the overload determination module 310 can estimate the soonest time at which its traffic flow will drop below a predetermined threshold, and then determine the first return time parameter based on that soonest time, such as making that soonest time the beginning of the window of time. Then ending of the window of time can be based on an estimate of the demand for the online service at future times as well.
In some example embodiments, the overload determination module 310 is configured to estimate a load level of the online service for a future time, determine that the estimated load level satisfies one or more return time criteria, and then define the first return time parameter to include the future time based on the determination that the estimated load level satisfies the one or more return time criteria.
In some example embodiments, the overload determination module 310 is further configured to store the first token in the database(s) 340 in association with the first return time parameter.
Referring back to
In some example embodiments, the overload determination module 310 is further configured to receive, from the first user, a second request for the online service to perform the operation at a corresponding time. The first token is received in association with the second request (e.g., via the cookie stored on the first client device).
In some example embodiments, the overload determination module 310 is further configured to identify the first return time parameter based on the first token received in association with the second request. The overload determination module 310 can identify the first return time parameter by looking up the first token stored in the database 340 and determining the first return time parameter that is stored in association with the first token.
In some example embodiments, the overload determination module 310 is further configured to determine whether or not the corresponding time of the second request satisfies the first return time parameter. For example, if the first return time parameter is a window of 10:30 AM-12:30 PM, and the corresponding time of the second request is 10:22 AM, then the overload determination module 310 would determine that the corresponding time of the second request does not satisfy the first return time parameter. On the other hand, given the same first return time parameter, if the corresponding time of the second request is 10:42 AM, then the overload determination module 310 would determine that the corresponding time of the second request does satisfy the first return time parameter.
In some example embodiments, the service module 320 is configured to perform the requested operation in response to the determination that the corresponding time of the second request satisfies the first return time parameter, and to prevent performance of the requested operation in response to the determination that the corresponding time of the second request does not satisfy the first return time parameter.
In some example embodiments, the notification module 310 is configured to generate and transmit to the first client device an overload notification.
The overload notification 510 can comprise an indication that the online service cannot process the first user's request at the current time. The overload notification 510 can also comprise an indication of the overload condition(s) that have caused the online service not to be able to fulfill the first user's request. The overload notification 510 can further comprise the first return time parameter and an indication that the request of the first user will be given priority if it is re-submitted in accordance with the first return time parameter.
In certain situations, the first user may decide to re-submit the request using a different client device than originally used. Therefore, since the subsequent different client device might not have the first token stored on it and available to provide in association with the second request, the overload notification 510 can comprise an indication of the first token for the first user to manually submit in association with the second request.
In some example embodiments, the notification module 330 is further configured to determine that a current time is within a predetermined amount of time of the first return time parameter, and to transmit a return time notification to the first user based on the determination that the current time is within the predetermined amount of time of the first return time parameter, thereby notifying the first user either shortly before the first return time parameter (e.g., 5 minutes before the specified window of time) or at the time of the first return time parameter (e.g., at the beginning of the specified window of time).
The return time notification 610 can be configured to indicate to the first user to request the operation again. The return time notification 610 can also be configured to indicate to the first user that the re-submitted request will be given special priority ahead of requests of other users or that the re-submitted request is guaranteed to be processed fully upon submission by the first user. In some example embodiments, the return time notification 610 also comprises one or more selectable user interface elements 620 configured to provide the first user with the option of re-submitting the request to the online service. One of the user interface elements 620 corresponding to re-submission of the request can be configured to trigger, or otherwise initiate, re-submission of the request in response to its selection. In some example embodiments, selection of the user interface element 620 corresponding to re-submission of the request triggers, or otherwise initiates, loading of a page on which the first user can re-submit the request.
Referring back to
In some example embodiment, the plurality of overload levels can correspond to different ranges of estimated response times. For example, the plurality of overload levels can comprise a high overload level, a medium overload level, and a low overload level. The low overload level can be selected for estimated response times between 1 minute and 15 minutes, the medium overload level can be selected for estimated response times between 15 minutes and 45 minutes, and the high overload level can be selected for any estimated response times above 45 min.
In some example embodiments, the plurality of overload levels can correspond to different numbers of overload conditions that are detected. As previously discussed, the overload conditions can comprise any condition that would cause the online service to have reduced performance of one or more specified functions to at least a predetermined degree. Such overload conditions can include, but are not limited to, conditions related to a status and/or capacity of a database of the online service, conditions related to a status and/or capacity of a server of the online service, and conditions related to a status and/or capacity of a network of the online service. Examples of overload conditions include, but are not limited to, a traffic level of the online service (e.g., a number of requests being processed during a particular time period, a number of requests being congested or stagnant during a particular time period) satisfying one or more predetermined traffic level criteria (e.g., exceed a predetermined threshold), a network connection speed of the online service satisfying one or more predetermined network connection speed criteria (e.g., the network connections speed is below a predetermined threshold), and a server speed of the online service satisfying one or more predetermined server speed criteria (e.g., the server speed is below a predetermined threshold). The overload determination module 310 can be configured to determine how many overload conditions apply during the time of the request for the performance of the operation, and then to determine the overload level based on the determined number of overload conditions. For example, the low overload level can be selected based on one overload condition being detected, the medium overload level can be selected based on two overload conditions being detected, and the high overload level can be selected based on three of ore overload conditions being detected. Other configurations are also within the scope of the present disclosure.
In some example embodiments, the notification module 330 is further configured to generate an overload notification based on the selected overload level, and to cause the overload notification to be displayed on the first client device. The overload notification can comprise an indication of the determined overload level.
In some example embodiments, the indication can comprise overload data, such as a textual explanation of the high overload level and an indication of a time at which the user should request the operation again (e.g., “PLEASE TRY AGAIN IN 1 HOUR AND 15 MINUTES” in
In some example embodiments, the indication can comprise overload data, such as a textual explanation of the medium overload level and an indication of a time at which the user should request the operation again (e.g., “PLEASE TRY AGAIN IN 45 MINUTES” in
In some example embodiments, the indication can comprise overload data, such as a textual explanation of the low overload level and an indication of a time at which the user should request the operation again (e.g., “PLEASE TRY AGAIN IN 15 MINUTES” in
Although the example above use three different overload levels, it is contemplated that other numbers of overload levels are also within the scope of the present disclosure.
Referring back to
One example of a standard of restriction that can be employed is permitting the performance of the requested operation to users on a first-in-first-out (FIFO) queue system.
Another example of a standard of restriction that can be employed is permitting the performance of the requested operation to every Nth user in a queue system where N is a number (e.g., every second user in the queue, every third user in the queue, every fourth user in the queue), while denying the performance of the requested operation of the other users (e.g., redirecting them to a redirection page).
Another example of a standard of restriction that can be employed is permitting the performance of the requested operation to every user submitting a request during repeated time intervals (or windows) interspersed between periods of nonperformance. For example, the requested operation can be permitted for every user submitting a request during 30 second intervals, while users submitting a request outside of the intervals have their requested operations temporarily denied and those user being redirected to a redirection page until another attempt at requesting the operation is made. The interval time can be adjusted based on the overload condition(s). In some example embodiments, the length of the time interval is inversely proportional to the number of overload conditions or the overload level, such that the greater the number of overload conditions or the higher the overload level, the smaller the time interval (i.e., the more restrictive the traffic control system 150 is in permitting the requested operations).
In some example embodiments, the overload determination module 310 is further configured to divide a user into one of two groups in response to, or otherwise based on, receiving a request for the performance of an operation of the online service. The first group is for users who are granted permission to have their requested operation performed by the online service, while the second group is for users who are denied permission to have their requested operation performed by the online service. Users in the first group can be issued a second token (e.g., a permission token transmitted to the user's client device), which can be used by the traffic control system 150 to initiate the performance of the requested operation (e.g., requested page is loaded on user's client device). Users in the second group can be directed to a redirection page (e.g., the pages on which overload notifications 710a, 710b, and 710c are displayed in
In some example embodiments, the overload determination module 310 is further configured to permit the performance of the requested operations for the users in the second group (e.g., the users that have had their requests denied) based on a determination that the return time parameter is satisfied. The overload determination module 310 can automatically cause the performance of the requested operation in response to the return time parameter being satisfied while the redirection page is loaded on the user's client device. In this fashion, the user simply has to wait until the return time parameter is satisfied. In some example embodiments, in response to a determination that the return time parameter has been satisfied, the overload determination module 310 can cause a selectable user interface element (e.g., a link) to be displayed to the user, where the selectable user interface element is configured to resubmit a request for the previously-requested operation in response to being selected by the user. In some example embodiments, the users in the second group are issued a first token and a return time parameter, which can be used to permit the performance of a requested operation when the requested operation is requested in accordance with the return time parameter, as previously discussed.
At operation 810, a first request for an online service to perform an operation can be received from a first user on a first client device. At operation 820, at least one overload condition for the online service can be detected, or otherwise determined, with the overload condition(s) corresponding to a first request time of the first request. At operation 830, a first token and a first return time parameter for the first user can be determined based on the determination of the overload condition(s). The performance of the requested operation can be denied in response to, or otherwise based on, the determination of the overload condition(s). At operation 840, the first token can be stored in association with the first return time parameter. At operation 850, the first token and the first return time parameter can be transmitted to the first client device. At operation 860, a second request for the online service to perform the operation can be received from the first user. The second request can have a corresponding time and comprise the first token. At operation 870, the first return time parameter can be identified based on the first token. At operation 880, a determination can be made that the corresponding time of the second request satisfies the first return time parameter. At operation 890, the operation can be performed in response to, or otherwise based on, the determination that the corresponding time of the second request satisfies the first return time parameter. It is contemplated that the operations of method 800 can incorporate any of the other features disclosed herein.
Operations 810 through 870 in
At operation 1010, a load level of the online service for a future time can be estimated. At operation 1020, a determination can be made that the estimated load level satisfies one or more return time criteria. At operation 1030, the first return time parameter can be defined or set to include the future time based on the determining that the estimated load level satisfies the one or more return time criteria. It is contemplated that the operations of method 1000 can incorporate any of the other features disclosed herein.
At operation 1110, a determination can be made that a current time is within a predetermined amount of time of the first return time parameter. At operation 1120, a return time notification can be transmitted to the first user in response to, or otherwise based on, the determination that the current time is within the predetermined amount of time of the first return time parameter. The return time notification can be configured to indicate to the first user to request the operation again. It is contemplated that the operations of method 1100 can incorporate any of the other features disclosed herein.
At operation 1210, an overload level can be selected from a plurality of overload levels based on the overload condition(s). At operation 1220, an overload notification can be generated based on the selected overload level. The overload notification can comprise an indication of the overload level. At operation 1230, the overload notification can be caused to be displayed on the first client device. It is contemplated that the operations of method 1200 can incorporate any of the other features disclosed herein.
At operation 1310, a standard of restriction can be selected from a plurality of standards of restriction based on the overload condition(s). At operation 1320, performance of requested operations of an online service can be restricted based on the selected standard of restriction. One or more users can be denied access to an operation of the online service based on the selected standard of restriction, while one or more other users can be allowed access to the operation of the online service based on the selected standard of restriction. It is contemplated that the operations of method 1300 can incorporate any of the other features disclosed herein.
At operation 1410, the traffic control system 150 is engaged by the user on a client device, such as by the user on the client device providing input (e.g., clicking a selectable user interface element) while the client device is interacting with a website. The input can include a submission of a request to access a page of the website (e.g., to load an item details page or an order page of the website).
At operation 1420, the traffic control system 150 determines whether or not to fulfill the user's request to access the page. This determination can be made based on a determination of whether any overload conditions are detected, and if so, how many and/or of what quality or degree, as previously discussed. If it is determined to fulfill the request, then, at operation 1430, the user is permitted to access the requested page. If it is determined to not fulfill the request, then, at operation 1440, the user is redirected to a redirection page. The redirection page can display an overload notification, including information indicating the overload condition(s), a return time parameter, and a user interface element indicating a status of the online service, as previously discussed.
At operation 1450, the traffic control system 150 employs a time distributor function to restrict the user from accessing the requested page until a determined time (e.g., the return time parameter). The user can then attempt again to access the page. At operation 1420, it is determined again whether or not to fulfill the user's request. The traffic control system 150 (e.g., the overload determination module 310) can determine an identification of the user, such as based on an internet protocol (IP) address of the user, and identify the corresponding return time parameter for the user based on the identification of the user. In some example embodiments, the user identification (e.g., the user's IP address) can be stored in association with the return time parameter in the database(s) 340. In this fashion, the user identification, such as the user's IP address, can be used to determine the appropriate return time parameter to use in deciding whether to allow access to the user during the user's repeated request, as an alternative to using an issued token.
In some example embodiments, the traffic control system 150 (e.g., the overload determination module 310) issues a cookie to users that are denied their request and redirected to the redirection page. The issued cookie can be stored on the user's client device. The traffic control system 150 can restrict the performance of the requested operation (e.g., entry or access to a particular page) using a script processor on the user's client device. The cookie on the user's client device can store the time at which the user enters the redirection page (e.g., the time at which the redirection page is loaded on the client device). The traffic control system 150 can then compare the current time of the user's attempt to resubmit the request (e.g., when the user attempts to enter or access the particular page again) with the time stored in the cookie. Using this comparison, the traffic control system 150 can determine whether the user's request is in accordance with the corresponding return time parameter, and thereby determine whether to deny the user's repeated request or grant the repeated request.
It is contemplated that the operations of method 1400 can incorporate any of the other features disclosed herein.
It is contemplated that any features of any embodiments disclosed herein can be combined with any other features of any other embodiments disclosed herein. Accordingly, these any such hybrid embodiments are within the scope of the present disclosure.
Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied on a machine-readable medium) or hardware modules. A “hardware module” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
In some embodiments, a hardware module may be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware module may include dedicated circuitry or logic that is permanently configured to perform certain operations. For example, a hardware module may be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware module may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware module may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware modules become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
Accordingly, the phrase “hardware module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. As used herein, “hardware-implemented module” refers to a hardware module. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where a hardware module comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware modules) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented module” refers to a hardware module implemented using one or more processors.
Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented modules. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)).
The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented modules may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented modules may be distributed across a number of geographic locations.
The modules, methods, applications and so forth described in conjunction with
Software architectures are used in conjunction with hardware architectures to create devices and machines tailored to particular purposes. For example, a particular hardware architecture coupled with a particular software architecture will create a mobile device, such as a mobile phone, tablet device, or so forth. A slightly different hardware and software architecture may yield a smart device for use in the “internet of things.” While yet another combination produces a server computer for use within a cloud computing architecture. Not all combinations of such software and hardware architectures are presented here as those of skill in the art can readily understand how to implement the features of the present disclosure in different contexts from the disclosure contained herein.
The machine 1600 may include processors 1610, memory 1630, and I/O components 1650, which may be configured to communicate with each other such as via a bus 1602. In an example embodiment, the processors 1610 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1612 and processor 1614 that may execute instructions 1616. The term “processor” is intended to include multi-core processor that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although
The memory/storage 1630 may include a memory 1632, such as a main memory, or other memory storage, and a storage unit 1636, both accessible to the processors 1610 such as via the bus 1602. The storage unit 1636 and memory 21@32 store the instructions 1616 embodying any one or more of the methodologies or functions described herein. The instructions 1616 may also reside, completely or partially, within the memory 1632, within the storage unit 21@36, within at least one of the processors 1610 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1600. Accordingly, the memory 1632, the storage unit 21@36, and the memory of processors 1610 are examples of machine-readable media.
As used herein, “machine-readable medium” means a device able to store instructions and data temporarily or permanently and may include, but is not be limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions 1616. The term “machine-readable medium” shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., instructions 1616) for execution by a machine (e.g., machine 1600), such that the instructions, when executed by one or more processors of the machine 1600 (e.g., processors 1610), cause the machine 1600 to perform any one or more of the methodologies described herein. Accordingly, a “machine-readable medium” refers to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se.
The I/O components 1650 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 1650 that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 1650 may include many other components that are not shown in
In further example embodiments, the I/O components 1650 may include biometric components 1656, motion components 1658, environmental components 1660, or position components 1662 among a wide array of other components. For example, the biometric components 1656 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components 1658 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environmental components 1660 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometer that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 1662 may include location sensor components (e.g., a Global Position System (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.
Communication may be implemented using a wide variety of technologies. The I/O components 1650 may include communication components 1664 operable to couple the machine 1600 to a network 1680 or devices 1670 via coupling 1682 and coupling 1672 respectively. For example, the communication components 1664 may include a network interface component or other suitable device to interface with the network 1680. In further examples, communication components 1664 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 1670 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).
Moreover, the communication components 1664 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1664 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 1664, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.
In various example embodiments, one or more portions of the network 1680 may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, the network 1680 or a portion of the network 1680 may include a wireless or cellular network and the coupling 1682 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling 1682 may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard setting organizations, other long range protocols, or other data transfer technology.
The instructions 1616 may be transmitted or received over the network 1680 using a transmission medium via a network interface device (e.g., a network interface component included in the communication components 1664) and utilizing any one of a number of well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions 1616 may be transmitted or received using a transmission medium via the coupling 1672 (e.g., a peer-to-peer coupling) to devices 1670. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions 1616 for execution by the machine 1600, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
Although an overview of the inventive subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present disclosure. Such embodiments of the inventive subject matter may be referred to herein, individually or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single disclosure or inventive concept if more than one is, in fact, disclosed.
The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
As used herein, the term “or” may be construed in either an inclusive or exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations may be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of embodiments of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes can be made to these embodiments without departing from the broader spirit and scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter can be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments can be utilized and derived therefrom, such that structural and logical substitutions and changes can be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
Such embodiments of the inventive subject matter can be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose can be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.
The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6049547 | Fisher et al. | Apr 2000 | A |
| 6308211 | Rosborough | Oct 2001 | B1 |
| 6728363 | Lieberman et al. | Apr 2004 | B2 |
| 7734648 | Eberlein | Jun 2010 | B2 |
| 8290838 | Thakur | Oct 2012 | B1 |
| 8509085 | Bader | Aug 2013 | B2 |
| 9258736 | Xiao | Feb 2016 | B2 |
| 20020057686 | Leon | May 2002 | A1 |
| 20030137938 | Belanger | Jul 2003 | A1 |
| 20040165531 | Brady | Aug 2004 | A1 |
| 20080075003 | Lee | Mar 2008 | A1 |
| 20100061238 | Godbole | Mar 2010 | A1 |
| 20100302950 | Zhao | Dec 2010 | A1 |
| 20110078321 | Muret | Mar 2011 | A1 |
| 20120209945 | Chandrasekhar et al. | Aug 2012 | A1 |
| 20120263036 | Barclay | Oct 2012 | A1 |
| 20120293007 | Byun | Nov 2012 | A1 |
| 20140045517 | Marti et al. | Feb 2014 | A1 |
| 20140052835 | Felton et al. | Feb 2014 | A1 |
| 20140362697 | Desnoyer | Dec 2014 | A1 |
| 20150156132 | Emejulu | Jun 2015 | A1 |
| 20150277964 | Atkins | Oct 2015 | A1 |
| 20160095059 | Salvador | Mar 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 1087596 | Mar 2001 | EP |
| Entry |
|---|
| “International Application Serial No. PCT/US2016/030086, International Search Report mailed Aug. 4, 2016”, 2 pgs. |
| “International Application Serial No. PCT/US2016/030086, Written Opinion mailed Aug. 4, 2016”, 4 pgs. |
| Number | Date | Country | |
|---|---|---|---|
| 20160337253 A1 | Nov 2016 | US |
