Satellite antenna ground station service system

Abstract

The present disclosure relates to a satellite antenna ground station service system. A satellite antenna ground station service includes a plurality of ground stations and associated data centers, where the data centers are part of a provider network. A client can reserve a satellite antenna access time slot via a user interface of the satellite antenna ground station service and store data directly to a data center of the provider network or a premises of the client via a direct connection between the client and the provider network. In some embodiments, the provider network can provide a plurality of network-based services, such as a computing service, a data storage service, a machine learning service, or a data analytics service, and the client can utilize one or more of these services to analyze and process data of a downlink received from a satellite of the client via a satellite antenna ground station of the satellite antenna ground station service of the provider network.

Description

[0001] This application is a divisional application of Inventive Patent Application No. 201980043600.7, filed on June 27, 2019, entitled “Satellite Antenna Ground Station Service System”. TECHNICAL FIELD

[0002] The present disclosure relates to satellite antenna ground station services. BACKGROUND

[0003] Increasingly, businesses, universities, and governments are using satellites for applications including weather, terrestrial imaging, communications, video broadcasting, and other applications. To do so today, a satellite owner / operator must also establish or obtain long-term leases on ground antennas to communicate with their satellites.

[0004] Establishing or obtaining long-term leases on ground antennas can be a significant effort and cost for a satellite owner / operator, as antennas are often needed in multiple countries to maintain connectivity for a satellite. Additionally, a satellite owner / operator’s infrastructure needs can also include computing servers and storage servers proximate to the antennas to process satellite communications and persistently store received data. Furthermore, a satellite owner / operator can need to host and run additional software to use received satellite data in their business.

[0005] All of these infrastructure needs can require significant capital investment and employee costs to build, monitor, manage, and maintain each antenna location. Additionally, the ground antennas and associated infrastructure can not be continuously or fully utilized. For example, for a satellite owner / operator with a limited number of satellites, a satellite owner / operator’s ground antennas can only be utilized when one of the satellite owner / operator’s satellites is within range of the ground antennas, otherwise, the ground antennas are not used between periods when one of the satellite owner / operator’s satellites is within range. SUMMARY

[0006] A service provider network is provided that includes: a plurality of data centers located in different geographic regions; a plurality of satellite antenna ground stations, where respective ones of the satellite antenna ground stations are located locally and connected to corresponding ones of the data centers in the different geographic regions; and one or more computing devices configured to implement a multi-tenant scheduling service configured to: receive satellite antenna ground station access requests from a plurality of clients of the service provider network; and schedule satellite antenna ground station access time slot reservations for the clients on respective ones of the satellite antenna ground stations, where the satellite antenna ground stations are integrated into the service provider network such that data received via one of the ground stations is available for use by cloud computing services of the service provider network. BRIEF DESCRIPTION OF DRAWINGS

[0007] Figure 1 A provider network is shown that includes data centers and associated satellite antenna ground stations, and where the provider network provides satellite antenna ground station services to clients, in accordance with some embodiments.

[0008] Figure 2 A provider network is shown that includes data centers and associated satellite antenna ground stations in various geographic locations, in accordance with some embodiments.

[0009] Figure 3A An example graphical user interface for a satellite antenna ground station service for scheduling satellite antenna access time slots for contact with client satellites, in accordance with some embodiments, is shown.

[0010] Figure 3B An example graphical user interface for a satellite antenna ground station service for managing reserved satellite antenna access time slots, in accordance with some embodiments, is shown.

[0011] Figure 4 A more detailed view of a ground station included in a satellite antenna ground station service, in accordance with some embodiments, is shown.

[0012] Figure 5 A more detailed view of components that can be included in a satellite antenna ground station service, in accordance with some embodiments, is shown.

[0013] Figure 6 Components of a provider network that can be used in conjunction with a satellite antenna access session for contact with client satellites, in accordance with some embodiments, are shown.

[0014] Figure 7 An example graphical user interface for a satellite antenna ground station service for providing command and control options to clients, in accordance with some embodiments, is shown.

[0015] Figure 8 An example graphical user interface for a satellite antenna ground station service for providing data downlink dashboards to clients is shown in accordance with some embodiments.

[0016] Figure 9 is a high level flow diagram illustrating various methods and techniques for providing satellite antenna access as a service to clients of a provider network in accordance with some embodiments.

[0017] Figure 10 is a high level flow diagram illustrating various methods and techniques for managing satellite antenna access during a satellite antenna access time slot in accordance with some embodiments.

[0018] Figure 11 is a high level flow diagram illustrating various methods and techniques for managing satellite antenna access requests involving multiple satellite antennas in accordance with some embodiments.

[0019] Figure 12 is a block diagram illustrating an example computing system in accordance with some embodiments.

[0020] While the embodiments herein are described by way of several embodiments and illustrative drawings, those skilled in the art will recognize that the embodiments are not limited to the embodiments or drawings described. It should be understood that the drawings and detailed description thereto are not intended to limit the embodiments to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the appended claims. The headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. As used throughout this application, the word "may" is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words "include," "including," and "includes" mean including, but not limited to. DETAILED DESCRIPTION

[0021] The systems and methods described herein can implement satellite antenna ground station services for a provider network. According to some embodiments, a service provider network includes a plurality of data centers and a plurality of satellite antenna ground stations located in different geographic regions, where respective ones of the satellite antenna ground stations are connected to corresponding ones of the data centers located in the same geographic region as the respective ones of the satellite antenna ground stations. For example, the provider network can include a plurality of availability zones, each located in a different geographic region and connected to each other via the provider network. Continuing with this example, each availability zone can include at least one data center and at least two satellite antennas located at one or more ground stations located near one of the data centers included in the availability zone. The service provider network also includes one or more computing devices, which can be included at one of the data centers or elsewhere, configured to implement a multi-tenant scheduling service for the multi-tenant satellite antenna ground station service. The multi-tenant scheduling service is configured to receive satellite antenna access requests from a plurality of clients of the provider network and schedule satellite antenna access time slot reservations for the clients on respective ones of the plurality of satellite antennas.

[0022] According to some embodiments, a multi-tenant satellite antenna ground station service includes a plurality of satellite antennas and one or more computing devices configured to implement a multi-tenant scheduling service. The multi-tenant scheduling service is configured to receive satellite antenna access requests from a client of a plurality of clients of the multi-tenant ground station service and schedule satellite antenna access time slot reservations for the client on respective ones of the plurality of satellite antennas.

[0023] According to some embodiments, a method includes providing a user interface of a multi-tenant satellite antenna ground station service to a client. The method also includes receiving a satellite antenna access request from the client via the user interface and scheduling a satellite antenna access time slot for the client on one or more of a plurality of satellite antennas of the multi-tenant ground station service.

[0024] In general, satellite owners / operators operate their own satellite antenna ground stations, or rent time on antennas and connect their own hardware and / or software to the rented antennas on ground stations operated by another entity. Additionally, most satellite owners / operators provide and manage the necessary network equipment to connect the satellite antennas owned or rented to a storage location to store data received from the satellite owner / operator's satellite. The cost involved in building and maintaining satellite antenna ground stations and / or renting satellite antennas at commercial satellite antenna ground stations can be high for many satellite owners / operators and potentially prohibitive for other potential satellite owners / operators. Additionally, because owning a satellite antenna ground station or renting antennas at commercial satellite antenna ground stations involves high costs, many satellite owners / operators can maintain a limited number of satellite antennas to contact their satellites. For example, to reduce costs, a satellite owner / operator can minimize the number of satellite antennas that the satellite / owner operator maintains access to.

[0025] A satellite owner / operator can communicate with its satellites via a limited number of satellite antennas that the satellite owner / operator maintains access to, but can not be able to communicate with the satellite owner / operator's satellites when the owner / operator's satellites are not within range of the satellite antennas that the satellite owner / operator maintains access to. During periods of time when satellites are not within range, the satellite antennas that the satellite owner / operator maintains access to can tend to go unused. This can represent a loss of cost because satellite antenna access time is a perishable resource that is lost forever if not used. For example, the amount of past unused time is lost and cannot be used in the future. Similarly, satellite resources can be at least partially perishable resources that are lost forever if not used. For example, a communications satellite that cannot relay communications during periods of time when satellites are not within range can lose cost because the amount of past unprocessed communications cannot be added to future capacity, but is instead lost forever. Thus, when the satellite owner / operator's satellite(s) are not within range of the satellite owner / operator's satellite antenna(s), a satellite owner / operator that has a limited number of satellite antennas can suffer a loss of perishable satellite antenna access time and a loss of perishable satellite access time. By way of example, a polar ground station and a polar orbiting satellite can be within range of each other for 10 minutes of a 90 minute polar orbit, but can be unused for the remaining 80 minutes of the 90 minute orbit.

[0026] In some embodiments, the satellite antenna ground station service provides clients with satellite antenna ground station access time slot reservations for access windows of short time periods, e.g., one minute, or other durations (e.g., 10 minutes, 15 minutes, etc.). Additionally, in some embodiments, the satellite antenna ground station service allows clients to make time slot reservation requests a short time before the requested time slot, e.g., within 15 minutes before the requested time slot. Given that traditional satellite antennas require long lead times to build, or to rent and configure, the satellite antenna ground station service can provide short lead times (e.g., as short as 10 minutes) by leveraging the network of satellite antenna ground stations and systems that are easily configured to access various types of satellites. Moreover, the satellite antenna ground stations are connected to high speed networks that include local data centers near the satellite antenna ground stations. Additionally, the satellite antenna ground station service can also provide clients with "elastic" satellite antenna ground station capacity that can be scaled up or down depending on client demand. For example, a client that needs a large amount of downlink data can reserve satellite antenna access time slots on multiple satellite antenna ground stations in various locations to downlink a large amount of data, and can not need to reserve other satellite antenna ground station time slots when the client does not need a large amount of downlink data or does not need downlink data at all. Thus, a client can be required to pay for the actual amount of satellite antenna ground station access time that the client needs, and can not be required to pay for satellite antenna ground station access time when the client does not need access to the client's satellite.

