The popularity and widespread appeal of video games has increased dramatically in recent years. The popularity of video games is not limited only to players, as many non-player individuals, sometimes referred to as spectators, often watch live streams of video games that are played by others. In some examples, a game player, sometimes referred to as a broadcaster, employs image capture software on the player's device to capture video of live gameplay and then stream the video to other locations, such as a video game streaming service. The video game streaming service may then, in turn, provide the streaming video to various subscribers for viewing. In some examples, the video captured from the game may be streamed live (e.g., in real time or near-real time) from the game player to the spectators for viewing. While this technology provides a number of advantages, it may also have a number of associated limitations. For example, in some cases, because the video may be captured from a player's device, spectators may be limited to viewing the same information that is provided to the player. However, spectators and players may often be interested in at least partially different information about the game. Additionally, in some cases, conventional video games may provide limited, if any, interfaces for requesting live statistical information, thereby not allowing statistical information to be specifically filtered or customized to different interests, game play styles, preferences, etc. or to be provided in a format that is easily parsed and converted into visual elements.
The following detailed description may be better understood when read in conjunction with the appended drawings. For the purposes of illustration, there are shown in the drawings example embodiments of various aspects of the disclosure; however, the invention is not limited to the specific methods and instrumentalities disclosed.
Techniques for providing streaming video game statistics are described herein. In some examples, statistics may be provided for a multi-player video game executed by multiple video game client applications at multiple client devices and one or more video game server applications at one or more remote servers. Also, in some examples, at least a first client device may be a operated by a broadcasting game player, and the first client device may capture video generated by a respective first game client and transmit (e.g., stream) the video, for example to a video game streaming service for viewing by one or more spectators. At least the first video game client application may include a local server component, such as a hypertext transfer protocol (HTTP) server, which executes locally at the first client device. The local server component may be employed to provide statistical information from the video game to a local client component, such as a web interface. In some examples, the statistical information provided by the local server component may be included in one or more visual display items (e.g., overlays, side panels, etc.) that are generated by the first client device. The visual display items may be included in the video that is captured and transmitted by the first client device, thereby potentially providing live streaming statistical information to spectators of the video game.
In some cases, the above-described example techniques may provide a number of advantages. For example, inclusion of the local server component in a video game client application may allow requested statistical information to be filtered and customized to different interests, game play styles, and other preferences. In some cases, broadcasting player may select statistics to reflect a current discussion or focus. This may serve to build engagement and also allows viewers to quickly acclimatize to the current state of a broadcast when tuning in halfway, or discovering the game for the first time. Additionally, because the local server component executes within the video game client at the client device, the local server component may provide live statistical information with no detectable latency between game play events and corresponding statistics that reflect those events. Furthermore, in some examples, the use of an HTTP server may allow generation of visual display items by leveraging a wide array of data processing and visualization tools, such as JavaScript, cascading style sheets (CSS), hypertext markup language (HTML) interfaces, and others. For example, in some cases, an HTML page may be generated to control the layout and behavior of each display item that the broadcasting player wishes to use. In some examples, a video game may include one or more standard templates that broadcasters may use, for example with relatively little, if any, editing, to generate display items. These standard templates may optionally be customized, for example using HTML editing tools. The use of these and other tools may allow generation of visual interfaces across multiple different games without forcing game developers to repeatedly have to code instructions for generation of those interfaces into the multiple different games, thereby potentially reducing game development time and production costs.
In some examples, statistical display items may be included in the captured video stream for transmission to spectators but may not be included in the resulting player view that is presented to the broadcasting game player at the first client device. This enables spectators to receive and view potentially large quantities of statistical information, while also allowing the broadcasting player's view of the game to remain uncluttered for effective and responsive game play. For example, a broadcasting player may wish to display certain statistics to spectators that highlight or emphasize particular player accomplishments (e.g., wins, kills, achievements, etc.) that may enhance the player's prestige or build spectator interest but that may not be required by the player for gameplay. Also, in some examples, certain player interfaces (or portions thereof) that are inserted into the broadcasting player's view of the game (e.g., a player head-up display (HUD), status bar, etc.) may not be included in the spectators' view of the game, thereby allowing a player to view statistics that may be needed for gameplay but may not be interesting to spectators and also allowing certain statistics to be observed privately by a player that the player may not wish to share with others.
In some cases, the local server component within the video game client may support a coordinated application programming interface (API) for querying of statistical information. For example, there may be a structured schema that maps uniform resource locators (URLs) to entities, components, and properties in the game state. This structured schema may allow display item elements to easily and efficiently retrieve statistics for the current game state. For example, in some cases, upon receiving a URL associated with a particular entity and/or component, the local server component may employ a handler that maps the URL to the entity and/or component and returns associated statistical information. In some examples, the statistical information provided by the local server component may include images and/or videos, for example depicting players, weapons, inventory, etc. for which statistics are presented. Also, in some examples, the statistical information may include raw statistical data, for example in a format such as JavaScript Object Notation (JSON).
In some examples, instructions for adding and including the local server component, the structured schema for URL mapping, and other features within the video game may be provided by a computing service provider, such as a service provider that hosts and executes the video game on behalf of the developer. For example, the service may provide an API, a software development kit (SDK) and/or other instructions that allow the game developer to easily integrate these and other features within the video game. For example, the service provider may supply a default implementation of the structured schema for mapping URLs to entities. The service provider may also supply handlers for common utility functions, such as searching. Developers may then configure filters for the handlers to restrict the view to whatever they feel is appropriate for their game. Additionally, developers may optionally implement their own handlers that may perform various different customized functions.
In some examples, statistical information may be requested from the local server component using a variety of different techniques. For example, in some cases, at least part of the statistical information may be provided using a subscription model, in which information is continuously and/or repeatedly provided to the local client without having to re-issue a request. Also, in some cases, at least part of the statistical information may be requested periodically by the local client, such as at particular intervals and/or in response to various events. In some examples, it may be advantageous to subscribe to statistics for metrics that change more frequently, such as virtual location, score, health, etc. Also, in some examples, it may be advantageous to issue periodic requests for metrics that change less frequently, such as number of wins, kills, etc. In some examples, a WebSocket connection may be generated between the local server and local client components, for example for streaming of statistical information such as via the subscription model. Also, in some examples, the local server component may listen, for example on a local HTTP port, to answer periodic statistical queries on demand, for example via standard HTTP requests.
As shown in
As also shown in
As will be described in detail below, the statistical information provided by local server component 125 to local client component 126 may be included in the captured video that is transmitted by client device 120 to spectators 140A-N via service 130, thereby potentially enhancing the experiences of spectators 140A-N and generating additional interest and prestige for the video game as well as the video game broadcaster. Because the local server component 126 executes within the video game client 122 at the client device 120, the local server component 125 may provide live statistical information with no detectable latency between game play events and corresponding statistics that reflect those events.
Referring now to
As also shown in
As set forth above, in some examples, local server component 125 may be an HTTP server and local client components 126 may include a web interface. As also set forth above, the use of an HTTP server and web interface may allow generation of display items 240 by leveraging a wide array of data processing and visualization tools, such as JavaScript, cascading style sheets (CSS), hypertext markup language (HTML) interfaces, and others. For example, in some cases, an HTML page may be generated to control the layout and behavior of each display item 240 that the broadcasting player wishes to use. The pages may be built using both native HTML elements and custom elements, for example written in Javascript. In some examples, a video game may include one or more standard templates that broadcasters may use, for example with relatively little, if any, editing, to generate display items. These standard templates may optionally be customized, for example using HTML editing tools. Image capture components 128 may, for example, capture and composite rendered images 230 and display item 240 using a layout definition, for example using chroma key compositing or another compositing technique to render transparency. An employed layout definition may allow the rendered images 230 and display items 240 to be layered, resized, cropped, and transformed as appropriate. In some examples, image capture components may support plugins that embed a web browser than can be rendered and captured in-process, including transparency, and then overlaid into the transmitted video stream.
In some examples, local server component 126 may support a structured schema that maps uniform resource locators (URLs) to entities, components, and properties in the game state. This structured schema may allow display item elements to easily and efficiently retrieve statistics for the current game state. For example, in some cases, upon receiving a URL associated with a particular entity and/or component, the local server component 125 may employ a handler that maps the URL to the entity and/or component and returns associated statistical information. Also, in some examples, upon receiving a URL, the local server component 125 may execute associated script to retrieve a custom data set. In some examples, instructions for adding and including the local server component, the structured schema for URL mapping, and other features within the video game may be provided by a computing service provider, such as a service provider that hosts and executes video game server 110. For example, the service may provide an API, a software development kit (SDK) and/or other instructions that allow the game developer to easily integrate these and other features within the video game. For example, the service provider may supply a default implementation of the structured schema for mapping URLs to entities. The service provider may also supply handlers for common utility functions like searching. Developers may then configure filters for the handlers to restrict the view to whatever they feel is appropriate for their game. Additionally, developers may optionally implement their own handlers that may perform any arbitrary function. In some examples, the computing service provider may provide documentation to game players to describe the general process of retrieving video game statistics and creating display items. Furthermore, in some examples, game developers may provide documentation to game players to describe specific statistical information for their games and how to access it.
The inclusion of the local server component 125 in video game client 122 may allow requested statistical information to be filtered and customized to different interests, game play styles, and other preferences. For example, different players within the same game may request wholly or partially different statistical information. Moreover, the statistical information included in display items 240 and provided to spectators 140A-N may be wholly or partially different than the information included in player interfaces 220 for display to the game player. For example, a broadcasting player may wish to display certain statistics to spectators that highlight or emphasize particular player accomplishments (e.g., wins, kills, achievements, etc.) that may enhance the player's prestige or build spectator interest but that may not be required by the player for gameplay. In the example of
As set forth above, in some examples, local server component 125 may be an HTTP server embedded in a video game client, and local client component 126 may be a web interface. Referring now to
In some examples, in order to provide additional statistical and other information for inclusion in display items 240, local server component 125 may communicate with one or more other components external to video game client 122 and video game server 110. Referring now to
In some examples, statistics service 411 may be operated by (or otherwise associated with) a computing service provider that hosts and executes video games on behalf of game developers, and the statistics service may collect, organize, and store statistical information reported by video games executed by the computing service provider. Additionally, in some cases, an API, SDK or other information provided by the computing service provider to video game developers may include instructions that may be embedded or included within the video games for reporting of statistical information to the statistics service 411.
In some examples, advertisement service 412 may provide advertisements, notifications, or other information that may be included within display items 320. In some cases, the provided advertisements may be related to the video game being played, such as advertisements for in-game purchases, advertisements for other associated games or game versions, gaming accessories, and other game related products or features. In some examples, the broadcasting player may receive compensation or other benefits for including advertisements in the captured and streamed video output.
Referring now to
It is noted that the statistical attributes and presentation formats selected for display item 510 merely non-limiting examples and that display items may include any combination of additional or alternative statistical attributes presented using any combination of additional or alternative presentation formats. For example, in some cases, as opposed to displaying only a single collection of statistics, a display item may periodically cycle through displays of various different statistics, for example using a presentation technique sometimes referred to as a ticker. This may be advantageous, for example, by allowing displays of large quantities of different statistics while reducing the amount of screen space required to display those statistics. It is also noted that, while example display items 510 and 520 are overlays that are layered on top of rendered image 530, there is no requirement that display items must directly overlay a portion of a rendered image. For example, in some cases, display items may not directly overlay rendered images but may instead, for example, be positioned in a side, top and/or bottom panel or area adjacent to the rendered images.
In some examples, the display items may include statistical results in which players or other entities and their respective statistics are ordered or ranked based on statistical values (e.g., high score to low score, most damage dealt to least damage dealt, etc.). Also, in some examples, the display items may include maps, for example corresponding to a virtual area associated with a video game. For example, in some cases, a heat map and/or line/dot graphics may be used to show a path that a ball or other object has traveled over time throughout a virtual area. As another example, a display item may include percentages to indicate relative amounts of time that a ball or other object has been located in various portions of a virtual area. It is further noted that the statistical information included in the display items is not limited to statistical attributes that are directly maintained by the video game itself. For example, in some cases, various statistics may be retrieved from a video game and then aggregated, combined, and adjusted as desired to provide additional statistical information that the video game may not itself directly maintain. Additionally, as described above, statistical information may also be retrieved from other sources external to the video game, such as a statistics service, and used in combination with (or separately from) statistical information retrieved from the video game itself.
At operation 612, at least part of the set of rendered images are provided for display by the first compute node, for example to a game player that operates the first compute node, using client display 250 of
As set forth above, in some examples, the first compute node may be operated by a player of the video game. Also, in some examples, this player may be a broadcasting player that captures and transmits video output from the video game for display to one or more spectators. The techniques described herein may, in some cases, allow such a broadcasting player to request statistical information for inclusion in the video game output that is displayed to these spectators. At operation 614, if statistical information is not requested by the broadcasting player, then the process returns to operation 610. By contrast, when statistical information is requested by the broadcasting player, the process proceeds to operation 616, at which a local server component within the first video game application receives, from a local client component, one or more requests for statistical information associated with the video game. The local client component may execute on the first compute node. As set forth above, in some examples, the local server component may be an HTTP server and the local client component may be a web interface. As also set forth above, in some examples, the local server component may interact with one or more schemas within the video game that map URL's to entities, components, and/or properties within the video game. In some examples, the one or more requests for statistical information received by the local server component may include one or more URL's identifying entities, components, and/or properties for which statistical information is requested. Upon receiving the one or more requests, the local server component may employ a handler that maps the URL's in the requests to entities, components and/or properties within the video game and returns associated statistical information. In some examples, a service provider that hosts execution of the video game (e.g., executes a video game server in communication with the first video game application) may provide an SDK having instructions for including the local server component and/or the one or more schemas within the video game
In some examples, one or more of the requests received at operation 616 may be in the form of a subscription, in which information is continuously and/or repeatedly provided to the local client without having to re-issue a request. Also, in some examples, one or more of the requests received at operation 616 may be issued periodically by the local client component, such as at particular intervals and/or in response to various events. In some examples, the requested statistical information may include images, videos, graphics, maps, icons, or other non-purely textual representations. In some examples, at least part of the statistical information may be generated by the video game. Also, in some examples, at least part of the statistical information may be generated by a source external to the video game, such as a statistics service. For example, historical information regarding players, teams, and other attributes may be provided by a statistics service. Furthermore, in some examples, the local server component may provide information received from other sources, such as advertisements from an advertisement service.
At operation 618, the local server component provides, to the local client component, the statistical information requested at operation 616. In some examples, at least a portion of the requested statistical information may be provided using a WebSocket connection between the local server and local client components, for example for streaming of statistical information such as via the subscription model. Also, in some examples, at least a portion of the requested statistical information may be provided via standard HTTP requests, for example for information that is periodically requested by the local client component.
At operation 620, the first compute node generates a first display item that include at least part of the statistical information. In some examples, the first display item may be an overlay, panel, bar, box, and/or other visual element. As set forth above, in some examples, an HTML page may be generated to control the layout and behavior of the first display item. The HTML page may be built using both native HTML elements and custom elements, for example written in Javascript. In some examples, a video game may include one or more standard templates that may be used, for example with relatively little, if any, editing, to generate display items. These standard templates may optionally be customized, for example using HTML editing tools. In some examples, the first display item may include information generated by one or more sources external to the video game, such as the statistics service and/or advertisement service described above. For example, the first display item may include enhanced statistical information from the statistics service and/or advertisements from the advertisement service.
At operation 622, the first compute node captures a set of captured images (e.g., captured images 255 of
At operation 624, the set of captured images is transmitted, by the first compute node, to one or more other compute nodes for display. For example, the captured images may be transmitted to a video game streaming service, which may, in turn, transmit the captured images to one or more spectators for display to the one or more spectators. In some examples, the set of captured images may be streamed from the first compute node to the streaming service and, in turn, to the spectators using live or real-time streaming transmission techniques, in which images may be viewed by spectators almost immediately after the images are captured by the image capture components at the first compute node. It is further noted that the inclusion of the local server component in the first video game application at the first compute node may allow the statistical information to be provided and streamed in real time, for example with no detectable latency between game play events and corresponding statistics that reflect those events. For example, the statistical information associated with the video game may include real-time statistical values that represent a current video game state associated with a rendered image that the real-time statistical values are overlaid upon.
It is noted that, while the above description includes examples in which statistical information display items are generated at the broadcasting player's device, the techniques described herein are not limited to such examples. In particular, in some examples, statistical information may be transmitted by the broadcasting player's device to one or more spectators (e.g., via a streaming service), and the spectators may then generate one or more display items based on the received statistical information. Specifically, in some cases, the broadcasting player's device may obtain statistical information using a local server component (e.g., HTTP server) using techniques such as those described above. The broadcasting player's device may also capture rendered video game images. However, in this scenario, the statistical information display items may not be included in the captured and transmitted images. Rather, the broadcasting player's device may instead transmit two separate streams including a first stream with rendered video game images and a second stream with the retrieved statistical information. These two streams may be encoded and transmitted separately to the streaming service and/or spectators. In some examples, upon receiving these separate streams, a spectator may use the statistical information to generate the statistical information display items, for example using techniques such as those described above. The generated display items may then be layered on top of (or otherwise combined with) one or more of the rendered images received in the separate rendered image stream, and the resulting images with display items may then be displayed to the spectators.
In some examples, because the statistical information and the rendered images may be transmitted using separate streams, there may be latency between the received statistical information and the image frames with which the statistical information is associated. Thus, in some examples, it may be advantageous for the broadcasting player to add timestamps to transmitted portions (e.g., frames) of the rendered image and corresponding statistical information streams, in order to allow the spectators to properly match received statistical information and the image frames with which the statistical information is associated. It is noted that the above described techniques for spectator display item generation may, in some examples, be advantageous, for example by providing spectators with greater control over the content, format, and other features of the generated display items. Also, in some examples, display items may be generated by an intermediate entity, such as the streaming service, before being provided to the spectators. It is further noted that, in any of the techniques set forth above, spectators, the streaming service, and/or other entities may communicate with the broadcasting player, for example using chat, email or other communications mediums, to request that the broadcasting player provide certain statistics, display items, formats, and/or any other requested information or data.
An example system for transmitting and providing data will now be described in detail. In particular,
Each type or configuration of computing resource may be available in different sizes, such as large resources—consisting of many processors, large amounts of memory and/or large storage capacity—and small resources—consisting of fewer processors, smaller amounts of memory and/or smaller storage capacity. Customers may choose to allocate a number of small processing resources as web servers and/or one large processing resource as a database server, for example.
Data center 85 may include servers 76a and 76b (which may be referred herein singularly as server 76 or in the plural as servers 76) that provide computing resources. These resources may be available as bare metal resources or as virtual machine instances 78a-d (which may be referred herein singularly as virtual machine instance 78 or in the plural as virtual machine instances 78).
The availability of virtualization technologies for computing hardware has afforded benefits for providing large scale computing resources for customers and allowing computing resources to be efficiently and securely shared between multiple customers. For example, virtualization technologies may allow a physical computing device to be shared among multiple users by providing each user with one or more virtual machine instances hosted by the physical computing device. A virtual machine instance may be a software emulation of a particular physical computing system that acts as a distinct logical computing system. Such a virtual machine instance provides isolation among multiple operating systems sharing a given physical computing resource. Furthermore, some virtualization technologies may provide virtual resources that span one or more physical resources, such as a single virtual machine instance with multiple virtual processors that span multiple distinct physical computing systems.
Referring to
Communication network 73 may provide access to computers 72. User computers 72 may be computers utilized by users 70 or other customers of data center 85. For instance, user computer 72a or 72b may be a server, a desktop or laptop personal computer, a tablet computer, a wireless telephone, a personal digital assistant (PDA), an e-book reader, a game console, a set-top box or any other computing device capable of accessing data center 85. User computer 72a or 72b may connect directly to the Internet (e.g., via a cable modem or a Digital Subscriber Line (DSL)). Although only two user computers 72a and 72b are depicted, it should be appreciated that there may be multiple user computers.
User computers 72 may also be utilized to configure aspects of the computing resources provided by data center 85. In this regard, data center 85 might provide a gateway or web interface through which aspects of its operation may be configured through the use of a web browser application program executing on user computer 72. Alternately, a stand-alone application program executing on user computer 72 might access an application programming interface (API) exposed by data center 85 for performing the configuration operations. Other mechanisms for configuring the operation of various web services available at data center 85 might also be utilized.
Servers 76 shown in
It should be appreciated that although the embodiments disclosed above discuss the context of virtual machine instances, other types of implementations can be utilized with the concepts and technologies disclosed herein. For example, the embodiments disclosed herein might also be utilized with computing systems that do not utilize virtual machine instances.
In the example data center 85 shown in
In the example data center 85 shown in
It should be appreciated that the network topology illustrated in
It should also be appreciated that data center 85 described in
In at least some embodiments, a server that implements a portion or all of one or more of the technologies described herein may include a computer system that includes or is configured to access one or more computer-accessible media.
In various embodiments, computing device 15 may be a uniprocessor system including one processor 10 or a multiprocessor system including several processors 10 (e.g., two, four, eight or another suitable number). Processors 10 may be any suitable processors capable of executing instructions. For example, in various embodiments, processors 10 may be embedded processors implementing any of a variety of instruction set architectures (ISAs), such as the x86, PowerPC, SPARC or MIPS ISAs or any other suitable ISA. In multiprocessor systems, each of processors 10 may commonly, but not necessarily, implement the same ISA.
System memory 20 may be configured to store instructions and data accessible by processor(s) 10. In various embodiments, system memory 20 may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/Flash®-type memory or any other type of memory. In the illustrated embodiment, program instructions and data implementing one or more desired functions, such as those methods, techniques and data described above, are shown stored within system memory 20 as code 25 and data 26.
In one embodiment, I/O interface 30 may be configured to coordinate I/O traffic between processor 10, system memory 20 and any peripherals in the device, including network interface 40 or other peripheral interfaces. In some embodiments, I/O interface 30 may perform any necessary protocol, timing or other data transformations to convert data signals from one component (e.g., system memory 20) into a format suitable for use by another component (e.g., processor 10). In some embodiments, I/O interface 30 may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of I/O interface 30 may be split into two or more separate components, such as a north bridge and a south bridge, for example. Also, in some embodiments some or all of the functionality of I/O interface 30, such as an interface to system memory 20, may be incorporated directly into processor 10.
Network interface 40 may be configured to allow data to be exchanged between computing device 15 and other device or devices 60 attached to a network or networks 50, such as other computer systems or devices, for example. In various embodiments, network interface 40 may support communication via any suitable wired or wireless general data networks, such as types of Ethernet networks, for example. Additionally, network interface 40 may support communication via telecommunications/telephony networks, such as analog voice networks or digital fiber communications networks, via storage area networks such as Fibre Channel SANs (storage area networks) or via any other suitable type of network and/or protocol.
In some embodiments, system memory 20 may be one embodiment of a computer-accessible medium configured to store program instructions and data as described above for implementing embodiments of the corresponding methods and apparatus. However, in other embodiments, program instructions and/or data may be received, sent or stored upon different types of computer-accessible media. Generally speaking, a computer-accessible medium may include non-transitory storage media or memory media, such as magnetic or optical media—e.g., disk or DVD/CD coupled to computing device 15 via I/O interface 30. A non-transitory computer-accessible storage medium may also include any volatile or non-volatile media, such as RAM (e.g., SDRAM, DDR SDRAM, RDRAM, SRAM, etc.), ROM (read only memory) etc., that may be included in some embodiments of computing device 15 as system memory 20 or another type of memory. Further, a computer-accessible medium may include transmission media or signals such as electrical, electromagnetic or digital signals conveyed via a communication medium, such as a network and/or a wireless link, such as those that may be implemented via network interface 40.
A network set up by an entity, such as a company or a public sector organization, to provide one or more web services (such as various types of cloud-based computing or storage) accessible via the Internet and/or other networks to a distributed set of clients may be termed a provider network. Such a provider network may include numerous data centers hosting various resource pools, such as collections of physical and/or virtualized computer servers, storage devices, networking equipment and the like, needed to implement and distribute the infrastructure and web services offered by the provider network. The resources may in some embodiments be offered to clients in various units related to the web service, such as an amount of storage capacity for storage, processing capability for processing, as instances, as sets of related services and the like. A virtual computing instance may, for example, comprise one or more servers with a specified computational capacity (which may be specified by indicating the type and number of CPUs, the main memory size and so on) and a specified software stack (e.g., a particular version of an operating system, which may in turn run on top of a hypervisor).
A compute node, which may be referred to also as a computing node, may be implemented on a wide variety of computing environments, such as commodity-hardware computers, virtual machines, web services, computing clusters and computing appliances. Any of these computing devices or environments may, for convenience, be described as compute nodes.
A number of different types of computing devices may be used singly or in combination to implement the resources of the provider network in different embodiments, for example computer servers, storage devices, network devices and the like. In some embodiments a client or user may be provided direct access to a resource instance, e.g., by giving a user an administrator login and password. In other embodiments the provider network operator may allow clients to specify execution requirements for specified client applications and schedule execution of the applications on behalf of the client on execution platforms (such as application server instances, Java™ virtual machines (JVMs), general-purpose or special-purpose operating systems, platforms that support various interpreted or compiled programming languages such as Ruby, Perl, Python, C, C++ and the like or high-performance computing platforms) suitable for the applications, without, for example, requiring the client to access an instance or an execution platform directly. A given execution platform may utilize one or more resource instances in some implementations; in other implementations, multiple execution platforms may be mapped to a single resource instance.
In many environments, operators of provider networks that implement different types of virtualized computing, storage and/or other network-accessible functionality may allow customers to reserve or purchase access to resources in various resource acquisition modes. The computing resource provider may provide facilities for customers to select and launch the desired computing resources, deploy application components to the computing resources and maintain an application executing in the environment. In addition, the computing resource provider may provide further facilities for the customer to quickly and easily scale up or scale down the numbers and types of resources allocated to the application, either manually or through automatic scaling, as demand for or capacity requirements of the application change. The computing resources provided by the computing resource provider may be made available in discrete units, which may be referred to as instances. An instance may represent a physical server hardware platform, a virtual machine instance executing on a server or some combination of the two. Various types and configurations of instances may be made available, including different sizes of resources executing different operating systems (OS) and/or hypervisors, and with various installed software applications, runtimes and the like. Instances may further be available in specific availability zones, representing a logical region, a fault tolerant region, a data center or other geographic location of the underlying computing hardware, for example. Instances may be copied within an availability zone or across availability zones to improve the redundancy of the instance, and instances may be migrated within a particular availability zone or across availability zones. As one example, the latency for client communications with a particular server in an availability zone may be less than the latency for client communications with a different server. As such, an instance may be migrated from the higher latency server to the lower latency server to improve the overall client experience.
In some embodiments the provider network may be organized into a plurality of geographical regions, and each region may include one or more availability zones. An availability zone (which may also be referred to as an availability container) in turn may comprise one or more distinct locations or data centers, configured in such a way that the resources in a given availability zone may be isolated or insulated from failures in other availability zones. That is, a failure in one availability zone may not be expected to result in a failure in any other availability zone. Thus, the availability profile of a resource instance is intended to be independent of the availability profile of a resource instance in a different availability zone. Clients may be able to protect their applications from failures at a single location by launching multiple application instances in respective availability zones. At the same time, in some implementations inexpensive and low latency network connectivity may be provided between resource instances that reside within the same geographical region (and network transmissions between resources of the same availability zone may be even faster).
As set forth above, content may be provided by a content provider to one or more clients. The term content, as used herein, refers to any presentable information, and the term content item, as used herein, refers to any collection of any such presentable information. A content provider may, for example, provide one or more content providing services for providing content to clients. The content providing services may reside on one or more servers. The content providing services may be scalable to meet the demands of one or more customers and may increase or decrease in capability based on the number and type of incoming client requests. Portions of content providing services may also be migrated to be placed in positions of reduced latency with requesting clients. For example, the content provider may determine an “edge” of a system or network associated with content providing services that is physically and/or logically closest to a particular client. The content provider may then, for example, “spin-up,” migrate resources or otherwise employ components associated with the determined edge for interacting with the particular client. Such an edge determination process may, in some cases, provide an efficient technique for identifying and employing components that are well suited to interact with a particular client, and may, in some embodiments, reduce the latency for communications between a content provider and one or more clients.
In addition, certain methods or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments.
It will also be appreciated that various items are illustrated as being stored in memory or on storage while being used, and that these items or portions thereof may be transferred between memory and other storage devices for purposes of memory management and data integrity. Alternatively, in other embodiments some or all of the software modules and/or systems may execute in memory on another device and communicate with the illustrated computing systems via inter-computer communication. Furthermore, in some embodiments, some or all of the systems and/or modules may be implemented or provided in other ways, such as at least partially in firmware and/or hardware, including, but not limited to, one or more application-specific integrated circuits (ASICs), standard integrated circuits, controllers (e.g., by executing appropriate instructions, and including microcontrollers and/or embedded controllers), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), etc. Some or all of the modules, systems and data structures may also be stored (e.g., as software instructions or structured data) on a computer-readable medium, such as a hard disk, a memory, a network or a portable media article to be read by an appropriate drive or via an appropriate connection. The systems, modules and data structures may also be transmitted as generated data signals (e.g., as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission media, including wireless-based and wired/cable-based media, and may take a variety of forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). Such computer program products may also take other forms in other embodiments. Accordingly, the present invention may be practiced with other computer system configurations.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some or all of the elements in the list.
While certain example embodiments have been described, these embodiments have been presented by way of example only and are not intended to limit the scope of the inventions disclosed herein. Thus, nothing in the foregoing description is intended to imply that any particular feature, characteristic, step, module or block is necessary or indispensable. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the inventions disclosed herein. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of certain of the inventions disclosed herein.
Number | Name | Date | Kind |
---|---|---|---|
8066572 | Timmons | Nov 2011 | B1 |
8485899 | Rom | Jul 2013 | B1 |
9032296 | Jeffs | May 2015 | B1 |
20030130040 | Dripps | Jul 2003 | A1 |
20040242306 | Tarantino | Dec 2004 | A1 |
20040266535 | Reeves | Dec 2004 | A1 |
20060121992 | Bortnik | Jun 2006 | A1 |
20070117617 | Spanton | May 2007 | A1 |
20070121534 | James | May 2007 | A1 |
20090147025 | Grigsby | Jun 2009 | A1 |
20130252737 | Mescon | Sep 2013 | A1 |
20140018165 | Kern | Jan 2014 | A1 |
20140243103 | Rom | Aug 2014 | A1 |
20140255881 | Rom | Sep 2014 | A1 |
20140274322 | McDonald | Sep 2014 | A1 |
20150139610 | Syed | May 2015 | A1 |
20160219338 | Wang | Jul 2016 | A1 |
20170021274 | Vonderhaar | Jan 2017 | A1 |
20170282075 | Michot | Oct 2017 | A1 |
20180126285 | Kehoe | May 2018 | A1 |
20180214777 | Hingorani | Aug 2018 | A1 |
20190295367 | McDonald | Sep 2019 | A1 |