[0027] Additionally, the satellite antenna ground station service can be part of a provider network that has sufficient capacity to store data received from satellites and make the data available at any location in the world. For example, the provider network can be accessed from any location connected to the Internet or otherwise connected to the provider network, such as via a direct physical connection to the provider network (e.g., a dedicated network connection such as those provided by AWS Direct Connect). Additionally, in some embodiments, the satellite antennas of the satellite antenna ground station service can be located in mid-latitude locations around the world, such that at least one of the satellite antennas of the satellite antenna ground station service is within range of a client satellite at any given time (or will be momentarily).

[0028] For example, a satellite antenna ground station service can enable a client to take a picture of Greece via the client's satellite, 10 minutes later download the picture data to a satellite antenna ground station service ground station in India, process the picture data in a data center located in India or on a compute instance of a provider network located in various other locations connected to the provider network, and deliver the processed picture data to the client in Saudi Arabia 10 minutes after the picture was captured over Greece. In contrast, a similar scenario using polar ground stations would cause the satellite to take 45 minutes to cross over Greece and reach the polar ground stations.

[0029] In some embodiments, mid-latitude locations can include populated land and ocean between 60 degrees north and 60 degrees south latitude.

[0030] In some embodiments, a satellite antenna ground station service integrates satellite antennas and software-defined radio / radio frequency digital converters to data center locations around the world to provide global ground station services, such as ground stations as a service (GSaaS). In some embodiments, the satellite antenna ground station service further includes front-end processors implemented on virtual compute resources and / or encryption modules implemented on virtual compute resources to further process and decrypt downlinked data and encrypt data to be uplinked to the client's satellite. In some embodiments, a client can perform the client's satellite operations via the satellite antenna ground station service (e.g., satellite control, data uplink, and / or data downlink), and in addition can process downlinked data via any one or more of a variety of services provided by a provider network, such as a virtual compute service, a data storage service, a machine learning service, a data analytics service, a visual recognition service, a database service, or other supported network-based services. In some embodiments, a client can choose to process the client's downlinked data at the client's own premises, and can use the satellite antenna ground station service to contact the client's satellite and transfer the downlinked data to the client's premises for processing.

[0031] In some embodiments, the satellite antenna ground station service can support S-band frequency communications and X-band frequency communications, for example for communicating with low earth orbit (LEO) satellites. In some embodiments, the satellite antenna ground station service can support C-band frequency communications, Ku-band frequency communications, and Ka-band frequency communications, for example for communicating with geosynchronous orbit (GEO) satellites. In some embodiments, the satellite antenna ground station service can support UHF band frequencies. In some embodiments, the satellite antenna ground station service can support various other frequency band communications for communicating with various other types of satellites. As an example, the satellite antenna ground station service can allow streaming communication company clients to receive and transmit live media content from events such as the Super Bowl or the Olympics by downlinking live media content to a high capacity provider network containing servers in data centers located around the world in the millions or thousands and streaming live media content from the servers to streaming communication company client customers.

[0032] In some embodiments, the satellite antenna ground station service can include or connect to an identity and access management service that enforces identity and access management policies for contacting satellites. In some embodiments, a client of the satellite antenna ground station service can submit information to the identity and access management service verifying the client's ownership of a satellite or authorization to access a satellite. Once verified, the client can schedule a contact with a satellite via a satellite antenna access reservation time slot of a satellite antenna of the satellite antenna ground station service.

[0033] In some embodiments, prior to reserving a satellite antenna access time slot, the satellite antenna ground station service can instantiate one or more session instances using virtualized computing resources of another service of the service provider network that includes the satellite antenna ground station service, such as a computing service of the provider network. In some embodiments, physical computing resources can be used for the session instances (as opposed to virtual computing resources). In some embodiments, the session instances can include client data processing instances, also referred to herein as “downlink instances.” The session instances can also include client command and control instances. In some embodiments, the client data processing or “downlink instances” can process downlinked data that has been converted from analog data received by the satellite antenna to Internet Protocol (IP) digital data. For example, a satellite antenna ground station of the satellite antenna ground station service can include a software-defined radio and / or a digital converter that converts analog radio signals to digital signals. The satellite antenna ground station can further include a receiver that can perform demodulation, forward error correction, and conversion to IP. For example, the downlinked data can be converted to IP according to the VITA 49 standard (VMEbus (Versa Module Europa bus) International Trade Association 49 standard). Additionally, the client data processing or “downlink instances” can break the digital data into frames via a front-end processor, and can further decrypt the downlinked data frames via an encryption / decryption module of the client data processing or downlink instances, where the downlinked data frames are decrypted to decrypted data frames.

[0034] In some embodiments, the session instances instantiated for a reserved satellite antenna access time slot, such as the client data processing instances or “downlink instances” and the client command and control instances, can be separated from the ground station controller and the ground station downlink router by a gateway of the ground station. In some embodiments, the gateway can restrict access to the ground station controller and the ground station downlink router. For example, during a time slot reserved for a first client, the session instances of the first client can access the ground station controller and the downlink router via the gateway, and outside of the reserved time slot for the first client, the session instances can be prevented from accessing the ground station controller and the ground station downlink router. In this way, multiple clients can each have session instances instantiated and configured to communicate with a respective satellite of the client at the same time, but only the session instances of a single client can access the satellite antenna during a reserved time slot. It should be noted that because the other clients have the session instances ready prior to the start of their time slots, these clients can not need to waste time during the reserved time slot instantiating data processing instances or client command and control instances configured to communicate with the respective satellite of the client.

[0035] In some embodiments, data from a client satellite downlink can be added to a “data lake” maintained by one or more data centers of a provider network that includes the satellite antenna ground station service. In some embodiments, more than one client can contribute downlinked data to the “data lake.” In some embodiments, the provider network can include a data analytics service, a machine learning service, a visual recognition service, or other services that utilize “data lake” data to learn new relationships or for other purposes. In some embodiments, in addition to the satellite antenna ground station access being elastic and easily scalable (up or down), other services of the provider network can be elastic and easily scalable (up or down). For example, a computing service that processes downlinked data can be elastic and easily scalable (up or down). In a similar manner, a data storage service can be elastic and easily scalable (up or down) to store data downlinked from a satellite or to store other types of data, such as data generated based on the downlinked data.

[0036] In some embodiments, the satellite antenna ground station service can be in contact with a low earth orbit satellite (LEO). As an example, a LEO satellite can be used for earth observation, and can transmit up to 15 terabytes of data to a client via the satellite antenna ground station service, or the satellite antenna ground station service can store the transmitted data on behalf of the client in a storage service of a provider network that includes the satellite antenna ground station service. In some cases, a LEO satellite can complete 16 orbits around the earth in a day. In some embodiments, the satellite antenna ground station service can be in contact with a medium earth orbit satellite. As an example, a medium earth orbit satellite can be used for global positioning (GPS), and can orbit the earth between 2 and 10 times a day. In some embodiments, the satellite antenna ground station service can be in contact with a geosynchronous satellite (GEO). A GEO satellite can only orbit the earth once a day, and can stay in the same position in the sky relative to the earth. Thus, GEO satellites can typically be used for broadcasting (as for satellite television services), communication relays, macro weather observation, tracking ships, planes, etc.

[0037] Notably, because a satellite antenna ground station service as described herein can be integrated into a provider network that includes multiple data centers and networking equipment to connect the multiple data centers to each other and to customers, a client of the satellite antenna ground station service can not need to build a network connection to a ground station of the satellite antenna ground station service because the ground station of the satellite antenna ground station service is already connected to a data center that is integrated into the provider network (this is the case with current commercial satellite antenna ground stations).

[0038] Figure 1A provider network is shown that includes data centers and associated satellite antenna ground stations, where the provider network provides satellite antenna ground station services to clients, in accordance with some embodiments.

[0039] Provider network 102 includes data center 110 and associated ground station 142, data center 112 and associated ground station 144, and data center 114 and associated ground station 146. In some embodiments, a provider network like provider network 102 can include additional data centers and associated ground stations. Provider network 102 is also connected to client A 140A, client B 140B, and client C 140C via network 138. In some embodiments, a provider network like provider network 102 can be connected to any number of clients, and satellite antenna ground station services like ground station services 116 of the provider network can provide satellite antenna ground station services to any number of clients of the provider network. For example, provider network 102 is also capable of contacting satellites owned or operated by clients A-C via satellite antennas at ground stations 142, 144, and 146 of ground station services 116. For example, ground station 142 can be contacting client A satellite 104, ground station 144 can be contacting client B satellite 106, and ground station 146 can be contacting client C satellite 108.

[0040] In some embodiments, data downlinked from a client satellite can be provided to and / or stored in a data center associated with a ground station of a satellite antenna ground station service. For example, data downlinked from client A satellite 104 can be made available to and / or stored in data center 110. Further, in some embodiments, each data center of a provider network can be connected to other data centers of the provider network via high speed network connections of the provider network. For example, data centers 110, 112, and 114 can be connected to each other via high speed network connections of provider network 102. Accordingly, any client of a satellite antenna ground station service that accesses the satellite antenna ground station service of the provider network including the satellite antenna ground station service, e.g., via an internet connection to the provider network, can access data downlinked from a client's satellite. Further, in some embodiments, a client can access downlinked data from a remotely located data center using high speed network connections of the provider network such that, from the perspective of the client, there is not a significant difference in data access latency compared to if the data were accessed from a locally located data center. Further, in some embodiments, downlinked client data can be relocated from multiple data centers to a data center near the client and / or consolidated in a data center near the client. For example, downlinked data can be collected using corresponding satellite antenna ground stations associated with multiple data centers and transmitted over high speed network connections of the provider network such that the downlinked data is consolidated in one or more data centers.

[0041] Further, computing devices of a provider network, such as storage servers, computing servers, networking devices, etc., of provider network 102 can implement a variety of other provider network services. For example, Figure 1The illustrated dashed boxes show a logical view of services that can be provided by the provider network 102 using physical hardware located in the data centers 110, 112, 114, etc. In some embodiments, in addition to the ground station services 116, the provider network can also provide compute services 126, where the compute services implement virtualized compute instances allocated to clients of the compute services, and where the virtualized compute instances are implemented using physical computing devices included in the data centers 110, 112, 114, etc. In some embodiments, the provider network, such as the provider network 102, also provides data storage services, such as the data storage services 128. In some embodiments, the data storage services can be any of a variety of types of data storage services, such as a block-based storage service that provides block storage resources to instances of compute services, such as the compute services 126. Additionally, in some embodiments, the data storage services can be an object-based storage service that stores data objects (such as downlinked satellite data) on behalf of clients, or can be a cold storage service that provides a low-cost storage solution for infrequently accessed data objects (such as downlinked satellite data).

[0042] In some embodiments, the provider network, such as the provider network 102, also includes machine learning services, such as the machine learning services 130. In some embodiments, the machine learning services can apply machine learning techniques to downlinked satellite data, such as can be stored in the data storage services 128. In some embodiments, the provider network, such as the provider network 102, can further include data analytics services, such as the data analytics services 132. In some embodiments, the data analytics services can perform data analytics operations on downlinked satellite data and / or other data stored in data storage services of the provider network. For example, in some embodiments, the data analytics services can compare data collected from other sources to downlinked satellite data to perform data analytics.

[0043] In some embodiments, a provider network, such as the provider network 102, can further include database services, such as the database service 134. In some embodiments, one or more databases managed by the database service 134 can be at least partially populated with satellite downlink data received from a client satellite, with the populated databases made available to the client. Additionally, in some embodiments, a provider network, such as the provider network 102, can provide a plurality of other network-based services, such as the other network-based services 136, which can be used to analyze, manipulate, store, etc. satellite downlink data received from a client satellite. For example, in some embodiments, the other network-based services 136 can include a flexible map-reduce service, a query service, a plurality of types of machine learning services (in addition to or as part of the machine learning service 130), an encryption key management service, a software development kit service, a networking service, a mobile communication service, an Internet of Things (IoT) service, a security service, an enterprise application, etc.

[0044] In some embodiments, a satellite antenna ground station service, such as the ground station service 116, implements a user interface, such as the user interface 124. In some embodiments, a client can verify ownership or authority over a satellite by submitting identification credentials to the satellite service via the user interface. In some embodiments, a scheduling / authorization component, such as the scheduling / authorization component 118, can verify ownership of a satellite by a client or authority of a client with respect to a satellite. Once a client is authorized to use a given client satellite, the client can submit a request for satellite antenna access time slots for a contact session with the client satellite for which the client has been authorized. For example, the clients A-C submit access requests to the ground station service 116 via the network 138 and the user interface 124 of the ground station service 116. In some embodiments, a user interface of a satellite antenna ground station service, such as the user interface 124, can be a web-based graphical user interface, with a client submitting satellite antenna access time slot requests via the graphical user interface. In some embodiments, a user interface of a satellite antenna ground station service, such as the user interface 124, can be an application programming interface (API), with a client programmatically submitting requests for satellite antenna access time slots via the API of the satellite antenna ground station service.

[0045] In some embodiments, in response to receiving a request from a client serviced by a satellite antenna ground station service, a scheduling / authorization component of the satellite antenna ground station service can reserve a time slot on a satellite antenna serviced by the satellite antenna ground station service. In some embodiments, the client of the satellite antenna ground station service can indicate in the request a desired ground station location, a desired time slot, a satellite to be contacted during satellite antenna access to the time slot, and / or additional information about the requested satellite antenna access time slot. In some embodiments, the scheduling / authorization component of the satellite antenna ground station service, such as the scheduling / authorization component 118 of the ground station service 116, can match the requested time slot, the requested ground station, etc. to available time slots on satellite antennas of ground stations included in the satellite antenna ground station service.

[0046] In some embodiments, a scheduling / authorization service, such as the scheduling / authorization component 118, can apply one or more priority factors to determine a priority of clients requesting a time slot in conflict. For example, some client applications can not be substantially impacted by using a different ground station than a requested ground station, while other client applications can be impacted, or some clients can not specify a requested ground station location. In such cases, when requests for the same ground station during the same time slot conflict, a scheduling / authorization component, such as the scheduling / authorization component 118, can prioritize requests from clients that are impacted by ground station location over requests from clients that are less impacted by ground station location by changing the ground station location. Additionally, in a similar manner, a scheduling / authorization component, such as the scheduling / authorization component 118, can apply one or more priority factors to resolve conflicting requests based on time. For example, some client applications can be sensitive to time delay, while other client applications can not be sensitive to time delay. In such cases, a scheduling / authorization component, such as the scheduling / authorization component 118, can prioritize requests that are time sensitive over other requests.

[0047] In some embodiments, a scheduling / authorization component can operate according to a first come, first served model, in which time slot reservations are provided to clients from an inventory of remaining available time slots of ground stations included in a satellite antenna ground station service based on an order in which requests are received. In some embodiments, a scheduling / authorization component can operate according to a hybrid model, in which time slot reservations are provided to clients from an inventory of remaining available time slots of ground stations included in a satellite antenna ground station service based on an order in which requests are received, with exceptions for certain categories of sensitive requests that can be time sensitive or ground station location sensitive.

[0048] In some embodiments, a satellite antenna ground station service integrates satellite and / or antenna control and data planes into a provider network service, such as a satellite antenna ground station service. For example, in some embodiments, a satellite antenna ground station service, such as ground station service 116, includes a command and control component and a data processing component, such as command and control component 120 and data processing component 122. In some embodiments, a client of a satellite antenna ground station service can remotely control one or more parameters of a ground station and / or a client's satellite via a command and control component, such as command and control component 120. For example, a client can interact with a command and control component via a user interface of a satellite antenna ground station service, such as a web-based graphical user interface, or an API of a satellite antenna ground station service, such as user interface 124.

[0049] In some embodiments, a command and control component can be implemented using a compute instance of a compute service, such as compute service 126, where the compute instance is allocated for instantiating the command and control instance. In a similar manner, a data processing component can be implemented using a compute instance of a compute service, such as compute service 126, where the compute instance is allocated for instantiating the data processing component.

[0050] In some embodiments, a session instance, such as a command and control instance and a data processing instance, can be instantiated prior to a reserved time slot reserved for a client. Accordingly, a command and control instance and a data processing instance can be ready to process downlinked or uplinked data from a client satellite at the beginning of a reserved time slot without needing to configure a command and control component or a data processing component after the beginning of a reserved time slot. Additionally, in some embodiments, a configuration of a command and control component and a data processing component for a particular client can be stored by a satellite antenna ground station service and can be used to instantiate a command and control instance and / or a data processing instance for a future time slot reserved for a client.

[0051] In some embodiments, a session instance, such as a command and control instance and a data processing instance, can be implemented on computing resources attached to or associated with a data center of a ground station at which a client has a reserved time slot for satellite antenna access. Accordingly, satellite downlinked data from a client via a satellite antenna of a satellite antenna ground station service during an access time slot can be processed locally via a data processing instance implemented at an attached data center. In a similar manner, a locally implemented command and control instance can be implemented at a data center attached to a satellite antenna allocated to a client during a reserved time slot of satellite antenna access.

[0052] In some embodiments, ground stations served by satellite antenna ground station services, such as ground stations 142, 144, and 146, include one or more satellite antennas, software-defined radios, and modems to communicate with satellites using radio signals. In some embodiments, ground stations can receive data from client satellites downlinks, monitor the health and status of client satellites, provide commands to client satellites to perform tasks, such as taking photographs, for example, or transmit television, voice, or radio signals to customers on Earth. In some embodiments, ground stations can include redundant components, such as primary and secondary antennas, software-defined radios, modems, and the like.

[0053] In some embodiments, user interfaces served by satellite antenna ground station services, such as user interface 124, can include one or more APIs that serve as endpoints that allow satellite antenna ground station services to be programmatically integrated into existing satellite operations systems. In some embodiments, satellite antenna ground station services can further relay communications to other ground stations using satellites owned or operated by the satellite antenna ground station services. For example, a satellite antenna ground station service can downlink data from a client satellite and then relay the downlinked data to another ground station via a geosynchronous satellite operated by the satellite antenna ground station service.

[0054] Figure 2 A provider network including data centers and associated satellite antenna ground stations in various geographic locations is shown in accordance with some embodiments.

[0055] In some embodiments, satellite antenna ground station services can include multiple ground stations and associated data centers distributed in mid-latitude regions of the Earth such that a client satellite is within range (or will be within range momentarily) of at least one ground station of the satellite antenna ground station service regardless of the satellite’s position in the satellite’s orbit.

[0056] For example, a provider network, such as provider network 102, can include a ground station 204 and associated data center 206 on the Pacific Ocean, which can be implemented on an island or on an ocean-going vessel or platform. The provider network can also include a ground station 240 and data center 242 located on the Pacific coast of the United States, which is connected to data center 206 via a network connection 202, which can be a fiber-optic high-speed cable, for example. In addition, the provider network can include another ground station 208 and data center 210 located on the East Coast of the United States.

[0057] As Figure 2As shown, the provider network, such as the provider network 102, can include any number of ground stations and associated data centers located around the world. For example, the provider network 102 also includes a ground station 236 and data center 238 located in Oslo, Norway, a ground station 212 and data center 214 located in Brazil, a ground station 216 and data center 218 located in South Africa, a ground station 220 and data center 222 located in Australia, a ground station 224 and data center 226 located in Japan, a ground station 228 and data center 230 located in India, a ground station 232 and data center 234 located in Turkey, and a ground station 236 and data center 238 located in London.

[0058] In some embodiments, each data center of the provider network 102 can be connected to each other via a high-speed connection 202. In some embodiments, more or fewer high-speed connections 202 can be included in the provider network 102 between data centers.

[0059] Figure 3A An example graphical user interface for scheduling satellite antenna access slots for satellite antenna ground station services to contact a client satellite is shown in accordance with some embodiments.

[0060] In some embodiments, the user interface of a satellite antenna ground station service, such as the user interface 124 of the ground station service 116 shown in Figure 1 may provide a client with a graphical user interface for scheduling satellite antenna access slots, such as shown in Figure 3A-3B For example, the scheduling interface 300 includes a satellite verification / authorization element 302, a contact scheduling element 312, and an automatic contact scheduling element 324.

[0061] In some embodiments, a client can provide satellite identification information and authorization information to a satellite antenna ground station service for a satellite owned or operated by the client. For example, the client can provide a satellite name via block 304, a satellite identifier such as a NORAD catalog number, NORAD ID, NASA catalog number, USSPACECOM object number, other catalog number and similar variants, COSPAR number, and the like via block 306. In addition, the client can provide other identifying information or authorization information via block 308. To verify authorization, the client can click a button 310 after filling in one or more of blocks 304, 306, or 308.

[0062] In some embodiments, the satellite antenna ground station service can maintain an authorization database and can compare the submitted information to the information stored in the authorization database in order to verify the client's authorization to communicate with the satellite. Additionally, in some embodiments, the satellite antenna ground station service can submit the information provided by the client to a third party to verify authorization, such as a government entity. Once authorization / ownership is verified, the client can schedule a contact session with the verified satellite via the scheduling element 312.

[0063] For example, the client can enter the name of the satellite to be contacted via block 314 of the scheduling element 312. The client can also indicate the desired time slot via block 316 and, optionally, the desired ground station location via block 320. In some embodiments, the client can wish the satellite antenna ground station service to provide a suggested time slot and / or ground station to schedule the reserved satellite antenna access time slot. For example, the client can enter the satellite name via block 312 and can click on button 332 to have a suggested time slot and / or suggested ground station location provided thereto. In some embodiments, the client can specify a ground station or time slot and can request a recommendation for a time slot at the specified ground station or a ground station at the specified time slot. To reserve a satellite antenna access time slot, the client can click on the submit button 322 to reserve the time and ground station indicated in blocks 316 and 320. In response, the satellite antenna ground station service can send a confirmation message to the client to confirm the reservation.

[0064] In some embodiments, the client can be more concerned with the amount of data to be uplinked to or downlinked from the client's satellite and can be less concerned with when the contact session occurs or from which ground station the contact session occurs. In such cases, the client can identify the satellite to be contacted via block 326 of the automatic contact scheduling element 324 and can indicate the amount of data to be transmitted via block 326 of the automatic contact scheduling element 324. The client can then click on button 330 to reserve a satellite antenna access time slot of sufficient amount and / or duration to transmit the amount of data indicated via block 328. In some embodiments, the scheduler of the satellite antenna ground station service can determine the number and duration of contact sessions required to transmit the requested amount of data and can reserve a satellite antenna access time slot sufficient to conduct the determined number and duration of contact sessions to transmit the indicated amount of data. In some embodiments, instead of indicating the amount of data to be transmitted, the client can indicate one or more files, objects, etc. to be uplinked to or downlinked from the satellite and the scheduler of the satellite antenna ground station service can determine the amount of data required to uplink or downlink the indicated files or objects. The scheduler of the satellite antenna ground station service can then reserve a satellite antenna access time slot sufficient to conduct the determined number and duration of contact sessions to transmit the determined amount of data.

[0065] In some embodiments, a client can request a contact session with different durations. For example, a client can request a contact session as short as five minutes. Additionally, in some embodiments, a client can request a contact session in multiple geographic regions or geographic regions (e.g., different ground station locations). In some embodiments, a scheduler of a satellite antenna ground station service can calculate when to reserve a contact session based on stored information about a client’s satellite. For example, a scheduler can perform orbital mechanics calculations to determine when to schedule a contact session with a client’s satellite. In some embodiments, a client can further indicate in a request for a contact session an identity and access management policy to apply to the client’s satellite (not shown).

[0066] Figure 3B An example graphical user interface for a satellite antenna ground station service for managing reserved satellite antenna access slots is shown in accordance with some embodiments.

[0067] In some embodiments, a satellite antenna ground station service can provide a contact session monitoring page in which a client can view scheduled contact sessions and modify or delete scheduled contact sessions. For example, a scheduling interface, such as a contact session monitoring page, can include any number of satellite contact queues for scheduled satellite contacts. As shown, Figure 3B The scheduling interface 350 includes a satellite 1 contact queue 352 and a satellite 2 contact queue 362. In some embodiments, a contact queue can list scheduled contact sessions for a client’s satellite and can include an option to modify or delete a scheduled contact session. For example, the satellite 1 contact queue 352 lists scheduled contact sessions 354, 356, and 358 and includes a modify / delete button 360. As another example, the satellite 2 contact queue 362 lists scheduled contact sessions 364, 366, and 368 and includes a modify / delete button 370.

[0068] In some embodiments, a client can modify or delete a scheduled contact session in a short time, such as 15 minutes before a scheduled start time of a contact session.

[0069] Figure 4 A more detailed view of a ground station included in a satellite antenna ground station service is shown in accordance with some embodiments.

[0070] In some embodiments, a ground station of a satellite antenna ground station service included in a provider network, such as a ground station 436 of the ground station service 116 of the provider network 102, includes two or more satellite antennas, such as satellite antennas 402 and 420. In some embodiments, any ground station described herein, such as the ground stations 142, 144, and 146 shown in Figure 1 FIG. 4, includes two or more satellite antennas. In some embodiments, a ground station of a satellite antenna ground station service included in a provider network, such as the ground station 436 of the ground station service 116 of the provider network 102, includes two or more satellite antennas, such as satellite antennas 402 and 420. In some embodiments, any ground station described herein, such as the ground stations 142, 144, and 146 shown inFigure 2 The ground stations 204, 208, 212, 216, 220, 224, 228, 232, 236, and / or 240 can each include components similar to those shown in FIG. 4 for the ground station 436. Figure 4

[0071] The ground station 436 includes a wideband receiver 404, a narrowband receiver 406, and one or more other band receivers 408 connected to the satellite antenna 402. In addition, an antenna control unit 410 is connected to the satellite antenna 402. In a similar manner, a wideband receiver 422, a narrowband receiver 424, and one or more other band receivers 426 are connected to the satellite antenna 420, as is an antenna control unit 428.

[0072] In some embodiments, the wideband receiver, the narrowband receiver, and / or the other band receivers can include a software-defined radio and / or a digital converter that converts analog signals transmitted to or received from a satellite into digital signals. In some embodiments, the software-defined radio and / or the digital converter can perform demodulation, forward error correction, and conversion of the digital signals into Internet Protocol formatted data (IP formatted data). In some embodiments, a router, such as the router 412, can route the downlinked data from the wideband receiver, the narrowband receiver, or the other band receivers to an additional router 414 that routes the downlinked data through a gateway 438 to a session instance 434 that instantiates a contact session for a client. The router 414 can also route the downlinked data to a ground station controller 416. In addition, the ground station controller 416 can communicate with a satellite antenna ground station service scheduler, for example, to determine which client is scheduled for a given time slot and to apply a configuration stored for the client during the client’s time slot. In a similar manner, the routers 430 and 432 and the gateway 440 can route data downlinked from the satellite antenna 420 to the client session instances 434 and / or the ground station controller 416.

[0073] In some embodiments, the ground station controller 416 can control the operation of the satellite antenna 402 or 420 through commands routed to the antenna control unit 410 or the antenna control unit 428 via the routers 414 and 412 or via the routers 432 and 430.

[0074] ​In some embodiments, the wideband receivers 404 and 422 and narrowband receivers 406 and 424 can include bi-directional digital converters with forward error correction (FEC) that convert between analog satellite signals and digital IP signals. In some embodiments, the data processing instances, including in the session instance 434, can further implement the receiver / modem and front-end processor. Additionally, the data processing instances 434 can include a command and control instance that allows a client to command and control the client's satellite.

[0075] In some embodiments, a client can utilize multiple satellite antennas to communicate with the client's satellite during a contact session. For example, in some embodiments, a client can use both satellite antennas 402 and 420 to communicate with the client's satellite during a contact session. In some embodiments, a client can downlink up to 7,000 megabits of data per second on two channels. In some embodiments, the electronic control array of the satellite antennas can allow multiple contacts with a single satellite sensor simultaneously or sequentially.

[0076] Figure 5 A more detailed view of components that can be included in a satellite antenna ground station service is shown, according to some embodiments. For example, Figure 5 Additional details regarding components that can be included in a ground station service 116 as shown in FIG. 1 or any satellite antenna ground station service described herein are shown. Figure 1 Additional details regarding components that can be included in a ground station service 116 as shown in FIG. 1 or any satellite antenna ground station service described herein are shown.

[0077] In some embodiments, an identity and access management service 538 included in or available to a satellite antenna ground station service such as the ground station service 116 can receive satellite identification information and ownership / authorization information, and can verify whether a client is authorized to communicate with a given satellite. As shown in FIG. 1, in some embodiments, the identity and access management service or component can be included in the satellite antenna ground station service scheduler or can be separate. Figure 1 As shown in FIG. 1, in some embodiments, the identity and access management service or component can be included in the satellite antenna ground station service scheduler or can be separate.

[0078] For example, an identity and access management service, such as identity and access management service 538, can receive a satellite identifier, such as a NORAD catalog number, NORAD ID, NASA catalog number, USSPACECOM object number, catalog number and similar variants, COSPAR number, and the like, and other identifying information or authorization information from a client via user interface 124. To verify authorization, the identity and access management service can maintain an authorization database and can compare the submitted information to information stored in the authorization database to verify authorization of the client to communicate with the satellite. Additionally, in some embodiments, an identity and access management service, such as identity and access management service 538, can submit information provided by the client to a third party to verify authorization, such as to a government entity. Once authorization / ownership is verified, the client can schedule a contact session with the verified satellite via ground station service scheduler 118.

[0079] In some embodiments, a ground station service scheduler, including in a satellite antenna ground station service, such as ground station service scheduler 118 included in ground station service 116, can include a session instance manager 508 that instantiates a session instance for a client prior to a scheduled reserved time slot. In some embodiments, a session instance manager, such as session instance manager 508, can cause a machine image to be loaded onto the instantiated session instance to implement a client data processing instance (such as shown at 604 of Figure 6 In some embodiments, a session instance manager 508 can cause a stored data processing machine image stored in data processing machine image store 532 to be launched on the instantiated session instance to implement a client data processing session instance. In a similar manner, a session instance manager 508 can cause a stored client command and control machine image stored in command and control machine image store 534 to be launched on the instantiated session instance to implement a client command and control session instance. Figure 6

[0080] ​In some embodiments, a ground station service scheduler, such as ground station service scheduler 118, can include an orbital propagator engine 510 to determine respective orbital positions of satellites at future times. These predicted orbital positions can be used when selecting time slots and ground stations for requested contact sessions (e.g., satellite antenna access time slot reservations) with particular satellites. In addition, ground station service scheduler 118 can include a minimum viable contact requirements store 512 for use in scheduling contacts with client satellites. Further, a ground station service scheduler can include a joint management element 514 to determine how communications with a particular satellite are affected by actual or apparent proximity of other orbital objects. In addition, a ground station service scheduler can include a hardware conflict resolution element 516 to resolve conflicting requests for the same satellite antenna hardware at the same time.

[0081] In some embodiments, a ground station service scheduler, such as ground station service scheduler 118, can submit a session instance request 504 to a provider network computing service, such as computing service 126, prior to reserving a time slot. The computing service can provision a session instance that then loads (or launches) a data handler image from a data handler image store 532 and then loads (or launches) a client command and control handler image from a command and control handler image store 534. In addition, ground station service scheduler 118 can submit a resource allocation request 502 to a ground station controller, such as ground station controller 416, and can submit a gateway access authorization 506 for the session instance to gateways 438 and 440. In some embodiments, a client can not be able to access a ground station controller or downlink data router via a gateway prior to reserving a time slot.

[0082] In some embodiments, a satellite antenna ground station service, such as ground station service 116, can store client configuration data and a current contact schedule in data store 518. The satellite antenna ground station service can further store telemetry information for a client satellite in telemetry store 536. A ground station controller, such as ground station controller 416, can include a state management system 524 for maintaining a state with a satellite during a contact session. In addition, the ground station controller can include a hardware telemetry system 528 to adjust an antenna based on satellite telemetry during a contact session. Further, the ground station controller 416 can include a hardware command module 522 for generating hardware commands for satellite antenna hardware and an alert response module 526 for indicating and / or allowing a response to satellite antenna alerts. In addition, the ground station controller 416 can issue commands to hardware interface driver(s) 530, which can work with antenna control unit 410 or antenna control unit 428 to execute commands issued by the ground station controller 416. For example, the ground station controller can cause a satellite antenna to be actuated in a direction of a satellite with which the satellite antenna is in contact and can adjust the antenna to maintain contact with the satellite during a contact session.

[0083] In some embodiments, in response to a failure of a satellite antenna or hardware associated with a satellite antenna, a ground station controller, such as ground station controller 416, can send a hardware failure / replanning request 520 to a ground station service scheduler, such as ground station service scheduler 118. For example, in some embodiments, in response to hardware failure / replanning request 520, a satellite antenna ground station service can reserve a time slot on another satellite antenna at the ground station or another ground station. In some embodiments, the satellite antenna ground station service can provide access to another satellite antenna at the same ground station for the remaining duration of the current contact session.

[0084] Figure 6 Components of a provider network that can be used in conjunction with a satellite antenna access session for contacting a client satellite are shown, in accordance with some embodiments.

[0085] As discussed previously, a session instance can be provided to a client prior to and during a contact session. For example, Figure 6 A session instance 618 provided to a client 140 during a contact session (e.g., a reserved satellite antenna access time slot) is shown. In addition, in some embodiments, a direct connection 602 from a provider network data center to a client premises can be provided to the client, where data for the downlink is processed by the client at the client premises.

[0086] In some embodiments, the session instance 618 can include the client data processing instance 604 and the client command and control instance 610. In some embodiments, the client data processing instance 604 can include the front-end processing element 606 and / or the encryption processing element 608. In some embodiments, the client command and control instance 610 includes the satellite status and health dashboard 612, the satellite control module 614, and / or the ground station control module 616. For example, the status and health dashboard 612 can provide status and health information as shown by the status and health dashboard 702 shown in FIG. 7. As another example, the satellite control module 614 can cause commands received via the satellite command interface 712 shown in FIG. 7 to be executed. As yet another example, the ground station control module 614 can cause commands received via the ground station control interface 720 shown in FIG. 7 to be executed. Figure 7 Figure 7 Figure 7

[0087] In some embodiments, the client data processing instance 604 can further include a data dashboard module (not shown) that implements a data dashboard 802 as shown in FIG. 8. Figure 8

[0088] In some embodiments, downlink data received via the gateway 438 or 440 can be routed to the client data processing instance 604 and further processed via the front-end processing element 606 and can be decrypted via the encryption processing element 608. The processed and decrypted data can be routed to any of a variety of services provided by the provider network 102, such as the compute service 126, the data storage service 128, the machine learning service 130, the data analytics service 132, other web-based services 136, etc. Additionally, the processed data can alternatively or additionally be provided to the client(s) 140 via the network 138. Additionally, the client(s) 140 can also access data processed or generated by any of the services of the provider network via the network 138.

[0089] ​​​​In some embodiments, the client(s) 140 can include satellite owners / operators and / or other client(s) that utilize services of the service provider network. The other clients can not have access to the session instance 618, but can utilize other services of the provider network. Clients of the provider network can communicate network-based service requests to the provider network 102 via an external network 138. In various embodiments, the external network 138 can encompass any suitable combination of networking hardware and protocols necessary to establish network-based communications between the clients and the provider network 102. For example, the network 138 can generally encompass various telecommunications networks and service providers that collectively implement the Internet. The network 138 can also include private networks such as local area networks (LANs) or wide area networks (WANs), as well as public or private wireless networks. For example, a given client and the provider network 102 can each be provided within an enterprise having their own internal networks. In such embodiments, the network 138 can include the hardware (e.g., modems, routers, switches, load balancers, proxy servers, etc.) and software (e.g., protocol stacks, accounting software, firewall / security software, etc.) necessary to establish networking links between the given client and the Internet, and between the Internet and the provider network 102. It should be noted that in some embodiments, the client 140 can communicate with the provider network 102 using a private network rather than the public Internet (e.g., a direct connection 602).

[0090] The provider network 102 can be established by an entity such as a company or a public sector organization to provide one or more services (such as various types of cloud-based computing or storage) to clients 140 that can be accessed via the Internet and / or other networks. In some embodiments, the provider network 102 can be the same as the provider network 102 described in Figure 1 and 2 The provider network 102 can include a plurality of data centers that implement and distribute a repository of hosted resources (such as a collection of physical and / or virtualized computer servers, storage devices, networking equipment, etc. (e.g., a computing system 1200 described below in relation to Figure 12 ) necessary to implement and distribute the infrastructure and services provided by the provider network 102. In some embodiments, the provider network 102 can include a plurality of data centers that implement and distribute a repository of hosted resources (such as a collection of physical and / or virtualized computer servers, storage devices, networking equipment, etc. (e.g., a computing system 1200 described below in relation to Figure 1 and Figure 2The provider network 102 can provide computing resources (such as virtual compute services 126), data storage services 128 (such as block-based storage services) or various other storage types (such as object / key-value based data stores), or various types of database systems (such as database services 134) and / or any other type of network-based service 136. Clients 140 can access these various services provided by the provider network 102 via the network 138. Likewise, the network-based services themselves can communicate and / or utilize each other to provide different services. For example, compute resources provided to clients 140 in "instances" such as virtual or physical compute instances or storage instances can utilize other resources.

[0091] The compute services 126 can provide various compute instances to clients 140. For example, virtual compute instances can be implemented on one or more resource hosts included in data centers (such as the data centers described in Figure 1 and 2 , which contain one or more servers with specified computing capabilities (which can be specified by indicating the type and number of CPUs, main memory size, etc.) and a specified software stack (e.g., a particular version of an operating system that can run on top of a hypervisor). A variety of different types of computing devices can be used, individually or in combination, to implement compute instances of the virtual compute services 126 in different embodiments, including dedicated computer servers, storage devices, network devices, etc. In some embodiments, an instance client 140 or any other user can be configured (and / or authorized) to direct network traffic to a compute instance.

[0092] The compute instances can operate or implement various different platforms, such as application server instances, Java TM virtual machines (JVMs), specialized operating systems, platforms that support various interpreted or compiled programming languages such as Ruby, Perl, Python, C, C++, etc., or high-performance computing platforms that are suitable for executing client applications without requiring, for example, that the clients 140 access the instances.

[0093] Clients of the service provider network can encompass any type of client configurable to submit requests to the provider network 102. For example, a given client can include a suitable version of a web browser, or can include a plug-in module or other type of code module configured to execute as an extension of or within an execution environment provided by a web browser. Alternatively, a client can encompass an application, such as a database application (or a user interface thereof), a media application, an office application, or any other application that can utilize a computing instance of the computing service 126 or other network-based service in the provider network 102 to perform various operations. In some embodiments, the clients 140 can include satellite owners / operators of the service provider network and / or other clients. In some embodiments, such an application can include sufficient protocol support (e.g., for a suitable version of the Hypertext Transfer Protocol (HTTP)) to generate and process network-based service requests without having to implement full browser support for all types of network-based data. In some embodiments, the clients 140 can be configured to generate network-based service requests according to a Representational State Transfer (REST) style network-based service architecture, a document- or message-based network-based service architecture, or another suitable network-based service architecture.

[0094] Figure 7 An example graphical user interface for a satellite antenna ground station service to provide command and control options to a client is shown in accordance with some embodiments.

[0095] In some embodiments, a user interface of a satellite antenna ground station service, such as the user interface 124 of the ground station service 116 shown in Figure 1 may provide a graphical user interface for a client to command and control a satellite and satellite antenna. For example, the command and control interface 700 includes a dashboard element 702, a satellite command interface 712, and a ground station control interface 720.

[0096] In some embodiments, a dashboard, such as the dashboard 702, can provide a client with information about the client's satellite, information about the ground station / satellite antenna assigned to the client during a contact session, and information about the contact session. In some embodiments, a dashboard can be configurable by a client to include the information elements most relevant to the client. For example, the dashboard 702 includes a satellite health element 704, a satellite status element 706, a satellite orbital position 708, a session countdown clock 734, and a button 710 that allows the client to add other monitoring parameters to the dashboard 702, modify the monitoring parameters included in the dashboard 702, or remove the monitoring parameters included in the dashboard 702.

[0097] In some embodiments, a satellite command interface, such as satellite command interface 712, includes one or more command elements that allow a client to remotely control a satellite of the client. For example, satellite command interface 712 includes telemetry, tracking, and control command element 714 and satellite program code element 716. For example, in some embodiments, a client can uplink command code for a task to be performed by a satellite via satellite program code element 716, and / or can issue satellite navigation or other commands to a satellite of the client via telemetry, tracking, and control command element 714. In some embodiments, to execute commands entered via telemetry, tracking, and control command element 714 and satellite program code element 716, a client can select submit button 718. In response, a client command and control instance, such as client command and control instance 610, can issue the indicated commands to a ground station controller, such as ground station controller 416, or to a satellite of the client via a wideband receiver, a narrowband receiver, or other band receiver, such as wideband receivers 404 and 422, narrowband receivers 406 and 424, or other band receivers 408 and 426. In some embodiments, satellite command and control can be signaled via S-band frequencies at a rate of approximately 56 kbps, and a ground station can receive mission payload data via X, Ka, C, or Ku frequency bands at a rate of 50-1,000 mbps. Command signals and payload signals can be converted between analog and digital signals via a software-defined radio and / or digital converter included in a wideband receiver, a narrowband receiver, or other band receiver.

[0098] In some embodiments, the ground station command interface, such as ground station command interface 720, includes one or more command elements that allow a client to remotely control the satellite antenna and / or other components of the ground station assigned to the client during a contact session (e.g., a reserved satellite antenna client access time slot). For example, ground station command interface 720 includes an automatic control option 722, a modem adjustment element 724, a software-defined radio adjustment element 724, a front-end processing adjustment element 728, and an antenna adjustment element 730. For example, in some embodiments, the client can select automatic control of the satellite antenna, wherein modem adjustments, software-defined radio adjustments, front-end processing adjustments, and antenna adjustments are automatically performed for the client during a contact session (e.g., a reserved satellite antenna client access time slot). In other embodiments, the client can make one or more adjustments to these parameters via modem adjustment element 724, software-defined radio adjustment element 724, front-end processing adjustment element 728, and / or antenna adjustment element 730. To implement client adjustments, the client can select a submit button 732. In response, the submitted adjustments can be performed by a ground station controller, such as ground station controller 416, or by a front-end processor of a session instance, such as front-end processing element 606 of client data processing instance 604. In some embodiments, instance adjustments that can be performed via a ground station control interface, such as ground station control interface 720, include frequency adjustments, protocol adjustments, frame synchronization adjustments, predefined configurations for normal and abnormal operation, and / or other adjustments to the communication frequencies of satellites used to contact clients.

[0099] Figure 8 An example graphical user interface for a satellite antenna ground station service for providing a data downlink dashboard to a client, according to some embodiments, is shown.

[0100] In some embodiments, the user interface of the satellite antenna ground station service, such as Figure 1 The user interface 124 of the ground station service 116 shown can provide a data dashboard to the client during a contact session. For example, the data dashboard interface 800 includes a data dashboard 802. The data dashboard 802 can be implemented based on information received by the user interface from a client data processing instance, such as client data processing instance 604.

[0101] In some embodiments, a data dashboard, such as data dashboard 802, can include a target storage location element 804 for data from a client's satellite downlink. In some embodiments, the data dashboard can also include an indicator 806 indicating the amount of downlinked data that has been received and an indicator 808 indicating the amount of downlinked data that has not been received. In some embodiments, a data dashboard, such as data dashboard 802, can further include a storage location selection element 810 that allows a client to select a storage location for data received from the client's satellite. For example, a client can select a storage location in a storage service of a provider network, such as data storage service 128.

[0102] Figure 9 is a high level flowchart illustrating various methods and techniques for providing satellite antenna access as a service to clients of a provider network, according to some embodiments.

[0103] At 902, a satellite antenna ground station service provides a user interface to a client of the satellite antenna ground station service to reserve a satellite antenna access time slot on a satellite antenna located at a ground station included in the satellite antenna ground station service and located around the world.

[0104] At 904, the satellite antenna ground station service receives a satellite antenna access request from the client via the user interface. The request can be received via a web-based graphical user interface, or can be received programmatically via an API of the user interface or via other means. In some embodiments, the request can indicate a client satellite to contact, and the satellite antenna ground station service can defer to select a time and ground station for contacting the client satellite. Alternatively, the request can indicate a desired time slot, a desired ground station, or both, and the satellite antenna ground station service can attempt to reserve a satellite antenna access time slot at the requested time and / or at the requested ground station. In some embodiments, if the desired time slot and / or ground station request cannot be satisfied due to conflicting reservations, the satellite antenna ground station service can provide an alternative suggestion.

[0105] For example, at 906, the satellite antenna ground station service can match the requested time slot and ground station to available time slots at multiple ground stations of the satellite antenna ground station service for multiple clients.

[0106] At 908, the satellite antenna ground station service can schedule a satellite antenna access time slot for the client according to the request during the matched time slot. Upon successfully reserving a satellite antenna access time slot for the client, the satellite antenna ground station service can provide a confirmation message to the client.

[0107] Figure 10is a high level flow diagram illustrating various methods and techniques for managing satellite antenna access according to some embodiments.

[0108] At 1002, during a contact session (e.g., a satellite antenna access time slot reserved for a client), the satellite antenna ground station service can transmit data to / from a client satellite via an assigned satellite antenna at a ground station of the satellite antenna ground station service.

[0109] At 1004, the satellite antenna ground station service can determine whether a failure or other problem has caused data transmission between the assigned satellite antenna and the satellite of the client to be lost. If a data transmission failure or loss is detected, at 1006 the satellite antenna ground station service can transmit a client reservation to a backup satellite antenna and continue transmitting data to / from the client satellite via the backup satellite antenna. In some embodiments, each ground station can include at least two satellite antennas and associated hardware for redundancy.

[0110] At 1008, the satellite antenna ground station service can determine whether there is remaining time during the reserved time slot. If there is remaining time, the satellite antenna ground station service can continue transmitting data at 1002. If there is no time remaining in the reserved time slot, at 1010 the satellite antenna ground station service can close access to the ground station gateway (e.g., gateway 438 or 440) for the client, and at 1012 the satellite antenna ground station service can provide an access window to another client of the satellite antenna ground station service via the gateway for another time slot reserved for another client at the ground station.

[0111] Figure 11 is a high level flow diagram illustrating various methods and techniques for managing satellite antenna access requests involving multiple satellite antennas according to some embodiments.

[0112] In some embodiments, the satellite antenna ground station service can coordinate contact sessions between multiple satellite antenna ground stations. For example, as a satellite orbits the earth, the satellite antenna ground station service can provide sequential contact sessions at ground stations in different locations following a satellite orbital pattern. For example, when a satellite moves out of range of a first ground station, a contact session at the first ground station can end and a new contact session at another ground station can begin, where the satellite is sequentially entering range of the other ground station after leaving range of the first ground station. In such cases, data downlinked from the satellite can be pre-sent through a provider network to a data center associated with the other ground station, so that the data downlinked from the satellite can be merged at the data center associated with the other ground station via the first ground station and the other ground station.

[0113] For example, at 1102, a satellite antenna ground station service can receive a satellite antenna request from a client of the satellite antenna ground station service to transfer data from a satellite of the client to a premises of the client or a storage location included in a provider network that includes the satellite antenna ground station service.

[0114] At 1104, a scheduler of the satellite antenna ground station service can determine whether a duration of the access request or an amount of data to be transferred indicated in the access request exceeds a respective duration of an access window at a ground station of the satellite antenna ground station service or whether the amount of data to be transferred exceeds an amount of data that can be transferred during a single access window at the ground station of the satellite antenna ground station service. If the answer is no, then at 1106, the scheduler schedules a satellite antenna access time slot for the client at a single ground station of the satellite antenna ground station service.

[0115] If the answer to 1104 is yes, then at 1108, 1110, and 1112, the scheduler schedules satellite antenna access time slots at 2 to N ground stations, where the number “N” is a number of sequential contact sessions at different ground stations required to satisfy the access window duration or data transfer amount of the client request.

[0116] At 1114, the satellite antenna ground station service then provides the sequential contact sessions at the satellite antennas of the multiple ground stations to satisfy the request of the client.

[0117] Figure 12 FIG. 12 is a block diagram illustrating an example computing system, in accordance with some embodiments. For example, in different embodiments, the computer system 1200 can be configured to implement a satellite antenna ground station service, a storage and / or computing node of a provider network, a data store, and / or various components of a client. The computer system 1200 can be any of a variety of types of devices, including, but not limited to, a personal computer system, desktop computer, laptop or notebook computer, mainframe computer system, handheld computer, workstation, network computer, a consumer device, application server, storage device, a telephone, mobile telephone, or generally any type of computing device.

[0118] The computer system 1200 includes one or more processors 1210 (any of which can include multiple cores, which can be single- or multi-threaded) coupled to a system memory 1220 via an input / output (I / O) interface 1230. The computer system 1200 further includes a network interface 1240 coupled to the I / O interface 1230. In various embodiments, the computer system 1200 can be a uniprocessor system including one processor 1210, or a multiprocessor system including several processors 1210 (e.g., two, four, eight, or other suitable number). The processors 1210 can be any suitable processors capable of executing instructions. For example, in various embodiments, the processors 1210 can be general- or embedded- purpose 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 the processors 1210 can typically, but need not, implement the same ISA. The computer system 1200 also includes one or more network communication devices (e.g., network interface 1240) for communicating with other systems and / or components over a communication network (e.g., the Internet, a LAN, etc.).

[0119] In the illustrated embodiment, the computer system 1200 also includes one or more persistent storage devices 1260 and / or one or more I / O devices 1280. In various embodiments, the persistent storage devices 1260 can correspond to disk drives, tape drives, solid-state memory, other mass storage devices, block-based storage devices, or any other persistent storage devices. The computer system 1200 (or a distributed application or operating system operating thereon) can store instructions and / or data in the persistent storage devices 1260 as needed, and can retrieve stored instructions and / or data as needed. For example, in some embodiments, the computer system 1200 can host a storage system server node, and the persistent storage 1260 can include an SSD attached to the server node.

[0120] Computer system 1200 includes one or more system memories 1220 configured to store instructions and data accessible to processor(s) 1210. In various embodiments, system memory 1220 can be implemented using any suitable memory technology, such as one or more of cache, static random access memory (SRAM), DRAM, RDRAM, EDO RAM, DDR 10 RAM, synchronous dynamic RAM (SDRAM), Rambus RAM, EEPROM, nonvolatile / Flash-type memory, or any other type of memory. System memory 1220 can contain program instructions 1225 that are executable by processor(s) 1210 to implement the methods and techniques described herein. In various embodiments, program instructions 1225 can be encoded in platform-native binary, in any interpreted language such as Java™ byte-code, or in any other language, such as C / C++, Java™, etc., or any combination thereof. For example, in the illustrated embodiment, program instructions 1225 include program instructions executable to implement the functionality of a resource host. In some embodiments, program instructions 1225 can implement multiple separate clients, nodes, and / or other components.

[0121] In some embodiments, program instructions 1225 can include instructions executable to implement an operating system (not shown), which can be any of a variety of operating systems, such as UNIX, LINUX, Solaris™, Mac OS™, Windows™, and the like. Any or all of program instructions 1225 can be provided as a computer program product, or software, that can include a non-transitory computer-readable storage medium having stored thereon instructions that can be used to program a computer system (or other electronic device) to perform a process according to various embodiments. The non-transitory computer-readable storage medium can include any mechanism for storing information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). Generally, a computer accessible medium can include a computer-readable storage medium or memory media such as magnetic or optical media, e.g., disk or DVD / CD-ROM, coupled to a computer system via I / O interface 1230. The non-transitory computer-readable storage medium can also include any volatile or non-volatile media such as RAM (e.g., SDRAM, DDR SDRAM, RDRAM, SRAM, etc.), ROM, etc., that can be included in some embodiments of computer system 1200 as system memory 1220 or another type of memory. In other embodiments, program instructions can be conveyed as propagated signals, e.g., carrier waves, infrared signals, digital signals, etc., via a communication medium, e.g., a network and / or a wireless link, as can be implemented via network interface 1240.

[0122] In some embodiments, system memory 1220 can include a data store 1245 that can be configured as described herein. Generally, system memory 1220 (e.g., data store 1245 within system memory 1220), persistent storage 1260, and / or remote storage 1270 can store data blocks, copies of data blocks, metadata and / or status associated with data blocks, configuration information, and / or any other information that can be used to implement the methods and techniques described herein.

[0123] In one embodiment, I / O interface 1230 can be configured to coordinate I / O traffic between processor 1210, system memory 1220, and any peripheral devices in the system. In some embodiments, I / O interface 1230 can perform any necessary protocol, timing or other data transformations to convert data signals from one component (e.g., system memory 1220) into a format suitable for use by another component (e.g., processor 1210). In some embodiments, I / O interface 1230 can 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, I / O interface 1230 can include an interface to one or more additional types of peripheral buses.

[0124] For example, network interface 1240 can be configured to allow data to be exchanged between computer system 1200 and other devices attached to a network (e.g., other computer systems 1290) via a wired or wireless medium. In addition, network interface 1240 can be configured to allow communication between computer system 1200 and various I / O devices 1250 and / or remote storage devices 1270. In some embodiments, input / output devices 1250 can include one or more display terminals, keyboards, keypads, touchpads, scanning devices, voice or optical recognition devices, or any other devices suitable for entering or retrieving data. Multiple input / output devices 1250 can be present in computer system 1200, or can be distributed on various nodes of a distributed system including computer system 1200. In some embodiments, similar input / output devices can be separate from computer system 1200, and can interact with one or more nodes of a distributed system including computer system 1200 through a wired or wireless connection, such as over network interface 1240. Network interface 1240 can typically support one or more wireless networking protocols (e.g., Wi-Fi / IEEE 802.11 or another wireless networking standard). However, in various embodiments, network interface 1240 can support communication via any suitable wired or wireless general data networks. For example, network interface 1240 can provide communication through Figure 12more, fewer, or different components (e.g., displays, video cards, audio cards, peripherals, other network interfaces, such as ATM interfaces, Ethernet interfaces, frame relay interfaces, etc.)

[0125] It should be noted that any of the distributed system embodiments described herein, or any of their components, can be implemented as one or more network-based services. For example, a compute cluster within a computing service can present compute and / or storage services to clients and / or other types of services employing the distributed computing systems described herein as network-based services. In some embodiments, a network-based service can be implemented by a software and / or hardware system designed to support machine-to-machine interoperation over a network. A network-based service can have an interface described in a machine-processable format, such as Web Services Description Language (WSDL). Other systems can interact with the network-based service based on the description of the interface of the network-based service provided in the WSDL. For example, the network-based service can define various operations that other systems can invoke, and can define a particular application programming interface (API) that other systems are expected to conform to when requesting the various operations.

[0126] In various embodiments, a network-based service can be requested or invoked by using a message that includes parameters and / or data associated with the network-based service request. Such messages can be formatted according to a particular markup language, such as extensible Markup Language (XML), and / or can be encapsulated using a protocol, such as Simple Object Access Protocol (SOAP). To perform a network-based service request, a network-based service client can assemble a message that includes the request using an Internet-based application layer transport protocol, such as Hypertext Transfer Protocol (HTTP), and address the message to an addressable endpoint (e.g., a Uniform Resource Locator (URL)) corresponding to the network-based service.

[0127] In some embodiments, a network-based service can be implemented using Representational State Transfer ("RESTful") techniques rather than message-based techniques. For example, a network-based service implemented according to RESTful techniques can be invoked by parameters included within an HTTP method, such as PUT, GET, or DELETE, rather than encapsulated within a SOAP message.

[0128] Embodiments of the present disclosure can be described in terms of the following clauses:

[0129] 1. A service provider network comprising:

[0130] a plurality of data centers located in different geographic regions;

[0131] a plurality of satellite antenna ground stations, wherein respective ones of the satellite antenna ground stations are located locally and connected to corresponding ones of the data centers in the different geographic regions; and

[0132] one or more computing devices configured to implement a multi-tenant scheduling service configured to:

[0133] receive satellite antenna ground station access requests from a plurality of clients of a service provider network; and

[0134] schedule satellite antenna ground station access time slot reservations for the clients on respective ones of the satellite antenna ground stations,

[0135] wherein the satellite antenna ground stations are integrated into the service provider network such that data received via one of the ground stations is available for use by cloud computing services of the service provider network.

[0136] 2. The service provider network of clause 1, wherein the service provider network implements:

[0137] a computing service;

[0138] a data storage service;

[0139] a machine learning service; or

[0140] a data analytics service,

[0141] wherein the plurality of satellite antenna ground stations are connected to the plurality of data centers such that data received from satellites via one or more of the satellite antenna ground stations is available for processing by the computing service, the data storage service, the machine learning service, or the data analytics service.

[0142] 3. The service provider network of clause 1 or 2, wherein at least two satellite antennas are located in each of the different geographic regions; and

[0143] wherein the multi-tenant scheduling service is further configured to:

[0144] in response to a failure associated with a first satellite antenna in a given geographic region, during the satellite antenna ground station access time slot reservations, transfer client satellite contact from being performed via the first satellite antenna in the given geographic region to being performed via another satellite antenna in the given geographic region.

[0145] 4. The service provider network of any of clauses 1 to 3, wherein the multi-tenant scheduling service is further configured to:

[0146] reserving a first satellite antenna ground station access time slot reservation for a given client of the plurality of clients at a first satellite antenna ground station in a first geographic region; and

[0147] reserving a second satellite antenna ground station access time slot reservation for the given client at a second satellite antenna ground station in a second geographic region,

[0148] wherein the first and second satellite antenna ground station access time slot reservations are reserved such that a satellite of the given client is reachable by the first satellite antenna ground station during the first satellite antenna access time slot reservation and subsequently is reachable by the second satellite antenna ground station during the second satellite antenna ground station access time slot reservation.

[0149] 5. A multi-tenant ground station service, comprising:

[0150] a plurality of satellite antenna ground stations; and

[0151] one or more computing devices configured to implement a multi-tenant scheduling service configured to:

[0152] receive a ground station access request from a client of a plurality of clients of the multi-tenant ground station service; and

[0153] schedule a ground station access time slot reservation for the client at a respective ground station of a plurality of ground stations,

[0154] wherein the multi-tenant ground station service is integrated into a provider network that provides cloud computing services to the plurality of clients.

[0155] 6. The multi-tenant ground station service of clause 5, further comprising:

[0156] a plurality of data centers co-located with respective ones of the satellite antenna ground stations.

[0157] 7. The multi-tenant ground station service of clause 5 or 6, wherein the multi- tenant ground station service is configured to:

[0158] implement a satellite command and control instance on a virtualized computing instance, wherein the virtualized computing instance is provisioned to the client prior to the ground station access time slot reservation via a computing service implemented using computing devices co-located with respective ones of the satellite antenna ground stations.

[0159] 8. The multi-tenant ground station service of any of clauses 5 to 7, wherein the multi-tenant ground station service is configured to:

[0160] implementing a satellite data processing instance on a virtualized compute instance to process data received from a satellite during a ground station access time slot, wherein the virtualized compute instance is provisioned to a client prior to the ground station access time slot reservation via a computing service implemented using computing devices of a plurality of data centers co-located with respective ones of a plurality of satellite antenna ground stations.

[0161] 9. The multi-tenant ground station service of any of clauses 6-8, wherein the computing devices of the plurality of data centers are configured to implement:

[0162] a computing service;

[0163] a data storage service;

[0164] a data analytics service;

[0165] a database service; or

[0166] a machine learning service, and

[0167] wherein the plurality of satellite antenna ground stations are connected to the plurality of data centers such that data received from a satellite via one or more of the satellite antenna ground stations is available to the computing service, the data storage service, the data analytics service, the database service, or the machine learning service.

[0168] 10. The multi-tenant ground station service of any of clauses 5-9, wherein one or more computing devices of the multi-tenant ground station service are configured to:

[0169] implement a web-based graphical user interface to receive ground station access requests from clients; or

[0170] implement an application programming interface (API) to receive ground station access requests from clients.

[0171] 11. The multi-tenant ground station service of any of clauses 5-10, wherein the multi- tenant ground station service is configured to manage antenna hardware control of a satellite antenna ground station assigned to a client on behalf of the client during a ground station access time slot assigned to the client.

[0172] 12. The multi-tenant ground station service of any of clauses 5-10, wherein the multi- tenant ground station service is configured to communicate with low earth orbit (LEO) satellites via S-band frequencies, with LEO satellites via X-band frequencies, with geosynchronous orbit (GEO) satellites via C-band frequencies, with GEO satellites via Ku-band frequencies, or with GEO satellites via Ka-band frequencies via the plurality of satellite antenna ground stations.

[0173] 13. The multi-tenant ground station service of any of clauses 5-10, wherein:

[0174] the ground station access request indicates a time window of a request to access a satellite of the client; and

[0175] to schedule the ground station time slot reservation, the multi-tenant scheduling service allocates one or more of the plurality of satellite antenna ground stations to the client during the time window of the request.

[0176] 14. The multi-tenant ground station service of clause 13, wherein:

[0177] the ground station access request indicates an amount of data to be transmitted to or from a satellite of the client; and

[0178] to schedule the ground station time slot reservation, the multi-tenant scheduling service allocates one or more satellite antennas at one or more of the plurality of satellite antenna ground stations to the client during the one or more time windows such that the requested amount of data indicated in the ground station access request is transmitted to or from a satellite of the client.

[0179] 15. A method comprising:

[0180] providing a user interface to a client for a multi-tenant satellite antenna ground station service integrated into a provider network providing cloud computing services;

[0181] receiving, via the user interface, a ground station access request from the client; and

[0182] scheduling a ground station access time slot for the client on one of a plurality of satellite antenna ground stations of the multi-tenant satellite antenna ground station service integrated into the provider network providing cloud computing services.

[0183] 16. The method of clause 15, further comprising:

[0184] receiving, via the user interface, another ground station access request from the client; and

[0185] scheduling another ground station access time slot for the client,

[0186] wherein a different number of satellite antennas are allocated to the client for the ground station access time slot and the other ground station access time slot based on different respective data transmission needs of the client for the ground station access time slot and the other ground station access time slot.

[0187] 17. The method of clause 15 or 16, wherein the serving the user interface to the multi-tenant satellite antenna ground station service includes serving a web-based graphical user interface to the client for the multi-tenant satellite antenna ground station service.

[0188] 18. The method of any one of clauses 15-17, further comprising:

[0189] receiving, via the user interface, a plurality of other ground station access requests from other clients of the multi-tenant satellite antenna ground station service;

[0190] matching time slots of the request included in the ground station access request and other time slots of the other ground station access requests included in the other ground station access requests to available time slots on the plurality of satellite antenna ground stations; and

[0191] scheduling, for the other clients, other ground station access time slots on one or more of the plurality of satellite antenna ground stations of the multi-tenant satellite antenna ground station service during respective ones of the matched available time slots, wherein the scheduled ground station access time slot for the client is scheduled during a respective one of the matched available time slots that matches the requested time slot.

[0192] 19. The method of any one of clauses 15-18, further comprising:

[0193] providing access to a satellite antenna of the satellite antenna ground station during the scheduled ground station access time slot; and

[0194] in response to a failure associated with the satellite antenna during the scheduled ground station access time slot, providing access to another satellite antenna of the satellite antenna ground station for the remaining portion of the scheduled ground station access time slot.

[0195] 20. The method of any one of clauses 15-19, further comprising:

[0196] providing access to a respective one of the satellite antenna ground stations during the scheduled ground station access time slot when the client’s satellite is within range to communicate with the respective one of the satellite antenna ground stations; and

[0197] providing access to another respective one of the satellite antenna ground stations during a sequentially scheduled ground station access time slot after the client’s satellite is not within range to communicate with the respective one of the satellite antenna ground stations.

[0198] While embodiments have been described in considerable detail herein, many variations and modifications will now become apparent to those skilled in the art. It is therefore contemplated to append to this description as appended claims so as to encompass all such variations and modifications as falling within the scope of the present disclosure. Accordingly, the description is to be construed as illustrative only and is for the purpose of teaching those skilled in the art the general manner of carrying out the present disclosure. It is the intent of the inventors to be entitled to all changes and modifications that come within the spirit and scope of the disclosure.

Claims

1. A satellite antenna ground station service system, comprising: Multiple data centers located in different geographical regions; Multiple satellite antenna ground stations, wherein each of the satellite antenna ground stations is connected to a corresponding data center in the data center in a different geographical region; and One or more computing devices, configured to provide a user interface for the satellite antenna ground station service, the user interface being configured to: Receive satellite identification information of the satellites of the customers served by the satellite antenna ground station; Provide a scheduling interface that allows the client to schedule communication with the client's satellite; as well as A data processing interface is provided that allows the client to specify one or more parameters for processing signals received from the client's satellite during scheduled communications. The one or more computing devices are further configured to: Scheduling two or more communications for the customer’s satellite, wherein the two or more communications to be scheduled are to be performed using two or more satellite antenna ground stations; as well as The scheduled connections are orchestrated via the two or more satellite antenna ground stations using one or more parameters specified by the customer for signal processing.

2. The satellite antenna ground station service system of claim 1, wherein the plurality of data centers includes computing devices configured to implement cloud-based services, the cloud-based services being configured to store data obtained by processing signals received from the satellite from the customer during a scheduled contact.

3. The satellite antenna ground station service system according to claim 1 or 2, wherein the satellite identification information of the customer's satellite includes: NORAD catalog number; NORAD ID; NASA catalog number; or USSPACECOM object number.

4. The satellite antenna ground station service system according to any one of claims 1 to 3, wherein the scheduling interface is configured to enable the customer to select: The satellite antenna ground station to be used for the aforementioned connection; and The time of the contact.

5. The satellite antenna ground station service system according to any one of claims 1 to 4, wherein the data processing interface is configured to enable the customer to specify: One or more parameters for a software-defined modem; or One or more parameters for a software-defined radio device The software-defined modem or the software-defined radio device is configured to process signals received from the customer's satellite during a scheduled contact.

6. The satellite antenna ground station service system of claim 5, wherein the data center or satellite antenna ground station includes a radio frequency to digital converter configured to convert analog signals or analog data received from the satellite from the customer into digital data.

7. The satellite antenna ground station service system of claim 6, wherein the satellite antenna ground station service is further configured to convert data received from the customer's satellite via the one or more satellite antenna ground stations into digital data formatted according to Internet Protocol (IP) format.

8. The satellite antenna ground station service system according to any one of claims 1 to 7, wherein the satellite antenna ground station service is further configured to provide: A satellite command interface that enables telemetry, tracking, and control of the satellite for the client during the communication.

9. The satellite antenna ground station service system according to any one of claims 1 to 8, wherein the data received during the communication is Earth observation data.

10. The satellite antenna ground station service system according to any one of claims 1 to 8, wherein the data sent to or received from the customer's satellite during the communication is streaming media content.

11. The satellite antenna ground station service system of claim 10, further comprising a provider network, wherein the data center is included in the provider network, and wherein the provider network is configured to distribute the streaming media content to a plurality of media content consumers at least in part via the provider network.

12. The satellite antenna ground station service system according to any one of claims 1 to 11, further comprising a provider network, wherein the data center is included in the provider network, and wherein the provider network implements: Computing services; Data storage services; Machine learning services; or Data analytics services The plurality of satellite antenna ground stations are connected to the plurality of data centers such that data received from the satellite via one or more of the satellite antenna ground stations can be used for processing by the computing service, the data storage service, the machine learning service, or the data analysis service.

13. The satellite antenna ground station service system according to any one of claims 1 to 12, wherein the satellite antenna ground station is configured to contact low Earth orbit (LEO) satellites.

14. The satellite antenna ground station service system according to any one of claims 1 to 13, wherein the satellite antenna ground station is configured to connect to a medium Earth orbit (MEO) satellite.

15. The satellite antenna ground station service system according to any one of claims 1 to 14, wherein the satellite antenna ground station is configured to contact a geostationary orbit (GEO) satellite.

16. The satellite antenna ground station service system according to any one of claims 1 to 15, wherein the satellite antenna ground station service is configured to: Satellite command and control instances are implemented on virtualized computing instances, wherein the virtualized computing instances are provided prior to ground station access time slot reservations via computing services implemented using computing devices in the plurality of data centers co-located with the respective satellite antenna ground stations.

17. The satellite antenna ground station service system according to any one of claims 1 to 16, wherein the satellite antenna ground station service is configured to: A satellite data processing instance is implemented on a virtualized computing instance to process data received from the satellite during a ground station access time slot, wherein the virtualized computing instance is provided via a computing service prior to the ground station access time slot reservation, the computing service being implemented using computing devices located in one location with the corresponding satellite antenna ground station in the plurality of data centers.

18. The satellite antenna ground station service system according to any one of claims 1 to 17, wherein the satellite antenna ground station service is configured to: A machine image is provided for implementing a data processing instance or a satellite command and control instance on a virtualized computing instance of a virtualized computing service that includes the provider network of the satellite antenna ground station service.

19. A non-transitory computer-readable medium storing one or more program instructions, which, when executed on or across one or more processors, cause the one or more processors to: Implement a user interface for satellite antenna ground station services, the user interface being configured as follows: Receive satellite identification information of the satellites of the customers served by the satellite antenna ground station; Provide a scheduling interface that allows the client to schedule communication with the client's satellite; Provide a data processing interface that allows the client to specify one or more parameters for processing signals received from the client's satellite during a scheduled contact; as well as Scheduling two or more communications for the customer’s satellite, wherein the two or more communications to be scheduled are to be performed using two or more satellite antenna ground stations.

20. A method for providing satellite antenna ground station services, comprising: Provides a user interface for the satellite antenna ground station service of the provider network, wherein the user interface is configured to: Receive satellite identification information of the satellites of the customers served by the satellite antenna ground station; Provide a scheduling interface that allows the client to schedule communication with the client's satellite; as well as Provide a data processing interface that allows the client to specify one or more parameters for processing signals received from the client's satellite during a scheduled contact; Scheduling two or more communications for the customer’s satellite, wherein the two or more communications are to be performed using two or more satellite antenna ground stations; as well as The scheduled connections are orchestrated via the two or more satellite antenna ground stations using one or more parameters specified by the client via the data processing interface.

Images